When CA Disk moves SMS data sets, it renames the original to a temporary name 
and creates the new one with the existing name.  If the new data set is 
correctly created, cataloged, written, and closed, then CA Disk deletes the 
original (now renamed) data set.  If the move operation fails the original data 
set is renamed back to the original name.  The Auto Restore intercepts would 
not become involved, but the CA Disk SVC will intervene so that the last use 
date remains the same.

IGD101I is produced for a new SMS data set allocation.  IGD103I is for existing 
SMS data sets.  

Is it possible that the moved data set would sometimes be created non-SMS?  
This might be due to redirection by the ACS routine or an allocation management 
product such as CA Allocate.

Also check the CA Disk SYSPARM SMSALLOC, which determines if CA Disk passes the 
existing STORCLAS, DATACLAS, and MGMTCLAS to the allocation request for the 
move.  

Bob Longabaugh
CA Technologies
Storage Management

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Greg Shirey
Sent: Tuesday, October 18, 2016 9:27 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Randomly disappearing IGD101I messages.

I would suggest asking CA about the DMS step not generating the IGD101I 
message.  (DMS has a "hook" in SMS, doesn't it?) 

Regards,
Greg Shirey
Ben E. Keith Company

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Tuesday, October 18, 2016 8:46 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Randomly disappearing IGD101I messages.

One I see BMC has asked for doc. I would definitely do that.
Two, I concur with Tom Conley, Most scheduling software will provide an SMF 
Exit in order to see when datasets are created/updated.  

I would follow up with BMC and see what they say.  If they are dependent on 
IGD101I then you need to open a case to IBM on how or when the IGD101I is 
produced to SYSLOG.

A message is produced or not based on MPF list, Automation Tools, or a user 
exit.  The Vendors (IBM and BMC) should be able to help you determine why this 
is going on.

What z/OS Maintenance has been implemented when you first noticed this issue 
What BMC maintenance has been implemented when you first noticed this issue

What user exits are in your system (IEF*) or MPF List exit, or Automation tool 
changes.



----------------------------------------------------------------------
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

Reply via email to