Content      ..     4      5      6      7     ..

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

1.2.4

Program Source Materials

There are no source materials available for DB2 for VSE.

1.3

Program Support

This section describes the IBM support available for DB2 for VSE.

1.3.1

Preventive Service Planning

Before installing DB2 for VSE, check with your IBM Support Center or use either Information/Access or

SoftwareXcel Extended to see whether there is additional Preventive Service Planning (PSP) information

that you should know. To obtain this information, specify the following UPGRADE and SUBSET values:

Figure 9. PSP Upgrade and Subset ID

UPGRADE

SUBSET

RETAIN Release

DB2VSEVM750

DB2VSE

5NN

1.3.2

Statement of Support Procedures

Report any difficulties you have using this program to your IBM Support Center. If an APAR is required,

the Support Center will provide the address to which any needed documentation can be sent.

Figure 10 identifies the component IDs (COMPID) for DB2 for VSE.

Figure 10. Component IDs

COMP ID

Component Name

CLC

5697-F42-01

DB2 Server for VSE V750

5NN

1.4

Program and Service Level Information

This section identifies the program and any relevant service levels of DB2 for VSE. The program level

refers to the APAR fixes incorporated into the program. The service level refers to the PTFs integrated.

Information about the cumulative service tape is also provided.

1.4.1

Program Level Information

This version of DB2 Server for VSE has incorporated all closed APARs from previous versions/releases at

the time of the product General Availability.

4

DB2 for VSE Program Directory

The z/VSE 3.1 system supplies the minimum requirements to support DB2 for VSE. However, the APARS

described in "Service Level Information" must be applied.

Refer to the planning manual for your VSE system to determine whether DB2 for VSE is supported as an

optional product.

If you have CICS transactions that access local DB2 for VSE Server(s), you must use the restart resyn-

chronization capability of CICS. Section 2.6: Prepare the CICS Environment, describes the CICS table

updates needed to use restart resynchronization.

If you plan to use non-DB2 for VSE facilities to backup a database, you can use the VSE/VSAM

Backup/Restore Feature.

Note: Backing up your data is vital to provide operational integrity.

Users of Double-Byte Character Set (DBCS) data should consider the following:

¹

PL/I programs using DBCS require no additional preprocessing (the PL/I compiler supports DBCS).

¹

DBCS variables and constants are not supported in FORTRAN and Assembler programs. This does

not prevent you from using DBCS in dynamically defined SQL statements.

¹

In COBOL/VSE programs for VSE, SQL identifiers, SQL host variables, and SQL labels with DBCS

characters can be used in SQL statements. The COBOL Kanji Preprocessor is not required.

A complete description of the software and hardware requirements is listed in chapter 1 of the DB2 Server

for VSE System Administration manual, GC09-2981. Read this chapter before you begin your installation.

DB2/VSE Components1

Supported Languages

DB2/VSE Environments

Base

ORA

ISQL

PL/I

Cobol

Fortran

C

ASM

Batch

X

X

X

X

X

X

Online

X

X

X

X

X

X

X

Interactive application

X

X

X

X

X

X

X

X

development

Query/Report Writing

X

X

X

DRDA Requestor

X

X

X

X

X

X

Notes:

1

For this column:

¹

Base refers to the database manager components that support batch applications, the pre-

processors, and the utilities including the database services (DBS) utility.

¹

ORA (online resource adapter) refers to the DB2 Server for VSE support for transaction proc-

essing (CICS*) environments.

¹

ISQL refers to the terminal user query and report-writing facilities.

Figure 11. VSE Environments

Prerequisite programs should be installed before you begin to do any of the steps described in this

manual.

6

DB2 for VSE Program Directory

Figure 12. Initial Storage Requirements of DB2

Server for VSE Database Partitions

Recommended Minimums for

Formula/Constraints

Single-User Mode

Multiple-User Mode

DB2 Server for VSE Code 1, 12

4011168

3642056

Code for DRDA password encryption 16

0

0

Message Repository 12

250000

250000

DB2 Server for VSE Control Blocks

¹ Base

140000

140000

¹ Lock Request Blocks

NLRBS x 24 2, 3, 5 + 32

12320

60512

¹ Concurrent Scans Storage

NCSCANS x 50 2, 3 x (NCUSERS+4) 2, 6

