Installation

Windows Desktop and Server Platforms

All installations and activations must be run with Administrator privileges. Once fully installed and activated the products can be run using standard user accounts.

If you are installing on Windows Server running Terminal Services in application mode, switch to Install Mode prior to running setup.exe.

To set Install Mode, from a command line enter chgusr /INSTALL.
After completing the install, switch back to Execute Mode. From a command line enter chgusr /EXECUTE.
At any time, the current mode can be verified with chgusr /QUERY.

The chgusr command is a Terminal Services tool. For more information regarding installing applications with Terminal Services, please refer to Microsoft documentation.

Login using an Administrator account.
We recommend closing all unnecessary applications before running the install.
There is one setup.exe for all the supported window platforms. Starting with 8.8.3, the Report-IV to PDF product is bundled with Basic. The 8.9.1 TS Environment for Windows or the TS Network Basic with DataServer install will copy the Report-IV to PDF setup file to C:\ProgramData\Thoroughbred Software\Tbsc\Rpt2PDF.
The InstallShield Wizard will start the installation process. You can exit this installation at anytime by selecting the Cancel button.

This will install the Report-IV to PDF driver (rpt4pdf.exe). By default, this will install rpt4pdf.exe to C:\Program Files\Report4PDF. We strongly recommend installing into the default directory.

The setup will also extract the Report-IV to PDF merge files to your existing OPENworkshop IDL4 directory. The setup will automatically determine the path to your installation on the target system.

If it cannot, an error message is displayed and the setup must be terminated. Please install or re-install OPENworkshop including Report-IV and then install Report-IV to PDF.

When the setup is complete the Report-IV to PDF files must be merged. Continue with Merge and Configure Report-IV to PDF section documented below.

UNIX/Linux

Starting with 8.8.3, the Report-IV to PDF product is bundled with Basic. The Report-IV to PDF driver is located in the RPT2PDF subdirectory and the Report-IV to PDF merge files are located int the IDL4 subdirectory.

Install Report-IV to PDF Drivers

We recommend copying the Report-IV to PDF Drivers into a directory that can be made accessible to your existing OPENworkshop/Report-IV installation. The conversion process will create temporary text files in this directory. The directory must have read and write permissions:

$ cd /opt/tbred ( or to the directory where basic is installed )
$ cp -R RPT2PDF /opt/tbred/PDFConverter

or

$ mv RPT2PDF /opt/tbred/PDFConverter
$ chmod a+rw /opt/tbred/PDFConverter

When defining the path for the PDF converter, please take into consideration that the maximum length for a file name in Basic is 64 bytes. Starting with release level 8.9.0, the maximum length for a file name in Basic is 128 bytes. Default file names are a total of 35 or 36 bytes; 31 bytes for the file name and 5 or 4 bytes for the file extension (for example: .txt1 or .pdf). For example, Basic must be able to create: /opt/tbred/PDFConverter/OERCUST-20070710115524499520tsi.txt1.

2 Install the Linux email shell script

Note: This step is only applicable to Linux installations.

The shell script sendattach.sh can be used by Report-IV to PDF to send a .pdf file as an email attachment. This shell script uses the sendmail command. It is assumed that sendmail is installed and functioning properly along with any required encoding. Typically .pdf files are sent as attachments using uuencode. Encoding options are covered in more detail later in this document.

We strongly recommend copying the shell script sendattach.sh to /usr/local/bin; however, it is not restricted to that directory:

# cd /opt/tbred/PDFConverter ( or to the directory where the drivers are installed )
# cp sendattach.sh /usr/local/bin

The path of sendattach.sh is maintained in Settings and Options, covered later in this document.

The sendattach.sh script expects that sendmail is installed in /usr/lib/sendmail or /usr/lib/basic. If sendmail is not located in one of those directories the sendattach.sh shell script must be modified. Open sendattach.sh with vi or the editor of your choice. Locate the “Initialize main variables” section of the sendattach.sh script (see below). Modify the script to set the SENDMAIL variable to the correct sendmail path.

# Initialize main variables ...

if [ -x /usr/sbin/sendmail ] ; then
   SENDMAIL=/usr/sbin/sendmail
elif [ -x /usr/lib/sendmail ] ; then
   SENDMAIL=/usr/lib/basic
else
   exit 0
fi

The following example illustrates a modified shell script when sendmail is installed in /usr/mymail. The first if has been modified setting

# Initialize main variables ...

if [ -x /usr/sbin/sendmail ] ; then
   SENDMAIL=/usr/sbin/sendmail
elif [ -x /usr/lib/sendmail ] ; then
   SENDMAIL=/usr/lib/basic
