Prev: compiling ProCOBOL
Next: .NET. Is it the Holy Grail?
From: Derek Schrock on 15 Apr 2010 10:29 Can I assume error codes returned by rtsora32 should be the same as what comes out of cobrun? http://supportline.microfocus.com/Documentation/books/sx40sp2/rhrerr01.htm is my reference. I'm trying to understand the 102 error code. This is the return code of an rtsora32 command after the the programs run in-full.
From: Richard on 15 Apr 2010 14:32 On Apr 16, 2:29 am, Derek Schrock <derekschr...(a)gmail.com> wrote: > Can I assume error codes returned by rtsora32 should be the same as > what comes out of cobrun? > > http://supportline.microfocus.com/Documentation/books/sx40sp2/rhrerr0... > is my reference. > > I'm trying to understand the 102 error code. "Sequential file with non-integral number of records" The file size is not a multiple of the record size. Reading the last record in the file gave only part record. > This is the return code of an rtsora32 command after the the programs > run in-full.
From: Derek Schrock on 15 Apr 2010 15:23 On Apr 15, 2:32 pm, Richard <rip...(a)Azonic.co.nz> wrote: > On Apr 16, 2:29 am, Derek Schrock <derekschr...(a)gmail.com> wrote: > > > Can I assume error codes returned by rtsora32 should be the same as > > what comes out of cobrun? > > >http://supportline.microfocus.com/Documentation/books/sx40sp2/rhrerr0... > > is my reference. > > > I'm trying to understand the 102 error code. > > "Sequential file with non-integral number of records" > > The file size is not a multiple of the record size. Reading the last > record in the file gave only part record. > > > This is the return code of an rtsora32 command after the the programs > > run in-full. > > That's what I was thinking but wouldn't it kill the program since it's a fatal error? Where would the 102 code be? The file status storage? If it's at the end of the file when it files the incomplete record the status would be 102 then 10 at the "same time?"
From: Richard on 15 Apr 2010 16:58 On Apr 16, 7:23 am, Derek Schrock <derekschr...(a)gmail.com> wrote: > On Apr 15, 2:32 pm, Richard <rip...(a)Azonic.co.nz> wrote: > > > > > On Apr 16, 2:29 am, Derek Schrock <derekschr...(a)gmail.com> wrote: > > > > Can I assume error codes returned by rtsora32 should be the same as > > > what comes out of cobrun? > > > >http://supportline.microfocus.com/Documentation/books/sx40sp2/rhrerr0.... > > > is my reference. > > > > I'm trying to understand the 102 error code. > > > "Sequential file with non-integral number of records" > > > The file size is not a multiple of the record size. Reading the last > > record in the file gave only part record. > > > > This is the return code of an rtsora32 command after the the programs > > > run in-full. > > That's what I was thinking but wouldn't it kill the program since it's > a fatal error? > Where would the 102 code be? The file status storage? If it's at the > end of the file when it files the incomplete record the status would > be 102 then 10 at the "same time?" If you have a file status for the file you will get a 9/102 status value. ie first byte 9 second byte x"66" (decimal 102). This is because it is a failure to reach a proper end of file. If you had not specified the file status clause for the file then to 102 error would kill the program because it is fatal. It may be that you have specified an incorrect record size or that the file has become corrupted.
From: Derek Schrock on 16 Apr 2010 08:08
On Apr 15, 4:58 pm, Richard <rip...(a)Azonic.co.nz> wrote: > On Apr 16, 7:23 am, Derek Schrock <derekschr...(a)gmail.com> wrote: > > > > > On Apr 15, 2:32 pm, Richard <rip...(a)Azonic.co.nz> wrote: > > > > On Apr 16, 2:29 am, Derek Schrock <derekschr...(a)gmail.com> wrote: > > > > > Can I assume error codes returned by rtsora32 should be the same as > > > > what comes out of cobrun? > > > > >http://supportline.microfocus.com/Documentation/books/sx40sp2/rhrerr0... > > > > is my reference. > > > > > I'm trying to understand the 102 error code. > > > > "Sequential file with non-integral number of records" > > > > The file size is not a multiple of the record size. Reading the last > > > record in the file gave only part record. > > > > > This is the return code of an rtsora32 command after the the programs > > > > run in-full. > > > That's what I was thinking but wouldn't it kill the program since it's > > a fatal error? > > Where would the 102 code be? The file status storage? If it's at the > > end of the file when it files the incomplete record the status would > > be 102 then 10 at the "same time?" > > If you have a file status for the file you will get a 9/102 status > value. ie first byte 9 second byte x"66" (decimal 102). This is > because it is a failure to reach a proper end of file. > > If you had not specified the file status clause for the file then to > 102 error would kill the program because it is fatal. > > It may be that you have specified an incorrect record size or that the > file has become corrupted. Well program isn't being killed because it runs to the end "STOP RUN." But back to the original question: should I expect all error codes returned by rtsor32 match with Microfocus' error code page? Will rtsora32 introduce any new return codes or use any that MF runtime is already producing? |