PLI_XRTDUMP=YES in TXSeries 8.2 should work like in COBOL: no CICS_CORE_ON_ASRA=1 should be necessary

CICS_CORE_ON_ASRA=1 is not recommended for productive
use as TXSeries documentation states
"... This variable must only be used on advice of IBM support
representative." presumely on a case-by-case basis only.

IBM COBOL already provides the default TRAP(ON) COBRTOPT setting.
This already generates a coredumpfile when severe signals are happening.
Setting CICS_CORE_ON_ASRA=1 is not required there!

Apparently all that PLI_XRTDUMP=YES does is NOT to modify the signal
handlers (which works in standalone PLI programs because the AIX
default settings will generate coredumps by default for fatal errors).

To achive the equivalent behaviour the PLIINITX code probably needs to
configure these signal handlers "back" to the AIX defaults; and restore
the previous handlers (established by TXseries probably) upon leaving
the PLI environment (or TXseries re-establishes their handler
preferences after EXEC CICS LINK rundown.)

However, unless explicit recommendation for productive use of
CICS_CORE_ON_ASRA=1 we cannot set this to get a consistent Post-Mortem-
Coredump for both IBM COBOL and IBM PLI 3.1 programs
even in cases where the CICSAS process will be better dead
anyway (or at least be unstable because it might as well have
overwritten foreign memory locations and should better be torn down
immediately).