4500

13500

¹ Miscellaneous LRBs

8 x (First Prime Number > (NLRBS/4))

1048

5048

¹ Static Agent Storage below 16M

NCUSERS x 57500 12

57500

287500

¹ Static Agent Storage anywhere

NCUSERS x 50000

50000

250000

¹ Working Storage Area 12

109000

109000

¹ Working Storage Queue Headers 2, 3

32 + (2 + 2 x (NCUSERS + 4) + NPACKAGE x

(NCUSERS + 1)) x 68

984

5472

¹ Package Control Blocks

NCUSERS x NPACKAGE x 72 bytes 2, 3

72

3600

¹ Communications Control Blocks

RMTUSERS x 710 2

0

0

¹ If TCP/IP Communications is used, add:

(NCUSERS+4) x 501+36600 15

0

0

¹ Stored Procedure Caches

(76 * the number of stored procedure servers)

+(32 * the number of stored procedure server groups)

+(for each procedure,

116

+the length of the LE options string (max 254)

+ (68 * the number of parameters) )

0

0

DB2 Server for VSE Buffers

¹ 4 x Maximum of ((the first power of 2

that is >= (NPAGBUF/8)) or 256) + (NPAGBUF x 4144)

2

59040

125344

¹ 4 x Maximum of (the first power of 2

that is >= (NDIRBUF/8)) or 256) + (NDIRBUF x 560)2

8864

17824

Database Control Blocks

¹ Base control blocks

88000

88000

¹ MAXDBSPC x 8 11

8000

8000

¹ MAXPOOLS x 18 11

576

576

¹ MAXEXTNT x 8 11

384

384

Database I/O Control Blocks

¹ NCUSERS x 216 x # of dbextents

2808

14040

¹ Minimum of (64 or NPAGBUF/10) x (NCUSERS+3) x 64

14

1344

1536

VSAM Control Blocks

¹ (NCUSERS x 1024 + 8192) x # of dbextents 4, 15

119808

173056

¹ VSAM Catalogs 13

81920

81920

---------------

---------------

5007336 7, 8

5277368 7, 8

8

DB2 for VSE Program Directory

Figure 13. Virtual Storage Requirements of DB2 Server for VSE Components in the CICS Partition

ONLINE RESOURCE ADAPTER:

Initialization, Termination,

666 280

(See Note 2)

and Transaction Display

Global Control Blocks

1200 + 8 192 x Number of links from the

CICS/VSE partition to the

Database partition (See Note 3)

Execution Time Code

215 000

Execution Time Control Blocks

3 x Maximum number of CICS/VSE transactions

that will access concurrently (See Note 3)

ISQL

613632 + Online resource manager requirements

+ 45000 for each ISQL user

+ 200000 for each additional message repository

Notes:

1. All numbers are in bytes.

2. The initialization/termination/transaction display code needs to be in the CICS partition only when the

CIRA, CIRB, CIRC, CIRT, or CIRD transactions are active. For certain abnormal conditions, the

system internally activates CIRT.

(For more information, see the manual.) This value is calculated by

adding the sizes of the following phases: ARIRCONT, ARI0OLRM, ARIMS001, and ARICMOD. If

CICS is not able to load the termination phase, the CICS/VSE system waits until storage becomes

available. Shutdown is thus delayed, and the wait can be long. Shutdown must complete its process

before online access to the database manager can be restarted. Therefore, it is important that the

CICS partition contain enough virtual storage to allow the initialization/termination/transaction display

code to run. (To avoid the problem of not being able to load the termination code at a critical time,

consider specifying RES=YES in the DFHPPT entry for ARIRCONT.)

3. The global control blocks are maintained until CIRT (termination) completes its processing. If the

virtual storage requirement for the control blocks is less than 32768 bytes, CICS provides the storage

from its own pool. Otherwise, the partition’s GETVIS area is used.

4. For execution time control blocks:

¹

This storage requirement does not include the virtual storage used by the application transaction.

¹

The maximum number of CICS transactions that concurrently access the database manager is not

the value NOLINKS (used by the CIRB transaction). The 3-kilobyte virtual storage area is required

for a transaction from the time of the first database manager access until the end of the trans-

action.

¹

During online link initialization, a message buffer of 8192 bytes is obtained. This message buffer

