RE: Updating DB2 table from one IBM i to Another IBM i

Thanks, Rob.

I have a new problem - the name of the relational database entry on the old production box is the same name of the relational database on the new production box (because we did an Option 21 backup/restore). I cannot add a new *LOCAL entry in the RDB directory entry on the old box, and I'm hesitant about deleting it (it gave me a nasty warning, so I cancelled it).

Is there a way to rename the directory entry on the old production box?

Thx.

/b;


Brian Piotrowski
Manager, I.S.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob Berendt
Sent: Wednesday, August 7, 2019 2:21 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Updating DB2 table from one IBM i to Another IBM i

First off there's sql naming (system.schema.table) then there's system naming (system/library/file). This is "3 part naming". Never tried it with system naming, only sql naming.



See also WRKRDBDIRE. Ensure that both systems show up here, on both systems.



See also ADDSVRAUTE, DSPSVRAUTE, CHGSVRAUTE. Alas no WRKSVRAUTE. It helps to have whomever runs this feed in here.



I think having system value QRETSVRSEC set to 1 helps.



Then it becomes really simple to pull data from another system with stuff like the following:

insert into rob.barf

(select * from gdihq.erplxf.rco)

;





Rob Berendt