IBM Mainframe Forum

HOW TO EXTEND A PDS DIRECTORY DYNAMICALLY

//STEP1 EXEC PGM=IEBCOPY
//SYSPRINT DD SYSOUT=*
//*OUT DD DISP=SHR,DSN=DATASET.WITH.FULL.DIRECTORY
//OUT DD DISP=SHR,DSN=TEST1.CHM45152.PROD.CNTL
//SYSIN DD *
ALTERDIR OUTDD=OUT,BLOCKS=52
But I am getting error as below:
PDF0101I START PDSFAST EXECUTION
PDF0255W FIRST STATEMENT HAS NO OPERATION KEYWORD
PDF0103C ALTERDIR OUTDD=OUT,BLOCKS=52
PDF0290I $
PDF0282A KEYWORD "ALTERDIR" NOT RECOGNIZED
PDF0165W COPY STEP WILL BE BYPASSED DUE TO ERROR
PDF0189I END OF COPY STEP 1 - RC(8)
PDF0120P JOB PERFORMANCE: .02 ELAPSED, .00 TCB CPU, 0 EXCPS
PDF0199I END OF PDSFAST EXECUTION - RC(8)

Any comments will be appreciated

thanks

IBM has one and only one recommended way to increase the size of a PDS directory: copy the PDS to another PDS which has the larger directory.

If your site has the PDS software from the CBT tape at http://www.cbttape.org then you can use it to increase the size of a PDS directory without having to copy it to another PDS. There are also vendor products that can do this. If your site is limited to the IBM utilities, however, there is ABSOLUTELY no way to dynamically change the size of a PDS directory using IBM software.

FWIW, I believe the CA version of IEBCOPY has this capability, but I do not know the command to expand the directory.

It is actually quite difficult to expand a directory; any members on the track or tracks required to expand the directory must be moved out of the way before the directory is expanded.

If it is inconvenient to copy the dataset to a new dataset - and that's sometimes the case, absolutely make a backup copy before you try to expand the directory, just in case the directory expansion damages the dataset. You may discover "lost" space in the track where the last directory block is located after the expansion. A PDS "compress" may recover this space.

Any comments will be appreciated

wouldn' t it be faster to look Yourself at the PDSFAST manuals
instead of lazily wait for us to do it for You ?

and once again you have failed to use the code tags.

Actually, I suspect code tags would not help here, since they do not usually preserve a single leading blank, which I suspect dn2012 didn't insert into his PDSFAST command.

Here is code in tag

Hello,


The error appears rather self-explanatory

A search of the IEBCOPY manual for alterdir returns:
No search hits found for: alterdir

Where did you get the syntax you used? It is a bad practice to create one's own syntax. . . The utilities are rather picky

dn2012, if your site is licensed for PDSFAST then you have access to the manuals. Either they exist somewhere at your site, or they are in an online repository at your site, or you can download them from the vendor. Since the syntax you are using is obviously invalid, you need to read the manual to identify the correct syntax and use it instead of what you used.

we do have PDSFAST utility. HOW TO EXTEND A PDS DIRECTORY DYNAMICALLY?


OPTION ===>
C - Copy R - Rename Member(s) CM - Copymod B - Browse
M - Move D - Delete Member(s) AM - Altermod E - Edit
Z - Compress RM - Recover Member(s) IP - Info Primary P - Print
V - Verify DS - Directory Size IS - Info Secondary RA - Realloc

PRIMARY DATA SET: SECONDARY DATA SET:
PROJECT ===> ===>
GROUP ===> ===>
TYPE ===> ===>
MEMBER ===> ===>
VOLUME ===> ===>
NEW NAME ==> (REQUIRED FOR RENAME)

OTHER PRIMARY DATA SET: ===>
OTHER SECONDARY DATA SET: ===>

REPLACE EXISTING MEMBERS: (YES OR NO) DISP IF SEQ: (OLD OR MOD)
CONFIRM MEMBER DELETE AND LRECL CHANGES: (YES OR NO)
DEFAULT HIGH LEVEL QUALIFIER: TSSDN PAD CHARACTER:
REALLOC SPACE: (#, 0, blank, +, -) PROCESS MEMBER ALIAS: (YES/NO

thanks