Pipe stage stage-number(VNAC), is missing command string
Error message issued by VNCRXC08, the PIPE host command, while it was validating the pipe command and did not find any command string operand for the VNAC stage. Validation of the pipe command ends with return code 12, indicating a syntax error.
Pipe stage stage-number(VNAC), command VNAC-command is not allowed in a pipe
Error message issued by VNCRXC08, the PIPE host command, while it was validating the pipe command and found an error in a stage operand for the VNAC stage that is the name of a VNAC supplied exec that is not allowed in a pipe. Exec names that are not allowed in the VNAC stage are pipe stage execs, execs that invokes a panel, automated test execs, and the obeyfile exec. Validation of the pipe command ends with return code 12, indicating a syntax error.
Pipe stage stage-number(VAR), variable name 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 that is a global variable name (as shown in VNC9333E) that was an operand of the VAR stage.
The possible values for error-message are invalid, missing, and too long. Validation of the pipe command ends with return code 12, indicating a syntax error.
Pipe stage stage-number(stage-name), text string 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 that is a delimited text string. The possible values for error-message are missing, missing end delimiter, over 255 characters, and empty. Validation of the pipe command ends with return code 12, indicating a syntax error.
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.
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.
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.
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.
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.
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.
