Unable to add a resource manager exit; RESMGR retc=return-code
VNAC uses a resource manager routine to clean up system resources in the event the address space does not terminate normally. The RESMGR call to add the routine failed with return code return-code.
Action: Examine the logs for other messages that may provide more information on the failure. If the problem persists, contact SDS Technical Support.
New alert rule configuration posted to VIP agent vip-agent
A VNAC agent’s rules for handling VIP alerts have been written to the cross-memory dataspace for delivery to a VIP agent.
This VNAC agent is configured to communicate with VIP agent vipagent
Affinity has been established between this VNAC agent and VIP agent named at the end of the message. Cross-memory communications between the two agents can now begin.
Requested VipAgent name vip-agent is being held by VNAC agent vnac-agent
An affinity was requested between the VNAC agent and the VIP agent named vip-agent,
but an affinity already exists between the VIP agent and the VNAC agent named vnac-agent.
Action: Examine and correct the configuration. If necessary, restart the VNAC agent. If the problem persists, contact SDS Technical Support.
No VIP agent configured, unable to pass alert rule configuration to VIP agent
Error message issued by VNCINI00, the VNAC agent initialization program, after the intial OBEYFILE command has completed.
VNCINI00 detects that alert rules are configured, but the GlobalConfig section provides no VipAgent=name parameter.
Action: To correct the problem, shutdown the VNAC agent, add a VIP agent name to VNAC agent configuration. The parameter VipAgent=name goes in the GlobalConfig section of the member VNCCFG00. The member is part of a dataset listed in the agent JCL, in the VNCCFG DD statement.
After setting the VIP agent name, restart the VNAC agent.
Failed to send alert alert-id status change to VIP agent vip-agent-name; RETC=decimal-return-code, RETV=hex-return-value
Error message issued by function ALERTRSL (VNCRXF32) after failure of an “alert resolve request” (request #4).
The return code in the message is from SCCDSP01, the program that creates and manages the dataspace. Codes 48 and 64 indicate the VIP agent is not available. Other codes may indicate an internal logic error.
Action: For assistance diagnosing this problem, contact SDS Technical Support.
sent change status to pending/ignore/resolve/reinstate for alert alert-id to VIP agent vip-agent-name
Informational message issued by function ALERTRSL (VNCRXF32) after an “alert resolve request” (request #4) succeeds, sending the status change request to the VIP agent that originated the alert.
Returned alert alert-id to VIP agent vip-agent-name with status alert-status
Informational message issued by function ALERTRTN (VNCRXF31) after an “alert return request” (request #3) succeeds, sending the alert back to the VIP agent originated the alert.
Failed to return alert alert-id to VIP agent vip-agent-name; RETC=decimal-return-code, RETV=hex-return-value
Error message issued by function ALERTRTN (VNCRXF31) after a failed attempt to write the “alert return request” (request #3) to the dataspace.
The return code in the message is from SCCDSP01, the program that creates and manages the dataspace. Codes 48 and 64 indicate the VIP agent is not available. Other codes may indicate an internal logic error.
Action: For assistance diagnosing this problem, contact SDS Technical Support.
No Dataspace configured, unable to pass alert rule configuration to VIP agent
Warning issued by VNCINI00, the VNAC agent initialization program, after the intial OBEYFILE command has completed.
VNCINI00 detects that VNAC agent configuration includes alert rules, but its GlobalConfig section provides no DataSpaceSize parameter, or specifies that DataSpaceSize = 0 (zero).
Action: To correct the problem, add a non-zero DataSpaceSize parameter to agent configuration. The parameter typically goes in the GlobalConfig section of the member VNCCFG00. That member is part of a dataset listed in the agent JCL, in the VNCCFG DD statement.
Once the non-zero value is in place, issue an OBEYFILE command to refresh VNAC agent configuration: OBEYFILE membername INSTALL
DataSpaceSize is configured in megabyte units, ranging from 0 to 256. 16 MB is usually adequate, unless the volume of alerts being forwarded and returned is very high.
Once a VNAC agent has created the dataspace, it only be re-sized or closed up by restarting the agent.
