It's normal operation actually; The directory blocks are considered sequentially accessed blocks. As there was no member name on the DSN basically IDCAMS did exactly what was asked, and wrote the data to the PDS Directory area.
I've done the same thing from COBOL at times when I've wanted to either read, or update the directory blocks programmatically Darren -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Patrick O'Keefe Sent: Wednesday, February 06, 2008 12:48 PM To: [email protected] Subject: Re: VSAM Surprise On Wed, 6 Feb 2008 08:38:52 -0800, GAVIN Darren * OPS EAS <[EMAIL PROTECTED]> wrote: >The problem is you are giving it a space param with directory block >counts on the output file (the third number in space card), SMS picks >that up and allocates a PDS instead of a Sequential file. > >Change SPACE=(CYL,(7,1,43),RLSE) to SPACE=(CYL,(7,1),RLSE) >... The original poster admitted all that. The question is whether or not IDCAMS should complain about being asked to write to a PDS (not a member of a PDS) as a PS dataset. >... >It's not a IDCAMS issue >... I don't think that's a given. It's easy to see why this happens, and it's not too difficult to deal with it (as others have noted), but I think it violates the principle of least astonishment. Writing to a PDS as a PS dataset is almost certainly done by accident. It would be nice it IDCAMS would just say "You didn't want to do that.". Pat O'Keefe ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
