DB2 Server for VSE. Operations Guide / Handbooks (2004-2007)

Parameter Name

Default value

Description

Used in member:

GLOBCAT

VSESP.USER.CATALOG

The default VSAM catalog

ARIS75CD, ARISSTDL

where SQLGLOB resides

BINDFILE

DB2.BIND.MASTER

This is the name of the

ARIS75CD, ARISSTDL,

dataset which will hold the

ARIS757D, ARISIQBD

global variables

BINDWKF

DB2.BIND.WORKF

This is the name of the

ARIS75CD, ARISSTDL,

dataset which will hold the

ARIS759D

preprocessor bind pack-

ages.

MASTERFILE

DB2.SQLGLOB.MASTER

This is the name of the

ARIS75CD, ARISSTDL,

dataset which will hold the

ARIS758D, ARISGDEF

global variables

ATYPE

CYL

The type of allocation unit

ARIS75CD, ARIS757D,

for database IDCHMC

ARIS759D

DEFINE.

The default allocation unit is

Cylinders. Use BLK for FBA

devices, or CYL for (E) CKD

devices

Figure 18. Description of global parameters

2.1

Preparation Step 1: Setup the VSE Environment

This step is mandatory

If your are migrating from a previous release of DB2 for VSE, you may have to increase the partition size.

Refer to DB2 Server for VSE System Administration manual for more information.

Ensure that your VSE system is prepared as follows:

Equip the system with a tape drive for the type of distribution tape ordered.

Be sure that the system files are assigned correctly. During the installation process, input is read from

SYSIPT and source members from the DB2 Server for VSE sublibrary. Output is written to the printer

file, SYSLST, and the SYS001 workfile.

Ensure that the SYS001 workfile size is at least equal to 1 cylinder on an IBM 3380 DASD (960 blocks

on FBA devices).

See the DB2 Server for VSE System Administration manual for detailed information about capacity plan-

ning for storage requirements.

The partition sizes given below are the minimum required to successfully install or migrate a database. For

a detailed discussion of how to calculate partition sizes based on real operating conditions see the DB2

Server for VSE System Administration manual. Also, refer to the IBM z/VSE Planning for information about

partition configuration that could be used during the installation of optional program product such as DB2

Server for VSE.

Compiling and running application programs - 2.0 megabytes;

CICS system to support ISQL - 8.0 megabytes;

DB2 for VSE Program Directory

- to support DRDA Requester, approximately 1 additional megabyte is required for the resident

online resource adapter

DB2 Server for VSE partition:

- without DRDA - 5.0 megabytes;

- with DRDA - 6.5 megabytes;

Note! When the application server is started in single user mode, both the application server and the

installation application program are executed in the DB2 Server for VSE partition.

When the application server is started in multiple user mode:

- Batch installation application programs can be started in any partition with enough storage. The

library search assignment must include the DB2 Server for VSE 7.5 sublibraries for installation

programs executed in the partition.

- ISQL must be executed in the CICS partition.

- If the ISQL facility will be used in the CICS partition, the available CICS dynamic transaction

storage size must be at least 900 kilobytes to support ISQL. See "Installation Step 2: Link-Edit the

DB2 Server for VSE 7.5 Online Support Components".

VSE/REXX Version 6 Release 1 must be enabled.

2.1.1

DB2 Server for VSE Key Enablement

Users on z/VSE Version 3 Release 1 and later, who want to run DB2 Server for VSE, are required to

install a DB2 permanent product activation key, or a DB2 "90-day trial mode" product key.

z/VSE Version 3 Release 1 and later is shipped with a DB2 "90-day trial mode" product key. After the

90-day trial period is over, it is necessary to supply a DB2 permanent product key. This DB2 permanent

product key is supplied automatically from IBM whenever an order is placed for DB2 Server for VSE &

VM.

DB2 product enabling is driven by a phase which can be generated by the following EXEC IVALPKEY.

The statement to execute IVALPKEY is supplied by z/VSE Version 3 Release 1, and later, in the member

SKUSERBG in ICCF library 59.

