|
That's great thanks Mike,
I very much appreciate you taking the time to explain.
Even if the DDM File works and performs ok I'll try to find time to look
into the process you describe, I always think of DDM Files as a bit clunky
( which I admit might be unfair of me... )
Best regards,
Craig
On 5 January 2018 at 17:35, Mike Jones <mike.jones.sysdev@xxxxxxxxx>
wrote:
Hi Craig,B,
3 part SQL looks like this:
=> While connected to system A <=, run an INSERT into a table on system
that looks like this:of 3
insert into B.MY_SCHEMA.MY_TABLE
...rest of insert statement
It is called 3 part SQL because there are 3 parts, separated by a period,
that identify the target table:
1) B is the remote system name
2) MY_SCHEMA is the schema name on system B
3) MY_TABLE is the table name on system B
It has been a long time since I've configured systems to allow the use
part SQL, but one part I recall is you need a RBD directory entry setupvia
the WRKRDBDIRE command that defines the remote system you're going toauthorization
access in that 3 part SQL. You also have authentication and
to deal with, because the remote system isn't going to allow just anyoneuse
(authentication) to connect to it and do whatever they want to whatever
resource (authorization), in typical security scenarios at least. I
believe the default configuration is an attempt to use 3 part SQL will
the same user ID and password that is in use on system A to authenticateto
onto system B and to determine if that authenticated user is authorized
the remote table being referenced.it
In that scenario, IDENTITY_VAL_LOCAL() has worked for me. When I tried
for the first time, I wasn't too confident it would work, but I wasof
pleasantly surprised it did. I lost track a long time ago of the number
times I've thrown something at the SQL engine where I was expecting agood
chance of regurgitation, and it replied with a "haha no problem I've gotpossible
your back".
Mike
On Fri, Jan 5, 2018 at 9:06 AM, Craig Richards <craig@xxxxxxxxxxxxxxxx>
wrote:
Hi Mike,
Thanks for your reply.
I'm sorry I'm not sure what you mean by "3 Part SQL" would it be
usedfor you to elaborate a little?you
The DDM is not my design and I'm not married to it so if there is a way
think is preferable I'm certainly open to suggestions.
thanks kindly,
Craig
On 5 January 2018 at 16:46, Mike Jones <mike.jones.sysdev@xxxxxxxxx>
wrote:
Hi Craig,
I've not tried that specific DDM example, but I have successfully
IIDENTITY_VAL_LOCAL() when I connected to, for example, system A, and
craig@xxxxxxxxxxxxxxxxusesystem
3 part SQL referencing system B involving INSERTs into a table on
B. That is an alternative to use, and in my opinion is preferable touse,
versus the DDM route to get that done.
Mike
On Fri, Jan 5, 2018 at 4:27 AM, Craig Richards <
DDM
wrote:
Hi All,
Does anyone know offhand if you can use Identity_Val_Local() on a
column.needFile?
I don't have the opportunity to test this at the moment but I will
to
tweak my design if not.
Specifically:
1. Client on LPAR 1 has a DDM File pointing to a file on LPAR2.
2. The file on LPAR2 has a "generated always as identity"
affiliateaffiliate(RPG400-L)3. Client on LPAR 1 writes a record to the DDM File
4. Can the client then use identity_val_local() to retrieve the
generated column value?
Thanks kindly in advance,
Craig
--
This is the RPG programming on the IBM i (AS/400 and iSeries)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our
(RPG400-L)link: http://amzn.to/2dEadiD--
This is the RPG programming on the IBM i (AS/400 and iSeries)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our
(RPG400-L)link: http://amzn.to/2dEadiD--
This is the RPG programming on the IBM i (AS/400 and iSeries)
--mailing list--
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
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.