Hi all, We found the answer.
Apparently IGD101I is produced when SMS creates and catalogues a dataset and Control-M relies on this message to detect dataset creation/cataloguing. But there appear to be other methods to create and catalog SMS managed datasets. As we already discovered, a dataset copied with FDR never produces IGD101I. A dataset copied by DMS sometimes does not produce IGD101I. Depending on the characteristics of the input dataset, DMS apparently takes different actions to create the output dataset: - When the input dataset is not multi-volume, DMS seems to create the output dataset simply via SMS, thereby having IGD101I produced. - When the input dataset is multi-volume DMS takes different actions to create and catalogue the output dataset, apparently not via SMS, so IGD101I is not produced. We noticed that the catalog entry of the output dataset contained the same number of volser-entries as the input dataset, but if the output datasets fits on less volsers than the input dataset, the other volser-entries in the catalogue are candidate volsers with "*" in the volser field. - FDR apparently always creates and catalogues the dataset itself, without SMS, so IGD101I is never produced. - We did not check what DFdss does. IGD101I is used by Control-M for the 'disp=catalog' rule of dataset triggering. IGD104I is used by Control-M for the 'disp=keep' rule of dataset triggering. In the case of the DMS step IGD104I is always produced, so we changed the Control-M rule to trigger on IGD104I, which solved our problem. However in the FDR case, neither IGD101I nor IGD104I are produced, so Control-M will probably never be triggered on datasets created by FDR. The conclusion is, that IGD101I (and even IGD104I in some situations) is not a reliable indicator for dataset creation and we will report this to BMC. Kees. -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Vernooij, Kees (ITOPT1) - KLM Sent: 18 October, 2016 11:04 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Randomly disappearing IGD101I messages. Hello, Control-M uses message IGD101I for dataset triggering: when a data set has been created, as indicated by IGD101I, a job must be triggered. We see every now and then that the triggering is not working, because IGD101I is not produced, although the dataset has been created. We don't have any clue on what makes IGD101I not appear in some situations: it happens in different runs of the same job, on same system, in the same step, with the same results, for nearly the same dataset, in the same SMS Storage Group. Anybody recognized this or has an idea where to look? Thanks, Kees. ******************************************************** 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 lists...@listserv.ua.edu 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
