Even though DB2 reports that a bind was successful for a remote AIX
package it is still possible to receive a -805 when an attempt to
connect to that server is attempted.  Without the bind option
SQLERROR(CONTINUE) it's possible for DB2 to report that the bind was
successful but if the DBA queries the system tables the package will not
be there.  The reason that SQLERROR(CONTINUE) is needed is the SAS91
DBRM includes the ASSOCIATE and the ALLOCATE commands.  These commands
are for the bulkload capability on Z/OS.  However, these commands do not
exist on AIX and thus will result in an error in the bind since they are
found in the DBRM.  SQLERROR(CONTINUE) tells DB2 to continue creating
the plan even though these 2 statements failed.  Since those statements
will never be used on AIX it's not a problem.

Without SQLERROR(CONTINUE) DB2 may give the following but the package is
not really there:

  BIND PACKAGE(CDWT.SAS91)    MEMBER(SAS91) ACTION(REPLACE)
  ISOLATION(CS) VALIDATE(BIND)    DEGREE(ANY) RELEASE(COMMIT)
  LIBRARY('SYS6.SAS.R9TS1M0.DBRM')
  DSNT270I  DB1T THE FOLLOWING SQLCA INFORMATION WAS RETURNED FROM
  SQLRABND
            SQLCODE  = 20
            SQLSTATE =
            SQLERRMT = STRDEL DECDEL RELEASE
            SQLWARN    0= ,1= ,2= ,3= ,4= ,5= ,6= ,7= ,8= ,9= ,A=
  DSNT271I  DB1T THE FOLLOWING SQLCA INFORMATION WAS RETURNED FROM
  SQLNQ6A8
            SQLCODE  = -20230
            SQLSTATE = 42601
            SQLERRMT =
            SQLWARN    0= ,1= ,2= ,3= ,4= ,5= ,6= ,7= ,8= ,9= ,A=
            STATEMENT= 544
  DSNT271I  DB1T THE FOLLOWING SQLCA INFORMATION WAS RETURNED FROM
  SQLNQ6A8
            SQLCODE  = -20230
            SQLSTATE = 42601
            SQLERRMT =
            SQLWARN    0= ,1= ,2= ,3= ,4= ,5= ,6= ,7= ,8= ,9= ,A=
            STATEMENT= 555
  DSNT232I  DB1T SUCCESSFUL BIND FOR
            PACKAGE = CDWT.SAS91.SAS91.()
  DSN

Operating System and Release Information