Troubleshooting
Problem
This document describes a couple of possible reasons for why a particular subsystem might not start after an IPL of the system.
Resolving The Problem
One cause for subsystems not starting after an IPL could be that the startup program specified in the system value QSTRUPPGM is not found or is in a different library. If changes were made to the startup program, verify that the system value is correct and that the program is compiled in the correct library.
Another possibility is that the controlling subsystem is QBASE -- not QCTL. The system value, QCTLSBSD, is used to determine the controlling subsystem. If QCTL is specified, other subsystems are started after an IPL. These subsystems are QINTER, QBATCH, QCMN, and QSPL. If QBASE is the controlling subsystem, only subsystems QBASE and QSPL are started after an IPL. To determine the controlling subsystem, use the following command:
Another possibility is that the controlling subsystem is QBASE -- not QCTL. The system value, QCTLSBSD, is used to determine the controlling subsystem. If QCTL is specified, other subsystems are started after an IPL. These subsystems are QINTER, QBATCH, QCMN, and QSPL. If QBASE is the controlling subsystem, only subsystems QBASE and QSPL are started after an IPL. To determine the controlling subsystem, use the following command:
WRKSYSVAL QCTLSBSD
[{"Type":"MASTER","Line of Business":{"code":"LOB68","label":"Power HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z0000000CHjAAM","label":"Job and Work Management"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Versions"}]
Historical Number
4295436
Was this topic helpful?
Document Information
Modified date:
07 October 2024
UID
nas8N1014720