Activity log data sets

Activity log data sets provide you with messages that relate to activity in one of five areas: space management, backup and recovery, dumps, ABARS, and command functions of DFSMShsm.

	Activity Log Data Sets
	Required: No. Allocated by starter set: No, DFSMShsm dynamically allocates the activity log data sets. Data set type: Physical sequential or SYSOUT. General guidance: SETSYS ACTLOGMSGLVL and ABARSACTLOGMSGLVL control the amount and kind of generated messages. SETSYS ACTLOGTYPE and ABARSACTLOGTYPE control where messages are written. Example: You can direct messages to a printer or to a DASD file where they can then be browsed. See Starter set example for an example of how these commands are specified in the starter set.

Activity Log Data Sets

Required:

No.

Allocated by starter set:

No, DFSMShsm dynamically allocates the activity log data sets.

Data set type:

Physical sequential or SYSOUT.

General guidance:

SETSYS ACTLOGMSGLVL and ABARSACTLOGMSGLVL control the amount and kind of generated messages.

SETSYS ACTLOGTYPE and ABARSACTLOGTYPE control where messages are written. Example: You can direct messages to a printer or to a DASD file where they can then be browsed.

See Starter set example for an example of how these commands are specified in the starter set.

DFSMShsm has five activity logs, each providing information that relates to activity in one of four DFSMShsm areas.

Log	Description
Migration Activity Log	Reporting on space management activity, this log is closed either when the volume space management control module finishes processing or when the storage administrator issues the RELEASE HARDCOPY command. The RELEASE HARDCOPY command has no effect for logs that are empty. This processing includes MIGRATE commands for volumes and levels, interval migration, automatic primary space management, and automatic secondary space management.
Backup Activity Log	Reporting on automatic backup or volume command backup, FRBACKUP and FRRECOV activities, and volume command recovery activities, this log is closed either after automatic backup has ended, after a set of BACKVOL, RECOVER, or EXPIREBV commands has been processed, or when the storage administrator issues the RELEASE HARDCOPY command. The RELEASE HARDCOPY command has no effect for logs that are empty.
Dump Activity Log	Reporting on automatic dump or command volume dump and command volume restore activities, this log is closed either after automatic dump has ended, after a set of BACKVOL or RECOVER commands has been processed, or when the storage administrator issues the RELEASE HARDCOPY command. The RELEASE HARDCOPY command has no effect for logs that are empty.
ABARS Activity Log	Reporting on aggregate backup and aggregate recovery activities, this log is closed after each aggregate backup, and each aggregate recovery request has been completed. One ABARS activity log is allocated for each aggregate backup or aggregate recovery command issued. This log is allocated, opened, written to, and closed by the ABARS secondary address space The SETSYS ABARSDELETEACTIVITY command allows you to specify whether you want DFSMShsm to automatically delete the ABARS activity log associated with an aggregate backup or recovery version during roll off or EXPIREBV ABARSVERSIONS processing.
Command Activity Log	This log reports on TAPECOPY and TAPEREPL activity, and also records error informational messages that occur during low-level type internal service processing. This log is closed either when DFSMShsm shuts down or when the storage administrator issues the RELEASE HARDCOPY command. The RELEASE HARDCOPY command has no effect for logs that are empty.