DSXchange

All of the previous responses are correct if, by "Julian dates", you mean a date containing the ordinal number of the day within the year. If you mean some other form if Julian date, such as the ordinal number of the day in the century, or since some given "day zero", then techniques are similar but...

Just out of curiosity, does the IPC stage manifest the same problems?

There's a subroutine called !MAKE.PATHNAME in DataStage BASIC that will construct a fully qualified pathname. If you leave the first argument as a zero-length string, it will return the fully-qualified pathname of its second argument. (And if you leave both empty, it returns the fully-qualified path...

Welcome aboard! :D In the Director client, log view (the "open book" tool), log entries are - by default - sorted in date/time order, so that the most recent are at the end. You can change the sorting order by double-clicking the the grid header. At the right hand side is a hidden column (that you c...

I recently completed a "best practices audit" for a client. One of the not-so-best practices I uncovered was use of the Saved category of Table Definitions. Developers (properly) use this as temporary storage for example to migrate column definitions from the input side of an Aggregator stage to the...

"Go" in French maps to "GB" in English.

Unfortunately I can't help with the actual problem.

This - or something quite like it - can also happen when you construct queries in something like Microsoft Word when it has the "replace straight quotes with smart quotes" enabled.

The "driver" is the uv command. For example, assuming that the DataStage bin directory is in PATH and that your current working directory is the project directory: uv "SELECT COUNT(*) FROM DS_JOBS WHERE NAME NOT LIKE '\\%';" Metadata for the DataStage repository tables is not in th...

Is anyone using SSA-NAME3 with DataStage?

If so, how do you manage the interface between the two pieces of software; that is, how do you call the SSA-NAME3 functionality from DataStage? Do you consider that the performance penalty is within acceptable bounds?

DSJ.ME is not a job name, it's a job handle. Deep within DSLogWarn, therefore, an "invalid data type" error has been generated, but not handled. Hence "unhandled failure". What you should have written was $IFNDEF JOBCONTROL.H $INCLUDE DSINCLUDE JOBCONTROL.H $ENDIF JobName = DSGetJobInfo(Arg1, DS...

For various reasons to do with the inner workings of DataStage, JOBNO is not a numeric column. Therefore, it must be quoted in the WHERE clause.

Kind of funny, but I've been doing this since 1998 and I've never seen that message. You only ever get this message if a user ID logs in and is allocated a "UniVerse" user number that was formerly owned by a recently logged out different user ID. So you would never see it, for example, where everyo...

It means exactly what it says, it's having a problem invoking DSRunJob when the job name is UKWH_ARRG_FIN_INFO_IntInup2job.Load_InterestOutstandingLess2Months Check that the job is in a runnable stage, compiled, all that kind of thing. It appears to be a multi-instance job (because of the "."). Is i...

Best practice is to have automatic log purging enabled, and to perform manual log purging when a large number of events is logged. Automatic log purging is triggered when a job completes successfully. It is not triggered if the job fails to complete successfully. You may need to propagate automatic ...

You can run a subsequent pair of jobs to FTP the control and data files to the other server. Or simply run the FTP from a BAT file, perhaps from an after-stage or after-job subroutine. You can use a "remote shell" or "remote execution" or "remote login" script (BAT file) to execute the bulk loader. ...