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
DISKMGR PGMOBJSV45 OS/400 V4R5M0
DISKMGR PGMOBJSV51 OS/400 V5R1M0
DISKMGR PGMOBJSV52 OS/400 V5R2M0
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 Enter the device ID for the tape drive you are using.
VOL 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.
OWNID Enter up to 14 characters for the owner identifier. The first volume will be initialized with this owner.
LIBRARY Enter one of the following values:
*ALL The system will process all dictionaries on your system.
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 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'.
ENDOPT 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 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.
*REWIND The tape will be rewound to the start of the tape and the drive will be left in ready status.
*LEAVE 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.
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 Enter the device ID for the tape drive you are using.
VOL 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.
OWNID Enter up to 14 characters for the owner identifier. The first volume will be initialized with this owner.
JOBQ 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'.
ENDOPT 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 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.
*REWIND The tape will be rewound to the start of the tape and the drive will be left in ready status.
*LEAVE 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.
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 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.
VOL 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.
OWNID Enter up to 14 characters for the owner identifier. The first volume will be initialized with this owner.
APPLCODE 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
one file must be coded with the application code.
JOBQ 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'.
STARTIME 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.
ENDOPT Specifies how you want to leave the tape when the group save is complete.
Choose one of the following values:
*REWIND Default. The tape will be rewound to the start of the tape.
*LEAVE 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.
*UNLOAD 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
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
operation. This is the default value.
D DSK MANAGER will produce a detailed report about your save operation.
N No report will be produced.
This feature allows you to create your own backup sets and then let DSK MANAGER know about them. DSK MANAGER will then log the backup set into the status file and update tape utilization information. To take advantage of this feature, your backup has to specify the following options on the SAVOBJ or SAVLIB command:
OUTPUT(*OUTFILE)
OUTFILE(DISKMGR/SAVEDETUSR) OUTMBR(*FIRST *REPLACE) INFTYPE(*MBR)
When the user save is complete, you must call this DSK MANAGER command to update the results of your save to DSK MANAGER.
Using Non-Standard Tape Densities
DSK MANAGER initializes the first tape for each backup unless an option to skip the initialization is specified. The default recording density for each specific tape device is used. For some installations, you may wish to use a different tape density than this default.
If this is the case, the solution is to initialize the tape or tapes prior to starting the DSK MANAGER save operation. Then, when you start the save, specify the '*MOUNTED' special value (or ‘*NOINZ’
as specified in earlier releases of DSK MANAGER) for the VOL parameter. This will force DSK MANAGER to bypass the tape initialization step.
Handling Tape Errors
Most tape errors will occur as error message CPF3794. This "Data Management" error can be caused by several things. These include tape media errors (bad tape), dirty tape read-write heads and a number of other similar causes.
The correct action to take in response to a CPF3794 error message is as follows:
1. Remove the current tape
2. Clean the tape drive using standard cleaning methods and tools
3. Mount a fresh tape on the same tape drive
4. Vary the tape drive off-line using the VRYCFG command
5. Vary the tape drive back on-line using the VRYCFG command with the RESET(*YES) option 6. Reply to the message with an 'R' to retry the save operation that failed.
DO NOT REPLY TO THIS MESSAGE WITH OPTION 'I'. DOING SO WILL