VNC1331E

Pipe stage stage-number(stage-name), operand “stage-operand” is error-message

Error message issued by VNCRXC08, the PIPE host command, while it was validating the pipe command and found an error in a stage operand. The possible values for error-message are invalid, out of order, duplicate, missing, missing a value, and invalid command. Validation of the pipe command ends with return code 12, indicating a syntax error.

VNC1330E

Pipe stage stage-number(stage-name) is not supported

Error message issued by VNCRXC08, the PIPE host command, when it encounters a valid stage name or abbreviation that is explicitly not supported at the moment, but will be supported in the future. See the PIPE Host Command and Stage User Guide for a list of the stages VNAC supports. Currently, there are no stage names in this category. Message VNC1311E is issued for unrecognized, unsupported stage names.

VNC1329D

Pipe stage stage-number(stage-name), argument length decimal-#, buffer class buffer-id

Debug message issued by VNCRXC08, the PIPE host command, after it has allocated a buffer to contain the stage arguments. Whenever the pipe arguments are longer than 256 bytes, it is necessary to allocate a separate buffer to contain them. The buffers have different class names corresponding to their size up to class B32K that can contain an argument list up to 32,736 bytes in length.

VNC1328E

Pipe stage stage-number(stage-name) argument length decimal-#, is too long

Error message issued by VNCRXC08, the PIPE host command, while it was validating the pipe command and found a stage argument list longer than 32,736 bytes. Validation of the pipe command ends with return code 12, indicating a syntax error.

VNC1327E

Connector label beginning with text-string is over 8 characters long

Error message issued by VNCRXC08, the PIPE host command, while it was validating a pipe command and found a connector label that was over 8 characters. Stage names, connector labels, and stage modifiers all are 8 characters or less in length.

VNC1326D

program-name: stage-name(task-name),PIPE=pipe-name(exec-name),STAGE=stage-number,PSTG(pstg-address),CPB(cpb-address)

Debug message issued by VNCRXM03, the REXX exec exit, upon being called by REXX before starting execution of a pipe stage exec. The purpose of the exit is to create and initialize a common set of REXX variables with values unique to each pipe stage exec to control the stage’s processing. For the SAFE stage, it loads the default safe with the message that triggered a message rule to call the exec that called the pipe command.

VNC1325E

Stage modifier text-string is invalid before debug option

Error message issued by VNCRXC08, the PIPE host command, when the stage modifier “NOT” is specified before either stage debug option, (DEBUG) or (DBGEXC). The required order of items that may precede the stage name, is connector label, stage debug option, and, last, stage modifier.

VNC1324I

stage-name (stage-number) awaits input from stage-name (stage-number) on stream stream-number

Informational message issued by VNCRXC08, the PIPE host command, as a result of a clogged pipe being detected and the DEBUG 2 pipe option having been specified. The message is issued after the clog is detected and before each pipe stage is signaled to terminate so it can display the status of each active input stream at the time of the clog.

VNC1323I

stage-name (stage-number) waiting to output to stage-name (stage-number) on stream stream-number

Informational message issued by VNCRXC08, the PIPE host command, as a result of a clogged pipe being detected and the DEBUG 2 pipe option having been specified. The message is issued after the clog is detected and before each pipe stage is signaled to terminate so it can display the status of each active output stream at the time of the clog.

VNC1322E

Pipeline pipe-name in exec exec-name is clogged

Error message issued by VNCRXC08, the PIPE host command when it detects that the TCB CPU time consumed by all the active stage tasks, since the last time it checked, has not changed enough to indicate normal processing. All stages are signaled to terminate immediately and the pipe command end with return code 50.