Correct. VATLST deals with new dataset allocations for non-specific non-sms volumes. Volume pools deal with HSM Recalls to non-specific non-sms volumes. Similar concepts for different uses.
On Wed, Jun 5, 2013 at 11:33 AM, esmie moo <[email protected]> wrote: > I found the explantaion for a volume pool. According to the doc : > A volume pool associates volumes from which data sets migrate with other > volumes, to aid in the selection of target volumes for recall. > > > I checked the VATLIST and these vols are not in it. Hence the reason for the > ADDVOL. > > Thanks to all who helped me out. > > > ________________________________ > From: "O'Brien, David W. (NIH/CIT) [C]" <[email protected]> > To: [email protected] > Sent: Wednesday, June 5, 2013 7:09:00 AM > Subject: Re: DFHSM QUESTION - SIGNIFICANCE OF ADDVOL PARM > > > An attempt to migrate an APF authorized library will result in the following: > > ARC1299I rc=14 where > > 14 The data set is an authorized program facility (APF) authorized > library. > > Unless of course the migration is running on an LPAR where said library is > not APF authorized. > > -----Original Message----- > From: Mike Schwab [mailto:[email protected]] > Sent: Tuesday, June 04, 2013 5:03 PM > To: [email protected] > Subject: Re: DFHSM QUESTION - SIGNIFICANCE OF ADDVOL PARM > > http://publib.boulder.ibm.com/infocenter/zos/v1r11/index.jsp?topic=/com.ibm.zos.r11.arcf000/hr1003.htm > Datasets migrated from a volume in the pool are recalled to any volume in the > pool. > If a dataset is APF authorized for a particular volume, migrating and > recalling to another volume would make it not authorized. > > ADDVOL volser PRIMARY is similar to the VATLST Public / Storage setting, but > only for HSM. > > On Tue, Jun 4, 2013 at 12:37 PM, Staller, Allan <[email protected]> > wrote: >> The addvol command is used to define non-SMS managed volumes to DFHSM. SMS >> managed volumes are defined in the MGMTCLAS/STORGRP ACS constructs. >> >> Deciphering: >> ADDVOL SYS009 PRIMARY(NOAM AREC NOAB NOAD MIGRATE(10)) >> >> NOAM - NO AUTOMIGRATION >> AREC - AUTORECALL >> NOAB - NO AUTOBACKUP >> NOAD - NO AUTODUMP >> Migrate after 10 days on non-use (command migration only). >> >> Not sure about the volumepool statement. Check the fine manuals. >> >> HTH, >> >> <snip> >> ADDVOL SYS009 PRIMARY(NOAM AREC NOAB NOAD MIGRATE(10)) UNIT(3390) >> ADDVOL SYS010 PRIMARY(NOAM AREC NOAB NOAD MIGRATE(10)) UNIT(3390) >> ADDVOL SYS011 PRIMARY(NOAM AREC NOAB NOAD MIGRATE(10)) UNIT(3390) >> >> DEFINE VOLUMEPOOL(SYS VOLUMES(SYS009 SYS010 SYS011)) >> >> I am not sure what it is supposed to do since there is no other parms. At >> first I thought it was for a dump. There are no other SETSYS statements >> after the DEFINE VOLUMEPOOL statement. >> </snip> >> >> ---------------------------------------------------------------------- >> 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 > > ---------------------------------------------------------------------- > 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
