kerravon86@yahoo.com.au [hercules-os380]
2018-06-15 22:50:26 UTC
From TSO I would like to be able to go:
proga | progb
and have the output of proga piped to the
input of progb.
The way I was thinking this could work is that
proga could check its command arguments
and see the "|" and instead of using PUTLINE
for stdout it would instead direct the output
to a temp file.
Then when it calls progb it would provide a
DD override list for just SYSIN, and progb
would respect that and open the given
DD name instead of using GETLINE.
For this to work, it would require proga to
start progb, and even though progb is a
flexible TSO CP, it should also be flexible
enough to accept a DD override list. I am
not sure whether ATTACH can start
progb from the TSO environment with a
DD override list. I would like progb to still
use PUTLINE for its output, as there
would be no override for SYSPRINT in
the above scenario, only SYSIN.
Any idea whether this is feasible?
Thanks. Paul.
proga | progb
and have the output of proga piped to the
input of progb.
The way I was thinking this could work is that
proga could check its command arguments
and see the "|" and instead of using PUTLINE
for stdout it would instead direct the output
to a temp file.
Then when it calls progb it would provide a
DD override list for just SYSIN, and progb
would respect that and open the given
DD name instead of using GETLINE.
For this to work, it would require proga to
start progb, and even though progb is a
flexible TSO CP, it should also be flexible
enough to accept a DD override list. I am
not sure whether ATTACH can start
progb from the TSO environment with a
DD override list. I would like progb to still
use PUTLINE for its output, as there
would be no override for SYSPRINT in
the above scenario, only SYSIN.
Any idea whether this is feasible?
Thanks. Paul.