View previous topic :: View next topic
|
Author |
Message |
Hooman24
New User
Joined: 20 Sep 2012 Posts: 36 Location: US
|
|
|
|
hi,
im trying to detect errors ( such as jcli ) that happend in application/operation ( in current plan ) and reporting them to the specific email ( by jobs sysout ) or highlight them to the console.
this work must be done immediatly after error,
im familiar with WTO, ETT, OCL and same solution for communication and detecting error but im intresting in general solution.
by adding occurence immediatly after error in any application and sending email, im trying to solve this problem. but i cant catching job id ( from value table ) to get sysout from job.
i wish you can help me on this problem.
thanks |
|
Back to top |
|
|
PeterHolland
Global Moderator
Joined: 27 Oct 2009 Posts: 2481 Location: Netherlands, Amstelveen
|
|
|
|
As far as I know, dependant operations will not be triggered if the predecessor operation(s) end(s) in error. |
|
Back to top |
|
|
David Robinson
Active User
Joined: 21 Dec 2011 Posts: 199 Location: UK
|
|
|
|
The usual method is to trap the EQQE036I message and send that to the Operator's console. |
|
Back to top |
|
|
PeterHolland
Global Moderator
Joined: 27 Oct 2009 Posts: 2481 Location: Netherlands, Amstelveen
|
|
|
|
The normal method is for TWS/OPC operators to look at the ended-in error-list and perform their rerun/alert procedures.
OPC/TWS was designed to lift the burden of failing jobs from the operators to scheduling people, so they could focus on really important matters like crashing CICS, IMS and other online systems.
The TS wants to run an occurrence after a failed occurrence and that will not happen.
But David, what you said is ok. But it is not the usual way. With MPF and System Automation one could probably do what the TS wishes. |
|
Back to top |
|
|
|