This procedure describes how to run a Robot Schedule job for Robot Save while in restricted state:

  1. Create a backup Class/Set that will perform a set type 9 backup.

  2. Schedule the job manually in Robot Schedule and use these commands: RBSRSUSTR, RBSRSUCMD, & RBSRSUEND.

  3. Prompt each command to enter parameters.

    • In the RBSRSUSTR command, identify the message queue for Inquiry to page as RSUQ in library QTEMP.

    • In the RBSRSUCMD command, enter RBSSAVE command and press function key 4 to prompt the command. Enter the Backup Class and Set name. Make sure the spelling is correct or the save will not run.

    • In the RBSRSUEND command, there is an option to choose to specify an IPL.

    • In Robot SCHEDULE, confirm that the job description is RBSJOBD in library RBSPGMLIB on the Control Options panel. Also confirm the job queue will be available when it is needed to run the RSU job.

  4. Put the system console in ready mode with these steps:

    • Sign on as a user who has "save all" authority and make sure that the libraries RBSPGMLIB, RBSDTALIB, and QTEMP are in the library list.

    • Then enter the command RBSRSURDY. The Robot Save Restricted State Utility At Work panel displays. Now leave the console alone. The console is now ready and constantly checking for the Robot Schedule job's commands to begin the RSU save. The RBSRSURDY command can be entered hours or days before the Robot Schedule job runs, as long as no one signs on to the console.

Note: The Robot Schedule job submits the command stack at the scheduled time, and the commands go to the message queue for the system console job. The Robot Schedule job completes immediately as its only function is to submit the commands.

The RBSRSURDY command monitors the designated message queue for messages. When the messages in RBS1041Q in library RBSPGMLIB are found, the RSU backup starts processing. There is no way to schedule the RBSRSURDY command.



Still have questions? We can help. Submit a case to technical support

Last Modified On:
You don't have the appropriate permissions.
No, open a new Support Case