I have several OS/390 mainframe Cobol programs (DB2 V6 is on the mainframe) that need to access DB2 UDB v8 on Linux.
I have communications figured appropriately and have compiled the SPUFI tool and EasyTrieve Plus packages (successfully executed remote processes).
BUT - I cannot figure out how...
I have several OS/390 mainframe Cobol programs (DB2 V6 is on the mainframe) that need to access DB2 UDB v8 on Linux.
I have communications figured appropriately and have compiled the SPUFI tool and EasyTrieve Plus packages (successfully executed remote processes).
BUT - I cannot figure out how...
Thank you!
We will try the "Classic Suite" toolset... Along with "Catalog Manager" and "Smart DBA Cockpit".
Any nuances that I should know about - what toolset combo works well for you?
DB2 UDB v8:
If the source data is in DB2 you can load from a cursor:
declare mycursor cursor for select * from my.table1
load from mycursor of cursor method P(1,2,3) insert into
my.table2(one,two,three)
(Not sure if that would work with a federated table to Oracle or not - seems like it...
We have looked at DBArtisan and Quest Central...
Anyone know of some good toolsets we can trail for administering DB2 UDB v8 on Linux?
Thank you in advance for your suggestions-
Rick
Error:
SQL0443N Routine "SYSIBM.SQLCOLUMNS" has returned an error SQLSTATE with diagnostic text "SYSIBM:CLI:-805". SQLSTATE=38553
Basically, a timestamp error...
I ran binds for the CLI packages, but the error persists!
[<> bnd]$ db2 bind @db2cli.lst
LINE MESSAGES FOR db2cli.lst
------...
The only class notes I have about this issue says - If the machine name changes, update "db2nodes.cfg"
You may want to get conformation from IBM before attempting that - but it might help you.
Rick
Actually, I think I know this one (and it is my post-lol!) The directory I was writing to was not really local (mapped) and the communication protocal on the mapped drive changed from protected packets (TCP?) to Unprotected (UDP?) - or something like that. I'm a mainframe DBA trying to get by in...
Anyone have a clue where I can look this error up? ("sqloopen -2062614522")
More info on the error: We are running the DB2 UDB v8 EXPORT utility (Linux) to pull a large amount of data from mainframe to a mapped directory on local server...
SQL3001C An I/O error (reason =...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.