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 On Thu, 9 Mar 2017 09:45:28 -0500, Robert S. Hansel (RSH) <[email protected]> wrote: >Hi Jeffrey, > >I did read the documentation, several times, but unbeknownst to me at the >time, it was the wrong version - v11.3. Your reply prompted me to look for >more recent documentation, and in the documentation for v12, CA added the >following sentence to the description of DSNPFX='batch.dsn.prefix.': "This hlq >must match the hlq for the BATCHI#x and BATCHO#x data sets that are defined to >the CA 7 started task." > >IMHO, it seems nonsensical that the program would let you specify a prefix >that didn't match the started tasks ones and not give some sort of a warning >or error message. Why else would you have such an option if not to specify >your own datasets (and perhaps this is how it worked prior to v12). > >Regards, Bob > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
