Michael,

>   If all you're doing is reading the file in the sequence generated by
the
>  OPNQRYF, then you should be able to code it for sequential organization
>   and access.  Then you won't have to be concerned about the RECORD KEY
>   clause.

>   SELECT HISTRY4 ASSIGN TO DATABASE-HISTRY4
>       ORGANIZATION IS SEQUENTIAL
>       ACCESS MODE IS SEQUENTIAL
>       FILE STATUS IS FILE-STATUS-01.

>   Your open query file will hand the records to your COBOL program in
HITEM,
>   LMRKTC sequence.

Thanks - this is exactly why I asked the group!  in RPG, you specify keyed
access - that allows the file to be accessed by the open data path.

Terry,

>We don't do a lot of OPNQRYF's feeding Cobol programs
>so I can't help you much there, however, I noticed
>you do not have an OPNSCOPE parm on your OPNQRYF statement.
>This could bite you depending on how your job calls
>are set up.  The majority of our jobs use OPNSCOPE(*JOB)
>to ensure that the open query file doesn't carry over
>into another job.

this shouldn't be a problem - I clof my opnid and dlt my ovr right after
the program call.

(i clofed my opnid - hee hee - and we all know how painful that can be ;)

thanks everybody,

Rick



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.