PM22114: JAVA CHANNEL ERROR USING JCICS ON A SECOND ATTEMPT TO PUT A CONTAINER ONTO A CHANNEL

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• You are trying to use JCICS for adding a CONTAINER on an
  existing CHANNEL.
  In Java, you are supposed to get the Task object and then
  execute the  createChannel(channel_name) method. This method
  call does not seem to  result in an EIP call but looks like it
  uses the ChannelFactory class to  create a Java object for the
  named channel. This seems consistent with the command level
  documentation, since a PUT CONTAINER will create the  named
  channel if it does not exist. When the container is put to the
  channel in Java using a method on the Channel object returned
  from task.createChannel, we see that CICS creates the channel
  and then puts the container on the channel.
  The next time into the application Java class (even when newly
  instantiated) during the same transaction, if you execute the
  same logic:
  -
   ? task.createChannel(channel_name)
  -
  instead of returning a reference to  the object for that
  existing channel, the ChannelFactory is returning a  channel
  error because the channel already exists.
  Additional Symptom(s) Search Keyword(s):
  KIXREVGJT
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION: No mechanism for obtaining a reference  *
  *                      to a channel object that has been       *
  *                      previously created.                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A Java application is using JCICS. It links to multiple CICS
  programs specifying the same channel name each time. Every time
  this is invoked it calls Task.createChannel with a fixed channel
  name. When it is invoked for a second time this results in a
  ChannelErrorException because the named channel already exists.
  
  There is no mechanism for the application to obtain a
  reference to an existing channel.
  

Problem conclusion

• The Task.getChannel method has been added to return a named
  channel if it exists or null if it does not.
  
  The Javadoc has been updated to include the new method.
  

Temporary fix

• FIX AVAILABLE BY PTF ONLY
  

Comments

APAR Information

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

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

  PM23305 UK62714

Modules/Macros

•    DFJ@H000 DFJ@H025
  

Fix information

• Fixed component name

  CICSTS V3 Z/OS

• Fixed component ID

  5655M1500

Applicable component levels

• R50D PSY UK62714

     UP10/12/03 P F012

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.