DSXchange

Your UserVariables stage is unnecessary in this case, as you can simply reference the $UserStatus returned by the first job in the parameter of the second job. Use the picker / parameter helper if you are unsure of the syntax. However, I have no idea if that answers your question or not... What do y...

If you looked at other posts with this error, does that mean you are handling the dynamic array that the Execute Command stage returns properly as they note? Meaning, you are removing the @FM at the end of the parameter value?

On the subject of sleeping, unless your job runs very very quickly it can't afford to sleep for the full 60 minutes, if you do you will slowly start creeping past your straight-up hour start time. When I had to do this in the past, I recorded the end time of the looped job and then computed how many...

The "DataStage scheduler" is simply an interlude to cron. There's nothing stopping you from doing an "Add to schedule" for every hour in that range except that it would be rather tedious. Don't recall if you can specify "Every weekday" there or not, worst case you would...

You should be using your internal SMTP mail server, whatever is accessable from the DataStage server.

Your DBA can.

If your conversion is simply the removal of the delimiters then what anbu posted should work fine for you. If it doesn't then let us know what your target for this "date" is...

You have to go back to the vendor for that answer, I'm afraid.

Typically that's because it is a unique index and you've loaded duplicate values into it. Ask your DBA for help if you are unsure what is going on but the reason should be in the .log file.

Add four new columns to the transformer, manually populate them with your heading names ("JAN_Sales", etc) and pivot them along with their actual, matched data.

Split from this resolved topic so Phil could have this one all to himself.

kris007 wrote:In version 7.x, we can demote warning messages to Informational messages. Not sure if there is an option in version 8.x to add rules to the message handler in the director to promote the warning messages as a Fatal error message.

Not for Server jobs.

You add them yourself, manually.

<click>

Locked

This has been asked and answered several times here... it will work just fine.