In a message dated 1/22/2007 7:30:12 A.M. Central Standard Time, usenet5678 @ YAHOO.COM writes: >I'm not sure what to make of this. My understanding is that if you OPEN >a BSAM or QSAM DCB for INPUT and the F1-DSCB has BLKSIZE=0, >you get an S013-34 abend. ... >Gilbert Saint-Flour The OP (_http://bama.ua.edu/cgi-bin/wa?A2=ind0701&L=ibm-main&O=D&X=75B8E4013E0C7C5F81&Y=DASDBILL2%40aol.com&P=81257_ (http://bama.ua.edu/cgi-bin/wa?A2=ind0701&L=ibm-main&O=D&X=75B8E4013E0C7C5F81&[EMAIL PROTECTED]&P=81257) ) said he had an Assembler subroutine that does GETs with QSAM on a RECFM=FB DCB and that the code had been working until recently. IBM's doc [1] says "An error occurred during the processing of an OPEN macro." We don't know the LRECL or OPEN options other than input. Quite a few causes are listed, of which the following seem possible given only the OP's facts: (1) "The following combination was specified: QSAM, MACRF=GD or PD, and a RECFM value that is not VS, VBS, DS, or DBS." (2) "An OPEN macro instruction was issued for a data set with BLKSIZE and BUFL equal to 0. The system determined that it had to obtain buffers but was unable to do so." (3) "The following combination was specified: QSAM, LRECL=0, and a RECFM value that is not V or VB." (4) "The following combination was specified: QSAM and BLKSIZE=0. No nonzero BLKSIZE value was available from any source and the system could not determine one." I described in a previous post that the command reject was caused by the Locate Record's transfer length factor's being zero, and then speculated that this was caused by a zero blocksize. With the large number of options available with QSAM DASD I/O, and since the OP did not say he had gotten a S013-34, I think we can conclude that either (1) there are some combinations of operands that include BLKSIZE=0 that will not cause a S013-34 and will allow QSAM to try to do an I/O with an invalid transfer length factor in the Locate Record parameters or (2) there is something else that the OP did not tell us. And regarding being able to read what a track's previous owner left on the track, the answer is of course you can do it. It may be difficult with some access methods, but it is quite easy with EXCP. This assumes that the track has never been erased. Bill Fairchild [1] z/OS MVS System Messages Volume 7 (IEB-IEE), SA22-7637-12; page 191, message IEC141I
---------------------------------------------------------------------- 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
