IBM Mainframe Forum

//xxxxxx JOB NOTIFY=&SYSUID,TIME=(,2)
//STEP1 EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DELETE xxxxxx1.UTIL.GDG PURGE
/*
for this program i can't delete the base gdg while i'm trying to delete getting the maxcc=8.
IDCAMS SYSTEM SERVICES TIME: 04:20:12
i am getting the sysprint error message as below
DELETE (xxxxx.UTIL.GDG) GDG FORCE
IDC2054I INVALID AUTHORIZATION TO EXECUTE FUNCTION
IDC3009I ** VSAM CATALOG RETURN CODE IS 190 - REASON CODE IS IGG0CLFT-12
IDC0551I ** ENTRY xxxxx1.UTIL.GDG NOT DELETED
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 8

IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 8
if any other syntax to delete the base gdg revert me back..

what happened when You looked at the messages manual for

IDC2054I INVALID AUTHORIZATION TO EXECUTE FUNCTION

???

Additionaly, a GDG base has to be empty to delete it, and then I do not think you will need the force.

hello Mongan,
i have tried the force also that time also i'm getting the same error message like this
or this program i can't delete the base gdg while i'm trying to delete getting the maxcc=8.
IDCAMS SYSTEM SERVICES TIME: 04:20:12
i am getting the sysprint error message as below
DELETE (xxxxx.UTIL.GDG) GDG FORCE
IDC2054I INVALID AUTHORIZATION TO EXECUTE FUNCTION
IDC3009I ** VSAM CATALOG RETURN CODE IS 190 - REASON CODE IS IGG0CLFT-12
IDC0551I ** ENTRY xxxxx1.UTIL.GDG NOT DELETED
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 8

IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 8
if any other syntax to delete the base gdg revert me back..

If you read the messages, you'll see that you, yourself, your TSO-id, are not allowed to do it. You have no authorisation to execute the function.

If you desperately feel the need to do this, go to your storage people, I'm sure they will have authority.

If you can't do it, for security reasons, then you can't do it, no matter how you try. Each attempt will be logged, probably. At some point, someone might start asking questions.

dear bilyboyo,
thanks a lot.......

mainframemunic wrote: i have tried the force also that time also i'm getting the same error message like this

Suggest you don't try it at home.

Assume that you have a generation data group with generation data sets that have migrated, and you wish to delete the group. If you use the Access Method Services DELETE GDG FORCE command to delete the catalog entries for the generation data group and its generation data sets, IDCAMS does not invoke DFSMShsm. You must then issue the DFSMShsm DELETE command for each of the now-uncataloged migration copies.

From a storage view, it is better that there are no uncataloged datasets held in the MCDS, however a HSM audit will highlight these datasets and offer the code to delete the HSM entries. On a downside, an audit can take up to many many hours to complete.

Long story short - using the ‘DELETE GDG FORCE’ command causes migrated GDSs to become uncataloged, but not deleted. This data takes up space and will be billable to the data owners if HSM is a billable component. (and every shop i had been to, it was billable.)

Usually the FORCE parameter is a protected species, and can only be issued by authorised users.

To delete a GDG base without using FORCE then the base MUST be empty.

Using IDCAMS will delete any HSM entries as well as those GDS resident on DASD or tape.

expat...
thanks i will try .......