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


Chapter 1 Using TIBCO Object Service Broker Utilities : S6BBRFRU (Reformat TIBCO Object Service Broker Files Transferred with FTP)

S6BBRFRU (Reformat TIBCO Object Service Broker Files Transferred with FTP)
S6BBRFRU reformats TIBCO Object Service Broker files transferred between z/OS and Open Systems using FTP. S6BBRFRU can be used to reformat on z/OS files received from Windows or Solaris or to reformat files on z/OS in preparation for transfer to Windows or Solaris.
Prerequisites
The TIBCO Object Service Broker files must be transferred using FTP. S6BBRFRU does not work with other file transfer tools.
Files created on z/OS must use the FTP LOCSITE sub command with the parameters RDW or NORDW as required. Use of these parameters is explained in the following sections.
File or Data Set Types That Can Be Reformatted
You can use S6BBRFRU to reformat the following types of files or data sets that are to be transferred with FTP:
The procedures for transferring and reformatting each of these file types are explained in the following sections.
Transferring TIBCO Object Service Broker Segment Archives
Reformatting Requirements for Segment Archives
Archives Created on z/OS and Transferred to Windows or Solaris
Segment archives created by the backup utility S6BTLBPS on z/OS can be transferred without intermediate processing to Windows or Solaris for use by TIBCO Object Service Broker. Transfer the files using binary mode and the z/OS FTP LOCSITE sub command with NORDW parameter specified.
Archives Created on Windows or Solaris and Transferred to z/OS
Segment archives created on Windows or Solaris must be reformatted before they can be used on z/OS.
To transfer archive files created by the backup utility hrntlbps on Windows or Solaris, complete the following steps:
1.
The z/OS target file must have a LRECL greater than 36 bytes and a format of either FB or VB. We recommend that FTP be permitted to allocate the file, except in the case of a very large file where you should preallocate a sufficiently large file.
2.
Refer to the following sample JCL.
You should always verify backups created on Windows or Solaris using the hrnbrptr (Batch Pointer Check) utility before using them as archives. Re-formatted archives on z/OS should also be checked with S6BBRPTR (Batch Pointer Check) before they are used.
JCL to Reformat Archives
The JCL must have a statement similar to the following:
PARM=’REFORMAT=ARCHIVE,SEG=segnum,PAGES=numofpages,BYTES=numofbytes’
This statement contains the following parameters:
Provide S6BBRFRU with the number of pages in the archive if you want to check if the archive is complete. This parameter cannot be used if there is more than one segment in the input data set.
Provide S6BBRFRU with the number of bytes in the archive if you want to check if the archive is complete. This parameter cannot be used if there is more than one segment in the input data set.
Sample JCL
The BRFRUARC member of the JCL data set distributed with TIBCO Object Service Broker contains sample JCL required to run this utility to reformat an archive. This sample is provided as a reference only; modify the JCL for your needs.
Transferring TIBCO Object Service Broker Export/Import Table Files
To avoid unpredictable changes to file data, the Default Import/Export Type on Open Systems must be set to the LENGTH_PREFIXED_EBCDIC format if the file is to be transferred. This applies even if the file transfer is occurring within the same operating system.
You must know how the file is going to be used on Windows or Solaris before you use S6BBRFRU. Variable length (V, VB) files or data sets used for import/export tables and workbench unloaded files or data sets are processed identically by S6BBRFRU, since their formatting requirements are identical. However, format requirements for z/OS VB data sets that are to be used by offline batch utilities on Windows or Solaris have different formatting requirements (see below).
Reformatting Requirements for Import/Export Table Files
Files Created on z/OS and Transferred to Windows or Solaris
 
No reformatting is required provided the file is transferred in binary mode and the correct record size is entered in the file’s filespec.dsn entry prior to importing.
These must be reformatted before they are transferred to Windows or Solaris, after which they can be used as import tables.
After reformatting the files using S6BBRFRU (refer to JCL to Reformat an Export Table Created in z/OS), transfer the files using binary mode and the z/OS FTP LOCSITE sub command with NORDW parameter specified.
Files Created on z/OS and Transferred to z/OS
 
No reformatting is required provided the file is transferred in block (not stream) mode.
Files Created on Windows or Solaris and Transferred to z/OS
 
