On Fri, Mar 10, 2017 at 8:40 AM, Jeffrey Holst <[email protected]> wrote:
> Bob, > > I just did a test on my 11.3 system (soon to be upgraded to 12.0). > > While the 11.3 documentation fails to include the sentence that you note > was added in 12.0, that sentence appears to describe how 11.3 works as > well. When I created my own set of batch terminal datasets, the output from > the commands was missing. > > The point of the option seems to be to allow the prefix for the batch > terminal datasets to not match the prefix on the COMMDS dataset, not to > allow each and every user to have their own set of batch terminal datasets. > I would think it would most often be set in the proc by the person setting > up CA-7. It does not really appear to be a proc parameter intended to be > used at the whim of the person executing SASSBSTR. > > Jeff > > I'll bet this is so convoluted because it was designed many years ago, I remember running the predecessor on an MVS system back in the 1980s. There weren't really any MVS APIs for "Inter Process Communications" back then, other than perhaps an LU-LU connection via VTAM. In today's z/OS, I (personally) would use UNIX message queues. They are designed much like a "mail box" wherein multiple processes can drop individual messages, then read by the same, or another, process. They remind me a bit of CICS temporary storage queues. -- "Irrigation of the land with seawater desalinated by fusion power is ancient. It's called 'rain'." -- Michael McClary, in alt.fusion Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
