If you are referring to the jdbc.custom.connection.properties within prpcUtils.properties you should generally never need to set this. This was added for Kerboros connectivity. You should only need to populate the first 6 properties under the "Connection Information" section and then whatever properties that are needed for the specific tool that you will be running.
Anyway, even if this option worked I would need a way to specify which connection in my connection.properties file to use. If this is supposed to work I'd love to know how...we're setting up deployment automation and being able to call prpcServiceUtils.sh with a target system and archive path parameter would be perfect.
Update: The prpcServiceUtils.sh usage displayed is incorrect, the parameter is --connPropFile
This was correct in the usage for prpcUtil.sh and it's also correct in the 7.2 help. I'll put in a bug report on that.
So now it accepts the connection.properties file and it seems to have targeted the system I put in that file rather than the one in prpcServiceUtils.sh. So is this intended to run the same action against multiple systems rather than to select between preconfigured targets?