// EXEC IVALPKEY,PARM='PRODUCT=DB2 KEY=0000-1111-2222-3333-4444 CUSTINFC

O=C111-111-1111'

The key that appears in this EXEC statement is the DB2 "90-day trial mode" product key. Please note that

the 90-day trial period starts when IVALPKEY is run (and not when DB2 Server for VSE is installed). Each

time DB2 Server for VSE is accessed, message ARI4027W is displayed informing you of the number of

days left within the 90-day trial period.

Once you have completed a license agreement for DB2 Server for VSE, you will replace the string shown

in the sample EXEC statement with the DB2 permanent product activation key.

IVALPKEY must be run whenever the z/VSE operating system is IPLed. Therefore, it is recommended that

you place the job to execute IVALPKEY on the POWER RDR queue so that it is released automatically at

each IPL of the z/VSE system during background processing.

Chapter 2. Preparing to Install DB2 Server for VSE 7.5

If IVALPKEY is not run when the z/VSE operating system is IPLed, DB2 Server for VSE cannot be

installed, migrated or started.

2.2

Preparation Step 2: Allocate DASD for the Distribution Library

This step is mandatory

APPROXIMATE SPACE REQUIREMENT: 30,000 LIBRARY 1K BLOCKS.

DASD Storage Requirements for DB2 Server for VSE Library

APPROXIMATE SPACE REQUIREMENT: 30,000 LIBRARY BLOCKS

Approximate Library Space

MSHP History File Space

DASD Device Type

Required

3375

120 cylinders

15 tracks

3380

74 cylinders

15 tracks

3390

70 cylinders

15 tracks

9345

84 cylinders

15 tracks

Figure 19. DASD Storage Requirements for DB2 Server for VSE Library

Notes:

1. These allocations include free space to allow for maintenance.

2. If you are installing versions of the DB2 Server for VSE HELP text or messages in languages other

than English, then you may consider an extra 400 library blocks for each supported language.

3. The sizes for the Maintain System History Program (MSHP) auxiliary history files are based on sug-

gested values in the IBM z/VSE System Control Statements manual for your VSE operating system.

2.3

Preparation Step 3: Allocate DASD for the Starter Database

This step is mandatory for the installation process, but optional for the migration process.

Allocate VSAM space for the Starter Database.

Figure 20 shows the approximate size of the Starter Database on various devices.

Figure 20 (Page 1 of 2). Recommended Starter Database DASD Sizes

Starter Database Data Set

3375 Cyls

3380 Cyls

3390 Cyls

9345 Cyls

Allocations

Directory

Log

Data Extend

Minimum

Recommended

121

Total Allocations

Minimum

104

DB2 for VSE Program Directory

Figure 20 (Page 2 of 2). Recommended Starter Database DASD Sizes

Recommended

187

119

101

132

Notes for Figure 20 on page 18:

A complete explanation of the Starter Database is in the DB2 Server for VSE System Administration

manual.

Fixed block (FB) storage devices store data in blocks of fixed size. These blocks are addressed by

block number relative to the beginning of the particular file.

In the installation process, you have to supply your own volume identifier when defining VSAM data sets.

Note that the Starter Database is designed to be installed on a single volume of a given device type.

Refer to the DB2 Server for VSE System Administration manual for more information on adding dbextents.

You can use any DASD currently supported by VSE/VSAM in your VSE system. If you are defining your

own database instead of using the Starter Database, refer to the DB2 Server for VSE System Adminis-

tration manual to estimate the space you require for a particular device to support a database of a given

size.

You can easily add dbextents or enlarge the directory after the database is generated. A utility program,

ARIMEXBD, is available to increase the size of the directory to support a larger VSAM dataset.

(See the

DB2 Server for VSE System Administration manual for information on ARIMEXBD.) Given the dbspace

definitions for the Starter Database, the actual space supported for public and private dbspaces is about

4.6 gigabytes.

2.4

Preparation Step 4: Restore the Distribution Library

This step is mandatory.

You can restore the DB2 Server for VSE Distribution Library in two ways. We recommend using the

