Fault Analyzer not producing entries in jes2 log nor FA

dot1q3 · Posted: Thu Aug 12, 2021 6:04 pm

Why would some users able to generate FA entry in 1 lpar but not another one?

for example, userA logged into lpar X generated an abend but not able to see the fault analyzer portion in the jes2 log. however, when userA logged into lpar Y, submitted the exact same JCL, produced abend, and able to see the FA portion in jes2 log.

Joerg.Findeisen · Posted: Thu Aug 12, 2021 6:11 pm

Should be a configuration thing in IDICNFxx, talk to your Sysprogs.

dot1q3 · Posted: Thu Aug 12, 2021 6:57 pm

@joerg.findeisen - thanks for your expeditious response.

will check with them. thanks again

hankoerlemans · New User Joined: 25 Jan 2018 Posts: 61 Location: Australia

Any IDI messages that are different ?
What does the ISPF dialog say about it ?
i.e. FA Main Menu->Help->About
and then FA Main Menu->Services->Service Information

but then .......your sysprogs are likely the ones that have to fix any discrepancies.

dot1q3 · Posted: Wed Aug 18, 2021 7:54 am

I'm not sure what the issue is, but they're unable to solve this issue.

Let see if i can clarify this a bit more.

very few users (excluding me) with their abend jobs are able to add IDI entries in FA on LPAR A. however, my abend jobs are able to add entries on LPAR B.

I look at the IDICNFxxA (lpar A) and IDICNFxxB (lpar B) and there are no differences (except the IDI.xx.HIST).

what could be the issue? these people are clueless!

any help is appreciated.

hankoerlemans · New User Joined: 25 Jan 2018 Posts: 61 Location: Australia

Time for a problem ticket ?
Got screen shots of the FA ISPF Dialog screen I mentioned ?

dot1q3 · Posted: Wed Aug 18, 2021 4:34 pm

under FA Main Menu->Help->About (for both LPARs)

IBM Fault Analyzer for Z/OS V14R1M2 (UI54624 2018/03/21)

Licensed materials - Property of IBM and/or HCL. 5655-Q41

--
FA Main Menu->Services->no Service Information (not listed).

hankoerlemans · New User Joined: 25 Jan 2018 Posts: 61 Location: Australia

Quite an old PTF level. See if you can get a ticket with IBM Support started.
Cant do any more here.

Joerg.Findeisen · Posted: Thu Aug 19, 2021 11:18 am

Hank is right, the PTF level is rather old. We do have IBM Fault Analyzer for z/OS V14R1M13 (UI74225 2021/03/08) installed.

dot1q3 · Posted: Thu Aug 19, 2021 2:38 pm

thanks guys for pointing that out.

i'm still puzzle (maybe because idk much!), but why would it work on 1 lpar but not the other? it's because the ptf is too old? it was working not long ago and still work for a small group of users.

so all they need to do is upgrade it to a newer one and this will fix this issue? is this something the internal team can perform or does it have to go through ibm support?

thanks for any clarifications.

dot1q3 · Posted: Fri Aug 20, 2021 1:31 am

ok some more information, which i hope can be useful in finding the root cause.

it appears COBOL programs that abended appear on this lpar but not ASM pgms.

is this configuration, setup, patch update, something else?

hankoerlemans · New User Joined: 25 Jan 2018 Posts: 61 Location: Australia

Can you use DDLIST (TSO ISRDDN) ?
If so command can you use command LOAD IEAVTABX.
Can you see IDIXDCAP ?
Do you have SDSF and can see the "DYNX Dynamic exits" Option ?
Select. Can you see IEAVTABX_EXIT referencing IDIXDCAP ?
If you can't see IDIXDCAP at all then call your friendly neighbourhood sysprog.
z/OS level could be a consideration for the DYNX coption BTW

dot1q3 · Posted: Fri Aug 20, 2021 7:06 am

hankoerlemans · New User Joined: 25 Jan 2018 Posts: 61 Location: Australia

Call your friendly neighbourhood sysprog.
All sorts of reasons why that might be the case.
Including some APARs

dot1q3 · Posted: Fri Aug 20, 2021 7:18 am

ok thx

dot1q3 · Posted: Thu Aug 26, 2021 5:09 am

a quick update on this, they finally opened a ticket with ibm after so much hesitation...

they suspect it could be related to the EXIT not being active. not sure what that means ?

if it's not active on this lpar, why does it still produced some fault history but not others.

something about:

EXIT ADD EXITNAME(IEAVTABX_EXIT) MODNAME(IDIXDCAP)

hankoerlemans · New User Joined: 25 Jan 2018 Posts: 61 Location: Australia

Yeah, saw the ticket.
LE enabled applications can use the LE abnormal termination exit.
Non-LE abends are picked up via a z/OS exit.
CICS also provides two ways of getting dumps captured.

dot1q3 · Posted: Thu Aug 26, 2021 5:22 am

you're able to see when others open tickets?

sorry but what is LE mean and what does it have to do with FA and exit?

hankoerlemans · New User Joined: 25 Jan 2018 Posts: 61 Location: Australia

I have a support role.
I saw a ticket that matches this conversation and I can put 2 and 2 together ;-)
LE = Language Environment.
Think of it as the runtime support for high level languages such as PLI Cobol and C.

dot1q3 · Posted: Thu Aug 26, 2021 5:35 am

ok thanks