On Mon, 28 Jan 2013 13:11:58 -0500, Jim Mulder <[email protected]> wrote:
>> OK, we finally noticed we had back-level IPLTEXT on the SADMP IPL
>> volume. Re-generated SADMP, captured the dump, and now IPCS gives
>> us this "hate mail":
>>
>> [ snip ]
>
> I would start with
>\
>STATUS CPU(0) REGS
CPU(X'000') STATUS:
BLS18100I NOCPU ASID(X'0001') FDBF48 not available for CVT
BLS18104I Symbol LCCAVT not found
BLS18104I Symbol LCCA0 not found
BLS18058I Warnings regarding STRUCTURE(Ascb) at NOCPU ASID(X'0001') FDA500:
BLS18300I Storage not in dump
BLS18100I NOCPU ASID(X'0001') FDA500 not available for LCCA0
PSW=07060000 00000000 00000000 00000000
No work wait
BLS18100I NOCPU ASID(X'0001') FDBF44 not available for CVT
BLS18104I Symbol PCCAVT not found
BLS18104I Symbol PCCA0 not found
Storage access could not read block at 026920E8 for CLTE
No storage areas were passed or obtained, formatting is terminated.
CURRENT FRR STACK IS: SVC
PREVIOUS FRR STACK(S): NORMAL
General purpose register values
0-1 00000000_00000000 C0000000_00000000
2-3 0002D048_00000000 C0000000_00000000
4-5 40000000_00000000 80000000_00000000
6-7 00000000_00000000 00000000_00000000
8-9 80000000_00000000 00000000_00000000
10-11 00000000_00000000 80000000_00000000
12-13 80000000_00000000 00000000_00000000
14-15 40000000_00000000 80000000_00000000
Access register values
0-3 00000000 00000000 00000000 00000000
4-7 00000000 00000000 00000000 00000000
8-11 00000000 00000000 00000000 00000000
12-15 00000000 00000000 00000000 00000000
Control register values
0-1 00000000_DF88EE70 00000000_7CC69007
2-3 00000000_7ED26FC0 00000001_00000001
4-5 00000001_00010001 00000000_07E29040
6-7 00000000_FE000000 00000000_7CC69007
8-9 00000000_00000000 00000000_00000000
10-11 00000000_00000000 00000000_00000000
12-13 00000000_85B7ADBC 00000000_7CC69007
14-15 00000000_DF882EB2 00000000_027AF010
The "No work wait" is kind of surprising.
>and
>
>VERBX SADMPMSG
A couple instances of "n MESSAGE BUFFERS MISSING" (total of 6), but otherwise
lists just about all the active ASIDs being processed.
> Also, make sure that IPCS is accessing the
>IPCS-related parmlib members for the correct release. These
>parmlib members would be coming from the IPCSPARM ddname
>if you are using one, or your parmlib concatenation
>(viewable via D PARMLIB ) otherwise.
Verified that only the IBM-supplied, unmodified IPCSPR00 and BLSCECT(X) are in
the parmlib concatenation. We don't have a BLSCUSER member at all.
> If the problem is not apparent, the easiest thing
>is usually to open a PMR and send in the dump so I
>can look at it.
That seems the best option at this point. So, it will be "coming at you"
shortly, Sev 3.
Thanks,
-jc-
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