VSE/Interactive Interface, Product Installation Dialog in z/VSE. If you use this method, you need to know

that DB2 Server for VSE is shipped on a NON-STACKED V2 FORMAT tape. For directions on using this

method, refer to the IBM z/VSE Installation for your VSE operating system.

If you have received your DB2 Server for VSE as part of your z/VSE order, see the z/VSE Installation

Manual 'Installing a Program from the z/VSE Extended Base Tape'

Alternatively, you may create the job control member shown in Figure 21 on page 20 to restore the Dis-

tribution Library. Mount the distribution tape and run your modified job.

Chapter 2. Preparing to Install DB2 Server for VSE 7.5

// JOB ARIS75AD

INSTALL DB2 Server

// MTC REW,cuu

*-- REWIND TAPE

// ASSGN SYS002,cuu1

*-- AUXILIARY HISTORY FILE

// ASSGN SYS005,UA

*-- NO RESTORE TO XXXXXX

// ASSGN SYS006,cuu

*-- DISTRIBUTION TAPE

// OPTION CATAL

// EXEC MSHP

INSTALL PRODUCT FROMTAPE ID='DB2/VSE

7.5.0' - *--ACTUAL TAPE ID (1)

PROD IN=PRD2.DB2750

*-- IDENTIFICATION OF LIBRARIES

(2)

DEFINE HISTORY AUX EXTENT=xxx:yyy

// MTC RUN,cuu

Figure 21. Job ARIS75AD (Using MSHP to Install DB2 Server for VSE)

Notes for Figure 21:

Before execution, modify the above statements as follows:

cuu

Replace with the address of the tape drive.

cuu1

Replace with the address of the disk drive on which the auxiliary history file resides.

xxx

Replace with the starting address of the auxiliary history file (in tracks or blocks).

yyy

Replace with the size of the auxiliary history file (in tracks or blocks).

You receive various messages from MSHP. These messages are normal and can be ignored. If you

want more details about the MSHP control statements, refer to the DB2 Server for VSE Messages and

Codes.

Later installation steps do not require the distribution tape.

(1)

DB2/VSE

7.5.0' is the actual ID of the tape.

(2)

If necessary, replace PRD2.DB2750 with the library and sublibrary names you used in

Figure 21.

2.5

Preparation Step 5: Prepare the CICS Environment

If you will not be using DB2 Server for VSE in an CICS interactive environment, or if you will not be using

ISQL, skip this step.

This step is optional for the installation process, but mandatory for the users who are migrating from a

previous release and are using ISQL.

To prepare the CICS system for DB2 Server for VSE, update the CICS control tables and modify the CICS

startup job control. The modifications to the tables take effect the next time the CICS system is stopped

for maintenance and then restarted. The changes to the startup job control ensure that the CICS system

can find the DB2 Server for VSE 7.5 sublibrary, and that the CICS subpool is properly defined. You may

also define a printer for ISQL.

You need to update the CICS control tables and startup job control to include journaling and the restart

resynchronization facility, to ensure the coordinated rollback of a CICS activity when a DB2 Server for

DB2 for VSE Program Directory

VSE activity is being rolled back. This is a requirement for CICS Database Switching support. Refer to the

DB2 Server for VSE System Administration manual for detailed information about this support.

Note: You have to allocate and format the journal files before restarting CICS.

Modifying the CICS Start-Up JCL

Figure 22 shows an example of CICS startup job control for the application server. Make sure that you

add the DB2 Server for VSE sublibrary in your library concatenation chain for your startup job.

// JOB CICS START

// LIBDEF PHASE,SEARCH=(PRD2.DB2750,...)

// UPSI 1

(1)

// DLBL SQLBIND,'DB2.BIND.MASTER',,VSAM=catalog,DISP=(OLD,KEEP) (5)

// DLBL SQLGLOB,'DB2.SQLGLOB.MASTER',,VSAM=catalog,DISP=(OLD,KEEP)

// DLBL ARITRAC,'TRACE.FILE1',

// EXTENT ,VOLXXX,1,0,nnn,120

(5)(6)

