|
midrange.com
I've never seen a way to view the way you are asking about it. Here are
the variables that SQL defines...
D SQLCA DS
SQL
D SQLCAID 8A INZ(X'0000000000000000')
SQL
D SQLAID 8A OVERLAY(SQLCAID)
SQL
D SQLCABC 10I 0
SQL
D SQLABC 9B 0 OVERLAY(SQLCABC)
SQL
D SQLCODE 10I 0
SQL
D SQLCOD 9B 0 OVERLAY(SQLCODE)
SQL
D SQLERRML 5I 0
SQL
D SQLERL 4B 0 OVERLAY(SQLERRML)
SQL
D SQLERRMC 70A
SQL
D SQLERM 70A OVERLAY(SQLERRMC)
SQL
D SQLERRP 8A
SQL
D SQLERP 8A OVERLAY(SQLERRP)
SQL
D SQLERR 24A
SQL
D SQLER1 9B 0 OVERLAY(SQLERR:*NEXT)
SQL
D SQLER2 9B 0 OVERLAY(SQLERR:*NEXT)
SQL
D SQLER3 9B 0 OVERLAY(SQLERR:*NEXT)
SQL
D SQLER4 9B 0 OVERLAY(SQLERR:*NEXT)
SQL
D SQLER5 9B 0 OVERLAY(SQLERR:*NEXT)
SQL
D SQLER6 9B 0 OVERLAY(SQLERR:*NEXT)
SQL
D SQLERRD 10I 0 DIM(6) OVERLAY(SQLERR)
SQL
D SQLWRN 11A
SQL
D SQLWN0 1A OVERLAY(SQLWRN:*NEXT)
SQL
D SQLWN1 1A OVERLAY(SQLWRN:*NEXT)
SQL
D SQLWN2 1A OVERLAY(SQLWRN:*NEXT)
SQL
D SQLWN3 1A OVERLAY(SQLWRN:*NEXT)
SQL
D SQLWN4 1A OVERLAY(SQLWRN:*NEXT)
SQL
D SQLWN5 1A OVERLAY(SQLWRN:*NEXT)
SQL
D SQLWN6 1A OVERLAY(SQLWRN:*NEXT)
SQL
D SQLWN7 1A OVERLAY(SQLWRN:*NEXT)
SQL
D SQLWN8 1A OVERLAY(SQLWRN:*NEXT)
SQL
D SQLWN9 1A OVERLAY(SQLWRN:*NEXT)
SQL
D SQLWNA 1A OVERLAY(SQLWRN:*NEXT)
SQL
D SQLWARN 1A DIM(11) OVERLAY(SQLWRN)
SQL
D SQLSTATE 5A
SQL
D SQLSTT 5A OVERLAY(SQLSTATE)
SQL
D* End of SQLCA
SQL
D SQLROUTE C CONST('QSYS/QSQROUTE')
SQL
D SQLOPEN C CONST('QSYS/QSQLOPEN')
SQL
D SQLCLSE C CONST('QSYS/QSQLCLSE')
SQL
D SQLCMIT C CONST('QSYS/QSQLCMIT')
SQL
D SQFRD C CONST(2)
SQL
D SQFCRT C CONST(8)
SQL
D SQFOVR C CONST(16)
SQL
D SQFAPP C CONST(32)
SQL
You can try one of those fields, but I don't see anything that will give
you what you want.
What I usually do, is get the values of the variables and then try to run
the statement interactively. But I understand, 10 of them is a lot.
Michael Schutte
Work 614-492-7419
email michael_schutte@xxxxxxxxxxxx
"Brian
Piotrowski"
<bpiotrowski@simc To
oeparts.com> "Midrange Systems Technical
Sent by: Discussion"
midrange-l-bounce <midrange-l@xxxxxxxxxxxx>
s@xxxxxxxxxxxx cc
Subject
03/21/2006 09:44 RE: Returning Passed SQL Statements
AM from Debug
Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>
Hi Mike,
Yeah, I can see it in the source, but the statement with which I'm
working has about ten different variables. I was hoping to see 'em all
in one shot instead of doing an EVAL on each of them.
Brian.
-----Original Message-----
From: Michael_Schutte@xxxxxxxxxxxx [mailto:Michael_Schutte@xxxxxxxxxxxx]
Sent: Tuesday, March 21, 2006 9:28 AM
To: Midrange Systems Technical Discussion
Subject: Re: Returning Passed SQL Statements from Debug
Can you not view it in the source of the program?
If you are having trouble with it... but it in debug mode and just the
value of the dynamic variables.
Michael Schutte
Work 614-492-7419
email michael_schutte@xxxxxxxxxxxx
"Brian
Piotrowski"
<bpiotrowski@simc
To
oeparts.com> "Midrange Systems Technical
Sent by: Discussion"
midrange-l-bounce <midrange-l@xxxxxxxxxxxx>
s@xxxxxxxxxxxx
cc
Subject
03/21/2006 09:11 Returning Passed SQL Statements
AM from Debug
Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>
Hi All,
Is there an EVAL function that will return the SQL statement passed into
the compiler if I do not declare it as a variable? Normally I build an
SQL statement using SQLSTMT = "xxxx". When I do this, all I need to do
is an EVAL SQLSTMT in debug to show me what was passed. However, there
are quite a few times when I just pass the entire statement through to
compiler with the dynamic variables. Is there an EVAL statement that I
can use to see it? I did a quick search, but all I could find were the
general evals on SQLCOD, SQLCA, etc.
Thanks,
Brian.
-=-=-=-=-=-=-=-=-=-=-=-=-=-
Brian Piotrowski
Specialist - I.T.
Simcoe Parts Service, Inc.
PH: 705-435-7814
FX: 705-435-6746
-=-=-=-=-=-=-=-=-=-=-=-=-=-
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-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.
