A fix is available
APAR status
Closed as program error.
Error description
ABEND46D RC10 is issued when ESPIE processing is scanning the chain of ESPIE environments to be deleted and finds at least one ESPIE environment that was not created at the same RB level as the ESPIE RESET was issued at.
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: * * All users of z/OS TSO/E * **************************************************************** * PROBLEM DESCRIPTION: * * An ABEND46D-10 can occur trying to do * * an ESPIE RESET (aka delete) to remove * * the null ESPIE exit that is sometimes * * established by the EXEC command when * * a REXX exec is invoked by a caller * * who already has an ESPIE. The EXEC * * command ESPIE can only be reset when * * done at the same RB level as where it * * had been established. Issuing the * * ESPIE RESET from a later RB will * * result in an ABEND46D. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND46D RC10 is issued when ESPIE processing is scanning the chain of ESPIE environments to be deleted and finds at least one ESPIE environment that was not created at the same RB level as the ESPIE RESET was issued at. . This problem can be seen if a REXX exec invoked by the EXEC command is hit by a non-retryable abend that causes the REXX recovery and EXEC command recovery to percolate. The EXEC command's recovery will attempt to remove any null ESPIE it had established when its recovery is unable to retry back into the mainline EXEC code (under the original RB) to remove the ESPIE. However, while running in the EXEC command recovery it is running under the abend SVRB, which is a lower level RB than the RB under which the ESPIE had been established. This results in the ABEND46D RC10. . This problem cannot occur if the REXX exec or EXEC command processor is hit with a retryable abend, or if the EXEC command does not see any abend, nor can it occur if the caller of the EXEC cmd did not already have its own ESPIE established when it invoked EXEC.
Problem conclusion
The EXEC command will verify that it is at the correct RB level when doing an ESPIE RESET to remove an ESPIE that it had previously established. If EXEC is not running at the correct RB level, as would be the case when the code to reset the ESPIE gets control under the EXEC command's ESTAE, then EXEC will avoid doing an ESPIE RESET. In this case, the ESPIE will be automatically reset by MVS when the RB terminates under which the ESPIE had been established. That is, when the EXEC command's RB terminates, MVS will automatically terminate any remaining ESPIE that had been previously established by that RB.
Temporary fix
Comments
APAR Information
APAR number
OA48390
Reported component name
TSO/E SCHEDULAR
Reported component ID
566528502
Reported release
790
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-07-16
Closed date
2017-07-20
Last modified date
2017-09-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UA92715 UA92750 UA92757 UA92758
Modules/Macros
IKJCT430 IKJCT43D
Fix information
Fixed component name
TSO/E SCHEDULAR
Fixed component ID
566528502
Applicable component levels
R780 PSY UA92757
UP17/08/10 P F708
R7B0 PSY UA92715
UP17/08/10 P F708
R7A0 PSY UA92750
UP17/08/10 P F708
R790 PSY UA92758
UP17/08/10 P F708
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"790","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"790","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 September 2017