A fix is available
APAR status
Closed as program error.
Error description
Received the following message. . DFHME0110 CICSREGN Optional value 04 is missing from insert 02 for message DFHIS1002. . Looking through the LOGs we see the following. . Joblog . DFHME0110 CICSREGN Optional value 04 is missing from insert 02 for message DFHIS1002 . MSGUSR . DFHSO1000 CICSREGN A request for TCP/IP communication failed code 0E20 for IPCONN 00000001 using applid 00000001. zOS UNIX system services supplied bpx_return_value -1 bpx_return_code 0000046, and bpx_reason_code 76650446. . DFHIS1021 CICSREGN Session error occurred on RECEIVE IPIC session in IPCONN 00000001. . DFHIS2009 CICSREGN Client web session 1 in IPCONN 00000001 from applid 00000001 released. . DFHIS2009 CICSREGN Client web session 2 in IPCONN 00000001 from applid 00000001 released. . DFHIS3030 CICSREGN IPCONN 00000001 deleted. . DFHSO1000 CICSREGN A request for TCP/IP communication failed code 0E20 for IPCONN 00000001 using applid 00000001. zOS UNIX system services supplied bpx_return_value 0, bpx_return_code 00000000, and bpx_reason_code 00000000. . DFHIS1021 CICSREGN Session error occurred on RECEIVE IPIC session in IPCONN 00000001. . DFHIS1002 CICSREGN Unable to ??? IPCONN 00000001. IPCONN not found. . You can see above that the DFHIS1002 message is being issued as being unable to ??? and this is what causes the DFHME0110 message to get issued. The message format should be. . DFHIS1002 date time applid Unable to 'acquire or release' IPCONN ipconn. IPCONN not found. . In the CICS Trace you see. . 0411 MEBU EXC - NO-OPTIONAL-INSERT . The problem is when CICS was notified that one of the CLIENT IS sockets was closed, a CIST task was attached to terminated the IPCONN, task 11111. The CIST task sucessfully RELEASED the IPCONN and because it was initially autoinstalled, it was also discarded at the same time. CICS was notified that the second CLIENT IS socket for the same IPCONN was closed. What should have happen here is that socket closed should have been ignored because the IPCONN no longer existed. Instead a second CIST task was attached, task 11112, to terminate the IPCONN leading to message DFHIS1002. There may be also another problem issuing message DFHIS1002 that caused the ME domain to produced an SDUMP. . Additional Symptom(s) Search Keyword(s): KIXREVxxx
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: All CICS users. * **************************************************************** * PROBLEM DESCRIPTION: DFHME0110 Optional value 04 is missing * * from insert 02 for message DFHIS1002. * **************************************************************** Two CICS regions are connected via IPIC connection. An error occurred which causes IPCONN termination processing. CICS locates the IPCONN first before the termination. If the IPCONN can not be located for some reason, message DFHIS1002 will be issued to report that the IPCONN can not be found. The ISCO_FUNCTION which has value 04 to indicate IPCONN termination will be passed as the optional value of insert 02 for message DFHIS1002. The value 04 is not defined in DFHMEISE, which causes DFHME0110 with a system dump.
Problem conclusion
DFHMEISE will be changed to make sure DFHIS1002 with optional value 04 in insert 02 can be properly displayed without DFHME0110 and system dump. CICS Transaction Server for z/OS Version 5 Release 2 CICS Messages and Codes Vol 1, GC34-7283-00 has amended the description of message DFHIS1002. In page 914, change the line "3=release" to "3=release,". After this line, add a new line "4=release". CICS Transaction Server for z/OS Version 5 Release 3 CICS Messages and Codes Vol 1, GC34-7418-00 has amended the description of message DFHIS1002. In page 924, change the line "3=release" to "3=release,". After this line, add a new line "4=release". CICS Transaction Server for z/OS CICS Messages Version 5 Release 4 has amended the description of message DFHIS1002. In page 664, change the line "3=release" to "3=release,". After this line, add a new line "4=release".
Temporary fix
Comments
APAR Information
APAR number
PI77842
Reported component name
CICS TS Z/OS V5
Reported component ID
5655Y0400
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-03-08
Closed date
2017-07-13
Last modified date
2017-08-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI48764 UI48765 UI48883
Modules/Macros
DFHMEISC DFHMEISE DFHMEISK
Fix information
Fixed component name
CICS TS Z/OS V5
Fixed component ID
5655Y0400
Applicable component levels
R000 PSY UI48765
UP17/07/21 P F707
R100 PSY UI48883
UP17/07/22 P F707
R900 PSY UI48764
UP17/07/20 P F707
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":"5.2","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":"5.2","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 August 2017