These two messages are output together.
A module not in the root overlay needs stack space, but the managed memory area already built into the module may be too small. Increase the parameter value for MM. From LOR. Class, caution.
LD060 - BECAUSE OF OVERLAY, MMLOC CHANGED TO BEFORE
The managed memory area must precede blank common for an overlay load. LOR had built the binary as if MMLOC were set to BEFORE. Correct the parameter value for MMLOC. From LOR. Class, caution.
LD062 - MIXED COMMON BLOCK USE: name The named common block has been used as both a regular common block and as a task common block. Correct the code so that only one type is used. From LOR. Class, fatal.
L0063 - MULTITASKING LIBRARIES NOT USED Task common blocks have been used in the application, but the libraries processed by LOR do not reference the control structure, iTASKCOM. Make sure that libraries of release level 1.13 or beyond are being used. From LOR. Class, fatal.
LD064 - RELOCAT. FIELD 22ND BIT SET, CAN'T RUN EMA: name
When building a binary on a machine with extended memory addressing, LOR has computed a 22-bit relocatable value for an 0'10, 0'11, 0'12, or 0'13 machine instruction such that the leftmost bit is set to one. Such an instruction will give bad results if run in extended mode. Options are:
• The binary can be run if EMA is turned OFF
• If the binary is reloaded with SEGLDR, a similar message may not result because of differences in storage allocations between the two loaders
• If the named module is CFT, recompile it with EMA turned ON
• If the named module is CAL, recode so that the relocatable expression is first loaded into an A-register, and then do the load or store based on the A-register
From LOR. Class, informative.
LD065 - CAN'T RUN EMA MODE & PROG. LENGTH
> 4MW
One or more instructions have been found that will give bad results if run in EMA mode, but the program length is greater than 4 megawords, and therefore cannot be run with EMA turned OFF. See message LD064 for more information and options.
From LOR. Class, fatal.
LD066 - CODE/LOCAL DATA IS GREATER THAN 4MW
A code and local data block is larger than 4 megawords in length. Change the source code so that large local data arrays are placed in common blocks. From LDR. Class, warning.
LDSOI - BAD DELIMITER FOLLOWING KEYWORD Syntax error in directive From LDR.
Class, fatal.
LOS02 - KEYWORD (name) UNKNOWN OR DUPLICATED
Correct the directive. From LDR. Class, fatal.
LDS03 - KEYWORD (name) MUST BE SPECIFIED Correct the directive. From LDR. Class, fatal.
LOS04 - KEYWORD (name) MUST BE EQUATED Correct the directive. From LDR. Class, fatal.
LDSOS - KEYWORD (name) CANNOT BE EQUATED COrrect the directive. From LDR. Class, fatal.
LDS06 - KEYWORD keyword VALUE OVERFLOWN WITH value
The value for the keyword is too big.
Correct the parameter value. See a Cray Research analyst. From LDR. Class, fatal.
LDS07 - CONTINUATION CARD NOT FOUND Correct the directive. From LDR. Class, fatal.
LD601 - DIRECTIVE (name) TERMINATOR MISSING
Correct the loader directive. From LDR.
Class, fatal.
LD602 - LITERAL SEPARATOR MISSING The beginning of a literal string was found but no data followed the
apostrophe. Correct the statement and reissue the request. From LDR. Class, .not reprievable.
LD603 - DIRECTIVE (name) TABLE OVERFLOW - USE CONTINUATION CARDS
From LDR. Class, fatal.
LD604 - DIRECTIVE (name) CONTAINS ILLEGAL CHARACTER
From LOR. Class, fatal.
LD60S - NO DIRECTIVE STATEMENT From LOR. Class, fatal.
MQOlO - MODSEQ, VERSION x.xx (mm/dd/yy) - TABLE CREATION RUN
The CREATE parameter was specified on the MODSEQ control statement. From MODSEQ.
Class, informative.
MQOll - n TRANSLATION-TABLE ENTRIES WRITTEN (CHECKSUM = x)
The n translation table entries are written with checksum = x. Save the checksum and compare it with the
corresponding value in the MQ02l message written during a resequencing run. From MODSEQ. Class, informative.
MQ012 - m SOURCE LINES, n DECKS COPIED FROM SR TO NSR
A MODSEQ creation run ended. From MODSEQ. Class, informative.
MQ013 - n GHOST NAMES STRIPPED FROM NSR Ghost deck names were found in columns 73-80 of some of the cards in the new source file (NSR) dataset. From MODSEQ.
Class, informative.
MQ020 - MODSEQ, VERSION x.xx (mrn/dd/yy) - RESEQUENCING RUN
Both the CREATE and REVERSE parameters are missing from the MODSEQ control statement. From MODSEQ. Class, informative.
MQ02l - n TRANSLATION-TABLE ENTRIES READ (CHECKSUM = x)
The input phase of a MODSEQ resequencing run ended. Compare the checksum to the corresponding value in the MQOll message written during the creation run. From MODSEQ. Class, informative.
MQ022 - m LINES, n DIRECTIVES TRANSLATED
A MODSEQ resequencing run ended. From MODSEQ. Class, informative.
MQ030 - MODSEQ, VERSION x.xx
(mm/dd/yy) - REVERSE RESEQUENCING RUN The CREATE parameter is missing from the MODSEQ control statement and the REVERSE parameter is present. From MODSEQ.
Class, informative.
MQ090 - n SOURCE LINES CONTAINED BAD SEQUENCE NUMBERS
One or more records in the old source file (SR) failed a test for a period in column 89. These records and possibly others contain missing or malformed UPDATE sequence numbers. If the number of source lines with bad sequence numbers equals the number of source lines read
(see message MQ012), the SR dataset is bad. Make sure the SR dataset is generated by UPDATE with the selected options S=sP, DW=80, and SQ. If the numbers reported by MQ012 and MQ090 are different, the SR dataset was modified;
some but not all sequence numbers were disturbed. From MODSEQ. Class, fatal.
MQlOO - nnn RESEQUENCING ERROR(S) DETECTED
One or more resequencing errors (MQlOl, MQl02, MQl03, MQl04, or MQlOS) were
detected'during a MODSEQ resequencing run. See the entries for the individual error messages. From MODSEQ. Class, caution.
MQlOl - DIRECTIVE nn ON LINE n. 10 NOT REPRESENTED IN' PL: ::c
A reference is made by an old mod to an 10 that is not present in the original PL. Correct the invalid directive, either before or after the MODSEQ resequencing run. From MODSEQ. Class, caution.
MQl02 - DIRECTIVE m ON LINE n.
NUMBER MISSING FROM PL: ::c
A reference is made by an old mod to a line number absent in the original PL
(although the 10 is present). Correct the invalid directive, either before or after the MODSEQ resequencing run. From MODSEQ. Class, caution.
MQl03 - DIRECTIVE d ON LINE 7,. RANGE SPANS DECKS: x~y
A deletion range begins and ends in two different decks, or the range is contained within one deck but the
beginning follows the end. The test that produces this message is suppressed if an MQlOl or an MQl02 error was detected in the same UPDATE directive. Correct the incorrect directive, either before or after the MODSEQ resequencing run. The correction might involve rewriting the mod. From MODSEQ. Class, fatal.
MQl09 - TRANSLATED LINE n TRUNCATED The translated directive requires more than 80 characters. All characters to the right of column 80 have been discarded. Examine the translated line carefully, because the translation might be correct. If it is incorrect, modify the old mod by omitting comments from the old line image. From MODSEQ. Class, fatal; not reprievable.
MQlll - THE SR DATASET CANNOT BE $IN OR
$OUT
The old source file (SR) was equated to an improper dataset name. Omit the parameter or equate it to a proper
dataset name. From MODSEQ. Class, fatal.
MQll2 - THE NSR DATASET CANNOT BE $IN OR
$OUT
The new source file (NSR) was equated to an improper dataset name. Omit the parameter or equate it to a proper
dataset name. From MODSEQ. Class, fatal.
MQl13 - THE TT DATASET CANNOT BE $IN OR
$OUT
The Translation Table (TT) parameter was equated to an improper dataset name.
Omit the parameter or equate it to a proper dataset name. From MODSEQ.
Class, fatal.
MQl14 - THE OM DATASET CANNOT BE $OUT The old mod (OM) parameter was equated to an improper dataset name. Omit the parameter or equate it to a proper
dataset name. From MODSEQ. Class, fatal.
MQllS - THE NM DATASET CANNOT BE $IN OR
$OUT
The new mod (NM) parameter was equated to an improper dataset name. Omit the parameter or equate it to a proper
dataset name. From MODSEQ. Class, fatal.
MQl16 - THE L DATASET CANNOT BE $IN The L parameter was equated to an improper dataset name. Omit the parameter or equate it to a proper
dataset name. From MODSEQ. Class, fatal.
MQl17 - THE E DATASET CANNOT BE $IN OR
$OUT
The E parameter was equated to an improper dataset name. Omit the parameter or equate it to a proper
dataset name. From MODSEQ. Class, fatal.
MQ12l - WARNING: NO SR FILE IS READ IN A RESEQUENCING RUN
The old source file (SR) parameter should have been omitted. Omit the parameter.
From MODSEQ. Class, caution.
MQ122 - WARNING: NO NSR FILE IS WRITTEN IN A RESEQUENCING RUN
The new source file (NSR) parameter specified should have been omitted. Omit the parameter. From MODSEQ. Class, caution.
MQ123 - WARNING: NO OM FILE IS READ IN A CREATION RUN
The old mod (OM) parameter should have been omitted. Omit the parameter. From MODSEQ. Class, caution.
MQ124 - WARNING: NO NM FILE IS WRITTEN IN A CREATION RUN
The new mod (NM) parameter should have been omitted. Omit the parameter. From MODSEQ. Class, caution.
MQ12S - WARNING: THE L FILE IS NOT USED IN A CREATION RUN
The L parameter should have been omitted. Omit the parameter. From MODSEQ. Class, caution.
MQ126 - WARNING: THE E FILE IS NOT USED IN A CREATION RUN
The E parameter should have been omitted. Omit the parameter. From MODSEQ. Class, caution.
MQ127 - WARNING: THE REVERSE KEYWORD IS IGNORED IN A CREATION RUN
The REVERSE parameter should have been omitted. Omit the parameter. From MODSEQ. Class, caution.
MQl31 - THE SR DATASET IS NOT LOCAL TO THE JOB
No Dataset Name Table exists for the old source file (SR) dataset. This dataset is required input for a creation run.
Examine the JCL for an error in misnaming or prematurely releasing the SR dataset.
If necessary, add an ACCESS or ACQUIRE statement. From MODSEQ. Class, fatal.
MQl32 - THE OM DATASET IS NOT LOCAL TO THE JOB
No Dataset Name Table exists for the old mod (OM) dataset. This dataset is
required input for a resequencing run.
Examine the job control language for an error in misnaming or prematurely releasing the OM dataset. If necessary, add an ACCESS or ACQUIRE statement. From MODSEQ. Class, fatal.
MQl33 - THE TT DATASET IS NOT LOCAL TO THE JOB
No Dataset Name Table exists for the Translation Table (TT) dataset, which is required input for a resequencing run.
Examine the job control language for an error in misnaming or prematurely releasing the TT dataset. If necessary, add an ACCESS or ACQUIRE statement. From MODSEQ. Class, fatal.
MQ141 - THE SR FILE DOES NOT BEGIN WITH THE MASTER CHARACTER, 'x'
The master character specified by the master character (MC) parameter (an asterisk by default) is incorrect, or the old source file specified by the old source file (SR) parameter contains incorrect data. Verify that the master character displayed in the message is correct. Examine the SR file to determine if it contains the correct UPDATE source cards. From MODSEQ.
Class, fatal.
MQ142 - THE OM FILE DOES NOT BEGIN WITH THE MASTER CHARACTER, 'x'
The master character (MC) parameter (an asterisk by default) is incorrect; or the OM parameter specifies an old mods file that contains incorrect data. Verify tha"t the master character displayed in the message is correct. Examine the OM file to determine if it contains the correct UPDATE mod decks. From MODSEQ.
Class, fatal.
MSOOI - DATASET dsname NOT FOUND Named input dataset to MODSET was not found. Correct the specified dataset name or verify that the dataset exists, and rerun MODSET. From MODSET. Class, fatal.
MS002 - L=O SPECIFICATION PREVENTS LISTING A LIST directive could not be implemented because L=O was specified on the control statement. Resubmit with the L control
statement parameter set to some local dataset. Omitting the L parameter will produce the listing on $OUT. From MODSET. Class, Warning
MS003 - AT LEAST 1 INPUT DATASET REQUIRED FOR MODS
The V, U, and A keywords are set to O.
Equate V, U, or A to a valid dataset name. From MODSET. Class, fatal; not reprievable.
MS004 - MODSET DIRECTIVE ERROR IN THE FOLLOWING RECORD:
A modset directive contained a string of more than eight non-blank characters.
MODSET ignored all but the first eight characters of the string. Recode the MODSET directive, insuring that all ident names and directive words (for example, LIST, OMIT) are blank-delimited. From MODSET. Class, warning.
PDOOO - PDN = pdn ID = id ED
=
ed OWN=
owne1"This is a header message for PDM
messages that follow. From PDM. Class, informative.
PDOOO - DATASET SAVE ON SCRATCH DEVICE dname
The dataset resides on a device which, after a system interruption, was specified as *SCRATCH. The SAVE is done. Site operations should be notified and the dataset copied to a non-*SCRATCH device. From PDM. Class, informative.
PDOOO - PREVIOUS EDITION EXISTS - ADN xxxxxxx IGNORED
On a SAVE or ACQUIRE, access control information was copied from the highest edition of the dataset, not from the specified Attributes Dataset Name xxxxxxx. From PDM. Class, informative.
PDOOO - UNABLE TO PROPAGATE DXT ATTRIBUTES The dataset being saved does not have DXT attributes propagated from the previous edition because of a DXT chain error.
See a Cray Research analyst. From PDM.
Class, informative.
PDOOO - n UNUSED BLOCKS RELEASED FOR CONTRACTING DATASET
The indicated dataset requires less space than it did previously. The excess blocks (n in the message) have been returned to the system for reuse. From PDM as the result of an ADJUST or RELEASE. Class, informative.
PDOOO - n ADDITIONAL BLOCKS ALLOCATED FOR EXPANDING DATASET
The indicated dataset requires more space than it did previously. In the message, n indicates the number of blocks by which it grew. From PDM as the result of an ADJUST. Class, informative.
PDOOO - xxx TAKEN FROM PREVIOUS EDITION - SPECIFIED VALUE IGNORED
On a SAVE or ACQUIRE, parameter xxx was specified with a value different from that found in the highest edition of the dataset. The value of the parameter xxx was copied from the highest
edition. From PDM. Class, informative.
PDOOl - DATASET NOT LOCAL TO JOB
A SAVE, DELETE, ADJUST, MODIFY, or DUMPTM request was issued to PDM, which could not find the local dataset specified in the ON parameter. Create the dataset, or recheck the dataset name. From PDM.
Class, informative.
PD002 - MAINTENANCE PERMISSION NOT GRAN.TED
• SAVE request: The user attempted to save a dataset with control words that did not match those of the previous edition.
• DELETE request: The requester did not supply the proper maintenance control word when the dataset was accessed in order to delete the dataset; or the requester did not supply the UQ parameter on the ACCESS statement.
Specify the correct maintenance control word on the request, or gain unique access. From PDM. Class, informative.
PD003 - EDITION ALREADY EXISTS
A request to SAVE a specific edition of a dataset was issued and a dataset with the specified edition already exists. Delete the saved edition and reissue the request or change the edition parameter. From PDM. Class, informative.
PD004 - DSC FULL
PDM has no room in the Dataset Catalog to save or update the new information.
Consult a Cray Research analyst. From PDM. Class, informative.
PDOOS - INVALID FUNCTION CODE
The function code given in the POD is out of range, or a queue that was neither
input nor output was given for an EQSDT request. Correct the function code.
From PDM. Class, informative.
PD006 - LOCAL DATASET NAME IS ALREADY IN USE
A job tried to access a permanent dataset, but the specified local name
(ON) is being used for another local dataset. Use a different local name.
From PDM. Class, informative.
PD007 - NO PERMISSION GRANTED
• ACCESS statement: The requested permission did not match the SAVE permission.
• MODIFY statement: One of the three permission control words did not match. Specify the correct value for the requested permission.
From PDM. Class, informative.
PD009 - DATASET NOT FOUND
An attempt was made to access a dataset that does not exist in the permanant dataset base. If an ACQUIRE was issued, this is a normal informative message, indicating that the dataset specified to be transferred from the front end was first searched for on a Cray disk. Check PDN and 10 to ensure that the correct dataset is being accessed. From PDM.
Class, informative.
PD010 - EDITION NOT FOUND An attempt was made to access a nonexistent edition of a permanent dataset. Check editions for this permanent dataset. From PDM. Class, informative.
PD012 - DATASET NOT PERMANENT A request was made to either DELETE, ADJUST, or MODIFY a local dataset that is not permanent. Access the dataset before attempting to delete, adjust, or modify.
From PDM. Class, informative.
PD013 - PDN 16 CHARACTERS LONG OR CONTAINS UNPRINTABLE CHARACTERS
The Permanent Dataset Name on a SAVE or MODIFY request either has more than 15 characters or contains unprintable characters (that is, octal codes 000-037 or 177-377). If this was encountered from a control statement, the station translation tables might be at fault;
check with a Cray site analyst. For CFT internal or CAL macro calls, check the PDN your program is supplying for the POD. From PDM. Class, informative.
PD014 - CONTINUATION ERROR
The Dataset Catalog contains erroneous data. See a Cray Research analyst. From PDM. Class, informative.
POOlS - OAT FULL
The system pool does not have room to move the dataset's disk allocation information. If the error recurs, consult a Cray Research analyst. From PDM. Class, informative.
PD018 - DATASET ALREADY ACCESSED BY JOB An attempt was made to access a dataset that is already accessed. Either release the dataset before attempting to access it, or remove the second access. From PDM. Class, informative.
PD02l - SPECIFIED DATASET IS EMPTY An attempt was made to change or create a permanent dataset having no disk
allocation assigned to it. This message only occurs for datasets that do not meet the conditions for closing the dataset described in the CRAY-OS Version 1 Reference Manual, publication SR-OOll.
For such a dataset, the user must manually force a flushing of the buffer.
From PDM. Class, informative.
PD025 - NO DATASET NAME IN PDD
A request was made in which neither the DN nor the PDN parameter was selected.
Correct the parameters. From PDM.
Class, informative.
PD026 - ACCESS CONTROL WORD VALIDATION ERROR
On an ACCESS or ACQUIRE, the read, write, or maintenance control word specified did not match the one saved in the Dataset Catalog entry for the requested dataset.
From PDM. Class informative.
PD027 - NOTES LENGTH EXCEEDS MAXIMUM ALLOWABLE
On a SAVE, ACQUIRE, or MODIFY, the specified NOTE is longer than the maximum
(480 characters). From PDM. Class, informative.
PD027 - MULTIPLE EDITIONS EXIST
An attempt was made to change one of the permission control words for a permanent dataset that has more than one edition.
All corresponding permission control words must match for all editions. From PDM. Class, informative.
PD028 - NO UNIQUE ACCESS ON SYSDIR A unique access was attempted on a dataset that is also entered into the system directory. From PDM. Class, informative.
PD029 - TEXT LENGTH IS ZERO
On a SAVE, ACQUIRE, or MODIFY, a TEXT address was specified, but no length was
On a SAVE, ACQUIRE, or MODIFY, a TEXT address was specified, but no length was