DSXchange

Add the -wait option to force the dsjob program to wait for the job to finish, or, go into a loop periodically checking the status yourself until you see that the job has finished.

It's not so much "Ken's utilities" as it is the method. A centralized job (kind of like a Sequence) that organizes the flow and execution of a series of jobs. In addition to parameter setting, we took it about 42 steps further and introduced dynamic instantiation, instantiation based on an array of ...

For those attending the conference, stop by the DSXchange booth and say hi. Ray Wurlod and myself will be there to meet and greet our many friends on the DSXchange.

My compile utility job is multi-instance enabled. You can run multiple instances and give the parameter for the folder a different value. I do this so that I have the compile running server side, as well as parallel executing jobs. It gets it done a lot quicker. The only issue I've found is that som...

The latest stuff is documented in the JobControlGoodies zip. There's even a job control document to go with it. Keep in mind, all of this stuff is part of a larger scheme, it's up to the individual to get it working in your environment. It's a little rough around the edges, but should be easy to get...

John is looking for a database level checksum/crc32 function to facilitate queries in the native database.

I'll get the job control libraries and full utility set out there today. Sorry for the delay.

There are folks running around as IBM consultants giving out core functionality items in job designs that uses the proprietary job design array structures to facilitate some transformation activities. In my opinion, this is a MAJOR mistake. The use of non-documented and internal knowledge means that...

There should be no overhead to the physical job execution. If a job is unnecessarily enabled but never ran as an instance, there is probably no impact whatsoever to performance. There's no extraneous job log messaging, etc.

Consider using an After-Stage subroutine call also. Maybe on the last link writing to the last Passive stage. Add a Transformer if necessary to do this. You do have After-Stage subroutine calls that are exactly the same as After-Job subroutine calls. Put one command in the stage, the other in the jo...

Absolutely, Server jobs are still an option, Sequence and Batch jobs as well. There is NO other method in PX to do similar things, because PX is just a job flavour.

You will always get back a string, unless the value is a NULL, you'll get a NULL. If the value is shorter in length than your position, you will get blank (you know quote-quote ""). Since you're using it in an If-Then-Else, you need to consider handling the NULL condition, which you're not. You're a...

The easiest method is going to be a DS Function that opens and reads a hashed file. You would want to stage all of the data into a hashed file. Then, read your parent rows and for each row use a Function to derive your required results. That Function can lookup a child row in the reference hashed fi...

By the way, the Informix, Sybase, and DB2 plugins all have this same issue. Get used to toggling DATE to TIMESTAMP. the DRS stage is just a facade to the plugins, so it's all the same.

The issue is that the DB2 Plugin and DRS stage set to DB2 have the same stupid logic that translates DATE datatype values to the internal DS BASIC date integer value. Toggling to TIMESTAMP prevents this from happening, and everything works fine. When loading into a table, DATE columns are expected t...