|
View previous topic :: View next topic
|
| Author |
Message |
rakesh17684
New User
Joined: 08 Oct 2006
Posts: 61
Location: San Diego
|
|
|
|
I am searching for a utility or any other method via the job itself, so that after sucessful execution of the job it will delete itself from the PDS it was run.
Currently i have been using this step in my job for the same purpose
MYID.TEST.JCLLIB(mem1)
mem1 is the member in which job is present and MYID.TEST.JCLLIB is the PDS name
| Code: |
000009 //IEBCOPY EXEC PGM=IEBCOPY
000010 //*
000011 //CA7PDS DD DSN=MYID.TEST.JCLLIB,DISP=SHR
000012 //*
000013 //SYSOUT DD SYSOUT=*
000014 //SYSPRINT DD SYSOUT=*
000015 //SYSIN DD *
000016 EDITDIR OUTDD=CA7PDS
000017 DELETE MEMBER=mem1
000018 /*
000019 //*
|
but am looking for an alternative approach, in which i need to avoid giving the PDS name MYID.TEST.JCLLIB.
The member name if present in JCL is fine |
|
| Back to top |
|
 |
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
| Well, if you do not specify the correct PDS to delete the member from ........ |
|
| Back to top |
|
|
Bill Dennis
Active Member
Joined: 17 Aug 2007
Posts: 562
Location: Iowa, USA
|
|
|
|
My prior site used this method before a scheduler pkg was obtained. All daily work was loaded into a PDS for the operators to submit.
Our method used a special utility pgm to copy member to INTRDR and delete at submit time rather than completion. Once the member was gone you knew the job had been submitted.
Of course, we knew the PDS name and didn't have to divine it from some mysterious method. |
|
| Back to top |
|
|
Terry Heinze
JCL Moderator
Joined: 14 Jul 2008
Posts: 1249
Location: Richfield, MN, USA
|
|
|
|
When I read the original post, the 1st thing to come to my mind was... Mission Impossible.  |
|
| Back to top |
|
|
rakesh17684
New User
Joined: 08 Oct 2006
Posts: 61
Location: San Diego
|
|
|
|
hmmmm... i was just expecting something out of the blue.. that i have never seen before in my JCL world
The problem is the whole of the JCL barring the delete step was/is created by a COBOL program. Now there came a immediate (and sudden) requirement to have a delete step to have that JCL delete step.
now all the JCL in our shop had the delete step i have put and the COBOL prog passing the PDS name, like where the job is submitted,demanded and executed. Poor them, didnt knew the prog i wrote for this JCL didnt have the code to pass the PDS name. so i have a extra burden of adding lines in prog which i thought would be a waste if there is something else present |
|
| Back to top |
|
|
|
|
