DSXchange

You need to be in the UV account and in the dssh shell (uvsh shell) to execute this command.

Link row counts are logged for all active stages in the "active stage finishing" messages in the job log.

Make sure you have a good backup (readable) before you start.

Search the Forum for a link to a paper called "Date Conversion Demystified" which is an easy introduction to date conversions.

You can have them both installed, but you can only have one at a time running unless you do some configuration, such as changing the shared memory identifier prefix in one of the instances and increasing the kernel parameters for shared memory and semaphores (particularly) to double the recommended ...

Welcome aboard! :D Whoever creates the table, or someone with DBA privilege, can grant appropriate privileges to anyone else, such as the user ID under which DataStage jobs will connect to Teradata. You should make the user ID and password (and database name) job parameters, because they will be dif...

The 'M' in 'DMY' is for a numeric month. You should be able to try a couple of difference things off the top of my head... Try "DDMBY2" as 'MB' is the abbreviated month name. Or just a "D2" all by itself, as the default format of 'D' is 'DD-MON-YYYY' and the two at the end tells it a two digit year...

The Version Control manual takes you through all the steps in quite a clear fashion.

The problem I had was developers destroying the template jobs by opening them, developing in them, and clicking Save.

I maintain the templates on the shared drive using Notepad - a template is an XML-tagged DSX file.

If you have "disable combination" set to True, there is one player process per Orchestrate operator on each processing node mentioned in the configuration file. If you have "disable combination" set to False, then some player processes will manage more than one operator, so there will be fewer playe...

2) Export bypasses the index because it selects all job names with which to populate the drop-down list.

The command is DS.REINDEX ALL

My suggestion was made in the absence of that new knowledge. If you use the Continue rule you could test the result of a lookup column, which should be null if the lookup failed. Make sure not to test a column that might actually return nulls. That is, the same technique as you might use in a server...

My bad. Failed to take into account that the print was an awk print - that is, in an awk block. Come's from replying after my bed time.

Go for the top. Sue the company. Oh, they don't exist any more. Shame.

In case they wanted to put in other stuff for interactive processes.