I've found that under DSSU, the DC ACS routine is not invoked at all and SC is the first ACS routine, which is opposite of normal allocation. Thus your SC cannot depend on a DC value under DSSU. I think the rational is that unlike the other classes DC is imutable in that a data sets characteristics can't be changed after allocation. For example a FB/80 data set can't be changed to VSAM just by changing the DC which explains why you cannot alter the DC of a data set. Think of DC as physical vs the others which are logical.
Probably your source data sets don't have a DC so a SC ACS looking for them is lost. The only way I've found to fix this is to duplicate the code in DC into SC as well so a SC gets assigned. Without a SC assignment, SG (and MC) are not invoked, thus you have non-SMS. Ken On Fri, Mar 21, 2014 at 1:00 PM, Nathan J Pfister <[email protected]>wrote: > We figured out the issue....since we're using ADRDSSU, it's getting a null > dataclass...and we had a condition within the storage class that said if > dataclas is '' then set storclas to ''. > > So I guess my next question...we attempted to code for dataclas = '' and > pgm = 'ADRDSSU' to fall to our DEFAULT stroage class...when moving > datasets this worked like a champ...but when restoring datasets it did > not. Obviously I am missing something else here. Is ADRDSSU not the > right pgm name? > > Thanks; > > Nathan Pfister > zOS Systems Programmer > AES\PHEAA - Tech Services > [email protected] > (717) 720-2663 > > > > From: "John McKown" <[email protected]> > To: [email protected] > Date: 03/21/2014 12:04 PM > Subject: Re: SMS Question > Sent by: "IBM Mainframe Discussion List" <[email protected]> > > > > My first guess is that the STORCLAS associated with the data set being > restore had the GUARANTEED SPACE attribute. Either remove that from the > STORCLAS or in the restore parameters include a VOLUME(*) parameter to > override the volume that DFDSS wants to use. > > > On Fri, Mar 21, 2014 at 9:36 AM, Nathan J Pfister > <[email protected]>wrote: > > > Hello; > > > > I am relatively new to SMS, and rather ignorant (read: uneducated) about > > how it fully works. I'm learning more and more by reading, but I've hit > > an issue which I can't find a quick solution to using google or finding > in > > the manuals. > > > > We just set up a new SANDBOX system, and set up SMS from scratch. When > we > > dump with ADRDSSU some datasets (from a production lpar) to be restored > to > > the Sandbox LPAR, we are getting errors where it is trying to select the > > volume that it came from (which is not online on the Sandbox). Shouldn't > > SMS be choosing a volume based on the ACS routines of the Sandbox > system? > > > > What are we missing? > > > > Thanks in advance. > > > > Thanks; > > > > Nathan Pfister > > zOS Systems Programmer > > AES\PHEAA - Tech Services > > [email protected] > > This message contains privileged and confidential information intended > for > > the above addressees only. If you > > receive this message in error please delete or destroy this message > and/or > > attachments. > > > > The sender of this message will fully cooperate in the civil and > criminal > > prosecution of any individual engaging > > in the unauthorized use of this message. > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to [email protected] with the message: INFO IBM-MAIN > > > > > > -- > There is nothing more pleasant than traveling and meeting new people! > Genghis Khan > > Maranatha! <>< > John McKown > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > > > > This message contains privileged and confidential information intended for > the above addressees only. If you > receive this message in error please delete or destroy this message and/or > attachments. > > The sender of this message will fully cooperate in the civil and criminal > prosecution of any individual engaging > in the unauthorized use of this message. > > ---------------------------------------------------------------------- > 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
