When a particular return code is passed to ARCERP, DFSMShsm examines both the requested error processing level passed by the calling routine and the level set by a possible TRAP command to determine the actual level of error processing used. In many cases, but not all, the TRAP command can be used to override the requested processing level as shown in Table 1.

Note that in a few cases, a code returned from a module may have resulted from several conditions. For example, the ARCCOPEN module passes back OPEN macro return codes and VERIFY macro return codes. The return code itself does not identify which macro has generated it. In such cases, the dump that results from the error processing must be examined to find the offset pointer into the ARCCOPEN module from which the ARCERP call has been made. The ARCCOPEN source code immediately advances this offset and indicates whether an OPEN or a VERIFY macro has been attempted.

Also note that if an abnormal end occurs, the system abnormal end code is reported in decimal format. For example, an abnormal end 0C1 in ARCCATBU is listed as "ARCO205I TRAP" in module ARCCATBU for code 0193 by the QUERY TRAP command. To obtain a snap dump for this example, enter: TRAP ARCCATBU 193 SNAP