![]() |
Copyright © TIBCO Software Inc. All rights reserved |
Option 1 of TIBCO Adapter for Files (IBM i) is for the RV samples, which are restored in library TIBFASMPRV by default. Similarly, Option 2 is for the EMS samples, which are restored in library TIBASMPEM. Each set of the samples provides the following files:
•
• File INIFPUB with sample configuration members PUB001, PUB002 and so on as appropriate for the sample set. Each member contains the configuration parameters for FilePublisher to do a specific type of work. See the README file for details, or the prologue at the top of each member.
• File INIFSUB with sample configuration members SUB001, SUB002 and so on as appropriate for the sample set. Each member contains the configuration parameters for FileSubscriber to do a specific type of work. See README file for details, or the prologue at the top of each member.
• File QCLSRC with members RUN001, RUN002 and so on as appropriate for the sample set. Each member contains CL code to start up a FilePublisher/FileSubscriber pair. Member SNDTRG002 contains the CL code to send a trigger to PUB002. Member COMPILE contains CL that can be used to compile the SNDTRG002 program, RUNFA001, RUNFA002 and so on.
• The following data files are used with the sample configuration files above: BIN2, FT11, FT21, and FT31.
•
•
• Programs RUNFA001, RUNFA002 and so on, and SNDTRG002 matching the members in QCLSRC. These programs were created when the option was restored using the COMPILE program.
• Each FilePublisher/FileSubscriber pair (except PUB002/SUB002) utilizes file polling at timer intervals to query whether there are any matching files in INPUT_LIBRARY to publish. PUB002/SUB002 starts publishing when FilePublisher receives an external trigger.Note that each executing FilePublisher/FileSubscriber pair can be configured to handle multiple FileType definitions concurrently. So all non-conflicting INIFPUB file members could be combined into one member, and FilePublisher can process all of these FileType definitions at the same time. The same is true for the Subscriber. For details on FileType definitions, see FileType Section.This example assumes that the RV daemon is running on the same machine as the adapter. If communicating with a RV daemon running on a remote machine, the remote host name has to be specified. For example, remote_host1:7500. For additional details, see the TIBCO Rendezvous documentation.
The publishing process requires a PROCESS_LIBRARY for holding intermediate data and a FilePublisher OUTPUT_LIBRARY for holding the file after it is published. In addition, there must be a FileSubscriber OUTPUT_LIBRARY for holding progress files, intermediate results, and the final published file. These three libraries are required before starting FilePublisher and FileSubscriber.
− Accept the FAPUBPROC, FAPUBOUT, and FASUBOUT library names which are already specified as defaults in the sample configuration files provided.
− Modify TIBFASMPRV/INIFPUB(PUB001) by changing names provided for PROCESS_LIBRARY and OUTPUT_LIBRARY to libraries of your choice, and modify TIBFASMPRV/INIFSUB(SUB001) by changing the OUTPUT_LIBRARY to a library of your choice.
Before proceeding, note that file FT11 exists in library TIBFASMPRV. If this file is not there because of a previous sample run, duplicate the file from BKP_FT11.
− Call the sample program RUNFA001.
ADDLIBLE TIBFALIB
qsh
cd /usr/tibco/tibfa/PRODUCT-LIBRARY-NAME
sxf3rsub -config 'TIBFASMPRV/INIFSUB(SUB001)'where PRODUCT-LIBRARY-NAME is the name of the library in which the product option is installed, usually TIBFALIB.ADDLIBLE TIBFALIB
qsh
cd /usr/tibco/tibfa/PRODUCT-LIBRARY-NAME
sxf3rpub -config 'TIBFASMPRV/INIFPUB(PUB001)'where PRODUCT-LIBRARY-NAME is the name of the library in which the product option is installed, usually TIBFALIB.Note also that to execute multithreaded applications from QShell, you must ensure that the environment variable QIBM_MULTI_THREADED has a value of Y. This might be done before starting the QSHELL, as follows:You can also set the environment variable at LEVEL(*JOB) so that the variable applies to the current job only.
1. Before submitting the samples edit the EMS_SESSION parameter in the publisher and subscriber configuration files to reference your EMS Server. For example if your EMS Server is running on a machine with IP address 10.98.32.103 and is using the default port the entry, would look like this:
The publishing process requires a PROCESS_LIBRARY for holding intermediate data and a FilePublisher OUTPUT_LIBRARY for holding the file after it is published. In addition, there must be a FileSubscriber OUTPUT_LIBRARY for holding progress files, intermediate results, and the final published file. These three libraries are required before starting FilePublisher and FileSubscriber.
− Accept the FAPUBPROC, FAPUBOUT, and FASUBOUT library names which are already specified as defaults in the sample configuration files provided.
− Modify TIBFASMPEM/INIFPUB(PUB001) by changing names provided for PROCESS_LIBRARY and OUTPUT_LIBRARY to libraries of your choice, and modify TIBFASMPEM/INIFSUB(SUB001) by changing the OUTPUT_LIBRARY to a library of your choice.
Before proceeding, note that file FT11 exists in library TIBFASMPEM. If this file is not there because of a previous sample run, duplicate the file from BKP_FT11.
− Call the sample program RUNFA001.
Display 1:
qsh
cd /usr/tibco/tibfa/PRODUCT-LIBRARY-NAME
sxf3esub -config 'TIBFASMPEM/INIFSUB(SUB001)'where PRODUCT-LIBRARY-NAME is the name of the library in which the product option is installed, usually TIBFALIB.where PRODUCT-LIBRARY-NAME is the name of the library in which the product option is installed, usually TIBFALIB.Note also that to execute multithreaded applications from QShell, you must ensure that the environment variable QIBM_MULTI_THREADED has a value of Y. This might be done before starting the QShell, as follows:You can also set the environment variable at LEVEL(*JOB) so that the variable applies to the current job only.Prior to starting the adapter, file FT11 was in library TIBFASMPRV or TIBFASMPEM. When the adapter was started, FilePublisher searched for matches for files with a prefix of FT1 specified in PUB001. File FT11 matched the prefix and was published. The file was copied to the PROCESS_LIBRARY, transmitted to FileSubscriber, and then moved to the FilePublisher OUTPUT_LIBRARY. FileSubscriber received the file and placed it in its OUTPUT_LIBRARY. FilePublisher then continues to poll for files with the prefix FT1.CD /usr/tibco/tibfa/PRODUCT-LIBRARY-NAMEThe termination message contains the name of the FilePublisher or FileSubscriber instance that you want to stop. For details on the adapter instance names, see the ADAPTER_NAME element in either FilePublisher or FileSubscriber configuration in Chapter 3.Examples of trace logs from a successful session and a failed session are shown in Appendix A, Trace Log Examples. Samples PUB001 and SUB001 have been configured to write the trace logs in TIBFASMPRV/PUBLOG(PUB001) and TIBFASMPRV/SUBLOG(SUB001), respectively.
Any major check point messages, such as start, stop, and error messages, are sent to QSYSOPR *MSGQ. The command to view the messages is as follows:
![]() |
Copyright © TIBCO Software Inc. All rights reserved |