HP OpenVMS Systems Documentation

OpenVMS User's Manual

Once a job has been entered in a batch job queue, you can monitor its status with the SHOW ENTRY command or the SHOW QUEUE command. If you have no jobs in the queue, the system displays the following message:

$  SHOW QUEUE BOSTON_BATCH
Batch queue BOSTON_BATCH, on BOSTON::

To see complete information on your jobs, use the /FULL qualifier with the SHOW ENTRY or SHOW QUEUE command. To see the status of other jobs in the queue, use the SHOW QUEUE/ALL command.

In the following example, entry number 999 is displayed:

$ SUBMIT EXCHAN.DAT
Job EXCHAN (queue SYS$BATCH entry 999) started on SYS$BATCH
$ SHOW ENTRY 999

  Entry  Jobname         Username     Blocks  Status
  -----  -------         --------     ------  ------
    999  EXCHAN          BLASS             3  Executing
         On batch queue SYS$BATCH

$ SUBMIT/NOPRINTER/PARAMETER=STATS.DAT UPDATE
Job UPDATE (queue SYS$BATCH entry 1080) started on BOSTON_BATCH
$ SHOW QUEUE BOSTON_BATCH
Batch queue BOSTON_BATCH on BOSTON::

  Entry  Jobname         Username     Blocks  Status
  -----  -------         --------     ------  ------
   1080  UPDATE          ODONNELL         36  Executing

In the next example, the /FULL qualifier displays statistics about BOSTON_BATCH and characteristics associated with job number 999:

$ SHOW ENTRY/FULL 999

  Entry  Jobname         Username     Blocks  Status
  -----  -------         --------     ------  ------
    999  EXCHAN          BLASS             3  Executing
         On batch queue BOSTON_BATCH
         Submitted 11-DEC-1999 13:12 /PRIORITY=100
         WRKD:[BLASS]EXCHAN.DAT;3

$ SHOW QUEUE/FULL BOSTON_BATCH
Batch queue BOSTON_BATCH, on BOSTON::
    /BASE_PRIORITY=3 /JOB_LIMIT=5 /OWNER=[EXEC] /PROTECTION=(S:E,O:D,G:R,W:W)

  Entry  Jobname         Username     Blocks  Status
  -----  -------         --------     ------  ------
   1080  UPDATE          ODONNELL         36  Executing
    Submitted 11-DEC-1999 10:46 /KEEP /PARAM=("STATS.DAT") /NOPRINTER /PRIO=4
    _BOSTON$DQA2:[ODONNELL]TEMP.COM;1 (executing)

In the following example, the SHOW QUEUE/ALL command is used to display all jobs in the BOSTON_BATCH queue:

$ SHOW QUEUE/ALL BOSTON_BATCH
Batch queue BOSTON_BATCH on BOSTON::

  Entry  Jobname         Username             Status
  -----  -------         --------             ------
    923  no privilege                         Executing
    939  no privilege                         Holding until 11-DEC-1999 19:00
   1080  UPDATE          ODONNELL             Executing

Note that, unless you are a privileged user, your information is limited to jobs submitted under your account.

16.5.7 Deleting and Stopping Batch Jobs

You can delete batch jobs before or during execution. To delete an entry that is pending or already executing in a batch queue, use the DELETE/ENTRY command. You need special privileges to delete a job that you did not submit. When a job terminates as a result of a DELETE/ENTRY command, the log file is neither printed nor deleted from your directory.

When you terminate a job using the DELETE/ENTRY command, it is handled as an abnormal termination because the operating system's normal job termination activity is preempted. As a result, the batch job log does not, for example, contain the standard logout message that summarizes job time and accounting information. Termination that results either from an explicit EXIT command or STOP command or the implicit execution of either of these commands (as the result of the current ON condition), however, is considered normal termination. The operating system performs proper rundown and accounting procedures after a normal termination.

The following command deletes the job entry 210 in SYS$BATCH:

$ DELETE/ENTRY=210 SYS$BATCH

If the system fails while your batch job is executing, your job does not complete. When the system recovers and the queue is restarted, your job is aborted and the next job in the queue is executed. However, by specifying the /RESTART qualifier when you submit a batch job, you indicate that the system should reexecute your job if the system fails before the job is finished.

By default, a batch job is reexecuted beginning with the first line. See Chapter 13 and Chapter 14 for more information about symbols you can add to your command procedures to specify a different restarting point.

