input dataset (default is $BLD) before all of the expected binary text or Program Descriptor Table was read. The input file probably does not contain binary load modules. Examine the job control language for errors. From ADSTAPE. Class, fatal.
AD004 - COMPILATION ERRORS
The binary load modules on the input dataset (default is $BLD) contain assembly or compilation errors. Correct the errors; if this is not feasible, add a DEBUG parameter to the associated APML statements to allow use of the binary modules with errors; reassemble. From ADSTAPE. Class, fatal.
ALOOI - OAL DATASET MUST BE SPECIFIED The dataset specified by the user as the OAL dataset does not exist. (The OAL dataset default is $OAL.) Correct the control statement and resubmit the job.
From BIND. Class, fatal.
AL002 - BUFFER IN UNEXPECTED STATUS (stat)
The status returned by BUFFERIN is not one of the status values expected by the program. Make sure that the OAL dataset is not corrupt. (If it can be processed by ITEMIZE and BUILD, it is probably acceptable.) Save the relevant dataset, job stream, and listing; see a Cray Research analyst. From BIND pass 1 processing, subroutine READPDT. Class, fatal.
AL003 - WRONG TABLE TYPE (type) The first loader table in an object record was not a PDT table. The octal digits in the message indicate the table type that was encountered. Make sure that the OAL dataset is not corrupt.
Save the relevant dataset, job stream, and listing; see a Cray Research analyst. From BIND pass 1 processing, subroutine READPDT. Class, fatal.
AL004 - TOO MUCH TRAILER INFORMATION (tinfo)
The trailer information in the PDT is too long for a BIND internal buffer. (See figure PDT-7 in the COS Table
Descriptions Internal Reference Manual, publication SM-004S. Trailer information is labeled PDT header data.) Make sure that the OAL dataset is not corrupt. If the trailer information is longer than 1024 words, additional space can be created by a change in the definition of parameter WORKSZ in the UPDATE comdeck ALWORK. (The actual size of the trailer information is given as a decimal number enclosed in parentheses in the message.) From BIND pass 1 processing, subroutine READPDT. Class, fatal.
ALOOS - TOO MUCH EXTERNAL INFORMATION (extinfo)
The external information in the PDT is too long for a BIND internal buffer.
Make sure that the OAL dataset is not corrupt. If the external information is longer than 1024 words, additional space can be created by a change in the definition of parameter WORKSZ in the UPDATE comdeck ALWORK. The actual size of the external information is given as a decimal number enclosed in parentheses in the message. From BIND pass 1
processing, subroutine READPDT. Class, fatal.
AL006 - UNEXPECTED STATUS READING HEADER (iostat)
BIND was unable to read a loader table during pass 2 processing. This condition
is abnormal because the dataset was read successfully during pass 1. See a Cray Research analyst. From BIND pass 2 processing, subroutine PASS2. Class, fatal.
AL007 - UNDEFINED TABLE TYPE type BIND encountered an undefined table type or a misplaced PDT-type table during pass 2 processing. (The table type is given in the two octal digits in the message.) This condition is abnormal because the dataset was successfully read during pass 1. See a Cray Research analyst. From BIND pass 2 processing, subroutine PASS2. Class, fatal.
AL008 - UNEXPECTED STATUS READING TABLE BODY iostat
BIND was unable to read the body of a table during pass 2 processing. This condition is abnormal because the dataset was successfully read during pass 1. See a Cray Research analyst. From BIND pass 2 processing, subroutine PASS2. Class, fatal.
AL009 - BUFFERIN UNEXPECTED STATUS (stat)
The status returned by BUFFERIN is not one of the status values expected by the program. This condition is abnormal because the dataset was read successfully during pass 1. See a Cray Research analyst. From BIND pass 2 processing, subroutine READPDT2. Class, fatal.
ALOIO - WRONG TABLE TYPE (type) The first loader table in an object record was not a PDT table. The octal digits in the message indicate the table type encountered. This condition is abnormal because the dataset was read successfully during pass 1. See a Cray Research analyst. From BIND pass 2 processing, subroutine READPDT2. Class, fatal.
ALOll - TOO MUCH ENTRY INFORMATION (entinfo)
The entry information in the PDT is too long for a BIND internal buffer. Make sure that the OAL dataset is not corrupt. If the entry information is longer than 1024 words, additional space can be created by a change in the definition of parameter WORKSZ in the UPDATE comdeck ALWORK. (The actual size of the entry information is given as a decimal number enclosed in parentheses in the message.) (Unlike messages AL009, ALOIO, and AL012, it is reasonable for this message to occur during pass 2 processing because pass 1 does not check this information.) From BIND pass 2 processing, subroutine READPDT2. Class, fatal.
AL012 - TOO MUCH EXTERNAL INFORMATION (extinfo)
The external information in the PDT is too long for a BIND internal buffer.
This condition is abnormal because the dataset was read successfully during pass 1. See a Cray Research analyst. From BIND pass 2 processing, subroutine READPDT2. Class, fatal.
AL013 - UNIMPLEMENTED BLOCK INDEX REFERENCE
BIND can handle only block indices 0 and 2. Any other block index value, such as a common block reference, produces this message. Your APML source must not use common blocks. Revise the APML program.
From BIND pass 2 processing, subroutine TXT2. Class, fatal.
AL014 - TXT TABLE INVALID
The Q bit was set in a TXT table. See the COS Table Descriptions Internal Reference Manual, publication SM-004S.
See a Cray Research analyst. From BIND pass 2 processing, subroutine TXT2.
Class, fatal.
ALOIS - TABLE tbL IS NOT IMPLEMENTED BIND encountered a loader table type that it cannot process. These table types are DMT, DIR, SMT, and USR. Make sure that the OAL dataset is not corrupt. Revise the APML source or the APML control statement to avoid unimplemented table types. From BIND. Class, fatal.
AL016 - BIND VERSION vsn
Initiation of BIND. From BIND. Class, informative.
AL017 - TOO MUCH BLOCK INFORMATION (bUnfo)
The block information in the PDT is too long for a BIND internal buffer. Make sure that the OAL dataset is not corrupt. If the block information is longer than 1024 words, additional space can be created by a change in the definition of parameter WORKSZ in the UPDATE comdeck ALWORK. (The actual size of the block information is given as a decimal number enclosed in parentheses in
the message.) From BIND pass 1
processing, subroutine READPDT. Class, fatal.
AL018 - n FIELD OVERFLOWS
When external references were being resolved, at least one external value would not fit in the receiving field.
The number in the message is the count of occurrences of this problem. See a Cray Research analyst. From BIND. Class, caution.
AL019 - a DBL DEFS b UNDEFINED e USES
One or more undefined or doubly-defined symbols were encountered during
processing.
a Number of doubly-defined symbols b Number of undefined symbols
referenced
e Number of references to undefined symbols
Correct the APML source and resubmit.
From BIND. Class, caution.
AL020 - ATTEMPT TO FREE UNALLOCATED BLOCK A call to routine DSFREE atempted to free an unallocated block of dynamic memory.
This should never occur. Save the relevant files and listings; see a Cray Research analyst. From BIND, subroutine DSFREE. Class, fatal.
AL021 - OUT OF STORAGE SPACE
DSGET was unable to satisfy a memory allocation request. Your program probably contains too many external symbols. BIND must be recompiled to correct this. The size of dynamic memory is defined in common deck CDSMEM with the parameter MEMSIZE. Increasing the value of the MEMSIZE parameter increases the dynamic storage available. From BIND, routine DSGET. Class, fatal.
AL022 - DSINIT PARAMETER ERROR
DSINIT was given an excessive parameter value for dynamic storage space. This should never occur. Save relevant files and listing; see a Cray Research
analyst. From BIND, routine DSINIT.
Class, fatal.
NOTE
Message classes for AP and CA messages, issued by APML and CAL, are different from those for other messages. The classes and meanings are as follows.
Abort: CAL or APML aborts Fatal: if the ABORT option is
off, the PDT fatal error flag is set. If the ABORT option is on, CAL or APML aborts when assembly of all modules in the current input is complete.
Warning: a possible error was detected, but no action is taken.
Informative: information only;
does not imply that any problem exists.
APOOO - [APML] INTERNAL 'APML' ERROR DETECTED AT P
=
paddressAPML detects an internal error at parcel address paddress and is unable to proceed. See a Cray Research analyst.
From APML. Class, abort (immediate).
APOOI - [APML] APML VERSION x.xx (mm/dd/yy) - epu
At the beginning of each assembly, APML issues an informative message indicating
the version number x.xx, the date mm/dd/yy on which APML was
assembled, and the opu that APML is assembling for. From APML. Class, informative.
AP002 - [APML] ASSEMBLY TIME: n CPU SECONDS
All programs in the current file of the source dataset have been assembled. n is the assembly time in floating-point CPU seconds. From APML. Class, informative.
AP003 - [APML] MEMORY WORDS: /7lJ + I/O BUFFERS: bw
All programs in the current file of the source dataset have been assembled. mw is the decimal number of memory words required in the user portion of the job field. bw is the decimal number of words needed for the I/O table and buffer area of this job step. From APML.
Class, informative.
AP004 - [APML] ASSEMBLY ERRORS If the user set the ABORT flag on the APML control statement and fatal errors were encountered during assembly, then APML will issue this message followed by an abort. Either remove the ABORT flag from the APML control statement or correct all fatal errors found by APML.
From APML. Class, abort.
aLternative fopms:
APOIO - [APML] 1 WARNING ERROR, PROGRAM MODULE pn
APOIO - [APML] n WARNING ERRORS, PROGRAM MODULE pn
APML issues this message for all source lines, from the previous program module (if any) through program module pn, in which warning errors have been detected.
pn will be equivalent to the name used on a particular IDENT pseudo statement.
Examine all warning errors and correct if necessary. See Appendix D of the APML Assembler Version 1 Reference Manual, CRI publication SM-0036, for a list of warning errors. From APML. Class, warning.
aLternative fopms:
APOll - [APML] 1 FATAL ERROR, PROGRAM MODULE pn
APOll - [APML] n FATAL ERRORS, PROGRAM MODULE pn
APML issues this message for all source lines, from the previous program module (if any) through program module pn, in which fatal errors have been detected.
pn will be equivalent to the name used on a particular IDENT pseudo statement.
Correct all fatal errors. See the APML Assembler Version 1 Reference Manual, CRI publication SM-0036, for a list of fatal errors. From APML. Class, fatal.
AP012 - [APML] MISSING IDENT STATEMENT An END pseudo on the source dataset occurred before an IDENT pseudo
instruction was found. Check the source dataset for matching IDENT and END pseudo instructions. From APML. Class, warning.
AP013 - [APML] MISSING END STATEMENT, PROGRAM MODULE pname
On the source dataset, an end of file occurred before an END pseudo instruction corresponding to the IDENT pseudo in program module pname. pname will be equivalent to the name used on that IDENT pseudo statement. Check the source dataset for matching IDENT and END pseudo instructions. From APML. Class, warning.
AP014 - [APML] EMPTY SOURCE FILE, DN
=
dname
An end of file or end of data was encountered on the source dataset before any source statements. Check the job control statements and the source dataset for a problem that causes a null file.
From APML. Class, warning.
aLternative fopms:
AP015 - [APML] 1 LINE EXCEEDS 90 CHARACTERS, DN = dn
AP015 - [APML] n LINES EXCEED 90 CHARACTERS, DN
=
dnThe given number of records in the named dataset contain more than 90 characters.
The most typical cause is UPDATE sequence numbers extending past column 90. (APML truncates the long records to 90
characters.) This message can also be issued when a binary dataset is
erroneously read. If the records exceed 90 characters, it might be possible to break up the long records with
continuation lines. From APML. Class, warning.
AP016 - [APML] OPEN ERROR, DN
=
dn The dataset dn was not found in the user's local environment or in the system directory. Access or create the dataset dn. From APML. Class, abort.AP017 - [APML] INVALID CPU TYPE SPECIFIED: opu
The invalid CPU parameter opu was passed on the APML control statement.
Correct the CPU type on the APML job control statement. From APML. Class, warning.
AP030 - [APML] BAD BINARY TEXT, ON
=
dn, (ERROR CODE=
00)An error was discovered in the binary system text dn. Following are the error codes and their meanings:
Code
P l
Meaning Prologue field BSTTT ~ 1 P2P3
prologue field BSTWC < LE@BSTPR EOR was encountered while prologue was being read
Code P4
Hl
H2 H3 H4 Ml
Meaning
EOF, EOD, or null record was encountered while the prologue was being read
EOF, EOD, or null record was encountered while a sub table header was being read
Header field BSTTT ~ 1 Header field BSTWC < 1
Header field BSTID is not recognized EOR was encountered while TMDF was being read
M2 EOF, EOD, or null record was encountered while TMDF was being read
M3 Length of TMDF entry < 0 M4 Length of TMDF entry
=
0M5 Global word count exceeded during TMDF processing
Sl EOR was encountered while TSYM entry was being read
S2 EOR, EOD, or null record was encountered while TSYM entry was being read
S3 Global word count was exceeded during TSYM processing
El Epilogue field BSTWC ~ 1 E2 Global word count ~ sum of
subtable word counts Do one of the following:
• Generate a new binary system text from the original source system text and rerun the job with the new binary system text.
• Rerun the job, replacing the binary system text with the source system text.
• Show the listing and DSDUMP output of the invalid binary system text to a Cray Research analyst.
From APML. Class, fatal.
AP031 - [APML] symbol DOUBLY-DEFINED IN BINARY TEXT dn
The named symbol is defined in the named binary system text but was defined differently in a previous system text.
Remove one of the definitions from the source system texts, generate a new binary system text, and resubmit job.
From APML. Class, fatal.
AP032 - [APML] MACRO opsyn NOT FOUND, BINARY TEXT dn
The named binary system text contains an OPSYN directive of the form name OPSYN opsyn, but no macro or pseudo-op with the name opsyn is known to the assembler. Do one of the following:
• Correct the spelling of opsyn.
• Remove the OPSYN from the named system text.
• Define the opsyn macro in a previous system text or before the OPSYN directive in the named system text. From APML. Class, fatal.
AP033 - [APML] MACRO mn REDEFINED IN BINARY TEXT dname
A definition for the named macro appears in the named dataset, but the macro has been previously defined. If the redefinition is intentional, the new definition will be used; otherwise, remove the unwanted macro definition.
From APML. Class, warning.
AROOO - BAD CALL TO ARLIB ERROR PROCESSOR The $ARLIB error message processor was entered with an illegal error message code. See a Cray Research analyst. From
$ARLIB. Class, 2; user abort;
reprievable.