Release 1538 responds to an error report from Berkeley about a DB2 abend
occurring in the nightly IVR/web update, specifically an attempt to insert a
record into the FCB table having the same employee id number, benefit type,
and effective date as a record that already exists.  This has bitten us several
times, also.  Per the release letter:

   It has been determined that this case can result from a situation where the
   system assigns a new Period of Initial Eligibility (PIE) End Date, but does
   not perform the appropriate default enrollments for a rehire.  This occurs
   when a rehire is processed and the Assigned BELI (EDB 0360) and BELI
   Effective Date (EDB 0341) are not changed.  For example, if a BELI '1'
   employee is separated, and a subsequent rehire is processed before
   monthly maintenance sets the BELI to '?', the Assigned BELI would not
   be changed if the new position is also eligible for BELI '1'.

One program is modified: PPEC102.  "If the employee is a rehire and the
BELI IND (EDB 0360) has not been explicitly changed, the Hire Date
(EDB 0113) is moved to the BELI Effective Date (EDB 0341)."  The
BELI Effective Date becomes the Coverage Effective Date for the
FCB table and does not duplicate the previous Effective Date, thus
preventing the DB2 error.

The Processing Group table (table 36) is modified to trigger execution
of PPEC102 for program id's 08 and 12 when the action is a rehire (02).
An interesting note is that although PPEC102 is specific to medical
insurance, triggering it will cause the corresponding dental, vision, and
legal edit programs to be triggered as well.

A series of possible scenarios is described in detail in the release letter.

Although marked as "not urgent", it would be advantageous to install
r1538 soon, to protect the nightly IVR/web update from the possibility
of an abend.  Ok to proceed?

   bvb