Default Job Queues

As delivered, the Lawson Environment has one default job queue, **********. Users of Lawson Security must have access granted explicitly to a job queue, default or otherwise, or else their jobs will not go to any queue.

When a user submits a job, the job is sent to the default job queue in the following circumstances:

• The user did not assign a job queue to the job

• No job queue default was assigned to the application (system code), the data area/data ID to which the job belongs, all programs with the same prefix for their form ID (such as "RW"), or the program form ID itself (such as "RW100").

You set up default job queues for data areas/data IDs, applications, form ID prefixes, or form IDs through the Job Queue Defaults utility (jqdflt). When you assign a default job queue to an application, form ID prefix, or form ID, the Job Scheduler utility schedules all of that item's jobs through the assigned job queue. You can control the job activity on your machine by assigning various system codes, form ID prefixes, and form IDs to different job queue default. For example, setting the default job queue for an application sends all jobs associated with a set of integrated Lawson applications to the same job queue. Default job queues are only valid for Lawson steps (that is, steps that run Lawson batch programs) in a job.

When you submit a multiple-step job whose first step uses a default job queue for a data area/data ID, application, form ID prefix, or form ID, all steps of the job run on the default job queue unless you override the job queue, regardless of a change in the data area/data ID, system code, form ID prefix, or form ID. The system assigns the default job queue when it activates the first step in a job. The system looks for the job queue assignment in the following order: