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

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

2.6.5

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

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

required by ISQL, to be available at 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 needs to be loaded

Figure 24. 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.6.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 A-member has been provided. Job

names are in the format ARIXUxxB. 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

ARISIQBD.A to any other bindfile (like ARIXU01B.A).

Parameter Name

Default value

Description

BINDCAT

VSESP.USER.CATALOG

The VSAM catalog where BINDFILE

resides

ARIXUxxB.A

Bindfile that needs to be loaded

Figure 25. 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:

Chapter 2. Preparing to Install DB2 Server for VSE Client Edition 7.5

ISQL BIND FILE CANNOT BE BUILT DUE TO ERROR

Otherwise, the following message will be displayed:

ISQL BIND FILE BUILT SUCCESSFULLY

2.7

Preparation Step 7: Updating Labels for the new datasets

Job name is ARISSTDL.

This step is Mandatory.

The job will add the labels for the new datasets to the standard label area.

It is recommended that the labels for the new datasets (SQLGLOB, SQLBIND, and BINDWKF) be added

to the system standard labels at system initialization. For co-existance consideration: if you have an

existing DB2 Server for VSE installed, you may want to create a

PROC for the labels required by DB2 Server for VSE, Client Edition instead of adding them to the

standard labels at system initializ ation. Please refer to the "z/VSE System Control Statements" and the

"VSE Guide to System Functions" for more information.

Parameter Name

Default value

Description

BINDCAT

VSESP.USER.CATALOG

The VSAM catalog where BINDFILE

resides

BINDWCAT

VSESP.USER.CATALOG

The VSAM catalog where BINDWFILE

resides

Figure 26. The parameters for ARISSTDL

Also see global parameters.

Note: The DLBL for BINDWKF must not have the DISP parameter coded.

Expected return code is 0.

DB2 for VSE Client Edition Program Directory

3.0

Chapter 3. Installing DB2 Server for VSE Client Edition

To install this product:

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

2. Refer to Appendix B, "Techniques Used for Installation" for a description of how to adapt the

IBM-supplied materials to your local needs.

3. Complete the steps in Chapter 2, "Preparing to Install DB2 Server for VSE Client Edition 7.5"

4. Perform all the mandatory steps in this chapter, and any of the optional ones that apply to your instal-

lation (See Figure 27).

Attention: If any procedure within any of the steps in this chapter fails to execute successfully, fix the

problem and rerun the step again before continuing.

Step

Optional/ Manda-

Automated/

Description

tory

Manual

Mandatory

Manual/ Auto-

Set up DBNAME Directory

mated

Mandatory

Automated

Set up default userid and password in ARISICON "A"

Member

Mandatory

Automated

Link-Edit the DB2 Server for VSE online Support Components

Mandatory

Manual

Start the default database server

Optional

Automated

Install Optional Components

Optional

Automated

Reload CCSID-Related Phases Package

Optional

Automated

Selecting National Language Support

Optional

Automated

Grant Schedule Authority

Optional

Automated

Create CCSID-Related Phases (Target DB must be DB2 on

VSE or VM)

Optional

Automated

Run the Sample Programs to verify Installation

Optional

Manual

Run ISQL to Verify Installation

Optional

Manual

Stop the DB2 VSE Client

Optional

Manual

System Customization Activities

Figure 27. Steps to Install DB2 Server for VSE Client Edition version 7 Release 5

 Copyright IBM Corp. 1981, 2007

Parameter Name

Default value

Description

Used in member:

PROC1

ARIS75DB

DB2 Server DATABASE ID

ARIS75WD

Proc

COMPILELIB

PRD2.DB2750C

Library for cataloging

ARISCNVD, ARIS6ASD,

PHASE type members

ARIS6C2, ARIS6CD,

ARIS6PLD, ARIS6FTD

WDISK

SYSWK1

Sequential workdisk volume

ARISCNVD, ARIS6ASD,

ARIS6C2, ARIS6CD,

ARIS6PLD, ARIS6FTD

START

xxxx

Start track or block allocated

ARISCNVD, ARIS6ASD,

for SYSPUNCH and

ARIS6C2, ARIS6CD,

SYSIPT.

ARIS6PLD, ARIS6FTD

FOR

xxxx

Extent size in tracks or

ARISCNVD, ARIS6ASD,

blocks allocated for

ARIS6C2, ARIS6CD,

SYSPUNCH and SYSIPT.

ARIS6PLD, ARIS6FTD

GLOBFILE

DB2.SQLGLOB.MASTER

This is the name of the

ARIS6ASD, ARIS6CD,

dataset which will hold the

ARIS6PLD, ARIS6FTD

global variables

CATALOG

VSESP.USER.CATALOG

The VSAM catalog where

ARIS6ASD, ARIS6CD,

SQLGLOB resides

ARIS6PLD, ARIS6FTD

LELIB

PRD2.SCEEBASE

Language Environment

ARIS6C2D, ARIS6CD,

library

ARIS6PLD

Figure 28. Description of global parameters

3.1

Installation Step 1: Setup the DBNAME Directory

Job name is ARISBDID.

This step is mandatory. Required for Local and Remote databases.

1. Punch the A-type source member ARISDIRD.

2. Update the DBNAME and other parameters. See "DB2 Server for VSE System Administration"

manual "Chapter 2: Setting Up the DBNAME Directory" for information about the input file format and

syntax.

3. Re-catalog the A-type source member ARISDIRD.

Start Job Manager - see Figure 59 on page 60.

Job ARISBDID (see Figure 29 on page 31) converts A-type source member ARISDIRD into an assembler

source file, which will be assembled and link-edited into two PHASEs, namely, ARICDIRD.PHASE for

online and ARICDBND.PHASE for batch.

DB2 for VSE Client Edition Program Directory

// SETPARM ISMIGR=%%MIGRATION%%

// IF ISMIGR='NO' THEN

// GOTO GENERATE

// EXEC REXX=ARICCDID, PARM='%%PLIB%%.%%INPUT%% %%LIB1%%.%%OUTPUTA%%'

/. GENERATE

// LIBDEF *,SEARCH=%%LIB1%%

// LIBDEF PHASE,CATALOG=%%COMPILELIB%%

*-- UPDATE LIBRARY

// EXEC REXX=ARICBDID,PARM='%%LIB1%%.%%OUTPUTB%%'

(1)

// IF $RC <

4 THEN

// GOTO EXITOK

/. ERREXIT

* SQL/DS DBNAME DIRECTORY CANNOT BE BUILT DUE TO ERROR

// GOTO SQLDONE

/. EXITOK

* SQL/DS DBNAME DIRECTORY BUILT SUCCESSFULLY

/. SQLDONE

Figure 29. Job ARISBDID (Setup DBNAME directory)

Notes for Figure 29:

(1)

%%LIB1%%.%%OUTPUTB%% is the input Dbname Directory source member. The

default parameter is: 'PRD2.DB2750C.ARISDIRD.A' - see Figure 30.

Parameter Name

Default value

Description

MIGRATION

Should be 'NO' for Installation process

OUTPUTB

ARISDIRD.A

Member containing defaults for

DBNAME

LIB1

PRD2.DB2750C

Installation Library

Figure 30. The parameters for ARISBDID

A return code of 2 is acceptable for this job. ARICDIRD.PHASE and ARICDBND.PHASE are created.

3.2

Installation Step 2: Setup default userid and password

Job name is ARIS75CZ.

This step is mandatory. Required for Local and Remote databases.

1. This step generates an A member ARISICON which will contain an SQL CONNECT statement. The

userid and password for the CONNECT statement will be read from the GLOBAL parameter section in

Installation section in the Z member ARISIVRR. The generated ARISICON.A member will be placed

in the installation sublibrary that will be read by other job steps such as ARIS360D, ARIS130D,

ARIS110D and ARIS063D.

Chapter 3. Installing DB2 Server for VSE Client Edition

Parameter Name

Default value

Description

DBUSRID

uuuuuuuu

Default administrative DBA userid

DBPWORD

pppppppp

Default administrative DBA password

Figure 31. The parameters for ARISIVRR

3.3

Installation Step 3: Link-Edit the DB2 Server for VSE Client Edition

Online Support Components

Job name is ARIS75BD.

This step is optional. Required for Local and Remote databases with CICS/VSE or CICS/TS.

If you will not be using DB2 Server for VSE Client Edition online support in a CICS interactive environ-

ment, skip this step.

Job control member ARIS75BD is used to link-edit the online support components. The link-edit will

include the CICS interface modules DFHEAI and DFHEAI0, found in the CICS PRD1.BASE sublibrary.

The output is cataloged to the installation library by default. If you want to use your own libraries, change

the parameter value.

If you do not want ISQL support, and only want support for your own CICS online applications, then set

the ARIS140D, ARIS150D, and ARIS160D parameters to *.

Parameter Name

Default value

Description

CICSLIB

PRD1.BASE

This is the name of the sublibrary

where CICS components are installed.1

ARIS140D

Default parameter to include ISQL

support. Enter * to omit this job.

ARIS150D

Default parameter to include ISQL

support. Enter * to omit this job.

ARIS160D

Default parameter to include ISQL

support. Enter * to omit this job.

Figure 32. The parameters for ARIS75BD

Note:

(1) The library search path is:

// LIBDEF *,SEARCH=(%%LIBNAME%%,%%CICSLIB%%,PRD2.CONFIG)

where LIBNAME is the installation library name. See Figure 60 on page 61.

Expected return code is 0.

DB2 for VSE Client Edition Program Directory

3.3.1

Installation Step 3.1: Link-Edit the DB2 Server for VSE Client

Batch

Resource Adapter DRDA code with Assembler Interface

This step is required for Remote databases.

Job name is ARIS75LD

This step is optional for the installation process.

Job ARIS75LD generates the batch resource adapter for a remote database environment by link-editing

the required object modules and producing the ARIRBARM.phase for batch.

3.4

Installation Step 4: Start the Default Database Server

This step is optional for the installation process. Only required for Local databases.

Bring up the default application server to which the installation process will connect to for binding DB2

VSE Client Applications,

Reload help text, reload CCSID packages (if the server is DB2 on VSE or VM). The optional steps to

perform the above mention steps will be carried

out only if this step is successfully completed and the

application server is running.

For information to bring up DB2 Server on VSE and VM, please refer to DB2 Server for VSE and VM

Operations Manual. For any other application server, please refer to respective program manuals.

3.5

Installation Step 5: Install Optional Components

This Step will be performed only if Step 4: Start the Default Database Server is successfully completed.

This step involves execution of two jobs ARIS75DU and ARIS75ED.

This step is optional and is onlt required for local databases.

We recommend that you install all these optional client components, even if you do not plan to use them

now.

Job ARIS75DU prepares the batch utility, DBSU to facilitate some of the Installation steps that follow

which use this utility to update the tables in the default database (the default database is identfied by the

keyword SYSDEF=Y in the DBNAME directory built in Installation Step 1).

Job ARIS75ED contains the job control statements to load the optional components of a database into an

existing database. You may omit specific optional components by removing the procedures in job

ARIS75ED that create that component.

If you do not want ISQL support, then set the ARIS110D, ARIS120D, ARIS130D parameters to *.

Chapter 3. Installing DB2 Server for VSE Client Edition

Parameter Name

Default value

Description

ARIS110D

Install ISQL

ARIS120D

Install ISQL

ARIS130D

Install ISQL

Figure 33. The parameters for ARIS75ED

Expected return code is 0.

Note:

The ARIS75ED job runs the application server in single user mode. Ensure that it runs in the

DB2 Server for VSE partition as described in "Preparation Step 3: Set Up the VSE Environ-

ment".

Procedure ARIS080D installs the DB2 Server for VSE online support, which you need to run

ISQL or any of your own interactive applications.

Procedure ARIS360D loads the FIPS flagger into the database. For more information on the

FIPS flagger, see the DB2 Server for VSE & VM Application Programming.

3.6

Installation Step 6: Reload CCSID-Related Phases Package

This Step will be performed only if Step 4: Start the Default Database Server is successfully completed.

Job name is ARIS75WD.

This step is optional and only required for local databases.

Job control member ARIS75WD, contains the job control statements to load the CCSID-related phases

package into the database. Procedure ARIS175D reloads the CCSID-related phases package in the data-

base by running the application server in single user mode or multiple user mode against that

database(defined in DBNAME Directory).

Parameter Name

Default value

Description

SUM

Load CCSID-Related Package in

Single User Mode. Code N to use Mul-

tiple User Mode.

DBNAME

SQLDS

Database to load the CCSID-Related

Package to in Multiple User Mode.

Figure 34. The parameters for ARIS75WD

Expected return code is 4.

DB2 for VSE Client Edition Program Directory

3.7

Installation Step 7: Selecting National Language Support

This Step will be performed only if Step 4: Start the Default Database Server is successfully completed.

Job name is ARIS75HZ.

This step is optional and only required for local databases.

This step will install a national language for DB2 Server for VSE, and optionally load the ISQL Help Text

for that language. The following steps will be performed:

Enlarge Help Text Dbspace.

"Install" Language.

Verify Installation.

Parameter Name

Default value

Description

PAGES

8192

Number of pages acquired for the

HELPTEXT DBSpace. Default value

8192 is enough to define 3 languages.

Figure 35. The parameters for ARIS75HZ

Expected return code is 0.

3.7.1

Install Language and ISQL Help Text

The ARIS75JZ Z-type member calls the ARIS380D PROC-type member that was modified according to

the parameters specified in ARISIVRR file when you started the Installation Step (Chapter 3). If you have

modified the parameters used in ARIS380D (Figure 37 on page 36) in ARISIVRR file after executing

Installation Step 1, you might need to update ARIS380D file manually before submitting ARIS75JZ.

This is only necessary if the Help Text Dbspace is not large enough to hold the addition of this language.

As supplied, DB2 Server for VSE has 8192 pages assigned for the PUBLIC.HELPTEXT dbspace. This is

sufficient for the Help Text for 3 languages.

Language List:

Language

Short Name

Mixed English

AME

Uppercase English

UCE

French

FRE

German

GER

Japanese

KAN

Chapter 3. Installing DB2 Server for VSE Client Edition

Parameter Name

Default value

Description

LANGUAGE

AME

Short form of the language name, taken from the language

list.

HELP

If you want only the ISQL help text to be loaded, change

value to HELP=ONLY. To install a National language in addi-

tion to the Help Text, set HELP=YES. If you do not want Help

Text to be loaded keep current value.

CUU

181

Tape drive address.

DEFAULTL

If you want this language to be the default language, set

DEFAULTL parameter to YES. Otherwise, set the value to

NO.

Figure 36. The parameters for ARIS75JZ

Parameter Name

Default value

Description

NLSLIB

PRD2.DB275 (For AME)

Language Library.

Note: There is no '0' at the

Note: The name of NLSLIB must not exceed 5 characters,

end of PRD2.DB275.

since NLS suffix is 3 characters - making library name

8 characters.

The NLS suffix will be added during the execution of

the program. The suffix is generated by procedure

ARIS385D.

For LANG=AME library will be PRD2.DB2750

For LANG=FRE library will be PRD2.DB275S03,etc.

CLIB

PRD2.DB2750C

The Installation Library

Figure 37. The parameters for ARIS380D

Note: Read "Appendix A: What should you keep in mind."

ARIS75JZ job will perform the following functions:

Define a sublibrary for the language components

Linkedit the message repository

Update SQLDBA.SYSLANGUAGE with language key and language id

Linkedit language specific parts

Change the default language if requested

Load Help text if requested.

Expected return code is 0, however, return code 6 is acceptable.

DB2 for VSE Client Edition Program Directory

3.8

Installation Step 8: Grant SCHEDULE Authority

Job name is ARIS75FD.

This step is optional and only required for local databases. This step is to enable the Client Edition to

CONNECT to a database server on VSE. If the target database server is on a non VSE platform this step

can be skipped.

If the CICS application name specified in the SIT table is DBDCCICS (APPLID=DBDCCICS) and you are

using the default password (SQLDBAPW), skip this step.

In "Installation Step 5: Install Optional Components", procedure ARIS080D granted SCHEDULE authority

to user ID DBDCCICS and assigned it the password SQLDBAPW. DBDCCICS is the default CICS appli-

cation name (APPLID). This would apply if the customer has a VSE or VM Guest Sharing database

server.

However, if in "Entries Required in DFHSIT", you specified a different CICS application name in the SIT

(APPLID=name), this name should be granted SCHEDULE authority instead. To do this, run job control

member ARIS75FD, shown in Figure 38. From the following example,

// EXEC PGM=DFHSIP,SIZE=DFHSIP,PARM='APPLID=OMYGW001 ...

you would GRANT SCHEDULE to OMYGW001

The password (namepw) specified in the GRANT SCHEDULE command must also be specified in the

CIRB and CIRT transactions used to start and stop the DB2 Server for VSE online support.

See "Starting the DB2 Server for VSE Online Support" on page 43 and "Stopping the DB2 Server for VSE

Online Support" on page 46. For details on the CICS APPLID, refer to the CICS manuals.

Parameter Name

Default value

Description

NAME

DBDCCICS

CICS application name

(APPLID=name)

NAMEPW

SQLDBAPW

Password

SUM

Load CCSID-Related Package in

Single User Mode. Code N to use Mul-

tiple User Mode.

DBNAME

SQLDS

Database to load the CCSID-Related

Package to in Multiple User Mode.

Figure 38. The parameters for ARIS75FD

Expected return code is 0.

Chapter 3. Installing DB2 Server for VSE Client Edition

3.9

Installation Step 9: Create CCSID-Related Phases

Job name is ARISCNVD.

There are three default copies of CCSID-Related Phases that are shipped in product tape which will be

copied to the distribution library during installation of the DB2 Server for VSE Client Edition. But this might

not contain some conversion code pages that are not part of the standard list.

If the default server that was brought up in "Installation Step 4: Start the Default Database Server" con-

tains these customer specific conversion then this step can be run to regenerate the CCSID-Related

