MSCAN command

The MSCAN command initiates the MCDS scan process. There are no parameters on the command.

Each MSCAN command causes all MCDS data sets to be read and summarized into an MSCAN collection data set. The collection data set is reused with each MSCAN process. The collection data set name is created by using the SMMSYS VSCAN_OINDX parameter value, which is the same data set name prefix that is used by the VTOC Scan collection data sets.

Reading MCDS data sets can be a resource consuming process. BMC recommends that the MSCAN command be run during lower periods of CPU and I/O usage. The MSCAN_MXTSK parameter can be used to increase or decrease the elapsed time of the process.

For reporting purposes, BMC recommends initiating the MSCAN command after primary and secondary space management have been completed. BMC also recommends initiating a systemwide VTOC Scan shortly before or after the MSCAN command is executed. As distributed, the Scheduled Services SMSCHD00 PARMLIB member issues the MSCAN command once a day at 11:30 P.M.

Using the SMMSYS MSCAN_POST parameter, you can initiate MSCAN automatically after primary or secondary space management completes processing.

MSCAN activity can be seen in the audit log views. An entry in the audit log is created when the command is received, and another is created when the MSCAN process is completed. The completion audit log record contains statistics from the process.

The MSCAN command needs to be initiated on only one system in an HSM-plex. Because the MCDS data sets are shared by the systems within an HSM-plex, the results are the same regardless of the system on which it is run.

MSCAN has the following restrictions:

• Only one MSCAN command can be active at a time. Any MSCAN command that is received while one is already active will be ignored.
• The SVHSM component must be active in order for SVOS to access MCDS data sets.
• The SVSGC component must be active for ML1 and ML2 reporting by application.