In <a6b9336cdb62bb46b9f8708e686a7ea00e924b4...@nrhmms8p02.uicnrh.dom>,
on 05/25/2012
at 10:23 AM, "McKown, John" <john.mck...@healthmarkets.com> said:
>From my view point, it is because the user of my program simply does
>EXEC PGM=MYPGM rather than PGM=IKJEFT01,PARM='%MYPGM' which runs a,
>in my case, REXX program called MYPGM, which then does the TSO
>allocates for the ISPF datasets, followed by ISPSTART CMD(%MYPGM2).
>Which is either a TSO command, or another REXX program which does a
>TSO CALL to actually invoke the processing program. All that
>"overhead" just so that my program can, for instance, use a DSINFO to
>__easily__ get a list of cataloged datasets and their attributes.
I don't see anything there that you wouldn't also have to do if you
used IKJTSOEV.
>Again, what I really would like is something like the ISPF services
>(non DISPLAY).
CSI is available from COBOL.
>But make them available via a simple COBOL CALL verb without the
>need for the "complicated" JCL and REXX layers.
Are you putting "complicated" in quotes because you agree that it is
*not* complicated? ;-)
>This would allow a COBOL program to easily allocate and "open" a
>PDS, get a list of the members, and then read one or more of the
>members.
A COBOL program can already do those.
>Or use DSINFO for some DASD management reports.
If you want to use the services of an application then you have to set
up the environment of that application.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see <http://patriot.net/~shmuel/resume/brief.html>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
