This agent is not using a subsystem because:
Description: The operator issued the SSINFO command to display subsystem information, but the agent is not using a subsystem because of the response listed in the following messages.
Static subsystems are not supported
Description: While preparing to connect to the subsystem, the agent determined that the target subsystem is defined as a static subsystem. This version of VNAC does not currently support static subsystems.
Action: Change the VNAC agent GlobalConfig startup parameter, Subsystem, to specify the name of an existing, dynamically defined VNAC subsystem, or the name of a subsystem that does not already exist, in which case the agent will define it.
Subsystem xxxx is not a VNAC subsystem
Description: While preparing to connect to the subsystem xxxx, the agent detected that the subsystem named by the GlobalConfig startup parameter Subsystem, is not a VNAC subsystem.
Action: If connecting to an existing VNAC subsystem, change the VNAC agent GlobalConfig startup parameter, Subsystem, to specify the name of an existing VNAC subsystem.
Version mismatch program version=program version control block version=cb version
Description: While preparing to connect to the subsystem, the agent detected a difference between the internal subsystem version program version assembled into program program and the control block version, cb version, in the control block.
Possible causes are that service has updated the program code, but the subsystem has not been cleared and reinitialized.
Action: Contact SDS Technical Support.
Subsystem command processor is available using cpf
Description: The agent has connected to the VNAC subsystem and is using the command prefix string cpf.
Action: None.
Command: verb operands
Description: The agent received the command indicated by verb operands.
Action: None.
Error sending SWE to command task
Description: While processing a command from the subsystem, the agent was unable to send the SWE (SDS Common Interface Work Element) control block containing the command to the VNAC command processing task.
Action: Review the agent logs for additional messages that may indicate why the agent was unable to schedule the SWE to the command task. Contact SDS Technical Support.
Error allocating SWE. Command not processed.
Description: While processing a command from the subsystem, the agent was unable to obtain an SWE (SDS Common Interface Work Element) control block. The command is not processed by the agent.
Action: Review the agent logs for additional messages that may indicate why the agent was unable to obtain the SWE. Contact SDS Technical Support.
No response from agent agent
Description: The subsystem had passed a command to the agent agent and was waiting for an acknowledgement that the command had been received, but the wait timed out before the agent responded.
Action: The command may still be processed by the agent. Review the agent logs to determine if the command was processed or not.
Error releasing ECSA UTOKEN storage
Description: After processing a command, the subsystem was attempting to release ECSA storage used to hold the user token for the command. The STORAGE RELEASE failed. The ECSA storage may be orphaned.
Action: If the problem persists, contact SDS Technical Support.