Setting Up and Maintaining Jobs › Usage Notes for DB.1, DB.10, and DB.11

Usage Notes for DB.1, DB.10, and DB.11

Many of the fields have predefined default values that are assigned when no value is entered. Once a job has been added, the LIST function returns this panel with all fields containing either the specified data or the defaults taken.

If you want different default values for a job, add a job with the wanted default values give it the name mentioned with the keywords that follow. All future adds, either online or batch, then use that job for default values. If you want some other job name for the defaults pattern job, set the initialization file DBASE statement with the parameter to the correct job name.

• DEFAULTJOB for CPU jobs (default is DEFAULTS)
• DEFAULTXPJ for cross-platform jobs (default is DEFAULTX)
• DEFAULTAG for agent jobs (default is DEFAULTA)

For all job types, you cannot set the UID value with a default job.

To control which jobs are eligible to be marked as LATE, use the LATEPROMPT keyword on the OPTIONS statement in the initialization file. If you specify LATEPROMPT=LATE, jobs that are defined with PROMPT: N never show a status of LATE on the LQ displays (including LREQ, LRDY, LACT, and so on). This setting lets your operations staff concentrate on important jobs when they show up as LATE.

The JOB and JOBL fields have different properties depending on which function has been specified:

• If you add a job definition, you can use both the JOB and JOBL fields simultaneously. The job name and long job name must both be unique. Additionally, if the length of the long job name is fewer than nine characters, it must match the regular job name, ignoring case.
• If you delete a job definition, you can use both the JOB and JOBL fields simultaneously. They must refer to the same job. A discrepancy causes an error message.
• If you update a job definition with both the JOB and JOBL fields in use, the following action occurs. When the JOBL field does not refer to the same job as the JOB field, the long job name for the job in the database is updated to match the field input. The same rules apply as for creating a job with a long job name.
• If a job definition does not have a long job name, you can assign one by completing the JOBL field and using the update function.