Copyright © Cloud Software Group, Inc. All Rights Reserved

Installing on a Remote Host

This section describes the procedure for installing the software on a remote host in relation to the Data Object Broker installation.

Distribution Media and Contents

This software is distributed in .xm1 format within a zip file. The file is in a format compatible with IBM System Modification Program/ Extended (SMP/E) naming conventions. The software is packaged in SMP/E txlib format.

Obtaining the Installation Media

You can download the software from the TIBCO web site by following these steps:

1.	Contact Cloud Software Group, Inc. for a password, directory information, etc.

2.	Connect to the TIBCO web site with the required information.

3.	Download the appropriate zip file.

Installation Files

The following zip file comprises the distribution media:

 

TIB_srvcgw-DB2_6.0.0_zos.zip

Uploading the Software

If you have acquired the software by downloading it from the TIBCO web site, you must upload the software to the z/OS host system.

Preparing and Uploading the Product File

1.	Download or copy the TIB_srvcgw-DB2_6.0.0_zos.zip file to a PC that can connect to the z/OS host system.

2.	Unzip the file to a temporary location on the PC. The zip file contains multiple files; of these, the following files are the only files used in this installation:

−	srvcgw_db2.xm1 – compressed file containing Service Gateway for DB2 for installation on a remote host

−	install.bin – the REXX EXEC to perform the installation

−	ostarrec.bin – the REXX EXEC to uncompress the .xm1 file

−	property.bin – a template of mandatory install variables required for product installation.

−	OSTAREDC – a load module to improve the performance of OSTARREC

The db2.xm1 file is not used in this procedure.

3.	Pre-allocate a PDS, fixed block data set on the z/OS host system with the following name:

<HLQ>.INSTALL

where <HLQ> is any valid high-level qualifier. Note that this <HLQ> will be used during the installation. See the sample JCL in the next step.

4.	Pre-allocate the following sequential data set on the z/OS host system:

<HLQ>.OS.DB2.XM1 (size 46,220 KB)

Use the same <HLQ> as the previous data set. Below is sample JCL to allocate these data sets. Provide a JOB card and submit the JCL.

 

//ALLOC EXEC PGM=IEFBR14
//DD1 DD DSN=<HLQ>.INSTALL,
// DISP=(,CATLG,DELETE),UNIT=SYSDA,
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=0),
// SPACE=(TRK,(5,15,100))
//DD2   DD DSN=<HLQ>.OS.DB2.XM1,
// DISP=(,CATLG,DELETE),UNIT=SYSDA,
// DCB=(RECFM=FB,LRECL=1024,BLKSIZE=0,DSORG=PS),
// SPACE=(TRK,(1000,50))

5.	FTP install.bin, property.bin and ostarrec.bin to your z/OS system in BIN mode to the <HLQ>.INSTALL data set. Name these utilities INSTALL, PROPERTY and OSTARREC, respectively.

6.	FTP the srvcgw_db2.xm1 file in BIN mode to the <HLQ>.OS.DB2.XM1 data set.

Installing the OSTAREDC Program

1.	Upload the OSTAREDC file to z/OS in binary format to a data set with LRECL=80 and RECFM=FB.

2.	In ISPF 3.4, against this data set, type the following:

“RECEIVE INDA(/)”

When prompted, specify DA('<HLQ>.INSTLOAD' as the name of the load library where you want the OSTAREDC program restored, using the following syntax:

DA(’datasetname’)

3.	Edit OSTARREC as follows:

−	Issue the command "FIND OSTAREDC 1".

−

Change the constant after the equal sign to contain the full data set name of the program. The string must start with a double quote and a single quote, and end with a single quote and a double quote (the double quotes delimit the string and the single quotes tell TSO that the data set name is fully qualified). For example, change the following:

 

OSTAREDC = "'<HLQ>.INSTLOAD(OSTAREDC)'"

to

OSTAREDC = "'your.load.library(OSTAREDC)'"

where your.load.library is the name of the library referenced in Step 2.

Installing the Software

You can start the installation if you have the following data sets ready:

•	<HLQ>.INSTALL

•	<HLQ>.OS.DB2.XM1

 

The <HLQ> referenced throughout this chapter is the high-level qualifier you specified when you uploaded the product software. This is the value of the INSTALL and XM1 files you specified. It will be used as the default value for all distribution files created when an XM1 is uncompressed. It is equivalent to the value of symbolic parameter $HLQ$ as described in OSEMOD.

Installation Overview

To install Service Gateway for DB2, perform the following:

1.	Determine your system environment values listed in System Environment Checklist.

2.	Edit the Properties File using the values determined in Step 1.

3.	Install the Software.

System Environment Checklist

Before you begin the installation, review the system environment information described in Table 4 and determine whether you will use the default value or provide your own value.

 

Table 4 OSEMOD Variables

Description	OSEMOD Variable	Default Value	Your Value
High level qualifier for uploaded data sets INSTALL and OS.DB2.XM1.	$HLQ$	Specified on upload
High level qualifier for non-VSAM and VSAM data sets you are authorized to create.	$HLQNONV$ $HLQVSAM$	TIBCO.TESTNV TIBCO.TESTVS
Second level qualifier for install files.	$INSTVER$	INS60
Second level qualifier for TIBCO Service Gateway system files.	$SLQ$	OSB60
Second level qualifier for SMP/E libraries	$SMP$	SMP60
For SMS Shops – managementclass, dataclass and storageclass, if required
For new non-VSAM data sets.	$NMGTCLAS $NDATCLAS$ $NSTOCLAS$	STANDARD STANDARD S6BNONV
For new VSAM data sets.	$VMGTCLAS $VDATCLAS$ $VSTOCLAS$	STANDARD STANDARD S6BVSAM
High level qualifier of Language Environment libraries for SCEELKED and SCEEBIND.	$CEELIB$	CEE
High level qualifier of IBM's Callable Services library CSSLIB.	$CSSLIB$	SYS1
Fully qualified DB2 load library.	$SYSDB2$	DSN810.SDSNLOAD
Name for a DB2 plan	$DB2PLN$	OSBPLAN

For additional information, refer to TIBCO Object Service Broker for z/OS Installing and Operating.

Edit the Properties File

Use the PROPERTY member in <HLQ>.INSTALL as a template, and modify to suit your requirements. Table 5 describes keywords in the properties file that correspond to the system environment variables in System Environment Checklist.

 

Table 5 Properties File Keywords

Keyword	Description
INSTALL=	To install Service Gateway for DB2, specify REMOTEGATEWAY: INSTALL=REMOTEGATEWAY
SERVICEGATEWAY=	To install Service Gateway for DB2, specify DB2: SERVICEGATEWAY=DB2
HLQNONV=	High level qualifier for non-VSAM data sets.
HLQVSAM=	High level qualifier for VSAM data sets.
INSTVER=	Second level qualifier for install files.
SLQ=	Second level qualifier for TIBCO Object Service Broker system files.
SMP=	Second level qualifier for SMP/E libraries.
SMS=	YES for SMS site, NO for non-SMS site. Warning: If you select the SMS=YES option, be sure to specify SMS-managed data-set names. The SMS automatic class selection (ACS) rules for your site determine whether a data-set name is eligible for SMS management. The name you specified that is determined by the ACS routines to be SMS-eligible is SMS-managed. Otherwise, the result is unpredictable.
COMPAT=	Use if SMS=YES. Valid values: YES for SMS compatible data set name classes; NO for SMS non-compatible data set name classes. If COMPAT=NO, specify the following: • NMGTCLAS – MANAGEMENTCLASS for non-VSAM data sets • NDATCLAS – DATACLASS for non-VSAM data sets • NSTOCLAS – STORAGECLASS for non-VSAM data sets • VMGTCLAS – MANAGEMENTCLASS for VSAM data sets • VDATCLAS – DATACLASS for VSAM data sets • VSTOCLAS – STORAGECLASS for VSAM data sets
VOLSER=	If SMS=YES, specify one DASD volume for VSAM data set allocation. Default is USER01. If SMS=NO, specify three DASD volumes separated by commas. Defaults are OSBS06, OSBD18, OSBB02. • vol1 – DASD volser for temp work files • vol2 – DASD volser for install files • vol3 – DASD volser for TIBCO Object Service Broker system files
CEELIB=	High level qualifier of Language Environment libraries.
CSSLIB=	High level qualifier of IBM's Callable Services library CSSLIB.
SYSDB2=	Fully qualified DB2 load library.
DB2PLN=	Name for a DB2 plan used in Service Gateway for DB2.

Install the Software

 

To exit the interactive session at any time after executing the REXX exec INSTALL, do the following: 1. Press PA1 2. Enter hi 3. Press ENTER twice

 

STEP 1:	Execute File Tailoring EXEC to start installation.
Member in:	<HLQ>.INSTALL
Member:	INSTALL (EX member)
	STEP 1 will verify that files can be allocated successfully using the values provided in the PROPERTY file. Test files of type sequential, PDS, PDSE, and VSAM will be allocated then deleted. Installation will stop if any test allocation fails. You should investigate the cause, correct the condition and repeat STEP 1. The DB2.JCL data set is created at the successful completion of this step.
STEP 2:	Edit the Job card to your site’s standards and run Job DB2.JCL.
JCL in:	<HLQ>.DB2.JCL (Edit Job Card to your site’s standards)
Data Set:	<HLQ>.DB2.JCL (SUB data set)
	This batch job will uncompress the OS.DB2.XM1 file to produce the distribution libraries. If you modify the job name, make sure it does not exceed seven characters. The job should successfully complete with a return code of 0.
STEP 3:	Edit OSEMOD. (Optional)
	If you wish to make additional changes to the values of OSEMOD variables, make the changes now.
Member in:	<HLQ>.FILECLS
Member:	OSEMOD
STEP 4:	Create and customize work copies of data sets.
Member in:	<HLQ>.OS.DB2.FILEI
Member:	S6P1CUST (EX member)
	The following work copies are created and customized with values specified by OSEMOD variables: Customized copy – Library Description • <HLQNONV>.<INSTVER>.CLIST – CLIST • <HLQNONV>.<INSTVER>.CNTL – CNTL • <HLQNONV>.<INSTVER>.JCL – Sample JCL • <HLQNONV>.<INSTVER>.OS.DB2.JOBS – Install jobs for remote Service Gateway for DB2
STEP 5:	Modify STATUS of installation jobs, as required.
Member in:	<HLQNONV>.<INSTVER>.OS.DB2.JOBS
Member:	JOBSP (EDIT member)
	Jobs in MEMBER are evaluated in the order they are listed and are submitted based upon their specified STATUS. The next job is submitted only if the previous one completed with its expected return code RC. Valid status: INSTALL (run the job), FUTURE/OPTIONAL (skip the job), DONE (job already completed). Status is modified from INSTALL to DONE only if the job's completion code is equal to or less than the stated return code. You can modify the STATUS of any job as per your requirement. For example, if your shop normally ACCEPTs the product FMID at some future time, then change the status of S6P4ACPT from INSTALL to FUTURE. Note that you must ACCEPT the remote Service Gateway for DB2 FMID before applying any hotfix maintenance using SMP/E. Skip this step if the default STATUS of all the jobs is acceptable.
STEP 6:	Initiate install jobs.
Member in:	<HLQNONV>.<INSTVER>.OS.DB2.JOBS
Member:	S6P2RUNJ (EX member)
	SEND messages are directed to the userid specified in the NOTIFY parameter of each job submitted, informing user of submission and normal completion or abnormal termination. The successful completion of the final job in JOBSP list is accompanied by the message ALL MEMBERS PROCESSED. This completes the installation process. See Starting the Gateway for details on starting a DB2 Gateway.
STEP 7:	Connect the Service Gateway for DB2 to the DOB.
	Modify the relay configuration file for the DB2 server on z/OS, and huron.dir on the DOB, as documented in Connecting the Gateway to a Windows, or Solaris Data Object Broker.

Uninstalling on a Remote Host

To uninstall the software, perform the following:

 

STEP 1:	Run the DB2 cleanup job.
Member in:	<HLQNONV>.<INSTVER>.OS.DB2.JOBS
Member:	S6P9CLEN (Edit JOBCARD and SUB member)
STEP 2:	Manually delete the following data sets (in the specified sequence):

 

1. $HLQ$.FILECLS 2. $HLQ$.FILECTL 3. $HLQ$.FILEEM1 4. $HLQ$.FILEEM2 5. $HLQ$.FILEJCL 6. $HLQ$.FILEOBJ 7. $HLQ$.FILETRK 8. $HLQ$.FILEXML 9. $HLQ$.MACRO 10. $HLQ$.DBRM 11. $HLQ$.OS.DB2.FILEI 12. $HLQNONV$.$INSTVER$.CLIST 13. $HLQNONV$.$INSTVER$.CNTL 14. $HLQNONV$.$INSTVER$.JCL 15. $HLQNONV$.$INSTVER$.OS.DB2.JOBS   At this point, you should only have the uploaded data sets: • $HLQ$.INSTALL • $HLQ$.OS.DB2.XM1 Manually delete the data sets.

 

Copyright © Cloud Software Group, Inc. All Rights Reserved