phases. This job step can be skipped and run post installation if the target server is not the default server.

This step is optional and only required for local databases. ARISCNVD must be executed while the data-

base

server is active.

Parameter Name

Default value

Description

PARMS

SQLDBA/SQLDBAPW/SQLDS

SQLDBA is user id with DBA authority,

SQLDBAPW is the connect password,

SQLDS is the RESID of the database

to connect to the DBNAME parameter

of the database server.

Figure 39. The parameters for ARISCNVD

Note: See global parameters for installation.

Expected return code is 0.

3.10

Installation Step 10

Run the Sample Programs to Verify Installation

This step is optional and only required for local databases.

You should run the sample application programs to verify that you correctly installed the DB2 Server for

VSE, Client Edition system.

For each language supported by an DB2 Server for VSE preprocessor program application program is

supplied that shows how SQL commands can be coded in the preprocessor programs. These sample

programs all access and manipulate the DB2 Server for VSE sample tables in a similar manner. Refer to

the manual for listings of the sample programs.

IBM also supplies the following DB2 Server for VSE Z-type source members with the job control state-

ments to run the sample programs.

ARIS6ASD preprocesses, assembles, link-edits, and runs the assembler.

DB2 for VSE Client Edition Program Directory

See global parameters.

Expected return code is 0.

ARIS6C2D preprocesses, assembles, link-edits, and runs COBOL.

Parameter Name

Default value

Description

COBLIB

CMPLR22.COBVSE

Default library for Cobol compiler

Figure 40. The parameters for ARIS6C2D

See global parameters.

Expected return code is 0.

ARIS6CD preprocesses, assembles, link-edits, and runs C (DO NOT run this job if C is not installed on

your system)

Parameter Name

Default value

Description

C-LIB

CMPLR22.CVSE

Default library for C compiler

Figure 41. The parameters for ARIS6CD

See global parameters.

Expected return code is 2.

ARIS6FTD preprocesses, assembles, link-edits, and runs FORTRAN (DO NOT run this job if FORTRAN is

not installed on your system)

Parameter Name

Default value

Description

FRTLIB

COMPILE.COMPILE

Default library for Fortran Compiler

Figure 42. The parameters for ARIS6FTD

See global parameters.

Expected return code is 4.

ARIS6PLD preprocesses, assembles, link-edits, and runs PL/I (DO NOT run this job if PL/I is not installed

on your system)

Parameter Name

Default value

Description

PLDLIB

COMPILE.COMPILE

Default library for PL/I Compiler

Figure 43. The parameters for ARIS6PLD

See global parameters.

Chapter 3. Installing DB2 Server for VSE Client Edition

Expected return code is 4.

3.11

Installation Step 11: Run ISQL to Verify Installation

3.11.1

Starting the CICS System

You have to restart the CICS system after updating both the CICS

starup job control and the CICS control tables before you can use

DB2 Server for VSE, Client Edition online support in the

CICS system. See "Preparation Step 6" and "Preparation Step 7".

3.11.1.1

Starting the DB2 Server for VSE Client Edition Online Support:

You can use the CICS CIRB transaction with all its internal default parameters, to start the DB2 Server for

VSE Client Edition online support. The CIRB transaction accepts six positional parameters having the

following default values:

password

Defaults to SQLDBAPW. This is the password for the CICS APPLID discussed under

"Installation Step 7: Grant SCHEDULE Authority ".

number of links (NOLINKS) defaults to 3.

default user ID (DEFUID) defaults to CICSUSER.

resource adapter ID (RMID) defaults to 0.

language ID

(LANGID) specifies the language that is link-edited and the search order. The default is

American English (AMENG).

