How Job Management Manager Works › Job Database Listing › Specifying a Job › Uniqueness of a Job Name and Number

Uniqueness of a Job Name and Number

• Job names are unique within a specific user’s set of jobs. For example, if user Doe and user Smith each own jobs named COPY_IT, the manager treats them as two separate jobs.
• Job numbers are unique within an OpenVMS Cluster.

Note: The manager assigns each job in the database a unique job number. For this reason, CA Technologies does not support the use of numerical job names.

Important! Never use the statement "READ SYS$COMMAND <symbol>" in any step of a Job Management Manager job (pre, main, or post). During the execution of Job Management Manager jobs, SYS$COMMAND points to the SCHEDULER$SHELL command procedure. The effect of the READ statement is to read a command from the SCHEDULER$SHELL.COM file and assign it to the symbol. When the user command finishes, the next line in the SCHEDULER$SHELL should be "EXIT $STATUS." However, if this line has been read and assigned to the user symbol, the file pointer now points to the next line in SCHEDULER$SHELL.COM and the EXIT command is skipped, causing the job run process to start again.