Page 1 of 2

NO SPACE in DIRECTORY

PostPosted: Tue Aug 30, 2011 12:12 pm
by apjohn1986
When i saving data in a new member, i got error msg like 'NO SPACE in DIRECTORY'. Is there any way to expand my PDS size or compress existing data, so that i can save my data?

Re: NO SPACE in DIRECTORY

PostPosted: Tue Aug 30, 2011 1:26 pm
by enrico-sorichetti
ask Your support for the practices in use...
the best approach is to copy the current PDS to a new one with a larger number of directory blocks
and do a double rename
copy <current> to <new>
rename <current> to <bak>
rename <new> to <current>
after having checked that everything works ... delete <bak>

even if it is possible quite a few organization frown upon <in place> mangling of things

Re: NO SPACE in DIRECTORY

PostPosted: Tue Aug 30, 2011 2:46 pm
by apjohn1986
thanks enrico..........

Re: NO SPACE in DIRECTORY

PostPosted: Wed Aug 31, 2011 12:31 pm
by jaggz
Try with FIXPDS tool available at CBTTAPE.ORG site which can increase the size of current PDS.

Re: NO SPACE in DIRECTORY

PostPosted: Wed Aug 31, 2011 1:17 pm
by enrico-sorichetti
Try with FIXPDS tool available at CBTTAPE.ORG site which can increase the size of current PDS.


I wonder why people answer basing the answer on pure technical grounds, disregarding completely organizational issues :evil:

to use the FIXPDS tool You would need to ...
have access to CBTTAPE.ORG
the capability of downloading from an url and upload to a MF dataset,
the permission to install NON CERTIFIED software on the system (*)
...
...
...
...
add as many more concerns/organization rules as You wish

on the forums it is always better to provide solutions based on a vanilla (no additional products) environment

(*) in most organization it would be the primary showstopper

Re: NO SPACE in DIRECTORY

PostPosted: Wed Aug 31, 2011 9:46 pm
by steve-myers
You can remove ISPF directory statistics. This changes the size of each PDS directory entry to 12 bytes from 42 bytes. However many sites would discourage or prohibit such foolishness. You can't mess with the user data in load module directory entries: program fetch and contents management require this data. Those are the most common users of user data in PDS directory entries.

The CA version of IEBCOPY provides a tool to add PDS directory blocks. It's kind of dangerous since it may have to move the first physical members to create the space for the new directory blocks, but this is less dangerous than "compressing" a PDS since fewer members are moved.

I am not familiar with the FIXPDS utility in CBTTAPE.

Re: NO SPACE in DIRECTORY

PostPosted: Wed Aug 31, 2011 11:19 pm
by Robert Sample
FIXPDS of the PDS utility on the CBTTAPE also moves physical members to create the space for the additional directory blocks. If this product is not installed at the site, it certainly should be installed ONLY by an authorized system programmer after appropriate management approval. If it is available, it will allow a PDS to acquire more directory blocks without the need for copying off and back -- but as has been pointed out, this increases the risk should the software have a problem while moving the PDS members around.

Re: NO SPACE in DIRECTORY

PostPosted: Thu Sep 01, 2011 12:37 am
by dick scherrer
Hello,

No matter how you proceed - create a backup of the pds before doing anything. . .

Re: NO SPACE in DIRECTORY

PostPosted: Tue Sep 20, 2011 9:18 pm
by Pedro
enrico-sorichetti wrote:ask Your support for the practices in use...
the best approach is to copy the current PDS to a new one with a larger number of directory blocks
and do a double rename
copy <current> to <new>
rename <current> to <bak>
rename <new> to <current>
after having checked that everything works ... delete <bak>

even if it is possible quite a few organization frown upon <in place> mangling of things


For the new dataset, specify LIBRARY rather than PDS. This will create a PDSE, which does not have the same directory problems as a PDS.

Re: NO SPACE in DIRECTORY

PostPosted: Tue Sep 20, 2011 11:32 pm
by steve-myers
Pedro wrote:... For the new dataset, specify LIBRARY rather than PDS. This will create a PDSE, which does not have the same directory problems as a PDS.
True, and you never have to "compress" it, but PDSE generally requires much more space than a corresponding PDS, and requires more CPU time to process.