The CP stage in question is used to send command output back to the original sender. PipeServ does not protect the CP stage from command output lines (think REXX TRACE I, e.g.) that are longer than CP can hande.
The most likely fix is a SPILL 255 or similar, but my attempts to position it have not met with success. I'm sure there is someone very smart out there who has developed a fix. On Thu, May 15, 2014 at 4:00 PM, Bruce Hayden <bjhay...@gmail.com> wrote: > The help for the cp stage states: > > "cp" terminates with an error message if a command is longer than the > 240 > bytes supported by CP. > > Since 240 bytes is all that CP supports via diag 8, there is no fix > possible in pipelines. > > Or maybe I didn't understand your problem with pipeserv? > > > On Thu, May 15, 2014 at 3:03 PM, Hobart Spitz <orexx...@gmail.com> wrote: > > > If anyone has a fix for this problem, which causes PipeServ to stop > > replying when long output lines are issued, could you post it to the > list? > > > > > > Thanks. > > > > > > PIPCOM062E Command length 263 too long for CP. > > > > PIPMSG004I ... Issued from stage 3 of pipeline 7 name "pipsrv03". > > > > PIPMSG001I ... Running "cp". > > > > > > > > -- > > OREXXMan > > > > > > -- > Bruce Hayden > z/VM and Linux on System z ATS > IBM, Endicott, NY > -- OREXXMan