// ASSGN SYS007,cnn

// ASSGN SYS098,cuu

(2)

// EXEC DFHSIP,SIZE=nnnnK *-- DETERMINATION OF THE CICS SUBPOOL SIZE (3)

// EXEC DFHSIP,SIZE=DFHSIP,PARM='DSALIMIT=6M...' *-- FOR CICS/TS(3)

| Optional CICS System

| Initialization Parameter |

(4)

| Override Statements

Figure 22. Starting the CICS System for Use with ISQL

Notes for Figure 22:

(1)

In a VSE/ICCF environment, place the UPSI statement after the EXEC statement (see

note 3 below). The UPSI setting shown in the example allows reconfiguration at initializa-

tion time and console responses from SYSIPT. You may need to use different UPSI set-

tings for your environment.

(2)

The logical unit SYS098 is used for ISQL report output. For multiple-copy support, assign

SYS098 to a VSE/POWER-intercepted printer (cuu). ISQL uses the 8-position resource

name "PRINT98" to control use of the printer.

The logical unit SYS098 is also used for the Online Resource Adapter FFDC Dump output.

(3)

For CICS/VSE, EXEC statement parameter SIZE=nnnnK controls the CICS subpool size,

which is the amount of dynamic storage remaining after the CICS system assigns storage

for management and resident program purposes, and is shared by all CICS transactions.

(nnnn) specified depends on the CICS configuration.

Chapter 2. Preparing to Install DB2 Server for VSE 7.5

FOR CICS/TS, the dynamic subpool size is specified with the DSALIMIT startup param-

eter.

You need at least 3 megabytes of virtual storage below the 16MB line for the CICS/TS

partition to run DB2 in ICCF. Refer to the IBM z/VSE Planning manual for more inf

ormation on how to allocate storage for a CICS system.

(4)

DB2 Server for VSE 7.5 requires the CICS system to support journaling. Set bit 1 of the

UPSI to 1 to force the CICS system to read the optional CICS system initialization param-

eter override statements from SYSIPT. You can then include the journaling parameter in

the override statements.

(5)

These are the job control statements for the BIND file, the SQLGLOB file, and the trace

output DASD SAM file to the CICS startup JCL. The file IDs specified for SQLBIND and

SQLGLOB must be identical to the name of the file that was specified in the respective

DEFINE command of IDCAMS and listed in the VSE/VSAM catalog. See "Preparation Step

8: Setup the SQLGLOB and BIND files" for more information on the IDCAMS DEFINE

CLUSTER jobs for the SQLGLOB and SQLBIND files. SQLBIND is an optional dataset, it

is only required for DRDA application requester functions.

It is recommended that SQLGLOB and SQLBIND DLBL statements be placed in Standard

Labels (see Figure 32 on page 34).

(6)

If the output of the application requester trace is directed to tape, a TLBL statement for the

trace output file must be included in the CICS start-up job instead. An example of a TLBL

statement for a trace output file is as follows:

// TLBL ARITRAC,'TRACE.FILE2'

2.5.1

CICS Table Entries Required by DB2 Server for VSE 7.5

The following CICS resources must be updated to define the DB2 Server for VSE online support and ISQL

to the CICS system. DB2 Server for VSE programs and transactions in the CICS System Definition (CSD)

file:

DFHSIT

System Initialization Table

DFHTCT

Terminal Control Tables.

DFHFCT

File Control Table

The entries required for each table are described later in this step.

This manual describes only the CICS resources required for DB2 Server for VSE. For complete

descriptions of the CICS tables and parameters, refer to the CICS manuals.

To update the CICS tables, you must make the changes and recompile them. However, you have to wait

until the CICS system is stopped and restarted for the changes to take effect. You can change programs

and transactions with a batch job, or online using the Resource Definition Online (RDO) tool. For more

information on RDO and CEDA, see the CICS/VSE Resource Definition (Online).

Beside the minimum entries required to use DB2 Server for VSE online support and ISQL, the CICS Jour-

naling Support and the CICS Restart Resynchronization Support must be enabled. These are discussed in

DB2 for VSE Program Directory

