Release 1527 modifies a single program, PPP330, in connection with
'final pay' processing.  We're not yet running 'final pay' computes, but
will no doubt run them eventually for all sites, some sooner than others.

PPP330 is executed each evening, after CICS comes down, for sites
using online time rosters, which is all of our sites except Santa Cruz
and ASUCLA.  (It will be required for 'final pay' processing, even if
online rosters aren't used for normal pay.)  Its purpose is to update
online time rosters to reflect changes in the EDB, and it was enhanced
in r1492 to support 'final pay' computes.

The modifications in r1492 were intended to work in such a way
that if a separating employee's employment were extended, he would
be dropped from the YX roster and be added to a regular roster.
To accomplish that, the 'final pay' roster must be processed first.

As originally implemented, the sequence in which compute rosters are
processed was determined by sorting Payroll Process Id (PPI) values
in descending order.  However, PPI values are simply labels and totally
dependent on local naming conventions, thus sorting on PPI results
in the correct sequence at some sites and not at others.  R1527 modifies
PPP330 to rely on the pay cycle id (MO, B1, YX, etc.) from the TTC table
rather than PPI, as a surefire way to ensure that YX's go first.  It's a
one line program change.

There are no table updates.

May we have your ok to install r1527?

   bvb