DSK MANAGER. For IBM iseries and AS/400. Version Last Updated September Kisco Information Systems 7 Church Street Saranac Lake, NY 12983

Transcription

1 DSK MANAGER For IBM iseries and AS/400 Version 5.01 Last Updated September 2002 Kisco Information Systems 7 Church Street Saranac Lake, NY Phone: (518) FAX: (518) Support@Kisco.com Website: , 2002 Kisco Information Systems

2

3 Table Of Contents Introduction...1 Overview...1 Installation and Security...4 OS/400 Compatibility...6 An Approach To Backups...7 Recommended Plan...7 Backup Override Codes...8 Synchronized Application File Groups...9 Performance Issues...9 Main Menu...11 Backup Menu...13 Master Data Backup...15 Incremental Data Backup...18 Library Program Backup...21 OS/400 Level Compatibility...24 Data Dictionary Backup...26 Document/Folder Backup...28 Application Group File Backup...30 Add User Save Set to Status File...32 Using Non-Standard Tape Densities...33 Handling Tape Errors...33 Restore Menu...35 Review Backup Sets...37 OS/400 Object Search...38 Restoring From Set Review...39 Folder Backup Review...41 IFS Backup Review...42 Backup Set Restore...44 Generalized Restore Procedure...46 Restoring Configuration Information...52 Maintenance Menu...54 Description File Update...56 Defining Application Codes...60

4 List Options...62 Disk Analysis Menu...63 Report Descriptions...68 Disk Tools...72 Delete Old Objects...74 Off-Line Archive Functions...77 Off-Line Archive Menu...78 Save Off-Line Archive To Tape...80 Move any object into Off-Line Archive Library...82 Move any file member into Off-Line Archive Library...83 Tape Management Functions Menu...85 Review Tape Library Status...87 Register New Tapes...88 Automatic Tape Scratch Report...91 Install Menu...92 Display installation status...94 Change installation status...96 Print documentation...98 Process Kisco PTF Package...99 Set Backup Performance Values Software Support Policies Contact Information Support on the World Wide Web...104

5 1 Introduction The disk drives on your iseries-as/400 are crucial to the success of your data processing installation. If they are not backed up on a regular basis, you run the risk of losing important data and programming if you suffer the loss of a disk drive. If your disks accidentally fill up to capacity, your computer could come to an unplanned (and unwanted) halt causing processing delays. DSK MANAGER for your iseries-as/400 is a set of program utilities for managing the disk on your iseries-as/400. These utilities include programs for backing up your iseries-as/400, utilities for restoring your backups, utilities for analyzing how the disk is being used and utilities for keeping track of your tape library so backup information can be found quickly and restored quickly. Each utility is designed to help you, as the manager responsible for data processing, to control the use of your disk space and be prepared for all possible problems. During your free thirty day trial of the software, we encourage you to try all of the features. Each is different and provides a different management tool for your use. Overview The utilities in DSK MANAGER are divided into several areas. There is a set of utilities specifically designed to help you with backing up your system. Another helps you to restore data and program objects from you backup tapes. Another set helps you with keeping track of your tape library and the backups that are located in the library. Another is for managing the way information and programs are stored on your computer. The Backup Utilities: DSK MANAGER implements a smart approach to disk backup on your iseries-as/400. Each object on disk is classified by DSK MANAGER into one of two types. These are: DATA objects PROGRAM objects By making this distinction, DSK MANAGER can save these objects on different schedules. DATA objects should be saved on a more frequent basis than PROGRAM objects. DSK MANAGER allows you to do this. DSK MANAGER includes Master and Incremental backup. Data objects can be saved weekly with a Master backup run. Then, on a daily basis, Incremental backups can be run. Incremental saves will only backup those files that are new or have changed since the last Master backup run.

