![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
These instructions are for a new TIBCO Object Service Broker installation; to migrate from a previous version, see TIBCO Object Service Broker Release Notes.You can start the installation if you have uploaded the following data sets as described in the Uploading the Software:
The <HLQ> referenced in 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 is used as the default value for all distribution files created when an XM1 is uncompressed. An ISPF edit macro called OSEMOD is supplied for the purpose of customizing installed data sets. It will be used later in the installation process. It is equivalent to the value of symbolic parameter $HLQ$ as described in OSEMOD (see Required Variables).Use the automated installation for a minimal installation; for example, for a proof of concept. Use the manual installation to customize the product to your site’s requirements.
2. Edit the Properties File using the values determined in Step 1.Before you begin the installation, review the system environment information described in Table 3 and determine whether you will use the default value or provide your own value. See Base Installation Listing for a list of the data set structure.
Table 3 Subset of OSEMOD Variables OSEMOD Variable Your
Value High level qualifier for uploaded data sets INSTALL, OSB.XM1, and METASTR.XM1. Specified on upload High level qualifier for non-VSAM and VSAM data sets you are authorized to create. Second level qualifier for TIBCO Object Service Broker system files. High level qualifier of Language Environment libraries for SCEELKED and SCEEBIND. High level qualifier of IBM's Callable Services library CSSLIB. Data Object Broker communication ID (if cross-memory facility will not be used). Use the PROPERTY member in <HLQ>.INSTALL as a template, and modify to suit your requirements. Table 4 describes keywords in the properties file that correspond to the system environment variables in System Environment Checklist.
Table 4 Properties File Keywords 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. 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 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. Authorize the <HLQNONV>.<INSTVER>.AUTH library that will be created during the installation.
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 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. This batch job will uncompress the OSB.XM1 and METASTR.XM1 files 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. If you wish to make additional changes to the values of OSEMOD variables, make the changes now.OSEMOD is an ISPF edit macro that is used to edit TIBCO-supplied data sets. Variables in the data sets are changed during the next step of the installation process. A complete list of variables may be found at Required Variables. It is suggested that values be supplied for $HOST$, $DOBPORT$ and $EEPORT$ to take advantage of TCP/IP. The following work copies are created and customized with values specified by OSEMOD variables:
• <HLQNONV>.<INSTVER>.OSB.JOBS – Install jobs for new OSB system Member JOBSA contains the list of jobs that will be submitted in the next step. Each non-commented line in the data set contains three fields: name of the member to be submitted, highest expected return code and the job status.Lines in JOBSA member are evaluated in the order they are listed and the STATUS field indicates if the corresponding job will be submitted. Also, the next job can be submitted only if the previous one completed with its expected return code.Valid status: INSTALL (run the job), FUTURE/OPTIONAL (skip the job), DONE (job already completed). By editing STATUS fields in JOBSA member, you control which steps will be initiated in step 6.Upon completion of step 5 the JOBSA member STATUS fields are updated to reflect the outcome of each job.Status is modified from INSTALL to DONE if the job completion code was equal or less than the stated return code.If any of the jobs in the list fails to complete with the expected return code, the jobs that follow will not be executed, but the STATUS field of those which preceded it on the list will be updated with STATUS DONE. Therefore, you can correct the reason for failure and simply re-run the step 5. 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 S6A4ACPT from INSTALL to FUTURE. If you wish to install any of the local Service Gateways later, it is mandatory that ACCEPT is done first. Note that you must ACCEPT the base OSB FMID before applying any hotfix maintenance using SMP/E.Status is modified from INSTALL to DONE only if the job's completion code is equal to or less than the stated return code. Note: Do not edit member JOBSA once the install jobs are initiated in STEP 6.You can keep the member unchanged if the STATUS fields of all jobs is acceptable (it will initiate all the jobs required). 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 JOBSA list is accompanied by the message ALL MEMBERS PROCESSED.This completes the auto-installation process. For a list of installed libraries and data sets, see Base Installation Listing. For installation details for the Service Gateways for CICS, IMS TM, and WMQ, refer to Chapter 5, Installing the Service Gateway for CICS, Chapter 6, Installing the Service Gateway for IMS TM, and Chapter 7, Installing the Service Gateway for WMQ. For the Service Gateway for Files, refer to TIBCO Object Service Broker Managing External Data. For all other gateways, refer to the gateway specific manuals. Download it and apply any required SMP maintenance at this point as per the documentation with the hotfix. You must respond to a WTOR on this occasion to allow the Data Object Broker to start. For example:12.02.21 JOB04800 S6BKR006A-XYZ REDOLOG AND CACHE FORMATTED. REPLY TO S6BKR09812.02.21 JOB04800 *454 S6BKR098-XYZ READ S6BKR006 AND REPLY G TO GO, C TO CANCEL If there is any database maintenance supplied with the hotfix downloaded in Step 8, apply it now as instructed in the hotfix documentation. COMMAND ==> ex tableprint('#ed_employees(educ)')
3. To validate output in SDSF, browse the job name of your TSO session and select the DDNAME SYSnnnnn with job class A and destination LOCAL.
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 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. This batch job will uncompress the OSB.XM1 and METASTR.XM1 files 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. If you wish to make additional changes to the values of OSEMOD variables, make the changes now. Below is a sample JCL to allocate and propagate the work copies. Provide a JOB card and submit the JCL. //ALLOC EXEC PGM=IEBCOPY//ICLIST DD DISP=SHR,DSN=<HLQ>.FILECLS//OCLIST DD DISP=(NEW,CATLG,DELETE),// DSN=<HLQNONV>.<INSTVER>.CLIST,// DCB=(RECFM=FB,LRECL=80,BLKSIZE=0),// SPACE=(TRK,(5,10,5),RLSE),UNIT=SYSDA//ICNTL DD DISP=SHR,DSN=<HLQ>.FILECTL//OCNTL DD DISP=(NEW,CATLG,DELETE),// DSN=<HLQNONV>.<INSTVER>.CNTL,// DCB=(RECFM=FB,LRECL=80,BLKSIZE=0),// SPACE=(TRK,(10,10,25),RLSE),UNIT=SYSDA//IJCL DD DISP=SHR,DSN=<HLQ>.FILEJCL//OJCL DD DISP=(NEW,CATLG,DELETE),// DSN=<HLQNONV>.<INSTVER>.JCL,// DCB=(RECFM=FB,LRECL=80,BLKSIZE=0),// SPACE=(CYL,(2,5,40),RLSE),UNIT=SYSDA//IJOBS DD DISP=SHR,DSN=<HLQ>.OSB.FILEI//OJOBS DD DISP=(NEW,CATLG,DELETE),// DSN=<HLQNONV>.<INSTVER>.OSB.JOBS,// DCB=(RECFM=FB,LRECL=80,BLKSIZE=0),// SPACE=(TRK,(5,10,5),RLSE),UNIT=SYSDA//SYSPRINT DD SYSOUT=*//SYSIN DD * CNTL members to edit with OSEMOD: DPLXREDO, OSRUNPRM, PARMBAT, PARMCICS, PARMDC, PARMNEE, PARMTSO, RELAYCFG, SPLXJRN1, SPLXJRN2, SPLXREDO, SPLXSEG0, SPLXSEG1, SPLXSG99Note: Be sure to edit with OSEMOD any member of the working copies of CLIST and JCL that you plan to execute or run. Also check any reference to CNTL parameters in the JCL and edit the affected CNTL member with OSEMOD if required.Invoking OSEMOD in the command line – If you have not added the <HLQNONV>.<INSTVER>.CLIST library in your installation's SYSPROC or SYSEXEC concatenation, you can manually type in the command below from TSO/ISPF Option 6, TSO Commands. It must be reentered every time you get into ISPF, and must be entered on each half of an ISPF split screen. Prefix it with TSO space if you enter it on an ISPF screen other than Option 6. Do not forget to edit CLIST members ADMIN and USER with OSEMOD. S6A3ALOC (EDIT member, invoke OSEMOD in command line, then SUB member) Repeat for the following jobs: S6A3APLY, S6A4ACPT, S6A5CFGR, S6A5DBDG, S6A5FRMT, S6A6POST, S6A7BKUP. For installation details for the Service Gateways for CICS, IMS TM, and WMQ, refer to Chapter 5, Installing the Service Gateway for CICS, Chapter 6, Installing the Service Gateway for IMS TM, and Chapter 7, Installing the Service Gateway for WMQ. For the Service Gateway for Files, refer to TIBCO Object Service Broker Managing External Data. For all other gateways, refer to the gateway specific manuals. Download it and apply any required SMP maintenance at this point as per the documentation with the hotfix. You must respond to a WTOR on this occasion to allow the Data Object Broker to start. For example:12.02.21 JOB04800 S6BKR006A-XYZ REDOLOG AND CACHE FORMATTED. REPLY TO S6BKR09812.02.21 JOB04800 *454 S6BKR098-XYZ READ S6BKR006 AND REPLY G TO GO, C TO CANCEL If there is any database maintenance supplied with the hotfix downloaded in Step 8, apply it now as instructed in the hotfix documentation.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |