ASMAXT2E messages

ASMAXT2E may generate the following messages. Each message is prefixed with an assembler indication of the form ASMA70ns, where n is 0, 1, 2, 3, or 4, and s is one of the standard severity-indication letters I, W, E, S, T. This indication is followed by the word "OBJECT: ". Then, the message text is preceded by "ASMAXT2E: ".

Exit not coded at same level (2,3) as Assembler
Severity:

16

Explanation:

The ASMAXT2E module expects a different I/O exit interface from that supplied by High Level Assembler.

User response:

This is an internal error. Report the problem to IBM service.

System action:

Processing is terminated.

Exit called for other than PUNCH or OBJECT
Severity:

16

Explanation:

The ASMAXT2E module was invoked as an exit of type other than PUNCH or OBJECT.

User response:

This is caused by incorrect assembler invocation options. Correct the options string and re-assemble.

System action:

Processing is terminated.

Exit not initialized, and not entered for OPEN
Severity:

16

Explanation:

The ASMAXT2E module was expected to be open and initialized, but was not

User response:

This is an internal error. Report the problem to IBM service.

System action:

Processing is terminated.

Insufficient working storage for exit
Severity:

16

Explanation:

The ASMAXT2E module requires more working storage than is available.

User response:

Specify a larger storage area, or specify a smaller SIZE option.

System action:

Processing is terminated.

Invalid action or operation type requested
Severity:

16

Explanation:

The ASMAXT2E module was invoked as an I/O exit with an invalid action or operation type.

User response:

This is an internal error. Report the problem to IBM service.

System action:

Processing is terminated.

Expecting input record, zero buffer length
Severity:

16

Explanation:

The ASMAXT2E module expected to receive an object file record to process, but none was present.

User response:

This is an internal error. Report the problem to IBM service.

System action:

Processing is terminated.

Close request for wrong exit type
Severity:

16

Explanation:

The ASMAXT2E module received a CLOSE request, but for the wrong exit type.

User response:

This is an internal error. Report the problem to IBM service.

System action:

Processing is terminated.

Invalid request-list options value
Severity:

12

Explanation:

The ASMAXT2E module was invoked to process a record, but an options string was provided.

User response:

This is an internal error. Report the problem to IBM service.

System action:

Processing is terminated.

Invalid parm-string length
Severity:

12

Explanation:

The ASMAXT2E module was provided with a parameter string, but its length was invalid.

User response:

Check that the assembler options specifying the I/O exit are valid.

System action:

Processing is terminated.

Too many ESD IDs
Severity:

12

Explanation:

The program being processed has too many ESD items with distinct ESD IDs.

User response:

Restructure the program to reduce the number of independently relocatable items.

System action:

Processing is terminated.

Too many RLD items
Severity:

12

Explanation:

The program being processed has too many relocatable address constants.

User response:

Restructure the program to reduce the number of address constants.

System action:

Processing is terminated.

Too many OBJ SD/CM/PC sections
Severity:

12

Explanation:

The program being processed has too many control sections.

User response:

Restructure the program to reduce the number of control sections.

System action:

Processing is terminated.

Too many ELF sections
Severity:

12

Explanation:

The program being processed requires more ELF sections than can be provided.

User response:

Restructure the program to reduce the number of independent items, or contact IBM service to request that ASMAXT2E be enhanced.

System action:

Processing is terminated.

String table overflow
Severity:

12

Explanation:

The program being processed requires more space in the ELF string table than can be provided.

User response:

Restructure the program to reduce the number of or length of external names, or contact IBM service to request that ASMAXT2E be enhanced.

System action:

Processing is terminated.

Too many LD items
Severity:

12

Explanation:

The program being processed contains too many ENTRY names.

User response:

Restructure the program to reduce the number ENTRY statements, or contact IBM service to request that ASMAXT2E be enhanced.

System action:

Processing is terminated.

Too many ELF symbols
Severity:

12

Explanation:

The program being processed requires more ELF symbols than can be processed.

User response:

Restructure the program to reduce the number of names, or contact IBM service to request that ASMAXT2E be enhanced.

System action:

Processing is terminated.

Insufficient storage for OBJ TXT records
Severity:

12

Explanation:

The program being processed requires more work space than is available to process machine language instructions and data.

User response:

Specify a larger storage area, or specify a smaller SIZE option.

System action:

Processing is terminated.

AMODE/RMODE 24 or 64 not supported in section 'xxxxxxxx'
Severity:

8

Explanation:

The program being processed contains a control section xxxxxxxx with an unsupported AMODE or RMODE.

User response:

Modify the program to specify valid AMODE and RMODE.

System action:

The section is discarded, and processing continues. No ELF object file will be produced.

External Dummy (XD) item 'xxxxxxxx' not supported
Severity:

8

Explanation:

The program being processed contains a dummy external control section (XD) xxxxxxxx.

User response:

Modify the program to remove the XD item.

System action:

The item is discarded, and processing continues. No ELF object file will be produced.

Adcon at xxxxxxxx in section with ID xxxx not 4 bytes long
Severity:

8

Explanation:

The program being processed contains an address constant at address xxxxxxxx in a control section with ESDID xxxx that is not 4 bytes long.

User response:

Modify the program to correct the address constant.

System action:

The item is discarded, and processing continues. No ELF object file will be produced.

Adcon at xxxxxxxx in section with ID xxxx not type A or V
Severity:

8

Explanation:

The program being processed contains an address constant at address xxxxxxxx in a control section with ESDID xxxx of type Q, or DXD, or CXD.

User response:

Modify the program to remove the address constant.

