For a specific customer, I added a basic cut-n-paste customization of a different bnapsql:// or osmsql:// query that that appends the final character of the fabric nickname to the hostname and the WWPN such that hosts in “XX_FAB_A” or “XX_FAB_1” or “XX_FAB_a” become appended with “_A”; “_B”, “_2”, or “_b” become appended with “_B”. Anything else gets a “_X”.

This is done using a protocol “msosmsql”, for example:

java -jar vict.jar --nickname=msosmsql://server/

or

vict.bat -N msosmsql://server/

or since the customer has non-standard password (and the -n to store the result)

vict.bat -N msosmsql://user:pass@server/ -n A:\VirtualWisdomData\DeviceNickname\bna.csv

This allows a single query to produce nicknames on a different schema; also highlights a non-portability in the code that can be improved… but this is in production today. The customer’s response was “oh, that’s it? I thought that would be more difficult. How anti-climatic…” How can “easier than expected” be bad?