Thanks . Going through the DFHSM manual finally helped me and performed with the changes
Grateful to everyone who have been so helpful On Mon, 23 Dec 2024, 22:18 Dave Gibney, < [email protected]> wrote: > You really would be better served reading the DFHSM manuals. There are > several changes to the HSM SETSYS commands in your ARCCMDnn member(s) > involved. And the sample JCL for the documented started set are helpful > > > -----Original Message----- > > From: IBM Mainframe Discussion List <[email protected]> On > > Behalf Of Peter > > Sent: Monday, December 23, 2024 3:48 AM > > To: [email protected] > > Subject: Re: DFHSM strange behaviour > > > > Hello > > > > I would like to move these from SMS .managed to NON SMS managed > > BACKUPS > > > > What are the changes required for making it to NON SMS managed volume ? > > > > Peter > > > > On Mon, 23 Dec 2024, 15:34 Dejan Stamatovic, <[email protected]> > > wrote: > > > > > Hello Peter, > > > > > > This kind of behavior is something that has been around for some time. > > > > > > When you see a message like the one you sent: > > > > > > STC19579 ARC0743I JRNL SUCCESSFULLY BACKED UP TO 050 > > > > > > ARC0743I (CONT.) DFHSM.JRNL.BACKUP.V0013042, ON VOLUME(S) > > > > > > what it is refering to here is the version of JRNL backup that got > > > deleted while a new version has been added. > > > > > > So, no wonder you can not see this data set > > DFHSM.JRNL.BACKUP.V0013042. > > > > > > This is a bit confusing I agree. > > > You would expect the message to refer to the newest backup version > > > rather that the one that got dropped! > > > > > > That the way this report has been created. > > > > > > Maybe one day IBM will go around and put in a better message which > > > should really explain what has been happening here. > > > In the meantime..... > > > > > > Best Regards > > > > > > Dejan Stamatovic > > > CROZ D.O.O. > > > > > > ---------------------------------------------------------------------- > > > 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 > > ---------------------------------------------------------------------- > 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
