> 
> Lizette,
> 
> Thanks very much for the info.  I never tried using the NEWNAME, which
> I will.
> However, I am trying to ALTER the MANAGEMENT class and not trying to
> rename the dsn.  Do you have any information for that?
> 
> --- On Sat, 12/4/10, Lizette Koehler <[email protected]> wrote:
> 
> 
> From: Lizette Koehler <[email protected]>
> Subject: Re: WILDCARDS - IDCAMS ALTER COMMAND
> To: [email protected]
> Received: Saturday, December 4, 2010, 1:49 AM
> 
> 
> > Good Morning Gentle Readers,
> >
> > Has anybody been able to ALTER  the HLQ dsns of a MANAGEMENT class
> > using wildcards for the IDCAMS command?  I am able to delete dsns
> using
> > wildcards HLQs.
> >
> > Here is my command that I am trying to issue:
> >
> >  //IDCAMS EXEC PGM=IDCAMS,REGION=4M
> > //SYSPRINT DD SYSOUT=*
> > //SYSIN    DD *
> >  ALTER 'IMSZ.ACBL*' -
> >         MGMTCLAS (NOMIG)
> > /*
> > I get the error message :
> > IDC3203I ITEM 'IMSZ.ACBL*' DOES NOT ADHERE TO RESTRICTIONS
> > IDC3202I ABOVE TEXT BYPASSED UNTIL NEXT COMMAND. CONDITION CODE IS 12
> >
> > Can wildcards be used when performing ALTER commands?
> >
> > Thanks in advance.
> 
> If you goggle IDCAMS WILDCARDS, I came up with the following APAR from
> IBM
> 
> Using wildcards with IDCAMS ALTER NEWNAME
> Technote (FAQ)
> 
> Question
> Using wildcards with IDCAMS ALTER NEWNAME
> 
> User is attempting to change the HLQ (High Level Qualifier) on all
> datasets
> starting with CICS to CICSA
> CICS.SYSTEM
> CICS.SYSTEM2
> CICS.SYSTEM.PROD
> CICS.SYSTEM.
> 
> Answer
> Description:
> 
>             Using wildcards with IDCAMS ALTER NEWNAME
> 
>             User is attempting to change the HLQ (High Level Qualifier)
> on
> all datasets starting with CICS to CICSA
>             CICS.SYSTEM
>             CICS.SYSTEM2
>             CICS.SYSTEM.PROD
>             CICS.SYSTEM.TEST
> 
>             Using the following ALTER job:
> 
>             //NEWNAME  EXEC
> PGM=IDCAMS,REGION=4M
>             //SYSPRINT
> DD   SYSOUT=A
>             //SYSIN    DD   *
> 
>                  ALTER CICS.* -
> 
>                     NEWNAME(CICSA.*)
> 
>                /*
> 
> 
>             The results are:
> 
>             CICSA.SYSTEM
>             CICSA.SYSTEM2
>             CICS.SYSTEM.PROD
>             CICS.SYSTEM.TEST
>             Only the datasets matching the level of qualification i.e 2
> are
> changed.
> 
> 
> 
>             Resolution:
> 
>             The generic in ALTER NEWNAME only replaces one qualifier
> not all
> following qualifiers.
> 
>             To ALTER the 3 level qualified datasets the following could
> be
> coded:
> 
>             ALTER CICS.SYSTEM.* -
>             NEWNAME(CICSA.SYSTEM.*)
> 
>             The following will validly fail with :
> 
>             ALTER CICS.*.* -
>             NEWNAME(CICSA.*.*)
>             IDC3203I ITEM 'CICS.*.*' DOES NOT ADHERE TO RESTRICTIONS
> 
>             A generic can be coded in the middle
> 
>             ALTER CICS.*.TEST -
>             NEWNAME(CICSA.*.TEST1)
> 
> Does this answer your question?
 

You can code CICS.* and cover CICS.A  CICS.B CICS.C and not CICS.A.B   

But you cannot code CICS* and get CICSA CICSB or CICSC

The wildcard is very restrictive in this process.

I guess that your are trying to action the following dataset types

'IMSZ.ACBL*'

IMSZ.ACBLIB
IMSZ.ACBLIBA
IMSZ.ACBLIBB

Which I do not think will work easily in IDCAMS.

I would suggest you use the ISMF panels with ALTER and do it interactive if
you do not have too many.  Otherwise you probably need to code each one
individually.  I have always created a REXX to read a list of datasets that
then creates the IDCAMS control cards.  It has always been easier that way
then trying to use wildcards.

>From the z/OS V1R11.0 DFSMS AMS for Catalogs

Use an asterisk to replace a qualifier to indicate a generic command with
certain commands. However, an asterisk cannot be used as the high level
(leftmost) qualifier, as a partial replacement for a qualifier, or to
replace more
than one qualifier. The following examples show you how to use an asterisk
for a generic name:
A.*
A.*.C
The following examples are not acceptable ways to use a generic name:
A.*.*
A.B*
*.B.C
Refer to the entryname subparameter of each command to determine if a
generic name is allowed and for more information on using one.

If I am incorrect, I am sure someone on the list will have a better
recommendation.

Lizette

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to