Controlling the device type for the activity logs

The second way you can reduce the burden of analyzing the activity logs is to automate the process. The ABARSACTLOGTYPE and the ACTLOGTYPE parameters allow you to choose whether to make the activity logs SYSOUT data sets or DASD data sets. If you send the activity logs to a DASD data set, you can browse the data online for information that is of interest to you.

DFSMShsm dynamically allocates DASD data sets with a unit name of SYSALLDA and a size of 20 tracks for primary allocation or 50 tracks for secondary allocation. Activity logs have names in the following forms:

Type of Activity Log	Activity Log Name
ABARS	mcvtactn.Hmcvthost.function.agname.Dyyddd.Thhmmss
All Other Types	mcvtactn.Hmcvthost.function.Dyyddd.Thhmmss
mcvtactn Activity log high-level qualifier H, D, and T Constants mcvthost Identifier for the DFSMShsm host that creates these activity logs function ABACKUP, ARECOVER, CMDLOG, BAKLOG, DMPLOG, or MIGLOG agname Aggregate group name yyddd Year and day of allocation hhmmss Hour, minute, and second of allocation

Note:

If you do not want the activity log data sets to appear in the master catalog, define an alias for HSMACT.
DFSMShsm provides a high-level qualifier of HSMACT for mcvtactn. If your data set naming convention is not compatible with this qualifier, you can use a PATCH command to modify this high-level qualifier. See Replacing HSMACT as the high-level qualifier for activity logs .