IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

MQ triggered job fails when database is stopped


IBM Mainframe Forums -> JCL & VSAM
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
t5590ag

Active User


Joined: 21 May 2009
Posts: 139
Location: United States

PostPosted: Tue May 08, 2012 12:39 am
Reply with quote

All, i am facing a problem where my job(JCL) is triggered by MQ input data(over which I have no control).
Process runs as follows-

1- Designated MQ triggered job starts when data comes to MQ.
2- STEP1 reads data from MQ, copies it to a GSAM file.
3- STEP2 runs a BMP which is supposed to process the data.

BMP goes down as at that particular time IMS databases are stopped for maintenance and all MQ triggered jobs go down if they try to process their corresponding MQs as they go to the same IMS database which is undergoing a REORG.

Alternatives already ruled out to avoid these jobs going down-
1- Control/Reschedule triggering of jobs which put data into MQ.
2- Change schedule of Database maintenance jobs to some other hour- still cannot be sure when MQ jobs will run, they can come to queue anytime, so not a 100% resolution.

Is there anyway in JCL, any utility which can check if an IMS database is stopped or not, if down then hold the rest of the steps(maybe until it starts), something like that.
Also if i can check completion of a particular job(which starts back the databases) will help.

All ideas are welcome where I do not have to reschedule anything.
Back to top
View user's profile Send private message
Nic Clouston

Global Moderator


Joined: 10 May 2007
Posts: 2455
Location: Hampshire, UK

PostPosted: Tue May 08, 2012 12:44 am
Reply with quote

Option 3 - change the scheduling of your job to run after maintenance
Back to top
View user's profile Send private message
dick scherrer

Moderator Emeritus


Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix

PostPosted: Tue May 08, 2012 12:47 am
Reply with quote

Hello,

Quote:
All ideas are welcome where I do not have to reschedule anything.
Kinda self-defeating. . .

Why does someone believe a scheduling solution is out of the question?

If the current method is not changed, i suspect there will be an ongoing unsupportable mess.
Back to top
View user's profile Send private message
t5590ag

Active User


Joined: 21 May 2009
Posts: 139
Location: United States

PostPosted: Tue May 08, 2012 12:53 am
Reply with quote

Even if I change the schedule I cannot make sure that the timeframe I am selecting for maintenance is safe, purpose of MQ triggered jobs is to process data as soon as it comes.
They can run anytime and overlap with maintenance jobs I understand.

that is the reason for ruling out a schedule change.
Back to top
View user's profile Send private message
dick scherrer

Moderator Emeritus


Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix

PostPosted: Tue May 08, 2012 1:03 am
Reply with quote

Hello,

I suspect that bringing IMS down is scheduled?

You might consider adding a job/step to shut down that queue immediately before bringing down IMS. When IMS comes back up, another process could re-activate the queue.

Hopefully, you have someone with mq experience that can help setting this up along with the scheduling group.

Quote:
They can run anytime and overlap with maintenance jobs I understand.
Messages might continue to arrive in the queue, but should not start jobs until IMS has been recycled.
Back to top
View user's profile Send private message
t5590ag

Active User


Joined: 21 May 2009
Posts: 139
Location: United States

PostPosted: Tue May 08, 2012 1:05 am
Reply with quote

thanks for the idea Dick ! i will check this possibility right away.
Back to top
View user's profile Send private message
dick scherrer

Moderator Emeritus


Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix

PostPosted: Tue May 08, 2012 1:07 am
Reply with quote

You're welcome - good luck icon_smile.gif

Please let us know when it is working or if there are any questions as you proceed.

d
Back to top
View user's profile Send private message
t5590ag

Active User


Joined: 21 May 2009
Posts: 139
Location: United States

PostPosted: Tue May 08, 2012 1:22 am
Reply with quote

Is it right that stopping the MQ will not affect data incoming to MQ, it will keep accumulating but would not trigger the jobs ?
Back to top
View user's profile Send private message
t5590ag

Active User


Joined: 21 May 2009
Posts: 139
Location: United States

PostPosted: Tue May 08, 2012 1:26 am
Reply with quote

Just making sure that under normal condition there would be no data losses, until MQ overflows by any chance in worst case(also i have not seen any loss of data in this case so far).
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> JCL & VSAM

 


Similar Topics
Topic Forum Replies
No new posts What database does Jobtrac use CA Products 4
No new posts MQ response when MQGET of a stopped q... Java & MQSeries 2
No new posts Capturing COBOL job and program names... All Other Mainframe Topics 2
No new posts Debugging not getting triggered throu... CICS 3
No new posts dsnrexx fails without error message CLIST & REXX 9
Search our Forums:

Back to Top