SERVER-NAME (SERVER-NAME) defaults to SQLDS (or to the system default application server if you

have performed "Installation Step 1: Set Up the DBNAME Directory".

Entering CIRB is thus the same as entering:

CIRB SQLDBAPW,3,CICSUSER,0,AMENG,SQLDS

Refer to the DB2 Server for VSE System Administration manual for details about the parameters that can

be passed in a CIRB transaction. (That discussion includes a description of how the user IDs DBDCCICS

and CICSUSER relate to the DB2 Server for VSE online support.)

If the CIRB transaction fails to run successfully, ensure that:

The required CICS table updates have been made.

The CICS system has been restarted after the required table updates were made, or RDO was used

to update the required tables

The DFHSIT application name (APPLID) has been granted SCHEDULE authority in the database.

(See "Installation Step 7: Grant SCHEDULE Authority".)

The DB2 Server for VSE sublibrary has been concatenated to the appropriate search chains in the

partition in which the CICS system or ICCF runs.

The application server has been started in multiple user mode.

DB2 for VSE Client Edition Program Directory

All prerequisite service required by DB2 Server for VSE has been applied.

The CICS restart resynchronization support has been enabled.

3.11.2

Starting ISQL

ISQL runs as a CICS transaction, and is invoked just like any other transaction. Details of the sign-on and

exit procedures are in the DB2 Server for VSE & VM Interactive SQL Guide and Reference.

After the CICS terminal has been activated and the DB2 Server for VSE online support has been started,

start ISQL by typing:

ISQL

The system responds with the ISQL sign-on screen, and prompts you to enter your user ID, password and

optionally a target database name.

All further actions are handled conversationally between the CICS user and ISQL.

If you cannot log on to ISQL, ensure that:

The CICS resources were successfully updated during "Preparation Step 6" and Preparation Step 7".

There is enough CICS dynamic storage for ISQL (900 kilobytes).

ISQL was installed successfully during "Installation Step 4: Install Optional Components".

- DB2 Server for VSE online support has been started with links to the specified (or default) data-

base.

- All links managed by DB2 Server for VSE online support have not been used up.

- All prerequisite service required by DB2 Server for VSE has been applied.

3.11.3

Verify the Installation

Set up the DBNAME directory (ARISDIRD.A) for all types of servers such as LOCAL, REMOTE,

HOSTVM, REMTPN.

To test the installation of the DB2 Server for VSE Client Edition batch client, if DBSU was not installed in

step 4, submit the preprocess DBSU job ARIS75DU to a target server listed in the DBNAME directory. To

install DBSU on all servers, repeat this step for all the DBNAMEs listed in the DBNAME directory.

Create a Job that looks like the one shown below to execute the DBSU utility ARISDBS. Replace userid

and password references with a valid userid and password in the JCL.

Figure 44 on page 42 uses the DBS utility to verify DB2 Server for VSE Client Edition installation.

Chapter 3. Installing DB2 Server for VSE Client Edition

// JOB TESTCLNT

// LIBDEF *,SEARCH=(PRD2.DB2750C)

ON $RC>4 GOTO END

// EXEC ARIDBS,SIZE=AUTO

CONNECT userid IDENTIFIED BY password;

SET ERRORMODE CONTINUE;

SET AUTOCOMMIT ON;

CREATE TABLE CHKINSTTAB (VAR1 INT, VAR2 CHAR(20));

INSERT INTO CHKINSTTAB VALUES (100, 'TESTCLIENT');

INSERT INTO CHKINSTTAB VALUES (200, 'SUCCESSFUL');

SELECT * FROM CHKINSTTAB;

Figure 44. Verify Batch Operations for the client Installation

If CICS environment is available, perform the CIRB transaction to enable the Online Resource Manager

for all the servers or add specific servers using the CIRA transactions after issuing CIRB to enable the

transaction.

If ISQL was not previously installed, follow instructions under topics 5.3.1

Installing ISQL after DB2

Server for VSE Client Edition, 5.3.2 Reloading the ISQL Package (SQLDBA.ARIISQL)

to install ISQL.

To test ISQL, sign on to CICS and execute the ISQL transaction

to verify that DB2 Server for VSE Client Edition is correctly

installed. For ISQL commands refer to DB2 Server for VSE & VM

Interactive SQL Guide & Reference manual.

Execute the following example SQL if you are connected to a target server.

CREATE command through ISQL:

CREATE TABLE CHKINSTTAB (VAR1 INT, VAR2 CHAR(20))

INSERT command through ISQL:

INSERT INTO CHKINSTTAB VALUES (100, 'TESTCLIENT')

INSERT INTO CHKINSTTAB VALUES (200, 'SUCCESSFUL')

CREATE command through ISQL:

CREATE TABLE CHKINSTTAB (VAR1 INT, VAR2 CHAR(20))

SELECT command through ISQL:

SELECT * FROM CHKINSTTAB

To print the display results, enter the ISQL display command:

The successful execution of the PRINT command verifies that SYS098 has been assigned to a

VSE/POWER-intercepted printer, or to a real printer. (Refer to "Modifying the CICS Start-Up JCL".)

DB2 for VSE Client Edition Program Directory

3.11.4

Stopping ISQL

To end the display and terminate the ISQL session:

Type the ISQL display command:

END

Type the ISQL session termination command:

EXIT

3.12

Installation Step 12: Stop the DB2 VSE Client

3.12.1

Stopping the DB2 Server for VSE Online Support

You can use the CICS CIRT transaction with all its internal default parameters, to stop the DB2 Server for

VSE online support. The CIRT transaction accepts three positional parameters, which have the following

default values:

password

Defaults to SQLDBAPW. This must be the same password as the one specified (or the

default) in the CIRB transaction.

mode

Defaults to NORMAL. Options are NORMAL or QUICK.

interval

Defaults to 30 (seconds). This is a decimal value between 0 and 3600 (seconds).

Entering CIRT is thus the same as entering:

CIRT SQLDBAPW,NORMAL,30

Refer to the DB2 Server for VSE System Administration manual for details about the parameters that can

be passed in a CIRT transaction.

3.12.2

Stopping the CICS System

The CICS system need not be stopped when the application server is being shut down; it can continue to

process transactions that do not access DB2 Server for VSE. If the CICS system must be stopped, that

action can be taken in its normal way; DB2 Server for VSE does not restrict CICS shutdown.

Chapter 3. Installing DB2 Server for VSE Client Edition

4.0

Post-Installation Activities

4.1

Installation Step 13: System Customization Activities

This step lists further administration and customization activities you should consider at this time. These

are:

Install and activate the DRDA Application Requestor code.

Prepare to Use TCP/IP. See the chapter "Using TCP/IP with DB2 Server for VSE" in DB2 Server for

VSE System Administration manual that pertain to VSE Requestor side.

Initialize the user partition since the default after installation is INTERNATIONAL. The CCSID defaults

for the target server are determined when a CHARNAME is chosen.

4.1.1

VSE Guest Sharing

This section discusses how to complete the installation of DB2 Server for VSE to enable VSE Guest

Sharing. It does not attempt to explain Guest Sharing in detail. For more information on Guest Sharing,

refer to the DB2 Server for VSE System Administration manual. You can also refer to the IBM z/VSE

Planning manual.

The term "Guest Sharing" is used because the VSE system is a "guest" of the z/VM system and it

"shares" the data with the host's application server.

The VSE Guest Sharing installation process requires you to install the complete DB2 Server for VSE

Client Edition as a guest of a z/VM system.

4.1.2

VSE Guest Machine Parameters

The number of links between the VSE guest machine and the VM database is limited by the MAXCONN

parameter in the VSE guest machine directory entry. If this parameter is not specified, the default is 16.

Each VSE guest machine partition that (batch and online) that will us the VSE guest sharing facility must

have a minimum of 40K PFIX storage allocated for the DB2 Server for VSE communication link. To allo-

cate this storage, use one of the following methods:

// SETPFIX LIMIT=40K,PERM - In the VSE partition during IPL

// SETPFIX LIMIT=40K

- In the VSE JCL before program execution

ALLOC R,fx=40K

- In the BG ASIPROC for the desired partition

See the z/VSE System Control Statements manual for further details on using either the SETPFIX or

ALLOC R commands.

Online users can access another application server on the z/VM systems by supplying a different data-

base name on the SERVER-NAME parameter of the CIRB transaction.

 Copyright IBM Corp. 1981, 2007

4.1.3

VSE Guest Sharing Installation Checklist

Here is the checklist for setting up guest sharing support for DB2/VSE

Preparation Step 1: Setup VSE Environment

Preparation Step 2: Allocate Dasd for the Distribution Library

Preparation Step 3: Restore the Distribution Library

Preparation Step 4: Prepare the CICS Environment

Preparation Step 5: Define DB2 Server Programs and Transactions

Preparation Step 6: Setup the SQLGLOB and SQLBIND Files

Preparation Step 8: Update Standard Labels

Installation Step 1: Setup the DBNAME Directory

Installation Step 2: Setup default userid and password

Installation Step 3: link Edit Online Support Components

Installation Step 4: Start the default database server

Installation Step 5: Install Optional Components

Installation Step 6: Reload CCSID-Related Phases Package

Installation Step 7: Select National Language Support

Installation Step 8: Grant Schedule Authority

Installation Step 9: Create CCSID-Related Phases

Installation Step 10: Run Sample Programs to Verify Installation

Installation Step 11: Run ISQL to Verify Installation

To set up the DBNAME directory for DB2/VSE, you must first determine the RESID and DBNAME of the

DB2/VM database server. Often they are the same name, but they can be different. The DBNAME is the

same as the DBNAME parameter used on the DB2/VM SQLSTART command The RESID was deter-

mined when SQLDBGEN was done. It corresponds to the filename of some of the DB2/VM database

definition files, resid SQLFDEF Q and resid SQLDBGEN Q. If the DB2/VM server is running, the SHOW

INITPARM operator command can be issued. The DBNAME and RESID can taken from that output.

Set up the ARISDIRD.A file specifying the RESID as the APPLID and the DBNAME as the DBNAME. Set

up system default and/or partition defaults if desired. The TPN, SYSID and REMTPN fields should be

blank. DB2/VSE determines that guest sharing is to be used if the APPLID field does not begin with

SYSARI0.

After the ARISDIRD.A file has been cataloged into the DB2/VSE library, ARISBDID job must be run to

generate the DBNAME directory phase. For example:

Post-Installation Activities

5.0

Chapter 4. Maintenance Activities

DB2 Server for VSE Client Edition maintenance includes adding new components (because they were not

installed initially) and replacing existing ones (because of service updates). Both types of activities are

discussed below.

The IBM-supplied procedures and source members for installing DB2 Server for VSE components assume

that the user ID is SQLDBA, and that the password is SQLDBAPW. If the password has been changed, it

should be reassigned before the reinstallation activity. The technique for changing the password is shown

when needed in each description below.

5.1

DBS Utility Maintenance

5.1.1

Reloading the DBS Utility Package (SQLDBA.ARIDSQL)

The DBS utility package must be reloaded in all databases if there is a service update to the A-type

source member ARIDSQLP. To reload it, prepare and run the job control statements shown in Figure 46.

Refer to the information supplied with each DB2 Server for VSE service update to see if you should take

this action.

// JOB RELOAD DBS UTILITY

// LIBDEF PROC,SEARCH=(PRD2.DB2750C)

// EXEC PROC=ARIS75SL

*-- DB2 Server LIBRARY DEFINITION

(1)

// EXEC PROC=ARISDBUD

*-- INVOKE DBSU (2)

CONNECT SQLDBA IDENTIFIED BY currentpw;

GRANT CONNECT TO SQLDBA IDENTIFIED BY SQLDBAPW;

// EXEC PROC=ARIS040D

*-- CREATE DBS UTILITY PACKAGE

(4)

// EXEC PROC=ARISDBUD

*-- INVOKE DBSU (5)

CONNECT SQLDBA IDENTIFIED BY SQLDBAPW;

GRANT CONNECT TO SQLDBA IDENTIFIED BY newpw;

Figure 46. Reloading the DBS Utility Package

Notes for Figure 46

(1)

Procedure ARIS75SL identifies the DB2 Server for VSE sublibraries.

(4)

Procedure ARIS040D creates the package SQLDBA.ARIDSQL in the database from the

DB2 Server for VSE A-type source member ARIDSQL P.

If the database view SQLDBA.SYSUSERLIST exists when you run this step, the step ends

with a return code of 0. If this view does not exist, this step ends with a return code of 4.

(5)

Provide a valid userid and password in place of SQLDBA and SQLDBAPW.

5.2

Online Resource Adapter Control Maintenance

 Copyright IBM Corp. 1981, 2007

5.2.1

Installing Online Resource Adapter Control after DB2 Server for

VSE Installation

If you have already installed the DB2 Server for VSE Client Edition without online resource adapter

control, you can add it later as follows:

1. Link-edit the online support as described below.

2. Run procedure ARIS080D to grant CONNECT authority to PUBLIC and SCHEDULE authority to the

CICS system.

3. Review "Installation Step 8: Grant SCHEDULE Authority" to determine if procedure ARIS080D granted

SCHEDULE authority to the correct user ID.

The procedures for installing these tables are found in "Preparation Step 5: Prepare the CICS System for

DB2 Server for VSE".

5.2.2

Re-Link-Editing Online Resource Adapter Control

If you must re-link-edit online resource adapter control after the initial installation of DB2 Server for VSE

Client Edition, prepare and run the job control statements shown in Figure 47

Refer to the information supplied with each DB2 Server for VSE Client Edition service update to see if you

should take this action.

// JOB RELINK ONLINE RESOURCE ADAPTER CONTROL

// LIBDEF *,SEARCH=(PRD2.DB2750C,PRD1.BASE,PRD2.CONFIG),

CATALOG=PRD2.DB2750C

(1)

// EXEC PROC=ARIS090D

*-- LINK-EDIT ONLINE RESOURCE ADAPTER CONTROL (2)

Figure 47. Re-Link-Editing Online Resource Adapter Control

Notes :

This job specifies the standard CICS libraries in the LIBDEF search path. If required, modify the job to

search your own CICS libraries.

(1)

This job requires that you specify the DB2 Server for VSE Client Edition sublibrary into

which the linkage editor output is cataloged; in this job, the output is cataloged in the

PRD2.DB2750C sublibrary. Specify your own if it has a different name. If you have

installed a National Language, then specify the sublibrary into which the language was

installed in the LIBDEF SEARCH chain (before PRD2.DB2750C), and also as the value for

the LIBDEF CATALOG parameter.

(2)

Procedure ARIS090D link-edits the DB2 Server for VSE Client Edition online resource

adapter control into the DB2 Server for VSE sublibrary. It must not be changed. This link-

edit job will include the CICS interface modules DFHEAI and DFHEAI0 found in the CICS

PRD1.BASE sublibrary, or your own CICS libraries.

Restart the CICS system after the link-edit is successfully completed. For information, refer to Preparation

Step 5: Prepare the CICS System for DB2 Server for VSE

DB2 for VSE Client Edition Program Directory

5.3

ISQL Maintenance

5.3.1

Installing ISQL after DB2 Server for VSE Client Edition

Installation

If you have already installed DB2 Server for VSE Client Edition without ISQL, you can add it later as

follows:

1. Reload the ISQL package (SQLDBA.ARIISQL).

2. Re-link-edit ISQL.

3. Re-link-edit the ISQL ITRM terminal transaction.

4. Re-link-edit the ISQL ITRX terminal extension.

Instructions for each of these tasks follow immediately.

5.3.2

Reloading the ISQL Package (SQLDBA.ARIISQL)

If you reload the ISQL package SQLDBA.ARIISQL after the initial DB2 Server for VSE Client Edition

installation, prepare and execute the job control statements shown in Figure 48. The package must be

reloaded in all applicable databases if there is a service update to A-type source member ARIISQLM.

Refer to the information supplied with each DB2 Server for VSE Client Edition service update to see if you

should take this action.

// JOB RELOAD ISQL

// LIBDEF PROC,SEARCH=(PRD2.DB2750C)

// EXEC PROC=ARIS75SL

*-- DB2 CE LIBRARY DEFINITION

(1)

// EXEC PROC=ARIS120D

*-- RELOAD THE ISQL PACKAGE

(2)

// EXEC PROC=ARIS75VD

*-- CONNECT TO DB2 VIA DBSU

(3)

CONNECT SQLDBA IDENTIFIED BY SQLDBAPW;

GRANT CONNECT TO SQLDBA IDENTIFIED BY newpw;

Figure 48. Reloading the ISQL Package

Notes for Figure 48

(1)

Procedure ARIS75SL identifies the DB2 Server for VSE, Client Edition sublibraries.

(2)

Procedure ARIS120D reloads the package SQLDBA.ARIISQL into the database from

the DB2 Server for VSEA-type source member ARIISQLM. This step must be exe-

cuted by the user SQLDBA.

(3)

Procedure ARIS75VD connects to the base to reset the password for SQLDBA.

This step successfully completes with a return code of 0 through 3.

Chapter 4. Maintenance Activities

5.3.3

Re-Link-Editing ISQL

To re-link-edit ISQL after initial installation, prepare and execute the job control statements shown in

Figure 49 on page 50

Refer to the information supplied with each DB2 Server for VSE Client Edition service update to see if you

should take this action.

// JOB RELINK ISQL

// LIBDEF *,SEARCH=(PRD2.DB2750C,PRD1.BASE,PRD2.CONFIG),

CATALOG=PRD2.DB2750C

(1)

// EXEC PROC=ARIS140D

*-- LINK-EDIT ISQL

(2)

Figure 49. Re-Link-Editing ISQL

Notes for Figure 49

This job specifies the standard CICS libraries in the LIBDEF search path. If required, modify the job to

search your own CICS libraries.

(1)

This job requires that you specify the DB2 Server for VSE Client Edition sublibrary into

which the linkage editor output is cataloged; in this job, the output is cataloged in the

PRD2.DB2750C sublibrary. Specify your own if it has a different name. If you have

installed a National Language, then specify the sublibrary into which the language was

installed in the LIBDEF SEARCH chain (before PRD2.DB2750C), and also as the value for

the LIBDEF CATALOG parameter.

(2)

Procedure ARIS140D link-edits the DB2 Server for VSE Client Edition ISQL facility into the

DB2 Server for VSE Client Edition library. It must not be changed. This link-edit job will

include the CICS interface modules DFHEAI and DFHEAI0 found in the CICS PRD1.BASE

sublibrary, or your own CICS libraries.

The CICS system must be restarted after the link-edit is successfully completed. See "Preparation Step 5:

Prepare the CICS System for DB2 Server for VSE Client Edition". Alternatively, you can access the new

phase by executing the CICS CEMT master command after the link-edit is successfully completed. Refer

to the CICS manuals for information on this command.

5.3.4

Re-Link-Editing the ISQL ITRM Terminal Transaction

To re-link-edit the ISQL ITRM terminal transaction after initial installation, prepare and execute the job

control statements shown in Figure 50 on page 51. This is required by a service update to the ISQL ITRM

terminal transaction program module.

Refer to the information supplied with each DB2 Server for VSE Client Edition service update to see if you

should take this action.

DB2 for VSE Client Edition Program Directory

// JOB RELINK ISQL ITRM TERMINAL TRANSACTION PROGRAM

// LIBDEF *,SEARCH=(PRD2.DB2750C,PRD1.BASE,PRD2.CONFIG),

CATALOG=PRD2.DB2750C

(1)

// EXEC PROC=ARIS150D

*-- LINK-EDIT ITRM TERMINAL TRANSACTION

(2)

Figure 50. Re-Link-Editing the ISQL ITRM Terminal Transaction

Notes for Figure 50:

This job specifies the standard CICS libraries in the LIBDEF search path. If required, modify the job to

search your own CICS libraries.

(1)

This job requires that you specify the DB2 Server for VSE Client Edition sublibrary into

which the linkage editor output is cataloged; in this job, the output is cataloged in the

PRD2.DB2750C sublibrary. Specify your own if it has a different name. If you have

installed a National Language, then specify the sublibrary into which the language was

installed in the LIBDEF SEARCH chain (before PRD2.DB2750C), and also as the value for

the LIBDEF CATALOG parameter.

(2)

Procedure ARIS150D link-edits the DB2 Server for VSE Client Edition ISQL facility ITRM

terminal transaction module into the DB2 Server for VSE Client Edition library. It must not

be changed. This link-edit job will include the CICS interface modules DFHEAI and

DFHEAI0 found in the CICS PRD1.BASE sublibrary, or your own CICS libraries.

The CICS system must be restarted after the link-edit is successfully completed. See "Preparation Step 5:

Prepare the CICS System for DB2 Server for VSE Client Edition". Alternatively, you can access the new

phase by executing the CICS CEMT master command after the link-edit is successfully completed. Refer

to the CICS manuals for information on this command.

5.3.5

Re-Link-Editing the ISQL ITRM Terminal Extension Program

To re-link-edit the ISQL ITRM terminal extension program after initial installation, prepare and execute the

job control statements shown in Figure 51. This is required by a service up date to the ISQL ITRM ter-

minal extension program module.

Refer to the information supplied with each DB2 Server for VSE Client Edition service update to see if you

should take this action.

// JOB RELINK ISQL ITRM TERMINAL EXTENSION PROGRAM

// LIBDEF *,SEARCH=(PRD2.DB2750C,PRD1.BASE,PRD2.CONFIG),

CATALOG=PRD2.DB2750C

(1)

// EXEC PROC=ARIS160D

*-- LINK-EDIT ITRM TERMINAL EXTENSION

(2)

Figure 51. Re-Link-Editing the ISQL ITRM Terminal Extension Program

Notes for Figure 51:

This job specifies the standard CICS libraries in the LIBDEF search path. If required, modify the job to

search your own CICS libraries.

Chapter 4. Maintenance Activities

(1)

This job requires that you specify the DB2 Server for VSE Client Edition sublibrary into

which the linkage editor output is cataloged; in this job, the output is cataloged in the

PRD2.DB2750C sublibrary. Specify your own if it has a different name. If you have

installed a National Language, then specify the sublibrary into which the language was

installed in the LIBDEF SEARCH chain (before PRD2.DB2750C), and also as the value for

the LIBDEF CATALOG parameter.

(2)

Procedure ARIS160D link-edits the DB2 Server for VSE Client Edition ISQL facility ITRM

terminal extension program module into the DB2 Server for VSE Client Edition library, and

must not be changed. This link-edit job will include the CICS interface modules DFHEAI

and DFHEAI0 found in the CICS PRD1.BASE sublibrary, or your own CICS libraries.

The CICS system must be restarted after the link-edit is successfully completed. See "Preparation Step 5:

Prepare the CICS System for DB2 Server for VSE Client Edition". Alternatively, you can access the new

phase by executing the CICS CEMT master command after the link-edit is successfully completed. Refer

to the CICS manuals for information on this command.

You can use operator commands to search the file for a new copy. See the appropriate CICS manual for

details.

5.4

CCSID-Related Phases Maintenance

5.4.1

Reloading the CCSID-Related Phases Package

(SQLDBA.ARIRSQR)

The CCSID-related phases package must be reloaded in all applicable databases if there is a service

update to A-type source member ARIRSQRM. To reload it, run job control member ARIS75WD shown in

Figure 52.

Refer to the information supplied with each DB2 Server for VSE Client Edition service update to see if you

should take this action.

// JOB ARIS75WD

RELOAD CCSID-RELATED PHASES PACKAGE

// LIBDEF PROC,SEARCH=(PRD2.DB2750C)

// EXEC PROC=ARIS75SL

*-- DB2 Server LIBRARY DEFINITION

// EXEC PROC=ARIS175D

*-- RELOAD CCSID-RELATED PHASES PACKAGE

Figure 52. Reloading the CCSID-Related Phases Package

Notes for Figure 52:

For procedure ARIS75SL, substitute your own procedures or job control statements that identify your

current database and the DB2 Server for VSE Client Edition Version 7 Release 5 sublibrary.

DB2 for VSE Client Edition Program Directory

5.4.2

Recreating the CCSID-Related Phases

To recreate the CCSID-related phases after initial installation, execute job ARISCNVD (supplied as a

Z-type job control member). You must recreate the CCSID-related phases after any updates are made to

the SYSTEM.SYSCCSIDS, SYSTEM.SYSCHARSETS, or SYSTEM.SYSSTRINGS system catalog tables.

Refer to "Migration Step 16: Create CCSID-Related Phases" for details.

5.5

FIPS Flagger Maintenance

5.5.1

Reloading the FIPS Flagger Package (SQLDBA.ARIFCRD)

The FIPS flagger package must be reloaded in all applicable databases if there is a service update to

A-type source member ARIFCRDM. To reload it, prepare and run the job control statements shown in

Figure 53

Refer to the information supplied with each DB2 Server for VSE Client Edition service update to see if you

should take this action.

// JOB RELOAD FIPS FLAGGER

// LIBDEF PROC,SEARCH=(PRD2.DB2750C)

// EXEC PROC=ARIS75SL

*-- DB2 Server LIBRARY DEFINITION

(1)

// EXEC PROC=ARISDBUD

*-- INVOKE DBSU (2)

CONNECT SQLDBA IDENTIFIED BY currentpw

GRANT CONNECT TO SQLDBA IDENTIFIED BY SQLDBAPW

// EXEC PROC=ARIS360D

*-- RELOAD THE FIPS FLAGGER

(3)

// EXEC PROC=ARISDBUD

*-- INVOKE DBSU CONNECT SQLDBA IDENTIFIED BY SQLDBAPW

GRANT CONNECT TO SQLDBA IDENTIFIED BY newpw

Figure 53. Reloading the FIPS Flagger Package

Notes for Figure 53:

(1)

Procedure ARIS75SL identifies the DB2 Server for VSE Client Edition sublibraries.

(2)

You must supply a valid DBA userid and password in the place of SQLDBA and

SQLDBAPW.

(3)

The step executed by procedure ARIS360D reloads the package SQLDBA.ARIFCRD into

the database from the DB2 Server for VSE Client Edition A-type source member

ARIFCRDM. The step must be executed by the user SQLDBA.

This step is successfully completed with a return code of 0 through 4.

5.6

DB2 Server for VSE Client Edition Library Maintenance

In a VSE environment, a production sublibrary is required for DB2 Server for VSE.

Chapter 4. Maintenance Activities

5.6.1

Replacing DB2 Server for VSE Client Edition

To replace DB2 Server for VSE Client Edition:

1. Purge the existing sublibrary as described below.

2. Restore DB2 Server for VSE Client Edition through MSHP by following "Preparation Step 4: Restore

the DB2 Server for VSE Distribution Library".

3. Perform the link-edits in "Installation Step 3: Link-Edit the DB2 Server for VSE 7.5 Online Support

Components".

5.6.2

Purging DB2 Server for VSE Client Edition Libraries

To purge existing sublibraries of all entries relating to DB2 Server for VSE, prepare and execute the job

control statements shown in Figure 54

// JOB DELETE DB2 Server VSE VERSION CLIENT EDITION 7.5 LIBRARIES

// EXEC LIBR,PARM='MSHP'

ACCESS SUBLIB=PRD2.DB2750

(1)

DELETE *.*

Figure 54. Purging DB2 Server for VSE Client Edition Libraries

Note for Figure 54:

(1)

The ACCESS statement must contain the name of the sublibrary that contains DB2 Server

for VSE Client Edition. Change this name as required.

5.7

DB2 Server for VSE Client Edition Link Books

Table 2 shows the relationships between DB2 Server for VSE Client Edition components, link books, and

phase names. Refer to it when re-link-editing DB2 Server for VSE phases.

Note:

1. Only the following DB2 Server for VSE Client Edition phases are eligible for the VSE shared

virtual area (SVA):

ARICDIRD

ARIDBS

ARIPRPA

ARIPRPC

ARIPRPF

ARIPRPP

ARIRBARM

If you install all of the phases eligible for SVA into the VSE shared virtual area, allocate an addi-

tional 4.1 megabytes of storage to the SVA.

Table 2. Link Books for the DB2 Server for VSE Client Edition Components

Figure 55 (Page 1 of 3). Link Books for the DB2 Server for VSE Client Edition Components

Component

Link Book

Phases

DB2 for VSE Client Edition Program Directory

Figure 55 (Page 2 of 3). Link Books for the DB2

Server for VSE Client Edition Components

DB2 Server for VSE Client Edition Cop-

None

$$$COSQL

yright

VSE Dependent Functions

ARISLKED

ARISD00D ARISD01D

ARISD10D

ARISD11D ARISD12D

ARISD13D

ARISD14D ARISD15D

ARISD16D

ARISD20D ARISD21D

ARISD22D

ARISD23D ARISD24D

ARISD25D

ARISD26D ARISD30D

ARISD31D

ARISD32D ARISD33D

ARISD34D

User Exit Router

ARISLKXD

ARIXSXR

Assembler Preprocessor

ARISLKAD

ARIPRPA

Flagger Semantic Routines

ARISLK4D

ARIFFVL

Flagger View Analysis Routines

ARISLK5D

ARIFBVL

Flagger LGP tables modules

ARISLK7D

ARIFF00 ARIFS00

ARIFB00

C Preprocessor

ARISLK6D

ARIPRPB

COBOL Preprocessor

ARISLKCD

ARIPRPC

PL/I Preprocessor

ARISLKPD

ARIPRPP

FORTRAN Preprocessor

ARISLKTD

ARIPRPF

DBS Utility

ARISLKUD

ARIDBS

Batch Resource Adapter

ARISLKBD

ARIRBARM

Batch RA with CSI Interface

ARISLKB1

ARIRBARM

Batch RA with EZASM Interface

ARISLKB2

ARIRBARM

Online RA Control with CSI

ARISLKY1

ARIRCONT

Online RA Control with EZASM

ARISLKY2

ARIRCONT

Online DRDA Router with CSI

ARISLKZ1

ARI0RTRM

Online RA with DRDA with CSI

ARISLKZ2

ARI0OLRM

Online RA with DRDA with EZASM

ARISLKZ3

ARI0OLRM

Online DRDA Router with EZASM

ARISLKZ4

ARI0RTRM

Online Resource Adapter

ARISLKZD

ARI0OLRM

DBNAME Directory Generator

ARISLK8D

ARICBDID

DBNAME Directory Services

ARISLKDA

ARICDIRD

Trace Formatter

ARISLKFD

ARIMTRA

Online Resource Adapter Control

ARISLKYD

ARIRCONT

(ENABLE/DISABLE CICS Resource

Adapter)

ISQL Mainline Transaction

ARISLKID

ARIISQL

ITRM Terminal Transaction program

ARISLKJD

ARIITRM

ITRM Terminal Extension Program

ARISLKLD

ARIITRX

Abend Checking Support for LE/VSE

None

ARICABC

Message Repository (American

None

ARIMS001

English)

DRDA2 Support

ARISLKVD

ARICDEBD

ARISLKOD

ARICDRAD

ARISLKND

ARICDAXD

ARISLKWD

ARICDR2

Chapter 4. Maintenance Activities

Figure 55 (Page 3 of 3). Link Books for the DB2 Server for VSE Client Edition Components

COBOL Dynamic Support

None

ARIPADR4 ARIPADR5 ARIPRDI ARISSMA

Note: Note: You can use Z-type

source member ARIS51LP to

create these Phases.

CCSID-Related Phases

ARISLKQZ

ARIRRFCD

ARISLKRZ

ARIRRFRD

ARISLKSZ

ARIRRFSD

CBND Mainline Transaction

ARISLKBA

ARIPCBND

CBND sub-transaction

ARISLKCA

ARIPCB2D

SQLGLOB File Default Setting Program

ARISLKGZ

ARICGDEF

ISQL Package Conversion Program

ARISLKBZ

ARICIQBD

Password encryption routine for online

ARISLKSV

ARICSCC

resource adapter

Password encryption routine for batch

ARISLKSE

ARICSEC

resource adapter and server

TCP/IP online resource adapter

ARISLKTV

ARICTCC

TCP/IP batch resource adapter

ARISLKTE

ARICTCP

Batch Binder

ARISLKBB

ARIPBIN

DB2 for VSE Client Edition Program Directory

6.0

Appendix A. How to Use the Job Manager

IMPORTANT: READ THIS APPENDIX BEFORE STARTING THE INSTALLATION.

6.1

Overview of Installation and Migration

This section is an introduction to the installation of DB2 Server for VSE Version 7 Release 5 (7.5) Client

Edition and the migration of existing databases to 7.5. At the beginning of chapters 2 throu gh 4, you can

find an outline of the preparation, installation and migration steps in each chapter.

An installation aid is supplied to help with the installation and migration processes. Some steps in Chap-

ters 2 through 4 utilize this aid, and some are performed manually.

6.2

Installation

If you are installing DB2 Server in a VSE Client Edition for the first time, follow the steps in Chapter 2,

Preparing to install DB2 Server Client Edition for VSE 7.5, and Chapter 3, Installing DB2 Server for VSE

Client Edition.

6.3

Optional Steps

Not all of the steps in the installation are mandatory. Depending on how you want to install DB2 Server for

VSE Client Edition, you may decide to not perform some optional steps.

6.4

The Job Manager

The Job Manager is a set of REXX Exec, Job Control members, and parameter tables, to assist in the

DB2 Server for VSE Client Edition Installation and Migration processes. REXX program ARISIMGC con-

trols the overall job flow, based on the contents of the job list control tables(supplied as Z-type members).

There are job lists for Preparation steps(ARISITCP), for Installation steps(ARISITCI), and for Migration

steps(ARISITCM).

The Job Manager selects the job control member from the job list, extracts the member from the library,

modifies the JCL, submits the job, evaluates the execution, posts the results, and then repeats the

process. Modifications to the job control members are based on substituting variables in the JCL, using

the parameters in ARISIVRR(a Z-type member).

6.4.1

How Parameter Substitution Works

The Job Manager reads variables stored in ARISIVRR (a Z-type member).

Before starting the Job Manager:

1. Punch and modify the sample ARISIVRR from your installation library.

2. Re-catalog ARISIVRR to your installation library.

Note:

Make sure to preserve the structure of ARISIVRR member.

You do not need to update parameters for a step, you are not planning to execute.

The parameter table (see ARISIVRR a Z-type member) has one line for each parameter for each job. The

lines of the parameter table are in the following format:

Job name

The job name that requires Parameter(s)

Parameter name

The variable name in the job JCL

Value of the parameter

The value of the parameter that can be changed

Figure 56. The description of parameters in ARISIVRR

The parameter table also has one line for each global parameter. These parameters are used in more

than one job, but apply only within the start/end group being processed.

Parameter name

GLOBAL (constant keyword)

Parameter name

This name appears in a JCL for the job

Value of the parameter

This is actual value of the global parameter, which can be

changed

Figure 57. The description of Global parameters in the ARISIVRR

6.4.2

How Job List Works

The job list is used by the Job Manager to determine the jobs required by each step (Preparation/ Installa-

tion or Migration).

DB2 for VSE Client Edition Program Directory

Job's name

Name of member in the distribution library

Job's type

Type of member in the distribution library

Return code

RC = 'X' - job did not complete successfully or has not run before.

RC=number, job has run and RC contains the return code of the job.

MAXRC

MAXRC maximum return code allowed for this job to continue the installation

process.

Is job Optional?

O - Optional, M - Mandatory (for Installation part)

Is job Optional?

O - Optional, M - Mandatory (for Migration part)

Is input required?

YES - input required (get variables from ARISIVRR)

NO - input is not required.

Note: If the only required parameter is installation library name or a global var-

iable, then input marked as 'NO'

Stop Job Manager?

YES - stop the execution of the Job Manager after this step.

NO - continue the execution of the Job Manager.

Figure 58. Description of each column in a job list

Note: Every parameter in a job list must be in upper case, separated from other parameters by one blank

space.

Here is an example of a job list for the Preparation Step:

ARIS75JD Z X 4 O M YES NO

In the example, ARIS75JD is a Z type member, which was not executed yet. The maximum return code

allowed for ARIS75JD is 4. ARIS75JD is Optional step in Preparation for Installation, but mandatory step

in Preparation for Migration. The ARIS75JD requires parameters from ARISIVRR and the execution of the

Job Manager will not stop after this step.

As ARIS75JD is submitted to your VSE system, the Job Manager will compare the maximum return code

from the execution to MAXRC. If the job completes with a return code greater than MAXRC, the Job

Manager stops.

6.4.2.1

How to Run All Jobs Again:

If you have multiple databases and want to execute Preparation, Installation, or Migration Step again this

section will explain how to do it. You can choose one of the following:

1. Punch a Job List corresponding to the step you want to execute:

ARISITCP - Job List for Preparation Step

ARISITCI - Job List for Installation Step

ARISITCM - Job List for Migration Step

Change the "Return Code" fields (See Figure 58) for all jobs with "X" and re-catalog the Job list to the

installation library.

WARNING: When changing the records in the file, note that the fields must be separated by only one blank.

Appendix A. How to Use the Job Manager

2. See Figure 60 on page 61.

6.4.3

Starting the Job Manager

IMPORTANT: Modify ARISIVRR Z-type member with the appropriate parameters. If you subsequently change ANY ARISIVRR

global variables you MUST restart the Job Manager.

After successful modification of ARISIVRR control table, punch and submit job control member

ARISIMGC.Z from the distribution library, which will start execution of Job Manager.

* $$ JOB JNM=ARISIMGC,CLASS=x

(1)

* $$ LST CLASS=V,DEST=(,userid)

*modify accordingly

// JOB ARISIMGC JCL TO START MANAGER EXEC

// LIBDEF *,SEARCH=(PRD2.DB2750C) *modify accordingly

// EXEC REXX=ARISIMGC

* $$ EOJ

Figure 59. Starting the Job Manager

(1)

For CLASS specify any available partition to run the Job Manager.

Note: ARISSTDL Z-type member must run in background partition, thus for the Prepara-

tion Step do not submit the Job Manager to run in background partition. See Figure 60 on

page 61:

Note: ARISIMGC Job will always complete with the return code of 0. You must check the return code of the executed job and

rely on the messages from the Job manager to make sure that the execution was successful.

See "How the Job Results are Evaluated".

6.4.3.1

User Interface:

DB2 for VSE Client Edition Program Directory

F4 0004 *************************************************************

F4 0004

PREPARE FOR INSTALLATION/MIGRATION PROCESS

F4 0004 *************************************************************

F4 0004 ENTER INSTALLATION LIBRARY NAME (PRD2.DB2750C default) Q Exit

(1)

F4-0004

F4 0004 YOU HAVE SELECTED PRD2.DB2750C

F4 0004 PRESS ENTER TO CONTINUE OR ENTER ANOTHER LIBRARY NAME

F4 0004

Q Exit

F4 0004 ENTER PARTITION NUMBER: (default 4)

Q Exit

(2)

F4-0004

F4 0004 YOU HAVE SELECTED

F4 0004 PRESS ENTER TO CONTINUE OR ENTER ANOTHER PARTITION NUMBER

F4-0004

F4 0004 PLEASE SELECT ONE OF THE FOLLOWING :

F4 0004 FOR PREPARATION

ENTER (P)

F4 0004 FOR INSTALLATION...

ENTER (I)

F4 0004 FOR MIGRATION

ENTER (M)

F4 0004

Q Exit

4 p

F4 0004 IF PREPARATION FOR:

Q Exit

F4 0004 INSTALLATION... PLEASE ENTER (I)

F4 0004 MIGRATION

PLEASE ENTER (M)

F4-0004

4 i

F4 0004 DO YOU WANT TO EXECUTE ALL JOBS? {Y|N-default}

Q Exit

(3)

F4-0004

4 n

F4 0004 IF YOU WANT TO START FROM A SPECIFIC JOB ENTER 1

(4)

F4 0004 IF YOU WANT TO EXECUTE ONLY ONE STEP

ENTER 2 (Default)

(5)

F4 0004

Q Exit

4 2

F4 0004 ENTER THE JOB NAME YOU WANT TO EXECUTE (ex. ARIS75JD):

F4 0004

Q Exit

4 ARIS75jd

F1 0001 1Q47I F4 ARIS75JD 00021 FROM (JCL) , TIME=12:45:32

BG 0000 * ** JOB JNM=ARIS75JD,CLASS=0,DISP=D

BG 0000 * ** LST CLASS=V,DISP=D,DEST=(,XXXXXXX)

BG 0000 // JOB ARIS75JD DEFINE DB2750C PROGRAMS AND TRANSACTIONS

Figure 60. Sample user answers when running the Job Manager

Notes for Figure 60:

(1)

The installation library name, which is specified here, is included in library search path for all jobs

as the parameter - LIBNAME.

// JOB name

// LIBDEF PROC,SEARCH=(%%LIBNAME%%)

(2)

For Preparation Step - answer 0 (BG partition). Note: the BG partition must be available.

For Installation/ Migration Steps - specify any available partition that has enough size to start

the DB2 startup database

Appendix A. How to Use the Job Manager

(3)

Enter 'YES' if you want to run all jobs within the current step (Preparation/ Installation/

Migration).

Note: the Job Manager will skip all jobs which were run successfully. The first job it will submit

will be a job which failed in previous execution or which was never run before.

The default answer is 'NO'.

(4)

Enter '1' if you want the Job Manager to start from a particular job and continue execution of all

jobs which follow the specified one.

Note: this choice is useful if you have to execute some jobs twice, even if the execution of the

jobs was successful.

(5)

The default answer is '2' - to execute only one job.

Note: At any time Enter Q to quit and terminate the Job.

6.4.4

Execution of Jobs Submitted by the Job Manager

On the console during the execution of job you should see the following:

F4 0001 1Q47I F4 name_of_submited_job 00025 FROM

(ARISIMGC) , TIME=11:39:33

F4 0004 // JOB name_of_job comment from submitted job

DATE 09/12/2001, CLOCK 11/39/33

* more comments from submitted_job (if available)

F4 0004 EOJ name_of_job MAX.RETURN CODE=0000

DATE 09/12/2001, CLOCK 11/39/36, DURATION 00/00/03

F4 0004 EOJ NO NAME

DATE 09/12/2001, CLOCK 11/39/37

F4 0001 1Q34I F4 WAITING FOR WORK

F1 0001 1Q34I LST WAITING FOR WORK ON 00E

F4-0004 ***********************************************

F4-0004 * JOB: name_of_job EXECUTED SUCCESSFULLY

(1)

F4-0004 ***********************************************

F4-0004 JOB MANAGER COMPLETED SUCCESSFULLY

(2)

F4-0004 EOJ JCL

MAX.RETURN CODE=0000

BG-0000

Figure 61. Console output from the Job Manager

(1)

This message will always appear if submitted job executed successfully.

The possible error messages are:

'ERROR! RETURN CODE FROM LAST STEP WAS xxx'

'JOB WAS CANCELED'

'READ CONSOLE FOR DETAILS.'

(2)

If error occurs you must investigate, correct the error and restart the Job Manager.

DB2 for VSE Client Edition Program Directory

6.4.5

How the Job Results are Evaluated

What do you look for:

Messages from the Job manager (ARISIMGC). If it was terminated, read console and check your reader to

make sure you understand what went wrong, correct the error, and restart Job Manager.

Messages from submitted jobs.

- Some jobs have error checking inside the JCL. In such situations Job Manager will wait for an user

response to continue or to stop the installation process.

- Other jobs that terminate abnormally will produce readable output on the console and send the console

output file to your reader. Please read the file to determine what went wrong.

- Some jobs will not terminate until there is a console response from the user. If no response was received

after 30 seconds, Job Manager will output a warning message on the console and wait for your response.

If the return code allowed for a job was greater than zero, it is your responsibility to check whenever this code

was expected or if it occurred because of some kind of error. This is very important for Z-type member

ARIS75DD. Please read the console output for this job and make sure no errors are found.

IMPORTANT: Always verify if the execution of the last job was successful. If the Job Manager stops its execution, before pro-

ceeding to another step, make sure that no errors occured and that you executed all mandatory jobs for the step.

6.4.6

What Should You Keep in Mind

As soon as you start the Job Manager for Installation or Migration Steps, it will update and recatalog three

members: ARIS75SL and ARIS380D

Note: If you need to make any changes to ARIS75SL or ARIS380D after starting the Job Manager for

Installation or Migration Steps, you must do it manually.

ARIS75SL

This member will be updated using following parameters:

Default Installation Library, which you specify when starting the Job Manager (default is

PRD2.DB2750C)

ARIS380D

This member will install a language. See 3.7.1, “Install Language and ISQL Help Text” on

page 35. If you need to install more than one language you need to modify this procedure manu-

ally.

6.5

The Disclaimer

The Job Manager is supplied as an installation aid for DB2 Server for VSE Client Edition, and is not intended to be

used as a general purpose monitoring tool. Any use of the Job Manager, other than Preparation, Installation, and

Migration for DB2 Server for VSE, Client Edition is not supported.

Appendix A. How to Use the Job Manager

7.0

Appendix B. Techniques Used for Installation

The following are techniques used in some of the DB2 Server for VSE Client Edition installation procedures and

members:

Embedding database identification statements

Embedding DB2 Server for VSE, Client Edition library identification statements

Using READ MEMBER statements

Suppressing preprocessor output.

7.1

Embedding DB2 Server for VSE, Client Edition Library

Identification Statements

The IBM-supplied procedure ARIS75SL contains the library identification (LIBDEF) statements for most of the

installation steps. The IBM-supplied procedure ARIS75PL contains the LIBDEF statements for normal use of DB2

Server for VSE Client Edition.

The LIBDEF statements in procedures ARIS75SL and ARIS75PL are not unique to a particular database. They are

included whenever a set of DB2 Server for VSE, Client Edition libraries is needed.

You can replace the references to ARIS75SL and ARIS75PL with your own LIBDEF statements, or with references

to your own procedures set up for this purpose.

7.2

Using the READ MEMBER Statement

DB2 Server for VSE, Client Edition can read input from a source member with a statement of the form:

READ MEMBER member-name[.member-type] [(NOCONT]

Note: The square brackets [ ] indicate an optional parameter.

member-name

Specifies a source member in the DB2 Server for VSE, Client Edition library.

member-type

Specifies the source member type. The default is “.A”. For example, either BOOK1 or

BOOK1.A is correct.

NOCONT Specifying NOCONT prevents READ MEMBER from continuing to read from SYSIPT. It

also ensures that the EOF indicator is returned. If NOCONT is specified, subsequent

records are read from SYSIPT after the end of member

A READ MEMBER statement:

Can occur anywhere between byte 1 and byte 71 of a SYSIPT record.

Is accepted only if it occurs immediately after an EXEC statement or another READ MEMBER

statement.

Is accepted after a SCHEMA or RELOAD PACKAGE command if the INFILE specified is

SYSIPT. The NOCONT option is required to properly end the file.

Is accepted after a DATALOAD command if the INFILE specified is (*). An ENDDATA

command is required at the end of the input data records, whenever the end of data is inside

the member or in SYSIPT.

Must not follow other SYSIPT data records. However, SYSIPT data records can follow it if the

NOCONT option is not specified.

Is not intended to be used outside of the DB2 Server for VSE Client Edition process. Using

READ MEMBER to include members with SQL INCLUDE statements results in errors.

You can place SYSIPT data immediately after an EXEC statement and not READ MEMBER state-

ment.

7.3

Suppressing Preprocessor Output

SYSPCH and SYSLST output from the DB2 Server for VSE Client Edition Assembler preprocessor is suppressed

during the database install action process. It is not required because only access modules are being built for the

database. Assignment and label information for SYSPCH is not needed when the SYSPCH output is suppressed.

The assignment and label information is only required for output to disk file.

Preprocessor parameters NOPRINT (NOPR) and NOPUNCH (NOPU) are used. Refer to the DB2 Server for VSE

Application Programming manual for a complete description of the preprocessor parameters.

Preprocessor diagnostic messages are always written to SYSLST.

Appendix B. Techniques Used for Installation

8.0

Appendix C. Procedures Provided by IBM

This appendix lists the procedures provided by IBM for your use. Any procedures not documented in this manual

are included in the DB2 Server for VSE System Administration manual.

Procedure

Purpose

ARISIMGC

Rexx Job Manager

ARISDBUD

Run the DBS Utility in DB2 Server for VSE

ARIS040D

Create the DBS Utility Package

ARIS055D

Load Sample Table and Routines

ARIS059D

Activate the Messages for Language xxxx

ARIS061D

Deactivate a Language

ARIS075D

Drop, Recreate, and Load the Sample Tables

ARIS090D

Link-edit Online Resource Adapter Control with Assembler TCP/IP interface

ARIS095D

Link-edit Online Resource Adapter Control with EZASMI TCP/IP interface

ARIS100D

Link-edit Online Resource Adapter Control with LE/C TCP/IP interface

ARIS110D

Create/Grant ISQL Tables/Authorizations

ARIS120D

Reload the ISQL Package

ARIS130D

Complete the Installation of ISQL

ARIS140D

Link-edit ISQL

ARIS150D

Link-edit ISQL ITRM Terminal Transaction

ARIS160D

Link-edit ISQL ITRM Terminal Extension Program

ARIS170D

Link-edit DB2 Server for VSE Batch Resource Adapter

ARIS175D

Reload the CCSID-related Phases Package

ARIS180D

Link-edit DB2 Server for VSE Trace Formatter

ARIS75FC

Sample File Control Table Entries for SQLBIND and SQLGLOB

ARIS75PL

DB2 Server for VSE Client Edition Production Library Definition

ARIS75SL

DB2 Server for VSE Client Edition Optional Service/Production Library Definition

ARIS360D

Load FIPS flagger

ARIS380D

User entry for NLS Installation

ARIS385D

Procedure to install NLS and Load Help Text

ARIS390D

Load initial record to SQLGLOB VSAM file

ARIS395D

Load initial record to SQLBIND VSAM file

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