EGL Reference Guide for iSeries


Use of build descriptors

A build descriptor helps to determine aspects of the debugging environment. The EGL debugger selects the build descriptor in accordance with the following rules:

If you are debugging a program that is intended for use in a text or batch application in a Java environment, and if that program issues a transfer statement that switches control to a program that is also intended for use in a different run unit in a Java environment, the EGL debugger uses a build descriptor that is assigned to the receiving program. The choice of build descriptor is based on the rules described earlier.

If you are debugging a program that is called by another program, the EGL debugger uses the build descriptor that is assigned to the called program. The choice of build descriptor is based on the rules described above, except that if you do not specify a build descriptor, the debugger does not prompt you for a build descriptor when the called program is invoked; instead, the build descriptor for the calling program remains in use.

Note:
You must use a different build descriptor for the caller and the called program if one of those programs (but not both) takes advantage of VisualAge Generator compatibility. The generation-time status of VisualAge compatibility is determined by the value of build descriptor option VAGCompatibility.

A build descriptor or resource association part that you use for debugging code may be different from the one that you use for generating code. For example, if you intend to access a VSAM file from a program that is written for a COBOL environment, you are likely to reference a resource association part in the build descriptor. The resource association part must refer to the run-time target system and must refer to a file type that is appropriate for the target system. The difference between the two situations is as follows:


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]