Job Log Cannot Be Displayed

Procedure

Analysis

Procedure

1) Can job logs be created?

– Perform the following test on all job servers:

– Schedule the job with the target server = name of host on which the job server is running.

For example, you can specify the ABAP program RSPARAM as a step.

Start date of job = ‘Immediate’

– Log on to job server (see Analyzing the Work Processes and System Log of an Application Server)

– Can the job log be displayed (see Analyzing Job Status)?

Yes: End of analysis

No : Continue with step 2

2) Are there unusual entries in the system log?

– Check the system log of the job server (see Analyzing the Work Processes and System Log of an Application Server)

– Are there any ‘permission denied’ entries, which indicate that the job server is not permitted to create a job log?

Yes: Change the access permissions belonging to the directory in which the job log was created, so that the user ID in which the job server is running (generally c11adm) is given read and write permission for the directory

End of analysis

No : Test on the job server whether the TemSe subsystem used for creating job logs is working (see Analyzing Status, Configuration, and Administration Data)

– Does the test report errors?

Yes: You will now find entries in the system log which describe the problem in more detail

End of analysis

No : Continue with step 3

3) Is the job log supposed to be displayed on an application server other than the job server?

– Find out which host the job is to be executed on (see Analyzing Job Status)

– Is the system attempting to display the job log from an application server which is running on a different host than the host on which the job is being executed?

Yes: Do the application server and the job server each have their own global directory?

Yes: - The job log cannot be displayed because the application server cannot access the global directory of the job server. Make the necessary changes so that both servers have the same global directory.

End of analysis

No: Report the problem to SAP

End of Content Area

No comments:

topics