When Solution Enabler issues commands against your box can use different syscalls with different parameters. Some of them needs the full list of symdevs to manage (split/resume/failover/failback/establish/whateveryouwant). Some other needs ranges of symdevs.
With SYMAPI_SYSCALL_RANGES_HEURISTIC you can enable "range syscalls" that will speed up command execution. But if you have a binfile with holes (non contiguous symdevs) syscalls may fail with strange and exotic errors. That's why you can always disable heuristic ranges and use good old "lists" of devices. Slower, but reliable
It would be helpful to know what it is you're trying to do, and what the current device configuration is.
Each Symmetrix device has 4 "mirror positions". A standard mirrored device uses two of these (one for each copy).
SRDF uses an additional mirror position (on both the R1 & R2), so our device is now up to 3. Establish a BCV and all 4 mirror positions are used. This means a second concurrent BCV or RDF volume cannot be established, since there's nowhere for it to go.
A traditional hotspare also takes up a mirror position whilst invoked, so a mirrored RDF volume with a spare invoked cannot then have a BCV established since there is no free mirror position.
You can use "symdev show <Vol#>" to see what's in the mirror positions, you'll get something like:
If I have a volume in a failed disk, and this volume have already it's 4 mirror possitions occupied by SRDF, TF/Mirror operations, etc, can there be any problem while invoking the Hotspare operation?
Symm devices only have 4 available mirror positions so if all 4 mirror positions are currently in use a hot spare will not invoke.
Lately the Hotspare scripts are taking very long in my platform, 12+ hours to finish sync. Is this normal, or could the lack of mirror possitions be affecting this operations?
Reads and writes from the host take priority over a hot spare syncing. There are many variables as to why a hot spare could be taking a longer time than suspected to sync up. You mention TF/Mirror, are you also currently doing BCV operations at the same time that the hot spare is syncing?
Looking for: - A way to see / visualise how many mirror positions are in use. - Clarification if TimeFinder Clone volumes occupy one of the 4 mirror positions (or not). - Clarification if free mirror position(s) are needed to use SymOptimizer
If you have a few spare minutes don't forget introducing yourself in coffee break area..
1) a way to see/visualize how many mirror position are in use.
Just issue "symdev -sid XXX show 0BAD" and look carefully at the output. Unfortunatly I can't show you an example output but I guess you can easily spot the required details. Or simply just post output of above command (assuming you want to know everything about your BAD device) and we'll help you in finding the details you need.
2) Clone won't ever use mirror positions. Fullstop.
3) I guess MikeMac will happily answer with plenty of details