Shutting down BMC AMI Utilities Subsystem
Use the following information if you need to shut down BMC AMI Utilities Subsystem (CDBSS Subsystem).
Before you begin
Ensure that the following conditions are in effect:
- The value of the XIPL initialization parameter is YES.
No local connection is active for utilities on the current system.
If a utility is connected when you attempt to shut down CDBSS Subsystem, CDBSS Subsystem issues message NGTC338. You can retry the shutdown command after all local connections have completed.
For remote connections, the local Db2 member must be inactive at the time of the shutdown.
If a Db2 member is active when you attempt to shut down CDBSS Subsystem, the CDBSS Subsystem issues message NGTC333 for each remote connection. You can retry the shutdown command after all Db2 members on the current system are shut down.
Sufficient data space storage exists on the utility's CDBSS Subsystem to support transferring the remote session data.
If insufficient memory exists on the target system, CDBSS Subsystem issues NGTC337. You can retry the shutdown command when sufficient memory is available on the target system.
To shut down CDBSS Subsystem
To shutdown CDBSS Subsystem, issue the following operator command:
CDBSS Subsystem completes an orderly shutdown. Any remote session data is transferred to the utility's CDBSS Subsystem data space memory.