Command data set conventions

Command data sets use the following conventions:

The sequence numbers of the command data set should be turned off.
SCLM processes all commands in the command data set regardless of the success or failure of previous commands.
Each command must start on a new line.
If a command takes more than one line, the continuation character should be the first character of the continuation line.
If you enter spaces between the continuation character and the character that follows, those spaces will be treated as part of the parameter.
If a command line exceeds the maximum record length of the command data set, continue the command by adding a plus sign (the continuation character) in the first position of the continuation line. You can add any number of continuation lines for any command.
The maximum command length is 512 bytes. Note that if a command consists of several command lines, SCLM deletes trailing blanks.
An asterisk (*) indicates comment lines. Place it in the first nonblank character of a command line. You can enter any number of comments within the command data set, but you cannot add a comment line within a series of command continuation lines.

The following example shows a command data set. The first command calls the SCLM LOCK service; the second command calls the SCLM UNLOCK service.

*
* This is an example of a command data set.
     * Note that comments do not have to start in column 1.
*
* The following command calls the SCLM LOCK service.
LOCK,PROJ1,,USER1,SOURCE,FLM01MD2,TESTAC,XXX#04,USERID
*
* The following command consists of four lines,
* and calls the SCLM UNLOCK service.
UNLOCK,PROJ1,,
+USER1,
+SOURCE,
+FLM01MD2,XXX#04

The following example shows a CLIST command procedure that calls the FILE format of FLMCMD.

PROC 0
  ALLOC DDNAME(SCLMIN) DA('USERID.FLMCMD.INPUT') SHR
  FLMCMD FILE,SCLMIN
  SET &FLMCMDCC =
  FREE DDNAME(SCLMIN)
  EXIT CODE(&FLMCMDCC)
END