Technical data

Using OpenVMS System Management Utilities and Tools

2.1 Understanding OpenVMS System Management Tools

When you execute this command procedure with the command @GO_WORK, you

set your default directory to [PERRY.WORK] and display a list of ﬁles in that

directory.

With complex command procedures, you can use DCL instead of a high-

level programming language. For more information about creating command

procedures, refer to the OpenVMS User’s Manual.

2.1.4.1 Executing Command Procedures in Batch Mode

You can execute command procedures in batch mode by submitting the

procedure to a batch queue. When resources are available, the system creates

a batch process to execute the commands in the procedure. Usually, processes

running in batch mode execute at a lower process priority to avoid competing

with interactive users for system resources.

You might execute a command procedure in batch mode for the following reasons:

• To automate a task

• To process work at a lower scheduling priority, so as not to compete with

interactive users for system resources

• To perform a task during off hours, such as at night or on weekends

• To allow an operation to continue without having a terminal logged in,

thereby increasing the security of the system

A batch-oriented command procedure can include a command to resubmit itself to

a batch queue, thereby repetitively performing the task with no user intervention.

For example, you might create a batch-oriented command procedure to run the

Analyze/Disk_Structure utility (ANALYZE/DISK_STRUCTURE) to report disk

errors. If you include a command to resubmit the procedure to a batch queue,

the procedure will automatically execute when scheduled, unless errors cause the

procedure to fail. The following example is a simple command procedure, named

SYSTEM-DAILY.COM:

$ SET NOON

$! Resubmit this procedure to run again tomorrow.

$ SUBMIT/KEEP/NOPRINT/QUEUE=SYS$BATCH/AFTER="TOMORROW+1:00"/USER=SYSTEM -

SYS$MANAGER:SYSTEM-DAILY.COM;

$! Purge the log files

$ PURGE/KEEP=7 SYS$MANAGER:SYSTEM-DAILY.LOG

$! Analyze public disks

$ ANALYZE/DISK/LIST=SYS$MANAGER:WORK1.LIS; WORK1:

$ ANALYZE/DISK/LIST=SYS$MANAGER:WORK2.LIS; WORK2:

$! Print listings

$ PRINT/QUEUE=SYS$PRINT SYS$MANAGER:WORK1.LIS;,SYS$MANAGER:WORK2.LIS;

$ EXIT

2–6 Using OpenVMS System Management Utilities and Tools