Like Richard, we run VM:Tape.  Here, it is NOT happy if it tries to start
when RMSMASTR isn't ready.  (Maybe we can chat Richard!)    Basically what
we do is to have a sleep in autolog2 to start up RMSMASTR, wait a few
minutes and then do VMTAPE.   It's not precise, but it works for us. :-)







|------------>
| From:      |
|------------>
  
>--------------------------------------------------------------------------------------------------------------------------------------------------|
  |"Schuh, Richard" <rsc...@visa.com>                                           
                                                                     |
  
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To:        |
|------------>
  
>--------------------------------------------------------------------------------------------------------------------------------------------------|
  |IBMVM@LISTSERV.UARK.EDU                                                      
                                                                     |
  
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date:      |
|------------>
  
>--------------------------------------------------------------------------------------------------------------------------------------------------|
  |07/28/2010 01:24 PM                                                          
                                                                     |
  
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Subject:   |
|------------>
  
>--------------------------------------------------------------------------------------------------------------------------------------------------|
  |Re: RMSMASTR : ready or not                                                  
                                                                     |
  
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Sent by:   |
|------------>
  
>--------------------------------------------------------------------------------------------------------------------------------------------------|
  |The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU>                      
                                                                     |
  
>--------------------------------------------------------------------------------------------------------------------------------------------------|





You could always loop while trying to mount a tape. When it is mounted,
RMSMASTR is ready.:-)

In reality, the tape manager should be able to wait to open the interface
until RMSMASTR is ready. Here, we have both a VTS, controlled by RMSMASTR,
and 2 SL3000s, controlled by STKACS, and some tapes that are outside the
silos. VMTAPE manages to initialize before RMSMASTR is ready and is quite
happy adding the VTS to its stable when it is ready.

If you really need to insure that RMSMASTR is running, you need an Observer
or a Secuser of it that looks for the message FSMSMS3203I RMSMASTR is
running.


Regards,
Richard Schuh



> -----Original Message-----
> From: The IBM z/VM Operating System
> [mailto:ib...@listserv.uark.edu] On Behalf Of Alain Benveniste
> Sent: Wednesday, July 28, 2010 11:40 AM
> To: IBMVM@LISTSERV.UARK.EDU
> Subject: RMSMASTR : ready or not
>
> Looking back to my autolog2 profile, I found not much pretty
> to xautolog rmsmastr and sleep 30 sec to xautolog products
> they require tape mounts.
> Rather than that I thought to trap a message that says in
> substance "rmsmastr is ready, the tapes drives are there...".
> Or "rmsmastr did not found a drive to initialize library ABC123...".
>
> What could I test to be sure of its good initialization ?
>
>
> Alain
>
>

Reply via email to