In VM/ESA, user archives are database archives created with non-DB2 Server for VM facilities such as the VM/ESA DASD Dump Restore Service Program (DDR).
In VSE/ESA, user archives are database archives done with non-DB2 Server for VSE facilities, such as the VSE/VSAM IDCAMS Backup/Restore Feature. User archives include the DB2 Server for VSE & VM directory and all dbextents, but not the log.
Because the DB2 Server for VSE & VM code that creates the archives is DASD independent, it does not take advantage of particular DASD characteristics to improve performance. Some non-DB2 Server for VSE & VM facilities exploit these characteristics and can archive and restore your database faster in some cases.
| Note: | The DB2 Server for VM directory and dbextent minidisks are non-CMS minidisks. |
If you are going to do a non-DB2 Server for VSE & VM archive of your database, you can only do it when you shut down. Use the following command:
SQLEND UARCHIVE |
After all logical units of work finish, the application server indicates in the log that a user archive will be done. It then reminds the operator to do the archive, and ends. Figure 23 shows an example of the control statements required to archive a DB2 Server for VSE database using the VSE/VSAM IDCAMS BACKUP command.
Figure 23. Example of VSE/VSAM Backup Command for a User Archive
// JOB USERARCH
// ASSGN SYS005,181
// DLBL IJSYSUC,'SQL301C',,VSAM
// EXEC IDCAMS,SIZE=AUTO
BACKUP (SQL301.BDISK, -
SQL301.DDSK1, -
SQL301.DDSK2, -
SQL301.DDSK3, -
SQL301.DDSK4, -
SQL301.DDSK5, -
SQL301.DDSK6, -
SQL301.DDSK7)
/*
/&
|
The control statements cause VSE/VSAM to archive a database having a directory (BDISK) and seven dbextents (DDSK1-DDSK7). You do not archive the log data set(s). For more information about the VSE/VSAM BACKUP command, see the IBM VSE/VSAM Using Commands and Macros manual. If LOGMODE=L, the system (VSE or VM) does a log archive before ending if there is information in the log. After the application server ends, you should archive the DB2 Server for VSE & VM directory and all the dbextents, but not the logs.
If you specify STARTUP=R or U the next time you start the application server, it assumes that you have not done the user archive; otherwise, the system sends a message to the operator console asking if the user archive was done successfully.
If you decide to do user archives, you can do intermediate log archives or intermediate database archives to free log space while the application server is running.
For intermediate log archives, set LOGMODE to L when starting the application server When LOGMODE=L, the system automatically does a log archive when the log fills to the ARCHPCT value. If you prefer to schedule your online log archives, you can periodically enter the LARCHIVE command.
For intermediate database archives, set LOGMODE to A. When LOGMODE=A, the application server automatically archives the database when the log fills to the ARCHPCT value. Note that database archiving, not user archiving, is performed. Use the ARCHIVE command if you want to schedule your online database archives. Refer to Archiving the Database for more information on the ARCHIVE command.
You can use the SHOW LOG operator command to monitor available log space and to assist you in scheduling user archives. See SHOW LOG for more information about the SHOW LOG command.