Distributing ReportWriter with Your Application

Below are three possible scenarios for how you might distribute ReportWriter.

The steps below should serve as a general guide for what you need to do to distribute ReportWriter. Your actual procedures may vary, depending on how much customization you choose to do, how you set up your development system, whether your development system consists of the same operating system and hardware as your target system, and so forth.

1. If desired, customize ReportWriter by doing one or more of the following:

If the target system is a different endian type than your development system, you must rebuild the ELB that contains these routines. See Endian types for a list of the endian types of various systems.

2. If your customers will be writing their own reports, create repository definitions for this distribution of ReportWriter. For information, see Create New Repository utility.
3. If you are distributing predefined reports that depend on name link associations between the files, or if you want to give this capability to your customers, generate and distribute a repository cross‑reference file. For information, see Generate Cross‑Reference utility (rpsxref).
4. Include the required application files.

For Windows, install Core Components and ReportWriter before installing your own application.

For UNIX and OpenVMS, refer to the table below, which shows the files you need to include when you distribute ReportWriter.

For more information about spawning, chaining to, and calling ReportWriter, see Accessing ReportWriter from Your Application.

If you are…

Include these files

Spawning or chaining to ReportWriter

RPT: rpt.dbr

RPTDAT: rptctl.is?

RPTLIB: synrpt.elb

SYNTXT: syntxt.is?

WND: tklib.elb

Calling ReportWriter with the external subroutine interface

RPTDAT: rptctl.is?

RPTLIB: synrpt.elb

SYNTXT: syntxt.is?

WIN: tklib.elb

Include the required data files:

Keep in mind that your repository files and—if you’re using one—the cross‑reference file must be in sync with one another, must agree with the end‑user’s data file layout, and must all be distributed together.

For information on moving the repository main and text files to other systems see Moving repository files. See also Moving a cross‑reference file and Moving report definition files.

5. Set the necessary environment variables, such as RPSMFIL and RPSTFIL, to point to the location of the data files.