Link to home
Start Free TrialLog in
Avatar of ttist25
ttist25

asked on

Userid can't create PDSE

Hello there,

I'm working as a consultant trying to do a data extraction from a z/OS mainframe system.  I'm having difficulty trying to allocate a dataset.  I can allocate a dataset of type PDS but I'm unable to create type LIBRARY (PDSE).

I don't have a solid mainframe background but I'm just looking for ideas as to why this might occur.  Would it be a permissions issue on the userid?  Any ideas what they should check?

TIA
ASKER CERTIFIED SOLUTION
Avatar of giltjr
giltjr
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of ttist25
ttist25

ASKER

Thanks for your response gilt.  

I'm using ISPF.  I am using LIBRARY as the data set type but I still get the error saying the userid can't create a PDSE.

I'm using TSO/B to allocate and compile and run everything which we've done in the past.  I don't see a TSO/E option in my menus.  Could that have anything to do with it?  Although we've run everything in TSO/B in the past, I think the userid may have had access to TSO/E.

Not sure what TSO/B is, I have never heard of it.  I have used TSO (decades ago) and TSO/E.

Try running the following JCL:

//ALLOC    EXEC PGM=IEFBR14                        
//FILE0001 DD DISP=(,CATLG),DSN=some.valid.dsn,
//            UNIT=SYSDA,DCB=(LRECL=80,BLKSIZE=27920,RECFM=FB),
//            DSNTYPE=LIBRARY,SPACE=(CYL,(10,5))    


You need to add your own JOB card and change the SPACE and DCB information as needed.  

If I remember correctly a LONG time ago, PDS/E's had to be system manged (SMS) dataset.  However, I am fairly sure that restriction was lifted, but I'm not sure what if there is something special you need to do.
Avatar of ttist25

ASKER

Hello Gilt,

I ended up using a PDS instead of LIBRARY.  It seems like the PDSE was overkill for the amount of data (not really sure).  Anyway, I got my data out but now I'm having a new problem if you'd like to give it a shot.  The question is here.

Thanks again for your help.
The difference between PDS and PDS/E really has nothing to do with the size of the file.

The difference is that PDS/E's will reuse space for member storage.  With PDS's when you update a member, it is saved to the end of the file, which will cause the PDS to become fragemented and you need to compress the file everynow and then, if you do a lot of udpates.

PDS/E will also not run out of directory blocks, the part of the file that stores the information about the indvidual members.