Filter
Top Products
172 VM/HSC 6.0 System Programmer’s Guide
1st ed., 6/30/04 - 312579601
Typical Use of Utilities
A typical use of utility functions might be, for example, to enter some cartridges into the
library through the CAP using the Enter Cartridges utility, add scratch volumes to the CDS
by invoking the Scratch Update utility, and run the Volume Report utility to determine the
physical location of volumes in an LSM. In the following example
• cartridges are being entered through CAP 02
• volumes A1B1C1 through A1B1C4 have been designated as scratch volumes
• the volume report is being run for ACS 01, LSMs 0 and 1.
Note: /PARM MIXED in the JCL specifies mixed characters.
The JCL for invoking these utilities is:
It is only necessary to supply those statements required by the particular utility function(s)
being invoked. Utility functions can also share data sets represented by the same
statement.
For convenience, most utility programs can be run as a single-step batch job submitted to
the ACS service machine, otherwise known as the SCP environment. The submitted file
consists of SCP job control statements which define the files needed to run the
SLUADMIN program, and utility control statements which specify the desired utility
functions and parameters.
Any virtual machine that is authorized for commands to the ACS service machine may
submit library utilities. The file to be submitted is ‘‘punched and spooled’’ to the ACS
service machine’s ‘‘reader.’’ Within the SCP environment, utilities then run as batch jobs
under the SCP. The submitting virtual machine is notified (via console messages) when
the job begins execution, when it ends, and what the final return code is. The resulting
reports are then spooled back to the submitter.
Exceptions to this are these reporting utilities:
• Activities Report utility
• Performance Log Reblocker
• Volume Report.
The Activities Report utility runs in the CMS environment, and the Performance Log
Reblocker runs in either the CMS or MVS environments. Utilities that are run in the CMS
environment require CP LINK read access to the MAINTSTK RUN-disk.
/JOB jobname SLUADMIN
/PARM MIXED
/FILE SLSCNTL DEV vaddr DSN dsname
/FILE SLSPRINT DEV PRNT CLASS A
ENTER CAP(02)
SCRATCH VOLSER(A1B1C1,A1B1C2,A1B1C3,A1B1C4)
VOLRPT ACS(01) LSM(0,1)