Previous Topic: Commands Executed by the DMS JCL ProcedureNext Topic: Coding Multiple Action Commands


Data Storage Command Language

The objective of the CA Disk Data Storage Command Language (DSCL) is to provide a rich, comprehensive palette of commands for efficient, common processing of mixtures of non-VSAM data sets and VSAM clusters.

Within a single execution you can report on, back up, archive, delete, expire, move, copy, and/or release idle space in non-VSAM data sets and VSAM clusters. You can do this based on scans of VTOCs of disk volumes, scans of ICF, VSAM or explicitly named OS CVOL catalogs, or the results of a catalog superlocate.

You also have a rich set of criteria to select data sets for and exclude data sets from processing as desired. In addition, a rich set of action parameters lets you control exactly what is done to these data sets.

CA Disk preprocesses your command stream to find any overlapping requests, that is, those that request processing of the same volumes or catalogs. Such requests are grouped together to allow all needed actions to be performed during a single pass of volume VTOCs, catalogs, or catalog superlocates.

The functions Sequential Migrate to Tape, Merge, Xcopy, Restore, and PDS Compression continue to use their own unique command sets. Functions using DSCL are invoked by executing the JCL procedure named DMS. In its simplest form, its use would look like:

//jobname JOB (acct,info),..

//STEP EXEC DMS
DSCL commands

Note: The FMS proc, used for data set recovery, is very similar to the DMS proc and its DSCL command structure. For more information, see Basic System ?FMS PROC the chapter "Basic System – FMS PROC."

To avoid unexpected execution of partially bad command strings, the DMS proc takes no action until all commands have been successfully understood, and all sysparm overrides have been validated.

To allow for sorted reports, the DMS proc has separate process, sort and print steps.