6 2 DSK MANAGER also includes the ability to save Synchronized Application File Groups. These are groups of related data file objects that, due to application requirements, must be all saved together. DSK MANAGER includes the support that allows you to define permanent application file groups. It also allows you to save them by use of a single command. Support for these file groups is also built-in to the Master and Incremental backups. The Master backup allows to you save all synchronized application file groups at the start of the backup run or at the end of the run. The Incremental backup will save only those synchronized file group where changes have occurred. If any single file in a group has changed, the entire file group will be saved. All file group saves in the Incremental save happen at the end of the backup run. DSK MANAGER also implements the ability to save DATA objects concurrent with normal processing. During a data object backup, if a file is found to be in use, DSK MANAGER goes ahead and saves that file anyway. It does so by using one of two different methods that you can control. The default is our "Shadow copy" copy method. This method creates a temporary copy of the file on disk. DSK MANAGER then saves the copy as if it were the original. An alternate method you can choose is IBM's "Save While Active" feature. Using either of these methods, most files can be saved while your users are active on the system. Using the Shadow copy method, some files may not be saved while in use because they are allocated exclusively to your application. When this happens, the files that are bypassed are automatically included in the next Incremental backup run. DSK MANAGER also provides control over the backup process by use of Backup Override codes. These codes are established on a file by file basis. Using a backup override code, you can tell DSK MANAGER to Never save a file, Skip a save if the file is in use and a variety of other overrides. This gives you control over the save process for files that must be synchronized at backup time. You can also vary the method used to save files that are in use on a file by file basis. Another code on the same file allows you to select an alternate method. The default method is established on a systemwide basis. Restore Utilities: DSK MANAGER includes several different ways to restore objects that have been saved using the Backup Utilities. Whenever DSK MANAGER creates a backup set, it logs the details of what was saved to a master file. You can review this master file of backup information and selectively restore individual objects directly from the review screen. For disaster recovery purposes, DSK MANAGER also includes a utility that will simply restore an entire backup set, provided that backup set was created by one of the DSK MANAGER backup utilities. This provides for a thorough and quick restore of backup objects to your system to get you back up and running quickly.

7 3 Tape Library Management: The tape management features help you keep track of what information is in your tape library. Whenever a backup operation is performed by DSK MANAGER, the results are logged into a history file. With this feature, you can keep track of individual tape volumes in your library. At any point in time, you will be able to check a specific tape volume to see what it s current status is and what information is stored on the tape. Support is included for logging in newly purchased tapes and deleting tapes that have been destroyed. DSK MANAGER also lets you know how many times a particular tape has been used. Disk Space Management: DSK MANAGER space management utilities are based on profiles created on your system. The analysis reports each run using information created in the disk profile. The profiles for your system are separated into two categories; System and User. The System profile contains information about system software libraries. The User profile contains information about the libraries on your system that run your application software. The User profile should be run on a regular basis since it probably changes on a day-to-day basis. The System profile only needs to be run when new versions of OS/400 are installed or when PTF's from IBM are received and applied.

8 4 Installation and Security The following procedure is used for both new installations and for update installations. To install DSK MANAGER, follow these easy instructions: 1. If you are doing an upgrade installation to a previously installed DSK MANAGER installation, the install process may take a long time if you have a lot of history information on file for existing backup sets. Before doing the upgrade install, we strongly recommend that you review the backup sets on file and delete sets that you no longer need to keep on file. This can save a lot of time during the installation process. 2. Sign on using the QSECOFR id. 3. Place the installation CD in your system and key the following command: LODRUN DEV(xxxx) where xxxx is the name of your CD (optical) reader. 4. During installation, DSK MANAGER does the following:! Checks to see if this is a new install or an update install.! For update installs, the old library is saved in library DISKMGROLD and history information is transferred to the newly installed library.! For new installs, the software is initialized for the free 30 days trial period.! Additional documentation is printed which covers topics that have been added or changed since the user documentation manual was last printed. 5. When the command finishes, the DSK MANAGER Master Menu will be displayed. During step 4, documentation for additional topics will be printed. This includes topics and features that are not covered in this manual, normally because new features or capabilities have been added since the last printing of the manual. Before using DSK MANAGER, please review all documentation in detail. If this is a new trial install, remember that the software will only operate on your system for about 30 days. When you decide to keep DSK MANAGER, you must send your payment to Kisco Information Systems. At that time, KIS must know the full serial number for your system. If you are not sure of your serial number, you can display it by using the following command: DSPSYSVAL QSRLNBR

9 When KIS receives your payment and serial number, they will issue a password to you. This password, when applied, will certify your copy of DSK MANAGER and will permanently activate the software on your system. The password and certification instructions will be provided in writing (by fax if your fax number is provided, otherwise by mail). Please review the section later in this manual which covers the INSTALL menu for additional installation specifics. 5

10 6 OS/400 Compatibility A message may be displayed at your terminal when the installation process completes that indicates a problem with OS/400 level compatibility. This message will appear at the base of the terminal screen and will read as follows: Installation is complete - Check OS/400 Level Compatibility This message means that the level of your OS/400 operating system is not automatically supported by the current version of DSK MANAGER. A manual adjustment may be required for the Library Program Backup to function correctly. All other functions of DSK MANAGER will work without any intervention. Please refer to the Library Program Backup section of this manual before you proceed.

