To access VSAM data directly from TIBCO Object Service Broker, you must define a TIBCO Object Service Broker table of type VSM. A VSAM table can have one or more fields, one or more data parameters (to a total maximum length of 255 bytes), up to 16 fields in a composite primary key (to a total maximum of 127 bytes), and an optional location parameter. The table can also contain multiple record formats.
COMMAND==> TABLE DEFINITION Table: EMPLOYEE_VSAM_KS Type: VSM Unit: USR40 IDgen: N
File :
DDname: Read Only: Y Load: N Data Set Type: KSDS
Ignore:
Server ID:
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
---------------- ---- ----- -- ----- - - -- ----- --- - - ----------
_
_
_
_
_
_
_
PFKEYS: 3=END 12=CANCEL 22=DELETE 13=PRT 14=FIELDS 6=OFFSET 21=DATA 2=DOC
When you create a table in the TIBCO Object Service Broker UI, you can use a copybook as the source for its definition. You can then have TIBCO Object Service Broker monitor changes to the copybook. For more information, refer to
Using Data Discovery.
After invoking the Table Definer (refer to Initial Step for Defining Tables for information on invoking the Table Definer), complete the following tasks to define a VSAM table:
TIBCO Object Service Broker Managing Data for more information on minimal definitions.