Release 2089
Service Request 100231
Health Savings Account
Installation Instructions
November 26, 2013
Prepared by Gerry Mulligan
Information Technology Services
Office of the President
University of California
This document provides installation instructions for release 2089. Please review these instructions carefully before
proceeding with the installation.
1.
DB2 Installation
This portion of the installation creates DB2 objects.
1.1
Modify DB2 objects:
o
Drop view PPPV400A_BEN, then recreate it by executing the following DDL member:
•
PPPV400A (adds field PPPBEN.EMP_HLTH_COVEFFDT to view PPPV400A_BEN)
2.
Include Member Installation
2.1
Install the following modified include member:
Include Members
PPPV400A
Installed?
3.
Copylib Member Installation
3.1
Install the following modified copy member:
Copylib Members
CPWSXEST
4.
Installed?
COBOL Program Preparation
At UCOP, all COBOL programs pass through the DB2 pre-compiler, whether or not the program contains
embedded SQL, to resolve INCLUDE references. Your site may have different requirements.
The “SPAS” designation indicates that a module needs to be compiled and linked into the appropriate SPAS loadlib.
If only “SPAS” is indicated in the Compile column, then the module is either a called procedure, or only called by a
stored procedure. The SPAS package bind differs from that used for CICS dual-use binds. If the SPAS application is
running, a STOP and START PROCEDURE is required to install the new version.
"DUAL" programs must be compiled twice and linked into batch and online libraries ("LOADLIB" and
"OLOADLIB" respectively). "CICS" programs must be CICS pre-compiled and compiled once and linked into
OLOADLIB. "BATCH" programs must be compiled once and linked into the batch LOADLIB only.
4.1
Install, compile, and link the following new program:
PROGRAM
PPP494
4.2
DB2?
Y
Compile Type
Batch
Done?
Install, compile, and link the following modified programs:
PROGRAM
PPESTEDB
DB2?
Y
Compile Type
Batch
Done?
Page 2
PPFCBBEN
PPNETCLC
Y
Y
Dual
Dual
4.3 Compile and link the following unmodified programs:
PROGRAM
PPP400
PPNETDTK
PPNETUPD
PPRCADVC
PPRCMDL2
PPRCNET
PPWRCO2
DB2?
Y
Y
Y
Y
Y
Y
Y
Compile Type
Batch
Dual
Dual
CICS
CICS
Dual
CICS
Done?
5. JCL
5.1 A sample JCL and Proc have been provided with the release, to be customized locally.
Typically each compute has a series of jobs (A-M). Please modify compute job "M", adding a new step to
execute PPSHSAP. PPSHSAP should execute last (after all other non-backup steps).
JCL member PPSHSAJ1 can be used as a reference but is not intended to be installed; only the Proc (PPSHSAP)
should be installed.
JCL - PPSHSAJ1
Proc - PPSHSAP
5.2 Create a new proc for the new program listed below. The sample proc PPSHSAP can be used as a model to
create the production proc.
Program
PPP494
Sample Proc
PPSHSAP
Installed?
Important Notes:

PPP494 must run after every compute and must use as its input the PAR file produced by that
compute.

PPSHSAP produces intermediate files and a PIN interface file. These should have the following
naming conventions:
. Intermediate Files:
PPX.PPP4941.HSA.ACTV.PAYTYPE.RMMMYY,
PPX.PPP4942.HSA.WARNRPT.PAYTYPE.RMMMYY, where X=
X
1
3
5
6
7
8
Campus
Berkeley
Davis
Riverside
San Diego
Santa Cruz
Santa Barbara
Page 3
9
10
and
Irvine
Merced
PAYTYPE = B1, MO, etc.
MMM
= Month for which the job was run
YY
= Year for which the job was run
e.g., if the PAR file was for Feb 2014, the MMMYY portion of the file name should have
FEB14.
. PIN Interface File: PIN.PPP4941.HSA.ACTVALL(+1)

For Hosted campuses: Please name the new files as shown above.

For non-Hosted campuses: Please send the new HSA file to vsftp as:
/ftphome/ftpusr<loc>/put/hsa/HSAACTV.paytype.Emmddyy
`
Where <loc>
= campus
<loc>
lb
2
4
Campus
LBNL
San Francisco
UCLA
paytype
= B1, MO, etc.
Emmddyy = checkdate
6. Testing
6.1
Perform installation verification testing as described in the release letter. In addition, perform any further
local testing.
7. Install in Production
7.1 Place modified objects in production.
8. Control Table Updates
8.1 Execute PPP004 to update the following DB2 CTL tables with release transactions.
o
Gross to Net Table (02)
- Use the transactions in CARDLIB (GTNPROD)
Local GTN Priority Numbers must be assigned in place of the ???? in columns 4 through 7. The
priority numbers should be *after* the medical plan and FSA GTNs and *before* the OASDI and
Page 4
Medicare GTNs.
o
Code Translation Table (38)
- Use the transactions in CARDLIB (CTTPROD)
o
System Messages Table (08)
- Use the transactions in CARDLIB (MSGPROD)
Page 5