11 7 An Approach To Backups DSK MANAGER uses a fresh approach to keeping safe backups of your iseries-as/400 system. Data objects are classified separately from program objects. By separating them, each can be saved on a different schedule. Since program objects change less frequently, they can be saved on a less frequent schedule. Data objects tend to change on a more frequent basis, so they can be saved more frequently. Also, by separating them, you don't end up wasting time and media saving the same program objects over and over again. To implement a backup plan using DSK MANAGER, we recommend you adopt the following method at the outset. As you become more familiar with this new tool, you can modify your plan to better suite your needs. Recommended Plan 1) DSK MANAGER does not backup the IBM System library (QSYS). You must create and maintain a current backup using the standard IBM command 'SAVSYS'. You must keep this tape in a safe place for possible use in the event of a total disk failure, it will be used to reload OS/400. You must remember to create a new SAVSYS tape whenever PTF's are applied to your system and whenever OS/400 updates are installed. 2) Using the Library Program Backup feature (menu option #3), you must create a backup of all IBM libraries on your system. This can be done by specifying *ALL libraries and using option 'X' for the IBM library option. This will save all the IBM libraries at once. This should be done whenever the SAVSYS is required. 3) Using the Library Program Backup feature again, create a backup of all program objects for all libraries, excluding the IBM libraries. This will save program objects but not data objects. Initially, we recommend this on a monthly basis. If you are in a period of busy program development where the programs are being changed more frequently, you may want to use this option more frequently. The Library Program Backup feature also allows you to save current Configuration information and Security information about your system. We recommend that you include these saves whenever you run a Library Program Backup. 4) If you use any IDDU (Interactive Data Definition Utility) dictionaries, you must save these dictionaries separately. (Note: IDDU Dictionaries are normally associated with installations that migrated to an iseries-as/400 from a System/36 where IDDU was implemented). Use the Data Dictionary Backup option (menu option #4) for this purpose. These should be saved on the same cycle as the program backups.

12 8 5) You must also save all objects in the Shared Folder environment on your system along with all objects in the Integrated File System (IFS). Use the Document/Folder Backup option (menu option #5) for this purpose. You can save these on any cycle, it is entirely dependent on how frequently they are changed. 6) Using the Master Data Backup feature (menu option #1), save your data objects on a weekly basis. This feature will look through all user libraries on your system and identify the data objects for every library. These will be saved to tape during this run. If you have files that, for application reasons, must be saved all at the same time, be sure to define them in Synchronized Application File Groups. See the following topic in this section for more information about file groups. 7) Using the Incremental Data Backup feature (menu option #2), save any changed or new data objects on a daily basis. This feature should be run on a daily basis, including a run for the same day that the Master Backup was done. We recommend that the Incremental Backup be scheduled for a time of day when there is low system activity. Changed objects are currently identified by the object change date. When the object change date/time for an object is later than the most recent master backup save date/time, the object will be considered changed and the Incremental backup will process it. For Synchronized Application File Groups, if any single file object in the group changes, the entire file group will be saved at the end of the Incremental run. Using this plan for backup on your iseries-as/400 will result in complete and safe system backups for every object in your system. As you gain experience with DSK MANAGER, you can alter the schedule and frequency of the backups to more closely meet the needs of your specific computer installation. Backup Override Codes For Master and Incremental Data Backup runs, DSK MANAGER allows you to specify backup control overrides. Using these overrides, you can modify the way the Master and Incremental Backups look at the data. Backup override codes are stored in the Description File and can be updated using menu option #8 from the MASTER menu. The following codes in the Description File will override the backup as indicated in the following chart: Code Override Action A Always Save The file should always be saved at Incremental save time regardless of change date/time currently indicated for the file.

13 9 B Bypass Mstr The file should always be skipped during the Master save and always included with the Incremental save. This allows for files to be synchronized at backup time. I Bypass Incr The file should always be skipped during the Incremental save and always included with the Master save. This allows for files that are specifically included in a separate application backup to be excluded from Incremental backup processing. This can avoid saving some very large files more than necessary for an adequate backup. N Never Save The file is always bypassed during both the Master and the Incremental back. This can be used for test files and any file that is easily recreated. S Not Shared The file should always be skipped if it is in use during either the Master or Incremental backup, regardless of file sharing level. You can refer to a later section in the manual that covers the Update Description File menu option for further information on defining and using the backup override codes. Synchronized Application File Groups Certain applications on your system may require that files be save together so that they are all synchronized with each other. An example of this might be an Order Entry system where you have an Order Header file and an Order Detail Line Items file. To save these two files correctly, they should be saved at the same point in time so that the relationship between the records can be preserved. DSK MANAGER, as of Release 3, provides support for defining these groups of files and saving them in a synchronous fashion. Application file groups are defined by using menu option #8 from the MASTER menu, Update Description File. When you use this option for the first time, be sure to select the '*YES' option on the prompt screen to update your current files. Further information on using the Description File Update and creating Application Codes and Application Groups can be found in the section of this manual that covers the Update Description File menu item. Performance Issues Performance can be an important issue when creating backups. With the approach used by DSK MANAGER, this becomes even more critical. This product was designed specifically to allow most backups to take place concurrent with normal processing. Because the backups are taking place along

14 10 with your regular processing, DSK MANAGER backups will take longer than the dedicated backups that you may be used to. Our design philosophy in this matter, however, is that backups can take as long as necessary as long as regular production can continue at the same time. DSK MANAGER backups will always take longer than a similar backup taken on a dedicated system. In fact, you may find that you want to increase the time needed for backups so that your normal production is not slowed. This can be done by changing execution priorities for the backups and by restricting the amount of storage allocated to the subsystem where your backups are running.

15 11 Main Menu The main menu used by DSK MANAGER is named MASTER. It is found in the library DISKMGR. You can issue the following GO command from any terminal command line: GO DISKMGR/MASTER You can use these methods to display any of the menus provided by the DSK MANAGER software. The main DSK MANAGER menu appears as follows: Menu items perform the following functions. Each function is discussed in greater detail later in this document: 1. Backup Functions Displays the menu where all of the DSK MANAGER Backup functions can be used. 2. Restore Functions Displays the menu where all of the Restore functions can be used.

16 12 3. Maintenance Functions Displays the menu where information can be added to the DSK MANAGER files which are used to control backup and restore functions. 4. Disk Space Analysis Functions Displays the menu where all of the disk space analysis and disk management tools can be used. 5. Offline Archive Functions Displays the menu where all functions can be used to implement the DSK MANAGER offline archive. 6. Tape Management Functions Display the menu where all Tape Management functions can be used. 10. To Install Menu Displays the DSK MANAGER installation menu. 90. Signoff Performs an iseries-as/400 system terminal session sign-off.

17 13 Backup Menu When you choose menu option #1 from the MASTER menu in DSK MANAGER, the following BACKUP menu is displayed: Menu items perform the following functions. Each function is discussed in greater detail later in this document: 1. Master Data Backup Backs up all data objects in the libraries specified. Can be run while users are still on your system. 2. Incremental Data Backup Backs up all data objects in the libraries specified that are new or have changed since the last Master backup. Can also be run while users are still on your system. 3. Library Program Backup Backs up all program objects in the libraries specified. Can be run while users are still on your system. Some program objects may be skipped.

18 14 4. Data Dictionary Backup Backs up all libraries that contain IDDU data dictionaries. Can be run while users are still on your system. 5. Document/Folder Backup Backs up all documents and folders used by OfficeVision/400 and Client Access/400 (PC Support/400). Also backs up information stored in the Integrated File System for systems using OS/400 V3R1 or higher. 6. Application Group File Group Backs up a group of files for a specific application code. Files are saved at the same time providing for synchronization of the file. 7. Add User Save Set to DSK Allows you to tell DSK MANAGER about a save that you MANAGER Status File have done external to DSK MANAGER. Stores information about your save in the DSK MANAGER system files. 11 thru 14. Status Check Displays the current status of backups while they are running in batch mode. Menu item corresponds to the backup on the left side of the menu. 10. Return to MASTER Menu Re-displays the DSK MANAGER MASTER menu. 90. Signoff Performs a terminal signoff. Each menu option on the BACKUP menu will be discussed in detail in this section of the user guide.

19 15 Master Data Backup When you select menu option #1 from the BACKUP menu, the following prompt screen will be displayed: The parameters can be filled in as follows: DEV VOL OWNID Enter the device ID for the tape drive you are using. If your system has more than one tape drive and they are identical units, you may enter a second device ID and DSK MANAGER will use both units for the backup. Enter the volume identifier for the first output volume or *MOUNTED. The first volume will be initialized to this VOLID. If the *MOUNTED value is used, the tape will not be initialized. Note: the *NOINZ is also support for compatibility with earlier releases of DSK MANAGER, it is identical to the *MOUNTED option. Enter up to 14 characters for the owner identifier. The first volume will be initialized with this owner.

20 16 LIBRARY Enter one of the following values: *ALL libraryname The system will process all user libraries on your system. The system will process just the library or libraries named. Keying a '+' sign in this field will open it up for as many as 50 library names. LFOPTION Enter one of the following values: Y N Will cause the backup to include logical files. When logical files are included, they are all saved at the end of the master backup procedure. Will cause the backup to skip all logical files. IBMOPTION Enter one of the following values: Y N Will cause the backup to include all data files from IBM libraries. Will cause the backup to skip all IBM files. APPLOPT Specifies how Application File Groups are to be processed during the Master Backup. N S E Default. Application File Groups will be ignored during the Master backup. Application File Groups will all be saved at the start of the Master backup operation. Application File Groups will all be saved at the end of the Master backup operation. JOBQ STARTIME To run the backup interactively from the current terminal session, leave this parameter blank. If you want to run the backup in batch mode, enter the name of the jobque you want to use in this field. On most systems, this can be accomplished by specifying 'QBATCH'. To run the backup immediately, leave this parameter blank. If you want to delay starting the backup until a later time, key the time you want the job to start processing here. If the time, expressed in HHMM format (hours and

21 minutes) is greater than the current time, the job will start later today. If the time is less than the current time, the job will start at that time tomorrow. If you specify a delayed time, we recommend that you process the job in a jobq other than the system QBATCH jobq. A delayed job could interfere with other regular production in QBATCH. 17 ENDOPT Specifies what you want to do with the tape when this function is completed. Choose from the following options: *UNLOAD *REWIND *LEAVE The default. The tape will be rewound to the start of the tape and the drive will be unloaded. The drive cannot be used again until a new tape is mounted or the current tape is re-mounted. The tape will be rewound to the start of the tape and the drive will be left in ready status. The tape will be positioned at the end of the save operation, ready for another tape operation to continue at that point. When all parameters have been selected, press enter to start the master backup process. When you specify to run the backup in batch mode, the job will be sent to the jobque and the terminal session will return to the menu. While the backup is running in batch, you can check its progress using menu option 11. The current library and file being processed will be displayed at your screen. When the backup is finished, a detailed report will be printed showing which data files were saved. If any data files were in use at the time of the backup, the report will show them with a message indicating how they were processed. Files not saved during the master backup will be automatically included as candidate files for the incremental backup. The Master backup processes data files in groups. When initially installed, each group consists of 10 files. While putting the groups together, if the total size of the group exceeds 1 MB characters, no more files will be added to the group and the group will be saved at that point. This method significantly speeds up saving data files while avoiding locking files for long periods of time. These grouping parameters can be adjusted to meet the needs of your installation. In most cases, the default parameters will not need to be changed. The performance values are maintained by using option #8 from the INSTALL menu. Please reference the section of this manual for a description of this feature. Note that the restrictions on the sizes of these groups does not apply to the Synchronized Application File Groups. Regardless of size, these groups will all be saved together in a single group where possible. See the notes following the description of the Application Group File Backup menu option.

22 18 Incremental Data Backup When you select menu option #2 from the BACKUP menu, the following prompt screen will be displayed: The parameters can be filled in as follows: DEV VOL OWNID LIBRARY Enter the device ID for the tape drive you are using. If your system has more than one tape drive and they are identical units, you may enter a second device ID and DSK MANAGER will use both units for the backup. Enter the volume identifier for the first output volume or *MOUNTED. The first volume will be initialized to this VOLID. If the *MOUNTED value is used, the tape will not be initialized. Note: the *NOINZ is also support for compatibility with earlier releases of DSK MANAGER, it is identical to the *MOUNTED option. Enter up to 14 characters for the owner identifier. The first volume will be initialized with this owner. Enter one of the following values:

23 19 *ALL libraryname The system will process all user libraries on your system. The system will process just the library or libraries named. Keying a '+' sign in this field will open it up for as many as 50 library names. LFOPTION Enter one of the following values: Y N Will cause the backup to include logical files. The master and incremental backups do not save the actual logical file data, just a description of file so it can be rebuilt during a restore. If your master backup included logical files, there is probably not a real requirement to include them with the incremental backup unless new files have been created. When logical files are included, they are saved at the end of each library group. Will cause the backup to skip all logical files. IBMOPTION Enter one of the following values: Y N Will cause the backup to include all data files from IBM libraries. Will cause the backup to skip all IBM files. APPLOPT Specifies how Application File Groups are to be processed during the Incremental Backup. Note that these options are not identical to the Master backup. N E Default. Application File Groups will be ignored during the Incremental backup. Application File Groups will all be saved at the end of the Incremental backup operation. JOBQ STARTIME To run the backup interactively from the current terminal session, leave this parameter blank. If you want to run the backup in batch mode, enter the name of the jobque you want to use in this field. On most systems, this can be accomplished by specifying 'QBATCH'. To run the backup immediately, leave this parameter blank. If you want to delay starting the backup until a later time, key the time you want the job to start processing here. If the time, expressed in HHMM format (hours and minutes) is greater than the current time, the job will start later today. If the time is less than the current time, the job will start at that time tomorrow. If you specify a delayed time, we recommend that you process the job in a jobq other

24 20 than the system QBATCH jobq. A delayed job could interfere with other regular production in QBATCH. ENDOPT Specifies what you want to do with the tape when this function is completed. Choose from the following options: *UNLOAD *REWIND *LEAVE The default. The tape will be rewound to the start of the tape and the drive will be unloaded. The drive cannot be used again until a new tape is mounted or the current tape is re-mounted. The tape will be rewound to the start of the tape and the drive will be left in ready status. The tape will be positioned at the end of the save operation, ready for another tape operation to continue at that point. When all parameters have been selected, press enter to start the incremental backup process. When you specify to run in batch mode, the job will be sent to the jobque and the terminal session will return to the menu. While the backup is running in batch, you can check its progress using menu option 12. The current library and file being processed will be displayed at your screen. The incremental backup will search out all data objects for the library or libraries specified. Each object will be checked to see if it was saved during the master backup. If it was saved during the master backup and the file has not changed since then, it will not be backed up again. Only those data objects that are new, have changed since the master run or were skipped during the master run will be saved during the incremental run. If an object was skipped during the master save, the incremental backup will attempt to save it. If it is still unavailable during the incremental save, it will be bypassed again. You should carefully check the output report to identify data objects that were skipped by both the master and incremental backups. Arrangements must be made to safely backup any data objects that fall into this situation. If you specify that Application File Groups are to be saved, DSK MANAGER will check all files in the group. If any single file has changed, the entire application group will be saved. All Application File Groups are saved at the end of the Incremental Backup operation.

25 21 Library Program Backup When you select menu option #3 from the BACKUP menu, the following prompt screen will be displayed: The parameters can be filled in as follows: DEV VOL OWNID LIBRARY Enter the device ID for the tape drive you are using. If your system has more than one tape drive and they are identical units, you may enter a second device ID and DSK MANAGER will use both units for the backup. Enter the volume identifier for the first output volume or *MOUNTED. The first volume will be initialized to this VOLID. If the *MOUNTED value is used, the tape will not be initialized. Note: the *NOINZ is also support for compatibility with earlier releases of DSK MANAGER, it is identical to the *MOUNTED option. Enter up to 14 characters for the owner identifier. The first volume will be initialized with this owner. Enter one of the following values:

26 22 *ALL libraryname The system will process all user libraries on your system. The system will process just the library or libraries named. Keying a '+' sign in this field will open it up for as many as 50 library names. IBMOPTION Enter one of the following values: Y N X Will cause the backup to include IBM libraries. Will cause the backup to skip all IBM libraries. Will cause the backup to process ONLY the IBM libraries. All other libraries will be excluded. CFGOPTION Enter one of the following values: Y N Will cause the backup to save the system configuration at the start of the backup process. Will cause the backup to bypass saving the system configuration. SECOPTION Enter one of the following values: Y N Will cause the backup to save the current system security information immediately after the configuration on the backup. Will cause the backup to bypass saving the current security information. JOBQ STARTIME ENDOPT To run the backup interactively from the current terminal session, leave this parameter blank. To run the backup in batch mode, enter the name of the jobque you want to use here. On most systems, this can be accomplished by specifying 'QBATCH'. To run the backup immediately, leave this parameter blank. If you want to delay starting the backup until a later time, key the time you want the job to start processing here. If the time, expressed in HHMM format (hours and minutes) is greater than the current time, the job will start later today. If the time is less than the current time, the job will start at that time tomorrow. If you specify a delayed time, we recommend that you process the job in a jobq other than the system QBATCH jobq. A delayed job could interfere with other regular production in QBATCH. Specifies what you want to do with the tape when this function is completed. Choose from the following options: *UNLOAD The default. The tape will be rewound to the start of the tape

27 23 *REWIND *LEAVE and the drive will be unloaded. The drive cannot be used again until a new tape is mounted or the current tape is re-mounted. The tape will be rewound to the start of the tape and the drive will be left in ready status. The tape will be positioned at the end of the save operation, ready for another tape operation to continue at that point. When all parameters have been selected, press enter to start the program backup process. When you specify to run in batch mode, the job will be sent to the jobque and the terminal session will return to the menu. While the backup is running in batch, you can check its progress using menu option 13. The current library and file being processed will be displayed at your screen. The program backup will save just program objects. This includes all objects in each library except physical data files and logical data files. The following is a partial list of the types of objects saved and is provided here to give you a better idea of the concept. Object Type *PGM *OUTQ *MSGF *FILE *CMD *MENU Others Description Program objects Output queues Message files Program file objects with the following attributes DSPF - Display Files PF-SRC - Source Files DKTF - Diskette device files PRTF - Printer device files TAPF - Tape device files (All except PF-DTA and LF-DTA) Command objects Menu objects At the end of the program backup, a listing is produced to show you exactly what was saved from each library. We recommend that you examine this listing after each program library backup for possible exception conditions. You will find two exceptions that may occur on a regular basis. One is that an IBM library has been skipped and the other is that an IBM library has been only partially saved. DSK MANAGER intentionally skips saving libraries QDOC, QRECOVERY, QRPLOBJ, QSPL, QSRV, QSYS and QTEMP due to OS/400 imposed restrictions on these libraries. They are either not required for a safe backup or may be saved using other methods. The partially saved libraries are normally caused by userid message queues that are not saved because they are in use at the time of the backup. This too is not a problem in creating a safe backup. One exception to the separation of data objects and program objects exists with the IBM libraries.

28 24 When DSK MANAGER creates a backup of an IBM library, it does a full library save (SAVLIB) rather than saving the objects separately. This is done to simplify restoration of the system in the event of a total disk loss. For this reason, we recommend that IBM libraries be saved separately (using the 'X' option) and that they only be saved when new OS/400 releases are installed and following PTF application. OS/400 Level Compatibility During installation, DSK MANAGER checks to see the current level of OS/400 installed on your machine. The current DSK MANAGER program automatically adjusts for levels V2R3, V3R0M5, V3R1 and V3R6. If your system is using another level of OS/400, a warning message is issued at the end of the installation procedure. When IBM updates OS/400, it will sometimes add a new object type or delete an old object type. Since DSK MANAGER differentiates between program and data objects, it must be kept current when the list of valid object types changes. Kisco will automatically notify you as soon as object type changes become known. The list of valid object types used by DSK MANAGER is kept in a data area named PGMOBJS. To display the current contents of the data area, enter the following command: DSPDTAARA DISKMGR/PGMOBJS When examining this list of object types, note that the *FILE type is missing. THIS IS INTENTIONAL, OBJECT TYPE *FILE SHOULD NEVER BE ADDED TO THIS TABLE. When you update your OS/400 to a new level, the list of possible object types must be checked and compared to the contents of this data area. Obsolete object types must be removed and new object types must be added. You can use the Change Data Area (CHGDTAARA) command to make the changes. When deleting object types, it is alright to leave blank gaps in the list. At least one blank character must separate each object type in the list. If you are unsure about making changes to the list, contact Kisco Information Systems and a customer service representative will talk you through the changes over the phone. Your system has been shipped with pre-formatted data areas for a variety of levels of OS/400. At any time, you can copy the contents of one of the following data areas into the active PGMOBJS data area to achieve release level compliance: Library Name Data Area Name OS/400 Release Level Supported DISKMGR PGMOBJSV44 OS/400 V4R4M0

29 DISKMGR PGMOBJSV45 OS/400 V4R5M0 DISKMGR PGMOBJSV51 OS/400 V5R1M0 DISKMGR PGMOBJSV52 OS/400 V5R2M0 25

30 26 Data Dictionary Backup When you select menu option #4 from the MASTER menu, the following prompt screen will be displayed: The parameters can be filled in as follows: DEV VOL OWNID LIBRARY Enter the device ID for the tape drive you are using. Enter the volume identifier for the first output volume or *MOUNTED. The first volume will be initialized to this VOLID. If the *MOUNTED value is used, the tape will not be initialized. Note: the *NOINZ is also support for compatibility with earlier releases of DSK MANAGER, it is identical to the *MOUNTED option. Enter up to 14 characters for the owner identifier. The first volume will be initialized with this owner. Enter one of the following values: *ALL The system will process all dictionaries on your system.

31 27 libraryname The system will process just the dictionary files found in the library or libraries named. Keying a '+' sign in this field will open it up for as many as 50 library names. JOBQ ENDOPT To run the backup interactively from the current terminal session, leave this parameter blank. If you want to run the backup in batch mode, enter the name of the jobque you want to use in this field. On most systems, this can be accomplished by specifying 'QBATCH'. Specifies what you want to do with the tape when this function is completed. Choose from the following options: *UNLOAD *REWIND *LEAVE The default. The tape will be rewound to the start of the tape and the drive will be unloaded. The drive cannot be used again until a new tape is mounted or the current tape is re-mounted. The tape will be rewound to the start of the tape and the drive will be left in ready status. The tape will be positioned at the end of the save operation, ready for another tape operation to continue at that point. When all parameters have been selected, press enter to start the dictionary backup process. When you specify to run in batch mode, the job will be sent to the jobque and the terminal session will return to the menu. While the backup is running in batch, you can check its progress using menu option 14. The current library and file being processed will be displayed at your screen. IDDU data dictionaries are stored in *FILE objects within given libraries. These *FILE objects cannot be saved individually or in groups. The only way to save the IDDU data dictionaries is to save the entire library with a SAVLIB command. This backup will look through your entire system and identify those libraries that contain an IDDU data dictionary. Each identified library will then be saved using a SAVLIB command. Because of this limitation, we recommend that you limit the use of IDDU dictionaries to libraries that are specifically created for this purpose. This will eliminate unnecessary backup of non-dictionary objects during this process.

32 28 Document/Folder Backup When you select menu option #6 from the BACKUP menu, the following prompt screen will be displayed: The parameters can be filled in as follows: DEV VOL OWNID JOBQ Enter the device ID for the tape drive you are using. Enter the volume identifier for the first output volume or *MOUNTED. The first volume will be initialized to this VOLID. If the *MOUNTED value is used, the tape will not be initialized. Note: the *NOINZ is also support for compatibility with earlier releases of DSK MANAGER, it is identical to the *MOUNTED option. Enter up to 14 characters for the owner identifier. The first volume will be initialized with this owner. To run the backup interactively from the current terminal session, leave this parameter blank. If you want to run the backup in batch mode, enter the name

33 29 of the jobque you want to use in this field. On most systems, this can be accomplished by specifying 'QBATCH'. ENDOPT Specifies what you want to do with the tape when this function is completed. Choose from the following options: *UNLOAD *REWIND *LEAVE The default. The tape will be rewound to the start of the tape and the drive will be unloaded. The drive cannot be used again until a new tape is mounted or the current tape is re-mounted. The tape will be rewound to the start of the tape and the drive will be left in ready status. The tape will be positioned at the end of the save operation, ready for another tape operation to continue at that point. When all parameters have been selected, press enter to start the document/folder backup. When you specify to run in batch mode, the job will be sent to the jobque and the terminal session will return to the menu. This procedure will identify all OfficeVision/400 documents and calendars and save them to the tape specified. All Client Access/400 (PC Support/400) folders on your system will also be identified and saved. An audit report listing all objects identified and saved is printed following successful completion of the backup. After all of the folders have been saved, this procedure will save the contents of the Integrated File System. This is done for all systems running OS/400 level V3R1M0 or higher. The portions of the IFS that are saved include those not included with the other regular features of DSK MANAGER. If the entire IFS were saved, this would save your entire system again. A listing of IFS objects saved will be produced when the backup completes. The Document/Folder save feature automatically takes advantage of the save-while-active features provided by OS/400 when saving document library objects. You do not need to do anything to take advantage of this feature, it is automatically invoked during the backup operation.

34 30 Application Group File Backup When you select menu option #7 from the BACKUP menu, the following prompt screen will be displayed: The parameters can be filled in as follows: DEV VOL OWNID APPLCODE Enter the device ID for the tape drive you are using. If your system has more than one tape drive and they are identical units, you may enter a second device ID and DSK MANAGER will use both units for the backup. Enter the volume identifier for the first output volume or *MOUNTED. The first volume will be initialized to this VOLID. If the *MOUNTED value is used, the tape will not be initialized. Note: the *NOINZ is also support for compatibility with earlier releases of DSK MANAGER, it is identical to the *MOUNTED option. Enter up to 14 characters for the owner identifier. The first volume will be initialized with this owner. Enter the two character code associated with the Application Group to be saved. This must already be defined in the Description Master file and at least

35 31 one file must be coded with the application code. JOBQ STARTIME ENDOPT To run the backup interactively from the current terminal session, leave this parameter blank. If you want to run the backup in batch mode, enter the name of the jobque you want to use in this field. On most systems, this can be accomplished by specifying 'QBATCH'. To run the backup immediately, leave this parameter blank. If you want to delay starting the backup until a later time, key the time you want the job to start processing here. If the time, expressed in HHMM format (hours and minutes) is greater than the current time, the job will start later today. If the time is less than the current time, the job will start at that time tomorrow. If you specify a delayed time, we recommend that you process the job in a jobq other than the system QBATCH jobq. A delayed job could interfere with other regular production in QBATCH. Specifies how you want to leave the tape when the group save is complete. Choose one of the following values: *REWIND *LEAVE *UNLOAD Default. The tape will be rewound to the start of the tape. The tape will be left positioned at the end of the save operation. This may be useful if you intend to perform a series of operations on the same tape. The tape will be rewound and unloaded at the end of the save operation. The tape device will not be useable until a new tape is mounted. When all parameters have been selected, press enter to start the master backup process. When you specify to run the backup in batch mode, the job will be sent to the jobque and the terminal session will return to the menu. When the backup is finished, a detailed report will be printed showing which data files were saved. Application File Groups must be defined using the Update Description File option on the MAINT menu. Refer to the section of this manual that documents that menu option. An application group can consist of as many files as necessary, up to a limit of 50 per group. Application groups can also be located in separate libraries. You should be aware, however, of certain limitation of the OS/400 SAVOBJ command that can affect how you define your groups. Application groups will be saved all at the same time. Up to 50 files at a time in each library will be

36 32 backed up to tape. If an application group consists of more than 50 files, the actual save will require more than one physical save operation. This is also true when an application group spans more than one library. All files in one library will be saved, then the files in the second and subsequent libraries will be saved. If the application group is defined with notification instructions, the userid specified will be sent a message at the start of the application group save. This message will indicate that the save will start in a specified number of seconds. If the save is occurring during normal working hours, this will help the user know that the save is occurring and allow them to take appropriate action. Some application degradation can be expected. When the group save is done, the notify user will receive another message advising that the group save is now complete. Add User Save Set to Status File When you select menu option #8 from the BACKUP menu, the following prompt screen will be displayed: The parameters can be filled in as follows: REPORT Choose the report option you want as follows: S DSK MANAGER will produce a summary report about your save