Customize JCL Procedures and Parameter Files

The degree to which the information provided in Step 1 is accurate will determine how much the JCL procedures and parameter files need to be modified in order to create the database instance.

JCL Procedures

All JCL procedures (or batch jobs) need to be reviewed carefully to ensure that they are valid. The JOBCARD job provided is only a default used by Oracle and will need to be tailored to your environment.

The batch jobs can be divided into the following categories:

Creating an Oracle Database Instance

■ Two sample PROCS that define the Oracle address space and the Net address space, and a procedure to copy them into a system installation library.

The PROCS are named in step 1 of the configuration process, and are

cross-referenced to the OSDI parameter file. Each procedure must be defined to RACF as a started task and associated with a user. The following are examples of RACF commands required to perform these tasks:

The batch job used to copy the two PROCS into a system PROCLIB library job is called COPYPROC and must be customized to point to the system PROCLIB library.

■ Sample PROCs which are used on a system-wide basis for Oracle utilities. These usually begin with the name ORA*, and should be customized and copied into system PROCLIB libraries before the new database goes into production.

Initially, they are not needed for the basic installation.

■ JCL procedures required to define, start and set up the database. These all begin with SQLsidn where sid is the SID name chosen for the instance, and n is a number from one to eight. These procedures perform specific tasks related to creating the database. The other batch jobs associated with this are called DEFINE and STRTSRVC. The DEFINE job is used to define the database files and the STRTSRVC job is used to define and activate the subsystem. Another set of PROCS provide basic functions like starting and stopping the database and starting the subsystem services.

Parameter Files

The parameter files are located in db_hlq.PARMLIB. They are the core definition files for the database. You should review these files for accuracy before you create the database instance. The parameter files can be divided into the following categories:

■ OSDI parameter files. Of this group of files, the the subsystem definition file is the core file. This file is called only by the OSDI subsystem name. This file has a major impact the other JCL batch jobs and parameter files and should be modified with care. The following is an example of the subsystem definition file:

INIT (ORASSI,SSN1) DEF SVG SSID(SSN1) DESC('OSDI Oracle 10G Subsystem - SSN1') DEF SRV ORAS10 PROC(ORA1S10) TYPE(ORA) MAXAS(1) - DESC('Oracle V10G RDBMS Service') - SID(ORA1) PARM('ORACLE.ORA1.PARMLIB(SSN1PARM)')

Creating an Oracle Database Instance

The file related to this is called sidPARM. This contains all the OSDI specific parameters. These parameters are documented in detail in this guide. Most default parameters are acceptable for most basic installations. The following is an example fo this file:

* SSN1 OSDI SUBSYSTEM PARAMETER FILE.

* USED BY SUBSYSTEM SSN1 SERVICE ORAS10 PROC ORA1S10

* LOAD MODULE TO USE.

SERVER_LOADMOD(ORACLE)

* NUMBER OF ADDRESS SPACES TO START. VALUES ARE 1-256 INIT_ADR_SPACES(1)

* MAXIMUM NUMBER OF SESSIONS ALLOWED FOR THIS ADDRESS SPACE MAX_SESSIONS(500)

* MAX MEMORY ALLOWED PER SESS. VALUES ARE NNNN {K|M}.

MAX_SESSION_MEM(100M)

* INITIAL STACK SIZE. VALUES ARE NNNN {K|M}.

INIT_STACK_SIZE(256K)

Creating an Oracle Database Instance

The third file in this section is called SUBSYS. It provides the command which needs to be issued in order to define and activeate the subsystem definition file.

■ The sidFPS parameter file contains all the default FPS parameters for creating the database files. Remove any which are not required. It contains the six most common data set types. If this is defined correctly, thendefining additional database files becomes easier. The minimum that is recommended is DFLT. Refer to this guide for details about what to code for this parameter file. An example is as follows

* Default parameters FILE_GROUP(DFLT) RECALL(NONE) MOUNT(NO) DEFAULT_SPACE(10000 10000) UNIT(SYSDA)

■ Instance-specific files

These are files which relate to the Oracle instance itself. They are the INITORA which is the standard initsid.ora file found on other platforms with default parameters for z/OS. This file should be modified to match any installation requirements. The installation utility does not ask many questions about tailoring this parameter file . It prompts only for the SID and number of processes because most parameters can be allowed to take the default for most installations.

The CREATE file which contains the SQL required to create a new Oracle database instance. This file along with the DEFINE JCL defines the basic layout of an Oracle instance. The type of instance it builds is a small, multi-purpose instance and follows the basic rules of Oracle database design. For example, it is highly recommended that there are at least two control files in any instance, the system data goes into the system tablespace and all user data goes elsewhere.

The sidENV contains the environment variables required for the Oracle

database. The most important is the ORACLE_HOME variable which should point to the ORACLE_HOME for the installation. The sidFNA is not required and is primarily used for compatibility reasons. It provides default naming conventions for SQL files.

Two other files which can be used are the TNSNAMES file and the SQLNET file.

The TNSNAMES file provides the default TNSNAMES entries for users to access this instance both through cross memory and through TCP/IP.

Creating an Oracle Database Instance