Yes, I missed the sigl part... Sorry. (must get new glasses :-)
Kris Buelens,
--- freelance z/VM consultant, Belgium ---
-----------------------------------------------------------------------
2016-02-26 20:30 GMT+01:00 Hobart Spitz <[email protected]>:
> Did you not read the part about sigl?
>
> I actually use "... name" UsedName"."ExecType".'LineNo()"...", where
> LineNo() is
>
> LineNo: return sigl
>
> I know enough about the internals of REXX and Pipes that there might be
> issues with getting the line number and/or changing sigl.
>
>
> On Fri, Feb 26, 2016 at 2:25 PM, Kris Buelens <[email protected]>
> wrote:
>
> > Execs often use ùmore than 1 PIPE command, so a default name will not be
> > much help.
> >
> > And, I hope your REXX code does use the default TRACE N, and not TRACE O.
> > With TRACE N all commands ending with a negative return code are traced.
> > PIPE does a very good job in producing negative return codes for syntax
> > errors and alike.
> >
> >
> > Kris Buelens,
> > --- freelance z/VM consultant, Belgium ---
> > -----------------------------------------------------------------------
> >
> > 2016-02-26 16:33 GMT+01:00 Hobart Spitz <[email protected]>:
> >
> > > Would it be feasible to default NAME to something like
> > > UsedName.ExecType.sigl for Rexx programs? UsedName could be word 6 of
> > > PARSE SOURCE and ExecType could be word 4. sigl would be the setting
> > from
> > > the last CALL/function invocation.
> > >
> > > I something like this, and i never have a question where to look when
> > doing
> > > diagnosis.
> > >
> > > On Tue, Feb 16, 2016 at 4:34 PM, Glenn Knickerbocker <[email protected]
> >
> > > wrote:
> > >
> > > > On 2/14/2016 12:55 AM, Paul Gilmartin wrote:
> > > > > addpipe MINE | > 'FILE'I ft fm
> > > > > ... other stuff, perhaps involving other pipes ...
> > > > > select output MINE
> > > > > sever output
> > > >
> > > > I'd read the output to make sure the file is read to completion.
> Also,
> > > > I'm not sure if this is still true, but when the alternate input was
> > > > added to >MDSK, if it wasn't initally connected, >MDSK didn't notice
> > and
> > > > would sometimes wait forever for EOF on the unconnected or even
> > > > undefined stream, so I have stages that connect and read the
> alternate
> > > > output just to make sure the file is closed, like so:
> > > >
> > > > 'addstream both MINE'
> > > > ...
> > > > 'addpipe (end /) *.out.MINE: | a: > FILE'i ft fm '/ a: |
> > *.in.MINE:'
> > > > ...
> > > > 'select both MINE'
> > > > 'sever output'
> > > > 'peekto'
> > > >
> > > > ¬R
> > > >
> > >
> > >
> > >
> > > --
> > > OREXXMan
> > >
> >
>
>
>
> --
> OREXXMan
>
