As for your first question, are you certain that you are connecting to
the mainframe? Could it be that you are connecting locally?
Larry E.
zgh1970 wrote:
> Hi, All,
> I have question on DB2 CONNECT configure.
> We installed DB2 ESE V8 FixPak 14 o AIX .
> When we set up the connection to DB2 Mainframe.
> We just catalog node and DB directory without DCS.
> From what I know, DB2 conenct needs to set up node, dcs and db
> directories.
>
> Why DB2 CONNECT can connect to DB2 mainframe without the DCS?
>
> Another issue on the Sysplex sup****t on the above db2 connect
> configuration.
> We have set DB2CONNECT_IN_APP_PROCESS=NO ,
> But i can still see reroute.
> I checked IBM http://www-1.ibm.com/sup****t/docview.wss?uid=swg21253021
> It has the difference on DB2 Connect and gateway.
> Is my above set is gateway or DB2 Connect?
>
>
> In case the client applications are running locally on the same
> physical machine as DB2 Connect, you need to set
> DB2CONNECT_IN_APP_PROCESS=NO to force the local clients to run in an
> agent so as to utilize Sysplex sup****t.
>
> db2set DB2CONNECT_IN_APP_PROCESS=NO
>
> db2stop
>
> db2start
>
>
> However, if you want to disable DB2 Connect Sysplex sup****t on your
> gateway, you can simply catalog a DCS database without specifying the
> Sysplex in the parameter list and re-catalog the DCS database as your
> database alias. You can also turn off Sysplex in V8 by setting the DB2
> registry variable DB2SYSPLEX_SERVER to zero, but this variable is
> deprecated in DB2 Connect V9. By default this variable is set to a
> nonzero value in DB2 Connect V8.
>
> thanks,
>


|