My ACS routines report (to JESYSMSG) the results and a code to indicate the place the final decision was made. It is my choice to do this reporting. When I was more concerned about performance in ACS routines, I built some Rexx code to add/remove this logging output. I later found it wasn't worth the trouble to turn this logging off (and MSGLEVEL=(0,0) is available also:)
But, I tend to the "there can't be too much available information" side of the verbosity argument. Back when much actually printed on paper, I got more push back than I do now. > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Paul Gilmartin > Sent: Friday, October 10, 2014 2:31 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: TSO in batch, RECEIVE storage class - solved > > On 2014-10-10 11:16, Mike Schwab wrote: > > How about, on the existing allocated message, listing the Dataclas, > > Mgmtclas, Storclas, and Storgrop? > > How about, on the existing dsn deleted message, listing the # volumes, > > # extents, and # tracks currently allocated? > > > Insufficient in some cases. If the perpetrator is a TSO or OMVS session, the > message must appear on the user's terminal; it shouldn't be necessary (and > isn't always permitted) to browse SYSLOG. Similarly, for batch jobs, such > messages should appear in the job log, not only in SYSLOG. > > -- gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
