DSXchange

Check your UNIX environment for all required packages. You are missing something.

Ray D

Thanks everyone. 2 things. Fix is contained in 8.1 FP2 (we are running FP1). My customer is using a single key value for 10+ tables instead of having 10 key values, thus going thru the keys much faster than they really need. I have asked them to create keys for each of the tables. Regards, Ray D

One of our development teams have a job that was running correctly. The job uses a surrogate key from an oracle database. The surrogate key is over 2 billion (defined as bigint) and it is returning a negative number.... Has anyone run into this before. I don't see anything in the DSXchange. I'm wait...

You of course realise that the term "Big Endian" and "Little Endian" actually comes from a 15 century book? Gulliver's Travels written by Mr. Swift wrote about the Lilliputians political system where the soft boiled eggs were opened with either the big side up, or the little side...

Basically, its allowed but not fully supported. You have to reproduce the problem on a non-citrix environment. However with the number of large sites requiring this type of functionality, it really needs to be fully supported.

Cheers,

Ray D

We ran into this same problem two weeks ago. I spent 15 hours in the office helping the team redesign their job. Datastage at it's heart is a 32bit application. 2^31 works about to about 2 GB in size. Turns out that the maximum size of a single lookup is 2GB in size as documented on the IBM website....

BTW, I agree that you should NOT be resizing the VOC file unless you know what you are doing inside UniVerse. Besides, it won't improve performance all that much. You are importing complex information into your XMETA repository. That's where the delay stems, not the VOC file. I've tried to get Peggy...

Depending on your Datastage revision, there is a unix based import process for DSX files. Move the DSX file to unix directory execute the unix shell script. It's the InformationServer/ASBNode/bin/DSXImportService.sh command. Perform the import from here and you don't have to worry about the VPN. Reg...

Depending on your Datastage revision, there is a unix based import process for DSX files. Move the DSX file to unix directory execute the unix shell script. It's the InformationServer/ASBNode/bin/DSXImportService.sh command. Perform the import from here and you don't have to worry about the VPN. Reg...

Having some issues with datastage client tools on Citrix. IBM Support has stated that they don't support Director/Designer clients running on Citrix. We have not had any problems with 8.1 clients on the system, but 8.5 clients are producing multiple core dumps on the Citrix systems filling up our di...

How many sites out there are using CITRIX to access your Datastage clients?

Regards,

Ray D

Control-M should have some client software that executes on the AIX box accepting commands from the Control-M environment. If there is no software, then create a unix script that does a ssh to the AIX box. Make sure you setup ssh keys establishing a trust between the AIX system and the Linux system....

Depending on your release you would use the "Import/Export Manager". This will be replaced in the future with the Import MANager.

Regards,

Ray D

Backing up a Type30 causes the ".Type30" to go missing. One solution is to add a .Type19 hidden file to the directory and at the ">" prompt, create a VOC ENTRY that looks like this: F PATHNAME D_VOC Then do a COPYI FROM PATHNAME TO REPAIREDHASH ALL -------- Cheers, Ray D

I'm looking over a job which is constructed as follows: Connector --> Lkp --> Lkp --> Lkp --> etc --> Dataset There are a total of 9 lookups. Each lookup is populated by a connector stage. Just populating the lookups can take 15 to 20 mins, and then the job starts processing. I'm not sure if the loo...