Subsystem not deactivated. RC=x′return-code′ Reason=x′reason-code′
The utility issued an IEFSSI REQUEST=DEACTIVATE request to deactivate the subsystem but it failed with the indicated return and reason codes.
Action: Review the return and reason codes for the IEFSSI REQUEST=DEACTIVATE macro. Contact SDS Technical Support for additional assistance.
Subsystem in use by one or more command issuers
The utility has determined that one or more command issuers are using the subsystem and awaiting a response from one or more agents. The utility waits for a maximum of 30 seconds before issuing this message to give any command issuers time to exit the subsystem interface.
Action: If no agents that use this subsystem are active, it is possible an agent or subsystem failure has left the agent control block in an unusable state. Take an SDUMP of ECSA and contact SDS Technical Support. Ensure there are no agents running that are using the subsystem. Use the FORCE option in the input parm to the utility to allow the utility to bypass this check.
Subsystem in use by agent jobname
The subsystem is in use by the agent with the jobname shown in the message.
Action: If the indicated agent is not active, it is possible an agent or subsystem failure has left the agent control block in an unusable state.
Take an SDUMP of ECSA and contact SDS Technical Support. Ensure there are no agents running that are using the subsystem. Use the FORCE option in the input parm to the utility to allow the utility to bypass this check.
Found agent slot marked in use/not ready
The utility found that an agent control block associated with the subsystem is marked as in use but that an agent has not completed its connection to the subsystem. If no agents are running that are using the subsystem, this could represent a ‘dead’ control block after an agent or subsystem failure.
Action: Take an SDUMP of ECSA and contact SDS Technical Support. Ensure there are no agents running that are using the subsystem. Use the FORCE option in the input parm to the utility to allow the utility to bypass this check.
Subsystem does not appear to belong to VNAC.
The storage area addressed by SSCTSUSE in the subsystem entry does not contain the VNAC eye catcher (VNCDSSCA) and is assumed to not be a VNAC subsystem. The utility will not process any subsystem it does not believe is a VNAC subsystem as this could lead to system failures or other errors.
Action: Check that the subsystem name specified on the JCL parm input to the program is correct and that the job ran on the correct system.
If the subsystem name is correct, take an SDUMP of ECSA and contact SDS Technical Support.
Subsystem not initialized, no action taken
The subsystem name entry was found but has not been initialized by VNAC (SSCTSUSE is zero). There is nothing for the utility to do.
Action: None.
Subsystem name xxxx not found
The specified subsystem name was not found on this system.
Action: Check that the subsystem name specified on the JCL parm input to the program is correct and that the job ran on the correct system.
Subsystem name too long (max 4 chars)
The subsystem name specified on the JCL parm input to the program was longer than four characters.
Action: Correct the JCL to specify a 1-4 character VNAC subsystem name as the parm operand to the VNCSSUTL program and rerun the job.
Subsystem name missing
No subsystem name was specified on the JCL parm input to the program.
Action: Correct the JCL to specify a 1-4 character VNAC subsystem name as the parm operand to the VNCSSUTL program and rerun the job.
Total storage used by all execs nnnnnnn bytes
RXLSTAT modify command summary output line. Shows the total amount of storage in bytes used by all currently loaded execs (including execs marked for refresh).
Destination: VNCOUT and VNCLOG.
Action: None.
