Whenever an assembly cannot complete, High Level Assembler provides a message and, in some cases, a specially formatted dump for diagnostic information. This might indicate an assembler malfunction or it might indicate a programmer error. The statement causing the error is identified and, if possible, the assembly listing up to the point of the error is printed. The messages in this book give enough information to enable you to correct the error and reassemble your program, or to determine that the error is an assembler malfunction.
If SYSPRINT or SYSLST (z/VSE) is unavailable, the assembler uses the macro WTO with a route code of 11 and a descriptor code of 7, or the system defaults, to output the message(s).
Messages
The assembler attempted to load the phase ASMA93, but the load failed either because there was insufficient GETVIS storage available to complete the load, or the phase could not be found.
The assembly stops and no listing is produced.
Check the LIBDEF chain to ensure that the sublibrary containing High Level Assembler is correctly concatenated. If it is, you should consider increasing the partition size.
20
The assembler attempted to load the named exit module, but the load failed.
The assembly stops and no listing is produced.
Check that the specified exit module is in a library accessible by the assembler.
20
The assembler attempted to load the named messages module, but the load failed. The name of the messages module is determined from the value specified in the LANGUAGE option.
The assembly stops and no listing is produced.
Check that you have correctly specified the correct messages module using the LANGUAGE option, and that the specified messages module is in a library accessible by the assembler.
20
The assembler attempted to load the named default options module, but the load failed.
The assembly stops and no listing is produced.
Check that the default options module is in a library accessible by the assembler.
20
The assembler encountered an error when attempting to open a required file.
Before this message is issued, one or more associated messages are issued that describe which file or files could not be opened. After this message is issued, the assembly stops.
Check the associated message or messages.
20
The assembler detected an error in one or more of the parameters specified when the assembler was invoked, and the installation default value for the PESTOP assembler option is YES.
Before this message is issued, one or more associated messages are issued that describe which parameter or parameters were in error. After this message is issued, the assembly stops.
Check the associated message or messages. Invoke the assembler with correct invocation parameters. Do not attempt to override the fixed installation defaults.
20
The assembler attempted to load the translation table called xxxxxxxx, but the load failed. The name of the translation table is determined from the value specified in the TRANSLATE option.
The assembly stops and no listing is produced.
Check you have correctly specified the translation table module using the TRANSLATE option, and the module is in a library accessible by the assembler.
20
The translation table specified in the TRANSLATE option is not valid.
The assembly stops.
Ensure the translation table is generated according to the instructions described in Appendix L. How to generate a translation table.
20
The assembler attempted to load the external function module xxxxxxxx, but the load failed.
The assembly stops and no listing is produced.
Check that the specified module is in a library accessible by the assembler, and that the external function name has been spelled correctly in the SETAF or SETCF statement.
20
The user supplied exit for exit-type failed when processing an operation request. The exit might have provided error text to assist in determination of the failure.
The assembly stops.
Check the specified exit program for the cause of failure.
20
The user supplied external function external function name failed during processing.
The assembly stops.
Check the specified external function program for the cause of failure.
20
The default options module ASMADOPT is not in the required format for this release of the assembler. The assembler checks to ensure the release of the module is the same as that of the assembler.
The assembly terminates
Ensure that you have the correct version of the ASMADOPT module available. You might need to reassemble your default options module with the current ASMAOPT macro.
20
The assembler tried to produce a heading line in the assembler listing but could not find the heading. This can be caused if the assembler load module has been corrupted.
The assembly is aborted.
Reassemble the program; it might assemble correctly. If it does not reassemble without error, save the output from the assembly, and the input source(s), and contact IBM for support.
20
The assembler attempted to load the module ASMA93, but the load failed either because there was insufficient main storage available to complete the load, or the module could not be found, or the Assembler was dynamically invoked by an APF-authorized program yet the Assembler does not reside in an APF-authorized library.
The assembly stops and no listing is produced.
on z/OS, ensure that the correct High Level Assembler load library is available in the standard load module search order. If the assembler is invoked by an APF-authorized program then ensure that the assembler resides in an APF-authorized library. Check that there is sufficient virtual storage available to the assembler and consider increasing the region size.
On CMS, ensure that the correct mini disk containing the High Level Assembler modules is being accessed. If it is, consider increasing your virtual machine storage size.
20
The assembler attempted to load the Code Page module called xxxxxxxx, but the load failed. The name of the module is determined from the value specified in the CODEPAGE option.
The assembly stops.
Check that you have correctly specified the Code Page module using the CODEPAGE option, and that the module is in a library accessible by the assembler.
20
The code page module specified in the CODEPAGE option is not valid.
The assembly stops.
Ensure the code page module is generated according to the instructions described in Appendix M. How to generate a Unicode translation table.
20
The assembly stops because of one of the errors described in ASMA950U through ASMA964U. This usually is caused by an error in the assembler itself. Under certain conditions, however, the assembly can be rerun successfully.
The assembly stops and a formatted abnormal termination dump is produced. Depending on where the error occurred, the assembly listing up to the failing statement might also be produced. The dump usually indicates which statement was being processed at the time of abnormal termination. It also might include contents of the assembler registers and work areas and other status information for use by an IBM support representative.
Check the statement that was being processed at the time of abnormal termination. Correct any errors in it or, if the statement is long or complex, rewrite it. Reassemble the program; it might assemble correctly. However, even if the program assembles correctly, there might be a problem with the assembler. Save the abnormal termination dump, the assembly listing (if one was produced), and the source program, and contact IBM for support.
20
The assembler attempted to load the named phase, but there was not enough GETVIS storage available for the phase.
The assembly stops and no listing is produced.
Increase the amount of GETVIS storage allocated to the partition.
20
The assembler attempted to acquire an initial block of storage, but there is not enough GETVIS storage available.
The assembly stops and no listing is produced.
Increase the amount of GETVIS storage allocated to the partition.
20
The statement is too complex to be evaluated by the macro generator phase of the assembler. It overflowed the evaluation work area of the assembler. Normally, there is no assembler malfunction; the statement can be corrected and the program reassembled successfully.
A special abnormal termination dump (High Level Assembler interrupt and diagnostic dump) follows the message. The statement causing termination is SETA, SETB, SETC, AGO, or AIF. The dump does not indicate which statement caused termination; however, it might show the last statement generated in the macro. The dump might also include contents of the assembler registers and work areas and other status information for use by IBM or your assembler maintenance programmers in determining the cause of the termination. However, it is not needed unless the error persists. This information could be helpful in diagnosing and fixing an assembler error.
Check the statement that caused termination. Rewrite the statement or split it into two or more statements. Reassemble the program; it should assemble correctly. However, if the error persists, there might be an assembler malfunction. Save the abnormal termination dump, the assembly listing (if one was produced), and the input source(s), and contact IBM for support.
20
The size of the dynamic storage area allocated for assembler buffer areas, tables, and work areas, as specified in the SIZE option, is not enough for the assembly to complete.
A special abnormal termination dump (High Level Assembler interrupt and diagnostic dump) follows the message. The dump usually indicates the statement being processed when the assembler determined there was not enough dynamic storage available to continue. Depending on where the error occurred, the assembly listing up to the statement being processed might also be produced. The other information in the dump, such as register and work area contents, is not needed.
Increase the value specified in the SIZE option, or split the assembly into two or more assemblies. Check for conditional assembly language loops in open code that could cause the symbol table to overflow.
20
The assembler attempted to acquire the amount of storage specified in the SIZE option, but there was not enough available storage in the region (z/OS), virtual machine (CMS), or partition GETVIS (z/VSE).
The assembly stops and no listing is produced.
Increase the region size (z/OS), the virtual machine size (CMS), or the partition GETVIS (z/VSE) size, or reduce the size requested in the SIZE option.
20
The SIZE option was specified as MAX-nnnK or MAX-nnM, but the amount of storage available to the assembler using this formula is not enough for the assembly to continue. The assembler requires a minimum of either 200K bytes or 10 times the work file blocksize, plus 20K, of working storage in the region (z/OS), virtual machine (CMS), or partition GETVIS (z/VSE) to proceed.
The assembly stops and no listing is produced.
Increase the region size (z/OS), virtual machine size (CMS), or the partition GETVIS (z/VSE) size, or reduce the amount of storage to be reserved in the MAX-nnnK or MAX-nnM form of the SIZE option.
20
The statement is too complex to be analyzed by the expression analysis routine of the assembler. It overflowed the analysis work area. The size of the analysis work area is the same as the work file block size. Normally, there is no problem with the assembler. The statement can be rewritten to simplify it, and the program reassembled successfully.
The assembly stops and a formatted abnormal termination dump is produced. The dump indicates which statement was being processed at the time of abnormal termination. It also includes the contents of the assembler registers and work areas and other status information that might be required by an IBM support representative if the problem persists.
Check the statement that was being processed at the time of abnormal termination. Rewrite the statement or split it into two or more statements. Alternatively, increase the work file block size. Reassemble the program; it should assemble correctly. However, if the problem persists, there might be a problem with the assembler. Save the abnormal termination dump, the assembly listing (if one was produced), and the input source(s), and contact IBM for support.
20
A difference has been detected between the symbol table and the location counter. The assembly stops and a special abnormal termination dump (High Level Assembler interrupt and diagnostic dump) is taken. The listing is not completed.
The High Level Assembler interrupt and diagnostic dump shows the statement that was being printed when the difference between the location counter and the symbol table was detected.
Reassemble the program using NOALIGN. If alignment is needed, use CNOP or DS to force alignment.
20
The assembly stops, because the assembler cannot find a COPY member that it has already read. This usually is caused by an error in the assembler itself or by an Operating System I/O error. Under certain conditions, however, the assembly can be rerun successfully.
A special abnormal termination dump (High Level Assembler interrupt and diagnostic dump) follows the message. The dump usually indicates which statement caused termination. It also might include contents of the assembler registers and work areas and other status information for use by IBM or your assembler maintenance programmers in determining the cause of the termination.
Reassemble the program; it might assemble correctly. If it does not reassemble without error, save the abnormal termination dump, the assembly listing (if one was produced), and the input source(s), and contact IBM for support.
20
The assembly was stopped because of a permanent I/O error on the data set indicated in the message. This is usually caused by a machine or an operating system error. The assembly usually can be rerun successfully. This message also appears on the console output device.
A special abnormal termination dump (High Level Assembler interrupt and diagnostic dump) follows the message. Depending on where the error occurred, the assembly listing up to the bad statement might also be produced. The dump usually indicates which statement caused termination. It also might include contents of the assembler registers and work areas and other status information for use by IBM or your assembler maintenance programmers in determining the cause of the termination.
If the I/O error is on SYSIN or SYSLIB, you might have concatenated the input or library data sets incorrectly. Make sure that all input or library data sets have the same device class (all DASD or all tape). Please also check that file attributes such as DSORG, RECFM, LRECL, and BLKSIZE have been correctly specified.
If the I/O error is on SYSUT1, check that SYSUT1 is allocated to a single volume--the assembler does not support a multivolume work file.
Reassemble the program; it might assemble correctly. If it does not reassemble without error, save the abnormal termination dump, the assembly listing (if one was produced), and the input source(s), and contact IBM for support. Also, if the program assembles correctly, submit a copy of the listing and input source(s) of the correct assembly.
20
[ Top of Page | Previous Page | Next Page | Contents | Index ]