DSXchange

Hi Arnd, I still have that patch. Here's what the readme says: Brief description of problem (ecase 70788) ========================================== Increase the timeout in DSD.RUN from 60 seconds to 600 seconds to allow for cases where the D/S server is under heavy load. Instructions for installing...

It's true, you cannot use UDBLoad for mainframe target, UDBLoad only works for for UDB on UNIX/Windows. For mainframe you can create the load file and place it on the host. You would then have to run a mainframe JCL to run the DB2 load utility. Another alternative would be to use the DSEE MVS compon...

Hello Arnd, hope you're doing well ;-) Yes, I've got that patch for a SOLARIS and an AIX customer, both on release 7.51A. I think they don't want to provide that patch in general, but on insisting specific customer request it was provided and helped resolve their issue. Greetings from good old Bavar...

Well, that really sounds like your DB2 mainframe admins shall install the stored procedures option


Klaus

I'd try to do the lookup the other way round: Take the 100 records as input and do the lookup into the big table directly (I hope it has an index on the keys).

In this case this should be much faster and end after the 100 rows are processsed...

Best regards

Klaus

It could be a stored procedure issue as well, as DS is retrieving the metadata with stored procedure calls.

But normally you then would also not be able to view data or import DB2 metadata.

Klaus

As Ray mentioned this is usually due to the fact that you are overloading your system. Means you are starting too many processes at the same time. If a process could not be scheduled 60s after being initiated, DS terminates it. You should try to more serialize your sequence flow. You may also try to...

Krishna, there are about 13 stored procedures in DB2 V8, names are like SYSIBM.SQLxxxxx, which need to be implemented/activated for DS DB2-plugin to work properly for metadate retrieval. Please have your DBA check if all these stored procedures are activated and you have the proper rights to execute...

Stiwari, it's a bit platform depended, but for Db2 typically you will need entries in dsenv like: LD_LIBRARY_PATH=`dirname $DSHOME`/branded_odbc/lib:$DSHOME/lib:$DSHOME/uvdlls:$DSHOME/java/jre/lib/i386/cl ient:$DSHOME/java/jre/lib/i386:/opt/IBM/db2/V8.1/lib/:$LD_LIBRARY_PATH export LD_LIBRARY_PATH P...

Have you sourced the db2profile in dsenv and modfied the LIBPATH for db2 libs? Be aware that you must use th 32bit DB2 client libraries. DS wont work with the 64bit client.

Best regards
Klaus

Check if you have written the file with varchars. You might have the option "varchar prefix byte" active. This bytes may get corrupted when using vi.

In this case you better write the file without varchar prefix bytes. Have a look at the schema definition.

Best regards
Klaus

Hi,

I'm not sure if I got your point, but on a stagevar derivation you can specify something like

If in.field1='xxx' then 1 else stagevar

to keep the contents of stagevar "untouched" in the else case.

Best regards
Klaus

Apologies, I forgot to mention you will be prompted for the file type. It shall be 30 by default (dynamic hash file).

Klaus

Sundar, I assume you created the hash files with the account option. If yes, you first have to create the hash files in the new project. In administrator go to command, then specify e.g. CREATE.FILE SAAB_VIN. After this you shall copy the original hash file into your project and it shall work. Best ...

Hello Christina, > Is it advisable to put all the column manipulation in the stage variables? In general its not a bad idea. I've seen customers doing so. There is, of course, some overhead as all this stage variables have to be maintained. My personal preference is to put "some" of the mo...