|
View previous topic :: View next topic
|
| Author |
Message |
mvenkatesha
New User
Joined: 18 Oct 2006
Posts: 23
Location: bangalore
|
|
|
|
| Code: |
//TOPPXXXX JOB (XXXXXX,ATOP),'DELETE',
//* TIME=1439,
// CLASS=A,
// NOTIFY=&SYSUID,
// MSGCLASS=7
//*
//STEP1 EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DELETE XXXXXX.XXXXXX.XXXXXX(TEMP)
/* |
I used the above JCL to Delete the member from the PDS WHICH IS USED in the CICS Concatination.
PDS details are as below:
| Code: |
Organization . . . : PO
Record format . . . : U
Record length . . . : 0
Block size . . . . : 27998
1st extent cylinders: 1
Secondary cylinders : 600
Data set name type : LIBRARY |
When I run the above JCL I have received below error with RC 08.
| Code: |
IDCAMS SYSTEM SERVICES TIME: 12:10:3
DELETE XXXXXX.XXXXXX.XXXXXX(TEMP)
IKJ56225I DATA SET XXXXXX.XXXXXX.XXXXXX ALREADY IN
IKJ56225I USE, TRY LATER
IKJ56225I DATA SET IS ALLOCATED TO ANOTHER JOB OR USER
IDC0548I ** MEMBER TEMP NOT DELETED
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 8
IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 8
**************************** E N D O F D A T A **************************** |
I tried searching but not found with some requirement like above. Can some one please help me if there is way I can delete the member of the PDS which is used in the CICS concatenation.
Since CICS will be always running I cannot get the CICS region Down to run my JOB. So we are currently manually deleting the members for the PDS used in CICS Start up concat. |
|
| Back to top |
|
 |
gcicchet
Senior Member
Joined: 28 Jul 2006
Posts: 1702
Location: Australia
|
|
|
|
Hi,
you can try this
| Code: |
//DELMEM EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//PDS DD DSN=input-dsn,DISP=SHR
//SYSIN DD *
DELETE input-dsn(TEMP) FILE(PDS)
/*
|
Gerry |
|
| Back to top |
|
|
MBabu
Active User
Joined: 03 Aug 2008
Posts: 400
Location: Mumbai
|
|
|
|
If CICS has the partitioned data set open, you will get an abend 213. Just out of curiosity, why is CICS using a PDS? What is it using it for?
When you say "the CICS concatenation", I don't know exactly which concatenation you mean. |
|
| Back to top |
|
|
gcicchet
Senior Member
Joined: 28 Jul 2006
Posts: 1702
Location: Australia
|
|
|
|
Hi,
I tried deleting a member from an opened dataset and job did not abend.
Gerry |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8697
Location: Dubuque, Iowa, USA
|
|
|
|
Mbabu: I would not expect an abend just because the PDS is open and a member is deleted -- unless CICS tried to access the deleted member without getting the updated directory.
I have compressed a PDS in one LPAR that is open in another LPAR by submitting a batch job with DISP=SHR so I know just having the PDS open doesn't cause abends. Of course, you have to know what is using the PDS and how before you can do this successfully -- not for someone without plenty of years of experience!
And considering the data set characteristics, I suspect this is a PDS-E (since it is a LIBRARY) concatenated to the DFHRPL for the region. |
|
| Back to top |
|
|
MBabu
Active User
Joined: 03 Aug 2008
Posts: 400
Location: Mumbai
|
|
|
|
| Sorry -- I meant to say opened for output. |
|
| Back to top |
|
|
mvenkatesha
New User
Joined: 18 Oct 2006
Posts: 23
Location: bangalore
|
|
|
|
| Code: |
//STEP1 EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DELETE XXXXXX.XXXXXX.XXXXXX(TEMP) FILE(PDS)
/*
LC DDNAME STEPNAME PROCSTEP Q TYPE PRI TOTRECS TOTPAGS DEST
__ SYSPRINT STEP1 7 9 10 0 LOCAL
IDCAMS SYSTEM SERVICES TIME: 14:47:0
DELETE XXXXXX.XXXXXX.XXXXXX(TEMP) FILE(PDS)
IDC3300I ERROR OPENING PDS
IDC3304I ** JCL STATEMENT MISSING
IDC3897I CONFLICT BETWEEN ENTRYNAME AND DD SPECIFIED DATA SET NAME
IDC0548I ** MEMBER TEMP NOT DELETED
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 8
IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 8
**************************** E N D O F D A T A **************************** |
Hi I tried the same by providing FILE(PDS) at end but received above error.
I will try my best to explain why we are having that PDS in CICS Concat.
The PDS members that I am trying to delete are the CICS LOADLIB's. So once we link the COBOL CICS programs the Loadlib will sit in that Library. The same Library is used in the CICS regions for the program "PGM=DFHSIP" so that once we take the NEW COPY the load module is in effect.
Problem is by using JCL, we are not able to delete the members from the PDS which is used in the CICS concatination. Currently we are doing it manually.
Reason for deletion-> in the CICS Concat XXXX dataset comes first and then the yyyyy dataset.
XXXXXX.XXXXXX.XXXXXX <- Any fixes.
YYYYYY.YYYYYYY.YYYYYYY <- For permanent change.
So what happens if there is a problem we get fixes and moved to XXXX.XXX.XXX fix dataset. Once they feel everything is working we delete from XXXX.XXXX.XXXX dataset and YYYYY.YYYYY.YYYYY will be having the permanent fix.
Please let me know if this helps. |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8697
Location: Dubuque, Iowa, USA
|
|
|
|
| Code: |
//STEP1 EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DELETE XXXXXX.XXXXXX.XXXXXX(TEMP) FILE(PDS)
/* |
Your JCL, which I quoted here, is missing one key piece -- the PDS DD name. Look at the example Gerry gave you and you'll see the extra DD statement. The delete is failing because the DD name is missing from the JCL. |
|
| Back to top |
|
|
mvenkatesha
New User
Joined: 18 Oct 2006
Posts: 23
Location: bangalore
|
|
|
|
Hello Gerry & Robert
Thank you for all your help. It works and yes I missed the PDS DD name. This is what I expected to achieve.
Once again thank you for your help. |
|
| Back to top |
|
|
|
|
