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

If you plan to use a DB2 for z/OSdatabase, you can use JCL template files to help you customize the database based on configuration prior to using DB2 for z/OS database.


Prerequisites


Install DB2 for z/OS
Modify properties for DB2 for z/OS

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

  1. 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:

    The templates and their descriptions.

    Template Description
    EJPSRACD This job executes the RACF commands required for the WebSphere Portal for z/OS database user IDs and schemas. Review with RACF administrator and, where required, modify the job before submitting. For example, if you have specified database user IDs that are already defined in 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:

    1. 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.

    2. 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.

    EJPSDBTC This job invokes CHECK DATA for the portal table spaces that are in status "CHECK PENDING" right 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.

  2. Modify the template copy with the appropriate information for 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 LikeMinds database.

  3. Save changes.

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

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

  6. Run the JCL jobs on z/OS system.


Parent

Prepare DB2 for z/OS


Previous

Modify properties for DB2 for z/OS


Next topic

Create users

  2011/12/17 v7. Edition 2: Second edition includes corrections a... 2011/12/15 documentation refresh


+

Search Tips   |   Advanced Search