The management class on the dataset may be set to require backup or migration to Level 1 before allowing migration to ML2.
On Tue, Dec 31, 2019 at 5:31 AM Lennie Dymoke-Bradshaw <[email protected]> wrote: > > Is it possible you have a tape device which is stuck in some allocation > failure? > > I encountered one of these many years back. Device management had issued a > message for a failed allocation and the message had been DOMed. Net result > was that tape allocations hung behind the first failure. I my case they hung > for several weeks. All tape used in this installation was for DFHSM, so it > looked like a DFHSM error. > > Lennie Dymoke-Bradshaw | Security Lead | RSM Partners Ltd > Web: www.rsmpartners.com > ‘Dance like no one is watching. Encrypt like everyone is.’ > > -----Original Message----- > From: IBM Mainframe Discussion List <[email protected]> On Behalf Of > Jake Anderson > Sent: 30 December 2019 03:50 > To: [email protected] > Subject: [IBM-MAIN] Strange Migration behaviour DFHSM > > Hi > > Our DFHSM is a single host based . Strange behaviour an noticing with it as > when i manually try to HMIGRATE to ML2(Virtual tape) and it's still in DFHSM > request queue for more than a 1 day. I scanned through HSM log and i dont see > any error related to the dataset am trying to migrate. > > The MCDS is at 90% and it's threshold is at 95%. Can this be a real issue? > > Jake > > ---------------------------------------------------------------------- > 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 -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
