What is allowed ?

[Ian Miller.]

Any change nomatter how trivial involves risk - its all about balancing risk and explaining this to the users, management, beancounters etc.

RE the previous reply by Jan - you've mentioned this before. Either you hope inertia of large organisations means the downgrade to a non-VMS solution does not happen or somebody high up wakes up to the risk of moving away from VMS. In these current troubled times avoidance of risk should be a good thing I would have thought.

[Jan van den Ende]

Ian:

In these current troubled times avoidance of risk should be a good thing I would have thought.


Yes, YOU would have thought!! (as would I)

Is there some way that you could don some (maybe only apparent, but absolutely convincing) authority on the subject, and then do a, publicized as VERY important, lecture to the right people? At that level, price will be no issue at all, but the convincing authority.....

just wishful thinking...


Cheers!


Have one on me.

Jan

[Ian Miller.]

Jan, I don't know who you need - someone important in a suit I suppose - parhaps you could try Mark Gorham as he does talking to top executives.

[Wim Van den Wyngaert]

The reason I asked this is because we had to plan a local scsi controller replacement. This meant 1 node of the GS160 down.

Intervention started. Power off not possible. 2nd qbb must be stopped too. Done that. Both clusters now in DRP (with writemap to allow mini copy afterwards).
Now not both qbbs are visible. 1 part must be replaced to restart the node. Part ordered and delivered within an hour.
That's where I'm now. Normally another hour and intervention is finished. Took 4 hours instead of 30 minutes and we lost all drp capability during these hours (not that important).

Think about what should have happened when I planned this during lunch hours ...

Wim

[Jan van den Ende]

Yeahhhh

It's been noted before:

Murphy always wins in the end.

And in your case, having a non-service window: I fully understand that you are now VERY glad you decided to invest part of your weekend, just BECAUSE it took more than expected!

I am facing somthing similar:

The electrical wiring in the building of one of our computer rooms is getting updated (and upgraded: with all those new Intel systems we have to keep adding, we are using more and more power, and that needs to be aircoed away again => still more power).
This will be done segment-by-segment, and the disconnected segments in the meantime will be fed by a row of big Diesel generators (ugly stinking stuff in themselves!!).
Monday evening there will be switchover.
And although everone expects smooth going, we WILL be on-site!
Rationale: if everything goes as expected, we get a thank-you for the extra effort, (and get paid overtime), but... SHOULD something somehow go not completely smouth, then, if we am NOT there, THEN we will have some explaining to do!!

Our job is more or less like boy-scouting:

"Be Prepaired"

Cheers.


Have one on me.


jpe

[Wim Van den Wyngaert]

Intervention finished exactly 4 hours after it started. Luckally our shutdown asks the other side (clusternode) to keep a bitmap and the shadow copy was done very fast.

The part arrived with a too high firmware version. So : downgrade. All the rest went smoothly. Had to do some explaining to the girlfriend that had to delay a family visit ...

Wim