HP 3000 Manuals

FIX PATH [ DBChange Plus User's Guide ] MPE/iX 5.0 Documentation


DBChange Plus User's Guide

FIX PATH 

Examines paths for broken chains and incorrect pointer linkages and
attempts to correct known problems.

Syntax 

             {@                                    }
F[IX] PAT[H] {MasterDataSetName                    }
             {DetailDataSetName {( @ )            }}
             {                  {(SearchItemName) }}

Parameters 

@                   indicates that all paths in all data sets in the
                    database should be examined and corrected.

MasterDataSetName   is the name of the master data set whose synonym
                    chains should be examined and corrected.

DetailDataSetName   is the name of the detail data set whose paths should
                    be examined and corrected.  DetailDataSetName can be
                    specified as follows:

                    (@)                 indicates that all paths in the
                                        detail data set should be
                                        examined and corrected.

                    (SearchItemName)    is the name of the search item
                                        defining the path to be examined
                                        and corrected.

Description 


NOTE Before using the FIX PATH command, read chapter 8, "Maintaining the Database."
Use this command to examine and correct broken chain and data set structural inconsistencies, such as user label, bit map, and delete chain problems. When used to examine a master data set, FIX PATH checks and attempts to fix the synonym chain pointers in the master data set. When used to examine a detail data set, FIX PATH checks and attempts to fix the path chain pointers in the detail data set and its associated master set(s). The database fixing process begins only after you issue a PERFORM COMMANDS. The FIX PATH command requires exclusive access to the database. Example In the example below, the FIX PATH command is used to fix all paths in all data sets in the ORDERS database. A description of the command output follows the example. >base orders >fix path @ FIX PATH issued for 5 set(s). >perform commands PERFORM COMMANDS now or create job file [job/y/N]? y Please wait ... HP36386 (A.00.00) DBALTER (c) COPYRIGHT Hewlett-Packard Co. 1985 FRI, MAY 25, 1990, 3:13 PM Database has been modified since last DBSTORE (DBA 220). Continue [y/N] ? y Starting data set serial reads. ..... Tabulating statistics. CHECK PATH Pct Set Name Type Max Avg Std Far Avg Packing Search Item (PS) Chain Chain Dev Ptrs Blocks Ratio ---------------------------------------------------------------------- CUSTOMER M SYNONYM CHAINS 1 1.00 0.00 0 1.00 N/A PRODUCT M SYNONYM CHAINS 2 1.07 0.25 0 1.00 N/A SALES D ACCOUNT ( S) 17231 2874.67 7033.14 6 1.17 6.86 STOCK# (P ) 5 2.13 1.64 6 1.13 0.89 SUP-MASTER M SYNONYM CHAINS 1 1.00 0.00 0 1.00 N/A INVENTORY D STOCK# 1 1.00 0.00 0 1.00 1.00 SUPPLIER (P ) 5 5.00 0.00 0 1.00 1.00 Starting data set chained reads. ... CHECK INFORMATION Set Name Type Search Item Message(s) ------------------------------------------------------------------------ CUSTOMER M Userlabel entry count does not match synonym chain count (CHK 570). Record 6 is not linked into the proper synonym chain (CHK 360). SALES D ACCOUNT (Path 1; linked to master CUSTOMER, path 1) Path Chain inconsistencies detected (CHK 400). Sum of chain counts in the related master set does not match bitmap entry count for this set (CHK 580). Chainhead record 113 chain count mismatches entries on chain (CHK 450). Record 3 contains bad backward pointer (CHK 440). Record 14 contains bad backward pointer (CHK 440). Record 15 is not linked into the proper chain (CHK 460). Record 16 contains bad forward pointer (CHK 430). STOCK# (Path 2; linked to master PRODUCT, path 1) Path Chain inconsistencies detected (CHK 400). Chainhead record 267 contains bad forward pointer (CHK 410). Chainhead record 267 contains bad backward pointer (CHK 420). Chainhead record 267 chain count mismatches entries on chain (CHK 450). Record 15 is not linked into the proper chain (CHK 460). FIX INFORMATION ------------------------------------------------------------------------ New Key value added for dataset CUSTOMER (FIX 170). Key value: INTEGER(I4/J4)=>> 1482184792 / 1482184792 New Key value added for dataset PRODUCT (FIX 170). Key value: ASCII( 8)==>> XXXXXXXX All problems detected have been fixed. HP36386 (A.00.00) DBCHANGE (c) COPYRIGHT Hewlett-Packard Co. 1985 > The FIX PATH command first checks all paths and all data sets in the database. (For a description of the CHECK PATH and CHECK SET output, refer to "CHECK BASE" and "CHECK SET" earlier in this chapter). After checking the paths and data sets, any problems that are detected are fixed and described in the FIX INFORMATION section of the output. In the above example, DBChange Plus adds new key values to the data sets CUSTOMER and PRODUCT. A message is returned verifying the status of the fix process.


MPE/iX 5.0 Documentation