DSXchange

You have to check the INTERIM status as suggested, otherwise all it's ever going to tell you after job is that the job is RUNNING.

Examine the dsapi.h header file in $DSHOME/include for a complete list of codes of that nature.

After Job you need to check the JOBINTERIMSTATUS first and only execute the rest of the code if it says the job is in the process of aborting. Or trigger a Routine Activity with this code in a Sequence after the job aborts.

All you need to check for null is one of the Key columns. That or use the NOTFOUND link variable if this is a hashed file lookup.

Server Shared Container.

Search here for examples of using the DSGetLinkInfo() function with the (off the top of my head) DSJ.LINKROWCOUNT InfoType. Build a generic routine that takes three arguments - job name, stage name and link name - then attach to the job, interrogate the link, set the return value to that count and t...

Ah... a much more thorough reply. Thank goodness for new fingers.

It's an all too common mistake. You need to realize there is no "output format" for a Date field... a date is a date is a date and it is stored in an internal/binary format. Only people readable external representations like in your string need a "format".

Just because you have the "Enterprise Edition" doesn't mean Server jobs work or run any differently.

OK... so what are you going to try next?

rsunny wrote:Find the number of rows that are going into the reject link and use DSSETUSERSTATUS of the row count and keep the job in sequence and trigger to send an email with the user status if it is greater than zero.

That's certainly another way - if we're talking about a Server job here.

If nothing of that is working, u can also do this StringToDate(ColName[1,4]:"-":ColName[5,2]:"-":ColName[7,2]) Not sure why U (one of our posters) would do this and a couple of issue here as well. One is that you are missing the format mask that the function needs. The other is ...

mac4rfree85 wrote:Regarding the dashes/slashes, do we really need to have it??? Datastage will not handle it from its side?

You need to remove them. The mask needs to match what your incoming source field looks like and yours does not have any such delimiter.

If it is a "20" why did you use "13" in the Convert? And that "box" is a 20 in decimal? Hex? For the former use CHAR(20), the latter CHAR(32).

Odd. Should it have been sometime in 2009? What does the job show for those values in the Director? If you rerun the dsjob command, do you get a new (i.e. current) value for the end time? Does it work properly for other jobs? :? I have absolutely no idea what might be going on (just trying to gather...