On Sun, 4 May 2008 05:04:36 -0400, Stocker, Herman wrote: >Thank you Scott, > >This time the procedure does not work, I'm getting an RC 8 from the LMDELETE >(8 - Member not found). > >When I copied the data set the members give the error message: >IEB189I DIRECTORY ENTRY §YB4I2QK IN BLOCK READ FROM DDNAME INVOL1 >IS OUT OF SEQUENCE OR DUPLICATE AT TTR X'001D0D' > MBBCCHHR X'0000000003000E0D' > Ouch! Wouldn't this be a serious structural error, resulting from a logic error. Even an empty member should be terminated with an EOF, which would cause the next member to begin at a different TTR.
>Both TSO & IDCAMS do not tale a hex character. > Decades ago, ISPF member lists would display members with nonstandard names, and they could be deleted with prefix commands (but not from the command line). I don't know what recent behavior might be. I consider it a significant design blunder for any file system to fail to enforce the syntactic rules intended by the designers: if the designers intended PDS member names to be case-insensitive, STOW and BLDL should convert their argument names to a single case. If they intended upper case only, STOW should fail when called with a mixed case name (but BLDL should perform the directory lookup and fail with member not found, or return it if it exists regardless of syntax rules). If the designers intended to support mixed case names, as STOW and BLDL do, TSO, ISPF, and other utilities should not overrule their design by forcing input to upper case, particularly if the member name is quoted. -- gil ---------------------------------------------------------------------- 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
