Step for obtaining diagnosis information when the binder is invoked from c89:

About this task

Before you begin: You need to make sure the IEWDUMP and IEWTRACE data sets are pre-allocated and cataloged. The lowest-level qualifier must be the same as the DDNAMEs (IEWTRACE or IEWDUMP), and the remainder (prefix) must be the same for both.

Rule: Both data sets must be pre-allocated even if only one of is used.

Perform the following step to obtain the diagnosis information.

In the UNIX shell, export _C89_DEBUG_PREFIX=your_prefix, where your_prefix is the prefix used on the names of the IEWDUMP and IEWTRACE data sets. The c89 command will do the allocations (DISP=SHR) during the bind step.

Guidelines: These guideline are designed to ease problem determination:

For problem diagnosis, you should also use export _BPXK_JOBLOG=2 so that any message appearing on the operator console is also written to stderr.
In addition to IEWDUMP and IEWTRACE, use both the c89 -v and -V options to capture stdout and stderr. This method makes the binder invocation parameters and the binder output listing with error messages available for diagnosis.
If you use the Cxx or C++ commands instead of c89, the environment variable name much match the command name. For example, use _CXX_DEBUG_PREFIX or _C++_DEBUG_PREFIX instead of _C89_DEBUG_PREFIX.