Program Loader

A program function request (ie. FETCH, COLOAD etc) has been issued by the program, however, an invalid parameter list was provided for the request.

The user program is abnormally terminated with a Com-plete online dump.

This error was caused by the application program. Seek the assistance of the application programmer responsible for the program in use when the error occurred.

R1 contains the location of the parameter list for the request. This points to an invalid location.

Com-plete invokes the IBM Binder under certain circumstances to load a module. The module indicated by $1 could not be loaded, the Binder returned a reson code which is indicated by $2.

Depends on what the module was to be loaded for.

Possibly there is a problem with the load module. See IBM DFSMS Program Managementfor the meaning of the Binder reason code.

Program $1 issued a program function request (ie. FETCH, COLOAD etc) for module $2, however, module $2 was not available to the Com-plete.

The user program is abnormally terminated with a Com-plete online dump.

R1 in the dump contains the location of the parameter list for the overlay function. The first word in the list contains the location of the name parameter. Check the validity of the name specified. If it was invalid, correct the name and retry the function. If the name specified was valid, ensure that the module is available to Com-plete in the appropriate OS load libraries or VSE libraries.

This error was probably caused by the application program. Seek the assistance of the application programmer responsible for the program in use when the error occurred.

Program $1 attempted to issue a program control request for module $2. This was disallowed as $2 may not be the object of such a request unless a user has logged on.

The user program is abnormally terminated.

A program can be allowed to run before someone has logged on to a terminal by setting this option for the program using ULIB. Refer to the ULIB documentation for more information.

Logon on to the terminal prior to running the program you are running. If it should be possible to run the program without logging on, report the error to your system administrator.

Start or continuation of the application was denied because its use has been suspended.

The "suspended" flag for an application can be switched in ULIB.

If you feel like the use of the application should not be suspended, contact your Com-plete system administrator.

Program $1 issued a program function request (ie. FETCH, COLINK etc.) however, the area or area length provided for the request is/are not valid.

The user program is abnormally terminated with an Com-plete online dump.

This error was caused by the application program. Contact the individual responsible for the program in use when the error occurred.

R1 in the dump contains the location of the parameter list for the overlay function. The second word in the list contains the location of the area parameter. The third word points to the length parameter.

Program $1 has issued a FETCH request for program $2, however, the user does not have access to the program $2.

The user program is abnormally terminated with a Com-plete online dump.

Contact your system administrator to get access to program $2 if you should normally have access to this program.

Determine and use the installation procedures for calling security protected programs or data.

This message is associated with overlays. It indicates that the module '$' was locked to a thread other than the one in which the calling program was executing.

The user program is abnormally terminated with a Com-plete online dump.

Seek the assistance of the application programmer responsible for the program in use when the error occurred.

Use the ULIB utility to make the thread lock status consistent for both programs.

Program $1 issued a program function request (ie. FETCH, ATTACH etc) however, the provided name $2 is not a valid name. This message may also indicate a six byte program name parameter field treated as an eight byte field due to an application program using six byte fields having been compiled / linked with libraries designed for eight byte fields.

The user program is abnormally terminated with a Com-plete online dump.

This error was caused by the application program. Seek the assistance of the application programmer responsible for the program in use when the error occurred.

R1 in the dump contains the location of the parameter list for the overlay function. The first word in the list contains the location of the name parameter.

This message is associated with the FETCH, LOAD, or LOADT functions of Com-plete. An installation may set security requirements on programs to prevent their unauthorised use. This message indicates that the security requirements were not satisfied for the program specified in the FETCH, LOAD, or LOADT request.

The user program is abnormally terminated with a Com-plete online dump.

This message may mean that the user ID in use is not authorised to use the program or that a particular function of the program is restricted. Contact the individual responsible for security.

For information about Com-plete FETCH, LOAD, and LOADT security, refer to the Com-plete System Programmer's Manual.

A user program issued an OS load for module $1. This was emulated by Com-plete, however, the LOAD or BLDL failed. The reason code $2 for a load failure is the abend code returned by load processing, for the BLDL it's the R0 following the BLDL.

The user program is terminated with a dump.

Contact your help desk or operations area for assistance.

The reason code printed by Com-plete along with message issued by the operating system should give all the information necessary to clear this problem.

A user program issued an OS LOAD which Com-plete attempted to emulate. During this emulation, Com-plete attempted to load module $1, however, the LOAD abended with code $2.

The user program is terminated.

Contact your help desk or operations area for assistance.

This normally indicates an I/O error, however, the abend code printed, along with message from the operating system which are normally issued in these cases should be enough to determine and solve the problem.

Program $1 issued a FETCH or LOAD request for program $2. This could not be completed as there was no storage available for the buffers required to complete the request.

The user program is terminated and program $2 is not fetched.

This indicates that a storage area within the Com-plete general buffer pool was not available to satisfy the request. Normally, an attempt will be made to expand the buffer pool so there is not enough storage in the region and the expand failed.

Program $1 issued a FETCH request for program $2, however, this has failed as the required region size for the program is larger than any of the currently available threads in the system.

The user program is terminated.

Report the problem to your system administrator.

Either the catalog size for the program must be lowered to a value which will fit in one of the currently defined threads using the ULIB utility, or the thread definitions must be changed to ensure that one or more threads exist which are large enough to accomodate the program's catalog size.

Self-explanatory message.

Self-explanatory message.

Program $1 issued a program control request for $2, however, this failed because there was no eligible processor group for program $2.

Report the error to your system administrator.

This will occur when a program has been catalogued with a specific processor group which should be used using ULIB. In this case either the processor group has not been defined or has been deleted.

Program $1 issued a program control request for $2, however, this failed because the system is quiescing.

If program $2 should be available when the system is quiescing, the appropriate option must be set for the program using ULIB. Refer to the ULIB documentation for more information.

Library access error from LIBRM

Startup will continue

Correct storage errors. Contact SAG for other errors.

Correct storage errors. Contact SAG for other errors.