Re: stupid cobol question

DAsmussen@aol.com wrote:

> Ohhhhh, I missed the "SQL pre-compiler" statement before! > 

You didn't miss it in my original post,  the sql part was in a later
post.

> 01     ORDR-REC-A
>          02 ORDR-NBR               PIC 9(9).
>          02 ORDR-NO                 REDEFINES ORDR-NBR.
>               03 ORDR-NBR6        PIC 9(6).
>               03 ORDR-REC-SEQ  PIC 9(3).
> 
> The "03" level fields CANNOT be used in SQL.  This is an SQL/400 limitation,
> and not a COBOL limitation.  We have the same limitation using data
> structures in RPG.  Is this your problem?

kinda, but I don't sessanarily need it to be a sub-definition, I just
need unique variable names, the same size and shape as fields in a file,
that I don't need to qualify, because you can't qualify variables in an
sql statement.  

I can't use the name. from the file because it is defined twice already
in the pgm.   The LIKE would have worked great, but the precompiler
doesn't resolve the LIKE field attributes before trying to compile the
sql statements, thus 
the "unusable or undefined" error.  
 
> HTH,

It probably did, I'm probably SOL.  I think I've spent enough time
researching this already, but it would be nice to know for future
reference.

Thanks again,

rick
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *