DSXchange

Well done on completing the diagnosis! :D

Now please mark the thread as resolved.

It can be done, but not directly. Routines may be called from jobs (as before/after subroutines or as job control routines) or from Transformer stages (as transform functions) or from any active stage (as before/after subroutines). You would need to construct a complex query (or a UNION) on DS_JOBS ...

Do the individual tests in separate stage variables. Working in internal format, the "+6 days" test automatically handles leap year. These date arithmetic routines may prove useful. Edit I've just noticed that you are running version 5.x. The export file will probably not import, but the code is leg...

OK, you can use Field() to get the date portion from a timestamp and Iconv() to convert that to an internal format date. All you need for the second argument of Iconv() is "DMDY" - it's pretty clever about delimiters and number of digits in the year. What you now need is a time dimension (hashed fil...

Depends how accurately you need it. You could use DateFromDaysSince() if you're happy to say that 15 years is 5479 days. Otherwise you need to break the date into its components, using YearFromDate(), MonthFromDate() and DayFromDate(), subtract 15 from the year component, re-assemble the date, subtr...

As noted, Convert is one character to one character. Search the forum for a parallel equivalent of EReplace() function which can replace strings with other strings. Then you should be able to use

Not without more information.
1. What is the format of ReportingPeriodEnd?
2. What are you trying to achieve?
3. Have you investigated the MONTH.LAST Transform, rather than trying to re-invent the wheel?

Upgrade to version 8 and use a Parameter Set.

You may be able to interface using an External Filter (or External Source or External Target) stage but, of course, what happens "inside" this stage actually happens outside of DataStage.

No, no, no. The Answer is 42.

"Better" in what way? Probably no significant difference.

The Filter stage does not require sorted input - without knowing precisely which post you are referring to I can not comment on that "solution".

My guess is that the DS_JOBS record was created but not populated. A job type of 0 (and empty is treated as 0) is a server job. If it won't lose you any information try deleting the incorrectly server job and doing the Save As operation afresh.

Given that this is a server job, the ideal solution would be routine containing a Locate statement.

The answer for Filter vs Transformer (no sort in either case) will depend on the version of DataStage you are running. In 7.5.1 and later - all else being equal, that is you are not having the Transformer do any other processing - the difference will be negligible.

I don't believe we have a member called Plz.