In addition to restarting a job after a system failure, you can also restart a job after you explicitly stop the job. To stop a job and then restart it on the same or a different queue, use the STOP/QUEUE/REQUEUE/ENTRY command.

The command shown in this example stops job 212 on SYS$BATCH and requeues it on SYS$BATCH.

$ STOP/QUEUE/REQUEUE/ENTRY=212 SYS$BATCH

To enter this command, job 212 must have been submitted using the /RESTART qualifier to the SUBMIT command. When the batch job executes for the second time, the system uses the global symbol BATCH$RESTART to determine where to begin executing the job.

16.5.9 Synchronizing Batch Job Execution

You can use the SYNCHRONIZE and WAIT commands within a command procedure to place the procedure in a wait state. The SYNCHRONIZE command causes the procedure to wait for the completion of a specified job. The WAIT command causes the procedure to wait for a specified period of time to elapse.

If you specify a job name with the SYNCHRONIZE command, note that the jobs to be synchronized must be associated with your user name. (A job is associated with the user name of the process that submits it.) To synchronize jobs for different users, you must use the /ENTRY qualifier with the SYNCHRONIZE command to specify the job entry number.

In the following example, if two jobs are submitted concurrently to perform cooperative functions, one job can contain the following command:

$ SYNCHRONIZE BATCH25

After this command is executed, the command procedure cannot continue execution until the job identified by the job name BATCH25 completes execution.

This SYNCHRONIZE command places the current command procedure in a wait state until job 454 completes:

$ SYNCHRONIZE/ENTRY=454

Figure 16-1 is an example of command procedures that are submitted for concurrent execution but must be synchronized for proper execution. Each procedure compiles a large source program.

Figure 16-1 Synchronizing Batch Job Execution

As you examine the example, note the following:

1. Individual SUBMIT commands are required to submit two separate jobs. The first process is created.
2. After the FORTRAN command is executed, the SYNCHRONIZE command is executed. If job 315 is either current or pending, job 314 will not execute the next command.
3. If job 315 has completed execution, job 314 continues with the next command.

The WAIT command is useful for command procedures that must have access to a shared system resource such as a disk or tape drive.

The following example shows a procedure that requests the allocation of a tape drive:

$ TRY:
$      ALLOCATE DM: RK:
$      IF $STATUS THEN GOTO OKAY
$      WAIT 00:05
$      GOTO TRY
$ OKAY:
$ REQUEST/REPLY/TO=DISKS -
     "Please mount BACK_UP_GMB on ''F$TRNLNM("RK")'"
   .
   .
   .

If the WAIT command does not complete successfully, the procedure places itself in a wait state. After a 5-minute interval, it retries the request.

The IF command following the ALLOCATE request checks the value of $STATUS. If the value of $STATUS indicates successful completion, the command procedure continues. Otherwise, the procedure executes the WAIT command; the WAIT command specifies a time interval of five minutes. After waiting five minutes, the next command, GOTO, is executed and the request is repeated. This procedure continues looping and attempting to allocate a device until it succeeds or until the batch job is deleted or stopped.

The DEC Multinational Character Set (MCS) consists of a definition of the characters identified by hexadecimal values 00 through FF, inclusive, that was created and used by Digital Equipment Corporation. The DEC MCS is divided into two parts, the ASCII 7-bit character set (identified by hexadecimal values 00 through 7F, inclusive), and the set of 8-bit characters identified by hexadecimal values 80 through FF, inclusive. The DEC MCS is familiar to most users of software created and sold by DIGITAL.

The Unicode Standard Character Set (UCS-2) is a definition, by The Unicode Consortium, of the set of 16-bit characters that can be identified by hexadecimal values 0000 through FFFF, inclusive.

The ISO Latin-1 character set is the UCS-2 definition of the 8-bit characters identified by hexadecimal values 00 through FF, inclusive. The ISO Latin-1 character set definition differs slightly from the DEC MCS definition of the hexadecimal values 80 through FF.

Table A-1 contains the DEC Multinational Character Set (MCS). Table A-1 indicates the characters that differ between the two character sets, and Figure A-1 shows the differing characters.

Table A-2 lists the characters in the DCL character set.

See The Unicode Standard, published by The Unicode Consortium, for details about the Unicode (UCS-2) character set.

Figure A-1 Differences Between DEC Multinational Character Set and ISO Latin-1 Character Set