We occasionally have the same problem. Nothing worse than seeing Automation wait for a recall. My take is to put such IPL-critical data sets on a volume not subject to migration at all. We have on every plex a handful of SYSxxx packs that are not SMS managed. Any data set that is crucial to getting a system 'up' (however you define that) should live on a non-migratable volume. I wish I could say that we have achieved that goal. ;-(
. . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] From: Lizette Koehler <[email protected]> To: [email protected], Date: 02/21/2014 08:33 AM Subject: Re: Why does a dataset that should never migrate does occassionally (hsm) Sent by: IBM Mainframe Discussion List <[email protected]> Is it possible someone might be manually migrating the file? I would run a PDA report for the file and see what information has been collected. Info on it can be found in the z/OS V1R12.0 DFSMShsm Diagnosis GC52-1083 I have found this process very helpful. Second, if you have the CBTTAPE.ORG utility DAF installed, then you can run it against your SMF data for the time you suspect it got migrated and see the history for the file. When a file is Migrated there is a Scratch event that is recorded. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Michael Bieganski > Sent: Friday, February 21, 2014 9:16 AM > To: [email protected] > Subject: Why does a dataset that should never migrate does occassionally (hsm) > > Hi, we have a mainframe dataset that is used daily used in our automated > scheduling processes. > Occassionally, our ops support gets paged out because a process is delayed and it > turns out it was because said dataset was migrated and had to be recalled. > this dataset's management class has nolimit on expires, and blanks for 'Primary > Days' > Partial Release is 'yes' so could hsm be migrating this dsn in Primary space mgmt, > despite we have primary-days set to blanks??? > And if so, short of setting partial release to no, how can we keep an sms managed > dataset from ever migrating at all? > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
