![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
You can use this task to specify the destination of the export table as well as the name of external routines if you want to manipulate the data at its source before exporting.
The File field contains the name of the file to which you are exporting the data. The maximum record size is 31,744 bytes on all platforms. The record length for fixed length files must be at least equal to, and the record length for variable length files must be at least four more than, the total length of the fields.
• z/OS: Under CICS, you do not have to define the data set in a Destination Control Table (DCT) but the CICS Region must have external security access to the data set.
• Open Systems: To specify the format of the data in external files to be processed by TIBCO Object Service Broker, use the DSIXFTYPE Execution Environment parameter. For more information on the DSIXFTYPE Execution Environment parameter, refer to TIBCO Object Service Broker Parameters.
• Open Systems: This filename maps to an entry in the filespec.dsn file. This file describes the absolute path through which this filename can be accessed along with other file attributes. If the filename is mapped to an entry in the file, special characters (*, ?, <, >) included in the filename are ignored. If a default path name is used, special characters in the filename are replaced and you do not receive the intended filename. For more information on filespec.dsn, refer to the Appendix B, Mapping File Names for Open Systems.
• If you use FTP to transfer a variable length export table file between z/OS and Windows or Solaris, you must reformat the file using the TIBCO Object Service Broker z/OS utility S6BBRFRU. If the export file is fixed length, you do not have to reformat the file.
• For parameterized export tables, you must specify a partitioned data set or a directory. Neither of these has to exist before you define the export table but must exist before you insert data. Parameter values you provide become the data set member names or the filenames in the directory. You can create only one table instance per TIBCO Object Service Broker transaction.The parameter must have syntax C. On z/OS, the parameter’s length must be 8. In Open Systems, its length must be 8 or less.
• With non-parameterized export tables you can export data to any file or member of a partitioned data set.TIBCO Object Service Broker for z/OS Utilities for more information about S6BBRFRU.The DDname field points to the file to which you are exporting the data. You specify a DDname if you want to change the export data set without changing the table definition or if you want to export to an uncataloged data set (possibly tape).
• z/OS: You must associate DDname with the data set that is the destination of the data. To do this, use JCL or the TSO ALLOCATE command.
• z/OS: To export data to a partitioned data set, specify the member in the DD statement of your JCL or your TSO ALLOCATE command.
• z/OS: The DDname field is valid in TIBCO Object Service Broker multiple session environments under CICS, IMS TM, or Native Execution Environment only if you use a file disposition other than DISP=SHR in the definition of these environments. This is to prevent concurrent updates.
• Open Systems: In the DDname field, specify either the name of the environment variable that contains the fully qualified name of the file, or the name of a DD definition in the filespec.dsn file.
• If you are writing multiple export tables to a single file, the DDname in all the export tables must be the same.The Server ID field points to the gateway that is to be used if the table is to be accessed remotely via the Service Gateway for Files. This is an optional specification. The value in this field is determined from the SERVERID Execution Environment parameter.Refer to Monitoring of Service Gateway for Files for details about the Server ID and the Service Gateway for Files.TIBCO Object Service Broker Parameters for information about the SERVERID parameter.The External Routine Name field, which is valid only for the z/OS platform, contains the name of an external routine that you can use to manipulate data before exporting it to the destination data set. This routine is a load module resulting from an assembler program and resides in a data set that is concatenated to the external utilities data set. For more information, refer to External Routines (Pre-processing the Data).
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |