Certain restrictions apply when you reload records that
have user-defined header format.
- If you specify the USERHDRX control statement and
the SORT control statement at the same time, you must specify one
of the following exit routine names on the USERHDRX control statement.
Table 1. Exit routine names and the formats of the unloaded file
| Exit routine name |
Format of the unloaded file |
| HPSRCVA3 |
*A3 |
| HPSRCVA4 |
*A4 |
| HPSRCVF1 |
*F1 |
| HPSRCVF2 |
*F2 |
| HPSRCVF3 |
*F3 |
| HPSRCVF6 |
*F6 |
- If the segment data of unloaded file is in compressed form, you must specify COMPRESS=NO.
- HALDB is not supported.
- Logical relationships are not supported.
Important: If the database has logical
relationships, you must use USERHDRX at your own risk.
Requirement: If the unload data set has logical child segments, the unload header, which is
generated by the user header conversion exit, must include enough information to resolve logical
relationships.
- If the USERHDR control statement is specified, a header
or a trailer record must not reside in the unloaded file.
- The Load API is not supported.