A fix is available
APAR status
Closed as program error.
Error description
In DFHRMLK, routine RMLK_Issue_Prepare_Proc calls RMLK_Lookup_Link to locate the link to be prepared for syncpoint. In our case, the link_ptr is nulls (this is erroneous but that's a different matter) so the call would set response = rmln_exception and reason = rmln_link_unknown. Later in the routine, we test if response = rmlk_exception & reason = rmlk_prepare_rejected which is wrong as we haven't driven the path to perform the prepare, yet. So we are testing a response of 2 and reason of 1, which happen to match the values we set earlier due to the null link. This makes us try to set link.vote to 0 and so program check trying to update low core.
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: All * **************************************************************** * PROBLEM DESCRIPTION: Program check (0C4) in routine * * rmlk_issue_prepare_proc due to null * * link token. * **************************************************************** * RECOMMENDATION: * **************************************************************** The customer had an invalid link token for a DTP conversation session. When an issue_prepare command was issued, DFHRMLN detected the invalid token and set up response and reason values for this error. However, it did not return to the caller at this stage, but continued on within the prepare logic. When the code reached the error checking logic at the end of the routine, the response and reason values it had set earlier resulted in DFHRMLN believing the prepare had been rejected. This led to an attempt to update the link object, but as the pointer to it was null because of the invalid link token, a program check (S0C4) occurred trying to modify low core. KEYWORDS: abend0c4 abends0c4 0c4 rmlk_exception rmlk_prepare_rejected
Problem conclusion
DFHRMLN has been modified to return the rmln_exception with a reason of rmln_unknown_link when an invalid link token is detected, rather than continue on within the prepare logic.
Temporary fix
FIX AVAILABLE BY PTF ONLY
Comments
APAR Information
APAR number
PM64554
Reported component name
CICS TS Z/OS V4
Reported component ID
5655S9700
Reported release
600
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-05-14
Closed date
2012-05-28
Last modified date
2012-06-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK79138 UK79139
Modules/Macros
DESRMLK DESRMLN DFHRMLKC DFHRMLN
Fix information
Fixed component name
CICS TS Z/OS V4
Fixed component ID
5655S9700
Applicable component levels
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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.1","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"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":"4.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
03 June 2012