PM74636: WEBSPHERE APPLICATION SERVER FOR Z/OS IS MAKING A CALL USING OTMA C/I TO IMS. RC/RSN FIELDS ARE NOT FILLED IN FOR THE CALL.

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • During testing with the WebSphere Application Server for z/OS,
    the servant region is making an OTMA C/I call using
    otma_send_receivex. After waiting on the ECB provided on
    the call the RC/RSN fields are not filled in with the RC/RSN.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All IMS V11 OTMA Callable Interface Users    *
    *                 with Synclevel Syncpoint (SL=2) and RRS.     *
    ****************************************************************
    * PROBLEM DESCRIPTION: OTMA CI client posted with no return    *
    *                      or reason code after issuing an         *
    *                      OTMA_Send_Receive(x) API call for a     *
    *                      synclevel synpoint (SL=2) transaction.  *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    This problem is caused by a mishandling of the deallocate
    message for synclevel syncpoint by OTMA CI, which results in
    the client being posted in error.
    
    The scenario is as follows:
    
    1. The CI client issues an otma_send_receive(x) API call for a
    synclevel syncpoint transaction and waits for the response.
    
    2. IMS processes the transaction and sends the response to
    OTMA CI.
    
    3. OTMA CI posts the CI client with the response.
    
    4. The CI client issues the RRS commit or backout and then
    issues the otma_free API call to release the session.
    
    5. The CI client issues a second otma_send_receive(x) API call
    for a synclevel syncpoint transaction and waits for the
    response.
    
    6. IMS proceeds with syncpoint for the first transaction and
    sends a deallocate message to OTMA CI.
    
    7. OTMA CI processes the deallocate message for the first
    transaction and posts the CI client with no return/reason code.
    
    Due to the timing of the second otma_send_receive(x) and the
    first deallocate message, OTMA CI posts the client's second
    request in error.
    
    Since this is synclevel syncpoint, the deallocate message is
    meaningless and should be ignored.
    

Problem conclusion

  • GEN:
    KEYWORDS:
    
    *** END IMS KEYWORDS ***
    DFSYOMSG has been modified to ignore the deallocate message
    for synclevel syncpoint.
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    PM74636

  • Reported component name

    IMS V11

  • Reported component ID

    5635A0200

  • Reported release

    100

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-10-09

  • Closed date

    2012-11-16

  • Last modified date

    2012-12-04

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

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

    PM76119 UK83586

Modules/Macros

  •    DFSYOMSG
    

Fix information

  • Fixed component name

    IMS V11

  • Fixed component ID

    5635A0200

Applicable component levels

  • R100 PSY UK83586

       UP12/11/21 P F211

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.



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

IMS

Software version:

100

Reference #:

PM74636

Modified date:

2012-12-04

Translate my page

Machine Translation

Content navigation