Release 1506 issues a one-time program similar to the one in r1355,
issued two years ago.  Because the intent of the program is to
determine eligibility and calculate across-the-board pay increases for
open-range employees in the RX unit, this release can be skipped for
ASUCLA and Hastings.

One-time program PPOT1506 is similar to program PPP910, even using
PPP910 spec cards, and operates much like a conventional range adjustment
process.  Differences are:

- Eligibility criteria based on the collective bargaining agreement.  See the
   release documents for specifics.

- TCS will not provide a payscale file.  Instead I'll manufacture a dummy
   payscale file containing only a header.  The effective date is 10/01/02,
   and for Davis, the header will also identify a biweekly effective date of
   09/29/02.

- The one-time program is intended to be run in only PRLM1 and FINAL
   modes.

- The costing transactions that are generated will have an action code of
   '43' instead of the usual '28'.  Note that none of our campuses have
   entries for '43' in their costing tables, so if you wish to cost these pay
   increases, you'll need to update your tables.  (That need not happen at
   the same time as release installation and running of PPOT1506.)
   An alternative would be to have us modify the program to assign a
   different action code.

The release installation document includes a section that describes how
the retro process for RX open range employees is to be run.  A key point
is that even though there will be only one step/sequence, it must be run as
a 'multi' process.  Additionally, when running program PPP684 (job PP*RRA),
error code overrides must be specified.  Information about the meaning of the
various error codes is given in the release letter.

IMPLEMENTATION

First, we'll need your approval to install the release.  Additionally, we'd
appreciate it if you would let us know:

- Dates when you'd like us to run the PRLM1 and FINAL phases of
   program PPOT1506.  I suggest that they be on different dates, so
   we don't run into problems with report files being overlaid.
- Your instructions regarding the costing action code.
- When you would like us to process the generated EDB file maintenance
   and costing transactions.
- The timeframe in which you anticipate having us run the retro process.
- The retro error code override values.
- Your target for retro payments.

Thanks!

   bvb