BUSINESS SOFTWARE, INC. (BSI) CONFIDENTIAL AND PROPRIETARY INFORMATION

OS/390

The TaxFactory server consists of a link library made of several C object modules based upon the features you have purchased. To calculate taxes, connect this link library with your payroll program and call the appropriate TaxFactory API.

The OS/390 version of TaxFactory uses IBM DB2 release 5.1 or higher as its database, and is compatible with OS/390 R2.6 or higher. The link library is compiled to be 31-bit RMODE=ANY compatible.

Installing the OS/390 Server

The OS/390 media package contains several transmitted data sets in the /server directory.

They are:

BSI.TF10x.DBRM	SQL Packages for binding to DB2
BSI.TF10x.H	TaxFactory API files
BSI.TF10x.JCL	Sample program JCL and DB2 Binding JCL
BSI.TF10x.OBJ	TaxFactory Server Link Library
BSI.TF10x.LOAD	TaxFactory Load Modules
BSI.TF10x.SAMPLE	TaxFactory Sample Programs
BSI.TF10x.SQL	TaxFactory DB2 Creation SQL
BSI.TF10x.CBL	COBOL Copybook/API
BSI.ZLIB.LIB	Compression Library
BSI.EXPAT.LIB	XML Library

Transferring Server Files to the OS/390

The following steps will assist you in transferring the BSI.TF10X.* transmitted files from the TaxFactory server directory into target data sets on OS/390. This is a two stage process: The first stage involves utilizing FTP to transfer the server files from your PC to temporary data sets on OS/390. The second stage involves expanding the transmitted files into their final target data sets.

Create a temporary OS/390 data set. To transfer the server files to OS/390, you must create target data set 'TF.XFER' on OS/390. Follow the normal procedures to create this data set (i.e. use 3.2 from the ISPF Primary Option Menu to get to the Data Set Utility, and use Allocate). The target sequential data set MUST be RECFM=FB (Fixed Block), and LRECL=80 (Record Length). BSI usually uses a Block Size of 3120, BLKSIZE=3120.
PC to OS/390. From the PC, use FTP to transfer a single server file to the OS/390 temporary data set as binary data. An example of the FTP commands are shown below.

ftp <name of your OS/390 system>

user <OS/390 userid> <OS/390 password>

binary

