Job Was Not Started

Analyzing

Procedure

Step 1:

Does the job have a start date?

Display the job's start date (see Analyzing Job Status )

Does the job have a start date?

• Yes :

  Continue with step 2

• No :

  assign the job a start date

Step 2:

Does the user who scheduled the job have authorization to release jobs?

Display the authorizations that the user has for background processing (see Analyzing Status, Configuration and Administration Data )

Does he have release authorization?

• Yes :

  Continue with step 3

• No :

  either give the user release authorization or have the batch administrator release the job.

Step 3:

Has the start date been reached?

• Yes :

  Is start date = 'after Event'and was the event raised using the sapevt program?

  • Yes :

    Check whether sapevt is working (see Analyzing Problems With Events )

    Is sapevt notifying problems?

    • Yes :

      End of analysis

    • No :

      Continue with step 4

  • No :

    Either wait until the start date is reached or assign the job a new start date (see Analyzing Job Status )

Step 4:

Are the resources necessary for executing the job available?

Call the graphical job monitor

(see Analyzing ABAP Runtime Problems )

Does the job have a target server?

• Yes :

  Is there a free background work process on the target server for the job class requested?

  • Yes :

    Continue with step 5

  • No :

    Either set up a minimum of one background work process on the target server for the job class (see Analyzing Parts of the Runtime Environment , Switching Between Operating Modes ) or remove the target server from the job definition (see Analyzing Job Status )

• No :

  -Is there at least one host with a free background work process for the job class requested?

  • Yes :

    Continue with step 5

  • No :

    Either wait until a background work process becomes free or set up an additional background work process for the job class (see Analyzing Parts of the Runtime Environment , Switching Between Operating Modes )

Step 5:

Can the time-controlled or the event-controlled job scheduler be started?

Does the job have a target server?

• Yes :

  Check the profile parameters of the background processing on the target server (see Analyzing Status, Configuration and Administration Data )

• No :

  Check the profile parameters of the background processing on all job servers (see Analyzing Status, Configuration and Administration Data )

Are errors evident in the log?

• Yes :

  Fix the problems, for example, change the profile parameters and so on.

• No :

  Continue with step 6

Step 6:

Are there unusual entries in the system log?

Does the job have a target server?

• Yes :

  Check the system log on the target server for entries (see Analyzing the Work Processes and System Log of an Application Server )

• No :

  Check the system logs of all job servers for entries (see Analyzing the Work Processes and System Logs )

Did you find entries?

• Yes :

  Can you solve the problem yourself?

  • Yes :

    End of analysis

  • No :

    Continue with step 7

• No :

  Continue with step 7

Step 7:

Record background processing

-Record the component of the background processing which is responsible for starting the job (see Analyzing Parts of the Runtime Environment )

Analyze the trace information

Can you solve the problems yourself?

• Yes :

  End of analysis

• No :

  Send the trace to SAP.