PI66144: EXIT ROUTER IS NOT HANDLING SYNCLEVL=SYNCPOINT REQUESTS FROM JAVA CLIENT

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• 1. When a request intended for HWSJAVA0 includes an XID the exit
  router is returning a badly formed message.
     Symptoms include:
        HWSP1490E INVALID OTMA SEQUENCE NUMBER
        Client error, "The OTMA header of the IMS output message
                       did not contain a [STATE DATA] segment."
  
  2. FUN2211I message is incorrectly issued if ISC or RMTCICS
     keywords are used in the IMS Connect configuration.
  3. If a REXX QUERY TYPE=SESSIONS command returns a session count
     of zero a RC=4 is issued with an unexpected reason code
  4. Any update to server or utility messages causes SMP/E to
     unnecessarily relink the ISPF load modules.
  
  Summary of changes:
  1. Correct the exit router to correctly handle XIDs in java
     requests.
  2. Update parsing routines to accept ISC or RMTCICS
     keywords
  3. Correct the RC/RSN logic.
  4. Remove the unused message tables from the ISPF load modules
  
  User action
     Apply the PTF and restart IMS Connect.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of IMS Connect Extensions V2.4         *
  ****************************************************************
  * PROBLEM DESCRIPTION: Exit router is not handling             *
  *                      synclevl=syncpoint requests             *
  *                      from Java client.                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  1. When a request intended for HWSJAVA0 includes an XID the
     exit router is returning a badly formed message.
     Symptoms include:
  
       HWSP1490E INVALID OTMA SEQUENCE NUMBER
       Client error, "The OTMA header of the IMS output message
       did not contain a  STATE DATA  segment."
  
  2. FUN2211I message is incorrectly issued if ISC or RMTCICS
     keywords are used in the IMS Connect configuration.
  
  3. If a REXX QUERY TYPE=SESSIONS command returns a session
     count of zero a RC=4 is issued with an unexpected reason
     code.
  4. Any update to server or utility messages causes SMP/E to
     unnecessarily relink the ISPF load modules.
  

Problem conclusion

• 1. Correct the exit router to correctly handle XIDs in java
     requests.
  
  2. Update parsing routines to accept ISC or RMTCICS keywords.
  
  3. Correct the RC/RSN logic.
  4. Remove the unused message tables from the ISPF load modules.
  

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:

  UI40507

Modules/Macros

• CEXDFNS  CEXEVTPR CEXEVTSR CEXEXRTR CEXMAIN
  CEXPRSR  CEXRXADR CEXR163  CEXTECL  H28S240J
  

Fix information

• Fixed component name

  IMS CONNECT EXT

• Fixed component ID

  5655K4800

Applicable component levels

• R240 PSY UI40507

     UP16/09/17 P F609

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.