"CICS Journaling Support" and in "CICS Restart Resynchronization Support" in this chapter. In addition,

you may make optional entries that allow you to use:

CICS Monitoring Facility

DB2 Server for VSE Accounting.

For a description of the entries required for each optional feature for CICS/ESA, refer to Appendix F,

"Additional CICS and VSE Updates for the DB2 Server System".

2.5.2

Entries Required in DFHSIT

The DFHSIT macro must always include:

AMXT=nn

Limit on the number of active tasks within the CICS system.

If you are adding DB2 Server for VSE work to an existing CICS environment, consider

increasing the AMXT value. Each active ISQL user requires two active tasks within the

CICS system. (If the AMXT limit is reached, response time may be adversely affected.)

DBP=YES|xx Dynamic transaction backout support.

Specifying DBP=YES requests use of the default dynamic transaction backout module. The

DBP parameter can be specified as DBP=xx, where "xx" is the 2-character suffix of the

module to be used.

EXEC=YES Command-level support.

EXITS=YES User exits will be used.

TST=NO|xx Identifies the auxiliary temporary storage program support.

Temporary storage queues defined to ISQL must be non-recoverable, because recoverable

storage queues are incompatible with ISQL. Temporary storage queues with names like

CISQXXXX and XXXXCISQ (where XXXX is the terminal ID) are reserved for use by

ISQL, and should not be used by other CICS applications.

For DB2 for VSE with CICS TS, the following System Initialization (DFHSIT) parameters are obsolete.

Refer to the CICS Release Guide below for a complete list of obsolete DFHSIT parameters.

AMXT=

EXEC=

(command level is mandatory)

EXITS= (the user-exit interface is always enabled)

MONITOR= (replaced by new monitoring parameters)

For information about the optional DFHSIT entries to control access to ISQL, see the DB2 Server for VSE

System Administration manual.

The DB2 Server for VSE installation process assumes that the application name identified by the DFHSIT

APPLID parameter is DBDCCICS. If the application name is not DBDCCICS, take special action (see

"Installation Step 7: Grant SCHEDULE Authority").

2.5.2.1

Entries in DFHTCT Required by ISQL:

The DFHTCT TYPE=TERMINAL macro must include:

Chapter 2. Preparing to Install DB2 Server for VSE 7.5

ALTSCRN=(lines,columns) Alternate screen size

This parameter is optional. Specify it if you want to use ISQL large-screen support for IBM

3270 terminals with screens larger than 24 rows by 80 columns.

DEFSCRN=(24,80) Default screen size

TRMSTAT=TRANSCEIVE Terminal status.

2.5.2.2

Entries in DFHTCT for CICS Local Terminal Printers:

The DFHTCT TYPE=TERMINAL macro should include the ALTPAGE and PGESIZE parameters.

If you specify FORMFEED=YES, the value you use for these two parameters should match the page size

of the CICS local terminal printer since the ISQL SET command will no longer have full control over the

page size.

If you specify FORMFEED=NO, assign the value (1,132) to the ALTPAGE and PGESIZE parameters. This

will allow the ISQL SET command to have full control over the page size.

To use the ISQL terminal printer support, define a DFHTCT entry for each terminal printer.

2.5.2.3

Entries in DFHFCT for DB2 Server for VSE: The entries in sample ARIS75FC, a

PROC-type member, should be placed in the

Terminal definitions can also be made in the CICS System definition facility. File Control Table (FCT) for

the CICS system in which online support is required. You can use a COPY statement to include the

entries. If you change the suffix on the FCT INITIAL statement, code an FCT=xx override on CICS Initial-

ization JCL.

DB2 for VSE Program Directory

***********************************************************

**********

DB2 FOR VSE AND VM 7.5

FCT ENTRIES

*********************************************************************

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

GLOBAL Variables

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

SQLGLOB DFHFCT TYPE=FILE,

ACCMETH=(VSAM),

FILE=SQLGLOB,

FILSTAT=(ENABLED,OPENED),

SERVREQ=(ADD,BROWSE,DELETE,UPDATE),

