[Sorry, I'm not sure what you mean by "member id" in this context.] That is just a field in both files. No, just one file on the iSeries and one on the server.
I am using the JDBC driver and your JDBC4 program.
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Friday, December 21, 2012 1:34 PM
To: RPG programming on the IBM i / System i
Subject: Re: SQL db in an RPG program - another question
Hi Kim,
Sorry, I'm not sure what you mean by "member id" in this context.
Surely, you aren't working with multiple member files on a SQL Server box?
I'm not clear on how you are reading your DB2 for IBM i table. Are you reading this with embedded SQL? JDBC? CLI? native I/O? I don't see any reason why it'd hurt to keep the file open, in any of these cases.
On 12/21/2012 11:29 AM, Kim Massar wrote:
Now I have to update 3 fields in a file(table) in the SQL db from an
RPG program.
I have to read an iSeries file to get a member id, and then get the
member record from the table in the SQL data base and update 3 fields.
Then loop back and get the next iSeries record.
Using Scott's code, I was planning on using the Prepstmt to hold the
member id value and the 3 variables. Then JDBC_ExecPrepUpd
subprocedure to update the 3 fields in the db. Am I understanding the
code correctly? Can I have the iSeries file 'open' while I get the db
record? Any other help would be appreciated. Thanks, Kim
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.
Email Confidentiality Notice: The information contained in this transmission is confidential, proprietary or privileged and may be subject to protection under the law, including the Health Insurance Portability and Accountability Act (HIPAA). The message is intended for the sole use of the individual or entity to whom it is addressed. If you are not the intended recipient, you are hereby notified that any use, distribution, copying or printing of this message is strictly prohibited and may subject you to criminal or civil penalties. If you received this transmission in error, please contact the sender immediately by replying to this email and then delete the material from any computer.
midrange.com
