II09391: ABEND04E RC00D3443B ON BIND FROM DB2/MVS AR TO DB2 COMMON SERVERAS (DB2/2 OR DB2/6000).

APAR status

• Closed as canceled.

Error description

• Search Argument: 5740XYR00 DB2 RC00D3443B BIND DB2/2 DB2/6000
  If DB2/MVS user is binding against DB2/2 or DB2/6000 v2.1.1 and
  if the user is using an unsupported BIND paramter, The user will
  get error code -4390 up on the host.  However, sometimes the
  user does not see -4390 but the following instead:
  
  DSNT500I ( DSNLXRCX RESOURCE UNAVAILABLE
             REASON 00D3443B
             TYPE 00001005
             NAME DTDBBS
  DSNT233I ( UNSUCCESSFUL BIND FOR
             PACKAGE = DTDBBS.SNYDERB.DSNTEP3.()
  .
  A DSNL031I message from DSNLXRCX0064 will appear at the console:
  DSNL031I ( DSNLZDJN DRDA EXCEPTION CONDITION IN 344
  RESPONSE FROM SERVER LOCATION=SUNDB FOR THREAD WITH
  LUWID=USIBMSY.SYUTEC8A.ACBCD45C7FCB=28
  REASON=00D3443B
  ERROR ID=DSNLXRCX0064
  CORRELATION ID=BNDTEPW
  CONNECTION ID=BATCH
  IFCID=0191
  .....................
  If the DB2/MVS user specifies an invalid BIND parm when creating
  package at a DB2/2 or DB2/6000 common server, they should get
  sqlcode -4930 and SQLERRMT that indicates the BIND parm this is
  in error. Apparently, after the application of IX54242, an
  invalid BIND parm causes a DRDA exception in the reply from the
  common server, and the user has no clear indication of the prob.
  Note that the underlying cause of the exception is simply an
  invalid BIND parm, but it will require DDCS trace to be able to
  tell which parm is in error (a readable error message is in
  ASCII in the trace). Will installation of IX57794, the user will
  again get the SQL errmsg text that enables most users to correct
  the BIND parms without placing a call to Tech Support.
  

Local fix

• If the customer has installed a servicepak recently or has a
  recent version of DB2/2 or DB2/6000 DRDA AS, then their BIND
  options should be checked by taking a DDCS trace or DB2 Global
  Trace Class(30) IFCID(180) to determine the bad BIND PARM.
  OR, it is better to get the IX57794 fix from Toronto and apply
  it and will be able to see which BIND option is in error.
  .
  The bug is circumvented by correcting the BIND options, but it
  can be quite difficult to determine the invalid option(s) due to
  the bug.
  

Problem summary

Problem conclusion

Temporary fix

Comments

• close for INTERNET viewing
  

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