CLASS X: IMPLEMENTATION DEPENDENT FEATURES
ERROR MESSAGES FOR MAJOR CLASSIFICATION
CLASSIFICATION “V” ERRORS ARE RELATED TO COMPILE-TIME VARIABLE ERRORS VA1 - SEVERITY 2
COMPILE TIME INTEGER/SCALAR ADDITION FAILED.
DURING COMPILE TIME, AN OVERFLOW OR UNDERFLOW OCCURRED. INTERMEDIATE CODE HAS GENERATED RUNTIME EXECUTABLE CODE FOR ADDITION. THIS TAKES PLACE BECAUSE ALTHOUGH THE HOST MACHINE WAS NOT ABLE TO HANDLE THE CALCULATIONS, IT IS
PRESUMED THE TARGET COMPUTER MAY HAVE THE CAPABILITY.
VA2 - SEVERITY 2
COMPILE-TIME INTEGER/SCALAR SUBTRACTION FAILED
SAME AS ABOVE, BUT FOR SUBTRACTION
VA3 - SEVERITY 2
COMPILE TIME INTEGER/SCALAR MULTIPLICATION FAILED
SAME AS ABOVE, BUT FOR MULTIPLICATION
VA4 - SEVERITY 2
COMPILE-TIME INTEGER/SCALAR DIVISION FAILED
SAME AS ABOVE, BUT FOR DIVISION
VA5 - SEVERITY 2
COMPILE-TIME INTEGER/SCALAR EXPONENTIATION FAILED
SAME AS ABOVE, BUT FOR EXPONENTIATION
VC1 - SEVERITY 2
COMPILE-TIME CATENATION PRODUCED TOO LONG A CHARACTER STRING - TRUNCATED TO 255 CHARACTERS
CHARACTER LITERALS AND VARIABLES MAY NOT HAVE A LENGTH GREATER THAN 255.
VE1 - SEVERITY 2
AN EXPRESSION NOT COMPUTABLE AT COMPILE-TIME HAS BEEN USED IN A CONTEXT WHERE A VALUE MUST BE KNOWN
ALL VALUES SPECIFIED IN DECLARE STATEMENTS, FOR INSTANCE, AS WELL AS THE WIDTHS OF ALL SUBSCRIPT PARTITIONS, MUST BE COMPUTABLE AT COMPILE TIME.
VF1 - SEVERITY 2
HAL/S-FC User’s Manual USA003090 32.0/17.0
B -68 November 2005
ERROR MESSAGES FOR MAJOR CLASSIFICATION X
CLASSIFICATION “X” ERRORS DEAL WITH IMPLEMENTATION DEPENDENT FEATURES NOTE: OCCURS EITHER BECAUSE THE FUNCTION WAS GIVEN CONSTANTS FOR ARGUMENTS, OR THE ARGUMENTS ARE OUTSIDE ALLOWABLE VALUES
XA1 - SEVERITY 2
ONLY ONE PROGRAM IDENTIFICATION DIRECTIVE IS ALLOWED IN A COMPILATION UNIT.
EACH COMPILATION UNIT MAY RECEIVE, AT MOST, ONE PROGRAM IDENTIFICATION NAME FOR THE PURPOSE OF ACCESS CONTROL.
XA2 - SEVERITY 2
THE PROGRAM IDENTIFICATION DIRECTIVE DOES NOT CONTAIN A VALID IDENTIFICATION. THE DIRECTIVE MUST BE OF THE FORM: D PROGRAM ID=<ID>
THE <ID> FIELD MUST CONSIST OF A 1 TO 8 CHARACTER IDENTIFYING NAME.
XA3 - SEVERITY 2
A PROGRAM IDENTIFICATION DIRECTIVE MUST APPEAR FOLLOWING ANY EXTERNAL TEMPLATES AND PRIOR TO THE BEGINNING OF THE PRIMARY UNIT OF COMPILATION. THE CURRENT DIRECTIVE IS OUT OF PLACE AND WILL NOT BE PROCESSED.
SEE U.G.-SECTION 5.2
XD1 - SEVERITY 2
UNINTELLIGIBLE INFORMATION IN DEVICE DIRECTIVE
THE DEVICE DIRECTIVE MUST TAKE THE FORM OF: “D DEVICE CHANNEL = N <OPTION>” WHERE N SPECIFIES THE CHANNEL INVOLVED (0-9), AND <OPTION> MAY BE PAGED, UNPAGED, OR EMPTY.
XD2 - SEVERITY 2
DUPLICATE DEVICE DIRECTIVE FOR CHANNEL ??
NO MORE THAN ONE DEVICE DIRECTIVE SHOULD BE SPECIFIED FOR EACH CHANNEL USED IN A COMPILATION UNIT.
XD3 - SEVERITY 2
DEVICE DIRECTIVE DOES NOT CONTAIN A VALID CHANNEL INDICATION
THE CHANNEL SPECIFIED MUST BE IN THE RANGE FROM 0-9.
XD4 - SEVERITY 2
CHANNEL NUMBERS MUST BE IN RANGE 0 TO 9 XD5 - SEVERITY 2
DEFINE DIRECTIVE DOES NOT CONTAIN A NAME
EVERY DEFINE DIRECTIVE, USED TO SPECIFY A LOCAL MEMBER OF AN INCLUDE LIBRARY, MUST GIVE THIS MEMBER A NAME. SEE U.G. - SECTION 5.2
XD6 - SEVERITY 2
CLOSE ?? DOES NOT MATCH NAME ON DEFINE DIRECTIVE
THE CLOSE DIRECTIVE MUST USE THE SAME NAME AS THE OPENING DEFINE DIRECTIVE. U.G. - SECTION 5.2
XD7 - SEVERITY 1
DEFINE SEQUENCE IS EMPTY
THE DEFINE DIRECTIVE IS IMMEDIATELY FOLLOWED BY A CLOSE DIRECTIVE.
XD8 - SEVERITY 2
DEFINE DIRECTIVES NOT ALLOWABLE FROM INCLUDED SEQUENCE
XD9 - SEVERITY 1
A DEFINE DIRECTIVE WITH THE NAME ?? ALREADY EXISTS AND WILL BE REPLACED
NON-EMPTY DEFINE DIRECTIVES MAY NOT HAVE THE SAME NAME.
XI1 - SEVERITY 2
NESTED INCLUDE DIRECTIVES NOT ALLOWED
SEE U.G.-SECTION 5.2. THE NESTED DIRECTIVE IS IGNORED.
XI10 - SEVERITY 1
?? NOT FOUND IN SDF LIBRARY XI11 - SEVERITY 1
WARNING--UNIT NAME ON INCLUDE CARD DIFFERS FROM THAT IN THE SDF: ??
POSSIBLY TWO COMPILATION UNITS HAVE THE SAME FIRST 6 CHARACTERS, OR THE UNIT NAME WAS MISSPELLED.
XI12 - SEVERITY 2
ILLEGAL TO INCLUDE A TEMPLATE WITHIN A DEFINE SEQUENCE--INCLUDE IGNORED XI2 - SEVERITY 2
INCLUDE DIRECTIVE DOES NOT CONTAIN A NAME
THE INCLUDE DIRECTIVE MUST EITHER SPECIFY OR IMPLY A NAME FOR THE INCLUDE’D UNIT, USING THE D INCLUDE <NAME> OR THE D INCLUDE TEMPLATE <UNIT NAME> FORMATS, RESPECTIVELY. SEE U.G.-SECTION 5.2. THE DIRECTIVE WILL BE IGNORED.
XI3 - SEVERITY 2
?? NOT IN INCLUDE LIBRARY
INCLUDE DIRECTIVES MUST SPECIFY UNITS TO BE INCLUDE’D WHICH ARE AVAILABLE IN A SYMBOLIC LIBRARY, DEFINED BY THE APPROPRIATE JCL. SEE U.G.-SECTION 5.2
XI4 - SEVERITY 2
‘REMOTE’ KEYWORD ONLY ALLOWED ON ‘INCLUDE TEMPLATE’ DIRECTIVES
THE KEYWORD, ‘REMOTE’ IS ILLEGAL IN THE INCLUDE SDF DIRECTIVE.
XI5 - SEVERITY 2
‘REMOTE’ KEYWORD SPECIFIED ON NON-COMPOOL TEMPLATE
CODE BLOCKS CANNOT BE REMOTE, ONLY DATA MAY BE.
XI6 - SEVERITY 2
STRUCTURE ?? NOT IN SDF
A STRUCTURE TEMPLATE NAME CONTAINED IN THE VARIABLE LIST FORM OF THE INCLUDE DIRECTIVE WAS NOT FOUND IN THE INCLUDED SDF.
XI7 - SEVERITY 2
SYMBOL ?? NOT IN SDF
A SYMBOL NAME CONTAINED IN THE VARIABLE LIST FORM OF THE INCLUDE SDF DIRECTIVE WAS NOT FOUND IN THE INCLUDED SDF.
XI8 - SEVERITY 2
ILLEGAL TO INCLUDE UNQUALIFIED STRUCTURE TERMINAL ?? FROM AN SDF-INCLUDE THE APPROPRIATE STRUCTURE TEMPLATE AND STRUCTURE VARIABLE INSTEAD
HAL/S-FC User’s Manual USA003090 32.0/17.0
B -70 November 2005
XI9 - SEVERITY 1
?? WAS FOUND IN SDF LIBRARY, BUT IT WAS CREATED BY A VERSION OF THE COMPILER NOT SUPPORTING SDF INCLUDES.
THE INCLUDED MODULE SHOULD BE RECOMPILED BY A LATER VERSION OF THE COMPILER TO ALLOW ITS SDF TO BE INCLUDED.
XM1 - SEVERITY 2
?? IS A NONEXISTENT %MACRO
THE ONLY LEGAL %MACROS ARE SVC, NAMECOPY, NAMEADD, NAMEBIAS, AND COPY. (NAMEADD AND NAMEBIAS ARE ILLEGAL FOR BFS)
XM10 - SEVERITY 2
ARGUMENT OF %MACRO HAS ILLEGAL MULTIPLE NAME COPYNESS XM2 - SEVERITY 2
?? HAS AN INCORRECT NUMBER OF ARGUMENTS
THE SVC %MACRO ACCEPTS 1 ARGUMENT; NAMECOPY ACCEPTS 2; COPY TAKES 2 OR 3, NAMEBIAS ACCEPTS 2, AND NAMEADD TAKES 3. SEE U.G.-SECTION 8.7
XM3 - SEVERITY 2
ARGUMENT OF %MACRO MAY NOT BE A LITERAL XM4 - SEVERITY 2
ARGUMENT OF %MACRO HAS ILLEGAL TYPE
THE ARGUMENTS TO NAME COPY MUST EACH BE STRUCTURES.
XM5 - SEVERITY 2
ARGUMENT OF %MACRO MAY NOT BE A VARIABLE
THE ARGUMENT MUST BE A NAME VARIABLE.
XM7 - SEVERITY 2
ARGUMENT OF %MACRO MAY NOT POSSESS ARRAYNESS XM8 - SEVERITY 2
ARGUMENT OF %MACRO MAY NOT BE A VARIABLE WITH THE TEMPORARY ATTRIBUTE XM9 - SEVERITY 2
ARGUMENT OF %MACRO POSSESSES ILLEGAL SUBSCRIPTING
A %MACRO IS SUBJECT TO THE SAME RESTRICTIONS AS SUBSCRIPTION OR WHEN BEING USED AS ASSIGN PARAMETERS FOR PROCEDURE ARGUMENTS. NAMEBIAS ACCEPTS NO
SUBSCRIPTS.
XQ101 - SEVERITY 2
ATTEMPTED AN ILLEGAL STACK WALKBACK LOOP FOR VARIABLE??
THIS SITUATION ARISES WHEN ONE PROCEDURE BLOCK IS TRYING TO INDIRECTLY LOCATE A STACK VARIABLE IN AN OUTER BLOCK. INSTEAD, PASS THE VARIABLE TO THE NESTED
PROCEDURE.
XQ102 - SEVERITY 2
ATTEMPT TO ASSIGN NAME OF REMOTE DATA ITEM TO A 16 BIT NAME VARIABLE. XR1 - SEVERITY 2
THE DATA_REMOTE DIRECTIVE MUST BE PLACED BEFORE THE PROGRAM/PROCEDURE STATEMENT. THE DIRECTIVE IS IMPROPERLY PLACED AND WILL NOT BE PROCESSED. XR2 - SEVERITY 2
XR3 - SEVERITY 1
THE REMOTE ATTRIBUTE IS IGNORED FOR NON-NAME VARIABLES WHEN THE DATA_REMOTE DIRECTIVE IS IN EFFECT.
XR4 - SEVERITY 2
THE FOLLOWING DATA_REMOTE FCOS RESTRICTION WAS ENCOUNTERED: ??
(REFERENCE: HALS-FC COMPILER SYSTEM SPECIFICATION, USA003089, SECTION 4.1.3.4 FOR MORE INFORMATION)
XR5 - SEVERITY 2
THE REMOTE ATTRIBUTE IS ONLY SUPPORTED FOR NAME VARIABLES OR FORMAL PARAMETERS WHEN SDL OPTION IS ON. TO PLACE DECLARED DATA IN A REMOTE SECTOR, USE DATA_REMOTE OR INCLUDE A COMPOOL REMOTE.
SEE SECTION 8.12 FOR MORE INFORMATION
XS1 - SEVERITY 1
THE FOLLOWING FUNCTION IS NOT IMPLEMENTED IN THE CURRENT LANGUAGE SUBSET: ??
XS2 - SEVERITY 1
THE ABOVE CONSTRUCT IS NOT IMPLEMENTED IN THE CURRENT LANGUAGE SUBSET. (VIOLATION AT PRODUCTION ??)
XS3 - SEVERITY 1
ATTEMPT TO INVOKE UNVERIFIED RUNTIME LIBRARY ROUTINE ?? XU1 - SEVERITY 2
D CARD CONTAINS UNKNOWN DIRECTIVE
THE ONLY LEGAL DIRECTIVES ARE DEVICE, INCLUDE, PROGRAM, VERSION, EJECT, SPACE, DEFINE, AND CLOSE. THE DIRECTIVE NAME MUST BE THE FIRST WORD TO FOLLOW THE D IN COLUMN 1
XV1 - SEVERITY 2
LAST LINE OF TEMPLATE LIBRARY MEMBER ?? IS NOT A VALID VERSION DIRECTIVE
A D VERSION STATEMENT IS EITHER MISSPELLED OR THE TEMPLATE DOES NOT HAVE ONE TO BEGIN WITH
HAL/S-FC User’s Manual USA003090 32.0/17.0
B -72 November 2005