Right. Actually, I think it is the zero BLOCK size not the zero RECORD length that ends up in an invalid CCW, but pretty much equivalent manifestations of the same root problem.
BTW, and FWIW, I have solved the problem by adding to the code a branch to normal EOF if after opening the input DCB, and before issuing the first GET, the DCBBLKSI is zero. Given the full circumstances of the situation, I see it as a normal condition -- an empty input dataset -- and not an error. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Shmuel Metz (Seymour J.) Sent: Sunday, January 21, 2007 6:33 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: What is "command reject" trying to tell me? In <[EMAIL PROTECTED]>, on 01/16/2007 at 10:36 AM, Paul Gilmartin <[EMAIL PROTECTED]> said: >Yet, unconditionally entering EODAD on any attempt to read beyond >DS1LSTAR _before_ formatting the CCW or issuing the EXCP would avoid >Charles's problem. How? The problem is an incorrect value in the channel program, not residual data on disk. OPEN should have detected[1] the LRECL=0,RECFM=FB and issued an S013. [1] After DCB exit, etc., processing. ---------------------------------------------------------------------- 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
