There is a nice product from DTS software called SMSDEBUG ($$) which can do this.
Or it is possible that any JCL Checker (PROJCL, JCLPLUS, etc...) might help Lizette -----Original Message----- >From: Paul Gilmartin <[email protected]> >Sent: Oct 24, 2012 8:55 AM >To: [email protected] >Subject: SMS Diagnosis/trace? > >In JCL I specified UNIT=esoteric-for-(virtual)-tape device. z/OS >instead allocated DASD. After some thrashing around and asking >the requester if he knew what was going on, I apealed to our systems >programmer, who said: > > ... in that job that you did not get any tape mounts for that > first step. The reason was because the SMS ACS routines > recognized the XXXXXX hilevel qualifier and assigned it to the > YYY storage class. The YYY storage class has the GUARANTEED > SPACE attribute set to NO so the UNIT and VOLUME parameters were > ignored. If the GUARANTEED SPACE attribute had been YES, we > would have gotten some type of a conflict message and the job > would have failed earlier. > >Is there any MSGLEVEL I can specify that will tell me exactly what >happened, and why so I neednt bother the sysprogs? Or, perhaps >a utility (cbttape.org?) which will analyze a DD statement image >and tell me what really happens? > >This design is WRONG! It's fine for SMS to supply elided options, >but any options explicitly supplied by the programmer should be >honored, or result in a JCL error _clearly_ describing the cause >and citing the applicable SMS rule. The message I received about >missing SPACE option wasn't helpful. Is there a setting for this? > >There's too much DWIM here. > >-- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
