Note for VCS DB2 agent to support 10.1, probably just means Symantec need to test it themselves, rather than change agent, but you can confirm this yourself as agent entry points are quite detailed for this agent which are:

About the online agent function for VCS agent for DB2

The agent uses the db2gcf program to start a DB2 instance or database partition.

The command is:

# su $DB2InstOwner -c "$InstHome/sqllib/bin/db2gcf -u -I\

$DB2InstOwner -p $nodenum"

This agent can also use the db2start command to start all DB2 partitions.

 

About the offline agent function for VCS agent for DB2

The agent uses the db2gcf program to stop a DB2 database partition. For a database

with only one partition, it stops the instance. The command is:

# su $DB2InstOwner -c "$InstHome/sqllib/bin/db2gcf -d -I\

$DB2InstOwner -p $nodenum"

The agent can also use the db2stop command to stop all DB2 partitions.

 

About the monitor agent function for VCS agent for DB2

The agent executes the

su $DB2InstOwner -c "$InstHome/sqllib/bin/db2gcf -s -I $DB2InstOwner -p $nodenum"

command to check the status of the database

partition or node number. If the exit status of the db2gcf command is 0, the

monitor returns the exit code 110. Otherwise, the monitor returns an exit code

of 100 and the resource is taken offline

 

About the clean agent function for VCS agent for DB2

The agent first uses the db2stop command with the force option. If the command

is unable to clean the agent function, the agent then uses the db2_kill script to

kill the instance. If the db2_kill script fails, the kill -9 command is invoked.

# su $DB2InstOwner -c "$InstHome/sqllib/bin/db2stop force

nodenum $nodenum"

 

So if the commands above have not changed from 9.1/9.5/9.7 for the new 10.1 version, then the agent should work, but if you used agent it would technically be unsupported until Symantec test it themselves

Mike

The DB2 agent guide says:

When an IMF-enabled agent starts up, the agent initializes the asynchronous

monitoring framework (AMF) kernel driver. After the resource is in a steady state,

the agent registers the details that are required to monitor the resource with the

AMF kernel driver. For example, the DB2 agent registers the PIDs of the processes

with the AMF kernel driver using its own imf_register function

and IMF is enabled by default, so if you disabled IMF, then the pid file MAY not be used.  To disable IMF use:

hatype -modify Db2udb IMF -update Mode 0

As the error is with the startup you could try using a different startup,so using StartUpOpt attribute set to CUSTOM or set UseDB2start to 1.  Then the online should work, but after the online is called it will call the monitor and the monitor according to docs just does:

su $DB2InstOwner -c "$InstHome/sqllib/bin/db2gcf -s -I $DB2InstOwner -p $nodenum"