RSL=PUBLIC,

STRNO=2

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Preprocessor BIND file

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

SQLBIND DFHFCT TYPE=FILE,

ACCMETH=(VSAM),

FILE=SQLBIND,

FILSTAT=(ENABLED,OPENED),

SERVREQ=BROWSE,

RSL=PUBLIC,

STRNO=2

Figure 23. DFHFCT Sample entries

For CICS/TS, the file definitions can be made in the CICS System Definition facility.

2.5.3

CICS Journaling Support

If the CICS Journaling Support wasn't enabled when the CICS system was installed, you have to update

the following CICS tables to provide the Journaling Support required by DB2 Server for VSE.

DFHJCT

Journal Control Table

DFHSIT

System Initialization Table.

DFHJCT Entries:

A journal used for the CICS system log must be defined in DFHJCT by specifying JFILEID=SYSTEM in a

DFHJCT TYPE=ENTRY macro.

Figure 24 on page 26 shows an example of how to code DFHJCT for a CICS system log allocated to a

3380 DASD device.

Chapter 2. Preparing to Install DB2 Server for VSE 7.5

DFHJCT TYPE=INITIAL,SUFFIX=jj

(1)

DFHJCT TYPE=ENTRY,

JFILEID=SYSTEM,

BUFSIZE=1024,

BUFSUV=1024,

JOUROPT=(CRUCIAL,INPUT),

JTYPE=DISK1,

OPEN=INITIAL,

DEVADDR=sysxxx,

(2)

JDEVICE=3380

DFHJCT TYPE=FINAL

END DFHJCTBA

Figure 24. DFHJCT Examples for CICS Journaling

Notes for Figure 24:

CICS journal files must be formatted before use. See the CICS manuals for information on CICS

journal files.

(1)

The SUFFIX value jj must be supplied in the DFHSIT JCT=jj parameter.

(2)

sysxxx is the logical unit address for the CICS system log journal (JFILEID=SYSTEM)

assigned to a 3380 DASD file.

DFHSIT Entries:

The DFHSIT macro must include the JCT parameter. Specify JCT=YES or JCT=(jj<,

>) where jj is the

SUFFIX parameter value specified in the DFHJCT TYPE=INITIAL macro defining the CICS system log

journal data set.

2.5.4

CICS Restart Resynchronization Support

If the CICS Restart Resynchronization Support was not enabled when the CICS system was installed, you

have to update the following CICS tables to enable the CICS Restart Resynchronization capability.

DFHJCT

Journal Control Table

DFHSIT

System Initialization Table.

DFHJCT Entries:

A journal used for the CICS system log must be defined in the DFHJCT by specifying JFILEID=SYSTEM

in a DFHJCT TYPE=ENTRY macro.

Figure 24 is an example of how you could code your DFHJCT for a CICS system log allocated to a 3380

DASD device.

Programs and Transactions: Use the CICS RDO tool to add the resources required for CICS Restart

Resynchronization.

CEDA ADD GROUP(DFHRMI) LIST(VSELIST)

Use the list that is coded in the value for GRPLIST in your DFHSIT or CICS startup.

DB2 for VSE Program Directory

DFHSIT Entries:

The DFHSIT macro must include the JCT parameter. Specify JCT=YES or JCT=(jj<,

>) where jj is the

SUFFIX parameter value specified in the DFHJCT TYPE=INITIAL macro defining the CICS system log

journal data set.

2.5.5

CICS Transaction Server (TS) considerations

CICS internal security and therefore the CICS Sign-On table (DFHSNT) has been withdrawn in CICS TS

for z/VSE 3.1. Instead, any external securit y manager (ESM) may be used that conforms to the z/VSE

RACROUTE interface. Alternatively, the basic form of external security manager z/VSE 3.1 may be used.

The BSM provides sign-on and transaction attach security only.

When using an ESM, refer to the relevant documentation supplied with the ESM on defining DB2 for VSE

user id(s), operator data and transaction security. If the BSM is used, DB2 for VSE userids in the

DFHSNT and DB2 for VSE transactions must be defined using the VSE Interactive Interface

