Although is a little hassle to setup if you dont have it already, there is the SMS storage class exit, which can be found in SYS1.SACBCNTL(IGDACSSC). I used this a lot in the early days of SMS, specifying ACCT=DEBUG on the EXEC card of the job/STC/TSO-id of the task in question, to prompt the exit to write out the R/O variables presented in the SC ACS routine. It was highly useful to understand what was being presented to the ACS routines in 'problem situations', and also allowed appropriate testcases to be constructed with the assurance that the 'inputs' were "real-world" (and thus, valid!), rather than just assumptions of what gets presented (coz it can matter quite a lot!).
Looks like it has been enhanced at some point in the last couple of decades, to write out SMF records containing the R/O variables....which is pretty neat. On 13 September 2013 07:44, Vernooij, CP - SPLXM <[email protected]>wrote: > No I can't. I worked together with the supplier and they told me which > parameters were passed to my SC routine what it did (did wrong). > > Kees. > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of efinnell15 > Sent: Thursday, September 12, 2013 22:04 > To: [email protected] > Subject: Re: ACS routine trace. > > Can you turn on verbose logging for the specific APP during the event in > question? Maybe something irregular would solve the mystery. I would > guess something like a temp creation and a rename. > > > > In a message dated 09/12/13 14:46:28 Central Daylight Time, > [email protected] writes: > I can only debug this problem in a live envirionment, hence the > 'tracing' needed for the live ACS routines. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO IBM-MAIN > ******************************************************** > For information, services and offers, please visit our web site: > http://www.klm.com. This e-mail and any attachment may contain > confidential and privileged material intended for the addressee only. If > you are not the addressee, you are notified that no part of the e-mail or > any attachment may be disclosed, copied or distributed, and that any other > action related to this e-mail or attachment is strictly prohibited, and may > be unlawful. If you have received this e-mail by error, please notify the > sender immediately by return e-mail, and delete this message. > > Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its > employees shall not be liable for the incorrect or incomplete transmission > of this e-mail or any attachments, nor responsible for any delay in receipt. > Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch > Airlines) is registered in Amstelveen, The Netherlands, with registered > number 33014286 > ******************************************************** > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
