PH00549: CICS: CHANNELERROREXCEPTION OCCURS WHEN CHANNEL IS DELETED AND SUBSEQUENTLY RECREATED (RESP=CHANNELERR, RESP2=1)

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When running CICS TS 5.4 and testing the new delete() function
  for the Channel JCICS API, it appears that when you delete the
  channel and then try to recreate it, it will fail with the
  following exception:
  .
   com.ibm.cics.server.ChannelErrorException: Channel
    "CICSChannel" already exists (RESP=CHANNELERR, RESP2=1)
  .
  where
     resp2_channelerr_invalid_name   bin(15) constant(1)
  .
  It turns out when the Channel.delete() function is called, it
  will delete the Channel from the CICS run time, but the Channel
  object does not get removed from the CICS Java code.
  .
  .
  .
  Additional Keyword(s) and Symptom(s):    KIXREVRJL
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS Users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: When the JCICS API                      *
  *                      Channel.createChannel() with the same   *
  *                      channel name is called after            *
  *                      Channel.delete(), RESP=CHANNELERR       *
  *                      RESP2=1 is returned.                    *
  ****************************************************************
  The application calls JCICS API Channel.delete(), it deletes the
  Channel from the CICS runtime, but the Channel object is not
  removed from the CICS Java code. Then when the application
  tries to recreate it using Channel.createChannel() it fails with
  exception: com.ibm.cics.server.ChannelErrorException: Channel
  "CICSChannel" already exists (RESP=CHANNELERR, RESP2=1)
  

Problem conclusion

• CICS has been changed to remove Channel object from the CICS
  Java code when JCICS API Channel.delete() is called.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UI58074

Modules/Macros

• DFJ@H223 DFJ@H239 DFJ@H356 DFJ@H361
  

Fix information

• Fixed component name

  CICS TS Z/OS V5

• Fixed component ID

  5655Y0400

Applicable component levels

• R10D PSY UI58074

     UP18/08/28 P F808

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.