<snip> With PREFERRED, it does the backup regardless. <unsnip> I've found that this is true except for VSAM files, then you get rc68,rsn412, and open for update nonVSAM (or problematic DSNs) then you get rc19 rsn00
Jack Kelly 202-502-2390 (Office) Bri P <[email protected]> Sent by: IBM Mainframe Discussion List <[email protected]> 07/14/2009 11:59 AM Please respond to IBM Mainframe Discussion List <[email protected]> To [email protected] cc Subject Re: HSM autobackup fuzzy backup Went through the same thing here, for the same reasons, a couple of years back. I changed the SETSYS BACKUP parameter to include SERIALIZATION(PREFERRED) (the default if you don't specify SERIALIZATION is REQUIRED). In both cases, if HSM can't serialise on the dataset first time round, it moves on to the next dataset and makes a note to try later (usually at the end of the 'normal' autobackup window). When it comes to try again, with REQUIRED, if it still can't serialise, it gives up. With PREFERRED, it does the backup regardless. Brian -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Neal Scheffler Sent: 14 July 2009 15:22 To: [email protected] Subject: HSM autobackup fuzzy backup Is there a patch or setting in HSM where if a dataset fails serialization during autobackup, to have HSM do a fuzzy backup anyway? I know the dataset backup will most likely be trash and unusable. This is just to appease management. Thanks, Neal ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
