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.
exec-name(task-name) ALR3 buffer is missing/invalid
Error message issued by functions ALERTRTN (VNCRXF31) and ALERTRSL (VNCRXF32).
If the ALR3 alert buffer is “missing,” then the exec that called the function was not called from an alert rule, so there is no alert buffer to process. This is a user error.
If the ALR3 alert buffer is invalid, the storage class ID in the buffer is not the expected ALR3.
This is an internal logic error.
exec-name received an invalid MDB prefix/header; ID=eyecatcher, VER=mdb-version, TYPE=MDB-type; no variables created
Error message issued by VNCRXM03, the REXX EXEC exit that creates variables for execs called from alert and message rules. The address of the MDB buffer is passed to the exec in the CPB.
The error occurs when the MDB buffer fails validation of the eyecatchers in the prefix or header sections, identified in the message by eyecatcher.
For the MDB prefix section, ID should equal MDBP, VER should equal 1, and TYPE should = 0 (zero).
For the MDB header, ID should equal MDB, VER should equal 1, and TYPE should equal 1.
This message probably indicates an internal logic error.
program-name: exec-name(task-name), MDB(buffer-address), CPB(buffer-address)
Debug message issued by VNCRXM03, the REXX EXEC exit that creates variables for execs called from alert and message rules. The exit acts before the exec begins processing the MDB message buffer. The address of the MDB buffer is passed to the exec in the CPB.
exec-name received an invalid ALR3 buffer; ID=buffer-id; LEN=buffer-length; no variables created
Error message issued by VNCRXM03, the REXX EXEC exit that creates variables for execs called from alert and message rules. The address of the ALR3 alert buffer is passed from the alert rule to the exec in the CPB.
The error occurs when the ALR3 alert buffer fails validation of its storage class, identified in the message by buffer-id.
The ID should be “ALR3” and the length should be 0x00001000 (4,096).
