exec-name: user-name activation key check PASSED; more than 30 days until expiration
Informational message issued by VNCRXF13, the PUTKEY function that processes activation keys. The function has processed a valid activation key with more than 30 days left until it expires.
exec-name: user-name Current CPU TYPE=cpu-type; MODEL=cpu-model; SERIAL=cpu-serial
Informational message issued by VNCRXF13, the PUTKEY function that processes activation keys. This message follows VNC0590E to show the current CPU type, model, and serial number on which the agent is running. You can use this information when you contact SDS support to obtain the correct activation key for the current system. Contact SDS Technical Support.
exec-name: user-name ERROR: error-message
Error message used by several function programs to display argument-syntax errors. If the message reports a REXX syntax error, then a REXX syntax error message follows this message, and REXX stops processing the exec.
exec-name and user-name identify the exec and user that called the function.
The functions and the value of error-message they generate are listed below.
VNCRXF12, GETCFG
Argument-syntax errors in the VNAC function that reads agent configuration records.
The possible values of the message text, error-message, are as follows:
GETCFG arg1, invalid message stem variable name.
GETCFG arg2, member name more than 8 characters
VNCRXF13, PUTKEY
Argument-syntax errors in the VNAC function that validates and installs agent activation keys.
The possible values of the message text, error-message, are as follows:
PUTKEY arg1, key is wrong length
PUTKEY arg2, processing option is not C or I
VNCRXF14, PUTMSG
Argument-syntax errors in the VNAC function that validates and installs message filter rules.
The possible values of the message text, error-message, are as follows:
PUTMSG arg2, Processing option is not C or I
PUTMSG arg1, -J option ignored because LocalCopy ALL configured
PUTMSG arg1, -J option ignored because LocalCopy NONE configured
PUTMSG arg1, -J option ignored because LocalCopy not configured
PUTMSG arg1, Command has unbalanced parentheses
PUTMSG arg1, Command has unbalanced single quotes
PUTMSG arg1, Endjob found without matching Job
PUTMSG arg1, invalid substitution variable name for job name
PUTMSG arg1, invalid substitution variable name for system name
PUTMSG arg1, Job found but previous Job is not ended
PUTMSG arg1, Job name must be 1-8 characters
PUTMSG arg1, Job statement must include jobname
PUTMSG arg1, LocalCopy option invalid, must be OPT, ALL, or NONE
PUTMSG arg1, log rule -X is not valid with display option -K
PUTMSG arg1, MaxLogRate value is missing or invalid
PUTMSG arg1, Message filter is too long
PUTMSG arg1, Message filter must be 1-8 characters
PUTMSG arg1, Message filters can contain only alpha-numeric characters and three wildcards: $ * ?
PUTMSG arg1, Message filters must not contain embedded asterisks
PUTMSG arg1, Next statement must be EndJob
PUTMSG arg1, Statement is unrecognizable
PUTMSG arg1, Syntax error in log rule
PUTMSG arg1, SYSLOG file not available, local copy impossible
PUTMSG arg1, System statement must include system name
PUTMSG arg1, Unrecognized log rule
PUTMSG arg1, user list contains separators that are not commas
PUTMSG arg1, user list does not contain any user IDs
PUTMSG arg1, user list has unbalanced parentheses
PUTMSG arg1, user list userid character not A-Z,0-9,$,#, or @
PUTMSG arg1, user list userid does not begin with A-Z,$,#, or @
PUTMSG arg1, user list userid not 1-8 characters in length
PUTMSG arg1, VipAgent has invalid substitution variable name for agent name
VNCRXF15, PUTEXC
Argument-syntax errors in the VNAC function that validates and installs autostart execs.
The possible values of the message text, error-message, are as follows:
PUTEXC arg1, auto start exec name is too long
PUTEXC arg2, processing option is not C or I
VNCRXF16, PUTGLB
Argument-syntax errors in the VNAC function that validates and installs global configuration parameters.
The possible values of the message text, error-message, are as follows:
PUTGLB arg1, global config parameter is too long
PUTGLB arg2, processing option is not C or I
DATASPACESIZE must be within the range 0 thru 256
DATASPACESIZE previously configured, cannot change
EojDump option must be YES or NO.
GlobalvMessages invalid option 1, must be ALL, ERROR, or NONE
GlobalvMessages invalid option 2, must be blank, EXEC, or NOEXEC
SAW option must be YES or NO
SAWAPPL name length must be 1 to 8 characters
SAWDB option must be ACTIVE, ENDED, or NONE
SAWNUM value must be in the range 2 thru 255
SAWPASS password length must be 1 to 8 characters
SAWSIZE value must be in the range 1 thru 64
SAWSMF option must be YES or NO
SecurityRegime must be 1 or 2.
SPIN line count and timeout values are required
SPIN line count must be in the range 0-9999999
SPIN time out must be in the range 0-1440
SPIN file must be *, VNCOUT, VNCLOG, or SYSLOG
SPIN file not spooled or not open, cannot proccess
TasksAttended initial value is out of bounds.
TasksAttended increment value is out of bounds.
TasksAttended limit value is out of bounds.
TasksAttended <16M usage % is out of bounds.
TasksUnattended initial value is out of bounds.
TasksUnattended increment value is out of bounds.
TasksUnattended limit value is out of bounds.
TasksUnattended <16M usage % is out of bounds.
Unrecognized statement in GlobalConfig.
ViewLimit value is out of bounds.
VNCRXF25, PUTSMF
Argument-syntax errors in the VNAC function that validates and installs SMF configuration (SmfConfig) parameters.
The possible values of the message text, error-message, are as follows:
TYPE value must be in the range 128 thru 255
SESSIONSTART option must be YES or NO
SESSIONEND option must be YES or NO
BINDFAILURE option must be YES or NO
INITFAILURE option must be YES or NO
Unrecognized statement in SmfConfig:
VNCRXF26, SAWCTRL
Argument-syntax errors in the VNAC function that controls collection of session-awareness data.
The possible values of the message text, error-message, are as follows:
SAWCTRL arg1, request must be START, STAT, STOP, or QUERY
VNCRXF28, PUTALR
Argument-syntax errors in the VNAC function that validates and installs alert rules.
The possible values of the message text, error-message, are as follows:
PUTALR arg1, alert filter is too long
PUTALR arg2, processing option is not C or I
PUTALR arg1, unrecognized option on alert filter statement
PUTALR arg1, syntax error in alert rule
PUTALR arg1, rules -X and -K cannot be specified together
PUTALR arg1, rules -X and -U cannot be specified together
PUTALR arg1, rules -X and -L cannot be specified together
PUTALR arg1, -C substitution variable must be 5-6 characters
PUTALR arg1, -C substitution variable is unrecognized
PUTALR arg1, alert filters must be 1-8 characters
PUTALR arg1, alert filters must not contain embedded asterisks
PUTALR arg1, alert filters must not contain embedded asterisk
PUTALR arg1, command has unbalanced single quotes
PUTALR arg1, command has unbalanced parentheses
PUTALR arg1, more than one LocalCopy statement
PUTALR arg1, LocalCopy option invalid, must be OPT, ALL, or NONE
PUTALR arg1, SYSLOG file not available, local copy impossible
PUTALR arg1, -J option ignored because LocalCopy ALL configured
PUTALR arg1, -J option ignored because LocalCopy NONE configured
PUTALR arg1, -J option ignored because LocalCopy OPT not configured
PUTALR arg1, user list has unbalanced parentheses
PUTALR arg1, user list userid not 1-8 characters in length
PUTALR arg1, user list userid does not begin with A-Z,$,#, or @
PUTALR arg1, user list userid character not A-Z,0-9,$,#, or @
PUTALR arg1, user list does not contain any userids
PUTALR arg1, user list contains separators that are not commas
exec-name: user-name activation key check PASSED; day-count days until expiration
Warning message issued by VNCRXF13, the PUTKEY function that processes activation keys. The function has processed a valid activation key with 30 days or fewer remaining until it expires.
program-name: exec-name function-name queued SWE buffer at buffer-address to dispatcher with CMD=exec-name
Debug message issued by VNCRXF17, the EXEC function, following message vnc0587D. This message shows the exec name and parameters that have been queued for execution on a new task.
program-name: exec-name function-name queued SWE buffer at buffer-address to dispatcher with SID=session-id
Debug message issued by VNCRXF17, the EXEC function, and VNCRXF20, the CNCLCMD function. The message indicates that the function successfully processed its request and has queued a request buffer at address buffer-address to the agent’s work dispatcher task.
exec-name: user-name activation key check FAILED; RTC=decimal-return-code; RSC=decimal-reason-code
Informational message issued by VNCRXF13, the PUTKEY function that processes activation keys. The function has found an error in the activation key it is currently processing. Processing continues with the next activation key.
decimal-reason-code has one of the following values:
4 – The checksum is invalid
8 – The expiration date has passed
12 – The activation date has not yet arrived
16 or 20 – The CPU information does not match the current system
For return codes other than 4 and reason codes other than those listed, contact SDS Technical Support.
program-name: exec-name function-name created LCR buffer #buffer-count at buffer-address; key=activation-key
Debug message issued by VNCRXF13, the PUTKEY function that processes activation keys. The function has stored the key it just processed in an activation key (LCR) buffer. The total number of activation key buffers allocated so far is buffer-count.
program-name: exec-name function-name enumerated and tossed buffer-count LCR buffers; CPB=cpb-address
Debug message issued by VNCRXF13, the PUTKEY function that processes activation keys. The message shows how many preexisting activation key (LCR) buffers were deleted before it started processing the new activation keys in the agent configuration file.
function-name: exec-name storage-request RTC=hex-return-code; RSC=hex-reason-code; error-message
Error message issued by several functions and host-command programs that allocate and manipulate temporary buffers. The message provides diagnostic information when a storage-request failure is caused by error-message. The most likely cause is that the agent has no more virtual storage available within its region. Try doubling the region size. If that fails, contact SDS Technical Support.