System action:

The item is discarded, and processing continues. No ELF object file will be produced.

Adcon at xxxxxxxx in section with ID xxxx requires unsupported negative relocation
Severity:

8

Explanation:

The program being processed contains an address constant at address xxxxxxxx in a control section with ESDID xxxx which requires negative relocation.

User response:

Modify the program to remove the address constant.

System action:

The item is discarded, and processing continues. No ELF object file will be produced.

ELF file not produced due to previous errors
Severity:

8

Explanation:

Previous errors have suppressed the production of an ELF object file.

User response:

Correct the errors.

Section length on END record not supported
Severity:

8

Explanation:

The OBJ END record contains the length of a control section.

User response:

The object file may be very old, possibly produced by a language translator that put the section length on the OBJ END record. (This condition will not arise with object files produced by High Level Assembler.)

System action:

The item is discarded, and processing continues. No ELF object file will be produced.

Invalid END-record entry point request
Severity:

8

Explanation:

The OBJ END record contains a request for a particular entry point in the program.

User response:

Remove the entry point request from the END record.

System action:

The item is discarded, and processing continues. No ELF object file will be produced.

LD item 'xxxxxxxx' in unsupported section is ignored
Severity:

8

Explanation:

The ENTRY name xxxxxxxx is in a control section that was previously discarded.

User response:

Correct the original error causing the section to be rejected.

System action:

The item is discarded, and processing continues. No ELF object file will be produced.

RLD item at address 'xxxxxxxx' in unsupported section with ID 'xxxx' is ignored
Severity:

8

Explanation:

The RLD item at address xxxxxxxx in a control section with ESDID xxxx is in a control section that was previously discarded.

User response:

Correct the original error causing the section to be rejected.

System action:

The item is discarded, and processing continues. No ELF object file will be produced.

RLD item at address 'xxxxxxxx' in unsupported section with ID 'xxxx' references unsupported section
Severity:

8

Explanation:

The RLD item at address xxxxxxxx in a control section with ESDID xxxx references a position in a control section that was previously discarded.

User response:

Correct the original error causing the section to be rejected.

System action:

The item is discarded, and processing continues. No ELF object file will be produced.

Section 'xxxxxxxx' ignored, addresses exceed X'FFFFFF'
Severity:

8

Explanation:

The control section named xxxxxxxx contains addresses either very close to or exceeding X'FFFFFF'.

User response:

Reduce the size of the section, change its starting address, or (if the source program contains multiple control sections) re-assemble with the NOTHREAD option.

System action:

The item is discarded, and processing continues. No ELF object file will be produced.

RLD items at 'xxxxxxxx' in section with ID 'xxxx' cause double relocation
Severity:

8

Explanation:

The RLD items at address xxxxxxxx in a control section with ESDID xxxx require more than a single relocation at that address.

User response:

Change the program so that only a single relocation is required at a given address.

System action:

The items are discarded, and processing continues. No ELF object file will be produced.

No TXT records in OBJ file
Severity:

8

Explanation:

The program generates no machine language instructions or data.

User response:

Verify that the program is correctly coded. (A DSECT statement may be misplaced.)

System action:

The item is discarded, and processing continues. No ELF object file will be produced.

Entry point in zero-length PC section rejected
Severity:

8

Explanation:

An entry point was specified in a zero-length Private Code section.

User response:

Verify that the program is correctly coded.

System action:

The item is discarded, and processing continues. No ELF object file will be produced.

LD item 'xxxxxxxx' in section with ID 'xxxx' lies outside its owning section
Severity:

8

Explanation:

An entry point named xxxxxxxx was specified that lies outside the bounds of its owning control section with ESDID xxxx.

User response:

Verify that the program is correctly coded.

System action:

The item is discarded, and processing continues. No ELF object file will be produced.

LD item 'xxxxxxxx' in COM section with ID 'xxxx' not supported
Severity:

8

Explanation:

An entry point named xxxxxxxx was specified in a common (COM) control section with ESDID xxxx.

User response:

Correct the program to remove the ENTRY point. (ENTRY points in COM sections are not supported; you may be able to reference items not at the origin of a COM section by specifying a constant offset in a referencing address constant.)

System action:

The item is discarded, and processing continues. No ELF object file will be produced.

Invalid or duplicate parm-string character ignored
Severity:

0

Explanation:

An invalid or duplicated character appears in the parameter string provided to ASMAXT2E.

User response:

Correct the options invoking ASMAXT2E to specify valid characters.

System action:

The item is ignored, and processing continues.

nnnnnnnn SYM records ignored
Severity:

0

Explanation:

The OBJ file contained nnnnnnnn SYM records, produced when the TEST option is provided to High Level Assembler.

User response:

Correct the options invoking High Level Assembler.

System action:

The records are ignored, and processing continues.

nnnnnnnn non-OBJect record(s) ignored
Severity:

0

Explanation:

The OBJ file contained nnnnnnnn records that are not object-module records.

User response:

The program may contain PUNCH or REPRO statements. Verify that they are not required.

System action:

The records are ignored, and processing continues.

Zero-length Private Code (PC) section ignored
Severity:

0

Explanation:

The program contains a zero-length Private Code (PC) section.

User response:

Correct the source program.

System action:

The section is ignored, and processing continues.

xxxxxxxx object records processed, xxxx usable control section(s)
Severity:

0

Explanation:

The program produced xxxxxxxx object records, and xxxx control sections were converted to ELF format.

ELF file length X'xxxxxxxx'
Severity:

0

Explanation:

The generated ELF file is X'xxxxxxxx' bytes long.


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