Command sequence for PARMLIB member ARCCMDxx

In the DFSMShsm environment, certain commands must follow a particular sequence to ensure that the command does not malfunction or fail. The following table lists these combinations:

ISSUE THIS COMMAND	BEFORE THIS COMMAND
SETSYS JES2 or JES3	Not Applicable
ADDVOL	DEFINE POOL
DEFINE BACKUP(...	SETSYS NOBACKUP
DEFINE DUMPCLASS	ADDVOL with either the AUTODUMP or the DUMPCLASS parameters
SETSYS MAXRECALLTASKS(tasks)	SETSYS TAPEMAXRECALLTASKS(tasks)
SETSYS SMALLDATASETPACKING	ADDVOL with SDSP
SETSYS SYSOUT	SETSYS ACTLOGTYPE
SETSYS USERUNITTABLE	ADDVOL
	DEFINE ARPOOL
	DEFINE DUMPCLASS with unit
	SETSYS ARECOVERUNITNAME
	SETSYS BACKUP(TAPE)
	SETSYS CDSVERSIONBACKUP
	SETSYS MIGUNITNAME
	SETSYS RECYCLEOUTPUT
	SETSYS SPILL
	SETSYS TAPEMIGRATION
	SETSYS UNITNAME
	SETSYS TAPEUTILIZATION for any esoteric
SETSYS USERDATASETSERIALIZATION	SETSYS DAYS

Note:

If you use the ONLYIF HSMHOST(hostid) command with both the DEFINE BACKUP and SETSYS NOBACKUP commands, and assign the commands to different hosts, there is no need for a specific command sequence.
SETSYS UNITNAME(unitname) should be specified before SETSYS CDSVERSIONBACKUP if you are not specifying a unit name as part of the BACKUPDEVICECATEGORY subparameter. If you do not specify SETSYS CDSVERSIONBACKUP BACKUPDEVICECATEGORY UNITNAME(unitname), and have not previously specified SETSYS UNITNAME(unitname), the default unit is 3590-1.
In an HSMplex environment, you should not use the SETSYS EXTENDEDTTOC(Y) command to enable extended TTOCs on any host in the HSMplex until the shared OCDS has been redefined with a record size of 6144 bytes.