>>> In this case, because it is the behavior of the header record (which for one I'm assuming is the first record), these would only be potential issues if the file only consisted of the header, no other records.
Bill, Not really. Assuming that OP's program is indeed dealing with VB files, the header might be a Short record and the MOVE resulted in moving the full length than the actual short record length and hence the S0C4. The detailed records following the Header record *may* be of full length and MOVE statements worked fine. Skipping the short header record *might* have solved the issue. (Just a guess) Kolusu IBM Mainframe Discussion List <[email protected]> wrote on 02/07/2017 02:13:13 PM: > From: Bill Woodger <[email protected]> > To: [email protected] > Date: 02/07/2017 02:13 PM > Subject: Re: Program now working, but why? > Sent by: IBM Mainframe Discussion List <[email protected]> > > In this case, because it is the behaviour of the header record > (which for one I'm assuming is the first record), these would only > be potential issues if the file only consisted of the header, no > other records. > > > > Of course, the header record can be a coincidence. In changing the > code, the size of > > On Tue, 7 Feb 2017 13:39:11 -0700, Sri h Kolusu <[email protected]> wrote: > > >>>> The programmer added code to bypass the header record on the first > >file read, now it runs at the development level. > > > >You may want to check this out > > > >http://www-01.ibm.com/support/docview.wss?uid=swg21242182 > > > > > >Kolusu > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