As the CICS TS System Definition (CSD) file is not compatible with earlier versions of CICS (e.g. CICS

2.3), a separate CSD file mustbe defined and all DB2 for VSE entries added using the DFHCSDUP utility

provided with CICS TS. All transaction Ids defined in the CSD file should be added to the VSE Trans-

action SECure Table(DTSECTXS.A) also.

For DB2 for VSE with CICS TS, the following System Initialization (DFHSIT) parameters are obsolete.

Refer to the CICS Release Guide below for a complete list of obsolete DFHSIT parameters.

AMXT=

EXEC=

(command level is mandatory)

EXITS= (the user-exit interface is always enabled)

MONITOR= (replaced by new monitoring parameters)

For more information on installing DB2 for VSE V7.5 with CICS TS, refer to the following publications:

CICS Release Guide

GC33-1645

CICS Migration Guide

GC33-1646

CICS Resource Definition Guide

SC33-1653

2.6

Preparation Step 6: Define DB2 Server Programs and Transactions

to CICS

Job name is ARIS75JD.

This step is mandatory if you will be using ISQL or online CICS transactions.

Job ARIS75JD is used to define resources to the CICS System Definition file, specifically Programs and

Transactions.

Start Job Manager - see Figure 82 on page 85.

Chapter 2. Preparing to Install DB2 Server for VSE 7.5

Parameter Name

Default value

Description

LIST

VSELIST

Name of the CICS definition List to

which the DB2 group has been added.

The List is referenced during CICS

startup.

GROUP

DB2750

Name of the group that contains the

run time routines and is in the group

list used during CICS startup.

CICSFILE

CICS.CSD

The VSAM catalog where CICSFILE

resides

CSDCAT

VSESP.USER.CATALOG

The VSAM catalog where CICSFILE

resides

TRANSEC

ISQL

Definitions will be made for ISQL.

Specify N to indicate that ISQL is not

used.

CICSTS

Specify N to use the CICS/VSE system

definitions. The default Y, will make

CICS Transaction Server entries.

Figure 25. The parameters for ARIS75JD

Expected return code is 4.

2.7

Preparation Step 7: Setup the SQLGLOB and BIND files

This step is mandatory if you will be using ISQL or online/batch applications or online/batch binding and

using DRDA.

This step is optional for Migration.

If you have used the default name for your existing DB2 system, then you should use a different dataset

name, if you are performing the installation process, and will be running both DB2 for VSE releases.

The SQLGLOB file is used to contain DB2 Server for VSE Global variables. Refer to the DB2 Server for

VSE System Administration Manual for more information.

When referencing the SQLGLOB file, after it has been defined, it is required to code the

DISP=(OLD,KEEP) parameter on the DLBL.

2.7.1

Defining the Global Variable File (SQLGLOB)

Job ARIS758D will be submitted to the VSE environment, followed by the jobs ARISGDEF, ARIS757D,

and ARIS759D.

DB2 for VSE Program Directory

Parameter Name

Default value

Description

VOLUME

XXXXXX

The volume in the VSAM catalog,

where the dataset will be defined

ATYPE1

TRACKS

The default allocation unit is Tracks.

Use BLK for FBA devices.

ALLOC1

This is the primary space allocation for

the VSAM dataset. The size of the

dataset is based on the number of

CICS users of DB2 for VSE. There will

be one record for each user who does

not use the system global defaults, and

will use his/her own. The default allo-

cation is sufficient for about 6000

users.

ALLOC2

This is the secondary space allocation

for the VSAM dataset. The allocation

unit is in tracks.

Figure 26. The parameters for ARIS758D

See global parameters.

The expected return code is 0. Return code 12 means that MASTERFILE already exists.

2.7.2

Updating the SQLGLOB file with IBM-Supplied Global Defaults

Submit ARISGDEF to update the SQLGLOB file with the IBM-supplied global SQLGLOB default values.

See global parameters.

Expected return code is 0.

2.7.3

Defining the Preprocessor Bind File

Job ARIS757D is required for batch or online binding only. This dataset is a repository for preprocessor

