OAM error testing DB2 8.1 New Function Mode

[LWagner]

We have been working with CMOD 8.4.0.3 on Z/OS 1.9, and DB2 8.1 in Compatibility Mode, without any errors.   To begin the DB2 migration to version 9.1, the DB2 specialist must first move to DB2 8.1 New Function Mode.  The initial test failed with an OAM access error, as shown below:

ARS0024E SACLWAG OBJECT >13QPNCD< IN APPLICATION GROUP >JNB< NOT FOUND  489 IN NODE >OD390PRD<  SRVR->MF-DR.LADWP.COM 10.150.88.8<-ARS0020E SACLWAG SM ERROR: ARSZDOCG: 00000017(00000010) OAM ERROR:  490 FUNCTION= ACCESS   RETURN CODE= 0000000C REASON-CODE= 60000102, RC=23, REASON=0, FILE=ARSSMSMS.CPP, LINE=928  SRVR->MF-DR.LADWP.COM 10.150.88.8<-

Is any one using DB2 8.1 New Function Mode, or DB2 9.1, with CMOD 8.4.0.3 or higher ?

[Ed_Arnold]

A quick search of the IBM site gives this technote which at the end which says that OTIS was probably not started.

http://www-01.ibm.com/support/docview.wss?uid=swg21002929

Would that be the problem?

Ed

[LWagner]

   Yes, it did turn out to be OTIS not started.  But the thing is, we have never manually started OTIS before.  I went through my usual startup sequence, but that was after DB2 8.1 was bought up in New Function Mode, rather than Compatibility Mode.

We are wondering about the connection.

[LWagner]

Turns out we also needed to run two binds also, one which needed two lines added to it:

<<new>>       BIND PACKAGE (DSNACLI) MEMBER(DSNCLINF) SQLERROR (CONTINUE)

BIND PLAN(DSNACLI)
 <<new>>            *.DSNACLI.DSNCLINF             -