Aborted jobs

Post by **admin** » Wed Apr 25, 2001 2:51 pm

Im setting up our DataStage jobs to message us when there
are errors. The problem with aborted jobs is that they just stop, and cant run a routine that will send us an error message. Is there any way to run some routine when a job aborts?

Thanks,

Kenny

Post by **admin** » Wed Apr 25, 2001 6:00 pm

Kenny,

Perhaps the best approach is to create a Batch (Job Control) which runs the job and based upon its completion code can send a message. This way it is one removed from the real process. In the next version of DataStage you will be able to run multiple instances of the same job/batch using job parameters. This way you would only need to create a single Batch process. Today you would need to create one for each respective job. The Batch would
be what you schedule (not the actual job). Hope this helps..

Regards,

-Allen Spayth

----- Original Message -----
From: "Salstrom, Kenneth"
To: "DataStage List (E-mail)"
Sent: Wednesday, April 25, 2001 7:51 AM
Subject: Aborted jobs

Im setting up our DataStage jobs to message us when there
are errors. The problem with aborted jobs is that they just stop, and cant run a routine that will send us an error message. Is there any way to run some routine when a job aborts?

Thanks,

Kenny

Post by **admin** » Wed Apr 25, 2001 8:52 pm

The approach we use is to have the controlling job, which started the job in question, detect the abort and send the email.

-----Original Message-----
From: Salstrom, Kenneth [SMTP:Kenneth.Salstrom@msnyuhealth.org]
Sent: Thursday, April 26, 2001 12:51 AM
To: DataStage List (E-mail)
Subject: Aborted jobs

Im setting up our DataStage jobs to message us when there
are errors. The problem with aborted jobs is that they just stop, and cant run a routine that will send us an error message. Is there any way to run some routine when a job aborts?

Thanks,

Kenny

*************************************************************************
This e-mail and any files transmitted with it may be confidential and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in
error, please notify the sender by return e-mail, and delete this e-mail from your in-box. Do not copy it to anybody else

*************************************************************************

Post by **admin** » Thu Apr 26, 2001 12:29 am

Its something you can manage in job control code, as David has already mentioned. In job control code you can also detect whether the job is runnable in the first place, and reset it if it is not (and thats an appropriate thing to do). These techniques - and many others - are taught in the class "Programming with DataStage BASIC".

-----Original Message-----
From: Salstrom, Kenneth [mailto:Kenneth.Salstrom@msnyuhealth.org]
Sent: Wednesday, 25 April 2001 22:51
To: DataStage List (E-mail)
Subject: Aborted jobs

Im setting up our DataStage jobs to message us when there
are errors. The problem with aborted jobs is that they just stop, and cant run a routine that will send us an error message. Is there any way to run some routine when a job aborts?

Thanks,

Kenny

Post by **admin** » Thu Apr 26, 2001 3:55 am

-----Original Message-----
From: Ray Wurlod [mailto:ray.wurlod@informix.com]
Sent: Wednesday, April 25, 2001 7:30 PM
To: informix-datastage@oliver.com
Cc: pavan.marpaka@ascentialsoftware.com
Subject: AD: Aborted jobs

Its something you can manage in job control code, as David has already mentioned. In job control code you can also detect whether the job is runnable in the first place, and reset it if it is not (and thats an appropriate thing to do). These techniques - and many others - are taught in the class "Programming with DataStage BASIC".

-----Original Message-----
From: Salstrom, Kenneth [mailto:Kenneth.Salstrom@msnyuhealth.org]
Sent: Wednesday, 25 April 2001 22:51
To: DataStage List (E-mail)
Subject: Aborted jobs

Im setting up our DataStage jobs to message us when there
are errors. The problem with aborted jobs is that they just stop, and cant run a routine that will send us an error message. Is there any way to run some routine when a job aborts?

Thanks,

Kenny