Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 10 Accessing and Processing VSAM LDS Data : Setup of Accesses to VSAM LDS Data

Setup of Accesses to VSAM LDS Data
Access to VSAM LDS data is only supported via the SDK. Once the SDK has been installed you need to define the appropriate tables to facilitate the manipulation of the VSAM LDS data and then write the rules to process the data. Your applications used to access the VSAM LDS data are comprised of these table definitions and rules.
Installation of the TIBCO Object Service Broker Base Component
You must install TIBCO Object Service Broker base component in order to use the SDK to access VSAM LDS data. The base component can reside on z/OS, Windows or Solaris. Installation instructions for all platforms are located in TIBCO Object Service Broker Installation and Operations.
Installation of the SDK
Installation instructions for the Service Gateway for Files, which includes the SDK, are located in TIBCO Object Service Broker Managing External Data.
Required Tables
VSAM LDS data is accessed via a combination of TIBCO Object Service Broker tables: VSAM LDS and VSAM MAP. An access to VSAM LDS is performed via a VSAM LDS table. Data manipulation is performed via VSAM MAP table support.
See Also
TIBCO Object Service Broker Managing External Data for information about the Service Gateway for Files and about the VSAM accesses discussed in this chapter.
TIBCO Object Service Broker Managing Data for information about MAP tables.
TIBCO Object Service Broker Shareable Tools for information about the tools used for MAP tables.
Definition of VSAM LDS Data
To access VSAM LDS data, first define a table of type of VSM from TIBCO Object Service Broker. This table is used to map the VSAM data for use within TIBCO Object Service Broker. For details on defining VSAM tables within TIBCO Object Service Broker, refer to TIBCO Object Service Broker Managing External Data.
The VSAM LDS definition is very similar to that for other VSAM data sets, with the following key differences:
The definition of the table must consist of 3 binary fields of the length 4, the first of which must be the primary key. While the Field names may be different their usage will remain constant.
The fields of the table definition are as follows:
This field is the Relative Byte Address of the LDS record to be processed. It must be on a control interval boundary and for an INSERT must be higher than the current High Used Relative Byte Address for the data set.
Following is the definition for a sample VSAM LDS table:

 
COMMAND==> TABLE DEFINITION

Table: LINEAR Type: VSM Unit: USR40 IDgen: N

File : S6B.XX.LINEAR
DDname: Read Only: N Load: N Data Set Type: LDS
Ignore:
Server ID: FGSERVER
Parameter Name Typ Syn Len Dec Class ' Event Rule Typ Acc
---------------- - -- --- -- - ' ---------------- - -
_ LOCATION I C 16 0 L ' _
_ ' _
-------- VSAM --------|---------- Metadata Definition ------
Field Name Xsyn Xlen Xdec Offset Key Typ Syn Len Dec Ord Rqd Default
---------------- ---- ----- -- ----- - - -- ----- --- - - --------

_ RBA B 4 0 0 P B 4 0
_ ADDRESS B 4 0 4 B 4 0
_ CISIZE B 4 0 8 B 4 0
_
_
_
_
PFKEYS: 3=END 12=CANCEL 22=DELETE 13=PRT 14=FIELDS 6=OFFSET 21=DATA 2=DOC

 
Definition of Associated MAP Table
In addition, you must also define an associated MAP table. For details on defining MAP tables within TIBCO Object Service Broker, refer to TIBCO Object Service Broker Managing Data.
The definition is very similar to a normal MAP table. For VSAM MAP tables the following definition rules apply:
The table definition may also contain a count parameter.
Following is the definition for a sample VSAM MAP table:

 
COMMAND==> TABLE DEFINITION

Table: LINEARMAP Type: VSM Unit: USR40 IDgen: Y

File : S6B.XX.LINEAR
DDname: Read Only: N Load: N Data Set Type: MAP
Ignore:
Server ID: FGSERVER
Parameter Name Typ Syn Len Dec Class ' Event Rule Typ Acc
---------------- - -- --- -- - ' ---------------- - -
_ ADDRESS I B 4 0 A ' _
_ LOCATION I C 16 0 L _
-------- VSAM --------|---------- Metadata Definition ------
Field Name Xsyn Xlen Xdec Offset Key Typ Syn Len Dec Ord Rqd Default
---------------- ---- ----- -- ----- - - -- ----- --- - - --------

_ KEY              B 4 0 0 P I   B 4 0
_ DATA             B 4 0       0         B 4 0
_
_
_
_
PFKEYS: 3=END 12=CANCEL 22=DELETE 13=PRT 14=FIELDS 6=OFFSET 21=DATA 2=DOC


 

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved