A fix is available
APAR status
Closed as program error.
Error description
5697E9300 Customer does not make use of ARM with CICS but ARM support is available. They have more than 999 CICS regions, thus reach the max user limit (IXCARMMAXUSERS) due to reaching the user coded limit of 999 when all of the CICS regions register with ARM. This causes DFHXQ0122 IXCARM REQUEST=REGISTER failed, return code 0000000C reason code 00000104. The registrations are coming out of the server modules: DFHNCRS - Named counter server DFHCFRS - Coupling Facility data table server DFHXQRS - Temp Storage Datasharing server . When these modules detect this combination of return and reason code, the associated server is terminated. This action is too drastic and should be handled by issuing a message to report max users was detected but then allow the server to continue running . Additional keywords: Automatic Restart Manager, maxusers, maximum, maxuser, slot, slots
Local fix
Increase maximum users within ARM.
Problem summary
**************************************************************** * USERS AFFECTED: All * **************************************************************** * PROBLEM DESCRIPTION: A shared temporary storage server * * abends with message DFHXQ0122, return * * code x'0000000C', reason code * * x'00000104'. * **************************************************************** * RECOMMENDATION: * **************************************************************** A customer has in excess of 999 CICS regions running concurrently, causing the MVS automatic restart manager (ARM) max user limit to be reached. This means that any subsequent attempts to start up address spaces which need to register with ARM, such as a shared temporary storage server, fail with with (for example) message DFHXQ0122, even though ARM support is not actually required. KEYWORDS: ixcarmmaxusers msgdfhxq0122 dfhnc0122 msgdfhnc0122 dfhcf0122 msgdfhcf0122 maxuser maxusers
Problem conclusion
Modules DFHXQRS, DFHCFRS and DFHNCRS have been amended so that, when IXCARMMAXUSERS is reached, new informational messages - DFHXQ0123, DFHCF0123 and DFHNC0123 respectively - are issued and the shared temporary storage server (or coupling facility datatable, or named counter server) continues initialisation. =============================================================== The following changes will be made to the CICS Transaction Server for z/OS Version 3 Release 1 CICS Messages and Codes manual (GC34-6442-00): (1) Immediately after the entry for message DFHCF0122, a new entry should be added as follows: DFHCF0123 IXCARM REQUEST=reqtype failed, return code retcode, reason code rsncode. Explanation: Automatic restart support is not available. The MVS automatic restart manager (ARM) gave an unexpected return code. The return and reason code are shown in hexadecimal notation. System Action: The server continues initialisation. User Response: See the IXCARM macro in OS/390 MVS Programming: Sysplex Services Reference (GC28-1772) for the explanation of the return and reason code. Note: This message cannot be changed with the message editing utility. Destination: Console and SYSPRINT Modules: DFHCFRS (2) Immediately after the entry for message DFHNC0122, a new entry should be added as follows: DFHNC0123 IXCARM REQUEST=reqtype failed, return code retcode, reason code rsncode. Explanation: Automatic restart support is not available. The MVS automatic restart manager (ARM) gave an unexpected return code. The return and reason code are shown in hexadecimal notation. System Action: The server continues initialisation. User Response: See the IXCARM macro in OS/390 MVS Programming: Sysplex Services Reference (GC28-1772) for the explanation of the return and reason code. Note: This message cannot be changed with the message editing utility. Destination: Console and SYSPRINT Modules: DFHNCRS (3) Immediately after the entry for message DFHXQ0122, a new entry should be added as follows: DFHXQ0123 IXCARM REQUEST=reqtype failed, return code retcode, reason code rsncode. Explanation: Automatic restart support is not available. The MVS automatic restart manager (ARM) gave an unexpected return code. The return and reason code are shown in hexadecimal notation. System Action: The server continues initialisation. User Response: See the IXCARM macro in OS/390 MVS Programming: Sysplex Services Reference (GC28-1772) for the explanation of the return and reason code. Note: This message cannot be changed with the message editing utility. Destination: Console and SYSPRINT Modules: DFHXQRS
Temporary fix
FIX AVAILABLE BY PTF ONLY
Comments
APAR Information
APAR number
PK17020
Reported component name
CICSTS 3.1 Z/OS
Reported component ID
5655M1500
Reported release
400
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2005-12-21
Closed date
2006-01-13
Last modified date
2006-02-02
APAR is sysrouted FROM one or more of the following:
PK16614
APAR is sysrouted TO one or more of the following:
UK10689
Modules/Macros
DFHCFMS DFHCFRS DFHMECFE DFHMENCE DFHMEXQE DFHNCMS DFHNCRS DFHXQMS DFHXQRS DFH17020 MFHMECFE MFHMENCE MFHMEXQE
GC34644200 |
Fix information
Fixed component name
CICSTS 3.1 Z/OS
Fixed component ID
5655M1500
Applicable component levels
R400 PSY UK10689
UP06/01/19 P F601
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":"3.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":"3.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 February 2006