It would help to mention which specific Solaris Cluster and Solaris version you are using.
The error message you cite is only the tail - the complete message would help. And you should also look into messages in /var/adm/messages on all cluster nodes.
It would also help to see the specific content of the sctomcat_config file that you used for registration.
The error message sort of suggests that you tried to create a resource with name "SUNW.gds", which won't work.
SUNW.gds is a resource type provided with Solaris Cluster. The HA Tomcat data service is implemented as a SUNW.gds resource.
As such you typically register the SUNW.gds resource type with:
clrt register SUNW.gds
The sctomcat_register script does all the required step to then create the SUNW.gds based HA Tomcat resource.
Typically you place the parameter file either on a global file system, or on a failover file system (ie. a file system managed by SUNW.HAStoragePlus) residing in the same resource group as your HA Tomcat resource.
I am not sure if by "\bin" you really meant /bin - in which case that would not be a good place for the parameter dir.
Within HAS_RS you specify the resource name for the SUNW.HAStoragePlus resource that manages the corresponding file systems you use with tomcat.
The sctomcat_register script does then set the correct resource dependencies.
Take a look at a specific deployment example (ie. http://docs.oracle.com/cd/E23623_01/html/E26824/gchqi.html#scrolltoc) to see the flow of a specific configuration.
Thank you for your help. Sorry, I was in a rush and felt a little frustrated since I was having trouble making it work. I actually got it working. I am running 3.2 and using the 3.2 deployment guide.
I only had to remove the value in the HAS_RS field in the sctomcat_config file and it successfully registered the resource.
It is working I just need to figure out the correct action for the probe to execute and the correct return string to look for so clustering doesn't ping pong