Creating an RSU Command Stack

Set up a Robot Schedule job scheduled to run at a later time and enter the RSU command stack. The console waits until the Robot Schedule job starts and issues the command stack, then begins the restricted state utility work. Use the following commands to create an RSU command stack. Press F1 from any command screen for detailed help.

RBSRSUSTR

The RBSRSUSTR command directs the console to put the system into a restricted state. This command defines how the system will be ended: it ends jobs, warns users that the system will be ending, manages errors that may occur, and uses Robot Alert to page the appropriate person should a problem arise.

RBSRSUCMD

Use the RBSRSUCMD (Robot Save Restricted State Utility Command) command to specify the command you want to run while the system is in the restricted state. If you want to run more than one command while in the restricted state, enter a separate RBSRSUCMD command for each. The commands are run in the order they were entered. Note: The commands you enter on the RBSRSUCMD command can be any command that requires a restricted state, for example, RGZPFM or RCLSTG.

RBSRSUEND

The RBSRSUEND command signals the utility that it has received a complete set of commands. The parameters on this command specify how to restart the system (end the restricted state) when RSU completes its work.

Note to V6R1 (IBM i 6.1) Users: The default behavior of the Power Down System (PWRDWNSYS) command has changed. The default value (*ENVVAR) for the CONFIRM parameter on the PWRDWNSYS command now displays a confirmation window. This will cause the Robot Save Restricted State Utility (RSU) to halt and wait for a confirmation before performing the IPL.

Enter the following command on a command line to permanently bypass the confirmation window on the PWRDWNSYS command:

ADDENVVAR

ENVVAR(QIBM_PWRDWNSYS_CONFIRM)

VALUE(*NO) LEVEL(*SYS)

Note: The RBSRSUSTR, RBSRSUCMD, and RBSRSUEND commands must be entered together to create an RSU command stack.