Barbara Nitz wrote: >Not sure if that helps, but I guess you should look into defining and >assigning a dataclas with valid space parms whenever a DSORG=PO is allocated >with the invalid space parms I used. Or feel free to open a PMR with IBM, >citing the doc and the obvious not-adherence to the docs. Sorry that I cannot >help out more.
I have repeated your test with ,DSNTYPE=PDS added. I got all the same symptoms, etc. So you are NOT alone! ;-) To Paul Gilmartin: I noted your surprise. I also repeated the first test on another system with a very simplified SMS and got a PDS (Not PDS-E) with all the same symptoms as described in this thread. When we started SMS in the 1990 years around, we forced the users to properly use the JCL statements or let SMS decides what the best options are. We found that sometimes incorrect set of options, like directory size = 0 when DSORG=PO, could lead to problems like this plus exposures, because you can use other means to read a PDS as if it is a PS. Later when PDS-E were introduced we found that we got fewer JCL errors during allocations if we let SMS by default give DSNTYPE=LIBRARY unless you force it by DSNTYPE=PDS. The same goes for STEPLIBs - we give in RACF only READ access to them so if an user specify a STEPLIB without a DISP statement, the job will fail immediately without any harm to these STEPLIB. :-D Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
