Ron, that's fine for DR tests, but we need to be able to come up automagically if we're all gone in a real DR, so our main 'goal' is to run as if it's a real DR and get the whole way up with no intervention. So I'll have autolog come up, it will fail, and in a test I'll force the linuxes and tcpip, then start autolog with a parm. That way I have intervention on a test but not in a real dr. Mary Anne
On 10/3/07, Ron Schmiedge <[EMAIL PROTECTED]> wrote: > > We have the PROFILE EXEC for AUTOLOG1 coded to stop and ask the > operator whether to continue normal startup or not every time we IPL. > In addition, the operator can use the SM reply to tell AUTOLOG1 to > carry on but that we are in a disaster recovery. > Like Kris, AUTOLOG1 does different things based on the operator's > instructions - and it's not an operator doing this at a DR, its one of > our tech support people, so there is a reasonable chance they know > what to do :-) > > Ron > > > On 10/3/07, Mary Anne Matyaz <[EMAIL PROTECTED]> wrote: > > Thanks All. Here's what I've come up with. I'm going to allow everything > to > > come up on D/R without intervention if it is a real disaster. If I am > > testing, I will allow it all to come up, and > > IP won't work, so I'll bring TCPIP and the linuxes down, and XAUTOLOG > > AUTOLOG2 Storage 6M. This way, if I'm in a test, programmatically I can > q v > > storage from within autolog2 and make decisions based on that, one of > which > > will be, if it's 6M: > > define timezone DR1 west 00.00.01 > > so that other apps can check for the existence of that timezone, and if > they > > find it, we are in DR test. > > > > MA > > > > >
