Considerations for a logical parent's concatenated key
By default, for a logical child segment with a logical parent's concatenated key (LPCK) that is specified as VIRTUAL on the SEGM statement of the DBD, FABHURG1 returns blanks in the I/O area that usually contains LPCK, and FABHFSU returns binary zeros in the area.
To have HSSR Engine build the LPCK and return it in the I/O area, you must specify BLDLPCK control statement in the HSSROPT data set. For details, see BLDLPCK control statement.
When you unload an uncorrupted database that has a logical child whose LPCK is defined as virtual, and if BLDLPCK statement is not specified, you must run the IMS Database Prereorganization utility with the control statement DBR= to get a successful reload and prefix resolution. The control statement DBIL= gives incorrect results in this case.
You must specify BLDLPCK statement when you unload a corrupted database that has a logical pointer error in a logical child whose LPCK is defined as virtual. Since you suspect that logical pointers are incorrect, you must also run the Database Prereorganization utility, using the DBIL= control statement. Otherwise, you will get an incorrect reload that would be detected during prefix resolution.