Milestone 3: Prepare Db2 Repository
This milestone describes all the planning required for the setup and installation of the ISPW Db2 repository for a new installation of ISPW. For a description of all the objects in the ISPW Db2 repository, see Repository Tables.
If you are performing an upgrade instead, skip ahead to Milestone 4: Install ISPW Using SMP/E.
Complete the following tasks to plan your Db2 Repository installation.
Task 3.1 Determine Basic Db2 Subsystem Information
Certain Db2 subsystem details are needed to execute the ISPW Db2 repository installation jobs.
Subsystem Name
What is the name of the Db2 subsystem where ISPW will be installed?
Db2 Subsystem Name:
VCAT Name
What is the catalog name to be used for the ISPW storage group (if one is to be created)?
VCAT Name:
Batch SQL Program
What is the name of the batch SQL plan (for example, DSNTEP2) that this program invokes?
Batch SQL Plan:
What is the name of the batch SQL program (for example, DSNTEP2) that is used at your site?
Batch SQL Program:
Library Names
What are the dataset names of the Db2 LOAD, EXIT, and RUNLIB libraries, respectively?
Db2 LOAD Library Name:
Db2 EXIT Library Name:
Db2 RUNLIB Library Name:
Task 3.2 Plan an Authorization Strategy
The authorization strategy needs to be understood before the repository is installed. Different privileges are required for different phases of the installation. See Installation Authority Used for details of which privileges are used to execute the installation jobs.
Installation AuthID
Under what AuthID will the installation of ISPW be performed?
Installation AuthID: Type:
Repository AuthID
What AuthID will be assigned to the ISPW repository owner?
Repository AuthID:
Maintenance AuthID (Optional)
Set up a maintenance AuthID if users—who don’t already have authority to access the ISPW repository database through existing system-level privileges—will need to:
- administer the ISPW repository database directly for housekeeping, or
- access the ISPW repository database for other maintenance reasons (for example, backup, reorganization, or bufferpool tuning).
Maintenance AuthID:
Task 3.3 Plan Db2 Subsystem Resource Utilization
Adding a new application to run on a Db2 subsystem creates an extra load on it. Resource limits and other maximum limits should be revised to ensure that the subsystem can easily handle the extra resources required by ISPW.
Maximum Threads
Determine the maximum number of concurrent threads that could be used by the ISPW server to communicate with the Db2 repository. This is the number of Server Processes (SPROCESS + GPROCESS) that have been defined in the ISPW Server Definition Initialization parameters, plus three internal processes:
Number of SPROCESSs:
Number of GPROCESSs: +
Internal processes: + 3
Total concurrent processes: = (Maximum)Make sure the values specified on the Db2 installation panels for MAX TSO CONNECT and MAX USERS are large enough to compensate for this number of concurrent threads.
Db2 Virtual Storage
Make sure the EDM pool is large enough to store ISPW package and plan information. Make sure there is adequate virtual bufferpool space for ISPW tablespaces and indexes. Make sure other Db2 pools are large enough to handle ISPW. Check the Db2 catalog for the plan, package, and DBD sizes.
Other Limits
Revise any other relevant subsystem level parameters to ensure they are appropriate.
Task 3.4 Develop Db2 ISPW Naming Standard
If your organization does not have a naming standard to follow, one should be established for ISPW Db2 objects. A sample naming standard is provided in Sample Db2 Naming Standards, and Your Db2 Naming Standards can be used to record your own naming standard.
Sample Names
This sample naming standard provides the ability to run multiple version of ISPW simultaneously by including version numbers in some names. The following placeholders are used in Sample Db2 Naming Standards.
x | 1-letter environment code (for example, T for TEST or P for PROD). |
vvv | 3-digit version code identifying the current version (for example, 172 for 17.02). |
zzzz | 4-letter file code identifying the ISPW repository file. This should not be changed because ISPW will fill in these values. |
eee | 3-letter environment code (for example, TST for TEST or PRD for PROD). |
a | 1-digit allowing multiple indexes per table. |
Sample Db2 Naming Standards
Db2 Object Type | Example Naming Standard | Example Name |
|---|---|---|
ISPW AuthID | WZZxvvv | WZZT172 |
Repository AuthID | ||
Maintenance AuthID | ||
Database Name | WZZxvvv | WZZT172 |
Tablespace Name | TSxzzzz | TSTCNTR |
Index Name | IXxzzzza | IXTCNTR1 |
Plan Name | WZZxSvvv | WZZTS172 |
Collection Name | WZZvvveee | WZZ172TST |
Image Copy Prefix | DSN.IMAGCOPY.WZZxvvv.TSx | DSN1.IMAGCOPY |
Storage Group (optional) | WZZSGx | WZZSGT |
Your Db2 Naming Standards
Db2 Object Type | Naming Standard | Example Name |
|---|---|---|
ISPW AuthID | ||
Repository AuthID | ||
Maintenance AuthID | ||
Database Name | ||
Tablespace Name | ||
Index Name | ||
Plan Name | ||
Collection Name | ||
Image Copy Prefix | ||
Storage Group (optional) |
Task 3.5 Planning for Other Items
There is other information that is required for the installation of the ISPW repository. Some items may need more planning than others, depending on the site configuration. This is also time to think of any other site-specific requirements that have to be addressed.
Bufferpools
Determine the bufferpool(s) that the ISPW repository tablespaces and indexes will use. The repository installation process allows different bufferpools to be specified for tablespaces and indexes. If further placement is required, it should be done after the DDL has been generated. For approximate sizes of the ISPW tablespaces and indexes, see Db2 Repository Sizes. All ISPW tablespaces have a page size of 4K.
Tablespace Bufferpool (#BPTBSP):
Index Bufferpool (#BPINDEX):
Repository Size
Use the table in Db2 Repository Sizes to determine whether the site is small, medium, or large. Use the related #SIZE code (either SML, MED, LRG, or SYS).
Repository Size (#SIZE):
DASD Requirements
Determine how the ISPW repository Db2 datasets are going to be physically stored on DASD. Ensure there is enough DASD for ISPW, taking into account the likely growth rate in the short and long terms. If SMS is used for dataset placement, determine any changes needed to the ACS routines. If not, determine which volumes the ISPW Db2 datasets will reside on.
ISPW CM STC UserID
Determine the UserID or AuthID associated with the ISPW CM started task. This value is used during the repository installation, because the UserID needs to be granted authority to execute the ISPW plan. Note that this ID must have access to the Db2 subsystem, so it needs authority on the appropriate DSNR SAF Resource Name for the subsystem.
ISPW CM UserID (#CMUSER ID):