When 'chlickey' is used to apply a new 5051 key, set the Threshold parameter to *USGLMT

We use the HMC command line command 'chlickey' to apply new IBM i License Keys.  Darn handy that, because I can script that to happen for every partition on a server!  More better still yet, I don't need to sign on to all those partitions! Sweet!  Given these are all customer partitions in our cloud, this saves us HOURS of opening console sessions and our password keeper and getting a profile and password to acces the system.  Most unfortunately, use of chlickey to apply the key, resets the THRESHOLD parameter to *CALC! Please leave this setting at *USGLMT.

This will be an even bigger deal come March as licenses will no longer be perpetual> Since the THRESHOLD parameter is set to *CALC, every partition on the system instantly begins to complain that the processor usage is nearing the limit.  In our cloud environment that generates a host of trouble tickets from customers thinking we're cheating IBM. 

THAT in turn requires us to go through the process of opening console sessions, and our password keeper, and getting a profile and password to access every the system. Then WRKLICINF and changing the limit back to *CALC.  Well, here's the thing:  if I gotta do THAT 80 or more times, I might just as well add the license keys in the console as well!.  Thus this problem effectively makes the chlickey command at the HMC, pointless!