On Sat, 2 Sep 2017 18:13:39 -0700, Charles Mills wrote:
>Elaborating a little bit, it seems like a very promising approach:
>
>- COBOL calling C seems to be fully supported (no personal experience)
>- C invoking UNIX services is about as basic as it gets
>- And C has the power to bridge readily any "incompatibilities" (e.g., "the
>COBOL programmer wants to pass this value in upper case but it needs to be in
>lower case for the called UNIX service"; or "this value will be passed fixed
>length; it needs to have the blanks stripped and be null-terminated").
>
Are all the BPX1* callable services available directly in COBOL?
And BPXBATCH PARM='SH { cmd1; cmd2; ... ; } &'? (I've never mastered the
intricacies
of its "local spawn" variant.)
So: BPX1PIP to create a pipe. (Be sure the descriptors are >2.)
BPXWDYN to allocate dd(STDOUT) to the *input* (yes) end of the pipe.
BPXWDYN to allocate dd(COBOLDD) to the output end of the pipe
BPXBATCH PARM='SH { cmd1; cmd2; ... ; } 2>&1 &' to run the commands in
background.
(Does COBOL ignore the archaic 100-character limit?)
Read the command output from COBOLDD
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
