Monitoring Jobs

Use these procedures to check the status of jobs that have been submitted. You can view the status of jobs through the Lawson Portal Job Schedule form or through the Lawson Interface Desktop (LID) Job Scheduler form. In addition, if you submitted a job through the Job Submission utility (jqsubmit) with the -n option (in order to print the job number), you can review the status of a single job by using the jobstatus jobnumber command.

This table shows the statuses that a job can have:

Status Description
Canceled A job that was deleted from the Active Jobs form, or a job that was deleted from the Waiting Jobs form with a status of Hold, Waiting, Waiting On Time, Waiting Recovery, Invalid Params, or Queue Inactive.
Hold A recurring job whose run was bypassed by the Environment this cycle, or a job that was put on hold by a user.
Invalid Params An invalid value was typed for a batch parameter. Before you can resubmit this job, you must either manually delete the job from the Waiting Jobs form, then redefine the job using valid values; or redefine the job using valid values, then change the job status to Waiting.
Needs Recovery The job failed during execution. You must fix the problem causing the program to stop before you can recover the job.
Normal Completion A job that executed normally.
Queue Inactive The assigned job queue has a queue status of Inactive and cannot run jobs.
Recovery Deleted A job that was deleted from the Waiting Jobs form with a status of Needs Recovery.
Recurring Job Skipped A recurring job that was too late to run.
Waiting The assigned job queue is temporarily full.
Waiting On Time The job's assigned start time has not yet arrived.
Waiting Recovery The job calls the same program as a previously submitted job that needs recovery.
Waiting Step

The step calls a nonconcurrent program that is already running and must wait until that program has executed. Nonconcurrent programs preserve report integrity by preventing two identical programs in the same data area from executing at the same time.

For instructions on defining concurrent and nonconcurrent programs, see Doc for Developers: Application Development Workbench.

Note: If two steps call the same program, but under different data areas or data IDs, the system does not recognize them as being identical and executes them at the same time as if they were different programs.