Re: Server Hung and BRMS Control Group

[Jim Oberholtzer <midrangel@xxxxxxxxxx>]

Sneha,

You can, but I would not.  Have this program as part of the control 
group so if you decide to not run the back up, this program does not 
cause you grief you don't expect.  Since the back up control group and 
this program are linked, put your four minute delay in the program 
itself and keep it an exit.  This sets up an administration land mine 
that you will eventually step on, event with the advanced job scheduler 
(or Robot) setting dependency schedules.

One other point to keep in mind.  If an *EXIT program fails for some 
reason, the control group does not have visibility to that, assumes it 
completed normally, and continues on its merry way.  Again, another land 
mine to step on.

Jim Oberholtzer
CEO/Chief Technical Architect
Agile Technology Architects, LLC


On 4/19/2010 8:01 AM, Sneha Verma wrote:
> *This message was transferred with a trial version of CommuniGate(r) Pro*
> Hi Rob,
>   
> Can I complie a CL containing the below mentioned commands:
>   
> ENDTCPSVR   
> MONMSG MSGID(CPF0000)
> DLYJOB DLY(30)
>
> ENDHOSTSVR   
> MONMSG MSGID(CPF0000)
> DLYJOB DLY(30)
>
> ENDTCP       
> MONMSG MSGID(CPF0000)
> DLYJOB DLY(30)
>
> And then schedule this compiled CL to run 4 minutes before the start of Daily Backup .I actually do not want to disturb the setting of the control group so want to schedule this CL 4 minutes before the backup.
>   
> Wil it affect the backup in any way?Pls advice asap.
>   
> Regards
> Sneha
>   
>
> --- On Mon, 19/4/10, rob@xxxxxxxxx<rob@xxxxxxxxx>  wrote:
>
>
> From: rob@xxxxxxxxx<rob@xxxxxxxxx>
> Subject: Re: Server Hung and BRMS Control Group
> To: "Midrange Systems Technical Discussion"<midrange-l@xxxxxxxxxxxx>
> Date: Monday, 19 April, 2010, 12:39 PM
>
>
> Which one, 10 or 20, does the ENDSBS *ALL?  Because you want to end TCP/IP
> before running that or unacceptable results may occur, even after the next
> system start!  I have seen this with 6.1
> ENDSBS *ALL ...
> "System ended to restricted condition"
> And, even after that, TCP/IP messages appearing in QSYSOPR.
> IBM changed TCP/IP that you really want to end it before doing the ENDSBS.
> I found out the hard way when some stuff didn't work right.
>
> See also:
> http://www-01.ibm.com/support/docview.wss?rs=0&dc=DB550&q1=endtcp+endsbs&uid=nas22ecc6868e655c8788625763a003c7219&loc=en_US&cs=UTF-8&lang=all
> http://www-01.ibm.com/support/docview.wss?rs=0&dc=DB550&q1=endtcp+endsbs&uid=nas2a68debf42e0d564a862575a2003c97a4&loc=en_US&cs=UTF-8&lang=all
>
> I'd post a link in the midrange-l archives but the adserver has rendered
> them useless this morning.  I've notified David.
>
>
> Rob Berendt
>