II07054: SQL30080N 0003-00000005 FROM OS/2 TO DB2.

APAR status

• Closed as canceled.

Error description

• 5740XYR00 DB2DDF DB2DRDA1 DB2DRDA2
  User has successfully established a connection between OS/2 and
  DB2.  At the DB2 system, DDF is shutdown by using the STOP DDF
  MODE(FORCE) command or STOP DB2 MODE(FORCE) command,
  or DB2 crashes for some reason.
  DB2 and/or DDF is then restarted.
  When an OS/2 application is executed which accesses this DB2
  system, the application receives SQLCODE -30080 with 0003 and
  00000005.
  Example:
    SQL30080N  A communication error "0003-00000005" occurred
    sending or receiving data from the remote database.
  On the MVS console at the DB2 site, VTAM issues message IST663I
  with sense code 08090000 or 08050000 (if VTAM APAR 0Y55542 is
  applied).
  Example:
    IST663I CDTERM REQUEST FROM SY99CDRM RECEIVED,
     SENSE=08050000
    IST664I REAL OLU=USIBMSY.SYD2118A  REAL DLU=USIBMSY.SYUTEC6A
    IST889I SID = E1C7F60419091EC9
    IST891I USIBMSY.SYUTEC6 GENERATED FAILURE NOTIFICATION
    IST893I ORIGINAL FAILING REQUEST IS BIND
    IST314I END
  In order to correct the problem, the user must reboot, or
  restart the OS/2 Comm Manager, or force a CNOS via Comm Manager
  screens, or have DDF do AUTOCNOS back to OS/2 when DDF starts.
  
  The problem occurs because OS/2 CM did not realize that DDF
  went down. Therefore, after DDF is restarted, OS/2 CM does not
  realize that it must drive CNOS to DB2.  So OS/2 CM just
  attempts to allocate a conversation which causes VTAM to issued
  IST663I with sense code 08090000.  Users may also receive
  IST663I with sense code 08050000 if VTAM APAR OY55542 is
  applied.
  
  The fix is a coordinated effort with VTAM and OS/2 CM. VTAM APAR
  OY55542 should be applied which will cause VTAM to return
  sense code 08050000 instead of 08090000.
  OS/2 CM APAR JR06063 should also be applied which recognizes the
  08050000 sense code and realizes that CNOS must be done before
  conversations can be allocated.
  *****************************************
  Additional symptoms and keywords:
    SQLCODE30080 SQLCODE30080N 30080 RCPRI0003 RCSEC00000005
    SENSE08050000 SENSE08090000
    MSGIST663I MSGIST663 IST663I IST663
  

Local fix

• One of the following may be done to correct the condition:
  1. Reboot OS/2 workstation.
  2. Stop and start OS/2 CM.
  3. Force a CNOS from Comm Manager.
     Go into Comm Manager ADVANCED, Subsystem Management,
     Session Services, Change APPC Session Limits.
       Enter the
         LU Alias (workstation LU name)
         Partner Alias (DB2 LU name)
         Mode name such as IBMRDB
       Hit enter
         On next screen, enter session limits and hit enter.
       This causes OS/2 CM to initiate session limit
       negotiation with DB2.
  4. Modify the DB2 CDB (Communications DataBase)
     SYSIBM.SYSLUMODES table to implement AUTOCNOS to the OS/2
     LU when DDF is started (this way DB2 will do the CNOS for
     OS/2 CM).
  

Problem summary

Problem conclusion

Temporary fix

Comments

• Closing informational APAR.
  

APAR Information

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

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

Fix information

Applicable component levels