No reformatting is required provided the file is transferred in binary mode and the correct file characteristics are specified for z/OS (FB, LRECL, and so on).
The files must be created in LENGTH_PREFIXED_EBCDIC form and transferred in binary mode. The format of the z/OS target file can be FB or VB. We recommend that you allow FTP to allocate the file, except for a very large file when you should preallocate a sufficiently large file.
Files Created on Windows or Solaris and Transferred to Windows or Solaris
No reformatting is required provided the file is transferred in binary mode.
JCL to Reformat an Export Table Created in z/OS
The JCL must contain a statement similar to the following:
PARM=’REFORMAT=platform’
where platform is one of the following:
Sample JCL
The BRFRUEXP member of the JCL data set distributed with TIBCO Object Service Broker contains sample JCL required to run this utility to reformat an export table. This sample is provided as a reference only; modify the JCL for your needs.
Transferring Missing BDW Variable Format Files
Missing BDW (Block Descriptor Word) Variable Format files are created when z/OS VB files are transferred to either Windows or Solaris using the z/OS FTP LOCSITE sub command with RDW parameter specified. FTP strips all block descriptor words during the transfer, so the file produced on the target platform is a non-z/OS-standard variable format file.
Reformatting Requirements for BDW Variable Format Files
If the file is to be transferred back to z/OS, it must be reformatted as follows:
1.
The z/OS target file must have a VB format. If the format is FB, there could be pad bytes appended to the last record in the file that could be taken as extra records. If there are pad bytes, a warning is issued by S6BBRFRU.
2.
Refer to the following sample JCL.
JCL to Reformat a Missing BDW Variable-Format File
The JCL must contain the following statement:
PARM=’REFORMAT=NODBW’
Sample JCL
The BRFRUBDW member of the JCL data set distributed with TIBCO Object Service Broker contains sample JCL required to run this utility to reformat a missing BDW variable-format file. This sample is provided as a reference only; modify the JCL for your needs.
Transferring Workbench Unload Files
To avoid unpredictable changes to file data, the Default Read/Write File Type on Open Systems for the UNLOAD tool must be set to LENGTH_PREFIXED_EBCDIC if the file is to be transferred. This applies even if the file transfer is occurring within the same operating system.
Reformatting Requirements for Workbench Unload Files
Unload Files Created on z/OS and Transferred to Windows or Solaris
These files must be reformatted by S6BBRFRU before they are transferred to Windows or Solaris. Complete the following steps:
1.
Refer to the following sample JCL.
2.
Transfer the file to Windows or Solaris using binary mode and the z/OS FTP LOCSITE sub command with NORDW parameter specified.
3.
Use the TIBCO Object Service Broker administrator’s workbench LOAD option or the LOAD tool from the developer’s workbench.
Unload Files Created on z/OS and Transferred to z/OS
No formatting is required provided the file is transferred in FTP block (not stream) mode.
Unload Files Created on Windows or Solaris and Transferred to z/OS
These files must be reformatted before they are loaded on z/OS. Complete the following steps:
1.
2.
The z/OS target file must have a format of FB or VB. We recommend that FTP be permitted to allocate the file, except in the case of a very large file where you should preallocate a sufficiently large file.
3.
Refer to the following sample JCL.
4.
Use the TIBCO Object Service Broker administrator’s workbench LOAD option or the LOAD tool from the developer’s workbench.
Unload Files Created on Windows or Solaris and Transferred to Windows or Solaris
No reformatting is required provided the file is transferred using binary FTP.
JCL to Reformat Workbench Unload Files
The JCL must contain a statement similar to the following:
PARM=’REFORMAT=platform’
where platform is one of the following:
Sample JCL to Reformat an Unload File Created from the z/OS Workbench
The BRFRUUNL member of the JCL data set contains sample JCL required to run this utility to reformat an unload file created in z/OS. This sample is provided as a reference only; modify the JCL for your needs.
Sample JCL to Reformat an Unload File Created in Windows or Solaris
The BRFRULOD member of the JCL data set distributed with TIBCO Object Service Broker contains sample JCL required to run this utility to reformat an unload file created in Windows or Solaris. This sample is provided as a reference only; modify the JCL for your needs.
Transferring TIBCO Object Service Broker Offline Batch Utility Unload Files
Offline batch utility unload files are created by the utilities S6BBRULB, S6BBRULH, or S6BBRULA.
Reformatting Requirements for Offline Batch Utility Unload Files
Files Created on z/OS and Transferred to Windows or Solaris
No formatting is required provided the files are transferred to Windows or Solaris using binary mode and the z/OS FTP LOCSITE sub command with RDW parameter specified. After the files are transferred, they can be loaded using hrnbrtbl or translated using hrnbrnls.
On Open Systems, when loading using hrnbrtbl or translating using hrnbrnls, ensure that the control file (-c) indicates variable format and do not specify the -m command line option. Although the transferred files are VB format on z/OS, after the transfer they no longer contain block descriptor words and are therefore not valid VB files.
TIBCO Object Service Broker format requirements for z/OS-created VB data sets to be used by offline batch utilities on Windows or Solaris are different from the requirements of Import/Export table data sets. You must therefore know what the intended use of the file on Windows or Solaris is before using S6BBRFRU.
Files Created on Windows or Solaris and Transferred to z/OS
These files must be reformatted on z/OS before they can be loaded or translated. Complete the following steps:
1.
The z/OS target file must have a VB format. If the format is FB, there could be pad bytes appended to the last record in the file that could be taken as extra records. If there are pad bytes, a warning is issued by S6BBRFRU.
2.
Refer to the following sample JCL.
3.
JCL for Reformatting Offline Batch Utility Unload Files
The JCL must contain the statement PARM=’REFORMAT=OFFLINE’.
Sample JCL
The BRFRUOFF member of the JCL data set distributed with TIBCO Object Service Broker contains sample JCL required to run this utility to reformat an offline unload file from the Batch utility. This sample is provided as a reference only; modify the JCL for your needs.

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