We've been holding back this release in favor of more immediate activities
such as MRK followups because the majority of the changes will have no
impact on our sites.  The primary purpose of r1649 is to remove the limit
(four) on number of sub-locations, however there are some incidental side
effects on programs used for web merit processing.  Our sites do not use
the sub-location feature, and I believe only UCLA does.

- The list of valid sub-location codes for a site will now be stored
    in copymember CPWSXIDC.  The corresponding descriptions
    will be taken from the Code Translation Table.

- A long list of programs edits sub-location values in TCT
   transactions against hard-coded lists of legal values .  These
   programs are modified to instead call new program PPSUBLED
   which will perform a comparison against the values in CPWSXIDC
   and return a valid or not valid status.

- The PPTCTUTL title code utility program has in the past fetched
   values for four sub-location codes but now is modified to look up
   just one value per call.  There is also an error fix that will ensure
   that when a sub-loc is not found, it will default to 'GN' or '**'.
   Batch programs PPP675 and PPP676 which are used in support of
   web merit processing call PPTCTUTL and previously contained logic
   to supports the sets of four sub-locs.  R1649 rewrites the logic
   related to PPTCTUTL calls.

   Because PPP675 and PPP676 were being modified anyway,
   Base included additional changes unrelated to sub-locs for which
   I had filed error reports.  Report id's are corrected, and failed runs
   will roll back changes to merit cycle status codes.

- Several programs used to read the CCR record to determine the
   site.  If it was UCLA, 'EA' was substituted for 'AG' as a legal
   sub-loc value.  This code has now been removed because
   site-specific values can be coded in CPWSXIDC.  Among these
   programs are two stored procedure programs, PPTCTSP2 and
   PPTCTSP5.  Their only DB2 activity was the the fetch of the CCR
   record, so all support for DB2 has been removed as well.

There are no table updates for this release.  (CTT descriptions
of sub-location values already exist.)

May we have your ok to install in production?

   bvb