Compile of an application program fails; no listing is generated. *

Compile listings are only created when a listing library is specified in the target.

To get a compiler listing, specify a listing library, compose the MAKE procedure, and execute the MAKE procedure.

Compile of an application program fails due to insufficient storage.

The compiler requires more storage than is available to compile the program.

The safest action is to execute the ITINSTAL dialog, increase the COBOL size parameter specified during IT installation and regenerate the PARM file.

The size parameter is stored in ISPF variable TIRCBLSZ, generated into the TIRIT member of the PARM file. TIRIT is generated when the IT is installed.

You can change the value in the PARM file; however, your change is overlaid if the TIUIT PARM file is regenerated.

Compose of a MAKE procedure fails with File Not Open

The IT is attempting to write the generated MAKE procedure and has found that the output file is not open.

Make sure that the script file associated with the target being used contains a valid openfile directive.

Installation of application DDL fails with an -818 timestamp error.

The IT uses a program (TIUUSQL) to execute SQL dynamically. The executable does not match the DBRM used to bind the program.

Contact your IT administrator. Rebind the plan for TIUUSQL for the DB2 subsystem you are using.

Installation of application DDL fails with a -922 authorization error.

The IT uses a program (TIUUSQL) to execute SQL dynamically. Either you are not authorized to execute the plan for this program or a plan has not been bound for the DB2 subsystem you are using.

Contact your IT administrator; ask him or her to grant you execute authority for the plan or to bind the plan for the DB2 subsystem you are using.

The JCL created by the IT to install an application database contains DDL statements in place of IDCAMS control statements.

The DDL IP you are processing contains IDCAMS and DDL statements. The IDCAMS statements are split to the IDCAMS location and the DDL statements are split to the DDL location. If the IDCAMS location and the DDL location are the same, the DDL overlays the IDCAMS statements.

Specify a unique DDL library and IDCAMS library.

NCAL link-edit of a module fails with an SD37 or SE37 abend. *

After the IT compiles a module, the resulting object module is input to the linkage editor to produce an NCAL load module

Delete unused load modules from the relevant NCAL load library and then compress it. If necessary, allocate the library with more space and re-execute the MAKE procedure.

The split of an RI trigger IP fails with a dataset not found error.

The split step places the source for the RI trigger modules in the RI trigger source library. This data set does not exist.

Correct the target to refer to an existing library or allocate the library that does not exist.

The split of a load module IP fails with a location not found error.

The split step places the installation control file in the installation control library and the generated source modules in the source library. One or both of these locations is unspecified (that is, a library is unspecified at the target, model or business system level).

Specify a source library and install control library at the target, model, or business system level.

The split of the load module IP fails with a dataset not found error.

The split step places the installation control file in the installation control library and the generated source modules in source library. Either the install control library or source library does not exist.

Correct the target to refer to existing libraries or allocate the libraries that do not exist.

Compilation of a module fails with a listing data set error. *

A listing data set was specified in the target. A problem was encountered allocating this data set.

Verify the relevant listing library exists. If it doesn’t, allocate it or change target to an existing library, recompose the MAKE procedure.

Compilation of a module fails with an SD37 or SE37 abend. *

A compiler output file ran out of space. The most likely cause is that the listing library is out of space.

If there is a listing library, check the number of library extents. If out of space, delete unused listings and compress library or allocate more space. Reexecute the MAKE procedure. If extents are adequate, there may be a space problem with the sys temp file allocated to the object module created by the compiler. Contact your IT Administrator.

DB2 precompiler fails with a RC=20.

Code with imbedded SQL is processed by the DB2 precompiler before its input to the COBOL compiler. The DB2 precompiler step failed.

Make sure you specified a DBRM library in your target. Make sure that DBRM library exists.