II09701: NCP PRODUCTS YEAR 2000 READY. YR2000 Y2K YEAR2000 YR2K

APAR status

• Closed as canceled.

Error description

• This informational APAR has been written to document YEAR 2000
  READINESS for all of the NCP Products (NCP, SSP, NtuneMON, EP,
  NRF, NTO, NPSI, NSF, XI, ALCI, NEF and NSI).
  
  (NtuneMON, EP, NRF, NTO, NPSI, NSF, XI, ALCI, NEF and NSI have
   NO Y2K problems and no further actions are required.)
  
  For NCP and SSP problems, refer to the following list for
  APARs or circumventions.  (Note,  if the problem is applicable
  to your release but there is no APAR shown, the circumvention
  under the 'Action required' may be used.)
  
  For an overview of the YEAR 2000 analysis of the product set
  please see APAR II11977
  
                                    LAST REVISION - 9/27/1999
  NCP considerations:
  -----------------------------------------------------------
  
  * Leap year was not considered when using NPM session
    accounting data collection
    - Description of problem:
      - NPM session accounting data session start and session
        end dates recorded on February 29th and later within
        a leap year are incorrectly recorded as one calendar
        day later than the actual date.
    - Affected users:
      - NCP V4R3, V4R3.1 and V5R2 through V7R5. Problem is
        fixed in base of V7R6 and later.
    - APARs available -
      - V4R3.1      - IR34194
      - V5R4        - IR34196
      - V6R2 (VM)   - IR34197
      - V6R3 (MVS)  - IR34197
      - V7          - IR34198
  
    - Action required when an APAR is not available
      - Alter applications which process session accounting
        data to recognize the error in the data
      - Migrate to latest level of NCP
  
  * Incorrect 4 digit year calculated
    - Description of problem:
     - When an NCP is activated with a date before the turn
       of the century and the generation date is after the
       turn of the century, an incorrect decade is calculated.
       The problem could occur when a user generates NCP in a
       time zone which is in the new century, but then
       activates NCP from a time zone which is not yet in the
       new century.
    - Affected users:
      - NCP V7R7 only (problem is fixed in base of V7R8).
    - APARs available -
      - NCP V7R7 - IR40823 (MVS,VM), IR40824 (VSE)
  
  SSP considerations:
  --------------------------------------------------------
  
  * ACF/TAP does not format date 12/31/99 correctly.
   - Description of problem:
     - ACF/TAP formats the date for 12.31.99
       as 01.00.00. This is incorrect.
   - Affected users:
     - All releases of SSP prior to V4R7.
         (Problem is fixed in base of V4R7 and later.)
   - APARs available:
     - SSP V3R9                (MVS) IR38702
     - SSP V4R1 and V4R2       (MVS) IR40337
     - SSP V4R1 and V4R3       (VM)  IR40338
     - SSP V4R1                (VSE) IR40339
     - SSP V4R3                (MVS) IR39851
     - SSP V4R4, V4R5 and V4R6 (MVS) IR37655
     -  "   "     "        "   (VM)  IR37726
     -  "   "     "        "   (VSE) IR37727
  
   - Action required when an APAR is not available
     - Problem is cosmetic only and will not cause any
       failures.  Formatted trace data will be correct.
  
  * ACF/TAP does not detect Feb 29, 2000 date correctly.
   - Description of problem:
     - On all ACF/TAP reports generated on
       FEBRUARY 29,2000 (02.29.00) the date is
       incorrect. The date printed on the
       reports is MARCH 1,2000 (03.01.00).
   - Affected users:
     - All releases of SSP prior to V4R7.
         (The problem is fixed in base V4R7.)
   - APARs available:
     - SSP V3R9                (MVS) IR38702
     - SSP V4R1 and V4R2       (MVS) IR40337
     - SSP V4R1 and V4R3       (VM)  IR40338
     - SSP V4R1                (VSE) IR40339
     - SSP V4R3                (MVS) IR39851
     - SSP V4R4, V4R5 and V4R6 (MVS) IR38074
     - SSP  "     "        "   (VM)  IR38270
     - SSP  "     "        "   (VSE) IR38271
  
   - Action required when an APAR is not available
     - Problem is cosmetic only and will not cause any
       failures.  Formatted trace data will be correct.
  
  * ACF/TAP - Incorporate YEAR 2000 parameters into ACF/TAP.
    - Description of problem:
      - Two-digit year processing could produce
        undesirable results for trace data that includes
        trace records spanning from 1999 to 2000 because ACF/TAP
        would consider the trace records produced in 2000 to be
        older than the trace records produced in 1999.
    - Affected users:
      - All releases of SSP prior to V4R7.
           (The problem is fixed in base V4R7.)
    - APARs available:
     - SSP V4R5 and V4R6 (MVS) IR38411 and PE APAR IR38907
     - SSP V4R5 and V4R6 (VM)  IR38472 and PE APAR IR39167
     - SSP V4R5 and V4R6 (VSE) IR38473 and PE APAR IR39168
  
     The problem is fixed in base V4R7.
  
   - Action required when an APAR is not available
     - The situation is simply remedied by running ACF/TAP
       twice where the pre-2000 entries are selected in the
       first pass and the 2000+ entries are selected in the
       2nd pass.
  
  * LOADER calculates incorrect year
    - Description of problem:
      - When an NCP is loaded on a date before the turn
        of the decade and the generation date is after the
        turn of the decade, an incorrect decade is calculated.
        The problem could occur when a user generates NCP in a
        time zone which is in the new decade, but then loads
        the NCP from a time zone which is not yet in the new
        decade.
    - Affected users:
      - All MVS and VM releases of SSP through V4R7.
        (This problem does NOT affect VSE releases!)
        (The problem is fixed in base V4R8.)
    - APARs available:
      - SSP V4R1,R2,R3,R4,R5,R6 and R7 (MVS) IR40968
      - SSP V4R1,R3,R4,R5,R6 and R7    (VM)  IR41017
      - SSP V3R8                       (VM)  IR41148
      - SSP V3R9                       (MVS) IR41147
  
    - Action required when an APAR is not available
      - Problem is cosmetic only and will not cause any
        failures. The incorrect date will appear as the NCP GEN
        date on the MOSS console and in Genric Alerts built by
        that NCP. Users should synchronize clocks when
        generating and loading from different host machines.
  
  -------   End of Product Considerations   ------------------
  
  Revision History:
   7/29/99 - Added note regarding SSP V3 APARS for loader prob. EB
   7/28/99 - Added problems described by NCP APARs IR40823 and
     IR40824 and SSP problems described by SSP APARs IR40968,
     IR41017 and IR41018.
     Removed NCP Analysis overview and restructured APAR
     contents.
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• This apar is being closed for RETENTION.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels