![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
Installation verification for an external DBMS provides a quick method to verify that the installation of a TIBCO Object Service Broker DOB and one or more DBMS Service Gateways was successful. This verifies that the communication between the DOB and a Service Gateway, and a Service Gateway and the DBMS, is functioning properly.The verification procedure is split between two elements. First, the IVPIMSP member that was placed in <HLQNONV>.<INSTVER>.JCL by the installation procedure for the Service Gateway for IMS/DB, creates a PSB with PROCOPT=GP, copied from DFSIVP6, and starts the Gateway.Once the Service Gateway is running, the second element, IVPIMS, must be run in the environment of the Data Object Broker. IVPIMS is a batch file, shell script, or JCL member, which loads a DBD file corresponding to the IBM-supplied IMS table IVPDB1, and accesses data in the external database to verify connectivity.Each of these steps can be done manually, meaning you can start the Service Gateway for IMS/DB normally rather than by using IVPIMSP, and you can browse data in the external database via the Gateway without using the shell script/batch file/JCL.TIBCO Object Service Broker tables are pre-defined with definitions that correspond to the sample tables or demo databases commonly included with the various external DBMSs. In the case of DB2, the table IVPDB1 is used. The TIBCO Object Service Broker tables are prefixed with the name S6BIVP*, for example S6BIVP_IMS.
If a DBMS does not have sample tables or a demo database, or these were not included in its installation, you need to manually verify access to one of your databases. Instructions to perform this can be found later in this manual.
•
• The installation of a Service Gateway that must be run from an APF authorized library. If the DOB is running on z/OS, the Gateway must be properly configured in Resource Management.
• The sample table IVPDB1, which is commonly installed with IMS. The IVP depends upon the presence of data in this table, but does not rely on any specific values within the table.
• The IBM-supplied data sets IMS1010.IMS1.DFSIVD1 and IMS1010.IMS1.DFSIVD1I (or versions appropriate to your version of IMS/DB) must be present, and the user must have TSS/RACF permissions to access these data sets. Note that if your version of these files are different from these, the data set names in the IVP itself will have to be changed to match. See variables $IMSIVPDB$ and $IMSIVPIX$ in OSEMOD.
• The configuration of the communications path between the Service Gateway and the Data Object Broker.
• A valid level 1 TIBCO Object Service Broker user Id must exist matching the IDPREFIX parameter specified in the Gateway startup JCL.Before you run the Installation Verification Procedure (IVP), you must configure the communication path that the Service Gateway will use to communicate with the Data Object Broker. The details of this configuration depend upon whether the Data Object Broker is installed on z/OS or on an open systems platform, and upon the communication protocol to be used.
• If the DOB is on z/OS and you are not using TCP/IP to communicate between it and the Gateway, comment out the DD statement for S6BRELAY in the IVPIMSP JCL member.
• If the DOB is on Windows or UNIX, and the communications protocol is TCP/IP, then the communications configuration for the Service Gateway is determined by the relay file placed in <HLQNONV>.<SLQ>.RELAYCFG by the installer. A complete discussion of how to configure the relay file is beyond the scope of this document; for details, see TIBCO Object Service Broker for z/OS Installing and Operating.For the purpose of the IVP only, a simplified file will suffice. The following example illustrates a relay file that configures a connection to a remote DOB on Windows/Unix.
<relay xmlns="http://www.tibco.com/OSB/relayparms.xsd">
<tcpipparms tcbnum="3" maxtcbsockets="50" />
<directory>
<node name="WINDOB">
<tcpip host="192.168.1.1" port="12000" />
</node>
</directory>
</relay>
Substitute the name, host, and port for your DOB into this template. They can be found in the HURON.DIR file in the database directory of the TIBCO Object Service Broker installation to which you are trying to connect.Member IVPIMSP in data set <HLQNONV>.<INSTVER>.JCL contains the job steps required to prepare the Service Gateway for the verification process. If all requirements are met, customize the JCL and run it. Note that if the Service Gateway has already been configured and started, this step is not necessary.To customize the JCL, replace each instance of $TDS$ in the JCL with the DOB node name that you placed in the relay file.In the same JCL, note the value of IDPREFIX. A valid TIBCO Object Service Broker user Id with this name must exist in the DOB to which you will be connecting.
• On Windows, the batch file ivpims.bat is in the bin directory of your TIBCO Object Service Broker installation. Variables within the file need to be customized; directions for doing so are in the file. The customization includes setting where the results will be placed.
• On Solaris, the (ksh) shell script ivpims.ksh is in the bin directory of your TIBCO Object Service Broker installation. Shell and environment variables within the script need to be customized; directions for doing so are in the script. The customization includes setting where the results will be placed.
• On z/OS the JCL member IVPIMS will be found in the <HLQNONV>.<INSTVER>.JCL data set associated with the DOB. The customization will involve supplying values for TDS, USERID, and PASSWORD. The results will be placed in the job's output, and may be viewed using SDSF.
1. Perform any DBMS preparation work, such as establishing a Program Specification Block.At the DOB's node, using ivpims.bat, or the corresponding shell script or JCL member:
2. Check the results. Sample data from the database will be present in the output if the verification procedure succeeded.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |