A fix is available
APAR status
Closed as program error.
Error description
After DB2 DSNAIMS apar PK24556, customer using DSNAIMS SEND ( as opposed to SENDRCV ) call for CM0 async message and using different TPIPE names on separate invocations encounters DSNA317I and OTMA C/I RC4 RSN1(12) RSN2(0) RSN3(-1) RSN4(10). The reason is PK24556 changed DSNAIMS to specify a single session on the OTMA_OPENX call. This doesn't matter for CM1 processing since OTMA_CI will dynamically obtain sessions as needed, (up to 999 ) but for CM0 processing once a TPIPE name is associated with a session, that session cannot be used for a SEND with a different TPIPE name.
Local fix
Use a common TPIPE name for all DSNAIMS SEND ( ASYNC, CM0, SEND-only ) flows if possible.
Problem summary
**************************************************************** * USERS AFFECTED: All of IMS V10 customers using OTMA C/I * **************************************************************** * PROBLEM DESCRIPTION: OTMA C/I async calls failed when * * invoked by DSNAIMS stored procedures * **************************************************************** * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF * **************************************************************** OTMA C/I asyc calls, such as otma_send_async and otma_receive_async calls, cannot dynamically allocate free session blocks when the session limit is reached. In the case of DB2 DSNAIMS, the session limit was set to 1 and the session was used. The subsequent OTMA C/I asyc call tried to get a free session and failed.
Problem conclusion
AIDS: RIDS/SYS RIDS/CNTRL SYS CNTRL GEN: *** END IMS KEYWORDS *** DFSYOUSE module was enhanced to dynamically allocate a free session when the session limit is reached.
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
PK52490
Reported component name
IMS V10
Reported component ID
5635A0100
Reported release
010
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2007-09-07
Closed date
2007-10-10
Last modified date
2008-04-30
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK30363
Modules/Macros
DFSYOUSE
Fix information
Fixed component name
IMS V10
Fixed component ID
5635A0100
Applicable component levels
R010 PSY UK30363
UP07/11/02 P F711
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.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCVRBJ","label":"System Services"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
30 April 2008