Re: Testing SFM policy

: Testing SFM policy > Testing was semi-successful. On one hand, QUIESCE stopped the system. > Missing heartbeat was detected by SFM and system was partitioned out. > However, I was also trying to test SAD and AutoIPL. > Nothing happened in that arena, so--as I do when all else fail

Re: Testing SFM policy

> Testing was semi-successful. On one hand, QUIESCE stopped the > system. Missing heartbeat was detected by SFM and system was > partitioned out. However, I was also trying to test SAD and AutoIPL. > Nothing happened in that arena, so--as I do when all else fails--I > RTFM. Found this: > >

Re: Testing SFM policy

> You can write a simple assembler program to load a WAIT PSW that is > disabled for interrupts or you can modify the RESTART NEW PSW in the > PSW with the wait bit on and disabled for interrupts. > > If you use the RESTART NEW PSW, then a PSW RESTART should result in > your system going into a

Re: Testing SFM policy

: Testing SFM policy You can write a simple assembler program to load a WAIT PSW that is disabled for interrupts or you can modify the RESTART NEW PSW in the PSW with the wait bit on and disabled for interrupts. If you use the RESTART NEW PSW, then a PSW RESTART should result in your system

Re: Testing SFM policy

. Both should kill your system. Adam -From: "Jesse 1 Robinson" To: Cc: Sent: Tue, 7 Jun 2016 19:19:08 + Subject: Re: Testing SFM policy Testing was semi-successful. On one hand, QUIESCE stopped the system. Missing heartbeat was detec

Re: Testing SFM policy

--Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jesse 1 Robinson Sent: Tuesday, June 07, 2016 8:19 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Testing SFM policy I will proceed with QUIESCE once our automation SME is ready to test

Re: Testing SFM policy

Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jesse 1 Robinson Sent: Tuesday, June 07, 2016 8:19 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Testing SFM policy I will proceed with QUIESCE once our automation SME is ready to test. Key goal is to capture the partitioni

Re: Testing SFM policy

Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mike Myers Sent: Tuesday, June 07, 2016 5:45 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Testing SFM policy Mark and Skip: I can assure you that QUIESCE will stop the XCF heartbeat. I have used it often

Re: Testing SFM policy

Mark and Skip: I can assure you that QUIESCE will stop the XCF heartbeat. I have used it often in training to demonstrate the loss of heartbeat and triggering the sysplex to respond to the loss of a member. With an active SFM policy, it will trigger your desired action. The advantage to

Re: Testing SFM policy

Subject: Re: Testing SFM policy Deactivate? Stop? Force all chpids, paths, devices offline? copy a bunch of zeros into low storage and wait for the havoc to begin.. Free CSA.. almost guaranteed IPL I am sure the creative members of IBM-MAIN can come up with a plethora of normally undesirable actions

Re: Testing SFM policy

On 6/6/2016 4:32 PM, Jesse 1 Robinson wrote: I'd like to test my Sysplex Failure Management policy. The question is how to make a system stop responding long enough to trigger expulsion from the sysplex. I'm thinking of issuing QUIESCE on a member. If you quiesce a system, it will indeed be

Re: Testing SFM policy

Deactivate? Stop? Force all chpids, paths, devices offline? copy a bunch of zeros into low storage and wait for the havoc to begin.. Free CSA.. almost guaranteed IPL I am sure the creative members of IBM-MAIN can come up with a plethora of normally undesirable actions to exercise SFM. Rob

Re: Testing SFM policy

Since Quiesce will put the system in a restartable wait state, I'd think that the XCF heartbeat would stop too. Mark Jacobs Jesse 1 Robinson June 6, 2016 at 7:32 PM I'd like to test my Sysplex Failure Management policy. The question is how to make a system

Testing SFM policy

I'd like to test my Sysplex Failure Management policy. The question is how to make a system stop responding long enough to trigger expulsion from the sysplex. I'm thinking of issuing QUIESCE on a member. Have not used that in decades. Will it cause lack of XCF heartbeat? I can just try it