|
C/EXEC SQL
C+ SELECT vuUnit INTO :retField
C+ FROM unitFile
C+ WHERE vuAss = :assocUnit
C/END-EXEC
/FREE
errorInfo.errorCode = DSRMUNITS_NO_ERROR;
if (SQLcod = *zeros);
errorInfo.errorCode = DSRMUNITS_UNIT_NOT_FOUND_ERROR;
retField = *blanks;
endif;
return retField;
/END-FREE
Thanks,
Tommy Holden
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
AGlauser@xxxxxxxxxxxx
Sent: Wednesday, September 27, 2006 11:18 AM
To: Midrange technical discussions
Subject: **SPAM** Embedded SQL, first steps
Hi all,
I'm dipping my toes in the embedded SQL waters, because I thought it
would
be more fun than adding a logical to an existing module (which requires
renaming record format and fields and seems like overkill when it will
likely only be used for one procedure). I am at V5R3. I was unable to
find any examples in the archives or a quick skim of the relevant
Redbooks
(Embedded SQL Guide, SQL Reference). Maybe I missed it due to my
limited
knowledge of embedded SQL.
So, I have a very simple procedure:
P*--------------------------------------------------
P* Procedure name: DSRMUNITS_getUnitByAssocUnit
P* Purpose: Retrieve the unit number with which a given unit
is...
P* associated
P* Returns: The unit to which the passed unit is associated
P* Parameter: assocUnit => The associated unit
P* Parameter: errorInfo => Return error information to the
caller
P*--------------------------------------------------
P DSRMUNITS_getUnitByAssocUnit...
P B EXPORT
D DSRMUNITS_getUnitByAssocUnit...
D PI LIKE(unit)
D assocUnit LIKE(unit)
D CONST
D errorInfo LIKEDS(UTTERRDS_errorDS)
D* Local fields
D retField S LIKE(unit)
C/EXEC SQL
C+ SELECT vuUnit INTO :retField
C+ FROM unitFile
C+ WHERE vuAss = (SELECT shopUnit
C+ FROM unitFile
C+ WHERE unit = :assocUnit
C+ )
C/END-EXEC
/FREE
errorInfo.errorCode = DSRMUNITS_NO_ERROR;
if (SQLER3 = *zeros);
errorInfo.errorCode = DSRMUNITS_UNIT_NOT_FOUND_ERROR;
retField = *blanks;
endif;
return retField;
/END-FREE
P DSRMUNITS_getUnitByAssocUnit...
P E
You may notice a problem with this - SQLER3 is not set for simple SELECT
statements. My question is this: is there a way to determine the number
of rows selected? In this case, I can probably just say 'if (retField =
*blanks)' instead of 'if (SQLER3 = *zeros)', but in future I may want to
handle the logical error where there are two matching records.
Any other pointers would also be appreciated,
Adam
########################################################################
#############
Attention:
The above message and/or attachment(s) is private and confidential and
is intended
only for the people for which it is addressed. If you are not named in
the address
fields, ignore the contents and delete all the material. Thank you. Have
a nice day.
For more information on email virus scanning, security and content
management, please contact administrator@xxxxxxxxxxxx
########################################################################
#############
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.