Release 1650 may clear up a small PPS mystery that I believe
has popped up from time to time on an anecdotal basis,
specifically that there are occasions when, even though a reject
error message is issued, an EDB update is not blocked.

The problem occurs in batch only, and therefore is most likely to
affect the Davis Medical Center and ASUCLA.

EDB editing and updating is performed in two phases, sometimes
referred to as '08' and '12', and one of the distinctions between them
is that - usually - consistency edits are performed by the first, '08',
phase, and implied maintenance is performed by the second, '12',
phase.  That's not an absolute requirement, and in fact, the problem
occurs when implied maintenance is performed by batch program
PPP080 and the only rejects are from implied maintenance.  In this
release, PPP080 is modified to 'examine Implied Maintenance
Trigger switches for failure indication in the same manner as that
of Consistency Edit Trigger switches.'

TABLE UPDATES
   Five new messages comparable to the existing conedit failure
messages are added for PPP080 rejects from called implied
maintenance programs PPEI125, PPEI204, PPEI205, PPEI340,
and PPEI505.  For example:  IMPLIED MAINT EDIT 125 FAILED

Ok to install?

   bvb