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 <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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
