On 8/21/2013 10:41 AM, bob gailer wrote: > On 8/21/2013 10:19 AM, John P. Hartmann wrote: >> The error is in a stage, not a pipeline command.
And note that "pipeline command" here means a command issued *to* Pipelines, such as PEEKTO or RESOLVE, not the CMS command that invokes Pipelines. > Is it safe to say that messages 2 and 3 will never be issued at the same > time for 1 pipe specification? ADDPIPE or CALLPIPE will issue both when the scanner finds an error in validating a stage's name or required argument: pipe literal addpipe junk | pipcmd PIPSCB027E Entry point JUNK not found. PIPMSG002I ... Processing "addpipe junk". PIPSCA003I ... Issued from stage 1 of pipeline 1. PIPSCA001I ... Running "junk". Ready(-0027); pipe literal callpipe specs | pipcmd PIPFPI011E Null or blank parameter list found. PIPMSG002I ... Processing "callpipe specs". PIPSCA003I ... Issued from stage 1 of pipeline 1. PIPSCA001I ... Running "specs". Ready(00011); ¬R
