Space announcement

   

This space provides the same content as before, but the organization of the home page has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Installing

The PACLOG installation process generates a customized installation data set.

This data set contains all of the jobs that are required to install PACLOG in your DB2 environment. The member named $C30DOPT establishes your initial control information for PACLOG.

When you submit the $C30DOPT job that is contained in the installation options, it copies the PACLOG options to the ALM$OPTS member of the . DBCNTL data set and creates the history file for the subsystem.

The PACLOG modeling tool is automatically tailored with your installation’s data set names and copied to your .EXEC data set when you install PACLOG.

Installing PACLOG on multiple DB2 subsystems

After the PACLOG compression services are installed on an OS/390 system, PACLOG can be activated on all DB2 subsystems for that OS/390 system by simply adding the new DB2 subsystems to the PACLOG control information and creating the history data set.

If you have the RECOVERY MANAGER for DB2 product, see Integrating for instructions. Otherwise, edit the data set referred to by the ALM$OPTS DD statement by adding the new control variables HIST, BSDS1, TSTAMP, and PROD.SNLOAD. You must have OS/390 data set READ and WRITE authority to edit the control information member. Then, create a new history file that refers to the PACLOG .DBCNTL data set member ALMHIST for a sample job.

Sample ALM$OPTS file

The following example shows a PACLOG control information data set.

You can choose any valid OS/390 data set name for the history file during installation. However, the name must be unique for each subsystem. You cannot use the same data set for multiple subsystems.

The naming conventions shown in the sample ensure a unique name for each subsystem.

Sample ALM$OPTS file

DBAA.BSDS1=DBAACAT.BSDS01
DBAA.PROD.DSNLOAD=SYS2.DB2V81M.DSNLOAD
DBAA.HIST=BMCALM.TEST.DBAA.HISTORY
DBAA.TSTAMP=Y 
DBN.HIST=BMCALM.TEST.DBN.HISTORY 
DBN.TSTAMP=N 
DBN.BSDS1=DSNDBN.BSDS01 
DBN.PROD.DSNLOAD=SYS2.DB2V81M.DSNLOAD 
WORKUNIT=WORK

PACLOG installation options

This section describes the PACLOG installation options and their default values.

WORKUNIT=SYSALLDA

WORKUNIT specifies the default unit for work data sets dynamically allocated by PACLOG. You can specify another valid unit name during installation if you do not want to use the default, SYSALLDA.

TSTAMP=YES

TSTAMP specifies to PACLOG that the timestamp (if it exists) is to be copied into the data set name of archive log copies 3 and 4. If TSTAMP is set to YES, the prefix for ARCHIVE3 and ARCHIVE4 cannot be more than 17 characters. If TSTAMP is set to NO, the prefix can be up to 35 characters. For more information, see PREFIX prefix.

HIST= dataSetName

HIST specifies the subsystem’s BMC Software archive history data set. For more information about the archive history file, see BMC archive history file.

BSDS1= dataSetName

BSDS1 specifies the bootstrap data set file name.

PROD.DSNLOAD= dataSetName

PROD.DSNLOAD specifies the production DB2 load library.

Related topic



Was this page helpful? Yes No Submitting... Thank you

Comments