A fix is available
APAR status
Closed as program error.
Error description
Service for PK66022 added a check in DFSAERG0 under label AERG2000 when processing a APSB call to check if aibrsa3 is zeros. When it is not zeros AIBRETRN 260, AIBREASN 580 are returned. . This check should not be made as we have not documented that aibras3 needs to be zeros during APSB processing. . AIBRETRN 260, AIBREASN 580 was means needs to be documented as to mean 'Invalid AIBRSA3 parameter' as INVRSA3 will still be set during CIMS FTHD processing when aibrsa3 does not contain a TCB address.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All IMS V10 ODBA users with PK66022/UK42410 * * installed. * **************************************************************** * PROBLEM DESCRIPTION: Problem 1: * * Aibretrn 0104, Aibreasn 0244 from * * AERTDLI APSB call when AIBRSA3 is not * * zeros after service for PK66022. * * * * Problem 2: * * IMS shutdown hangs due to orphaned * * ODBA threads. * * * * Problem 3: * * Abendu0711 RC10 in DFSRRSI0 routine * * POST_DEFERRED_UR. Reg 2 contains F00. * **************************************************************** * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF * **************************************************************** Problem 1: A check for a zero value in field AIBRSA3 was added to APSB call processing by PK66022. This field is not required nor is it documented as needing to be set. When AIBRSA3 is not zero, aibreturn 0104 , aibretrn 0244 are returned on the APSB call. Problem 2: Orphaned ODBA threads cause IMS shutdown to hang. These threads show up in IMS display commands but stop commands have no affect. The thread may have a residual flow in the PST that contains DFSAERC0 -> DFSRRSI0 -> DFSDSC00 indicating that syncpoint processing has been done but the LCRE remains enqueued on the ODBA subsystem SIDX with the PST cleaned up. This is the result of the SIDX dequeue request in DFSAERC0 specifying the wrong SIDX name. These threads are typically orphaned by an abnormal end from the application which results in no DPSB being performed. One common scenario that results in an orphaned thread is when a DB2 ASU timeout is encountered by a stored procedure that accesses ODBA. Diagnostic observation from problem 2: The LCRE for the orphaned thread is enqueued on the ODBA subsystem SIDX (SIDX name is ODBAxxxx where xxxx = hex asid of the ODBA address space). The LCRE is cleaned up including the recovery token. Problem 3: Abendu0711 RC10 in DFSRRSI0 routine POST_DEFERRED_UR. Register 2 at abend contains x'00000F00'. This abend occurs under an ODS tcb. A STIMER call is issued to retry the RRS post_deferred call. Because an IMS FRR is active at the time of the call, issuing the STIMER SVC results in an MVS abend that is captured by the FRR and converted to an abendu0711 rc10. Additional Keywords: rc0104 rc0260 rsn0244 rsn0580
Problem conclusion
GEN: KEYWORDS: *** END IMS KEYWORDS *** DFSAERG0 - Now clears field aibrsa3 during APSB processing. It no longer checks the passed in value. DFSAERC0 - Will dequeue the LCRE from the correct SIDX based on LCRE flags LCREUNHK and LCRECDRA. DFSRRSI0 - Issue ATRSROI call if PSTUTKN is zero during Perform_Syncpoint processing. Disable the IMS FRR before issuing STIMER. DFSCWU00 - Clear PSTUTKN for PST create work unit DFSDASP0 - Check for setting PSTUTKN.
Temporary fix
********* * HIPER * *********
Comments
POSTREQ PM09700 REPINNED RP10/03/12 (ATXT) TO ADD POSTREQ PM09700 INFO. **** PE10/03/12 PTF IN ERROR. SEE APAR PM09700 for description. ×**** PE10/03/10 FIX IN ERROR. SEE APAR PM09700 FOR DESCRIPTION
APAR Information
APAR number
PK82475
Reported component name
IMS V10
Reported component ID
5635A0100
Reported release
010
Status
CLOSED PER
PE
YesPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2009-03-13
Closed date
2009-09-18
Last modified date
2010-05-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PK82562 UK50263
Modules/Macros
DFSAERC0 DFSAERG0 DFSCWU00 DFSDASP0 DFSRRSI0
Fix information
Fixed component name
IMS V10
Fixed component ID
5635A0100
Applicable component levels
R010 PSY UK50263
UP09/09/24 P F909 «
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":"10.1","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCVRBJ","label":"System Services"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
04 May 2010