No, I didn't. But I don't think this will help here, because I don't know what is being presented to the ACS routines and the problem occurs only on a specific allocation of a specific product with one specific data set. I can only debug this problem in a live envirionment, hence the 'tracing' needed for the live ACS routines. Kees.
________________________________ Van: IBM Mainframe Discussion List namens Darth Keller Verzonden: do 12-9-2013 17:21 Aan: [email protected] Onderwerp: Re: ACS routine trace. I'm curious. Do you ever use the NaviQuest SMS test facility? ddk But first I must trigger some trace data. I found there is an SMS trace, but I wonder if this produces much more than I need. I found a replacement for the WRITE-trace mechanism: I defined a Storage Class that is not used and at the point that I needed the WRITE trace info, I set the SC to this specific SC. By moving this piece of code to different decision points in the SC routine, I found the place where it made the wrong decision. I could define several trace-SCs and at point 1 set SC1, at point 2 set SC2 etc. Thus one can determine which code was executed. A little bit complicated, but an adequate replacement for the missing WRITE information. Kees. ---------------------------------------------------------------------- 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
