This section documents some system automations that are available to start or stop the system and certain z/OS® subsystems.
z/OS system startup and shutdown are handled by NetView®. There are two tasks (CNMPSSI and CNMPROC) that are started automatically at the beginning of the IPL process. When NetView has initialized, it will start the remaining z/OS subsystem tasks.
- Modify z/OS command. For example,
- Use the subsystem command character at the z/OS console. For example,
||Shut down all z/OS system tasks.|
||Show the status of all z/OS system tasks that are managed by NetView.|
||Start a managed task.|
||Stop a managed task.|
||Set a specific status for a managed task.|
||Display and update the status for all managed tasks.|
||Display the task global variables, for example, start or stop command.|
||Display the list of valid commands.|
NetView managed task status settings
The output of the GETSTAT command might show any of the following status settings for a managed task.
The status of NOSTART indicates that the task is not automatically started after an IPL. Typically, this status occurs because the software was not selected when the z/OS image is built from ZVDT. In some cases, when software is not selected during image build, the disk volumes are not present to support starting these tasks. If there are no disk volume dependencies for the task that has a status of NOSTART, you can start the task by using the STRTTASK command that is described in the preceding table for NetView Commands.
The status of COMPLETE indicates that the task is transient, or multiple tasks have the same start or stop task name, or the task does not remain active in the z/OS system after the task is started. The tasks that have a status of COMPLETE are considered as UP after the tasks are started, and the continuous status of the tasks will not be tracked. Therefore, the tasks that have a status of COMPLETE might be down, and manual verification might be required if some errors occur with these tasks.
Task is up.
Task is down.
All z/OS tasks are set with an initial status of IPL when the system is restarted. If a task still has the status of IPL after an IPL is complete, some errors might occur with the automation and manual actions might be required to start the task.
To list all tasks that are managed by NetView run the GETSTAT command on the z/OS system, the startup messages are displayed as follows.
INFO: 011620 17:44:10: : OPRMSG: BPXF002I FILE SYSTEM DFH550.JVMPROFS.ZFS WAS INFO: 011620 17:44:10: : OPRMSG: NOT MOUNTED. RETURN CODE = 00000080, REASON CODE = EF096055
INFO: 011520 17:05:33: : OPRMSG: * IGGN505A SPECIFY UNIT FOR DFH550.CICS.SDFHLINK ON A4C551 OR CANCEL
The first example of message indicates that the volume where the ZFS file is allocated was not included in the ZVDT z/OS image. The system will attempt to mount all ADCD ZFS files regardless of what is contained in the ZVDT image. This process can provide more flexibility by allowing ZFS mounts to succeed after dynamically adding volumes to the running system.
The second example relates to CICS® Version 5.5. Since CICS V5.5 was not included in the ZVDT z/OS image, some disk volume files are intentionally excluded. Therefore, the data sets on the volume cannot be added to the system LINKLIST. The IGGN505A message will be automatically responded by ZVDT to bypass this condition and the message can be safely ignored.
Manual IPL Information
If you want to IPL the z/OS system manually by using the zPDT® IPL command, you need to use the following IPL string.
ipl 0a80 parm 0a82nv
This IPL string allows z/OS system parmlib automation to handle some early IPL responses that might be required. These responses can normally be made by ZVDT. However, when the manual IPL process of z/OS is done, ZVDT will not be aware of any outstanding responses that might be needed.
Automated Task Startup at IPL time
- For ADCD z/OS systems that are deployed to non-OpenShift® targets, the symbolic parameters are defined in IEASYMAU.
The symbolic parameter name matches to the name of the z/OS subsystem, for example, SYMDEF(&CICSTS55='NOS'). This symbolic parameter name indicates that CICSTS55 will not start automatically after an IPL. Set the value of the symbolic parameter to IPL to allow the task to start automatically. You must ensure that you selected CICS 5.5 when the image was created for this deployment.