thanks for your fast reply. I fixed this but I get the same error.
I now tested this with a standard db2 pluging configuration and it's working fine.
But I have another configuration here:
The customer wants to snapshot 4 dbs at the same time so I quiesce them serially, take a snapshot and unquiesce them again.
So I have a configuration for each database containing the db2 (un)quiesce command (db2 plugin), and one main configuration file with the filer logon and volumes. The main configuration calls each db2 configuration by e.g command
Yeah I didnt understand that there was two systems involved until I saw the use of the CMDs and your configs.
This is a really cool feature of SC where you can run CMDs in different places but unfortunately not well documented, we will fix that.
In addition the one thing I didnt tell you is there is a third location you can run CMDs CLONETARGET the CLONETARGET acts as a second agent SC_CLONE_TARGET and is used mostly for cloning applications but you can also use it to fire CMDs, just an FYI in case your setup requires talking to a second host.
In SC 4.0 you can send CMDs to any agent so this is only getting better