MVSFORUMS.com

priyam · Beginner Joined: 05 Jul 2006 Posts: 16 Topics: 12

Hi all,

Am new to REXX. I want to develop a REXX tool, which creates a delete step in the beginning of the JCL for all the datasets that are newly created in that JCL. (DISP=(NEW, CATLG)).
This is mainly for testing purpose. Because, we would run the same job many times and every time we need to go and delete the datasets manually. To avoid this, i want to create a tool.

For e.g.

My JCL is having three steps, in which each step is creating two output files. So if i give "DELNEW" in the command line it should create the delete step at the beginning of the JCL (after JOB card) with all 6 files.

If anyone have the code already, it would be very helpful if you provide the code.

Thanks in advance!!!

vkphani · Intermediate Joined: 05 Sep 2003 Posts: 483 Topics: 48

Check the below link. It has the solution

http://www.mvsforums.com/helpboards/viewtopic.php?t=8456&highlight=rexx+tool+delete+datasets+created+job

Nic Clouston · Posted: Fri Oct 19, 2007 2:15 pm Post subject:

Much though I love REXX and I contributed to the thread in the link all you need here is an IEFBR14 step at the fron of the job to delete all datasets created in the job or before each step that creates a dataset to delete thos particular datasets.

expat · Posted: Sat Oct 20, 2007 2:08 am Post subject:

Or good old IDCAMS will do just as well
_________________
If it's true that we are here to help others,
then what exactly are the others here for ?

Nic Clouston · Posted: Sat Oct 20, 2007 7:23 am Post subject:

Except with IDCAMS, if you are running a procedure, your control cards are hidden away in a dataset somewhere whereas with BR14 what it is dealing with is in plain view so you know which files it is cleaning up and you can check that all the required files are being deleted without leaving the procedure. Still doesn't stop me getting the dataset names wrong though Mr. Green

_________________
Utility and Program control cards are NOT, repeat NOT, JCL.

semigeezer · Posted: Sun Oct 21, 2007 2:50 am Post subject:

And IEFBR14 does not do anything. It is the JCL interpreter that does the work so this method is more efficient.

I always get a kick out of all the references to IEFR14 doing allocations and the JCL that gets posted here with things like //SYSPRINT, //SYSOUT, //SYSIN DD DUMMY and the like for IEFBR14 steps because IEFBR14 is nothing more than an SR 15,15; BR 14 (or maybe XR).

You can get the same results for allocations/deletions within JCL by specifying a nonexistent program in the EXEC PGM=xxx statement. Sure, you'll get an ABEND 806, but the allocations or deletions will work because they are done before the program is invoked (at least with JES2, though I suspect JES3 will do the same).
_________________
New members are encouraged to read the How To Ask Questions The Smart Way FAQ at http://www.catb.org/~esr/faqs/smart-questions.html.