Re: Re: z/VM 6.1 under Hercules - How To

Thanks.  That is what I expected.  PFPO has been a thorn in our side for 
some time ever since IBM has been requiring the setting to be there 
during operating system initialization.  Linux looks for it too.  No 
surprise VM is also looking for it.  In reality, it is probably passing 
it along to Linux.

Harold

[email protected] wrote:

>Harold,
>
>Yes, your suspicion is correct. The STFLE bits need to reflect that the PFPO feature is available for z/VM 6.1 to IPL. The two instructions below are taken from the z/VM 6.1 IPL trace. These are what to look for if you're doing your own trace.
>
>002AA994 INST=B2B02000     STFLE 0(2)                  store_facility_list_extended
>002AA998 INST=4710C2F2     BC    1,754(0,12)            branch_on_condition
>
>R2 = xxxxxxxx F0700000
>
>The 7 has bits 41-43 turned on. Bit 40 is not used by IBM.
>The 0 (after the 7) needs bit 44 (the PFPO bit) turned on. 
>Bit 44 is the last bit currently used by IBM.
>
>So, technically, F0700000 should be changed to F0780000 to turn on just the PFPO bit.
>Since bit 40 & bits 45-47 aren't used by IBM (currently), F0FF0000 accomplishes the same results.
>
>STFLE bits:
>
>41 The floating-point-support-enhancement facilities
>(FPR-GR-loading, FPS-sign-handling, and DFProunding)
>are installed in the z/Architecture
>architectural mode.
>
>42 The DFP (decimal-floating-point) facility is installed
>in the z/Architecture architectural mode.
>
>43 The DFP (decimal-floating-point) facility has high
>performance. Bit 42 is one if bit 43 is one.
>
>44 The PFPO instruction is installed in the
>z/Architecture architectural mode.
>
>--- In [email protected], Harold Grovesteen <h.grovsteen@...> wrote:
>  
>
>>Can you explain what you are changing and why?  I suspect it is STFLE 
>>bits, but am curious. 
>>
>>Harold Grovesteen
>>
>>ioob@... wrote:
>>
>>    
>>
>>>To All,
>>>   For the group. Basically you have to set a Breakpoint in Hercules, modify VM storage and continue the IPL. I strongly suggest you use the Hercules CMD Prompt window, not the Hercules GUI. If you're using the z/VM 6.1 Base system, follow/use the "Base" values below. If you apply the z/VM 6.1 RSU, then use the values on the left side.
>>>
>>>Once a new RSU comes out, it may modify storage locations again and a new Hercules Trace will have to be done (see below).
>>>
>>>IPL (from Hercules CMD prompt window)
>>>
>>>1. hercules -f c:\hercules\zvm610\hercules.txt            (change to your Hercules config file location)
>>>2. B+ 2AAF98                                  (z/VM 6.1.0 Base: 2AA998)
>>>3. IPLC 340D                                   (replace address with your IPL address)
>>>4. GPR                                              (R2=002F4108) (z/VM 6.1.0 Base: R2=002F3008)
>>>5. R 2F4108                                      (z/VM 6.1.0 Base: R 2F3008 ---> xxxxxxxx F0700000)
>>>6. R 2F410C=F0FF0000                   (z/VM 6.1.0 Base: R 2F300C=F0FF0000)
>>>7. (press ENTER)
>>>  (IPL should complete normally)
>>>8. CMDTGT SCP                              (sends commands to z/VM)
>>>8.5 ENABLE ALL                              (enable all VM 3270 terminals)
>>>...have fun...
>>>9. HERC CMDTGT HERC                (sends commands back to Hercules)
>>>10. QUIT                                          (exit hercules)
>>>
>>>Hercules TRACE (took approx. 40 mins on my 2.53Ghz laptop)
>>>1.Log c:\herclog.txt
>>>2.traceopt noregs
>>>3.T+
>>>4.IPLC 340D
>>>6.G
>>>
>>>
>>>
>>>------------------------------------
>>>
>>>Yahoo! Groups Links
>>>
>>>
>>>
>>>
>>> 
>>>
>>>      
>>>
>
>
>
>
>------------------------------------
>
>Yahoo! Groups Links
>
>
>
>
>  
>