> -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Ed Jaffe > Sent: Thursday, June 21, 2018 1:41 PM > To: [email protected] > Subject: Re: ARC0104I INVALID INITIALIZATION COMMAND > > On 6/21/2018 11:59 AM, Gibney, Dave wrote: > > I expected as much. Another possibility is to insert some LOG commands > > into your ARCCMD00 perhaps even as frequently as to echo each SETSYS > > I thought we could try something like that, but it seems that some (or maybe > all?) of the commands are being executed asynchronously. Plus, I'm not sure > what kind of "log" commands are available in the ARCCMDxx member. Do > you know?
I've not found a command I couldn't include in ARCCMDxx, but I admit I've not tried many. I didn't know about the aysnc possibility, but I guess I'm not surprised DFHSM has been "mulit threaded" from the start. I am sorry, I can't remember the last time I had an error to find here. Once set, this is not a frequently changing member :) My last thought now is a tedious hand comparison against the results of a QUERY SETSYS > > I'm truly astonished that this problem exists in the first place and -- based > on > responses I've seen so far -- has been around from the beginning. Should not > the error message include the first 'n' characters of command text and/or > line number in the input "deck"? The whole thing is crazy! No one has > complained to IBM about this serious shortcoming before now?! > > -- > Phoenix Software International > Edward E. Jaffe > 831 Parkview Drive North > El Segundo, CA 90245 > https://urldefense.proofpoint.com/v2/url?u=http- > 3A__www.phoenixsoftware.com_&d=DwICaQ&c=C3yme8gMkxg_ihJNXS06Z > yWk4EJm8LdrrvxQb- > Je7sw&r=u9g8rUevBoyCPAdo5sWE9w&m=6HHwIpeS03fXGc0- > 6ZMywYq4ZlEvs6LnH6mTp0zX4Bo&s=I4PoX6uvRkUi-frBbIOv8- > 0sgKN8HSbUYQpch5F7H84&e= > > -------------------------------------------------------------------------------- > This e-mail message, including any attachments, appended messages and the > information contained therein, is for the sole use of the intended > recipient(s). If you are not an intended recipient or have otherwise received > this email message in error, any use, dissemination, distribution, review, > storage or copying of this e-mail message and the information contained > therein is strictly prohibited. If you are not an intended recipient, please > contact the sender by reply e-mail and destroy all copies of this email > message and do not otherwise utilize or retain this email message or any or > all of the information contained therein. Although this email message and any > attachments or appended messages are believed to be free of any virus or > other defect that might affect any computer system into which it is received > and opened, it is the responsibility of the recipient to ensure that it is > virus > free and no responsibility is accepted by the sender for any loss or damage > arising in any way from its opening or use. > > ---------------------------------------------------------------------- > 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
