Home The Company Publications Products Links Tips

PREDICT

Experiences With PREDICT Upgrade
From Version 3.4.2 to 4.3.2
In a NAT413 and ADA742 Environment

Last update: 31 March 2005

After I finished the upgrade from NAT232 to NAT413, I am in the process to upgrade PREDICT from version 3.4.2 to 4.3.2. To avoid problems, I created a new FDIC and started the installation.

  1. Read all Release Notes

  2. Unloaded/copied all files from cartridge to disk.

  3. Did a Consistency Check PRD342 / sysdic / menu / s / p / with update
    - Check database records
    - Check the extended descriptions
    - Conversion of EDIT MASKS in Field Entries
    - Check consistency of files and fields
    - Compress help texts after INPL
    - Check consistency of keywords
    - Check entries for programs
    - Conversion of free and automatic rules
    - Check verifications
    - Check Naming conventions
    - Check XREF data

  4. SAG recommended the following update plan
    To going directly from PRD342 to PRD422 is faster but you do the conversion work when you do a sysdicbe load. This is the draw back of this plan. You have to correct the error in the coordinator or source FDIC, then start the sysdicbe load again. Then do the same thing again at the next load error.
    (SAG didn't mention that you have to correct their errors!)
    Here is my baby steps upgrade plan:
    - Upgrade NAT232 to NAT316.
    - Apply zap NA46043 and NAT316 service pack 15 (NAT316I015).
    - Also upgrade Natural Security 232 to 316.
    - Do the PRD342 to PRD412 upgrade.
    - Most of the upgrade work is done in this step.
    - PRD41 is much different from PRD34.
    - Upgrade PRD412 to PRD422.
    - NAT413 requires ADA713, may have to upgrade ADABAS.
    - Upgrade NAT316 to NAT413.
    - Upgrade PRD422 to PRD432.
    - Apply service pack PRD432I004 (service pack 4)
    - The PRD412, to PRD422 to PRD432 upgrade will be very simple.
    - Predict has not changed much between PRD41 to PRD43
    - Basically you are upgrading with all of the fixes.

  5. Decided to go directly from PRD342 to PRD432
    Using FIRST-TIME installation, new FDIC, because I had good experience with NAT413 upgrade.

  6. PRDI050: ADALOD for new FDIC and new COORD
    - Using the coordinator file the first time

  7. PRDI060: Add Natural Parameters
    Updated and used member NATI0601 from NAT413 installation
    - DATSIZE=250 (at least)
    - SSIZE=64 (was)
    - RI=OFF
    - FDIC=(,109)

  8. PRDI061: Load programs (INPL) into FNAT
    - FNAT was also new when I started with NAT413

  9. PRDI100: Only instructions for COORD file

  10. PRDI200: Copy DDMs from old FDIC to new FDIC
    - SYSMAIN in batch
    - ASSIGN COORDINATOR DBNR=xxx FNR=yy UTILITY-CLEAR=Y
    - Prepare COORD file for NPR322 and ISP252 (not used)
    This was a big mistake. Shouldn't copy OLD SYSDIC* DDMs. Must generate DDMs from new Predict. Instructions didn't point this out.

  11. PRDI500: load DATA and DEMO

  12. Unload PRD342 data
    As recommended in the Technical Paper, upgrading from version 3.4 of Predict
    It is strongly recommended to unload the data in the source environment using Internal-ID=Y. I used their unload example:
    LOGON SYSDICBE
    MENU
    UNLOAD OBJECTTYPE ALL CODE=Y

  13. Load PRD342 data into PRD432
    It is impossible to load all old SAG files into the new version. I received tons of errors like this:
    (snip) 
    DIC1628 CHECKED WITH ERRORS KY SAG-PRD-DEPEND .                  
    DIC1754 CHECKING OBJECTTYPE: KY , OBJECT-ID: SAG-PRD-IMS .       
    DIC1635 OBJECT WITH THIS OBJECT ID, BUT DIFF. INTERNAL ID EXISTS. 
    (snip) 
    DIC1754 CHECKING OBJECTTYPE: FI , OBJECT-ID: SYSDIC-EL .         
    DIC1635 OBJECT WITH THIS OBJECT ID, BUT DIFF. INTERNAL ID EXISTS. 
    DIC1628 CHECKED WITH ERRORS FI SYSDIC-EL .                       
    DIC1754 CHECKING OBJECTTYPE: FI , OBJECT-ID: SYSDIC-FI .         
    DIC1635 OBJECT WITH THIS OBJECT ID, BUT DIFF. INTERNAL ID EXISTS. 
    (snip) 
    
    Only SAG objects failed:
    - SYSDIC*
    - SYSTEM*
    - VEHIC*
    - EMPL*
    - SAG-PRD*
    - and other SAG objects

  14. SAG Solution #1 (SAG request #569060):
    "The SAG information likely already exists because of the PRD43 install. You can remove these items from the coordinator if you are executing in batch you can logon SYSDIC then enter the command Coordinator this will take you to the coordinator file where you can fix the error, then resubmit the batch job with the continue command."

    "The SAG items should be able to be purged from the coordinator file, but you cannot use the P on the selection list you must select each item then go back to maintenance then purge, the reason is because of the workplan user id. Then go on with the CONTINUE. As for getting the load of the SAG files altered, I could create and Enhancement request that the load of the SAG files be enhanced, then if you let other customers know about the Enhancement they can add their vote to how high of a priority this is. You will be able to monitor the Enhancement on ServLine24."

    SAG recommended that I should manually select and purge all single SAG-PRD*, SYSTEM*, SYSDIC*, and other objects. And this can take days. I cannot believe that all customers have to clean up SAG objects. There must be an easier way.

  15. SAG Solution #2 (SAG request #569060):
    "Sorry I didn't realize there would be that many objects to delete ..... However, it is possible to delete all the SYSDIC and related SAG keys by purging the SYSDIC adabas file online you will be prompted, if it is ok do delete all field, view etc related to this file. So it can be removed from the Coordinator this way.
    .....I have tested the following and it will also work. I think your problem with the REPLACE = N is your unload used internal-id=Y. Here is what I test and worked.

    LOGON SYSDICBE
    MENU
    UNLOAD OBJECTTYPE ALL INTERNAL-ID=N
    FIN
    -----------------------------------------------------------
    LOGON SYSDICBE
    MENU
    LOAD OBJECTTYPE ALL REPLACE=N
    FIN

    Hmmmmmm... SAG's Technical Paper "Predict 4.3 - Important hint for upgrade from Predict 3.4 and 4.1" said: It is strongly recommended to unload the data in the source environment using Internal-ID=Y.

    This time, it passed the coordinator and conflict management test

    • Start of Transfer Coordinator FDIC at 12:11:01.0 on 2005-02-28
    • End of Transfer Coordinator FDIC at 14:28:59.2 on 2005-02-28
    • Start of Conflict management at 14:28:59.6 on 2005-02-28
    • End of Conflict management at 15:19:53.3 on 2005-02-28
    • Start of Check consistency at 15:19:53.4 on 2005-02-28
      Many errors, just an excerpt:
      (snip)
      DIC1613 OBJECT NAME CONTAINS DISALLOWED CHARACTER ' ' .
      DIC1628 CHECKED WITH ERRORS KY ANY REPLACEMENT .
      DIC1754 CHECKING OBJECTTYPE: KY , OBJECT-ID: BILL REFORMATTING .
      DIC1613 OBJECT NAME CONTAINS DISALLOWED CHARACTER ' ' .
      DIC1628 CHECKED WITH ERRORS KY BILL REFORMATTING .
      DIC1754 CHECKING OBJECTTYPE: KY , OBJECT-ID: TEAM TABLE MAINTENANCE .
      DIC1613 OBJECT NAME CONTAINS DISALLOWED CHARACTER ' ' .
      DIC1628 CHECKED WITH ERRORS KY TEAM TABLE MAINTENANCE .
      (snip)
      DIC2625 FORMAT NOT COMPATIBLE TO MASTER FIELD FORMAT 'B' .
      FIELD ID PERSONNEL-NUMBER .
      DIC1628 CHECKED WITH ERRORS FI FINANCE .
      (snip)
      DIC1783 DEVICE TYPE 9990 NOT DEFINED IN PREDICT .
      But it is defined in PRD342 - thought it would be migrated??
      (snip)
      End of Check consistency at 16:37:08.5 on 2005-02-28
      DIC1637 TRANSFER TERMINATED ABNORMALLY. ERROR DURING CHECK CONSISTENCY .
      NAT9987 Natural session terminated abnormally - RC=115.

  16. Decision to unload from PRD342 and load into a clean PRD432 environment.

  17. Cleaning the Coordinator File:
    Just describing different types of errors with one example

    • DIC1754 CHECKING OBJECTTYPE: FI , OBJECT-ID: FINANCE .
      DIC2625 FORMAT NOT COMPATIBLE TO MASTER FIELD FORMAT 'B' .
      FIELD ID PERSONNEL-NUMBER .
      DIC1628 CHECKED WITH ERRORS FI FINANCE .
      Old demo file, couldn't fix, so deleted from the coordinator

    • DIC1754 CHECKING OBJECTTYPE: FI , OBJECT-ID: FINANCE .
      DIC1754 CHECKING OBJECTTYPE: FI , OBJECT-ID: ADABAS.**.ASSO1 .
      DIC1613 OBJECT NAME CONTAINS DISALLOWED CHARACTER '*' .
      DIC1628 CHECKED WITH ERRORS FI ADABAS.**.ASSO1 .
      Was possible under PRD342, replaced by '-' in coordinator

    • DIC1754 CHECKING OBJECTTYPE: FI , OBJECT-ID: PERSONNEL .
      DIC2625 FORMAT NOT COMPATIBLE TO MASTER FIELD FORMAT 'B'
      FIELD ID PERSONNEL-NUMBER .
      DIC1628 CHECKED WITH ERRORS FI PERSONNEL .
      No error under PRD342, couldn't fix, so deleted from coordinator

    • DIC1754 CHECKING OBJECTTYPE: FI , OBJECT-ID: CHANGE-Z .
      DIC1613 OBJECT NAME CONTAINS DISALLOWED CHARACTER ' ' .
      FIELD ID RELEASE 3A .
      DIC1628 CHECKED WITH ERRORS FI CHANGE-Z .
      No error under PRD342, updated ' ' with '-' in coordinator

    • DIC1754 CHECKING OBJECTTYPE: FI , OBJECT-ID: RELEASE-1B-Z .
      DIC2949 NO OCCURRENCES ALLOWED.
      FIELD ID DOC-TYPE-BATCH-SEQ .
      DIC1628 CHECKED WITH ERRORS FI RELEASE-1B-Z .
      No error under PRD342, deleted occurence 3 in coordinator

    • DIC1754 CHECKING OBJECTTYPE: FI , OBJECT-ID: WKB-TROUBLE-LOG .
      DIC2718 DEFINITION FOR DESCRIPTOR/INDEX MISSING.
      FIELD ID KEY-TYPE-PROD-AREA-ABEND-LOG .
      DIC1628 CHECKED WITH ERRORS FI WKB-TROUBLE-LOG .
      No error under PRD342, couldn't fix, deleted from coordinator

    • DIC1754 CHECKING OBJECTTYPE: FI , OBJECT-ID: CONFIRMATION-STATISTICS .
      DIC2515 INVALID FIELD TYPE .
      FIELD ID HDR/PROCG-CDE/DIV/SOLN/PGM-NBR .
      DIC1628 CHECKED WITH ERRORS FI CONFIRMATION-STATISTICS .
      No error under PRD342, couldn't fix name of SP, deleted from coordinator

    • DIC1754 CHECKING OBJECTTYPE: PR , OBJECT-ID: ICIS3151 .
      DIC2515 INVALID LANGUAGE .
      DIC1628 CHECKED WITH ERRORS PR ICIS3151 .
      Language was set in PRD342, was not unloaded, inserted 'J' for jobs in field language in coordinator

    • DIC2519 METADATA WITH INTERNAL CODE: DOES NOT EXIST.
      DIC1628 CHECKED WITH ERRORS ADATEST .
      UDEs were unloaded from PRD342, but there is no way to fix it in the coordinator
      SAG request #569060

  18. UDEs cannot be cleaned easily from the Coordinator File:
    Development has provided a small program, which will remove the metadata with internal code that does not exist (DIC2519 error).

    • Logon to Natural with FDIC assigned to the coordinator file (very important). This is a dynamic override FDIC=(coordinatorDB,coordinatorFILE).

    • Copy DDM SYSDIC from FDIC Predict to COORDINATOR

    • Enter the following program (it's Reporting Mode!)
      R. FIND SYSDIC WITH EXTRACT = '#SAG-TRANSFER'-H'00'
                               THRU '#SAG-TRANSFER'-H'FF'
        IF RECORD-TYPE(R.) = ' '
          DO
          D. GET SYSDIC *ISN(R.)
          DELETE (D.)
          END TRANSACTION
          PRINT SYSTEM-NAME(R.) 'deleted'
          DOEND
        ELSE
          PRINT RECORD-TYPE SYSTEM-NAME(R.) 'OK'
      END
      

    • After the UDEs with errors are deleted, restart the batch job with the CONTINUE command to complete the LOAD.
      LOGON SYSDICBE 
      MENU           
      CONTINUE       
      FIN    
      
      Output:
      ---------------------------------------------------------
      Start of Conflict management at 15:23:52.9 on 2005-03-10 
      ---------------------------------------------------------
      (snip)
      -------------------------------------------------------
      End   of Conflict management at 15:39:16.8 on 2005-03-10 
      -------------------------------------------------------
      -------------------------------------------------------
      Start of Check consistency   at 15:39:16.9 on 2005-03-10 
      -------------------------------------------------------
      (snip)
      -------------------------------------------------------
      End   of Check consistency   at 16:35:32.6 on 2005-03-10   
      -------------------------------------------------------
      -------------------------------------------------------
      Start of Transfer Main FDIC  at 16:35:43.5 on 2005-03-10
      -------------------------------------------------------
      (snip)
      -----------------------------------------------------
      End   of Transfer Main FDIC  at 16:54:56.4 on 2005-03-10
      -----------------------------------------------------
      DIC1654 LOAD TERMINATED SUCCESSFULLY.                        
      

  19. SAG will change their installation procedure.
    Unload and load of UDEs must be done before other unloads
    Closed SAG request #569060

  20. U-SEC Exit
    After logon sysdic, a security display pops up. It looks like a display that was forgotten to remove.
    Solution:
    • Go to Defaults / General Defaults / Protection
      Set the Protect File to N and enter the DBID and NSC FNR.
    • Go to Special Function option N and set the defaults
    • Go back and set the Protect Predict file to Y
....... to be continued ......