Re: ARC0104I INVALID INITIALIZATION COMMAND
How about an RFE to stop doing this: 07:00:04.58 S0002089 0090 ARC0522I SPACE MANAGEMENT STARTING ON VOLUME 783 783 0090 ARC0522I (CONT.) SMS019(SMS) AT 07:00:04 ON 2018/06/22, SYSTEM DVLP 07:00:04.79 S0002089 0090 ARC0523I SPACE MANAGEMENT ENDED ON VOLUME SMS019, 784 784 0090 ARC0523I (CONT.) DATA SET(S) MIGRATED/DELETED, 00 784 0090 ARC0523I (CONT.) TRACK(S) FREED, MINAGE 0, TIME 07:00:04 07:00:04.79 S0002089 0090 ARC0522I SPACE MANAGEMENT STARTING ON VOLUME 785 785 0090 ARC0522I (CONT.) SMS018(SMS) AT 07:00:04 ON 2018/06/22, SYSTEM DVLP 07:00:04.81 S0002089 0090 ARC0523I SPACE MANAGEMENT ENDED ON VOLUME SMS020, 786 786 0090 ARC0523I (CONT.) DATA SET(S) MIGRATED/DELETED, 00 786 0090 ARC0523I (CONT.) TRACK(S) FREED, MINAGE 0, TIME 07:00:04 07:00:04.82 S0002089 0090 ARC0522I SPACE MANAGEMENT STARTING ON VOLUME 787 787 0090 ARC0522I (CONT.) SMS017(SMS) AT 07:00:04 ON 2018/06/22, SYSTEM DVLP 07:00:04.97 S0002089 0090 ARC0523I SPACE MANAGEMENT ENDED ON VOLUME SMS018, 788 788 0090 ARC0523I (CONT.) DATA SET(S) MIGRATED/DELETED, 00 788 0090 ARC0523I (CONT.) TRACK(S) FREED, MINAGE 0, TIME 07:00:04 07:00:04.98 S0002089 0090 ARC0522I SPACE MANAGEMENT STARTING ON VOLUME 789 789 0090 ARC0522I (CONT.) SMS016(SMS) AT 07:00:04 ON 2018/06/22, SYSTEM DVLP 07:00:05.00 S0002089 0090 ARC0523I SPACE MANAGEMENT ENDED ON VOLUME SMS017, 790 790 0090 ARC0523I (CONT.) DATA SET(S) MIGRATED/DELETED, 00 790 0090 ARC0523I (CONT.) TRACK(S) FREED, MINAGE 0, TIME 07:00:04 07:00:05.01 S0002089 0090 ARC0522I SPACE MANAGEMENT STARTING ON VOLUME 791 791 0090 ARC0522I (CONT.) SMS015(SMS) AT 07:00:05 ON 2018/06/22, SYSTEM DVLP 07:00:05.08 S0002089 0090 ARC0523I SPACE MANAGEMENT ENDED ON VOLUME SMS016, 792 792 0090 ARC0523I (CONT.) DATA SET(S) MIGRATED/DELETED, 00 792 0090 ARC0523I (CONT.) TRACK(S) FREED, MINAGE 0, TIME 07:00:05 07:00:05.09 S0002089 0090 ARC0522I SPACE MANAGEMENT STARTING ON VOLUME 793 793 0090 ARC0522I (CONT.) SMS014(SMS) AT 07:00:05 ON 2018/06/22, SYSTEM DVLP 07:00:05.13 S0002089 0090 ARC0523I SPACE MANAGEMENT ENDED ON VOLUME SMS015, 794 794 0090 ARC0523I (CONT.) DATA SET(S) MIGRATED/DELETED, 00 794 0090 ARC0523I (CONT.) TRACK(S) FREED, MINAGE 0, TIME 07:00:05 07:00:05.14 S0002089 0090 ARC0522I SPACE MANAGEMENT STARTING ON VOLUME 795 795 0090 ARC0522I (CONT.) SMS013(SMS) AT 07:00:05 ON 2018/06/22, SYSTEM DVLP 07:00:05.22 S0002089 0090 ARC0523I SPACE MANAGEMENT ENDED ON VOLUME SMS014, 796 796 0090 ARC0523I (CONT.) DATA SET(S) MIGRATED/DELETED, 00 796 0090 ARC0523I (CONT.) TRACK(S) FREED, MINAGE 0, TIME 07:00:05 07:00:05.23 S0002089 0090 ARC0522I SPACE MANAGEMENT STARTING ON VOLUME 797 797 0090 ARC0522I (CONT.) SMS012(SMS) AT 07:00:05 ON 2018/06/22, SYSTEM DVLP 07:00:05.27 S0002089 0090 ARC0523I SPACE MANAGEMENT ENDED ON VOLUME SMS013, 798 798 0090 ARC0523I (CONT.) DATA SET(S) MIGRATED/DELETED, 00 798 0090 ARC0523I (CONT.) TRACK(S) FREED, MINAGE 0, TIME 07:00:05 07:00:05.28 S0002089 0090 ARC0522I SPACE MANAGEMENT STARTING ON VOLUME 799 799 0090 ARC0522I (CONT.) SMS011(SMS) AT 07:00:05 ON 2018/06/22, SYSTEM DVLP 07:00:05.35 S0002089 0090 ARC0523I SPACE MANAGEMENT ENDED ON VOLUME SMS012, 800 800 0090 ARC0523I (CONT.) DATA SET(S) MIGRATED/DELETED, 00 800 0090 ARC0523I (CONT.) TRACK(S) FREED, MINAGE 0, TIME 07:00:05 07:00:05.35 S0002089 0090 ARC0522I SPACE MANAGEMENT STARTING ON VOLUME 801 801 0090 ARC0522I (CONT.) SMS010(SMS) AT 07:00:05 ON 2018/06/22, SYSTEM DVLP 07:00:05.45 S0002089 0090 ARC0523I SPACE MANAGEMENT ENDED ON VOLUME SMS011, 802 802 0090 ARC0523I (CONT.) DATA SET(S) MIGRATED/DELETED, 00 802 0090 ARC0523I (CONT.) TRACK(S) FREED, MINAGE 0, TIME 07:00:05 07:00:05.46 S0002089 0090 ARC0522I SPACE MANAGEMENT STARTING ON VOLUME 803 803 0090 ARC0522I (CONT.) SMS009(SMS) AT 07:00:05 ON 2018/06/22, SYSTEM DVLP 07:00:05.53 S0002089 0090 ARC0523I SPACE MANAGEMENT ENDED ON VOLUME SMS010, 804 804 0090 ARC0523I (CONT.) DATA SET(S) MIGRATED/DELETED, 00 804 0090 ARC0523I (CONT.) TRACK(S) FREED, MINAGE 0, TIME 07:00:05 07:00:05.54
Re: ARC0104I INVALID INITIALIZATION COMMAND
Please open an RFE for this, we responded to another RFE to enhance the ARC0103I message to be more descriptive in the next release. We will look at doing the same for the ARC0104I message. Thanks, Max Smith DFSMS Development -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ARC0104I INVALID INITIALIZATION COMMAND
I set up the PDO logs to swap just like the SMF logs, When HSM would swap from X to Y, Automation would kick off a IEBGENER to copy it to a "permanent " dataset with the System & Time stamps as dataset name and HSM/SMS Management Class to keep them around for 45 days with No backup and 0 days on primary, and go directly to ML2 "Tape". Jim - Original Message - From: "Gibney, Dave" Newsgroups: bit.listserv.ibm-main To: Sent: Thursday, June 21, 2018 5:28 PM Subject: Re: ARC0104I INVALID INITIALIZATION COMMAND I have both LOG and PDA files. Never needed them, but the recomenadtion was to have them active for IBM if needed. DFHSM.LOGX DFHSM.LOGY DFHSM.PDOX DFHSM.PDOY -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ed Jaffe Sent: Thursday, June 21, 2018 2:21 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ARC0104I INVALID INITIALIZATION COMMAND On 6/21/2018 2:17 PM, Gibney, Dave wrote: > Looking some more and remembering. Do you have the HSM PDA (Problem Determination AID) active? SETSYS PDS() and a couple datasets. > I have a vague memory that this data can also be found using IPCS > against the active region. Or something. Yes. I posted some of that data in response to Carmen Vitullo's query. No help whatsoever... -- 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=CK- VATOToJANlm1EWo7JHmZyFP9PKP4GGqo_6Zp6bWs&s=z41wqfPdr4WHaTk DTu98jbwgbpdwIkUakMf_lDfl6s8&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 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 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ARC0104I INVALID INITIALIZATION COMMAND
My reason for suggesting an APAR is that intrinsic inability to track down the source of an error message strikes me as a design failure. Furthermore, an APAR tied to a defect may get better (= quicker) resolution than an enhancement RFE. In Ed's case, a syntax typo in the initialization options might be difficult capture succinctly. Nonetheless there are products that flag errors by 'line number' without trying to diagnose the error in depth. ISPF HILITE pointed to the problem, which was sufficient to fix it. HSM should be able to provide comparable guidance. Other products do. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Elardus Engelbrecht Sent: Friday, June 22, 2018 1:50 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: ARC0104I INVALID INITIALIZATION COMMAND Jesse 1 Robinson wrote: >I'd say that this is such an egregious oversight that it should be APARable >even after all this time. There's no statute of limitations on bad design. Or ask for a thing to do Syntax Checking of ARCCMDxx just like the one for BPXPRMxx member (SETOMVS SYNTAXCHECK=(??) ). Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ARC0104I INVALID INITIALIZATION COMMAND
Jesse 1 Robinson wrote: >I'd say that this is such an egregious oversight that it should be APARable >even after all this time. There's no statute of limitations on bad design. Or ask for a thing to do Syntax Checking of ARCCMDxx just like the one for BPXPRMxx member (SETOMVS SYNTAXCHECK=(??) ). Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ARC0104I INVALID INITIALIZATION COMMAND
I have both LOG and PDA files. Never needed them, but the recomenadtion was to have them active for IBM if needed. DFHSM.LOGX DFHSM.LOGY DFHSM.PDOX DFHSM.PDOY > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Ed Jaffe > Sent: Thursday, June 21, 2018 2:21 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: ARC0104I INVALID INITIALIZATION COMMAND > > On 6/21/2018 2:17 PM, Gibney, Dave wrote: > > Looking some more and remembering. Do you have the HSM PDA > (Problem Determination AID) active? SETSYS PDS() and a couple datasets. > > I have a vague memory that this data can also be found using IPCS against > the active region. Or something. > > Yes. I posted some of that data in response to Carmen Vitullo's query. > No help whatsoever... > > -- > 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=CK- > VATOToJANlm1EWo7JHmZyFP9PKP4GGqo_6Zp6bWs&s=z41wqfPdr4WHaTk > DTu98jbwgbpdwIkUakMf_lDfl6s8&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 > 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
Re: ARC0104I INVALID INITIALIZATION COMMAND
On 6/21/2018 2:17 PM, Gibney, Dave wrote: Looking some more and remembering. Do you have the HSM PDA (Problem Determination AID) active? SETSYS PDS() and a couple datasets. I have a vague memory that this data can also be found using IPCS against the active region. Or something. Yes. I posted some of that data in response to Carmen Vitullo's query. No help whatsoever... -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/ 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ARC0104I INVALID INITIALIZATION COMMAND
Looking some more and remembering. Do you have the HSM PDA (Problem Determination AID) active? SETSYS PDS() and a couple datasets. I have a vague memory that this data can also be found using IPCS against the active region. Or something. > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Jesse 1 Robinson > Sent: Thursday, June 21, 2018 2:02 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: ARC0104I INVALID INITIALIZATION COMMAND > > I'd say that this is such an egregious oversight that it should be APARable > even after all this time. There's no statute of limitations on bad design. > > . > . > J.O.Skip Robinson > Southern California Edison Company > Electric Dragon Team Paddler > SHARE MVS Program Co-Manager > 323-715-0595 Mobile > 626-543-6132 Office ⇐=== NEW > robin...@sce.com > > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Gibney, Dave > Sent: Thursday, June 21, 2018 1:51 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: (External):Re: ARC0104I INVALID INITIALIZATION COMMAND > > > > > -Original Message- > > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > > On Behalf Of Ed Jaffe > > Sent: Thursday, June 21, 2018 1:41 PM > > To: IBM-MAIN@LISTSERV.UA.EDU > > 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 > > -- > 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
Re: ARC0104I INVALID INITIALIZATION COMMAND
On 6/21/2018 11:00 AM, Ed Jaffe wrote: I recently noticed we're receiving the following (maybe three times) on the MVS log during HSM startup: ARC0104I INVALID INITIALIZATION COMMAND Found them! How? Via manual inspection! (HSM facilities were no help AT ALL...) I used ISPF highlighting with "HILITE PLI LOGIC PAREN" and discovered a colorized paren mismatch situation. Turns out the last (continued) part of an ADDVOL statement was repeated unnecessarily and then cloned to two other nearly-identical non-SMS volume definitions. -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/ 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ARC0104I INVALID INITIALIZATION COMMAND
I'd say that this is such an egregious oversight that it should be APARable even after all this time. There's no statute of limitations on bad design. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Gibney, Dave Sent: Thursday, June 21, 2018 1:51 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: ARC0104I INVALID INITIALIZATION COMMAND > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Ed Jaffe > Sent: Thursday, June 21, 2018 1:41 PM > To: IBM-MAIN@LISTSERV.UA.EDU > 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 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ARC0104I INVALID INITIALIZATION COMMAND
> -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Ed Jaffe > Sent: Thursday, June 21, 2018 1:41 PM > To: IBM-MAIN@LISTSERV.UA.EDU > 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 > 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
Re: ARC0104I INVALID INITIALIZATION COMMAND
On 6/21/2018 12:14 PM, John McKown wrote: How about just issuing each HSM command in the member as an operator command, perhaps via (E)JES? That's a thought, but what a *major* PITA. Most of our commands are split across multiple lines with /* xxx */ comments interspersed. It will be very time consuming to edit them all down to a single line each. However, once that's done, I agree we should be able to issue them via TSO HSEND or MODIFY operator command. As I said in my response to Dave Gibney, I'm truly astonished this problem exists in the first place and has been around for so long! -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/ 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
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'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 http://www.phoenixsoftware.com/ 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ARC0104I INVALID INITIALIZATION COMMAND
On Thu, Jun 21, 2018 at 1:53 PM Ed Jaffe wrote: > On 6/21/2018 11:35 AM, Gibney, Dave wrote: > > What is your SETSYS ACTLOGMSGLVL? > > That parameter is not relevant here. I did have ACTLOGMSGLVL(REDUCED) > so, just to prove the point, I changed it to ACTLOGMSGLVL(FULL) and > recycled HSM. No difference... > How about just issuing each HSM command in the member as an operator command, perhaps via (E)JES? > > -- > Phoenix Software International > Edward E. Jaffe > 831 Parkview Drive North > El Segundo, CA 90245 > http://www.phoenixsoftware.com/ > > > > 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- There is no such thing as the Cloud. It is just somebody else’s computer. Maranatha! <>< John McKown -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ARC0104I INVALID INITIALIZATION COMMAND
I expected as much. Another possibility is to insert some LOG commands into your ARCCMD00 perhaps even as frequently as to echo each SETSYS > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Ed Jaffe > Sent: Thursday, June 21, 2018 11:53 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: ARC0104I INVALID INITIALIZATION COMMAND > > On 6/21/2018 11:35 AM, Gibney, Dave wrote: > > What is your SETSYS ACTLOGMSGLVL? > > That parameter is not relevant here. I did have ACTLOGMSGLVL(REDUCED) > so, just to prove the point, I changed it to ACTLOGMSGLVL(FULL) and > recycled HSM. No difference... > > -- > 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=loznVd5jmn- > XnGsBIQGaS3Ub2q_W9GRtuansIHKm6jE&s=2t2SEy0hVfBzXP3I- > 1rB13WKV0pydxdIT7qT4VTW3X8&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 > 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
Re: ARC0104I INVALID INITIALIZATION COMMAND
On 6/21/2018 11:35 AM, Gibney, Dave wrote: What is your SETSYS ACTLOGMSGLVL? That parameter is not relevant here. I did have ACTLOGMSGLVL(REDUCED) so, just to prove the point, I changed it to ACTLOGMSGLVL(FULL) and recycled HSM. No difference... -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/ 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ARC0104I INVALID INITIALIZATION COMMAND
Back when I had this issue, my only choice was to count responses and then count commands. Some of the commands had relatively unique responses which assisted in synching my counts. Based on your question, it appears that newer versions of HSM don't provide any additional information. If you have the time and a sandbox LPAR, you could start HSM with only the first 10 commands and look for the error. Then add 10 more in each iteration. This will reduce the span of commands to be checked. > -Original Message- > From: IBM Mainframe Discussion List On Behalf > Of Ed Jaffe > Sent: Thursday, June 21, 2018 11:01 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: ARC0104I INVALID INITIALIZATION COMMAND > > I recently noticed we're receiving the following (maybe three times) on > the MVS log during HSM startup: > > ARC0104I INVALID INITIALIZATION COMMAND -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ARC0104I INVALID INITIALIZATION COMMAND
What is your SETSYS ACTLOGMSGLVL? > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Ed Jaffe > Sent: Thursday, June 21, 2018 11:01 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: ARC0104I INVALID INITIALIZATION COMMAND > > I recently noticed we're receiving the following (maybe three times) on the > MVS log during HSM startup: > > ARC0104I INVALID INITIALIZATION COMMAND > > How can we tell which commands are generating this? I can find no HSM- > produced log of commands and responses. All I see are the responses. > > Thanks, > > -- > 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=NFuXAZR0ZpDnfKO7veV0RNxEx7 > hDB9fT6sfPVF7jHCY&s=hC7IEUU3uTSU0MRGgey6HTYPYvQDeNYawq0d3ujL1x > I&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 > 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
Re: ARC0104I INVALID INITIALIZATION COMMAND
okay, I thought so, I was hoping it would provide more info Carmen Vitullo - Original Message - From: "Ed Jaffe" To: IBM-MAIN@LISTSERV.UA.EDU Sent: Thursday, June 21, 2018 1:22:08 PM Subject: Re: ARC0104I INVALID INITIALIZATION COMMAND On 6/21/2018 11:15 AM, Carmen Vitullo wrote: > Been a while for me supporting / having HSM > IIRC isn't there a LOG1 + LOG2 that goes to a dataset? Yes. Such data sets exist. Browsing under ISPF you see only the comman responses, not the commands themselves. For example, I see "SETSYS COMMAND COMPLETED" but not the actual SETSYS command that was issued: .ÃM:_.(Þå3STARTUP.é..M:_.+.É3**OPER**.ARC0001I DFSMS ..M:_.Ý@Û3.DSR..^ .8 .þ.ã..M:_.]1.3.u..**OPER**.ARC1700I DFSMSHSM COMMANDS ARE RA .S.\..M:_.AÓM3...M. .à**IPL***.. .S.\..M:_.BÁa3...M. .à**IPL***.. .m.\..M:_.B..3...M. .à**IPL***.. ...\..M:_.D..3...M. .à**IPL***.. .:M:_.Eý<3. .à**IPL***.. .0M:_.Hm.3. .à**IPL***.. .ûM:_.ÃX3. .à**IPL***.. ..M:_.ôa.3. .à**IPL***.. ..\..M:_.ö.43...M. .à**IPL***.. .=M:_.K;ë3.À..**OPER**.ARC0100I SETSYS COMMAND COMPLETED .R.\..M:_.NëÔ3...M. .à**IPL***.. .cM:_.O.Ð3. .à**IPL***.. ...\..M:_.P..3...M. .à**IPL***.. -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/ 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 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
Re: ARC0104I INVALID INITIALIZATION COMMAND
On 6/21/2018 11:15 AM, Carmen Vitullo wrote: Been a while for me supporting / having HSM IIRC isn't there a LOG1 + LOG2 that goes to a dataset? Yes. Such data sets exist. Browsing under ISPF you see only the comman responses, not the commands themselves. For example, I see "SETSYS COMMAND COMPLETED" but not the actual SETSYS command that was issued: .ÃM:_.(Þå3STARTUP.é..M:_.+.É3**OPER**.ARC0001I DFSMS ..M:_.Ý@Û3.DSR..^ .8 .þ.ã..M:_.]1.3.u..**OPER**.ARC1700I DFSMSHSM COMMANDS ARE RA .S.\..M:_.AÓM3...M. .à**IPL***.. .S.\..M:_.BÁa3...M. .à**IPL***.. .m.\..M:_.B..3...M. .à**IPL***.. ...\..M:_.D..3...M. .à**IPL***.. .:M:_.Eý<3. .à**IPL***.. .0M:_.Hm.3. .à**IPL***.. .ûM:_.ÃX3. .à**IPL***.. ..M:_.ôa.3. .à**IPL***.. ..\..M:_.ö.43...M. .à**IPL***.. .=M:_.K;ë3.À..**OPER**.ARC0100I SETSYS COMMAND COMPLETED .R.\..M:_.NëÔ3...M. .à**IPL***.. .cM:_.O.Ð3. .à**IPL***.. ...\..M:_.P..3...M. .à**IPL***.. -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/ 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ARC0104I INVALID INITIALIZATION COMMAND
Been a while for me supporting / having HSM IIRC isn't there a LOG1 + LOG2 that goes to a dataset? Carmen Vitullo - Original Message - From: "Ed Jaffe" To: IBM-MAIN@LISTSERV.UA.EDU Sent: Thursday, June 21, 2018 1:00:51 PM Subject: ARC0104I INVALID INITIALIZATION COMMAND I recently noticed we're receiving the following (maybe three times) on the MVS log during HSM startup: ARC0104I INVALID INITIALIZATION COMMAND How can we tell which commands are generating this? I can find no HSM-produced log of commands and responses. All I see are the responses. Thanks, -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/ 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 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
ARC0104I INVALID INITIALIZATION COMMAND
I recently noticed we're receiving the following (maybe three times) on the MVS log during HSM startup: ARC0104I INVALID INITIALIZATION COMMAND How can we tell which commands are generating this? I can find no HSM-produced log of commands and responses. All I see are the responses. Thanks, -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/ 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
