gtpd1m0n | Database Reference |
The following describes the file addressing formats that can be used to read a
general file data set (using FIND or FIND SPECIAL).
- Note:
- In these descriptions, the pseudo module number is defined as the sum of the
starting general file module number and the number of the data set the user
wants to access. For example, if the TPF system is generated to start
general file pseudo module numbers at 010 (see the GFMOD parameter of the RAM
macro in TPF System Generation), then general file
data set number 03 will be pseudo module number 013. The module number
that the user specifies will be the hexadecimal equivalent of 013, that is,
0D.
The parameter mmgggggg that must be provided for a general file
relative record number request has the following format:
If the calling segment is processing a relative record request (as in the
ZDFIL mmgggggq format):
-
mmgggggq must be placed in fields CE1FMn, CE1FCn, CE1FHn, and CE1FRn
of the appropriate entry control block (ECB) data level fields or IDECFM,
IDECFC, IDECFH, and IDECFR of the appropriate data event control block
(DECB).
- The caller must issue a FIND using the GDS=Y keyword.
If the calling segment is processing a request for an extended MCHR address
(as in the ZDFIL mmmmcccchhhhrr format):
- CE1FXn bytes 0-1 must contain hex zeros.
- CE1FXn bytes 2-3 must specify the cylinder address.
- CE1FXn bytes 4-5 must specify the head address.
- CE1FXn byte 6 must contain the record number.
- CE1FMn bytes 0-1 must contain the pseudo mod number.
- The caller must issue an FNSPC macro specifying extended addressing (E
parameter).