Creating an image copy of the Db2 directory and catalog: DSNTIJIC (optional)

If you decide to image copy the Db2 directory and catalog, use the DSNTIJIC job that was generated during the installation or migration of the originating member. You do not need to make an image copy of the Db2 catalog or user data sets for recovery because Db2 uses image copies that were made before you enabled data sharing.

Procedure

To create an image copy of the directory and catalog:

  1. Examine job DSNTIJIC for the following information:
    • The device type or unit name.

      The default value is SYSDA. If this is incorrect for your site, correct it.

    • Expiration date or retention period. You can add a retention period or an expiration date to the job.
    • The user on the JOB statement. Ensure that the user is authorized. If Db2 is started under ACCESS(MAINT), this must be the same user that you specified for either the SYSTEM ADMIN 1 option or the SYSTEM ADMIN 2 option on installation panel DSNTIPP1.
  2. Run job DSNTIJIC.

    The DSNTIJIC job contains a list of all the Db2 directory and catalog table spaces. When you run job DSNTIJIC, it invokes the Db2 image copy utility to copy these table spaces to disk or tape, depending on the value that you select for IC DATA SET UNIT NAME field. Having copies of table spaces enables you to recover the Db2 catalog and Db2 directory in case of a failure.

  3. If the DSNTIJIC job fails or abends, verify that no problems exist with the tape or disk setup for image copy. If you find no problems with the setup, examine the utility job output (JOBLOG) or the console log for problems. For example, look for I/O errors or incorrect sizes.

What to do next

Run the DSNTIJIC job periodically, perhaps daily or weekly, to reduce the amount of time required for recovering the directory or catalog. The copied data and log data sets are needed for recovery.

During the ISPF tailoring session, you named one or two IDs to have installation SYSADM authority. One of these users can now grant various levels of authority to other users. You can use SPUFI or a job similar to DSNTIJSG to perform the authorization. To grant SYSOPR authority to all primary and secondary user IDs that issue Db2 commands from the z/OS® console or TSO SDSF, issue the following statement in SPUFI: 
GRANT SYSOPR TO userid