PH11872: JCICS CONTAINERITERATOR DOES NOT ACCURATELY MAP TO EXEC CICS GETNEXT CONTAINER

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Container objects do not map to actual containers in CICS.  The
  JCICS API therefore does not keep the Java list of containers
  in step with the CICS list of containers.  .
  
  A Java application runs in a JVM server.  It links to a non-Java
  program passing a number of containers.  The non-Java program
  deletes one of the input containers and also creates a new
  output container, which it adds to the channel.
  On return, the Java program uses a ContainerIterator to access
  each container in turn.  It is expected that this is analogous
  to using STARTBROWSE CONTAINER and GETNEXT CONTAINER commands in
  COBOL.  What they find is that the deleted container gets
  returned by the next() method of the iterator, which then causes
  a CONTAINERERR condition if a GET is issued against it.  They
  also find that the newly created container is not returned at
  all.
  

Local fix

• No Locla Fix
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS Users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: JCICS ContainerIterator does not        *
  *                      accurately map to EXEC CICS             *
  *                      STARTBROWSE CONTAINER and GETNEXT       *
  *                      CONTAINER.                              *
  ****************************************************************
  The container objects in JCICS API do not keep in step with
  the CICS containers. When the Java application uses
  ContainerIterator to browse the Containers in a Channel,
  next() method may return a container which is deleted by CICS,
  then Container get() method will return ContainerErrorException.
  

Problem conclusion

• JCICS has been changed to keep the container objects in JCICS
  API in step with the CICS containers.
  

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:

  UI65625 UI65626 UI65627 UI65664

Modules/Macros

• DFJ@H356
  

Fix information

• Fixed component name

  CICS TS Z/OS V5

• Fixed component ID

  5655Y0400

Applicable component levels

• R00D PSY UI65626

     UP19/11/01 P F910

• R10D PSY UI65627

     UP19/11/01 P F910

• R200 PSY UI65664

     UP19/11/01 P F910

• R90D PSY UI65625

     UP19/10/04 P F910

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.