DSXchange

That's a kinder approach. The suggestions given earlier are appropriate - either a Routine activity in the controlling sequence to get the link row count on the reject-handling link followed by a Notification activity to send the email, or an after-job subroutine to do the same. The mailbomb techniq...

Actually you can do it while rejecting records, but do you really want to send a separate email for each record rejected? The recipient(s) will quickly begin to hate you if you do. Therefore I'll not be explaining the technique.

And, having done that, use DateToString() with the format you require, namely "%mm/%dd/%yyyy" - and make sure that the target column data type is a string of some kind, for example Char(10).

So the change was in the volume of data.

If there is an entry for the routine in DS_ROUTINES the source code is stored in field #15 of that record. The reason I wanted to see the VOC result was to confirm that it was a user-written routine (with "DSU." prefix) rather than some other kind. Because other kinds are not stored in DS_...

What Craig said.

Yes it can, and it's straightforward. The manual for ISM describes the process of configuring. Once configured you get an extra sub-menu (called Team) in Information Server Manager that you can use for check-in, check-out, etc.

Open the DataStage Administrator client. On the Scheduling tab you can specify the user name and password for the scheduling user, and validate that this user can be authenticated.

Note that this functionality is only available where the DataStage Engine is on a Windows platform.

Welcome aboard.

When you're providing the value to a parameter in a Job activity (or to an argument in a Routine activity) you can use any DataStage BASIC expression. Current date can be produced by (Change the format string to suit your needs.)

I don't know that you can. What happens if you try?

SLEEP takes either seconds or a time in HH:MM format. So SLEEP 13:45 will sleep until 1:45pm. If it is already after that time, no sleep will occur.

Whatever your Engine-credentialled user is should be able to run.

Easiest is to unzip; you can make this a Filter command in the Sequential File stage and read the output of the unzip utility.

Another possibility, if you have a Java class that can read the zip file (which assumes a known format) is to use the Java pack in DataStage to read the file.

Try leaving out the street name; resolve just the city, postal code and state/province/county.

I'm not sure what that statement from IBM Is about. Can you please cite a source? Meanwhile, you do not have to clear the RT_STATUS file (that would be unwise); you only need to delete the entries corresponding to the invocation ID(s) that you want to purge.