|
midrange.com
Hi Dave,
You actually need to have SQLCA_DS as a member in your library list.
Paste these D specs into a member SQLCA_DS in a source file on your
iSeries, then code a /COPY for that source member.
D SQLCA DS
D SQLAID 1 8A INZ(X'0000000000000000')
D SQLABC 9 12B 0
D SQLCOD 13 16B 0
D SQLERL 17 18B 0
D SQLERM 19 88A
D SQLERP 89 96A
D SQLERRD 97 120B 0 DIM(6)
D SQLERR 97 120A
D SQLER1 97 100B 0
D SQLER2 101 104B 0
D SQLER3 105 108B 0
D SQLER4 109 112B 0
D SQLER5 113 116B 0
D SQLER6 117 120B 0
D SQLWRN 121 131A
D SQLWN0 121 121A
D SQLWN1 122 122A
D SQLWN2 123 123A
D SQLWN3 124 124A
D SQLWN4 125 125A
D SQLWN5 126 126A
D SQLWN6 127 127A
D SQLWN7 128 128A
D SQLWN8 129 129A
D SQLWN9 130 130A
D SQLWNA 131 131A
D SQLSTT 132 136A
D* End of SQLCA
Regards,
Nazmin Haji
Eclipse iSeries Tooling Development
Dave Boettcher
<DBoettch@xxxxxxxxx To: "'CODE/400
Discussion & Support'" <code400-l@xxxxxxxxxxxx>
a.wi.us> cc:
Sent by: Subject: RE: Verifying
SQLRPGLE
code400-l-bounces@x
idrange.com
05/28/2003 05:10 PM
Please respond to
CODE/400 Discussion
& Support
I hope I can make this work but I just tried it and got this error:
The program verifier does not support ifs copy files.
What did I miss?
Dave Boettcher
-----Original Message-----
From: Michele Cummings [mailto:mcumming@xxxxxxxxxx]
Sent: Wednesday, May 28, 2003 3:35 PM
To: CODE/400 Discussion & Support
Subject: RE: Verifying SQLRPGLE
Hi Rick..
If the problem that you are encountering is due to the fact that the SQLCA
DS is not defined, you could use the following workaround:.
Define a compiler-condition. Specify NEED_SQLCA in the Verify
dialog for your Code/400 verify, but don't define it for your regular
compiles.
This way you do not have to keep changing your program.
/IF DEFINED(NEED_SQLCA)
/COPY sqlca_ds
/ENDIF
Hope that helps.
Michele Cummings
WDSC for iSeries
|---------+-------------------------------------------------->
| | "Chevalier, Rick" |
| | <Rick.Chevalier@xxxxxxxxxxxxxxx> |
| | Sent by: |
| | code400-l-bounces+mcumming=ca.ibm.com@x|
| | idrange.com |
| | |
| | |
| | 05/28/2003 10:55 AM |
| | Please respond to CODE/400 Discussion &|
| | Support |
| | |
|---------+-------------------------------------------------->
>
---------------------------------------------------------------------------
-----------------------------------------------|
|
|
| To: "'CODE/400 Discussion & Support'"
<code400-l@xxxxxxxxxxxx> |
| cc:
|
| Subject: RE: Verifying SQLRPGLE
|
|
|
|
|
>
---------------------------------------------------------------------------
-----------------------------------------------|
Probably doable but I can just compile and get the returned errors in WDSc
which sounds a lot easier than tracking down the intermediate source from a
compile and verifying that. I just wanted to play with the new features
and
try to keep as much off of the iSeries as possible. It seems to work fine
for non SQLRPG programs.
Rick
-----Original Message-----
From: Vern Hamberg [mailto:vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx]
Sent: Wednesday, May 28, 2003 8:36 AM
To: CODE/400 Discussion & Support
Subject: RE: Verifying SQLRPGLE
Rick
There's an option in the CRT commands for embedded SQL, to save the
generated source. Then you could compile from this, or perhaps verify that.
Not the ideal, but doable?
HTH
Vern
At 07:38 AM 5/28/2003 -0500, you wrote:
>I experience the same situation using 5.0. I do a lot of embedded SQL and
>would sure like to be able to verify the SQLRPGLE source members if there
is
>a way to do it.
>
>Rick
_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/code400-l
or email: CODE400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.
NOTE: WDSc for iSeries disucssion has it's own mailing list.
Information can be found at
http://lists.midrange.com/cgi-bin/listinfo/wdsc-l
_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/code400-l
or email: CODE400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.
NOTE: WDSc for iSeries disucssion has it's own mailing list.
Information can be found at
http://lists.midrange.com/cgi-bin/listinfo/wdsc-l
_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/code400-l
or email: CODE400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.
NOTE: WDSc for iSeries disucssion has it's own mailing list.
Information can be found at
http://lists.midrange.com/cgi-bin/listinfo/wdsc-l
_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/code400-l
or email: CODE400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.
NOTE: WDSc for iSeries disucssion has it's own mailing list.
Information can be found at
http://lists.midrange.com/cgi-bin/listinfo/wdsc-l
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.
