EYU9XDBT utility error handling

Three levels of error can occur in EYU9XDBT utility program processing.

These errors are as follows:
  • Errors in the command parameter stream that are detected by EYU9XDBT.

    EYU9XDBT processes each command as it occurs in the command input stream. If the utility program detects an error in a command (for example, an unrecognized parameter), it stops processing without reading any more commands and issues message EYUXU1448E Data stream rejected which gives an EYU9XDBT return code of 12.

  • Errors in the CICSPlex® SM API detected by CICSPlex SM when it is processing calls from EYU9XDBT.

    If a command and its parameters are recognized by EYU9XDBT, it calls the CICSPlex SM API to perform the specified action. However, if CICSPlex SM detects an error, only that command fails (with an EYU9XDBT return code of 8 or 12), and EYU9XDBT continues with the next command. For example, a DEFINE REGION command that specifies SYSID ABCDE is accepted by EYU9XDBT but rejected by CICSPlex SM because the SYSID value is more than 4 characters long, producing the following error messages:

    EYUAR0021E
    Length of data for attribute (CSYSDEF._SYSID) is invalid.
    EYUXU1441S
    TBUILD failed for CSYSDEF data: FAILURE.
    EYUXU1448E
    Datastream rejected.
  • Abend code 878 when a program attempts to use more storage than it has allocated.

    In EYU9XDBT this abend is caused by an insufficient region size. The solution is to increase the region size. This abend code can occur in the following situation:

    • Not accounting for the retention by EYU9XDBT of large numbers of definitions in memory when setting your region size.

      You can calculate the storage required by multiplying the definition size by the definition count. However, if you cannot modify the region size, you might be able to modify the existing commands to use less storage. Because each command is run separately, reducing the number of definitions per command is a straightforward and effective way of lowering storage requirements.

      One way of reducing storage requirements is to avoid using the generic * (asterisk) character to define the definition type and the definition name in IMPORT, EXPORT, and PRINT commands because it can result in large numbers of definitions held in storage. Instead, use separate commands that select the least number of definitions feasible.



eyua700006.html | Timestamp icon Last updated: Sunday, 4 June 2017