IBM Mainframe Forum

Hi
In a simple IEBR14
//STEP1 EXEC PGM=IEFBR14
//DDFILE1 DD DSN=HLQ.ATEMP1,DISP=(OLD,DELETE,DELETE)
//SYSPRINT DD SYSOUT=*
/*
The dataset gets deleted but if I have * in the DSN name like
//DDFILE1 DD DSN=HLQ.ATEMP*,DISP=(OLD,DELETE,DELETE)

I get
IEFC628I INCORRECT USE OF ASTERISK IN THE DSN FIELD

Any idea?
Thanks

IEFC628I INCORRECT USE OF ASTERISK IN THE DSN FIELD

what does the messages and codes tell about it
no reason to rewrite the same things that the manuals tells in a much better style

start from here
http://www-03.ibm.com/systems/z/os/zos/ ... index.html

and use the lookAT facility ( cut and paste the message number -IEFC628I )

Thanks for the hint
But these manuals have nothig new. It says the use of * where its not allowed.
Soultion is "remove it"
This is not what I am looking for,
How can I use "*" in my DSN to delete multiple files ?

It might not be what you are looking for, but that is the way it is.

Have a look at IDCAMS and the DELETE in there.

It's just like BillyBoyo said. IEFBR14 is a program with the purpose of doing nothing. It actually lets MVS handle the datasets. For your information, the IEF part of the name is only because of the naming convention and BR14 is the assembler instruction Branch Register 14, which is to return to the caller.

Hello,

Soultion is "remove it"
This is not what I am looking for,
How can I use "*" in my DSN to delete multiple files ?

As you have been told and seen in the manual - you cannot. There are JCL rules that have to be followed whether you like it or not. . . Suggest you learn the rules before trying to implement something unknown. Suggest you also believe what is in the manuals - it is very rare that they contain misinformation.

There are several ways to "mask" dataset names, but they are not in JCL.

hi dick scherrer & BillyBoyo
Thanks for your input. IDCAMS alo has the same issue and new MASK feature also doesnot work.

So let me forget IEBR14 and IDCAMS,
and as you suggested
"There are several ways to "mask" dataset names, but they are not in JCL."

Can you point me towards some ?
Thanks

Hello,

Suggest you look at adrdssu/dfdss. . .

Maybe if next time you define your datasets as



instead of



then you can get IDCAMS to "work" and won't have your storage people breathing down your neck.