Vax VC-1002 Spezifikationen

DIGITAL Visual FortranError MessagesDate: September, 1998Software Version: DIGITAL Visual Fortran Version 6.0, Standard and Professional EditionsOpera

Visual Fortran Run-Time Errors Page 7 of 48RECORDTYPE=’FIXED’ or ’VARIABLE’ in effect, or was created by a program written in a language other than Fo

NMAKE Messages Page 2 of 12NMAKE Fatal Error U1005syntax error : text must follow ’:’ in macroA string substitution was specified for a macro, but the

NMAKE Messages Page 3 of 12NMAKE Fatal Error U1024illegal argument to !CMDSWITCHESAn unrecognized command switch was specified. NMAKE Fatal Error U102

NMAKE Messages Page 4 of 12syntax error : too many names to left of ’=’Only one string is allowed to the left of a macro definition. NMAKE Fatal Error

NMAKE Messages Page 5 of 12NMAKE Fatal Error U1049macro or inline file too long (maximum : 64K)An inline file or a macro exceeded the limit of 64K. Re

NMAKE Messages Page 6 of 12A file by that name exists with a read-only attribute. The disk is full. NMAKE Fatal Error U1055out of environment spaceThe

NMAKE Messages Page 7 of 12NMAKE Fatal Error U1063missing macro name before ’=’A macro definition on the NMAKE command line contained an equal sign (=

NMAKE Messages Page 8 of 12Check the spelling of the target name. If targetname is a pseudotarget, specify it as a target in another description block

NMAKE Messages Page 9 of 12target macro ’target’ expands to nothingThe given target is an invocation of a macro that has not been defined or has a nul

NMAKE Messages Page 10 of 12NMAKE Fatal Error U1093cannot mix dot directivesMultiple dot directives cannot be specified on one line. The dot directive

NMAKE Messages Page 11 of 12Return to Main NMAKE Messages PageNMAKE Error U2001 through Warning U4011The following topics cover NMAKE Error U2001 thro

Visual Fortran Run-Time Errors Page 8 of 48FOR$IOS_INCRECTYP. The RECORDTYPE value in an OPEN statement did not match the record type attribute of the

NMAKE Messages Page 12 of 12Because the target was not specified in the .PRECIOUS list, NMAKE deleted the file. NMAKE Warning U4010’target’ : build fa

Profiler Errors PRF1005 through PRF4642 Page 1 of 7Profiler Errors PRF1005 through PRF46427KHIROORZLQJGHVFULSWLRQVFRYHU3URILOHU(UURUV35)

Profiler Errors PRF1005 through PRF4642 Page 2 of 7IDWDOHUURUFRPPRQILOHILOHQDPHKDVDQLQFRUUHFWROGVLJQDWXUH$3%,3%23%7B;(RUB//

Profiler Errors PRF1005 through PRF4642 Page 3 of 73URILOHU(UURU35)IDWDOHUURU35(3,ILOHQDPHLQYDOLGUXQWLPHUHORFDWLRQWU\UHOLQN7KH

Profiler Errors PRF1005 through PRF4642 Page 4 of 7WKHLQFRPLQJ3%7RU3%2ILOHV$OOSURILOHUVWHSVPXVWEHUXQRQWKHVDPHW\SHRIFRPSXWHU3URILOH

Profiler Errors PRF1005 through PRF4642 Page 5 of 7IDWDOHUURU352),/(1W6HW,QWHUYDO3URILOH17LQWHUQDOHUURUQXPEHURFFXUUHG$:LQGRZV17HUURU

Profiler Errors PRF1005 through PRF4642 Page 6 of 7FRYHUDJHSURILOLQJ3URILOHU(UURU35)ZDUQLQJFRPPRQQRHUURUILOH(VSHFLILHGIRU$

Profiler Errors PRF1005 through PRF4642 Page 7 of 735(3FRXOGQRWILQGWKHVSHFLILHGVWDUWIXQFWLRQHQWU\IXQFWLRQLQWKHPDSILOHVHH6)VZLWFK

Resource Compiler Messages Page 1 of 24Resource Compiler Messages-RCnThe following topics cover Resource Compiler Errors RC1000 through Warning RC4413

Resource Compiler Messages Page 2 of 24The specified option is not valid. Resource Compiler Fatal Error RC1008no input file specifiedOne or more sourc

Visual Fortran Run-Time Errors Page 9 of 48other operations on the logical unit may be performed between the READ and REWRITE statements. 55severe (5

Resource Compiler Messages Page 3 of 24Resource Compiler Fatal Error RC1018unexpected ’#elif’The #elif directive did not appear within an #if, #ifdef,

Resource Compiler Messages Page 4 of 24The program exceeded the maximum allowable nesting levels for #if and #ifdef directives. This error can be caus

Resource Compiler Messages Page 5 of 24Resource Compiler Fatal Error RC1110could not open filenameRC could not open the specified resource script file

Resource Compiler Messages Page 6 of 24The Specify Default Language (/l) option was specified, but was followed by an invalid hexadecimal language ID.

Resource Compiler Messages Page 7 of 24expected ’defined(id)’An identifier was expected after the left parenthesis following the specified preprocessi

Resource Compiler Messages Page 8 of 24Resource Compiler Error RC2017illegal escape sequenceAn escape sequence appeared where one was not expected. An

Resource Compiler Messages Page 9 of 24the file that contains the offending #pragma directive may not be immediately obvious. The #ifndef RC_INVOKED t

Resource Compiler Messages Page 10 of 24AUTOCHECK, AUTORADIO, BEDIT, CHECKBOX, COMBOBOX, CONTROL, CTEXT, DEFPUSHBUTTON, EDITTEXT, GROUPBOX, HEDIT, ICO

Resource Compiler Messages Page 11 of 24Resource Compiler Error RC2121BEGIN expected in menuThe BEGIN keyword must immediately follow the MENU keyword

Resource Compiler Messages Page 12 of 24#line expected a string containing the file name, found ’token’A #line directive was missing a required filena

Visual Fortran Run-Time Errors Page 10 of 48Number Severity Level, Number, and Message Text; Condition Symbol and Explanation61severe or info¹ (61): F

Resource Compiler Messages Page 13 of 24A CHARACTERISTICS resource must be a number. Resource Compiler Error RC2141invalid typeA different type was ex

Resource Compiler Messages Page 14 of 24Resource Compiler Error RC2151cannot re-use string constantsYou are using the same value twice in a STRINGTABL

Resource Compiler Messages Page 15 of 24expected macro formal parameterThe token following a stringizing operator (#) was not a formal parameter name.

Resource Compiler Messages Page 16 of 24Resource Compiler Error RC2175resource file filename is not in 3.00 formatThe specified resource used a format

Resource Compiler Messages Page 17 of 24Resource Compiler Warning RC4002too many actual parameters for macro ’identifier’The number of actual paramete

Resource Compiler Messages Page 18 of 24Check the syntax of the line containing the specified token. Resource Compiler Warning RC4093unescaped newline

Resource Compiler Messages Page 19 of 24The type of specified file is not known to the Resource Compiler. It was compiled as an 8-bit ASCII file. Retu

Resource Compiler Messages Page 20 of 24Resource Compiler Fatal Error RW1030Output ErrorThe output error can be caused by any of following conditions:

Resource Compiler Messages Page 21 of 24Accelerator type required (ASCII or VIRTKEY)The type field in the ACCELERATORS statement must contain either t

Resource Compiler Messages Page 22 of 24you have used a #define constant to specify the value and that the constant is spelled correctly. Expected num

Visual Fortran Run-Time Errors Page 11 of 48FOR$IOS_VFEVALERR². The value of a variable format expression was not within the range acceptable for its

Resource Compiler Messages Page 23 of 24have a #define statement for the control. Mismatched parenthesesMake sure you have closed every open parenthes

Resource Compiler Messages Page 24 of 24Resource Compiler Warning RW4004ASCII character not equivalent to virtual key codeA string literal was used fo

Visual Fortran Run-Time Errors Page 12 of 4877³severe (77): Subscript out of rangeFOR$IOS_SUBRNG. An array reference was detected outside the declared

Visual Fortran Run-Time Errors Page 13 of 48Run-Time Errors 120 Through 300This section describes in detail Visual Fortran run-time errors 120 through

Visual Fortran Run-Time Errors Page 14 of 48146¹severe (146): Null pointer error FOR$IOS_NULPTRERR. Attempted to use a pointer that does not contain a

Visual Fortran Run-Time Errors Page 15 of 48155¹severe(155): Array index out of bounds for index nn FOR$IOS_RANGE2. An array subscript is outside the

Visual Fortran Run-Time Errors Page 16 of 48FOR$IOS_PGM_BOUNDS. The program tried to access an array element that is outside the specified boundaries

Copyright Page Digital Equipment Corporation makes no representations that the use of its products in the mannerdescribed in this publication will not

Visual Fortran Run-Time Errors Page 17 of 48FOR$IOS_PGM_INPGERR. The program tried to access a page that was not present, so the system was unable to

Visual Fortran Run-Time Errors Page 18 of 48FOR$IOS_FLAWEDPENT. The Fortran run-time system detected a flawed Pentium® processor. Please contact Intel

Visual Fortran Run-Time Errors Page 19 of 48encountered during program execution was nn. This summary message appears at program completion.298¹info (

Visual Fortran Run-Time Errors Page 20 of 48FOR$IOS_F6098. The label assigned to the integer-variable name was not specified in the label list of the

Visual Fortran Run-Time Errors Page 21 of 48opened with FORM=’FORMATTED’ and ACCESS=’SEQUENTIAL’. 553severe (553): Terminal I/O not consistent with

Visual Fortran Run-Time Errors Page 22 of 48562severe (562): IOFOCUS option illegal with non-window unitFOR$IOS_F6211. IOFOCUS was specified in an OP

Visual Fortran Run-Time Errors Page 23 of 48This section describes in detail Visual Fortran run-time errors 570 through 614. In the following table, t

Visual Fortran Run-Time Errors Page 24 of 48575severe (575): Illegal SHARE valueFOR$IOS_F6309. An illegal value was used with the SHARE= option. SHA

Visual Fortran Run-Time Errors Page 25 of 48FOR$IOS_F6400. A BACKSPACE statement specified a unit connected to a terminal device such as a terminal or

Visual Fortran Run-Time Errors Page 26 of 48For example, consider you have a file LONG.DAT that is one continuous record with data fields separated by

ContentsThis document contains information on the following topics (this color denotes a link): oVisual Fortran Run-Time Messages oLinker Tools Messag

Visual Fortran Run-Time Errors Page 27 of 48605severe (605): Illegal structure for unformatted fileFOR$IOS_F6419. The file was opened with FORM=’UNFOR

Visual Fortran Run-Time Errors Page 28 of 48612severe (612): File not open for reading or file locked FOR$IOS_F6500. The program tried to read from a

Visual Fortran Run-Time Errors Page 29 of 48For example, consider the following: READ(*,*) I, J The preceding statement would cause this error if t

Visual Fortran Run-Time Errors Page 30 of 48625severe (625): Wrong number of array dimensionsFOR$IOS_F6513. In namelist input, an array name was quali

Visual Fortran Run-Time Errors Page 31 of 48634severe (634): D field exceeds W field in ES edit descriptorFOR$IOS_F6970. The specified decimal length

Visual Fortran Run-Time Errors Page 32 of 48FOR$IOS_F6985. To control interpretation of embedded and trailing blanks within numeric input fields, you

Visual Fortran Run-Time Errors Page 33 of 48commas or slashes (/). 651severe (651): %c or $: nonstandard edit descriptor in formatFOR$IOS_F6994. 652se

Visual Fortran Run-Time Errors Page 34 of 48Number Severity Level, Number, and Message Text; Condition Symbol and Explanation657severe (657): DIM argu

Visual Fortran Run-Time Errors Page 35 of 48length ’len’FOR$IOS_F6709. A substring ending position must be a positive integer variable or expression t

Visual Fortran Run-Time Errors Page 36 of 48(’size1’ and ’size2’)FOR$IOS_F6718. ORDER specifies the order of the array dimensions given in SHAPE, and

Visual Fortran Run-Time Errors Page 1 of 48Visual Fortran Run-Time ErrorsThis section describes Visual Fortran run-time error messages. For each error

Visual Fortran Run-Time Errors Page 37 of 48to the number of dimensions in the array to be shifted. That is, 1 <= DIM <= n, where n is the numbe

Visual Fortran Run-Time Errors Page 38 of 48In the following table, the first column lists error numbers returned to IOSTAT variables when an I/O erro

Visual Fortran Run-Time Errors Page 39 of 48rank ’rank’FOR$IOS_F6739. The optional argument DIM specifies the dimension along which to sum the element

Visual Fortran Run-Time Errors Page 40 of 48EOSHIFTFOR$IOS_F6746. The SHIFT argument to EOSHIFT must be either scalar or an array one dimension smalle

Visual Fortran Run-Time Errors Page 41 of 48711severe (711): INTEGER zero raised to zero powerFOR$IOS_F6756. Zero of any type (integer, real, or compl

Visual Fortran Run-Time Errors Page 42 of 48FOR$IOS_F6763. There is not enough memory space to hold a temporary array.Dynamic memory allocation is lim

Visual Fortran Run-Time Errors Page 43 of 48Dynamic memory allocation is limited by several factors, including swap file size and memory requirements

Visual Fortran Run-Time Errors Page 44 of 48FOR$IOS_F6773. There is not enough memory space to hold the automatic data object.Dynamic memory allocatio

Visual Fortran Run-Time Errors Page 45 of 48FOR$IOS_F6779. MOD(A,P) is computed as A - INT(A/P) * P. So, P cannot be zero.735severe (735): P argument

Visual Fortran Run-Time Errors Page 46 of 48741severe (741): Recursive i/o referenceFOR$IOS_F6786. 742severe (742): Argument to SHAPE intrinsic is not

Visual Fortran Run-Time Errors Page 2 of 48Default Run-Time Error ProcessingHandling Run-Time ErrorsLocating Run-Time ErrorsRun-Time Environment Varia

Visual Fortran Run-Time Errors Page 47 of 48POSITION= accepts the following values: ’ASIS’ (the default) ’REWIND’ - on Fortran I/O systems, this is th

Visual Fortran Run-Time Errors Page 48 of 48754severe (754): Illegal CARRIAGECONTROL= valueFOR$IOS_F6799. An illegal value was used with the CARRIAGE

Linker Tools Messages Page 1 of 32Linker Tools MessagesThe following topics cover linker tools errors and warnings (LNKnnnn), which can be generated L

Linker Tools Messages Page 2 of 32The version of MSPDBxx.DLL available on your system does not match the version required by this tool. Linker Tools E

Linker Tools Messages Page 3 of 32the problem. There may be a bad block on your disk. Although the operating system and disk hardware should have dete

Linker Tools Messages Page 4 of 32file in the input. Linker Tools Error LNK1117syntax error in option "option"The given option was not corre

Linker Tools Messages Page 5 of 32Linker miscalc (base relocations off by number)There was not enough space in the image to write base relocations. Li

Linker Tools Messages Page 6 of 32Linker Tools Error LNK1145/MERGE created circular link for section "section"You attempted to merge a secti

Linker Tools Messages Page 7 of 32The given symbol is reserved for use by LINK. Linker Tools Error LNK1156.sbss section not supportedAn object file co

Linker Tools Messages Page 8 of 32The build failed due to fixup errors. The /FORCE or /FORCE:UNRESOLVED option overrides this error. Linker Tools Erro

Visual Fortran Run-Time Errors Page 3 of 48Fortran run-time messages. 8severe (8): Internal consistency check failureFOR$IOS_BUG_CHECK. Internal error

Linker Tools Messages Page 9 of 32failed to /REBASE filenameThe rebase operation failed on the given file. Linker Tools Error LNK1177TOC size limit ex

Linker Tools Messages Page 10 of 32Your COFF object module is corrupt since it contains a relocation entry for an undefined static symbol. See Corrupt

Linker Tools Messages Page 11 of 32Linker Tools Error LNK1199invalid or corrupt import object: non-zero reserved fieldsThe import library has become c

Linker Tools Messages Page 12 of 32for an object file, recompile to recreate the PDB. Linker Tools Error LNK1210insufficient memory for incremental li

Linker Tools Messages Page 13 of 32Mismatched case in your code or module-definition (.DEF) file can cause LNK2001. For example, if you named a variab

Linker Tools Messages Page 14 of 32you don’t create an entrypoint to wWinMainCRTStartup. Use the /ENTRY option or type this value in the Project Setti

Linker Tools Messages Page 15 of 32When you are porting an application from 16 to 32 bits, LNK2001 can occur. The current 32-bit module-definition (.D

Linker Tools Messages Page 16 of 32more than one file but was changed between compilations. Recompile all files that include the symbol. The given sym

Linker Tools Messages Page 17 of 32However, if data is referenced in multiple modules, then the TOC space cannot be eliminated to save space. Linker T

Linker Tools Messages Page 18 of 32invalid version number "number"; default version assumedEither the major or the minor number in the speci

Visual Fortran Run-Time Errors Page 4 of 48An array variable was specified with too many or too few subscripts for the variable. An attempt was made t

Linker Tools Messages Page 19 of 32Linker Tools Warning LNK4022cannot find unique match for symbol "symbol"LINK or LIB found multiple matche

Linker Tools Messages Page 20 of 32Linker Tools Warning LNK4038displaying raw data in number units per lineThe /RAWDATA option was specified without a

Linker Tools Messages Page 21 of 32Linker Tools Warning LNK4045creating LINK_REPRO test case in dir "directory"The LINK_REPRO environment va

Linker Tools Messages Page 22 of 32the linker before library2. For example, library1 might contain an updated version of a function in library2. If yo

Linker Tools Messages Page 23 of 32cannot create map and/or checksum image; checksum set to 0This warning can occur if IMAGEHLP.DLL is not available.

Linker Tools Messages Page 24 of 32Linker Tools Warning LNK4076invalid incremental status file "filename"; linking nonincrementallyLINK cann

Linker Tools Messages Page 25 of 32Linker Tools Warning LNK4087CONSTANT keyword is obsolete; use DATAThis warning occurs if you use CONSTANT with your

Linker Tools Messages Page 26 of 32duplicate name "name" in order file; using last oneOrder files specify the order you want the linker to l

Linker Tools Messages Page 27 of 32The linker was unable to find your .PDB file. Copy it into the directory that contains object/library. Return to Ma

Linker Tools Messages Page 28 of 32"/option" not supported by this version of MSPDBxx.DLL; ignoredMSPDBxx.DLL does not support the specified

Visual Fortran Run-Time Errors Page 5 of 48This error is returned by END and ERRSNS. 25severe (25): Record number outside rangeFOR$IOS_RECNUMOUT. A di

Linker Tools Messages Page 29 of 32reference the library. The linker ignored the container. Linker Tools Warning LNK4546Mismatch in versions detected.

Linker Tools Messages Page 30 of 32exports changed; performing full linkOne or more exports were added or deleted since the last incremental linking s

Linker Tools Messages Page 31 of 32bss (uninitialized data) change; performing full linkA bss symbol was changed since the last incremental linking se

Linker Tools Messages Page 32 of 32A full link was required. The format of debugging information from Visual C++ version 4.0 or earlier. Code that was

BSCMAKE Messages BK1500 through BK4503 Page 1 of 4BSCMAKE Messages BK1500 through BK45037KHIROORZLQJGHVFULSWLRQVFRYHU%6&0$.((UURU%.

BSCMAKE Messages BK1500 through BK4503 Page 2 of 4UHSHDWWKHEXLOG7KHGLVNZDVIXOO$KDUGZDUHHUURURFFXUUHG7KHVSHFLILHGRXWSXWILOHKDGWKHVD

BSCMAKE Messages BK1500 through BK4503 Page 3 of 4QRQLQFUHPHQWDOXSGDWHUHTXLUHVDOO6%5ILOHV$QDWWHPSWZDVPDGHWREXLOGDQHZEURZVHLQIRUPDWLRQ

BSCMAKE Messages BK1500 through BK4503 Page 4 of 47KHZURQJILOHQDPHZDVVSHFLILHG7KHILOHZDVGHOHWHG(UURU%.ZLOOUHVXOW7KHILOHZDVFRU

C Run-Time Errors R6002 through R6025 Page 1 of 3C Run-Time Errors R6002 through R60257KHIROORZLQJGHVFULSWLRQVFRYHU&5XQ7LPH(UURUV5

C Run-Time Errors R6002 through R6025 Page 2 of 3&5XQ7LPH(UURU5QRWHQRXJKVSDFHIRUHQYLURQPHQW7KHUHZDVHQRXJKPHPRU\WRORDGWKHSURJUDP

Visual Fortran Run-Time Errors Page 6 of 48In the following table, the first column lists error numbers returned to IOSTAT variables when an I/O erro

C Run-Time Errors R6002 through R6025 Page 3 of 31RREMHFWKDVEHHQLQVWDQWLDWHGWRKDQGOHWKHSXUHYLUWXDOIXQFWLRQFDOO7KLVHUURULVFDXVHGE\FDO

CVPACK Messages CK1001 through CK4010 Page 1 of 4CVPACK Messages CK1001 through CK40107KHIROORZLQJGHVFULSWLRQVFRYHU&93$&.HUURU&.

CVPACK Messages CK1001 through CK4010 Page 2 of 4&93$&.)DWDO(UURU&.FDQQRWZULWHRXWSXWILOH7KHGLVNLVSUREDEO\IXOO7KLVHUURUOH

CVPACK Messages CK1001 through CK4010 Page 3 of 4&93$&.)DWDO(UURU&.FDQQRWRSHQSURJUDPGDWDEDVHSGEILOH&93$&.FRXOGQRWRSH

CVPACK Messages CK1001 through CK4010 Page 4 of 4GLVFDUGHGWKHUHFRUG7KHGHEXJJHUFDQUXQWKHUHVXOWLQJH[HFXWDEOHILOH+RZHYHUWKHV\PEROZLOOEH

CVTRES Messages CVT1100 through CVT4001 Page 1 of 2CVTRES Messages CVT1100 through CVT40017KHIROORZLQJGHVFULSWLRQVFRYHU&97WKURXJKZDU

CVTRES Messages CVT1100 through CVT4001 Page 2 of 2PDFKLQHW\SHQRWVSHFLILHGDVVXPHGW\SH&975(6GLGQRWILQGDPDFKLQHVSHFLILFDWLRQ,WDVVXPHG

Math Errors M6101 through M6205 (x86 only) Page 1 of 2Math Errors M6101 through M6205 (x86 only)7KHIROORZLQJGHVFULSWLRQVFRYHU0DWK(UURUV0WKU

Math Errors M6101 through M6205 (x86 only) Page 2 of 20DWK(UURU0VWDFNXQGHUIORZ$IORDWLQJSRLQWRSHUDWLRQUHVXOWHGLQDVWDFNXQGHUIORZRQWKH

NMAKE Messages Page 1 of 12NMAKE MessagesThe following topics cover NMAKE Error U1000 through Warning U4011: NMAKE Errors U1000 to U1049NMAKE Errors U