DSXchange

Hmmm... hmmm... hmmm... patiently waits for Ray to whack Ken with the same stick he whacked me with [taps foot] One can get away without bullet-proofing routines, because JOBCONTROL.H is never (up to version 7.0 anyway) automatically defined/included in user-written Routines. I still put the check ...

Also, make sure that all your jobs are in categories.

At one site I worked at there were hundreds of jobs not in categories. They all had to be loaded every time the Jobs part of the repository tree view was selected.

When clients are logged in, take a look at the contents of the DS_LICENSE hashed file in the UV account.
These records' keys are also visible in the LIST.READU output, but it's the other fields that I think you'll find interesting given that you want to know how it works.

I realized that I wasnt actualy using the parramiter that I had available to me so I did, but I would still like to know how to add a paramiter to a before/after routne Jim If you want to use a job parameter in a before/after subroutine, you can do it the same way as in a job control routine. That ...

You can get the file names with a Folder stage, or in Job Control code. You can extract everything to the left of the first underscore using the Field() function. For example: Field(filename, "_", 1, 1) In job control code, you would open the directory as if it were a table (using ...

You can set this up with auto-purge. In director, choose the Job menu, then Clear Log. Instead of choosing immediate purge, choose to enable auto-purge. This opens the auto-purge options frame, in which you can set "clear up to last run". Director will ask you to confirm that you want to override th...

I second Ken's remarks.

If you must do it, pre-encode it with something that converts it to a text-compatible encoding, use Sequential File stages, don't attempt to transform it, and decode the resulting text file prior to bulk loading into SQL Server. Yuk.

Adding to Roy's point, the CREATE TABLE statement (which can be captured from the stage type) is only part of the story. There is always the setting up of the physical storage (and, depending on the database, logical storage too) which is an implicit part of getting best performance from the databas...

The other problem with a WAN is that there are many potential points of failure, any one of which can lead to a "connection is broken" (81002) error occurring and your having to re-start the client. Sometimes a dedicated dialup line may prove to be a more viable solution even if notionally slower. D...

Hi Can anyone explain the purpose of job parameters, why and how they are used ... Thanks In a word, insurance. Insurance against changes between environments (development, test and production); things such as data source names, pathnames and so on. Insurance against things that change over time; t...

A final thought on this topic. If you call the UVFIXFILE command above through DSExecute, the exit status will be 0 in the case of success and non-zero (probably -1) otherwise. So, if you need to test for 64-bit from BASIC, this is an easy solution. * This code relies on the fact that there's no res...

What do you mean by "surrogate key" based on two columns? Are you saying that the natural key contains two columns? The surrogate key itself, of course, need only occupy one column; it's an artificial value with no inherent meaning, used only to guarantee uniqueness. That you've included "based on" ...

I noticed that you specified 5.x as your DataStage release.
If that's true, you don't have PX at all!

There's no need to edit the macro definitions. You can simply override them with newer macro definitions of your own. The newer $DEFINE will replace the older.
In your case, leave out the $IFNDEF that tests whether it is already defined (and its corresponding $ENDIF of course).

You need to add this at the top of the routine to get it to compile: $INCLUDE DSINCLUDE JOBCONTROL.H Also note that your error will never get passed out if there's a problem. You need to add an 'else' in there. It's better (more "bullet proof") to guard against redefinition of constants. The token ...