(mailbox) is used by the resource adapter to gather all the inputs generated by one SQL state-

ment. The inputs are sent as one contiguous message to the database partition. If the SQL state-

ment generates more input than 8192 bytes, the resource adapter attempts to get a larger

message buffer from the partition’s GETVIS area.

10

DB2 for VSE Program Directory

If the GETVIS fails due to insufficient storage, SQLCODE -932 and an indication (SQLERRD1) of

the amount of storage required are returned to the transaction. If this occurs, either the GETVIS

area must be made larger, or the transaction must be run when fewer transactions are active.

5. For online application programs, if the fetch/insert blocking option is in effect, add 8 kilobytes to the

CICS partition size for each currently open cursor that qualifies for blocking.

6. The numbers shown in the figure do not include a user-written accounting exit.

7. If DRDA is used, add 1 megabyte to the CICS partition size to allow for the additional code in the

online resource adapter.

Figure 14. Recommended Virtual Storage Increase for User Machine

Recommended Minimum Virtual Storage Increase for a VSE

DB2 Server for VSE Component

Partition (in Kilobytes)

Batch resource adapter

365 (if base code installed)

2260 (if DRDA code installed)

DBS utility

225 + batch resource adapter =

590 (base)

225 + batch resource adapter = 2485 (DRDA)

Any DB2 Server for VSE

250 + batch resource adapter =

615 (base)

preprocessor

250 + batch resource adapter = 2510 (DRDA)

(PL/I, Assembler, COBOL,

FORTRAN, or C)

User program

User application size + batch resource adapter

Notes:

1. The batch resource adapter uses a minimum of 365 kilobytes of virtual storage in the batch (or

VSE/ICCF) application's partition. This value must be added to the virtual storage requirements of the

SQL application to arrive at the total VSE or VSE/ICCF partition size.

2. For programs running in multiple user mode, if the fetch/insert blocking option is in effect, add 8 kilo-

bytes for each currently open cursor that qualifies for blocking.

3. If you have coded an accounting exit, a cancel exit or a TRANSPROC, add its size to the total virtual

storage requirements.

1.7

CICS Dynamic Storage Considerations

The amount of virtual storage in the CICS dynamic area varies for ISQL. An average of 35 to 45 kilobytes

for each user, plus 330 kilobytes, is recommended at the start. This supports most ISQL usage. The fol-

lowing variables can be considered to adjust the size of the dynamic area:

¹

Use of SELECT

¹

Use of routines

¹

Other CICS transactions.

Chapter 1. Before You Begin

11

2.0

Chapter 2. Preparing to Install DB2 Server for VSE 7.5

To prepare to install DB2 Server for VSE:

1. Read "Appendix A: How to Use the Job Manager".

2. Read "Planning for Installation" in the DB2 Server for VSE System Administration Manual

3. Ensure that the VSE operating system and all necessary programs are already installed and running

correctly. (See "Prerequisite Programs" in Chapter 1)

4. Review this document completely before installing DB2 Server for VSE. For any optional steps, under-

stand why the step is optional.

5. Review the section on service considerations, check for any prerequisite program temporary fixes

(PTFs). Contact the IBM Support Center, or access with Information/Access or IBM Link, to see

whether there is any additional preventative service planning (PSP) information which you should be

aware of.

6. Complete all of the mandatory steps in this chapter, and any optional ones that apply to your installa-

tion. These steps are shown in Figure 17.

Step

Optional/ Manda-

Automated/ Manual

Description

tory

1

M

Manual

Set up the VSE Environment

2

M

Manual

Allocate DASD for the Distribution

Library

3

M 1

Manual

Allocate DASD for the Starter Database

4

M

Manual

Restore the DB2 Server for VSE Dis-

tribution Library

5

O

Manual

Prepare the CICS Environment

6

O

Automated

Define CICS programs and Trans-

actions

7

O

Automated

Setup the SQLGLOB and BIND files

8

M 1

Automated

Define VSAM Data Sets for the Starter

Database

9

M

Automated

Update Labels for the New Datasets

Figure 17. Preparation Steps

Note:

1. The Starter Database is mandatory for Installation, and optional for Migration

Figure 18 on page 16 includes the global variables required in the Preparation Step.

 Copyright IBM Corp. 1981, 2007

15

Content      ..     4      5      6      7     ..