DSXchange

You actually wear the cost twice - when connecting to the site, then after logging in.

Please explain how you called this routine, and from where in your job or routine design. You can examine this routine's code (it's provided as part of the SDK; it's name is UtilityMessageToLog - the all-upper case version is its "catalog" name) and you will note therein that it sets a return value ...

Put it in a server Routine and use the Test button there.

Then all you need is a before-job subroutine executing ExecSH with your script's path and command line arguments (all can be job parameter references) in the Input Values field.

A Wrapped stage would execute the script for every row processed by the job.

This is where you have to begin being a real detective. Maybe a good first step is to use a before/after subroutine to report who you are, your environment, and so on. If you have MKS Toolkit you can use UNIX commands like id and env to report these factors. Look for differences. Similarly look for ...

IBM Certified Solutions Developer Websphere IM DataStage Enterprise Edition Test Purpose This test will certify that the successful candidate has the skills and knowledge necessary to professionally design and develop an efficient and scalable DataStage solution to a complex enterprise level busine...

How about losing the large pictures from the home page - move them to an optionally selected side page? Over the past week I've been using various connection modes, including hotel dialup lines charged by the nanosecond. The time to load the home page (about which there's no choice) was quite costly...

You avoided the question. Do you want to invoke this shell script once, or once for every row processed in a job? The answer to your original question depends on your answer to this one.

You need to define "duplicate". This answer uses "has same key column(s)" as the definition. The UNIX command is sort -u (plus any other command line options needed). Most server job developers use a hashed file to remove duplicates, relying on the fact that any write to a hashed file with the same ...

Please test your SELECT statement outside of DataStage, to determine whether that is the culprit.

LHS and RHS are metasyntactic variables - placeholders if you prefer. The pseudo-expression LHS=RHS serves only to remind you that whatever expression you use here must be resolvable in a Boolean context - that is, generate a true/false value.

The fact that no-one replied suggests that this is a difficult problem to which no-one could contribute anything.

If you have solved it, please post the solution, so that others can be more productive.

If you have abandoned it, please post that fact also.

This is a place where we share.

DSJS.JOBSTATUS does not exist. The -1 you're getting is an error code meaning "bad handle", that is you have not attached the job to the current process. DSJ.JOBSTATUS is a DataStage constant, it is one of the possible arguments to DSGetJobInfo(). You can not use this in a job design to achieve your...

Welcome aboard. :D The size can be as large as the operating system will permit in the case of a Sequential File, and very very large (if needed) for a File Set. A File Set is spread over the processing nodes defined in the configuration file and consists of one or more logical files (each no larger...

Do you want to invoke this script once, or once for every row processed?