Attempting to forcibly terminate stuck tasks
While the agent was shutting down, the VNAC dispatcher detected that one or more tasks had not ended. The VNAC dispatcher is attempting to forcibly stop the tasks.
Destination: VNCOUT and VNCLOG.
Action: None. Shutdown continues.
See message VNC0154I
See message VNC0154I
| VNC0154I CPR task statistics: | Init | Max | Curr | HWM | Incr | Decr |
| VNC0155I Attended tasks | nn | nn | nn | nn | nn | nn |
| VNC0155I Unattended tasks | nn | nn | nn | nn | nn | nn |
| VNC0156I High-water mark of nnMbyte storage: nn% | ||||||
Explanation: A set of messages generated by the command MODIFY agentNam,CPRSTAT.
A report of a VNAC agent’s task configuration, task pool size, and memory use.
Init: The configured initial/minimum number of tasks.
Max: The configured maximum number of tasks.
Curr: The number of tasks currently in a pool.
HWM: The high-water mark, the highest number of tasks in a pool at any one time since the agent started.
Incr: The number of times the agent has added tasks to a pool.
Decr: The number of times the agent has released tasks.
VNC0156I: Highest memory use seen when the agent added tasks.
For details, see the section Task Management in the manual Administer VNAC.
Action: None.
Continuing agent initialization
Explanation: This message is issued after VNC0152I, when the agent resumes its initialization processing.
Action: None.
Waiting for VNAC agent agentname (job jobid, ASID asid) to terminate
Explanation: During initialization, VNAC has discovered that a job or started task with the same agent name as the issuing agent is running but has begun termination. VNAC will wait for that agent to terminate, and then resume initialization.
Action: None.
VNAC agent agentname is already active
Explanation: A VNAC agent named agentname has been started, but an agent of that name is already active on the same z/OS image.
Action: Change the agent name using the MYNAME parameter on the EXEC card for the agent step. Restart the agent.
VAAB anchored at address
Explanation: The VitalSignsAgent Anchor Block is loaded at address in ECSA.
Action: None.
The maximum of eight VNAC agents have been started
Explanation: Each uniquely named VNAC agent takes a permanent slot in the VitalSigns Agent Anchor Block (VAAB). The VAAB is maintained until the system is next IPLed. A maximum of eight VNAC agents (by name) may be run on a single z/OS image between IPLs. This agent would be the ninth. The agent is terminated.
Action: If there are eight VNAC agents currently active, you cannot start another. If there are fewer than eight agents running, then there have been eight uniquely named agents started since the last IPL. You can run this agent using the name of an earlier agent that is no longer active. Change the MYNAME parameter on the EXEC statement in the agent procedure and restart the agent.
Unable to create VNAC anchor; IEANTCR retcode=return-code
Explanation: An error occurred during VNAC initialization. An error was returned from Name/Token services when the VNAC agent attempted to create the VitalSigns anchor block. The agent terminates.
Action: Restart the agent. If the problem persists, contact SDS Technical Support.
