Linux stand-alone: Use JCL templates to set up DB2 for z/OS

Linux stand-alone: Use JCL templates to set up DB2 for z/OS

To use a DB2 for z/OS database, we can use JCL template files to help customize the database based on the configuration prior to using the DB2 for z/OS database.

Prerequisites

Linux stand-alone: Install DB2 for z/OS

Linux stand-alone: Modify DB2 for z/OS properties

To use the JCL templates to set up the DB2 for z/OS database:

Make a copy of the template files you plan to use; the following templates exist in the PORTAL_HOME/base/wp.db.impl/config/templates/setupdb/db2_zos_remote directory:

Template Description
EJPSRACD This job executes the RACF commands required for the IBM WebSphere Portal for z/OS database user IDs and schemas. Review with the RACF administrator and, where required, modify the job before submitting.
For example, if you have specified database user IDthat are already defined in the RACF, remove the ADDUSER commands for them from the job. If you have some other security product such as Top Secret or ACF2 instead of RACF, then translate the RACF commands in the job into the appropriate syntax before submitting.
User ID requirement: RACF special authority.
Run this job on the server where the database will be created.
EJPSCRDB This job defines and creates the WebSphere Portal for z/OS database. The job has the following two steps:

Delete the existing database. If you have never run this job before, the attempt will not be successful. This is expected and can be ignored.

Define the database. This step must complete successfully.

User ID requirement: Connected to DB2 SYSADM authority.
Run this job on the server where the database will be created. Review the output from this job to verify all messages and SQL codes are expected/acceptable.
EJPSMCKD This job invokes CHECK DATA for the portal table spaces that are in status "CHECK PENDING" after database transfer. It also executes the RUNSTATS utility on the database
User ID requirement: Connected to DB2 SYSADM authority.
Run this job on the server where the database exists. Upon completion, examine job output. Success is indicated with "rc=4" in the job output.
Review the requirements of the EJPDBQRY program before attempting to run this job.
EJPDBQRY This program is executed by the EJPSMCKD job. It performs the DB2 CHECK DATA and RUNSTATS commands as required. Prior to executing this program for the first time you must run the DSNTIJRX jon created when installing DB2 for z/OS. This job makes the DB2 REXX function package required by EJPDBQRY available at runtime.

Modify the template copy with the appropriate information for the configuration.
Customization variables have the format, !!VARIABLE!! where "VARIABLE" is the descriptive name of what should go in place of the variable name.
For example, replace all occurrences of !!LM_DB_NAME!! with the name of the LikeMinds database.

Save the changes.

Allocate a data set from the z/OS system to contain the modified JCL jobs. It should have a fixed block (FB) record format length of 80.

Use FTP, or a similar utility, to upload the files and convert them from ASCII to EBCDIC.

Run the JCL jobs on the z/OS system.

Parent: Linux stand-alone: Prepare DB2 for z/OS
Previous: Linux stand-alone: Modify DB2 for z/OS properties
Next: Linux stand-alone: Create DB2 for z/OS users

Template	Description
EJPSRACD	This job executes the RACF commands required for the IBM WebSphere Portal for z/OS database user IDs and schemas. Review with the RACF administrator and, where required, modify the job before submitting. For example, if you have specified database user IDthat are already defined in the RACF, remove the ADDUSER commands for them from the job. If you have some other security product such as Top Secret or ACF2 instead of RACF, then translate the RACF commands in the job into the appropriate syntax before submitting. User ID requirement: RACF special authority. Run this job on the server where the database will be created.
EJPSCRDB	This job defines and creates the WebSphere Portal for z/OS database. The job has the following two steps: Delete the existing database. If you have never run this job before, the attempt will not be successful. This is expected and can be ignored. Define the database. This step must complete successfully. User ID requirement: Connected to DB2 SYSADM authority. Run this job on the server where the database will be created. Review the output from this job to verify all messages and SQL codes are expected/acceptable.
EJPSMCKD	This job invokes CHECK DATA for the portal table spaces that are in status "CHECK PENDING" after database transfer. It also executes the RUNSTATS utility on the database User ID requirement: Connected to DB2 SYSADM authority. Run this job on the server where the database exists. Upon completion, examine job output. Success is indicated with "rc=4" in the job output. Review the requirements of the EJPDBQRY program before attempting to run this job.
EJPDBQRY	This program is executed by the EJPSMCKD job. It performs the DB2 CHECK DATA and RUNSTATS commands as required. Prior to executing this program for the first time you must run the DSNTIJRX jon created when installing DB2 for z/OS. This job makes the DB2 REXX function package required by EJPDBQRY available at runtime.