The request could not be dispatched; the request message could not be parsed.
A request was received by the dispatcher, but a failure occurred while parsing the XML request message.
Action: Look for other messages providing more information about the error. If the condition persists, contact SDS Technical Support.
The request could not be dispatched; the request message could not be read.
A request was received by the dispatcher, but a failure occurred when reading the request from the TCP buffer.
Action: Look for other messages providing more information about the error. If the condition persists, contact SDS Technical Support.
TasksUnattended decreased from nn to mm tasks.
The number of VNAC tasks in the agent pool increases and decreases with the agent workload. Tasks are added when the request queue is 2 to 7 seconds long. They are removed when they have been idle for one hour.
Agents use two pools of tasks, one for attended tasks, one for unattended tasks. Attended tasks are those started by an interactive command, typically at the VNAC command interface. Unattended tasks are those generated by agent startup or by automated responses to system messages.
The initial and maximum number of tasks, and the number added or deleted at any one time, are specified in agent configuration, by the TasksAttended and TasksUnattended parameters.
For details, see “Task Management” in the manual Administer VNAC.
Action: None.
TasksAttended decreased from nn to mm tasks.
The number of VNAC tasks in the agent pool increases and decreases with the agent workload. Tasks are added when the request queue is 2 to 7 seconds long. They are removed when they have been idle for one hour.
Agents use two pools of tasks, one for attended tasks, one for unattended tasks. Attended tasks are those started by an interactive command, typically at the VNAC command interface. Unattended tasks are those generated by agent startup or by automated responses to system messages.
The initial and maximum number of tasks, and the number added or deleted at any one time, are specified in agent configuration, by the TasksAttended and TasksUnattended parameters.
For details, see “Task Management” in the manual Administer VNAC.
Action: None.
Request cancel in progress.
Informational message issued by VNCDSP01 after it received a request to cancel a REXX exec and verified that the exec is running. The program posts an ECB to signal other programs to halt execution of the exec.
Command canceled prior to dispatch.
A request that was in the dispatcher’s queue waiting for an available command processor has been withdrawn and canceled. The command will not be executed.
This message may appear in the browser, when a user presses the Cancel button to cancel a request that is waiting for an available command processor.
This message will be preceded by message VNC0315I and accompanied by message VNC0331I.
Action: None.
The request has been removed from the dispatch queue.
A request that was in the dispatcher’s queue waiting for an available command processor has been withdrawn.
This message appears in VNCOUT and in the browser, when a user presses the Cancel button to cancel a request that is waiting for an available command processor.
This message will be preceded by message VNC0315I.
Action: None.
Proceeding to Phase 2 termination.
The SlowShutDown delay configured for the agent has expired. Agent termination continues. Active requests will be cancelled.
Action: None required. If an excessive number of execs are canceled during Phase 2 termination (indicated by messages VNC0319I), you may wish to examine the execs and make changes so that they will clean up and terminate before the SlowShutDown delay expires.
Phase 1 termination posted.
Agent termination has begun. Agent configuration specifies SlowShutDown.
A slow shutdown means there is a delay of up to 60 secondes during which active requests will be allowed to run. If they are still running at the end of the delay, they are cancelled.
Any new requests for the following functions and commands are rejected: EXEC, GETMSG, WAIT, ALLOCATE, CONSOLE, and SEND (if it requests a reply, WTOR).
Beginning Phase 1 termination.
Agent termination has begun. Agent configuration specifies SlowShutDown.
A slow shutdown means there is a delay of up to 60 seconds during which active requests will be allowed to run. If they are still running at the end of the delay, they are cancelled.
Any new requests for the following functions and commands are rejected: EXEC, GETMSG, WAIT, ALLOCATE, CONSOLE, and SEND (if it requests a reply, WTOR).
