How a Robot Save Save Works

This topic briefly describes each step in the process that Robot Save follows automatically when it saves a library or an object list. This process takes place after you have defined the backup class and set information. You can use this discussion to guide you in setting up Robot Save to do exactly what you want. The steps here follow the Robot Save Save Process diagram.

Execute the RBSSave command to start the save

If the RBSSave parameters for backup set and rotation are *NEXT, Robot Save determines the next set and rotation to be executed and proceeds with the save.

A Robot Save status message record is created for each backup set save session (see the Status Messages section for more information). The starting date and time are placed in the status record.

If you specified that you want to add undefined libraries to the backup set on the Extended Backup Set Information panel, Robot Save finds unassigned libraries and adds them, based on the criteria you specified on the System Defaults panel during system setup.

Execute the backup set before backup user program

If you have certain procedures that should be done before the save session starts, you can put them in a before backup user program and enter the program name on the Extended Backup Set Information panel. That program will be executed before the save session starts.

Terminate subsystems

Robot Save cannot save files that users or batch programs are using. To ensure that there are no file locks during the save process, have Robot Save terminate the user subsystems. Robot Save will terminate the subsystems specified for this backup set. Any jobs running in these subsystems will be ended.

Execute the library before backup user program (only if the library has files to reorganize)

If you have certain procedures that should be done before the save of a library starts, put them in a library before backup user program and enter the program name on the Extended Library Save Information panel. That program will be executed before the library save if files are to be reorganized.

A great use for this feature is to vary off workstations that might be using a library. Then, use a library after backup user program to vary them back on immediately after the library is saved. You can do this instead of terminating subsystems to minimize the downtime your users have to suffer.

If the library before backup user program is not executed in this step because there are no files to be reorganized, it will be executed at Step 7 or 11, as appropriate.

Reorganize files

At your option, Robot Save can reorganize a library’s files that exceed a certain percentage of deleted records. It’s important to save a journaled file immediately after reorganization because its journal records are worthless after reorganization. This option increases your save time, so files should not be reorganized on days you must minimize downtime.

Determine libraries to save to save files

Robot Save reads through the libraries to be saved by this backup set and selects the libraries that are to be saved to save files. Libraries with the following save codes are saved to a save file at this point:

SLSS SCSS SLSD SCSD SLSF SCSF

When Robot Save finds a library with one of these save codes, it executes Steps 7, 8, and 9 for that library. When no more libraries remain to be saved to a save file, Robot Save proceeds to Step 10.

Execute the library before backup user program

If the library before backup user program was not executed in Step 4, it is executed here. Let your imagination run with this function. There are many procedures you might want to do before a library is saved. Remember, no users should be using the library at this point.

Save the library to save file

When doing a save file operation, Robot Save creates the save file in a special library assigned to each backup class. Robot Save can save either entire libraries or just changed objects.

Execute library after backup user program

If you had a library before backup user program, the after backup user program should undo what the before backup user program did. For example, if your before backup user program varied off workstations, your after backup user program should vary them back on.

When the library after backup user program is executed, the save procedure returns to Step 6 to check for the next library.

Determine the libraries to save to tape

Robot Save reads through the libraries to be saved by this backup set and selects the libraries that are to be saved to tape. The libraries with the save codes “SL” and “SC” are saved to tape at this point.

When Robot Save finds a library with one of these save codes, it executes Steps 11, 12, and 13 for that library. When no more libraries remain, Robot Save proceeds to Step 14.

Execute the library before backup user program

See Step 7.

Save the library to tape

Robot Save does a normal save to tape with the following additional enhancements:

  • It intercepts all device messages and tells you what to do next, rather than giving you dangerous options.

  • It handles all the messages necessary for the unattended operation of the cartridge stacking mechanisms on magazine tape drives.

  • If you have Robot Alert, our optional paging software, Robot Save sends a pager message if a tape mount is needed or if the tape device jams.

  • It automatically records any scratch tape that you mount.

  • At your option, Robot Save tells you the proper volume to mount next and does not allow you to mount volumes out of order.

Execute the library after backup user program

See Step 9. When the library after backup user program is executed, the save procedure returns to Step 10 to check for the next library.

Start subsystems

Robot Save starts all subsystems that were terminated when the backup session started.

Save all the save files to tape

Robot Save reads through the libraries to be saved by this backup set and selects the libraries with save files that should be saved to tape. Libraries with the following save codes have their save files saved to tape at this point:

SLSS SCSS SLSD SCSD SF SFD

Delete all save files that should be deleted

Robot Save reads through the libraries to be saved by this backup set and selects the libraries with save files that should be deleted. Libraries with the following save codes have their save files deleted at this point:

SLSD SCSD SFD

Save Robot Save system restoration data

At the completion of a backup and restore class-type backup set, Robot Save automatically saves the library RBSDTALIB onto the last tape. This library contains the files necessary to print the system restoration instructions as of this save session. This lets you restore the RBSDTALIB and RBSPGMLIB libraries while Robot Save guides you through the restoration process.

Create Audit Report

The Robot Save status message record created for this backup set save session in Step 1 is updated with the ending date and time. Robot Save then creates the Audit Report. (You must schedule the save of RBSPGMLIB to save the object archive.)

Execute the backup set after backup user program

If you had a backup set before backup user program, the after backup user program should undo what the before backup user program did.

Create Object Archive

Robot Save submits a job to create the object archive, if one has been specified. Note: You must schedule the save of RBSPGMLIB to save the object archive.