StorageTek 6 manual Utility Control Statements, Control Statements vs. JCL

Utility Control Statements

Control Statements vs. JCL

In contrast to the SCP Job Control Language, the utility control statements are processed only by the executed utility, not by the SCP. They supply all the specific parameters required to execute a utility program (that is, function, cartridge VOLSER, location, etc.).

Briefly then, a control statement consists of a command (indicating the utility function) followed by zero or more parameters in 80 column card-image records. A complete syntax for the statements can be found in Appendix A, “Macros, Control Statements, Utilities, and Commands Syntax Reference” on page 429.

Sample SCP Batch Job File - JCL and Control Statements

The ACS UTIL command used to create a template for invoking three utility functions (first a Scratch Update utility, followed by an Audit utility against one Library Storage Module [LSM], and finally a Volume Report) is:

EXEC ACS UTIL SCRATCH AUDIT VOLRPT

A sample job file might appear as follows:

/JOB	jobname SLUADMIN
/FILE	SLSPRINT	DEV PRNT CLASS A
/FILE	SLSIN	*

* SCRATCH	VOLSER(vol-list)
* AUDIT	ALL APPLY(YES)
* AUDIT	ACS(acsid) LSM(lsmlist) PANEL(panel-list) CAP(capid) -
*	ROW(row-list) COLUMN(col-list) APPLY(YES)
* VOLRPT	ACS(acsid) LSM(lsmlist)
* VOLRPT	VOLSER(vol-list)

Note: It is only necessary to supply those /FILE statements required by the particular utility function(s) being invoked. Utility functions can also share data sets represented by the same /FILE statement.

180VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601