323W

Unit record logging in effect ‑ UR I/O suspended until CA‑ACF2 is active

Reason

Your system supports Unit Record Logging and you tried to start up unit record devices before CA ACF2 for z/VM was ready to process SMF (logging) records. You can start unit record equipment (printers, punches, readers) from three sources.

The system automatically initiates a START at startup time if the operator did not specify DRAIN to the spool startup prompt.
The system spooling operator can issue the CP START command.
Some VM releases issue this message if the system operator issued the SPOOL CONSOLE CLOSE command, even though the printer was drained before the system is totally initialized.

The operator should always respond DRAIN to the spool startup prompt and wait until CA ACF2 for z/VM is active. If you need to get output in NOAUTO mode, wait until VM issues the following message:

DMKCPI966I INITIALIZATION COMPLETE.

The spool operator should not issue the START command after the SHUTDOWN command. It can cause CA ACF2 for z/VM to restart to validate the START command, delaying shutdown.

Action

This is an information only message. Repeated attempts to start unit record devices to print a file can cause VM to put it in a holding status (you can rectify this with a CP CHANGE command) or vary the printer offline (fix this with the CP VARY ONLINE command). In other words, avoid starts until the system is ready.

Instruct the operator to always respond DRAIN at system startup and manually start up the unit record devices when the system is initialized. Alternatively, you can use AUTOLOG1 to automatically start up your unit record devices if AUTOLOG1 issues a command limited CP command or if you have installed CMS security. Another possibility is to have unit record startup commands in a PROP exec. Use AUTOLOG1 or PROP to start up unit record devices to save you from keeping the default classes for unit record startup in HCPRIO and regenerating the system.