You can configure FilePublisher to publish non-text files by using the isBinary=true parameter and the
messageItem parameter tags in the FileType section. When transmitted to a Subscriber, numeric data types are converted to
FLOAT,
STRING or
INTEGER TIBCO data types.
When you configure one of these data types, you use the “type” tag to identify the type of numeric field. To specify a binary decimal field, you can specify
type=”
binary” or
type=”
COMP” or
type=”
COMP-4”. To specify packed decimal, you can specify
type=”
PACKED” or
type=”
COMP-3”.
Floating-point numeric fields are specified as either COMP-1 or
COMP-2.
COMP-1 indicates that the input field is a 4 byte long floating point number.
COMP-2 indicates that the input field is an 8 byte long floating point number.
See File Publisher Examples for an example of a FilePublisher configuration file that handles the supported numeric data types.
You can configure the Adapter to publish a field without translating the data within the field. Usually, when FilePublisher reads a record from a file, it translates the data within each field to TIBCO Rendezvous “wire format,” which is then published. When FileSubscriber receives the published message, it converts the “wire format” message to the appropriate data type for the platform that it is on.
If it is necessary to publish binary data other than the supported COBOL numeric data types, from one platform to another platform that supports the same data types (such as from one EBCDIC machine to another EBCDIC machine), you can specify
OPAQUE for the data type. When you do this, the data in the field is published “as is,” with no conversion. When the FileSubscriber receives the
OPAQUE TIBCO Rendezvous message, it writes the data in that field to the field “as is.”
1.
|
Set the isBinary parameter in the FILE_OPTIONS element to true.
|
2.
|
Set the type tag in the messageItem parameter to the desired value.
|
This section explains how to configure the FilePublisher for Virtual Storage Access Method (VSAM) files. Configuration for VSAM files is similar to that for GDG and Sequential file types. FilePublisher supports all three VSAM file types named, entry-sequenced data sets (ESDS), key-sequenced datasets (KSDS), relative-record data sets (RRDS).
FilePublisher reads a VSAM file and publishes each record as a TIBCO message. Each VSAM file type has a separate FILETYPE definition. A VSAM file type can be perceived as a Sequential file type when it comes to configuration. A VSAM file can only be published by using the trigger message method. The polling method is not supported. By default, a VSAM file type is treated as a binary file and hence all the characteristics of the binary files apply to VSAM files.
FilePublisher reads the z/OS catalog information for the VSAM file specified in the
inputDataset and uses it to open the file and read the data from the file being published. The VSAM file to publish must be allocated using IDCAMS. For KSDS VSAM files, the
inputDataset name is the cluster name when you are publishing using the primary key. The flag
vsamAltIndex allows you to specify alternate path file names for KSDS VSAM files. This facilitates the publishing of the KSDS VSAM files based on alternate keys. For ESDS and RRDS files, the
inputDataset name is the cluster name. The following catalog information is retrieved:
•
|
NAME—associated file names. Used when tracking down the underlying base DATA file's file type, record length and share information for ALTINDEX files.
|
The file can be published from the beginning (from the first record) or from a specified beginning key (STARTKEY). The file is published from this point until the end of file is reached, a specified end key (ENDKEY) is reached, or a specified number of records (MAXRECORDS) is published. All these values can be listed in the trigger message. The file name to be published is specified in the DATA field of the trigger.
This file name must match the file name specified in inputDataset. The file name is usually the name of the cluster. When publishing a file based on the alternate index, the name of the file must be the path name for that alternate index, and it must match one of the
vsamAltIndex names specified in the configuration file. See
Sample Configuration for VSAM Files Using the Alternative Key.
|
|
|
|
|
|
|
|
|
|
|
|
|
NOTE: This option is not available while publishing the KSDS AlternatePath files.
|
|
|
Data from a file is normally published with a predefined subject name. However, if the subject name is not constant for all the lines of data in a file, and if the subject depends on a certain data field from the input file, specify a valid node within angle brackets (< >). A valid node is a label of a defined
messageItem parameter prefixed by its container name separated by a period.
uses data of the label RoutingCode in the container name
ChKey to construct the
publishSubjectName. That is, if the value of
RoutingCode in the message to publish is 154363, the
publishSubjectName for publishing, that message is
CHECK.JAN.154363.CLEARED.
FilePublisher supports publishing of floating point (double) values, as either float (4 byte) or double (8 byte). The adapter defaults to 6-digit precision for these values. In all other cases, you should publish float and double values as type
STRING.
You can configure FilePublisher to specify the list of anticipated subscribers for the subjects it is publishing. By pre-registering the anticipated subscribers, the delivery of certified messages is guaranteed even if FileSubscribers start before or after the configured FilePublisher or even if a FileSubscriber is stopped and restarted later. To use this feature, both the FilePublisher and FileSubscriber should establish RVCM sessions with the
requireOldMessages parameter set to
true. To implement the pre-registering of subscribers, include this section in the FilePublisher configuration file:
listeningSubject = "<name of the subject subscribed for>" },
listeningSubject = "<name of the subject subscribed for>" }
•
|
useExplicitConfirmation: Flag that specifies whether Explicit Confirmation Mode is on or off during block transfer.
|
•
|
ECMSubsriberName: This field specifies the corresponding ECM subscriber(s) name. When there are more than one participating subscribers, repeat this option and enter a unique subscriber name.
|
•
|
retransmissionDelayTicks: Specifies the number of seconds the FileSubscriber should wait between retries to re-connect to the Publisher after a startup. It is used to coordinate the startup handshake used between the Publisher and Subscriber, when ECM is being used. Default is 10 seconds.
|
•
|
noWaitAfterConfirmations: If true, the next transaction is processed immediately after FilePublisher receives all the confirmations. If false, it uses the normal transactionDelay parameter to process transactions. Default is " true".
|