All, I'm bypassing all the commentary following this email.
I think two things are rather obvious: 1) the DATACLAS ACS does not support the RECALL or RESTORE environment 2) DFSMShsm and DFSMSdss store the original dataset attributes as part of the migration or backup, and use this to allocate the new dataset Considered alone or together, these conditions make it kind of obvious that you cannot change the dataset attributes when you recall a dataset. Try restoring a DFSMSdss dataset to a pre-allocated dataset with different attributes. What happens? What other discussion could there be on this besides a rewrite of the DFSMSdss and or DFSMShsm data mover? Ron > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Don Williams > Sent: Wednesday, January 09, 2013 11:09 AM > To: [email protected] > Subject: Re: [IBM-MAIN] ESDS extent ... > > When HSM (or equivalent product) recalls a data set, it has to allocate the > space on the primary DASD. That allocation will need data class attributes. > In my opinion, the HSM manuals are not clear how or where HSM gets the > data class attributes. I believe you, but it would be nice if the HSM manuals > clearly stated that the data class attributes of a recalled data set were solely > obtained from the migrated copy of data set and not from the current SMS > data class. > > From the z/OS V1R12.0 DFSMShsm Storage Administration manual: > ========================================================== > ================== > ============================================= > Chapter 54. RECALL command: Recalling a specific migrated data set > > The RECALL command recalls a migrated data set. If you want, you can > specify the volume and type of unit where DFSMShsm is to recall the data > set. > > If you specify the volume and type of unit when recalling an SMS-managed > data set, the volume and unit type will be passed to the automatic class > selection (ACS) Routines. ACS ultimately determines to which volume the > data set is recalled. > > The FORCENONSMS parameter allows the ability to force recall of an SMS- > managed data set to a non-SMS-managed volume. It is not possible to > convert a data set that is not extended format to a data set that is extended > format during a recall. However, you can convert an extended format data > set to a data set that is not extended format during a recall, if you specify the > FORCENONSMS optional parameter. > ========================================================== > ================== > ============================================= > > Don Williams > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of R.S. > Sent: Tuesday, January 08, 2013 3:32 PM > To: [email protected] > Subject: Re: ESDS extent ... > > W dniu 2013-01-08 21:26, Don Williams pisze: > > HSM Recall does not re-invoke the DataClas ACS routine (several years > > ago, I had to proof that to my teammates). Therefore a recalled data > > set will have the same data class name. Since a data class could > > affect many hundreds or thousands of data sets (we still have some > > applications that cannot handle extended data sets), I've never > > changed a data class from non-extented to extended then tried to > > recall the data set. It would be interesting to know if that would work. > > It is not matter whether DC is called or not (it's not AFAIK). It's matter that > even changed DC does not affect existing dataset parameters. > It will not affect. > Caution: parameters like DVC can be changed dynamically, but actually DVC is > some "potential bahavior" not "actual shape" of the physical object. > > Of course REPRO or EXPORT/IMPORT will change the EA parameter. > > > -- > Radoslaw Skorupka > Lodz, Poland > > > > > > > -- > Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku > przeznaczone wycznie do uytku subowego adresata. Odbiorc moe > by jedynie jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie > jeste adresatem niniejszej wiadomoci lub pracownikiem upowanionym > do jej przekazania adresatowi, informujemy, e jej rozpowszechnianie, > kopiowanie, rozprowadzanie lub inne dziaanie o podobnym charakterze > jest prawnie zabronione i moe by karalne. Jeeli otrzymae t > wiadomo omykowo, prosimy niezwocznie zawiadomi nadawc > wysyajc odpowied oraz trwale usun t wiadomo wczajc w to > wszelkie jej kopie wydrukowane lub zapisane na dysku. > > This e-mail may contain legally privileged information of the Bank and is > intended solely for business use of the addressee. This e-mail may only be > received by the addressee and may not be disclosed to any third parties. If > you are not the intended addressee of this e-mail or the employee > authorised to forward it to the addressee, be advised that any dissemination, > copying, distribution or any other similar activity is legally prohibited and may > be punishable. If you received this e-mail by mistake please advise the > sender immediately by using the reply facility in your e-mail software and > delete permanently this e-mail including any copies of it either printed or > saved to hard drive. > > BRE Bank SA, 00-950 Warszawa, ul. Senatorska 18, tel. +48 (22) 829 00 00, fax > +48 (22) 829 00 33, www.brebank.pl, e-mail: [email protected] Sd Rejonowy > dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru > Sdowego, nr rejestru przedsibiorców KRS 0000025237, NIP: 526-021-50-88. > Wedug stanu na dzie 01.01.2013 r. kapita zakadowy BRE Banku SA (w > caoci wpacony) wynosi 168.555.904 zotych. > > > ---------------------------------------------------------------------- > 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
