Skip to Content

//*ROUTE XEQ //*NET

The //*ROUTE XEQ processing is handled in one of two ways:

  1.  It is translated to JES2 //*ROUTE XEQ. A TMPARM statement is required for this option. If the statement is translated, the data is not captured in the JAL Descriptor (i.e. $JES3_ROUTE_XEQ has no value).
  2.  It is captured and the routing effected by adding a binding agent in JAL based on the $JES3_ROUTE_XEQ Descriptor. The information on the //*ROUTE XEQ statement is passed to JAL for decision-making processes.

Please refer to the Base Product: System Programming Guide for a description of the handling of //*ROUTE XEQ and JBS Job Binding Services.

The //*NET statement is honored by JES2 if the TMPARM feature NET has been enabled.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Compuware ThruPut Manager 18.02