=====================================================================================================================================
3.3	limit (Only support Intel and AMD platform)

	abstract: Power limit management command.
			
	usage	: java -jar GbtUtility-2.1.76.jar [options] limit <get | activate | deactivate>

	<get>		: Get target node power limit configurations. (no rest args)
	<activate>	: Activate target node power limit. (no rest args)
	<deactivate>	: Deactivate target node power limit. (no rest args)

	usage	: java -jar GbtUtility-2.1.76.jar [options] limit <set> <walts> [action] <correction> <sample>
	<set>		: Set target node power limit configurations.
	<walts>		: The maximum limitations of power (Unit: Walts)
	[action]	: Execute the exception action when power range out of limitation.
			  The default is set to "No actions".
		<no>	: No actions
		<off>	: Hard Power Off system & log event to SEL
		<log>	: Log event to SEL
	<correction>	: Correction time (milliseconds)
	<sample>	: Sampling period (seconds)

	Example	:
		  by node list (default) : java -jar GbtUtility-2.1.76.jar limit set 220
		  by node list (default) : java -jar GbtUtility-2.1.76.jar limit set 220 no
		  by node list (specified) : java -jar GbtUtility-2.1.76.jar limit -L ./nodelist set 200 off
		  by node list (specified) : java -jar GbtUtility-2.1.76.jar limit -L ./nodelist set 210 log 6000 3
		  by single host : java -jar GbtUtility-2.1.76.jar -H 10.1.27.79 limit get
		  by single host : java -jar GbtUtility-2.1.76.jar -H 10.1.27.79 limit activate
		  by single host : java -jar GbtUtility-2.1.76.jar -H 10.1.27.79 limit deactivate
		  by scan host	 : java -jar GbtUtility-2.1.76.jar -S rmcp,10.1.27.1,10.1.27.150 limit deactivate
		  by scan host	 : java -jar GbtUtility-2.1.76.jar -S rmcp,10.1.27.1,10.1.27.150 limit set 210 log
=====================================================================================================================================