Re: [open-cobol-list] RM/Cobol C$RERR

[emre]

Hi,

My issue with extended status was resolved via the procedure described 
in section
5.1.4 of http://www.emunix.emich.edu/info/cobol/books/cgrmci.htm

I had a few other minor/easily resolved issues to contend with.
1. comp-1 gives a 32 bit value and my c-code screen library assumed 16 bit.
2. my comp-1 fields had a pic, had to remove.
3. remove RANDOM in 'ASSIGN TO RANDOM'.
4. changed hex indicators H" -> X"

I have my application now running under opencobol... yeah!

-Emre.



vince coen wrote:
> Hi;
> On Thursday 06 August 2009, emre wrote:
>   
> > Hello Everyone,
> >
> > I am working on converting some rmcobol-85 code to oc.
> >
> > rmcobol has a "C$RERR" call which  returns an expanded I-O completion
> > status.  The status is a 4 character (or 11 character) status for the last
> > attempted I-O operation.
> >
> >     
> OC uses the standard status code vis ANSI 85 with some others from the 2002 
> spec.
>
> Download http://www.cobolstandard.info/j4/files/std.zip for the current 
> document dont print it out as its very long (almost 900 pages) see from page 
> 169 for the values of I-O status (mostly implemented) as well as CRT status 
> (which appear to be fully implemented).
>
> For the full list see the OC source code.
>
> Vince
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
> trial. Simplify your report design, integration and deployment - and focus on 
> what you do best, core application coding. Discover what's new with 
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> open-cobol-list mailing list
> address@hidden
> https://lists.sourceforge.net/lists/listinfo/open-cobol-list
>
>