OPS/MVS

  • 1.  Anybody using BCPii and MCL 27?

    Posted Sep 06, 2017 03:30 AM

    We just upleveled 2 of our z13 cpc's from microcodel level 22 to 27.

    Now we see that the OPS/MVS HISRV API returns data in a different order, causing haywire to the messages:

    Example:

    Before:

    HWSSECUR   SECURITY EVENT CPC IBM390PS.CPC110 ID=943 The current processing capped value for the GP CPs in partition NLH100   changed from 1 to 0 (0=not capped, 1=capped). 

    After:

    HWSSECUR   SECURITY EVENT CPC IBM390PS.CPC210 ID=943 The current processing capped value for the 0 CPs in partition 1 changed from zIIP to NLGX00   (0=not capped, 1=capped). 

    Clearly words 14 and 23, as well as 18 and 21 have been switched.

     

    There's other API msgs that show similar switched words.....

     

    We opened a PMR with IBM, but was wondering if anyone else ran into this?



  • 2.  Re: Anybody using BCPii and MCL 27?

    Posted Sep 13, 2017 06:26 AM

    Well, on IBM's advice took a peek in the HMC SE security log where I noticed:

    12 september 2017 0:59:14 uur CEST     943 The current processing capped value for the GP CPs in partition DEHAMD changed from 1 to 0 (0=not capped, 1=capped).

     

    While this is the actual API message in our OPSLOG (some time difference as the HMC is not synched with the lpar 's time)

     

    12SEP 00:59:00 HWSSECUR   SECURITY EVENT CPC IBM390PS.CPC210 ID=943 The current processing capped value for the 1 CPs in partition 0 changed fr          
    12SEP 00:59:00 HWDATA Hardware Event: HWSSECUR     OPSsubsys: OPSS                                                                                       
    12SEP 00:59:00 **********************************************************************                                                                    
    12SEP 00:59:00 * App: HIS        Ver: 02.04.00   Level: RESERVED   TYPE: ENTITY    **                                                                    
    12SEP 00:59:00 * DATE/TIME: 2017/09/12  00:59:00.85      EV LEVEL: 4               **                                                                    
    12SEP 00:59:00 * DESC: SECURITY EVENT                                              **                                                                    
    12SEP 00:59:00 * Event Entity: CPC IBM390PS.CPC210                                 **                                                                    
    12SEP 00:59:00 * *Entity Hierarchy*                                                **                                                                    
    12SEP 00:59:00 * CPC              Lv: 4         IBM390PS.CPC210                    **                                                                    
    12SEP 00:59:00 * Ensemble         Lv: 3         IBM390PS.CPC210                    **                                                                    
    12SEP 00:59:00 * Installation     Lv: 2         EMH Datacenter                     **                                                                    
    12SEP 00:59:00 * Enterprise       Lv: 1         Atos Mainframe Services            **                                                                    
    12SEP 00:59:00 * Msg Timestamp:  09-12-2017 00:59:14:149                           **                                                                    
    12SEP 00:59:00 * Message Text:                                                     **                                                                    
    12SEP 00:59:00 * ID=943 The current processing capped value for the 1 CPs in parti **                                                                    
    12SEP 00:59:00 * tion 0 changed from GP to DEHAMD   (0=not capped, 1=capped).      **                                                                    
    12SEP 00:59:00 **********************************************************************                     

     

    While I still feel it's IBM's issue (as that's where the change lies) they now ask me to register an issue with CA to discuss it, which we'll do.

     

    Thanks,

     

    Marcel van Ek

    Atos                                           



  • 3.  Re: Anybody using BCPii and MCL 27?

    Posted Mar 27, 2019 03:54 AM

    In the end IBM upleveled the microcode and fixed our problem.