Michael, For a quick fix, do you have any of the more popular JCL management tools? If so, there is a way to always ensure the dataset is allocated and available before the initial access from your production processing hits it for the first time.
Mitch -----Original Message----- From: Michael Bieganski <[email protected]> To: IBM-MAIN <[email protected]> Sent: Fri, Feb 21, 2014 8:16 am 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 cheduling processes. ccassionally, our ops support gets paged out because a process is delayed nd it turns out it was because aid dataset was migrated and had to be recalled. his dataset's management class has nolimit on expires, and blanks for Primary Days' artial Release is 'yes' so could hsm be migrating this dsn in Primary pace mgmt, despite we have rimary-days set to blanks??? nd if so, short of setting partial release to no, how can we keep an sms anaged dataset from ever migrating at all? ---------------------------------------------------------------------- or IBM-MAIN subscribe / signoff / archive access instructions, end 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