put bsi.tf10a.cbl 'TF.XFER' (replace

bye

Receive the transmitted file. From an OS/390 TSO command prompt, use the "receive" command to expand the transmitted file into the final data set. An example session is shown below.

receive indsname('TF.XFER')

Note: This will produce output such as:

INMR101I data set BSI.TF10A.CBL from P390 on NODENAME

INMR106A Enter restore parameters or 'DELETE' or 'END' +

Hit Enter to continue with the expansion, and you should see several lines of output, including the line:

IEB147I END OF JOB - 0 WAS HIGHEST SEVERITY CODE

Repeat steps 2 and 3 for the remaining server files.
Delete temporary data set. Follow the normal OS/390 procedures to remove the temporary data set (i.e. use 3.2) from the ISPF Primary Option Menu to get to the Data Set Utility, and use Delete.

To Create TaxFactory Tables on the DB2 Database:

The OS/390 DB2 DBA should review BSI.TF10x.SQL(TF10MVS) for the storage group, bufferpool, and user permissions assignments to create the TaxFactory 1.0 DB2 database. Following creation of the TF10 database using SPUFI, the BSI.TF10x.SQL(TF10MVS) script should be executed through SPUFI to create the TaxFactory 1.0 tables.

To Bind the OS/390 DB2 Database:

The site DBA should review and amend BSI.TF10x.JCL(BINDTSO) with respect to site database security policy. When completed, this job should be executed to bind the OS/390 DB2 database and make it addressable to the TaxFactory server and site user community.

For clients using the Resource Recovery Services Attach Facility:

To Populate the TaxFactory Tables on the DB2 Database:

There are two methods available to load data into the TaxFactory tables:

Using ODBC from the PC
Using an OS/390 load program

All sequential files and download instructions are located on the BSI web site.

Method A: ODBC Load

Population of the TaxFactory database via an ODBC connection from the Windows client is documented in the user documentation under the Tech Tools, Database Load section.

Note: When configuring the ODBC connection from Windows to the OS/390, the connection type will be required to be 'DRDA'. The OS/390 database name will be required during configuration. More information regarding IBM DB2/Connect DRDA configuration can be found in the IBM documentation shipped with the DB2/Connect ODBC drivers.

Method B: OS/390 Load

Another method that can be used to populate the TaxFactory database on OS/390 is a load program executed on the server. To use the server program, you must first transfer the desired data file from your PC to OS/390. This can be done using binary FTP into a data set on OS/390.

Create an OS/390 data set. To transfer the sequential files to OS/390, you must create a single file (non-partitioned data set) TF10.XML OS/390. Follow the normal OS/390 procedures to create this data set. The target data set MUST be RECFM=VB (Variable Block), and LRECL=256 (Record Length). The system should default the variable block size to 16640. The storage requirements for this dataset will change as more data is added to TaxFactory . A minimum of 16 megabytes should be allocated to hold the TaxMaster and TaxLocator sequential files.
The initial Tax Master and TaxLocator sequential files downloaded from the web will be named tfuvvnnn.pkg, where vv is the release version, and nnn is the bulletin level. Transfer this file to OS/390. (Ex. tfu01031.pkg becomes TF10.XML).

From the PC, use FTP to transfer the data file to the OS/390 PDS as binary data. An example of the FTP commands are shown below:

ftp <name of your OS/390 system>

user <OS/390 userid> <OS/390 password>

binary

put tfu01031.pkg 'TF10.XML' (replace

bye

Once these sequential files are in place, use the JCL member BSI.TF10x.JCL(TFLOADER) to load the data.

Note: You may need to edit the TFLOADER JCL for the dataset name and the applicable sequential file names. The TFLOADER JCL can also be edited to provide the desired options to the TFLOADER program; see Alternate Save/Restore Database loading process for a review of the TFLoader syntax. An example of this follows

//LD    EXEC PGM=TFLOADER,
//   PARM=('ENVAR("TF10_DATASET=DEFAULT",',
//       '"TF10_DATABASE=;;;DSN2;TF100;;C")',
//         '/-z -v DD:XX')                     <<==
//STEPLIB DD DSN=BSI.TF10.LOAD,DISP=SHR
//XX       DD DSN=TF10.XML,DISP=SHR,RECFM=VB, <<==
//            LRECL=256,BLKSIZE=16640
//SYSPRINT DD SYSOUT=*
//SYSOUT   DD SYSOUT=*

To Execute the Statically Linked Sample Program Provided:

BSI.TF10x.JCL(CCSAMPLE) contains the JCL required to compile, prelink, and linkedit a C sample program. The sample program creates a load member BSI.TF10x.LOAD(TFSAMPLE) that can be executed under the CAF environment. To execute the sample, submit job BSI.TF10x.JCL(RCSAMPLE). The sample program should yield various tax calculation and tax location outputs.

BSI.TF10x.JCL(CCBLCAF) contains the JCL required to compile, prelink, and linkedit a COBOL sample program. The sample program creates a load member BSI.TF10x.LOAD(CAFSMPL) that can be executed under the CAF environment. To execute the sample, submit job BSI.TF10x.JCL(RCBLCAF).The sample program should yield various tax calculation and tax location outputs.

Note: Edit the sample program to modify the connection string used on the database connect. This string will be specific to your DB2 environment. See the Connect to Database/Dataset section for the syntax.

To Link the TaxFactory Library, perform the following steps:

Step 1 -- Include BSI Header Files/Copybooks

Step 2 -- Linking TaxFactory Library to your Payroll System

Step 3 -- Connect to the Database/data set

Step 4a -- Call the Calculation Function

Step 4b -- Call the Import Function

Step 4c -- Call the Pension Calculation Function

Step 4d -- Call the Pension Import Function

Step 4e -- Call the Locator Function

Step 5 -- Disconnect from the Database