Previous Topic: Frequently Asked Questions

Next Topic: Setting Up Jobs

General Job Management Manager Questions

How can I see what version of Job Management Manager I am running and other information about the manager?

Use the following command:

SCHEDULE> SHOW STATUS

My account UIC has been changed. How do I change or modify the UIC in the manager’s database?

  1. From an account with the CMKRNL privilege (such as the SYSTEM account), enter a command similar to the following:
    	SCHEDULE> MODIFY *=SMITH/USERNAME=SYSTEM
    

    This command line changes ownership of all jobs owned by username Smith to username SYSTEM. Carefully note the list of job numbers that are changed, because SYSTEM may already own a number of jobs. If SYSTEM already has a job with the same name as Smith, Smith will also have to change the job name because job names must be unique within an OpenVMS username. Using a GROUP name is a way of keeping the job separated from jobs that belong to the SYSTEM account.

  2. Enter the following command to display job names and numbers, and be prompted if you want to change the username for each. Answer yes only if the job was originally your job. Those jobs will then have your new UIC.
    	SCHEDULE> MODIFY *=SYSTEM/USERNAME=SMITH/CONFIRM
    

I have a job that runs successfully in batch, but fails in the manager with the following error. What’s the problem?

RMS-E-DEV, Error in device name or inappropriate device type for operation

If you have specified an output file, check to ensure that the file specification is defined at the system level. Output file specifications cannot reference a file using logicals that were set up at the time of login. A logical used to specify an output file must be a system logical.

For example, an output file named SYS$LOGIN:my_job.LOG will fail because it is not defined at the time the process was created. An output file named SYS$MANAGER:my_job.LOG will work successfully because SYS$MANAGER is a system-wide logical.

Why does my stall job (SJOB) run more than once?

If a job is stalled (not started by the time it should have), the designated notification occurs. If the manager "looks" at that job (anytime a job is modified), the manager discovers that the job is stalled and sends the notification again, possibly running any SJOBs again.