OBEYFILE: Failed to load ASASYMBP. Symbolic substitution will not be performed. Return code=return-code
The parser failed to load the ASASYMBP system substitution service program. Return code return-code was returned from the LOAD request. No substitution will be performed.
Retry retry # of max # retries for console open
This message is issued in the unlikely event that a request to open a console session to issue a system command fails and circumstances allow it to be retried.
The VNAC host command CONSOLE ACTIVATE SESSION opens a console session for the purpose of issuing a system command. That command could be issued from a user exec or from any of the VNAC-supplied execs that issue system commands.
retry # is the number of the current retry.
max # retries is the maximum number of retries allowed. The maximum is 5 retries, 3 seconds apart.
VNCRXF08: exec-name JOB/MSG=data-value; FILTER=filter-value; MATCHED/UNMATCHED; TASK=task-name
Debug message issued by VNCRXF08, the GETMSG function processor, to confirm the result of its filtering process for one unsolicited message obtained from the console listener. The JOB/MSG input data, data-value, is compared with the filter, filter-value, and the result is MATCHED/UNMATCHED.
Identical to VNC0573D, but with 16-character FILTER and MSG values to accomodate the external host command CONSOLE ACTIVATE LISTENER .
OBEYFILE: MessageRules processing order is implied. Continue options may not work as expected.
In the MessageRules configuration, Order Implicit is specified or defaulted and one or more Continue (-p) flags is coded.
The message rules will be processed in an order implied by their specificity, and not explicitly in the order coded. The Continue option may not work as expected.
Action: Examine the MessageRules configuration and ensure the rules will be processed in the order you want. Use the MSGRULE command to see the order in which message filters will be processed.
Consider adding Order Explicit to the MessageRules configuration. See the VNAC Programming & Automation manual for details.
VNCUTL05: CGVSAVE {SAVED|ERASED} global-variable-name
Debug message issued by VNCUTL05, the process triggered by a GlobalvSave statement in agent configuration.
GlobalvSave creates the CGVSSAVE timer, which runs VNCUTL05 at fixed intervals. VNCUTL05 scans an agent’s global variable buffers and saves changes to a VSAM file. VNCUTL05 issues the message for each change save to VSAM.
VNCRXF16: OBEYFILE PUTGLB CGVSAVE {START|STOP} failed; R15=hex-return-code
Error message issued by VNCRXF16, the global configuration statement processor, when it encounters an error while either stopping or starting a CGVSAVE timer.
CGVSAVE is the timer created by a GlobalvSave statement in agent configuration. CGVSAVE triggers VNCUTL05, a proccess that scans an agent’s global variable buffers and saves changes to a VSAM file. When CGVSAVE is active, its setting appears in the report produced by the TIMER command.
If this error occurs, contact SDS Technical Support for advice about gathering diagnostic information.
To recover from this error, edit the GlobalConfig section of member VNCCFG00 to specify GlobalvSave 0, then shutdown and restart the agent, or use an OBEYFILE command to reresh agent configuration. That will disable the CGVSAVE timer. VSAM updates for global variables will be queued immediately after each change, rather than scheduled to occur at time intervals.
OBEYFILE: Job &VTAM (=<local job name>) specified in foreign system (=<foreign system name>) message rule
Warning message issued by function PUTMSG (VNCRXF14) when it it processes a MessageRule in agent configuration that refers to a remote system.
More specifically, the configuration has a system statement that names a z/OS system other than the VNAC agent’s host, followed by a job statement with the &VTAM substitution parameter.
local job name is the name of the VTAM job on the agent’s host system, and foreign system name is the name defined in the configuration’s system statement.
When the VTAM job name is the same on both systems, ignore this warning.
exec-name(ALERTRSL) alert alert-id from VIP agent vip-agent-name not suppressed, REINSTATE status not allowed
Error message issued by function ALERTRSL (VNCRXF32).
The error occurs when an alert rule does not include the -s option, but calls an exec that reinstates the alert.
Without the -s option, the alert is not suppressed at the VIP agent. An exec cannot reinstate an alert that has not been suppressed.
This is a user error.
exec-name(ALERTRSL) alert alert-id from VIP agent vip-agent-name already has alert-status status
Error message issued by function ALERTRSL (VNCRXF32).
The error occures when the exec attempts to reset the status of the alert, but the new status is the same as the current status, identified in the message as alert-status.
This is a user error.
The one exception is that a suppressed alert in REINSTATE status may be re-set to REINSTATE without error.
exec-name(task-name) alert alert-id not suppressed; cannot return to VIP agent vip-agent-name
Error message issued by function ALERTRTN (VNCRXF31).
The error occurs when an alert rule does not include the -s option, but calls an exec that tries to reinstate the alert.
Without the -s option, the alert is not suppressed at the VIP agent. An exec cannot reinstate an alert that has not been suppressed.
This is a user error.
