In Pipe Ahelp Snake I find: > Premature Termination: "snake" terminates when it discovers > that its output stream is not connected.
I found this statement _after_ a little test directly from the XEDIT command line > pipe(sep !)literal + - :!dup *!split!snake 7 2!take 5!term what made me learn I do not know how to enter PIPMOD STOP or hx from Xedit (also could not remember other magic spells) so I forced the user. :) I assume, finished TAKE 5 does not tell SNAKE that it will never get a chance to deliver more than the 5 lines already issued and as such the DUP/SPLIT/SNAKE trio continues work for a time I was not patient enough to wait. Found it using PIPE V.1 R.1 M.12 S.12 Ciao.....Mike PS: Only to grumble is not enough for me, so I entered a. m. pipe again on the CMS command line and tried to brake it there with PIPMOD STOP - with no success at all. PIPMOD ACTIVE results sometimes in DMSABE141T Addressing exception..., and sometimes it shows about the active stage in a bundle of messages (which are delayed when using Fullscreen CMS). PIPMOD STOP ACTIVE helps occasionally: > 14:12:36 MSG FROM FH : PIPMOD1479I Running: ^^^^^^^^^^^^^^^^^^^ > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > 14:12:36 MSG FROM FH : PIPMOD1481I Stage is flagged to stop. P > SW not in CMS/TSO Pipelines code Is the Pipe version too advanced for use on z/VM Version 5 Release 3.0? -- www.Ok.de - die kostenlose E-Mail Adresse
