Are there any drawbacks to using the colon-separated list for redundancy?
Yes. By default, once an application has successfully checked out a license from one host, all subsequent checkouts must be satisfied from the same host. If the application requires more than one FEATURE, then this could result in a license denial when the license may be available on another server. An application can bypass this restriction with the use of multiple FLEXlm `license jobs’, but in practice, few applications do at this time. If the application supports license queueing, all licenses are only queued from the first host on the list.
