|
Ok perhaps a dumb question, but could I specify the name in a WS element and call the procedure like:
01 Call-Name Pic X(12) Value "QlnDumpCobol".
.
.
Call Call-Name Using nn nn nn..... End-Call
Thanks to all who pointed out this case thing, I thought it looked strange that the SQL compile listing was UC and the non SQL was not, but other than trying the above I had no clue how to "easily" get around the problem.
-----Original Message-----
From: Simon Coulter [mailto:shc@flybynight.com.au]
Sent: Friday, July 20, 2001 19:40
To: MIDRANGE-L@midrange.com
Subject: Re: System API QlnDumpCobol
Hello Howard,
You wrote:
>Does anyone have a clue what object has become invisible to the compiler
>that is causing this to be not found?
>If I CRTBNDCBL it works, When I use CRTSQLCBLI it does not work! I am so
>confused!!
The QlnDumpCobol API is a procedure that is exported from the QLNRMAIN
service program. If you display the procedure exports for QLNRMAIN you will
see the procedure uses a mixed-case name. That means you must call it using
the mixed-case name. However COBOL's default behaviour is to use
OPTIONS(*MONOPRC) which effectively upper-cases all procedure calls so you
must be specifying OPTIONS(*NOMONOPRC) when using CRTBNDCBL.
The SQL precompiler does not expose the COBOL compiler options so you must
use CRTSQLCBLI to simply do the first pass and then use CRTBNDCBL on the
resulting output from CRTSQLCBLI.
Specify OPTION(*NOGEN) and TOSRCFILE() on CRTSQLCBLI. The precompiler will
process the SQL statements and convert the SQL source into normal COBOL
source in the specified target source file. Then you can run CRTBNDCBL in
the usual way.
Regards,
Simon Coulter.
«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»
«» FlyByNight Software AS/400 Technical Specialists «»
«» Eclipse the competition - run your business on an IBM AS/400. «»
«» «»
«» Phone: +61 3 9419 0175 Mobile: +61 0411 091 400 /"\ «»
«» Fax: +61 3 9419 0175 mailto: shc@flybynight.com.au \ / «»
«» X «»
«» ASCII Ribbon campaign against HTML E-Mail / \ «»
«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.