bind files(bind-records), which will be bound to application servers.

Chapter 2. Preparing to Install DB2 Server for VSE 7.5

Parameter Name

Default value

Description

BINDCAT

VSESP.USER.CATALOG

The VSAM catalog where BINDFILE

resides

VOLUME

XXXXXX

The volume in the VSAM catalog,

where the BINDFILE will be defined

ALLOC1

This is the primary space allocation for

the VSAM dataset. The size of the

dataset is based on the number of bind

files contained in it, and on the size of

the packages.

The allocation unit is ATYPE param-

eter.

ALLOC2

This is the secondary space allocation

for the VSAM dataset. The size of the

dataset is based on the number of bind

files contained in it, and on the size of

the packages.

The allocation unit is ATYPE param-

eter.

Figure 27. The parameters for ARIS757D

Expected return code is 0. Return code 12 means that BINDFILE already exists.

2.7.4

Defining the Preprocessor Bind Work File (BINDWKF)

Job ARIS759D is required for batch and online binding. This dataset is a repository for preprocessor bind

files(bind-records) which will be bound to application servers.

Parameter Name

Default value

Description

BINDWCAT

VSESP.USER.CATALOG

The VSAM catalog where BINDFILE

resides

VOLUME

XXXXXX

The volume in the VSAM catalog,

where the BINDFILE will be defined

ALLOC1

This is the primary space allocation for

the VSAM dataset. The size of the

dataset is based on the size of the

packages.

The allocation unit is Cylinders

ALLOC2

This is the secondary space allocation

for the VSAM dataset. The size of the

dataset is based on the size of the

packages.

The allocation unit is Cylinders

Figure 28. The parameters for ARIS759D

Expected return code is 0. Return code of 12 means that BINDWKF already exists.

DB2 for VSE Program Directory

2.7.5

Loading the ISQL bindfile ARISIQBD.A to a VSAM bindfile File

Job ARISIQBD is required by batch or online to create ISQL package. The ISQL package is required by

ISQL, to be available at the target server. Job ARISIQBD will load the supplied A-type member ARISIQBD

in the VSAM Bind file.

Parameter Name

Default value

Description

BINDCAT

VSESP.USER.CATALOG

The VSAM catalog where BINDFILE

resides

READ MEMBER

ARISIQBD.A

Bindfile that need to be loaded

Figure 29. The parameters for ARISIQBD

Expected return code is 0.

If the ISQL bind file cannot be stored on the VSAM dataset, the following message is displayed on the

VSE console:

ISQL BIND FILE CANNOT BE BUILT DUE TO ERROR

Otherwise, the following message will be displayed:

ISQL BIND FILE BUILT SUCCESSFULLY

2.7.6

Loading the other bindfiles (A-member) to a VSAM bindfile

IBM does not provide you VSAM bindfile that contains ISQL, DBSU and Stored Procedure bindfiles(bind-

records) that are created as result of prep with "BIND" option. Instead,Bindfile (bind-records) of

ISQL,DBSU and Stored Procedures are sent as A-member.You need to create your own VSAM bindfile

and load bindfiles provided you as A-member. One job to load each of the bindfile has been provided.

Jobs are ARIXU01B ARIXU02B ARIXU03B ARIXU04B ARIXU05B ARIXU06B ARIXU07B ARIXU08B

ARIXU09B ARIXU10B ARIXU11B ARIXU12B ARIXUPTB ARIDSQLB Each job will load the corresponding

A-member into VSAM bindfile as one record for each member.

By default, ARISIQBD.Z loads supplied A-type member ARISIQBD in the VSAM Bind file. ARISIQBD can

be used to load DBSU and Stored Procedure bindfiles (A-members) by replacing the name of ARISIQB.A

to any other bindfile (like ARIXU01B.A).

Chapter 2. Preparing to Install DB2 Server for VSE 7.5

Parameter Name

Default value

Description

BINDCAT

VSESP.USER.CATALOG

The VSAM catalog where BINDFILE

resides

READ MEMBER

ARIXU01B.A