The IGD101I is in IBM code. As long as the output volume is SMS controlled, the IGD101I should appear consistenly.
There are some ways that an SMS data set can become non-SMS after the move. This would depend on the ACS rules in place, or whether you are using an Allocation Management product like CA Allocate to redirect allocations, the TOVOL parameter which may have non-SMS target volumes, or if the SMS MC, DC, and SC of the original data was used by setting SMSALLOCY. If that kind of a quick check does not produce the reason, then it would be best to open a case with Level 1 Support and they can look over the documentation. IEF196I appears when a message is for a job running under the MSTR subsystem. This does not appear to be the case here. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Lizette Koehler Sent: Wednesday, October 19, 2016 9:26 AM To: [email protected] Subject: Re: Randomly disappearing IGD101I messages. In my case we have automation suppressing the messages. However, I will see them occasionally when it is preceded by an IEF196I message IEF196I IGD101I .... Our scheduling software reads the SMF Records as they are created. It does not require the IGD101I messages to trigger the next job when a dataset/file is created/updated. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Vernooij, Kees (ITOPT1) - KLM > Sent: Wednesday, October 19, 2016 4:48 AM > To: [email protected] > Subject: Re: Randomly disappearing IGD101I messages. > > I am not looking for a workaround, we already have one. > I am looking for the mysterious algorithm that decided to produce or > not produce IGD101I. This is what makes Control-M trigger a job. > > Kees. > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Elardus Engelbrecht > Sent: 19 October, 2016 12:44 > To: [email protected] > Subject: Re: Randomly disappearing IGD101I messages. > > Vernooij, Kees (ITOPT1) - KLM wrote: > > >Well, the situation is becoming more and more curious: > - I checked 400 runs of the job in the last year and IGD101I appears > in 2/3 of the jobs and does not appear in 1/3 of the jobs, without an > indication of why > > Ok, try this temporary workaround: > > In Control-M, insert JOBEND for the job which creates that dataset. > Now trigger a job which checks whether the dataset is in fact there > (allocated / SMS / etc. ) [1] If true, trigger then your second job. > > Groete / Greetings > Elardus Engelbrecht > > [1] - Something like this little Clist: > > IF &SYSDSN('<datasetname passed as argument>') = OK THEN + > DO > WRITE DATASET FOUND > SET &RC = 0 > END > ELSE + > DO > WRITE DATA SET NOT FOUND > SET &RC = 4 > END > ---------------------------------------------------------------------- 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