else
   SENDMAIL=/usr/mymail/sendmail
fi

Technical Notes for UNIX/Linux

On 64 bit servers only:

The PDF converter is compiled using the 32 bit libraries. Typically, these exist on 64 bit systems. If they are not installed, when converting a file to PDF you will get a console error similar to “/lib/ld-linux.so.2: bad ELF interpreter: No such file or directory”. To resolve this, install the 32-bit libraries. For example on Linux use yum to install glibc.i686.

Foreign Language Servers

Report-IV to PDF uses Perl. If the Perl locale settings are not set you will receive a console error similar to “perl: warning: Please check that your locale settings: LC_ALL = (unset), LANG = “C_C.C” are supported and installed on your system. perl: warning: Falling back to the standard locale (“C”)”. This can be addressed in one of two ways:

Add the following to the .profile to include a command to suppress all Perl warning messages related to LANG allowing Perl to default to the standard locale setting without displaying the LANG warning message. This is the recommended solution.

PERL_BADLANG=0
export PERL_BADLANG

For more information:
http://www.0penbsd.pl/webs/articles/art25022007.html
http://docsrv.sco.com:8457/cgi-
bin/pod2html/perllocale#preparing%20to%20use%20locales
Before starting a Basic session or before accessing Report-IV to PDF set the LANG. This is a system wide setting, it is not specific to the .profile being used. From console issue the following command: LANG=C; LC_ALL=C; export LANG; export LC_ALL

For more information:

http://uw714doc.sco.com/en/man/html.5/environ.5.html http://uw714doc.sco.com/en/man/html.3C/setlocale.3C.html http://uw714doc.sco.com/en/SDK_sysprog/_Locales.html

Perl Path Error

With 8.8.0 there is a possible Perl 5 path console error:”PLEASE SEE THE PERL2EXE USER MANUAL UNDER “Can’t locate somemodule.pm in @INC” Can’t locate attributes.pm”. To correct this set the Perl path by either doing a system command or by modifying the profile: PERL5LIB=/usr/lib/perl5/5.8; export PERL5LIB

Merge Report-IV to PDF with Dictionary-IV/OPENworkshop/Report-IV

The following applies to all operating systems.

The following is required when printing using T-Connect. This includes slave printing, Report-IV, and TS ReportServer. For more information, please see the T-Connect Web Terminal Reference Manual.

The following is required when using the 3GL wrapper with the exception of adding a DEV line to the IPLINPUT file and assigning it to the PDFCNV printer table. Defining the PDF converter as a printer device is only required to convert Report-IV output to PDF format.

Before starting the merge process make the necessary modifications to your IPLINPUT file.

On Windows Desktop and Servers, the IPLINPUT file is located in Thoroughbred common data directory. The default is C:\ProgramData\Thoroughbred Software\Tbsc.

On Linux, SCO, AIX, HP-UX, the IPLINPUT file is located in the Basic directory.

A hierarchical DEV line is required. Verify that the IPLINPUT file contains a DEV line with the hierflg set to 1. For example:

DEV D9,1,,,,1,,

Modify the IPLINPUT file adding a null DEV line for the Report-IV to PDF converter. For example, to define RC as the Report-IV to PDF converter device add the following to your IPLINPUT file:

DEV RC,4,,,1,,,/dev/null

or for window platforms:

DEV RC,4,,,,,,NULL

For more information see the Basic Customization and Tuning Guide (System Files).

Start Basic using the modified IPLINPUT file. From Basic console mode enter RUN “INSTALL”. This will install the Report-IV to PDF programs, Dictionary-IV definitions and the PDFCNV printer table.

When the Installation Complete screen is displayed press Enter to continue with the final phase of the install process. The Report-IV to PDF Settings and Options configuration screen is displayed. To skip configuring Report-IV to PDF, press F4. However, until Report-IV to PDF is properly configured it will not be able to locate certain directories and files and will report errors if you attempt to run the product. It is strongly recommended that you configure Report-IV to PDF at this point. For more information see Configure the Settings and Options section of this manual.

In order to select Report-IV to PDF as the printer device the PDFCNV printer table must first be assigned to a printer device. It is possible to have multiple printer devices configured for PDF; it is the PDFCNV printer table, not the printer ID that identifies a printer as a PDF output device. From the OPENworkshop System Administration menu, select Printer Assignment. Assign the printer table PDFCNV to the null printer device specified in your IPLINPUT file.

Using printer device RC as an example, when RC is selected for output from the Report-IV Select Printer prompt, the report will be converted and saved as a .pdf file.

From the Report-IV to PDF Installation and User Guide, version 8.9.1. Open this page in the PDF