This data area (for a layout see Network Print Facility's Routing Data Area (RDA)) is the cornerstone of the Network Print Facility. It contains the routing information referenced by the Network Print Facility. The Network Print Facility can build the RDA, or the user can build it. In either case, it must be established so the Network Print Facility can access the routing information required.

The routing data area is accessible to all three exits. If the general routing exit builds the routing data area, it should initialize all fields. Fields that can be modified by either the specific routing exit or the input record exit are marked.

Use the general routing exit (EZAGRPPR) to create the routing data area.

Both the general routing exit and the specific routing exit affect the RDA. The Network Print Facility modifies the RDA depending on the result of a series of checks, as follows:

1. Does a general routing exit exist?

   Invoke it. The general routing exit does one of the following thing:

   1. Builds the RDA (don't read the routing and options files).
   2. Modifies the keys used to read the routing and options files.
   3. Nothing.
2. The GRE notifies NPF of the results of this check. If no RDA was built, NPF builds one.

   The system then checks if a specific routing exit exists. If there is one, the Network Print Facility invokes it.

   The specific routing exit can modify the RDA.

See Network Print Facility's Routing Data Area (RDA) for the exact structure of the RDA.