|
View previous topic :: View next topic
|
| Author |
Message |
siebertr
New User
Joined: 25 Aug 2010
Posts: 7
Location: Brazil, Sao Paulo, Hortolandia
|
|
|
|
Hi,
i am trying to find one information about IMS BMP jobs. Currently im the system that i work with there is an automation process that issue the command:
/STO REG XX,ABDUMP
where XX is the region number of a specific BMP that is captured via REXX automation process by job name(this is done to cancel a 24x7 job). I'd like to know if it is possible to make a IMS BMP stop running with other command to make it complete with success(no cancel message, which generates an abend). |
|
| Back to top |
|
 |
mlp
New User
Joined: 23 Sep 2005
Posts: 91
|
|
|
|
Why there is a requirement to stop the BMP?
If you are making use of program DFSRRC00 to execute your batch program then I dont think there is need to use IMS command to stop the BMP. I think intention over here is to complete the process gracefully. But by issuing STOP (/STO) you are in fact forcibly closing the process. I suggest to handle the completion of the process in the source code itself and make it time dependent or on demand. |
|
| Back to top |
|
|
siebertr
New User
Joined: 25 Aug 2010
Posts: 7
Location: Brazil, Sao Paulo, Hortolandia
|
|
|
|
The BMP is stopped before the shutdown-IPL process. Every weekend we do a procedure that brings IMS down, run backups, shutdown the system and the IPL the system.
So, the BMP is always cancelled due to this procedure. I am trying to find a way to stop the BMP without having to cancel it to avoid a failure message. |
|
| Back to top |
|
|
mlp
New User
Joined: 23 Sep 2005
Posts: 91
|
|
|
|
Is that REXX procedure scheduled one which brings down the region? If that so, then you must be knowing the specific time on which it runs. Now considering above is true there can be solutions as mentioned below.
1) Set a dependency between the REXX and your BMP via your scheduler if that is possible..so that REXX procedure do no run till BMP processing is completed
2) Run the BMP after REXX procedure is done. I mean change the scheduled time
3) If above is not possible then you can gracefully close your processing of BMP programmtically, on a time just before the REXX procedure runs.
Hope this will help.... |
|
| Back to top |
|
|
siebertr
New User
Joined: 25 Aug 2010
Posts: 7
Location: Brazil, Sao Paulo, Hortolandia
|
|
|
|
| The problem is that this BMP is a process that runs 24x7. It will never complete. I was wondering if there is any way to set it to complete in a specific time. I can manage the REXX code that issue the /STO REG XX,ABDUMP command to run at any time i want, but the problem is that i don't see a possibility of setting the execution of this BMP to complete in a determined time. |
|
| Back to top |
|
|
don.leahy
Active Member
Joined: 06 Jul 2010
Posts: 765
Location: Whitby, ON, Canada
|
|
|
|
| If changing the BMP is an option, you can use some sort of control database to signal the BMP to stop running. IOW, you would create a separate process to update a flag in the control database. When the BMP sees this flag, it could gracefully terminate itself. |
|
| Back to top |
|
|
PeterHolland
Global Moderator
Joined: 27 Oct 2009
Posts: 2481
Location: Netherlands, Amstelveen
|
|
|
|
| Quote: |
an automation process that issue the command:
/STO REG XX,ABDUMP
|
Automation process : is that a SA/390 automation process ?
What kind of BMP are we talking about :
Message Driven BMPs (also called transaction oriented), which read and
process messages off the IMS message queue.
Non-message BMPs (batch oriented), which do not process IMS messages.
Transaction-oriented BMPs are not scheduled by IMS, so i guess bringing down IMS will have no influence on such a BMP.
Maybe the next link has some useable info :
publib.boulder.ibm.com/infocenter/dzichelp/v2r2/index.jsp?topic=/com.ibm.ims11.doc.apg/ims_bmpprocessingtransoriented.htm |
|
| Back to top |
|
|
mlp
New User
Joined: 23 Sep 2005
Posts: 91
|
|
|
|
Though requirement of your BMP is to run 24x7, it is actually not running 24x7 due to that REXX utlity. So anyways right now the process is dis-continued for a short period of time. Only problem with that is your BMP result into an abend. That you dont want to happen. On the other side you said you can manage the time of run of the REXX code, but problem is that you are still interupting the BMP as its running 24x7. So if you want to keep intact the 24x7 running nature of BMP then you have to abandon the REXX utility.
On the contrary, if you want the REXX utlity to run then you have sacrifice the 24x7 nature of the job for few minutes within a day. If that is accepatble then as don.leahy said you have devise a mechanism in such a way that your BMP comes to know that its time for REXX utility to run and better shut down to avoid abend. NAd after REXX utlity has run and resion is again started schedule the BMP again |
|
| Back to top |
|
|
|
|
