I have a procedure with a complex data structure /COPY'd under an 01-level 
Linkage Section item. This procedure needs to extract one of the fields for 
some work, but most other fields in the data structure are not directly 
referenced. I've created a Working-storage Section field that uses LIKE to get 
the same definition as the single field that I want.

However, it looks like I need to move the Linkage Section specs ahead of 
Working-storage in order for the compiler to see the LIKE object first. Of 
course, this causes a "Working Storage out of sequence. Accepted." warning 
message on the compile; but otherwise it seems to compile fine. Without this 
sequence, I get LNC2515, "LIKE object <field-name> not defined. Clause 
discarded." as well as LNC1236, "No PICTURE for elementary item <field-name>".

I didn't see any restriction in the manual except that if the LIKE object was 
grouped with other fields that had a TYPE clause, the TYPE must be fully 
resolved first (or something similar to that). It didn't seem exactly to be 
what I was doing, but it pushed me into rearranging the order of Linkage and 
Working-storage Sections just to see if it'd work.

Has anybody else seen similar behavior? Is there are better approach than the 
one I took?

Thanks.

Tom Liotta

--
--
Tom Liotta
The PowerTech Group, Inc.
19426 68th Avenue South
Kent, WA 98032
Phone  253-872-7788 x313
Fax    253-872-7904
http://www.powertechgroup.com


__________________________________________________________________
The NEW Netscape 7.0 browser is now available. Upgrade now! 
http://channels.netscape.com/ns/browsers/download.jsp

Get your own FREE, personal Netscape Mail account today at 
http://webmail.netscape.com/


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.