RE: [open-cobol-list] OC issues

[Bill Klein]

So then, it has nothing to do with your original

  COPY C2 REPLACING ==01 == BY ==02 ==

If it DOES, then please show the exact COPY statement(s) and what is in each
COPY member.

Certainly having an 02-level AFTER an 05-Level - when there is no 02 level
above is NON-Standard and not something that COBOL source code is SUPPOSED
to do.

P.S.  Having
    REPLACING ==01 == BY ==02 ==

in source code is ALWAYS dangerous, because given source code like:

01 Field1.
       05  Field2  Pic X(01).

BOTH the 01 level indicator and the 01 in the picture will get replaced. The
space is NOT significant in COPY REPLACING pseudo-text.

> -----Original Message-----
> From: Sergey Kashyrin [mailto:address@hidden 
> Sent: Tuesday, January 17, 2006 10:54 AM
> To: Bill Klein; address@hidden
> Subject: Re: [open-cobol-list] OC issues
> 
> Bill,
> 
> It's not about the margin.
> That will work:
> 01 A.
> 02 FILLER.
> 05 FIELD PIC X.
> 02 FLD2 PIC X.
> 
> That does not work:
> 01 A.
> 05 FIELD PIC X.
> 02 FLD2 PIC X.
> 
> ----- Original Message ----- 
> From: "Bill Klein" <address@hidden>
> To: "'Sergey Kashyrin'" <address@hidden>; 
> <address@hidden>
> Sent: Tuesday, January 17, 2006 11:46 AM
> Subject: RE: [open-cobol-list] OC issues
> 
> 
> > Sorry,
> >  Your reply still doesn't make sense.  It is PERFECTLY 
> legal to change an
> > 01-level to an 02-level (before an 05-Level) ASSUMING that 
> you have an
> > 01-level in the structure.  As I indicated, there are 
> issues about 01-levels
> > being in the A-margin and 02-levels being in the B-margin.
> > 
> > I don't think anyone is going to be able to help you until 
> you can show us
> > the actual code and error messages. 
> > 
> >> -----Original Message-----
> >> From: address@hidden 
> >> [mailto:address@hidden On 
> >> Behalf Of Sergey Kashyrin
> >> Sent: Tuesday, January 17, 2006 10:32 AM
> >> To: Bill Klein; address@hidden
> >> Subject: Re: [open-cobol-list] OC issues
> >> 
> >> 
> >> The issue is that level 02 is following level 05 and there 
> >> was no 02 before.
> >> I'm not a Cobol guru but I expect that standard does not 
> allow that.
> >> Tandem (HP Nonstop) Cobol gives an error too.
> >> The rest  - at least  all 390 mainframe, AS400, MFocus, 
> >> Fujitsu are giving only warning and producing the correct code.
> >> 
> >> I think if it's possible it's better to fix (at least for 
> >> mf,ibm,mvs dialects)
> >> 
> >> Regards,
> >> Sergey
> >> 
> >> ----- Original Message ----- 
> >> From: "Bill Klein" <address@hidden>
> >> To: "'Sergey Kashyrin'" <address@hidden>; 
> >> <address@hidden>
> >> Sent: Tuesday, January 17, 2006 11:03 AM
> >> Subject: RE: [open-cobol-list] OC issues
> >> 
> >> 
> >> >I don't understand the issue.  Is the problem that of 
> "A-margin" vs
> >> > "B-margin" or what error are you getting?
> >> > 
> >> > (The '85 Standard *did* have rules about replacing text 
> >> must go in the
> >> > margin where replaced text was - but I thought OC had an 
> >> option - or default
> >> > - to ignoring A-/B-margin issues).
> >> > 
> >> > P.S.  It would NOT surprise me if this caused a problem on 
> >> IBM mainframes.
> >> > Are you using one of those dialects? 
> >> > 
> >> >> -----Original Message-----
> >> >> From: address@hidden 
> >> >> [mailto:address@hidden On 
> >> >> Behalf Of Sergey Kashyrin
> >> >> Sent: Monday, January 16, 2006 11:27 PM
> >> >> To: address@hidden
> >> >> Subject: [open-cobol-list] OC issues
> >> >> 
> >> >> Hi everybody,
> >> >> 
> >> >> Currenltly I'm trying to make a small project (8M+ lines) to 
> >> >> work under OC (amd64) :-)))
> >> >> Small annoying issues (currently just one but I expect more 
> >> >> to follow) :
> >> >> 
> >> >> The situation is that the very old dog has that construction:
> >> >> 01 XXX.
> >> >>    05 AAA PIC X.
> >> >>    02 BBB PIC Y.
> >> >> 
> >> >> Not exactly initially but as a result of playing with a 
> >> copybook like
> >> >> COPY C1
> >> >> COPY C2 REPLACING ==01 == BY ==02 ==.
> >> >> when they want to combine something in a woraking area or 
> >> >> LINKAGE section :-(
> >> >> 
> >> >> As a matter of fact all Cobols that I know (but Tandem) are 
> >> >> giving the WARINING and working fine with that.
> >> >> 
> >> >> OC gives an ERROR and not producing the code.
> >> >> 
> >> >> I don't have a time right now to look into that but maybe 
> >> >> will try later (it's not that critical, not too many 
> occurances).
> >> >> Overall from 2800+ programs 350 didn't compile. Will look 
> >> >> into all remaining issues and inform.
> >> >> 
> >> >> Regards,
> >> >> Sergey
> >> >> 
> >> >> 
> >> >> 
> >> >> -------------------------------------------------------
> >> >> This SF.net email is sponsored by: Splunk Inc. Do you grep 
> >> >> through log files
> >> >> for problems?  Stop!  Download the new AJAX search engine 
> >> that makes
> >> >> searching your log files as easy as surfing the  web.  
> >> >> DOWNLOAD SPLUNK!
> >> >> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&;
> >> >> dat=121642
> >> >> _______________________________________________
> >> >> open-cobol-list mailing list
> >> >> address@hidden
> >> >> https://lists.sourceforge.net/lists/listinfo/open-cobol-list
> >> >> 
> >> >
> >> 
> >> 
> >> -------------------------------------------------------
> >> This SF.net email is sponsored by: Splunk Inc. Do you grep 
> >> through log files
> >> for problems?  Stop!  Download the new AJAX search engine 
> that makes
> >> searching your log files as easy as surfing the  web.  
> >> DOWNLOAD SPLUNK!
> >> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&;
> >> dat=121642
> >> _______________________________________________
> >> open-cobol-list mailing list
> >> address@hidden
> >> https://lists.sourceforge.net/lists/listinfo/open-cobol-list
> >> 
> >
>