Wiki Category: VNC03nn: VNAC Agent VNCDSP00 Task

Waiting for an available command processor.

A request has arrived from a VNAC server. The VNAC agent has no idle command processors to dispatch the request to. The request will be put in a wait pending an available processor.

Session # sess-number is dead. Cleanup proceeding.

The Dispatcher’s session monitor found an entry in the session list with no active connection. The session resources are freed and the session is removed from the list.

Action: This can happen occasionally if the VNAC client is unable to send a session termination request to the agent. If the message is issued frequently, contact SDS Technical Support.

The request could not be dispatched; no storage is available.

A request has arrived from a VNAC server. The VNAC agent could not obtain storage to satisfy the request.

Action: This is a sever error. Increase the REGION size in the VNAC agent JCL and restart the agent. If the condition persists, contact SDS Technical Support.

The request could not be dispatched; the session could not be located.

A request arrived from a VNAC server. The session associated with the request could not be located in the agent’s session list.

Action: Look for other messages providing more information about the error. If the condition persists, contact SDS Technical Support.

Failed to create session for user userid; return code=return-code

A VNAC session could not be created with the named server for user userid.

Action: Look for other messages providing more information about the error. If the condition persists, contact SDS Technical Support.

New session # sess-number created with server server-name for user userid

A new VNAC session has been created with the named server for user userid.

Subtask VNCUAsubtask cannot be started because storage is constrained

For VNAC tasks, the maximum percentage of memory use below 16MB is specified in agent configuration. See GlobalConfig Statements in the manual Administer VNAC.

Subtask task-id timed out during initialization

The dispatcher attached a subtask, but the subtask failed to complete initialization within 5 seconds.

Action: Look for other messages providing more information about the error. If the condition persists, contact SDS Technical Support.

TasksUnattended increased 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 increased 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.