Read these instructions completely before you begin.
This document provides specific instructions on how to convert Robot Save using the HelpSystems Product Loader. For general information about the HelpSystems Product Loader, see “Using the HelpSystems Product Loader.”
Robot Save must be at R11M00 or higher to convert to Robot Save 12. If the current release of Robot Save on your system is below this level, update Robot Save before attempting the conversion.
Converting to Robot Save 12 preserves your Save SAVE license code.
The Robot Save conversion process creates or changes two user profiles: RBTUSER and RBTADMIN. These profiles were created for the following reasons:
They satisfy requests from corporate auditors that our objects be owned differently from IBM objects.
They allow us to build a secure product for your environment.
They isolate the Robot products from IBM changes to the QPGMR or QSECOFR profile defaults.
Note: If you’ve made any manual changes to the RBTUSER or RBTADMIN user profiles or their authorities, these changes will be lost with any product installation or conversion.
IBM Media and Storage Extensions (MSE) are required for Robot Save 12 to work properly.
Before loading Robot Save, we check if RBTSYSLIB needs to be updated. If it does, you’ll be asked to bring down the subsystem RBTSLEEPER. This ends all Robot products running on your system. When the update completes, the subsystem will restart automatically.
When you’re finished, read the After You Are Done section for additional information.
Use the following checklist to help you plan for your conversion. Some items must be done right before you start the conversion; others can be done up to several days in advance. If you can answer “Yes” to the question in the first column, read the instructions in the second column. If you answer “No” to the question, skip to the next question. By taking the time to prepare your system, your conversion to Robot Save 12 should proceed smoothly.
|If you answer Yes to this...||Read this...|
Do you use other Robot products with Robot Save?
For other Robot products to work properly with Robot Save 12, they must be at the following release/modification levels or higher. Update these products on your system before converting Robot Save.
Do you have libraries on your system from previous upgrade or conversion operations?
If any of the following libraries exist, delete them by entering the appropriate commands before starting the conversion:
If you have any questions, contact Technical Support.
Is the system you are converting in a data center?
You will be required to end the Robot Save monitor jobs. See the Robot Save User Guide for information on ending these jobs.
Do you mirror Robot Save libraries?
Call Technical Support before starting the conversion.
Have you placed objects or data in your Robot Save libraries?
The conversion will not copy or move objects you have placed in RBSPGMLIB or RBSDTALIB. Save these objects before converting.
Do you have RBSPGMLIB, RBSDTALIB, or RBSTMPLIB in the system value QSYSLIBL?
Remove the libraries and IPL your system before beginning the conversion.
Have you modified any Robot Save parameter values by calling the program RBS900?
The conversion preserves any changes you have made.
Do you have personal programs or Robot Schedule jobs that use Robot Save commands or programs?
Robot Save sometimes requires adjustments to variable lengths or parameter changes in your programs. You also might need to recompile your programs if you make changes after converting Robot Save.
Have you modified the Robot Save job descriptions RBSJOBD or RBSARCHIVE?
The job descriptions will be changed to the default values during the conversion. Make a note of any changes you have made. You must re-enter them after the conversion has completed.
Are there Robot Save jobs that have not completed or are waiting in the job queue (for example, archive jobs)?
Make sure all Robot Save 11 jobs have completed before starting the conversion. If there are incomplete archive jobs in a job queue, run them before converting. If you need to resume a backup that was run in version 11, do so before converting to Robot Save 12. You cannot resume save jobs run in a previous version after converting to Robot Save 12.
Do you currently use an IBM automated media library (AML) with Robot Save?
After the conversion completes, run the RBSAMLLRN command to inventory the tapes in the IBM AML. See the Robot Save 12 User Guide for complete information on setting up your AML in Robot Save 12.
|Do you currently use the PC Backup feature with Robot Save 11?||For Robot Save 12, the PC Backup feature has been removed. As a result, the conversion process will not complete until any Robot SAVE Backup Sets defined for PC Backup have been removed. The pre-conversion checker program will indicate whether PC Backup-type backup sets exist.|
Before you load Robot Save, you can run a pre-checker to determine whether or not the load will complete successfully. To run the pre-checker, do the following:
Use the "Converting Robot Save" instructions to download everything to your PC.
When you reach the Product Load Options panel, select Staged Load (step 5b below) and wait until the processing completes.
On the IBM i, execute the following command to display the Work with Loads panel:
Enter option 2, Run pre-checker, next to the Load Name for Robot Save and press Enter.
Review the information on the Pre-check Install Save 12 panel. Select *UPGRADE for the conversion, then press Enter.
Note: A pre-checker automatically runs during the first part of the Robot Save conversion process, but we recommend you run it in advance to identify any potential problems before attempting a full conversion.
The Robot Save conversion process downloads everything to your PC and transfers the objects to the IBM i. This process is described in the following section.
Download the Robot Save installer (setupSave12.exe) from My Downloads page on our website. Double-click it to start it.
On the Choose Components panel, select which components you want to load. You can choose the Manuals and the Software for IBM i. Click Next.
If you’re only installing the manuals, the process completes and the installer closes. The manuals were installed at the following location, and you can skip the rest of these steps.
C:\Program Files (x86)\Help Systems\Robot SAVE 12\manuals
If you’re loading the Software for IBM i (with or without the Manuals), continue to step 4.
On the Choose a Destination IBM i panel:
Select or enter the IBM i where you want to load Robot Save.
Enter a user profile and password that’s a member of the user class *SECOFR and has at least the following special authorities: *ALLOBJ, *SECADM, *JOBCTL, and *IOSYSCFG. The user profile should have Limit capabilities set to *NO. This profile will be used to restore and copy objects, and for product maintenance on the IBM i.
(Optional) In the Advanced Settings section:
Enter a port number or use the arrows if you want to change the FTP port number to something other than the default of 21.
Select Secure File Transfer if you want to use FTPS (FTP over SSL) during the file transfer. The default FTPS secure port is 990, but it can be changed to the required secure port for your environment.
In the Timeout (seconds) field, enter the number of seconds the session should be kept active during an FTP transfer. You can choose anywhere between 25 and 1800 seconds (30 minutes).
Note: If the transfer takes longer than the amount of time specified, the session will expire.
You have two options on the Product Load Options panel:
Click Immediate Load if you’d like to load the product on the IBM i now.
Note: This ends Robot Save until the product load completes. After you are done, we’ll restart the product.
Note: See “Loading Staged Objects on the IBM i” below for instructions on how to load the staged objects on your selected IBM i system.
The Product Load Progress panel for Robot Save launches. When the processing is complete, you have two choices:
If this is the only conversion of Robot Save that you're doing, click Finish.
If you have conversions to do on other IBM i systems, click Restart. Then, return to step 4.
Note: If the Product Load Progress panel ends with an overall Failed message, the product upload could not complete properly. To find the reason the upload failed, click View Logs and review your logs. You can also use Download at the top of the logs to save the information for future review.
If you chose to stage your objects during step 5b of the conversion process, do the following to manually load them on the IBM i you identified above.
Execute the following command to make sure no users are signed on to the product you’re converting:
WRKOBJLCK OBJ(RBSPGMLIB) OBJTYPE(*LIB)
Back up the Robot Save libraries using the following command:
SAVLIB LIB(RBSPGMLIB RBSDTALIB RBSPCBLIB RBTROLLIB RBTSYSLIB) DEV(TAPxx) VOL(*MOUNTED) ENDOPT(*REWIND)
Note: Make sure all objects from the libraries are saved.
Execute the following commands in the order shown:
Important: You must run the following command when no tape or save commands are running interactively or in batch:
Execute the following commands to remove the libraries from your library list:
Make sure that RBSPGMLIB, RBSDTALIB, and RBSTMPLIB are not in the system library list.
Make sure that no active jobs have locks on RBSPGMLIB, RBSDTALIB, or RBSTMPLIB. Enter the following commands to check for object locks:
WRKOBJLCK RBSPGMLIB *LIB
WRKOBJLCK RBSDTALIB *LIB
WRKOBJLCK RBSTMPLIB *LIB
WRKOBJLCK RBSPCBLIB *LIB
Execute the following command to display the Work with Loads panel:
Enter option 1, Load, next to the Load Name for Robot Save and press Enter.
After the conversion completes, execute the WRKSPLF command to check the spooled files for any errors that may have occurred. If you have any questions, contact Technical Support.
To access the product’s Main Menu on the IBM i, execute RBO on a command line to display the Robot Automated Operations Solution panel. Then, enter option 13 for Robot Save.
You can access the Robot Save User Guide and other documentation from our website.
The conversion process restored the following three Robot Save libraries: RBTSYSLIB, RBSPGMLIB, and RBSDTALIB.
If you use Robot Network and the system you just converted is a host system running Robot NETWORK 10, manually delete the Robot Save Product Master library, RBNRBSMST.
If you want to initialize volumes outside of Robot Save using the INZTAP CHECK(*NO) VOL(*MOUNTED) command, you must change the Allow blind initialization field on the Robot Save Media Defaults panel. Robot Save does not allow this type of volume initialization. See the section on media defaults in the Robot Save User Guide for complete information.
If you previously modified the Robot Save job descriptions RBSJOBD or RBSARCHIVE, re-enter those changes.
Three libraries were restored to your system for use during the conversion process: HSLOADMGR, HSLOADMGRW, and RBTCDRLIB. We don't remove them from your system in case you're doing multiple conversions. You can delete them when you're finished.
Note: You can move the library HSLOADMGR to a different system on the IBM i and use it to complete additional conversions. For more information, see “Using the HelpSystems Product Loader.”
As of operating system level V6R1, and if you plan to use the Robot Save Restricted State Utility (RSU), be aware that the default behavior of the Power Down System (PWRDWNSYS) command has changed. The default value (*ENVVAR) for the CONFIRM parameter on the PWRDWNSYS command displays a confirmation window. This causes the 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)
For backup set types A, 6, 7, 8, and 9, the libraries saved are no longer listed on the Items to be Saved panel in the backup set setup. Items are listed on the panel only if the Save code is NO (Item should be omitted) or EXT (files in the library are set to be reorganized).
Still have questions? We can help. Submit a case to Technical Support.