VNC1410W

No exec(s) matching mask found in the list of loaded execs

Issued in response to a REFRESH MODIFY command. No execs that match mask were found.

Destination: GUI console.

Action: None if mask is correct, else correct and re-enter the command.

VNC1404E

IRXLOAD FREE call for exec execname gave RC=return-code.

While attempting to release REXX EXEC execname that was marked for refresh and with a use count of zero, the VNAC REXX Loader received a non-zero return code return-code from the REXX Loader program, IRXLOAD.

Destination: VNCOUT and VNCLOG.

Action: Collect the agent job output and contact SDS Technical Support.

VNC1403E

SSMALLOC SPACE=VNC,CLASS=XXCB RC=return-code

While attempting to obtain storage for a VNAC REXX Loader control block, an error occurred. return-code is the return code from the request.

Destination: VNCOUT and VNCLOG.

Action: Collect the agent job output and contact SDS Technical Support.

VNC1402E

IRXTERM call failed. RC=return-code.

The VNAC REXX loader task has received a shutdown request but the call to IRXTERM to terminate its local REXX environment failed with return code return-code.

Destination: VNCOUT and VNCLOG.

Action: Review the agent logs to see if it is possible to determine why the IRXTERM call failed. Contact SDS Technical Support for additional assistance.

VNC1401E

SSMCLASS SPACE=VNC,CLASS=XXCB RC=return-code

While defining the VNAC storage class for the VNAC REXX Loader task, an error occurred. return-code is the return code from the request.

Destination: VNCLOG and GUI console.

Action: Collect the agent job output and contact SDS Technical Support.

VNC1400E

Missing or invalid exec name in REFRESH command

Issued in response to a REFRESH MODIFY command. The command was issued without an exec name mask specified or with an exec name mask longer than eight characters.

Destination: GUI console.

Action: None.

VNC1346E

Pipe stage stage-number(STEM), stemroot error-message

Error message issued by VNCRXC08, the PIPE host command, while it was validating the pipe command and found an error in the stemroot name operand of the STEM stage.

The possible values for error-message are missing, too long, invalid characters, and missing end period.

Validation of the pipe command ends with return code 12, indicating a syntax error.

This message applies to the global variable name as shown in VNC9346E.

VNC1345E

Pipe stage stage-number(stage-name), does not have the minimum required operands

Error message issued by VNCRXC08, the PIPE host command, while it was validating a pipe command and found a stage that did not have the minimum number of operands specified to perform its function. Refer to the description of the stage that got the error in the PIPE Host Command and Stage User Guide to find out which operands are required by the stage. Validation of the pipe command ends with return code 12, indicating a syntax error.

VNC1344E

Pipe (pipe-name) cannot be dispatched: decimal-#
task-type tasks required would exceed limit task-limit

Error message issued by VNCRXC08, the PIPE host command, just before it begins dispatching the pipe stage execs when there are not enough attended or unattended tasks to run all the pipe stages. Each pipe stage runs in a separate agent task.

The limits for attended and unattended tasks are configured with the TasksAttended and TasksUnattended statements in the GlobalConfig section of the configuration file that is processed by the OBEYFILE command.

Validation of the pipe command ends with return code 62, indicating insufficient tasks available.

VNC1343I

msg-dump-data

Informational message issued by VNCRXF34, the STAGEOUT function, when the DUMPTEXT or DUMPMDB argument is specified as the sixth argument. NODUMP is the default.

The dump line consists of 16 bytes in hex followed by 16 EBCDIC characters for each 16 bytes of data dumped.

The output format is the same as that produced by the CONSOLE DUMP and XDUMP operands.

DUMPTEXT only shows the MDB text sections. DUMPMDB shows the MDB general, control and text sections.

This argument is intended only for debugging during stage development. No pipe stage currently uses either dump argument.