So, Esmie, since it's an older version, could you rename the dataset ie. ZACTQUE, TACTQUE, so that it's not first and retry the command. I would expect it to process as many as possible until it reaches the first error. Strictly speculation on my part, natch.
ps. I haven't read IBM-Main yet today.... --------> signature = 6 lines follows <-------- Neil Duffee, Joe Sysprog, uOttawa, Ottawa, Ont, Canada telephone:1 613 562 5800 x4585 fax:1 613 562 5161 mailto:NDuffee of uOttawa.ca http:/ /aix1.uOttawa.ca/ ~nduffee "How *do* you plan for something like that?" Guardian Bob, Reboot "For every action, there is an equal and opposite criticism." "Systems Programming: Guilty, until proven innocent" John Norgauer 2004 -----Original Message----- From: esmie moo [mailto:[email protected]] Sent: May 7, 2015 11:25 To: esmie moo; Neil Duffee Neil, Yes, the first dsn was SYS2.CA1.TMSA.ACTQUE on the list. -------------------------------------------- On Wed, 5/6/15, Neil Duffee <[email protected]> wrote: Subject: RE: IDCAMS vs IDC3194I To: "esmie moo" <[email protected]> Received: Wednesday, May 6, 2015, 11:57 AM Caveat: yeah, you know the routine, digest delay, already answered, etc. Esmie: when using ListDS (=3.4) for SYS2.CA1.TMSA.**, is ACTQUE the 1st entry? My suspicion is that IdcAms stopped processing when it encountered the IDC3194I which happens to be the first of the bunch. -----Original Message----- From: esmie moo [mailto:[email protected]] Sent: May 5, 2015 13:55 Subject: Re: IDCAMS QUESTION The dsns are all SMS managed except for SYS2.CA1.TMSA.ACTQUE. This dsn is on a non-SMS volume. Since IDCAMS encountered this dsn did it prevent the ALTER of the other dsns? The SYS2.CA1.TMSA dsns are from an older version of CA1. The current versions are on non-SMS vols. -------------------------------------------- On Tue, 5/5/15, Lizette Koehler <[email protected]> wrote: Received: Tuesday, May 5, 2015, 1:06 PM Your dataset is not managed by SMS - So you cannot alter the management class IDC3194I SMS CONSTRUCT MANAGEMENTCLASS SPECIFIED FOR NON-SMS MANAGED Did you place your SYS2.CA1.TMSA on SMS managed volumes? Do you have the under control of SMS? - This is something I would not do for CA1 TMC. > -------------------------------------------- > On Tue, 5/5/15, esmie moo <[email protected]> wrote: > > Received: Tuesday, May 5, 2015, 11:31 AM > [snip] trying to alter the Management Class of the the following dsns >using > IDCAMS: SYS2.CA1 .TMSA.**. [snip] The message error > posted for one dsn is self explanatory, however when I check all the > dsns it > shows that the alter did not work. Is it because it detected a problem > with > one dsn and doesn't process any of the dsns? Below is the output of the > job : > > IDCAMS SYSTEM SERVICES > ALTER SYS2.CA1 .TMSA.* - > MGMTCLAS (NOMIG) > > IDC3194I SMS CONSTRUCT MANAGEMENTCLASS SPECIFIED FOR NON-SMS MANAGED > IDC3194I OBJECT > IDC0532I **ENTRY SYS2.CA1 .TMSA.ACTQUE NOT ALTERED ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
