Reading database records from FZ files

CALL HDBFRFZ (PATH,LUN,NSKIP,KEYS,CHOPT,IRC*)

PATH

Pathname of the directory into which the records are to be copied.

LUN

Logical unit number for the FZ file.

NSKIP

Skip NSKIP records before reading. If option R is chosen the start-of-run record is not included in NSKIP.

KEYS

Vector of KEYS containing the period of validity.

CHOPT

Character variable containing a string of single character options

' '

No start-of-run record and take period of validity from input. Store as base record.

'A'

Create the directory specified by PATH before reading the FZ file (cannot create a new file if a whole database is to be loaded).

'B'

Store as base record.

'C'

Header contains the pathname, i.e. first header contains length of the pathname (max. 40 words) and the following words contain the pathname. However, the pathname cannot be written into the start-of-run header.

'H'

Take period of validity from the first 6 words of each header. If option P is chosen take sub-run type from the seventh word of the header.

'I'

extend the validity range beyond one experiment number

'P'

Store as partial record.

'R'

FZ file begins with start-of-run record.

'RH'

As option R and take period of validity from start-of-run header as is described for option H.

'T'

Take time stamp from input KEYS vector

'W'

The whole directory is loaded via call to RZFRFZ.

 

IRC

Return status

0

Normal completion

An FZ file created using the routine HDBTOFZ or the routines HDBMERG or HDBEXTR with the X option may be read using the routine HDBFRRZ. In the special case that the FZ file contains the contents of a complete database, using the option W in HDBTOFZ, a new database file should be created using the routine HDBNEW before calling this routine. In all other cases, the data is entered into the subdirectory specified by the path PATH, or else the subdirectory tree stored is added at the level specified by the path PATH. This routine may also be used to process FZ files that are not written by one of the HEPDB routines. For example, an FZ file containing a single datastructure may be read in and entered into the database in the directory specified by the variable PATH with the period of validity as specified by ISEL.

Clearly, if the FZ file contains a database or directory tree, the validity of the recovered records is the same as those originally stored. However, when the FZ file contains a single record extracted from a database previously, or a completely new ZEBRA structure, then the validity may be specified. If the validity has been stored with the record, then this may be retrieved and applied. If the record contains a start-of-run record, the option R must be used.