Avoid "Too many Data Sets" allocation problems in Rexx 1

[philipvd]

Hi all,

I have a never encountered problem and it's rather difficult to search for (but I'll do in the meanwhile).
While executing my new rexx I encountered problems while allocating a pds-member. The "Too many data sets"-error
is very strange because I have written different rexx execs before with the allocation of even more Data Definition ID's.

>O> "ALLOC FI(SYSUT2) DA('MS.LLV39.UTIL.VTBCKUP(TEST)') SHR REU"
IKJ56220I DATA SET MS.LLV39.UTIL.VTBCKUP NOT ALLOCATED, TOO MANY DATA SETS+
IKJ56220I MAXIMUM NUMBER OF DATA SET ALLOCATIONS ALLOWED BY YOUR SESSION HAS BEE

Does somebody know how I can solve this problem or where to look for.

Thanks in Advance,

http://philipvd.says.it

 

[rexxhead]

Try issuing a "LISTA STATUS". This will list all the DDs and DSNs currently allocated.

I would not be surprised to find you were in a loop of some sort.


Frank Clarke
Tampa Area REXX Programmers' Alliance
REXX Language Assn Listmaster

 

[KiwiREXXDude]

Further to Frank's response, you can also do a 'TSO ISRDDN' which is an ISPF GUI into datasets allocated to your session. Hopefully your site have not 50 million (slight exaggeration) datasets allocated to things like SYSEXEC, SYSPROC, ISPLLIB, STEPLIB, ISPTLIB etc, but I have seen it! A certain large bank in Australia has about 40 datasets in the SYSPROC alone!

It could also be that you are not doing a FREE after you have finished with a file using ALLOC. If you write something to read or write members of a PDS it is very easy to forget to free the previous allocation (though you do have a REUSE).

If it gets too bad, run it in batch with a DYNAMNBR keyword.

 

[stanleyrx]

I agree with KiwiRexxdude, since I have also come across this messagae in MVS and PC DOS. You should free/close files after using them. You may want to try writing a program that keeps opeing files and display the number to demonstrate at what point the message comes up. Then you'll know the limit.

 

[philipvd]

Dear all,

problem has been solved.
The sollution was to add dynambr=20 to the job step in my jcl.

Thanks all for the reply.

Philip Van Daele,

http://philipvd.says.it