Yes, that I understand. However, I have always been reluctant to set any TEMP DSN different than other TEMP DSNs. But this is a unique case and I am hoping this will resolve the issue.
The other issue is the consistency for the temp DSN pattern. If anything changes, this code will no longer work. (Sigh) Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Greg Shirey > Sent: Tuesday, March 17, 2015 7:30 AM > To: [email protected] > Subject: Re: SMS ACS and TEMP DSN Parsing > > I don't think there's anything wrong with the logic, but you know that most > attributes of a DATACLAS can be overridden. > > Greg Shirey > Ben E. Keith Company > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Lizette Koehler > Sent: Monday, March 16, 2015 7:02 PM > To: [email protected] > Subject: SMS ACS and TEMP DSN Parsing > > I am trying to create a process in the Dataclas that will change some of the > dataset attributes of on specific Temp DSN. > > The DSN comes in with DSTYPE = TEMP > > Does anyone know if this will work? The DSN will look like this: > SYS15070.T105514.RA000.MYDSN1.R0226931 > > > If (&DSTYPE = Temp and &DSN(4) = 'MYDSN1') > Then > Do > Set Dataclas = X > Write DSN set to X Dataclas > Exit > End ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
