Nastran Dmap Error Message List

Transcript

1 Overview of Error Messages NX Nastran displays User Information, Warning, and Error messages in the printed output. The amount of information reported in a message is controlled by system cell 319. When 319=0, only message summaries are reported. When 319=1, the full messages are reported. User messages typically indicate problems with the input file. Corrective action is often indicated er input file in the message text. Refer to the NX Nastran Quick Reference Guide for prop formats. Warning and information messages appear at various places in the output. Fatal messages will cause the program to terminate. These messages will appear at the end of the output. Nastran output. The format of these Operating system specific messages can appear in the NX messages will vary with the operating system. You should refer to your operating system manuals for interpretation of these messages. Nastran Dmap Error Message List - 999 1000 - 1999 0 2000 - 2999 3000 3999 4000 - 4999 5000 - 5999 - - 7000 - 7999 6999 8000 - 8999 6000 9000 - 9999 10000 - 10999 20000 - 21999 22000 22999 - *** USER FATAL MESSAGE %1 (%2) 1.0 *** USER WARNING MESSAGE %1 (%2) 2.0 *** USER INFORMATION MESSAGE %1 (%2) 3.0 *** SYSTEM FATAL MESSAGE %1 (%2) 4.0 *** SYSTEM WARNING MESSAGE %1 (%2) 5.0 *** SYSTEM INFORMATION MESSAGE %1 (%2) 6.0 *** USER FATAL MESSAGE 7 (XGPIDG) 7.0 ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2 PARAMETER NO. %3 NEEDS PARAMETER NAME User information: The parameter is not in correct format. *** USER WARNING MESSAGE 7 (XGPIDG) 7.1 POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2 PARAMETER NO. %3 NEEDS PARAMETER NAME *** USER FATAL/WARNING MESSAGE 8 (XGPIDG) 8.0 BULK DATA PARAM CARD ERROR - MUST NOT DEFINE PARAMETER NAMED %1. User inf ormation:

2 In DMAP, the "N" in V,N %1 or in TYPE PARM,A,B,N means user cannot set the value of the parameter with name %1 on a PARAM entry. In DMAP, when defining a parameter, the "N" in V,N %1 means %1 on a PARAM user cannot set the value of the parameter with name entry in Bulk Data. *** USER FATAL MESSAGE 9 (XGPIDG) 9.0 ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2 VALUE NEEDED FOR PARAMETER NO. %3 User information: The constant needs value in a DMAP instruction or on a PARAM entry. here is a parameter in the referenced DMAP instruction which must have a value assigned before the execution of the module. *** USER WARNING MESSAGE 9 (XGPIDG) 9.1 POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2 VALUE NEEDED FOR PARAMETER NO. %3 *** USER FATAL MESSAGE 10 (XGPIDG) 10.0 ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2 ILLEGAL INPUT DATA BLOCK SPECIFICATION. User information: Too many or too few inputs are specified in the input for the ref erenced module. *** USER WARNING MESSAGE 10 (XGPIDG) 10.1 POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2 ILLEGAL INPUT DATA BLOCK SPECIFICATION. *** USER FATAL MESSAGE 11 (XGPIDG) 11.0 ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2 ILLEGAL OUTPUT DATA BLOCK SPECIFICATION. *** USER WARNING MESSAGE 11 (XGPIDG) 11.1 POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2 ILLEGAL OUTPUT DATA BLOCK SPECIFICATION. *** USER FATAL/WARNING MESSAGE 12 (XGPIDG) 12.0 ERROR IN DMAP INSTRUCTION NO. %1, ILLEGAL CHARACTER IN DMAP INSTRUCTION NAME. User information: - numeric characters, the first The name of a module must be alpha ot allowed. character being alphabetic. Special characters are n For example DMAP names like "8MOD" or "SETI=2" are not allowed.. *** USER FATAL/WARNING MESSAGE 13 (XGPIDG) 13.0 ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2 DMAP INSTRUCTION NOT IN MODULE LIBRARY. User information: The named DMAP refers to a non - existent module name. Check spelling.

3 *** SYSTEM FATAL MESSAGE 14 (XGPIDG) 14.0 ARRAY NAMED %1 OVERFLOWED System information: See XGPI module description in MFD section of NX NASTRAN Programmer's Manual. The usual cause is insufficient open core. In other cases, it may be necessary to divide the DMAP sequence into subDMAPs. *** SYSTEM FATAL MESSAGE 14 (XGPIDG) 14.1 ARRAY NAMED %1 OVERFLOWED AT DMAP INSTRUCTION NO. %2. *** USER FATAL MESSAGE 15 (XGPIDG) 15.0 ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2 INCONSISTENT LENGTH USED FOR PARAMETER NAMED %3 User information: This parameter was used in a previous DMAP instruction which gave it a different type. DMAP Module Dictionary. See the NX NASTRAN *** USER WARNING MESSAGE 15 (XGPIDG) 15.1 POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2 INCONSISTENT LENGTH USED FOR PARAMETER NAMED %3 *** USER FATAL MESSAGE 16 (XGPIDG) 16.0 ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2 ILLEGAL FORMAT User information: Usually caused by early termination such as a LABEL statement without a NAME. *** USER WARNING MESSAGE 16 (XGPIDG) 16.1 CTION NO.%2 POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRU ILLEGAL FORMAT User information: Usually caused by early termination such as a LABEL statement without a NAME. *** USER/SYSTEM FATAL/WARNING/INFORMATION MESSAGE 17 17.0 (EVLMSG) SYMBOL "%1" IS UNDEFINED USER FATAL MESSAGE 18 (XGPIDG) *** 18.0 ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2 TOO MANY PARAMETERS IN DMAP PARAMETER LIST User information: Incorrect calling sequence for DMAP instruction. Compare the DMAP statement to the description in the NX NASTRAN DMAP Module Dictionary or the NX NASTRAN Programmer's Manual to find the error. *** USER WARNING MESSAGE 18 (XGPIDG) 18.1 POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2

4 TOO MANY PARAMETERS IN DMAP PARAMETER LIST User information: Inco rrect calling sequence for DMAP instruction. Compare the DMAP statement to the description in the NX NASTRAN DMAP Module Dictionary or the NX NASTRAN Programmer's Manual to find the error. *** USER FATAL/WARNING MESSAGE 19 (XGPIDG) 19.0 ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2 LABEL NAMED %3 IS MULTIPLY DEFINED. User information: LABEL named appears in more than one place in DMAP program. *** USER FATAL MESSAGE 20 (XGPIDG) 20.0 EXTRANEOUS 'ELSE' / 'ELSEIF' STATEMENT AT INSTRUCTION %1 *** USER FATAL MESSAGE 22 (CDBDP1) 22.0 DATABLOCK NAMED %1 MUST BE DEFINED PRIOR TO THIS INSTRUCTION USER ACTION: CHECK FOR CORRECT SPELLING, OR MISSING TYPE STATEMENT, AND RERUN. User info rmation: A common mistake is to forget that DMAP statements DMIIN and DTIIN are required to read DMI and DTI matrices, respectively. Note that RF24D41 requires a DTIIN command. *** USER FATAL MESSAGE 22 (XGPIDG) 22.1 ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2 DATA BLOCK NAMED %3 MUST BE DEFINED PRIOR TO THIS INSTRUCTION *** USER WARNING MESSAGE 22 (XGPIDG) 22.2 POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2 DATA BLOCK NAMED %3 MUST BE DEFINED PRIOR TO THIS INSTRUCTION *** USER FATAL MESSAGE 23 (XGPIDG) 23.0 ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2 DATA BLOCK NAMED %3 IS NOT REFERENCED IN SUBSEQUENT FUNCTIONAL MODULE *** USER WARNING MESSAGE 23 (XGPIDG) 23.1 POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2 DATA BLOCK NAMED %3 IS NOT REFERENCED IN SUBSEQUENT FUNCTIONAL MODULE *** SYSTEM FATAL/WARNING MESSAGE 24 (XGPIDG) 24.0 CANNOT FIND DATA BLOCK NAMED %1 ON DATA POOL TAPE System information: The contents of /XDPL/ do not match contents of Pool Tape. *** USER FATAL MESSAGE 25 (XGPIDG) 25.0 ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2

5 PARAMETER NAMED %3 HAS AN INCONSISTENT USER AUTHORIZATION User information: Parameter is referenced in nonfunctional module, but is nowhere defined. An example is COND LBL,X where X is not a variable parameter in a module before this statement. *** USER WARNING MESSAGE 25 (XGPIDG) 25.1 POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2 PARAMETER NAMED %3 HAS AN INCONSISTENT USER AUTHORIZATION *** USER FATAL MESSAGE 26 (XGPIDG) 26.0 ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2 LABEL NAMED %3 NOT DEFINED User information: LABEL name does not appear in LABEL instruction. For example a COND,XXX statement appears without a LABEL,XXX statement. *** USER WARNING MESSAGE 26 (XGPIDG) 26.1 POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2 LABEL NAMED %3 NOT DEFINED User information: LABEL name does not appear in LABEL instruction. For example a COND,XXX statement appears without a LABEL,XXX statement. *** USER FATAL/WARNING MESSAGE 27 (XGPIDG) 27.0 LABEL NAMED %1 NOT REFERENCED User information: LABEL na me appears only in a LABEL instruction. It is not necessary to reference a LABEL. *** USER FATAL MESSAGE 32 (XGPIDG) 32.0 ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2 DATA BLOCK NAMED %3 MUST BE DEFINED PRIOR TO THIS INSTRUCTION USER WARNING MESSAGE 32 (XGPIDG) *** 32.1 POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2 DATA BLOCK NAMED %3 MUST BE DEFINED PRIOR TO THIS INSTRUCTION *** SYSTEM FATAL/WARNING MESSAGE 34 (XGPIDG) 34.0 CANNOT TRANSLATE DMAP INSTRUCTION NO. %1 System information: Error in subroutine XSCNDM. *** SYSTEM FATAL/WARNING MESSAGE 36 (XGPIDG) 36.0 CANNOT FIND DATA BLOCK NAMED %1 ON OLD PROBLEM TAPE

6 *** USER FATAL MESSAGE 37 (XGPIDG) 37.0 ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2 MAY NOT BE ENOUGH FILES AVAILABLE FOR ARNING ONLY - W MODULE REQUIREMENTS FILES NEEDED = %3 FILES AVAILABLE = %4 *** USER WARNING MESSAGE 37 (XGPIDG) 37.1 POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2 MAY NOT BE ENOUGH FILES AVAILABLE FOR - WARNING ONLY MODULE REQUIREMENTS FILES NEEDED = %3 FILES AVAILABLE = %4 *** SYSTEM FATAL MESSAGE 38 (XGPIDG) 38.0 NOT ENOUGH CORE FOR GPI TABLES. System information: The user must break up DMAP program. *** SYSTEM FATAL/WARNING MESSAGE 39 (XGPIDG) 39.0 RIGID FORMAT DMAP SEQUENCE DOES NOT CORRESPOND TO MED TABLE System information: The MED Table must have the same number of entries as there are DMAP instructions in DMAP sequence. Can be caused by having more than one END DMAP statement. *** USER FATAL/WARNING MESSAGE 40 (XGPIDG) 40.0 ERROR IN ALTER DECK - CANNOT FIND END OF DMAP INSTRUCTION User information: The user should check the ALTER part of the Executive Control Section. *** SYSTEM FATAL/WARNING MESSAGE 41 (XGPIDG) 41.0 TABLES INCORRECT FOR REGENERATING DATA BLOCK %1 System information: File Name Table and MED Table used by routine XFLDEF are wrong. The e user can compensate by altering OUT and IN module(s) which regenerat the data block. *** USER FATAL MESSAGE 42 (XGPIDG) 42.0 ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2 PARAMETER NAMED %3 ALREADY HAD VALUE ASSIGNED PREVIOUSLY *** USER WARNING MESSAGE 42 (XGPIDG) 42.1 POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2 PARAMETER NAMED %3 ALREADY HAD VALUE ASSIGNED PREVIOUSLY User information: A DMAP instruction is attempting to assign a default value to a parameter that appears in a previous instruction which as signed it a value.

7 *** USER/SYSTEM FATAL/WARNING/INFORMATION MESSAGE 43 43.0 (EVLMSG) "%1" IS INVALID *** USER FATAL MESSAGE 45 (XGPIDG) 45.0 ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2 DATA BLOCK NAMED %3 ALREADY APPEARED AS OUTPUT OR WAS USED AS INPUT BEFORE BEING DEFINED *** USER WARNING MESSAGE 45 (XGPIDG) 45.1 POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2 DATA BLOCK NAMED %3 ALREADY APPEARED AS OUTPUT OR WAS USED AS INPUT BEFORE BEING DEFINED *** USER FATAL/WARNING MESSAGE 46 (XGPIDG) 46.0 INCORRECT REENTRY POINT *** USER FATAL MESSAGE 47 (XGPIDG) 47.0 ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2 THIS INSTRUCTION CANNOT BE FIRST INSTRUCTION OF LOOP *** USER WARNING MESSAGE 47 (XGPIDG) 47.1 POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2 THIS INSTRUCTION CANNOT BE FIRST INSTRUCTION OF LOOP *** USER FATAL MESSAGE 48 (XGPIDG) 48.0 ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2 DATA SET %3 IS A LWAYS REGENERATED, THEREFORE IT WILL NOT BE CHECKPOINTED *** USER WARNING MESSAGE 48 (XGPIDG) 48.1 POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2 DATA SET %3 IS ALWAYS REGENERATED, THEREFORE IT WILL NOT BE CHECKPOINTED *** SYSTEM FATAL/WARNING MESSAGE 49 (XGPIDG) 49.0 MPL TABLE (MODULE PROPERTIES LIST) IS INCORRECT System information: The error is in common block /XGP12/. *** SYSTEM FATAL/WARNING MESSAGE 49 (XGPIDG) 49.1 MPL TABLE (MODULE PROPERTIES LIST) IS INCORRECT DECIMAL LOCATION RELATIVE TO MPL(1) = %1,MODULE NAME = %2 *** SYSTEM FATAL/WARNING MESSAGE 50 (XGPIDG) 50.0 CANNOT FIND JUMP OSCAR ENTRY NEEDED FOR THIS RESTART *** SYSTEM FATAL MESSAGE 51 (XGPIBS) 51.0 NOT ENOUGH OPEN CORE FOR XGPIBS ROUTINE System information: Additional core memory is required to compile DMAP or rigid format. *** SYSTEM FATAL MESSAGE 52 (XGPIDG) 52.0

8 NAMED COMMON /XLINK/ IS TOO SMALL System information: rd in LINK table for every entry in MPL. There must be one wo *** USER FATAL MESSAGE 53 (XGPIDG) 53.0 INCORRECT FORMAT IN ABOVE CARD User information: The link specification updated data (DIAG 28, 29, 30) is incorrect. *** USER FATAL MESSAGE 55 (XGPIDG) 55.0 THE "SUBDMAP" KEYWORD CAN BE USED ONLY ONCE PER SUBDMAP User information: Check your DMAP to be sure that each subDMAP has only one "SUBDMAP" statement and also that each one has an "END" statement. *** SYSTEM FATAL MESSAGE 57 (XGPI) 57.0 ATE MPL NAME ENCOUNTERED. NAME = %1 DUPLIC *** SYSTEM FATAL MESSAGE 58 (CSPACE) 58.0 THE OSCAR REGION OF OPEN CORE IS INSUFFICIENT FOR DMAP CODE EXPANSION PROGRAMMER INFORMATION: LOSCAR = %1 *** USER FATAL MESSAGE 59 (CIFTHN) 59.0 ENDIF AT DMAP STATEMENT # %1 IS MISSING AN IF THEN STATEMENT *** USER FATAL MESSAGE 60 (CIFTHN) 60.0 IF THEN AT DMAP STATEMENT # %1 IS MISSING AN ENDIF STATEMENT *** USER FATAL MESSAGE 61 (CIFTHN) 61.0 AN EXTRA "ELSE" STATEMENT EXISTS AT DMAP STATEMENT %1 *** USER FATAL MESSAGE 63 (CBRNCH) 63.0 %1 AT DMAP NO. %2 IS ILLEGALLY BRANCHING INTO OR OVERLAPS AN "IF THEN", "DO WHILE", OR "REPT" *** USER FATAL MESSAGE 64 (CBRNCH) 64.0 DMAP STATEMENT %1 ATTEMPT TO JUMP BACKWARDS AT *** USER FATAL MESSAGE 65 (CDOWCH) 65.0 NO MATCHING DO WHILE FOR ENDDO AT DMAP STATEMENT %1 *** USER FATAL MESSAGE 66 (CDOWCH) 66.0 INSUFFICIENT CORE AVAILABLE FOR DO WHILE PROCESSING IN DMAP COMPILER *** USER FATAL MESSAGE 67 (CSYNTX) 67.0 DMAP STRUCTURE HAS MISMATCHED NUMBER OF IF THEN AND ENDIF STATEMENTS *** USER FATAL MESSAGE 68 (CSYNTX,CDOWHC) 68.0

9 THE NUMBER OF %1 STATEMENTS IS LESS THEN THE NUMBER OF %2 STATEMENTS. *** USER FATAL MESSAGE 69 (CGPIB) 69.0 SUBDMAP STATEMENT PARAMETER %1 NOT DEFINED *** USER WARNING MESSAGE 70 (CGPIB) 70.0 TYPE STATEMENT PARAMETER %1 NOT IN VPS TABLE MUST BE A CODE LOGIC ERROR FOR THIS TO HAPPEN *** USER FATAL MESSAGE 71 (CDOWHI) 71.0 SYNTAX ERROR IN ABOVE DO WHILE STATEMENT *** USER FATAL MESSAGE 72 (CCALL,CMESAG,CPARM2) 72.0 PARAMETER SYNTAX ERROR IN ABOVE STATEMENT. PARAMETER IS %1 ERROR CODE = %2 --- User information: If the value of a param eter is allowed to change in the called subDMAP, then it must be specified as S,XXXXX, where XXXXX is the parameter name. If it is specified as S,N,XXXXX, then error code 2 will occur pointing to a parameter named N. on a CALL subDMAP statement, then If a parameter field is left blank error code 2 will be improperly issued pointing to the last parameter in the command preceding the blank field. The correction for this is to place either a parameter name or value in the blank field. ER FATAL MESSAGE 73 (CCALL,CMESAG,CPARM2) *** US 73.0 THE PARAMETER NAMED %1 IS UNDEFINED *** USER FATAL MESSAGE 74 (CPARM2) 74.0 PARAMETER SYNTAX ERROR IN ABOVE STATEMENT IN PARAMETER POSITION NUMBER %1 *** USER FATAL MESSAGE 75 (CIFTHN) 75.0 ELSE AT DMAP STATEMENT # %1 APPEARS BEFORE AN ELSE IF THEN STATEMENT *** SYSTEM FATAL MESSAGE 76 ( ) 76.0 A PROGRAM INTERNAL LIMIT RELATING TO CALL STATEMENTS HAS BEEN EXCEEDED. USER INFORMATION: THIS LIMIT DEPENDS ON THE TOTAL NUMBER OF ARGUMENTS SPECIFIED ON ALL THE CALL STATEMENTS BEEN COMPILED IN THIS RUN. USER ACTION: REDUCE THE NUMBER OF CALL STATEMENTS OR THE NUMBER OF ARGUMENTS ON THE CALL STATEMENTS. PROGRAMMER ACTION: INCREASE THE SIZE OF VARIABLE MAXCAL AND ARRAY CALLS OF COMMON BLOCK CCALL1. *** USER WARNING MESSAGE 81 (CFLORD) 81.0 DATABLOCK %1 IS DECLARED APPEND ON A FILE STATEMENT

10 AND IS ALSO SPECIFIED AS OUTPUT ON AN EQUIV OR EQUIVX STATEMENT AT STATEMENT NO.%2. USER INFORMATION: THIS MAY LEAD TO UNPREDICTABLE AND/OR ERRONEOUS RESULTS. SEE THE EQUIVX MODULE DESCRIPTION IN THE NX NASTRAN DMAP MODULE dICTIONARY. *** USER FATAL MESSAGE 100 (NDDL) 100.0 THE ABOVE CARD HAS AN INCORRECT FORMAT. ERROR CODE= %1 *** SYSTEM FATAL MESSAGE 101 (NDDL) 101.0 INCORE LIST OF DEPENDENCY CARDS HAS OVERFLOWED AVAILABLE OPEN CORE SPACE AVAILABLE OPEN CORE WORDS IS %1 -- INCORE LIST OF DEPENDENCY CARDS HAS OVERFLOWED AVAILABLE OPEN CORE SPACE AVAILABLE OPEN CORE WORDS IS %2 -- -- 12 WORDS ARE NEEDED FOR EACH DEPENDENCY CARD IN NDDL *** SYTEM FATAL MESSAGE 102 (NDDL) 102.0 INSUFFICIENT STORAGE SPACE FOR NDDL DEFINED QUALIFIERS - - NUMBER OF QUALIFIERS CURRENTLY LIMITED TO %1 ** USER FATAL MESSAGE 103 (NDDL) * 103.0 INSUFFICIENT OPEN CORE TO HOLD NDDL DATA BLOCK DESCRIPTION FOR %1 -- AVAILABLE OPEN CORE WORDS IS %2 *** USER FATAL MESSAGE 104 (NDDL) 104.0 INSUFFICIENT STORAGE SPACE FOR NDDL PATH CARDS STORAGE SPACE LIMITED TO %1 PATH CARDS -- *** USER FATAL MESSAGE 105 (NDDL) 105.0 'PATH=' KEYWORD NOT FOUND ON NDDL DATA BLOCK STATEMENT FOR %1 *** USER FATAL MESSAGE 106 (NDDL) 106.0 NDDL PATH NAME = %1 ON DATA BLOCK STATEMENT FOR %2 HAS NOT BEEN DEFINED *** USER FATAL MESSAGE 107 (NDDL) 107.0 INSUFFICIENT OPEN CORE SPACE FOR NDDL PARAMETER CARD TABLE -- AVAILABLE OPEN CORE IN WORDS IS %1 -- EACH PARAMETER REQUIRES 9 WORDS OF THIS STORAGE SPACE *** USER FATAL MESSAGE 108 (NDDL) 108.0 NDDL PATH NAME = %1 ON DATA BLOCK STATEMENT FOR %2 HAS NOT BEEN DEFINED

11 *** USER FATAL MESSAGE 109 (NDDL) 109.0 NO NDDL DEPENDENCY CARDS FOUND *** USER FATAL MESSAGE 110 (NDDL) 110.0 A QUALIFIER NAMED %1 USED ON A PATH CARD HAS NOT BEEN DEFINED *** USER FATAL MESSAGE 111 (NDDL) 111.0 INSUFFICIENT STORAGE SPACE FOR NDDL PATH CARDS PROGRAMMER ACTION: INCREASE ARRAY PATHTB AND MAXDB USER ACTION: DECREASE NUMBER OF PATHS AND/OR NUMBER OF QUALIFIERS ON PATH CARDS. STORAGE SPACE LIMITED TO %1 WORDS. EACH PATH REQUIRES ((2 * #QUALIFIERS) +1) WORDS. *** SYSTEM FATAL MESSAGE 112 (NDDL) 112.0 ABLE SIZE OF THE PVA TABLE EXCEEDS THE MAXIMUM ALLOW %1. PROGRAMMER ACTION: INCREASE THE SIZE OF PVATB ARRAY. *** USER FATAL MESSAGE 113 (NDDL) 113.0 INVALID LOGICAL ASSIGNMENT ATTEMPTED IN NDDL DESCRIPTION *** USER FATAL MESSAGE 114 (NDDL) 114.0 INVALID ASSIGNMENT OF TRUE OR FALSE ATTEMPTED IN NDDL DESCRIPTION *** USER FATAL MESSAGE 115 (NDDL) 115.0 THE DATA BLOCK DESCRIPTION FOR %1 IS MISSING THE 'LOCATION= KEYWORD *** USER FATAL MESSAGE 116 (NDDL) 116.0 LOCATION PARAMETER= %1 IS UNDEFINED FOR PARAMETER= %2 *** USER FATAL MESSAGE 116 (NDDL) 116.1 LOCATION PARAMETER= %1 IS UNDEFINED FOR DATA BLOCK= %2 *** SYSTEM FATAL MESSAGE 117 (NDDL) 117.0 THE PATH VALUE TABLE HAS OVERFLOWED. THE NUMBER OF PATHS IN THIS NDDL EXCEEDS THE MAXIMUM ALLOWED USER INFORMATION: MAXIMUM NUMBER OF PATHS ALLOWED = %1 PROGRAMMER ACTION: INCREASE THE SIZE OF THE PVATB ARRAY *** SYSTEM FATAL MESSAGE 118 (NDDL) 118.0 THE NDDL TABLES INITIALIZED BY SUBROUTINE XCSA ARE BAD. CHECK THE RECORD AND OPTIONS OF OPENS (I.E. WRT, WRTREW) *** USER FATAL MESSAGE 119 (NDDL) 119.0

12 THE LIMIT ON THE NUMBER OF NDDL PARAMETERS HAS BEEN EXCEEDED. IMIT IS = %1 USER INFORMATION: THE CURRENT L *** USER INFORMATION MESSAGE 120 (NDDL) 120.0 *** ERROR IN DATA BLOCK %1 *** USER INFORMATION MESSAGE 121 (NDDL) 121.0 RECORD %2 *** ERROR IN DATA BLOCK %1 - *** YOU MAY NOT SPECIFY TYPE=%3 FOR AN ARRAY *** USER INFORMATION MESSAGE 121 (NDDL) 121.1 - RECORD %2 *** ERROR IN DATA BLOCK %1 *** USER FATAL MESSAGE 122 (NDDL) 122.0 IN DATABLK %1 A RECORD DESCRIPTION WITH SAMEAS,%2 IS NOT SPECIFIED BELOW THE DESCRIPTION OF RECORD=%3. USER ACTION: SPECIFY THE DESCRIPTION OF RECORD=%4 ABOVE ALL OF ITS SAMEAS REFERENCES. *** USER WARNING MESSAGE 141 (LINKND) 141.0 NDDL 'PARAMETER' DEFINITION TABLE NOT FOUND User information: Insert ACQUIRE NDDL or ACQUIRE NDDLOLD in FMS. *** USER WARNING MESSAGE 142 (LINKND) 14 2.0 NDDL 'QUALIFIER' DEFINITION TABLE NOT FOUND User information: Insert ACQUIRE NDDL or ACQUIRE NDDLOLD in FMS. *** USER WARNING MESSAGE 143 (LINKND) 143.0 NDDL 'DATABLOCK' DEFINITION TABLE NOT FOUND User information: Insert ACQUIRE NDDL or ACQUIRE NDDLOLD in FMS. *** USER FATAL MESSAGE 144 (LINKSB) 144.0 SUBDMAP %1 (CALLED BY SUBDMAP %2) IS NOT IN THE DATA BASE User information: A "CALL" statement refers to an undefined subDMAP. Check the format on the offending "CALL" statement. *** USER WARNING MESSAGE 145 (LINKSB) 145.0 SUBDMAP %1 (CALLED BY SUBDMAP %2) DOES NOT HAVE - CORRECT NUMBER OF WORDS IN FIRST RECORD. IT MUST NOT BE AN OSCAR FILE USER ACTION: SEND RUN TO SIEMENS PLM SOF TWARE CUSTOMER SUPPORT. DUMP OF BAD FIRST RECORD: %3 %4

13 %5 *** USER WARNING MESSAGE 146 (LINKTP) 146.0 A 'TYPE' STATEMENT DEFINES A DATABLOCK %1 IN SUBDMAP %2 WHICH IS NOT DEFINED IN THE 'NDDL' USER INFORMATION: THIS ERROR MAY BE ISSUED IN THE FOLLOWING CIRCUMSTANCES: 1. THE TYPE STATEMENT REFERENCES AN ITEM WHICH HAS NOT BEEN DEFINED IN THE NDDL. 2. THE NDDL STORED IN THE USER'S MASTER DBSET IS INCONSISTENT WITH THE NDDL AND DMAP STORED IN THE DELIVERY DATABA SE; FOR EXAMPLE, A DATABASE CREATED IN VERSION 66 OR 66A IS BEING USED IN A VERSION 67 RUN. ANOTHER EXAMPLE OF WHEN THIS ERROR WILL OCCUR IS WHEN A USER IS ACCIDENTALLY ATTACHING TO AN OLD DATABASE, BECAUSE HE HAS RUN MULTIPLE JOBS WITH THE SAME INPUT FILENAME, AND HE HAS ALSO CHANGED FROM A USS TO SSS SOLUTION SEQUENCE OR VICE - VERSA. (E.G., SOL 24 TO SOL 101). *** USER WARNING MESSAGE 147 (LINKTP) 147.0 A 'TYPE' STATEMENT DEFINES A QUALIFIER/PARAMETER %1 IN SUBDMAP %2 WHICH IS NOT DEFINED IN THE 'NDDL' USER INFORMATION: THIS ERROR MAY BE ISSUED IN THE FOLLOWING CIRCUMSTANCES: 1. THE TYPE STATEMENT REFERENCES AN ITEM WHICH HAS NOT BEEN DEFINED IN THE NDDL. 2. THE NDDL STORED IN THE USER'S MASTER DBSET IS INCONSISTENT WITH THE NDDL AND DMA P STORED IN THE DELIVERY DATABASE; FOR EXAMPLE, A DATABASE CREATED IN VERSION 66 OR 66A IS BEING USED IN A VERSION 67 RUN. ANOTHER EXAMPLE OF WHEN THIS ERROR WILL OCCUR IS WHEN A USER IS ACCIDENTALLY ATTACHING TO AN OLD DATABASE, BECAUSE HE HAS RUN MUL TIPLE JOBS WITH THE SAME INPUT FILENAME, AND HE HAS ALSO CHANGED FROM

14 A USS TO SSS VERSA. (E.G., SOL 24 TO SOL 101). SOLUTION SEQUENCE OR VICE - *** USER WARNING MESSAGE 148 (LINKTP) 148.0 A 'TYPE' STATEMENT DEFINES A QUALIFIER/PARAMETER %1 IN SUBD MAP %2 WHICH DOES NOT MATCH THE VARIABLE TYPE IN THE 'NDDL' User information: 1. The TYPE statement references an item which has not been defined in the NDDL. 2. The NDDL stored in the user's MASTER dbset is inconsistent with the NDDL and DMAP stored in the delivery database; for example, a database created in Version 66 or 66A is being used in a Version 67 run. Another example of when this error will occur is when a user is accidentally bs with attaching to an old database, because he has run multiple jo the same input filename, and he has also changed from a USS to SSS versa. (e.g., SOL 24 to SOL 101). solution sequence or vice - *** USER WARNING MESSAGE 149 (LINKAR) 149.0 CALL STATEMENT %1 IN SUBDMAP %2 HAS AN ARGUMENT LIST OF DIFFERENT LENGTH THAN THE CALLED SUBDMAP User information: The run can fail in an unpredictable manner. Make sure that the number of arguments in the subDMAP CALL match the number of the subDMAP. arguments in *** USER WARNING MESSAGE 150 (LINKAR) 150.0 SUBDMAP %1 CALLED BY SUBDMAP %2 CANNOT BE FOUND IN DATA BASE. *** USER WARNING MESSAGE 151 (LINKAR) 151.0 CALL STATEMENT %1 IN SUBDMAP %2 HAS A PARAMETER THAT BDMAP IN AUTHORIZATION CODE. DOES NOT MATCH CALLED SU USER INFORMATION: PARAMETER IS NUMBER %3 AUTHORIZATION CODE IS : %4 AUTHORIZATION CODE SHOULD BE: %5 *** USER WARNING MESSAGE 151 (LINKAR) 151.1 CALL STATEMENT %1 IN SUBDMAP %2 HAS A PARAMETER THAT DOES NOT MATCH CALLED SUBDMAP IN TYPE AND/OR LENGTH USER INFORMATION: PARAMETER IS NUMBER %3 TYPE IS : %4 TYPE SHOULD BE : %5 (0 - UNDEFINED, 1 - INTEGER, 2 - REAL S.P., 3 - BCD, 4 - REAL D.P., 5 - LOGICAL) COMPLEX S.P. - COMPLEX D.P., 7 - , ,6 LENGTH IS : %6 LENGTH SHOULD BE : %7

15 *** USER WARNING MESSAGE 152 (LWRTBK) 152.0 ---- SUBDMAP %1 CANNOT BE FOUND IN DATA BASE, MUST BE CODE LOGIC ERROR. USER ACTION: SEND RUN TO SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER WARNING MESSAGE 153 (LWRTBK) 153.0 END OF - FILE HIT WHILE READING SUBDMAP %1 --- MUST BE - CODE LOGIC ERROR. USER ACTION: SEND RUN TO SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER WARNING MESSAGE 154 (LINKTP) 154.0 A 'TYPE' STATEMENT DEFINES A VARIABLE %1 IN SUBDMAP %2 WHICH IS DEFINED AS BOTH A QUALIFIER AND A PARAMETER IN THE 'NDDL' *** USER WARNING MESSAGE 155 (LINKTP) 155.0 A 'TYPE' STATEMENT DEFINES A CHARA CTER QUALIFIER/PARAMETER %1 IN SUBDMAP %2 WHICH DOES NOT MATCH THE CHARACTER LENGTH IN THE 'NDDL' *** USER WARNING MESSAGE 156 (LINKSB) 156.0 MAIN SUBDMAP (%1) IS NOT IN THE DATA BASE USER ACTION: CHECK SOL STATEMENT FOR CORRECT SOLUTION REQUEST *** SYSTEM FATAL MESSAGE 157 (LINKER) 157.0 TOTAL NUMBER OF SUBDMAPS REFERENCED BY THIS SOLUTION SEQUENCE HAS EXCEEDED THE ALLOWABLE NUMBER. USER ACTION: REDUCE THE NUMBER OF SUBDMAPS. PROGRAMMER'S ACTION: INCREASE THE SIZE OF LIST2 ARRAY *** SYSTEM FATAL MESSAGE 158 (LINKER) 158.0 END OF RECORD OF FILE 315 IN LINKER. EACH RECORD IN THIS FILE SHOULD CONSIST OF 10 WORDS. THIS FILE CONTAINS THE LINK CARDS GENERATED IN XCSA/PRLINK *** USER INFORMATION MESSAGE 159 (PRLINK) 159.0 EXTERNAL SUBDMAP CALLS FOR %1 (MAIN) SUBDMAP WILL THE BE SATISFIED BY OBJECTS FROM EDSOBJ DBSET *** USER FATAL MESSAGE 160 (LINKSB) 160.0 OBJECT FILE FOR SUBDMAP %1 IS EMPTY. USER ACTION: RECOMPILE THIS SUBDMAP. USER FATAL MESSAGE 161 (CTYPE) *** 161.0 DATABLOCK %1 IS REFERENCED ON A TYPE DB STATEMENT AND THE SUBDMAP STATEMENT. USER ACTION: REMOVE THE REFERENCE FROM THE SUBDMAP

16 STATEMENT OR THE TYPE DB STATEMENT. User information: If a datablock is on the SUBDMAP statem ent, the calling subDMAP will define whether it is a TYPE DB or not. Therefore, having a "TYPE DB" statement in the called subDMAP is a conflict. *** SYSTEM INFORMATION MESSAGE 200 (XGPIMW) 200.0 NO ERROR MESSAGE EXISTS FOR XGPIMW INTERNAL CODE NUMBER %1 *** SYSTEM INFORMATION MESSAGE 200 (XGPIDG) 200.1 NO ERROR MESSAGE EXISTS FOR XGPIDG INTERNAL CODE NUMBER %1 *** SYSTEM INFORMATION MESSAGE 200 (PRXMSG) 200.2 S FOR PRXMSG INTERNAL CODE NO ERROR MESSAGE EXIST NUMBER %1 CALLED FROM %2 DURING %3 %4 PROCESSING *** SYSTEM INFORMATION MESSAGE 200 (NDDMSG) 200.3 NO ERROR MESSAGE EXISTS FOR NDDMSG INTERNAL CODE NUMBER %1 CALLED FROM %2 *** SYSTEM INFORMATION MESSAGE 200 (LNKMSG) 200.4 NO ERROR MESSAGE EXISTS FOR LNKMSG INTERNAL CODE NUMBER %1 CALLED FROM %2 *** SYSTEM INFORMATION MESSAGE 200 (CEPMSG) 200.5 NO ERROR MESSAGE EXISTS FOR CEPMSG INTERNAL ERROR CODE %1 CALLED FROM %2 *** USER FATAL MESSAGE 201 (A?) 201.0 %1 %2 NOT FOUND IN %3 VPS TABLE. *** SYSTEM FATAL MESSAGE 202 (A?) 202.0 UNABLE TO ADD %1 CONSTANT %2 TO %3 VPS TABLE *** SYSTEM WARNING MESSAGE 203 (A?) 203.0 TYPE CODE %1 IS CURRENTLY NOT IMPLEMENTED IN THE %2 EXPRESSION PARSER *** USER FATAL MESSAGE 204 (A?) 204.0 NULL CHARACTER %1 AT POSITION %2 OF %3 %4 *** USER FATAL MESSAGE 205 (A?) 205.0 SYNTAX ERROR IN STRING CONSTANT AT POSITION %1 OF %2 %3 *** USER FATAL MESSAGE 206 (A?) 206.0 SYNTAX ERROR DETECTED IN STRING AT POSITION %1 OF %2 %3 CHARACTER = %4 *** USER FATAL MESSAGE 207 (A?) 207.0 INVALID USE OF %1 CONSTRUCTING %2 CONSTANT AT POSITION %3 OF %4 %5 User information: This can occur if a complex number has a decimal point immediately

17 following the sign -- make sure that there is a zero between the sign and the decimal point. *** USER FATAL MESSAGE 208 (A?) 0 208. INVALID %1 PRECISION CONSTANT AT POSITION %2 OF %3 %4 *** USER FATAL MESSAGE 209 (A?) 209.0 INVALID CHARACTER DETECTED IN COMPLEX CONSTANT AT POSITION %1 OF %2 %3 *** USER FATAL MESSAGE 210 (A?) 210.0 MULTIPLE SIGN DETECTED IN COMPLEX CONSTANT AT POSITION %1 OF %2 %3 *** USER FATAL MESSAGE 211 (A?) 211.0 EMBEDDED BLANKS DETECTED IN COMPLEX NUMBER AT POSITION %1 OF %2 %3 *** USER FATAL MESSAGE 212 (A?) 212.0 ARACTERS AT POSITION %1 CHARACTER STRING EXCEEDS 80 CH OF %2 %3 *** USER FATAL MESSAGE 213 (A?) 213.0 %1 PRECEDED BY %2 AT POSITION %3 OF %4 %5 *** USER FATAL MESSAGE 214 (A?) 214.0 LOGICAL CONSTANTS MAY NOT APPEAR ON THE LEFT - SIDE OF AN ASSIGNMENT STATEMENT. AN ATTEMPT WAS MADE TO REDEFINE %1 AT POSITION %2 OF %3 %4 *** USER FATAL MESSAGE 215 (A?) 215.0 BINARY OPERATORS CANNOT BE THE FIRST SYMBOL FOUND IN AN ARITHMETIC OR LOGICAL EXPRESSION *** USER WARNING MESSAGE 216 (A?) 216.0 VARIABLE NAME EXCEEDS 8 CHARACTERS AT POSITION %1 OF %2 %3. VARIABLE NAME IS TRUNCATED TO %4. RESULTANT PROCESSING MAY BE INCORRECT OR AMBIGUOUS. *** SYSTEM FATAL MESSAGE 217 (A?) 217.0 THE %1 OSCAR %2 ADDRESS POINTER (%3) IS INVALID *** USER FATAL MESSAGE 218 (A?) 218.0 NUMERIC MIXED MODE ASSIGNMENTS ARE NOT ALLOWED IN %1 %2S. ASSIGNMENT ATTEMPTED: %3 DATA TO %4 VARIABLE. User information: This indicates that an assignment statement has mixed - mode arithmetic. Check that all variables in the expression are of the same type (example: real - single precision). If not, there are expressions to convert from one type (example: integer) to another (example: real - single precision).

18 E 219 (A?) *** USER WARNING MESSAG 219.0 A NUMERIC MIXED MODE ASSIGNMENT WAS MADE IN THE PRECEDING %1 %2. ASSIGNMENT MADE: %3 DATA TO %4 VARIABLE User information: This indicates that an assignment statement has mixed mode arithmetic. - Check that all variables in the expression are of the same type single precision). If not, there are expressions to (example: real - convert from one type (example: integer) to another single precision). (example: real - *** USER FATAL MESSAGE 220 (A?) 220.0 E IS ILLEGAL IN %3 ASSIGNMENT OF %1 VALUE TO %2 VARIABL %4S. User information: mode arithmetic. This indicates that an assignment statement has mixed - Check that all variables in the expression are of the same type - single precision). If not, there are expressions to (example: real from one type (example: integer) to another convert (example: real single precision). - *** USER FATAL MESSAGE 221 (A?) 221.0 INVALID MIXED MODE EXPONENTIATION OPERATION DURING %1 %2 PROCESSING. %3 BASE RAISED TO %4 POWER User information: This indicates that an assignment statement has mixed - mode arithmetic. Check that all variables in the expression are of the same type single precision). If not, there are expressions to (example: real - convert from one type (example: integer) to another (example: real - single precision). *** USER FATAL MESSAGE 222 (A?) 222.0 - NON NUMERIC %1 USED IN EXPONENTIATION OPERATION DURING %2 %3 PROCESSING. User information: This indicates that an assignment statement has mixed - mode arithmetic. Check tha t all variables in the expression are of the same type (example: real - single precision). If not, there are expressions to convert from one type (example: integer) to another - single precision). (example: real *** USER FATAL MESSAGE 223 (A?) 223.0 THE %1 OPERATOR %2 CANNOT BE USED ON %3 OPERANDS DURING %4 %5 PROCESSING. User information: This indicates that an assignment statement has mixed - mode arithmetic. Check that all variables in the expression are of the same type (example: real - single pr ecision). If not, there are expressions to

19 convert from one type (example: integer) to another - single precision). (example: real *** USER FATAL MESSAGE 224 (A?) 224.0 MIXED MODE USAGE BY THE ARITHMETIC OPERATOR %1 IS PROCESSING. INVALID DURING %2 %3 USAGE IS BETWEEN %4 AND %5 OPERANDS User information: This indicates that an assignment statement has mixed - mode arithmetic. Check that all variables in the expression are of the same type (example: real - single precision). If not, there ar e expressions to convert from one type (example: integer) to another (example: real single precision). - *** USER FATAL MESSAGE 225 (A?) 225.0 THE %1 OPERATOR %2 CANNOT BE USED BETWEEN %3 AND %4 OPERANDS DURING %5 %6 PROCESSING. User information: - mode arithmetic. This indicates that an assignment statement has mixed Check that all variables in the expression are of the same type (example: real - single precision). If not, there are expressions to convert from one type (example: integer) to anoth er (example: real - single precision). *** USER FATAL MESSAGE 226 (A?) 226.0 THE %1 OPERATOR CANNOT BE USED ON %2 VALUES IN A %3 %4 User information: mode arithmetic. - This indicates that an assignment statement has mixed Check that all variables in the expression are of the same type - (example: real single precision). If not, there are expressions to convert from one type (example: integer) to another - single precision). (example: real *** USER FATAL MESSAGE 227 (A?) 227.0 UNMATCHED %1 DETECTED IN %2 %3 User information: If the DMAP statement is followed by a "$" to denote a comment, and the comment contains a single quote ( ' ), then this error will occur. See Error Report 3774 in Chapter 17. *** USER FATAL MESSAGE 228 (A?) 228.0 THE KEYWORD %1 WAS USED AS A VARIABLE AT POSITION %2 OF %3 %4 *** USER WARNING MESSAGE 229 (A?) 229.0 NO INFORMATION AVAILABLE TO PROCESS ON %1 %2 *** SYSTEM FATAL MESSAGE 230 (A?) 230.0 THE FUNCTION %1 WAS NOT FOUND IN LIBRARY FUNCTION TABLE DURING %2 %3 PROCESSING.

20 *** USER FATAL MESSAGE 231 (A?) 231.0 THE NUMBER OF ARGUMENTS IN THE ARGUMENT LIST FOR %1 IS %2 THAN THE %3 %4 ARGUMENTS %5 NUMBER OF ARGUMENTS SPECIFIED WAS %6 *** SYSTEM FATAL MESSAGE 232 (A?) 232.0 %1 ARGUMENT FORMAT FOR FUNCTION %2 NOT DEFINED IN LIBRARY FUNCTION TABLE *** SYSTEM FATAL MESSAGE 233 (A?) 233.0 %1 OCCURRED DURING PROCESSING OF %2 STACK DURING %3 %4 PROCESSING. USER INFORMATION: THIS ERROR OCCURS WHEN THE EXPRESSION BEING PARSED CONTAINS MORE UNIQUE VARIABLES AND CONSTANTS THAN ALLOWED USER ACTION: SIMPLIFY EXPRESSION AND NOTIFY SIEMENS PLM SOFTWARE CUSTOMER SUPPORT PROGRAMMER INFORMATION: STACK POINTER = %5 WI TH %6 = %7 *** SYSTEM FATAL MESSAGE 233 (A?) 233.1 %1 OCCURRED DURING PROCESSING OF %2 STACK DURING %3 %4 PROCESSING. PROGRAMMER INFORMATION: STACK POINTER = %5 WITH %6 = %7 *** USER FATAL MESSAGE 234 (A?) 234.0 PROCESSING %1 PRECISION SYNTAX ERROR DETECTED WHILE CONSTANT IN A %2 %3. USER ACTION: CORRECT SYNTAX FOR %4 PRECISION CONSTANT AND RESUBMIT RUN. *** USER FATAL MESSAGE 235 (A?) 235.0 THE MAXIMUM SPACE IN THE %1 ARRAY HAS BEEN EXCEEDED DURING %2 %3 PROCESSING. USER INFORMATION: 1. THE MAXIMUM NUMBER OF AVAILABLE TOKENS IS %4 2. EACH OPERATOR, VARIABLE NAME, OR CONSTANT VALUE MAKE ONE TOKEN USER ACTION: SIMPLIFY EXPRESSION AND RESUBMIT RUN. *** USER FATAL MESSAGE 300 300.0 FROM XRCARD ABOVE. *** USER FATAL MESSAGE 300 (RCARD) 300.1 DATA ERROR IN FIELD UNDERLINED. *** USER FATAL MESSAGE 300 FROM CRCARD ABOVE. 300.2 THE MESSAGES ABOVE ARE FROM CRCARD. *** USER WARNING MESSAGE 301 (IFS4P) 301.0 BULK DATA ENTRY %1 CONTAINS INCONSISTENT DATA. SORTED

21 ENTRY COUNT = %2 User information: One or more of the Poisson's ratios on a MAT3 entry is greater than 1.0. *** USER INFORMATION MESSAGE 302 (IFS3P) 302.0 ONE OR MORE GRID ENTRIES HAVE DISPLACEMENT COORDINATE SYSTEM ID OF - 1 User information: 1 indicate fluid grid Coordinate system identification numbers of - point in coupled fluid - structure analysis. See Chapter 24 of NX NASTRAN Users Guide. *** SYSTEM FATAL MESSAGE 305 (IFPDRV) 305.0 IFP MODULE CANNOT OPEN GINO FILE %1 System information: Unexpected nonstandard return from OPEN. *** SYSTEM FATAL MESSAGE 306 (IFPDRV) 306.0 READ LOGICAL RECORD ERROR. System information: Short record enc ountered. Bulk Data entries occupy 20 words. *** SYSTEM FATAL MESSAGE 307 (IFPSIZ) 307.0 THE NAME OF BULK DATA ENTRY %1 IS INVALID. PROGRAMMER ACTION:IF THE ABOVE NAME IS A VALID BULK ENTRY, THEN CHECK THE HASHING FUNCTION TABLE(S), AND MAKE SURE THERE ARE NO "LOST" ITEMS. *** USER FATAL MESSAGE 307 (IFPDRV) 307.1 ILLEGAL NAME FOR BULK DATA ENTRY %1 User information: See Section 5 of the NX NASTRAN Quick Reference Guide. *** USER FATAL MESSAGE 308 (IFPDRV) 308.0 DATA ENTRY %1 NOT ALLOWED IN %2 APPROACH. BULK User information: See Section 5 of the NX NASTRAN Quick Reference Guide. *** USER WARNING MESSAGE 309 (IFPDRV) 309.0 BULK DATA ENTRY %1 IMPROPER IN %2 APPROACH. User information: See Section 5 of the NX NASTRAN Quick Reference Guide. *** USER FATAL MESSAGE 310 (IFPDRV) 310.0 BULK DATA ENTRY %1 NOT ALLOWED IN SAME DECK WITH AXIC CARD. User information: See Section 5 of the NX NASTRAN Quick Reference Guide. *** USER FATAL MESSAGE 310 (IFS1P/IFS3P) 310.1 %1 AND %2 ENTRIES ARE NOT ALLOWED IN THE SAME BULK

22 DATA SECTION. User information: Use one or the other of the above bulk data entries, but not both. *** USER FATAL MESSAGE 310 (IFS3P) 310.2 FOR SOL 401, BULK DATA CARD, DELAY NOT SUPPORTED WITH TLOAD1. User information: See TLOAD1 DOCUMENTATION IN NX NASTRAN Quick Reference Guide. *** USER FATAL MESSAGE 311 (IFPDRV) 311.0 NON - UNIQUE FIELD 2 ON BULK DATA ENTRY %1%2 SORTED = %3 ENTRY COUNT User information: Sorted Bulk Data entry type indicated must have a unique integer in field 2. An error in the input has been detected. Two or more grid points, elements, or properties have the same id. (For example, you may not use two GRID entr ies with the GID=2 in the same run.) *** USER FATAL MESSAGE 311 (IFPDRV) 311.1 - UNIQUE FIELD 2 ON BULK DATA ENTRY %1%2 SORTED NON ENTRY COUNT = %3 User information: This for character Id's Sorted Bulk Data entry type indicated must be unique in f ield 2. An error in the input has been detected. Two or more grid points, elements, or properties have the same id. (For example, you may not use two GRID entries with the GID=2 in the same run.) *** USER FATAL MESSAGE 312 (IFPDRV) 312.0 TOO MANY CONTINUATIONS FOR BULK DATA ENTRY %1%2 SORTED ENTRY COUNT = %3 User information: See Bulk Data entry description in Section 5 of the NX NASTRAN Quick Reference Guide. *** USER FATAL MESSAGE 313 (IFPDRV) 313.0 ILLEGAL NUMBER OF WORDS ON BULK DATA ENTRY %1%2 SORTED ENTRY COUNT = %3 User information: See Bulk Data entry description in Section 5 of the NX NASTRAN Quick Reference Guide. One cause of this message is using a "D" before less noted the exponent for a real number. Only "E" is allowed, un otherwise on the Bulk Data entry description in Section 5 of the NX NASTRAN Quick Reference Guide. Another cause is placing a BCD variable in a real or integer field, such as using the letter O when the number 0 is intended. *** USER FATAL MESSAGE 313 (IFPDRV) 313.1 ILLEGAL NUMBER OF WORDS ON BULK DATA ENTRY %1%2

23 SORTED ENTRY COUNT = %3 OR EXPLICIT CONTINUATION EXPECTED AND NOT FOUND. User information: See Bulk Data entry description in Section 5 of the NX NASTRAN Quick Reference Guide. One cause of this message is using a "D" before the exponent for a real number. Only "E" is allowed, unless noted otherwise on the Bulk Data entry description in Section 5 of the NX NASTRAN Quick Reference Guide. Another cause is placing a BCD v ariable in a real or integer field, such as using the letter O when the number 0 is intended. A third cause might be the existence of an explicit continuation definition in field 10 of the previous entry. In this case, the specified continuation must i mmediately follow the previous bulk data entry. *** SYSTEM FATAL MESSAGE 314 (IFPDRV) 314.0 INVALID CALL FROM IFP : K = %1 System information: Code error, machine failure, or cell is being destroyed. *** USER FATAL MESSAGE 315 (IFPDRV) 315.0 FORMAT ERROR ON BULK DATA ENTRY %1%2 SORTED ENTRY COUNT = %3 User information: See Bulk Data entry description in Section 5 of the NX NASTRAN Quick Reference Guide. If you are using the large field format number of entries is even. make sure the *** USER FATAL MESSAGE 315 (IFPDRV) 315.1 FORMAT ERROR ON BULK DATA ENTRY %1 User information: See Bulk Data entry description in Section 5 of the NX NASTRAN Quick Reference Guide. If you are using the large field form at make sure the number of entries is even. *** USER FATAL MESSAGE 316 (IFS2P): 316.0 THE PRECONDITIONER OPTION %1 SPECIFIED ON THE ITER ENTRY IS INVALID. USER ACTION: CHECK BULK DATA CARD ITER. *** USER FATAL MESSAGE 316 (IFPDRV) 316.1 ILLEGAL DATA ON BULK DATA ENTRY %1%2 SORTED ENTRY COUNT = %3 User information: See Bulk Data entry description in Section 5 of the NX NASTRAN Quick Reference Guide. If you are using the large field format make sure the number of entries is even. *** USER FATAL MESSAGE 316 (IFPDRV) 3 16.2 ILLEGAL DATA ON BULK DATA ENTRY %1

24 User information: See Bulk Data entry description in Section 5 of the NX NASTRAN Quick Reference Guide. If you are using the large field format make es is even. sure the number of entri *** USER FATAL MESSAGE 316 (IFPDRV) 316.3 ILLEGAL DATA ON BULK DATA ENTRY %1 ON SORTED ENTRY COUNT %2 USER INFORMATION: %3 ID %4 EXCEEDS MAXIMUM VALUE ALLOWED %5. *** USER FATAL MESSAGE 316 (IFPDRV) 316.4 ILLEGAL DATA ON BULK DATA ENTRY %1 OR EXPLICIT CONTINUATION ENTRY NOT FOUND IMMEDIATELY AFTER THIS ENTRY User information: See Bulk Data entry description in Section 5 of the NX NASTRAN e Quick Reference Guide. If you are using the large field format mak sure the number of entries is even. If this entry has an explicit continuation defined in field 10, make sure that the referenced bulk data continuation entry occurs immediately after this entry. *** USER FATAL MESSAGE 316 (IFPDRV) 316.5 ILLEGAL DATA ON BULK DATA ENTRY %1 PCOMPG WITH MORE THAN 100 PLIES ARE NOT PRINTED. User information: PCOMPG requires unique global ply identification numbers. *** USER FATAL MESSAGE 317, 317.0 - BAD DATA OR FORMAT OR NON UNIQUE NAME FOR DTI %1 SO RTED CARD COUNT = %2 User information: See Bulk Data entry description in Section 5 of the NX NASTRAN Quick Reference Guide. *** SYSTEM FATAL MESSAGE 318, 318.0 NO ROOM IN /XDPL/ FOR DTI %1 System information: Overflow of Data Pool Table. See Chapter 2 of the NX NASTRAN Programmer's Manual. *** SYSTEM FATAL MESSAGE 319 (IFPDRV) 319.0 IFP READING EOF ON NPTP. System information: Unexpected EOF encountered while attempting to read a bulk data entry. *** SYSTEM FATAL MESSAGE 320 (IFPTBL) 320.0 ERROR ENCOUNTERED PROCESSING BULK DATA. PROGRAMMER ACTION:INCREASE THE NUMBER OF LIST(S) MXLIST BY %1 WORDS. *** SYSTEM FATAL MESSAGE 320 (IFPTBL) 320.1

25 ERROR ENCOUNTERED PROCESSING BULK DATA. PROGRAMMER ACTION: INCREASE THE DEPTH OF THE LIST(S) MXDEEP BY APPROXIMATELY %1 WORDS. *** SYSTEM FATAL MESSAGE 320 (IFPDRV) 320.2 IFP ERROR%1. LAST ENTRY PROCESSED IS %2. SORTED ENTRY COUNT = %3 System information: Code error in IFP or XSORT. *** USER FATAL MESSAGE 321 (IFPDRV) 321.0 UNIQUE PARAM NAME - %1 - NON - User information: All names of parameters must be unique. *** SYSTEM FATAL MESSAGE 322 (IFS9P) 322.0 ILLEGAL ENTRY TO IFS1P. *** SYSTEM FATAL MESSAGE 322 (IFS8P) 322.1 ILLEGAL ENTRY TO IFS8P. *** SYSTEM FATAL MESSAGE 322, 322.2 ILLEGAL ENTRY TO IFS7P. *** SYSTEM FATAL MESSAGE 322 (IFS6P) 322.3 ILLEGAL ENTRY TO IFS6P. *** SYSTEM FATAL MESSAGE 322 (IFS5P) 322.4 ILLEGAL ENTRY TO IFS5P. *** SYSTEM FATAL MESSAGE 322 (IFS4P) 322.5 ILLEGAL ENTRY TO IFS4P. *** SYSTEM FATAL MESSAGE 322 (IFS3P) 322.6 ILLEGAL ENTRY TO IFS3P. *** SYSTEM FATAL MESSAGE 322, 322.7 ILLEGAL ENTRY TO IFS2P. *** SYSTEM FATAL MESSAGE 322 (IFS1P) 322.8 ILLEGAL ENTRY TO IFS1P. System information: IFP code error detected in IFS1P, IFS2P, IFS3P, IFS4P, IFS5P, IFS6P. *** SYSTEM FATAL MESSAGE 322 (IFS11P) 322.9 INTERNAL ERROR IN IFS11P. *** SYSTEM FATAL MESSAGE 322 (IFS11P) 322.10 ILLEGAL ENTRY TO IFS11P. *** SYSTEM FATAL MESSAGE 322, 322.11 ILLEGAL ENTRY TO IFS10P. *** USER FATAL MESSAGE 322, 322.12 THE REAL FORMAT SPECIFIED BY ACPOLE1 IS NOT SUPPORTED WITH THE MONOPOLE SOURCE TYPE POWER.

26 *** USER FATAL MESSAGE 322, 322.13 THE TRANSFER ADMITTANCE CONTINUITY IS ONLY SUPPORTED WITH ACOUSTIC FEM ADAPTIVE ORDER SOLUTION. *** USER FATAL MESSAGE 322, 322.14 BOTH REAL AND IMAGINARY PART OF IMPEDANCE/ADMITTANCE ARE SPECIFIED AS ZERO. *** USER WARNING MESSAGE 324 (XSORSO) 324.0 BLANK ENTRIES ENCOUNTERED WILL BE IGNORED. User information: Blank Bulk Data entries are ignored by NASTRAN. *** USER FATAL MESSAGE 325, 325.0 UNIQUE NAME. DMI %1 SORTED BAD DATA OR FORMAT OR NON - 2 CARD COUNT = % User information: See Bulk Data entry description in Section 5 of the NX NASTRAN Quick Reference Guide. *** SYSTEM FATAL MESSAGE 326, 326.0 NO ROOM IN /XDPL/ FOR DMI %1 System information: NASTRAN Overflow of Data Pool Table. See Chapter 2 of the NX Programmer's Manual. *** USER FATAL MESSAGE 327, 327.0 BAD DATA OR FORMAT OR NON - UNIQUE NAME. DMIG %1 SORTED CARD COUNT = %2 User information: See Bulk Data entry description in Section 5 of the NX NASTRAN Quick Reference Guide. Often this is related to simply having having the wrong type of input. For example, if the matrix type for input is declared as double precision, then all values must be of the form x.xxxD+yy, or double precision. *** USER FATAL MESSAGE 329 (IFS3P) 329.0 ONLY ONE(1) AXIC ENTRY ALLOWED. User information: See Bulk Data entry description in Section 5 of the NX NASTRAN Quick Reference Guide. *** SYSTEM FATAL MESSAGE 330 (IFS3P) 330.0 ES. NO ROOM IN MEMORY FOR PARAM ENTRI System information: Change overlay or increase core size. *** USER FATAL MESSAGE 331 (IFS3P) 331.0 IMPROPER PARAM ENTRY %1 SORTED ENTRY COUNT = %2 User information: See Bulk Data entry description in Section 5 of the NX NASTRAN Quick Reference Guide.

27 *** USER FATAL MESSAGE 332 (IFS3P) 332.0 AXIC BULK DATA ENTRY REQUIRED. User information: The presence of any conical shell data entries requires the presence of an AXIC entry. See the AXIC Bulk Data entry description in Section 5 of the NX NASTRAN Quick Reference Guide. *** USER WARNING MESSAGE 333 (SEMTRN) 333.0 THE BEGIN BULK STATEMENT IS MISSING. A BEGIN BULK STATEMENT WILL BE INSERTED BY THE PROGRAM User information: No BEGIN BULK command was found in the input. Check input and add a BEGIN BULK command. *** USER WARNING MESSAGE 334 (SEMTRN) 334.0 THE ENDDATA STATEMENT IS MISSING. AN ENDDATA STATEMENT WILL BE INSERTED BY THE PROGRAM User information: No ENDDATA entry was found in the input. Check input and add an ENDDATA entry. *** USER FATAL MESSAGE 335 (CNDRV2) 335.0 THE EXPRESSION IN A CONVERT CLAUSE EQUATION HAS INVALID SYNTAX *** USER ACTION: 1. REWRITE THE CONVERT CLAUSE EQUATION USING CORRECT SYNTAX 2. RESUBMIT RUN. *** USER FATAL MESSAGE 335 (CNDRV2) 335.1 THE EXPRESSION IN A WHERE CLAUSE EQUATION HAS INVALID SYNTAX *** USER ACTION: 1. REWRITE THE WHERE CLAUSE EQUATION USING CORRECT SYNTAX 2. RESUBMIT RUN. *** USER WARNING MESSAGE 336 (CNDRV2) 336.0 THE VARIABLE ON THE LEFT - SIDE OF A CONVERT CLAUSE EQUATION WAS NOT FOUND IN THE PRIMARY DATABASE QUALIFIER TABLE *** USER FATAL MESSAGE 336 (CNDRV2) 336.1 - SIDE OF A WHERE CLAUSE THE VARIABLE ON THE LEFT EQUATION WAS NOT FOUND IN THE PRIMARY DATABASE QUALIFIER TABLE *** USER FATAL MESSAGE 337 (IFS6P) 337.0 MORE THAN ONE %1 ENTRY EXISTS. ONLY ONE IS ALLOWED. User information: Make sure only one such entry exists.

28 USER WARNING MESSAGE 338 (IFS2P) *** 338.0 - THE LAST X VALUE ON %1 ENTRY ID = %2 VALUE. THE - IS MISSING A CORRESPONDING Y VALUE WILL BE IGNORED. LAST X - User information: There has to be an even number of entries. If there is an odd number, then this message is i ssued and the last value ignored. *** USER FATAL MESSAGE 339 (MDCASE) 339.0 SUBCASE %1 DOES NOT INCLUDE AN ANALYSIS CASE CONTROL COMMAND. USER INFORMATION: AN ANALYSIS COMMAND MUST BE SPECIFIED FOR EACH SUBCASE. *** USER FATAL MESSAGE 340 (MDCASE) 340.0 BOTH MODAL (ANAL = MFREQ) AND DIRECT (ANAL = DFREQ) FREQUENCY ANALYSIS HAVE BEEN SPECIFIED. USER ACTION: SPECIFY EITHER MODAL OR DIRECT FREQUENCY RESPONSE BUT NOT BOTH. *** USER FATAL MESSAGE 341 (MDCASE) 341.0 SUBCASE %1 CONTAINS THE ANALYSIS = %2 COMMAND BUT LACKS THE REQUIRED METHOD CASE CONTROL COMMAND. USER ACTION: FOR MULTIDISCIPLINARY ANALYSIS THAT REQUIRE A NORMAL MODES OR BUCKLING SOLUTION, THE METHOD COMMAND MUST BE SPECIFIED AT THE subcase LEVEL OR A BOVE THE SUBCASE LEVEL. *** USER FATAL MESSAGE 342 (MDCASE) 342.0 THERE ARE %1 MODAL TRANSIENT SUBCASES. USER INFORMATION: ONLY ONE MODAL TRANSIENT SUBCASE IS PERMITTED WHEN PERFORMING MULTIDISCIPLINARY ANALYSIS. *** USER FATAL MESSAG E 343 (MDCASE) 343.0 THERE ARE MULTIPLE DESGLB COMMANDS IN THE CASE CONTROL SECTION. USER INFORMATION: ONLY ONE DESGLB COMMAND IS PERMITTED. *** USER FATAL MESSAGE 343 (MDCASE) 343.1 THERE ARE MULTIPLE DESOBJ COMMANDS IN THE CASE CONTROL SECTION. USER INFORMATION: ONLY ONE DESOBJ COMMAND IS PERMITTED. *** USER FATAL MESSAGE 344 (MDCASE) 344.0 DESGLB COMMAND = %1 IN SUBCASE = %2 IS DIFFERENT THAN THE PREVIOUS SUBCASE USER INFORMATION: SPECIFY THE DESGLB COMMAND ABOVE THE SUBCASE LEVEL. *** USER FATAL MESSAGE 345 (IFS1P) 345.0

29 FACE TYPE %1 IS INVALID ON THE QHBDY ENTRY. *** USER FATAL MESSAGE 346 (IFS1P) 346.0 AN AREA FACTOR IS SPECIFIED FOR AN INAPPROPRIATE FACE TYPE = %1. USER INFORMATION: AREA FACTOR IS PERMITTED FOR TYPE = POINT AND LINE ONLY. *** USER FATAL MESSAGE 347 (IFS1P) 347.0 AN INVALID, OR NO, AREA FACTOR IS SPECIFIED FOR FACE TYPE = %1. *** USER FATAL MESSAGE 348 (MDCASE) 348.0 THE ANALYSIS=MODES SUBCASE(S) DOES NOT INCLUDE A DESSUB COMMAND. USER INFORMATION: SPECIFY THE DESSUB COMMAND IN ALL SUPERELEMENT AND RESIDUAL SUBCASES WITH ANALYSIS=MODES. *** USER FATAL MESSAGE 349 (MDCASE) 349.0 THERE ARE %1 COMPLEX EIGENVALUE SUBCASES. USER INFORMATION: ONLY ONE COMPLEX EIGENVALUE SUBCASE, DCEIG OR MCEIG, IS PERMITTED IN SOL 200. *** USER FATAL MESSAGE 350 (IFS350) 350.0 THE FOLLOWING GRID OR SCALAR POINTS ARE SPECIFIED MORE THAN ONCE ON THE BULK DATA ENTRY SHOWN BELO W: *** USER FATAL MESSAGE 350 (IFS350) 350.1 THE FOLLOWING GRID/SCALAR POINT - COMPONENT IS SPECIFIED MORE THAN ONCE ON THE BULK DATA ENTRY SHOWN BELOW: *** SYSTEM FATAL MESSAGE 370 (IFP3EM) 370.0 AXIC FILE RECORD FOR ENTRY(%1) NOT OF LENGTH = TO ENTRY MULTIPLES + 3. RECORD HEADER =%2 *** USER FATAL MESSAGE 371 (IFP3EM) 371.0 %1 ID = %2 IS OUTSIDE THE PERMISSIBLE RANGE: 1 THROUGH 9999. *** USER FATAL MESSAGE 372 (IFP3EM) 372.0 MINIMUM PROBLEM REQUIRES %1 ENTRY, NONE FOUND. *** USER FATAL MESSAGE 373 (IFP3EM) 373.0 RING ID =%1 ON ENTRY TYPE (%2) IS OUTSIDE THE ALLOWABLE RANGE: 1 THROUGH %3. *** SYSTEM FATAL MESSAGE 374 (IFP3EM) 374.0 INCONSISTENCY, AXIC TRAILER BI T IS ON, BUT RECORD COULD NOT BE FOUND BY LOCATE. RECORD HEADER =%1 *** USER FATAL MESSAGE 375 (IFP3EM) 375.0 HARMONIC NUMBER =%1 ON ENTRY TYPE (%2) IS OUTSIDE THE

30 ALLOWABLE RANGE: 0 THROUGH %3. *** SYSTEM FATAL MESSAGE 376 (IFP3EM) 376.0 INCONSISTENT ERROR READING BALANCE OF %1%2 ENTRIES. *** SYSTEM FATAL MESSAGE 377 (IFP3EM) 377.0 RECORD INCONSISTENCY FOR %1%2 ENTRIES *** USER FATAL MESSAGE 378 (IFP3EM) 378.0 SPCAX OR MPCAX ENTRY HAS A SETID = 101 OR 102. USER INFORMATION: 101 AND 102 ARE SPECIAL SETS RESERVED FOR SINE AND COSINE SETS. *** USER FATAL MESSAGE 379 (IFP3EM) 379.0 RINGAX ENTRY WITH RING ID = %1 HAS A ZERO RADIUS SPECIFIED. *** USER FATAL MESSAGE 380 (IFP3EM) 380.0 ENTRY TYPE %1 HAS BAD COMPONENT SPECIFICATION OF %2 *** SYSTEM FATAL MESSAGE 381 (IFP3EM) 381.0 AXIC TRAILER BIT ON BUT LOCATE CAN NOT FIND POINTAX OR SECTAX ENTRY. *** USER FATAL MESSAGE 382 (IFP) 382.0 AN INVALID BULK DATA ENTRY HAS BEEN SPECIFIED FOR AXI - SYMMETRIC CONICAL SHELL ANALYSIS *** USER INFORMATION MESSAGE 382 (IFP) 382.1 THE ELEMENT ITERATIVE SOLVER CAN ONLY BE USED IN LINEAR STATICS. SWITCHING TO SPARSE MATRIX METHOD. *** USER WARNING MESSAGE 383 (IFS8P) 383.0 NO ORIENTATION IS SPECIFIED FOR CHBDYP ELEMENT %1 *** USER FATAL MESSAGE 384 (IFS1P) 384.0 THE LOWER RANGE FREQUENCY ,F1, IS LESS THAN 0.0 HZ. *** USER FATAL MESSAGE 385 (IFS1P) 385.0 THE UPPER RANGE FREQUENCY ,F2, IS LESS THAN THE LOWER RANGE FREQUENCY. *** USER FATAL MESSAGE 387 (IFS1P) 387.0 THE FREQUENCY SPREAD ,FSPD, ON FREQ4 ENTRY %1 IS LESS THAN OR EQUAL TO 0.0 OR GREATER THAN 1.0. *** USER FATAL MESSAGE 388 (IFS1P) 388.0 THE NUMBER OF FREQUENCIES ,NFM, ON FREQ4 ENTRY %1 IS LESS THAN 1. *** USER FATAL MESSAGE 389 (IFS1P) 389.0 ONE OR MORE FRACTIONS ,FRI, ON FREQ5 ENTRY %1 ARE LESS THAN 0.0 *** USER FATAL MESSAGE 390 (IFSEGL) 390.0 FIELD %1 ON EIGRL ENTRY, SID = %2 IS SPECIFIED MORE THAN

31 ONCE. *** USER FATAL MESSAGE 390 (IFSEGC) 390.1 FIELD %1 ON EIGC ENTRY, SID = %2 IS SPECIFIED MORE THAN ONCE. *** USER FATAL MESSAGE 391 (XSDFF) 391.0 %1 THE COMMA - FIELD FORMAT IS NOT ALLOWED - DELIMITED FREE FOR THE ABOVE ENTRY. USER INFORMATION: REWRITE ENTRY WITH FIXED FORMAT IN FIELDS 1, 2, AND 10. FIELDS 3 THROUGH 9 ARE TREATED AS ONE CONTIGUOUS FIELD. *** USER FATAL MESSAGE 392 (XSORSO) 392.0 THE AUXMID OR SEID ON THE FOLLOWING BEGIN BULK COMMAND IS NOT GREATER THAN 0. BULK ENTRY: %1 User information: Can also result by accidently including a second begin bulk command. *** USER FATAL MESSAGE 393 (IFS2P) 393.0 ON MAT8 ID = %1, ONLY ON E OR TWO OF Xt, Yt AND S ARE SPECIFIED. USER ACTION: SPECIFY VALUES FOR Xt, Yt AND S IF ANY OF Xt, Xc, Yt, Yc, AND S ARE SPECIFIED. *** USER WARNING MESSAGE 394 (IFS5P) 394.0 INCONSISTENT OPTIONS FOR LOAD TYPE AND SCALE FACTOR ARE SPECIFIED ON PLOAD1 BULK ENTRY = %1 . USER INFORMATION: THE SCALE FACTOR = %2 IS IGNORED WHEN A LOAD TYPE = %3, BASED ON ELEMENT COORDINATES IS USED. *** USER FATAL MESSAGE 397 (GETLIN) 397.0 THE INPUT FILE INCLUDE NEST DEPTH (= %1) HAS BEEN EXCEEDED. FILE '%2' IS INCLUDED IN FILE '%3' AT RECORD NUMBER %4. THE INCLUDE REQUEST IS SKIPPED. *** USER FATAL MESSAGE 398 (GETLIN) 398.0 A REQUESTED %1 FILE WAS NOT FOUND. FILE '%2' IS INC LUDED IN FILE '%3' AT RECORD NUMBER %4. THE INCLUDE REQUEST IS SKIPPED. *** USER FATAL MESSAGE 398 (GETLIN) 398.1 NO FILE NAME SPECIFIED ON %1 STATEMENT. STATEMENT IS INCLUDED IN FILE '%3' AT RECORD NUMBER %4.

32 THE INCLUDE REQUEST IS SKIPPED. *** USER FATAL MESSAGE 398 (GETLIN) 398.2 FILE NAME SPECIFIED ON %1 STATEMENT EXCEEDS MAXIMUM ALLOWABLE LENGTH OF %2 FILE '%3' IS INCLUDED IN FILE '%4' AT RECORD NUMBER %5. THE INCLUDE REQUEST IS SKIPPED. *** USER FATAL MESSAGE 399 (GETLIN) 399.0 OPEN FOR %1 FILE FAILED. ERROR FLAG = %2, ERROR CODE = %3. FILE '%4' IS INCLUDED IN FILE '%5' AT RECORD NUMBER %6. THE INCLUDE REQUEST IS SKIPPED. *** SYSTEM FATAL MESSAGE 400 (CTYPE) 400.0 THE COMPILER HAS BECOME LOST, DURING PROCESSING OF THE ABOVE TYPE CARD USER ACTION: NOTIFY SIEMENS PLM SOFTWARE CUSTOMER SUPPORT AS SOON AS POSSIBLE. *** SYSTEM FATAL MESSAGE 400 (CSUBDM) 400.1 THE COMPILER HAS BECOME LOST, DURING PROCESSING OF TH E ABOVE SUBDMAP CARD USER ACTION: NOTIFY SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 400 (CEPMSG) 400.2 THE COMPILER HAS BECOME LOST, DURING PROCESSING OF THE ABOVE %1 CAR ** USER ACTION: 1. NOTIFY SIEMENS PLM SOFTWARE CUSTOME R SUPPORT AS SOON AS POSSIBLE. 2. CHANGE %2 STATEMENT TO %3 STATEMENTS *** SYSTEM FATAL MESSAGE 400 (CEPMSG) 400.3 THE NUMBER OF DATA BLOCKS ON THE %1 CARD EXCEEDS THE MAXIMUM (%2 ) ALLOWED *** SYSTEM FATAL MESSAGE 401 (CGVPST) 401.0 NUMBER OF NDDL PARAMETERS EXCEEDS THE MAXIMUM ALLOWED OF %1 *** SYSTEM FATAL MESSAGE 401 (CGVPST) 401.1 NUMBER OF PARAMETER ARGUMENTS EXCEEDS THE MAXIMUM ALLOWED OF %1 *** USER FATAL MESSAGE 402 (CTYPE) 402.0 %1 WAS DETECTED WHEN %2 WAS EXPECTED USER ACTION: ADD CORRECT %3 AND RECOMPILE *** USER FATAL MESSAGE 402 (CSUBDM) 402.1

33 %1 WAS DETECTED WHEN THE SUBDMAP NAME WAS EXPECTED USER ACTION: ADD SUBDMAP NAME AND RECOMPILE USER FATAL MESSAGE 402 (CTYPE) *** 402.2 %1 WAS DETECTED WHEN %2 WAS EXPECTED USER ACTION: ADD CORRECT %3 AND RECOMPILE USER INFORMATION: VALID SCOPE IDENTIFIERS ARE "NDDL" AND " " *** USER FATAL MESSAGE 402 (CTYPE) 402.3 %1 WAS DETECTED WHEN %2 WAS EXPEC TED USER ACTION: ADD CORRECT %3 AND RECOMPILE USER INFORMATION: VALID PARAMETER TYPE CODES ARE "I", "RS", "CHAR", "RD", "CS", "CD", "LOGI", "RX", OR "CX" *** USER FATAL MESSAGE 402 (CTYPE) 402.4 %1 WAS DETECTED WHEN %2 WAS EXPECTED USER ACTION: ADD CORRECT %3 AND RECOMPILE USER INFORMATION: VALID AUTHORIZATION CODES ARE "Y", "N", OR " " *** USER FATAL MESSAGE 402 (CTYPE) 402.5 %1 WAS DETECTED WHEN %2 WAS EXPECTED USER ACTION: ADD CORRECT %3 AND RECOMPILE USER INFORMATION: VALID IDENTIFIER KEYWORDS ARE "PARM" AND "DB" *** USER FATAL MESSAGE 403 (CSUBDM) 403.0 A NUMERIC VALUE WAS DETECTED WHEN A DELIMITER, DATA BLOCK NAME, PARAMETER NAME, OR END - - CARD WAS OF EXPECTED FROM SUBDMAP USER ACTION: REMOVE NUMERIC VALUE STATEMENT AND RECOMPILE *** USER FATAL MESSAGE 404 (CTYPE) 404.0 - %1 DELIMITER WAS DETECTED WHERE A %2 DELIMITER A NON IS REQUIRED *** USER FATAL MESSAGE 404 (CSUBDM) 404.1 A NON - SLASH DELIMITER WAS DETECTED WHERE A SLASH DELIMITER IS REQUIRED - SLASH DELIMITER WITH A SLASH, USER ACTION: REPLACE NON AND RECOMPILE User information: This message can result when the default value of a real or complex parameter is specified to be a letter instead of a number. A common occurrence of this is using the letter "O" in place of the number "0". See Error Report 3782 in section 17.4 of NX NASTRAN Reference Manual. *** SYSTEM FATAL MESSAGE 405 (CSUBDM) 405.0 THE NUMBER OF WORDS ALLOCATED FOR PROCESSING THIS SUBDMAP'S %1 HAS BEEN EXCEEDED. THE MAXIMUM IS %2

34 WORDS USER ACTION: EACH NAME USES 2 WORDS. REDUCE THE NUMBER OF %3 AND RESUBMIT PROGRAMMER ACTION: ENLARGE COUNTER %4 AND ARRAY DIMENSION FOR %5 *** USER FATAL MESSAGE 406 (NDDL) 406.0 INVALID DATA TYPE CODE %1. VALID DATA TYPE CODES ARE "I", "RS", "CHAR", "RD", "CS", "CD", "LOGI", "RX", OR "CX" *** USER FATAL MESSAGE 406 406.1 INVALID PARAMETER TYPE CODE %1. "RD", VALID PARAMETER TYPE CODES ARE "I", "RS", "CHAR", "CS", "CD", "LOGI", "RX", OR "CX" *** USER FATAL MESSAGE 406 (CTYPE) 406.2 INVALID IDENTIFIER KEYWORD %1. VALID IDENTIFIER KEYWORDS ARE "PARM" AND "DB" *** USER FATAL MESSAGE 406 (CTYPE) 406.3 INVALID USER AUTHORIZATION CODE %1. VA LID AUTHORIZATION CODES ARE "Y", "N", OR " " *** USER FATAL MESSAGE 406 (CTYPE) 406.5 INVALID VARIABLE SCOPE IDENTIFIER %1. VALID SCOPE IDENTIFIERS ARE "NDDL" AND " " *** SYSTEM WARNING MESSAGE 406 (FORTIO) 406.6 INVALID PARAMETER CLOSE OPTION CODE %1. VALID PARAMETER OPERATION CODES ARE 1 (REWIND), 2 (CLOSE/KEEP), AND 3 (CLOSE/DELETE) *** SYSTEM WARNING MESSAGE 406 (FORTIO) 406.7 INVALID PARAMETER OPERATION CODE %1. VALID PARAMETER OPERATION CODES ARE "O PEN" OR "CLOSE" *** SYSTEM FATAL MESSAGE 406 (ZRDBLK) 406.8 INVALID INTERNAL NDDL DATA CODE %1 PROCESSING RECORD %2 OF DATABLOCK %3 VALID INTERNAL NDDL DATA CODES ARE 1 THROUGH 10 *** SYSTEM FATAL MESSAGE 406 (ZRDBLK) 406.9 INVALID INTERNAL NDDL DATA CODE %1 PROCESSING RECORD %2 OF DATABLOCK %3 VALID INTERNAL NDDL DATA CODES ARE 1 THROUGH 10 INTERNAL NDDL DATA CODE 11 GENERALLY INDICATES AN NDDL COMPILATION ERROR USING THE "SAMEAS" OPTION VERIFY RECORDS DESCRIBED AS "SAMEA S" APPEAR AFTER THE REFERENCED "SAMEAS" RECORD *** USER FATAL MESSAGE 407 (CTYPE) 407.0 USER AUTHORIZATION FIELD IS MISSING ON ABOVE TYPE

35 STATEMENT User information: All "TYPE PARM" statements require a "Y" or "N" authorization code. *** USER WARNING MESSAGE 408 (CTYPE) 408.0 PARAMETER %1 HAS BEEN PREVIOUSLY DEFINED TO THE VPS (PARAMETER) TABLE. THIS DEFINITION IS IGNORED. USER INFORMATION: THIS PARAMETER MAY BE EITHER A PERMANENT VPS TABLE ENTRY, OR DEFINED BY A PREVIOUS TYPE STATEMENT. User information: User is attempting to define a parameter twice. *** USER WARNING MESSAGE 409 (CTYPE) 409.0 THE PARAMETER %1 IS IGNORED BECAUSE IT HAS BEEN PREVIOUSLY DEFINED IN A TYPE DMAP STATEMENT *** USER WARNING MESSAGE 410 (CT YPE) 410.0 -- DEFAULT VALUE IGNORED FOR NDDL TYPED PARAMETER DEFAULTS MUST BE SET IN NDDL DECK *** USER FATAL MESSAGE 411 (CTYPE) 411.0 THE VALUE ASSIGNED TO ONE OF THE PARAMETERS ON THIS TYPE STATEMENT IS INCONSISTENT WITH REQUESTED %1 TYPE CODE *** USER FATAL MESSAGE 411 (CTYPE) 411.1 THE '%1' VALUE ASSIGNED TO THE PARAMETER %2 ON THIS TYPE STATEMENT IS INCONSISTENT WITH REQUESTED '%3' TYPE CODE *** SYSTEM FATAL MESSAGE 412 (CTYPE) 412.0 THE NUMBER OF WORDS ALLOCATED FOR PROCESSING TYPED PARAMETERS HAS BEEN EXCEEDED. THE MAXIMUM IS %1 WORDS USER ACTION: EACH PARAMETER USES 2 WORDS. REDUCE THE NUMBER OF PARAMETERS AND RESUBMIT PROGRAMMER ACTION: ENLARGE COUNTER MAXPRM AND FOR PARAMS ARRAY DIMENSION *** USER FATAL MESSAGE 413 (CEPMSG) 413.0 FOUND BCD VALUE WHEN EXPECTING DELIMITER, DURING PROCESSING OF %1 CARD *** USER FATAL MESSAGE 413 (CEPMSG) 413.1 FOUND NUMERIC VALUE WHEN EXPECTING DELIMITER, DURING PROCESSING OF %1 CARD *** USER FATAL MESSAGE 413 (CEPMSG) 413.2 FOUND END - OF - CARD WHEN EXPECTING DELIMITER, DURING PROCESSING OF %1 CARD *** USER FATAL MESSAGE 413 (CEPMSG) 413.3 FOUND BCD VALUE WHEN EXPECTING DELIMITER OR END - OF -

36 CARD, DURING PROCESSING OF ABOVE %1 CARD *** USER FATAL MESSAGE 413 (CEPMSG) 413.4 FOUND NUMERIC VALUE WHEN EXPECTING DELIMITER OR END - OF - CARD, DURING PROCESSING OF ABOVE %1 CARD *** USER FATAL MESSAGE 413 (CEPMSG) 413.5 FOUND NUMERIC VALUE WHEN EXPECTING DATA BLOCK NAME, DURING PROCESSING OF %1 CARD *** USER FATAL MESSAGE 413 (CEPMSG) 413.6 OF - CARD WHEN EXPECTING DATA BLOCK NAME, FOUND END - DURING PROCESSING OF %1 CARD *** USER FATAL MESSAGE 413 (CEPMS G) 413.7 FOUND NUMERIC VALUE WHEN EXPECTING DATA BLOCK NAME OR DELIMITER, DURING PROCESSING OF %1 CARD *** USER FATAL MESSAGE 413 (CEPMSG) 413.8 FOUND END OF - CARD WHEN EXPECTING DATA BLOCK NAME OR - DELIMITER, DURING PROCESSING OF ABOVE %1 CARD *** USER FATAL MESSAGE 413 (CEPMSG) 413.9 FOUND NUMERIC VALUE WHEN EXPECTING PARAMETER NAME, DURING PROCESSING OF %1 CARD *** USER FATAL MESSAGE 413 (CEPMSG) 413.10 FOUND END - OF - CARD WHEN EXPECTING PARAMETER NAME, DURING PROCESSING OF %1 CARD *** USER FATAL MESSAGE 413 (CEPMSG) 413.11 FOUND NUMERIC VALUE WHEN EXPECTING PARAMETER NAME, - DELIMITER, OR END - CARD, WHILE PROCESSING %1 CARD OF *** SYSTEM FATAL MESSAGE 414 (CEPMSG) 414.0 DMAP INSTRUCTION %1 NOT FOUND IN DMAP LIBRARY ACTION: NOTIFY SIEMENS PLM SOFTWARE CUSTOMER ** USER SUPPORT. *** USER FATAL MESSAGE 415 (CEPMSG) 415.0 %1 DMAP INSTRUCTION REQUIRES AT LEAST TWO DATA BLOCKS *** USER FATAL MESSAGE 416 (CEPMSG) 416.0 NO DATA BLOCK NAME(S) SPECIFIED ON THIS %1 CARD *** USER FATAL MESSAGE 418 (CEPMSG) 418.0 DATA BLOCK NAME(S) AND PARAMETER NAME NOT DELIMITED BY '/' ON %1 CARD *** USER FATAL MESSAGE 419 (CEPMSG) 419.0 NO PARAMETER NAME SPECIFIED ON THIS %1 CARD *** USER FATAL MESSAGE 420 (CEPMSG) 420.0 EXTRANEOUS DATA FOUND AFTER PARAMETER NAME, BUT BEFORE DELIMITER OR END - OF - CARD. DATA IS IGNORED FOR THIS %1 STATEMENT

37 *** USER FATAL MESSAGE 421 (CEPMSG) 421.0 USE OF 'S,Y', 'S,N', 'V,N', OR 'V,Y' IS INVALID FOR P ARAMETERS USED ON %1 STATEMENTS ** USER ACTION: REMOVE INVALID SYNTAX AND RERUN *** USER FATAL MESSAGE 421 (CEPMSG) 421.1 USE OF 'S' OR 'V' IS INVALID FOR PARAMETERS USED ON %1 STATEMENTS ** USER ACTION: REMOVE INVALID SYNTAX AND RERUN *** SYSTEM INFORMATION MESSAGE 422 (CEPMSG) 422.0 FOR COMPILATION PURPOSES %1 WILL BE USED AS THE PARAMETER NAME FOR THIS %2 STATEMENT *** USER FATAL MESSAGE 423 (ATTDBS) 423.0 THE FOLLOWING PHYSICAL FILE DOES NOT EXIST %1 THIS FILE IS A PART OF TH E M A S T E R DBSET OF THE DELIVERY DATABASE BEING ATTACHED TO THIS RUN. User information: The MASTER dbset is required for all runs which use an existing database. If the MASTER has been allocated to several physical files, t be available for all runs using the then all of these files mus database set. Also, see Error Reports 3652 in section 17.2 of NX NASTRAN Reference Manual. *** USER FATAL MESSAGE 424 (CEXPRS) 424.0 THE EXPRESSION FOUND IN AN IF, DO WHILE, OR WHERE STATEMENT IS NOT ENCLOSED IN PARENTHESES. User information: First check that the expression is enclosed in parentheses. If it is, then check the offending statement for syntax. It is possible that the expression has been improperly entered. 25 (MODXTR) *** USER FATAL MESSAGE 4 - 425.0 TOO MANY CONTINUATION CARDS DETECTED ON A %1 STATEMENT. INVALID CONTINUATION CARD IMAGE IS: %2 USER ACTION: SIMPLIFY EXPRESSION. USER INFORMATION: MAXIMUM ALLOWABLE NUMBER OF CONTINUATIONS IS %3 CARD IMAGES, OR %4 CHARACTERS. *** USER FATAL MESSAGE 425 425.1 TOO MANY CONTINUATION CARDS DETECTED ON AN IF OR A DO WHILE STATEMENT, OR ON A DBVIEW WHERE CLAUSE. INVALID CONTINUATION CARD IMAGE IS: %1 USER ACTION: SIMPLIFY EXPRESSION. USER INFORMATION: MAXIMUM ALLOWABLE NUMBER OF CONTI NUATIONS IS 6 CARD IMAGES, OR 432 CHARACTERS. *** USER FATAL MESSAGE 426 (XTRLEF) 426.0

38 THE FOLLOWING KEYWORD(S) ARE ILLEGAL FOR THE %1 COMMAND %2 *** USER FATAL MESSAGE 426 (XCSOL2) 426.1 ILLEGAL FOR THE SOL THE FOLLOWING KEYWORD(S) ARE EXECUTIVE CONTROL COMMAND %1 *** USER FATAL MESSAGE 426 (XCSACM) 426.2 THE FOLLOWING KEYWORD(S) ARE ILLEGAL FOR THE COMPILE EXECUTIVE CONTROL COMMAND %1 *** USER FATAL MESSAGE 426 (RDUPDT) 426.3 THE FOLLOWING KEYWORD(S) ARE ILLEGAL FOR THE DBUPDATE EXECUTIVE CONTROL COMMAND %1 *** USER FATAL MESSAGE 426 (RDSECU) 426.4 THE FOLLOWING KEYWORD(S) ARE ILLEGAL FOR THE SECURITY COMMAND %1 *** USER FATAL MESSAGE 426 (RDREST) 426.5 THE FO LLOWING KEYWORD(S) ARE ILLEGAL FOR THE RESTART COMMAND %1 *** USER FATAL MESSAGE 426 (RDPROJ) 426.6 THE FOLLOWING KEYWORD(S) ARE ILLEGAL FOR THE PROJECT COMMAND %1 *** USER FATAL MESSAGE 426 (RDINIT) 426.7 THE FOLLOWING KEYWORD(S) ARE ILLEGAL FOR THE INIT EXECUTIVE CONTROL COMMAND %1 *** USER FATAL MESSAGE 426 (RDFIX) 426.8 THE FOLLOWING KEYWORD(S) ARE ILLEGAL FOR THE DBFIX COMMAND %1 *** USER FATAL MESSAGE 426 (RDEXPN) 426.9 THE FOLLOWING KEYWORD(S) ARE ILLEGAL FOR EXPAND EXECUTIVE CONTROL COMMAND %1 *** USER FATAL MESSAGE 426 (RDDIRP) 426.10 THE FOLLOWING KEYWORD(S) ARE ILLEGAL FOR DBDIR EXECUTIVE CONTROL COMMAND %1

39 *** USER FATAL MESSAGE 426 (RDDBCL) 426.11 THE FOLLOWING KEYWORD(S) ARE ILLEGAL FOR THE DBCLEAN EXECUTIVE CONTROL COMMAND. %1 *** USER FATAL MESSAGE 426 (IFSLFT) 426.12 THE FOLLOWING KEYWORD(S) ARE ILLEGAL OR REPEATED ON THE %1 BULK ENTRY %2 *** USER FATAL MESSAGE 426 (CHKSTR) 426.13 THE FOLLOWING KEYWORD(S) ARE ILLEGAL FOR THE %1 COMMAND. %2 *** SYSTEM FATAL MESSAGE 427 (CLOPBK) 427.0 THE LOPBLK TABLE HAS EXCEEDED ITS MAXIMUM %1 NUMBER OF ENTRIES USER INFORMATION: THIS TABLE CONTAINS THE SCRA TCH DATABLOCKS TO BE DELETED AT THE TOP OF EACH LOOP) USER ACTION: USE FILE=SAVE OPTION TO SAVE THE SCRATCH DATABLOCK OUTPUT INSIDE LOOPS. NOTIFY SIEMENS PLM SOFTWARE CUSTOMER SUPPORT OF THIS ERROR. PROGRAMMER ACTION: INCREASE TABLE SIZE OF LOPBLK AND L OPMAX. *** USER FATAL MESSAGE 428 (COSGEN) 428.0 ALTER %1 IS OUT OF RANGE. LAST DMAP NUMBER IS %2 User information: When modifying a DMAP using Alter statements, the line numbers on the Alter statement must be within the range of the line numbers of the DMAP being modified. *** USER FATAL MESSAGE 428 (CKALTR) 428.1 DMAP LINE NUMBER K1 IS OUT OF RANGE. LAST DMAP LINE NUMBER IS:%1 *** USER WARNING MESSAGE 429 (C PARAM) 429.0 THE CHARACTER CONSTANT USED AS PARAMETER NUMBER %1 HAS BEEN TRUNCATED TO '%2'. USER INFORMATION: TRUNCATION MAY RESULT IN AMBIGUOUS OR INCORRECT PROCESSING. User information: This means that a character constant has been defined using more char acters than are allowed based on either the "TYPE PARM" statement or in the NDDL. Any characters beyond the defined length will be truncated. *** USER FATAL MESSAGE 430 (CPARAM) 430.0 C,N AND C,Y CONSTANT FORMATS ARE NO LONGER SUPPORTED.

40 %1 CONSTANT FORMAT FOUND IN PARAMETER NUMBER %2 USER ACTIONS: 1. CHANGE BCD CONSTANTS TO QUOTED CHARACTER STRINGS 2. CHANGE NUMERIC CONSTANTS TO NUMERIC VALUES ONLY 3. CHANGE PARAMETER NAMES TO V,N OR V,Y FORMAT *** USER WARNING MESSAGE 431 (CPARAM) 431.0 THE DEFAULT VALUE FOR AN NDDL TYPED PARAMETER IS IGNORED FOR PARAMETER NUMBER %1 USER INFORMATION: NDDL DEFAULTS MUST BE SET IN NDDL DECK Defaults may not be assigned on the TYPE PARM,NDDL statement. *** SYSTEM FATAL MESSAGE 432 (LCFENT) 432.0 INSUFFICIENT OPEN CORE AVAILABLE TO STORE DBENTRY OF THE LOCATED DATA BASE *** SYSTEM WARNING MESSAGE 432 (DIRPT2) 432.1 INSUFFICIENT OPEN CORE AVAILABLE TO STORE THE REMAINING TRAILER RECORDS. USER INFORMATION: THE REMAINING RECORDS HAVE BEEN TRUNCATED. *** SYSTEM FATAL MESSAGE 432 (CPYNDL) 432.2 INSUFFICIENT OPEN CORE AVAILABLE TO COPY NDDL TABLES TO THE PRIMARY DATA BASE *** SYSTEM WARNING MESSAGE 434 (CSCDMP) 434.0 UNABLE TO LOCATE PARAMETER NUMBER %1 IN VPS FOR INSTRUCTION %2 *** SYSTEM WARNING MESSAGE 435 (CSCXRF) 435.0 - - FILE ON OSCAR TRAILERS DURING OF UNEXPECTED END PROCESSING OF THE CROSS REFERENCE *** SYSTEM WARNING MESSAGE 435 (CSCDMP) 435.1 UNE XPECTED END - OF - FILE FOUND DURING PROCESSING OF CROSS REFERENCE. *** SYSTEM WARNING MESSAGE 436 (CSCDMP) 436.0 OPEN CORE OVERFLOW IN CROSS REFERENCE. CROSS REFERENCE TERMINATED. *** SYSTEM FATAL MESSAGE 437 (CSTORE) 437.0 LOGIC ERROR. TYPE VARIABLE %1 IS NOT VALID *** USER WARNING MESSAGE 438 (CSTRNG) 438.0 THE CHARACTER STRING ABOVE HAS BEEN TRUNCATED FROM %1 CHARACTERS TO THE CURRENT LIMIT OF 80 CHARACTERS User information: There is a limit of 80 characters for any single character string. It would be best to use two or more character parameters, rather than one.

41 *** USER FATAL MESSAGE 440 (CVIEW) 440.0 ERROR IN PARSING DBVIEW DMAP STATEMENT. *** SYSTEM FATAL MESSAGE 441 (CVIEW) 441.0 ERROR IN PROCESSING DBVIEW DMAP STATEMENT. OVERFLOW IN DBVIEW OSCAR TRAILER RECORD. USER ACTION: PLEASE NOTIFY SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 443 (DBALOC) 443.0 THE SUBDMAP %1 REFERENCED BY THE SOL, LINK OR COMPILE STATEMENT WAS NOT FOUND ON THE %2 DBSET. User information: See also Error Report 2992 in section 17.4 of NX NASTRAN Reference Manual. *** USER FATAL MESSAGE 444 (DBALOC) 444.0 LINKAGE OF THE SOLUTION SEQUENCE HAS FAILED BECAUSE THE OBJECT FILE FOR SUBDMAP %1 WAS NOT FOUND ON THE %2 DBSET. *** USER FATAL MESSAGE 445 (DBALOC) 445.0 THE EXECUTABLE (OSCAR) FILE FOR SUBDMAP %1WAS NOT FOUND ON THE %2 DBSET. USER INFORMATION: THE EXECUTABLE WAS NEVER CREATED. USER ACTION: SUBMIT RUN TO COMPILE AND LINK THIS SUBDMAP. *** SYSTEM FATAL MESSAGE 446 (XCL300) 446.0 ERROR ATTEMPTING TO %1 A FILE (LOGICAL= %2) FOR DBSET SCRATCH WITH READ AND WRITE PRIVILEGES. USER ACTION: CHE CK THE AVAILABLE/ALLOCATED SPACE AND THE PRIVILEGES GRANTED THIS ACCOUNT. User information: This may occur if BUFFSIZE is too large. See the NX NASTRAN Installation and Operations Instructions for maximum allowable value. This error may occur if the co rresponding ASSIGN statement references an incorrect physical file specification. Another possible cause is two restart jobs trying to access (read/write) the same database simultaneously. DBLOCATing (read only) the same ble. database by two jobs is accepta Another cause is if a restart is attempted from a database in which the MASTER is split into multiple physical files. An avoidance is to explicitly point to the physical name associated with the MASTER DBsets on ASSIGN statements. See Error Report 2953 in section 17.4 of NX NASTRAN Reference Manual. *** SYSTEM FATAL MESSAGE 446 446.1 ERROR ATTEMPTING TO CREATE A FILE (LOGICAL= %1) FOR DBSET %2 WITH READ AND WRITE PRIVILEGES.

42 USER ACTION: CHECK THE AVAILABLE/ALLOCATED SPACE AND THE PRIVILEGES GRANTED THIS ACCOUNT. *** SYSTEM FATAL MESSAGE 446 (DBCRT) 446.2 ERROR ATTEMPTING TO OPEN A FILE (LOGICAL= %1) FOR DBSET %2 WITH READ PRIVILEGE. EGE GRANTED THIS FILE. USER ACTION: CHECK THE READ PRIVIL *** SYSTEM FATAL MESSAGE 446 (DBCRT) 446.4 ERROR ATTEMPTING TO OPEN A FILE (LOGICAL= %1) FOR DBSET %2 WITH READ AND WRITE PRIVILEGES. USER ACTION: CHECK THE READ AND WRITE PRIVILEGES GRANTED THIS FILE. SYSTEM FATAL MESSAGE 447 (DBCRT) *** 447.0 ERROR ATTEMPTING TO CREATE A PHYSICAL FILE WITH READ_ONLY OPTION. USER INFORMATION: LOGICAL FILE = %1 OF DBSET %2 *** SYSTEM FATAL MESSAGE 449 (DBDEF2) 449.0 THE FILE ASSIGNMENT TABLE (DBSPACE) CONTAINS NO TION FOR THE %1 DBSET. INFORMA PROGRAMMER INFORMATION: THE XFIST1 ARRAY HAS INFORMATION ABOUT THIS DBSET EITHER BY DEFAULT OR AS STORED BY THE RDINIT SUBROUTINE AFTER PROCESSING INIT CARDS. THIS INFORMATION DOES NOT MATCH THE DBSPACE TABLE CONTENTS. *** SYSTEM FATAL MESSAGE 450 (DBMAP) 450.0 DBMAP FILE NOT IN FIST. UNABLE TO OPEN FOR DBSET = %1 *** SYSTEM FATAL MESSAGE 450 (DBDIR) 450.1 DBDIR FILE NOT IN FIST. UNABLE TO OPEN FOR DBSET = %1 *** SYSTEM FATAL MESSAGE 452 (DBNADD) 452.0 THE DATA BASE DIRECTORY FILE (DBNAME) IS FULL. NO ADDITIONAL SUBDMAPS CAN BE ADDED TO THE DBSET %1 USER ACTION: MODIFY COMPILE CARD TO STORE SUBDMAP ON A PREVIOUSLY USED DBSET PROGRAMMER INFORMATION: VARIABLES OF INTEREST ARE: DBNBOT = %2 DBNTOP = %3 LS TDBN = %4 DBSET = %5 *** USER FATAL MESSAGE 453 (LCXSIZ) 453.0 THE DATABASE WITH DBSNO=%1 DOES NOT CONTAIN A COMPILED NDDL. THE DBSNO NUMBERS ARE PRINTED NEAR THE TOP OF THE EXECUTION SUMMARY TABLE. *** USER FATAL MESSAGE 453 (LCXLOD) 453.1 THE DATABASE NUMBER (IDBSNO)=%1 BEING USED IN THIS RUN DOES NOT HAVE ENOUGH INFORMATION TO START FROM.

43 *** USER FATAL MESSAGE 453 (DBOLD) 453.2 THE DATABASE WITH DBSNO=%1 DOES NOT CONTAIN A COMPILED NDDL. OP OF THE THE DBSNO NUMBERS ARE PRINTED NEAR THE T EXECUTION SUMMARY TABLE. *** SYSTEM FATAL MESSAGE 457 (DBOLD) 457.0 INSUFFICIENT CORE TO READ ONE RECORD FROM THE FILE ASSIGNMENT (DBSPACE) TABLE USER ACTION: INCREASE OPEN CORE SIZE PROGRAMMER INFORMATION: NWDS = %1 THE AMOUNT OF OPEN CORE REQUIRED IN DBOLD IS : %2 * ( MAXIMUM NUMBER OF PHYSICAL FILES OF THE %3 DATABASE *** SYSTEM FATAL MESSAGE 458 (LCLDBS) 458.0 THE MASTER DBSET ON THE LOCATED DATABASE HAS A BUFFSIZE REQUIREMENT EXCEEDING THE BUFFSIZE USED FOR THIS RUN. USER INFORMATION: A SYSTEM BUFFER OF %1 HAS BEEN DEFINED FOR THIS RUN. USER ACTION: ADD FOLLOWING KEYWORD TO DATA DECK:%2BUFFSIZE=%3 *** SYSTEM FATAL MESSAGE 458 (DBOLD) 458.1 A DBSET ON THE %1 DATABASE HAS A BUFFS IZE REQUIREMENT EXCEEDING THE BUFFSIZE USED FOR THIS RUN. USER INFORMATION: A SYSTEM BUFFER OF %2 HAS BEEN DEFINED FOR THIS RUN. USER ACTION: ADD THE FOLLOWING KEYWORD TO THE NASTRAN (EMAS) CARD: BUFFSIZE=%3 *** SYSTEM FATAL MESSAGE 458 (DBDEF) 458.3 THE MASTER DBSET ON THE PRIMARY DATABASE HAS A BUFFSIZE REQUIREMENT EXCEEDING THE BUFFSIZE USED FOR THIS RUN. USER INFORMATION: A SYSTEM BUFFER OF %1 HAS BEEN DEFINED FOR THIS RUN. USER ACTION: ADD THE FOLLOWING KEYWORD TO THE %2 CARD: BUFFSIZE=%3 *** SYSTEM FATAL MESSAGE 458 (ATTDBS) 458.4 THE MASTER DBSET ON THE DELIVERY DATABASE HAS A BUFFSIZE REQUIREMENT EXCEEDING THE BUFFSIZE USED FOR THIS RUN. USER INFORMATION: A SYSTEM BUFFER OF %1 HAS BEEN DEFINED FOR THI S RUN. USER ACTION: ADD THE FOLLOWING KEYWORD TO THE NASTRAN CARD: BUFFSIZE=%2

44 *** USER FATAL MESSAGE 459 (DBPREQ) 459.0 SHORT RECORD ENCOUNTERED IN TRANSACTION FILE (%1). USER INFORMATION: THIS INDICATES THAT THE DATABASE HAS IS IRRECOVERABLE. BEEN DESTROYED AND - GENERATE THE DATABASE. USER ACTION: DELETE AND RE *** USER FATAL MESSAGE 460 (DBPREQ) 460.0 THE TRANSACTION TABLE HAS EXCEEDED AVAILABLE OPEN CORE. USER ACTION: RE - SUBMIT THIS JOB WITH A LARGER HICORE ATTACHED TO CLEAN UP THE AND WITH ALL DBSETS TRANSACTION FILE USER INFORMATION: SEE THE EXECUTION SUMMARY FILE FOR THE LIST OF UNATTACHED DBSETS. *** USER FATAL MESSAGE 461 (DBSCIN) 461.0 THE PHYSICAL FILE ASSIGNED TO THE %1 DBSET ALREADY EXISTS. USER ACTIONS: DELET E THE FOLLOWING FILE AND RESUBMIT THE JOB. %2 *** USER FATAL MESSAGE 462 (DBSPC) 462.0 THE FOLLOWING PHYSICAL FILE NAME EXCEEDS THE MAXIMUM NUMBER OF CHARACTERS ALLOWED. %1 USER INFORMATION: THE CURRENT LIMIT IS %2 CHARACTERS. *** USER FATAL MESSAGE 462 (DBSEXP) 462.1 THE PHYSICAL FILE NAME FOLLOWING EXCEEDS THE MAXIMUM NUMBER OF CHARACTERS ALLOWED NAMES IN THE DBSPACE TABLE %1 USER INFORMATION: THE CURRENT LIMIT IS %2 CHARACTERS. *** USER FATAL MESSAGE 463 (DBSPC) 463.0 THE NU MBER OF ASSIGNED PHYSICAL FILE NAMES FOR THE %1 DBSET EXCEEDS %2 User information: There is a limit on the number of physical files which may exist in one DBSET. Check Section 2 in the NX NASTRAN Quick Reference Guide for the limits. If you need more f iles than are allowed, there are several options: 1)Create a new DBSET; 2) Use DBUNLOAD and DBLOAD to unload the DBSET and then to load it back using larger files. *** USER FATAL MESSAGE 465 465.0 THE LINK TABLE FOR SUBDMAP %1 DOES NOT EXIST. US ER ACTIONS: 1. ENSURE THAT THE SUBDMAP IS THE APPROPRIATE MAIN

45 SUBDMAP 2. ENSURE THAT THE SUBDMAP WAS LINKED PROPERLY. USER INFORMATION: THE LINK TABLE IS DESCRIBED UNDER THE LINK STATEMENT. *** USER FATAL MESSAGE 465 (OSCRIN) 465.1 THE OSCAR LIST FILE FOR SUBDMAP %1 IS EMPTY, OR IT WAS NEVER CREATED. USER ACTIONS: 1. MAKE SURE THAT THE SUBDMAP WAS CREATED AS A MAIN SUBDMAP 2. MAKE SURE THAT THE SUBDMAP WAS LINKED PROPERLY. *** SYSTEM FATAL MESSAGE 466 (DBSWRT) 466.1 T TO WRITE FILE ASSIGNMENT (DBSPACE) TABLE TO ATTEMP MASTER DBSET FAILED. - RESIDENT FILE ASSIGNMENT (DBSPACE) TABLE IS THE CORE EMPTY USER ACTION: SEND RUN TO SIEMENS PLM SOFTWARE CUSTOMER SUPPORT PROGRAMMER INFORMATION: VALUES OF INTEREST %2 LSTDBS = %3 DBSTOP = %1 DBSBOT = IF THE ABOVE VALUES SEEM UNREASONABLE THEN /XSPACE/ COMMON BLOCK HAS BEEN OVERWRITTEN *** USER FATAL MESSAGE 467 467.0 THE MAXIMUM NUMBER OF CALLS WITHIN %1 MAIN SUBDMAP HAS BEEN EXCEEDED. USER INFORMATION: THE MAXIMUM NUMBER OF C ALLS IN THIS VERSION IS %2 User information: Combine subDMAPs in order to alleviate this problem. *** USER FATAL MESSAGE 467 (OSCRIN) 467.1 THE MAXIMUM NUMBER OF CALLS WITHIN %1 MAIN SUBDMAP HAS BEEN EXCEEDED. USER INFORMATION: THE MAXIMUM NUMBER OF CALLS IN THIS VERSION IS 50 *** USER FATAL MESSAGE 468 468.0 THE DBSET %1 IS NOT PART OF ANY DATA BASE ATTACHED TO THIS RUN, INDICATING IT WAS NOT ALLOCATED FOR THIS RUN. *** SYSTEM FATAL MESSAGE 469 (DGETTS) 469.0 THE WRONG TIME STAMP BLOCK WAS READ FOR THE FOLLOWING PHYSICAL FILE NAME: %1 User information: Each database file created by NX NASTRAN contains a "time stamp" indicating the time the file was initially created. The M ASTER dbset

46 contains a record of these time stamps and NX NASTRAN compares these values. This message indicates that a file attached has a different time stamp than expected. Check the files to verify they are correct. s a System Cell (135 or TSTAMP) that If you are sure they are, there i turns off this checking. *** USER FATAL MESSAGE 470 (LCLDBS) 470.0 THE LOGICAL NAME %1 WAS ASSIGNED TO THE FOLLOWING PHYSICAL FILE, WHICH DOES NOT EXIST. %2 %3 USER ACTION: CHECK FILE ASSIGNMENTS. *** SYSTEM FATAL MESSAGE 471 (DGETTS) 471.0 ERROR ATTEMPTING TO CLOSE THE FOLLOWING PHYSICAL FILE NAME: %1 *** SYSTEM FATAL MESSAGE 471 (DGETTS) 471.1 ERROR ATTEMPTING TO OPEN THE FOLLOWING PHYSICAL FILE NAME (PFILEX=%1) : %2 USER ACTION: 1) CHECK THE READ/WRITE PRIVILEGES GRANTED THIS FILE. 2) CHECK MAXIMUM NUMBER OF FILES THAT MAY BE OPENED SIMULTANEOUSLY. 3) CHECK THAT THIS DATABASE FILE IS COMPATIBLE WITH THIS PLATFORM. 4) ENSURE THAT NO OTHER JOB HAS OPENED THE DATABASE FOR UPDATING. User information: NX NASTRAN is attempting to read information from a file for which the system is not allowing access. *** SYSTEM FATAL MESSAGE 471 (DPR3IJ/DPSP23/DSECAS) 471.2 ERROR ATTEMPTING TO OPEN DATA BLOCK FILE NUMBER %1 USER ACTION: CONTACT CUSTOMER SUPPORT *** USER FATAL MESSAGE 472 (DBSEXP) 472.0 THE PHYSICAL FILE FOLLOWING AND REFERENCED BY THE EXPAND COMMAND WITH THE LOGICAL NAME OF %1 ALREADY EXISTS. %2 USER INFORMATION: FILES BEING ASSIGNED BY EXPAND COMMA NDS CANNOT EXIST PRIOR TO THEIR ASSIGNMENTS. *** USER INFORMATION MESSAGE 474 (GNADD) 474.0 THE %1 FOR SUBDMAP %2 HAS BEEN REPLACED BY THE CURRENT ONE ON %3 DBSET *** SYSTEM FATAL MESSAGE 475 (GNADD) 475.0

47 LOGIC ERROR - THE %1 FOR SUBDMAP %2 HAS BEEN EQUIVALENCED TO ANOTHER FILE (SUBDMAP) IN DBSET %3 USER ACTION: SET THE OBJOUT OR OSCAROUT OF THIS SUBDMAP TO SCRATCH DBSET. *** USER FATAL MESSAGE 476 (GPFILX) 476.0 THE LOGICAL NAME %1 ASSIGNED TO A P HYSICAL FILE NAME OF THE %2 DATA BASE, DOES NOT EXIST. USER INFORMATION: PHYSICAL FILE NAME = %3 *** USER FATAL MESSAGE 477 (GPFILX) 477.0 THE LOGICAL NAME %1 OF THE %2 DATABASE IS AUTO - ASSIGNED TO THE FOLLOWING ASSOCIATED PHYSICAL FILE NAME:%3 THE TIME STAMP OF THIS PHYSICAL FILE DOES NOT MATCH THE ONE IN THE FILE ASSIGNMENT (DBSPACE) TABLE. - USER ACTION: CHECK OR RE CREATE THE %4 DATABASE TO RESOLVE THIS ERROR *** SYSTEM FATAL MESSAGE 478 (GPFILX) 478.0 OF THE %1 DATA BASE, THE FOLLOWING LOGICAL NAME, PART HAS A NULL TIME STAMP. USER INFORMATION: LOGICAL NAME = %2 *** USER FATAL MESSAGE 479 (LCLDBS) 479.0 THE REQUESTED LOGICAL NAME %1 WAS NOT ASSIGNED. USER ACTION: CHECK FILE ASSIGNMENTS. User information: This error may be i ssued if the LOGICAL keyword on DBLOCATE references a reserved logical name such as DBC, PUNCH, etc. *** SYSTEM INFORMATION MESSAGE 480 480.0 JOB TERMINATED DUE TO ABOVE ERROR(S) *** SYSTEM INFORMATION MESSAGE 480 (XSEMIN) 480.1 JOB TERMINATED DUE TO ENDJOB OPTION. *** SYSTEM INFORMATION MESSAGE 480 (XSEMIN) 480.2 JOB TERMINATED DUE TO NOEXE OPTION ON SOL CARD OR NOGO OPTION ON COMPILER CARD. *** SYSTEM INFORMATION MESSAGE 480 (XSEMIN) 480.3 JOB TERMINATED DUE TO LACK OF SOL CARD IN EXECUTIVE CONTROL SECTION. *** SYSTEM INFORMATION MESSAGE 480 (XSEMIN) 480.4 JOB TERMINATED DUE TO ABOVE ERRORS IN THE DMAP/NDDL LINKAGE EDITOR (LINKER) *** SYSTEM INFORMATION MESSAGE 480 (XSEM IN) 480.5 JOB TERMINATED DUE TO ABOVE ERRORS IN THE DMAP COMPILER (XGPI) *** SYSTEM INFORMATION MESSAGE 480 (XSEMIN) 480.6

48 JOB TERMINATED DUE TO ABOVE ERRORS IN THE NDDL COMPILER. *** SYSTEM INFORMATION MESSAGE 480 (XSEMIN) 480.7 JOB TERMINATED DUE TO ABOVE ERRORS IN THE NDDL AND DMAP COMPILERS. *** USER INFORMATION MESSAGE 480 (XSEMIN) 480.8 JOB TERMINATED DUE TO LACK OF SOL, COMPILE, OR LINK CARDS IN THE EXECUTIVE CONTROL SECTION. *** SYSTEM INFORMATION MESSAGE 480 480.9 JOB TERMINATED DUE TO ABOVE ERROR(S) IN THE FILE MANAGEMENT SECTION. *** SYSTEM INFORMATION MESSAGE 480 (LCLDBS) 480.11 JOB TERMINATED DUE TO ABOVE ERRORS IN THE LCLDBS/DBLOCATE *** SYSTEM INFORMATION M ESSAGE 480 (DBINIT) 480.12 JOB TERMINATED DUE TO ENDJOB OPTION *** USER/SYSTEM FATAL/WARNING/INFORMATION MESSAGE 480 480.16 (EVLMSG) JOB TERMINATED DUE TO ABOVE ERROR(S) IN THE %1 STATEMENT PROCESSOR. *** SYSTEM INFORMATION MESSAGE 482 (UNDRVR) 482.0 NO %1 DATA HAS BEEN UNLOADED FROM THE DATABASE TO UNIT %2. *** SYSTEM INFORMATION MESSAGE 482 (UNDRVR) 482.1 %1 PARAMETER(S) HAVE BEEN UNLOADED FROM THE DATABASE TO UNIT %2 IN %3 FORMAT. *** SYSTEM INFORMATION MESSAGE 482 (UNDRVR) 482.2 %1 DATABLOCK(S) HAVE BEEN UNLOADED FROM THE DATABASE TO UNIT %2 IN %3 FORMAT. *** SYSTEM INFORMATION MESSAGE 482 (LDDRVR) 482.3 NO %1 DATA HAS BEEN LOADED TO THE DATABASE FROM UNIT %2. *** SYSTEM INFORMATION MESSAGE 482 (LDDRVR) 482.4 %1 PARAMETER(S) HAVE BEEN LOADED TO THE DATABASE FROM UNIT %2 IN %3 FORMAT. *** SYSTEM INFORMATION MESSAGE 482 (LDDRVR) 482.5 %1 DATABLOCK(S) HAVE BEEN LOADED TO THE DATABASE FROM UNIT %2 IN %3 FORMAT. *** SYSTEM INFORMATION MESSAGE 482 (LCDRVR) 482.6 NO DATA HAS BEEN LOCATED ON THE %1 DATABASE. *** SYSTEM INFORMATION MESSAGE 482 (LCDRVR) 482.7 %1 PARAMETER(S) HAVE BEEN LOCATED ON THE %2 DATABASE.

49 System information: This is an information message which results when using DBLOCATE. *** SYSTEM INFORMATION MESSAGE 482 (LCDRVR) 482.8 %1 DATABLOCK(S) HAVE BEEN LOCATED ON THE %2 DATABASE. System information: DBLOCATE. This is an information message which results when using *56* SYSTEM INFORMATION MESSAGE 482 (DBEQIV) 482.9 NO DATA HAS BEEN LOCATED ON THE PRIMARY DATABASE. *56* SYSTEM INFORMATION MESSAGE 482 (DBEQIV) 482.10 %1 PARAMETER(S) HAVE BEEN LOCATED ON THE PRIMARY DATABASE. SYSTEM INFORMATION MESSAGE 482 (DBEQIV) *56* 482.11 %1 DATABLOCK(S) HAVE BEEN LOCATED ON THE PRIMARY DATABASE. *56* SYSTEM INFORMATION MESSAGE 482 (DBDELE) 482.12 NO DATA HAS BEEN DELETED ON THE PRIMARY DATABASE. *56* SYSTEM INFORMATION MESSAGE 482 (DBDELE) 482.13 %1 PARAMETER(S) HAVE BEEN DELETED ON THE PRIMARY DATABASE. *56* SYSTEM INFORMATION MESSAGE 482 (DBDELE) 482.14 %1 DATABLOCK(S) HAVE BEEN DELETED ON THE PRIMARY DATABASE. *** USER FATAL MESSAGE 4 83 (UNLDBP) 483.0 THE %1 NAME = %2 CANNOT BE FOUND IN THE NDDL OF THE PRIMARY DATA BASE. USER ACTION: MAKE SURE THAT THE ABOVE %3 NAME EXISTS IN THE NDDL OF THIS DATABASE. *** USER FATAL MESSAGE 483 (LCDRVR) 483.1 THE DATABLOCK/PARAMETER NAME = %1 CANNOT BE FOUND IN THE NDDL OF %2 DATA BASE. USER ACTION: MAKE SURE ABOVE DATABLOCK/PARAMETER NAME EXISTS IN THE NDDL OF THIS DATA BASE. *** USER FATAL MESSAGE 483 483.2 THE DATABLOCK/PARAMETER NAME = %1 CANNOT BE FOUND IN THE NDDL OF PRIMARY DATA BASE. USER ACTION: MAKE SURE ABOVE DATABLOCK/PARAMETER NAME EXISTS IN THE NDDL OF THIS DATA BASE. *** SYSTEM FATAL MESSAGE 485 (TMALOC) 485.0 THE QUALIFIER NAME %1 CANNOT BE FOUND IN THE PATH TABLE *** SYSTEM FATAL MESSAGE 487 (VWDRVR) 487.0 THE KEY USED IN CREATING THE DBVIEW DATA BLOCK WAS

50 NOT FOUND. USER ACTION: SEND RUN TO SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 487 (LCFENT) 487.1 THE PATH USED IN CREATING THE LOCATE D ATA BLOCK WAS NOT FOUND. *** SYSTEM WARNING MESSAGE 487 (DIRPT3) 487.2 THE QUALIFIER USED IN SEARCHING FOR DATA BLOCKS WAS NOT FOUND. USER ACTION: SEND RUN TO SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 487 (DBALO2) 487.3 THE PATH USED IN CREATING THE LOCATE DATA BLOCK WAS NOT FOUND. USER ACTION: SEND RUN TO SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 493 (VWDRVR) 493.0 QUALIFIERS THE LENGTH OF THE STRING WHICH HOLDS THE AND THEIR VALUES FOR DATABLOCK %1 EXCEEDS THE LIMIT OF%2. USER ACTION: 1) REDUCE NUMBER OF QUALIFIERS FOR THE DATABLOCK IN THE NDDL SEQUENCE. 2) CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: 1) WLEN = %3 %4 2) NWLEN = 3) STRING = *** SYSTEM FATAL MESSAGE 494 (LTMVPS) 494.0 THE TEMPORARY VPS TABLE USED IN PROCESSING USER - SUPPLIED EQUATIONS HAS OVERFLOWED. USER ACTIONS: SIMPLIFY EQUATION AND NOTIFY SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. USER WARNING MESSAGE 495 (DBSPC) *** 495.0 THE BUFFSIZE OF DBSET %1, ON DATABASE NUMBER %2 IS UNABLE TO BE PROCESSED. A SYSTEM DEFAULT BUFFSIZE = %3 HAS BEEN SELECTED FOR THIS DBSET. *** USER FATAL MESSAGE 496 (XCSOL2) 496.0 THE DBSET NAME %1 IS NOT IN THE DBSPACE TABLE USER INFORMATION: THE DBSET WAS NOT ASSIGNED TO THIS RUN USER ACTIONS: CHECK SPELLING OF DBSET NAME AND ASSIGNMENT OF CORRECT MASTER DBSET TO THIS RUN

51 *** USER FATAL MESSAGE 497 (OSCRIN) 497.0 THE DBSET %1 CONTAINING THE EXECUTABLES (OSCARS) HAS BEEN ATTACHED TO THIS RUN. USER ACTION: REMOVE SOLIN KEYWORD FROM THE SOL CARD TO LINK THIS SOLUTION SEQUENCE. *** USER WARNING MESSAGE 498 (DBSPC) 498.0 YOU HAVE SELECTED A BUFFER SIZE OF %1 FO R THE MASTER DBSET, WHICH IS DIFFERENT THAN SCRATCH BUFFER SIZE OF%2 THIS IS NOT ALLOWED WITH MASTER(RAM) OPTION. THE SCRATCH BUFFER SIZE %3 HAS BEEN SELECTED. *** USER WARNING MESSAGE 498 (DBSPC) 498.1 YOU HAVE SELECTED A BUFFER SIZE OF %1 FOR T HE SCRATCH DBSET, WHICH IS DIFFERENT THAN MASTER BUFFER SIZE OF%2 THIS IS NOT ALLOWED WITH MASTER(RAM) OPTION. THE SCRATCH BUFFER SIZE %3 HAS BEEN SELECTED. *** USER INFORMATION MESSAGE 499 (PRLINK) 499.0 SUBDMAP %1 WILL BE LINKED. *** USER FATAL MESSAGE 500 (GETLIN) 500.0 I/O ERROR ENCOUNTERED READING %2 FILE. IOSTAT = %1. USER ACTION: CHECK STATUS OF FILE OR FILESYSTEM. FILE IS '%3' ERROR MESSAGE IS '%4' *** SYSTEM FATAL MESSAGE 501 (GETLIN) 501.0 INTERNAL LOGIC ERROR ENCOUNT ERED. INCLUDE PROCESSING FOUND INVALID HANDLE. HANDLE VALUE IS %1. *** USER FATAL MESSAGE 502 (CVIEW1) 502.0 THE VIEW NAME AND DATABLOCK NAME ARE IDENTICAL ON THE DBVIEW %1 = %1 STATEMENT. *** USER FATAL MESSAGE 505 (XCSA) 505.0 CONTROL CARD %1 IS ILLEGAL User information: The statement preceding Message 505 cannot be processed correctly. This message may also be issued if an invalid character; such as a control character appears on the statement. See Table 1 in or valid characters. Section 3.1 f *** USER FATAL MESSAGE 506 (XCSA) 506.0 CONTROL CARD %1 DUPLICATED User information: The statement preceding Message 506 cannot be input more than once. *** USER FATAL MESSAGE 507 (XCSA) 507.0 ILLEGAL SPECIFICATION OR FORMAT ON PRECEDING CARD User information:

52 Executive control statements cannot have equal (=) signs. *** USER FATAL MESSAGE 508 (XCSA) 508.0 PROBLEM TAPE MUST BE ON PHYSICAL TAPE FOR CHECK POINTING *** SYSTEM FATAL MESSAGE 510 (XCSA) 510.0 REMAINING CHECKPOINT DICTIONARY EXCEEDS CORE SIZE - RESTART CARDS IGNORED *** SYSTEM FATAL MESSAGE 511 (XCSA) 511.0 DMAP SEQUENCE EXCEEDS CPRE SIZE - REMAINING DMAP INSTRUCTIONS IGNORED System information: There is no more open core. Split the DMAP sequence somewhere prior to where Message 511 was printed out. *** SYSTEM FATAL MESSAGE 511 (XCSA) 511.1 - REMAINING NDDL NDDL SEQUENCE EXCEEDS CORE SIZE INSTRUCTIONS IGNORED *** USER FATAL M ESSAGE 512 (XCSA) 512.0 OLD PROBLEM TAPE IS MISSING AND IS NEEDED FOR RESTART *** USER FATAL MESSAGE 515 (XCSA) 515.0 END INSTRUCTION MISSING IN DMAP SEQUENCE User information: DMAP sequence must end with END control card. (END must begin in column 1.) *** USER FATAL MESSAGE 519 (XCSA) 519.0 ID CARD MUST PRECEDE ALL OTHER CONTROL CARDS User information: ID statement must come before all other statements except the RAN and FMS statements. Although the ID statement is documented NAST as being an optional comment statement, if it is used, it must be before all other Executive Control statements. *** USER FATAL MESSAGE 520 (XCSA) 520.0 CONTROL CARD %1 IS MISSING *** USER FATAL MESSAGE 521 (XCSA) 521.0 SPECIFY A SOLUTION OR A DMAP SEQUENCE, BUT NOT BOTH *** USER FATAL MESSAGE 522 (XCSA) 522.0 NEITHER A VALID SOL CARD NOR A DMAP SEQUENCE WAS INCLUDED *** USER FATAL MESSAGE 526 (XCSA) 526.0 CHECKPOINT DICTIONARY OUT OF SEQUENCE - REMAINING RESTART CARDS IGNORED *** USER FATAL MESSAGE 527 (DOMSOL) 527.0 THE VALUE ASSIGNED TO THE DOMAIN SOLVER OPTION %1 IS

53 INVALID OR MISSPELLED. *** USER FATAL MESSAGE 528 (DOMSOL) 528.0 THE %1 D OMAIN SOLVER METHOD IS INVALID OR MISSPELLED. *** USER FATAL MESSAGE 529 (DOMSOL) 529.0 THE DOMAIN SOLVER OPTION %1 IS INVALID OR MISSPELLED. *** USER FATAL MESSAGE 530 (DOMSOL) 530.0 THE DOMAIN SOLVER OPTION %1 IS NOT SUPPORTED FOR THE %2 METHOD. *** SYSTEM WARNING MESSAGE 531 (DOMSOL) 531.0 THE %1 DOMAIN SOLVER METHOD IS NOT SUPPORTED IN THE %2 SOLUTION SEQUENCE. USER INFORMATION: THE DOMAIN SOLVER METHOD WILL BE IGNORED FOR THIS RUN. *** USER FATAL MESSAGE 532 (DOMSOL) 532.0 THE SELECTED COMBINATION OF DOMAIN SOLVER METHODS %1 IS NOT SUPPORTED IN THE %2 SOLUTION SEQUENCE. *** SYSTEM WARNING MESSAGE 533 (DOMSOL) 533.0 THE NUMBER OF PROCESSORS SPECIFIED ON THE DMP KEYWORD OF THE NASTRAN SUBMITTAL COMMAND -- DMP=%3 -- IS NOT EQUAL TO THE NUMBER OF DOMAINS SPECIFIED FOR THE %1 DOMAIN SOLVER METHOD -- NUMDOM=%2. USER INFORMATION: NUMDOM WILL BE RESET TO %3. ER FATAL MESSAGE 534 (DOMSOL) *** US 534.0 THE %1 DOMAIN SOLVER METHOD IS NOT SUPPORTED IN A %2 RUN. *** SYSTEM WARNING MESSAGE 535 (DOMSOL) 535.0 THE NUMBER OF DOMAINS SPECIFIED FOR THE FDMODES -- NUMDOM=%2 -- DOMAIN SOLVER METHOD EXCEEDS THE MAXIMUM LIMIT OF %1. USER INFORMATION: NUMDOM WILL BE RESET TO %1. *** USER FATAL MESSAGE 536 (DOMSOL) 536.0 THE NUMBER OF DOMAINS HAS NOT BEEN SPECIFIED. USER INFORMATION: FOR SERIAL EXECUTION OF THE %1 DOMAIN SOLVER METHOD, NUMDOM MUST BE SPECIFIED. * ** USER WARNING MESSAGE 600 (IFP1D) 600.0 NO TEXT AVAILABLE FOR MESSAGE %1 *** USER WARNING/FATAL MESSAGE 601 (IFP1D) 601.0 THE KEYWORD ON THE ABOVE CARD TYPE IS ILLEGAL OR MISSPELLED. User information: Case Control expects each command to begin with a keyword (usually 4 characters in length). To remove the error, consult the Case Control

54 command descriptions, Section 4 of the NX NASTRAN Quick Reference Guide, and spell your request correctly. curs for SURFACE and VOLUME commands that are not in the This oc OUTPUT(POST) section. *** USER WARNING/FATAL MESSAGE 602 (IFP1D) 602.0 TWO OR MORE OF THE ABOVE CARD TYPES DETECTED WHERE ONLY ONE IS LEGAL. THE LAST FOUND WILL BE USED. User information: Remove the command with the duplicate meaning. Note that some commands have alternate forms. *** USER WARNING MESSAGE 602 (IFP1) 602.1 TWO OR MORE DESCRIBERS OF CKGAP(GRID, GAUSS, BOTH) ARE DETECTED. ONLY THE LAST FOUND WILL BE USED. *** USER WARNING/FATAL MESSAGE 603 (IFP1D) 603.0 THE ABOVE CARD DOES NOT END PROPERLY. COMMENTS SHOULD BE PRECEDED BY A DOLLAR SIGN. User information: - Case Control commands of the form, name value, should not contain more than one value. Consult the Case Control command descriptions, Section 4 of the NX NASTRAN Quick Reference Guide, for a complete description of the command or precede the comments with a dollar sign. *** USER WARNING/FATAL MESSAGE 604 (IFP1D) 604.0 - GER IN AN INTEGER FIELD. THE ABOVE CARD HAS A NON INTE User information: Consult the Case Control command descriptions, Section 4 of the NX NASTRAN Quick Reference Guide, for legal values. *** USER WARNING/FATAL MESSAGE 605 (IFP1D) 605.0 UT A SYMCOM OR A SYMSEQ OR SUBSEQ CARD APPEARS WITHO SUBCOM CARD. User information: SYMSEQ or SUBSEQ commands must appear in a subcase defined by a SYMCOM or SUBCOM command. Check the Case Control and relabel the combination subcase. *** USER WARNING/FATAL MESSAGE 606 (IFP1D) 606.0 INVALID USE OF TEMPERATURE DEPENDENT MATERIALS OCCURS AT THE SUBCASE LEVEL. ONLY ONE SUCH CARD IS ALLOWED PER PROBLEM OR PER SUPERELEMENT. *** USER WARNING/FATAL MESSAGE 607 (IFP1D) 607.0 A REPCASE CARD MUST BE PRECEDED BY A SUBCASE CARD User in formation: A REPCASE subcase is an attempt to reoutput the previously computed

55 case; therefore, it cannot be the first subcase. *** USER WARNING/FATAL MESSAGE 608 (IFP1D) 608.0 THE SET ID SPECIFIED ON THE ABOVE CARD MUST BE DEFINED CARD. PRIOR TO THIS User information: Set identification numbers must be specified prior to their use. Also sets specified within a subcase are valid only within that subcase. Redefine the errant set (or define a required set) or move the set out is in. of the subcase it *** USER WARNING/FATAL MESSAGE 609 (IFP1D) 609.0 THE SUBCASE NUMBER SPECIFIED VIOLATES ONE OR MORE OF THE FOLLOWING RULES : A. EACH MUST BE A POSITIVE INTEGER. B. EACH MUST BE GREATER THAN THE PREVIOUS. C. EACH MUST BE LESS THAN 9999999. *** USER WARNING/FATAL MESSAGE 610 (IFP1D) 610.0 THE VALUE FOLLOWING THE EQUAL SIGN ON THE ABOVE CARD IS ILLEGAL. User information: Case control cannot identify the value after the equal sign. Consult on 4 of the NX NASTRAN the Case Control command descriptions, Secti Quick Reference Guide. For example, only real data can follow SUBSEQ -- not integers. and SUBCOM commands *** USER WARNING/FATAL MESSAGE 611 (IFP1D) 611.0 TEN CARDS HAVE ILLEGAL KEY WORDS. THE PROGRAM ASSUMES BEGIN BULK CARD IS MISSING. IT WILL NOW PROCESS YOUR BULK DATA. User information: In Case Control, only ten key words may be misspelled. A common source of this error may be the omission of the OUTPU T(PLOT) or OUTPUT(XYOUT) delimiter commands. *** USER WARNING/FATAL MESSAGE 612 (IFP1D) 612.0 DUPLICATE KEYWORDS ENCOUNTERED ON ABOVE CARD. *** USER WARNING/FATAL MESSAGE 613 (IFP1D) 613.0 THE ABOVE SET CONTAINS - EXCEPT - WHICH IS NOT PRECE DED BY - - . THRU User information: Only identification numbers included by the THRU keyword may be expected. Simplify the SET request. *** USER WARNING/FATAL MESSAGE 614 (IFP1D) 614.0 THE ABOVE SET IS BADLY SPECIFIED. User information: Simplify the SET list.

56 *** USER WARNING/FATAL MESSAGE 615 (IFP1D) 615.0 AN IMPROPER OR NO NAME GIVEN TO THE ABOVE SET. User information: SET lists must have integer names. This SET list does not have one. SET 10 = is an example of the correct fo rmat. Give the SET a correct integer name. *** USER WARNING/FATAL MESSAGE 616 (IFP1D) 616.0 EXCEPT - CANNOT BE FOLLOWED BY - THRU - . LIST EXPLICITLY - ALL EXCEPTIONS. User information: EXCEPT in SET list can only be followed by integers. An integer larger than the THRU pair terminates the THRU. Either list exceptions explicitly, use two THRUs or terminate the first THRU. *** USER WARNING/FATAL MESSAGE 617 (IFP1D) 617.0 A NON POSITIVE INTEGER APPEARS IN A POSITIVE POSITION User information: Most integer values specified on Case Control command must be positive. The above command either has a negative integer or a character value in a positive position. See Section 4 of the NX NASTRAN Quick Reference Guide. SAGE 618 (IFP1D) *** USER FATAL MES 618.0 INVALID DESCRIBER ON RIGID CASE CONTROL CARD. USER INFORMATION: THE VALID DESCRIBERS ARE LINEAR AND LAGRANGE *** USER FATAL MESSAGE 619 (IFP1D) 619.0 THE RIGID CASE CONTROL CARD MUST COME BEFORE THE FIRST SUBCASE CARD *** USER FATAL MESSAGE 620 (IFP1D) 620.0 THE UNIT KEYWORD IS MISSING FROM THE MBDEXPORT OP4 COMMAND *** USER FATAL MESSAGE 621 (IFP1) 621.1 WHEN THE RMAXMIN CARD IS USED FOR SOLUTION SEQUENCE 101, ALL SUBCASES MUST MAKE IDENTICAL OUTPUT REQUESTS. THI S RUN CONTAINS DIFFERENT OUTPUT REQUESTS FOR STRESS. THE RMAXMIN REQUEST HAS BEEN DISABLED FOR THIS RUN. *** USER FATAL MESSAGE 621 (IFP1) 621.2 WHEN THE RMAXMIN CARD IS USED FOR SOLUTION SEQUENCE 101, ALL SUBCASES MUST MAKE IDENTICAL OUTPUT REQ UESTS. THIS RUN CONTAINS DIFFERENT OUTPUT REQUESTS FOR DISPLACEMENT. THE RMAXMIN REQUEST HAS BEEN DISABLED FOR THIS RUN.

57 *** USER FATAL MESSAGE 621 (IFP1) 621.3 WHEN THE RMAXMIN CARD IS USED FOR SOLUTION SEQUENCE 101, ALL SUBCASES MUST MAKE IDENTICAL OUTPUT REQUESTS. THIS RUN CONTAINS DIFFERENT OUTPUT REQUESTS FOR ELEMENT FORCE. THE RMAXMIN REQUEST HAS BEEN DISABLED FOR THIS RUN. *** USER WARNING MESSAGE 622 (IFP1D) 622.0 IC(TZERO) IS ONLY VALID FOR SOLUTION SEQUENCE 112 (SEMTRAN); IT WILL BE IGNORED FOR THIS SOLUTION. *** USER WARNING MESSAGE 623 (IFP1D) 623.0 SUBCOM OR SYMCOM COMBINES A SUBCASE CONTAINING A TEMP(LOAD) OR TEMP(BOTH) CARD; HOWEVER, THE SUBCOM OR SYMCOM DOES NOT CONTAIN A TEMP(LOAD) CARD. THUS, THE SUBCOM OR SYMCOM MAY INCORRECTLY ACCOUNT FOR THE EFFECTS OF THE TEMP(LOAD) IN THE SUBCASE. *** USER WARNING MESSAGE 624 (IFP1D) 624.0 SUBCOM OR SYMCOM COMBINES A SUBCASE CONTAINING A DEFORM CARD; HOWEVER, THE SUBCOM OR SYMCOM DOES NOT CONTAIN A DEFORM CARD. THUS, THE SUBCOM OR SYMCOM MAY INCORRECTLY ACCOUNT FOR THE EFFECTS OF THE DEFORM IN THE SUBCASE. *** USER WARNING/FATAL MESSAGE 625 (IFP1D) 625.0 E TYPE CARD. ALL ID - S TOO LARGE ID ON PRECEDING SUBCAS MUST BE LESS THAN 9,999,999 User information: Reduce the size of the subcase identification number. Note also that character string subcase identification numbers are not legal. D) *** USER WARNING/FATAL MESSAGE 626 (IFP1 626.0 SUBCOM SUBCASE DOES NOT HAVE A SUBSEQ CARD. User information: A SUBCOM SUBCASE must contain a SUBSEQ command to define the linear combination coefficients. *** USER WARNING/FATAL MESSAGE 627 (IFP1D) 627.0 THE ABOVE SUBCASE HAS BOTH A STATIC LOAD AND A REAL EIGENVALUE METHOD SELECTION -- REMOVE ONE. User information: The buckling solution requires two subcases: one for statics and

58 one for buckling. Both a load and a method selection cannot appear me subcase. in the sa *** USER WARNING/FATAL MESSAGE 628 (IFP1D) 628.0 THERMAL, DEFORMATION, AND EXTERNAL LOADS CANNOT HAVE THE SAME SET IDENTIFICATION NUMBER. User information: Set IDs specified on the LOAD, TEMP(LOAD), and DEFRM Case Control commands mu st be unique. *** USER WARNING/FATAL MESSAGE 629 (IFP1D) 629.0 ECHO CARD HAS REPEATED OR UNRECOGNIZABLE SPECIFICATION DATA. REPEATED SPECIFICATIONS WILL BE IGNORED. UNRECOGNIZABLE SPECIFICATIONS WILL BE TREATED AS SORT. User information: tion 4 of the NX NASTRAN Quick Reference Guide. See Sec *** USER WARNING/FATAL MESSAGE 630 (IFP1D) 630.0 ECHO CARD WITH NONE - SPECIFICATION HAS ADDITIONAL - SPECIFICATIONS WHICH WILL BE IGNORED. User information: See Section 4 of the NX NASTRAN Quick Reference Guide. *** USER WARNING/FATAL MESSAGE 631 (IFP1D) 631.0 TWO OR MORE TEMPERATURE(INIT) CARDS AND/OR TEMPERATURE(MATE) CARDS DETECTED WHERE ONLY ONE IS ALLOWED. User information: Only one TEMPERATURE( INIT) or TEMPERATURE(MATE) command is required for temperature initialization. Remove the extra command(s). *** USER WARNING/FATAL MESSAGE 632 (IFP1D) 632.0 USING THE MATERIAL OPTION IN THE TEMPERATURE CASE CONTROL CARD WILL RESULT IN UPDATING OF MATERIAL PROPERTIES ONLY ONCE. USE THE INITIAL OPTION IN THE TEMPERATURE CASE CONTROL CARD FOR UPDATING OF MATERIAL - PROPERTIES AT EVERY LOAD ITERATION IN MATERIAL NON LINEAR ANALYSIS. *** USER WARNING/FATAL MESSAGE 633 (IFP1D) 633.0 I NCONSISTENT USE OF TEMPERATURE CASE CONTROL CARD. EITHER A TEMPERATURE(INIT), TEMPERATURE(MATERIAL) OR A TEMPERATURE(BOTH) CASE CONTROL CARD IS ALLOWED PER RUN. User information: Use TEMP(LOAD) and TEMP(MATERIAL) together, or TEMP(BOTH) by itself.

59 *** USER WARNING/FATAL MESSAGE 634 (IFP1D) 634.0 SERST CASE CONTROL ENTRY SUPPORTS KEYWORDS SEMI OR SEDR ONLY *** USER WARNING/FATAL MESSAGE 635 (IFP1D) 635.0 WRONG FORMAT OF DATA FOR THE EVEN FIELD ON CONTOUR CARD *** USER WARNING/FATAL MESSAGE 636 (IFP1D) 636.0 THE TRIM AND DIVERG COMMANDS MAY NOT BE SPECIFIED IN THE SAME SUBCASE. *** USER WARNING/FATAL MESSAGE 637 (IFP1D) 637.0 THE TYPE USED ON AN ANALYSIS CASE CONTROL ENTRY IS INVALID. USER WARNING/FATAL MESSAGE 638 (IFP1D) *** 638.0 A SPACE IS REQUIRED BETWEEN THE SET COMMAND AND THE SET ID. *** USER WARNING/FATAL MESSAGE 639 (IFP1D) 639.0 YOU MAY NOT SPECIFY BOTH MAX AND MIN FOR OBJECTIVE THE DEFAULT VALUE OF MIN WILL BE USED. *** USER WARNING/FATAL MESSAGE 640 (IFP1D) 640.0 YOU MAY NOT SPECIFY THIS CASE CONTROL ENTRY AT THE SUBCASE LEVEL. *** USER WARNING/FATAL MESSAGE 641 (IFP1D) 641.0 CSSCHD=ALL IS NOT ALLOWED. USER INFORMATION: SPECIFY CSSCHD=NONE OR CSSCHD=n WHERE n IS A CONTROL SURFACE SCHEDULE ID. *** USER FATAL MESSAGE 642 (IFPERR) 642.0 THE ABOVE CASE CONTROL COMMAND OR KEYWORD, %1, IS AMBIGUOUS. USER ACTION: SPECIFY EITHER %2 OR %3 ** * USER FATAL MESSAGE 643 (IFPERR) 643.0 AERO SYMMETRY CASE CONTROL COMMAND: %1 SPECIFIES AN ILLEGAL VALUE: %2 USER INFORMATION: LEGAL VALUES ARE: ANTISYMMETRIC, ASYMMETRIC, AND SYMMETRIC. *** USER FATAL MESSAGE 644 (IFP1) 644.0 THE NUMBER OF %1 COEFFICIENTS, %2 , HAS EXCEEDED THE MAXIMUM ALLOWABLE %3 . *** USER INFORMATIONAL MESSAGE 644 (IFP1) 644.1 NONLINEAR CASE CONTROL CARD NOT VALID IN SOLUTION SEQUENCE %1 . IT WILL BE IGNORED. *** USER WARNING MESSAGE 6 44 (IFPMDE) 644.2

60 MODALE NOT VALID IN SOLUTION SEQUENCE %1 . *** USER WARNING MESSAGE 644 (IFP1) 644.3 TSTEP IN SUBCASE IS IGNORED. *** USER FATAL MESSAGE 644 (IFP1) 644.4 THE USE OF TEMP(MATE) OR TEMP(BOTH) IS NOT ALLOWED IN SOL401 AND SOL402. *** USER FATAL MESSAGE 644 (IFP1) 644.5 WHEN SYS440 = 0, TEMP(INIT) MUST BE SPECIFIED ABOVE THE SUBCASE LEVEL FOR ALL LINEAR SOLUTIONS. *** USER FATAL MESSAGE 644 (IFP1) 644.6 S ARE IF TEMPERATURE DEPENDENT MATERIAL PROPERTIE SPECIFIED VIA MATTI CARDS, THE FOLLOWING MAT2 CARDS MAY NOT REFLECT TEMP(LOAD) OR TEMP(INIT) MATERIAL PROPERTIES BECAUSE THE MATERIAL PROPERTIES LISTED BELOW ARE EVALUATED AT TREF WHICH IS SPECIFIED ON THE PCOMP/PCOMPG CARDS. IF (INIT) TEMP(LOAD) OR TEMP IS SPECIFIED, THE MATERIAL PROPERTIES ASSOCIATED WITH THE PCOMP/PCOMPG WILL BE RE - EVALUATED WHEN NEEDED. *** USER FATAL MESSAGE 644 (IFP1) 644.7 NSM MUST BE SPECIFIED ABOVE THE SUBCASE LEVEL. *** USER FATAL MESSAGE 644 (IFP1) 644.8 A SUBCASE CAN NOT HAVE BOTH TEMP(LOAD) AND DTEMP CARD. *** USER FATAL MESSAGE 644 (IFP1) 644.9 ADAPTERR MUST BE SPECIFIED ABOVE THE SUBCASE LEVEL. *** USER WARNING/FATAL MESSAGE 645 (IFP1D) 645.0 THE OUTPUT(POST) AND SETS DEFINITION COMMANDS CANNOT BE SPECIFIED AT THE SAME TIME. *** USER FATAL MESSAGE 646 (IFP1D) 646.0 ILLEGAL OR UNRECOGNIZABLE OPTION SPECIFIED ON THE ABOVE MAXMIN STATEMENT. USER WARNING MESSAGE 647 (IFP1FC) *** 647.0 ERROR DETECTED IN ABOVE CASE CONTROL COMMAND %1. PROGRAMMER INFORMATION: DETECTED A NEGATIVE COUNT, WHEN EXPECTING A POSITIVE GROUP COUNTER, A CONTINUATION INDICATOR, OR AN END OF ENTRY INDICATOR WHILE PROCESSING ABOVE COMMAND. USER INFORMATION: ATTEMPTING TO CONTINUE PROCESSING

61 *** USER FATAL MESSAGE 648 (IFP1FC) 648.0 INVALID CASE CONTROL COMMAND STRUCTURE DETECTED ON ABOVE %1 ENTRY. USER INFORMATION: A DESCRIBER NAME WAS EXPECTED, BUT NOT FOUND. *** USER WARNING MESSAGE 649 (IFP1FC) 649.0 AN EQUAL SIGN WAS MISSING BETWEEN THE CASE CONTROL DESCRIBER %2 AND ITS VALUE DURING ABOVE %1 ENTRY PROCESSING. USER INFORMATION: THE DATA FOLLOWING THE DESCRIBER IS HOLLERITH. *** USER WARNING MESSAGE 649 (IFP1FC) 649.1 AN EQUAL SIGN WAS MISSING BETWEEN THE CASE CONTROL DESCRIBER %2 AND ITS VALUE DURING ABOVE %1 COMMAND PROCESSING. USER INFORMATION: THE DATA FOLLOWING THE DESCRIBER IS NUMERIC. (IFP1FC) *** USER WARNING MESSAGE 649 649.2 AN OPEN PARENTHESIS WAS MISSING BETWEEN THE CASE CONTROL DESCRIBER %2 AND ITS COMPOUND VALUE DURING ABOVE %1 COMMAND PROCESSING. USER INFORMATION: THE DATA FOLLOWING THE DESCRIBER IS HOLLERITH. *** USER WARNING MESSAGE 649 (IFP1FC) 649.3 AN OPEN PARENTHESIS WAS MISSING BETWEEN THE CASE CONTROL DESCRIBER %2 AND ITS COMPOUND VALUE DURING ABOVE %1 COMMAND PROCESSING. USER INFORMATION: THE DATA FOLLOWING THE DESCRIBER IS NUMERIC. *** USER WARNING MESSAGE 650 (IFP1FC) 650.0 A PREMATURE END OF THE CASE CONTROL DETECTED COMMAND %1 PROCESSING DESCRIBER %2. USER INFORMATION: THE DESCRIBER IS IGNORED. *** USER WARNING MESSAGE 650 (IFP1FC) 650.1 DETECTED A PREMATURE END OF THE CASE CONTROL COMMAND %1 PROCESSING DESCRIBER %2. INFORMATION: THE DESCRIBER IS IGNORED. USER *** USER FATAL MESSAGE 651 (IFP1FC) 651.0 INVALID HOLLERITH VALUE %3 SPECIFIED FOR %1 CASE CONTROL DESCRIBER %2. USER INFORMATION: VALID VALUES ARE: ALL ( 1) AND NONE (0) - USER FATAL MESSAGE 651 (IFP1FC) *** 651.1 INVALID HOLLERITH VALUE %3 SPECIFIED FOR %1 CASE CONTROL DESCRIBER %2.

62 USER INFORMATION: VALID VALUES ARE: NONE ( - 1) AND ALL (0) *** USER FATAL MESSAGE 651 (IFP1FC) 651.2 CASE INVALID HOLLERITH VALUE %3 SPECIFIED FOR %1 CONTROL DESCRIBER %2. USER INFORMATION: VALID VALUES ARE: ALL ( - 1) AND NOPRINT ( - 2) *** USER FATAL MESSAGE 651 (IFP1FC) 651.3 INVALID HOLLERITH VALUE %3 SPECIFIED FOR %1 CASE CONTROL DESCRIBER %2. USER INFORMATION: VALID VALUES ARE: DESCENDING (1), ASCENDING (2), ABSOLUTE (10), REAL (20), IMAGINARY (30), PHASE (40) *** USER FATAL MESSAGE 651 (IFP1FC) 651.4 INVALID HOLLERITH VALUE %3 SPECIFIED FOR %1 CASE CONTROL DESCRIBER %2. ION: VALID VALUES ARE: YES AND NO USER INFORMAT *** USER FATAL MESSAGE 651 (IFP1FC) 651.5 INVALID HOLLERITH VALUE %3 SPECIFIED FOR %1 CASE CONTROL DESCRIBER %2. USER INFORMATION: VALID VALUES ARE: PEAK AND RMS *** USER FATAL MESSAGE 651 (IFP1FC) 651.6 INVALID HOLLERITH VALUE %3 SPECIFIED FOR %1 CASE CONTROL DESCRIBER %2. USER INFORMATION: VALID VALUES ARE: YES (0) AND NO ( - 1) INVALID HOLLERITH VALUE %3 SPECIFIED FOR %1 CASE CONTROL DESCRIBER %2. USER INFORMATION: VALID VALUES ARE: PUNCH AND STOP *** USER FATAL MESSAGE 652 (IFP1FC) 652.0 BOTH HOLLERITH VALUES ( %3,%4 ) SPECIFIED FOR THE %1 CASE CONTROL DESCRIBER %2 ARE INVALID. USER INFORMATION: VALID VALUES ARE ONE OF: DESCENDING (1), ASCENDING (2), AND ONE OF: ABSOLUTE (10), REAL (20), IM AGINARY (30), PHASE (40) *** USER FATAL MESSAGE 652 (IFP1FC) 652.1 ONE OF THE HOLLERITH VALUES ( %3,%4 ) SPECIFIED FOR %1 CASE CONTROL DESCRIBER %2 IS INVALID. USER INFORMATION: VALID VALUES ARE ONE OF: DESCENDING (1), ASCENDING (2), AND ONE OF: ABSOLUTE (10), REAL (20), IMAGINARY (30), PHASE (40) *** USER FATAL MESSAGE 653 (IFP1FC) 653.0 INVALID CASE CONTROL DESCRIBER %2 SPECIFIED ON %1 COMMAND.

63 USER INFORMATION: VALID DESCRIBERS ARE: ARF, ARS, FEPS, FLUIDMP, GRIDFMP, GRIDMP, OUTFMP, OUTSMP, O2E, PANELMP, PSORT, SEPS, STRUCTMP *** USER FATAL MESSAGE 653 (IFP1FC) 653.1 INVALID CASE CONTROL DESCRIBER %2 SPECIFIED ON %1 COMMAND. USER INFORMATION: VALID DESCRIBERS ARE: FLUIDSE, HF REQ, HFREQFL, LFREQ, LFREQFL, LMODES, LMODESFL *** USER FATAL MESSAGE 653 (IFP1FC) 653.2 INVALID CASE CONTROL DESCRIBER %2 SPECIFIED ON %1 COMMAND. USER INFORMATION: VALID DESCRIBERS ARE: ACOUT, ACSYM, ASCOUP, PREFDB, SKINOUT, AGGPCH, SFEF70 *** USER FATAL MESSAGE 654 (IFP1FC) 654.0 INVALID INTEGER VALUE %3 SPECIFIED FOR %1 CASE CONTROL DESCRIBER %2. USER INFORMATION: VALID VALUES ARE: 1 = ALL - 0 = NONE >0 *** USER FATAL MESSAGE 654 (IFP1FC) 654.1 INVALID INTEGER VALUE %3 SPECI FIED FOR %1 CASE CONTROL DESCRIBER %2. USER INFORMATION: VALID VALUES ARE: 1 = NONE - 0 = ALL >0 *** USER FATAL MESSAGE 654 (IFP1FC) 654.2 INVALID INTEGER VALUE %3 SPECIFIED FOR %1 CASE CONTROL DESCRIBER %2. USER INFORMATION: VALID VALUES ARE: - 2 = NOPRINT - 1 = NONE 0 = ALL >0 *** USER FATAL MESSAGE 654 (IFP1FC) 654.3 INVALID INTEGER VALUE %3 SPECIFIED FOR %1 CASE CONTROL DESCRIBER %2. USER INFORMATION: VALID VALUES ARE SUM OF: ONE OF THE FOLLOWING, 0 (DEFAULT), 1 (DESCENDING), AN D 2 (ASCENDING) AND ONE OF THE FOLLOWING, 0 (DEFAULT), 10 (ABSOLUTE), 20 (REAL), 30 (IMAGINARY), 40

64 (PHASE) *** USER FATAL MESSAGE 654 (IFP1FC) 654.4 INVALID INTEGER VALUE %3 SPECIFIED FOR %1 CASE CONTROL DESCRIBER %2. USER INFORMATION: VALID VA LUES ARE: - 1 = NO 0 = YES *** USER FATAL MESSAGE 655 (IFP1FC) 655.0 INVALID DATA TYPE ON SPECIFIED %1 CASE CONTROL DESCRIBER %2. USER INFORMATION: THIS MAY MEAN THE DESCRIBER SPECIFIED ABOVE IS EITHER INCORRECT OR MISSPELLED. VALID DESCRIBERS ARE: ARF, ARS, FEPS, FLUIDMP, GRIDFMP, GRIDMP, OUTFMP, OUTSMP, O2E, PANELMP, PSORT, SEPS, STRUCTMP *** USER FATAL MESSAGE 655 (IFP1FC) 655.1 INVALID DATA TYPE ON SPECIFIED %1 CASE CONTROL DESCRIBER %2. MEAN THE DESCRIBER USER INFORMATION: THIS MAY SPECIFIED ABOVE IS EITHER INCORRECT OR MISSPELLED. VALID DESCRIBERS ARE: FLUIDSE, HFREQ, HFREQFL, LFREQ, LFREQFL, LMODES, LMODESFL *** USER FATAL MESSAGE 655 (IFP1FC) 655.2 INVALID DATA TYPE ON SPECIFIED %1 CASE CONTROL DESCRIB ER %2. USER INFORMATION: THIS MAY MEAN THE DESCRIBER SPECIFIED ABOVE IS EITHER INCORRECT OR MISSPELLED. VALID DESCRIBERS ARE: ACSYM, ACOUT, ASCOUP, PREFDB *** USER FATAL MESSAGE 656 (IFP1FC) 656.0 INVALID NUMERIC DATA TYPE SPECIFIED ON %1 CASE CONTROL DESCRIBER %2. USER INFORMATION: REQUIRED DATA TYPE IS REAL. *** USER FATAL MESSAGE 656 (IFP1FC) 656.1 INVALID NUMERIC DATA TYPE SPECIFIED ON %1 CASE CONTROL DESCRIBER %2. USER INFORMATION: RE QUIRED DATA TYPE IS INTEGER. *** USER FATAL MESSAGE 656 (IFP1FC) 656.2 INVALID DATA TYPE SPECIFIED ON %1 CASE CONTROL DESCRIBER %2. USER INFORMATION: REQUIRED DATA TYPE IS REAL. *** USER FATAL MESSAGE 656 (IFP1FC) 656.3 INVALID DATA TYPE SPECIFIED ON %1 CASE CONTROL

65 DESCRIBER %2. USER INFORMATION: REQUIRED DATA TYPE IS HOLLERITH *** USER FATAL MESSAGE 657 (IFP1D) 657.0 THE UNIT NUMBER ON THE ABOVE CARD HAS NOT BEEN DEFINED ON AN ALUE. ASSIGN COMMAND OR IS AN INVALID V User information: - Using PSETID= sktunit on an ADAMSMNF or MBDEXPORT ADAMS case control entry requires that the unit number for the sketch file be defined on ASSIGN SKT='sketch_file.dat',UNIT=sktunit. Using UNIT=unit_number on a MBDEXPORT OP4 cas e control entry requires that the unit number for the OP4 file be defined on ASSIGN OUTPUT4='filename',UNIT=unit_number. Using DMIGOP2=unit_number on an EXTSEOUT case control entry requires that the unit number for the OP2 file be defined on ASSIGN OU TPUT2='filename',UNIT=unit_number. unit_number cannot be 12. Using MATOP4=unit_number or MATRIXOP4=unit_number on an EXTSEOUT case control entry requires that the unit number for the OP4 file be defined on ASSIGN OUTPUT4='filename',UNIT=unit_number. *** USER FATAL MESSAGE 658 (IFP1D) 658.0 TEMP(MATERIAL) AND TEMP(BOTH) ARE NOT ALLOWED FOR ADVANCED NONLINEAR. USE TEMP(INIT) AND TEMP(LOAD) INSTEAD. *** USER FATAL MESSAGE 659 (IFP1D) 659.0 ADAMSMNF AND MBDEXPORT CASE CONTROL COMMANDS BOTH EXIST OR MULTIPLE MBDEXPORT CASE CONTROL COMMANDS EXIST. ONLY ONE IS ALLOWED. *** USER WARNING MESSAGE 660 (IFP1D) 660.0 ABOVE PARAM CARD IS NOT ALLOWED IN THE CASE CONTROL. INVALID RESULTS MAY O CCUR. PLEASE MOVE IT TO THE BULK DATA. *** USER FATAL MESSAGE 661 (IFP1D) 661.0 ONLY 1 OUTPUT MEDIUM MAY BE SPECIFIED ON THE EXTSEOUT CASE CONTROL ENTRY. *** USER FATAL MESSAGE 662 (IFP1D) 662.0 EXTID=SEID IS REQUIRED ON THE EXTSEOUT CASE CONTROL ENTRY WHENEVER ASMBULK, EXTBULK, DMIGPCH, OR MATOP4 ARE SPECIFIED. *** USER FATAL MESSAGE 663 (IFP1D) 663.0

66 A VALID UNIT NUMBER IS REQUIRED ON THE EXTSEOUT CASE CONTROL ENTRY OP4 ARE SPECIFIED (I.E. SPECIFY WHEN DMIGOP2 OR MAT DMIGOP2=UNIT OR MATOP4=UNIT). *** USER FATAL MESSAGE 664 (IFP1D) 664.0 THE EXTSEOUT CASE CONTROL ENTRY IS NOT SUPPORTED IN THIS SOLUTION SEQUENCE. *** USER WARNING MESSAGE 665 (IFP1D) 665.0 IC CASE CONTROL IS NOT VALID FOR THIS SOLUTION SEQUENCE; IT WILL BE IGNORED. *** USER WARNING MESSAGE 666 (IFP1D) 666.0 THE DIFFK KEYWORD IS NOT VALID FOR THIS SOLUTION SEQUENCE; IT WILL BE IGNORED. *** USER WARNING MESSAGE 667 (IFP1 D) 667.0 THE STATSUB KEYWORD IS NOT VALID FOR THIS SOLUTION SEQUENCE; IT WILL BE IGNORED. *** USER FATAL MESSAGE 668 (IFP1D) 668.0 STATSUB AND STATSUB,DIFFK CANNOT BOTH APPEAR IN THE SAME EXECUTION. *** USER FATAL MESSAGE 668 (IFP1D) 669.0 STATSUB AND IC(STATSUB) CANNOT BOTH APPEAR IN THE SAME SUBCASE. *** USER WARNING MESSAGE 670 (IFP1D) 670.0 DIFFK KEYWORD WITHOUT STATSUB KEYWORD IS MEANINGLESS. DIFFK KEYWORD WILL BE IGNORED. *** USER FATAL MESSAGE 671 (IFP1D) 671.0 PHYSICAL, MODAL, STATSUB AND TZERO KEYWORDS CANNOT BE SPECIFIED ON THE SAME IC ENTRY. ONLY ONE IS ALLOWED. *** USER FATAL MESSAGE 672 (IFP1D) 672.0 EQUAL SIGN MISSING. *** USER WARNING MESSAGE 673 (IFP1D) 673.0 IC(MODAL) IS ONLY VALID FOR SOLUTION SEQUENCE 112 (SEMTRAN); IT WILL BE IGNORED FOR THIS SOLUTION. *** USER FATAL MESSAGE 674 (IFP1D) 674.0 THE VALUE OF EXTID MUST BE >0 AND <= 999999 WHEN USING DMIGSFIX=EXTID.

67 675, *** USER FATAL MESSAGE 675.0 - NUMERIC WORD. ABOVE CARD DOES NOT BEGIN WITH A NON User information: XYPLOT commands must begin with character data. *** USER FATAL MESSAGE 676, 676.0 %1 IS NOT RECOGNIZED ON ABOVE CARD. User information: Unrecognized XYPLOT command. *** USER FATAL MESSAGE 677, 677.0 ILLEGAL VALUE SPECIFIED. User information: See Section 13.3 of NX NASTRAN Reference Manual. *** USER FATAL MESSAGE 678, 678.0 %1 CONTRADICTS PREVIOUS DEFINITION. User information: Conflicting requests on a n XYPLOT command. *** USER FATAL MESSAGE 679, 679.0 %1 DELIMITER ILLEGALLY USED. User information: XYPLOT error; see Section 13.3 of NX NASTRAN Reference Manual. *** USER FATAL MESSAGE 680, 680.0 %1 IS ILLEGAL IN STATEMENT. User information: XYPLOT error; see Section 13.3 of NX NASTRAN Reference Manual. *** USER FATAL MESSAGE 681, 681.0 %1 IS ILLEGAL IN STATEMENT. User information: XYPLOT error; see Section 13.3 of NX NASTRAN Reference Manual. USER FATAL MESSAGE 682, *** 682.0 %1 IS ILLEGAL IN STATEMENT. User information: XYPLOT error; see Section 13.3 of NX NASTRAN Reference Manual. *** USER FATAL MESSAGE 683, 683.0 - OUTPUT TOO MANY SUBCASES. MAXIMUM = 200 ON ANY ONE XY COMMAND CARD. rmation: User info No more than 200 subcases are allowed on an XYPLOT request command. *** USER FATAL MESSAGE 684, 684.0 SUBCASE - ID IS LESS THAN 1 OR IS NOT IN ASCENDING ORDER. User information: Subcases must be positioned in ascending order. *** USER FATAL MESSAGE 685, 685.0 %1 = POINT OR ELEMENT ID IS ILLEGAL (LESS THAN 1).

68 User information: XYPLOT error; see Section 13.3 of NX NASTRAN Reference Manual. *** USER FATAL MESSAGE 686, 686.0 NEGATIVE OR ZERO COMPONENTS ARE ILLEGAL. User information: XYPLOT error; see Section 13.3 of NX NASTRAN Reference Manual. *** USER FATAL MESSAGE 687, 687.0 ALPHA - COMPONENTS ARE NOT PERMITTED FOR STRESS OR FORCE XY - OUTPUT REQUESTS. *** USER FATAL MESSAGE 688, 688.0 %1 COMPONENT NAME NOT RECOGNIZED. User information: XYPLOT error; see Section 13.3 of NX NASTRAN Reference Manual. *** USER FATAL MESSAGE 689, 689.0 LAST CARD ENDED WITH A DELIMITER BUT NO CONTINUATION CARD WAS PRESENT. User information: XYPLOT error; see Section 13.3 of NX NASTRAN Reference Manual. If an XYPLOT command ends in a delimiter (i.e., comma or slash) then the next entry is assumed to be a continuation for that entry. This error often occurs when a command is longer than 72 charact ers. Any characters in columns 73 and on are ignored in the XYPLOT section. *** USER FATAL MESSAGE 690, 690.0 TYPE OF CURVE WAS NOT SPECIFIED. (E.G. DISPLACEMENT, STRESS, ETC.). User information: XYPLOT error; see Section 13.3 of NX NASTRAN Refe rence Manual. *** USER FATAL MESSAGE 691, 691.0 - S MORE THAN 2 OR UNEQUAL NUMBER OF COMPONENTS FOR ID WITHIN A SINGLE FRAME. User information: XYPLOT error; see Section 13.3 of NX NASTRAN Reference Manual. *** USER FATAL MESSAGE 692, 692.0 - XY OUTPUT COMMAND IS INCOMPLETE. User information: XYPLOT error; see Section 13.3 of NX NASTRAN Reference Manual. This may simply be a command that is too long (that is, a command that extends into column 73 or beyond). Those columns are not used in the XYPLOT section. *** USER FATAL MESSAGE 693, 693.0 INSUFFICIENT CORE FOR SET TABLE. User information: Reduce the number of requests or increase memory. Six words are used for each frame.

69 *** USER FATAL MESSAGE 694, 694.0 AUTO OR PSDF REQUESTS MAY NOT USE SPLIT FRAME, THUS ONLY ONE COMPONENT PER ID IS PERMITTED. User information: AUTO or PSDF requests may only be specified for full frames. *** USER FATAL MESSAGE 695, 695.0 COMPONENT VALUE = %1 IS ILLEGAL FOR AUTO OR PSDF VECTOR REQUESTS. User information: XYPLOT error; see Section 13.3 of NX NASTRAN Reference Manual. *** USER FATAL MESSAGE 696, 696.0 COMPONENT VALUE = %1 IS ILLEGAL FOR VECTOR TYPE SPECIFIED. User information: XYPLOT error; see Section 13.3 of NX NASTRAN Reference Manual. *** USER FATAL MESSAGE 697 (IFP1XY). 697.0 THE ABOVE COMMAND MUST END WITH ONE INTEGER VALUE. *** USER FATAL MESSAGE 701 701.0 THE NUMBER OF SUBDMAPS BEING COMPILED EXCEEDS THE MAXIMUM ALLOWED NUMBER OF %1 FOR THIS VERSION. *** USER INFORMATION MESSAGE 702 (PRCMPL) 702.0 THE NDDL WILL NOT BE COMPILED BECAUSE THE DATA BASE ALREADY EXISTS User information: If a run is using an existing database, the valid NDDL for the database is stored in the MASTER. If a new version were to be created, the information on the database would no longer be considered valid, since it would not match the current NDDL. *** USER FATAL MESSAGE 703 (XCSA) 703.0 DMAP COMPILATION IS NOT ALLOWED WHEN "SOL" STATEMENT REQUESTS "SOLIN=" USER ACTION: REMOVE DMAP COMPILES FROM INPUT AND RESUBMIT User information: You can also remove the SOLIN = from the SOL statement and provide the correct information for compiling and linking the solutio n. *** USER FATAL MESSAGE 706 (PRCMPL) 706.0 THE SUBDMAP STATEMENT IS MISSING OR THE SUBDMAP NAME IS INCORRECT. USER ACTION: ASSURE THAT THE SUBDMAP NAME SPECIFIED ON THE SUBDMAP STATEMENT IS THE SAME ON THE COMPILE STATEMENT User information: W hen compiling a user - supplied SUBDMAP, the SUBDMAP must always

70 begin with a SUBDMAP statement. *** USER FATAL MESSAGE 707 (PRCMPL) 707.0 THE "SOUIN=" COMPILE OPTION AND INLINE DMAP CANNOT BOTH BE SPECIFIED *** USER FATAL MESSAGE 708 (PRCMPL) 708.0 THE "SOUIN=" DBSET CANNOT BE A "SCRATCH" DBSET *** USER FATAL MESSAGE 709 (PRCMPL) 709.0 THE COMPILE COMMAND CANNOT RESTORE SOURCE FROM %1 DBSET, SINCE THIS IS A DATA BASE INITIALIZATION RUN USER ACTION: CHECK SPEL LING OF THE ABOVE SPECIFIED DBSET FOR THE "SOUIN" KEYWORD, OR SUPPLY THE DMAP FOR %2 SUBDMAP User information: When creating a database, use the ACQUIRE NDDL FMS statement or SOL xxx, NOEXE to attach the data paths. *** USER FATAL MESSAGE 710 (XTRAC4) 710.0 NO INFORMATION TO PROCESS ON THE PROJECT KEYWORD *** USER FATAL MESSAGE 710 (XCSOL2) 710.1 NO INFORMATION TO PROCESS ON SOL STATEMENT *** USER FATAL MESSAGE 710 (XCSACM) 710.2 NO INFORMATION TO PROCESS ON TH E COMPILE EXECUTIVE COMMAND *** USER FATAL MESSAGE 710 (XALTER) 710.3 EXTRANEOUS DATA FOUND ON %1 STATEMENT. *** USER FATAL MESSAGE 710 (RDSECU) 710.4 NO INFORMATION TO PROCESS ON SECURITY COMMAND USER FATAL MESSAGE 710 (RDPROJ) *** 710.5 PROJECT ID MUST BE ENCLOSED IN SINGLE QUOTES *** USER FATAL MESSAGE 710 (RDPROJ) 710.6 MISSING PROJECT ID ON PROJECT COMMAND *** USER FATAL MESSAGE 710 (RDLINK) 710.7 NO INFORMATION TO PROCESS ON LINK CARD *** USER FATAL MESSAGE 710 (RDINIT) 710.8 NO INFORMATION TO PROCESS ON INIT STATEMENT *** USER FATAL MESSAGE 710 (RDEXPN) 710.9 NO INFORMATION TO PROCESS ON EXPAND STATEMENT *** USER FATAL MESSAGE 710 (RDASGN) 710.10 NO INFORMATION TO PROCESS ON ASSIGN COMMAND. *** USER FATAL MESSAGE 710 (RDACQU) 710.11 NO INFORMATION TO PROCESS ON ACQUIRE STATEMENT.

71 *** SYSTEM FATAL MESSAGE 713 (PRTNDL) 713.0 - OF FILE ENCOUNTERED WHILE READING NDDL. END - *** SYSTEM WARNING MESSAGE 714 (PVAPRT) 714.0 A DATA BASE PATH WITH KEY NUMBER %1 WAS NOT FOUND IN THE PVA (PATH VALUE TABLE) WHILE PROCESSING DIRECTORY PRINT INFORMATION FOR THE DATA BLOCK %2 USER INFORMATION: THIS INDICATES A PROBLEM WITH THE POINTERS IN YOUR DATABASE'S MASTER DIRECTORIES USER ACTION: DELETE THE OFFENDING DATA BLOCK WITH THE FMS SECTION COMMAND -- > DBFIX *** SYSTEM INFORMATION MESSAGE 715 (RCARD) 715.0 THE ALTERNATE SECOND FIELD FORMAT FOR VPS TYPE %1 IS NOT CURRENTLY SUPPORTED. USER INFORMATION: THIS FIELD WILL BE ASSUMED CHARACTER ( VPS TYPE 3 ) DATA USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 716 (RDACQU) 716.0 AN UNRECOGNIZABLE NDDL NAME APPEARS ON THE ACQUIRE STATEMENT USER INF ORMATION: THE VALID NAMES ARE NDDLOLD AND NDDL FOR THE OLD AND THE NEW SOLUTION SEQUENCES, RESPECTIVELY. *** USER WARNING MESSAGE 717 (RDASGN) 717.0 RECL SPECIFICATION IS NOT REQUIRED FOR %1 LOGICAL NAME. USER INFORMATION: ASSIGNED RECL OF %2 WORD S IS REPLACED BY SYSTEM DEFAULT RECL OF 1024 WORDS. *** USER WARNING MESSAGE 717 (RDASGN) 717.1 RECL SPECIFICATION IS NOT REQUIRED FOR %1 LOGICAL NAME. USER INFORMATION: RECL IS IGNORED. *** USER WARNING MESSAGE 717 (RDASGN) 717.2 RECL SPECIFICATION IS NOT REQUIRED FOR WRITING DATA BASE FILES. USER INFORMATION: RECL IS IGNORED. *** USER WARNING MESSAGE 717 (RDASGN) 717.3 FORM SPECIFICATION IS NOT REQUIRED FOR WRITING DATA BASE FILES. USER INFORMATION: FORM IS IGNORED. *** USER WARNING MESSAGE 717 (RDASGN) 717.4 UNIT SPECIFICATION IS NOT REQUIRED FOR %1 LOGICAL NAME. USER INFORMATION: UNIT IS IGNORED. *** USER WARNING MESSAGE 717 (RDASGN) 717.5

72 UNIT SPECIFICATION IS NOT REQUIRED FOR WRITING DATA BASE FILES. USER INFORMATION: UNIT IS IGNORED. *** USER WARNING MESSAGE 717 (RDASGN) 717.6 SIZE SPECIFICATION IS NOT REQUIRED FOR WRITING DATA BASE FILES. USER INFORMATION: SIZE IS IGNORED. USER ACTION: USE AN INIT CARD TO SPECIFY THE SIZE. *** USER FATAL MESSAGE 718 (RDASGN) 718.0 FORM SPECIFICATION IS MISSING ON THIS ASSIGN CARD. *** USER FATAL MESSAGE 718 (RDASGN) 718.1 STATUS SPECIFICATION IS MISSING ON THIS ASSIGN CARD. *** USER FATAL MESSAGE 718 (RDASGN) 718.2 RECL SPECIFICATION IS MISSING ON THIS ASSIGN CARD. *** USER FATAL MESSAGE 718 (RDASGN) 718.3 UNIT SPECIFICATION IS MISSING ON THIS ASSIGN CARD. *** USER FATAL MESSAGE 718 (RDASGN) 718.4 SIZE SPECIFICATION IS MISSING ON THIS ASSIGN CARD. USER FATAL MESSAGE 719 (RDREST) *** 719.0 THE SECURITY KEYWORD IS MISSING ON THE RESTART COMMAND. USER ACTION: REMOVE THE PARENTHESES, IF NO SECURITY IS DEFINED IN THIS DATA BASE. *** USER FATAL MESSAGE 719 (RDDIRP) 719.1 THE SECURITY KEYWORD IS MISSING ON THE DBDIR COMMAND. REMOVE PARENTHESES IF NO SECURITY CODE DEFINED IN THIS DATA BASE *** USER FATAL MESSAGE 719 (RDDBCL) 719.2 THE SECURITY KEYWORD IS MISSING ON THE DBCLEAN COMMAND. THESES, IF NO SECURITY USER ACTION: REMOVE THE PAREN CODE DEFINED IN THIS DATA BASE *** USER FATAL MESSAGE 720 (RDEXPN) 720.0 THE EXPAND STATEMENT IS MISSING THE KEYWORD "LOGICAL=" *** USER FATAL MESSAGE 720 (RDDIRP) 720.1 ID THE DBDIR COMMAND IS MISSING KEYWORD "VERSION=" *** USER FATAL MESSAGE 720 (RDDBCL) 720.2 THE DBCLEAN COMMAND IS MISSING THE KEYWORD "VERSION=" ID *** USER FATAL MESSAGE 721 (RDASGN) 721.0 ILLEGAL FORM KEYWORD.

73 USER INFORMATION: THE VALID FORM KEYWORDS ARE: FORMATTED OR UNFORMATTED. *** USER FATAL MESSAGE 721 (RDASGN) 721.1 INVALID STATUS KEYWORD. USER INFORMATION: THE VALID STATUS KEYWORDS ARE: OLD OR NEW. *** USER FATAL MESSAGE 722 (RDASGN) 722.0 LOGICAL NAME EXCEEDS MAXIMUM NUMBER OF CHARACTERS ALLOWED. USER INFO RMATION: MAXIMUM CHARACTER LENGTH IS 8. *** USER FATAL MESSAGE 723 (XTRDPO) 723.0 DMAP EXPRESSION HAS AN UNBALANCED NUMBER OF PARENTHESES User information: This can occur when the DBLOCATE feature is used with the WHERE(PROJECT=*) clause. Modify the WHERE clause to include VERSION specification such as WHERE(PROJECT=*,VERSION=*); otherwise, the default for VERSION is "last" and the specification of "PROJECT=*" VERSION=LAST" will be conflicting. 723 (XTRDAP) *** USER FATAL MESSAGE 723.1 %1 EXPRESSION HAS AN UNBALANCED NUMBER OF PARENTHESES User information: This can occur when the DBLOCATE feature is used with the WHERE(PROJECT=*) clause. Modify the WHERE clause to include VERSION specification such ERSION=*); otherwise, the default for VERSION as WHERE(PROJECT=*,V is "last" and the specification of "PROJECT=*" VERSION=LAST" will be conflicting. *** USER FATAL MESSAGE 723 (XTRCLO) 723.2 THE ABOVE DMAP MODULE EXPRESSION HAS AN UNBALANCED NUMBER OF PARENTHESES. U ser information: This can occur when the DBLOCATE feature is used with the WHERE(PROJECT=*) clause. Modify the WHERE clause to include VERSION specification such as WHERE(PROJECT=*,VERSION=*); otherwise, the default for VERSION is "last" and the specif ication of "PROJECT=*" VERSION=LAST" will be conflicting. *** USER FATAL MESSAGE 723 (XTRCLA) 723.3

74 THE ABOVE %1 EXPRESSION HAS AN UNBALANCED NUMBER OF PARENTHESES. User information: This can occur when the DBLOCATE feature is used with the WHERE(PROJECT=*) clause. Modify the WHERE clause to include VERSION specification such as WHERE(PROJECT=*,VERSION=*); otherwise, the default for VERSION is T=*" VERSION=LAST" will be "last" and the specification of "PROJEC conflicting. *** USER FATAL MESSAGE 723 (XTRACI) 723.4 THE ABOVE FILE NAME CONTAINS AN UNBALANCED NUMBER OF DELIMITERS. User information: This can occur when the DBLOCATE feature is used with the WHERE(PROJECT=*) se. Modify the WHERE clause to include VERSION specification such clau as WHERE(PROJECT=*,VERSION=*); otherwise, the default for VERSION is "last" and the specification of "PROJECT=*" VERSION=LAST" will be conflicting. (XTRAC4) *** USER FATAL MESSAGE 723 723.5 PROJECT ID EXPRESSION HAS AN UNBALANCED NUMBER OF SINGLE QUOTES User information: This can occur when the DBLOCATE feature is used with the WHERE(PROJECT=*) clause. Modify the WHERE clause to include VERSION specification such CT=*,VERSION=*); otherwise, the default for VERSION as WHERE(PROJE is "last" and the specification of "PROJECT=*" VERSION=LAST" will be conflicting. *** USER FATAL MESSAGE 723 (XTRAC2) 723.6 THE ABOVE COMMAND CONTAINS AN UNBALANCED NUMBER OF SINGLE QUOTES. User information: This can occur when the DBLOCATE feature is used with the WHERE(PROJECT=*) clause. Modify the WHERE clause to include VERSION specification such as WHERE(PROJECT=*,VERSION=*); otherwise, the default for VERSION is "last" and the speci fication of "PROJECT=*" VERSION=LAST" will be conflicting. *** USER FATAL MESSAGE 723 (XALTER) 723.7 %1 STATEMENT HAS AN UNBALANCED NUMBER OF

75 PARENTHESES. User information: This can occur when the DBLOCATE feature is used with the WHERE(PROJECT=*) clause. Modify the WHERE clause to include VERSION specification such as WHERE(PROJECT=*,VERSION=*); otherwise, the default for VERSION is "last" and the specification of "PROJEC T=*" VERSION=LAST" will be conflicting. *** USER FATAL MESSAGE 723 (XALTER) 723.8 %1 STATEMENT HAS AN UNBALANCED NUMBER OF SINGLE QUOTES. User information: This can occur when the DBLOCATE feature is used with the WHERE(PROJECT=*) clause. Modif y the WHERE clause to include VERSION specification such as WHERE(PROJECT=*,VERSION=*); otherwise, the default for VERSION is "last" and the specification of "PROJECT=*" VERSION=LAST" will be conflicting. *** USER FATAL MESSAGE 723 (RDREST) 723.9 VERSION EXPRESSION HAS AN UNBALANCED NUMBER OF PARENTHESES. User information: This can occur when the DBLOCATE feature is used with the WHERE(PROJECT=*) clause. Modify the WHERE clause to include VERSION specification such as WHERE(PROJECT=*,VERSION= *); otherwise, the default for VERSION is "last" and the specification of "PROJECT=*" VERSION=LAST" will be conflicting. *** USER FATAL MESSAGE 723 (RDPROJ) 723.10 PROJECT ID HAS UNBALANCED NUMBER OF SINGLE QUOTES User information: This can occ ur when the DBLOCATE feature is used with the WHERE(PROJECT=*) clause. Modify the WHERE clause to include VERSION specification such as WHERE(PROJECT=*,VERSION=*); otherwise, the default for VERSION is "last" and the specification of "PROJECT=*" VERSION =LAST" will be conflicting. *** USER FATAL MESSAGE 723 723.11 LOGICAL= EXPRESSION HAS AN UNBALANCED NUMBER OF PARENTHESES User information:

76 This can occur when the DBLOCATE feature is used with the WHERE(PROJECT=*) se to include VERSION specification such clause. Modify the WHERE clau as WHERE(PROJECT=*,VERSION=*); otherwise, the default for VERSION is "last" and the specification of "PROJECT=*" VERSION=LAST" will be conflicting. *** USER FATAL MESSAGE 723 723.13 VERSION EXPRESSION HAS AN UNBALANCED NUMBER OF PARENTHESES User information: This can occur when the DBLOCATE feature is used with the WHERE(PROJECT=*) clause. Modify the WHERE clause to include VERSION specification such as WHERE(PROJECT=*,VERSION=*); otherwise, the default for VERSION is "last" and the specification of "PROJECT=*" VERSION=LAST" will be conflicting. *** USER FATAL MESSAGE 723 (PARSYS) 723.15 THE ABOVE COMMAND CONTAINS AN UNBALANCED NUMBER OF SINGLE QUOTES. User information: This can occur when the DBLOCATE feature is used with the WHERE(PROJECT=*) clause. Modify the WHERE clause to include VERSION specification such as WHERE(PROJECT=*,VERSION=*); otherwise, the default for VERSION is CT=*" VERSION=LAST" will be "last" and the specification of "PROJE conflicting. *** USER WARNING MESSAGE 724 (RDASGN) 724.0 SIZE SPECIFICATION IS NOT NECESSARY FOR THIS MACHINE. USER INFORMATION: SIZE IS IGNORED. *** USER FATAL MESSAGE 725 725.0 THE EQUAL SIGN IS MISSING AFTER THE LOGICAL KEYWORD *** USER FATAL MESSAGE 725 (RDASGN) 725.2 THE EQUAL SIGN IS MISSING AFTER THE LOGICAL KEYWORD *** USER FATAL MESSAGE 725 (PARSYS) 725.3 THE EQUAL SIGN IS MISSING AFTER THE SYS KEYWORD. *** USER FATAL MESSAGE 726 (RDINIT) 726.0 THE LIST OF LOGICAL NAMES MUST BE IN ENCLOSED PARENTHESES *** USER WARNING MESSAGE 727 (RDINIT) 727.0 NO SPACE WAS REQUESTED FOR LOGICAL NAME %1 USER INFORMATION: A DEFAULT OF %2 IS USED

77 User informa tion: Assign the desired disk space by using the ASSIGN statement or by JCL. *** USER INFORMATION MESSAGE 727 (RDEXPN) 727.1 NO SPACE WAS REQUESTED FOR LOGICAL NAME %1 USER INFORMATION: A DEFAULT OF %2 IS USED User information: Assign the desired disk space by using the ASSIGN statement or by JCL. *** USER FATAL MESSAGE 728 (RDINIT) 728.0 THE LOGICAL NAME SPACE OR MEM REQUEST IS MISSING A CLOSING PARENTHESIS. USER ACTION : VERIFY THAT THE STATEMENT DOES NOT COLUMN 72. EXTEND BEYOND *** USER FATAL MESSAGE 728 (RDEXPN) 728.1 THE LOGICAL NAME SPACE REQUEST IS MISSING A CLOSING PARENTHESIS *** USER WARNING MESSAGE 729 (RDINIT) 729.0 THE BUFFSIZE FOR USROBJ CANNOT BE CHANGED FROM THE MACHINE DEFAULT. USER INFORMATION: BUFFSIZE PARAMETER IGNORED. *** USER FATAL MESSAGE 730 (XCSACM) 730.0 SYNTAX ERROR IN COMPILE EXECUTIVE COMMAND USER INFORMATION: CHECK SYNTAX AND FORMAT OF COMPILE CARD *** USER FATAL MESSAGE 730 (RDLINK) 730.1 SYNTAX ER ROR IN LINK EXECUTIVE COMMAND USER INFORMATION: CHECK SYNTAX AND FORMAT OF LINK CARD *** USER WARNING/FATAL MESSAGE 731 (IFP1D) 731.0 INVALID USE OF NSM OCCURS AT THE SUBCASE LEVEL. ONLY ONE SUCH CARD IS ALLOWED PER PROBLEM OR PER SUPERELEMENT. *** USER WARNING MESSAGE 735 (RDREST) 735.0 THE MODIFIED AND UNMODIFIED KEYWORDS ARE NO LONGER VALID ON THE RESTART COMMAND. *** USER INFORMATION MESSAGE 736 (RDREST) 736.0 THE RESTART VERSION ID IS NOT DEFINED ON THE RESTART COMMAND. A RES TART OF LAST VERSION ID IS ASSUMED. User information: Whenever performing a restart, the program assumes that the restart will use the most recent version in the database unless a version number is specified. *** USER FATAL MESSAGE 737 (XTRUNI) 737.0

78 THE FORTRAN UNIT NUMBER SPECIFIED ON FMS COMMAND MUST BE AN INTEGER UNIT=%1 *** USER FATAL MESSAGE 737 (XTRKIV) 737.1 THE VALUE SPECIFIED FOR %1 MUST BE AN INTEGER %2=%3 *** USER FATAL MESSAGE 737 (RD UPDT) 737.2 THE VALUE SPECIFIED FOR DBUPDATE CARD HAS A BAD INTEGER FORMAT %1 *** USER FATAL MESSAGE 737 (RDREST) 737.3 THE VALUE SPECIFIED FOR VERSION IS NOT AN INTEGER. THE VALUE IS %1 *** USER FATAL MESSAGE 737 (RDINIT) 737.4 THE SPACE SPECIFIED FOR LOGICAL NAME %1 MUST BE AN INTEGER SPACE DEFINED IS %2 *** USER FATAL MESSAGE 737 (RDINIT) 737.5 THE VALUE OF THE SPECIFIED CLUSTER SIZE IS NOT AN INTEGER THE VALUE IS %1 *** USER FATAL MESSAGE 737 (RDINIT) 737.6 THE VALUE SPECIFIED FOR BUFFSIZE IS NOT AN INTEGER THE VALUE IS %1 *** USER FATAL MESSAGE 737 (RDINIT) 737.7 THE BUFFSIZE SPECIFIED FOR "MEM" MUST BE AN INTEGER MEM=%1 *** USER FATAL MESSAGE 737 (RDINIT) 737.8 THE VALUE SPECIFIED FOR RAM SIZE MUST BE AN INTEGER %1=%2 *** USER FATAL MESSAGE 737 (RDEXPN) 737.9 SPACE SPECIFIED FOR LOGICAL NAME %1 MUST BE INTEGER SPACE DEFINED IS %2 *** USER FATAL MESSAGE 737 (RDDIRP) 737.10 THE VALUE SPECIFIED FOR FORMAT IS NOT AN INTEGER THE VALUE IS %1 *** USER FATAL MESSAGE 737 (RDDIRP) 737.11 THE VALUE SPECIFIED FOR VERSION IS NOT AN INTEGER THE VALUE IS %1 *** USER FATAL MESSAGE 737 (RDDBCL) 737.12 THE VALUE SPECIFIED FOR VERSION IS NOT AN INTEGER THE VALUE IS %1 *** USER FATAL MESSAGE 737 (RDASGN) 737.13 THE VALUE SPECIFIED FOR RECL IS NOT AN INTEGER.

79 THE VALUE IS %1 *** USER FATAL MESSAGE 737 (RDASGN) 737.14 THE VALUE SPECIFIED FOR UNIT IS NOT AN INTEGER. THE VALUE IS %1 *** USER FATAL MESSAGE 737 (RDASGN) 737.15 THE VALUE SPECIFIED FOR SIZE IS NOT AN INTEGER. THE VALUE IS %1 *** USER FATAL MESSAGE 737 (INPTT4) 737.16 THE FORTRAN UNIT NUMBER SPECIFIED ON AN INPUTT4 STATEMENT MUST BE AN INTEGER GREATER THAN 0. UNIT SPECIFIE D=%1 *** USER FATAL MESSAGE 737 (IN4WAMLS) 737.17 CANNOT OPEN FILE SPECIFIED IN THE IN4AMLS DMAP. ERROR CODE RETURNED =%1 *** USER FATAL MESSAGE 737 (IN4WAMLS) 737.18 CANNOT CLOSE FILE SPECIFIED IN THE IN4AMLS DMAP. ERROR CODE RETURNED =%1 *** USER FATAL MESSAGE 738 (RDASGN) 738.0 THE FILE NAME MUST BE DEFINED FOR LOGICAL %1 *** USER FATAL MESSAGE 739 (RDASGN) 739.0 THE LOGICAL NAME %1 IS NOT USER ASSIGNABLE. *** USER FATAL MESSAGE 740 (RDASGN) 740.0 UNIT NUMBER %1 HAS ALREADY BEEN ASSIGNED TO THE LOGICAL NAME %2 *** USER FATAL MESSAGE 741 (RDASGN) 741.0 THE LOGICAL NAME %1 HAS ALREADY BEEN ASSIGNED TO THE FOLLOWING PHYSICAL FILE: %2 *** USER FATAL MESSAGE 742 742.0 ILLEGAL USAGE OF DBSET KEYWORD %1 *** USER FATAL MESSAGE 742 (RDINIT) 742.1 ILLEGAL USAGE OF SCRATCH KEYWORD %1 *** USER FATAL MESSAGE 743 (RDEXPN) 743.0 A LOGICAL KEYWORD HAS NOT BEEN DEFINED. USER ACTION: SPECIFY LOGICAL NAME(S) TO EXPAND THIS DBSET. USER INFORMATION: LOGICAL NAMES ENABLE US TO OBTAIN THE PHYSICAL FILES WHICH YOU INTEND TO ADD TO A PARTICULAR DBSET. *** USER FATAL MESSAGE 744 (RDEXPN) 744.0 %1 IS AN INVALID EXPAND CARD KEYWORD USER INFORMATION: THE VALID KEYWORDS FOR THE EXPAND

80 STATEMENT ARE: "MASTER", "DBALL", "USROBJ", "USRSOU", "OBJSCR", "DBSET_NAME", AND "SCRATCH" *** USER FATAL MESSAGE 745 745.0 IGNABLE TO THIS RUN THE MAXIMUM NUMBER OF DBSETS ASS HAS BEEN EXCEEDED USER INFORMATION: THE MAXIMUM NUMBER ALLOWED IS %1 *** USER FATAL MESSAGE 746 (RDEXPN) 746.0 THE MAXIMUM NUMBER OF LOGICALS THAT CAN BE ASSIGNED WITH THE EXPAND COMMAND HAS BEEN EXCEEDED. USER INFORMATION: TH E MAXIMUM NUMBER ALLOWED IS %1 *** USER FATAL MESSAGE 746 (FNDUNT) 746.1 THE MAXIMUM NUMBER OF LOGICALS THAT CAN BE ASSIGNED WITH THE ASSIGN COMMAND HAS BEEN EXCEEDED. USER INFORMATION: THE MAXIMUM NUMBER ALLOWED IS %1 *** USER FATAL MESSAGE 747 (XDFNAM) 747.0 THE MAXIMUM NUMBER OF MEMBERS FOR THE ABOVE DBSET HAS BEEN EXCEEDED. USER INFORMATION: THE MAXIMUM NUMBER ALLOWED IS %1. NOTES FOR DBSET SCRATCH: 1) IF NO MEMBERS ARE EXPLICITLY DEFINED FOR THE NON - SCR300 PARTITION, A DE FAULT MEMBER SCRATCH IS PROVIDED. 2) IF NO MEMBERS ARE EXPLICITLY DEFINED FOR THE SCR300 PARTITION, A DEFAULT MEMBER SCR300 IS PROVIDED IF SYSTEM(142)=2. *** USER FATAL MESSAGE 748 (DBINIT) 748.0 NO MORE THAN TEN DBCLEAN COMMANDS ARE ALLOWED. *** USER FATAL MESSAGE 748 (DBINIT) 748.1 NO MORE THAN ONE %1 COMMAND IS ALLOWED. *** USER WARNING MESSAGE 749 (DBINIT) 749.0 WHEN THE PROJECT ID ON THE DBCLEAN CARD HAS NOT BEEN DEFINED, A DELETION WITH "BLANK" PROJECT ID WILL BE ASSUMED. HE PROJECT CARD HAS TO BE DEFINED PRIOR TO THE DBCLEAN T CARD, WHEN DELETIONS OF THE CURRENT PROJECT ID ARE DESIRED. *** USER WARNING MESSAGE 749 (DBINIT) 749.1 WHEN THE PROJECT ID ON THE RESTART CARD HAS NOT BEEN DEFINED, A RESTART WITH "BLANK" PROJ ECT ID WILL BE ASSUMED. THE PROJECT CARD HAS TO BE DEFINED PRIOR TO THE RESTART CARD, WHEN RESTARTS OF THE CURRENT PROJECT ID ARE DESIRED.

81 *** USER WARNING MESSAGE 750 (DBINIT) 750.0 ONLY ONE %1 COMMAND IS FUNCTIONAL. THE OTHERS ARE IGNORED ***USER WARNING MESSAGE 750 (DBINIT) 750.1 DIRECTORY OUTPUT FORMAT OF FIRST DBDIR COMMAND WILL OVERWRITE THE CURRENT DBDIR COMMAND *** USER FATAL MESSAGE 751 (DBINIT) 751.0 THE PRIMARY DATA BASE CONTAINS BAD OR NULL MASTER DIRECTORIES. USER ACTIONS: 1. CORRECT THE CAUSE OF THIS PROBLEM 2. RESUBMIT THE DATA BASE INITIALIZATION RUN. *** USER WARNING MESSAGE 752 (DBINIT) 752.0 %1 CARDS IN DATA BASE INITIALIZATION RUNS ARE IGNORED. *** USER FATAL MESSAGE 753 (XSEMIN) 753.0 THE SOLUTION SEQUENCE %1 DOES NOT EXIST IN THE FIST. USER INFORMATION: IT HAS EITHER NOT BEEN ALLOCATED OR NOT BEEN LINKED. USER ACTION: SUPPLY THE NECESSARY LINK CARD, IF THIS SOLUTION SEQUENCE IS BEING COMPILED IN THIS RUN. USER FATAL MESSAGE 755 (XCSA) *** 755.0 THE ABOVE STATEMENT IS NOT SUPPORTED IN THE EXECUTIVE CONTROL SECTION, BUT IN THE FILE MANAGEMENT SECTION (FMS). USER INFORMATION: THE FMS IS DELIMITED BY ANY EXECUTIVE CONTROL STATEMENT. USER ACTION: MOVE THE STATEMENT ABO VE THE EXECUTIVE CONTROL SECTION. *** USER FATAL MESSAGE 756 (XCSA) 756.0 THE %1 CARD IS NO LONGER SUPPORTED IN THE EXECUTIVE CONTROL SECTION. *** USER FATAL MESSAGE 756 (XCSA) 756.1 THE %1 CARD IS NO LONGER SUPPORTED IN THE EXECUTIVE CONTR OL SECTION. USER INFORMATION: THE RESTART STATEMENT IN THE EXECUTIVE CONTROL SECTION HAS BEEN REPLACED BY THE RESTART FILE MANAGEMENT STATEMENT. SEE USER MANUAL SECTION 2.2. User information: This can occur if the RESTART statement of the File Manageme nt Section does not begin in column one. *** USER FATAL MESSAGE 756 (XCSA) 756.2 THE %1 CARD IS NO LONGER SUPPORTED IN THE EXECUTIVE CONTROL SECTION.

82 USER INFORMATION: THE BEGIN STATEMENT IN THE EXECUTIVE CONTROL SECTION HAS BEEN REPLACED BY THE SUBDMAP DMAP STATEMENT. SEE USER MANUAL SECTION 5. *** USER FATAL MESSAGE 757 (XCSA) 757.0 THE FIRST ALTER CARD OF A SUBDMAP MUST BE PRECEDED BY A COMPILE CARD THAT SPECIFIES THE SUBDMAP NAME AND LOCATION. User information: The ALTER Executive Control statement must immediately follow a COMPILE statement. *** USER FATAL MESSAGE 758 (XCSA) 758.0 THE READ EXECUTIVE COMMAND IS NO LONGER A VALID COMMAND, OR IT IS NOT SUPPORTED IN THIS VERSION USER FATAL MESSAGE 760 (XCSOL2) *** 760.0 THE ABOVE SOL CARD CONTAINS A DBSET VALUE EXCEEDING 8 CHARACTERS VALUE = %1 *** USER FATAL MESSAGE 761 (XCSSUB) 761.0 INVALID SOLUTION SEQUENCE REQUESTED. USER INFORMATION: VALID SOL NUMBERS ARE: *** SYSTEM FATAL MESSAGE 762 (XGPI) 762.0 UNEXPECTED END - OF - RECORD DETECTED ON SCRATCH FILE %1 USER INFORMATION: THE SCRATCH FILE CONTAINING THE COMPILE STATEMENTS HAS PROBABLY BEEN DESTROYED. *** SYSTEM FATAL MESSAGE 763 (XXLOAD) 763.0 INSUFFICIENT OPEN CORE AVAILABLE TO STORE DATA BASE DIRECTORY TABLES USER ACTION: INCREASE MEMORY REQUEST AND RERUN. PROGRAMMER INFORMATION: THE AMOUNT OF MAIN MEMORY AVAILABLE BEFORE STORAGE OF DIRECTORY TABLES = %1 FOLLOWING IS A DUMP OF VALUES IN THE COMMON BLOCK /XDIR/, WHICH TRACKS THE POSITION OF DIRECTORY TABLES IN OPEN CORE AS THEY ARE READ FROM DISK. NOTE: THE FIRST WORD OF EACH 3 WORD ENTRY IS UNUSED, THE SECOND WORD IS THE TOP POINTER, AND ABLE THE 3RD WORD IS THE END POINTER+1 TO A DIRECTORY T THE DIFFERENCE BETWEEN THE SECOND WORD OF THE LAST - ZERO ENTRY AND THE AVAILABLE OPEN CORE WILL NON INDICATE HOW MUCH SPACE THE LAST TABLE TOOK UP BEFORE RUNNING OUT OF OPEN CORE THE DUMP OF THE COMMON BLOCK /XDIR/ IS: %2 *** SYSTEM FA TAL MESSAGE 763 763.1

83 INSUFFICIENT OPEN CORE AVAILABLE TO STORE DATA BASE DIRECTORY TABLES USER ACTION: INCREASE MEMORY REQUEST AND RERUN. PROGRAMMER INFORMATION: THE AMOUNT OF MAIN MEMORY AVAILABLE BEFORE STORAGE OF DIRECTORY TABLES = %1 FOLLOWING IS A DUMP OF VALUES IN THE COMMON BLOCK /XDIR/, WHICH TRACKS THE POSITION OF DIRECTORY TABLES IN OPEN CORE AS THEY ARE READ FROM DISK. NOTE: THE FIRST WORD OF EACH 3 WORD ENTRY IS UNUSED, THE SECOND WORD IS THE TOP POINTER, AND THE 3RD WORD IS THE END POINTER+1 TO A DIRECTORY TABLE THE DIFFERENCE BETWEEN THE SECOND WORD OF THE LAST - NON ZERO ENTRY AND THE AVAILABLE OPEN CORE WILL INDICATE HOW MUCH SPACE THE LAST TABLE TOOK UP BEFORE RUNNING OUT OF OPEN CORE THE DUMP OF THE COMMON BLOCK /XDIR/ IS: %2 %3 %4 %5 %6 %7 %8 %9 *** SYSTEM FATAL MESSAGE 763 (XDIRLD) 763.2 INSUFFICIENT OPEN CORE AVAILABLE TO STORE DATA BASE DIRECTORY TABLES USER ACTION: INCREASE MEMORY REQUEST AND RERUN. PROGRAMMER INFORMATION: THE AMOUNT OF MAIN MEMORY STORAGE OF DIRECTORY TABLES = %1 AVAILABLE BEFORE FOLLOWING IS A DUMP OF VALUES IN THE COMMON BLOCK /XDIR/, WHICH TRACKS THE POSITION OF DIRECTORY TABLES IN OPEN CORE AS THEY ARE READ FROM DISK. NOTE: THE FIRST WORD OF EACH 3 WORD ENTRY IS UNUSED, THE SECOND WORD IS T HE TOP POINTER, AND THE 3RD WORD IS THE END POINTER+1 TO A DIRECTORY TABLE THE DIFFERENCE BETWEEN THE SECOND WORD OF THE LAST NON - ZERO ENTRY AND THE AVAILABLE OPEN CORE WILL INDICATE HOW MUCH SPACE THE LAST TABLE TOOK UP BEFORE RUNNING OUT OF OPEN CORE THE DUMP OF THE COMMON BLOCK /XDIR/ IS: %2 %3 %4 %5 %6

84 %7 %8 %9 %10 %11 %12 *** SYSTEM FATAL MESSAGE 764 (XSCNDM) 764.0 - OF - FILE ENCOUNTERED WHILE READING SUBDMAP SOURCE END USER INFORMATION: SUBDMAP FILE MUST BE EMPTY USER FATAL MESSAGE 765 (XREAD) *** 765.0 - OF FILE ENCOUNTERED ON UNIT %1. THE INPUT FILE IS END - INCOMPLETE. USER INFORMATION: THE FOLLOWING GUIDE LINES SHOULD BE FOLLOWED FOR PREPARATION OF AN INPUT DECK. FILE MANAGEMENT SECTION (FMS) CAN BE ENDED BY EITHER AN "EN - FMS CARD. DJOB" OR A NON EXECUTIVE CONTROL SECTION CAN ONLY BE TERMINATED BY A "CEND" CARD. User information: This error can also occur when there is a missing right or left parenthesis in an IF - THEN DMAP statement. 767 (XSCNDM) *** USER FATAL MESSAGE 767.0 - - RECORD ENCOUNTERED WHILE READING SUBDMAP END OF SOURCE USER INFORMATION: SUBDMAP SOURCE IS MISSING AN "END" STATEMENT *** USER FATAL MESSAGE 769 (XTRACT) 769.0 COMPILE CARD SYNTAX ERROR. MISSING "=" OR NAME FOLLOWING EQUAL SIGN *** USER FATAL MESSAGE 773 (DBDEF) 773.0 THE FOLLOWING PHYSICAL FILE ALREADY EXISTS. LOGICAL NAME = %1 PHYSICAL FILE = %2 USER INFORMATION: NO ASSOCIATED DEFAULT FILES OR ASSIGNED DBSETS CAN EXIST PRIOR TO THE DATA BASE INITIALIZATION RUN. USER ACTI ON: DELETE THIS FILE AND RESUBMIT THE JOB. *** USER FATAL MESSAGE 774 (XDMAP) 774.0 THE "END" STATEMENT IS MISSING FROM THE SUBDMAP SOURCE. USER INFORMATION: THE "END" STATEMENT MARKS THE END OF EACH SUBDMAP. *** USER FATAL MESSAGE 775 (DBFASG) 775.0 NUMBER OF ASSIGNED PHYSICAL UNITS HAS BEEN EXCEEDED

85 THE LIMIT =%1 *** USER WARNING MESSAGE 776 (DGETTS) 776.0 THERE IS NO REQUEST FOR PROCESSING OF THE TIME STAMP BLOCK. THAT: IT IS ASSUMED FOR ANY EXISTING MASTER DBSET 1. THE DEFAULT BUFFER SIZE =%1 2. THE DEFAULT CLUSTER SIZE = 1 *** USER FATAL MESSAGE 777 (XTRLGN) 777.0 THE MAXIMUM NUMBER OF DBLOCATE DATABASES HAS BEEN EXCEEDED. MAXIMUM NUMBER NUMBER ALLOWED =%1 SYSTEM FATAL MESSAGE 778 (GALLOX) *** 778.0 LOGIC ERROR. USER ACTION : SEND RUN TO SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM INFORMATION MESSAGE 781 (CGPIB) 781.0 SUBDMAP %1 HAS GENERATED ONE OR MORE FATAL ERROR(S) -- (SEE ABOVE MESSAGES) NOGO = %2 *** USER/SYSTEM FATAL/WARNING/INFORMATION MESSAGE 782 782.0 (EVLMSG) THE %1 BUFFSIZE PARAMETER CANNOT BE SMALLER THAN MACHINE DEFAULT =%2 USER INFORMATION: %3 BUFFSIZE PARAMETER IGNORED. USER ACTION: USE THE INIT FMS STATEMENT TO SET THE DESIRED BUFFSIZE FOR EACH INDIVIDUAL DBSET. *** USER WARNING MESSAGE 784 (XCLNUP) 784.0 VERSION = %1 PROJECT = %2 OF THIS DATA BASE IS NOT VALID FOR RESTART PURPOSES. User information: ccur in a run when a user's DMAP sequence and SYTEM cell This can o 125 has not been set to 1. If this is the case, insert PUTSYS(1,125) into the DMAP sequence. *** USER FATAL MESSAGE 786 (NDDL) 786.0 A CIRCULAR DEPENDENCY CONDITION WAS FOUND WHILE PROCESSI NG %1 User information: Examine the DEPEN statements and make the appropriate modifications. *** USER FATAL MESSAGE 787 (XSEM) 787.0 ILLEGAL ALTER OR DMAP SEQUENCE DETECTED USER INFORMATION: NO DMAP MODULES MAY BE EXECUTED BEFORE THE XSORT AND IFP1 MODULES. User information: In Multi - Link (2 or more) Systems, Link 1 cannot be reentered. The only modules currently found exclusively in Link 1 are IFP1 and XSORT.

86 Some statem ents may be executed before these modules (arithmetic assignments/expressions). Put misplaced module after IFP1 module. *** USER WARNING MESSAGE 789 (RDSDEL) 789.0 THE DBSET NAME "%1" SPECIFIED ON A DBSETDEL STATEMENT DOES NOT EXIST. *** USER FATAL MESSAGE 790 (RDSDEL) 790.0 THE DBSETDEL STATEMENT HAS A SYNTAX ERROR NEAR COLUMN %1 USER ACTION: CHECK FOR ILLEGAL CHARACTERS, UNMATCHED PARENTHESES, OR DBSET NAMES LONGER THAN 8 CHARACTERS. *** USER FATAL MESSAGE 791 (RDSDEL) 791.0 THE DBSETDEL STATEMENTS HAVE MORE THAN %1 DBSET NAMES. *** USER FATAL MESSAGE 792 (RDSDEL) 792.0 A DBSETDEL STATEMENT SPECIFIES "%1" DBSET WHICH SHOULD NOT BE DELETED. *** USER FATAL MESSAGE 793 (CFLORD) 793.0 NGLE SUBDMAP HAS A LIMIT THE SIZE OF THE OSCAR FOR A SI OF %1 WORDS WHICH HAS BEEN EXCEEDED FOR THIS SUBDMAP (%2 WORDS REQUIRED). USER ACTION: PARTITION THIS SUBDMAP INTO SMALLER SUBDMAPS. *** USER FATAL MESSAGE 794 (XSTORE) 794.0 THE OBJECT FOR THIS SUBDMAP IS NOT COMPATIBLE WITH THIS VERSION OF NASTRAN. USER ACTION: RECOMPILE THIS SUBDMAP. *** USER FATAL MESSAGE 795 (CTYPE) 795.0 NUMBER OF CHARACTERS SPECIFIED FOR PARAMETER %1 EXCEEDS THE ALLOWABLE LIMIT OF 80. *** USER FATAL MESSAGE 796 (CCALL) 796.0 DATA BLOCK "%1" IS A DBVIEW NAME AND IS SPECIFIED AS INPUT OR OUTPUT IN A CALL STATEMENT. THIS IS NOT ALLOWED. *** USER FATAL MESSAGE 797 (CVIEW) 797.0 THE VIEWNAME %1 IS REFERENCED ON MORE THAN ONE DBVIEW STATEMENTS. *** SYSTEM WARNING MESSAGE 798 (NDDL) 798.0 THE ITEM NAMES WITH (C) OPTION OF DATA BLOCK=%1, RECORD=%2,HAVE EXCEEDED THE MAXIMUM NUMBER OF %3 PROGRAMMER ACTION: REDUCE THE NUMBER OF (C) ITEM NAMES, OR, CHANGE THE INTERNAL LIMIT TO A GREATER NUMBER *** USER FATAL MESSAGE 799 (SELCHK) 799.0

87 A SYNTAX ERROR WAS DETECTED WHILE PROCESSING A %1 CLAUSE ON A %2 STATEMENT. USER INFORMATION: ITEM BEING PROCESSED IS %3 *** USER FATAL MESSAGE 800 (CVIEW1) 800.0 THE VIEW NAME = %1 SPECIFIED ON A DBVIEW STATEMENT IS ALSO SPECIFIED AS A DATA BLOCK NAME ON A TYPE STATEMENT OR THE SUBDMAP STATEMENT. *** USER FATAL MESSAGE 801 (CKALTR) 801.0 RESULTS IN A THE OFFSET ON ALTER/MALTER STRING%1 NEGATIVE LINE NUMBER. *** USER FATAL MESSAGE 802 (CKALTR) 802.0 NO MATCH WAS FOUND FOR STRING%1. *** USER FATAL MESSAGE 803 (CKALTR) 803.0 DMAP LINE NUMBER K1 IS GREATER THAN DMAP LINE NUMBER K2. USER FATAL MESSAGE 804 (CKALTR) *** 804.0 DMAP LINE NUMBER K1 OVERLAPS PREVIOUS ALTER. PREVIOUS LINE NUMBER: %1 PREVIOUS K1:%2 PREVIOUS K2:%3 ALTER: %4 *** USER FATAL MESSAGE 805 (PRALTR) 805.0 THE INLINE SUBDMAP %1 CANNOT BE SEARCHED FOR ALTER/MALTER STRINGS. USER ACTION: COMPILE THE SUBDMAP AND APPLY THE ALTERS IN SEPARATE RUNS. *** USER FATAL MESSAGE 806 (RLALTR) 806.0 THE FOLLOWING MALTER STATEMENTS WERE NOT FOUND IN FILES: THE DMAP SOURCE *** USER FATAL MESSAGE 807 (XALTER) 807.0 THERE IS A SYNTAX ERROR IN %1 OF %2 STATEMENT. *** USER FATAL MESSAGE 809 (XALTER) 809.0 STRING1 IS NOT SPECIFIED ON THE MALTER STATEMENT ABOVE. USER FATAL MESSAGE 810 (XALTER) *** 810.0 COMPILATION OF REGULAR EXPRESSION FAILED WITH RETURN CODE:%1 *** USER FATAL MESSAGE 811 (PRCMPL) 811.0 SUBDMAP %1 IS SPECIFIED ON MORE THAN ONE COMPILE STATEMENT WITH DIFFERENT SOUIN REQUESTS. USER ACTION: SPECIFY SAME SOUIN ON THE COMPILE STATEMENTS. *** USER FATAL MESSAGE 812 (XALTER) 812.0 THE VALUE SPECIFIED FOR OCCURRENCE ON THE %1

88 STATEMENT IS LESS THAN ZERO. USER INFORMATION: THE VALUE FOR OCCURRENCE MUST BE AN INTEGER GREATER THAN ZERO. *** USER FATAL MESSAGE 813 (XCSSUB) 813.0 SOLUTION SEQUENCE%1 HAS BEEN %2 USER ACTION: USE A VERSION OF NX NASTRAN PRIOR TO VERSION 69. *** USER FATAL MESSAGE 813 (XCSSUB) 813.1 SOLUTION SEQUENCE%1 HAS BEEN %2 USER ACTION: USE SOL %3. CHECKOUT, YES IN THE BULK DATA. SPECIFY PARAM, *** USER FATAL MESSAGE 813 (XCSSUB) 813.2 SOLUTION SEQUENCE%1 HAS BEEN %2 USER ACTION: USE SOL %3. SPECIFY PARAM, ALTRED, YES IN THE BULK DATA. SPECIFY PARAM, SERST, SEMI IN THE BULK DATA IF YOU WISH TO AVOID AUTOMATIC RESTART PROCESSING. *** USER FATAL MESSAGE 813 (XCSSUB) 813.3 SOLUTION SEQUENCE%1 HAS BEEN %2 USER ACTION: USE SOL %3. *** USER FATAL MESSAGE 813 (XCSSUB) 813.4 UTION SEQUENCE%1 HAS BEEN %2 SOL USER ACTION: USE SOL %3. SPECIFY PARAM, SERST, SEMI IN THE BULK DATA IF YOU WISH TO AVOID AUTOMATIC RESTART PROCESSING. *** USER FATAL MESSAGE 813 (XCSSUB) 813.5 SOLUTION SEQUENCE%1 HAS BEEN %2 USER INFORMATION: ALTERNATE SOLUTION SEQUENCE%3 WILL BE EXECUTED. *** USER FATAL MESSAGE 813 (XCSSUB) 813.6 SOLUTION SEQUENCE%1 HAS BEEN %2 USER INFORMATION: ALTERNATE SOLUTION SEQUENCE%3 WILL BE EXECUTED. ATA IF YOU WISH SPECIFY PARAM, SERST, SEMI IN THE BULK D TO AVOID AUTOMATIC RESTART PROCESSING. *** USER WARNING MESSAGE 814 (XCSSUB) 814.0 SOLUTION SEQUENCE%1 HAS BEEN %2 USER ACTION: USE A VERSION OF NX NASTRAN PRIOR TO VERSION 69. *** USER WARNING MESSAGE 814 (XCSSUB) 814.1 SOLUTION SEQUENCE%1 HAS BEEN %2 USER ACTION: USE SOL %3. SPECIFY PARAM, CHECKOUT, YES IN THE BULK DATA.

89 *** USER WARNING MESSAGE 814 (XCSSUB) 814.2 SOLUTION SEQUENCE%1 HAS BEEN %2 USER ACTION: USE SOL %3. SPECIFY PARAM, ALTRED, YES IN THE BULK DATA. SPECIFY PARAM, SERST, SEMI IN THE BULK DATA IF YOU WISH TO AVOID AUTOMATIC RESTART PROCESSING. *** USER WARNING MESSAGE 814 (XCSSUB) 814.3 SOLUTION SEQUENCE%1 HAS BEEN %2 USER ACTION: USE SOL %3. *** USER WARNING MESSAGE 814 (XCSSUB) 814.4 SOLUTION SEQUENCE%1 HAS BEEN %2 USER ACTION: USE SOL %3. SPECIFY PARAM, SERST, SEMI IN THE BULK DATA IF YOU WISH TO AVOID AUTOMATIC RESTART PROCESSING. *** USER WARNING MESSAGE 814 (XCSSUB) 814.5 CE%1 HAS BEEN %2 SOLUTION SEQUEN USER INFORMATION: ALTERNATE SOLUTION SEQUENCE%3 WILL BE EXECUTED. *** USER WARNING MESSAGE 814 (XCSSUB) 814.6 SOLUTION SEQUENCE%1 HAS BEEN %2 USER INFORMATION: ALTERNATE SOLUTION SEQUENCE%3 WILL BE EXECUTED. SPECIFY PARAM, SERST, SEMI IN THE BULK DATA IF YOU WISH TO AVOID AUTOMATIC RESTART PROCESSING. *** USER FATAL MESSAGE 815 (RDINIT) 815.0 DBSET %1 IS ALREADY SPECIFIED ON AN INIT STATEMENT. USER INFORMATION: ONLY ONE INIT STATEMENT MAY BE SPECIFIED PER DBSET. *** USER WARNING MESSAGE 816 (RDACQU) 816.0 "NDDLOLD" IS NO LONGER AVAILABLE. USER INFORMATION: "NDDL" WILL BE USED INSTEAD. *** USER FATAL MESSAGE 817 (CKALTR) 817.0 THE FOLLOWING ALTER STATEMENT INSERTS AFTER THE END STATEMENT. *** USER FATAL MESSAGE 818 (CHKFM) 818.0 THE FMS STATEMENT %1 IS NOT UNIQUE. USER ACTION: SPECIFY EITHER %2 OR %3 *** USER/SYSTEM FATAL/WARNING/INFORMATION MESSAGE 819 819.0 (EV LMSG) INVALID CHARACTER "%1" *** USER/SYSTEM FATAL/WARNING/INFORMATION MESSAGE 820 820.0 (EVLMSG) OPERAND IS MISSING BEFORE "%1"

90 *** USER FATAL MESSAGE 821 (A?) 821.0 THE EQUAL SIGN IS MISSING IN A %1 %2 *** USER/SYSTEM FATAL/WARNING/INFORMATION MESSAGE 821 821.1 (EVLMSG) THE EQUAL SIGN IS MISSING BEFORE "%1" *** USER/SYSTEM FATAL/WARNING/INFORMATION MESSAGE 822 822.0 (EVLMSG) EXTRA CHARACTERS ARE SPECIFIED ON DEFINE STATEMENT "%1" *** USER/SYSTEM FATAL/WARNING/INFORMATION MESSAGE 823 823.0 (EVLMSG) OPERATOR IS MISSING BEFORE "%1" *** USER/SYSTEM FATAL/WARNING/INFORMATION MESSAGE 824 824.0 (EVLMSG) RIGHT PARENTHESIS IS UNBALANCED AT "%1" *** USER/SYSTEM FATAL/WARNING/INFORMATION MESSAGE 825 825.0 (EVLMSG) RIGHT PARENTHESIS IS MISSING AFTER "%1" *** USER WARNING MESSAGE 826 (SSWTOF) 826.0 THE DIAG%1 EXECUTIVE CONTROL STATEMENT IS INVALID. USER INFORMATION: THE DIAG NUMBER MUST BE GREATER TH AN ZERO AND LESS THAN 65. *** USER WARNING MESSAGE 975, 975.0 XYTRAN DOES NOT RECOGNIZE %1 AND IS IGNORING User information: Keyword XYPLOT package is not correct; see Section 13.3 of NX NASTRAN Reference Manual. *** USER WARNING MESSAGE 976, 976.0 OUTPUT DATA BLOCK%1 IS PURGED. XYTRAN WILL PROCESS ALL REQUESTS OTHER THAN PLOT User information: The data block output from XYTRAN has been purged; thus no XYPLOTs are possible. *** USER WARNING MESSAGE 977, 977.0 FOLLOWING NAMED DATA - BLOCK IS NOT IN SORT - II FORMAT User information: Probably a DMAP calling sequence error to XYTRAN. Only SORT2 data blocks can be purged. *** USER WARNING MESSAGE 979, 979.0 AN XY - OUTPUT REQUEST FOR POINT OR ELEMENT ID%1 - - CURVE IS BEING PASSED OVER. THE ID COULD NOT BE %2 FOUND IN DATA BLOCK%3 SUBCASE%4 *** USER WARNING MESSAGE 979, 979.1

91 AN XY - OUTPUT REQUEST FOR POINT OR ELEMENT ID%1 %2 - CURVE IS BEING PASSED OVER. THE ID COULD NOT BE - FOUND IN DATA BLOCK%3 User information: Curve request could not be found. Point, element or subcase requested was not on input data block. *** SYSTEM WARNING MESSAGE 979 (XYTRAN) 979.2 OUTPUT REQUEST FOR POINT OR ELEMENT ID%1 - %2 - - AN XY CURVE IS BEING IGNORED BECAUSE A LOCAL MEMORY AREA HAS BEEN EXCEEDED, REQUEST= %3 CURRENT SIZE=%4. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT DEVELOPMENT WITH INFORMATION. *** USER WARNING MESSAGE 979 (XYTRN2) 979.3 - OUTPUT REQUEST FOR FLUID POINT ID%1 - AN XY 2 - CURVE IS % BEING PASSED OVER. THE ID COULD NOT BE FOUND IN DATA BLOCK%3%4 User information: Curve request could not be found. Point, frequency, mode number, panel name or panel grid id was not on input data block. *** USER WARNING MESSAGE 980, 980.0 INSUFFICIENT CORE TO HANDLE ALL DATA FOR ALL CURVES OF THIS FRAME ID =%1 COMPONENT =%2 COMPONENT =%3 DELETED FROM OUTPUT User information: Increase memory request. *** USER WARNING MESSAGE 981, 981.0 COMPONENT =%1 FOR ID=%2 IS TOO LARGE. THIS COMPONENTS CURVE NOT OUTPUT User information: Component request was larger than the data item available; see Section 13.3 of NX NASTRAN Reference Manual. *** USER WARNING MESSAGE 981, 981.1 COMPONENT =COMPONENT =%1 FOR I D=%2 IS NULL. THIS COMPONENTS CURVE NOT OUTPUT. *** USER WARNING MESSAGE 982. 982.0 FORMAT OF %1 INCOMPATIBLE WITH SDR3 DESIGN. CODE =%2 User information: This message appears when the SDR3 module encounters trouble. The exact nature of the problem can be detected from the "code" number. The file type causing the problem can be determined from its name (for example, OESi is the stress output file, and OUGVi the displacement,

92 velocity, and acceleration output file). The function of this module is to convert SORT1 output tables to SORT2 tables. It operates on one output type per pass (for example, displacements, then velocities, then stresses in BAR elements, then ROD elements, etc.). Since the user controls the co ntent and size of the output tables with case control and plot requests, it is often possible to avoid these errors, as described below. Codes Cause and User Action --------------------- ----- 110 Insufficient memory. Increase memory request, ease the number 140 of variables output or decr on one run by using restarts for additional output. 150 The following codes should not occur on standard solution sequences. Please send any such runs to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. ser - written DMAPs, it is likely that an illegal input block is If they occur on u used, or that the input block is not correctly formatted. Codes Cause and User Action ----- --------------------- 100 The ID record is missing on the input file. 120 rd. 101 Missing data reco 102 Wrong number of words in input block. 122 112 The number of words per record is not an integer multiple of the number 142 of words per entry. 152 165 Logic error or ID record indicates zero words. *** USER WARNING MESSAGE 984. 984.0 O UTPUT DATA BLOCK NO.%1 IS PURGED. SDR3 CANNOT PROCESS INPUT DATA BLOCK %2 User information: Probably DMAP calling sequence error. Needed output is purged. *** USER WARNING MESSAGE 992, 992.0 XYPLOT INPUT DATA FILE I.D. RECORDS TOO SHORT. XYPLOT ABANDONED. User information: The input data file records have invalid word counts and further plotting is not feasible. *** USER WARNING MESSAGE 993, 993.0 XYPLOT FOUND ODD NR. OF VALUES FOR DATA PAIRS IN FRAME%1, CURVE NR.%2. LAST VALUE IGNORED. User information:

93 May indicate a bad input file, but plotting continues. *** USER WARNING MESSAGE 994, 994.0 XYPLOT OUTPUT FILE NAME %1 NOT FOUND. XYPLOT ABANDONED. User information: PLT2 is missing. *** USER WARNING MESSAGE 997, 997.0 NR.%1. FRAME NR.%2 INPUT DATA INCOMPATIBLE. ASSUMPTIONS MAY PRODUCE INVALID PLOT. User information: Nr. %1 may take any value from 1 to 4 with the following meaning: 1. Specified X maximum equal X minimum. If this value is zero, - then X maximum is set to 5.0 and X minimum to 5.0, otherwise 5 times the absolute value of X maximum is added to X maximum and subtracted from X minimum. 2. Specified X maximum is smaller than X minimum. The values are reversed. 3. Same meaning as number 1 except for Y maximum and Y minimum. 4. Same meaning as number 2 except for Y maximum and Y minimum. *** SYSTEM FATAL MESSAGE 1001 (BGNSYS) 1001.0 ERROR IN READING FORTRAN UNIT 2 FILE *** SYSTEM FATAL MESSAGE 1002 (BGNSYS) 1002.0 - - FILE IN READING FORTRAN UNIT 2 FILE OF PREMATURE END *** SYSTEM FATAL MESSAGE 1003 (OPNPFL) 1003.0 *** SYSTEM FATAL MESSAGE 1003 (CLSPFL) 1003.1 SYSTEM WARNING MESSAGE 1003 (FORTIO) *** 1003.2 UNIT %1 DOES NOT HAVE A CORRESPONDING VALUE IN FORUNT ARRAY. *** USER INFORMATION: UNITS MUST BE ASSIGNED A PHYSICAL FILE NAME USING AN ASSIGN STATEMENT. User information: As an example, for punch files unit 7 must be one of the units on the ASSIGN statement. *** SYSTEM FATAL MESSAGE 1003 (ISHELL) 1003.3 UNIT %1 DOES NOT HAVE A CORRESPONDING VALUE IN FORUNT ARRAY. *** USER INFORMATION: UNITS MUST BE ASSIGNED A PHYSICAL FILE NAME USING AN ASSIGN STATEMENT. User information: As an example, for punch files unit 7 must be one of the units on the ASSIGN statement.

94 *** SYSTEM FATAL MESSAGE 1004 (XSEM) 1004.0 FORTRAN UNIT OPEN/CREATE ERROR. USER INFORMATION: UNIT=%1, IOSTAT=%2 *** SYSTEM FATAL MESSAGE 1004 (XSEM) 1004.1 FORTRAN UNIT CLOSE/DELETE ERROR. USER INFORMATION: UNIT=%1, IOSTAT=%2 User information: A possible cause is that you ran out of disk space. *** USER FATAL MESSAGE 1004 (CLSPFL) 1004.2 SYSTEM FATAL MESSAGE 1005 (ENDSYS) *** 1005.0 ERROR IN WRITING FORTRAN UNIT 2 FILE *** SYSTEM WARNING MESSAGE 1006 (F04SUM) 1006.0 CANNOT FIND END FOR %1%2 BEGIN AT LINE NUMBER %3 *** SYSTEM WARNING MESSAGE 1007 (F04SUM) 1007.0 LOGIC ERROR %1 WITH FOLLOWING RECORD(S): %2 %3 System information: Possible cause: If DIAG 49 is turned on and the time spent in some of the modules are too small to cause the END statement to to be printed, then the message may be issued without sum ming the time spent in an individual module. This can occur even when there are other modules that substantial time. USER ACTION: Add the following NASTRAN System Cell to your run: NASTRAN SYSTEM(20) = 0 4SUM) *** SYSTEM WARNING MESSAGE 1008 (F0 1008.0 CANNOT FIND END FOR %1 AT LINE NUMBER%2 *** USER INFORMATION MESSAGE 1009 (F04SUM) 1009.0 STATISTICAL SUMMARY OF ABOVE LOG FILE FOLLOWS. *** USER INFORMATION MESSAGE 1010 (F04SUM) 1010.0 LOG FILE DOES NOT CONTAIN ANY PERTINENT STATISTICAL INFORMATION *** USER FATAL MESSAGE 1012 (GALLOC) 1012.0 DBSET %1 IS FULL AND NEEDS TO BE EXPANDED. USER ACTION: INCREASE THE DBSET SIZE IN THE DECK. ALTERNATIVELY, YOU CAN SET SSCR=80GB AND SDBA LL=80GB IN THE RC FILE OR AS PART OF THE NASTRAN COMMAND LINE. THE VALUE OF 80GB HERE IS USED ONLY AS AN EXAMPLE. THIS VALUE SHOULD REFLECT THE AMOUNT OF FREE DISK SPACE AVAILABLE ON THE MACHINE. THE DBSET IS NOT ALLOWED

95 TO GROW ANY LARGER THAN THIS VA LUE. *** SYSTEM FATAL MESSAGE 1013 1013.0 CANNOT FIND CORRECT CLUSTER POINTER RECORD *** SYSTEM FATAL MESSAGE 1014 (GBKZ67) 1014.0 ERROR IN LOOKING UP CLUSTER NUMBER System information: This has been observed when the maximum number of superelements has been exceeded. *** SYSTEM FATAL MESSAGE 1015 (GBKZ67) 1015.0 PHYSICAL FILE NOT FOUND IN FILE ASSIGNMENT TABLE System information: This may be on restart issued if scratch files were not deleted in previous run. It may also be issued if there is insufficient memory. *** SYSTEM FATAL MESSAGE 1017 (GBKZ67) 1017.0 NO CLUSTER RECORD INCORE FOR DATA BASE DIRECTORY *** USER FATAL MESSAGE 1019 (OPNPFL) 1019.0 *** SYSTEM FATAL MESSAGE 1020 (ZIO) 1020.0 UNABLE TO PERFORM LOGICAL TO PHYSICAL FILE ASSIGNMENT *** SYSTEM FATAL MESSAGE 1021 (ZIO) 1021.0 ERROR OCCURRED IN BIORD *** SYSTEM FATAL MESSAGE 1022 (ZIO) 1022.0 ERROR OCCURRED IN BIOWRT *** SYSTEM FATAL MESSAGE 1023 (ZIO) 1023.0 ATTEMPT TO OPEN A FILE WHICH WAS PREVIOUSLY OPENED (%1) *** SYSTEM FATAL MESSAGE 1026 (ZIO) 1026.0 ATTEMPT TO ACCESS A FILE WHICH IS NOT OPENED *** SYSTEM FATAL MESSAGE 1027 (ZIO) 1027.0 SAVPOS ATTEMPTED ON A FILE WHICH WAS OPENED TO UPDATE *** SYSTEM FATAL MESSAGE 1028 (ZIO) 1028.0 FILPOS ATTEMPTED ON A FILE WHICH WAS OPENED TO APPEND *** SYSTEM FATAL MESSAGE 1029 (ZIO) 1029.0 ATTEMPT TO READ FROM AN EMPTY FILE *** SYSTEM FATAL MESSAGE 1030 (ZIO) 1030.0 BLOCK NUMBER MISMATCH IN READ *** SYSTEM FATAL MESSAGE 1031 (ZIO) 1031.0 FIELD 3 OF CONTROL WORD NOT EQUAL TO RECORD LENGTH. FIELD3 =%1 REC LENGTH =%2 System information: One cause of this may be an illega l BUFFSIZE (e.g., larger than allowed). *** SYSTEM FATAL MESSAGE 1032 (ZIO) 1032.0 ATTEMPT TO READ PAST END OF DATA

96 *** SYSTEM FATAL MESSAGE 1033 (ZIO) 1033.0 FILE %1 NOT FOUND IN FIST *** SYSTEM FATAL MESSAGE 1034 (ZIO) 1034.0 UNRECOGNIZED CONTROL WORD ENCOUNTERED AFTER FILPOS OPERATION *** SYSTEM FATAL MESSAGE 1035 (ZIO) 1035.0 ATTEMPT TO BCKREC PAST BEGINNING OF BLOCK *** SYSTEM FATAL MESSAGE 1036 (ZIO) 1036.0 UNRECOGNIZED CONTROL WORD ENCOUNTERED AFTER BCKREC OPERATION *** SYSTEM FATAL MESSAGE 1037 (ZIO) 1037.0 ATTEMPT TO BCKREC ON A FILE OPENED FOR APPEND *** SYSTEM FATAL MESSAGE 1038 (ZIO) 1038.0 ILLEGAL OPCODE =%1 *** SYSTEM FATAL MESSAGE 1041 (GALLEX) 1041.0 - DIRECTORY FOR %1 HAS BEEN FILLED UP AND IS NOT THE DB EXPANDABLE. USER ACTION: 1. DELETE UNWANTED FILES FROM THE DBSET IF PERMANENT. 2. INCREASE BUFFSIZE AND/OR CLUSTER SIZE FOR THIS DBSET, IF TEMPORARY. *** SYSTEM FATAL MESSAGE 1042 (GALLEX) 1042.0 FILE %1 NOT FOUND IN FIST *** USER FATAL MESSAGE 1046, (INQPFL) 1046.0 FORTRAN INQUIRE ERROR IOSTAT = %1, %2 LOGICAL = %3 FILE = %4 *** USER FATAL MESSAGE 1047 (PRCMPL) 1047.0 ILLEGAL INPUT FOR SUBDMAP %1. THE ABOVE COMMAND IS AN NDDL COMMAND. USER ACTION: CORRECT OR REMOVE THE SUBDMAP COMPILE CARD. User information: This error occurs when compiling a SUBDMAP which contains NDDL specify that you statements. Correct your COMPILE statement to are compiling NDDL, using the NDDL keyword on the COMPILE statement. *** USER FATAL MESSAGE 1048 (PRCMPL) 1048.0 ILLEGAL INPUT FOR NDDL %1. THE ABOVE COMMAND IS NOT AN NDDL COMMAND. USER ACTION: CORRECT OR REMOVE THE NDDL COMPILE CARD. User information: This error occurs when compiling an NDDL which contains DMAP statements.

97 Correct your COMPILE card to specify that you are compiling SUBDMAP, LE card. using the SUBDMAP keyword on the COMPI *** USER FATAL MESSAGE 1049 (XSPAC) 1049.0 AMOUNT OF USER OPENCORE(HICORE), MASTER(RAM) SCRATCH(MEM) AND BUFFER POOL SIZE HAVE EXCEEDED THE NX NASTRAN MEMORY LIMIT: NX NASTRAN MEMORY LIMIT =%1 WORDS USER OPENCORE(HICORE) =%2 MASTER(RAM ) SIZE =%3 SCRATCH(MEM) SIZE =%4 (%5 BUFFERS) BUFFER POOL SIZE =%6 (%7 BUFFERS) USER ACTION: DECREASE THE SUM OF HICORE, MASTER(RAM), SCRATCH(MEM) AND BUFFER POOL SIZE TO FIT WITHIN THE NX NASTRAN MEMORY LIMIT. *** USER WARNING MESSAGE 1 050 (DBPRVR) 1050.0 THE PROJECT ID = '%1' SPECIFIED ON THE DBDIR CARD IS NOT DEFINED IN THIS DATA BASE *** USER WARNING MESSAGE 1051 (DBPRVR) 1051.0 THE VERSION ID = %1 OF PROJECT '%2' ON THE DBDIR CARD HAS ALREADY BEEN DELETED. USER INFORMATION: THIS DBDIR CARD IS IGNORED. *** USER WARNING MESSAGE 1052 (DBPRVR) 1052.0 THE VERSION ID = %1 OF PROJECT '%2' ON THE DBDIR CARD HAS NEVER BEEN CREATED. USER INFORMATION: THIS DBDIR CARD IS IGNORED. SSAGE 1053 (GPVTSH) *** USER FATAL ME 1053.0 PARAMETER INPUT DATA ERROR, ILLEGAL VALUE FOR PARAMETER NAMED %1. *** SYSTEM WARNING MESSAGE 1102 (BPOPEN) 1102.0 BUFFER FOUND IS ALREADY AN ACTIVE BUFFER *** SYSTEM FATAL MESSAGE 1103 (BPOPEN) 1103.0 LOGIC ERROR IN BUFFER POOL MANAGEMENT LINK LIST. BUFFER IN LINK LIST OF %1 EXCEEDS DEFAULT SIZE OF %2 USER ACTION: PLEASE SEND RUN TO SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. System information: trices. This has been observed for very dense complex unsymmetric ma An avoidance is to increase WSL or decrease HICORE and REAL. See Error Report 3670 in section 17.4 of NX NASTRAN Reference Manual. *** SYSTEM FATAL MESSAGE 1104 (XCHK) 1104.0 FDICT TABLE IS INCORRECT *** SYSTEM WARNING MESSAGE 1105 (BPSIZE) 1105.0

98 NO MEMORY AVAILABLE FOR BUFFER POOLING. PROGRAMMER INFORMATION: BPOOL = %1 MAXBUF = %2 NEEDBF = %3 LIMIT = %4 *** USER FATAL MESSAGE 1105 (XCHK) 1105.1 CANNOT FIND DATA BLOCK NAMED %1 HEADER RECORD = %2 *** SYSTEM FATAL MESSAGE 1106 1106.0 ATTEMPT TO CLOSE FILE %1 WHICH IS NOT CURRENTLY OPENED. USER INFORMATION: THE ABOVE FILE CONTAINS THE DATA BASE DIRECTORY *** SYSTEM FATAL MESSAGE 1106 (CLSDBS) 1106.1 ATTEMPT TO CLOSE FILE %1 WHICH IS NOT CURRENTLY OPENED. USER INFORMATION: THE ABOVE FILE CONTAINS THE DATA BASE DIRECTORY *** SYSTEM FATAL MESSAGE 1106 (CLSDBM) 1106.2 ATTEMPT TO CLOSE FILE %1 WHICH IS NOT CURRENTLY OPENED. USER INFORMATION: THE ABOVE FILE CONTAINS THE DATA BASE BIT MAP *** USER FATAL MESSAGE 1107 (OPNENT) 1107.0 A NON - 400 FIST NUMBER OF %1 USED, WHEN ATTEMPTING TO OPEN THE DBENTRY FILE *** SYSTEM FATAL MESSAGE 1107 (CLSENT) 1107.1 - 400 FIST NUMBER OF %1 USED, WHEN ATTEMPTING TO A NON CLOSE THE DBENTRY FILE *** SYSTEM FATAL MESSAGE 1108 (XCHK) 1108.0 PURGE TABLE OVERFLOWED *** SYSTEM FATAL MESSAGE 1108 (ZRDBLK) 1108.1 TEMPORARY NDDL BULK ENTRY NAME TABLE OVERFLOWED **** SYSTEM FATAL MESSAGE 1112 (LCLEAD) 1112.0 ATTEMPT TO ADD A DBENTRY IN A LOCATION WHERE ANOTHER DBENTRY ALREADY EXISTS. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: DBENTRY POINTER, /FREEX/ AND DBENTRY ARE: CONTENTS OF %1 %2 %3 **** SYSTEM FATAL MESSAGE 1112 (DBEADD) 1112.1 ATTEMPT TO ADD A DBENTRY IN A LOCATION WHERE ANOTHER DBENTRY ALREADY EXISTS. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM WARNING MESSA GE 1113 (DBEDEL) 1113.1

99 WHILE ATTEMPTING TO DECREMENT THE PVA TABLE COUNTER, NO ENTRIES WERE FOUND FOR THIS PATH. USER ACTION: MAKE RUN USING FMS COMMAND DBFIX *** SYSTEM FATAL MESSAGE 1114 (XREMOV) 1114.0 LOOP PROBLEM EXISTS IN DBENTRY TABLE POTENTIAL INFINITE - FOR DATA BLOCK = %1 USER ACTION: RESUBMIT THIS RUN WITH FMS COMMAND DBFIX *** SYSTEM FATAL MESSAGE 1114 (XECHRD) 1114.1 POTENTIAL INFINITE - LOOP PROBLEM EXISTS IN DBENTRY TABLE USER ACTION: RESUBMIT THIS RUN WITH FMS COMMAND DBFIX PROGRAMMER INFORMATION: ENTPTR=%1 CNTBLK=%2 *** SYSTEM FATAL MESSAGE 1114 (XECHAD) 1114.2 - LOOP PROBLEM EXISTS IN DBENTRY TABLE POTENTIAL INFINITE USER ACTION: RESUBMIT THIS RUN WITH FMS COMMAND DBFIX PROGRAMMER INFORMATION: ENTPTR=%1 ENTPT2=%2 CNTBLK=%3 %4%5%6 *** SYSTEM FATAL MESSAGE 1114 (PRJVFN) 1114.3 - LOOP PROBLEM EXISTS IN DBENTRY TABLE POTENTIAL INFINITE FOR %1 = %2 USER ACTION: RES UBMIT THIS RUN WITH FMS COMMAND DBFIX. *** SYSTEM FATAL MESSAGE 1114 (DBXREM) 1114.4 POTENTIAL INFINITE - LOOP PROBLEM EXISTS IN DBENTRY TABLE FOR DATA BLOCK = %1 USER ACTION: RESUBMIT THIS RUN WITH FMS COMMAND DBFIX. *** SYSTEM FATAL MESSAGE 1115 (XEQDIN) 1115.0 ERROR OPENING THE DATABASE TRANSACTION FILE (DBRQUE). GINO FILE NAME = %1 USER ACTION: SEND THIS RUN TO SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. System information: the B matrix This has been observed when using the SOLVE module and in A x = B is null. Explicitly define an identity matrix for the B B matrix input. If the SOLVE module is not used, then contact SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 1117 (DBESEA) 1117.0 DBENTRY TABLE POI NTER TO DB DIRECTORY EQUALS 0. *57* SYSTEM WARNING MESSAGE 1119 (DIRCLN) 1119.0 - DIRECTORY ATTEMPTING TO DELETE AN EMPTY DB USER INFORMATION: THIS MAY INDICATE A PROBLEM. NAME=%1 ON DBSET %2 User information: This message will be issued if a dat a block name appears twice - time - used) is also at that as input to a module and its LTU (last

100 module. For example, in the following module, SMPYAD PHI,MAA,PHI,,,/X/3////1 $ this error would occur if this were the last time PHI were used. This does not indicate a problem. *** SYSTEM FATAL MESSAGE 1120 (DIRPT3) 1120.0 THE DATA BASE DBENTRY TABLE HAS NO DBSET/FILPOS OFFSET USER INFORMATION: THIS MAY INDICATE THAT THE DATABASE DIRECTORY HAS BEEN DESTROYED USER ACTION: TURN ON DIAG 2 AND SEND RUN TO SIEMENS PLM SOFTWARE CUSTOMER SUPPORT PROGRAMMER ACTION: VARIABLES OF INTEREST: NAME = %1 DBEPTR,DBDPTR,DBSPTR = %2 *** USER WARNING MESSAGE 1121 (DIRPT2) 1121.0 L OPCODE = %1. ROUTINE DIRPT2 WAS CALLED WITH AN ILLEGA USER INFORMATION: NO ***DIAG 2*** PRINT HAS BEEN PRODUCED. *** USER FATAL MESSAGE 1122 (DIRPT3) 1122.0 THE FILE ASSIGNMENT (DBSPACE) TABLE DOES NOT CONTAIN AN ENTRY FOR THE SCRATCH DBSET, INDICATING IT WAS NOT ALLOCATED FOR THIS RU N. *** SYSTEM FATAL MESSAGE 1123 (GDBSNO) 1123.0 DATABASE NUMBER:%1 IS OUT OF RANGE. DBSPTR =%2 USER ACTION : MAKE SURE ALL ATTACHED DATABASE(S), INCLUDING THE DELIVERY DATABASE, ARE VERSION (e.g. 69) COMPATIBLE. *** USER FATAL MESSAGE 1124 (GNFIST) 1124.0 AN APPENDABLE OUTPUT FILE %1 CANNOT BE ACCESSED WITH THE DBLOCATE COMMAND. USER ACTION: REMOVE THIS DATABLOCK NAME FROM THE DBLOCATE COMMAND AND RERUN JOB ****SYSTEM FATAL MESSAGE 1125 (GNFIST) 1125.0 PROGRAM LOGI C ERROR -- UNGENERATED OUTPUT DATA BLOCK %1(%2) DETECTED AT CONCLUSION OF FILE ALLOCATION ROUTINE. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 1126 (GNFIST) 1126.0 DMAP MODULE %1 IS ATTEMPTING TO OUTPUT DATABLOCK %2 NAME = %3, WHICH ALREADY EXISTS. USER ACTION: DELETE THE DATABLOCK, OR USE FILE %4=OVRWRT User information: In nonlinear analysis, this occurs when iterations for the current subcase have

101 been terminat ed without convergence. *** USER FATAL MESSAGE 1127 (SALLOC) 1127.0 DBUNLOAD IS ATTEMPTING TO ACCESS DATA BLOCK NAME = %1 WHICH IS ON AN UNAVAILABLE DBSET =%2 *** USER FATAL MESSAGE 1127 (GNFIST) 1127.1 DMAP MODULE %1 IS ATTEMPTING TO ACCE SS DATA BLOCK %2 NAME = %3 WHICH IS ON AN UNAVAILABLE DBSET *** SYSTEM FATAL MESSAGE 1128 (GNLOC) 1128.0 A LOCATION PARAMETER HAS AN INCORRECT TYPE AND/OR LENGTH. USER INFORMATION: 1. GNLOC PERFORMS MODULE FILE ALLOCATIONS 2. LOCATION PARAMETER MUST BE TYPE 3 (BCD) AND LENGTH 2 USER ACTION: SEND RUN TO SIEMENS PLM SOFTWARE CUSTOMER SUPPORT PROGRAMMER INFORMATION: 1. THE DBDIR RECORD INDICATES TYPE = %1 AND LENGTH = %2 2. THE FULL DBDIR RECORD IS: %3%4%5 VALUE = %6 %7 %8 PROGRAMMER ACTION: THE NDDL COMPILER SHOULD HAVE CAUGHT THIS DISCREPANCY. THE DATA BASE MAY HAVE BEEN DESTROYED *** USER FATAL MESSAGE 1129 (GNLOC) 1129.0 THE FILE ASSIGNMENT (DBSPACE) TABLE CONTAINS NO ENTRY FOR LOCATION PARAMETER %1 = %2 ER INFORMATION: US 1. GNLOC PERFORMS MODULE FILE ALLOCATIONS 2. THE DBSET %3 WAS NOT ALLOCATED FOR THIS RUN PROGRAMMER INFORMATION: THE FULL DBDIR RECORD CONTAINING THIS LOCATION PARAMETER IS: %4%5%6%7 *** SYSTEM FATAL MESSAGE 1130 (GNLOC) 1130.0 PARAMETERS USED AS "LOCATION" PARAMETERS MUST BE OF TYPE=3 (BCD) AND LENGTH=2. USER INFORMATION: THE PARAMETER DBNAME TABLE ENTRY FOR THIS PARAMETER IS : %1%2 USER ACTION: SEND RUN TO SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION:

102 1. THE NDDL COMPILER SHOULD HAVE CAUGHT THIS ERROR. 2. IF THE PARAMETER ENTRY DUMP IS CORRECT, THEN OPEN CORE MAY HAVE BEEN OVERWRITTEN, OR 3. THE DATA BASE MAY HAVE BEEN DESTROYED/DAMAGED *** SYSTEM FATAL MESSAGE 1131 (GNPARM) 1131.0 THE POINTER INTO THE VPS TABLE FROM THE OSCAR IS ZERO USER ACTION: SEND RUN TO SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: THIS ERROR MAY MEAN THAT OPEN CORE HAS BEEN OVERWRITTEN *** USER FATAL MESSAGE 1133 (GNXFST) 1133.0 LID INPUT FIST NUMBER = %1 INVA JOB TERMINATED DUE TO ABOVE ERROR *** USER FATAL MESSAGE 1135 (XTVPS2) 1135.0 DMAP MODULE %1 IS ATTEMPTING TO ACCESS PARAMETER NAME = %2 WHICH IS ON AN UNAVAILABLE DBSET = %3 IN DATABASE NUMBER (DBSNO) = %4 *** USER FATAL MESSAGE 1135 1135.1 THE FILE ASSIGNMENT (DBSPACE) TABLE CONTAINS NO ENTRY FOR THE %1 DBSET, INDICATING IT WAS NOT ALLOCATED FOR THIS RUN. User information: Check ASSIGN FMS statements and DBS keyword for misspelled or improper pecification. physical file s *** USER FATAL MESSAGE 1135 (GNPREP) 1135.3 THE FILE ASSIGNMENT (DBSPACE) TABLE CONTAINS NO ENTRY FOR THE SCRATCH DBSET, INDICATING IT WAS NOT ALLOCATED FOR THIS RUN. User information: Check ASSIGN FMS statements and DBS keyword fo r misspelled or improper physical file specification. *** USER FATAL MESSAGE 1135 (GNPARM) 1135.4 DMAP MODULE %1 IS ATTEMPTING TO ACCESS PARAMETER NAME = %2 WHICH IS ON AN UNAVAILABLE DBSET = %3 IN DATABASE NUMBER (DBSNO) =%4 *** USER FATAL MESSAGE 1135 (GNLOC) 1135.5 THE FILE ASSIGNMENT (DBSPACE) TABLE CONTAINS NO ENTRY FOR THE MASTER DBSET, INDICATING IT WAS NOT ALLOCATED FOR THIS RUN. User information:

103 Check ASSIGN FMS statements and DBS keyword for misspelled or improper file specification. physical *** USER FATAL MESSAGE 1135 (GNALOC) 1135.6 THE FILE ASSIGNMENT (DBSPACE) TABLE CONTAINS NO ENTRY FOR THE SCRATCH OR OBJSCR DBSETS, INDICATING THEY WERE NOT ALLOCATED FOR THIS RUN. User information: Check ASSIGN FMS statemen ts and DBS keyword for misspelled or improper physical file specification. *** SYSTEM FATAL MESSAGE 1139 (QVAGEN) 1139.0 THE MAXIMUM QUALIFIER TABLE LENGTH HAS BEEN EXCEEDED USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT REGARDING THIS ERROR. PROGRAMMER INFORMATION: THE MAXIMUM LENGTH IS %1 PROGRAMMER ACTION: INCREASE MAXIMUM TABLE LENGTH IN CALLING ROUTINE. *** SYSTEM FATAL MESSAGE 1139 (QUASEA) 1139.1 T HE MAXIMUM QUALIFIER TABLE LENGTH HAS BEEN EXCEEDED USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT REGARDING THIS ERROR. PROGRAMMER INFORMATION: THE MAXIMUM TABLE LENGTH IS %1 THE REQUESTED NUMBER OF QUALIFIER IS %2 ASE MAXIMUM TABLE LENGTH IN PROGRAMMER ACTION: INCRE CALLING ROUTINE. *** SYSTEM FATAL MESSAGE 1139 1139.2 THE MAXIMUM QUALIFIER TABLE LENGTH HAS BEEN EXCEEDED *** USER FATAL MESSAGE 1140 (RESENT) 1140.0 AN ERROR HAS BEEN DETECTED IN THE DATABASE POINTERS USER ACTION: SUBMIT A RUN WITH FMS COMMAND DBFIX. PROGRAMMER ACTION: THIS ERROR OCCURRED WHILE SEARCHING FOR THE BEGINNING OF THE DBENTRY FREE - CHAIN. THE FREE - CHAIN APPEARS TO BE CONNECTED IN A CIRCULAR LOOP. *** USER INFORMATION MESSAGE 1141 (RESENT) 1141.0 A DB - DIRECTORY NOT PROPERLY CLOSED IN THE PREVIOUS RUN IS BEING RESTORED BY THIS RUN. *** USER FATAL MESSAGE 1142 (RSPRVR) 1142.0 THE RESTART PROJECT ID = '%1' IS NOT DEFINED IN THIS DATA BASE *** USER FATAL MESSAGE 1142 (DBCLPR) 1142.1

104 THE PROJECT ID ='%1' SPECIFIED ON THE DBCLEAN CARD IS NOT DEFINED IN THIS DATA BASE *** USER FATAL MESSAGE 1143 (RSPRVR) 1143.0 THE RESTART STATEMENT REFERENCES RESTART VERSION ID = %1,WHICH DOES NOT EXIST. *** USER INFORMATION MESSAGE 1144 (RSPRVR) 1144.0 LAST VERSION CREATED IS BEING USED FOR THIS RESTART JOB. LAST VERSION = %1 PROJECT = %2 *** USER FATAL MESSAGE 1145 (RSPRVR) 1145.0 THE VERSION ID = %1 OF PROJECT '%2' SPECIFIED ON RESTART CARD HAS BEEN DELETED PRIOR TO THIS RUN. A RESTART IS IMPOSSIBLE. *** SYSTEM FATAL MESSAGE 1146 (RESENT) 1146.0 ATTEMPTING TO READ BEYOND THE END OF DATA ON THE DATABASE DBENTRY TABLE. USER ACTION: RESUBMIT THIS RUN WITH FMS COMMAND DBFIX. PROGRAMMER INFORMATION: ATTEMPT TO READ DBENTRY BLOCK NUMBER %1. THE LAST DBENTRY BLOCK NUMBER SPECIFIED IN DBDIR TABLE IS %2. *** SYSTEM WARNING MESSAGE 1147 (WRTTRL) 1147.0 BAD TRAILER FOR FILE %1 System information: This message will be issued when one of the trailer values (see the NX NASTRAN DMAP Module Dictionary) is outside an accepted range. For example, if the density of a matrix exceeds 1.0, the message is issued. Usually, these mes sages will not have an adverse affect on the job, but should be reported to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT as a precaution. *** SYSTEM WARNING MESSAGE 1147 (SSMHFD) 1147.1 BAD TRAILER FOR FILE %1 System information: This message will be issued when one of the trailer values (see the NX NASTRAN DMAP Module Dictionary) is outside an accepted range. For example, if the density of a matrix exceeds 1.0, the message is issued. Usually, these messages will not have an adv erse affect on the job, but should be reported to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT as a precaution. *** SYSTEM WARNING MESSAGE 1148 (WRTTRL) 1148.0 UNABLE TO WRITE TRAILER FOR FILE %1 *** SYSTEM WARNING MESSAGE 1148 (PTNZTM) 1148.1 UN ABLE TO WRITE EXTENDED TRAILER FOR FILE %1 *** SYSTEM FATAL MESSAGE 1150 (XRSLTU) 1150.0 END OF FILE ENCOUNTERED WHILE DOING CONDITIONAL JUMP

105 FROM COND, DMAP STATEMENT NUMBER IS %1 USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 1151 (XCEI) 1151.0 ERROR DELETING SCRATCH FILE %1 AT TOP OF DMAP LOOP *** USER WARNING MESSAGE 1152 (XCLNUP) 1152.0 SOME DBSETS IN THIS DATA BASE WERE NOT INITIALIZED COMPLETELY. USER INFORMATION: THE DATA BASE CREATED IN THIS RUN IS TOO IMMATURE TO BE RESTARTED. USER ACTION: DELETE THIS DATA BASE BEFORE STARTING YOUR NEXT RUN. *** USER WARNING MESSAGE 1153 (XCLNUP) 1153.0 THE NDDL FOR THIS DATA BASE HAS NEITHER BEEN CREATED NOR OBTAINED FROM THE DELIVERY DATA BASE. USER INFORMATION: THE DATA BASE CREATED IN THIS RUN IS TOO IMMATURE TO BE RESTARTED. USER ACTION: DELETE THIS DATA BASE BEFORE STARTING YOUR NEXT RUN. *** SYSTEM FATAL MESSAGE 1155 (XCLOAD) 1155.0 FILPOS POINTER TO DBDIR (DBEN TRY) TABLE = 0 USER ACTION: SEND RUN TO SIEMENS PLM SOFTWARE CUSTOMER SUPPORT, WITH DATA BASE DIRECTORY PRINT PROGRAMMER ACTION: EXAMINE DBENTRY ENTRY -- DBEPTR = %1 *** SYSTEM INFORMATION MESSAGE 1156 (XCLNUP) 1156.0 GINO FILE %1 WAS LEFT OPEN AT PROGRAM TERMINATION. *** USER FATAL MESSAGE 1157 (XDRMGR) 1157.0 THE %1 DATA BASE CONTAINS INVALID OR NULL MASTER DIRECTORIES(NDDL). USER INFORMATION: THE NDDL FOR THIS DATA BASE HAS NEITHER BEEN CREATED NOR OBTAINED FROM THE DELIVERY DATA BASE. THE DATA BASE ATTACHED TO THIS RUN IS TOO IMMATURE TO BE RESTARTED. USER ACTION: DELETE THIS DATA BASE AND RESUBMIT ITS DATA BASE INITIALIZATION RUN. *** SYSTEM FATAL MESSAGE 1158 (XRETUR) 1158.0 UNEXPECTED END OF FIL E ENCOUNTERED WHILE POSITIONING BACK TO CALLING SUBDMAP %1 *** SYSTEM FATAL MESSAGE 1159 (XRETUR) 1159.0 THE "MAIN" SUBDMAP %1 CANNOT HAVE A "RETURN" STATEMENT

106 *** SYSTEM FATAL MESSAGE 1160 (XSTORE) 1160.0 - OF OSCAR FILE MUST BE INCORRECTLY POSITIONED SINCE END - FILE ENCOUNTERED USER ACTION: SEND RUN TO SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER ACTION: CHECK LOGIC IN ROUTINE XSEM. *** SYSTEM FATAL MESSAGE 1160 (XRSLTU) 1160.1 BE INCORRECTLY POSITIONED SINCE END - OF - OSCAR FILE MUST FILE ENCOUNTERED USER ACTION: SEND RUN TO SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER ACTION: CHECK LOGIC IN ROUTINE XRSLTU. *** SYSTEM FATAL MESSAGE 1160 (XCEI) 1160.2 OSCAR FILE MUST BE INCORRECTLY POSITIONED SINCE END - OF - FILE ENCOUNTERED USER ACTION: SEND RUN TO SIEMENS PLM SOFTWARE CUSTOMER SUPPORT PROGRAMMER ACTION: CHECK LOGIC IN ROUTINE XCEI. *** SYSTEM FATAL MESSAGE 1161 (XSTORE) 1161.0 THE PREALLOCATED SPACE FOR DBDIR RECORDS IS INSUFFICIENT USER ACTION: SEND THIS RUN TO SIEMENS PLM SOFTWARE CUSTOMER SUPPORT PROGRAMMER ACTION: INCREASE THE APPROPRIATE FIXED BUFFER SIZE *** SYSTEM FATAL MESSAGE 1162 (XSTORE) 1162.0 CODING LOGIC ERROR ,TYPE VARIA BLE = %1 IS INVALID IN CALLS TO XSTORE *** SYSTEM INFORMATIONAL MESSAGE 1163 (XSTVPS) 1163.0 AN ATTEMPT WAS MADE TO UPDATE AN UNKNOWN LOCAL VPS ENTRY %1 *** SYSTEM INFORMATIONAL MESSAGE 1164 (XSTVPS) 1164.0 AN ATTEMPT WAS MADE TO UPDATE THE LOCAL VPS ENTRY %1, WHOSE VALUE IS STORED ON THE DATA BASE *** SYSTEM FATAL MESSAGE 1165 (XSTVPS) 1165.0 AN ATTEMPT WAS MADE TO UPDATE THE TYPE OF THE LOCAL VPS ENTRY %1 FROM TYPE %2 TO TYPE %3 *** SYSTEM INFORMATIONAL MESSAGE 1166 (XSTVPS) 1166.0 AN UPDATE TO THE CHARACTER ENTRY %1 IN THE LOCAL VPS WAS TRUNCATED FROM %2 WORDS TO %3 WORDS *** SYSTEM FATAL MESSAGE 1167 (XSUBLD) 1167.0 THE DUMMY RECORD IS MISSING FROM THE OSCAR FILE %1 *** SYSTEM FATAL MESSAGE 1168 (DBOLD) 1168.0

107 THE NUMBER OF ENTRIES IN THE EXECUTIVE TABLE HAS BEEN EXCEEDED. USER ACTION: 1) ADD THE FOLLOWING KEYWORD TO THE %1 STATEMENT: SYSTEM(162)=%2 2) OR REDUCE NUMBER OF SUBDMAPS IN THIS RUN. *** SYSTEM FATAL MESSAGE 1169 (XSTVPS) 1169.0 AN ATTEMPT WAS MADE TO UPDATE THE LENGTH OF THE LOCAL VPS ENTRY %1 OF TYPE %2 FROM %3 TO %4 WORDS *** SYSTEM INFORMATIONAL MESSAGE 1170 (XSTVPS) 1170.0 AN UPDATE TO THE CHARACTER ENTRY %1 IN THE LOCAL VPS - FILLED FROM WORD %2 FOR %3 WORDS WAS BLANK *** SYSTEM FATAL MESSAGE 1171 (XSUBLD) 1171.0 UNEXPECTED END OF RECORD FOUND ON THE FIRST RECORD OF THE OSCAR FILE = %1 USER INFORMATION: THIS IS PROBA BLY NOT AN OSCAR DATA BLOCK USER ACTION: SEND RUN TO SIEMENS PLM SOFTWARE CUSTOMER SUPPORT PROGRAMMER ACTION: EXAMINE THE FOLLOWING DUMP OF THE OSCAR FILE *** USER INFORMATION MESSAGE 1173 (DBCLPR) 1173.0 VERSION %1 OF PROJECT '%2' HAS BEEN DELETED FROM THE PRIMARY DATA BASE. THE CREATION DATE OF THIS VERSION IS %3/%4/%5 %6:%7.%8 *** USER WARNING MESSAGE 1174 (DBCLPR) 1174.0 THE VERSION ID = %1 OF PROJECT '%2' ON THE DBCLEAN CARD HAS NEVER BEEN CRE ATED. USER INFORMATION: THIS DBCLEAN CARD IS IGNORED. *** USER WARNING MESSAGE 1174 (DBCLPR) 1174.1 THE VERSION ID = %1 OF PROJECT '%2' ON THE DBCLEAN CARD HAS ALREADY BEEN DELETED. USER INFORMATION: THIS DBCLEAN CARD IS IGNORED. *** USER FATAL MESSAGE 1175 (COPY1) 1175.0 THE DBSET OF THE OUTPUT DATABLOCK HAS A BUFFSIZE LESS THEN THE DBSET OF THE INPUT DATABLOCK USER INFORMATION: THE DBSET OF THE INPUT DATABLOCK HAS BUFFSIZE OF %1 THE DBSET OF THE OUTPUT DATABLOCK HAS BUFFSIZE OF %2 *** SYSTEM FATAL MESSAGE 1175 (COPY1) 1175.1 THE DBSET OF THE OUTPUT DATABLOCK %1 (%2) HAS A NBUFF2 NOT EQUAL TO THE DBSET OF THE INPUT DATABLOCK %3 (%4). SYSTEM INFORMATION: THE DBSET OF THE INPUT DATABLOCK HAS AN NBUFF2 OF %5

108 THE DBSET OF THE OUTPUT DATABLOCK HAS AN NBUFF2 OF %6 *** SYSTEM FATAL MESSAGE 1175 (COPY1) 1175.2 THE DBSET OF THE OUTPUT DATABLOCK %1 (%2) HAS A NBUFF2 LESS THAN THE DBSET OF THE INPUT DATABLOCK %3 (%4). SYSTEM INFORMATION: THE DBSET OF THE INPUT DATABLOCK HAS AN NBUFF2 OF %5 THE DBSET OF THE OUTPUT DATABLOCK HAS AN NBUFF2 OF %6 *** SYSTEM WARNING MESSAGE 1176 (DIRPT3) 1176.0 NOT ENOUGH SPACE AVAILABLE TO PRINT ENTIRE PATH VALUE TABLE. PRINT WILL NOT INCLUDE PATH VAL UES. *** SYSTEM WARNING (TEMPORARY) MESSAGE 1177 (DIRPT3) 1177.0 SPILL LOGIC NOT YET INCORPORATED INTO THIS MODULE, AND DATA WILL NOT FIT IN OPEN CORE. DBDIR ABORTED. *** SYSTEM FATAL (TEMPORARY) MESSAGE 1178 (GNDIR) 1178.0 DURING A DATABLOCK ALLOCATION THE DATA BASE DIRECTORY (DBDIR) HAS OVERFLOWED. USER ACTIONS: 1. DELETE ANY UNWANTED FILES FROM THE DBSET THIS DATABLOCK IS ON (VIA DBCLEAN FMS COMMAND) AND RE RUN. - 2. CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. MER INFORMATION: PROGRAM 1. DATA BLOCK BEING ALLOCATED IS %1 2. XFIST # OF DBDIR IS %2 *** USER INFORMATION MESSAGE 1179 (RESDBS) 1179.0 - DIRECTORY IMPROPERLY CLOSED IN THE PREVIOUS RUN IS A DB BEING RESTORED BY THIS RUN. *** SYSTEM FATAL ME SSAGE 1180 (DBCLN) 1180.0 LOGIC ERROR IN DATA BASE CLEANUP ROUTINE PROGRAMMER INFORMATION: VARIABLE DBUPTR (THE 10TH ENTRY OF THE DBTEMP ARRAY) INDICATES NO NEW OUTPUT DBDIR ENTRY WAS GENERATED FOR DATA BLOCK %1 ALL OUTPUT OR SCRATCH (300 SERIES) DATA BLOCKS MUST HAVE A NON - ZERO DBUPTR VALUE -- USER ACTION: RERUN WITH DIAG 44 AND THEN SEND RUN TO SIEMENS PLM SOFTWARE CUSTOMER SUPPORT *** SYSTEM FATAL MESSAGE 1181 (GPUTTS) 1181.0 ERROR WRITING THE TIME STAMP TO THE DBSET %1 USER INFORMATION: THE CORRESPONDING PHYSICAL FILE IS: %2 *** SYSTEM FATAL MESSAGE 1181 (GGETTS) 1181.1 ERROR READING THE TIME STAMP FROM THE DBSET %1 USER INFORMATION: THE CORRESPONDING PHYSICAL FILE IS: %2

109 SYSTEM FATAL MESSAGE 1182 (GPUTTS) *** 1182.0 THE BIT MAP SHOWS CLUSTER FOR TIME STAMP IS ALREADY IN USE. *** SYSTEM WARNING MESSAGE 1183 (BPRITE) 1183.0 FILE REQUESTED HAS NOT BEEN PREVIOUSLY OPENED PROGRAMMER INFORMATION: REFNUM = %1 FILEX = %2 BPUNRF=%3 *** SYSTEM WARNING MESSAGE 1183 (BPREWI) 1183.1 FILE REQUESTED HAS NOT BEEN PREVIOUSLY OPENED PROGRAMMER INFORMATION: REFNUM = %1 *** SYSTEM FATAL MESSAGE 1183 (BPREAD) 1183.2 FILE REQUESTED HAS NOT BEEN PREVIOUSLY OPENED MATION: REFNUM = %1 FILEX = %2 PROGRAMMER INFOR BPUNRF=%3 *** SYSTEM WARNING MESSAGE 1183 (BPCLOS) 1183.3 FILE REQUESTED HAS NOT BEEN PREVIOUSLY OPENED PROGRAMMER INFORMATION: REFNUM = %1. FILEX = %2. NAM=%3 TOP=%4 BOT=%5 CUR=%6 *** SYSTEM WARNING MESSAGE 1183 (BPBACK) 1183.4 FILE REQUESTED HAS NOT BEEN PREVIOUSLY OPENED PROGRAMMER INFORMATION: REFNUM = %1 *** SYSTEM WARNING MESSAGE 1184 (BPREWI) 1184.0 REWIND FILE WAS OPENED FOR WRITE PROGRAMMER INFORMATION: REFNUM = %1 NAM = %2 TOP = %3 BOT = %4 CUR = %5 *** SYSTEM WARNING MESSAGE 1184 (BPBACK) 1184.1 BACKSPACE FILE WAS OPENED FOR WRITE PROGRAMMER INFORMATION: REFNUM = %1 NAM = %2 TOP = %3 BOT = %4 CUR = %5 *** SYSTEM FATAL MESSAGE 1185 (ADDPAT) 1185.0 THE PATH VALUE TABLE HAS GROWN TOO LARGE FOR ITS CURRENT LIMITS. USER ACTION: INCREASE MASTER(RAM) SIZE ON THE INIT MASTER COMMAND TO INCREASE THE SIZE OF THE TABLE. *** SYSTEM FATAL MESSAGE 1186 1186.0 THE DBDIR CLUSTER PONTER RECORD LENGTH HAS B EEN EXCEEDED AND IS NOT EXPANDABLE. USER ACTION: DELETE DATA BLOCKS WHICH ARE NOT NEEDED ON THE DATABASE WITH THE DELETE DMAP MODULE, OR DELETE ENTIRE VERSIONS WITH THE DBCLEAN FILE MANAGEMENT COMMAND. System information: Currently, a DB Directories cl uster pointer record is unexpandable.

110 If it has filled up, the user must delete data blocks for the cluster pointer record in order to proceed writing to his database. This has been observed when the maximum number of superelements has been exceeded. *** USER INFORMATION MESSAGE 1187 (XRETUR) 1187.0 RETURNING TO SUBDMAP %1 WHICH WAS RECURSIVELY CALLED *** USER FATAL MESSAGE 1188 (GALLEX) 1188.0 DBSET %1 DOES NOT HAVE %2 CONTIGUOUS BLOCKS TO EXPAND THIS DBSET DIRECTORY USER ACTION: 1. USE FILE MANAGEMENT COMMAND "INIT" FOR A TEMPORARY (SCRATCH) DBSET. 2. USE FILE MANAGEMENT COMMAND "EXPAND" FOR A PERMANENT DBSET. User information: A number of contiguous blocks need to be allocated for an expansion of a DBSET directory. The BIT - MAP is s earched for available bits and it cannot find the requested bits. *** SYSTEM FATAL MESSAGE 1189 (GALLOC) 1189.0 THE SIZE DATA BLOCK %1 ON DBSET %2 HAS EXCEEDED THE NX NASTRAN LIMIT OF 65535 GINO BLOCKS. USER ACTION: 1. REDUCE THE SIZE OF THE MODE L OR DIVIDE THE MODEL INTO (MORE) SUPERELEMENTS, OR 2. CREATE A NEW DATA BASE WITH A LARGER BUFFSIZE FOR THE DBSET, OR 3. CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT FOR OTHER POSSIBLE AVOIDANCES. *** SYSTEM INFORMATION MESSAGE 1190 (NUMCPU) 1190.0 NUMBER OF PROCESSORS REQUESTED=%1, NUMBER OF PROCESSORS AVAILABLE=%2 System information: This is issued if the number of parallel processors specified on the NASTRAN PARALLEL statement exceeds the number availab le. *32* SYSTEM INFORMATION MESSAGE 1191 (XSTORE) 1191.0 THE EXECUTIVE SYSTEM WORK AREA WILL BE INCREASED BY %1 WORDS DUE TO AN OVERFLOW OF TABLE TYPE = %2 *32* *** SYSTEM FATAL MESSAGE 1192 (LDUSAV) 1192.0 THE SAVENT TABLE SIZE HAS BEEN EXCEEDED FOR %1 %2. *** USER INFORMATION: THE TABLE SIZE IS EQUAL TO %3 WORDS PARTITIONED FROM THE AVAILABLE OPENCORE SPACE. *** USER ACTION: INCREASE HICORE SIZE AND RERUN JOB. *** SYSTEM FATAL MESSAGE 1192 (LCXSIZ) 1192.1

111 THE DIRECTORY TABLES SIZE HAS BEEN EXCEEDED. USER INFORMATION: INCREASE HICORE SIZE AND RERUN JOB. PROGRAMMER INFORMATION: IDBSNO %1 NZ %2 BUF1 %3 DIRSIZ %4 *** SYSTEM FATAL MESSAGE 1192 (LCXLOD) 1192.2 THE D IRECTORY TABLES SIZE HAS BEEN EXCEEDED. USER INFORMATION: INCREASE HICORE SIZE AND RERUN JOB. PROGRAMMER INFORMATION: IDBSNO%1 MXDLEN%2 BUF1%3 STARTZ%4 LENDIR%5 NZ%6 XPTRS%7 %8 %9 *** SYSTEM FATAL MESSAGE 1192 (CKEQUV) 1192.3 THE EQUIVALENCE CORRESPONDENCE TABLE SIZE HAS BEEN EXCEEDED. *** USER INFORMATION: THE TABLE SIZE IS EQUAL TO %1 WORDS PARTITIONED FROM THE AVAILABLE OPENCORE SPACE. *** USER ACTION: INCREASE HICORE SIZE AND RERUN JOB. *** SYSTEM FATAL ME SSAGE 1192 (XINSBL) 1192.4 THE NDDL RECORDS LENGTH TABLE SIZE HAS BEEN EXCEEDED. PROGRAMMER INFORMATION: THE TABLE SIZE IS EQUAL TO %1 WORDS PARTITIONED FROM THE AVAILABLE OPENCORE SPACE. *** USER WARNING MESSAGE 1193 (UNLDRF) 1193.0 THE FORMAT ON THE A SSIGN,DBUNLOAD STATEMENT IS INCOMPATIBLE WITH THE FORM ON THE DBUNLOAD STATEMENT FOR UNIT %1 *** USER INFORMATION: 1. FORMAT ON ASSIGN IS %2 2. FORM ON DBUNLOAD IS %3 3. DBUNLOAD FORM DEFAULTS ARE SET FOR THIS UNIT RECL = %4 FORMAT = %5 *** USER WARNING MESSAGE 1193 (LDLDRF) 1193.1 THE FORMAT ON THE ASSIGN,DBLOAD STATEMENT IS INCOMPATIBLE WITH THE FORM ON THE DBLOAD STATEMENT FOR UNIT %1 *** USER INFORMATION: 1. FORMAT ON ASSIGN IS %2 2. FORM ON DBLOAD IS %3 3. DBLOAD FORM DEFAULTS ARE SET FOR THIS UNIT RECL = %4 FORMAT = %5

112 *** SYSTEM FATAL MESSAGE 1194 (UNLIFU) 1194.0 OVERFLOW OF DBUNLOAD FORTRAN UNIT ARRAY *** USER ACTION: REDUCE THE NUMBER OF FORTRAN UNITS SPECIFIED IN DBUNLOAD STATEMENTS *** USER INFORMATION: THE MAXIMUM NUMB ER OF FORTRAN UNITS THAT CAN BE SPECIFIED ON DBUNLOAD STATEMENTS IS %1 *** USER FATAL MESSAGE 1195 (UNLODR) 1195.0 INVALID VALUE SPECIFIED FOR FORM KEYWORD ON DBUNLOAD STATEMENT *** SYSTEM FATAL MESSAGE 1200 (UNDRVR) 1200.0 AN ERROR HAS OCCURRED WHILE ATTEMPTING TO READ A DBUNLOAD HEADER RECORD FROM THE FMS CONTROL FILE. *** PROGRAMMER INFORMATION: ERROR FLAG FROM FMSGEH = %1. *** SYSTEM FATAL MESSAGE 1200 (LDDRVR) 1200.1 AN ERROR HAS OCCURRED WHILE ATTEMPTING TO RE AD A DBLOAD HEADER RECORD FROM THE FMS CONTROL FILE. *** PROGRAMMER INFORMATION: ERROR FLAG FROM FMSGEH = %1. *** SYSTEM FATAL MESSAGE 1200 (DBDICT) 1200.2 AN ERROR HAS OCCURRED WHILE ATTEMPTING TO READ A DBDICT HEADER RECORD FROM THE FMS CONTROL FILE. *** PROGRAMMER INFORMATION: ERROR FLAG FROM FMSGEH = %1. *** SYSTEM FATAL MESSAGE 1201 (UNDRVR) 1201.0 AN ERROR HAS OCCURRED WHILE ATTEMPTING TO READ ONE OR MORE DBUNLOAD DATA RECORDS FROM THE FMS CONTROL FILE. *** PROGRAMMER INFORMATION: 1. ERROR FLAG 1 FROM FMSGEI = %1. 2. ERROR FLAG 2 FROM FMSGEI = %2. 3. ERROR FLAG 3 FROM FMSGEI = %3. 4. ERROR FLAG 4 FROM FMSGEC = %4. 5. ERROR FLAG 5 FROM FMSGEC = %5. *** SYSTEM FATAL MESSAGE 1201 (LDDRVR) 1201.1 AN ERROR HAS OCCURRED WHIL E ATTEMPTING TO READ ONE OR MORE DBLOAD DATA RECORDS FROM THE FMS CONTROL FILE. *** PROGRAMMER INFORMATION: 1. ERROR FLAG 1 FROM FMSGEI = %1. 2. ERROR FLAG 2 FROM FMSGEI = %2. 3. ERROR FLAG 3 FROM FMSGEI = %3. 4. ERROR FLAG 4 FROM FMSGEC = %4.

113 5. ERR OR FLAG 5 FROM FMSGEC = %5. *** SYSTEM FATAL MESSAGE 1201 (LCDRVR) 1201.2 AN ERROR HAS OCCURRED WHILE ATTEMPTING TO READ ONE OR MORE DBLOCATE DATA RECORDS FROM THE FMS CONTROL FILE. *** PROGRAMMER INFORMATION: 1. HEDTYP FROM FMSGEH = %1. 2. ERRO R FLAG 0 FROM FMSREW = %2. 3. ERROR FLAG 1 FROM FMSGEH = %3. 4. ERROR FLAG 2 FROM FMSGEI = %4. 5. ERROR FLAG 3 FROM FMSGEI = %5. 6. ERROR FLAG 4 FROM FMSGEI = %6. 7. ERROR FLAG 5 FROM FMSGEC = %7. 8. ERROR FLAG 6 FROM FMSGEC = %8. *** SYSTEM FATAL MESSAGE 1202 (UNDRVR) 1202.0 AN ERROR HAS OCCURRED WHILE ATTEMPTING TO REWIND THE FMS CONTROL FILE. *** PROGRAMMER INFORMATION: ERROR FLAG FROM FMSREW = %1. *** USER WARNING MESSAGE 1203 (UNDRVR) 1203.0 THE CONVERT CLAUSE IS NOT SUPPORTED BY THE DBUNLOAD STATEMENT. THE CONVERT CLAUSE SPECIFIED WILL BE IGNORED. SPECIFIED CONVERT CLAUSE WAS: *** SYSTEM WARNING MESSAGE 1204 (UNRTN) 1204.0 ABSOLUTE VALUE OF SINGLE PRECISION VALUE IS %1 THAN THE %2 FILTER OF %3, AND WILL BE RESET TO THE CORRECTLY SIGNED FILTER VALUE *** SYSTEM WARNING MESSAGE 1204 (UNMTND) 1204.1 ABSOLUTE VALUE OF DOUBLE PRECISION VALUE IS %1 THAN THE %2 FILTER OF %3, AND WILL BE RESET TO THE CORRECTLY SIGNED FILTER VALUE **** SYSTEM INFORMATION MESSAGE 1205 (UNEND) 1205.0 %1 ERRORS OCCURRED DURING TRANSMISSION PROCESS *** USER INFORMATION MESSAGE 1206 1206.0 THE DATABLOCK %1 IN A DBUNLOAD REQUEST IS NOT DEFINED IN THE NX NASTRAN DATA DEFINITION LANGUAGE (NDDL) THIS DATA BLOCK WILL NOT BE TRANSLATED TO NEUTRAL FORMAT *** USER INFORMATION MESSAGE 1206 1206.1 THE DATABLOCK %1 IN A DBUNLOAD REQUEST IS NOT DEFINED IN THE NX NASTRAN DATA DEFINITION LANGUAGE (NDDL) THIS DATABLOCK WILL NOT BE BYTE SWAPPED

114 *** USER INFORMATION MESSAGE 1206 (OUTPBN2) 1206.2 THE DATABLOCK %1/%2 IN AN OUTPUT2 REQUEST IS NOT DEFINED IN THE NX NASTRAN DATA DEFINITION LANGUAGE (NDDL) THIS DATABLOCK WILL NOT BE TRANSLATED TO ILP32/LP64 FORMAT OR BYTE SWAPPED USER INFORMATION MESSAGE 1206 (OUTPN2) *** 1206.4 THE DATABLOCK %1/%2 IN AN OUTPUT2 REQUEST IS NOT DEFINED IN THE NX NASTRAN DATA DEFINITION LANGUAGE (NDDL) THIS DATABLOCK WILL NOT BE TRANSLATED TO NEUTRAL FORMAT *** USER FATAL MESSAGE 1206 (OUTPT2) 1206.5 BYTE SWAPPING ON LONG WORD MACHINES IS SUPPORTED - BIT OUTPUT2 FILE. ONLY WHILE WRITING A 32 PLEASE SUBMIT THE DECK AGAIN WITH PARAM,OP2FMT,32 TO GENERATE A BYTE SWAPPED 32 - BIT OUTPUT2 FILE. *** USER FATAL MESSAGE 1206 (OUTPT4) 1206.6 BYTE SWAPPING ON LONG WORD MACHINES IS SUPPORTED - BIT OUTPUT4 FILE. ONLY WHILE WRITING A 32 PLEASE SUBMIT THE DECK AGAIN WITH PARAM,OP4FMT,32 TO GENERATE A BYTE SWAPPED 32 - BIT OUTPUT4 FILE. *** USER FATAL MESSAGE 1206 (INPTT4) 1206.7 BYTE SWAPPING ON LONG WORD MACHINES IS SUPPORTED ONLY WHILE READING A 32 BIT OUTPUT4 FILE. - PLEASE SUBMIT THE DECK AGAIN WITH PARAM,INP4FMT,32 TO READ IN A BYTE SWAPPED 32 BIT OUTPUT4 FILE. - *** USER INFORMATION MESSAGE 1206 (RDDATABLK) 1206.8 ATABLOCK %1/%2 IN AN INPUTT2 REQUEST IS NOT THE D DEFINED IN THE NX NASTRAN DATA DEFINITION LANGUAGE (NDDL) THIS DATABLOCK WILL NOT BE TRANSLATED INTO ILP64 FORMAT OR BYTE SWAPPED *** USER INFORMATION MESSAGE 1207 (UNLNEU) 1207.0 THE DATABLOCK %1 DEFINE D AS NDDL TYPE %2 IS NOT SUPPORTED BY NEUTRAL FILE TRANSLATION. THIS DATABLOCK WILL NOT BE TRANSLATED TO NEUTRAL FORMAT. *** USER INFORMATION MESSAGE 1207 (OUTPN2) 1207.1 THE DATABLOCK %1/%2 DEFINED AS NDDL TYPE %3 IS NOT SUPPORTED BY NEUTRAL FILE TRANSLATION. THIS DATABLOCK WILL NOT BE TRANSLATED TO NEUTRAL FORMAT *** USER INFORMATION MESSAGE 1207 (OUTPN2) 1207.2

115 THE DATABLOCK %1/%2 DEFINED AS NDDL TYPE %3 IS NOT SUPPORTED BY BYTE SWAPPING. THIS DATABLOCK WILL NOT BE BYTE SWAPPED *** USER INFORMATION MESSAGE 1207 (RDDATABLK) 07.3 12 THE DATABLOCK %1/%2 DEFINED AS NDDL TYPE %3 IS NOT SUPPORTED FOR INPUTT2 CONVERSION (LP64 TO ILP64 OR FOR BYTE SWAPPING). THIS DATABLOCK WILL NOT BE READ INTO NASTRAN *** SYSTEM FATAL MESSAGE 1208 (UNSTR) 1208.0 ERROR SETTING UP TRANSLATE TABLE AT LOC = %1 *** SYSTEM FATAL MESSAGE 1209 (LDPARM) 1209.0 INSUFFICIENT OPENCORE SPACE AVAILABLE TO LOAD SAVENT ARRAY FOR PARAMETER %1. USER ACTION: INCREASE OPENCORE USER INFORMA TION: 1. THE SAVENT ARRAY USES 15 PERCENT OF AVAILABLE OPENCORE, OR %2 WORDS IN THIS RUN. 2. THIS SAVENT ARRAY CONTAINS %3 WORDS. *** SYSTEM FATAL MESSAGE 1209 (LDDBLK) 1209.1 INSUFFICIENT OPENCORE SPACE AVAILABLE TO LOAD SAVENT ARRAY FOR DATABLO CK %1. USER ACTION: INCREASE OPENCORE USER INFORMATION: 1. THE SAVENT ARRAY USES 15 PERCENT OF AVAILABLE OPENCORE, OR %2 WORDS IN THIS RUN. 2. THIS SAVENT ARRAY CONTAINS %3 WORDS. *** SYSTEM FATAL MESSAGE 1210 (LDPARM) 1210.0 THE PRIMARY QUALIFIER TABLE SIZE HAS BEEN EXCEEDED FOR PARAMETER %1 USER INFORMATION: THE MAXIMUM PRIMARY QUALIFIER TABLE SIZE IS %2 WORDS. USER ACTION: 1. DECREASE NUMBER OF QUALIFIERS FOR PARAMETER AND RERUN JOB 2. NOTIFY SIEMENS PLM SOFTWARE CUSTOM ER SUPPORT *** SYSTEM FATAL MESSAGE 1210 (LDDBLK) 1210.1 THE PRIMARY QUALIFIER TABLE SIZE HAS BEEN EXCEEDED FOR DATABLOCK %1 USER INFORMATION: THE MAXIMUM PRIMARY QUALIFIER TABLE SIZE IS %2 WORDS. USER ACTION: 1. DECREASE NUMBER OF QUALIFIERS F OR DATABLOCK AND RERUN JOB 2. NOTIFY SIEMENS PLM SOFTWARE CUSTOMER SUPPORT

116 *** SYSTEM FATAL MESSAGE 1211 (LDDRVR) 1211.0 AN ERROR WAS DETECTED IN THE SUBROUTINE LDLENT WHEN ATTEMPTING TO LOAD A DATABLOCK OR PARAMETER TO THE DATABASE RMATION: *** USER INFO THE REMAINING INPUT FILE WILL NOT BE PROCESSED *** SYSTEM FATAL MESSAGE 1212 (LDINPT) 1212.0 INVALID DATABLOCK TRAILER DETECTED FOR %1 DURING DBLOAD NEUTRAL FILE PROCESSING. *** USER INFORMATION: 1. DATABLOCK TRAILERS CONSIST OF%2 WORDS. 2. THIS TRAILER CONTAINS %3 WORDS. *** SYSTEM FATAL MESSAGE 1213 (LDPHDR) 1213.0 HEADER RECORD MISSING ON NEUTRAL FILE ATTACHED TO UNIT%1 *** SYSTEM INFORMATION MESSAGE 1214 (LDRTRN) 1214.0 ERROR T RANSLATING DATA FROM NEUTRAL FILE READ FOR SUBROUTINE %1. CHARACTER = A POSITION IS LINE %2 CHARACTER %3 *** USER FATAL MESSAGE 1215 (CKRVER) 1215.0 THE PRIMARY DATABASE IS INCOMPATIBLE WITH THIS VERSION OF THE PROGRAM. USER INFORMATION: PRIMARY DATABASE VERSION IS %1 PROGRAM VERSION IS %2 USER ACTIONS: 1. CONVERT THE PRIMARY DATABASE USING THE SIEMENS PLM SOFTWARE CUSTOMER SUPPORT MIGRATION TOOLS. 2. OR, SET SYSTEM CELL 148 ON %3 STATEMENT TO IGNORE THIS INCOMPATIBILITY, E.G., STEM(148)=1". HOWEVER, IGNORING THIS "%4 SY INCOMPATIBILITY MAY LEAD TO UNPREDICTABLE RESULTS. *** SYSTEM INFORMATION MESSAGE 1216 (LDDBLK) 1216.0 THE DATABLOCK %1 CLASSIFIED AS NDDL - TYPE %2 CANNOT BE LOADED TO THIS DATABASE BECAUSE THE PROGRAM BUFFER SIZ ES ARE INCOMPATIBLE UNLOAD BUFFER SIZE: %3 LOAD BUFFER SIZE: %4 *** SYSTEM INFORMATION MESSAGE 1216 (LDDBLK) 1216.1 THE DATABLOCK %1 CLASSIFIED AS NDDL - TYPE %2 CANNOT BE LOADED TO THIS DATABASE BECAUSE THE MACHINE TYPES ARE INCOMPATIBLE UNLOAD MACHINE TYPE: %3

117 LOAD MACHINE TYPE: %4 *** USER FATAL MESSAGE 1217 (LCDEFC) 1217.0 VERSION IS NOT SPECIFIED IN CONVERT CLAUSE. CONTENTS OF CONVERT CLAUSE: %1 USER ACTION: SPECIFY PROJECT AND VERSION. User information: If either PROJECT or VERSION is specified then both must be specified. *** USER FATAL MESSAGE 1218 (VWDRVR) 1218.0 RUN IS TERMINATED DUE TO ABOVE ERROR(S) IN DBVIEW STATEMENT. *** USER FATAL MESSAGE 1218 (LCDRVR) 1218.1 RUN IS TERMINATED DUE TO ABOVE ERRORS IN DBLOCATE. *** USER FATAL MESSAGE 1219 (LCLENT) 1219.0 AN ATTEMPT TO OVERWRITE THE EXISTING DATABLOCK/PARAMETER %1 WITH %2 WAS MADE BUT THE NOOVRWRT KEYWORD IS SPECIFIED. PROGRAMMER INFORMATION: PATH - POINTER %3 DBENTRY POINTER%4 *** USER INFORMATION MESSAGE 1220 (LCLPJV) 1220.0 %1 IS CREATING - ID=%2 OF V E R S I O N P R O J E C T ID="%3" (PROJECT - NO=%4) IN THE PRIMARY - DATABASE. *** USER INFORMATION MESSAGE 1220 (LCLPJV) 1220.1 %1 IS CREATING - ID="%2" (PROJECT - NO=%3) IN THE PRIMARY P R O J E C T DATABASE. *** USER INFORMATION MESSAGE 1220 (LCLPJV) 1220.2 %1 IS RECREATING - ID=%2 OF V E R S I O N P R O J E C T - ID="%3" (PROJECT - NO=%4) IN THE PRIMARY DATABASE. *** USER INFORMATION MESSAGE 1221 1.0 122 - THE PARTITION OF THE SCRATCH DBSET USED FOR DMAP SCRATCH DATABLOCKS IS FULL. USER INFORMATION: THE DMAP - SCRATCH PARTITION WILL NOW SPILL INTO THE 300 - SCRATCH PARTITION BECAUSE NASTRAN SYSTEM(151)=1. *** USER FATAL MESSAGE 1221 (GALLOX) 1221.1 THE PARTITION OF THE SCRATCH DBSET USED FOR DMAP - SCRATCH DATABLOCKS IS FULL. USER INFORMATION: THE DMAP SCRATCH PARTITION WILL NOT

118 SPILL INTO THE 300 - SCRATCH PARTITION. USER ACTION: 1. SET NASTRAN SYSTEM(151)=1, OR 2. INCREASE THE NUMBER OF MEMBERS, AND/OR THEIR MAXIMUM SIZE, FOR THE SCRATCH DBSET ON THE "INIT" STATEMENT. *** USER INFORMATION MESSAGE 1221 (GALLOC) 1221.2 SCRATCH THE PARTITION OF THE SCRATCH DBSET USED FOR 300 - FILES IS FULL. USER INFORMATION: THE 300 - SCRATCH PARTITION WILL NOW - SPILL INTO THE DMAP SCRATCH PARTITION. *** SYSTEM FATAL MESSAGE 1222 (LDRTRN) 1222.0 AN UNEXPECTED END OF FILE WAS DETECTED ON A NEUTRAL FILE DURING A DBLOAD OPERATION USER INFORMATION: OGRAM EXECUTION AND THIS ERROR TERMINATES PR GENERALLY OCCURS WHEN THE DBUNLOAD JOB FAILS DURING NEUTRAL FILE CREATION USER ACTION: REVIEW NEUTRAL FILE CREATION JOB FOR FATAL MESSAGES *** SYSTEM FATAL MESSAGE 1222 (INPTT4) 1222.1 AN UNEXPECTED END OF FILE WAS DETECTED ON %1 INPUTT4 FILE ON UNIT %2 USER INFORMATION: THIS ERROR TERMINATES PROGRAM EXECUTION AND GENERALLY OCCURS WHEN RECORD 2 INDICATES MORE DATA THEN ACTUALLY EXISTS ON RECORD 3 USER ACTION: REVIEW DATA FILE FOR PO SSIBLE DATA DISCREPANCIES *** SYSTEM FATAL MESSAGE 1222 (INPTT4) 1222.2 THE INPUTT4 FILE BEING READ IN SEEMS TO BE A BIG ENDIAN FILE USER ACTION: READ THE FILE USING FORM=BIGENDIAN. SEE QRG FOR SYNTAX *** SYSTEM FATAL MESSAGE 1222 ( INPTT4) 1222.3 THE INPUTT4 FILE BEING READ IN SEEMS TO BE A LITTLE ENDIAN FILE USER ACTION: READ THE FILE USING FORM=LITTLEENDIAN. SEE QRG FOR SYNTAX *** USER WARNING MESSAGE 1223 (UNLDRF) 1223.0 THE RECL SPECIFIED ON THE ASSIGN STATEMENT IS %1 THAN THE %2 VALUE ALLOWED FOR NEUTRAL FILES USER INFORMATION:

119 1. THE SPECIFIED RECL OF %3 HAS BEEN RESET TO THE %4 ALLOWED RECL OF %5 2. UNIT NUMBER = %6 LOGICAL NAME = %7 FILE NAME = %8 ** * USER WARNING MESSAGE 1223 (RDASGN) 1223.1 THE %1 SPECIFIED ON THE %2 STATEMENT IS %3 THAN THE %4 VALUE ALLOWED FOR NEUTRAL FILES USER INFORMATION: 1. THE SPECIFIED RECL OF %5 HAS BEEN RESET TO THE %6 ALLOWED RECL OF %7 2. UNIT NUMBER = %8 LOGICAL NAME = %9 FILE NAME = %10 *** USER WARNING MESSAGE 1223 (OUTPN2) 1223.2 THE %1 SPECIFIED ON THE OUTPUT2 STATEMENT IS %2 THAN THE %3 VALUE ALLOWED FOR NEUTRAL FILES USER INFORMATION: 1. THE SPECIFIED RECL OF %4 HAS BEEN RESET TO THE %5 ALLOWED RECL OF %6 2. UNIT NUMBER = %7 LOGICAL NAME = %8 FILE NAME = %9 *** USER WARNING MESSAGE 1223 (LDLDRF) 1223.3 THE RECL SPECIFIED ON THE ASSIGN STATEMENT IS %1 THAN THE %2 VALUE ALLOWED FOR NEUTRAL FILES USER INFORMATION: 1. THE SPECIFIED RECL OF %3 HAS BEEN RESET TO THE %4 ALLOWED RECL OF %5 2. UNIT NUMBER = %6 LOGICAL NAME = %7 FILE NAME = %8 *** USER WARNING MESSAGE 1224 (LDLDRF) 1224.0 NO RECL WAS SPECIFIED ON THE ASSIGN,DBLOAD STATEMENT FOR UNIT %1. USER INF ORMATION: THE RECL HAS BEEN SET TO THE DEFAULT VALUE OF %2 CHARACTERS *** USER WARNING MESSAGE 1224 (LDLDRF) 1224.1 NO RECL WAS SPECIFIED ON THE ASSIGN,DBLOAD STATEMENT FOR UNIT %1. USER INFORMATION: ACTERS THE RECL HAS BEEN SET TO THE VALUE OF %2 CHAR DETECTED ON THE NEUTRAL FILE *** USER WARNING MESSAGE 1225 (LDLDRF) 1225.0 THE RECL ON THE ASSIGN,DBUNLOAD STATEMENT DIFFERS FROM THE INTERNAL RECL OF THE NEUTRAL FILE OF UNIT %1. USER INFORMATION:

120 1. THE INTERNAL RECL FROM THE NEUTRAL FILE WILL BE USED. 2. THE INTERNAL NEUTRAL FILE RECL IS %2. 3. THE ASSIGN,DBUNLOAD STATEMENT RECL IS %3. *** SYSTEM FATAL MESSAGE 1226 (DBINIT). 1226.0 THE LENGTH OF THE %1 STATEMENT HAS EXCEEDED THE OF %2 CHARACTERS. MAXIMUM USER INFORMATION: THE NUMBER OF CHARACTERS DOES NOT INCLUDE COMMENTS OR LEADING AND TRAILING BLANKS. USER ACTION: REMOVE REDUNDANT EMBEDDED BLANKS OR USE MULTIPLE %3 STATEMENTS. *** USER FATAL MESSAGE 1227 (LCDRVR) 1227.0 TABLOCK/PARAMETER NAME %1 CANNOT BE PROCESSED THE DA DUE TO ABOVE POSSIBLE SYNTAX ERROR IN THE ABOVE DBLOCATE STATEMENT. *** USER FATAL MESSAGE 1227 (DBEQIV) 1227.1 THE DATABLOCK/PARAMETER NAME %1 CANNOT BE PROCESSED DUE TO POSSIBLE SYNTAX ERROR IN THE DBEQUIV STATEMENT ABOVE. *** USER FATAL MESSAGE 1227 (DBDELE) 1227.2 THE DATABLOCK/PARAMETER NAME %1 CANNOT BE PROCESSED DUE TO POSSIBLE SYNTAX ERROR IN THE DBDELETE STATEMENT ABOVE. *** USER WARNING MESSAGE 1243, (NASLOG) 1243.0 AN ERROR OCCURRED PROCESSING SYMBOL NAMES IN THE CONTROL FILE. SYMBOL SPECIFICATION IGNORED RECORD = %1, NLOG = %2 LOG = %3 ALIAS = %4 USER ACTION: CHECK SYMBOL NAME SPECIFICATION. THE SYMBOL NAME MUST BE PRESENT. THE SYMBOL NAME CAN BE NO MORE THAN 16 CHARACTERS IN LENGTH. THE SYMBOL VALUE CAN BE NO MORE THAN %5 CHARACTERS IN LENGTH. *** USER FATAL MESSAGE 1245, (BIO) 1245.0 AN ALLOCATION ERROR HAS OCCURRED FOR A DATABASE FILE, FILX = %1. WRITE ATTEMPTED ON FILX WHICH WAS OPENED FOR READONLY. LOGICAL = %2 FILE = %3 USER ACTION: CHECK FILE ASSIGN STATEMENTS AND FILE ACCESS PRIVILEGES. *** CONTINUATION MESSAGE (SEVERITY = MCONT ( - 1)) 1246.0 BIOMSG: ERROR %1 HAS OCCURRED IN ROUTINE %2, FILE INDEX = %3.

121 - 1)) *** CONTINUATION MESSAGE (SEVERITY = MCONT ( 1246.1 LOGICAL NAME IS %1 FILENAME IS %2 *** CONTINUATION MESSAGE (SEVERITY = MCONT ( - 1)) 1246.2 STATUS = %1 *** USER FATAL MESSAGE 1247, (BIO...) 1247.0 UNABLE TO VALIDATE DATABASE FILE FORMAT. DATABASE MAY NOT HAVE BEEN BUILT ON A COMPATIBLE PLATFORM. TIMESTAMP/RECL VALIDATION FAILED. FILX = %1, LOGNAME = %2, NSBUF3 = %3 FILE IS %4 - *** CONTINUATION MESSAGE FOR 1247.0 (SEVERITY = MCONT ( 1247.1 1)) TIMESTAMP OFFSET INVALID. *** CONTINUATION MESSAGE FOR 1247.0 (SEVERITY = MCONT ( - 1247.2 1)) TIMESTAMP SIGNATURE VALIDATION FAILED. *** CONTINUATION MESSAGE FOR 1247.0 (SEVERITY - = MCONT ( 1247.3 1)) RECL VALUE NOT POSITIVE. *** CONTINUATION MESSAGE FOR 1247.0 (SEVERITY = MCONT ( - 1247.4 1)) WORK AREA ALLOCATION (FMALLC) FAILED. *** CONTINUATION MESSAGE FOR 1247.0 (SEVERITY = MCONT ( - 1247.5 1)) FILE IS EMPTY. *** CONTINUATION MESSAGE FOR 1247.0 (SEVERITY = MCONT ( - 1247.6 1)) NUMERIC FORMAT NOT COMPATIBLE WITH THIS PLATFORM. *** CONTINUATION MESSAGE FOR 1247.0 (SEVERITY = MCONT ( - 1247.7 1)) RECL SHOULD BE %1, ACTUAL VALUE IS %2. SYSTEM INFORMATION MESSAGE 1248, (BIO) *** 1248.0 - File locking suppressed. SYSTEM(207).NE.0 *** USER WARNING MESSAGE 1249, (BIO) 1249.0 STATUS = %1, FILX = %2, LOGNAME = %3, NSBUF3 = %4 FILE = %5 *** CONTINUATION MESSAGE FOR 1249.0 (SEVERITY = MCONT ( - 1249.1 1)) BLKNBR = %1 *** CONTINUATION MESSAGE FOR 1249.0 (SEVERITY = MCONT ( - 1249.2 1))

122 WARNING MESSAGE IS -- *** CONTINUATION MESSAGE FOR 1249.0 (SEVERITY = MCONT ( - 1249.3 1)) %1 *** USER FATAL MESSAGE 1250, (BIO) 1250.0 STATUS = %1, FILX = %2, LOGNAME = %3, NSBUF3 = %4 FILE = %5 *** CONTINUATION MESSAGE FOR 1250.0 (SEVERITY = MCONT ( - 1250.1 1)) BLKNBR = %1 - *** CONTINUATION MESSAGE FOR 1250.0 (SEVERITY = MCONT ( 1250.2 1)) ERROR MESSAGE IS -- - *** CONTINUATION MESSAGE FOR 1250.0 (SEVERITY = MCONT ( 1250.3 1)) %1 *** SYSTEM FATAL MESSAGE 1251, (BIO) 1251.0 FILX = %1 (%2 HEX) OUT OF RANGE *** SYSTEM FATAL MESSAGE 1254 (RPLPAT) 1254.0 CANNOT REPLACE THE EXISTING PATH. REPTR=%1 KEYNO=%2 PATCNT=%3 *** SYSTEM FATAL MESSAGE 1254 (RPLPAT) 1254.1 CANNOT REPLACE MIS - MATCHED NUMBER OF QUALIFIERS. LENGTH=%1 QUALS(1)=%2 *** SYSTEM FATAL MESSAGE 1254 (RPLPAT) 1254.2 E THE NONEXISTENT PATH. CANNOT REPLAC REPTR=%1 KEYNO=%2 *** USER WARNING MESSAGE 1255 (LCLDBS) 1255.0 THE DATABASE ASSIGNED TO LOGICAL NAME %1 IS INCOMPATIBLE WITH THIS VERSION OF THE PROGRAM. USER INFORMATION: DATABASE VERSION IS %2 PROGRAM VERSION IS %3 USER ACTIONS: IF RUN TERMINATES DUE TO THE INCOMPATIBILITY, CONVERT THE DATABASE USING THE SIEMENS PLM SOFTWARE MIGRATION TOOLS. *** USER WARNING MESSAGE 1255 (LCLDBS) 1255.1 THE DATABASE ASSIGNED TO LOGICAL NAME %1 IS INCOMPATIBLE WITH THIS VERSI ON OF THE PROGRAM. USER INFORMATION: DATABASE VERSION IS %2 PROGRAM VERSION IS %3

123 *** USER FATAL MESSAGE 1256 (ATTDBS) 1256.0 THE DELIVERY DATABASE ASSIGNED TO LOGICAL NAME %1 IS INCOMPATIBLE WITH THIS VERSION OF THE PROGRAM. USER INFORMATION: DELIVERY DATABASE VERSION IS %2 PROGRAM VERSION IS %3 USER ACTIONS: REBUILD THE DELIVERY DATABASE UNDER THE PROGRAM VERSION. *** USER FATAL MESSAGE 1257 1257.0 THE MAX - SIZE SPECIFIED ON THE INIT FMS STATEMENT FOR THE DBSET %1 IS %2 BLOCKS FIRST MEMBER OF AND IS LESS THAN THE RECOMMENDED MINIMUM OF %3 BLOCKS. - USER ACTION: SPECIFY A MAX SIZE VALUE AT OR ABOVE THE RECOMMENDED VALUE. *** USER FATAL MESSAGE 1257 1257.1 THE MAX SIZE SPECIFIED ON THE INIT FMS STATEMENT OR - SMEM VALU E IN THE RC FILE OR SMEM KEYWORD IN THE COMMAND PROCEDURE FOR THE MEMFILE OF DBSET %1 IS %2 BLOCKS AND IS LESS THAN THE RECOMMENDED MINIMUM OF %3 BLOCKS. USER ACTION: SPECIFY A MAX - SIZE OR SMEM VALUE AT OR ABOVE THE RECOMMENDED VALUE. *** USER FATAL MESSAGE 1259 (SEMTRN) 1259.0 PREPROCESSOR CONTROL VALIDATION FAILED.%1 *** USER INFORMATION: THE BULK DATA SECTION OF THE INPUT DATA HAS BEEN CHANGED OR WAS CREATED ON A DIFFERENT COMPUTER. *** SYSTEM FATAL MESSAGE 1260 (SLCDRV) 1260.0 UNABLE TO OPEN DBDIR DBSET FOR DATABLOCK %1. *** SYSTEM FATAL MESSAGE 1261 (UNLNXT) 1261.0 INSUFFICIENT LOCAL WORKING ARRAY. PROGRAMMER ACTION: INCREASE LOCAL ARRAY FIST IN UNLNXT. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 1261 (OUTPX2) 1261.1 INSUFFICIENT LOCAL WORKING ARRAY. PROGRAMMER ACTION: INCREASE LOCAL ARRAY FIST IN OUTPX2. *** SYSTEM FATAL MESSAGE 1261 (CPYFIL) 1261.2

124 INSUFFICIENT LOCAL WORKING ARRAY. PROGRAMMER ACTION: INCREASE LOCAL ARRAY FIST IN CPYFIL. *** SYSTEM FATAL MESSAGE 1261 (COPY1) 1261.3 INSUFFICIENT LOCAL WORKING ARRAY. PROGRAMMER ACTION: INCREASE LOCAL ARRAY FIST IN COPY1. *** SYSTEM FATAL MESSAGE 1262 (UNLNXT) 1262.0 ABLOCK %1 (%2) HAS ASSOCIATED FILES THAT CANNOT BE DAT RETRIEVED BY UNLNXT. *** SYSTEM FATAL MESSAGE 1262 (OUTPX2) 1262.1 DATABLOCK %1 (%2) HAS ASSOCIATED FILES THAT CANNOT BE RETRIEVED BY OUTPX2. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 1262 (LDINPT) 1262.2 DATABLOCK %1 (%2) HAS ASSOCIATED FILES THAT CANNOT BE RETRIEVED FROM THE NEUTRAL FILE. PROGRAMMER INFORMATION: %3 NAMES SHOULD BE %4 WORDS ARE STORED IN THE 2ND RECORD OF THE RETRIEVED. CURRENT DATABLOCK. *** SYSTEM FATAL MESSAGE 1262 (CPYFIL) 1262.3 DATABLOCK %1 (%2) HAS ASSOCIATED FILES THAT CANNOT BE RETRIEVED BY CPYFIL. *** SYSTEM FATAL MESSAGE 1262 (COPY1) 1262.4 DATABLOCK %1 (%2) HAS ASSOCIATED FILES THAT CANNOT BE RETRIEVED BY COPY1. *** SYSTEM WARNING MESSAGE 1265 (GTASCT) 1265.0 THE DATABLOCK %1 (%2) HAS NO ASSOCIATED FILES. *** SYSTEM FATAL MESSAGE 1266 (SLCDRV) 1266.0 THE FILE %1 IS NOT A MAIN FILE. PROGRAMMER INFORMATION: THE FIRST ARGUMENT OF XOPEN, XGOPEN OR XMOPEN HAS TO BE THE FIST NUMBER OF A MAIN FILE. *** SYSTEM FATAL MESSAGE 1266 (GTASCT) 1266.1 THE FILE %1 IS NOT A MAIN FILE. PROGRAMMER INFORMATION: THE FIRST ARGUMENT OF GTASCT HAS TO BE THE FIST NUMBER OF A MAIN FILE. *** SYSTEM FATAL MESSAGE 1267 (GTFREE) 1267.0 NO MORE MEMORY SPACE AVAILABLE FOR EXECUTIVE TABLES. USER ACTION: INCREASE DEFAULT NUMBER OF EXECUTIVE TAB LES ENTRIES VIA SYSTEM CELL 162. SYSTEM(162) IS CURRENTLY SET TO %1. *** SYSTEM FATAL MESSAGE 1268 (SLCDRV) 1268.0

125 SUBROUTINE SALLOC RETURNED A NULL FIST NUMBER. PROGRAMMER ACTION: CHECK SALLOC ARGUMENTS. *** SYSTEM FATAL MESSAGE 1269 (SLCDRV) 1269.0 THE ASSOCIATED FILE %1 OF DATABLOCK %2 IS ALREADY OPEN. *** SYSTEM FATAL MESSAGE 1270 (SLCDRV) 1270.0 THE ASSOCIATED FILE %1 CANNOT BE ATTACHED TO DATABLOCK %2. PROGRAMMER INFORMATION: NO MORE THAN %3 ASSOCIATED FILES CAN BE ATTACHED TO ONE DATABLOCK. *** USER FATAL MESSAGE 1273 (WRTTRL) 1273.0 ATTEMPT TO OPEN DATABLOCK %1 (%2). INVALID DATABLOCK FORMAT, ITS NUMERIC OR/AND INDICES FILES WERE NOT FOUND. USER INFORMATION: THE DATABLOCK WAS PROBABLY CREATED IN A PRIOR VERSION OF THE PROGRAM. USER ACTION: MAKE SURE THAT THE DATABLOCK IS COMPATIBLE WITH THE CURRENT VERSION OF THE PROGRAM. *** USER FATAL MESSAGE 1273 (OPNFCU) 1273.1 ATTEMPT TO OPEN DA TABLOCK %1 (%2). INVALID DATABLOCK FORMAT, ITS NUMERIC OR/AND INDICES FILES WERE NOT FOUND. USER INFORMATION: THE DATABLOCK WAS PROBABLY CREATED IN A PRIOR VERSION OF THE PROGRAM. USER ACTION: MAKE SURE THAT THE DATABLOCK IS COMPATIBLE WITH THE CURRENT V ERSION OF THE PROGRAM. *** USER FATAL MESSAGE 1273 (OPNFAC) 1273.2 ATTEMPT TO OPEN DATABLOCK %1 (%2). INVALID DATABLOCK FORMAT, ITS NUMERIC FILE WAS NOT FOUND. USER INFORMATION: THE DATABLOCK WAS PROBABLY CREATED IN A PRIOR VERSION OF THE PROGRAM. USER ACTION: MAKE SURE THAT THE DATABLOCK IS COMPATIBLE WITH THE CURRENT VERSION OF THE PROGRAM. *** SYSTEM WARNING MESSAGE 1274 (GTASCT) 1274.0 THERE ARE MORE THAN %1 ASSOCIATED FILES ATTACHED TO DATABLOCK %2 (%3). PROGRAMMER INFORMATION: ONLY THE FIRST %4 ASSOCIATED FILES ARE RETURNED. *** SYSTEM FATAL MESSAGE 1275 (BPGETB) 1275.0 THE SIZE OF THE BUFFER POOL AREA IS INSUFFICIENT TO CONTINUE PROCESSING. USER ACTION: INCREASE THE SIZE WITH THE BUFFPOOL KEYWOR D ON THE NASTRAN STATEMENT. USER INFORMATION: THE NUMBER OF BLOCKS CURRENTLY ALLOCATED FOR BUFFER POOLING IS%1.

126 *** SYSTEM FATAL MESSAGE 1276 (LDINPT) 1276.0 SPARSE FACTOR MATRIX %1 (%2) HAS AN INCORRECT NUMBER OF ASSOCIATED FILES STORED IN THE NE UTRAL FILE. PROGRAMMER INFORMATION: THE SPARSE FACTOR MATRIX TYPE IS %3 AND SHOULD HAVE %4 FILES. THE NEUTRAL FILE FOR THE MATRIX HAS %5 FILES. *** USER FATAL MESSAGE 1277 (LCLDBS) 1277.0 THE FILE ASSIGNED TO LOGICAL NAME = %1 IS NOT A VALID MASTER DBSET FOR A DBLOCATED DATABASE. USER ACTION : VERIFY THE FILE NAME SPECIFIED ON THE ASSIGN %2 STATEMENT. *** USER FATAL MESSAGE 1277 (DBDEF) 1277.1 IS NOT A VALID THE FILE ASSIGNED TO LOGICAL NAME = %1 MASTER DBSET FOR A PRIMARY DATABASE. USER ACTION : VERIFY THE FILE NAME SPECIFIED ON THE ASSIGN %2 STATEMENT. *** USER FATAL MESSAGE 1277 (ATTDBS) 1277.2 THE FILE ASSIGNED TO LOGICAL NAME = %1 IS NOT A VALID DELIVERY DATABASE. MASTER DBSET FOR A *** SYSTEM WARNING MESSAGE 1279 (RDINIT) 1279.0 THE BUFFSIZE IS LARGER THAN THE MAXIMUM ALLOWABLE BUFFSIZE FOR THIS MACHINE. USER INFORMATION: THE SPECIFIED VALUE WILL BE RESET TO THE MAXIMUM ALLOWED WHICH IS %1 *** USER FATAL MESSAGE 1280 (RDINIT) 1280.0 THE LOGICAL NAME %1 IS ALREADY SPECIFIED FOR A MEMBER OF THE %2 DBSET. *** SYSTEM FATAL MESSAGE 1281 (SLCDRV) 1281.0 AN ATTEMPT WAS MADE TO ATTACH AN ASSOCIATED FILE TO EXECUTIVE FILE %1. PROGRAMMER INFORMATIO N: ASSOCIATED FILES ARE NOT ALLOWED TO BE ATTACHED TO EXECUTIVE FILES. *** SYSTEM FATAL MESSAGE 1282 (SLCDRV) 1282.0 AN ATTEMPT WAS MADE TO OPEN A NON EXISTENT ASSOCIATED FILE %1,%2, TO READ. PROGRAMMER INFORMATION: CHECK THE NAME OF THE ASSOCIATED FILE TO OPEN. *** SYSTEM FATAL MESSAGE 1283 (XOPEN) 1283.0 AN ATTEMPT WAS MADE TO ATTACH AN ASSOCIATED FILE TO DATABLOCK %1 WITHOUT BUFFER POOLING. USER ACTION: BUFFERPOOLING IS ACTIVATED WI TH NASTRAN SYSTEM(119) AND NASTRAN BUFFPOOL STATEMENTS. *** SYSTEM FATAL MESSAGE 1283 (XGOPEN) 1283.1

127 AN INVALID ATTEMPT WAS MADE TO ATTACH AN ASSOCIATED FILE TO DATABLOCK %1 WITHOUT BUFFER POOLING. TRAN USER ACTION: BUFFERPOOLING IS ACTIVATED WITH NAS SYSTEM(119) AND NASTRAN BUFFPOOL STATEMENTS. *** USER FATAL MESSAGE 1284 (REIGL) 1284.0 THE REQUESTED NUMBER OF SEGMENTS (NUMS OR SYSTEM(197)=%1) IS NOT VALID. LIMITS ARE 1 TO %2. *** USER/SYSTEM FATAL/WARNING/INFORMATION MESSAGE 1284.1 1284 (EVLMSG) THE REQUESTED NUMBER OF SEGMENTS ( SYSTEM(197)=%1 ) IS TOO LARGE. THE LIMIT IS %2. *** USER FATAL MESSAGE 1285 (RDINIT) 1285.0 - NAME ON THE INIT FILE SCR300 IS SPECIFIED AS A DBSET ENT STATEMENT. MANAGEM USER INFORMATION: SCR300 IS A RESERVED NAME AND CANNOT BE INITIALIZED AS A DBSET NAME. THE SCR300 PARTITION IS INITIALIZED ON THE INIT SCRATCH STATEMENT. FOR EXAMPLE, INIT SCRATCH SCR300=(SCRA(50000)). *** USER/SYSTEM FATAL/WARNING/INFORMATION MESSAGE 1286.0 1286 (EVLMSG) THE VALUE SPECIFIED FOR %1 SYSTEM CELL 119 IS %2 USER INFORMATION: THE VALUE MUST BE EQUAL TO %3 WHICH IS THE DEFAULT. *** USER/SYSTEM FATAL/WARNING/INFORMATION MESSAGE 1287.0 G) 1287 (EVLMS THE VALUE SPECIFIED FOR %1 SYSTEM CELL 114 (OR 'BUFFPOOL KEYWORD) IS %2 USER INFORMATION: THE VALUE MUST BE GREATER THAN %3 *** USER INFORMATION MESSAGE 9100 (BIOCRT) 1288.0 MAXIMUM SIZE REQUESTED FOR FILE EXCEEDS FILE SYSTEM CAPACITY LOGICAL NAME IS '%4', BLOCK SIZE = %3 WORDS FILE NAME IS '%5' REQUESTED BLOCKS COUNT = %1, BLOCKS COUNT RESET TO %2. *** USER FATAL MESSAGE 2001 (USRMSG) 2001.0 SEQGP ENTRY REFERENCES UNDEFINED GRID POINT %1 User information: SEQGP references a point which is not a grid or scalar point. *** SYSTEM FATAL MESSAGE 2002 (USRMSG) 2002.0 GRID POINT %1 NOT IN EQEXIN. User information: This message indicates a program design error in GP1.

128 *** USER FATAL MESSAGE 2003 (GP1C) 2003.0 COORDINATE SYSTEM %1 REFERENCES UNDEFINED GRID POINT %2 IN SUPERELEMENT %3 User information: Applies to CORD1j definitions. *** USER FATAL MESSAGE 2003 (USRMSG) 2003.1 COORDINATE SYSTEM %1 REFERENCES UNDEFINED GRID POINT %2 User information: Applies to CORD1j definitions. *** USER FATAL MESSAGE 2004 (GP1C) 2004.0 COORDINATE SYSTEM %1 REFERENCES UNDEFINED COORDINATE SYSTEM %2 IN SUPERELEMENT %3 User information: Applies to CORD2j definitions. *** USER FATAL MESSAGE 2004 (USRMSG) 2004.1 COORDINATE SYSTEM %1 REFERENCES UNDEFINED COORDINATE SYSTEM %2 User information: Applies to CORD2j definitions. *** SYSTEM FATAL MESSAGE 2005 (GP1C) 2005.0 INCONSISTENT COORDINATE SYSTEM DEFINITIONS DETECTED IN S UPERELEMENT %1 System information: At least one coordinate system cannot be tied to the basic system. *** SYSTEM FATAL MESSAGE 2005 (USRMSG) 2005.1 INCONSISTENT COORDINATE SYSTEM DEFINITION. System information: nnot be tied to the basic system. At least one coordinate system ca *** USER FATAL MESSAGE 2006 2006.1 GRID POINT %1 REFERENCES UNDEFINED COORDINATE SYSTEM %2 IN SUPERELEMENT %3 *** USER FATAL MESSAGE 2006 (USRMSG) 2006.2 GRID POINT %1 REFERENCES UNDEFINED COORDINATE SYSTEM %2 User information: The grid point whose internal sequence number is printed above references an undefined coordinate system in either field 3 or field 7 for a GRID entry. AL MESSAGE 2007 (USRMSG) *** USER FAT 2007.0 ELEMENT %1 REFERENCES UNDEFINED GRID POINT %2 User information: The element specified points to a non - existent grid or scalar point. This message may occur in superelement analysis when the reference

129 grid point GO is neither e xterior nor interior to the superelement. An avoidance is to instead use the vector component method to define the element coordinate system. *** USER FATAL MESSAGE 2007 (MODGM2) 2007.1 ELEMENT %1 ID = %2 REFERENCES UNDEFINED GRID POINT %3 *** USER FATAL MESSAGE 2008 (USRMSG) 2008.0 LOAD SET %1 REFERENCES UNDEFINED GRID POINT %2 User information: The LOAD set specified points to a non - existent grid or scalar point. *** USER FATAL MESSAGE 2008 (MKAEF1) 2008.1 ID = %1 IS REFERENCED BY FORCEI OR UNDEFINED GRID POINT MOMENTI BULK DATA ENTRY. *** USER FATAL MESSAGE 2009 (USRMSG) 2009.0 TEMPERATURE SET %1 REFERENCES UNDEFINED GRID POINT %2 User information: - The TEMP set specified points to a non existent grid or scalar point. *** USER FATAL MESSAGE 2010 (USRMSG) 2010.0 ELEMENT %1 REFERENCES UNDEFINED PROPERTY %2 User information: The element specified points to a non - existent property entry. *** USER FATAL MESSAGE 2010 2010.1 2 IS DUPLICATED PROPERTY ID %1 FOR ELEMENT TYPE % *** USER WARNING MESSAGE 2010 2010.2 ELEMENT ID %1 HAS DUPLICATED CID SPECIFIED ON MATCID. *** USER FATAL MESSAGE 2010 2010.3 ELEMENT ID %1 HAS TWO DIFFERENT CID VALUES %2 and %3 SPECIFIED ON MATCID. ONLY TWO DIFFERENT CID VALUES HAVE BEEN LISTED. OTHER CONFLICTING CID VALUES MAY EXIST FOR THIS ELEMENT. *** USER FATAL MESSAGE 2010 (TA1A) 2010.4 ELEMENT %1 REFERENCES UNDEFINED PROPERTY %2. IF PAABSF1 CARD IS SPECIFIED, IT IS NOT SUPPORTED IN THE CURRENT SOLUTION TYPE. User information: The element specified points to a non - existent property entry. *** USER FATAL MESSAGE 2011 (TA1A) 2011.0 NO PHBDY ENTRIES FOR CHBDYP *** USER FATAL MESSAGE 2011 (USRMSG) 2011.1 ALL ELEMENTS OF TYPE %1 HAVE NO PROPERTY CARD DEFINED. *** USER FATAL MESSAGE 2011 (TA1A) 2011.2 ALL ELEMENTS OF TYPE CAABSF HAVE NO PROPERTY CARD

130 PAABSF DEFINED. IF PAABSF1 CARD IS SPECIFIED, IT IS NOT SUPPORTED IN THE CURRENT SOLUTION TYPE. *** USER FATAL MESSAGE 2012 (GP1GSM) 2012.0 IDENTIFICATION %1 SAME BETWEEN GRID, SCALAR OR POINT IN SUPERELEMENT%2 *** USER FATAL MESSAGE 2012 (USRMSG) 2012.1 G RID POINT %1 SAME AS SCALAR POINT. User information: Identification of grid and scalar points must be unique. *** USER INFORMATION MESSAGE 2012 (GP1GSM) 2012.2 NUMBER OF DUPLICATE GRIDS ENCOUNTERED AND ELIMINATED = %1 USER INFORMATION MESSAGE 2012 (GP1CEL) *** 2012.3 NUMBER OF DUPLICATE COORDINATE SYSTEMS ENCOUNTERED AND ELIMINATED = %1 *** USER WARNING MESSAGE 2013 (USRMSG) 2013.0 NO STRUCTURAL ELEMENTS EXIST. User information: Model check for structural elements. *** SYSTEM FATAL MESSAGE 2014 (USRMSG) 2014.0 LOGIC ERROR IN ECPT CONSTRUCTION. System information: Internal logic error in connection table construction. Send run to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT for analysis. *** USER WARNINT MESSAGE 2015 (USRMSG) 2015.0 EITHER NO ELEMENTS CONNECT INTERNAL GRID POINT %1 OR IT IS CONNECTED TO A RIGID ELEMENT OR A GENERAL ELEMENT. *** USER FATAL MESSAGE 2016 (USRMSG) 2016.0 NO MATERIAL PROPERTIES EXIST. User information: Materia l properties are required for matrix generation and none are present in the Bulk Data Section. *** USER FATAL MESSAGE 2017 (USRMSG) 2017.0 MATERIAL PROPERTY IDENTIFICATION %1 WAS DUPLICATED. User information: Duplicate material identifications cannot be used on more than one MATi entry type. Check all MATi entries for unique material identification numbers. *** USER FATAL MESSAGE 2018 (USRMSG) 2018.0 MATT%1 ENTRY %2 DID NOT MATCH PARENT TYPE.

131 User in formation: dependent material entry does not match the correct - A temperature type of parent entry. Make sure that referenced temperature and material entries are identified as the same type. *** USER WARNING MESSAGE 2019, 2019.0 - NU.21 - AN INCONSISTENT HAS BEEN COMPUTED FOR VALUE FOR MAT8 ID %1. User information: The evaluation of gamma = 1 - nu12*(nu12*E2/E1) resulted in a negative value. This will not cause mathematical failure, but could his MAT ID. Review cause strange behavior on elements which reference t values for E1 and E2 to make sure that they are correct. *** USER WARNING MESSAGE 2019 (USRMSG) 2019.1 NU.21 - AN INCONSISTENT VALUE FOR - HAS BEEN COMPUTED FOR MAT8 ID %1. User information: - nu12*(nu12*E2/E1) resulted in a The evaluation of gamma = 1 negative value. This will not cause mathematical failure, but could cause strange behavior on elements which reference this MAT ID. Review values for E1 and E2 to make sure that they are corr ect. *** USER WARNING MESSAGE 2019, 2019.2 AN INCONSISTENT VALUE FOR GAMMA HAS BEEN COMPUTED FOR MAT11 ID %1. User information: NU12NU21 or gamma2 = 1 - NU23NU32 - The evaluation of gamma1 = 1 NU31NU13 resulted in a negative value. Thi s will - or gamma3 = 1 not cause mathematical failure, but could cause strange behavior on elements which reference this MAT ID. Review values for E1, E2, E3, NU12, NU13 and NU23 to make sure that they are correct. *** USER WARNING MESSAGE 2019, 2019.4 AN INCON SISTENT VALUE FOR DELTA HAS BEEN COMPUTED FOR MAT11 ID %1. User information: - The evaluation of delta = 1 - NU23NU32 - NU13NU31 NU12NU21 - 2NU21NU32NU13 resulted in a negative value. This will not cause mathematical failure, but could cause strange behavior o n elements which reference this MAT ID. Review values for E1, E2, E3, NU12, NU13 and NU23 to make sure that they are correct. *** USER WARNING MESSAGE 2019, 2019.5 THE SHEAR MODULUS IS NOT DEFINED CORRECTLY FOR MAT11 ID %1. User information: The shear modulus should be greater than zero.

132 *** USER WARNING MESSAGE 2020 (USRMSG) 2020.0 ONE OR MORE OF THE ALLOWABLE STRESS CONSTANTS WERE INCORRECT FOR ELEMENT %1 PLY %2 User information: Failure theory calculations were requested, but Sb o n the PCOMP entry or Xt, Xc, Yt, Yc, or S on the MAT8 were less than or equal to zero. See the element/PLY for which PCOMP or MAT8 entry is in error. The failure index calculations were not sure that Sb,Xt, made. Either drop request for Failure theory calculations or be Xc, Yt, Yc and S are positive. If a MAT1 card was used, verify that the ST,SC and SS values are valid. *** SYSTEM FATAL MESSAGE 2021 (USRMSG) 2021.0 - CALLING SEQUENCE. BAD GMMAT System information: subroutine which calls either subroutine The calling sequence of the GMMATD or GMMATS defined a nonconformable matrix product. The subroutine The subroutine examines the transpose flags in combination with the orders of the matrices to make sure that a conformable matrix product is defined by this input data. This test clearly is made for purposes of calling routine checkout only. No tests are made, nor can they be made, to insure that the calling routine has provided sufficient storage for arrays. *** USER FATAL MESSAGE 2022 (USRMSG) 2022.0 PROBLEM SIZE OF %1 DOF HAS EXCEEDED THE LIMIT OF 65535 FOR AN INDIVIDUAL PROBLEM OR SUPERELEMENT. *** USER FATAL MESSAGE 2024, 2024.0 OPERATION CODE %1 NOT DEFINED FOR MODULE PARAM. USER ACTION: MAKE SURE OPERATIO N CODE PARAMETER IS ENCLOSED WITHIN SINGLE QUOTES ("'") User information: The operation code "SUB" was not chosen from the legal list or was misspelled. *** SYSTEM FATAL MESSAGE 2024 (USRMSG) 2024.1 UNDEFINED MESSAGE. USER FATAL MESSAGE 2025 (SEPOMT) *** 2025.0 COORDINATE SYSTEM %1 REFERENCED BY GRID %2 IS UNDEFINED IN SUPERELEMENT %3. *** USER FATAL MESSAGE 2025 (MODULE) 2025.1 UNDEFINED COORDINATE SYSTEM ID = %1 User information:

133 Check coordinate system numbers used o n Bulk Data entries against those defined on CORD1C, CORD1R, etc., Bulk Data entries to insure that there are no undefined coordinate systems. This message can occur in superelement analysis when the CORD1x entry is in the Bulk Data entry. The cause is that grid points referenced on the CORD1x entry are not connected by elements in the superelement. An avoidance is to use the CORD2x formats, which reference points in space rather than grid points. This message also occurs frequently when using a non - SIEMENS PLM software model generation program that places grid point identification numbers in the field used for material identification numbers by modern plate elements. See especially the CTRIA3 entry, field 7. USER FATAL MESSAGE 2025 (EBSH4D) *** 2025.2 UNDEFINED COORDINATE SYSTEM ID = %1 IS REFERRED IN OCID FIELD OF CBUSH ENTRY ID = %2. User information: Check coordinate system numbers used on Bulk Data entries against those defined on CORD1C, CORD1R, etc., Bulk Data entries to insure that there are no undefined coordinate systems. This message can occur in superelement analysis when the CORD1x entry is in the Bulk Data entry. The cause is that grid points referenced on the CORD1x entry are not connected by element s in the superelement. An avoidance is to use the CORD2x formats, which reference points in space rather than grid points. - SIEMENS PLM This message also occurs frequently when using a non software model generation program that places grid point identif ication numbers in the field used for material identification numbers by modern plate elements. See especially the CTRIA3 entry, field 7. *** USER FATAL MESSAGE 2025 (EBSH3D) 2025.3 UNDEFINED COORDINATE SYSTEM ID = %1 IS REFERRED IN CBUSH ENTRY I D = %2. User information: Check coordinate system numbers used on Bulk Data entries against those defined on CORD1C, CORD1R, etc., Bulk Data entries to insure that there are no undefined coordinate systems. sis when the CORD1x This message can occur in superelement analy entry is in the Bulk Data entry. The cause is that grid points referenced on the CORD1x entry are not connected by elements in the superelement. An avoidance is to use the CORD2x formats, which reference points in space rather than grid points. This message also occurs frequently when using a non - SIEMENS PLM software model generation program that places grid point identification numbers

134 in the field used for material identification numbers by modern the CTRIA3 entry, field 7. plate elements. See especially *** USER FATAL MESSAGE 2025 (APD0) 2025.4 %1 COORDINATE SYSTEM ID = %2 REFERENCED BY %3 ENTRY IS NOT DEFINED. User information: Check coordinate system numbers used on Bulk Data entries against those defined on CORD1C , CORD1R, etc., Bulk Data entries to insure that there are no undefined coordinate systems. This message can occur in superelement analysis when the CORD1x entry is in the Bulk Data entry. The cause is that grid points referenced e not connected by elements in the superelement. on the CORD1x entry ar An avoidance is to use the CORD2x formats, which reference points in space rather than grid points. - SIEMENS PLM This message also occurs frequently when using a non software places grid point identification numbers model generation program that in the field used for material identification numbers by modern plate elements. See especially the CTRIA3 entry, field 7. *** USER FATAL MESSAGE 2025 2025.5 COORDINATE SYSTEM ID = %1 REFERENCED BY PLPLANE ENTRY FOR ELEMENT ID = %2 IS NOT DEFINED. User information: Check coordinate system numbers used on Bulk Data entries against those defined on CORD1C, CORD1R, etc., Bulk Data entries to insure that there are no undefined coordinate systems. This message can occur in superelement analysis when the CORD1x entry is in the Bulk Data entry. The cause is that grid points referenced on the CORD1x entry are not connected by elements in the superelement. An avo idance is to use the CORD2x formats, which reference points in space rather than grid points. This message also occurs frequently when using a non - SIEMENS PLM software model generation program that places grid point identification numbers in the field used for material identification numbers by modern plate elements. See especially the CTRIA3 entry, field 7. *** SYSTEM FATAL MESSAGE 2025 (APDST2,APDCST) 2025.7 COORDINATE SYSTEM ID = %1 REFERENCED BY CAERO%2 ENTRY ID = %3 IS NOT FOUND. User inf ormation: Check coordinate system numbers used on Bulk Data entries against those defined on CORD1C, CORD1R, etc., Bulk Data entries to insure that there are no undefined coordinate systems. This message can occur in superelement analysis when the CORD 1x entry is in the Bulk Data entry. The cause is that grid points referenced

135 on the CORD1x entry are not connected by elements in the superelement. An avoidance is to use the CORD2x formats, which reference points in space rather than grid points. - s message also occurs frequently when using a non Thi SIEMENS PLM software model generation program that places grid point identification numbers in the field used for material identification numbers by modern plate elements. See especially the CTRIA3 entry , field 7. *** USER FATAL MESSAGE 2025 (BGSLPD) 2025.8 UNDEFINED COORDINATE SYSTEM ID = %1 IS REFERRED IN %2 ENTRY ID = %3. User information: Check coordinate system numbers used on Bulk Data entries against those defined on CORD1C, CORD1R, etc., Bulk Data entries to insure that there are no undefined coordinate systems. This message can occur in superelement analysis when the CORD1x entry is in the Bulk Data entry. The cause is that grid points referenced on the CORD1x entry are not connected by elements in the superelement. An avoidance is to use the CORD2x formats, which reference points in space rather than grid points. This message also occurs frequently when using a non - SIEMENS PLM software model generation program that places grid point identification numbers in the field used for material identification numbers by modern plate elements. See especially the CTRIA3 entry, field 7. *** USER WARNING MESSAGE 2025 (SDR2MM) 2025.9 COORDINATE SYSTEM ID=%1 SPECIFIED ON THE MAXMIN COMMAND IS UNDEFINED. USER INFORMATION: THE %2 COORDINATE SYSTEM WILL BE USED. *** USER FATAL MESSAGE 2026 (USRMSG) 2026.0 ELEMENT %1 GEOMETRY YIELDS UNREASONABLE MATRIX. User information: Referenc ed element geometry and/or properties yield a numerical result which causes an element stiffness or mass matrix to be undefined. Possible causes include, but are not limited to, (1) the length of a rod or bar is zero because the end points have the sam e coordinates, (2) the sides of a triangle or quadrilateral are collinear which leads to a zero cross product in defining an element coordinate system, (3) the bar orientation vector is parallel to the bar axis, or (4) a shear panel has zero thickness or modulus. Check GRID Bulk Data entries defining element end points for bad data. *** USER FATAL MESSAGE 2027 (USRMSG) 2027.0 ELEMENT %1 HAS INTERIOR ANGLE GREATER THAN 180

136 DEGREES AT GRID POINT %2 User information: SHEAR panel element with the referenced element number has been defined with the four grid points out of the proper cyclical order. See Bulk Data entry definition for CSHEAR entry. *** SYSTEM FATAL MESSAGE 2028 (USRMSG) 2028.0 SMA3A ERROR NUMBER %1 System information: Internal logic error in Subroutine SMA3A of Module SMA3. Possibly an error exists in the generation of the GEI data block. Use the TABPT module to print GEI. *** USER FATAL MESSAGE 2029 (USRMSG) 2029.0 UNDEFINED TEMPERATURE SET %1 on: User informati The referenced temperature set had no default temperature defined. Define a temperature or default temperature for each grid point in the model. *** SYSTEM FATAL MESSAGE 2030 (USRMSG) 2030.0 BAD GPTT DATABLOCK DETECTED. *** USER FATAL MESSAGE 2031 (USRMSG) 2031.0 ELEMENT %1 UNACCEPTABLE GEOMETRY. User information: Possible error on GRID entry or connection entry. *** USER FATAL MESSAGE 2033 (USRMSG) 2033.0 SINGULAR H - MATRIX FOR ELEMENT %1 User information: r on GRID entry or connection entry. Possible erro *** SYSTEM FATAL MESSAGE 2034 (USRMSG) 2034.0 - S DO NOT MATCH PIVOT. ELEMENT %1 SIL *** USER FATAL MESSAGE 2035 (USRMSG) 2035.0 QUADRILATERAL %1 INTERIOR ANGLE GREATER THAN 180 DEGREES. User information: Possible error on connection entry for element. *** USER FATAL MESSAGE 2036 (USRMSG) 2036.0 SINGULAR MATRIX FOR ELEMENT %1 User information: Possible error on GRID entry or connection entry. *** USER FATAL MESSAGE 2037. 2037.0 ILLEGAL G EOMETRY FOR TRIAR ELEMENT WITH ID =%1 *** USER FATAL MESSAGE 2037 (USRMSG) 2037.1 BAD ELEMENT %1 GEOMETRY. User information:

137 Possible error on GRID entry or connection entry. *** SYSTEM FATAL MESSAGE 2038, 2038.0 SINGULAR MATRIX FOR ELEMENT %1 System information: Possible error on GRID entry, connection entry, or rigid element. Rigid elements must have 6 n - set degrees of freedom that define all six rigid body motions of the element. *** USER FATAL MESSAGE 2038, 2038.1 RBE3 ELEMENT %1 IS SINGULAR. USER ACTION: ADD MORE DOFS TO THE CONNECTED POINTS TO INSURE THAT THEY CAN CONSTRAIN ALL 6 RIGID BODY MODES OF THE ELEMENT. *** USER FATAL MESSAGE 2039 (USRMSG) 2039.0 ZERO SLANT LENGTH FOR HARMONIC %1 OF CCONEAX %2 User information: Possible error on GRID entry or connection entry. *** USER FATAL MESSAGE 2040 (USRMSG) 2040.0 SINGULAR MATRIX FOR ELEMENT %1 User information: nection entry or a zero value Possible error on GRID entry or con of G was specified on a MAT1 entry for a Beam element. A zero value of G may be used if K1 and K2 are explicitly set to zero also. Their default value is nonzero. *** USER FATAL MESSAGE 2041 (USRMSG) 2041.0 MATT1, MATT2, MATT3, MATT11 OR MATS1 ENTRY A REFERENCES TABLE NUMBER %1 WHICH IS NOT DEFINED ON A TABLEM1,TABLEM2,TABLEM3,TABLEM4 OR TABLES1 ENTRY. User information: The user must insure that all table identification numbers on MATT1, MATT2, MATT3, MATT1 1 or MATS1 entries reference tables which exist in the Bulk Data Deck. *** USER FATAL MESSAGE 2042 (USRMSG) 2042.0 MISSING MATERIAL TABLE %1 FOR ELEMENT %2 User information: The referenced material table identification number is missing. The us er should check to see that all element property Bulk Data entries (e.g., PBAR, PROD) reference material identification number for material property entries that exist in the Bulk Data Section. *** USER FATAL MESSAGE 2043 (USRMSG) 2043.0 MISSING MATERIAL TABLE %1 *** USER FATAL MESSAGE 2044 (USRMSG) 2044.0 UNDEFINED TEMPERATURE SET %1 User information:

138 The referenced temperature set was selected in the Case Control but not defined in the Bulk Data. *** USER FATAL MESSAGE 2045 (USRMSG) 2045.0 TEMPERATURE UNDEFINED AT GRID POINT WITH INTERNAL INDEX %1 *** USER FATAL MESSAGE 2046 (USRMSG) 2046.0 UNDEFINED ELEMENT DEFORMATION SET %1 User information: The referenced element deformation set was selected in the Case Control but not defined in the Bulk Data. *** USER WARNING MESSAGE 2047 (USRMSG) 2047.0 - POINT CONSTRAINT SET %1 UNDEFINED MULTI User information: A multipoint constraint set selected in the Case Control could not be found in either an MPC or MPCADD entry or a set referenced on an MPCADD entry could not be found on an MPC entry. *** USER FATAL MESSAGE 2048 (USRMSG) 2048.0 UNDEFINED GRID POINT %1 IN MULTI - POINT CONSTRAINT SET %2 User information: An MPC en try references a grid point which has not been defined. This message can be output in superelement analysis if: 1. All grids referenced on the MPC are not interior to the same superelement, or 2. The dependent DOF are downstream of the independent DOF. As a minimum requirement, when an MPC (or RBE) definition includes grid points interior to more than one superelement, then the independent DOF must be downstream of the dependent DOF. *** USER WARNING MESSAGE 2049 (SEPSEQ) 2049.0 SPECIFIED ON %2 IS NOT DEFINED FOR GRID POINT %1 SUPERELEMENT %3 *** USER FATAL MESSAGE 2049, 2049.1 UNDEFINED GRID POINT %1 HAS A COORDINATE REFERENCED ON A %2 CARD. *** USER FATAL MESSAGE 2049 (GP4) 2049.3 UNDEFINED GRID POINT %1 HAS A COORDINATE REFERENCED ON A USET CARD. *** USER FATAL MESSAGE 2049 (USRMSG) 2049.4 UNDEFINED GRID POINT %1 HAS A COORDINATE REFERENCED ON A CONSTRAINT CARD. User information: An ASET, BSET, CSET, QSET, MPC, SPC, OMIT, or SUPORT entry references an undefined grid or scalar point. In superelement analysis, the equivalent entries SEBSET, SECSET, or SEQSET must refer to exterior

139 points of the superelement being processed. This message has been ement has no exterior points, due to observed when the superel modeling errors. This message has also been observed to reference grid point 0 when scalar points have any of the components 1 through 6 referenced in the C field. Zero or blank should be used instead. *** USER WARNING MESSAGE 2049 (GP4) 2049.5 UNDEFINED GRID POINT %1 ON A USET1 CARD IGNORED. *** USER WARNING MESSAGE 2049 2049.6 UNDEFINED GRID POINT %1 ON A %2 CARD IGNORED. ANY OTHERS ALSO IGNORED. *** USER WARNING MESSAGE 2049 2049.7 UNDEFINED GRID POINT %1 ON A %2 CARD IGNORED. *** USER FATAL MESSAGE 2050 (USRMSG) 2050.0 UNDEFINED GRID POINT %1 HAS A SUPPORT COORDINATE. User information: A SUPORT entry references a grid point which has not been defined. USER INFORMATION MESSAGE 2050 (ESCHEL) *** 2050.1 AUTOMPC PROCESSING COMPLETE *** USER INFORMATION MESSAGE 2050 (ESCHEL) 2050.2 AUTOMPC PROCESSING ELIMINATED %1 REDUNDANT CONSTRAINT EQUATIONS *** USER INFORMATION MESSAGE 2050 (AUTOMPC) 2050.3 ERROR PROCESSING %1 IN AUTOMPC PROCESSING *** USER INFORMATION MESSAGE 2050 (AUTOMPC) 2050.4 AUTOMPC PROCESSING ABORTED DUE TO INSUFFICIENT - INCREASE MEMORY MEMORY VALUE BY %1 WORDS *** USER INFORMATION MESSAGE 2050 (ESCHEL) 2050.5 CONSTR AINT EQUATION %1 HAS BEEN FOUND TO CONTAIN IMPROPER DOFS (SUCH AS ONLY SPC DOFS) BY THE AUTOMPC PROCESSING *** SYSTEM FATAL MESSAGE 2050 2050.6 INSUFFICIENT MEMORY FOR ROTOR DYNAMICS *** USER FATAL MESSAGE 2050 (ROTPCD) 2050.7 ROTOR DYNAMICS LIMITED TO A MAXIMUM OF 10000 MODES *** USER INFORMATION MESSAGE 2050 (ESCHEL) 2050.8 ALL DOFS OF CONSTRAINT EQUATION %1 ARE DEFINED AS EXCLUDED BY THEIR INCLUSION IN USER SET 5 DURING AUTOMPC PROCESSING *** USER INFORMATION MESSAGE 2050 (AUTOMPC) 2050.9 AUTOMPC PROCESSING ABORTED DUE TO FAILURE TO EXTEND

140 MEMORY SUFFICENTLY TO KEEP THE EXPANDING CONSTRAINT MATRIX IN MEMORY. THIS IS A VERY UNUSUAL OCCURENCE BUT CAN RESULT FROM A LARGE NUMBER OF DOFS BEING IN THE U5 SET. INCREASING THE MEMORY DEFINED ALLOCATION WILL RESULT IN SUCCESS BUT THE AMOUNT NEEDED MAY BE MORE THAN IS FEASIBLE. *** USER WARNING MESSAGE 2050 (ESCHEL) 2050.10 AUTOMPC PROCESSING ENCOUNTERED %1 SMALL PIVOTS WHICH WERE NOT SMALL ENOUGH TO MAKE THE EQUATION REDUNDANT AND THEREFORE MAY MAKE THE CONSTRAINT MATRIX ILL - CONDITIONED RESULTING IN LARGE NUMERICAL ROUNDOFF ERRORS. SETTING THE PARAMETER AMPCZ TO 1.0E - 4 OR LARGER WILL RESULT IN THESE EQUATIONS BEING ELIMINATED (REDUNDANT). THIS SIT UATION OCCURS MOST FREQUENTLY WHEN EXCESSIVE DOFS ON GRIDS OF RIGID ELEMENTS ARE RESTRAINED. *** USER FATAL MESSAGE 2050 (ROTSDB) 2050.11 ROTOR DYNAMICS LIMITED TO A MAXIMUM OF %1 TIDs ON TABLEST. REDUCE THE NUMBER OF TIDs ON TABLEST %2. *** USER FATAL MESSAGE 2050 (ROTSDB) 2050.12 ROTOR DYNAMICS REQUIRES THAT THE DISP/FORCE VALUES ON TABLEST %1 BE THE SAME FOR EACH TABLEDi. *** USER FATAL MESSAGE 2050 (CKROTCN) 2050.13 GRID NUMBER %1 IN ROTORG SET NUMBER %2 ILLEGALLY CONNECTED TO A CBEAR ELEMENT. User information: Grids on a ROTORG can only be connected to RBE1, RBE2, RBE3, RBAR, RROD, RTRPLT, CMASS1, CMASS2, CONM1, or CONM2 element tpes or via MPC equations. *** USER FATAL MESSAGE 2050 (CKROTCN) 2050.14 GRID NUMBER %1 IN ROTORG SET NUMBER %2 ILLEGALLY CONNECTED TO ELEMENT NUMBER %3, TYPE %4. User information: Grids on a ROTORG can only be connected to RBE1, RBE2, RBE3, RBAR, RROD, RTRPLT, CMASS1, CMASS2, CONM1, or CONM2 element tpes or via

141 MPC equati ons. *** USER FATAL MESSAGE 2051 (USRMSG) 2051.0 - POINT CONSTRAINT SET UNDEFINED GRID POINT %1 IN SINGLE %2 User information: In superelement analysis this message may not be issued. It is recommended that all superelement definitions (e.g., SESE T and SEID field on GRID entries) be removed temporarily so that PARAM,CHECKOUT may be used to check for this type of error. *** USER WARNING MESSAGE 2051 (GP4) 2051.1 UNDEFINED GRID POINT %1 IN SPC SET %2 IGNORED. (ANY OTHERS ALSO IGNORED) *** USER FATAL MESSAGE 2052 (GP4) 2052.0 UNDEFINED GRID POINT %1 ON AN SPCD CARD WITH STATIC LOAD SET ID %2 *** USER FATAL MESSAGE 2052 (USRMSG) 2052.1 UNDEFINED GRID POINT %1 IN SINGLE - POINT CONSTRAINT SET %2 User information: An SPC entry in the selected SPC set references a grid point which has not been defined. *** USER WARNING MESSAGE 2053 (USRMSG) 2053.0 UNDEFINED SINGLE POINT CONSTRAINT SET %1 - User information: A single point constraint set selected in the Case Control could not be found on either an SPCADD, SPC or SPC1 entry, or a set referenced on an SPCADD entry could not be found on either an SPC or SPC1 entry. *** USER FATAL MESSAGE 2054 (USRMSG) 2054.0 SUPER ELEMENT %1 REFERENCES UNDEFINED SIMPLE ELEMENT %2 *** USER FATAL MESSAGE 2056 (USRMSG) 2056.0 UNDEFINED SUPER ELEMENT %1 PROPERTIES *** USER FATAL MESSAGE 2057 (USRMSG) 2057.0 IRRATIONAL SUPER ELEMENT %1 TOPOLOGY *** USER WARNING MESSAGE 2058 (USRMSG) 2058.0 ELEMENT %1 CONTRIBUTES TO THE DAMPING MATRIX WHICH IS PURGED. IT WILL BE IGNORED. *** USER FATAL MESSAGE 2059 (USRMSG) 2059.0 UNDEFINED GRID POINT %1 ON SE -- BFE ENTRY FOR SUPER ELEMENT %2 *** USER FATAL MESSAGE 2060 (USRMSG) 2060.0 UNDEFINE D GRID POINT %1 ON QDSEP ENTRY FOR SUPER

142 ELEMENT %2 *** USER FATAL MESSAGE 2061 (USRMSG) 2061.0 UNDEFINED GRID POINT %1 ON GENERAL ELEMENT %2 User information: A general element references an undefined grid point. USER FATAL MESSAGE 2062 (USRMSG) *** 2062.0 UNDEFINED SUPER ELEMENT PROPERTY %1 FOR SUPER ELEMENT %2 *** SYSTEM FATAL MESSAGE 2063 (USRMSG) 2063.0 TA1C LOGIC ERROR *** USER FATAL MESSAGE 2064 (USRMSG) 2064.0 UNDEFINED EXTRA POINT %1 REFERENCED ON SEQEP ENTRY. User information: An attempt has been made to resequence an undefined extra point. *** USER FATAL MESSAGE 2065 (USRMSG) 2065.0 UNDEFINED GRID POINT %1 ON DMIG ENTRY. User information: Direct matrix input references an undefined grid point. *** USER FATAL MESSAGE 2066 (USRMSG) 2066.0 UNDEFINED GRID/SCALAR POINT %1 ON DAREA, DELAY, DPHASE ENTRY. User information: A DAREA, DELAY or DPHASE entry references an undefined grid/scalar point. *** USER FATAL MESSAGE 2067 (USRMSG) 2067.0 UNDEFINED GRID/SCALAR/EXTRA POINT %1 IN BULK DATA ENTRY. User information: /scalar/extra point. A nonlinear dynamic load references an undefined grid *** USER FATAL MESSAGE 2068 (USRMSG) 2068.0 UNDEFINED GRID POINT %1 IN TRANSFER FUNCTION SET %2 User information: A dynamic loading entry references an undefined grid point. *** USER FATAL MESSAGE 2069 (USRMSG) 2069.0 UNDEFINED GRID POINT %1 IN TRANSIENT INITIAL CONDITION SET %2 User information: An attempt has been made to specify initial conditions for an undefined grid point. *** USER FATAL MESSAGE 2070 (USRMSG) 2070.0 REQUESTED DMIG MATRIX %1 IS UNDEFINE D. User information: A DMIG matrix was selected in the Case Control but was not present

143 in the Bulk Data. *** USER FATAL MESSAGE 2071 (DPD2) 2071.0 DYNAMIC LOAD %1 ENTRY %2 REFERENCES UNDEFINED %3 SET %4 User information: A referenced dynamic load table was not present in the Bulk Data. *** USER WARNING MESSAGE 2071 (DPD2) 2071.1 EXCITATION SET %1 REFERENCED IN DYNAMIC LOAD %2 ENTRY %3 DEFINES A NULL LOAD User information: 1. Check for proper excitation ID references on RLOADi, TLOADi and/or ACSRCE entries and the associated DAREA and/or static load entries. (FORCEi, MOMENTi, etc.). - 2. Check for null magnitudes on the above mentioned entries. *** USER WARNIN G MESSAGE 2071 (DPD2) 2071.2 DAREA SET %1 REFERENCED IN DYNAMIC LOAD %2 ENTRY %3 DEFINES NULL ENFORCED MOTION User information: 1. Check for proper DAREA ID references on RLOADi, TLOADi and/or ACSRCE entries and the associated enforced motion entries (SPC, SP CD, etc.) 2. Check for null magnitudes on the above - mentioned entries. 3. If enforced motion is defined via SPCD entries, make sure that the referenced components also appear on SPC, SPC1 or the PS field of GRID entries. If the above condition exists, USER WARNING MESSAGE 2108 is also issued. *** USER WARNING MESSAGE 2071 (DPD2) 2071.3 DAREA SET %1 REFERENCED IN DYNAMIC LOAD %2 ENTRY %3 DEFINES A NULL LOAD OR NULL ENFORCED MOTION User information: 1. Check for proper DAREA ID references on RLO ADi, TLOADi and/or ACSRCE entries and the associated DAREA and/or static load and enforced motion entries (FORCEi, MOMENTi, SPC, SPCD, etc.). 2. Check for null magnitudes on the above - mentioned entries. 3. If enforced motion is defined via SPCD entries , make sure that the referenced components also appear on SPC, SPC1 or the PS field of GRID entries. If the above condition exists, USER WARNING MESSAGE 2108 is also issued. *** SYSTEM WARNING MESSAGE 2072 (USRMSG) 2072.0 CARD TYPE %1 NOT FOUND ON DATA BLOCK. System information:

144 This warning message is issued when the trailer bit for the card type= 1 but the corresponding record is not on the data block. *** USER INFORMATION MESSAGE 2073 (USRMSG) 2073.0 HOD %1,NO. PASSES = %2 MPYAD MET *** USER FATAL MESSAGE 2074 (USRMSG) 2074.0 UNDEFINED TRANSFER FUNCTION SET %1 User information: A transfer function set was selected in the Case Control but was not present in the Bulk Data. *** SYSTEM FATAL MESSAGE 2075 (USRMSG) 2075.0 - %1 - IMPROPER VALUE FOR FIRST PARAMETER IN DMAP INSTRUCTION SDR2. System information: Data recovery was requested for a problem type which was not defined. *** SYSTEM FATAL MESSAGE 2075. 2075.1 - %1 - IMPROPER VALUE FOR FIRST PARAMETER IN DMAP INSTRUCTION CASE. *** SYSTEM FATAL MESSAGE 2075 (DPD). 2075.2 EIGR ENTRY SET ID = %1 HAS UNDEFINED GRID OR SCALAR POINT %2 *** SYSTEM FATAL MESSAGE 2075 (DPD). 2075.3 TF SET ID = %1 HAS UNDEFINED GRID OR SCALAR POINT %2 *** SYSTEM FATAL MESSAGE 2075 (DPD). 2075.4 DAREA SET ID = %1 HAS UNDEFINED GRID OR SCALAR POINT %2 *** SYSTEM FATAL MESSAGE 2075 (DPD). 2075.5 ALAR POINT %2 NOLINI SET ID = %1 HAS UNDEFINED GRID OR SC *** SYSTEM FATAL MESSAGE 2075 (DPD). 2075.6 NFTUBE SET ID = %1 HAS UNDEFINED GRID OR SCALAR POINT %2 *** SYSTEM FATAL MESSAGE 2075 (DPD). 2075.7 NOLIN5 SET ID = %1 HAS UNDEFINED GRID OR SCALAR POINT %2 SYSTEM FATAL MESSAGE 2075 (DPD). *** 2075.8 NLRGAP SET ID = %1 HAS UNDEFINED GRID OR SCALAR POINT %2 *** SYSTEM FATAL MESSAGE 2075 (DPD). 2075.9 TIC SET ID = %1 HAS UNDEFINED GRID OR SCALAR POINT %2 *** USER FATAL MESSAGE 2076 (USRMSG) 2076.0 ELEMENT %1 REFERENCES TABLES1 %2 WHICH IS THE INCORRECT FORM FOR NONLINEAR ELASTIC ANALYSIS. User information: The user has referenced a TABLES1 entry of FORM=1 which is plastic strains and slopes of the curve in the plastic region rather than FORM=0 w hich is a list of stress - strain data points. For FORM=0 tables, the second point was not at the yield location. Enter the correct table

145 form or change the MATS1 analysis type. *** SYSTEM FATAL MESSAGE 2077 (USRMSG) 2077.0 INVALID NONLINEAR EST APPENDAGE ENCOUNTERED FOR ELEMENT %1 AT LOCATION %2. System information: While processing the nonlinear EST data block, an appendage was located which did not conform to the bit specifications on the trailer, thus it could not be core area. This processed n the routine's open - is a possible user error. Regenerate the ESTNL data block from TA1. If this does not work, then the code must be reexamined for error. *** USER FATAL MESSAGE 2078 (USRMSG) 2078.0 SUFFICIENT NUMBER OF ENTRIES. TABLES1 ID.%1 HAS IN User information: The user has entered a nonlinear table composed of less than three points which implies that the plastic strain versus stress - strain slope appendage cannot be computed. Supply a TABLES1 with a minimum of three entries. *** USER FATAL MESSAGE 2079 (USRMSG) 2079.0 GRID OR SCALAR POINT %1 HAS AN ILLEGAL COMPONENT REFERENCED ON A %2 ENTRY. *** USER FATAL MESSAGE 2079 (GP1D) 2079.1 DAREA BULK DATA ENTRY %1 REFERENCES ILLEGAL COMPONENT %2 FOR %3 POINT ID %4 *** USER FATAL MESSAGE 2079 (DPD) 2079.2 EIGR ENTRY SET ID = %1 HAS AN ILLEGAL COMPONENT %2 REFERENCED ON A GRID OR SCALAR POINT %3 *** USER WARNING MESSAGE 2 080 (USRMSG) 2080.0 AN OBSOLETE CAPABILITY FOR %1 PROCESSING IS BEING USED. THIS CAPABILITY MAY BE DELETED IN THE NEXT SYSTEM. User information: As capabilities are replaced by newer technology, the old version is removed. Usually a system or two is allowed for removal. Currently the following capabilities are being considered for removal. PLOTTING The SC 4020 plotter ELEMENT The element entries CHEXA1, CHEXA2, CHEX8, CHEX20, CQDPLT, CQDMEM, CQUAD1, CQUAD2, CQDMEM1, CQDMEM2, CTRIA1, CTRIA2, CTRBSC, CTRPLT , CTRMEM and CWEDGE CNGRNT The CNGRNT Bulk Data entry. Before the next system release of NX NASTRAN, change your input to use the newer capabilities. *** USER FATAL MESSAGE 2081 (USRMSG) 2081.0 NULL DIFFERENTIAL STIFFNESS MATRIX. *** USER FATAL MESSAGE 2082 (USRMSG) 2082.0

146 PROJECTED OR CONCENTRATED LOAD USED ON BEND ELEMENT %1 User information: The PLOAD1 options for projected or concentrated loads are not supported for bend elements. *** USER FATAL MESSAGE 2083 (TA1NLE) . 2083.0 FOR NONLINEAR MATERIAL PROPERTIES REFERENCED ON THE PSHELL ENTRY, 12I/T3 FIELD MUST BE 1.0 (OR BLANK). *** USER FATAL MESSAGE 2083 (TA1NLE). 2083.1 FOR NONLINEAR MATERIAL PROPERTIES REFERENCED ON THE PSHELL ENTRY, MID4 MUST BE BLANK AND MID1 AND MID2 MUST REFERENCE THE SAME MAT1/MATS1 ENTRY COMBINATION. User information: For nonlinear material properties referenced on the PSHELL entry, MID4 must be blank and MID1 and MID2 must reference the same MAT1/MATS1 entry combination. *** USER FATAL MESSAGE 2083 (USRMSG) 2083.2 MATERIAL INPUT INCONSISTENT WITH NONLINEAR FORMULATION FOR ELEMENT %1 *** USER WARNING MESSAGE 2083 (TA1NLE) 2083.3 FOR ELEMENT %1 MID3 REFERENCE TO A MATS1 IS IGNORED BECAUSE NX NA STRAN SHELL THEORY IS A 2 - D REPRESENATION OF PLASTICITY. *** USER WARNING MESSAGE 2083 (TA1NLE) 2083.4 FOR ELEMENT %1 MID3 REFERENCE TO A MATS1 IS IGNORED BECAUSE NX NASTRAN SHELL THEORY IS A 2 D REPRESENATION - OF PLASTICITY. 0 TO LIMIT THE NUMBER OF MESSAGES, THE SET SYSTEM(634)> DEFAULT IS 100. SET SYSTEM(634)=0 TO SUPPRESS ALL THE MESSAGES, SET SYSTEM(634)= - 1 TO PRINT ALL THE MESSAGES. *** USER FATAL MESSAGE 2084 (USRMSG) 2084.0 GAP ELEMENT WITH ID. = %1 HAS ILLEGAL GEOMETRY OR CONN ECTIONS. User information: Bad CGAP geometry has been detected. Review CGAP element definition. *** SYSTEM FATAL MESSAGE 2085 (USRMSG) 2085.0 ELEMENT TYPE %1 NOT SUPPORTED FOR NONLINEAR ANALYSIS. System information: An element type not currentl y implemented was encountered on the data block ESTNL. This should be impossible unless the user inputs an EST data block with its trailer altered. *** USER WARNING MESSAGE 2086 (MODGM2) 2086.0

147 THE QUADR/TRIAR ELEMENTS ARE NOT AVAILABLE FOR THE NONLINEAR ANALYSIS. THEY ARE USED AS LINEAR ELEMENTS. *** USER FATAL MESSAGE 2086 (MODGM2) 2086.1 THE COMPOSITE SOLID ELEMENTS ARE ONLY AVAILABLE FOR SOL 101, 103, 105, 108, 109, 111, 112 AND 401. *** USER FATAL MESSAGE 2086 (MODGM2) 2086.2 THE PLANE STRESS & STRAIN ELEMENTS DO NOT SUPPORT SOL 114, 115, 116, 118, 144, 145, AND 146. *** USER FATAL MESSAGE 2086 (MODGM2) 2086.3 CURRENTLY, THE GENERALIZED PLANE STRAIN ELEMENTS ONLY SUPPORT SOL 401. *** USER FATAL MESSAGE 2086 (MODGM2) 2086.4 MICROPHONE ELEMENTS VIA THE PMIC BULK DATA ARE NOT ALLOWED FOR THIS ANALYSIS. *** USER FATAL MESSAGE 2086 (MODGM2) 2086.5 CUR RENTLY, THE COMPOSITE SHELL ELEMENTS REFERS TO PCOMPG1 ONLY SUPPORT SOL 401, 402. *** USER FATAL MESSAGE 2088 (USRMSG) 2088.0 DUPLICATE TABLE ID %1 User information: All tables must have unique numbers. Check for uniqueness. USER FATAL MESSAGE 2089 (USRMSG) *** 2089.0 TABLE %1 IS UNDEFINED. User information: The table number in the list of table numbers input to subroutine PRETAB with argument 7 was not found after reading the DIT data block. Check list of tables in the Bulk Data. *** SYSTEM FATAL MESSAGE 2090 (USRMSG) 2090.0 TABLE DICTIONARY ENTRY %1 IS MISSING. System information: Logic error in subroutine PRETAB, or open core used by PRETAB has been destroyed. *** SYSTEM WARNING MESSAGE 2092 (USRMSG) 2092.0 SDR2 FINDS A SYMMETRY SEQUENCE LENGTH =%1 AND AN INSUFFICIENT NUMBER OF VECTORS AVAILABLE =%2 WHILE ATTEMPTING TO COMPUTE STRESSES AND FORCES. ALL FURTHER STRESS AND FORCE COMPUTATION TERMINATED. System information: The number of SUBSEQ command coeffic ients must be less than or equal to the number of SUBCASES that precede the SUBCOM which contains the SUBSEQ command. Either increase the number of SUBCASEs or reduce the number of SUBSEQ coefficients. , *** USER FATAL MESSAGE 2093 --- 2093.0

148 NOLI N OR NLRGAP SET%1 REFERENCES GRID%2 COMPONENT%3 SIL%4 WHICH IS NOT IN UD SET. User information: Nonlinear loads can only be applied to points in the dynamic analysis set. *** USER WARNING MESSAGE 2094 (TABFMT) 2094.0 KEYNAME %1 NOT IN LIST OF AVAILABLE KEYNAMES. User information: Formatted table print is requested for a data block which is not coded in the module. *** USER WARNING MESSAGE 2099 (TABFMT) 2099.0 NUMWDS =%1 *** USER FATAL MESSAGE 2 101 (USRMSG) 2101.0 GRID POINT %1 COMPONENT %2 ILLEGALLY DEFINED IN SETS %3 %4 %5 %6 %7 %8 %9 *** USER FATAL MESSAGE 2101 (USRMSG) 2101.1 SCALAR POINT %1 ILLEGALLY DEFINED IN SETS %2 %3 %4 %5 %6 %7 %8 User information: The above grid point and component are defined in each of the above dependent subsets. A point may belong to a maximum of one dependent subset. This error occurs when a DOF is defined as belonging to two mutually exclusive sets. s occurs when a DOF is defined as dependent on A common example of thi an MPC (M set) as well as being constrained (s - set) on an SPC entry. - The message for this states that the component is illegally defined in set) sets. Thes the um (user set) and us (user - defined s - - e two defined m - sets are mutually exclusive because all MPC equations are processed - set DOFs before the SPCs are applied (exception is SOL 24) and the m are removed from the matrix. When the program attempts pply the SPC, FATAL message is issued. The the DOF is no longer available, and the normal correction for this is to modify the MPC so that the DOF in - set). Then there is no conflict. question is independent (N *** SYSTEM FATAL MESSAGE 2101 (GP4) 2101.2 GRID OR SCALAR POINT ID= %1 COMPONENT = %2 FOUN D ON THE MPC ENTRY IS ILLEGAL. USER ACTION: CHECK MPC ENTRIES. User information: The above scalar point has been defined in each of the above dependent subsets. A point may belong to at most one dependent subset. *** USER WARNING MESSAGE 2102 (USRMSG) 2102.0 LEFT HAND MATRIX ROW POSITION %1 OUT OF RANGE - IGNORED. LEFT HAND MATRIX ROW POSITION %2 OUT OF RANGE - IGNORED.

149 *** SYSTEM FATAL MESSAGE 2103 (USRMSG) 2103.0 SUBROUTINE MAT WAS CALLED WITH INFLAG=2, THE SINE OF THE ANGLE X MATERIAL ORIENTATION ANGLE, NON - ZERO, BUT, SIN(X)**2+COS(X)**2 DIFFERED FROM 1 IN ABSOLUTE VALUE BY MORE THAN .0001 . *** USER FATAL MESSAGE 2104 (USRMSG) 2104.0 SYSTEM %1 UNDEFINED COORDINATE *** USER FATAL MESSAGE 2105 (USRMSG) 2105.0 PLOAD2 CARD FROM LOAD SET %1 REFERENCES MISSING OR - 2 - D ELEMENT OR HYPERELASTIC PLANE ELEMENT %2 NON User information: - PLOAD2 entries must reference two dimensional elements and not reference hyperelastic elements. *** USER FATAL MESSAGE 2106 (USRMSG) 2106.0 - UNIQUE LOAD SET %1 LOAD ENTRY DEFINES NON User information: All load sets must have unique identification numbers. *** USER FATAL MESSAGE 2107 (USRMSG) 2107.0 EIG - ENTRY FROM SET %1 REFERENCES DEPENDENT COORDINATE OF GRID POINT %2 User information: When the point option is used on an EIGR entry, the referenced point and component must be set) for use in normalization. in the analysis set (a - *** USER WARNING MESSAGE 2108 (USRMSG) 2108.0 SPCD ON A POINT NOT IN S SET. GRID %1 COMP. %2 *** USER FATAL MESSAGE 2109 (USRMSG) 2109.0 NO GRID, SCALAR, OR EXTRA POINTS DEFINED. User information: Dynamics problems must have at least one grid, scalar, or extra point. *** USER WARNING MESSAGE 2111 (USRMSG) 2111.0 BAR %1 COUPLED BENDING INERTIA SET TO 0.0 IN DIFFERENTIAL STIFFNESS. *** SYSTEM FATAL MESSAGE 2112 (USRMSG) 2112.0 ATTEMPT TO USE TABLE PROCESSING FOR MATERIAL %1 WHEN NO TABLE SUPPLIED. System information: This error occurs in nonlinear analysis when, for a given value of strain, a table lookup was requested but the user did not supply a table. Make sure that tables refer enced by MATS1 or CREEP entries are supplied. *** USER FATAL MESSAGE 2113 (USRMSG) 2113.0 ELEMENT %1 REFERENCED MATID %2 WHICH CANNOT BE USED

150 TO OBTAIN REQUIRED PROPERTIES. User information: A search procedure in MAT allows any possible MATi entry to be referenced under any INFLAG. However, only certain material formats can be used to construct the required output in /MATOUT/. Make certain the element can reference the material entry type. *** USER WARNING MESSAGE 2114 (USRMSG) 2114.0 THE VALUE OF PARAMETER F12 DOES NOT SATISFY THE STABILITY CRITERION FOR ELEMENT %1 PLY %2 User information: Failure theory calculations for the noted element/ply were not calculated. The value of the parameter F12 did not satisfy the following equations for Tsai - Wu failure theory: - F12 ** 2 > 0 (1/(Xt * Xc)) * (1/(Yt * Yc)) Change the value of the parameter F12. *** USER WARNING MESSAGE 2114 (USRMSG) 2114.1 THE VALUE OF PARAMETER F12 DOES NOT SATISFY THE STABILITY CRITERION FOR THE WU FAILURE THEORY FOR MATERIAL %1. TSAI - The value of the parameter F12 did not satisfy the following equation for - Wu failure theory. Tsai - F12 ** 2 > 0 (1/(Xt * Xc)) * (1/(Yt * Yc)) The parameter F12 will b e set zero for ply failure calculations. *** USER WARNING MESSAGE 2114 (USRMSG) 2114.2 THE VALUE OF PARAMETER F23 DOES NOT SATISFY THE STABILITY CRITERION FOR THE - TSAI WU FAILURE THEORY FOR MATERIAL %1. The value of the parameter F23 did not satisfy the following equation for Tsai - Wu failure theory. - (1/(Zt * Zc)) * (1/(Yt * Yc)) F23 ** 2 > 0 The parameter F23 will be set zero for ply failure calculations. *** USER WARNING MESSAGE 2114 ( USRMSG) 2114.3 THE VALUE OF PARAMETER F13 DOES NOT SATISFY THE STABILITY CRITERION FOR THE TSAI - WU FAILURE THEORY FOR MATERIAL %1. The value of the parameter F13 did not satisfy the following equation for - Wu failure theory. Tsai - F13 ** 2 > 0 (1/(Xt * Xc)) * (1/(Zt * Zc)) The parameter F13 will be set zero for ply failure calculations. *** USER FATAL MESSAGE 2115 (USRMSG) 2115.0 TABLE %1 (TYPE%2) ILLEGAL WITH STRESS DEPENDENT - MATERIAL. User information: Only TABLES1 entries may be used to define stress - strain curves for

151 use in piecewise linear analysis. *** USER FATAL MESSAGE 2116 (USRMSG) 2116.0 ALL TABLES MUST BE SUPPLIED FOR CREEP ENTRY %1. User information: When the table option is selected for CREEP analysis, all possible table fields must be supplied. *** SYSTEM FATAL MESSAGE 2117 (USRMSG) 2117.0 LOGIC ERROR, ELEMENT %1 MATERIAL %2 REQUIRES A MATS1 OR CREEP ENTRY WHICH WAS NOT LOADED. System information: Normally, module TA1 det ermines which types of analysis are possible for an element based upon which material is referenced. The processing routine has requested processing other than that for which the element was flagged. Review references to MATS1 or CREEP entries by MATi entries. *** USER FATAL MESSAGE 2120, 2120.0 - - ZERO. I = %1 MODULE VEC BOTH SUBSET BITS ARE NON User information: Possible error in partitioning set definition. *** USER FATAL MESSAGE 2121, 2121.0 - MODULE VEC BOTH SUBSET BITS ARE ZERO. I = %1 User information: Possible error in partitioning set definition. *** USER FATAL MESSAGE 2122, 2122.0 - MODULE VEC SET X BIT IS ZERO BUT SUBSET X0 BIT IS NOT. I = %1 User information: in partitioning set definition. Possible error *** USER FATAL MESSAGE 2123, 2123.0 - SET X BIT IS ZERO BUT SUBSET X1 BIT IS NOT. I = MODULE VEC %1 User information: Possible error in partitioning set definition. *** USER WARNING MESSAGE 2124, 2124.0 MODULE VEC - NR=0, OUTPUT WILL BE PURGED. User information: Requested partitioning vector is null. *** USER WARNING MESSAGE 2125, 2125.0 MODULE VEC - NZ=0, ONE OR MORE COLUMNS OF OUTPUT MATRIX WILL BE NULL. User information: Requested partitioning vector is full. *** USER FATAL MESSAGE 2126 (USRMSG) 2126.0

152 UNDEFINED MATERIAL FOR ELEMENT %1 *** USER FATAL MESSAGE 2131 (USRMSG) 2131.0 SCALAR ELEMENT %1 REFERENCES A SCALAR POINT. NON - User information: An element which must be attached to a geometric grid point has been attached to a scalar point. No geometry data can be inferred. *** USER FATAL MESSAGE 2132 (USRMSG) 2132.0 ZERO SINGLE POINT CONSTRAINT VALUE SPECIFIED BUT NON - RGED. DATA BLOCK YS IS PU *** USER FATAL MESSAGE 2133 (USRMSG) 2133.0 INITIAL CONDITION IN SET %1 SPECIFIED FOR POINT NOT IN ANALYSIS SET. User information: Initial conditions can only be specified for analysis set points. Therefore the point/component mentioned on TIC entries must or h - sets. belong to the d - *** USER FATAL MESSAGE 2133 (DPD4) 2133.1 INITIAL CONDITION IN SET %1 SPECIFIED COMPONENT %2 ON POINT %3 IS NOT IN ANALYSIS SET. User information: onditions can only be specified for analysis set points. Initial c Therefore the point/component mentioned on TIC entries must belong to the d - or h - sets. *** USER FATAL MESSAGE 2134 (USRMSG) 2134.0 LOAD OR DEFORM SET %1 DEFINED FOR BOTH GRAVITY AND NON G RAVITY LOADS. - User information: The same load set identification number cannot appear on both a GRAV entry and another loading entry such as FORCE or MOMENT. To apply both a gravity load and a concentrated load simultaneously, the LOAD entry must be u sed. *** USER FATAL MESSAGE 2134 (GP1D) 2134.1 DAREA BULK DATA ENTRY %1 IS THE SAME AS A LOAD OR GRAV BULK DATA ENTRY *** USER FATAL MESSAGE 2135 (USRMSG) 2135.0 DLOAD CARD %1 HAS A DUPLICATE SET ID FOR SET ID %2. User information: The Li Set IDs on a DLOAD entry are not unique. See the DLOAD Bulk Data description. *** USER FATAL MESSAGE 2136 --- 2136.0 DUPLICATE %1 SET ID NUMBER =%2 HAS BEEN ENCOUNTERED FOR %3 SET =%4 User information: Dynamic loads may not be combined by giving multiple data entries

153 with the same ID. Use unique IDs. *** USER FATAL MESSAGE 2136 (DPD2) 2136.1 %1 SET ID %2 HAS BEEN DUPLICATED ON A %3 CARD. *** USER FATAL MESSAGE 2137 (USRMSG) 2137.0 PROGRAM RESTRICTION FOR MODULE %1. ONLY 300 LOAD SET ID'S ALLOWED. DATA CONTAINS %2 LOAD SET ID'S. *** USER FATAL MESSAGE 2138 (USRMSG) 2138.0 ELEMENT IDENTIFICATION NUMBER %1 IS TOO LARGE. *** USER WARNING MESSAGE 2139 (USRMSG) 2139.0 ELEMENT %1 IN DEFORM SET %2 IS UNDEFINED. User information: A selected element deformation set includes an element twice, - includes a non existent element, or includes a non includes a non - one - dimensional element. *** USER FATAL MESSAGE 21 40 (USRMSG) 2140.0 GRID POINT OR SCALAR POINT ID %1 IS TOO LARGE. User information: This is a program restriction on the size of integer numbers. An entry defining a grid point or scalar point has a number larger than the maximum of 2,000,000. *** USER INFORMATION MESSAGE 2141, 2141.0 HOUSEHOLDER TIME ESTIMATE IS %1 SECONDS. PROBLEM SIZE IS %2 . *** USER INFORMATION MESSAGE 2141, 2141.1 GIVENS TIME ESTIMATE IS %1 SECONDS. PROBLEM SIZE IS %2, SPILL WILL OCCUR FOR THIS CORE AT A PROBLEM SIZE OF %3 . User information: The time estimate includes the time of the tridiagonalization and eigenvalue calculation when the GIV or HOU methods are used. If ND is given on the EIGR ent ry, it also includes the time of the eigenvector generation. If F1 and F2 are used instead, the eigenvector times *** USER FATAL MESSAGE 2142, 2142.0 INSUFFICIENT CORE FOR MODULE VEC. AVAILABLE CORE = %1 WORDS. ADDITIONAL CORE NEEDED = %2 WORDS. User information: Additional main memory is needed to execute module VEC. *** USER FATAL MESSAGE 2143, 2143.0 MODULE VEC UNABLE TO IDENTIFY SET OR SUBSET DESCRIPTOR %1 User information: Illegal set name for partitioning vector definition.

154 *** USER FATAL MESSAGE 2145, 2145.0 %1 FATAL MESSAGES HAVE BEEN GENERATED IN SUBROUTINE VEC. ONLY THE FIRST %2 HAVE BEEN PRINTED. User information: Only a limited number of error messages are printed. *** USER FATAL MESSAGE 2146, 2146.0 BOTH OF THE SECOND AND THIRD VEC PARAMETERS REQUEST COMPLEMENT. User information: Illegal definition of partitioning vector. *** USER FATAL MESSAGE 2150, 2150.0 ILLEGAL VALUE FOR FOURTH PARAMETER = %1 *** USER WARNING MESSAGE 2154, 2154.0 ZERO AREA OR ILLEGAL CONNECTION FOR %1 ELEMENT NUMBER.%2 User information: Possible error on connection entry or property entry. *** USER WARNING MESSAGE 2154, 2154.1 ZERO AREA OR ILLEGAL CONNECTION FOR ELEMENT NUMBER.%1 User information: Possi ble error on connection entry or property entry. *** USER WARNING MESSAGE 2155, 2155.0 MAT4 AND MAT5 MATERIAL DATA CARDS HAVE SAME ID =%1 MAT4 DATA WILL BE SUPPLIED WHEN CALLED FOR THIS ID. User information: The same identification number has been used for an isotropic and an anisotropic material. *** USER FATAL MESSAGE 2157, 2157.0 MATERIAL ID =%1 FOR ELEMENT ID = %2 DOES NOT APPEAR ON ANY RADM RADIATION MATERIAL DATA CARD User information: Materi al properties required for thermal matrix generation are not present in the Bulk Data. *** USER FATAL MESSAGE 2157, 2157.1 MATERIAL ID =%1 FOR ELEMENT ID = %2 DOES NOT APPEAR ON ANY MAT4 OR MAT5 MATERIAL DATA CARD. User information: Material pr operties required for thermal matrix generation are not present in the Bulk Data. *** USER FATAL MESSAGE 2160 (ESLTD) 2160.0

155 BAD GEOMETRY OR ZERO COEFFICIENT FOR SLOT ELEMENT NUMBER %1 User information: Possible error on GRID entry or connection entry. *** USER FATAL MESSAGE 2161, 2161.0 PARTITION FILE %1 IS OF SIZE%2 ROWS BY%3 COLS. PARTITIONING VECTORS INDICATE THAT THIS PARTITION SHOULD BE OF SIZE%4 ROWS BY%5 COLUMNS FOR A SUCCESSFUL MERGE. U ser information: Check RP and CP sizes for MERGE. *** USER WARNING MESSAGE 2162, 2162.0 THE FORM PARAMETER AS GIVEN TO THE MERGE MODULE IS INCONSISTENT WITH THE SIZE OF THE MERGED MATRIX, HOWEVER IT HAS BEEN USED. FORM =%1 SIZE MNS. =%2 ROWS BY%3 COLU User information: Use square forms for square matrices, etc, or use FORM=0. *** USER WARNING MESSAGE 2163, 2163.0 REQUESTED VALUE OF %1%2 %3USED BY %4. LOGICAL CHOICE IS%5 User information: The type of the output matrix is not consistent with the precision of the computer. *** USER FATAL MESSAGE 2166, 2166.0 MATRIX TO BE PARTITIONED IS OF SIZE%1 ROWS BY%2 COLUMNS. ROW PARTITION SIZE IS %3 COLUMN PARTITION SIZE IS %4 (INCOMPATIBLE). User information: The RP or CP matrices do not match the incoming matrix size. Check the DMAP and DIAG 8 output. Note that in versions prior to V65C, the size of the partitioning vector did not have to be compatible with the matrix being partitioned. This was changed starting with V65C, when a warning message was issued. Starting with V67.5, this was changed to a fatal message. *** USER WARNING MESSAGE 2168, 2168.0 THE FORM PARAMETER AS GIVEN TO THE PARTITIONING MODULE FOR SUB - PARTITION %1 I S INCONSISTENT WITH ITS SIZE. FORM =%2 SIZE =%3 ROWS BY%4 COLUMNS. User information: Either use FORM=0, or label square results square, etc. *** USER FATAL MESSAGE 2170, 2170.0

156 BOTH THE ROW AND COLUMN PARTITIONING VECTORS ARE PURGED AND ONLY ONE MAY BE PURGED. User information: Check your DMAP PARTN or MERGE for loss of both RP and CP. *** USER WARNING MESSAGE 2171, 2171.0 SYM FLAG INDICATES TO THE PARTN OR MERGE MODUL E THAT A SYMMETRIC MATRIX IS TO BE OUTPUT. THE PARTITIONING VECTORS%1 HOWEVER DO NOT - ZEROS. CONTAIN AN IDENTICAL NUMBER OF ZEROS AND NON User information: Do not specify both RP and CP if a symmetric partition is desired. *** USER WARNING MESSAGE 2172, 2172.0 ROW AND COLUMN PARTITIONING VECTORS DO NOT HAVE IDENTICAL ORDERING OF ZERO AND NON - ZERO ELEMENTS, AND SYM FLAG INDICATES THAT A SYMMETRIC PARTITION OR MERGE IS TO BE PERFORMED. User information: Do not specify both RP and CP if a symmetri c partition is desired. *** USER WARNING MESSAGE 2173, 2173.0 PARTITIONING VECTOR FILE%1 CONTAINS %2 COLUMNS. THE FIRST COLUMN WILL BE USED, NOT THE REQUESTED COLUMN%3 User information: The COLNO parameter has been set longer than the number of columns in RP or CP in the PARTN or MERGE modules. *** USER WARNING MESSAGE 2174, 2174.0 - PARTITIONING VECTOR ON FILE%1 IS NOT REAL SINGLE OR REAL - DOUBLE PRECISION. User information: Part itioning vectors may not be complex for the PARTN or MERGE modules. *** SYSTEM WARNING MESSAGE 2184, 2184.0 STRESS OR FORCE REQUESTS FOR ELEMENT TYPE =%1 WILL NOT BE HONORED AS THIS ELEMENT IS UNDEFINED TO SDR2. *** USER FATAL MESSAGE 2187 (OUTPX2) 2187.0 INSUFFICIENT WORKING CORE TO HOLD FORTRAN LOGICAL RECORD IN MODULE %1. LENGTH OF WORKING CORE = %2, LENGTH OF FORTRAN LOGICAL RECORD = %3. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USE R FATAL MESSAGE 2187 (OUTPN2) 2187.1

157 INSUFFICIENT WORKING CORE TO HOLD FORTRAN LOGICAL RECORD IN MODULE %1. LENGTH OF WORKING CORE = %2, LENGTH OF FORTRAN LOGICAL RECORD = %3. *** USER FATAL MESSAGE 2187 2187.2 INSUFFICIENT WORKING CORE TO HOLD FORTRAN LOGICAL RECORD. LENGTH OF WORKING CORE = %1, LENGTH OF FORTRAN LOGICAL RECORD = %2. *** SYSTEM FATAL MESSAGE 2190 (OUTPX2) 2190.0 ILLEGAL VALUE FOR KEY =%1. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTO MER SUPPORT. *** SYSTEM FATAL MESSAGE 2190 (OUTPX2) 2190.1 ILLEGAL VALUE FOR KEY =%1, EXPECTED VALUE = %2. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 2190 2190.2 ILLEGAL VALUE FOR KEY =%1. *** SYSTEM FATAL MESSAGE 2190 2190.3 ILLEGAL VALUE FOR KEY =%1, EXPECTED VALUE = %2. *** SYSTEM FATAL MESSAGE 2190 2190.4 ILLEGAL VALUE FOR KEY =%1. *** SYSTEM FATAL MESSAGE 2190 (INPTN2) 2190.7 ILLEGAL VALUE FOR KEY = %1. *** USER FATAL MESSAGE 2192 (USRMSG) 2192.0 UNDEFINED GRID POINT %1 IN RIGID ELEMENT %2 *** USER FATAL MESSAGE 2193 (USRMSG) 2193.0 A REDUNDANT SET OF RIGID BODY MODES WAS SPECIFIED FOR THE GENERAL ELEMENT. User information: Only a non - redundant list o f rigid body modes is allowed to appear in the ud set when the S matrix is to be internally calculated in subroutine TA1CA. *** USER FATAL MESSAGE 2194 (USRMSG) 2194.0 A MATRIX D IS SINGULAR IN SUBROUTINE TA1CA. User information: While attempting to calculate the [S] matrix for a general element in TA1CA, it was discovered that the matrix Dd which relates ub to ud was singular and could not be inverted. *** USER FATAL MESSAGE 2195 (TIMTST) 2195.0 ILLEGAL VALUE FOR P4 =%1

158 *** SYSTEM FATAL MESSAGE 2197, 2197.0 ABORT CALLED DURING TEST TEST OF %1 *** SYTEM FATAL MESSAGE 2198 (USRMSG) 2198.0 INPUT DATA BLOCK %1 HAS BEEN PURGED. *** SYTEM FATAL MESSAGE 2199 (USRMSG) 2199.0 SUMMARY, ONE OR MORE OF THE ABOVE FATAL ERRORS WAS ENCOUNTERED IN SUBROUTINE %1. *** USER FATAL MESSAGE 2200, 2200.0 INCONSISTENT RIGID BODY SYSTEM. User information: - body mass matrix is not positive definite. Possible The rigid causes are uncon strained mechanisms or input of negative mass terms. A diagnostic method is to remove all SUPORT entries and inspect the resulting eigenvectors for implausible behavior. *** USER WARNING MESSAGE 2251 (IFS1P) 2251.0 ONE OR MORE MAT1 ENTRIES HAVE UNREASONABLE OR INCONSISTENT VALUES OF E,G OR NU. ID OF FIRST ONE = %1 User information: Potentially bad elastic constants have been defined on one or more MAT1 entries. Checks are made for (a) any of E << 0.0, G << 0.0, ( unless two of the three data fields are blank). Verify that the values defined are meaningful for the designated application. *** USER WARNING MESSAGE 2251 (IFS1P) 2251.1 THE NUMBER OF MAT1 ENTRIES HAVING UNREASONABLE OR INCONSISTENT VALUES FOR E, G AND/OR NU IS %1 ID OF LAST ONE = %2 User information: See Message 2251.0. Check all MAT1 entries in the range indicated for the ones with potentially bad elastic constants. These values should be verified for application suitability. **USER WARNING MESSAGE 2257, * 2257.0 SET %1 IS EMPTY. User information: While processing the SET1 or SET2 entry referenced on the SPLINEi entry, no included grid points were found. If SET1 was used, either no points were included or they were all scalar point s. If SET2 was used, the volume of space referenced did not include any structural grid points. This may occur if a tapered element is extended too far. The spline is omitted from the problem and processing continues. ***USER FATAL MESSAGE 2258, 2258.0 SET %1 REFERENCED ON SPLINE CARD %2 NOT FOUND. User information: The necessary SET1 or SET2 entry was not found. Include the proper SET entry.

159 *** USER FATAL MESSAGE 2258 (APD0) 2258.1 SPLINE ENTRY ID = SET ENTRY ID = %1 THAT IS REFERENCED ON %2 WAS NOT FOUND. *** USER FATAL MESSAGE 2258 (GISPL) 2258.2 %1 %2 REFERENCED ON SPLINE CARD %3 NOT FOUND. ***SYSTEM FATAL MESSAGE 2259, 2259.0 POINT ASSIGNED TO BOX %1 FOR CAERO1 %2 NOT IN ECTA. System information: No internal k point could be found for external box. If box number is correct, module APD is in error; if box number is incorrect, module GI is in error. *** USER FATAL MESSAGE 2260 2260.0 SINGULAR MATRIX DEVELOPED WHILE PROCESSING SPLINE%1 User information: Matrix developed by SSPLIN or LSPLIN (depending on type of spline) could not be inverted; possibly for the surface spline all points lie in a straight line, or not enough points are included. *** USER FATAL MESSAGE 2261 (L1SPLD) 2261.0 PLANE OF LINEAR SPLINE %1 PERPENDICULAR TO PLANE OF AERO ELEMENT %2 User information: Y - axis of linear spline was perpendicular to connected element and could not be projected onto element. MESSAGE 2262 (GIPUSG) *** USER FATAL 2262.0 SPLINE %1 CONTAINS AERO BOX CONTAINED ON AN EARLIER SPLINE. User information: Two splines are attached to the same box. Splines must be connected to the same structural grid point but not the same aerodynamic grid point. e of error checking will stop with one error, so check this spline This typ and subsequent splines (sorted) for overlaps before resubmitting. *** USER FATAL MESSAGE 2263 2263.0 INSUFFICIENT CORE TO PROCESS SPLINE%1 User information: Depending on type of spline and input options, subroutine SSPLIN, or LSPLIN would not have had enough core for this spline. Either allow more core or break this spline into smaller splines. *** SYSTEM FATAL MESSAGE 2264, 2264.0 NUMBER OF ROWS COMPUTED (%1) WAS GREATER THAN SIZE REQUESTED FOR OUTPUT MATRIX (%2). System information: Module ADD determines size of output matrices (j set size). Sum of number of rows added by different method total more than maximum allowed.

160 *** USER FATAL MESSAGE 2266 (FA1) 22 66.0 ONE OR MORE OF THE FOLLOWING FLFACT SETS WERE NOT FOUND %1 - User information: One or more of the FLFACT IDs on the FLUTTER entry could not be found. Include all sets mentioned. *** USER FATAL MESS AGE 2266 (DOPR3I) 2266.1 FLUTTER ENTRY ID = %1 REFERENCES A FLFACT BULK DATA ENTRY ID = %2 WHICH cannot be found. *** USER FATAL MESSAGE 2267 (FA1) 2267.0 INTERPOLATION METHOD %1 UNKNOWN. User information: Matrix interpolation method on FLUTTER entry is not implemented. *** USER FATAL MESSAGE 2268 (FA1) 2268.0 FMETHOD SET %1 NOT FOUND. User information: FLUTTER entry for FMETHOD = %1 in case control could not be found. MESSAGE 2269 (FA1) *** USER FATAL 2269.0 FLUTTER METHOD %1 NOT IMPLEMENTED. *** USER WARNING MESSAGE 2269 (FA1) 2269.1 THE KE FLUTTER METHOD DOES NOT SUPPORT A BHH MATRIX AND THESE DATA ARE IGNORED. USER ACTION: DELETE THE INPUT DATA WHICH GENERATES THE BHH MATRIX OR USE AN ALTERNATIVE FLUTTER METHOD (PK OR K ). ***USER FATAL MESSAGE 2270, 2270.0 LINEAR INTERPOLATION WITHOUT ENOUGH IND. MACH NUMBERS EQUAL TO DEP. MACH %1 User information: L inear interpolation is for points with the same Mach number, and less than two more found from QHHL list which matched the requested Mach on an FLFACT entry. ***USER FATAL MESSAGE 2271, 2271.0 INTERPOLATION MATRIX IS SINGULAR User information: Possibly for the surface spline, all the Mach numbers were the same, or for either method, not enough points were included. The range of Mach numbers and reduced frequencies must be larger on the MKAEROi entry than on the FLFACT entry. *** USER FATAL MESSAGE 2286. (SSGSLB) 2286.0 ELEMENT %1 REFERENCED ON PLOAD1 %2 NOT FOUND User information: An element identification number is referenced on a PLOAD1 entry which does not exist on either a CBAR or CBEAM Bulk Data entry.

161 RNING MESSAGE 2317, *** USER WA 2317.0 PARAM HAS STORED OUTSIDE DEFINED RANGE OF COMMON BLOCK /SYSTEM/. INDEX VALUE = %1 *** USER FATAL MESSAGE 2318 (APD0) 2318.0 NO %1 ENTRY FOUND FOR %2 AEROELASTIC ANALYSIS. USER INFORMATION: AN %3 ENTRY IS REQUIRED FOR %4 AEROELASTIC ANALYSIS. *** USER FATAL MESSAGE 2319 (APD0) 2319.0 NO CAERO ENTRIES FOUND. User information: At least one CAERO MESSAGE entry is required for module APD. USER FATAL MESSAGE 2322 (APD0) *** 2322.0 NEITHER MKAERO1 OR MKAERO2 ENTRIES FOUND. User information: Either MKAERO1 or MKAERO2 entries are required. *** USER FATAL MESSAGE 2323 (APD12) 2323.0 PAERO %1 ENTRY ID = %2 THAT IS REFERENCED BY CAERO %3 ENTRY ID = %4 DOES NOT EXIST. *** USER FATAL MESSAGE 2324 (MKSPL) 2324.0 CAERO ENTRY ID = %1 THAT IS REFERENCED ON SPLINE %2 ENTRY ID = %3 DOES NOT EXIST. User information: Either a SPLINE1 or a SPLINE2 entry references a CAERO1 entry which is missing. *** USER FATAL MESSAGE 2325 (MKSPLN) 2325.0 CAERO ENTRY ID = %1 THAT IS REFERENCED ON SET2 ENTRY ID = %2 DOES NOT EXIST. User information: A SET2 entry points to a CAERO1 which was not included. *** USER FATAL MESSAGE 2326 (APD12) 2326.0 AEFACT ENTRY ID = %2 THAT IS REFERENCED ON CAERO1 ENTRY ID = %1 DOES NOT EXIST. *** USER FATAL MESSAGE 2326, 2326.1 DUPLICATE %1 DIVISIONS FOUND ON AEFACT ID = %2. *** USER FATAL MESSAGE 2328 (MKSPL) 2328.0 NO SPLINES ENTRIES HAVE BEEN FOUN D. USER INFORMATION: SPLINE ENTRIES ARE REQUIRED FOR AEROELASTIC ANALYSIS. *** USER FATAL MESSAGE 2329 (APD0) 2329.0 DUPLICATE EXTERNAL MESHING POINT GRID ID = %1 GENERATED. User information:

162 The external ID's assigned to each generated box must be unique, and different from any grid or scalar point ID. *** USER FATAL MESSAGE 2329 (APD0) 2329.1 DUPLICATE EXTERNAL AERO GRID (BOX) ID = %1 GENERATED. User information: The external ID's assigned to each generated box must be unique, and different from any grid or scalar point ID. *** USER FATAL MESSAGE 2329 (APD0) 2329.2 DUPLICATE EXTERNAL INTERFERENCE ELEMENT CENTER POINT ID = %1 GENERATED. *** USER FATAL MESSAGE 2330 (APD0) 2330.0 USER INFORMATION: SET1 OR SPLINE3 ENTRY NO. %1 REFERENCES EXTERNAL ID NO. %2 WHICH DOES NOT EXIST. User information: External ID on SET1 or SPLINE3 entry does not exist as structural grid point. *** USER FATA L MESSAGE 2331 (MKSPL) 2331.0 BOXES PICKED ON SPLINE%1 ENTRY ID = %2 HAVE NOT BEEN GENERATED BY CAERO ENTRY ID = %3. USER INFORMATION: CAERO ENTRY ID = %4 GENERATES BOXES %5 to %6. *** SYSTEM INFORMATION MESSAGE 2333 (DDRMM) 2333.0 ED WITH VARIABLE IERROR = %1 MODULE DDRMM TERMINAT USE PARAM,DDRMM, - 1 TO SKIP USE OF MODULE DDRMM. System information: IERROR CODE CAUSE ----- ----------- 2 Frequency list is empty probably due to DMAP error *** USER WARNING MESSAGE 2334. (DDRMM - 3) 2334.0 ILLEGAL MAJOR OR MINOR OFP ID IDENTIFICATIONS = %1 - DETECTED IN DATA BLOCK%2. PROCESSING OF SAID DATA BLOCK DISCONTINUED. *** USER WARNING MESSAGE 2335. (DDRMM1 - 1) 2335.0 THE AMOUNT OF DATA IS NOT CONSISTENT FOR EACH EIGENVALUE IN DATA BLOCK %1 PROCESSING OF THIS DATA BLOCK TERMINATED. *** USER WARNING MESSAGE 2336. (DDRMM1 - 2) 2336.0 A CHANGE IN WORD 2 OF THE OFP - ID RECORDS OF DATA BLOCK %1 HAS BEEN DETECTED. PROCESSING OF THIS DATA BLOCK HAS BEEN TERMINATED. 2) *** USER WARNING MESSAGE 2337. (DDRMM2 - 2337.0 DATA BLOCK%1 CAN NOT BE PROCESSED DUE TO A MEMORY INSUFFICIENCY OF APPROXIMATELY%2 DECIMAL

163 WORDS. - *** USER WARNING MESSAGE 2338. (DDRMM2 3) 2338.0 DATA BLOCK%1 MAY NOT BE FULLY COMPLETED DUE TO A FICIENCY MEMORY INSUF OF APPROXIMATELY%2 DECIMAL WORDS. *** USER WARNING MESSAGE 2339. (DDRMM2 - 1) 2339.0 A CHANGE IN WORD 2 OF THE OFP ID RECORDS OF DATA BLOCK - %1 HAS BEEN DETECTED. PROCESSING OF THIS DATA BLOCK HAS BEEN TERMINATED. *** USER INFORMATION MESSAGE 2340 2340.0 MODULE %1 HAS BEEN REQUESTED TO DO UNSYMMETRIC DECOMPOSITION OF A SYMMETRIC MATRIX. User information: The matrix to be solved has a matrix trailer that indicates that it is symmetric ("FORM=6"). The DMAP call requests that the unsymmetric decomposition algorithm be used. The symmetric algorithm is more economical that the unsymmetric algorithm, and unconditionally stable for positive - definite matrices. Change the DMAP call to request symmetric decomposition, unless it is known that the unsymmetric algorithm is required. *** USER WARNING MESSAGE 2340 (TCSSLV) 2340.1 TCSSLV MATRIX GENERATION FAILED. FALL BACK TO NXN WITHOUT TAUCS. *** USER WARNING MESSAGE 2340 (TCSSLV) 2340.2 TCSSLV DECOMPOSITION FAILED. M ATRIX MAY BE INDEFINITE. FALL BACK TO NXN WITHOUT TAUCS. *** USER FATAL MESSAGE 2340 (TCSSLV) 2340.3 MIXED TYPE (COMPLEX RIGHT HAND SIDE AND REAL MATRIX) IS NOT SUPPORTED BY TAUCS FBS. *** USER FATAL MESSAGE 2340 (TCSSLV) 2340.4 TCSSLV FBS FAILED. *** USER FATAL MESSAGE 2340 (TCSSLV) 2340.5 TCSSLV FBS RIGHT HAND SIDE GENERATION FAILED. *** USER INFORMATION MESSAGE 2341 2341.0 MODULE %1 HAS BEEN FURNISHED A SQUARE MATRIX MARKED UNSYMMETRIC FOR SYMMETRIC DECOMPOSITION. User information: The module has been instructed to perform the symmetric decomposition algorithm in the DMAP call, but the trailer of the input matrix indicates that it is not of Form 6. If the matrix should be symmetric, a MODTRL modu le call can be scheduled before the module to convert the matrix trailer to Form 6. If this message is encountered in a

164 solution sequence,it is a signal that a solution is being requested . for a system (unsymmetric matrices) for which it was not designed Wrong answers may result if the solution is forced through with the MODTRL technique. *** SYSTEM WARNING MESSAGE 2342. (GPFDCC) 2342.0 UNRECOGNIZED DMAP APPROACH PARAMETER = %1 USER INFORMATION: NO GPFORCE, ESE, EKE OR EDE RESULTS WILL BE PRIN TED. *** SYSTEM FATAL MESSAGE 2342 (APCODE) 2342.1 UNRECOGNIZED DMAP APPROACH PARAMETER = %1 USER INFORMATION: AVAILABLE NAMES ARE %2 %3 %4 %5 %6 %7 %8 %9 %10 %11 *** SYSTEM WARNING MESSAGE 2342. (GPFDCC) 2342.2 UNSUPPORTED DMAP APPROACH PARAMETER = %1 USER INFORMATION: NO GPFORCE, ESE, EKE OR EDE RESULTS WILL BE PRINTED. *** SYSTEM WARNING MESSAGE 2343. (GPFDR) 2343.0 DATA BLOCK %1 IS EITHER NOT - EQEXIN - OR POSSIBLY INCORRECT. SYSTEM WARNING MESSAGE 2344. (GPFDR) *** 2344.0 GPFDR FINDS A SYMMETRY SEQUENCE LENGTH %1 WHILE ATTEMPTING TO COMPUTE GRID POINT FORCES AND ENERGIES. THERE IS AN INSUFFICIENT NUMBER OF VECTORS AVAILABLE %2. *** SYSTEM WARNING MESSAGE 2345. (GPFDR) 2345.0 FDR FINDS AND IS IGNORING UNDEFINED ECT DATA WITH GP LOCATE NUMBERS = %1 *** SYSTEM WARNING MESSAGE 2346. (GPFDR) 2346.0 DATA FOR ELEMENT TYPE = %1 IN DATA BLOCK %2 IS NOT IN AGREEMENT WITH THAT WHICH IS EXPECTED. SYSTEM WARNING MESSAGE 2347. (GPFDR) *** 2347.0 TOO MANY ACTIVE CONNECTING GRID POINTS FOR ELEMENT ID = %1 *** USER INFORMATION MESSAGE 2348. (GPFTDL) 2348.0 THERMAL (TEMPij) AND ELEMENT DEFORMATION (DEFORM) LOADS ARE IGNORED IN THE CALCULATION OF GRID POINT FORCES AND ELEMENT ENERGIES IN FREQUENCY AND TRANSIENT RESPONSE ANALYSIS. *** SYSTEM WARNING MESSAGE 2349. (GPFDR) 2349.0 FINDS AN ELEMENT ENTRY CONNECTING PIVOT SIL =%1 ON DATA BLOCK%2 TOO LARGE FOR A LOCAL ARRAY. ENTRY IS BEING IGNORED. *** USER INFORMAION MESSAGE 2350. (GPFDCC) 2350.0

165 INERTIAL AND DAMPING EFFECTS ARE IGNORED IN THE CALCULATION OF GRID POINT FORCES. *** USER INFORMATION MESSAGE 2351. (GPFDR) 2351.0 A FORCE CONTRIBUTION DUE TO ELEMENT TYPE = %1, ON POINT ID =%2 - POINT - FORCE - BALANCE WILL NOT APPEAR IN THE GRID SUMMARY. *** SYSTEM WARNING MESSAGE 2352. (GPFDR) 2352.0 IS NOT ABLE TO FIND PIVOT SIL =%1 AS READ FROM DATA BLOCK %2 IN TABLE OF SILS. *** SYSTEM WARNING MESSAGE 2352 (GPFDFA) 2352.1 UNABLE TO FIND PIVOT SIL =%1 AS READ FROM DATA BLOCK %2 (GPECT) IN TABLE OF SILS. *** USER WARNING MESSAGE 2353. (GPFDR) 2353.0 - - LOAD AND F - INSUFFICIENT CORE TO HOLD ALL NON ZERO APP - OF SPC OUTPUT LINE ENTRIES OF GRID POINT - FORCE - - SOME POINTS BALANCE REQUESTS. REQUESTED FOR OUTPUT WILL BE MISSING THEIR APP - LOAD OR F - OF - SPC CONTRIBUTION IN THE PRINTED BALANCE. *** USER WARNING MESSAGE 2354. (GPFDR) 2354.0 MODULE IS UNABLE TO CONTINUE AND HAS BEEN TERMINATED OR BELOW THIS DUE TO ERROR MESSAGE PRINTED ABOVE MESSAGE. THIS ERROR OCCURRED IN CODE WHERE THE VARIABLE - - WAS SET = %1 NERROR User information: This can occur in nonlinear solutions which invoke GPFDR via user - written DMAP. *** USER WARNING MESSAGE 2355. (GPFDR) 2355.0 NULL DISPLACEMENT VECTOR ENCOUNTERED IN CROSS STRAIN ENERGY CALCULATIONS. *** USER FATAL MESSAGE 2360 (ADG) 2360.0 CAERO 3, 4, OR 5 ENTRIES HAVE BEEN FOUND IN THE AERO MODEL BUT ARE NOT ALLOWED IN STATIC AERO PROBLEMS. User information: Static ae roelasticity only supports the doublet - lattice method of aerodynamics. Remove these entry types from the Bulk Data. *** USER FATAL MESSAGE 3000 3000.0 EOF ENCOUNTERED WHILE READING DATA BLOCK %1 *** USER WARNING MESSAGE 3000 (SITDEL) 3000.1 THE USE OF CTRIA6, CQUAD8 OR RBE2 ELEMENTS IN THE

166 ELEMENT BASED ITERATIVE SOLVER REQUIRES THE USE OF THE PARAMETERS AUTOSPC AND ELITASPC. WITHOUT THESE PARAMETERS, A SINGULAR MATRIX MAY OCCUR. *** USER FATAL MESSAGE 3000 (ELEINFF) 3000.2 UNSUPP ORTED ELEMENT TYPE %1 ENCOUNTERED IN THE ELEMENT BASED ITERATIVE SOLVER *** USER FATAL MESSAGE 3000 (SITDEL) 3000.3 THE MATRIX/TABLE %1 IS REQUIRED FOR THE ELEMENT BASED ITERATIVE SOLVER *** USER FATAL MESSAGE 3000 (SITDELC) 3000.4 - PROBABLY ERROR %1 RETURNED FROM THE UBBIO ROUTINES INSUFFICENT DISK SPACE *** USER WARNING MESSAGE 3000 (SITDELC) 3000.5 ITERATIVE SOLUTION FAILED TO CONVERGE IN %1 ITERATIONS. FINAL ERROR WAS %2. CHECK RESULTS FOR ACCURACY. *** USER FATAL MESSAGE 3000 (SITDELC) 3000.6 ITERATIVE SOLUTION FAILED DUE TO FAILURE OF PRECONDITIONER TO FACTOR. THIS ERROR CAN RESULT IF THE STRUCTURE IS NOT RESTRAINED SUFFICIENTLY TO PREVENT RIGID BODY MOTION OR IF INTERNAL MECHANISMS EXIST. User information : 9). - The preconditioner factor diagonal is smaller than ZPIVOT (default: 1.0e Reducing ZPIVOT in ITER card may continue the run, but the solution may be inaccurate. *** USER FATAL MESSAGE 3000 (SITDELC) 3000.7 GATIVE DIAGONAL ITERATIVE SOLUTION FAILED DUE TO NE ELEMENT, THIS ERROR CAN RESULT IF THE STRUCTURE IS NOT RESTRAINED SUFFICIENTLY TO PREVENT RIGID BODY MOTION OR IF INTERNAL MECHANISMS EXIST. *** USER FATAL MESSAGE 3000 (SITDELC) 3000.8 ITERATIVE SOLUTION FAILED DUE TO ZERO DIVISI ON *** USER FATAL MESSAGE 3000 (SITDELC) 3000.9 ITERATIVE SOLUTION FAILED DUE TO SQUARE ROOT OF NEGATIVE NUMBER *** USER FATAL MESSAGE 3000 (SITDELC) 3000.10 ITERATIVE SOLUTION FAILED DUE TO INSUFFICIENT MEMORY *** USER FATAL MESSAGE 3000 (SITDELC) 3000.11 ITERATIVE SOLUTION FAILED DUE TO INCONSISTENCY IN INPUT

167 DATA. CHECK THE .PCS FILE FOUND IN THE SCRATCH DIRECTORY FOR FURTHER INFORMATION. IF MESSAGES OF THE FORM "Failed to identify a slave variable ..." EXIST, SET THE PARAMETER AUTOMPC TO YES AND RERUN. *** USER FATAL MESSAGE 3000 (SITDELC) 3000.12 ITERATIVE SOLUTION FAILED DUE TO FILE IO FAILURE *** USER FATAL MESSAGE 3000 (SITDELC) 3000.13 ITERATIVE SOLUTION FAILED DUE TO SINGULAR MATRIX. CHECK THAT THE MODEL IS PROPERLY RESTRAINED AND HAS NO MECHANISMS. *** USER FATAL MESSAGE 3000 (SITDELC) 3000.14 ITERATIVE SOLUTION FAILED SINGULAR JACOBIAN. CHECK THE ELEMENT QUALITY OF TETRAHEDRAL ELEMENTS. PARABOLIC *** USER FATAL MESSAGE 3000 (SITDELC) 3000.15 ITERATIVE SOLUTION FAILED DUE TO EARLIER ABORT *** USER FATAL MESSAGE 3000 (SITDELC) 3000.16 ITERATIVE SOLUTION FAILED FOR REASON %1 REDUCEDIO DEACTIVATED DUE TO INSUFFICIENT VIRTUAL 3000.17 MEMORY. INCREASE VIRTUAL MEMORY %1 MB TO RUN WITH REDUCEDIO TURNED ON INSUFFICIENT MEMORY SPECIFIED FOR THE ITERATIVE SOLVER. 3000.18 INCREASE THE MEMORY LIMIT BY %1 MB CONTACT IS NOT SUPPORTED IN THE ITERATIVE SOLVER LINEAR 3000.19 *** USER WARNING MESSAGE 3000 (GETMESG) 3000.20 PRECONDITIONER FAILED TO FACTOR. SETTING A SMALLER ZPIVOT ON THE ITER CARD MAY HELP. MORE INFORMATION CAN BE FOUND IN LOG FILE. TO OPEN A SOLUTION MONITOR OUTPUT FILE. UNABLE 3000.99 SOLUTION MONITORING STOPPED THE %1 FILE %2 DOES NOT EXIST. 3001.0 PROGRAMMER INFORMATION: SUBROUTINE %3 THE %1 DATA BLOCK NAMED %2 AT POSITION %3 DOES NOT 3001.1 EXIST. USER INFORMATION: THIS ERROR I S CAUSED BY ONE OF THE FOLLOWING: 1. THE DATA BLOCK WAS NEVER CREATED. 2. THE DATA BLOCK WAS DELETED. 3. THE DATA BLOCK IS SPECIFIED ON A TYPE STATEMENT IN THE

168 CURRENT SUBDMAP OR A HIGHER SUBDMAP BUT THE CURRENT QUALIFIER VALUES DO NOT MATCH THE QUALI FIER VALUES OF THE DATA BLOCK(S) ON THE DATABASE. USER ACTION: 1. IF YOU ARE EXECUTING A SIEMENS PLM SOFTWARE SUPPLIED SOLUTION SEQUENCE AND NOT USING THE ALTER EXECUTIVE CONTROL STATEMENT, THEN CHECK FOR BULK DATA AND/OR CASE CONTROL INPUT ERRORS. IF N O ERRORS CAN BE FOUND, THEN CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. 2. IF YOU ARE EXECUTING A DMAP PROGRAM NOT SUPPLIED BY SIEMENS PLM SOFTWARE, THEN FOR DEBUGGING PURPOSES INSERT STATEMENT DIAGON(20) BEFORE THE MODULE SHOWN ABOVE. PROGRAMMER INF ORMATION: THE FIST NUMBER IS %4 AND SUBROUTINE IS %5 User information: This message should normally not occur for SIEMENS PLM SOFTWARE SOLs, but it has been observed when there is a mismatch between Case Control commands and of this are: a missing FREQi entry in modal Bulk Data entries. Examples frequency response analysis or a DLOAD entry in the Case Control that has no matching DLOAD, RLOADi, TLOADi, or ACSRCE entry in the Bulk Data. Verify that all Case Control entries have corresponding reference s in the Bulk Data. THE %1 DATA BLOCK IN POSITION %2 DOES NOT EXIST. 3001.2 USER INFORMATION: THIS ERROR IS CAUSED BY ONE OF THE FOLLOWING: 1. THE DATA BLOCK IS UNSPECIFIED ON THE DMAP MODULE. 2. THE DATA BLOCK IS SPECIFIED ON THE DMAP MODULE AND ON THE SUBDMAP STATEMENT BUT NOT ON THE CORRESPONDING CALL STATEMENT. USER ACTION: 1. IF YOU ARE EXECUTING A SIEMENS PLM SOFTWARE SUPPLIED SOLUTION SEQUENCE AND NOT USING THE ALTER EXECUTIVE CONTROL STATEMENT, THEN CHECK FOR BULK DATA AND/OR CASE CONTROL INPUT ERRORS. IF NO ERRORS CAN BE FOUND, THEN CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. 2. IF YOU ARE EXECUTING A DMAP PROGRAM NOT SUPPLIED BY SIEMENS PLM SOFTWARE, THEN FOR DEBUGGING PURPOSES INSERT STATEMENT DIAGON(20) BEFORE THE MODULE SHOWN ABOVE. PROGRAMMER INFORMATION: THE FIST NUMBER IS %3 AND SUBROUTINE IS %4

169 PTELM IS PURGED 3001.3 *** USER WARNING MESSAGE 3001. (DRMH3) 3001.4 LL BE OUTPUT DATA BLOCK %1 IS PURGED, NO OUTPUT WI GENERATED *** USER WARNING MESSAGE 3001. (DRMH3) 3001.5 INPUT DATA BLOCK %1 IS PURGED, OUTPUT DATA BLOCK %2 WILL NOT BE GENERATED *** USER WARNING MESSAGE 3001. (DRMH3) 3001.6 THE CASE CONTROL DATA BLOCK IS PURGED, OUTPUT DATA BLOCKS WILL BE GENERATED; SOME OUTPUT LABELS MAY BE MISSING *** USER WARNING MESSAGE 3001. (DRMH1) 3001.7 INPUT DATA BLOCK %1 IS NOT SORT 1 FORMAT. INPUT DATA BLOCK IGNORED. *** USER FATAL MESSAGE 3001. (MATMOD - 26) 3001.9 UNABLE TO OPEN DATA BLOCK %1 BECAUSE IT IS PURGED. *** SYSTEM INFORMATION MESSAGE 3001 3001.10 ATTEMPT TO OPEN THE DATA SET %1 WHICH WAS NOT DEFINED IN FIST. *** SYSTEM FATAL MESSAGE 3001 3001.11 ATTEMPT TO OPEN THE DATA SET %1 WHICH WAS NOT DEFINED IN FIST. EOF ENCOUNTERED WHILE READING DATA BLOCK %1 (FILE %2) 3002.0 IN SUBROUTINE %3 *** SYSTEM FATAL MESSAGE 3002 (SK11RD) 3002.1 END OF FILE WAS ENCOUNTERED WHILE READING K11 MATRIX FOR ITERATIVE SOLVER INSIDE STATICS MODULE. *** SYSTEM FATAL MESSAGE 3002 (SCALRD): 3002.2 END OF FILE WAS ENCOUNTERED WHILE READING K11 MATRIX FOR ITERATIVE SOLVER INSIDE STATICS SUPERMODULE. *** SYSTEM INFORMATION MESSAGE 3002 3002.3 EOF ENCOUNTERED WHILE READING DATA SET %1. *** SYSTEM FATAL MESSAGE 3002 3002.4 EOF ENCOUNTERED WHILE READING DATA SET %1. System information: This message is issued when an END - - FILE occurs whil e trying OF to skip the header record. The data block is not in the proper format. This generally occurs when data that the subroutine expects is missing. expects is missing. *** SYSTEM FATAL MESSAGE 3002 (DISOFM) 3002.5 UNEXPECTED END OF FILE WAS ENCOUNTERED WHILE READING %1 FROM PARALLEL NODE %2

170 *** SYSTEM FATAL MESSAGE 3002 3002.6 ERROR ENCOUNTERED DURING READ OF EQMAP USER ACTION : CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MES SAGE 3002 (PARAML) 3002.7 RECORD NO. %1 SPECIFIED BY THE %2 PARAMETER EXCEEDS THE NUMBER OF RECORDS (%3) IN THE INPUT DATA BLOCK UNEXPECTED EOF ENCOUNTERED IN SUBROUTINE DRMH2 3002.8 ATTEMPT TO READ PAST THE END OF A LOGICAL RECORD IN 3003.0 DATA BLOCK %1 (FILE %2) IN SUBROUTINE %3 System information: The data block is not in proper format. *** SYSTEM FATAL MESSAGE 3003 (NSL1SD) 3003.1 ATTEMPT TO READ PAST THE END OF A LOGICAL RECORD IN DAT A SET %1. *** system fatal message 3003 (disofm) 3003.2 UNEXPECTED END OF RECORD WAS ENCOUNTERED WHILE READING %1 FROM PARALLEL NODE %2 *** USER FATAL MESSAGE 3003 (PARAML) 3003.3 WORD NO. %1 IMPLIED BY THE %2 PARAMETER EXCEEDS THE NUMBER OF WORDS (%3) IN RECORD %4 OF THE INPUT DATA BLOCK INCONSISTENT TYPE FLAGS ENCOUNTERED WHILE PACKING 3004.0 DATA BLOCK %1 ATTEMPT TO OPERATE ON THE SINGULAR MATRIX %1 IN 3005.0 SUBROUTINE %2 User information: Subroutine SDCOMP or subroutine UDCOMP has detected a singular matrix and the calling routine does not support this case. A User Information Message defining the singularity has al ready been printed. ***SYSTEM FATAL MESSAGE 3006, 3006.0 BUFFER ASSIGNED WHEN OPENING DATA BLOCK %1,FILE %2, CONFLICTS WITH BUFFERS CURRENTLY OPEN. ILLEGAL INPUT TO SUBROUTINE %1 3007.0 System information: Subroutine %1 has encountered data which it cannot process. This error should not be caused by user input data, except as described in the next paragraphs. A system or programming error is indicated. Go directly to the subroutine listing or description to determine the exact cause of the problems. This message occurs in superelement analysis when restarting improperly. The illegal input message is usually caused by a purged input file.

171 One example is if the subroutine is CALCV. A common cause of this error is when attempting to perform a PARTN (or MERGE) on matrices with null partitioning vectors, or attempting to perform UPARTN (or UMERGE) on a matrix for which the original set is the same size as the final set. In this case, the partitioning vec tor generated by the program is null and this error is generated. In CALCV, if the DMAP coded" and the set does not exist, you'll get this error. partition "hard - set, but the user hasn't For example, if a UPARTN module is using the Q - used any Q set ent ries, this error will be issued. One remedy is to conditionally jump over the problem DMAP based on parameters such as NOQSET, NORSET, etc. This can also occur if inertia relief is not used properly in SOLs 91 or 101. Make sure that the rules stated in Chapter 9 for inertia relief are followed. This has also been observed in SOL 129 models with initially closed GAPs that specify the ADAPT method on the TSTEPNL entry. It can be avoided by specifying the AUTO method instead. See Error Report 3733 section 17.4 of NX NASTRAN Reference Manual. in This error has also been observed when analyzing large models when insufficient memory has been requested. If mem=estimate is used, the memory estimator may not be able to determine all requirements, resultin g in an estimated memory that is too low. Try increasing the memory allocation manually. *** SYSTEM FATAL MESSAGE 3007 3007.1 MODULE = GEOMSRVR ILLEGAL INPUT TO SUBROUTINE GEOMSR *** SYSTEM FATAL MESSAGE 3007 3007.2 ILLEGAL INPUT TO SUBROUTINE %1 INPUT MATRIX %2 IS COMPLEX, TRANSIENT RESPONSE DOES NOT SUPPORT COMPLEX ARITHMETIC INSUFFICIENT MEMORY AVAILABLE FOR SUBROUTINE %1 3008.0 *** SYSTEM FATAL MESSAGE 3008 (UTMCOR), 3008.1 MODULE = %1 INSUFFICIENT CORE AVAILABLE FOR SUBROUTINE %2 PROGRAMMER INFORMATION: LOCATION KEY = %3 System information: This message implies that the particular subroutine does not have sufficient memory to meet its demands. The subroutine or module description s hould be consulted to determine the memory requirements. Refer to Chapter 12 for instructions to increase the memory for the run. If an increase in memory is desired for only the module producing the error, an alter must be included in the Executive sec tion of the input file. An example of the alter is included below. COMPILE DMAP=dmap,SOUIN=source $ source=EDSSOU or USRSOU

172 ALTER # $ before module TYPE PARM,,I,N,MVAL $ MVAL = GETSYS(MVAL,57) PUTSYS(value1,57) $ value1=increased memory value ALTER # $ after module PUTSYS(MVAL,57) $ ENDALTER $ One cause observed for this in the Bulk Data SORT module is too many continuation entries. An avoidance is to have the Bulk Data already sorted and to increase available memory. See Error Report 2925 in se ction 17.2 of NX NASTRAN Reference Manual. Also, large THRU ranges can cause excessive memory to be used. *** SYSTEM FATAL MESSAGE 3008 (UTMCOR), 3008.2 MODULE = %1 INSUFFICIENT CORE AVAILABLE FOR SUBROUTINE %2 USER ACTION: INCREASE OPEN CORE BY AT LEAST %3 WORDS PROGRAMMER INFORMATION: LOCATION KEY = %4 *** USER WARNING MESSAGE 3008 (UDSFB) 3008.3 INSUFFICIENT MEMORY TO PERFORM FBS METHOD S3. THIS MAY LEAD TO POOR PERFORMANCE IN THE MCE1 MODULE FOR BETTER PERFORMANCE INCREASE MEMORY BY%1 WORDS *** USER INFORMATION MESSAGE 3008 (SSM10D) 3008.4 INSUFFICIENT MEMORY TO COMPUTE ERROR RATIOS. USER ACTION: SUPPLY AN ADDITIONAL %1 WORDS OF MEMORY IF EPSILON CHECKING IS DESIRED. *** SYSTEM FATAL MESSAGE 3008 (SK11RD) 3008.5 ITERATIVE SOLVER IN STATICS MODULE: ONLY %1 COLUMNS OF THE MATRIX FIT IN MEMORY. CURRENTLY THERE IS NO SPILL LOGIC FOR THE ITERATIVE SOLVER INSIDE THE STATICS MODULE. USER ACTION: INCREASE MEMORY OR USE THE DIRECT MET HOD. *** SYSTEM FATAL MESSAGE 3008 (SEPCAG) 3008.6 INSUFFICIENT MEMORY FOR MAIN BULK BASIC GEOMETRY. *** SYSTEM FATAL MESSAGE 3008 (SEPCAG) 3008.7 INSUFFICIENT MEMORY FOR SUPERELEMENT %1 BASIC GEOMETRY. SYSTEM FATAL MESSAGE 3008 *** 3008.9 INSUFFICIENT MEMORY FOR UNROLLED DESCRIPTOR. *** SYSTEM FATAL MESSAGE 3008 3008.10 INSUFFICIENT DYNAMIC MEMORY. *** SYSTEM FATAL MESSAGE 3008 3008.13 INSUFFICIENT MEMORY AT ROW %1. *** SYSTEM FATAL MESSAGE 3008 (IFPDRV) 3008.20

173 NO OPEN CORE FOR IFP MODULE. *** SYSTEM FATAL MESSAGE 3008 (IFP4) 3008.21 INSUFFICIENT MEMORY TO PERFORM OPERATIONS REQUIRED AS A RESULT OF FREEPT OR PRESPT ENTRIES. SYSTEM FATAL MESSAGE 3008 (IFP4) *** 3008.22 INSUFFICIENT MEMORY TO BUILD FREE SURFACE LIST TABLE. *** SYSTEM FATAL MESSAGE 3008 (IFP4) 3008.23 INSUFFICIENT MEMORY TO HOLD RINGFL ENTRIES. *** SYSTEM FATAL MESSAGE 3008 (IFP4) 3008.24 INSUFFICIENT MEMORY TO BUILD BOUNDARY LIST TABLE. *** SYSTEM FATAL MESSAGE 3008 (IFP4) 3008.25 INSUFFICIENT MEMORY =%1 TO HOLD GRIDB ENTRIES. *** SYSTEM FATAL MESSAGE 3008 (IFP4) 3008.26 INSUFFICIENT CORE =%1 TO READ DATA ON AXIF ENTRY. *** USER FATAL MESSAGE 3008. (DRMH3E) 3008.27 INSUFFICIENT MEMORY FOR TIME POINT LABELS, %1 WORDS ADDITIONAL MEMORY NEEDED. *** USER FATAL MESSAGE 3008. 3008.28 INSUFFICIENT MEMORY FOR FREQUENCIES, %1 WORDS ADDITIONAL MEMORY NEEDED. *** USER INFORMATION MESSAGE 3008. (DRMH3A) 3008. 30 INSUFFICIENT MEMORY FOR TIME POINTS, %1 READ UNKNOWN AMOUNT OF ADDITIONAL MEMORY NEEDED DRMH3 ABORTING. *** USER INFORMATION MESSAGE 3008. (DRMH3A) 3008.31 INSUFFICIENT MEMORY FOR FREQUENCIES, %1 READ UNKNOWN AMOUNT OF ADDITIONAL MEMORY NEEDED DRMH3 ABORTING. *** USER INFORMATION MESSAGE 3008. (DRMH3A) 3008.32 INSUFFICIENT MEMORY TO STORE COLUMN LABELS ADDITIONAL %1 WORDS NEEDED. USER INFORMATION MESSAGE 3008. (DRMH3A) *** 3008.33 INSUFFICIENT MEMORY FOR LAMA, %1 MODES READ; %2 * (REMAINING MODES) WORDS OF ADDITIONAL MEMORY NEEDED; DRMH3 ABORTING *** USER INFORMATION MESSAGE 3008. (DRMH3) 3008.34 RECORD, INSUFFICIENT MEMORY FOR CASE CONTROL ADDITIONAL %1 WORDS NEEDED; DRMH3 ABORTED *** USER INFORMATION MESSAGE 3008. (DRMH3) 3008.35 INSUFFICIENT MEMORY, ADDITIONAL %1 WORDS ARE NEEDED. *** SYSTEM FATAL MESSAGE 3008 (AELOOP) 3008.36 INSUFFICIENT CORE AVAILABLE FOR SUBROUTINE AELOOP. *** USER FATAL MESSAGE 3008 (HOUSE) 3008.37

174 INSUFFICIENT MEMORY TO HOLD ONE COLUMN OF THE MATRIX IN HOUSEHOLDER TRIDIAGONALIZATION. ***SYSTEM FATAL MESSAGE 3008 (PXMLOC) 3008.38 PID%1 UNABLE TO ACQUIRE SPACE OF%2 WORDS. USER INFORMATION: INCREASE MEMORY AVAILABLE TO JOB. *** SYSTEM INFORMATION MESSAGE 3008 (SDRVP) 3008.39 NOT ENOUGH MEMORY FOR COMPUTING OPTIMIZED COMMUNICATION PATTERN. SWITCHED TO REGULAR PATTERN. USER ACTION: ADD A MINIMUM OF %1 ADDITIONAL WORDS IF AN OPTIMIZED PATTERN IS DESIRED. *** SYSTEM INFORMATION MESSAGE 3008 (SITDRV) 3008.40 INSUFFICIENT CORE TO COMPUTE RIC PRECONDITIONER. USER ACTION: INCREASE MEMORY BY AT LEAST %1 WORDS. *** SYSTEM INFORMATION MESSAGE 3008 (SITDRV) 300 8.41 INSUFFICIENT CORE TO KEEP RIC PRECONDITIONER IN MEMORY. USER ACTION: INCREASE MEMORY BY AT LEAST %1 WORDS. *** SYSTEM INFORMATION MESSAGE 3008 3008.42 INSUFFICIENT CORE FOR CHOLESKY FACTORIZATION. USER ACTION: INCREASE CORE BY %1 WORDS. SWITCHED TO JACOBI PRECONDITIONER. *** SYSTEM INFORMATION MESSAGE 3008 (BGCASO) 3008.43 INSUFFICIENT CORE IS AVAILABLE FOR BUILDING CONTACT MASTER SET. *** SYSTEM INFORMATION MESSAGE 3008 (BGCAU1) 300 8.44 INSUFFICIENT CORE IS AVAILABLE TO PROCESS CONTACT REGION OUTPUT REQUEST. *** SYSTEM FATAL MESSAGE 3008 (BGCONR) 3008.45 INSUFFICIENT CORE IS AVAILABLE FOR READING %1 RECORD. *** SYSTEM FATAL MESSAGE 3008 (BGLSCW) 3008.47 INSUFFICIENT CORE IS AVAILABLE FOR READING BLSEG SLAVE AND MASTER RECORDS. *** SYSTEM FATAL MESSAGE 3008 (BGPECT) 3008.48 INSUFFICIENT CORE TO ACCOMMODATE BGPECT RECORD. SYSTEM FATAL MESSAGE 3008 (BGTPEN) *** 3008.50 INSUFFICIENT CORE TO BUILD BTOPO AND ESTNL RECORDS. *** USER FATAL MESSAGE 3008 (IFP5) 3008.51 INSUFFICIENT MEMORY TO HOLD ALL GRIDS ENTRIES. *** USER FATAL MESSAGE 3008 (IFP5) 3008.52 INSUFFICIENT MEMORY TO HOLD ALL GRIDF ENTRIES. *** USER FATAL MESSAGE 3008 (IFP5) 3008.53 INSUFFICIENT MEMORY TO HOLD ALL GRIDF ENTRIES BEING CREATED INTERNALLY DUE TO GRIDS ENTRIES SPECIFYING AN

175 IDF. *** USER FATAL MESSAGE 3008 (IFP5) 3008.54 INSUFFICIENT MEMORY TO CONSTRUCT ENTIRE BOUNDARY TABLE FOR SLBDY ENTRIES PRESENT. *** USER FATAL MESSAGE 3008 (BGUPEN) 3008.55 INSUFFICIENT CORE IS AVAILABLE. *** USER FATAL MESSAGE 3008 (SEQMRP) 3008.56 INSUFFICIENT SPACE IN MEMORY TO CREATE %1 RECORD IN SCRATCH FILE RBESCR. PROGRAMMER INFORMATION: NUMBER OF WORDS TO BE STORED IN THIS RECORD OF RBESCR: %2. NUMBER OF WORDS AVAILABLE IN SCRATCH ARRAY: %3. SING USER INFORMATION: THIS MODEL CANNOT BE ANALYSED U THE DOMAIN DECOMPOSITION METHOD. USER ACTION: PLEASE SUBMIT THE JOB IN SERIAL MODE (DO NOT SET DMP ON THE SUBMITTAL LINE). *** USER INFORMATION MESSAGE 3008 (OUTPRT) 3008.57 INSUFFICIENT MEMORY WAS AVAILABLE TO PROCESS THE OUTPUT REQUESTS. U SER INFORMATION: MORE ECONOMICAL DATA RECOVERY MAY BE POSSIBLE IF ADDITIONAL MEMORY IS PROVIDED. *** SYSTEM WARNING MESSAGE 3008.58 (LDNSSEL) 3008.58 NOT ENOUGH MEMORY AVAILABLE TO LOAD NSERVER_SELECT CLAUSE(S). REQUESTED I= %1 WORDS USER INFORMATION: CLAUSE(S) WILL BE IGNORED. USER ACTION: INCREASE MEMORY OR REDUCE NUMBER OF NSERVER_SELECT CLAUSE(S) *** SYSTEM WARNING MESSAGE 3008.59 (NSSELWH) 3008.59 INSUFFICIENT MEMORY WHILE WORKING ON NSERVER_SELECT WHERE CLAUSE STARTING W ITH %1 MEMORY USED = %2. USER INFORMATION: WHERE CLAUSE IS IGNORED. USER ACTION: INCREASE MEMORY SIZE OR REDUCE NSERVER_SELECT STATEMENT. *** SYSTEM WARNING MESSAGE 3008 (IFPINDX) 3008.61 INSUFFICIENT MEMORY TO BUILD INDEX ADDITIONAL MEMORY RE QUIRED: %1 MW. USER INFORMATION: %2 NOT INDEXED USER ACTION: INCREASE MEMORY IF THIS FILE NEEDS TO BE INDEXED *** USER WARNING MESSAGE 3008. (RMXAVGM) 3008.62 INSUFFICIENT MEMORY FOR RMAXMIN CALCULATIONS,

176 ADDITIONAL %1 WORDS ARE NEEDED. RMAXMIN WILL INSTEAD BE CALCULATED USING SCRATCH DISK FILES. THIS MAY SIGNIFICANTLY INCREASE DISK USAGE AND COMPUTATION TIME. DATA TRANSMISSION ERROR ON DATA BLOCK %1(FILE %2) 3009.0 ATTEMPT TO MANIPULATE DATA BLOCK %1(FILE %2) BEFORE 3010.0 OPENING THE FILE ATTEMPT TO WRITE A TRAILER ON FILE %1 WHEN IT HAS BEEN 3011.0 PURGED System information: The file did not exist in the FIST when WRTTRL was called. ATTEMPT TO OPEN DATA BLOCK %1(FILE %2) WHICH HAS 3012.0 ALREADY BEEN OPENED ATTEMPT TO READ DATA BLOCK %1(FILE %2) WHEN IT WAS 3013.0 OPENED FOR OUTPUT ATTEMPT TO WRITE DATA BLOCK %1(FILE %2) WHEN IT WAS 3014.0 OPENED FOR INPUT ATTEMPT TO FWDREC ON DATA BLOCK %1(FILE %2) WHEN IT 3015.0 WAS OPENED FOR OUTPUT %1 MATRIX IS NOT IN PROPER FORM IN SUBROUTINE %2 3016.0 System information: This implies that the input matrix is not in the proper form of type acceptable to the subroutine. Check the trailer information on the matrix and the subroutine description for the discrepancy. NO MESSAGE FOR MESSAGE NO. = %1 3017.0 PARAMETERS =%2 MODULE %1, SEQUENCE NO.%2, REQUIREMENTS EXCEED 3018.0 AVAILABLE FILES System information: Segment File Allocator (SFA) did not have sufficient logical files available to fill the request of the module. Reduce module requirements or increase the logical files within the computer system. See Section 5 of the NX NASTRAN Programmer's Manual. MAXIMUM LINE COUNT EXCEEDED IN SUBROUTINE %1 LINE 3019.0 COUNT EQUALS %2 User information: The total number of lines written on the system output file has exceeded the set limit. To increase this value, specify the MAXLINES=n command in the Case Co ntrol Section. GNFIST OVERFLOWED FIST TABLE AT SEQUENCE NO.%1DATASET 3020.0 %2

177 FILE%1 NOT DEFINED IN FIST 3021.0 *** USER INFORMATION MESSAGE 3023 (originally 3028??) 3023.0 B =%1 C =%2 R =%3 THE BANDWIDTH OF MATRIX %1 EXCEEDS THE MAXIMUM 3024.0 BANDWIDTH. A MAXIMUM BANDWIDTH OF %2 WILL BE USED ILLEGAL INDEX IN ACTIVE ROW OR COLUMN CALCULATION IN 3025.0 %1 MATRIX %1 EXCEEDS MAXIMUM ALLOWABLE SIZE FOR BAND 3026.0 WIDTH PLUS ACTIVE COLUMNS. BM AX = %2 CMAX = %3 *** USER INFORMATION MESSAGE 3028, 3028.0 BBAR =%1 CBAR =%2 R = %3 *** USER INFORMATION MESSAGE 3028, 3028.1 B =%1 C =%2 R =%3 *** SYSTEM FATAL MESSAGE 3029, 3029.0 PHYSICAL EOF ENCOUNTERED ON DATA BLOCK %1 (FILE %2 ). *** SYSTEM WARNING MESSAGE 3030 (OFP) 3030.0 THE OFP MODULE CANNOT PRINT THE DATABLOCK %1 USER ACTION: USE THE MATPRN OR TABPT MODULE. PROGRAMMER INFORMATION: OFP LOC CODE = %2 FILE =%3 *** USER WARNING MESSAGE 3030, 3 030.1 MACOFP UNABLE TO PROCESS DATA BLOCK, ALTER IN A TABLE PRINT TO SEE DATA MACOFP LOC CODE = %1 User information: The format of the file is unrecognized. This may be caused by an output request for an element for wh ich formats are not defined. INVALID PARAMETER DEFINITION(S) IN SUBROUTINE (%1). 3031.0 User information: One or more parameters have been mis - defined. Please refer to the DMAP Programmer's Guide. TO FIND SELECTED SET (%1) IN TABLE (%2) IN UNABLE 3032.0 SUBROUTINE (%3). User information: A particular set used in the problem was not included in the data. Good examples are loads, initial conditions, or frequency sets. Include the required data or change the Cas e Control commands to select data already in the problem. Set zero (0) has a special meaning. A set selection was required, but none was made. For example, no METHOD was selected for an eigenvalue extraction problem, or no FREQ was selected for frequen cy response. This message can also indicate that a LOAD entry references another LOAD entry, which is not permitted. This message can also occur if a DLOAD entry references a nonexisting LOAD entry, e.g., RLOAD1.

178 *** USER WARNING MESSAGE 3 032 (LCGEN) 3032.1 SELECTED LSEQ ENTRY %1 REFERENCES UNDEFINED %2 SET ID %3 *** USER WARNING MESSAGE 3032 (LCGEN) 3032.2 SELECTED LSEQ ENTRY %1 DOES NOT REFERENCE DAREA SET ID %2 SPECIFIED ON A RLOAD1/RLOAD2/TLOAD1/TLOAD2/ACSRCE ENTRY *** USER WARNING MESSAGE 3032 (LCGEN) 3032.3 THE EXCITE ID NUMBER %1 FOUND IN THE SELECTED LSEQ ID %2 IS NOT REFERRED TO BY ANY RLOAD1/RLOAD2/TLOAD1/TLOAD2/ACSRCE ENTRIES *** USER FATAL MESSAGE 3033, 3033.0 SUBCASE ID%1 IS REFERENCED ON ONE OR MORE RANDPS C ARDS BUT IS NOT A CURRENT SUBCASE ID. User information: The RANDPS set selected can only reference subcase identification numbers included in the current loop. All subcases in which the direct together. input matrices or transfer functions do not change are run Either add a subcase with referenced identification number, change your RANDPS entries, or change the identification numbers on your current subcases. ORTHOGONALITY CHECK FAILED, LARGEST TERM = %1, EPSILON 3034.0 = %2 *** USER WARNING MESSAGE 3034, 3034.1 ORTHOGONALITY TEST FAILED. LARGEST TERM = %1 ,NUMBER FAILED = %2 PAIR = %3,%4 , EPSILON = %5 User information: This indicates that eigenvector accuracy is in doubt. This message - diagonal terms o f the modal mass matrix is printed only when the off are larger than 1.0E - 10. The eigenvectors are not orthogonal to this extent. This nonorthogonality is especially important if a modal formulation is used. The pair of eigenvectors listed exhibit the worst behavior. The number fa iled is the number of pairs above the criteria. You can improve the numerical conditioning of the problem by reducing the range of mass ratios, stiffness ratios, and eigenvalue range. *** SYSTEM FATAL MESSAGE 3034 (LNNHERR) 3034.2 INTERNAL FAILUR E IN THE LANCZOS PROCEDURE: M - ORTHOGONAL QR PROCEDURE FAILED TO CONVERGE. PROBABLE CAUSE: MASS MATRIX IS INDEFINITE (MODES) OR STIFFNESS MATRIX IS INDEFINITE (BUCKLING).

179 USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. FOR SUBCASE NUMBER %1 EPSILON SUB E =%2 3035.0 *** USER INFORMATION MESSAGE 3035 3035.1 FOR DATA BLOCK %1 SUPPORT PT.NO. EPSILON STRAIN ENERGY EPSILONS LARGER THAN %2 ARE FLAGGED WITH ASTERISKS User information: nent referenced on the One line of output is printed for each compo SUPORT and SUPORT1 entries. Large values of either EPSILON or STRAIN ENERGY indicate errors in the constraints. THE VALUES OF EPSILON AND STRAIN ENERGY SHOULD BE 3035.2 NUMERICAL ZERO. THE LARGE VALUES INDICATE ORT DEGREES OF FREEDOM ARE NOT PROPERLY THAT THE SUP SPECIFIED AS TO BE CAPABLE OF SUPPORTING RIGID BODY MOTION. SET SYSTEM CELL 505 TO 1 TO OVERRIDE FTL MESSAGE. DATA BLOCK %1 IS REQUIRED AS INPUT BUT HAS NOT BEEN 3036.0 GENERATED OR PURGED JOB TERMINATED IN SUBROUTINE %1 3037.0 System information: This message designates the subroutine in which the program terminated. It should be preceded by a user message which explains the cause of the termination. The module in which the program be found by examining the log messages. terminated can DATA BLOCK %1 DOES NOT HAVE MULTI - REEL CAPABILITY 3038.0 *** SYSTEM FATAL MESSAGE 3039, 3039.0 ENDSYS CANNOT FIND SAVE FILE. TO WRITE DATA BLOCK %1(FILE %2) WHEN IT IS AN ATTEMPT 3040.0 INPUT FILE System information: Input data blocks for a module (FILE NO. 101 - 199) may be read only. EXTERNAL GRID POINT %1 DOES NOT EXIST OR IS NOT A 3041.0 GEOMETRIC GRID POINT. THE BASIC ORIGIN WILL BE USED. User information: The reference grid point specified on the PARAM, GRDPNT entry for weight and balance calculations in GPWG cannot be used. GPWG cannot be used. Possible causes include: 1. The referenced grid point does not exist. 2. In sup erelement analysis, if the referenced grid point

180 is not either interior or exterior to the current superelement, this message is issued. If it is desired to use the listed grid point as a reference, then a CSUPEXT entry should be used to make or to the superelement. it exteri INCONSISTENT SCALAR MASSES HAVE BEEN USED. 3042.0 EPSILON/DELTA = %1 User information: The GPWG has detected inconsistent scalar masses. Direct masses have been used. Skew inertia's will result. Examine the scalar masses and CONM1 entry. UNCONNECTED EXTRA POINT (MODAL COORDINATE =%1 ) HAS 3043.0 BEEN DETECTED BY SUBROUTINE %2 User information: Extra points must be connected via Direct Matrix Input (or Transfer ponse. Functions) in modal transient or frequency res A POINT ON NON - LINEAR LOAD SET %1 NOLIN%2 IS NOT AN 3044.0 EXTRA POINT. ONLY EXTRA POINTS MAY HAVE NON - LINEAR LOADS IN A MODAL FORMULATION. User information: Modal transient analysis will support nonlinear loads only on extra points. Pick another nonlinear load Set. *** USER WARNING MESSAGE 3045, 3045.0 INSUFFICIENT TIME TO COMPLETE THE REMAINING %1 SOLUTION(S) IN MODULE %4 USER INFORMATION: TIME ESTIMATE TO COMPLETE: %2 SECONDS TIME REMAINING %3 SECONDS tion: User informa The estimated time for completion of the module is less than the time remaining, as specified on the Executive Control TIME statement. The module and computes one solution (for example, one excitation frequency in frequency response analysis) and then processes all output requests. The remaining frequencies can be obtained on restart by adding or changing a FREQ command. *** USER FATAL MESSAGE 3046 (TRD1) 3046.0 THIS TRANSIENT RESPONSE ANALYSIS HAS NO EXCITATION SPECIFIED FOR IT. APPLIE D LOADS, ENFORCED MOTION, INITIAL CONDITION AND NON - LINEAR FORCES ARE ALL NULL. THE RESULT WILL THEREFORE BE A ZERO SOLUTION. User information: Transient response solutions must have one of the above nonzero. Also, make sure that LOADSET is spelled cor rectly, in its entirety.

181 *** USER FATAL MESSAGE 3046 (SQFREQ/DPFREQ/CYCL4A) 3046.1 THIS FREQUENCY RESPONSE ANALYSIS HAS NO EXCITATION SPECIFIED FOR IT. APPLIED LOADS AND ENFORCED MOTION ARE BOTH NULL. THE RESULT WILL THEREFORE BE A ZERO SOLUTION. User information: Frequency response solutions must have one of the above nonzero. Also, make sure that LOADSET is spelled correctly, in its entirety. *** USER INFORMATION MESSAGE 3046 (SQFREQ) 3046.2 THE FREQUENCY RESPONSE ANALYSIS ON THIS NOD E HAS NO EXCITATION SPECIFIED. THIS MESSAGE MAY RESULT IF THERE ARE FEWER FREQUENCIES SPECIFIED THAN THE NUMBER OF PROCESSORS. FOR MOST EFFICIENT DMP PERFORMANCE, THE NUMBER OF FREQUENCIES SHOULD BE EQUAL TO OR GREATER THAN THE NUMBER OF PROCESSORS. *** USER FATAL MESSAGE 3047, 3047.0 NO MODES WITHIN RANGE AND LMODES = 0. A MODAL FORMULATION CANNOT BE MADE. User information: The modes used for a modal formulation must be selected by a PARAM entry. Set LFREQ, HFREQ, or LMODES to request modes. *** SYSTEM FATAL MESSAGE 3048, 3048.0 BUFFER CONTROL WORD INCORRECT FOR GINO %1 OPERATION ON DATA BLOCK %2 *** SYSTEM FATAL MESSAGE 3049, 3049.0 GINO UNABLE TO POSITION DATA BLOCK %1 CORRECTLY DURING %2 OPERATION. *** USER FATAL MESSAGE 3050, 3050.0 INSUFFICIENT TIME REMAINING FOR %1. TIME ESTIMATE IS %2 SECONDS. User information: The time estimate for execution of the named subroutine exceeds the time remaining as specified on the TIME statement. *** USER FATAL MESSAGE 3050 (DFMSA) 3050.1 INSUFFICIENT TIME REMAINING FOR SPARSE MATRIX DECOMPOSITION *** USER FATAL MESSAGE 3051, 3051.0 INITIAL CONDITION SET %1 WAS SELECTED FOR A MODAL TRANSIENT PROBLEM. INITIAL CONDITIONS ARE NOT ALLOWED IN SUCH A PROB LEM.

182 User information: The IC command is not allowed for modal transient response problems. *** USER WARNING MESSAGE 3052, 3052.0 - , POINT - %2 - A RANDOM REQUEST FOR CURVE TYPE %1 - - , SPECIFIES TOO LARGE A COMPONENT ID. THE COMPONENT %3 LAST C OMPONENT WILL BE USED. User information: Check Item Codes in QRG for componet order. *** USER WARNING MESSAGE 3053, 3053.0 THE ACCURACY OF EIGENVALUE %1 IS IN DOUBT. GIV/HOU QR FAILED TO CONVERGE IN %2 ITER. User information: Each eigenvalue is computed to the precision limits of each machine consistent with the maximum number of iterations allowed. - AN ATTEMPT TO MULTIPLY OR MULTIPLY AND ADD NON 3055.0 CONFORMABLE MATRICES TOGETHER WAS MADE IN MODULE %1 User informatio n: The multiply/add subroutine requires conformable matrices. There are two possible equations 1. X = A * B + C The number of columns of [A] must be equal to the number of rows of [B] the number of columns of [C] be equal to the number of columns of [ B] and the number of rows of [C] must be equal to the number of rows of [A]. 2. X = A(T) *B + C The number of rows of [A] must be equal to the number of rows of [B] the number of columns of [C] must be equal to the number of columns of [B] mber of rows of [C] must be equal and the nu to the number of columns of [A]. One cause of this is if the model in a cyclic symmetry analysis contains MPCs and only the zero harmonic is requested. This can be avoided by requesting an additional harmonic. NO MASS MATRIX IS PRESENT BUT MASS DATA IS REQUIRED 3056.0 NO MASS MATRIX IS PRESENT BUT MASS DATA IS REQUIRED FOR 3056.1 RFORCE AND RFORCE1 LOADING. LOAD IS IGNORED. MATRIX %1 IS NOT POSITIVE DEFINITE. 3057.0 User information: A Cholesky decomposition was attempted on the above matrix, but a diagonal term of the factor was imaginary or equal to zero such that the decomposition failed. This message is from the regular (as opposed to sparse) decomposition method. This message may be produced because of constraint problems. Check

183 the output for UWM 4698 for large factor diagonal ratios and constrain appropriately. EPSILON IS LARGER THAN %1 FOR SUBCASE %2 3058.0 SET IDENTIFIER %1 DOES NOT EXIST. ERROR DETECTED IN 3059.0 SUBROUTINE %2 User information: When describing displacement matrices only those set identifiers (such as M or G) listed in DMAP module MATGPR are legal set names. Choose a set name which is legal (and de scribes the matrices to be operated on). NEW SET IDENTIFIER %1 IN DEFUSET IS NOT UNIQUE. ERROR 3059.1 DETECTED IN SUBROUTINE %2 User information: When Using new set names, these must be unique with respect to all other set names. * ** USER FATAL MESSAGE 3060, 3060.0 - OPTION %2 NOT IN APPROVED LIST. SUBROUTINE %1 SYSTEM DATE (MM/DD/YY): %3/%4/%5 SYSTEM UGSID: %6 (DECIMAL) %7 (HEXADECIMAL) SYSTEM MODEL NUMBER: %8 SYSTEM OS CODE: %9 REFER TO THE NX NASTRAN LOG FILE FOR DETAILED INFORMATIO N User information: This option is not authorized for your authorization code. Contact SIEMENS PLM SOFTWARE CUSTOMER SUPPORT for the list of options available at your site. This option can be easily enabled with a contractual change on your present sy stem and a new authorization code. There may be a problem with the file that contains the authorization code. Refer to the NX NASTRAN Installation and Operation Instructions for a description and use of the file. *** USER FATAL MESSAGE 3060 3060.1 SUBROUTINE %1 - OPTION %2 NOT IN APPROVED LIST. SYSTEM DATE (MM/DD/YY): %3/%4/%5 SYSTEM UGSID: %6 (DECIMAL) %7 (HEXADECIMAL) SYSTEM MODEL NUMBER: %8 SYSTEM OS CODE: %9 SYSTEM UGSID: %10 (DECIMAL) %11 (HEXADECIMAL) SYSTEM MODEL N UMBER: %12 SYSTEM OS CODE: %13 SYSTEM UGSID: %14 (DECIMAL) %15 (HEXADECIMAL) SYSTEM MODEL NUMBER: %16 SYSTEM OS CODE: %17 SYSTEM UGSID: %18 (DECIMAL) %19 (HEXADECIMAL) SYSTEM MODEL NUMBER: %20 SYSTEM OS CODE: %21 SYSTEM UGSID: %22 (DECIMAL) %23 (HEXADEC IMAL) SYSTEM MODEL NUMBER: %24 SYSTEM OS CODE: %25 SYSTEM UGSID: %26 (DECIMAL) %27 (HEXADECIMAL) SYSTEM

184 MODEL NUMBER: %28 SYSTEM OS CODE: %29 SYSTEM UGSID: %30 (DECIMAL) %31 (HEXADECIMAL) SYSTEM MODEL NUMBER: %32 SYSTEM OS CODE: %33 ECIMAL) %35 (HEXADECIMAL) SYSTEM SYSTEM UGSID: %34 (D MODEL NUMBER: %36 SYSTEM OS CODE: %37 REFER TO THE NX NASTRAN LOG FILE FOR DETAILED INFORMATION User information: This option is not authorized for your authorization code. Contact SIEMENS PLM SOFTWARE CUSTOMER SUPPORT for the list of options available at your site. This option can be easily enabled with a contractual change on your present system and a new authorization code. There may be a problem with the file that contains the authorization NASTRAN Installation and Operation Instructions code. Refer to the NX for a description and use of the file. *** USER FATAL MESSAGE 3060 (MSGWRT) 3060.2 - AUTHORIZATION ERROR *** UNABLE TO OBTAIN LICENSES FOR %1 PLEASE REFER TO THE LOG FILE FOR ADDITIONAL DETAILS *** USER FATAL MESSAGE 3060, 3060.3 SUBROUTINE %1 - OPTION %2 NOT IN APPROVED LIST. SYSTEM DATE (MM/DD/YY): %3/%4/%5 CHECK THAT AN NX NASTRAN FOR WINDOWS DONGLE IS PROPERLY CONNECTED TO THIS COMPUTER User information: This option is not authorized for your authorization code. Contact SIEMENS PLM SOFTWARE CUSTOMER SUPPORT for the list of options available at your site. This option can be easily enabled with a contractual change zation code. on your present system and a new authori There may be a problem with the file that contains the authorization code. Refer to the NX NASTRAN Installation and Operation Instructions for a description and use of the file. *** USER INFORMATION MESSAGE 3061 (DMK9NS) 3061.0 THE MEASURE OF NON - PLANARITY IS %1 FOR ELEMENT NUMBER %2 User information: The measure of non - planarity for isoparametric quadrilateral membrane elements is the distance from actual grid points to mean plane divided by the average length of the diagonals. This message is issued only when the absolute value of this measure is greater than .01. *** SYSTEM WARNING MESSAGE 3071, 3071.0 EXTRA DATA IN RADLST RECORD OF MATPOOL DATA BLOCK IGNORED.

185 *** USER WARNING MESSAGE 3072, 3072.0 TOO MANY MATRIX VALUES INPUT VIA RADMTX BULK DATA FOR COLUMN %1. EXTRA VALUES IGNORED AS MATRIX SIZE IS DETERMINED TO BE - S. OF SIZE %2 FROM RADLST COUNT OF ELEMENT ID *** USER FATAL MESSAGE 3073, 3073.0 HBDY - NO R ELEMENT - ELEMENT SUMMARY DATA IS PRESENT FO ID = %1 WHICH APPEARS ON A - RADLST - BULK DATA CARD. *** USER FATAL MESSAGE 3074 (SDRMG) 3074.0 COLUMN %1 OF THE YSYM MATRIX IS NULL. *** USER FATAL MESSAGE 3079, 3079.0 HBDY - ELEMENTS PRESENT. THERE ARE NO - *** USER FATAL MESSAGE 3080 (QLOADL) 3080.0 QVECT TABLE INPUT NOT ALLOWED FOR STEADY STATE. *** SYSTEM WARNING MESSAGE 3081 (DFMSYA) 3081.0 The size of the matrix to be decomposed is not equal to the size of the degree - of - freedom set. Size od set ID %1 = %2 . Size of matrix = %3 USER INFORMATION: DECOMPOSITION PERFORMANCE MAY BE DEGRADED AND/OR MORE MEMORY MAY BE REQUIRED. *** SYSTEM FATAL MESSAGE 3081 3081.1 INCONSISTENT USET DATA DETECTED. System information: Input matrices whose dimensions are inconsistent with the matrix sizes stored in the USET table have been detected. The usual cause is a restart that does not select the proper SE type Case Control - commands. Try an SEALL=ALL restart YSTEM FATAL MESSAGE 3094 (SSGSLT) *** S 3094.0 SLT LOAD TYPE %1 IS NOT RECOGNIZED. System information: A new load type was added to SLT but not to subroutine SSGSLT. *** USER FATAL MESSAGE 3094 (SSGSLT) 3094.1 MULTIPLE ACCEL CARDS HAVE SAME ID *** USER WARNING MESSAGE 3095 (SSGSLT) 3095.0 ALL ELEMENT TYPE %1, REFERENCED BY A QVOL CARD IN LOAD SET %2, ARE NOT BEING USED FOR INTERNAL HEAT GENERATION IN THIS LOAD SET AS THIS ELEMENT TYPE IS CURRENTLY NOT SUPPORTED IN THIS AREA.

186 ARNING MESSAGE 3095 (SSGSLT) *** USER W 3095.1 ELEMENT TYPE %1 WITH ID =%2, REFERENCED BY A QVOL CARD IN LOAD SET %3, IS NOT BEING USED FOR INTERNAL HEAT GENERATION IN THIS LOAD SET BECAUSE ANOTHER ELEMENT TYPE WITH THE SAME ID HAS ALREADY BEEN PROCESSED. * ** USER FATAL MESSAGE 3096 (SSGSLT) 3096.0 ELEMENT ID =%1 AS REFERENCED ON A QVOL, QBDY1, QBDY2, QBDY3, OR QVECT ENTRY COULD NOT BE FOUND AMONG ACCEPTABLE ELEMENTS FOR THAT LOAD TYPE. User information: ments. QBDY1, QBDY2 or QVECT entries can only point to CHBDY ele QVOL can only point to legal heat transfer elements. See the NX NASTRAN Thermal Analysis User's Guide for the list. *** USER WARNING MESSAGE 3097. 3097.0 SYMMETRIC DECOMPOSITION OF DATA BLOCK %1 ABORTED DUE USER OPTION. TO ABOVE MESSAGES AND *** USER WARNING MESSAGE 3097. 3097.1 SYMMETRIC DECOMPOSITION OF DATA BLOCK %1 ABORTED BECAUSE THE FOLLOWING COLUMN IS NULL -- %2 User information: The user can avoid this message by using the DECOMP=16 statement to zero column. (This is set by setting SYSTEM(69)=16 continue with the or via DMAP.) This puts 1.0 on the diagonal of the null column. See the NX NASTRAN Numerical Methods User's Guide. *** USER WARNING MESSAGE 3097. 3097.2 SYMMETRIC DECOMPOSITION OF DATA BLOCK %1HA S ZERO ON DIAGONAL AT COLUMN%2. DECOMPOSITION ABORTED. *** USER WARNING MESSAGE 3097. 3097.3 SYMMETRIC DECOMPOSITION LEADING MINOR OF DATA BLOCK %1 IS SINGULAR AT COLUMN%2. DECOMPOSITION ABORTED. *** SYSTEM FATAL MESSAGE 3097. 3097.4 PARALLEL DECOMPOSITION OF DATA BLOCK%1 ABORTED BECAUSE THE FOLLOWING COLUMN IS NULL %2 *** SYSTEM FATAL MESSAGE 3097 3097.5 PARALLEL DECOMPOSITION OF DATA BLOCK %1 HAS ZERO ON DIAGONAL AT COLUMN %2 DECOMPOSITION ABORTED *** USER WARNING MESSAGE 3097 (DFMSA) 3097.6 COLUMN %1 HAS ZERO DIAGONAL TERM, DECOMPOSITION

187 ABORTED ON USER REQUEST. *** USER WARNING MESSAGE 3097 (DFMSA) 3097.7 COLUMN %1 IS NULL, DECOMPOSITION ABORTED ON USER REQUEST. *** USER WARNING MESSAGE 3097 (DFMSAP) 3097.8 ZERO DIAGONAL TERMS ENCOUNTERED, DECOMPOSITION ABORTED ON USER REQUEST. *** SYSTEM FATAL MESSAGE 3097 3097.9 PARALLEL DECOMPOSITION OF LEADING MINOR OF DATA BLOCK %1 IS SINGULAR AT COLUMN %2 D DECOMPOSITION ABORTE *** SYSTEM INFORMATION MESSAGE 3097 3097.10 PARALEL DECOMPOSITION OF DATA BLOCK %1 HAS ZERO DIAGONAL AT COLUMN %2 *** SYSTEM FATAL MESSAGE 3097 3097.11 PARALLEL DECOMPOSITION OF DATA BLOCK %1 ABORTED DUE TO ABOVE MESSAGES AND USER OPTION *** SYSTEM INFORMATION MESSAGE 3097 3097.12 COLUMN %1 of DATA BLOCK %2 IS NULL. *** SYSTEM INFORMATION MESSAGE 3097 3097.13 DATA BLOCK %1 HAS ZERO DIAGONAL TERM AT COLUMN%2 *** SYSTEM INFORMATION MESSAGE 3097 3097.14 PARTIAL DECOMPOSITION FAILED USER ACTION : CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM INFORMATION MESSAGE 3097 3097.15 BOUNDARY DECOMPOSITION FAILED USER ACTION : CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SY STEM FATAL MESSAGE 3097 3097.16 SPILL ACTIVATED IN SORT PHASE, BUT NPASS = %1 USER ACTION : CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 3097 3097.17 NUMERIC PHASE RETURNED ERROR CODE %1 USER ACTION : CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER WARNING MESSAGE 3098 (ROTCDA) 3098.0 THERE IS NO DATA FOR ROTOR SPEED; POST PROCESSING CANNOT BE DONE *** USER WARNING MESSAGE 3098 (ROTCDA) 3098.1 THERE ARE NO REAL EIG ENVALUES;

188 POST PROCESSING CANNOT BE DONE *** USER WARNING MESSAGE 3098 (ROTCDA) 3098.2 THERE ARE NO IMAGINARY EIGENVALUES; POST PROCESSING CANNOT BE DONE *** USER INFORMATION MESSAGE 3098 (ROTSSD) 3098.3 THERE ARE NO REAL EIGENVALUES FOR SYNCHRONOUS ANALYSIS *** USER INFORMATION MESSAGE 3098 (ROTSSD) 3098.4 NO WHIRL MATRIX IS PRESENT; WHIRL DIRECTION CANNOT BE CALCULATED *** USER INFORMATION MESSAGE 3098 (ROTSSD) 3098.5 THERE ARE NO IMAGINARY EIGENVALUES FOR SYNCHRONOUS ANALYSIS *** USER INFORMATION MESSAGE 3098 (ROTCDA) 3098.6 NO WHIRL MATRIX WAS CALCULATED; CAMPBELL DIAGRAM IS ESTABLISHED BUT WHIRL DIRECTION AND CONVERSION TO ROTATING SYSTEM CANNOT BE ED CALCULAT *** USER INFORMATION MESSAGE 3098 (ROTCDA) 3098.7 NO WHIRL MATRIX WAS CALCULATED; CAMPBELL DIAGRAM IS ESTABLISHED BUT WHIRL DIRECTION AND CONVERSION TO FIXED SYSTEM CANNOT BE CALCULATED *** USER WARNING MESSAGE 3098 (ROTCDA) 3099.0 SELECTED COORDINATE SYSTEM %1 NOT FOUND *** USER FATAL MESSAGE 3100 (NXNADAMS) 3100.1 ADAMS MNF TRANSFER HAS NOT BEEN INITIALIZED *** USER FATAL MESSAGE 3100 (NXNADAMS) 3100.2 ERROR PROCESSING ELEMENT FACES FOR ADAMS MNF *** USER FATAL MESSAGE 3100 (NXNADAMS) 3100.3 ERROR PROCESSING NODE GEOMETRY FOR ADAMS MNF *** USER FATAL MESSAGE 3100 (NXNADAMS) 3100.4 ERROR PROCESSING NODAL MASS AND INERTIAS FOR ADAMS MNF (POSSIBLY INSUFFICIENT MEMORY) *** USER FATAL MESSAGE 3100 (NXNADAMS) 3100.5 ERROR PROCESSING GENERAL MATRIX DATA (I.E. MODAL PARAMETERS) FOR ADAMS MNF *** USER FATAL MESSAGE 3100 (NXNADAMS) 3100.6 ERROR PROCESSING MODE SHAPE DATA FOR ADAMS MNF (POSSIBLY INSUFFICIENT MEMORY)

189 *** USER FATAL MESSAGE 3100 (NXNADAMS) 3100.7 ERROR WRITING OUT ADAMS MODAL NEUTRAL FILE (MNF) *** USER FATAL MESSAGE 3100 (NXNADAMS) 3100.8 INVALID UNITS ENTRIES FOR ADAMS MNF CREATION *** USER WARNING MESSAGE 3100 (NXNADAMS) 3100.9 WARNING GENERATED FROM ADAMS MNF *** USER FATAL MESSAGE 3100 (NXNADAMS) 3100.10 ERROR GENERATED FROM ADAMS MNF *** USER FATAL MESSAGE 3100 (NXNADAMS) 3100.11 ERROR READING UNITS DATA BLOCK *** USER FATAL MESSAGE 3100 (NXNADAMS) 3100.12 ERROR READING CASES DATA BLOCK *** USER FATAL MESSAGE 3100 (NXNADAMS) 3100.13 ERROR PROCESSING MODAL STRESS DATA FOR ADAMS MNF (POSSIBLY INSUFFICIENT MEMORY) *** USER FATAL MESSAGE 3100 (NXNADAMS) 3100.14 ERROR PROCESSING MODAL STRAIN DATA FOR ADAMS MNF (POSSIBLY INSUFFICIENT MEMORY) *** USER WARNING MESSAGE 3100 (NXNADAMS) 3100.15 INVALID OUTPUT COORDINATE SYSTEM FOR SURFACE OR VOLUME MUST BE ZERO. - O THE MNF. THESE STRESSES/STRAINS WILL NOT BE WRITTEN T *** USER FATAL MESSAGE 3100 (NXNADAMS) 3100.16 THE SKETCH FILE UNIT NUMBER SPECIFIED FOR THE PSETID DESCRIBER HAS NOT BEEN ASSIGNED. PLEASE ASSIGN SKT='SKETCH_FILE_NAME' UNIT=UNIT_NUMBER. *** USER FATAL MESSAGE 3100 (NXNADAMS) 3100.17 ERROR PROCESSING MASS INVARIANT DATA FOR ADAMS MNF (POSSIBLY INSUFFICIENT MEMORY) *** USER INFORMATION MESSAGE 3100 (NXNADAMS) 3100.18 GLOBAL MASS/INERTIA NOT PRESENT; PROPERTIES WILL BE GENERATED. PARAM,GRDPNT ,VALUE; WHERE VALUE> - 1 WILL CAUSE THE GRID POINT WEIGHT GENERATOR TO BE EXECUTED, PRODUCING THE GLOBAL MASS/INERTIA. *** USER WARNING MESSAGE 3101 (ROTCSD) 3101.0 MORE THAN 30 INSTABILITIES FOUND.

190 CHECK THE RESULTS *** USER FATAL MESSAGE 3102 (ROTCZG) 3102.0 NO SCALAR INDEX LIST PRESENT *** USER FATAL MESSAGE 3102 (ROTCZG) 3102.1 NO GRID POINT TABLE PRESENT *** USER FATAL MESSAGE 3102 (ROTCZG) 3102.2 NO MASS MATRIX PRESENT *** USER FATAL MESSAGE 3102 (ROTCZG) 3102.3 NO COORDINATE DATA PRESENT *** USER FATAL MESSAGE 3102 (ROTURS) 3102.4 INPUT TABLE NOT PRESENT; UNIQUE ROTOR SPEEDS COULD NOT BE CALCULATED *** USER WARNING MESSAGE 3103, 3103.0 EITHER OF DATA BLOCKS%1 EMGCOR OF EMG MODULE FINDS OR %2 ABSENT AND THUS %3. MATRIX WILL NOT BE FORMED. *** USER WARNING MESSAGE 3103, 3103.1 EMGCOR OF EMG MODULE FINDS DATA BLOCK %1 ABSENT AND THUS WILL NOT BE FORMED. *** SYSTEM FATAL MESSAGE 3104, 3104.0 EMGCOR FINDS EST (ASSUMED DATA BLOCK%1) MISSING. EMG MODULE COMPUTATIONS THUSLY LIMITED. *** USER FATAL MESSAGE 3105 (ROTEDT) 3105.0 INPUT TABLE MISSING FOR TABLE EDITOR *** USER FATAL MESSAGE 3106 (ROTEQD) 3106.0 MORE THAN ONE ZERO ROTOR SPEED IN MODE TRACKING PROCESS *** USER FATAL MESSAGE 3107 (NXNRFI) 3107.1 RECURDYN RFI TRANSFER HAS NOT BEEN INITIALIZED *** USER FATAL MESSAGE 3107 (NXNRFI) 3107.2 ERROR PROCESSING ELEMENT FACES FOR RECURDYN RFI *** USER FATAL MESSAGE 3107 (NXNRFI) 3107.3 ERROR PROCESSING NODE GEOMETRY FOR RECURDYN RFI *** USER FATAL MESSAGE 3107 (NXNRFI) 3107.4 ERROR PROCESSING NODAL MASS AND INERTIAS FOR RECURDYN RFI (POSSIBLY INSUFFICIENT MEMORY) *** USER FATAL MESSAGE 3107 (NXNRFI) 3107.5 ERROR PROCESSING GENERAL MATRIX DATA (I.E. MODAL PARAMETERS)

191 FOR RECURDYN RFI *** USER FATAL MESSAGE 3107 (NXNRFI) 3107.6 ERROR PROCESSING MODE SHAPE DATA FOR RECURDYN RFI (POSSIBLY INSUFFICIENT MEMORY) *** USER FATAL MESSAGE 3107 (NXNRFI) 3107.7 ERROR WRITING OUT RECURDYN FLEX INPUT (RFI) FILE *** USER FATAL MESSAGE 3107 (NXNRFI) 3107.8 INVALID UNITS ENTRIES FOR RECURDYN RFI CREATION *** USER WARNING MESSAGE 3107 (NXNRFI) 3107.9 WARNING GENERATED FROM RECURDYN RFI *** USER FATAL MESSAGE 3107 (NXNRFI) 3107.10 ERROR GENERATED FROM RECURDYN RFI *** USER FATAL MESSAGE 3107 (NXNRFI) 3107.11 ERROR READING UNITS DATA BLOCK *** USER FATAL MESSAGE 3107 (NXNRFI) 3107.12 ERROR READING CASES DATA BLOCK *** USER FATAL MESSAGE 3107 (NXNRFI) 3107.13 ERROR PROCESSING MODAL STRESS DATA FOR RECURDYN RFI (POSSIBLY INSUFFICIENT MEMORY) *** USER FATAL MESSAGE 3107 (NXNRFI) 3107.14 ERROR PROCESSING MODAL STRAIN DATA FOR RECURDYN RFI (POSSIBLY INSUFFICIENT MEMORY) *** USER WARNING MESSAGE 3107 (NXNRFI) 3107.15 INVALID OUTPUT COORDINATE SYSTEM FOR SURFACE OR - MUST BE ZERO. VOLUME THESE STRESSES/STRAINS WILL NOT BE WRITTEN TO THE RFI. *** USER FATAL MESSAGE 3107 (NXNRFI) 3107.16 ERROR PROCESSING MASS INVARIANT DATA FOR RECURDYN RFI (POSSIBLY INSUFFICIENT MEMORY) *** USER INFORMATION MESSAGE 3107 (NXNRFI) 3107.17 GLOBAL MASS/INERTIA NOT PRESENT; PROPERTIES WILL BE GENERATED. PARAM,GRDPNT,VALUE; WHERE VALUE> - 1 WILL CAUSE THE GRID POINT WEIGHT GENERATOR TO BE EXECUTED, PRODUCING THE GLOBAL MASS/INERTIA. *** USER FATAL MESSAGE 3108 (ROTWHD) 3108.0 THERE ARE NO REAL EIGENVECTORS;

192 WHIRL DIRECTION CANNOT BE CALCULATED *** USER FATAL MESSAGE 3108 (ROTWHD) 3108.1 THERE ARE NO IMEGINARY EIGENVECTORS; WHIRL DIRECTION CANNOT BE CALCULATED *** USER FATAL MESSAGE 3109 (LCGEN) 3109.0 ROTORD %1 REFERENCED BY RMETHOD CASE CONTROL NOT FOUND *** USER FATAL MESSAGE 3110 (NXNMATLB) 3110.1 MATLAB SCRIPT FILE TRANSFER HAS NOT BEEN INITIALIZED *** USER FATAL MESSAGE 3110 (NXNMATLB) 3110.2 ERROR PROCESSING GENERAL MATRIX DATA (I.E. MODAL PARAMETERS) FOR MATLAB SCRIPT FILE *** USER FATAL MESSAGE 3110 (NXNMATLB) 3110.3 ERROR PROCESSING MODE SHAPE MATRIX FOR MATLAB SCRIPT FILE (POSSIBLY INSUFFICIENT MEMORY) *** USER FATA L MESSAGE 3110 (NXNMATLB) 3110.4 ERROR PROCESSING STATE SPACE MATRICES FOR MATLAB SCRIPT FILE (POSSIBLY INSUFFICIENT MEMORY) *** USER FATAL MESSAGE 3110 (NXNMATLB) 3110.5 ERROR PROCESSING STATE SPACE DOF VECTORS FOR MATLAB SCRIPT FILE (POSSIBLY INSUFFICIENT MEMORY) *** USER FATAL MESSAGE 3111 (NXNSMPK) 3111.1 SIMPACK FBI TRANSFER HAS NOT BEEN INITIALIZED *** USER FATAL MESSAGE 3111 (NXNSMPK) 3111.2 ERROR PROCESSING ELEMENT FACES FOR SIMPACK FBI *** USER FATAL MESSAGE 3111 (NXNSMPK) 3111.3 ERROR PROCESSING NODE GEOMETRY FOR SIMPACK FBI *** USER FATAL MESSAGE 3111 (NXNSMPK) 3111.4 ERROR PROCESSING NODAL MASS AND INERTIAS FOR SIMPACK FBI (POSSIBLY INSUFFICIENT MEMORY) *** USER FATAL MES SAGE 3111 (NXNSMPK) 3111.5 ERROR PROCESSING GENERAL MATRIX DATA (I.E. MODAL PARAMETERS) FOR SIMPACK FBI *** USER FATAL MESSAGE 3111 (NXNSMPK) 3111.6 ERROR PROCESSING MODE SHAPE DATA FOR SIMPACK FBI (POSSIBLY

193 INSUFFICIENT MEMORY) *** USER FATAL MESSAGE 3111 (NXNSMPK) 3111.7 ERROR WRITING OUT SIMPACK FLEXIBLE BODY INPUT (FBI) FILE *** USER FATAL MESSAGE 3111 (NXNSMPK) 3111.8 INVALID UNITS ENTRIES FOR SIMPACK FBI CREATION *** USER WARNING MESSAGE 3111 (NXNSMPK) 3111.9 WARNING GENERATED FROM SIMPACK FBI *** USER FATAL MESSAGE 3111 (NXNSMPK) 3111.10 ERROR GENERATED FROM SIMPACK FBI *** USER FATAL MESSAGE 3111 (NXNSMPK) 3111.11 ERROR READING UNITS DATA BLOCK *** USER FATAL MESSAGE 3111 (NXNSMPK) 3111.12 ERROR READING CASES DATA BLOCK *** USER FATAL MESSAGE 3111 (NXNSMPK) 3111.13 ERROR PROCESSING MODAL STRESS DATA FOR SIMPACK FBI (POSSIBLY INSUFFICIENT MEMORY) *** USER FATAL MESSAGE 3111 (NXNSMPK) 3111.14 ERROR PROCESSING MODAL STRAIN DATA FOR SIMPACK FBI (POSSIBLY INSUFFICIENT MEMORY) *** USER WARNING MESSAGE 3111 (NXNSMPK) 3111.15 INVALID OUTPUT COORDINATE SYSTEM FOR SURFACE OR MUST BE ZERO. VOLUME - THESE STRESSES/STRAINS WILL NOT BE WRITTEN TO THE FBI. *** USER FATAL MESSAGE 3111 (NXNSMPK) 3111.16 ERROR PROCESSING MASS INVARIANT DATA FOR SIMPACK FBI (POSSIBLY INSUFFICIENT MEMORY) *** USER INFORMATION MESSAGE 3111 (NXNSMPK) 3111.17 GL OBAL MASS/INERTIA NOT PRESENT; PROPERTIES WILL BE GENERATED. PARAM,GRDPNT,VALUE; WHERE VALUE> - 1 WILL CAUSE THE GRID POINT WEIGHT GENERATOR TO BE EXECUTED, PRODUCING THE GLOBAL MASS/INERTIA. *** USER INFORMATION MESSAGE 3112, 3112.0 ELEMENTS CONGRUENT TO ELEMENT ID =%1 WILL BE RE - COMPUTED AS THERE IS INSUFFICIENT CORE AT THIS MOMENT TO HOLD DICTIONARY DATA. *** USER FATAL MESSAGE 3118. 3118.0 ROD ELEMENT WITH ID =%1 HAS ILLEGAL GEOMETRY OR

194 CONNECTIONS. LOC CODE =%2 *** USER WARNING MESSAGE 3199, 3199 .0 NON - FATAL MESSAGES MAY HAVE BEEN LOST BY ATTEMPTING TO QUEUE MORE THAN %1 MESSAGES. LOGIC ERROR DETECTED BY SUBROUTINE%1%2 = LOCATE CODE 3200.0 OR VALUE. *** USER WARNING MESSAGE 3200 3200.1 IFLAG = %1 *** SYSTEM FATAL MESSAGE 3200 (TRLGCD/S and FRRD1A) 3200.2 -- JFLAG = LOGIC ERROR %1 ENCOUNTERED IN SUBROUTINE %2 %3 USER ACTION: REPORT THIS PROBLEM TO SIEMENS PLM SOFTWARE CUSTOMER SUPPORT SYSTEM FATAL MESSAGE 3200 (SECNV1/SECNV2/SECNV3 and *** 3200.3 BDYINF/BDYINA/BDYINP) LOGIC ERROR %1 ENCOUNTERED IN SUBROUTINE %2 USER ACTION: REPORT THIS PROBLEM TO SIEMENS PLM SOFTWARE CUSTOMER SUPPORT FIAT OVERFLOW IN SUBROUTINE %1 3201.0 SYSTEM FATAL MESSAGE 3201 (ELFDR) *** 3201.1 PROGRAMMER INFORMATION : JSUB = %1 IMSG = %2 LOC= %3 FILE = %4 USER ACTION : CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM WARNING MESSAGE 3201 (COMPRS) 3201.2 PROGRAMMER INFORMATION :%1 : CONTACT SIEMENS PLM SOFTWARE CUSTOMER USER ACTION SUPPORT. DATA POOL DICTIONARY (DPD) OVERFLOW IN SUBROUTINE %1 3202.0 *** SYSTEM FATAL MESSAGE 3202 (DBSPC) 3202.1 PROGRAMMER INFORMATION: THE LOGICAL FILE NAME %1 CAN NOT BE FOUND. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. - - NU AN ILLEGAL VALUE OF HAS BEEN 3203.0 SPECIFIED UNDER MATERIAL ID%1 FOR ELEMENT ID%2 User information: Plate elements must not have Poisson's ratio equal to + 1.0 or 1.0. - Solid elem ents must not have Poisson's ratio equal to +0.5 or - 1.0. UNABLE TO FIND SELECTED SET (%1) IN TABLE (%2) IN 3204.0 SUBROUTINE (%3).

195 User information: A load set ID referenced either in Case Control or on a LOAD Bulk the structure or for the current Data entry does not exist for superelement. This message can also indicate that a LOAD Bulk Data entry has referenced another LOAD Bulk Data entry, which is not permitted. Remove the ID of existent LOAD from the Bulk Data entry. the non - e will also be output if the case control LOAD card references This messag only SPCD cards. If this is the case, this message can be ignored as there are no follower forces associated with SPCD loading. *** SYSTEM FATAL MESSAGE 3300 (DSVG1P) 3300.0 INVALID VALUE = %1 SUPPLIED TO 6TH PARAMETER. *** SYSTEM WARNING MESSAGE 3300 3300.1 INVALID PARAMETER %1 SUPPLIED TO MODULE DIAGONAL, COLUMN SUBSTITUTED *** SYSTEM WARNING MESSAGE 3300 (DVSKMD) 3300.2 INVALID ELEMENT TYPE = %1 ***SYSTEM FATAL MESSAGE 3300 (MACOFP) 3300.3 IMPROPER OP CODE P1 %1 *** SYSTEM FATAL MESSAGE 3300 (MTMD32) 3300.4 ILLEGAL VALUE FOR PARAMETER P2 = %1 - MODULE ABORTING *** USER FATAL MESSAGE 4010, 4010.0 TEMPP3 BULK DATA CARD WITH SET ID = %1 AND ELEMENT ID = %2 DOES NOT HAVE ASCENDING VALUES SPECIFIED FOR Z. User information: See TEMPP3 entry description in Section 5 of the NX NASTRAN Quick Reference Guide. *** USER FATAL MESSAGE 4011, 4011.0 ELEMENT TEMPERATURE SET%1 CONTAINS MULTIPLE TEMPERATURE DATA SPECIFIED FOR ELEMENT ID =%2 User information: Temperature for element is specified on more than one bulk data card. *** USER WARNING MESSAGE 4012, 4012.0 THERE IS NO ELEMENT, GRID POI NT, OR DEFAULT TEMPERATURE DATA FOR TEMPERATURE SET %1, WITH RESPECT TO ELEMENT ID = %2 User information: Required temperature data is probably missing from the Bulk Data. Check for TEMPD or for TREF on the MAT1 entry. *** USER FATAL MESS AGE 4013 (EDTL) 4013.0 INSUFFICIENT MEMORY FOR TEMPERATURE SETS.

196 ***USER INFORMATION MESSAGE 4015. 4015.0 TABLE NAMED %1 PUNCHED ONTO %2 CARDS. *** USER FATAL MESSAGE 4016, 4016.0 THERE IS NO TEMPERATURE DATA FOR ELEMENT %1 IN SET %2 User information: Required temperature data is probably missing from Bulk Data. *** USER FATAL MESSAGE 4016, (GETEMP) 4016.1 THERE ARE NO TEMPERATURES FOR %1 ELEMENT %2 IN SET %3 User information: Required temperature data is probably missing from Bulk Data. *** USER FATAL MESSAGE 4017 4017.1 ESTNL AND FILE (%1) ARE NOT PROPERLY ALIGNED *** USER FATAL MESSAGE 4018 4018.0 UNEXPECTED ERROR ENCOUNTERED IN NLCETT2. USER INFORMATION: PLE ASE CONTACT NASTRAN DEVELOPMENT AND SUPPORT. *** USER FATAL MESSAGE 4018.1 4018.1 ERROR IN DTEMP CARD %1. TIME INTERVAL FOR INTERPOLATION NOT FOUND. USER INFORMATION: PLEASE CONTACT NASTRAN DEVELOPMENT AND SUPPORT. *** USER FATAL MESSAGE 4018.2 4018.2 BOTH DTEMP AND TEMP(LOAD) SPECIFIED IN SUBCASE %1. *** USER FATAL MESSAGE 4018.3 4018.3 MISMATCH BETWEEN ELEMENT TYPES IN ETT AND ELDATA TABLES. USER INFORMATION: PLEASE CONTACT NASTRAN DEVELOPMENT AND SUPPORT. *** USER FATAL MESSAGE 4018.4 4018 .4 MISMATCH BETWEEN ELEMENT IDS IN ETT AND ELDATA TABLES. USER INFORMATION: PLEASE CONTACT NASTRAN DEVELOPMENT AND SUPPORT. *** SYSTEM FATAL MESSAGE 4020 4020.0 TA1A HAS PICKED UP TEMPERATURE SET %1 AND NOT THE REQUESTED SET %2. System information: The requested temperature set ID for temperature dependent material properties cannot be found in data block GPTT. *** USER FATAL MESSAGE 4020 (CECORF) 4020.1 CORE IS INSUFFICIENT BY AMOUNT= %1 WORDS TO PROCESS ELEMENT WITH ID = %2 *** USER FATAL MESSAGE 4023 (TA1A) 4023.0

197 FINDS NO ELEMENT, GRID POINT, OR DEFAULT TEMPERATURE DATA FOR ELEMENT ID =%1 User information: Required temperature data is probably missing from Bulk Data. *** USER FATAL MESSAGE 4024. 4024.0 NO CYJOIN CARDS WERE SUPPLIED. User information: CYJOIN entries are required in cyclic symmetry problems to define the boundary points. *** USER WARNING MESSAGE 4025. 4025.0 NO SIDE 2 DATA FOUND. *** USER WARNING MESSAGE 4025. 4025.1 NO SIDE 1 DATA FOUND. User information: See CYJOIN entry description in Section 5 of the NX NASTRAN Quick Reference Guide. *** USER WARNING MESSAGE 4025. 4025.2 NO SIDE 2 DATA FOUND. *** USER WARNING MESSAGE 4025. 4025.3 NO SIDE 1 DATA FOUND. *** USER FATAL MESSAGE 4026. 4026.0 TOO MANY SIDE 1 CYJOIN BULK DATA CARDS. User information: Only one Side 1 entry is permitted. *** USER FATAL MESSAGE 4027. 4027.0 NUMBER OF ENTRIES IN SIDE 1(%1) NOT EQUAL TO NUMBEER IN SIDE 2(%2) (MINIMUM VALUE WILL BE PROCESSED) User information: on Side 2. Number of boundary points on Side 1 must be the same as *** USER FATAL MESSAGE 4028. 4028.0 THE CODE FOR GRID POINT %1 DOES NOT MATCH THE CODE FOR GRID POINT %2 *** USER FATAL MESSAGE 4029. 4029.0 GRID POINT %1 APPEARS IN BOTH SIDE LISTS. User information: A grid point cannot be on both Side 1 and Side 2. *** USER WARNING MESSAGE 4030. 4030.0 COMPONENT %1 OF GRID POINTS %2,%3 CANNOT BE CONNECTED. (GRID POINT %4 IS AT FAULT) *** USER WARNING MESSAGE 4032. 4032.0 NO COMPONENTS OF GRID POINTS %1 AND %2 WERE CONNECTED.

198 *** USER WARNING MESSAGE 4032. 4032.1 - SET. NO COMPONENTS OF GRID POINT %1 WERE IN THE A *** USER FATAL MESSAGE 4033 (IFP4) 4033.0 COORDINATE SYSTEM ID =%1 AS SPECIFIED ON AXIF ENTRY IS NOT PRESENT AMONG ANY OF CORD1C, CORD1S, CORD2C, OR CORD2S ENTRY TYPES. CYLINDRICAL TYPE ASSUMED FOR CONTINUING DATA CHECK. *** USER FATAL MESSAGE 4035 (IFP4) 4035.0 THE FLUID DENSITY HAS NOT BEEN SPECIFIED ON A BDYLIST ENTRY AND THERE IS NO DEFAULT FLUID DENSITY SPECIFIED ON THE AXIF ENTRY. User information: Required information missing from Bulk Data. *** USER FATAL MESSAGE 4037. 4037.0 GRID POINT %1 IS LISTED MORE THAN ONCE ON CYJOIN CARDS. *** USER FATAL MESSAGE 4038 (IFP4) 4038.0 RINGFL ENTRY HAS ID =%1 WHICH HAS BEEN USED. User information: An identification number of a RINGFL entry is not unique. *** USER FATAL MESSAGE 4040 (IFP4) 4040.0 ID =%1 APPEARS ON A BDYLIST ENTRY, BUT NO RINGFL ENTRY IS PRESENT WITH THE SAME ID. User information: All entries on BDYLIST card must be defined on a RINGFL entry. *** USER FATAL MESSAGE 4041, 4041.0 ID =%1 IS OUT OF PERMISSIBLE RANGE OF 1 TO 49 9999. User information: The identification number of a RINGFL is too large to be processed. *** USER FATAL MESSAGE 4042 (IFP4) 4042.0 COORDINATE SYSTEM IS CYLINDRICAL BUT RINGFL ENTRY ID =%1 HAS A NON - ZERO X2 VALUE. User information: The azimut hal angle of a RINGFL point must be zero. *** USER FATAL MESSAGE 4043 (IFP4) 4043.0 COORDINATE SYSTEM IS SPHERICAL BUT RINGFL ENTRY ID =%1 HAS A NON - ZERO X3 VALUE. *** USER FATAL MESSAGE 4044 (IFP4AD) 4044.0 RINGFL ENTRY ID =%1 HAS SPECIFIED A ZERO RADIAL LOCATION. User information: Fluid points cannot be located on the axis of symmetry.

199 *** USER FATAL MESSAGE 4045 (IFP4AD) 4045.0 - THE BOUNDARY LIST ENTRY FOR ID =%1 HAS A ZERO CROSS SECTION LENGTH. U ser information: A hydroelastic boundary can not be defined between two RINGFL points having the same location. Check BDYLIST and RINGFL entries. *** USER FATAL MESSAGE 4048 (IFP4) 4048.0 THE FLUID DENSITY HAS NOT BEEN SPECIFIED ON AN FSLIST ENTRY AND THERE IS NO DEFAULT FLUID DENSITY SPECIFIED ON THE AXIF ENTRY. User information: Required information missing from Bulk Data. *** USER FATAL MESSAGE 4050 (IFP4) 4050.0 FSLIST ENTRY HAS INSUFFICIENT IDF DATA, OR FSLIST DATA MISSING. User information: A referenced RINGFL point doesn't exist or the FSLIST entry is in error. At least two points must be defined. *** USER FATAL MESSAGE 4051 (IFP4) 4051.0 AN MPC ENTRY HAS A SET I D SPECIFIED = 102. SET 102 IS ILLEGAL WHEN FLUID DATA IS PRESENT. User information: This set identification number is reserved for internal use in hydroelastic problems. *** USER FATAL MESSAGE 4052 (IFP4) 4052.0 IDF =%1 ON A FREEPT ENTRY DOES NOT APPEAR ON ANY FSLIST ENTRY. User information: A referenced RINGFL point must also appear on a FSLIST entry. *** USER FATAL MESSAGE 4055 (IFP4) 4055.0 SET ID = 102 MAY NOT BE USED FOR SPC ENTRIES WHEN USING YDROELASTIC - FLUID ELEMENTS. THE H User information: This set identification number is reserved for internal use in hydroelastic problems. *** USER FATAL MESSAGE 4056, 4056.0 RECORD ID =%1 IS OUT OF SYNC ON DATA BLOCK NUMBER%2 AN IFP4 SYSTEM ERROR. U ser information: The record identification numbers are the values of LOCATE record ID. The data block numbers are the GINO file numbers. Error implies that IFP4 is possibly operating on the wrong data block. This system error should not occur. Message comes from IFP4B.

200 *** USER FATAL MESSAGE 4057 (IFP4) 4057.0 GRIDB ENTRY WITH ID =%1 HAS A REFERENCE IDF =%2 WHICH DOES NOT APPEAR IN A BOUNDARY LIST. User information: GRIDB points must be in the fluid boundary. *** USER FATAL MESSAGE 4058 (IFP4) 4058.0 THE FLUID DENSITY HAS NOT BEEN SPECIFIED ON A CFLUID ENTRY WITH ID =%1 AND THERE IS NO DEFAULT ON THE AXIF ENTRY. User information: Required data missing from the Bulk Data Section. 59 (IFP4) *** USER FATAL MESSAGE 40 4059.0 THE FLUID BULK MODULUS HAS NOT BEEN SPECIFIED ON A CFLUID ENTRY WITH ID =%1 AND THERE IS NO DEFAULT ON THE AXIF ENTRY. User information: Required data missing from the Bulk Data Section. *** SYSTEM FATAL MESSAGE 4060 (BMG) 4060.0 COORDINATE SYSTEM = %1 CAN NOT BE FOUND IN CSTM DATA System information: Data blocks MATPOOL or CSTM have been changed illegally. *** USER FATAL MESSAGE 4062 (IFP4) 4062.0 DMIG BULK DATA ENTRY SPECIFIES DATA BLOCK %1 WHICH ALSO APPEARS ON A DMIAX ENTRY. User information: One direct input matrix may not be specified by both types of bulk data entries. *** USER FATAL MESSAGE 4081 (IFP5) 4081.0 AXSLOT ENTRY IS NOT PRESENT OR IS INCORRECT. User information: Acoustic analysis data is prese nt and this entry is necessary. *** USER FATAL MESSAGE 4086 (IFP5) 4086.0 CELAS2 BULK DATA ENTRY HAS ID =%1 WHICH IS GREATER THAN 10000000 AND 10000000 IS THE LIMIT FOR CELAS2 ID WITH ACOUSTIC ANALYSIS ENTRIES PRESENT. User information: The program is generating CELAS2 entries and a possible conflict of ID numbers exists. *** USER FATAL MESSAGE 4087 (IFP5) 4087.0 SLBDY ID =%1 DOES NOT APPEAR ON ANY GRIDS ENTRIES. User information: The SLBDY entry has a point listed which does n ot exist in the data. *** USER FATAL MESSAGE 4088 (IFP5) 4088.0

201 ONE OR MORE OF THE FOLLOWING ID - - 1 HAVE S NOT EQUAL TO INCORRECT OR NO GEOMETRY DATA ID = %1 ID = %2 ID = %3 User information: The listed GRIDS points may have a bad radius or a slot width greater than geometrically possible. *** USER FATAL MESSAGE 4089 (IFP5) 4089.0 RHO AS SPECIFIED ON SLBDY OR AXSLOT ENTRY IS 0.0 FOR ID =%1 User information: A value of density is requ ired to formulate the slot boundary matrix terms. *** USER FATAL MESSAGE 4090 (IFP5) 4090.0 - ONE OF THE FOLLOWING NON ZERO IDENTIFICATION NUMBERS APPEARS ON SOME COMBINATION OF GRID, GRIDS, OR GRIDF BULK DATA ENTRIES. ID=%1 ID=%2 ID=%3 mation: User infor All GRID, SPOINT, EPOINT, GRIDS, and GRIDF data entries should have unique identification numbers. *** SYSTEM FATAL MESSAGE 4101 4101.0 PMTPCH UNABLE TO FIND NAME FOR DATA BLOCK %1 *** SYSTEM FATAL MESSAGE 4101 4101.1 MATPCH UNABLE TO FIND NAME FOR DATA BLOCK %1 *** USER INFORMATION MESSAGE 4103 4103.0 PMTPCH HAS PUNCHED MATRIX DATA BLOCK %1 ONTO %2 DMI CARDS. *** USER INFORMATION MESSAGE 4103 4103.1 MATPCH HAS PUNCHED MATRIX DATA BLOCK %1 ONTO %2 DMI CARDS. *** USER FATAL MESSAGE 4104 4104.0 ATTEMPT TO PUNCH MORE THAN 99999 DMI CARDS FOR A SINGLE MATRIX. *** USER INFORMATION MESSAGE 4105 (INPTX2) 4105.0 DATA BLOCK %1 HAS BEEN RETRIEVED FROM FORTRAN UNIT %2 THE ORIGINAL NAME OF DATA BLOCK ON THE FORTRAN UNIT WAS %3. User information: As each block is retrieved, its new and old names are printed. Check to be sure your DMAP and INPUTT2 statements are in sync. USER INFORMATION MESSAGE 4105 (INPTX4) *** 4106.0 DATA BLOCK %1 HAS BEEN RETRIEVED FROM FORTRAN UNIT %2 THE ORIGINAL NAME OF DATA BLOCK ON THE FORTRAN UNIT

202 WAS %3. User information: As each block is retrieved, its new and old names are printed. Check to be sure your DMAP and INPUTT4 statements are in sync. *** SYSTEM FATAL MESSAGE 4108 (LDINPT) 4108.0 MODULE DBLOAD UNABLE TO OPEN OUTPUT DATA BLOCK %1 *** SYSTEM FATAL MESSAGE 4108 4108.1 MODULE %1 UNABLE TO OPEN OUTPUT DATA BLOCK %2 *** USER INFORMATION MESSAGE 4109 (UNPHDR) 4109.0 THE LABEL IS %1 FOR NEUTRAL FILE FORTRAN UNIT %2 *** USER INFORMATION MESSAGE 4109 4109.2 THE LABEL IS %1 FOR FORTRAN UNIT %2 (MAXIMUM SIZE OF FORTRAN RECORDS WRITTEN =%3 WORDS.) (NUMBER OF FORTRAN RECO RDS WRITTEN =%4 RECORDS.) (TOTAL DATA WRITTEN FOR TAPE LABEL =%5 WORDS.) *** USER INFORMATION MESSAGE 4110 (UNDRVR) 4110.0 - - DATA SIMULATION ON NEUTRAL FILE FORTRAN UNIT %1 END OF *** USER INFORMATION MESSAGE 4110 (OUTPX2) 4110.1 - OF - DATA SIMULATION ON FORTRAN UNIT %1 END (MAXIMUM SIZE OF FORTRAN RECORDS WRITTEN =%2 WORDS.) (NUMBER OF FORTRAN RECORDS WRITTEN =%3 RECORDS.) (TOTAL DATA WRITTEN FOR EOF MARKER =%4 WORDS.) *** USER INFORMATION MESSAGE 4110 (OUTPN2) 4110.2 - OF DATA SIMULATION ON FORTRAN UNIT %1 END - (MAXIMUM SIZE OF FORTRAN RECORDS WRITTEN =%2 WORDS.) (NUMBER OF FORTRAN RECORDS WRITTEN =%3 RECORDS.) (TOTAL DATA WRITTEN FOR EOF MARKER =%4 WORDS.) *** USER INFORMATION MESSAGE 4110 (OUTPBN2) 4110.3 - OF - DATA SIMULATION ON FORTRAN UNIT %1 END (MAXIMUM SIZE OF FORTRAN RECORDS WRITTEN =%2 WORDS.) (NUMBER OF FORTRAN RECORDS WRITTEN =%3 RECORDS.) (TOTAL DATA WRITTEN FOR EOF MARKER =%4 WORDS.) *** USER FATAL MESSAGE 4113 4113.0 - MODULE %1 ILLEGAL VALUE FOR FIRST PARAMETER = %2 User information: See the NX NASTRAN DMAP Module Dictionary. *** USER INFORMATION MESSAGE 4114 4114.0 DATA BLOCK %1 WRITTEN TO NEUTRAL FILE FORTRAN UNIT %2 TRL = %3 User information: This mess age is issued for each nonpurged data block as it is written. *** USER INFORMATION MESSAGE 4114 4114.1

203 DATA BLOCK %1 WRITTEN TO NEUTRAL FILE FORTRAN UNIT %2 *** USER INFORMATION MESSAGE 4114 4114.11 DATA BLOCK %1 WRITTEN ON FORTRAN UNIT %2, TRL = %3 (MAXIMUM POSSIBLE FORTRAN RECORD SIZE =%4 WORDS.) (MAXIMUM SIZE OF FORTRAN RECORDS WRITTEN =%5 WORDS.) (NUMBER OF FORTRAN RECORDS WRITTEN =%6 RECORDS.) (TOTAL DATA WRITTEN FOR DATA BLOCK =%7 WORDS.) *** SYSTEM FATAL MESSAGE 4115 (OUTPX2) 4115.0 MODULE %1 - SHORT REC. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 4116 4116.0 MODULE DBUNLOAD UNABLE TO OPEN INPUT DATABLOCK %1 *** SYSTEM FATAL MESSAGE 4116 (OUTPX2) 4116.4 MODULE %1 UNABLE TO OPEN INPUT DATA BLOCK %2 USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 4116 (OUTPN2) 4116.5 MODULE OUTPUT2 UNABLE TO OPEN INPUT DATABLOCK %1 *** SYSTEM FATAL MESSAGE 4116 (OUTPBN2) 4116.6 MODULE OUTPUT2 UNABLE TO OPEN INPUT DATABLOCK %1 *** USER FATAL MESSAGE 4120 (OUTPX2) 4120.0 - ILLEGAL VALUE FOR FIRST PARAMETER =%2 MODULE %1 USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. User information: See the NX NASTRAN DMAP Module Dictionary. *** USER FATAL MESSAGE 4121 (IFS4P) 4121.0 ONLY ONE (1) AXIF ENTRY ALLOWED IN BULK DATA. User information: See Bulk Data Description in Section 5 of the NX NASTRAN Quick Reference Gu ide. *** USER FATAL MESSAGE 4122 (IFS4P) 4122.0 AXIF BULK DATA ENTRY NOT FOUND. *** USER FATAL MESSAGE 4123 (IFS4P) 4123.0 ONLY ONE (1) FLSYM ENTRY ALLOWED IN BULK DATA. User information: See Bulk Data Description in Section 5 of the NX NASTRAN Quick Reference Guide. *** USER WARNING MESSAGE 4124 (IFS3P) 4124.0 THE SPCADD OR MPCADD UNION CONSISTS OF A SINGLE SET. User information:

204 Only one SET was on an SPCADD or MPCADD entry. Th ere are no sets to add together. *** USER WARNING MESSAGE 4124 (IFS15P) 4124.1 THE NSMADD UNION CONSISTS OF A SINGLE SET. User information: Only one SET was on an NSMADD entry. There are no sets to add together. *** USER FATAL MESSAGE 4125 (IFS4P) 4125.0 MAXIMUM ALLOWABLE HARMONIC ID IS 99. ENTRY CONTAINS MAXIMUM = %1 User information: See Bulk Data Description in Section 5 of the NX NASTRAN Quick Reference Guide. *** USER FATAL MESSAGE 4126 (IFS4P) 4126.0 TA OR FORMAT OR NON UNIQUE NAME, DMIAX %1 BAD DA - User information: See Bulk Data Description in Section 5 of the NX NASTRAN Quick Reference Guide. *** USER WARNING MESSAGE 4127 (IFS15P) 4127.0 THE VALUE FIELD ON NSM OR NSM1 ENTRY SID = %1 IS BLANK. *** USER WARNING MESSAGE 4127 (IFS15P) 4127.1 THE VALUE FIELD ON NSM OR NSM1 ENTRY SID = %1 IS LESS OR EQUAL TO ZERO. *** USER WARNING MESSAGE 4128 (TA1NSM) 4128.0 NSMADD AND NSM/NSM1 HAVE THE SAME SID, AND NSM/NSM1'S SID = %1 IS NOT PART OF THE NSMADD SI LIST OF ENTRIES. *** USER WARNING MESSAGE 4128 (TA1NSM) 4128.1 UNDEFINED NSM/NSM1 SET = %1 *** USER WARNING MESSAGE 4128 (TA1NSM) 4128.2 UNDEFINED NONSTRUCTURAL MASS SET = %1 *** USER WARNING MESSAGE 4128 (TA1NSM) 4128.3 NSMADD AND NSML/NSML1 HAVE THE SAME SID, AND NSML/NSML1'S SID = %1 IS NOT PART OF THE NSMADD SI LIST OF ENTRIES. *** USER FATAL MESSAGE 4129 (GP6) 4129.0 The Area of Element %1 is Zero. USER FATAL MESSAGE 4129 (GP6) *** 4129.1 The Length of Element %1 is Zero. *** USER FATAL MESSAGE 4130 (OUTPX2) 4130.0 MODULE %1 - ILLEGAL TAPE CODE HEADER = %2 USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER

205 SUPPORT. *** USER WARNING MESSAGE 4131 (OUTPX2) 4131.0 - DOES NOT MATCH THIRD %2 DMAP %1 - FORTRAN TAPE ID CODE - PARAMETER - %3 . *** USER FATAL MESSAGE 4132 (GP6) 4132.0 - NSML1 Entry with Set ID %1 and Property Type "ELEMENT" has 1 D and D Elements Defined. - 2 *** USER WARNING MESSAGE 4133 (GP6) 4133.0 Property or Element ID %1 specified in NSML entry of SID %2 is not defined. *** USER WARNING MESSAGE 4133 (GP6) 4133.1 Property or Element ID %1 specified in NSML1 entry of SID %2 is not defined. *** USER FATAL MESSAGE 4134 (INPTX2) 4134.0 MODULE %1 ILLEGAL TAPE CODE HEADER = %2 - *** USER WARNING MESSAGE 4135 (INPTX2) 4135.0 - %1 - DOES NOT MATCH THIRD %2 DMAP USER TAPE ID CODE - %3 - . PARAMETER *** USER FATAL MESSAGE 4136 (INPTX2) 4136.0 USER TAPE ID CODE - - DOES NOT MATCH THIRD %2 DMAP %1 - - . PARAMETER %3 *** USER WARNING MESSAGE 4137 (INPTX2) 4137.0 ALL OUTPUT DATA BLOCKS FOR INPUTT2 ARE PURGED. *** USER WARNING MESSAGE 4138 (INPTX2) 4138.0 DATA BLOCK %1 (DATA BLOCK COUNT = %2) HAS PREVIOUSLY BEEN RETRIEVED FROM FORTRAN TAPE %3 AND WILL BE IGNORED. *** USER INFORMATION MESSAGE 4139 (INPTX2) 4139.0 DATA BLOCK %1 RETRIEVED FROM FORTRAN TAPE %2 (DATA BLOCK COUNT = %3) USER WARNING MESSAGE 4140 (INPTX2) *** 4140.0 SECONDARY VERSION OF DATA BLOCK HAS REPLACED EARLIER ONE. *** USER WARNING MESSAGE 4141 (INPTX2) 4141.0 ONE OR MORE DATA BLOCKS NOT FOUND ON FORTRAN TAPE. *** USER FATAL MESSAGE 4142 (INPTX2) 4142.0 ONE OR MORE DATA BLOCKS NOT FOUND ON FORTRAN TAPE. *** SYSTEM FATAL MESSAGE 4143. 4143.0 SEMAP WAS GENERATED ON A PRIOR RELEASE. IT MUST BE REGENERATED ON THIS RELEASE. System information: Format of SEMAP was changed between releases (Versions of NX

206 NASTRAN). Execute SEP1 in order to generate a new SEMAP. *** USER INFORMATION MESSAGE 4148 --- 4148.0 CSUPER%1 HAS BEEN WRITTEN ON UNIT%2, NUMBER OF CARD IMAGES=%3 User information: This message indicates the number of CSUPER entries punched by the TABPRT module. --- *** USER WARNING MESSAGE 4149 4149.0 MORE THAN 1000 CARD IMAGES ENCOUNTED IN PUNCHING CSUPER%1 ON UNIT%2 ONLY 1000 WERE PUNCHED. User information: s been made to punch more than 1000 CSUPER entries An attempt ha (8000 grid points on the boundary). *** USER FATAL MESSAGE 4152 (GP4) 4152.0 DUPLICATE ENFORCED DISPLACEMENT ON SPCD CARD. EXTERNAL ID =%1 DOF =%2 VALUE = %3 User information: zero enforced displacement value has been duplicated. An SPC with a non *** USER FATAL MESSAGE 4152 (GP4) 4152.1 DUPLICATE ENFORCED DISPLACEMENT ON SPC CARDS. EXTERNAL ID =%1 DOF =%2 VALUE = %3 User information: An SPC with a nonzero enforced displacement value has been duplicated. *** USER INFORMATION MESSAGE 4153. 4153.0 LEFT HANDED FBS TIME ESTIMATE TO FORM %1 CPU=%2, I/O=%3, TOTAL=%4, PASSES=%5 *** USER INFORMATION MESSAGE 4153. 4153.1 OD %1 TIME ESTIMATE TO FORM %2 - CPU=%3, I/O=%4, FBS METH TOTAL=%5, PASSES=%6 User information: I/O seconds are equivalent to CPU seconds based on the estimated number of blocks to be transferred between main and secondary storage and the blocks per second rate . Seconds printed is the sum of CPU and I/O. This message is printed when the time estimate is greater than the contents of SYSTEM(20). *** USER WARNING MESSAGE 4154 (SEP1C) 4154.0 SEELT ENTRY REFERENCES UNDEFINED SUPERELEMENT %1. ELEMENT ASSIGNMENTS ARE IGNORED. User information: Element reassignment specified by SEELT entry not possible because superelement specified does not exist. ***USER WARNING MESSAGE 4155 --- 4155.0

207 GRID POINTS FOR SECONDARY SUPERELEMENT%1 ARE COLLINEAR. CONFORMITY CHECKS NOT MADE. *** USER WARNING MESSAGE 4155. 4155.1 GRID POINTS FOR PRIMARY SUPER ELEMENT%1 WHICH IS REFERENCED BY SECONDARY%2 ARE COLLINEAR. CONFORMITY CHECKS NOT MADE. *** USER FATAL MESSAGE 4156. 4156.0 DIMENSIONS OR TYPE OF DATA BLOCK %1, SUPERELEMENT %2 TRAILER=(%3) ARE INCONSISTENT WITH SUPERELEMENT MAP. User information: The referenced superelement matrix is not consistent with the new st SEALL for the superelement. superelement map. Reque *** USER INFORMATION MESSAGE 4157 (DFMSA) --- 4157.1 PARAMETERS FOR SPARSE DECOMPOSITION OF DATA BLOCK %1( TYPE=%2) FOLLOW MATRIX SIZE =%3 ROWS NUMBER OF NONZEROES =%4 TERMS DIAGONAL NUMBER OF ZERO COLUMNS =%5 NUMBER OF ZERO TERMS =%6 *** SYSTEM INFORMATION MESSAGE 4157 (SITDRV) 4157.2 PARAMETERS FOR THE ITERATIVE SOLUTION WITH DATA BLOCK %1(TYPE = %2) FOLLOW MATRIX SIZE =%3 ROWS DENSITY =%4 STRING LENGTH =%5 AVG NUMBER OF STRINGS =%6 K NONZERO TERMS =%7 K FULL BAND WIDTH =%8 AVG MEMORY AVAILABLE =%9 K WORDS MIN MEMORY NEEDED =%10 K WORDS NUMBER OF RHS =%11 NUMBER OF PASSES =%12 OPTIMAL MEMORY =%13 K WORDS PREFACE CPU TIME =%14 SECONDS System information: This information is useful i n optimizing the performance of your run. When spill is indicated, the model is too large to fit into memory. The job may run faster by increasing the available memory (this will decrease the number of spill group). See the NX NASTRAN Installation and Operation Instructions for a description of these terms. See also the NX NASTRAN Numerical Methods User's Guide. *** SYSTEM INFORMATION MESSAGE 4157 (SITDRV) 4157.3 PARAMETERS FOR THE ITERATIVE SOLUTION WITH DATA BLOCK %1(TYPE = %2) FOLLOW MATR IX SIZE =%3 ROWS DENSITY =%4 GEOMETRIC DOFS =%5 HIERARCHIC DOFS =%6 STRING LENGTH =%7 AVG NUMBER OF STRINGS =%8 K NONZERO TERMS =%9 K FULL BAND WIDTH =%10 AVG

208 MEMORY AVAILABLE =%11 K WORDS MIN MEMORY NEEDED =%12 K WORDS SSES =%14 NUMBER OF RHS =%13 NUMBER OF PA OPTIMAL MEMORY =%15 K WORDS PREFACE CPU TIME =%16 SECONDS System information: This information is useful in optimizing the performance of your run. When spill is indicated, the model is too large to fit into memory. The increasing the available memory (this will job may run faster by decrease the number of spill groups). See the NX NASTRAN Installation and Operation Instructions for a description of these terms. See also the NX NASTRAN Numerical Methods User's Guide. *** USE R INFORMATION MESSAGE 4157 --- 4157.4 PARAMETERS FOR THE ITERATIVE SOLUTION WITH DATA BLOCK %1(TYPE = %2) FOLLOW MATRIX SIZE =%3 ROWS DENSITY =%4 NONZERO TERMS =%5 K NUMBER OF RHS =%6 MEMORY AVAILABLE =%7 K WORDS MIN MEMORY NEEDED =%8 K WORDS n: User informatio This information is useful in optimizing the performance of your run. When spill is indicated, the model is too large to fit into memory. The job may run faster by increasing the available memory (this will decrease the number of spill groups). the NX NASTRAN Installation and Operation Instructions for a See description of these terms. See also the NX NASTRAN Numerical Methods User's Guide. *** SYSTEM INFORMATION MESSAGE 4157 (SITDR3) 4157.5 PARAMETERS FOR THE ITERATIVE SOLUTION WITH DATA BLOCK %1(TYPE = %2) FOLLOW MATRIX SIZE =%3 ROWS DENSITY =%4 STRING LENGTH =%5 AVG NUMBER OF STRINGS =%6 K NONZERO TERMS =%7 K FULL BAND WIDTH =%8 AVG MEMORY AVAILABLE =%9 K WORDS IPAD =%10 NUMBER OF RHS =%11 System information: When spill is indicated, the model is too large to fit into memory. The job may run faster by increasing the available memory (this will decrease the number of spill groups). See the NX NASTRAN Installation and Operation Instr uctions for a description of these terms. See also the NX NASTRAN Numerical Methods User's Guide. *** USER INFORMATION MESSAGE 4157 --- 4157.6 PARAMETERS FOR THE ITERATIVE SOLUTION WITH DATA

209 BLOCK %1(TYPE = %2) FOLLOW MATRIX SIZE =%3 ROWS DENSITY =%4 NONZERO TERMS =%5 K FULL BAND WIDTH =%6 AVG MEMORY AVAILABLE =%7 K WORDS PREFACE CPU TIME =%8 SECONDS NUMBER OF RHS =%9 NUMBER OF PASSES =%10 User information: When spill is indicated, the model is too large to fit int o memory. The job may run faster by increasing the available memory (this will decrease the number of spill groups). See the NX NASTRAN Installation and Operation Instructions for a description of these terms. See also the NX NASTRAN Numerical User's Guide. Methods *** USER INFORMATION MESSAGE 4157 --- 4157.7 PARAMETERS FOR THE ITERATIVE SOLUTION WITH DATA BLOCK %1(TYPE = %2) FOLLOW MATRIX SIZE =%3 ROWS DENSITY =%4 NONZERO TERMS =%5 K FULL BAND WIDTH =%6 AVG MEMORY AVAILABLE =%7 K WORDS IPAD =%8 NUMBER OF RHS =%9 User information: When spill is indicated, the model is too large to fit into memory. The job may run faster by increasing the available memory (this will decrease the number of spill groups). d Operation Instructions for a See the NX NASTRAN Installation an description of these terms. See also the NX NASTRAN Numerical Methods User's Guide. *** USER INFORMATION MESSAGE 4157 4157.8 PARAMETERS FOR THE DISTRIBUTED ITERATIVE SOLUTION WITH DATA BLOCK %1(TYPE = %2) FOLLOW: *** USER INFORMATION MESSAGE 4157 --- 4157.9 PARAMETERS FOR %1E%2 DECOMPOSITION OF DATA BLOCK %3( TYPE=%4) FOLLOW MATRIX SIZE =%5 ROWS CPU TIME ESTIMATE =%6 SECONDS ADDITIONAL MEMORY =%7 K WORDS PASSIVE COLUMNS =%8 GROUPS ACTIVE COLUMNS =%9 MAX PAS SIVE COLUMNS =%10 MAX ACTIVE COLUMNS =%11 RMS PASSIVE COLUMNS =%12 AVG SPILL =%13 GROUPS I/O TIME ESTIMATE =%14 SECONDS SPILL ROWS =%15 AVG NZ NBR IN FACTOR =%16 K TERMS FACTOR STRNG LGTH =%17 AVG FACTOR STRNG SUM =%18 STRINGS User information: When spill is indicated, the model is too large to fit into memory. The job may run faster by increasing the available memory (this will

210 decrease the number of spill groups). See the NX NASTRAN Installation and Operation Instructions for a description of th ese terms. See also the NX NASTRAN Numerical Methods User's Guide. *** USER INFORMATION MESSAGE 4157 --- 4157.10 PARAMETERS FOR PARALLEL %1DECOMPOSITION OF DATA BLOCK %2( TYPE=%3) FOLLOW MATRIX SIZE =%4 ROWS CPU TIME ESTIMATE =%5 SEC MAX.HALFBAND WIDTH =%6 TERMS I/O TIME ESTIMATE =%7 SEC AVG.HALFBANDWIDTH =%8 TERMS ROLLING (0=N/1=Y) =%9 iN SKYLINE ELE. =%10 K TERMS REQUESTED PROC. =%11 CPUS - REQUI. WORK MEMORY =%12 K WORDS AVAIL. WORK MEMORY =%13 K WORDS User information: When spill is indicate d, the model is too large to fit into memory. The job may run faster by increasing the available memory (this will decrease the number of spill groups). See the NX NASTRAN Installation and Operation Instructions for a description of these terms. See al so the NX NASTRAN Numerical Methods User's Guide. *** USER INFORMATION MESSAGE 4157 --- 4157.11 PARAMETERS FOR PARALLEL %1DECOMPOSITION OF DATA BLOCK %2( TYPE=%3) FOLLOW MATRIX SIZE =%4 ROWS CPU TIME ESTIMATE =%5 SEC MAX.HALFBANDWIDTH =%6 TERMS I/O TIME ESTIMATE =%7 SEC AVG.HALFBANDWIDTH =%8 TERMS ROLLING (0=N/1=Y) =%9 - SKYLINE ELE. =%10 TERMS REQUESTED PROC. =%11 CPUS IN REQUI. WORK MEMORY =%12 K WORDS AVAIL. WORK MEMORY =%13 K WORDS User information: When spill i s indicated, the model is too large to fit into memory. The job may run faster by increasing the available memory (this will decrease the number of spill groups). See the NX NASTRAN Installation and Operation Instructions for a description of these ter ms. See also the NX NASTRAN Numerical Methods User's Guide. --- *** USER INFORMATION MESSAGE 4157 (DFMSA) 4157.12 PARAMETERS FOR PARALLEL SPARSE DECOMPOSITION OF DATA BLOCK %1( TYPE=%2) FOLLOW MATRIX SIZE =%3 ROWS NUMBER OF NONZEROES =%4 TERMS N UMBER OF ZERO COLUMNS =%5 NUMBER OF ZERO DIAGONAL TERMS =%6 SYSTEM (107) =%7 REQUESTED PROC. =%8 CPUS User information: When spill is indicated, the model is too large to fit into memory.

211 The job may run faster by increasing the available memory (this will decrease the number of spill groups). See the NX NASTRAN Installation and Operation Instructions for a description of these terms. See also the NX NASTRAN Numerical Methods User's Guide. *** USER INFORMATION MESSAGE 4157 --- 4157.13 PARAME TERS FOR SPARSE DECOMPOSITION OF DATA BLOCK %1( TYPE=%2) FOLLOW MATRIX SIZE =%3 ROWS NUMBER OF NONZEROES =%4 TERMS NUMBER OF ZERO COLUMNS =%5 NUMBER OF ZERO DIAGONAL TERMS =%6 User information: o memory. When spill is indicated, the model is too large to fit int The job may run faster by increasing the available memory (this will decrease the number of spill groups). See the NX NASTRAN Installation and Operation Instructions for a description of these terms. See also the NX NASTRAN Numerical User's Guide. Methods *** SYSTEM INFORMATION MESSAGE 4157 (PDDRV) 4157.16 LOCAL PARAMETERS AND TIMINGS FOR THE DISTRIBUTED PARALLEL SPARSE DECOMPOSITION *** SYSTEM INFORMATION MESSAGE 4157 (DFMSAP) 4157.17 PARAMETERS FOR PARALLEL SPARSE DECOMPOSITION OF DATA BLOCK %1( TYPE=%2) FOLLOW MATRIX SIZE =%3 ROWS NUMBER OF NONZEROES =%4 TERMS NUMBER OF ZERO COLUMNS =%5 NUMBER OF ZERO DIAGONAL TERMS =%6 SYSTEM (231) =%7 REQUESTED PROC. =%8 CPUS YSTEM INFORMATION MESSAGE 4157 (SITDRV) *** S 4157.18 PARAMETERS FOR THE ITERATIVE SOLUTION WITH DATA BLOCK %1(TYPE = %2) FOLLOW MATRIX SIZE =%3 ROWS DENSITY =%4 STRING LENGTH =%5 AVG NUMBER OF STRINGS =%6 K NONZERO TERMS =%7 K FULL BAND WIDTH =%8 AVG MEMORY AVAIL ABLE =%9 K WORDS MIN MEMORY NEEDED =%10 K WORDS NUMBER OF RHS =%11 NUMBER OF PASSES =%12 OPTIMAL MEMORY =%13 K WORDS PREFACE CPU TIME =%14 SECONDS IPAD =%15 IEXT =%16 System information: When spill is indicated, the model is too large to fit into memo ry. The job may run faster by increasing the available memory (this will decrease the number of spill groups). See the NX NASTRAN Installation and Operation Instructions for a

212 description of these terms. See also the NX NASTRAN Numerical s Guide. Methods User' *** SYSTEM INFORMATION MESSAGE 4157 (FBSTIM) 4157.19 TIMING DETAILS FOR FBS METHOD 2 COLSB=%1, TERMSL=%2, FWDFAC=%3, TEMP1=%4, TEMP2=%5, ARITH=%6 ***SYSTEM INFORMATION MESSAGE 4157 4157.20 P/C GROUPS FOLLOW.. *** SYSTEM INFORMATION MESSAGE 4157 4157.21 SPILL GROUPS FOLLOW.. ***SYSTEM INFORMATION MESSAGE 4157 4157.22 ARITH=%1 IOA =%2 SPILL=%3 IOSPL=%4 NBR SPILL ROWS=%5 P/C =%6 IOP/C=%7 IOCPU=%8 IOL =%9 *** SYSTEM INFORMATION MESSAGE 4157 4157.23 PARAMETERS FOR FRDGPU FOLLOW MATRIX SIZE =%1 NUMBER OF FREQUENCIES = %2 SYSTEM (107) =%3 SYSTEM (573) = %4 *** USER INFORMATION MESSAGE 4158 --- 4158.0 STATISTICS FOR %1E%2 DECOMPOSITION OF DATA BLOCK %3 FOLLOW NUMBER OF NEGATIVE TERMS ON FACTOR DIAGONAL =%4 *** USER INFORMATION MESSAGE 4158 --- 4158.1 STATISTICS FOR PARALLEL %1 DECOMPOSITION OF DATA BLOCK %2 *** USER INFORMATION MESSAGE 4158 (DFMSA) 4158.2 STATISTICS FOR SPARSE DECOMPOSITION OF DATA BLOCK ---- %1 FOLLOW NUMBER OF NEGATIVE TERMS ON FACTOR DIAGONAL = %2 MAXIMUM RATIO OF MATRIX DIAGONAL TO FACTOR DIAGONAL = %3 AT ROW NUMBER %4 User information: One, two or three of the statistics will be pr inted as follows: (1) negative terms on factor diagonal only if they exist; (2) maximum ratio only if it exceeds a threshold defined by the parameter MAXRATIO (default 1.0E7); (3) spill rows only if the problem spills. Depending on the context, these m essages may indicate modeling problems. The threshold may be changed with the parameter MAXRATIO, however, the user is cautioned against arbitrarily increasing the MAXRATIO value just to get the model to run. The cause of large MAXRATIOs should be inve stigated. This message is also generated (though the text is slightly different) when a Sturm check is performed during eigenvalue extraction. For this

213 case, the message does not generally indicate a modeling problem. d Operation Instructions for See the NX NASTRAN Installation an a discussion of these statistics. See also the NX NASTRAN Numerical Methods User's Guide. *** SYSTEN INFORMATION MESSAGE 4158. 4158.3 SPILL I/O =%1 SEC *** USER INFORMATION MESSAGE 4158 (SDCBOD) 4158.4 STATISTICS FOR %1E%2 DECOMPOSITION OF DATA BLOCK %3 FOLLOW MAXIMUM RATIO OF MATRIX DIAGONAL TO FACTOR DIAGONAL =%4 AT ROW NUMBER %5 User information: One, two or three of the statistics will be printed as follows: only if they exist; (2) maximum (1) negative terms on factor diagonal ratio only if it exceeds a threshold defined by the parameter MAXRATIO (default 1.0E7); (3) spill rows only if the problem spills. Depending on the context, these messages may indicate modeling y be changed with the parameter MAXRATIO, problems. The threshold ma however, the user is cautioned against arbitrarily increasing the MAXRATIO value just to get the model to run. The cause of large MAXRATIOs should be investigated. This message is also generated (though the tex t is slightly different) when a Sturm check is performed during eigenvalue extraction. For this case, the message does not generally indicate a modeling problem. See the NX NASTRAN Installation and Operation Instructions for a discussion of these stati stics. See also the NX NASTRAN Numerical Methods User's Guide. *** USER INFORMATION MESSAGE 4158 (SDCBOD) 4158.5 STATISTICS FOR %1E%2 DECOMPOSITION OF DATA BLOCK %3 FOLLOW NUMBER OF ROWS WRITTEN TO SPILL FILE =%4, RATIO =%5 *** USER INFORMATION MESSAGE 4158 (SDCBOD) 4158.6 STATISTICS FOR %1E%2 DECOMPOSITION OF DATA BLOCK %3 FOLLOW NUMBER OF NEGATIVE TERMS ON FACTOR DIAGONAL =%4 MAXIMUM RATIO OF MATRIX DIAGONAL TO FACTOR DIAGONAL =%5 AT ROW NUMBER %6 User information: One, two or th ree of the statistics will be printed as follows: (1) negative terms on factor diagonal only if they exist; (2) maximum ratio only if it exceeds a threshold defined by the parameter MAXRATIO (default 1.0E7); (3) spill rows only if the problem spills. D epending on the context, these messages may indicate modeling problems. The threshold may be changed with the parameter MAXRATIO, however, the user is cautioned against arbitrarily increasing the

214 MAXRATIO value just to get the model to run. The cause of large MAXRATIOs should be investigated. This message is also generated (though the text is slightly different) when a Sturm check is performed during eigenvalue extraction. For this case, the message does not generally indicate a modeling problem. Se e the NX NASTRAN Installation and Operation Instructions for a discussion of these statistics. See also the NX NASTRAN Numerical Methods User's Guide. *** USER FATAL MESSAGE 4179 (SEPTRE) 4179.0 UNIQUE DOWNSTREAM ID - - 2 SETREE CONTAINS NON S %1 AND % FOR SUPERELEMENT %3. *** USER FATAL MESSAGE 4179 (SEP1A) 4179.1 - UNIQUE DOWNSTREAM ID S %2 AND - TABLE %1 CONTAINS NON %3 FOR SUPERELEMENT %4 *** USER FATAL MESSAGE 4180 --- 4180.0 NUMBER OF GENERALIZED COORDINATES REQUIRED IS %1 ONLY%2 GENERALIZED COORDINATES AVAILABLE User information: An insufficient number of generalized coordinates has been specified by the user on the DYNRED Bulk Data entry. Bulk Data entry. *** USER INFORMATION MESSAGE 4181 --- 4181.0 NUMBER OF RO OTS BELOW %1 CYCLES IS %2 NUMBER OF GENERALIZED COORDINATES SET TO %3 User information: The message specifies the number of generalized coordinates as determined by the program. The number of generalized coordinates chosen (if autoselection is used) i s the minimum of the following quantities: 1. 1.5 times the number of natural frequencies below FMAX, rounded up to the next integer multiple of the number of initial random vectors. 2. The number of non - zero columns of the matrix. If there are any n atural frequencies below FMAX, a minimum of NIRV (from the DYNRED entry) generalized coordinates is always provided. If FMAX is below all natural frequencies and there are no physical degrees of freedom in the a set, User Fatal Message 4683 will result. *** USER FATAL MESSAGE 4182 (SEPTRE) 4182.0 SETREE REFERENCES UNDEFINED SUPERELEMENT %1. *** USER FATAL MESSAGE 4182 (SEP1A) 4182.1 TABLE %1 REFERENCES UNDEFINED SUPERELEMENT %2 *** USER WARNING MESSAGE 4183 (SEP1A) 4183.0 TABLE %1 DID NOT SPECIFY DOWNSTREAM CONNECTION FOR THE FOLLOWING SUPERELEMENTS.

215 USER INFORMATION: A RESIDUAL - ONLY MODEL IS ASSUMED. *** USER FATAL MESSAGE 4185 (SEPTRE) 4185.0 SETREE SPECIFIES CLOSED SUPERELEMENT CONNECTIVITY LOOP UPERELEMENT %1 BEGINNING WITH S SE ID DOWNSTREAM ID *** USER FATAL MESSAGE 4185 (SEP1A) 4185.1 TABLE %1 SPECIFIES CLOSED SUPERELEMENT CONNECTIVITY LOOP BEGINNING WITH SUPERELEMENT %2 SE ID DOWNSTREAM ID *** SYSTEM FATAL MESSAGE 4192 (SEDR) 4192.0 GRID POINT %1 IN SUPERELEMENT %2 IS NOT DEFINED IN GDNTAB FOR DOWNSTREAM SUPERELEMENT %3. System information: There are two probable causes for the failure: (1) User has made some changes to the geometry for the superelement and has not regenerated the SEMAP data block (or has fetched an incorrect version of SEMAP from the database); or (2) a programming logic error exists in SEP2 in preparing the data block subsets. *** SYSTEM FATAL MESSAGE 4192 (SEMA) 4192.1 GRID POINT %1 IN SUPERELEMENT %2 IS NOT DEFINED IN BGPDT FOR DOWNSTREAM SUPERELEMENT %3 System information: There are two probable causes for the failure: (1) User has made some changes to the geometry for the superelement and has not n incorrect regenerated the SEMAP data block (or has fetched a version of SEMAP from the database); or (2) a programming logic error exists in SEP2 in preparing the data block subsets. *** SYSTEM FATAL MESSAGE 4192 (SEMA) 4192.2 BOUNDARY POINT%1B IN SUPERELEMENT%2 IS NOT DEFINED IN BGPDT FOR DOWNSTREAM SUPERELEMENT%3 *** USER WARNING MESSAGE 4193 --- 4193.0 A GRID AND COMPONENT SPECIFICATION ON A %1SID = %2, DOES NOT APPEAR ON A DAREA OR SPCD CARD. User information: area specification is set to zero. The *** USER FATAL MESSAGE 4194. 4194.0 ROD ELEMENT %1 HAS ILLEGAL GEOMETRY DUE TO DEFORMATIONS. *** USER FATAL MESSAGE 4194. 4194.1 PENTA ELEMENT %1 HAS ILLEGAL GEOMETRY DUE TO DEFORMATIONS. *** USER FATAL MESSAGE 4194. 4194.2

216 HEXA ELEMENT %1 HAS ILLEGAL GEOMETRY DUE TO DEFORMATIONS. *** USER FATAL MESSAGE 4194. 4194.3 BEAM ELEMENT %1 HAS ILLEGAL GEOMETRY DUE TO DEFORMATIONS. *** USER FATAL MESSAGE 4194 (GTR3D) 4194.4 TRIA3 ELEMENT %1 HAS ILLEGAL GEOMETRY DUE TO DEFORMATIONS. *** USER FATAL MESSAGE 4194 (GTR3D) 4194.5 TRIAR ELEMENT %1 HAS ILLEGAL GEOMETRY DUE TO DEFORMATIONS. *** USER FATAL MESSAGE 4194. 4194.6 QUAD4 ELEMENT %1 HAS ILLEGAL GEOMETRY DUE TO DEFORMATIONS. *** USER FATAL MESSAGE 4194. 4194.7 QUADR ELEMENT %1 HAS ILLEGAL GEOMETRY DUE TO DEFORMATIONS. *** USER FATAL MESSAGE 4194. 4194.10 QUADR ELEMENT %1 HAS ILLEGAL GEOMETRY DUE TO DEFO RMATIONS. *** USER FATAL MESSAGE 4194. 4194.11 TRIAR ELEMENT %1 HAS ILLEGAL GEOMETRY DUE TO DEFORMATIONS. *** USER WARNING MESSAGE 4196, 4196.0 POINT ID =%1 .GE. %2 (MESSAGE NOT REPEATED FOR ANY OTHER SUCH POINTS) User information: The indicated point ID is greater than the maximum allowed. Only one such message is printed. *** USER WARNING MESSAGE 4197, 4197.0 MORE THAN %1 UNIQUE ENTRYS WILL NOT BE LISTED IN FULL. User information: Word size insufficient to hold the indicated number of unique entries. Additional unique entries will not be processed. Only one such message printed. *** USER WARNING MESSAGE 4198, 4198.0 UNABLE TO PRINT UNIQUE CONNECTIVITY LIST SORTED BY SUPERELEMENT ID DUE TO INSUFFICIENT CORE. ADDITIONAL CORE NEEDED =%1 WORDS. User information: The indicated additional memory is required to process the unique connectivity list sorted by superelement ID. *** USER WARNING MESSAGE 4200, 4200.0

217 KEYWORD %1 NOT RECOGNIZED. IT WILL BE IGNORED. User information: DIT keyword for superelement time estimation not in recognized list and is ignored. List of acceptable keywords is printed after first un recognized keyword is encountered. *** SYSTEM FATAL MESSAGE 4201 (GNFMID) 4201.0 THE DICTIONARY DESCRIPTION OF THE STIFFNESS MATRIX IS UNACCEPTABLE AT LOC= %1 EITHER IN FORM= %2 OR BAD SIL = %3 FOR ELEMENT ID = %4 System information: Programming error in processing stiffness matrix in nonlinear analysis. *** SYSTEM FATAL MESSAGE 4201 (NKUPTD) 4201.1 THE DICTIONARY DESCRIPTION OF THE STIFFNESS MARTIX IS UNACCEPTABLE TO %1 EITHER IN FORM=%2 OR BAD SIL =%3 FOR ELEMENT ID =%4 System information: Programming error in processing stiffness matrix in nonlinear analysis. *** SYSTEM FATAL MESSAGE 4202 (GNFM) 4202.0 CANNOT FIND CORRELATED ENTRIES IN THE EST, STIFFNESS, AND DIFFERENTIAL STIFFNESS MATRICES. LOC=%1 ELTYPE= %2 E LID=%3,%4,%5, System information: Programming error in processing stiffness matrix in nonlinear analysis. *** USER WARNING MESSAGE 4203 , 4203.0 THE SEMAP DATA BLOCK HAS BEEN MARKED NON - EXECUTABLE BY MODULE SEP1. User information: Warning messa ge is issued by SEP1 during generation of the superelement map. Fatal message is issued by SEP3 if further execution is attempted without regenerating the superelement map. *** SYSTEM WARNING MESSAGE 4203 (SEP1) 4203.1 THE SEMAP DATA BLOCK HAS BEEN MARKED NON - EXECUTABLE. ( SEE ERRORS NOTED ABOVE ) System information: Warning message is issued by SEP1 during generation of the superelement map. Fatal message is issued by SEP3 if further execution is attempted without r egenerating the superelement map. *** SYSTEM FATAL MESSAGE 4203. 4203.2 THE SEMAP DATA BLOCK HAS BEEN MARKED NON - EXECUTABLE BY SEP1.( SEE ERRORS NOTED IN CREATION RUN ) System information: Warning message is issued by SEP1 during generation of th e superelement map. Fatal message is issued by SEP3 if further execution is attempted without regenerating the superelement map.

218 *** USER WARNING MESSAGE 4204, 4204.0 RSPLINE %1 SEGMENT %2 HAS NO DEPENDENT DEGREES OF FREEDOM. User information: The RSPLINE has a segment with two independent grid points with no dependent grid points between them. *** USER INFORMATION MESSAGE 4214. 4214.0 ROW AND COLUMN%1 OF DATA BLOCK %2 ARE NULL. DIAGONAL TERM REPLACED WITH 1.0 User information: This message is printed (depending on the option selected) by the unsymmetric decomposition routine. If the default option is selected, this message will be treated as an error condition and the execution decomposition. aborted at the completion of the preface of the Schedule matrix partitioning or other technique to remove singularities. *** SYSTEM INFORMATION MESSAGE 4214 (SDCBOD) 4214.1 %1 SUBSTITUTED FOR DIAG. TERM OF LOWER TRIANGULAR FACTOR AT ROW %2 *** USER WARNING MESSAGE 4 215. 4215.0 %1%2%3 OF DATA BLOCK %4 IS NULL BUT %5%6%7 IS NOT. User information: The matrix is singular and cannot be decomposed by the unsymmetric decomposition routine. Examine and correct data which caused singular matrix to be generated. *** USER INFORMATION MESSAGE 4216 --- 4216.0 PARAMETERS FOR PARALLEL SPARSE UNSYM. DECOMP OF DATA BLOCK %1( TYPE=%2) FOLLOW MATRIX SIZE =%3 ROWS NUMBER OF NONZEROES =%4 TERMS NUMBER OF ZERO COLUMNS =%5 NUMBER OF ZERO DIAGONAL TERMS =%6 SYSTEM (107) =%7 REQUES TED PROC. =%8 CPUS *** USER INFORMATION MESSAGE 4216 --- 4216.1 PARAMETERS FOR SPARSE UNSYM. DECOMP OF DATA BLOCK %1( TYPE=%2) FOLLOW MATRIX SIZE =%3 ROWS NUMBER OF NONZEROES =%4 TERMS NUMBER OF ZERO COLUMNS =%5 NUMBER OF ZERO DIAGONAL TERMS =%6 *** USER INFORMATION MESSAGE 4216. 4216.2 PARAMETERS FOR UNSYMMETRIC DECOMPOSITION OF DATA BLOCK %1( TYPE=%2) FOLLOW MATRIX SIZE =%3 ROWS CPU TIME ESTIMATE =%4 SECS I/O TIME ESTIMATE =%5 SECS ACTIVE COLS =%6 AVG ACTIVE COLS =%7 MAX ACTIVE COLS*RO WS =%8 AVG

219 ACTIVE ROWS =%9 AVG ACTIVE ROWS =%10 MAX ACTIVE COLS*ROWS =%11 MAX SPILL =%12 GROUPS SPILL GROUP AVG =%13 ROWS SPILL TOTAL =%14 BLOCKS PASSIVE COLS/ROWS =%15 GROUPS PASSIVE COLS*ROWS =%16 AVG PASSIVE COLS*ROWS =%17 MAX WORDS NZ NBR IN LOWER =%19 ADDITIONAL MEMORY =%18 TERMS NZ NBR IN UPPER =%20 TERMS *** USER INFORMATION MESSAGE 4217. 4217.0 DECOMPOSITION OF DATA BLOCK %1 TERMINATED ACCORDING TO USER REQUEST. User information: The bit corresponding to 26 has been set in SYSTEM(69) indicating that the execution is to be terminated after execution of the preface of symmetric or unsymmetric decomposition. This occurs when a zero nue (SYSTEM(69)=16). diagonal occurs and SYSTEM(69) is not set to conti This message is often preceded by a message that indicates the offending column. *** USER INFORMATION MESSAGE 4217 4217.3 ITERATIVE SOLVER TERMINATED ACCORDING TO USER REQUEST (PREFONLY *** USER INFORMATION MESSAGE 4217. 4217.9 DECOMPOSITION OF DATA BLOCK %1 TERMINATED ACCORDING TO USER REQUEST. *** SYSTEM FATAL MESSAGE 4218. 4218.0 UNSYMMETRIC DECOMPOSITION OF DATA BLOCK %1 IS ABORTED DUE TO INSUFFICIENT MEMORY. REASON =%2 System informat ion: The preface of the unsymmetric decomposition has insufficient memory to execute. Reasons are: 100 minimum core= * MATRIX SIZE + 7 * BUFFSIZE not available. 190 nonzero terms in longest column do not fit. 218 active row vector does not fit. 222 n onzero terms in longest row do not fit. 302 active column vector does not fit. 320 spill definition table does not fit. 335 spill definition table does not fit. *** SYSTEM FATAL MESSAGE 4219. 4219.0 UDCOMP LOGIC ERROR %1. CONTENTS OF /UDCOMX/ FO LLOW... System information: A situation which the program is not prepared to handle has occurred. Contact SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER WARNING MESSAGE 4221 (SEP2SE) 4221.0

220 %1 ENTRY REFERENCES SECONDARY SUPERELEMENT %2 WHICH IS NOT ALLOWED. User information: The referenced entries define interior constraints of superelements. Secondary superelements automatically have the same interior constraints as their primary superel ement, hence no other constraints may be specified. Remove the entries listed. *** USER FATAL MESSAGE 4222 (SEP2SE) 4222.0 %1 ENTRY FOR SUPERELEMENT %2 REFERENCES INTERIOR POINT %3. User information: The referenced entries are used to place exte rior points in special boundary sets. Either change grid from interior to exterior, or - remove offending SE type bulk data entry. *** USER FATAL MESSAGE 4223 4223.0 %1 ENTRY FOR SUPERELEMENT %2 REFERENCES UNDEFINED POINT %3. User information: ese entries must reference exterior grid or scalar points for Th the superelement they reference. Inspect the SEMAP for the list of exterior degrees of freedom of the superelement. %1 ENTRY REFERENCES UNDEFINED SUPERELEMENT %2 4224.0 USER INFORMATION: THE %3 ENTRY WILL BE IGNORED. These entries define generalized coordinates of superelements. Inspect the SEMAP table for the list of superelement identification numbers in the model. *** USER FATAL MESSAGE 4224 (SEPMC1) 4224.1 SECONCT ENTRY REFERENCES UNDEFINED SUPERELEMENT %1 USER INFORMATION: THE SENQSET ENTRY WILL BE IGNORED. *** USER WARNING MESSAGE 4224 (SEPMA1) 4224.2 %1 ENTRY REFERENCES AN UNDEFINED SUPERELEMENT %2. User information: These entries define genera lized coordinates of superelements. Inspect the SEMAP table for the list of superelement identification numbers in the model. *** USER WARNING MESSAGE 4224 (SEPAQN) 4224.3 SENQSET ENTRY REFERENCES UNDEFINED SUPERELEMENT %1 USER INFORMATION: THE SENQSET ENTRY WILL BE IGNORED. *** USER FATAL MESSAGE 4224 (SEP1C) 4224.4 %1 ENTRY REFERENCES UNDEFINED SUPERELEMENT %2 User information: These entries define generalized coordinates of superelements. Inspect the SEMAP table for the list of supe relement identification numbers in the model.

221 --- , *** USER FATAL MESSAGE 4225 4225.0 THE NUMBER OF GENERALIZED COORDINATES IS%1, WHICH IS GREATER THAN THE ASET SIZE%2 User information: For generalized dynamic reduction, the user must define at l east as many ASET points as there are generalized coordinates. The user may either reduce the number of generalized coordinates or increase the number of ASET points. *** USER FATAL MESSAGE 4227 4227.0 ILLEGAL VALUE SPECIFIED FOR CTYPE PARAMETER User information: CTYPE can only take on the values DIH, AXI or ROT. *** USER FATAL MESSAGE 4228, 4228.0 TEMPERATURE SET %1 CONTAINS DUPLICATE GRID ID (%2 ). User information: A grid point has been referenced more than once within the tempera ture set indicated. *** USER FATAL MESSAGE 4229, 4229.0 TEMPERATURE SET %1 CONTAINS DUPLICATE GRID ID (%2 ). THIS TEMP SET HAS BEEN CREATED FROM A BUN/UNV FILE FOR A TEMPEX/DTEMPEX CARD. TYPICALLY THIS INDICATES THAT THE BUN FILE HAS MULTIPLE 2414 NODAL TEMPERATURE DATASETS (EXAMPLE: A NODAL TEMPERATURE DATASET AND A NODAL ABSOLUTE OR A NODAL TOTAL TEMPERATURE DATASET). CHECK THE BUN FILE FOR MULTIPLE 2414 NODAL TEMPERATURE DATASET. THE BUN FILE SHOULD HAVE ONLY ONE NODAL TEMPERATURE DATASET. User information: A grid point has been referenced more than once within the temperature set indicated. *** USER INFORMATION MESSAGE 4234. 4234.0 UFBS TIME ESTIMATE TO FORM %1( TYPE=%2 ) CPU=%3, I/O=%4,TOTAL=%5,PASSES=%6 *** USER INFORMATION MESSAGE 4234. 4234.1 UFBS METHOD %1 TIME ESTIMATE TO FORM %2 - CPU=%3, I/O=%4, TOTAL=%5, PASSES=%6 *** USER INFORMATION MESSAGE 4234. 4234.3 LEF T HANDED UFBS TIME ESTIMATE TO FORM %1CPU=%2, I/O=%3,TOTAL=%4,PASSES=%5 *** USER FATAL MESSAGE 4235 (SEP1C) 4235.0 CSUPER ENTRY %1 REFERENCES INTERIOR POINT %2 OF ITS PRIMARY SUPERELEMENT.

222 *** USER FATAL MESSAGE 4236 (SEP1C) 4236.0 NUMBER OF EXTERIOR GRID POINTS FOR SECONDARY SUPERELEMENT %1 IS NOT EQUAL TO NUMBER FOR PRIMARY SUPERELEMENT %2 User information: Probably an error on the CSUPER Bulk Data entry for the secondary superelement. *** USER FATAL MESSAGE 4237 (SEP1C) 4237.0 SEQSEP ENTRY REFERENCES SECONDARY SUPERELEMENT %1 WHICH WAS NOT DEFINED ON A CSUPER ENTRY. *** USER FATAL MESSAGE 4238 (SEP1C) 4238.0 NUMBER OF GRID POINTS ON SEQSEP %1 DOES NOT MATCH NUMBER ON REFERENCED CSUPER ENTRY. *** USER FATAL MESSAGE 4239 (SEP1C) 4239.0 SEQSEP %1 REFERENCES PRIMARY SUPERELEMENT %2 WHICH IS DEFINED AS A SECONDARY. *** USER FATAL MESSAGE 4240 (TA1BND) 4240.0 BEND ELEMENT %1 BEND RADIUS OR ARC ANGLE INCONSISTENT WITH GEOM OPTION User information: RB is nonzero on PBEND entry when GEOM option on CBEND entry is 1, 2, or 4 or RB is zero when GEOM option is 3 or AB is nonzero when when GEOM option is 1, 2, or 3 or B is .LE. zero or .GT. 180, when GEOM option is 4. Fix inconsistency and resubmit run. *** SYSTEM INFORMATION MESSAGE 4241 (COMIFP) 4241.0 --- , COMIFP ABORTED, %1%2 FILE COMPARISON OF CARD TYPE %3 ESTIMATED INCREASED CORE REQUIREMENT = %4 WORDS. System information: Increase core available by at least suggested amount. *** SYSTEM INFORMATION MESSAGE 4242 (COMIFP) 4242.0 --- -- CARD IMAGE(S) CANNOT BE RECONSTRUCTED %1 PRESENTLY, ( ICS=%2 ). THE CARD(S) REPRESENTED BY THIS %3 RECORD ARE %4 System information: Either insufficient information in the IFP file to reconstruct t he entry type or the entry is currently not implemented in module. ***USER FATAL MESSAGE 4243 (IFPDRV) 4243.0 ELEMENT TYPE %1 IS OUT OF SORT STARTING WITH ID %2 User information: Elements which were allowed to be input two per entry, must now be input in sort. Make two physical entries for the out - of - sort elements and resubmit. *** USER FATAL MESSAGE 4244 (SEP1C) 4244.0 SEQSEP %1 REFERENCES PRIMARY SUPERELEMENT %2 WHICH IS

223 UNDEFINED. User information: The PSID field should reference t he same primary superelement that the CSUPER entry does. Change the PSID field on the CSUPER and SEQSEP entries to reference a primary superelement. *** USER FATAL MESSAGE 4245 (SEP1C) 4245.0 SEQSEP %1 REFERENCES GRID POINT %2 WHICH IS NOT IN ERELEMENT %3 SUP User information: SEMAP table to find the exterior grid points of the primary superelement. Inspect the SEMAP table to find the exterior grid points of the primary superelement. *** USER FATAL MESSAGE 4246 (SEP1C) 4246.0 SEQSEP %1 REFERENCES UNDEFINED GRID POINT %2 User information: Same comments as Message 4245. *** USER FATAL MESSAGE 4247. 4247.0 SECONDARY SUPERELEMENT%1 AND PRIMARY SUPERELEMENT%2 HAVE SCALAR POINTS IN DIFFERENT SEQUENCE. User information: S calar points are included in the same sequence as grid points when establishing exterior grid and scalar point sequencing. *** USER INFORMATION MESSAGE 4248. 4248.0 NUMBER OF EXTERIOR GRID POINTS .LT. 3 FOR SECONDARY SUPERELEMENT%1 CONGRUENCE TES T WITH PRIMARY SUPERELEMENT%2 CANNOT BE PERFORMED. User information: The first three noncollinear exterior grid points of the secondary superelement and its primary superelement are used to establish local coordinate systems for grid point location and global coordinate congruence test. These tests will not be performed if there are less than three exterior grid points. A third point may be attached to the primary superelement by use of a CSUPEXT entry, if congruence tests are desired. It will not c hange the load paths of the structure. *** USER FATAL MESSAGE 4249. 4249.0 SUPERELEMENT PROCESSING REQUESTED BUT SEMAP DATA BLOCK IS MISSING. User information: One cause is improper use of PARAM,DLOAD or PARAM,NODATA. Another cause might be lack of a RESTART FMS statement on restart. Use PARAM,DBDICT,2 to print the contents of database.

224 *** USER FATAL MESSAGE 4251 (SEPSET) 4251.0 CONFLICTING DEFINITIONS FOR GRID POINT %1 ON SESET ENTRIES FOR SUPERELEMENTS %2 AND %3 Us er information: SESET entries are used to describe the interior grid point membership of superelements. A grid point may be interior to only one superelement. Remove one of the offending SESET entries. *** SYSTEM FATAL MESSAGE 4252 (SEMA) 4252.0 MATRIX %1 FOR UPSTREAM SUPERELEMENT %2 DOES NOT EXIST. USER INFORMATION: THE CURRENT SUPERELEMENT REQUIRES ALL OF ITS UPSTREAM SUPERELEMENT MATRICES FOR ASSEMBLY INTO THE CURRENT SUPERELEMENT. THE PROBABLE CAUSES ARE: ET OR DATABASE IS NOT 1. THE UPSTREAM SUPERELEMENT'S DBS ATTACHED. 2. THE UPSTREAM SUPERELEMENT DID NOT COMPLETE REDUCTION IN A PREVIOUS RUN. USER ACTION: RERUN THE REDUCTION OF THE UPSTREAM SUPERELEMENT AND/OR ENSURE THAT THE DBSET AND/OR DBLOCATE'D DATABASE WHICH CONTAINS THE UPSTREAM SUPERELEMENT MATRIX IS ATTACHED. *** SYSTEM FATAL MESSAGE 4253, 4253.0 GRID POINTS LISTED FOR DOWNSTREAM SUPERELEMENT IN BGPDT TABLE DO NOT MATCH CURRENT SEMAP. System information: If the downstream database is assembled, and then its bulk data is changed, its stored matrices and tables will not match the current SEMAP. This can also happen using multiple databases if an obsolete database is mounted. Perform the SEALL operation on the downstream atabase. superelement, or attach the correct downstream d Another possible cause is JCL errors that cause the old database to be improperly attached. *** USER FATAL MESSAGE 4254 (SEP1A) 4254.0 CSUPER ENTRY DEFINES SECONDARY SUPERELEMENT %1 WHICH IS ALREADY DEFINED AS A PRIMARY. User informatio n: Image, mirror and external superelements are defined on CSUPER entries. They may not have the same identification number as existing primary superelements. Change the SSID field on the CSUPER entry. *** SYSTEM FATAL MESSAGE 4255. 4255.0 UNSY MMETRIC DECOMPOSITION OF DATA BLOCK %1 FAILS AT ROW %2. UNABLE TO PIVOT. UII/MAXUIJ =%3 System information:

225 The matrix is undoubtedly singular. No terms which exceed the user specified threshold (or its default) were available to allow pivoting e place. Use SOL 60 or PARAM,CHECKOUT to determine where the to tak problems exist, and look for large MAXRATIOs. See Chapter 9 or the NX NASTRAN Numerical Methods User's Guide for further discussion. If this message is followed by UFM 3005, referring to subro utine MCE1, it can be because the DOF defined on the dependent set on an RBE3 entry are indeterminate and form a redundant set. See Section 9.4.1 and Remark 3 under RBE3 in the NX NASTRAN Quick Reference Guide, Section 5. See also Error Report 3486 in Chapter 17. *** SYSTEM FATAL MESSAGE 4255. 4255.1 INCORE UNSYMMETRIC DECOMPOSITION FAILS AT COLUMN %1 UNABLE TO PIVOT. *** SYSTEM INFORMATION MESSAGE 4256 --- , 4256.0 MPC SEQUENCE PROCESSING HAS COMPLETED. System information: Message appears if NOGO flag set information message to indicate - 1 that MPC processing has completed. Under condition where NEWSEQ= and MPC 0 on input, the NOGO flag is set at start of SEQP module processing. If MPC processing is successful, no error me ssages or other information messages would appear prior to termination of run. Some doubt may otherwise be left in the user's mind that anything had been done. *** USER FATAL MESSAGE 4257. 4257.0 S%1 FLUID MATRIX CALCULATION STOPPING BECAUSE ELEMENT AND%2 HAVE ZERO DISTANCE. User information: Elements noted have zero separation. Element centers are coincidental, not allowed for fluid interaction calculation. *** USER FATAL MESSAGE 4258. 4258.0 ELEMENT%1, WHICH IS ON FLUID STRUCTURE BOUNDARY, CROSSES A PLANE OF SYMMETRY. User information: None of the elements included in an MFLUID group may span a symmetry plane. *** USER FATAL MESSAGE 4259. (FMPH1D) 4259.0 ELIST VALUES ON MFLUID CARDS MAY NOT BOTH BE ZERO. User information: MFLUID entry parameters ELIST1 and ELIST2 may not both be zero. This constitutes a fluid group containing no element surfaces. ***USER WARNING MESSAGE 4260 (SBEN2D) 4260.0 %1 CHARACTERISTIC PARAMETER EXCE EDS RANGE OF APPLICABILITY FOR ELEMENT %2

226 User information: Stress output for the CBEND element may exceed the range of applicability for the following stress intensification options. For CBEND elements with hould be within the FSI option of 3; the bending parameter s - nu**2)) < = 1.0 0.5 < = T*RB/(r**2*SQRT(1 the pressure should be within 0. < = P*RB**2/(E*r*t) < = 0.1 For the CBEND elements with the FSI option of 2, 4 or 5 the bending parameter should be t*RB/(r**2*SQRT(1 - nu**2)) > = 0.2 arameter so equations are within range. Change p ***USER WARNING MESSAGE 4260 (EBEND) 4260.1 FLEXIBILITY FACTOR KX EXCEEDS RANGE OF APPLICABILITY FOR ELEMENT %1 User information: The flexibility factor should be greater or equal to 1.0. The analysis will continue with a value of 1.0. ***USER WARNING MESSAGE 4260 (EBEND) 4260.2 FLEXIBILITY FACTOR KY EXCEEDS RANGE OF APPLICABILITY FOR ELEMENT %1 User information: The flexibility factor should be greater or equal to 1.0. The analysis will continue with a value of 1.0. ***USER WARNING MESSAGE 4260 (EBEND) 4260.3 FLEXIBILITY FACTOR KZ EXCEEDS RANGE OF APPLICABILITY FOR ELEMENT %1 User information: The flexibility factor should be greater or equal to 1.0. The analysis will continue with a value of 1.0. ***USER WARNING MESSAGE 4260 (SBEN2D) 4260.4 STRESS INTENSITY FACTOR SX EXCEEDS RANGE OF APPLICABILITY FOR ELEMENT %1 User information: The stress intensity factor should be greater or equal to 1.0. The analysis will continue with a value of 1.0. ***USER WARNING MESSAGE 4260 (SBEN2D) 4260.5 STRESS INTENSITY FACTOR SY EXCEEDS RANGE OF APPLICABILITY FOR ELEMENT %1 User information: The stress intensity factor should be greater or equal to 1. 0. The analysis will continue with a value of 1.0. ***USER WARNING MESSAGE 4260 (SBEN2D) 4260.6 STRESS INTENSITY FACTOR SZ EXCEEDS RANGE OF APPLICABILITY FOR ELEMENT %1

227 User information: The stress intensity factor should be greater or equal to 1.0. The analysis will continue with a value of 1.0. ***USER WARNING MESSAGE 4260 (SBEN2D) 4260.7 ARC ANGLE LESS THAN APPLICABILITY ANGLE OF 30 DEGREES FOR ELEMENT %1 User information: e arc angle should be no less than 30 degrees for computing the Th plane stress intensification factor with FSI = 4. in - The analysis will continue with a value interpolated at 30 degrees. *** USER FATAL MESSAGE 4261 --- , 4261.0 THE INPUT MAXIMUM NUMB ER OF GENERALIZED COORDINATES IS ZERO. User information: NCMAX field on DYNRED entry is 0 or blank. Must be nonzero if QSETi or SEQSETi entries are not used. *** USER FATAL MESSAGE 4262 --- , 4262.0 MASS MATRIX IS NOT PRESENT OR IS PURGED. User information: Dynamic reduction computes approximate eigenvectors and therefore requires nonzero mass terms. Determine why no mass terms are present and rectify. Common causes are no mass density input on material propriate for massless superelement. cards, or dynamic reduction not ap *** USER WARNING MESSAGE 4265 --- , 4265.0 RBE3 RECORD HAS ERRONEOUS GRID %1 AND COMPONENTS %2 SPECIFIED. User information: set on the RBE3 entry All grid and components specified in the m - must also be specifie d either in the REFGRID and component or in the independent grid and components. *** SYSTEM FATAL MESSAGE 4266 --- , 4266.0 UNABLE TO FIND EXTERNAL GRID %1 IN THE EXTERNAL V. INTERNAL CONVERSION TABLE. System information: Either an internal logic error has occurred or erroneous data has been detected incoming to subroutine SEQMR for use in its MPC relations processing. *** USER FATAL MESSAGE 4267 --- , 4267.0 THE NUMBER OF PHYSICAL DEGREES OF FREEDOM PLUS GENERALIZED CO - ORDINATES %1 IS LESS THAN NCMAX %2 User information: The number of generalized coordinates specified by SPOINT and ASETi entries must match the NCMAX field. , *** SYSTEM FATAL MESSAGE 4268 --- 4268.0

228 MINIMUM CONNECTIVITY SEARCH FAILED AFTER %1 GRIDS SEQUENCED. ystem information: S Subroutine SEQMAC was unable to choose the next grid for sequencing before all grids had been sequenced. Possible cause believed to be machine failure or logic error. *** USER FATAL MESSAGE 4269. (FMPH1D) 4269.0 IST BULK DATA CARDS IS MISSING. ONE OR MORE EL User information: MFLUID entry selects an ELIST entry which cannot be located. *** USER FATAL MESSAGE 4270. (FMPH1D) 4270.0 SELECTED MFLUID BULK DATA CARD WITH ID %1 CANNOT BE FOUND. User information: MFLUID set selected in Case Control Section cannot be found. *** USER WARNING MESSAGE 4271. (FMPH1D) 4271.0 MFLUID SET%1 CONTAINS NO ELEMENTS BELOW THE FLUID FREE SURFACE. User information: Possible error in defining fluid free surface. No elemen ts are wetted. *** USER FATAL MESSAGE 4272. (FMPH1D) 4272.0 COORDINATE SYSTEM%1 USED FOR FLUID - STRUCTURE INTERACTION NOT DEFINED OR IS NOT A RECTANGULAR SYSTEM. User information: The coordinate system used to identify the orientations of the fre e surface (normal to X3) and the planes of symmetry (if any) must be rectangular. Review CID value on MFLUID entry. *** USER WARNING MESSAGE 4273. (FMPH1D) 4273.0 ELEMENT %1 HAS BEEN LISTED MORE THAN ONCE FOR FLUID STRUCTURE BOUNDARY. THIS COULD CAUSE UNPREDICTABLE OR INCORRECT RESULTS. User information: ELIST entries have referenced a given element ID more than once in an MFLUID group. This could cause unpredictable or incorrect results. *** USER WARNING MESSAGE 4274. (FMPH1D) 4274.0 %1 ELEMENTS SELECTED FOR FLUID STRUCTURE BOUNDARY CANNOT BE FOUND AMONG ALLOWED ELEMENT TYPES. User information: One or more element IDs referenced on ELIST entries were not present. *** SYSTEM FATAL MESSAGE 4275. 4275.0 DURING A %1 OP ERATION, UNIT = %2, DATA BLOCK=%3 , A %4 CONDITION OCCURRED. ( %5CODE=%6)

229 System information: Fatal error in subroutine IOVAX while processing I/O request. I/O ERROR is either program logic or possible machine error condition. - - DATA data block is from previous run, END OF If run is a restart and OF - DATA is may be caused by improper job setup. Otherwise, END - probably caused by a program logic error. If error is in job setup, correct DCL and resubmit. Otherwise, examine the RMS codes for a possible I/ O error or other type of machine error. If it does not appear to be caused by local hardware problems, forward the run to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. Another possible cause is that the disk is full. See Error X NASTRAN Reference Manual. Report 3161 in section 17.4 of N Another possible cause is that the BUFFSIZE needs to be increased. See Error Report 3484. If this corrects the error, please notify SIEMENS PLM SOFTWARE CUSTOMER SUPPORT so it can be better documented. SYSTEM FATAL MESSAGE 4276 (%1). *** 4276.0 ERROR CODE %1 PID=%2 USER INFORMATION: THIS ERROR MAY BE CAUSED BY EXCEEDING THE CAPACITY OF A SYSTEM RESOURCE. (E.G., ALLOCATED DISK IS FULL, OR MAXIMUM FILE SIZE HAS BEEN REACHED) AGE 4276 (%1). *** USER INFORMATION MESS 4276.1 TO OBTAIN %1 DUMP RESUBMIT JOB WITH DIAG 44 INSERTED IN THE EXECUTIVE CONTROL SECTION. *** SYSTEM FATAL MESSAGE 4276 (%1). 4276.2 ERROR CODE %1 PID=%2 *** USER FATAL MESSAGE 4277. 4277.0 GRID POINT%1 OF SECONDARY SUPERELEMENT%2 IS NOT IN SAME RELATIVE LOCATION AS GRID POINT%3 OF PRIMARY SUPERELEMENT%4 DELTA ALLOWED =%5 DELTA CALCULATED =%6 User information: All grid points for secondary superelement must be in the same location as for primary superelement. See PARAMeter CONFAC described in Section 6 of the NX NASTRAN Quick Reference Guide. *** USER FATAL MESSAGE 4278. 4278.0 GRID POINT%1 OF SECONDARY SUPERELEMENT%2 DOES NOT HAVE SAME GLOBAL ORIENTATION AS GRID POINT%3 OF PRIM ARY SUPERELEMENT%4 User information: All grid points for a secondary superelement must have the same global coordinate system as the primary superelement. See PARAMeter CONFAC described in Section 6 of the NX NASTRAN Quick Reference Guide.

230 *** USER FATAL MESSAGE 4281, 4281.0 POOR CHOICE OF DEPENDENT DEGREE OF FREEDOM ON RIGID ROD %1 User information: The dependent degree of freedom should not be perpendicular (or nearly so) to the RROD. *** USER FATAL MESSAGE 4282, (RBSRHD) 4282.0 UNDEFINED GRID POINT %1 RIGID ELEMENT %2 User information: The rigid element references a grid point that does not exist in the model, or is disjoint from the superelement being processed. Check the Bulk Data Section and the superelement SEMAP table f or the existence of the grid point referenced. *** USER FATAL MESSAGE 4283. (RBDNMD) 4283.0 ILL - CONDITIONED CONSTRAINT MATRIX FOR RIGID ELEMENT %1 User information: The independent degrees of freedom of a rigid element must form a nonredundant a nd sufficient set of freedoms to define rigid motions. *** USER FATAL MESSAGE 4284. (RBE3D) 4284.0 RIGID ELEMENT %1 HAS ILLEGAL UM SET SPECIFICATION User information: One or more unique dependent degrees of freedom must be selected for a rigid element. *** USER FATAL MESSAGE 4284. (RBE3D) 4284.1 GRID POINT %1 ON RBE3 ELEMENT %2 IS NOT CONNECTED TO ANOTHER ELEMENT User information: If a dependent grid on an RBE3 element is not connected to another c'd thus grounding the structure. element, it will be autosp *** USER FATAL MESSAGE 4284. (RBE3D) 4284.2 GRID POINT %1 ON RBE3 ELEMENT %2 IS NOT CONNECTED TO ANOTHER ELEMENT WITHIN THIS SUPERELEMENT DOMAIN. CONFIRM THAT THE GRID POINT IN QUESTION IS CONNECTED TO ELEMENTS I N ANOTHER SUPERELEMENT OR DOMAIN AND, IF SO, SET SYSTEM CELL 409 TO A 1 TO MAKE THE RBE3 CHECK ONLY A WARNING. User information: If a dependent grid on an RBE3 element is not connected to another element, it will be autospc'd thus grounding the structu re. *** USER FATAL MESSAGE 4286, 4286.0 RSPLINE %1 HAS MORE THAN 100 GRID POINTS

231 User information: The number of grid points for an RSPLINE is limited. *** USER FATAL MESSAGE 4287 , 4287.0 ILLEGAL THICKNESS FOR PLATE ELEMENT ID = %1 User information: The user can supply thickness either on the connection entry or the PSHELL property entry. No corner thickness may be negative and at least one corner thickness must be positive. *** USER FATAL MESSAGE 4287 , 4287.1 ILLEGAL THI CKNESS FOR CRAC2D ELEMENT ID = %1 *** USER FATAL MESSAGE 4288 (EPTTRD) 4288.0 ILLEGAL GEOMETRY FOR QUAD8 ELEMENT WITH ID =%1. CODE PATH = %2 User information: The code paths refer to the reason. Reasons 1 through 5 mean that the program was unable to find an element coordinate system. Reasons 6 through 12 imply the program cannot find a local coordinate system at a Gauss point. Reason 13 may be due to a negative 12I/T3 (PSHELL). Reason 14 is due to zero transverse she ar thickness (PSHELL). Reason 21 occurs if the isoparametric mapping is unreasonable, which can occur if the midside nodes are too close to the corners. *** USER FATAL MESSAGE 4288. (NTR6D) 4288.1 ILLEGAL GEOMETRY FOR TRIA6 ELEMENT WITH ID =%1. C ODE PATH =%2 *** USER FATAL MESSAGE 4288. (GPJAC) 4288.2 ILLEGAL GEOMETRY FOR %1 ELEMENT WITH ID =%2. CODE PATH =%3 *** SYSTEM FATAL MESSAGE 4289. 4289.0 CORE IS INSUFFICIENT BY A BASE10 AMOUNT =%1 WORDS TO PROCESS PENTA ELEMENT WITH ID =%2 *** SYSTEM FATAL MESSAGE 4289. 4289.1 CORE IS INSUFFICIENT BY A BASE10 AMOUNT =%1 WORDS TO PROCESS QUAD8 ELEMENT WITH ID =%2 *** SYSTEM FATAL MESSAGE 4289 (STR61D) 4289.2 CORE IS INSUFF ICIENT BY A BASE10 AMOUNT =%1 WORDS TO PROCESS TRIA6 ELEMENT WITH ID =%2 *** SYSTEM WARNING MESSAGE 4289 4289.3 THE OUT - OF - PLANE MATERIAL FAILURE CONSTANTS FOR %1 FAILURE THEORY ON MATERIAL ID =%2 ARE MISSING. ONLY THE IN - PLANE FAILURE INDICES/STRENGTH RATIOS WILL BE COMPUTED. *** SYSTEM WARNING MESSAGE 4289 4289.4

232 THE MATERIAL FAILURE CONSTANTS FOR %1 FAILURE THEORY ON MATERIAL ID =%2 ARE MISSING. THE FAILURE INDICES/STRENGTH RATIOS WILL NOT BE COMPUTE D FOR ALL PLIES ASSOCIATED WITH THIS MATERIAL. *** USER FATAL MESSAGE 4290. 4290.0 FOR QUAD ELEMENT WITH ID =%1 THE MATERIAL ROUTINE - RETURNS MAT - A 3X3 MATERIAL MATRIX WITH EITHER OR BOTH OF TERMS G11 EQUALS%2 ANDG22 EQUAL TO ZERO. MATERIAL ID CONCERNED *** USER FATAL MESSAGE 4290. 4290.1 FOR QUAD8 ELEMENT WITH ID =%1 THE MATERIAL ROUTINE - - RETURNS MAT A 3X3 MATERIAL MATRIX WITH EITHER OR BOTH OF TERMS G11 ANDG22 EQUAL TO ZERO. MATERIAL ID CONCERNED EQUALS%2 User information: Nonzero values of bending stiffness are required if MID2 data is supplied. *** USER FATAL MESSAGE 4291. 4291.0 FOR TRIA3 ELEMENT WITH ID =%1 - MAT THE MATERIAL ROUTINE RETURNS A 2X2 J - MATRIX FOR - MATERIAL ID =%2 WHICH IS SINGULAR. ** * USER FATAL MESSAGE 4291. (SQD41D ) 4291.2 FOR QUAD4 ELEMENT WITH ID =%1 THE MATERIAL ROUTINE - MAT - RETURNS A 2X2 J - MATRIX FOR MATERIAL ID =%2 WHICH IS SINGULAR. *** USER FATAL MESSAGE 4291. 4291.3 FOR QUAD8 ELEMENT WITH ID =%1 MAT - THE MATERIAL ROUTINE - MATRIX FOR - RETURNS A 2X2 J MATERIAL ID =%2 WHICH IS SINGULAR. *** USER FATAL MESSAGE 4291. 4291.5 FOR TRIA6 ELEMENT WITH ID =%1 - MAT - RETURNS A 2X2 J THE MATERIAL ROUTINE MATRIX FOR - MATERIAL ID =%2 WHICH IS SINGULAR. *** USER FATAL MESSAGE 4291 (EQDRD) 4291.6 FOR QUADR ELEMENT WITH ID =%1 THE MATERIAL ROUTINE - - RETURNS A 2X2 J - MATRIX FOR MATERIAL ID =%2 MAT WHICH IS SINGULAR. *** USER FATAL MESSAGE 4291. (EQD4D) 4291.7 FOR ELEMENT WITH ID =%1 MATRIX FOR THE MATERIAL ROUTINE MAT - RETURNS A 2X2 J - - MATERIAL ID =%2 WHICH IS SINGULAR. *** USER FATAL MESSAGE 4291. 4291.8

233 FOR TRIAR ELEMENT WITH ID =%1 - THE MATERIAL ROUTINE RETURNS A 2X2 J - MATRIX FOR MAT - MATERIAL ID =%2 WHICH IS SINGULAR. *** USER FATAL MESSAGE 4291 (STR61D) 4291.9 TRIA6 ELEMENT WITH ID =%1 MAT - RETURNS A 2X2 J THE MATERIAL ROUTINE MATRIX FOR - - MATERIAL ID =%2 WHICH IS SINGULAR. *** USER FATAL MESSAGE 4292 (EQD81D). 4292.0 FOR QUAD8 ELEMENT WITH ID =%1 THE FLEXIBILITY MATRIX Z(4X4) IS SINGULAR. *** USER INFORMATION MESSAGE 4293. 4293.0 - ID 1 NOT SPECIFIED FOR %1 ELEMENT WITH ID =%2 MATERIAL - *** USER FATAL MESSAGE 4294. 4294.0 QUAD8 ELEMENT%1 HAS ILLEGAL GEOMETRY DUE TO DEFORMATIONS. User information: For geometric nonlinear calculation, the deformations are so large that the geometry tests fail. *** USER FATAL MESSAGE 4294. 4294.1 DUE TO TRIA6 ELEMENT%1 HAS ILLEGAL GEOMETRY DEFORMATIONS. *** USER FATAL MESSAGE 4295. 4295.0 NON - LINEAR FOR ELEMENT WITH ID =%1 IS INVALID WITH MATID - - 2, MATID - 4, 1, MATID RESPECTIVELY =%2 NLFLAG NLTYPE =%3 User information: For a material nonlinear element an incorrect set of mat erial identifications were selected. Review material limitations for material nonlinear elements. *** USER FATAL MESSAGE (MTX244) 4295.1 ELEMENT WITH ID =%1 HAS INVALID MATERIAL ID =%2 *** USER FATAL MESSAGE 4295 (EQDRD) 4295.2 NON - LINEAR FOR ELEMENT WITH ID =%1IS INVALID WITH MATID - 1, MATID - 2, MATID - 4, RESPECTIVELY =%2 User information: For a material nonlinear element an incorrect set of material identifications were selected. Review material limitations ear elements. for material nonlin *** USER FATAL MESSAGE 4295. (EQD4D) 4295.3 NON - LINEAR FOR ELEMENT WITH ID =%1 4, RESPECTIVELY IS INVALID WITH MATID 1, MATID - 2, MATID - - =%2 *** USER FATAL MESSAGE 4295.4

234 NON LINEAR FOR ELEMENT WITH ID =%1 - 1, MATID - - 4 RESPECTIVELY =%2 IS INVALID WITH MATID - 2, MATID %3 %4 *** USER FATAL MESSAGE 4295. (EQD4D) 4295.5 QUAD4 ELEMENT WITH ID = %1 HAS A SINGULAR MEMBRANE MATERIAL MATRIX. IF MAT2 IS USED, BE SURE G33 IS POSITIVE OR G12 IS POSITIVE. IF MAT8 IS USED, BE SURE *** USER FATAL MESSAGE (MTX242) 4295.6 ELEMENT WITH ID =%1 HAS INVALID MATERIAL ID =%2 *** USER FATAL MESSAGE (MTX243) 4295.7 ELEMENT WITH ID =%1 HAS INVALID MATERIAL ID =%2 *** USER FATAL MESSAGE (MTX245) 4295.8 ELEMENT WITH ID =%1 HAS INVALID MATERIAL ID =%2 *** USER FATAL MESSAGE (MTX24*) 4295.9 - SYMMETRIC ELEMENT TYPES ARE NOT THE FOLLOWING AXIS SUPPORTED BY SOLUTION %1: CTRAX3, CQUADX4, CTRAX6, CQUADX8. *** USER FATAL MESSAGE (MTX255) 4295.10 ELEMENT WITH ID =%1 HAS INVALID MATERIAL ID =%2 \ ETRXED \ ETX6D) *** USER WARNING MESSAGE 4295. (EQUXED 4295.11 THE AXIS - SYMMETRIC ELEMENTS CTRIAX6/CQUADX/CTRIAX ARE NOT AFFECTED BY SYS440=0. *** USER FATAL MESSAGE (MTX26*) 4295.12 =%1 HAS NO COMPEST DATA BLOCK. ELEMENT ID *** USER FATAL MESSAGE 4295. 4295.13 ELEMENT WITH ID =%1 HAS INVALID MATERIAL ID =%2 *** USER FATAL MESSAGE 4295. 4295.14 THE FOLLOWING CHOCKING ELEMENT TYPES ARE NOT SUPPORTED BY SOLUTION %1: CCHOCK3, CCHOCK4, CCHOCK6, CCHOCK8. *** USER FATAL MESSAGE 4295. 4295.15 THE FOLLOWING PLANE STRESS ELEMENT TYPES IN FOURIER SOLUTION ARE NOT SUPPORTED BY SOLUTION %1: CPLSTS3, CPLSTS4, CPLSTS6, CPLSTS8. *** USER WARNING MESSAGE 4296. (SQD41D) 4296.0 ILLEGAL GEOMETRY FOR QUAD4 ELEMENT WITH ID =%1 User information: This may be caused by improper specification of geometry and/or connectivity. Make sure that the QUAD4 connectivity goes

235 completely around the element - clockwise. clockwise or counter *** USER FATAL MESSAGE 4296 (EQDRD) 4296.2 ILLEGAL GEOMETRY FOR QUADR ELEMENT WITH ID=%1 *** USER FATAL MESSAGE 4296. (EQD4D) 4296.3 ILLEGAL GEOMETRY FOR QUAD4/QUADR ELEMENT WITH ID = %1 User information: This may be caused by improper specification of geometry and/or connectivity. Make sure that the QUAD4/QUADR connectivity goes completely around the element clockwise or counter - clockwise. *** USER FATAL MESSAGE 4296 (EQDGED) 4296.4 ETRY FOR ELEMENT WITH ID = %1 IMPROPER GEOM *** USER FATAL MESSAGE 4296. (SECNSD) 4296.5 ILLEGAL GEOMETRY FOR %1 ELEMENT WITH ID = %2 *** USER FATAL MESSAGE 4296. (T3_HEAT) 4296.6 ILLEGAL GEOMETRY FOR TRIA3/TRIAR ELEMENT WITH ID = %1 User information: This may be caused by improper specification of geometry and/or connectivity. Make sure that the TRIA3/TRIAR connectivity goes completely around the element clockwise or counter - clockwise. *** USER WARNING MESSAGE 4297. 4297.0 ID =%1 QUAD4 ELEMENT WITH HAS AN INTERIOR ANGLE POSSIBLY GREATER THAN OR EQUAL 180 DEGREES. User information: This may be caused by improper specification of geometry and/or connectivity. Make sure that the CQUAD4 connectivity goes e or counter - completely around the element clockwis clockwise. *** USER FATAL MESSAGE 4297. 4297.1 QUAD4 ELEMENT WITH ID =%1 HAS AN INTERIOR ANGLE POSSIBLY GREATER THAN OR EQUAL 180 DEGREES. User information: This may be caused by improper specification of geometry and/or connectivity. Make sure that the CQUAD4 connectivity goes - clockwise. completely around the element clockwise or counter *** USER FATAL MESSAGE 4297 (EQDRD) 4297.2 QUADR ELEMENT WITH ID =%1 HAS AN INTERIOR ANGLE POSSIBLY GREATER THAN OR EQUAL 180 DEGREES. User information: This may be caused by improper specification of geometry and/or connectivity. Make sure that the CQUAD4 connectivity goes completely around the element clockwise or counter - clockwise. *** USER FATAL ME SSAGE 4297. 4297.3

236 TRIA3 ELEMENT WITH ID =%1 HAS AN INTERIOR ANGLE POSSIBLY GREATER THAN OR EQUAL 180 DEGREES. User information: This may be caused by improper specification of geometry and/or connectivity. Make sure that the CTRIA3 connectivity goes - clockwise. comple tely around the element clockwise or counter *** USER FATAL MESSAGE 4297 (EQDRD) 4297.4 TRIAR ELEMENT WITH ID =%1 HAS AN INTERIOR ANGLE POSSIBLY GREATER THAN OR EQUAL 180 DEGREES. User information: This may be caused by improper specif ication of geometry and/or connectivity. Make sure that the CTRIAR connectivity goes - completely around the element clockwise or counter clockwise. *** USER FATAL MESSAGE 4298. 4298.0 A CORNER POINT MEMBRANE THICKNESS HAS NOT BEEN SPECIFIED FOR ELEMENT WITH ID =%1 AND THERE IS NO DEFAULT VALUE ON THE ASSOCIATED PROPERTY CARD. *** USER FATAL MESSAGE 4298. 4298.1 A CORNER POINT GAP OPENING HAS NOT BEEN SPECIFIED FOR ELEMENT WITH ID =%1 AND THERE IS NO DEFAULT VALUE ON THE ASSOCIATED PROPERTY CARD. *** USER FATAL MESSAGE 4298. 4298.2 THE THICKNESS OF CHOCKING ELEMENT WITH ID = %1 IS LESS THEN ZERO. *** USER FATAL MESSAGE 4298. 4298.3 THE RADIAL DISPLACEMENT OF CHOCKING ELEMENT WITH ID = %1 IS TOO LARGE. *** USER FATAL MESSAGE 4298. 4298.4 THE GAP VALUE CHOCKING ELEMENT WITH ID = %1 IS UNREASONABLE. *** USER WARNING MESSAGE 4298 4298.5 COMPUTED GAP VALUE IS TOO LARGE FOR ELEMENT %1 User information: For chocking elements, the gap value is supposed to be much smaller than circumference. Please try to check the model, trigger more stiffness update, or reduce the time step. *** USER FATAL MESSAGE 4298. 4298.6 FAILURE TO QUERRY ELEMENT THICKNESS IN SUBROUTINE PLDE1T. *** USER FATAL MESSAGE 4298. 4298.7

237 ELEMENT %1, TYPE, %2 NOT FOUND IN OPEN CORE EST CACHE OF ELEMENTS SUPPORTING PLOADE1. *** USER FATAL MESSAGE 4298. 4298.8 INSUFFICIENT OPEN CORE M EMORY, ENCOUNTERED IN SUBROUTINE PLDE1T; TRY INCREASING AVAILABLE MEMORY (MEM SETTING). *** USER FATAL MESSAGE 4298. 4298.9 FAILURE TO QUERRY ELEMENT GAP IN SUBROUTINE PLDX1G. *** USER FATAL MESSAGE 4299. (SQD41D) 4299.0 FOR ELEMENT WITH ID =%1 THE JACOBIAN FOR INTEGRATION POINT NUMBER %2 IS ZERO. User information: This may be caused by improper specification of geometry and/or connectivity. As an example, connecting the CRACi in the wrong direction (counterclockwise) can cause this. *** USER FATAL MESSAGE 5479. 4299.1 FOR ELEMENT WITH ID =%1 *** THE INTERNAL STRAIN MODES ARE SINGULAR. *** USER FATAL MESSAGE 4299. 4299.2 FOR ELEMENT WITH ID =%1 *** THE JACOBIAN MATRIX IS SINGULAR. USER FATAL MESSAGE 4299 *** 4299.3 FOR ELEMENT WITH ID =%1 THE JACOBIAN FOR INTEGRATION POINT IS LESS OR EQUAL ZERO. User information: This may be caused by improper specification of geometry and/or connectivity. *** USER FATAL MESSAGE 4299 4299.4 FOR ELEMENT WITH ID =%1 THE JACOBIAN FOR INTEGRATION POINT IS LESS OR EQUAL ZERO. User information: This may be caused by improper specification of geometry and/or connectivity. *** USER FATAL MESSAGE 4299 4299.5 FOR ELEMENT WITH ID =%1 THE JA COBIAN FOR INTEGRATION POINT IS LESS OR EQUAL ZERO. User information: This may be caused by improper specification of geometry and/or connectivity. *** USER FATAL MESSAGE 4299 4299.6

238 FOR ELEMENT WITH ID =%1 LESS OR EQUAL THE JACOBIAN FOR INTEGRATION POINT IS ZERO. User information: This may be caused by improper specification of geometry and/or connectivity. *** USER FATAL MESSAGE 4299 4299.7 FOR ELEMENT WITH ID =%1 THE JACOBIAN FOR INTEGRATION POINT IS LESS OR EQUAL ZERO. User information: This may be caused by improper specification of geometry and/or connectivity. *** USER FATAL MESSAGE 4299 4299.8 FOR ELEMENT WITH ID =%1 THE JACOBIAN FOR INTEGRATION POINT IS LESS OR EQUAL ZERO. User information: caused by improper specification of geometry and/or This may be connectivity. *** USER FATAL MESSAGE 4300. (SQD41D) 4300.0 FOR ELEMENT WITH ID =%1 THE THICKNESS FOR INTEGRATION POINT NUMBER %2 IS ZERO. *** USER FATAL MESSAGE 4301. 4301.0 FOR ELEMENT WITH ID =%1 MAT - RETURNS A 3X3 G - MATRIX WITH THE MATERIAL ROUTINE - EITHER OR BOTH OF TERMS G11 AND G22 EQUAL ZERO. MATERIAL ID CONCERNED EQUALS %2 User information: The material data (Gxx and Gyy) is not supplied for the QUAD4 element. In material nonlinear analysis this message will be issued if PARAM,NLAYERS is greater than or equal to 12 and a stiffness update is performed during the nonlinear iterations. The avoidance is to set PARAM,NLAYERS less than 12. If the MID2 SHELL entry is greater than 0, PARAM,NLAYERS field on the P should be set to a value greater than 1 or bending stiffness will be ignored. *** USER FATAL MESSAGE 4302. (Q4_ST2D_CMPLX) 4302.0 FOR ELEMENT WITH ID =%1 GT MATRIX IS SINGULAR WHEN CONSIDERING THERMAL MEMBRANE - BENDING COUPLING. *** USER FATAL MESSAGE 4303. (SQD41D) 4303.0

239 FOR ELEMENT WITH ID =%1 THE FLEXIBILITY MATRIX Z(4X4) IS SINGULAR. User information: Logic error. To avoid problem, add transverse shear flexibility. SYSTEM FATAL MESSAGE 4304. *** 4304.0 LOGIC ERROR IN ROUTINE SQD41D FOR ELEMENT WITH ID =%1 LOC CODE =%2 *** SYSTEM FATAL MESSAGE 4304. 4304.1 LOGIC ERROR IN ROUTINE SQDR1D OR SQDR1S FOR ELEMENT WITH ID =%1 LOC CODE =%2 ESSAGE 4305. (SQD41D) *** USER INFORMATION M 4305.0 - ID NOT SPECIFIED FOR ELEMENT =%1 - MATERIAL *** USER FATAL MESSAGE 4306. 4306.0 DEGENERATE GEOMETRY OR INADEQUATE MATERIAL DATA SPECIFIED FOR TRIA6 ELEMENT WITH ID =%1 REASON NUMBER =%2 User information: See UFM 4288 for an explanation of reason numbers, except that Reason 28 corresponds to CODE 21. *** USER FATAL MESSAGE 4311 (XSEM) 4311.0 TIME EXPIRED PRIOR TO LINK %1, CALLING MODULE - %2 User information: ent in the Executive The time specified on the TIME statem Control Section has been exceeded. *** USER WARNING MESSAGE 4312. (MCONMD) 4312.0 CONM2 %1 HAS NON POSITIVE - DEFINITE INERTIA MATRIX. User information: Most dynamic analysis methods require positive definite mass - matrices. Inserting inertia data into the wrong fields can - positive definite systems, which are not physically result in non realistic for normal modeling practices. Reduce the size of the off - diagonal terms to provide a positive - definite determinant. *** USER WARNING MESSAGE 4312 (GPSP) 4312.9 SVD FAILED FOR GRID POINT %1, AUTOSPC IGNORED FOR THIS GRID. *** USER WARNING MESSAGE 4313 (GPSP) 4313.0 GRID POINT %1, REFERENCED BY CYAX, CYSUP, OR CYJOIN BULK DATA ENTRY DOES NOT EXIST. *** USER FATAL MESSAGE 4313. 4313.1 GRID POINT %1 REFERENCED BY CYSUP BULK DATA CARD IS UNDEFINED. *** USER FATAL MESSAGE 4313. 4313.2

240 GRID POINT %1 REFERENCED BY %2 BULK DATA CARD IS UNDEFINED. *** USER FATAL MESSAGE 4313. 4313.4 GRID POINT %1 REFERENCED BY A CYJOIN BULK DATA CARD IS UNDEFINED. *** USER FATAL MESSAGE 4314, 4314.0 HARMONICS CARD IS REQUIRED IN CASE CONTROL DECK FOR CYCLIC SYMMETRY ANALYSIS BUT IS NOT SUPPLIED BY USER. *** USER FATAL MESSAGE 4314, 4314.1 HARMONICS CARD IS REQUIRED IN CASE CONTROL FOR AXI - SYMMETRIC FOURIER ANALYSIS BUT IS NOT SUPPLIED BY USER. *** USER FATAL MESSAGE 4314, 4314.2 - HOUTPUT CARD IS REQUIRED IN CASE CONTROL FOR AXI SYMMETRIC FOURIER ANALYSIS BUT IS NOT SUPPLIED BY USER. *** USER FATAL MESSAGE 4314, 4314.3 - SYMMETRIC FOURIER ANALYSIS, HARMONICS CARD FOR AXI ALLOWS ONLY POSITIVE INTEGER. *** USER FATAL MESSAGE 4315, 4315.0 OVERALL SYMMETRY OPTION IS NOT ALLOWED UNDER ROTOR AXI CYCLIC SYMMETRY ANALYSIS. *** USER FATAL MESSAGE 4316. 4316.0 GRID POINT %1 REFERENCED BY A CYAX CARD WAS ALSO DEFINED AS A SIDE%2 POINT BY A CYJOIN CARD. USER FATAL MESSAGE 4317. *** 4317.0 GRID POINT%1, DOF =%2. AXIS POINTS MAY NOT BE CONSTRAINED BY MULTI POINT CONSTRAINTS. *** USER FATAL MESSAGE 4318. 4318.0 GRID POINT ID %1 WHICH LIES ON THE AXIS OF SYMMETRY HAS ILLEGALLY DEFINED SPC CONSTRAINTS. *** USER INFORMATION MESSAGE 4319. 4319 .0 SUPPORT POINT ID %1 HAD COMPONENT %2 DEFINED ON SPC, SPC1, OMIT, OMIT1,CARDS OR IN RIGID ELEMENTS OR MULTIPOINT CONSTRAINTS AS DEPENDENT COORDINATES. *** USER FATAL MESSAGE 4320. 4320.0 SUPPORT POINT %1 WAS LOCATED ON THE %2 NSEG = %3 *** USER WARNING MESSAGE 4321, 4321.0 SOME VALUES OF THE HARMONICS SPECIFIED FOR ANALYSIS IN THE HARMONICS CARD ARE GREATER THAN THE MAXIMUM VALUE PERMISSIBLE. VALUES OF HARMONICS GREATER THAN NSEG/ 2 WILL NOT BE USED IN THE ANALYSIS. *** USER WARNING MESSAGE 4312. (MCONMD) 4321.1

241 CONM2 %1 HAS NON POSITIVE - DEFINITE INERTIA MATRIX. *** USER INFORMATION MESSAGE 4326, 4326.0 USER SUPPLIED LOADCYH AND GRAV CARDS ARE REPLACED AS FOLLOWS - *** USER INFORMATION MESSAGE 4327, 4327.0 USER SUPPLIED LOADCYH AND RFORCE CARDS ARE REPLACED AS FOLLOWS - *** USER WARNING MESSAGE 4328, (ECONED) 4328.0 THE ANISOTROPIC MATERIAL PROPERTY FOR MEMBRANE ACTION DEFINED BY MAT2 ID %1 ENT WITH CONICAL SHELL THEORY. G13 AND G23 IS INCONSIST WILL BE SET TO ZERO *** USER WARNING MESSAGE 4329, (ECONED) 4329.0 THE ANISOTROPIC MATERIAL PROPERTY FOR BENDING ACTION DEFINED BY MAT2 ID %1 IS INCONSISTENT WITH CONICAL SHELL THEORY. G13 AND G23 WILL BE SET TO ZERO *** USER WARNING MESSAGE 4330, 4330.0 THE ANISOTROPIC MATERIAL PROPERTY FOR TRANSVERSE SHEAR ACTION DEFINED BY MAT2 ID %1 G23 IS INCONSISTENT WITH CONICAL SHELL THEORY. G13 AND WILL BE SET TO ZERO *** USER WARNING MESSAGE 4330, 4330.2 THE ANISOTROPIC MATERIAL PROPERTY FOR TRANSVERSE SHEAR ACTION DEFINED BY MAT2 ID %1 IS INCONSISTENT WITH CONICAL SHELL THEORY. G12 WILL BE SET TO ZERO *** USER FATAL MESSAGE 4334 ***, 4334.0 - POSITIVE DEFINITE MASS MATRIX FOUND IN DYNAMIC NON REDUCTION. User information: Generalized dynamic reduction assumes a non - negative definite mass matrix. This prevents computation of modes with negative generalized mass . User input of negative mass, large off - diagonal mass terms, or requesting more modes than there are independent degrees of freedom with mass can lead to this condition. Inspect the input mass data X if the number data for the conditions described above, or reduce FMA of degrees of freedom with mass is not adequate. *** USER FATAL MESSAGE 4335. 4335.0 THERE MAY ONLY BE ONE SUPPORT POINT. ALL OF THE FOLLOWING WERE ENCOUNTERED ON CYSUP BULK DATA CARDS. *** USER FATAL MESSAGE 4336, 4336.0

242 C YSYM BULK DATA CARD MUST BE PRESENT IN CYCLIC SYMMETRY ANALYSIS, BUT IS NOT SPECIFIED IN THE DECK. *** USER FATAL MESSAGE 4337, 4337.0 HARMONICS SET SPECIFIED ON HOUTPUT CASE CONTROL CARD IS UNDEFINED. User information: The HOUTPUT Case Control command defines the values of harmonics for which output will be produced. The set ID specified by this command is not defined in Case Control. *** USER FATAL MESSAGE 4338, 4338.0 SEGMENTS SET SPECIFIED ON NOUTPUT CASE CO NTROL CARD IS UNDEFINED. User information: The NOUTPUT Case Control command defines the values of segments for which output will be produced. The set ID specified by this command is not defined in Case Control Section. *** USER FATAL MESSAGE 4339, 4339.0 HARMONICS SET SPECIFIED ON NOUTPUT CASE CONTROL CARD IS UNDEFINED. User information: In the solution of vibration problems, the segment output can be selected for a specified set of harmonics. The set of harmonics specified in the NOUTPUT Case Control command is not defined in the Case Control. *** USER FATAL MESSAGE 4340, 4340.0 LINEAR COMBINATION OF SUBCASES NOT ALLOWED IN CYCLIC SYMMETRY ANALYSIS. User information: symmetry analysis. SUBCOMS and/or SYMCOMS are not allowed in cyclic Delete requests of SUBCOMS and/or SYMCOMS. *** USER FATAL MESSAGE 4341, 4341.0 HARMONICS SET SPECIFIED FOR ANALYSIS IS UNDEFINED. User information: The values of harmonics for which analysis will be performed is given by the set specified in the HARMONICS Case Control Section. This set is not defined. Define the set of integer values of harmonics for analysis. *** USER FATAL MESSAGE 4342, 4342.0 THE LOAD BULK DATA CARD GIVEN BELOW IS INCONSISTENT WITH SPECIFIED ANALYSIS HARMONICS OR SEGMENTS OR SYMMETRY TYPE. User information: The load specified by LOADCYH Bulk Data entry should specify loading for harmonics that are valid for the problem. For example, the integer

243 value of the harmonics that are loaded should be contained in the analysis harmonics set and furthermore the harmonic type should also be contained in analysis harmonics type. If not, this fatal message load specified by LOADCYN Bulk Data entry will result. Similarly, the should specify loading for segments that are in the model. In addition, if symmetry option is used in DIHEDRAL type problems, the load should be plane (or quadrant) of the m odel. applied in segments in the first half - Specify valid harmonic loading or segment loading. In buckling problems, the static preload must be the same for all segments, which is ensured by providing a zero (cosine) harmonic loading. e loading is For such problems, this fatal message will result if th specified any other way than via LOADCYH entry. See also Error Report 3502 in Chapter 17. *** USER FATAL MESSAGE 4342, 4342.1 THE LOAD BULK DATA CARD GIVEN BELOW IS INCONSISTENT WITH SPECIFIED ANALYSIS HARMONICS OR SEGMENTS OR RY TYPE. SYMMET LOADCYN %1 %2%3 %4 *** USER FATAL MESSAGE 4342, 4342.2 THE LOAD BULK DATA CARD GIVEN BELOW IS INCONSISTENT WITH SPECIFIED ANALYSIS HARMONICS OR SEGMENTS OR SYMMETRY TYPE. LOADCYH %1 %2%3 %4 *** USER FATAL MESSAGE 4343, 4343.0 LOAD ID = %1 WAS ILLEGALLY REFERENCED BY BOTH LOADCYH AND LOADCYN CARDS. User information: The same load set ID has been referenced by both LOADCYH and LOADCYN Bulk Data entries. This is illegal. Define separate load IDs for loads referenced by LOADCYH and LOADCYN entries. *** USER FATAL MESSAGE 4344, 4344.0 SELECTED LOAD SET, ID =%1 WAS NOT DEFINED ONA LOADCYH, LOADCYN OR LOADCYT CARD. User information: The load set ID selected in case control is not defined by a LOADCYH, CYT Bulk Data entry. Define the load set ID LOADCYN and/or LOAD selected in case control by means of LOADCYH, LOADCYN, and/or LOADCYT Bulk Data entry. *** USER FATAL MESSAGE 4345, 4345.0 USER SPECIFIED CASE CONTROL LOAD ID =%1 WHICH SPECIFIES A %2 LOAD ID =%3 WHICH WAS USED ELSEWHERE.

244 *** USER FATAL MESSAGE 4346, 4346.0 FREQUENCY RESPONSE SET, ID = %1 IS UNDEFINED. User information: Define the set of frequencies to be used for analysis. *** USER FATAL MESSAGE 4347, 4347.0 RFORCE OPTION SPECIFIED ON LOADCYH CARD, BUT NO RFORCE CARD FOUND. User information: Define RFORCE Bulk Data entry selected by LOADCYH Bulk Data entry. *** USER FATAL MESSAGE 4348, 4348.0 GRAV OPTION SPECIFIED ON LOADCYH CARD, BUT NO GRAV UND. CARD FO User information: Define GRAV loading via GRAV Bulk Data entry. *** USER FATAL MESSAGE 4350, 4350.0 LOADCYT CARD WITH SID= %1, SPECIFIES NON - EXISTENT TABLE ID=%2 *** USER WARNING MESSAGE 4351, 4351.0 TEMPERATURE/DEFORMATION SET ID = %1 SPECIFIES INPUT IN HARMONIC VARIABLES. PHYSICAL ELEMENT STRESS OUTPUT WILL BE IN ERROR, USE ONLY STRESS OUTPUT IN HARMONIC VARIABLES. *** USER WARNING MESSAGE 4352, 4352.0 CIFIES INPUT IN TEMPERATURE/DEFORMATION SET ID = %1 SPE PHYSICAL VARIABLES. HARMONIC ELEMENT STRESS OUTPUT WILL BE IN ERROR, USE ONLY STRESS OUTPUT IN PHYSICAL VARIABLES. *** USER FATAL MESSAGE 4353 4353.0 DMIG MATRICES SELECTED BY A2GG, K2GG, M2GG, B2GG OR FORM. K42GG DO NOT HAVE CORRECT User information: For DMIG matrices K2GG, M2GG, B2GG and K42GG added before constraints are applied, their form must be symmetric. The form is specified in the IFO field (Field 4) of the DMIG entry. Set IFO to 6. For DMIG matrix A2GG added befor e constraints are applied, its form must be either square or symmetric. The form is specified in the IFO field (Field 4) of the DMIG entry. Set IFO to either 1 (square) or 6 (symmetric) as appropriate. *** USER WARNING MESSAGE 4356, 4356.0 MATMOD MODULE OPTION 16 WILL NOT PROCESS MATRIX %1 BECAUSE IT IS NOT OF FORM 1, 2, 6, OR 9. User information:

245 This option converts NX NASTRAN matrices to DMIG entry formats. The other forms of matrices are not suitable for DMIG formats. Convert the matrix t o the proper form using the MODTRL and ADD modules. *** USER WARNING MESSAGE 4357, 4357.0 MATRIX %1 INPUT TO MATMOD OPTION 16 HAS %2 ROWS AND %3 COLUMNS. SIZE IS %4. NO OUTPUT PRODUCED. G - User information: All matrices input for Option 16 with third parameter = 0 must have g - size rows. If they are Form 1 or 6 they must also have g size columns. Merge the - matrices to g size. - *** USER FATAL MESSAGE 4358. 4358.0 SUPPORT POINT IS ILLEGALLY SPECIFIED AS A SCALAR POINT. User information: The support point should be a grid point in cyclic symmetry analysis. Redefine the support point such that it is a grid point and not a scalar point. *** USER WARNING MESSAGE 4359. 4359.0 COMPONENT%1 REFERENCED ON CYSUP BULK DATA CARD FORCES COMP ONENT%2 TO ALSO BE SUPPORTED. User information: See CYSUP Bulk Data entry for explanatory remarks. *** USER WARNING MESSAGE 4360. 4360.0 COMPONENT 2 WILL BE SUPPORTED INSTEAD OF COMPONENT 6, AS REFERENCED ON THE CYSUP BULK DATA CARD. User inform ation: See CYSUP Bulk Data entry for explanatory remarks. *** USER INFORMATION MESSAGE 4361 (SEQRS). 4361.0 SINCE THE ORIGINAL PERFORMANCE IS BETTER THAN THE RESEQUENCED PERFORMANCE DATA, THE NEW SEQGP ENTRIES WILL NOT BE GENERATED. *** USER FATAL MESSAGE 4362. 4362.0 INTERIOR POINTS ILLEGALLY DEFINED IN THE AXI OPTION OF THE CYCLIC SYMMETRY PROBLEM. User information: In the AXI option of cyclic symmetry, all degrees of freedom must be on Side 1, Side 2, or on the axis. Define all grid points to be on Side 1, Side 2, or on the axis. *** USER FATAL MESSAGE 4363, 4363.0 SYMMETRY ON TWO PLANES OF THE MODEL ILLEGALLY SPECIFIED WITH ODD NUMBER OF SEGMENTS. User information:

246 Symmetry on the planes of the model is allowed only when the total number of segments is even. Use only symmetry with respect to Side 1 of Segment 1 of the model. *** USER FATAL MESSAGE 4364. 4364.0 COMPONENT %1 OF GRID POINTS %2,%3 CANNOT BE CON NECTED. (GRID POINT %4 IS AT FAULT) User information: In the AXI option of CYCLIC symmetry, all degrees of freedom in the analysis set must be on SIDE 1, SIDE 2, or on the AXIS. If a SIDE 2, or on the AXIS. If a degree of freedom is on either SIDE 1 or SIDE 2, then its connected d.o.f. must not be constrained out in any way. (This same condition is only a warning error for the ROT option.) Make all SIDE 1 and SIDE 2 points meet the above stated restrictions. *** USER INFORMATION MESSAGE 4365 4365.0 USER SUPPLIED LOADCYT BULK DATA CARD (SID = %1) IS USED AS EQUIVALENT TO THE FOLLOWING LOADCYH CARD(S). User information: When Method = 0 (or blank) option is used with the LOADCYT Bulk dset ID) Data entry, the magnitude of the load (specified by the loa will be multiplied by the following harmonic coefficients. *** USER INFORMATION MESSAGE 4366 4366.0 USER SUPPLIED LOADCYT BULK DATA CARD (SID = %1) IS USED AS EQUIVALENT TO THE FOLLOWING LOADCYN CARD(S). User information: When Method = 1 option is used with the LOADCYT Bulk Data entry, the magnitude of the load (specified by the LOADSET ID) at corresponding points in the various segments of the model will be multiplied by the following scale factors. *** US ER INFORMATION MESSAGE 4367. 4367.0 STATISTICS FOR UNSYMMETRIC DECOMPOSITION OF DATA BLOCK %1 FOLLOW NUMBER OF PIVOT OPERATIONS = %2 User information: Pivot operations only occur when the ratio of the diagonal term of the pivot row to the largest term in the pivot column is less than the threshold. (Default = 1.E - 6) See the NX NASTRAN Numerical Methods User's Guide. , *** USER WARNING MESSAGE 4368 --- 4368.0 THERE MAY BE INSUFFICIENT TIME TO COMPLETE GENERALIZED DYNAMIC REDUCTION. TIME REQUIRED IS%1 SECONDS. USER INFORMATION: THE RUN WILL BE ALLOWED TO PROCEED BECAUSE CPU TIME ESTIMATES, IN SOME CASE, ARE POOR.

247 User information: An interval time estimate made using parameters reflecting the consume users model, indicates that DYNAMIC reduction module will more than the user allowed for when the time estimate was set for the entire job. *** USER FATAL MESSAGE 4368 --- , 4368.1 INSUFFICIENT TIME TO COMPLETE GENERALIZED DYNAMIC REDUCTION. TIME REQUIRED IS%1 SECONDS. User information: An interval time estimate made using parameters reflecting the users model, indicates that DYNAMIC reduction module will consume more than the user allowed for when the time estimate was set for the entire job. *** USER FATAL MESSAGE 4369. 4369.0 FOR THE DIH OR AXI OPTION OF CYCLIC SYMMETRY (EXCEPT FOR HEAT TRANSFER) THE DEGREE OF FREEDOM - FIELD 3 CYJOIN BULK DATA NORMAL TO SIDE 1 (AND/OR SIDE 2) - CARD MUST BE DEFINED. User information: Field 3 of the CYJOIN entry for Side 1 must be filled in for non - heat transfer problems. Supply degree of freedom perpendicular to Side 1 (and/or Side 2) in Field 3 of CYJOIN Bulk Data entry. *** SYSTEM FATAL MESSAGE 4370. 4370.0 DECOMPOSITION REQUIRES THAT PRECISION OF DATA BLOCK %1 ISION. EQUAL SYSTEM PREC System information: The symmetric and unsymmetric decomposition routines require that the input matrix be single precision for CDC and CRAY machines, and double precision for all other machines. *** USER WARNING MESSAGE 4372 (NLTINT) 4372.0 *** NO NONLINEAR ELEMENTS HAVE BEEN FOUND FOR NONLINEAR ANALYSIS SOLUTION. USE ADAPT METHOD FOR LINEAR PROBLEMS. User information: Material nonlinear analysis solution sequences must have at least t. one nonlinear elemen *** USER FATAL MESSAGE 4375, 4375.0 SUBCASE LISTS ARE ILLEGAL FOR AUTO OR PSDF REQUESTS *** USER FATAL MESSAGE 4376. 4376.0 ILLEGAL NUMBER OF SUPPORT POINTS ARE GIVEN FOR AUTOMATIC RIGID BODY MATRIX CALCULATION. SIX ARE REQUIRED. User information: Module VECPLOT provides an option to compute a rigid - body

248 transformation matrix based on grid point coordinates. To use this option, there must set degrees of freedom specified on SUPORT be six, and only six, r - commonly used in component modal synthesis entries. This option is of - freedom using external superelements. The user must provide six degrees - - on SUPORT entries or input the rigid body transformation on DMIG entries. *** USER FATAL MESSAGE 4377 (IFS3P) 4377.0 PCOMP ID. %1 HAS NO PLY DATA. USER ACTION: VERIFY EXISTENCE AND/OR UNIQUENESS OF CONTINUATION FIELD(S) User information: User supplied no ply information for the specified PCOMP bulk data entry. Supply some ply data. *** USER FATAL MESSAG E 4377 4377.1 PCOMP ID.%1 HAS NO PLY DATA User information: User supplied no ply information for the specified PCOMP bulk data entry. Supply some ply data. *** USER FATAL MESSAGE 4377 (IFS3P) 4377.2 PCOMP ID. %1 HAS NO PLY DATA. USER ACTION: VERIFY E XISTENCE AND/OR UNIQUENESS OF CONTINUATION FIELD(S) *** USER FATAL MESSAGE 4377 4377.3 PCOMP ID.%1 HAS NO PLY DATA *** USER FATAL MESSAGE 4377 (IFS3P) 4377.4 PCOMPG ID. %1 HAS NO PLY DATA. USER ACTION: VERIFY EXISTENCE AND/OR UNIQUENESS OF CONTINUATION FIELD(S) User information: User supplied no ply information for the specified PCOMPG bulk data entry. Supply some ply data. *** USER FATAL MESSAGE 4377 (IFS3P) 4377.5 HAS NO PLY DATA. PCOMPS ID. %1 USER ACTION: VERIFY EXISTENCE AND/OR UNIQUENESS OF CONTINUATION FIELD(S) *** USER FATAL MESSAGE 4377 (IFS3P) 4377.6 Material ID %1 referenced by PCOMP or PCOMPG exceeds 99,999,999. User information: MID referenced by PCOMP or PCOMPG can not exceed 99,999,999. *** USER FATAL MESSAGE 4378 (IFS3P) 4378.0 PCOMP ID. %1 HAS AN INVALID LAM OPTION. USER ACTION: CHECK THE LAM FIELD ON THE PCOMP DATA ENTRY.

249 S3P) *** USER FATAL MESSAGE 4378 (IF 4378.1 PCOMPG ID. %1 HAS AN INVALID LAM OPTION. USER ACTION: CHECK THE LAM FIELD ON THE PCOMPG DATA ENTRY. *** USER FATAL MESSAGE 4378 (IFS3P) 4378.2 PCOMPG ID. %1 HAS AN INVALID LAM OPTION. THE SYM OPTION IS NOT SUPPORTED BY PCOMPG. USER ACTION: CHECK THE LAM FIELD ON THE PCOMPG DATA ENTRY. *** USER FATAL MESSAGE 4378 (IFS3P) 4378.3 PCOMPG ID. %1 HAS DUPLICATED GLOBAL PLY ID NUMBERS. GLOBAL PLY ID NUMBER %2 APPEARS %3 TIMES ON THIS PCOMPG ENTRY. USER ACTION: MAKE SURE GLOBAL PLY ID NUMBERS ARE UNIQUE WITHIN ONE PCOMPG ENTRY. *** USER FATAL MESSAGE 4378 (IFS3P) 4378.4 PCOMPS ID %1 HAS DUPLICATE GLOBAL PLY ID VALUES. GLOBAL PLY ID NUMBER %2 APPEARS %3 TIMES ON THIS PCOMPS ENTRY. USER ACTION: MAKE SURE GLOBAL PLY ID NUMBERS ARE UNIQUE WITHIN ONE PCOMPS ENTRY. *** USER FATAL MESSAGE 4378 (IFS3P) 4378.5 MATFT ID. %1 HAS A DUPLICATE %2 FAILURE THEORY SPECIFIED. EACH FAILURE THEORY CAN ONLY BE SPECIFIED ONCE. *** USER INFORMATION MESSAGE 4379, 4379.0 THE USER SUPPLIED PCOMP BULK DATA CARDS ARE REPLACED BY THE FOLLOWING PSHELL AND MAT2 CARDS. WARNING, MAT2 RECORDS WITH MID GREATER THAN 400000000 USE A SPECIAL FORMAT FOR PCOMPS. N IN THE NX REFER TO REMARK 13 OF THE MAT2 DESCRIPTIO NASTRAN QUICK REFERENCE GUIDE. User information: Output is only produced when PCOMP Bulk Data entries are present and sorted ECHO output is requested. *** USER INFORMATION MESSAGE 4379 (IFP9A) 4379.1 THE USER SUPPLIED %1 BULK DATA ENTRIES ARE REPLACED BY THE FOLLOWING %2 ENTRIES. *** SYSTEM FATAL MESSAGE 4380 4380.0 RECORD ID =%1 IS OUT OF SYNC ON DATA BLOCK NUMBER %2 AN %3 SYSTEM ERROR. System information: IFP output files of either EPT or MPT were not properly formed. *** SYSTEM FATAL MESSAGE 4381 (IFP6) 4381.0 ABNORMAL END OF PCOMP RECORD ENCOUNTED ON DATA

250 BLOCK%1 System information: An unexpected end of record mark was encountered while processing the PCOMP record as output by IFP. Check PCOMP Bulk Data entries for proper format. *** USER FATAL MESSAGE 4382 (IFP9) 4382.0 PBEAML AND PBEAM IDENTIFICATION %1 WAS DUPLICATED *** USER FATAL MESSAGE 4382 (IFP9) 4382.1 PBARL AND PBAR IDENTIFICATION %1 WAS DUPLICATED PCOMP AND PSHELL IDENTIFICATION%1 WAS DUPLICATED 4382.2 User information: While merging the new PSHELL bulk data entries generated from the presence of the PCOMP bulk data entries a duplicate identification number (PID) was encountered within the u ser supplied PSHELL data. The user record is temporarily copied to the EPT data block to continue preface processing. Remove duplicate identification. PCOMP AND PCOMPG HAVE THE SAME ID%1. PCOMP AND 4382.3 PCOMPG IDs MUST BE UNIQUE. USER ACTION: CHANGE THE ID ON EITHER THE PCOMP OR PCOMPG. *** USER FATAL MESSAGE 4383 4383.0 TRANSVERSE SHEAR MATERIAL MATRIX IS SINGULAR FOR PCOMP %1 User information: Review properties given for MAT2 and MAT8 bulk data entries for specified PC OMP record causing error. *** USER FATAL MESSAGE 4384 4384.0 THERMAL MATRIX INVERSION FAILURE FOR PCOMP %1 MID %2 User information: Review properties given for MAT2 and MAT8 bulk data entries for specified PCOMP record causing error. *** USER WARNING MESSAGE 4385, 4385.0 STRESS PROCESSING FOR %1 ELEMENTS IN SUBCASE %2 NOT COMPLETE BECAUSE OF INSUFFICIENT DATA IN DATA BLOCK %3 User information: The composite stress was not calculated for the noted element type in a particular subcase b ecause the data needed could not be found. If the data block is the force data block, then perhaps forces were not requested in this subcase. If the data block is any other, the problem is a programming bug. *** USER WARNING MESSAGE 4386, 4386.0 COMPOSITE STRESSES FOR ELEMENT %1 NOT CALCULATED. FORCE RECORD WAS NOT FOUND

251 User information: For composite stress calculations there must be a force element record for each requested stress. Match up the stress and force requests or make the stress request a subset of the force request. *** USER INFORMATION MESSAGE 4387. 4387.0 THE FOLLOWING TABLE SUMMARIZES THE SIZE IN BLOCKS OF INTERNAL PERMANENT UNITS NAME SIZE *** USER FATAL MESSAGE 4388. 4388.0 AXIS POINT %1 DEFINED BY THE CYAX BULK DATA CARD HAS - COMPONENTS OF MOTION IN THE O SET. User information: If there are ASET, ASET1 and/or OMIT, OMIT1 bulk data entries present the components of axis points must be in the analysis set. Include - set. f freedom of axis points in the a degrees o *** USER FATAL MESSAGE 4390, 4390.0 LSEQ ENTRY %1 REQUESTED VIA LOADSET FOR SUPERELEMENT %2 DOES NOT EXIST IN THE BULK DATA User information: h A LOADSET entry has selected a set of LSEQ bulk data entries whic do not exist in the static load table. Check bulk data LSEQ entries for proper set ID. *** USER FATAL MESSAGE 4390, 4390.1 LSEQ ENTRY %1 REQUESTED VIA LOADSET DOES NOT EXIST IN THE BULK DATA User information: t of LSEQ bulk data entries which A LOADSET entry has selected a se do not exist in the static load table. Check bulk data LSEQ entries for proper set ID. *** USER FATAL MESSAGE 4391, 4391.0 - UNIQUE DAREA SET%1 HAS BEEN SPECIFIED FOR LSEQ NON DEFINED VECTOR%2. User information: Each vector number defined on an LSEQ Bulk Data entry must have a unique DAREA set specification, i.e., the combination of vector number and DAREA set number must be maintained throughout all LSEQ sets. fies the same DAREA Make sure that each vector number "X" always speci "Y", regardless of which LSEQ set the vector is in. *** USER FATAL MESSAGE 4393. 4393.0 ILLEGAL DELETE CARD. User information: A delete card contains a / in Field 1, a positive integer in Field 2 and a positive integer or blank in Field 3. If Field 3 is non - blank, its contents must be greater than or equal to Field 2. Failing to

252 meet any of these conditions results in the error message. - field format (i.e., /,a,b). It may be best to use free *** USER WARNING MESSAGE 4394 (MODB) 4394.0 SOLUTION SIZE REDUCTION PARAMETER %1 IS NOT APPROPRIATE FOR THIS PROBLEM. User information: The MODB module has been asked to retain more vectors than exist. The module will retain all that have been found . *** USER WARNING MESSAGE 4395 (MODB) 4395.0 PROBLEM SIZE (VECTORS RETAINED) HAS BEEN REDUCED TO %1 VECTORS. User information: The number of vectors retained has been reduced by user request. USER INFORMATION MESSAGE 4396 (MODB) *** 4396.0 MASS CONVERGENCE OF %1 ACHIEVED AFTER %2 CYCLES. User information: The generalized masses have all passed the test - N(old)) / M(new) < = MVAR (M(new) *** USER INFORMATION MESSAGE 4397 (MODB) 4397.0 FREQUENCY CONVERGENCE OF %1 ACHIEVED AFTER %2 CYCLES. User information: The frequencies (f) have all (not including f < .01) passed the test. *** USER WARNING MESSAGE 4398 (GPSP) 4398.0 GRID POINT %1 FOR %2DEGREES OF FREEDOM DOES NOT PASS SYMMETR Y CHECK. NO SINGULARITY TESTS MADE ON THESE TERMS. %3 %4 %5 User information: The stiffness matrix is inspected for singularities before any user supplied unsymmetric terms are allowed. The solution technique - will result if unsymmetric makes it unlikely that correct answers - by - three stiffness terms exist. When these tests are made, the three matrix terms printed are the terms about the diagonal of the listed grid point, normalized to the largest term in the three - - three by s are unsymmetric terms from user submatrix. Likely cause supplied - matrices, downstream superelements whose upstream members have mechanisms suppressed due to use of PARAM,MAXRATIO or PARAM,BAILOUT, or errors in NX NASTRAN code. If the stiffness terms were generated from NX N ASTRAN elements rather than matrices from outside NX NASTRAN, and no large factor - to - diagonal messages are present, please send runs to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT.

253 *** USER FATAL MESSAGE 4401 (PRTPRN) 4401.0 - SET EXISTS, BUT AN O SE T DOES NOT EXIST. A Q - User information: This error is detected by the GPSP module and issued by the PRTPARM DMAP statement. The q - set is used for Generalized Dynamic Reduction set. and Component Mode Synthesis. It requires the presence of an o - - set is formed only if ASETi or OMITi entries are present. Put An o degrees of freedom listed on QSETi entries on ASETi entries. *** USER FATAL MESSAGE 4402 (PRTPRN) 4402.0 - SET REMAINS AFTER CONSTRAINTS AND O - NO L SET REMOVED. User information: - No degrees of freedom remain in the L set after multipoint and single point constraints and omitted coordinates are removed. Although this may be a well - defined engineering problem, all solution sequences - set degree of freedom. Ei ther remove some require at least one L constraints or omitted coordinates or add unconstrained degrees of freedom. *** USER FATAL MESSAGE 4403 (PRTPRN) 4403.0 STIFFNESS MATRIX FOR Q SET NOT NULL. - User information: The q - set is reserved for generalized coordinates. I n superelement analysis, each superelement must have a unique set of variables - specified for its q set set. Remove any elements connected to q - points and provide a unique set of degrees of freedom for each superelement that has generalized coordinates. *** USER FATAL MESSAGE 4404 (PRTPRN) 4404.0 - MASS MATRIX FOR Q SET NOT NULL. User information: The q set is reserved for generalized coordinates. In superelement - analysis, each superelement must have a unique set of variables specified for its q - set. Remove any elements connected to q - set points and provide a unique set of degrees of freedom for each superelement that has generalized coordinates. *** USER FATAL MESSAGE 4405 (PRTPRN) 4405.0 NO EIGENVECTORS COMPUTED FOR COMPONENT MODE SYNTHESIS OR SYSTEM SOLUTION. User information: The eigenvectors computed in component mode synthesis (CMS) are used to approximate the motion of the component. Some vectors must be present to perform this re duction. For the system solution, an exit is taken if eigenvalues are requested but not eigenvectors. Reset the "range of frequency" and/or the "number desired" on the EIGR EIGR or EIGRL entry. If the superelement does not have any eigenvalues in the r ange of interest, remove the CMS request for that particular superelement.

254 This message is also issued when the eigenvectors calculated with a transformation method such as GIV do not pass internal orthogonality error. checks. This is indicative of a modeling This message can also be issued if insufficient memory is available for the Lanczos method with sparse decomposition. This could occur with UFM 5401 and be related to UWM 5411. *** USER FATAL MESSAGE 4406 (PRTPRN) 4406.0 THE SEMG OPERATI ON HAS NOT BEEN COMPLETED FOR THIS SUPERELEMENT. User information: The SEMG operation must be completed before the SEKR, SEMR, SELR, and SELG operation is requested. If these other operations are prior requested and the SEMG operation was not completed on a run, certain data blocks such as the SIL will not be in the Database. Request the SEMG operation for the superelement that fails. *** USER FATAL MESSAGE 4407 (PRTPRN) 4407.0 MR MATRIX HAS NULL DIAGONAL TERM. User information: x contains the rigid - The MR matri body mass matrix of the structure as measured at the degrees of freedom listed on the SUPORT entry. If any of these degrees of freedom have null mass, they result in invalid eigenvectors. Put in enough masses to define all rigid - bod y modes. *** USER FATAL MESSAGE 4408 (PRTPRN) 4408.0 - Q SET NOT IMPLEMENTED FOR SOL 62. User information: The q - set is used for generalized coordinates and has no function in this solution sequence. Load reduction errors will occur if it is present. Remove QSETi entries. *** USER WARNING MESSAGE 4409 (PRTPRN) 4409.0 PARAM, FIXEDB USED IN SOLUTION SEQUENCE WHERE NOT SUPPORTED. User information: This capability is intended for the data recovery in the statics and normal modes solu tion sequences only. If requested in other solution sequences it will cause an exit from the data recovery loop for the present superelement and continuation to the next superelement. *** USER WARNING MESSAGE 4410 (PRTPRN) 4410.0 DATA RECOVERY REQUESTED WHEN USET TABLE NOT PRESENT. User information: This is caused by improper restarts or improper use of the multiple file database concept. The program will terminate processing the superelement listed at the top of the page, and attempt data recovery on the next superelement. Attach the database that has the superelement data on it or rerun the superelement and all downstream superelements

255 through the SEALL process. *** USER FATAL MESSAGE 4411 (PRTPRN) 4411.0 GEOMETRIC NONLINEAR MODEL WITH NO STRUCTURAL ELEMENTS AND/OR GENELS. User information: Solution 64 requires "simple" (conventional) elements and does not process GENEL entries. *** USER FATAL MESSAGE 4412 (PRTPRN) 4412.0 - SET OR R - OES NOT SUPPORT O GEOMETRIC NONLINEARITY D SETS. User information: - set. SOL 64 does not process any sets that are subsets of the f Remove OMITi, SUPORT, ASETi, BSETi, CSETi entries from the Bulk Data Section. *** USER FATAL MESSAGE 4413 (PRTPRN) 4413.0 NEGATIV E TERMS IN FACTOR. STATICALLY UNSTABLE SYSTEM. User information: Negative terms on the diagonal terms of the factor of the decomposed stiffness matrix indicates that portions of the structure are in a - buckled state. If allowed to iterate, the solu tion may not post converge. PARAM, TESTNEG may be used to force iteration to continue. *** USER FATAL MESSAGE 4414 (PRTPRN) 4414.0 SIL TABLE NOT AVAILABLE FOR COMPRESSIBLE VIRTUAL FLUID MASS. User information: The SEALL operation must be completed on the residual structure before this capability may be used. *** USER INFORMATION MESSAGE 4415 (PRTPRN) 4415.0 - SET DEGREES OF FREEDOM HAVE EITHER THE FOLLOWING A NULL MASSES OR NULL MASSES AND STIFFNESS. r information: Use If the listed degrees of freedom have null mass for the GIV, HOU, MHOU, or MGIV methods, they are automatically omitted. For the INV method, or for direct frequency or direct transient response, they are given the auto - elimination operat ion. Inspect the listed degrees of freedom to ensure that masses or stiffnesses are not left out inadvertently. *** USER FATAL MESSAGE 4416 (PRTPRN) 4416.0 NO DYNAMIC LOAD TABLE AVAILABLE. User information: A frequency response or transient res ponse analysis was requested, but no dynamic load data is available. Include dynamic load data in model. *** USER FATAL MESSAGE 4417 (PRTPRN) 4417.0

256 NO TRANSIENT RESPONSE LIST AVAILABLE. User information: A transient response dynamic analysis was requested, but no transient response list is available. Include TSTEP entry in Bulk Data. *** USER FATAL MESSAGE 4418 (PRTPRN) 4418.0 NO EIGENVALUE EXTRACTION DATA IS AVAILABLE. User information: A dynam ic analysis was requested, but no eigenvalue extraction data was available. Include eigenvalue extraction data EIGR or EIGRL in the Bulk Data. Possible causes are METHOD command in Case Control, no EIGR or EIGRL in Bulk Data. METHOD command in Case Co ntrol, EIGRL entry in Bulk Data, or no RF3D83 (SOL 3 only). No correspondence between set IDs on METHOD and EIGR/EIGRL entries. *** USER FATAL MESSAGE 4419 (PRTPRN) 4419.0 NO QSET, THOUGH REQUIRED FOR DYNAMIC REDUCTION. User information: Dynami c reduction was requested for dynamic analysis but no QSET was specified. Define QSET in bulk data. *** USER WARNING MESSAGE 4420 (PRTPRN) 4420.0 THE FOLLOWING DEGREES OF FREEDOM ARE POTENTIALLY SINGULAR. User information: During decomposition, the degrees of freedom listed had pivot ratios greater than MAXRATIO. Verify that the degrees of freedom are not part of a mechanism and that elements do not have excessive stiffness. In superelement analysis, this condition causes run termination. PARAM,BAILOUT may be used to continue the run. See the NX NASTRAN Numerical MethodsUser's Guide. *** USER FATAL MESSAGE 4421 (PRTPRN) 4421.0 NO FREQUENCY RESPONSE LIST AVAILABLE. User information: A frequency response dynamic analysis was requested, but no frequency data is available. Include frequency data (FREQ, FREQ1, FREQ2) in the Bulk Data. *** USER FATAL MESSAGE 4422 (PRTPRN) 4422.0 NUMBER OF NULL ROWS IN THE DYNAMIC MATRICES IS NOT EQUAL TO THE NUMBER OF NULL COLUMNS. AUTOMATIC CONSTRAINTS CANNOT BE PERFORMED. User information: This problem may be caused by improper direct inputs for K2PP, M2PP and B2PP. Check all DMIGs and TFs defining K2PP, M2PP and B2PP It can also occur when all input matrices are null. This problem may also be caused by singularities in the model. Check the constraints

257 in the model. *** USER FATAL MESSAGE 4423 (PRTPRN) 4423.0 A NONLINEAR ELEMENT IS ATTACHED TO AN OMITTED DEGREE OF FREEDOM. User information: In material and geometric nonlinear analysis all nonlinear elements must not be attached to o - set degrees of freedom. Move the degree - set. This error will occur if there are QSETi of freedom to the a entries present but no ASETi or OMITi entries. USER WARNING MESSAGE 4424 (PRTPRN) *** 4424.0 ESTNL IS PURGED. CHECK YOUR DATABASE OR PARAM, LOOPID. *** USER INFORMATION MESSAGE 4425 (PRTPRN) 4425.0 ONE OR MORE FATAL ERRORS HAVE OCCURRED. THERE MAY BE MORE ERROR MESSAGES IN THE PRECEDING OUTPUT User information: One or more modules has found a fatal error condition. A message is printed for each fatal error condition. They have set a flag, which causes this message to be printed at the end of the run. Error messages output, so you should search your output for may occur anywhere in the these errors (search for FATAL). This message is most likely when PARAM,ERROR,0 is used. However, this error will be issued in superelement analysis if User Warning Message 4698 is also issued. mmetry analysis, if no eigenvalues are found in the In cyclic sy prescribed frequency range on the EIGR or EIGRL entry for the current harmonic, the run will not continue to the next harmonic and the message the desired will result. Instead of selecting a frequency range, input number of modes. *** USER WARNING MESSAGE 4500 (GPSP) 4500.0 STIFFNESS MATRIX PURGED, GRID POINT SINGULARITY NOT TESTED. User information: The stiffness matrix (KGG) input to module GPSP was purged. No singularity testing was possible. This can occur normally during checkout of downstream superelements before their upstream components are reduced. Assemble and reduce the upstream superelements. *** USER FATAL MESSAGE 4501 (TRLGA) 4501.0 RLOADI CARD SELECTED IN TRANSIENT ANALYSIS. USE TLOADI . User information: RLOADi entries are used in frequency response analysis. These entries have no meaning in transient analysis. Replace RLOADi with TLOADi entries. *** USER WARNING MESSAGE 4502. 4502.0 ALL PLOT VECTORS FOR SEUPPLOT%1 DO NOT HAVE THE SAME

258 NUMBER OF COLUMNS. User information: The SEUPPLOT command causes plot vectors that were generated for each superelement to be combined. There must be an equal number of vec tors for all superelements. Common causes of this error include not using SUBCOM - the same SUBCASE - REPCASE structure for all superelements and restart errors. Print the database dictionary, and inspect the number of columns in all PUGV matrices. Rer un any superelement with an incorrect number through data recovery. *** USER FATAL MESSAGE 4503. (FMPH1D) 4503.0 SELECTED ELIST BULK DATA CARD WITH ID%1 CANNOT BE FOUND. User information: An ELIST entry selected on an MFLUID Bulk Data entry coul d not be found in the MATPOOL. *** USER FATAL MESSAGE 4504. (FMPH1D) 4504.0 COMPRESSIBLE FLUID (MFLUID SET = %1) NOT ALLOWED FOR SUPERELEMENT ID = %2 ONLY ALLOWED ON THE RESIDUAL STRUCTURE. User information: Compressible fluid may only be place d on the elements of the residual structure -- not on upstream superelements. *** USER INFORMATION MESSAGE 4505 4505.0 AUXILIARY ANGLE CONCEPT IS BEING USED FOR INTERNAL GRID NO. =%1 AT DOF = %2 AND = %3 IN RADIANS *** USER WARNING MESSAGE 4506. (GPFDR) 4506.0 TOTAL STRAIN ENERGY IS ZERO. THE PERCENT OF TOTAL STRAIN ENERGY IS ALSO SET TO ZERO. *** USER INFORMATION MESSAGE 4507. (GPFDEV) 4507.0 IN SUBCASE %1 %2 %3 THERE ARE %4 %5 ELEMENTS HAVING STRAIN ENERGY WHICH IS LESS THAN %6 PERCENT OF THE TOTAL STRAIN ENERGY OF ALL ELEMENTS. *** USER INFORMATION MESSAGE 4507. (GPFDEV) 4507.1 IN SUBCASE %1 %2 %3 THERE ARE %4 %5 ELEMENTS HAVING KINETIC ENERGY WHICH IS LESS THAN %6 PERCENT OF THE TOTAL STRAIN ENERGY OF ALL ELEMENTS. *** USER INFORMATION MESSAGE 4507. (GPFDEV) 4507.2 IN SUBCASE %1 %2 %3 THERE ARE %4 %5 ELEMENTS HAVING ENERGY LOSS WHICH IS LESS THAN %6 PERCENT OF THE TOTAL STRAIN ENERGY OF ALL ELEMENTS. *** USER FATAL MESSAGE 4508 4508.0

259 A GRID AND COMPONENT HAS BEEN SPECIFIED TWICE ON DMIG %1 User information: The referenced DMIG matrix has an element input more than once. This is not allowed, even if both entries are of the same value. Delete all multipl e entries. *** USER FATAL MESSAGE 4508 4508.1 A GRID AND COMPONENT HAS BEEN SPECIFIED TWICE ON DMIK %1 *** USER FATAL MESSAGE 4508 4508.2 A GRID AND COMPONENT HAS BEEN SPECIFIED TWICE ON DMIJ %1 *** USER FATAL MESSAGE 4508 4508.3 A GRID AND COMPONENT HAS BEEN SPECIFIED TWICE ON DMIJI %1 *** USER FATAL MESSAGE 4509 4509.0 A GRID AND COMPONENT HAS BEEN SPECIFIED TWICE ON TF FUNCTION %1 User information: The referenced TF entry has an element input more than once. Delete all multiple entries. *** USER FATAL MESSAGE 4511. 4511.0 SUBCASE %1 DOES NOT REFERENCE ANY %2 BULK DATA CARD. (REQUIRED BY NON - LINEAR ANALYSIS.) User information: Each subcase in a nonlinear analysis must contain an NLPARM Bulk Data entry selec tion. The subcase indicated does not contain this selection. *** USER FATAL MESSAGE 4512. 4512.0 SUBCASE %1 REFERENCES UNDEFINED %2 CARD WITH ID =%3. User information: The NLPARM Bulk Data entry referenced in the subcase indicated does not exist in the MPT. *** USER INFORMATION MESSAGE 4520 (TA1THT) 4520.0 THE USER SUPPLIED COORDINATE SYSTEM ID %1 IS ORIENTED AT AN ANGLE OF %2 TO SIDE 1 - 2 OF THE ELEMENT ID %3 *** USER FATAL MESSAGE 4521 (TA1THT) 4521.0 THE X - AXIS OF COORDINATE SYSTEM %1 IS PERPENDICULAR TO ELEMENT %2 User information: The user supplied material orientation coordinate system x - axis is normal to the plane of the element and, hence, the material orientation angle with lines = constant o f the element is indeterminate. Choose a

260 new coordinate system ID whose x - axis is not normal to the plane of the element. *** USER FATAL MESSAGE 4522 4522.0 THE NON - RECTANGULAR AREA4 ELEMENTS ARE DIVIDED INTO TWO AREA3 ELEMENTS BY THE PROGRAM. THIS HAS CREATED TOO MANY ELEMENTS FOR THE PROGRAM TO HANDLE. INCREASE YOUR MEMORY REQUEST OR DECREASE THE NUMBER OF ELEMENTS. User information: Increase memory. *** USER FATAL MESSAGE 4523 4523.0 LEMENT ERROR IN CHBDY CARD%1 THE GRID POINTS OF A LINE E MUST BE DISTINCT. VECTOR (V1,V2,V3) MUST NOT BE THE ZERO VECTOR NOR MAY IT COINCIDE WITH THE LINE CONNECTING THE TWO GRID POINTS. User information: CHBDY entry defines an illegal line element. *** USER FATAL MESSAGE 4524 4524.0 ERROR IN C HBDY CARD%1 THIS CARD REFERENCES AN UNDEFINED VIEW CARD. User information: Either the VIEW entry number in field 9 of the CHBDY entry is incorrect, or the VIEW entry is incorrect (field 1 or 2). *** USER WARNING MESSAGE 4525 4525.0 THE USER HAS SPECIFIED A ZERO SUB - ELEMENT MESH SIZE FOR CHBDY CARD%1 THE PROGRAM DEFAULTS TO A 1 X 1 MESH SIZE AND CONTINUES PROCESSING. User information: The results are quite sensitive to subelement mesh size. *** USER FATAL MESSAGE 4526 4526.0 ERROR IN PHBDY CARD%1 THE AREA SPECIFIED MUST BE POSITIVE. User information: Element must be given positive areas. *** USER FATAL MESSAGE 4527 4527.0 ERROR IN CHBDY CARD %1 GRID POINTS %2 AND %3 ARE COINCIDENT. User information: Coincident gr id points will not properly define the element shape specified in field 4 of the CHBDY entry. *** USER FATAL MESSAGE 4528 4528.0 ERROR IN CHBDY CARD%1 AN AREA4 ELEMENT MUST BE A

261 QUADRILATERAL CONTAINING NO ANGLE GREATER THAN OR EQUAL TO 180 DEGREES. THE GRID POINTS MUST BE SPECIFIED SEQUENTIALLY AROUND THE QUADRILATERAL. *** USER FATAL MESSAGE 4529 4529.0 ERROR IN CHBDY CARD%1 VECTOR (V1,V2,V3) MUST NOT BE THE ZERO VECTOR. FIELDS 6,7, AND 8 OF THE CONTINUATION CARD OF THE CHBD Y CARD WERE ALL FOUND TO BE ZERO. User information: Thus, a vector V = (0, 0, 0) was defined. The element type (either POINT or LINE) defined in field 4 of the CHBDY entry requires V to be nonzero. *** USER FATAL MESSAGE 4530 4530.0 ERROR IN CH BDY CARD%1 THE FOUR GRID POINTS MUST ALL BE IN ONE PLANE User information: All four grid points of AREA4 element must be coplanar. *** USER WARNING MESSAGE 4531 4531.0 EITHER NB OR NG HAS BEEN CALCULATED AS ZERO FOR THE SECOND TRIANGLE COMPOSING CHBDY CARD%1 . REPLACE THE ZERO WITH A ONE. User information: The AREA4 element was split into two triangles as it is nonrectangular. The MESH distribution for NB and NG yielded a zero MESH. It was changed lacing AREA4 with two AREA3 to one. The user should consider rep elements to assume control of the MESH. *** USER FATAL MESSAGE 4532. 4532.0 FOR LOAD SET =%1, A %2 CARD REFERENCES UNDEFINED GRID ID =%3 . User information: The referenced entry refers to a grid point ID that is not i n the Bulk Data deck. *** USER INFORMATION MESSAGE 4534, 4534.0 %1 ELEMENTS HAVE A TOTAL VIEW FACTOR (FA/A) LESS THAN 0.99, ENERGY MAY BE LOST TO SPACE. User information: Some radiation HBDY elements have a column sum in the RADMTX matrix which is less than the element area. If you intended to allow energy loss, no action is required. If you do not want the loss, adjust the values on the RADMTX input data entries. *** USER WARNING MESSAGE 4535 (PTHBDY) 4535.0 CHBDY ELEMENT %1 HAS NO NORMAL OR BAD GEOMETRY

262 WHICH MAKES IT UNPLOTTABLE. User information: CHBDY types "POINT" and "LINE" must have an orientation vector. For type LINE the two grid points must be spatially distinct and not define a line collinear wi th the orientation vector (V1, V2, V3 on CHBDY entry). Check V1, V2 and V3 on CHBDY entry. *** USER WARNING MESSAGE 4536, 4536.0 COL %1, ROW %2 OF RADMTX IS NEGATIVE (%3). User information: A negative RADMTX value is not valid for a real structu re, since it corresponds to a negative view factor. Correct RADMTX entries. *** USER FATAL MESSAGE 4536. 4536.1 FREE FIELD BULK DATA CARD HAS GENERATED AN INTEGER THAT OVERFLOWS THE ALLOWED 8 COLUMNS. User information: The free field Bulk Data e ntry generator only works with 8 column - fields, but input to it generated an integer less than 9999999 or greater than 99999999. Redesignate the numbering scheme or switch to double field entries. NOTE: Double field entries CANNOT be generated using f ree field entries. *** USER INFORMATION MESSAGE 4537, 4537.0 TOTAL VIEW FACTOR (FA/A), FOR ELEMENT %1 IS %2, ELEMENT AREA IS %3. User information: This information is requested by SYSTEM(88) = 1. Correct RADMTX data, unless it is intended to radiate to space (lost to zero absolute temperature surroundings). *** USER FATAL MESSAGE 4538 (NL2INT) 4538.0 UNABLE TO FIND SELECTED TSTEPNL SET (%1) IN %2 DATA IN SUBROUTINE %3 *** USER FATAL MESSAGE 4538 (NLCINT) 4538.1 UNABLE TO FIND SELECTED %1 SET (%2) IN %3 DATA IN SUBROUTINE %4 User information: The set identification was either not selected within case control or the Bulk Data entry for the set was not supplied. Check both the case control and bu lk data for the requested NLCNTL set. *** USER FATAL MESSAGE 4538 (NLCINT) 4538.3 UNABLE TO FIND SELECTED %1 SET (%2) IN %3 DATA IN SUBROUTINE %4 User information: The set identification was either not selected within case control or the Bulk Data entry for the set was not supplied. Check both the case control and bulk data for the requested NLPARM set.

263 *** USER FATAL MESSAGE 4538 (NL2INT2) 4538.4 UNABLE TO FIND SELECTED NLCNTL SET (%1) IN %2 DATA IN SUBROUTINE %3 *** USER FATAL MESSAGE 4538 (NL2INT2) .5 4538 UNABLE TO FIND SELECTED TSTEP1 SET (%1) IN %2 DATA IN SUBROUTINE %3 *** USER FATAL MESSAGE 4538 (NL2INT2) 4538.6 UNABLE TO FIND SELECTED NLARCL SET (%1) IN %2 DATA IN SUBROUTINE %3 *** USER FATAL MESSAGE 4539 (NL2INT) 4539.0 THE TSTEPNL DATA CARDS HAVE NOT BEEN ENTERED. *** USER FATAL MESSAGE 4539 (NLCINT) 4539.1 THE %1 DATA CARDS HAVE NOT BEEN ENTERED. User information: The user requested nonlinear analysis and supplied the correct Case Control commands but did not supply the corresponding NLPARM OR TSTEPNL Bulk Data entries. Enter the corresponding NLPARM or TSTEPNL Bulk Data entries. AGE 4539 (NL2INT2) *** USER FATAL MESS 4539.2 THE NLCNTL DATA CARDS HAVE NOT BEEN ENTERED. *** USER FATAL MESSAGE 4539 (NLCINT) 4539.3 THE %1 DATA CARDS HAVE NOT BEEN ENTERED. User information: The user requested SOL 401 nonlinear analysis and supplied the correct Case C ontrol commands but did not supply the corresponding NLCNTL Bulk Data entries. Enter the corresponding NLCNTL Bulk Data entries. *** SYSTEM FATAL MESSAGE 4540 (NL2INT) 4540.0 INPUT ESTNL DATA BLOCK IS NOT IN NON LINEAR FORMAT. - System information: The EST data block which was submitted to the nonlinear iteration module was not in the correct format. This implies that the nonlinear appendages were nonexistent and no computations can be performed. (This is detected by the fact that the second tra iler word for linear EST data blocks is a zero, and it is non - zero for nonlinear appendage format.) Make sure that the DMAP has the correct EST data block as the input to the NLITER module. *** USER FATAL MESSAGE 4542 (NLINIT) 4542.0 NO LOAD INC REMENT EXISTS FOR NONLINEAR SUBCASE. User information: The DELPLV data block, which is the incremental load vector for the subcase, was null. This implies that no change in the nonlinear occurred. Review the LOAD requests and make sure a valid SUBCASE was selected.

264 *** USER WARNING MESSAGE 4543 (NL2IML) 4543.0 - LINEAR SUBCASE. NO RESTART DISPLACEMENTS EXIST FOR NON User information: On a NLITER restart condition the nonlinear incremental displacement vector was zero. Review the SUBCASE and LOAD options for correctness. *** SYSTEM FATAL MESSAGE 4546 (NLEMG) 4546.0 ESTNL AND FILE (%1) ARE NOT PROPERLY ALIGNED System information: The nonlinear EST file has become misaligned with the associated file number. Check that no elements have been inadvertently eliminated. Review element and set definitions. *** SYSTEM FATAL MESSAGE 4546 (NLEMG2) 4546.1 ESTNL AND ESTNLINI ARE NOT PROPERLY ALIGNED System information: The nonlinear EST file has become misaligned with ESTNLINI. Check that no elements have been inadvertently eliminated. Review element and set definitions. *** SYSTEM FATAL MESSAGE 4548 (NBEM1D) 4548.0 SINGULAR (C - KRR) MATRIX ENCOUNTERED FOR BEAM ELEMENT %1 System informat ion: A singular CBEAM plastic hinge matrix was detected. Review definition of CBEAM element. *** SYSTEM FATAL MESSAGE 4549 (NBEM2D) 4549.0 SINGULAR (C+KBRR) MATRIX ENCOUNTERED FOR BEAM ELEMENT %1 System information: A singular CBEAM plastic hinge update matrix was encountered. Review definition for CBEAM element. *** USER INFORMATION MESSAGE 4550 4550.0 *** NEW STIFFNESS MATRIX IS REQUIRED *** User information: This is issued based on the stiffness matrix u pdate strategy specified on the NLPARM or TSTEPNL entry, or when the adaptive gap element stiffens or its penalty value is adjusted after convergence. *** USER INFORMATION MESSAGE 4550 (NL2CON) 4550.1 *** BISECTION IS ACTIVATED BY LINE CONTACT. *** USER INFORMATION MESSAGE 4550 (NCONVG) 4550.2 *** NEW STIFFNESS MATRIX IS REQUIRED BY GAP *** *** USER INFORMATION MESSAGE 4550 (NCONVG) 4550.3 *** NEW STIFFNESS MATRIX IS REQUIRED BY LINE CONTACT. *** USER INFORMATION MESSAGE 4550 (NLITER) 4550.4

265 *** NEW STIFFNESS MATRIX IS REQUIRED BY GAP FOR PENALTY VALUE ADJUSTMENT *** *** USER FATAL MESSAGE 4551 (NL2CON) 4551.0 STOPPED PROBLEM DUE TO FIVE CONSECUTIVE DIVERGING TIME STEPS. User information: A solution is not possible. Review NLPARM requests and modify to select a better solution approach. *** USER FATAL MESSAGE 4551 (NL2CON) 4551.1 STOPPED PROBLEM DUE TO TWO DIVERGENCES IN THE SAME TIME STEP. User information: sible. Review NLPARM requests and modify A solution is not pos to select a better solution approach. *** USER FATAL MESSAGE 4551 (NL2CON) 4551.2 *** PREVIOUS MESSAGE HAS OCCURRED ON FIVE CONSECUTIVE TIME STEPS. User information: ARM requests and modify A solution is not possible. Review NLP to select a better solution approach. *** USER FATAL MESSAGE 4551 (NCONVG) 4551.3 *** STOPPED PROBLEM DUE TO FAILED CONVERGENCE User information: A solution is not possible. Review NLPARM requests and modify to select a better solution approach. *** SYSTEM FATAL MESSAGE 4551 (NLTCON) 4551.4 STOPPED PROBLEM DUE TO FIVE CONSECUTIVE DIVERGING TIME STEPS. System information: A solution is not possible. Review NLPARM requests and modify to select a bette r solution approach. *** SYSTEM FATAL MESSAGE 4551 (NLTCON) 4551.5 STOPPED PROBLEM DUE TO TWO DIVERGENCES IN THE SAME TIME STEP. System information: A solution is not possible. Review NLPARM requests and modify to select a better solution approa ch. *** USER INFORMATION MESSAGE 4551 (NLTRD) 4551.6 *** DIVERGENCE HAS OCCURRED ON THE EXTRA TIME STEP %1 AND CONVERGENCE HAS BEEN FORCED. User information: A solution is not possible. Review NLPARM requests and modify to select a better solution approach. *** USER FATAL MESSAGE 4551 (NL2CON2) 4551.7

266 STOPPED: PROBLEM FAILS TO CONVERGE EVEN AFTER PERFORMING MAXBIS BISECTIONS. User information: A solution is not possible. Review NLCNTL/TSTEP1 requests and modify to select a better solution approach. *** USER FATAL MESSAGE 4551 (NL2CON2) 4551.8 STOPPED: PROBLEM FAILS TO CONVERGE FOR SOLUTION AT TIME ZERO. User information: A solution is not possible. Review NLCNTL/TSTEP1 requests and modify to select a better solution approach. *** USER FATAL MESSAGE 4551 (NL2CON2) 4551.9 STOPPED: PROBLEM FAILS TO CONVERGE AFTER PERFORMING MAXIMUM PERMISSIBLE ITERATIONS WHILE SOLVING AT TIME=%1. User information: A solution is not possible. Review N LCNTL/TSTEP1 requests and modify to select a better solution approach. *** USER INFORMATION MESSAGE 4551 (NL2CON2) 4551.10 THE MAGNITUDE OF THE RESIDUAL AT TIME=%1 FOR THE CURRENT ITERATION IS GREATER THAN OR THE SAME AS THE INITIAL RESIDUAL INDI CATING NON CONVERGENCE. User information: A solution is not possible. Review NLCNTL/TSTEP1 requests and modify to select a better solution approach. *** USER INFORMATION MESSAGE 4551 (NL2CON2) 4551.11 DEFAULT CONVERGENCE CRITERION IS MODIFIED BY CONTACT ALGORITHM. TO ENFORCE A SPECIFIC CONVERGENCE, PLEASE SET ONE OR ALL OF THE FOLLOWING NLCNTL PARAMETERS TO DESIRED VALUE: CONV, EPSU, EPSP, EPSW ) *** USER INFORMATION MESSAGE 4551 (NL2CON2 4551.12 BISECTION TRIGGERED BY CONTACT ALGORITHM AS THE NUMBER OF CONTACT DIVERGENCES EXCEEDS THEN VALUE %1 SET BY NLCNTL PARAMETER CNTMDIV. THIS FEATURE CAN BE DE - ACTIVATED BY SETTING CNTMDIV PARAMETER TO 1. *** USER WARNING MESSAGE 4557 (XSBFF ) 4557.0 THE BELOW FREE FIELD BULK DATA ENTRY IS INCORRECTLY FORMATTED. THIS ENTRY WILL MOST LIKELY BE FLAGGED AS A FATAL ERROR LATER ON.

267 %1 User information: There was an error in the free field format. Most likely an "=(n)" was coded outside of field 1, t here was a parenthesis mismatch, or an alphabetic character incorrectly included in a numeric field (e.g., "*(1.2F7)" instead of "*(1.2E7)." Correct the entry. *** USER FATAL MESSAGE 4558 4558.0 INAPPROPRIATE GEOMETRY OR INCORRECT MATERIAL DATA SPECIFIED FOR ELEMENT WITH ID =%1. SUBROUTINE REASON IS NUMBER %2. *** USER FATAL MESSAGE 4558 4558.1 INAPPROPRIATE GEOMETRY OR INCORRECT MATERIAL DATA SPECIFIED FOR ELEMENT WITH ID =%1. SUBROUTINE REASON IS NUMBER %2. - INAPPROPRIATE GEOME TRY. TRIAR - *** USER FATAL MESSAGE 4558 4558.2 INAPPROPRIATE GEOMETRY OR INCORRECT MATERIAL DATA SPECIFIED FOR ELEMENT WITH ID =%1. SUBROUTINE REASON IS NUMBER %2. - - 3X3 MATRIX INSUFFICIENT, MATERIAL ID G MID2 MATERIAL =%3 INAPPROPRIATE GEOMETRY OR INCORRECT MATERIAL DATA 4558.3 SPECIFIED FOR ELEMENT WITH ID =%1. SUBROUTINE REASON IS NUMBER %2. ZERO MOMENT OF INERTIA HAS BEEN COMPUTED. *** USER FATAL MESSAGE 4558 4558.4 INAPPROPRIATE GEOMETRY OR INCORRECT MATERIAL DATA LEMENT WITH ID =%1. SUBROUTINE REASON IS SPECIFIED FOR E NUMBER %2. MID3 MATERIAL - G - 2X2 MATRIX INSUFFICIENT, MATERIAL ID =%3 *** USER FATAL MESSAGE 4559. 4559.0 ILLEGAL GEOMETRY FOR TRIA3 ELEMENT WITH ID =%1 User information: d while calculating the local element An illegal geometry was determine reference system. Check the element grid locations and properties for acceptable values. *** USER WARNING MESSAGE 4561. 4561.0 INSUFFICIENT MEMORY INWHICH TO PERFORM ORTHOGONALITY CHECKS. ADDITIONAL MEMORY REQUIRED = %1 . User information: The amount of memory needed for eigenvector orthogonalization is 1/2 [number of eigenvectors * (number of eigenvectors +1)] +

268 2 * BUFFSIZE + number of eigenvalues. If this equation is not met, des are orthogonalized, but the checking function is not the mo performed. However, all outputs from the module are provided. If the check is desired, you should either increase memory or decrease the number of eigenvectors to satisfy the above equation. *** USER FATAL MESSAGE 4562 4562.0 TSTEP (TIME STEP) DATA IS MISSING User information: Transient analysis requires the time step data. Add a TSTEP Bulk Data entry, and select it with a Case Control command. *** USER FATAL MESSAGE 4566 4566.0 SEALED RESPONSE SPECTRA REQUESTED BUT, SPECSEL FILE NOT IN DATA BASE. User information: The Bulk Data entry used to control scaled response spectra is named DTI,SPSEL. It is described in Section 5 of the NX NASTRAN Quick Reference Guide under that name . It must be stored in the database using a DMAP alter, as described on the referenced entry description. Print the database directory to see if the SPSEL block is present. See also Error Report 3042 in Chapter 17. *** USER WARNING MESSAGE 4567, 4567.0 HESSENBERG METHOD FAILED TO CONVERGE. ALTERNATE METHOD RECOMMENDED. User information: For certain pathological problems, the transformation method may fail. In SIEMENS PLM SOFTWARE testing, this has occurred only for problem s with multiple only for problems with multiple real roots or complex conjugate roots with real components. Avoidances are to add a small damping or stiffness - zero term, to add degrees of freedom, or otherwise perturb the problem to on the real axis or move them into the complex plane. separate the roots *** USER WARNING MESSAGE 4567, 4567.1 NEW HESSENBERG METHOD FAILED TO CONVERGE. *** USER WARNING MESSAGE 4567, 4567.2 NEW HESSENBERG METHOD STOPPED TO CONVERGE. *** USER WARNING MESSAGE 4568 4568.0 THE NUMBER OF SPECTRUMS SELECTED ON THE, DLOAD CARD DOES NOT MATCH THE NUMBER OF SUPPORT POINTS., CALCULATIONS FOR THIS SUBCASE TERMINATED. User information: The DLOAD Bulk Data entry is used for an unconventional purpose in response spectrum analysis. It is required, and is used to place a scaling factor on each coordinate with enforced motion. Each of these coordinates must also be on SUPORT Bulk Data

269 entries. (See Section 15.10.) Change the number of pairs of ries to match the number of coordinates where enforced Si, Li ent motion occurs. *** USER FATAL MESSAGE 4569 4569.0 ERROR ON RECORD %1 of %2 - WRONG TYPE, NO TABLES OR INCOMPLETE PAIRS. User information: used for An error has been found in the DTI Bulk Data entries response spectra input. Check your input against the examples given in the Handbook for Dynamic Analysis. In particular, check for the presence of "D", "U", or "A" on each record. ***USER INFORMATION MESSAGE 4570 (SELA) 4570.0 NO LOADS WERE FOUND FOR UPSTREAM SUPERELEMENT %1. User information: One of the matrices needed for load assembly was not found on the database. It is assumed that no loads exist for this superelement. , *** USER FATAL MESSAGE 4571 --- 4571.0 THE PARAMETER OLDSEQ FOR THE SEQUENCER MODULE HAS A VALUE%1 - 1 WHICH IS NOT AN ACCEPTABLE VALUE. VALID SETTINGS ARE THRU 8 FOR SERIAL RUNS AND 9 OR 11 FOR PARALLEL RUNS. User information: The referenced parameter is set to an illegal value. See the NASTRAN Quick Reference Guide, Section 6 for proper values NX for the parameter, and their action. *** USER WARNING MESSAGE 4571 --- , 4571.1 THE PARAMETER NEWSEQ FOR THE SEQUENCER MODULE HAS A VALUE OF ZERO THIS WILL BE CHANGED TO NEWSEQ=3 formation: User in The referenced parameter is set to an illegal value. See the NX NASTRAN Quick Reference Guide, Section 6 for proper values for the parameter, and their action. --- , *** USER FATAL MESSAGE 4572 4572.0 RESEQUENCING PROCESSING CANNOT BE COMPLETED. User information: The resequencing algorithm has failed to converge. Avoidances are: (1) request more memory; (2) divide the structure into groups, using the SESET Bulk Data entry; (3) avoid the resequencin - 1. g operation by use of PARAM,NEWSEQ, *** USER FATAL MESSAGE 4574 (SDR1) 4574.0 DATA RECOVERY STARTED BUT NO DISPLACEMENT VECTORS AVAILABLE

270 User information: The SDR1 module has begun to expand the displacement vector from - set size, but no solution set vector is available. solution set size to g Usual causes are a null load vector. Check the loading input. If only enforced displacements are desired, add a very small load to produce a load vector. superele ment unstructured solution This message may also occur in a non - sequence if SEALL, SEMG, SELG, SEKR, SELR, or SEMP are used in the Case Control. DISPLACEMENT OR VELOCITY OUTPUT REQUEST FOR GRID 4576.0 POINT %1 REFERENCED IN DTI, SPSEL NOT PRESENT IN CASE CONTROL. SPECTRA WILL BE CALCULATED FOR IT. NO SCALED RESPONSE User information: Response spectra of the form requested by XYPLOT SPECTRAL etc. requires the presence of the DTI Bulk Data entries named SPECSEL. See Section 15.10. Scaled response spectra of the form requested by X YPLOT SPECTRAL etc. has been listed on the required Bulk Data entry DTI,SPECSEL, but not in DISP and VELO Case Control requests. Add Case Control requests for DISP and VELO. *** USER FATAL MESSAGE 4577. (GP3C) 4577.0 PLOAD4 LOAD SET =%1 REFERENCES ELEMENT ID =%2 WHICH WAS NOT FOUND AMONG TRIA3, TRIA6, QUAD4, QUAD8, HEXA, PENTA, PYRAM OR HYPERELASTIC SOLID ELEMENTS IN THE PROBLEM. *** USER FATAL MESSAGE 4578. (GP3C) 4578.0 PLOAD4 LOAD SET =%1 WITH DIAGONAL CONN ECTING GRIDS %2 AND %3 IS INCORRECT FOR ELEMENT WITH ID =%4 User information: The two grids must be at opposite corners of a quadrilateral face. *** USER FATAL MESSAGE 4578. (GP0P4B) 4578.1 PLOAD4 LOAD SET =%1 ELEMENT WITH ID =%2 GRIDS %3 AND % 4 ARE NOT CONNECTING DIAGONALLY OPPOSITE. PROGRAMMERS NOTE ( CORNER GRIDS ARE:%5 ) *** USER FATAL MESSAGE 4578. (GP0P4A) 4578.2 PLOAD4 LOAD SET =%1 HEXA ELEMENT WITH ID =%2 GRIDS %3 AND %4 ARE NOT CONNECTING DIAGONALLY OPPOSITE. *** USER FATAL MESSAGE 4579. (GP3C) 4579.0 PLOAD4 LOAD SET =%1. TETRA ELEMENT%2 DOES NOT CONTAIN GRID%3 AS A CORNER NODE FOR ANY TRIANGULAR FACE.

271 *** USER FATAL MESSAGE 4579. (GP3C) 4579.1 PLOAD4 LOAD SET =%1. PENTA ELEMENT%2 DOES NOT CONTAIN GRID%3 AS A CORNER NODE FOR EITHER TRIANGULAR FACE. *** USER FATAL MESSAGE 4579. (GP0P4A) 4579.2 PLOAD4 LOAD SET =%1 TETRA ELEMENT WITH ID =%2 %3 IS NOT A CORNER NODE FOR THE TRIANGULAR FACE WHICH DOES NOT CONTAIN "G4" = %4 *** USER FATAL MESSAGE 4579. (GP0P4A) 4579.3 PLOAD4 LOAD SET =%1 TETRA ELEMENT WITH ID =%2 GRID POINT %3 IS A INVALID FOR "G4". *** USER FATAL MESSAGE 4579. (GP0P4A) 4579.4 PLOAD4 LOAD SET =%1 PENTA ELEMENT WITH ID =%2 ODE FOR EITHER DOES NOT CONTAIN GRID %3 AS ACORNER N TRIANGULAR FACE. *** USER WARNING MESSAGE 4580. DET METHOD HAS 4580.0 CONVERGED TO A MULTIPLE POLE AT %1 INCREASE M. User information: The EIGP Bulk Data entry is used to input known roots "poles"), and the number of roots at the pole (the multiplicity, "M"). If M is underestimated, the method will not converge. If this condition is detected, the iteration process is halted. Increase M. *** USER WARNING MESSAGE 4581 (FA1PKE) 4581.0 ALYSIS FAILED TO CONVERGE FOR LOOP %1, PK FLUTTER AN ROOT %2 User information: When using the PK - method for flutter analysis, the FA1 module may not always converge to a solution. The last estimate has been kept for output. If DIAG 39 is used, the iteration data can be printed for examination. *** USER WARNING MESSAGE 4582 (DPDBB), 4582.0 DAREA ID=%1 SPECIFIED IN DYNAMIC LOAD DATA REFERS TO A NON - EXISTENT STATIC LOADS MATRIX COLUMN%2 ( NCOLS=%3 User information: The most likely cause occurs when changing a n LSEQ entry on a restart without regenerating and assembling the static load matrix. This error is detected in subroutine DPD2. , *** SYSTEM WARNING MESSAGE 4584 --- 4584.0 UNABLE TO EXECUTE THE SEQUENCER PROCESSOR DUE TO THE LACK OF CONNECTION DATA. System information: No connection data could be found probably due to missing or incomplete Bulk Data entries.

272 *** USER WARNING MESSAGE 4585. (PLOD1D) 4585.0 TH SID %1 HAS AN APPLIED LOAD BEYOND THE END PLOAD1 WI OF ELID %2 User information: The load specified or the element specified is being applied outside the end points of the CBAR, CBEAM or CBEND element. The load will be applied correctly, but it is probably no t what was desired. The effective values for X1 and X2 on the PLOAD1 entry should be less than or equal to 1.0. *** USER FATAL MESSAGE 4587, 4587.0 NO LOAD DATA AVAILABLE FOR CYCLIC SYMMETRY ANALYSIS. User information: s was requested but no load data is available. A cyclic symmetry analysi Include load data in model (i.e., LOADCYN, LOADCYH, or LOADCYT and other appropriate load data). For superelement analysis the user must include loads in all superelements. THE SEQUENCER RIGID BODY PROCESSING REQUIRES AN 4589.0 ESTIMATED%1 WORDS OF ADDITIONAL MEMORY. NO SPILL WILL OCCUR IN THE SEQUENCER (MPC & RIGIDS) WITH 4589.1 %1 WORDS OF ADDITIONAL MEMORY. *** USER INFORMATION MESSAGE 4589 --- , 4589.2 NO SEQUENCING CO ULD OCCUR WITH %1 WORDS LESS MEMORY. *** SPILL FACTOR =%2 *** *** USER INFORMATION MESSAGE 4589 , --- 4589.3 NO SPILL WILL OCCUR IN THE SEQUENCER WITH %1 WORDS OF ADDITIONAL MEMORY. *** USER WARNING MESSAGE 4590. 4590.0 A SURFACE OR VOLUME CARD HAS BEEN IMPROPERLY DEFINED IGNORED. - User information: The SURFACE or VOLUME command does not have a valid ID. Check all SURFACE or VOLUME commands for proper integer IDs. *** USER WARNING MESSAGE 4591. 4591.0 ILLEGAL PARAMETER SPECIFICATION ON A SURFACE OR VOLUME CARD. ID= %1 User information: The SURFACE or VOLUME command indicated contains data which cannot be properly interpreted or which is not a legal value for a given parameter. Check indicated SURFAC E or VOLUME commands for illegal data. *** USER WARNING MESSAGE 4592. 4592.0 THE SURFACE OR VOLUME CARD WITH ID =%1 HAS NO SET SPECIFICATION - IGNORED.

273 User information: The SURFACE or VOLUME command indicated does not select a set of Check indicated SURFACE or VOLUME command for missing elements. set ID specification. *** USER WARNING MESSAGE 4593. 4593.0 THE SURFACE OR VOLUME CARD WITH ID =%1 HAS COLLINEAR AXIS AND NORMAL SPECIFICATION. SURFACE OR VOLUME WILL BE IGNORED NOT ALLOWED - User information: The SURFACE or VOLUME command indicated fails to select different axis and normal specifications. Check indicated SURFACE or VOLUME command for improper AXIS/NORMAL specification combination. They must be different. USER WARNING MESSAGE 4594. *** 4594.0 THE POSTCDB CONTAINS NO LEGITIMATE SURFACE OR VOLUME DEFINITIONS. USER INFORMATION: SINCE NO LEGITIMATE SURFACE OR VOLUME COMMANDS EXIST, PROCESSING STOPPED. CHECK OUTPUT(POST) AND CASE CONTROL GRID POINT STRESS REQUESTS FO R CONSISTENCY. ALSO, MAKE SURE THAT SURFACE IS SPELLED CORRECTLY (SEE ERROR REPORT 3576 IN CHAPTER 17). *** USER WARNING MESSAGE 4595. 4595.0 UNABLE TO OPEN INTERNAL DATA BLOCK %1 IN GPSTR1 MODULE PROCESS STOPPED. - User information: l data block to module GPSTR1 is purged. A programming An essentia logic error exists in GPSTR1 which failed to supply the indicated data block. *** USER WARNING MESSAGE 4596. 4596.0 A SURFACE OR VOLUME CARD WITH ID= %1 REFERENCES A NON - EXISTENT SET ID = %2. User information: The set referenced on the surface card has not been defined within the post control section of the CASE CONTROL, i.e. OUTPUT(POST). Check OUTPUT(POST) and Case Control grid point stress requests for consistency of SURFACE definition s. *** USER WARNING MESSAGE 4596. 4596.1 A SURFACE OR VOLUME CARD ID REFERENCES A NON - EXISTENT SET ID. User information: The set referenced on the surface card has not been defined within the post control section of the CASE CONTROL, i.e. OUTPUT(POST).

274 Check OUTPUT(POST) and Case Control grid point stress requests for consistency of SURFACE/VOLUME definitions. *** USER WARNING MESSAGE 4597. 4597.0 A SURFACE OR VOLUME CARD WITH ID = %1 REFERENCES A SET ID =%2 WHICH CONTAINS NOELEMENTS OF PERMISSIBLE TYPE. User information: The set referenced contains no CQUAD4, CQUAD8, CQUADR, CTRIA3, CTRIA6 or CTRIAR elements. Grid point stresses are not calculated which contain no elements of permissible types. *** USER WARNING MESSAGE 4598. 4598.0 REFERENCE COORDINATE SYSTEM %1 SPECIFIED ON %2 CARD %3 IS NOT DEFINED IN CSTM. %4 IGNORED. User information: The surface card references a nonexistent coordinate system. Reference coordi nate system on indicated SURFACE is not defined in (superelement) model. Surface ignored. *** USER WARNING MESSAGE 4599. 4599.0 - AXIS IS PERPENDICULAR TO THE REFERENCE STRESS OUTPUT X STRESS SURFACE %1 AT ELEMENT %2, GRID ID = %3. STRESSES ARE ILL - DEFINED AT THIS GRID POINT. User information: - The reference stress output X AXIS does not project on the local average surface for indicated element. The element to output stress rotation angle and fibre co nsistency cannot be determined. Keys are - defined at the indicated assumed to be the same. Stresses are ill grid point number. Check reference output system and AXIS specification for consistency with indicated element. *** USER WARNING MES SAGE 4600. 4600.0 THE REFERENCE STRESS OUTPUT NORMAL IS NEARLY PARALLEL TO ELEMENT, SURFACE %1 AT ELEMENT %2, GRID ID = %3. User information: The reference stress output NORMAL nearly lies in the element surface. Element fibre to output fibre consistency may be incorrect. Stress must indicate internal grid point number may not be valid. Check reference output system and NORMAL specification for consistency with indicated element. *** USER WARNING MESSAGE 4601. 4601.0 THE REFERENCE STRESS OUTPUT X - AX IS IS NEARLY PERPENDICULAR TO ELEMENT, SURFACE %1 AT ELEMENT %2, GRID ID = %3.

275 User information: - AXIS does not project on the element The reference stress output X surface. Element to output stress rotation angle cannot be determined. Rotation angle s et to 0. Stresses at indicated internal grid point number may not be valid. Check reference output system and AXIS specification for consistency with indicated element. *** USER WARNING MESSAGE 4602. 4602.0 BREAK WARNING MESSAGE - GRID%1 IN SURFACE%2 CONNECTS TO A LINE SEGMENT SHARED BY MORE THAN TWO ELEMENTS. User information: Indicated grid point connects to a line segment shared by more than ed internal two elements (GEOMETRIC interpolation only). Stress at indicat grid point may not be valid. *** USER FATAL MESSAGE 4603. 4603.0 THE LSEQ SET ID %1 IS NOT UNIQUE WITH RESPECT TO OTHER STATIC LOAD IDS. User information: LSEQ set IDs must be unique with respect to all other static load set IDs. *** USER FATAL MESSAGE 4604. 4604.0 FLUID MASS INTEGRATION ROUTINE HAS DETECTED ILLEGAL GEOMETRY. SENDER ELEMENT ID =%1. RECEIVER ELEMENT ID =%2 User information: Surface elements used for virtual mass must not overlap. This message occurs when the center of a receiver element lies at an edge of a sender element. Correct geometry or selection of elements. *** USER FATAL MESSAGE 4605. 4605.0 INPUT MATRIX %1 IS INCOMPATIBLE WITH ITS ASSOCIATED TOL,FOL,LAMA,CLAMA). OUTPUT LIST (I.E., User information: Input matrix to module MODACC has fewer columns than its output list indicates. Probable DMAP error. *** USER WARNING MESSAGE 4606. 4606.0 SURFACE OR VOLUME ID %1 HAS BEEN MULTIPLY DEFINED. LAST DEFINITION USED. *** USER WARNING MESSAGE 4607. 4607.0 %1 %2 CONTAINS ELEMENTS OF QUESTIONABLE STRESS/STRAIN RECOVERY FORMULATIONS, REASONS: %3 %4 %5 %6 1. MIX OF ELEMENTS WITH PLANE STRESS AND PLANE STRAIN RECOVERY. 2. MIX OF H - ELEMENTS AND HYPERELASTIC E LEMENTS

276 DETECTED. 3. GAUSS DATA RECOVERY DETECTED ON SOME ELEMENTS. AXISYMMETRIC HYPERELASTIC 4. AXISYMMETRIC AND NON - ELEMENTS PRESENT. USER ACTION: REASSIGN THE %1 WITH ELEMENTS THAT HAVE CONSISTENT STRESS/STRAIN RECOVERY FORMULATIONS. *** USER WARNING MESSAGE 4608 FROM GPSTR1 4608.0 COORDINATE SYSTEM SPECIFIED ON PSOLID BULK DATA ENTRY BUT NO CSTM DATA BLOCK PRESENT. *** USER WARNING MESSAGE 4609 . 4609.0 FOR ELEMENT ID=%1, THE CORNER POINTS HAVE NOT BEEN RMINATED. SUPPLIED CORRECTLY. GPSTR1 TE *** USER WARNING MESSAGE 4610 . 4610.0 THE CORNER/BILIN OPTION FOR STRESS AND FORCE IS IGNORED FOR CQUAD4 ELEMENTS WITH A THERMAL LOAD AND A SHELL OFFSET AS THIS PRODUCES INCORRECT STRESS/FORCE RESULTS. WORK AROUNDS INCLUDE: ADR ELEMENT (SEE SYSTEM CELL 370 or QRMETH). 1) USE CQU 2) USE CENTER, SGAGE OR CUBIC OPTION ON STRESS/FORCE CARDS. *** USER WARNING MESSAGE 4620, 4620.0 GPSTRESS REQUEST IN SUBCASES IGNORED SINCE NO BGPDT INPUT. *** USER WARNING MESSAGE 4621 (STDCON), 4621.0 NO STRESS DATA IS AVAILABLE FOR ELEMENT %1 SUBCASE %2 SURFACE/VOLUME %3. USER ACTION : REQUEST ELEMENT STRESS OUTPUT FOR ALL ELEMENTS IN THE SURFACE/VOLUME. User information: as not requested. This stress Stress output for the specified element w output is required to calculate the grid stresses for the specified surface. *** USER WARNING MESSAGE 4623 4623.0 OES1 MISSING GPSTR2 PROCESSING ERMINATED. *** USER FATAL MESSAGE 4625 4625.0 INSUFFICIENT MEMORY FOR GPSTR2 MODULE GINO BUFFER ALLOCATION. *** USER FATAL MESSAGE 4626 4626.0 INSUFFICIENT MEMORY FOR GPSTR2 MODULE TO PROCESS GPL. *** USER FATAL MESSAGE 4627 4627.0 INSUFFICIENT MEMORY FOR GPSTR2 MODULE TO PROCESS CASECC. *** USER FATAL MESSAGE 4628 4628.0

277 INSUFFICIENT MEMORY FOR GPSTR2 MODULE TO STORE STRFIELD SET. *** USER FATAL MESSAGE 4629 4629.0 INSUFFICIENT MEMORY FOR GPSTR2 MODULE TO STORE GPSTR ESS SET. *** USER FATAL MESSAGE 4630 4630.0 INSUFFICIENT MEMORY FOR GPSTR2 MODULE TO STORE ELEMENT LIST. *** USER WARNING MESSAGE 4631, 4631.0 STRFIELD SET %1 NOT FOUND IN CASECC SUBCASE%2 *** USER WARNING MESSAGE 4632, 4632.0 GPSTRESS SET %1 NOT FOUND IN CASECC SUBCASE%2 *** USER WARNING MESSAGE 4633, 4633.0 NO OUTPUT STRESS REQUEST FOR SUBCASE %1 SO NO GRID STRESSES CALCULATED *** USER WARNING MESSAGE 4634, 4634.0 NO STRESSES FOR SUPPORTED ELEMENT TYPES ON OES1 FOR SUBCASE %1 SO NO GRID STRESSES CALCULATED *** USER WARNING MESSAGE 4635, 4635.0 GPSTRESS REQUEST IN SUBCASE %1 IGNORED SINCE OGS1 PURGED *** USER WARNING MESSAGE 4636, 4636.0 STRFIELD REQUEST IN SUBCASE %1 IGNORED SINCE EGPST PURGED *** USER FATAL MESSAGE 4637 4637.0 INSUFFICIENT MEMORY FOR GPSTR2 MODULE TO STORE ELEMENT POINTER LIST User information: GPSTR2 requires at least enough working space to hold in memory an element pointer list consisting of two computer words for each element of a supported type (CQUAD4, CQUAD8, CTRIA3, or CTRIA6) selected for output. *** SYSTEM FATAL MESSAGE 4638, 4638.0 LOGIC ERROR SUBROUTINE GPS2GS - SCR1 FILE INCONSISTENT WITH P OINTER TABLE. SEARCHING FOR EID %1 FOUND EID %2 *** USER WARNING MESSAGE 4639, 4639.0 GPSTRESS REQUEST IN SUBCASE %1 BUT NO MATCHING SURFACE OR VOLUME ID ON EGPSF *** SYSTEM FATAL MESSAGE 4639, (GPS2GD) 4639.1 LOGIC ERROR SUBROUTINE GPS2GS - SCR1 FILE ENTRY FOR EID %1

278 DOES NOT HAVE GRID PT. %2 *** USER WARNING MESSAGE 4640, 4640.0 STRFIELD REQUEST IN SUBCASE %1 BUT NO MATCHING SURFACE OR VOLUME ID ON EGPSF User information: STRFIELD must reference set x x, which in turn references SURFACE or VOLUME yy. For example, SET 21 = 91 GPSTRESS = 21 STRFIELD = 21 ... OUTPUT(POST) ... --- SURFACE 91 *** USER WARNING MESSAGE 4642 (NLINIT) 4642.0 NLPARM SET%1 DISPLACEMENT CONVERGENCE OPTION IS INVALID FOR MATRIX UPDATE INTERVAL OF ONE WHEN METHOD IS EITHER ITER OR LSQN. THE WORK(W) CONVERGENCE OPTION HAS BEEN SUBSTITUTED IF NONE SUPPLIED. *** USER WARNING MESSAGE 4642 (NLTINT) 4642.1 NL SET%1 CONVERGENCE OPTION IS INVALID FOR MATRIX TSTEP UPDATE INTERVAL OF ONE HWHEN METHOD IS TSTEP. THE LOAD(P) CONVERGENCE OPTION HAS BEEN SUBSTITUTED. *** USER FATAL MESSAGE 4643 (GP1C) 4643.0 DUPLICATE COORDINATE SYSTEM ID %1 FOUND IN SUPERELEMENT %2 User information: Message indicates user has defined a coordinate system twice. Check for duplicate coordinate system IDs on CORD ij entries. ***USER FATAL MESSAGE 4645 ---- 4645.0 THE SHIFTED STIFFNESS MATRIX IS NOT POSITIVE DEFINITE IN MHOUSEHOLDER METHOD. User information: The matrix sum K + LAMBDA * M is decomposed by the Cholesky method at the start of the MGIV method of eigensolution. This decomposition requires that the ma - definite. A condition that prevents this is a massless trix be positive mechanism (for example, a point mass on an offset with no rotational stiffness). ***USER FATAL MESSAGE 4645 ---- 4645.1 THE SHIFTED STIFFNESS MATRIX IS NOT POSITIVE DEFINITE IN MGIVENS METHOD. ***USER FATAL MESSAGE 4646 ---- 4646.0

279 THE MASS MATRIX IS NOT POSITIVE DEFINITE, USING THE HOUSEHOLDER METHOD. USE MGIV INSTEAD. ***USER FATAL MESSAGE 4646 ---- 4646.1 THE MASS MATRIX IS NOT POSITIVE DEFINITE, USING THE GIVENS METHOD. USE MGIV INSTEAD. User information: The reduced mass matrix has columns that are not linearly independent. Common causes are rotation degrees of freedom whose only inertia terms from point masses on offsets. Use the MGIV or MHOU method instead result since it does not require a positive definite mass matrix. *** USER FATAL MESSAGE 4646. 4646.4 THE MASS MATRIX INPUT TO THE REAL EIGENSOLVER IS INDEFINITE. ELEMENTS CONNECTED TO THIS USER ACTION: INSPECT THE POINT. IF ALL ARE VALID, A VALUE OF 1.E - 6 OR MORE TIMES THE MASS DIAGONAL TERM PRINTED ABOVE ADDED TO THIS DOF MAY MAKE THE MASS MATRIX ACCEPTABLE, IF THIS IS AN ACCEPTABLE CHANGE TO YOUR MODEL. S MATRIX DIAGONALS BY YOU MAY ALSO PERTURB THE MAS SPECIFYING SYSTEM(304)=0 ON THE NASTRAN CARD. IF SUCH CHANGES ARE NOT VALID, CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. YOU MAY HAVE DISCOVERED AN ERROR IN THE ELEMENT CODE. *** USER FATAL MESSAGE 4647. 4647.0 INSUFFICIENT TIME TO COMPLETE %1 CPU ESTIMATE =%2 SEC. CPU REMAINING =%3 SEC. I/O ESTIMATE =%4 SEC. I/O REMAINING =%5 SEC. User information: CPU and I/O limits are supplied on the Executive Control statement minated program is listed. TIME (in minutes). The module where the ter If the time to completion appears reasonable, you should increase the estimates on the TIME statement and resubmit the run. For large models, an increase in the system memory request should also be considered. ** *USER WARNING MESSAGE 4648 ---- 4648.0 THE MODAL MASS MATRIX IS NOT POSITIVE DEFINITE. User information: The modal mass matrix cannot be decomposed by the Cholesky algorithm after merging elastic and free - body modes. (Cholesky decomposition is used to orthogo nalize the eigenvectors with respect to the mass matrix.) Causes include the input of negative masses and the calculation of eigenvectors for eigenvalues approaching machine infinity. Inspect Inspect the model or ask for fewer eigenvectors using of the F2 option. When this condition occurs, the eigenvectors are not orthogonalized r normalized. The second parameter of the READ or REIGL module is given

280 a negative sign. This parameter is used in the solution sequences to inting the real eigenvalue table. branch to an error exit after pr You may use a DMAP Alter to print these eigenvectors if the cause of the problem is not apparent in the eigenvalues. The solution can be forced to completion by changing the sign of this parameter. You that a poor quality of solution is provided for this should be aware case. This poor solution may be useful for diagnosing the problem but should not be used for other purposes. The error can occur when large offsets (large relative to the element length) are used for the BEAM element and coupled mass is selected. *** SYSTEM INFORMATION MESSAGE 4652 (NL2INT) 4652.0 THE ADDITIONAL MEMORY ESTIMATE IS %1 WORDS. REDUCE P SET BY APPROXIMATELY %2 DEGREES OF FREEDOM. - System information: er statics or transient) there was For nonlinear problems (eith insufficient open core space to process the problem. This attempts to estimate the additional memory requirements in machine words and supply an alternative approach to allow the user to reduce his r supply more machine memory or reduce the problem problem size. Eithe size by the indicated amount. This is similar to the UFM 6136. *** SYSTEM FATAL MESSAGE 4653. (TTX6D) 4653.0 CORE IS INSUFFICIENT BY A BASE10 AMOUNT =%1 WORDS TO PROCESS ELEMENT WITH ID =%2 System information: Reduce problem size or increase memory. *** USER FATAL MESSAGE 4654 . 4654.0 ELEMENT WITH ID =%1 CONNECTS TWO POINTS HAVING THE SAME COORDINATES. CONNECTION ORDER OF GRID POINTS IN QUESTION =%2 AND %3 User information: Two grid points which should be unique are defined as coincident. Check connectivity. *** USER FATAL MESSAGE 4654 4654.1 ELEMENT WITH ID =%1 CONNECTS TWO GRID POINTS=%2 AND %3 HAVING SAME COORDINATES. *** USER FATAL MESSAGE 4654 (SECNV3) 4654.2 GRID POINTS %1 AND %2 REFERENCED ON THE FOLLOWING %3 BULK DATA ENTRY %4 ARE COINCIDENT *** USER FATAL MESSAGE 4654 (SECNV3) 4654.3 THE VECTORS DEFINED BY THE GRID POINT PAIRS %1 / %2 AND %3 / %4 REFERENCED ON THE FOLLOWING %5 BULK DATA ENTRY %6 ARE COINCIDENT *** USER WARNING MESSAGE 4654 (EHEXLGC/EPENLGC) 4654.4 THE THICKNESS OF ELEMENT ID %1 IS NOT CONSISTENT WITH

281 THE SUM OF THE PLY THICKNESSES DEFINED ON THE PCOMPS CARD. THE PLY THICKNESSES WILL BE SCALED TO FIT THE ELEMENT THICKNESS . *** USER FATAL MESSAGE 4654 (EPENLGC,STS268) 4654.5 THE STACKING DIRECTION FOR THE COMPOSITE PENTA ELEMENT ID %1 IS ONLY SUPPORTED ALONG THE NORMAL DIRECTION OF THE TWO TRIANGULAR FACES. *** USER WARNING MESSAGE 4654 (EHEXLGC/EPENLGC) 4654.6 THE LONGEST TO SHORTEST EDGE RATIO IN THE STACKING DIRECTION OF COMPOSITE SOLID ELEMENT %1 IS GREATER THAN %2. *** USER WARNING MESSAGE 4654 (EHEXLGC/EPENLGC) 4654.7 THE THICKNESS RATIO IN COMPOSITE SOL ID ELEMENT %1 IS GREATER THAN %2. *** USER INFORMATION MESSAGE 4655 . 4655.0 RATIO OF LONGEST EDGE TO SHORTEST EDGE EXCEEDS 100 FOR ELEMENT WITH ID =%1 User information: Aspect ratio too large. Try to idealize the structure in such a way that all the edges are nearly the same size. *** USER WARNING MESSAGE 4655 4655.1 IN CRAC2D ELEMENT%1 ,THE ASPECT RATIO EXCEEDS 2 TO 1 CAUSES RESULTS IN WRONG ANSWERS *** USER WARNING MESSAGE 4655 4655.2 IN CRAC3D ELEMENT%1 ,THE ASPECT RATIO EXCEED S 2 TO 1 CAUSES RESULTS IN WRONG ANSWERS *** USER INFORMATION MESSAGE 4655 4655.3 THE RATIO OF LONGEST EDGE TO SHORTEST EDGE EXCEEDS %1 FOR %2 ELEMENT ID =%3 User information: Aspect ratio too large. Try to idealize the element in such a way that all the edges are nearly the same length. *** USER INFORMATION MESSAGE 4656 4656.0 ELEMENT WITH ID =%1 HAS A SIDE WHICH IS CONSIDERABLY OUT OF PLANE. User information: One of grid points for the element may be defined wrong. Check connectivity. *** USER INFORMATION MESSAGE 4657 . 4657.0 CONNECTION ORDER GRID NUMBER %1 DOES NOT LIE APPROXIMATELY BETWEEN CONNECTION ORDER

282 GRID NUMBERS %2 AND %3 FOR ELEMENT ID = %4 information: User Midside node for the element node may be defined wrong. Check connectivity of all nodes for the element. *** USER FATAL MESSAGE 4658 . 4658.0 DIFFICULT GEOMETRY PREVENTS FURTHER COMPUTATIONS FOR ELEMENT WITH ID =%1 User information: Difficult geometry for solid elements occurs when faces have zero areas, or when Jacobians at integration points do not all have the same sign, which signifies that the edges are crossed. In geometric e for initial and deformed geometry. nonlinear analysis, tests are mad Elements should be modeled such that their faces are as nearly equilateral as possible and midside nodes should be positioned close to the center of their edges. *** USER FATAL MESSAGE 4658 . 4658.5 DIFFICULT GEOMETRY PREVENTS FURTHER COMPUTATIONS FOR QHBDY WITH GRID POINTS %1 *** USER FATAL MESSAGE 4659. 4659.0 DURING INTEGRATION FOR ELEMENT WITH ID =%1 BAD GEOMETRY HAS BEEN DETECTED. User information: The element may be folding on itself. Check the grid points which connect all the edges of the element. *** USER WARNING MESSAGE 4659 (PSNORD) 4659.6 DURING COMPUTING NORMALS AT EDGE FOR ELEMENT WITH ID =%1 BAD GEOMETRY HAS BEEN DETECTED. *** USER WARNING MESSAGE 4659 (PSNORD) 46 59.7 DURING COMPUTING NORMALS AT VERTEX FOR ELEMENT WITH ID =%1 BAD GEOMETRY HAS BEEN DETECTED. *** USER FATAL MESSAGE 4659 (ETETD) 4659.10 DURING INTEGRATION FOR ELEMENT WITH ID =%1 BAD GEOMETRY HAS BEEN DETECTED. USER ACTION: IF YOU WISH TO CONTINUE, THEN SET SYSTEM(213)=1, HOWEVER, THE RESULTS MAY BE POOR. BAD GEOMETRY IGNORED FOR ELEMENT WITH ID =%1 BASED ON 4659.20 SYSTEM(213)=3. HOWEVER, RESULTS MAY BE POOR. USER ACTION: REMOVE SMALL GEOMETRIC FEATURES AND/OR REDUCE ELEMENT SIZE

283 IN THE IMMEDIATE NEIGHBORHOOD OF THIS ELEMENT BEFORE REMESHING. SEE BELOW FOR ELEMENT CORNER GRID LOCATIONS. ELEMENT CORNER GRID INFORMATION (X,Y,Z): GRID 1: %2 GRID 2: %3 GRID 3: %4 GRID 4: %5 BAD GEOMETRY IGNORED FOR ELEMENT WITH ID =%1 BASED ON 4659.21 SYSTEM(213)=3. HOWEVER, RESULTS MAY BE POOR. USER ACTION: REMOVE SMALL GEOMETRIC FEATURES AND/OR REDUCE ELEMENT SIZE IN THE IMMEDIATE N EIGHBORHOOD OF THIS ELEMENT BEFORE REMESHING. SEE BELOW FOR ELEMENT CORNER GRID LOCATIONS. ELEMENT CORNER GRID INFORMATION (X,Y,Z): GRID 1: %2 GRID 2: %3 GRID 3: %4 GRID 4: %5 GRID 5: %6 GRID 6: %7 GEOMETRY IGNORED FOR ELEMENT WITH ID =%1 BASED ON BAD 4659.22 SYSTEM(213)=3. HOWEVER, RESULTS MAY BE POOR. USER ACTION: REMOVE SMALL GEOMETRIC FEATURES AND/OR REDUCE ELEMENT SIZE IN THE IMMEDIATE NEIGHBORHOOD OF THIS ELEMENT BEFORE REMESHING. SEE BELOW FOR ELEMENT CORNER GRID LOCATIONS. ELEMENT CORNER GRID INFORMATION (X,Y,Z): GRID 1: %2 GRID 2: %3 GRID 3: %4 GRID 4: %5 GRID 5: %6 GRID 6: %7 GRID 7: %8 GRID 8: %9 *** USER WARNING MESSAGE 4659 (EMBPMD) 4659.23 BAD GEOMETRY IGNORED FOR ELEMENT WITH I D =%1 BASED ON SYSTEM(213)=1, HOWEVER RESULTS MAY BE POOR *** USER FATAL MESSAGE 4660 . 4660.0 FOR ELEMENT WITH ID =%1

284 THE CORNER POINTS HAVE NOT BEEN SUPPLIED CORRECTLY. *** USER FATAL MESSAGE 4660 (CTRIAXI3) . 4660.1 FOR ELEMENT WITH ID =%1 ALL THE GRID POINTS HAVE NOT BEEN SUPPLIED CORRECTLY. User information: See Bulk Data entry description for CTRIAXI3 in Section 5 of the NX NASTRAN Quick Reference Guide. *** USER FATAL MESSAGE 4660 (CQUADAX4) . 4660.2 F OR ELEMENT WITH ID =%1 ALL THE GRID POINTS HAVE NOT BEEN SUPPLIED CORRECTLY. User information: See Bulk Data entry description for CQUADAX4 in Section 5 of the NX NASTRAN Quick Reference Guide. *** USER FATAL MESSAGE 4660 (CTRIAX6/CTRAX3/ CTRAX6) . 4660.3 FOR ELEMENT WITH ID =%1 ALL THE GRID POINTS HAVE NOT BEEN SUPPLIED CORRECTLY. User information: See Bulk Data entry description for CTRAX3/CTRAX6/CTRIAX6 in Section 5 of the NX NASTRAN Quick Reference Guide. *** USER FATAL MESSAGE 4660 (CQUADX4/CQUADX8/CCHOCK*) . 4660.4 FOR ELEMENT WITH ID =%1 ALL THE GRID POINTS HAVE NOT BEEN SUPPLIED CORRECTLY. User information: See Bulk Data entry description for CQUADX4/CQUADX8/CCHOCK* in nce Guide. Section 5 of the NX NASTRAN Quick Refere *** USER FATAL MESSAGE 4660 . 4660.5 FOR ELEMENT WITH ID =%1 THE GEOMETRY HAS NOT BEEN DEFINED PROPERLY . *** USER FATAL MESSAGE 4660 . 4660.6 FOR ELEMENT WITH ID =%1 THE GEOMETRY HAS NOT BEEN DEFINED PROPERLY. THE X (RADIAL) COORDINATE MUST BE GREATER OR EQUAL TO ZERO. *** USER FATAL MESSAGE 4660 4660.7 (CPLSTS3/CPLSTS4/CPLSTS6/CPLSTS8) . FOR ELEMENT WITH ID =%1 ALL THE GRID POINTS HAVE NOT BEEN SUPPLIED CORRECTLY. *** USER FATAL MESSAGE 4660 . 4660.8 FOR ELEMENT WITH ID =%1 THE GEOMETRY HAS NOT BEEN DEFINED PROPERLY. THE INITIAL GAP OPENING IN THE SYMMETRY AXIS MUST BE EQUAL TO ZERO. *** USER FATAL MESSAGE 4660 (EGRACT) 4660.11

285 FOR ELEMENT WITH ID =%1 ALL THE CORNER POINTS HAVE NOT BEEN SUPPL IED. USER ACTION: SPECIFY ALL REQUIRED CORNER POINTS. User information: Elements like CHEXA and CPENTA require, at a minimum, 8 or 6 corner points, respectively. Minimum number of corner points are mandatory for certain elements. Check connectivity. *** USER FATAL MESSAGE 4660 4660.12 (MTX324Z/MTX325Z/MTX326Z/MTX327Z) THE PGPLSN ENTRY REFERENCES THE CONTROL GRID POINT %1 WHICH CANNOT BE CONNETECTED TO THE GENERALIZED PLANE STRAIN ELEMENT %2 *** USER FATAL MESSAGE 4661 . 4661.0 ELEMENT %1 HAS SINGULAR STRAIN FUNCTIONS . CHECK MATERIAL PROPERTIES. User information: Because of 0 in a diagonal element of strain function stiffness matrix, inversion is not possible. Check to make sure tangent matrix is nonsingular. * ** USER WARNING MESSAGE 4662 . 4662.0 SOME VARIABLES ARE RESET TO AVOID OVERFLOW OR UNDERFLOW CONDITIONS IN ELEMENT ID = %1 User information: Creep laws are unit dependent. Creep parameters could get into ., lb and ksi). overflow condition if inconsistent units are used (e.g The program resets the value to 1.0E38 and continues. Check structural units (length, force, stress, time, etc.). Reduce the time step (t). *** USER WARNING MESSAGE 4664 . 4664.0 UNREALISTIC VALUE OF STRESSES FOR PLASTIC DEFORMATION - ID =%1 IN ELEMENT User information: This message is issued if the second invariant of the deviatoric stress is nearly zero during plastic deformation. This condition should not occur under the norma l deformation process. It may be a program error if it happens. Use smaller steps. If this does not work, contact SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER WARNING MESSAGE 4665 . 4665.0 THE NUMBER OF LAYERS MUST BE GREATER THAN 0 AND LESS THAN 13 . FOR THIS PROBLEM , NLAYER = %1 User information: NLAYER must be greater than zero and less than thirteen. NLAYER is the number of layers for integration through the thickness. For bending, it is advisable to have NLAYER greater than 1.

286 *** USER WARNING MESSAGE 4665 . 4 665.1 THE ALLOWED NUMBER OF LAYERS MUST BE 3/5/7/9 FOR SOL401, OTHERWISE, THE DEFAULT VALUE OF 5 WILL BE USED. FOR THIS PROBLEM, NLAYER = %1 User information: NLAYER must be either 3/5/7/9 for shell elements of SOL401. NLAYER is the number of layers for integration through the thickness. PROBABLE ERROR . NEED MORE LAYERS THAN ONE IF BENDING . 4666.0 User information: If bending is present, then wrong results are likely if only one layer is specified for integration through the thickness. Either use the default (5) or specify NLAYERS greater than 1. INCREMENTAL 4667.0 TIME INTERVAL FOR CREEP ANALYSIS IS EXCESS IVE IN ELEMENT ID=%1 User information: This message is issued if the incremental creep strain (primary and/or total creep) is greater than 10** - 3 or if the incremental stress and/or strain is too large compared to the total stress/strain. This message is issued only when the solution is converging. Reduce the creep time interval. This message may also be issued when the initial static subcase is missing. Include a static subcase before the creep subcases. *** USER FATAL MESSAGE 4669 . 4669.0 NO LOAD DATA EXISTS FOR VECTOR =%1 User information: Check the CLOAD entry. *** USER FATAL MESSAGE 4670 . 4670.0 SELECTED CLOAD BULK DATA CARD DOES NOT EXIST FOR SID = %1 *** USER FATAL MESSAGE 4671 . 4671.0 LOAD COMBINATION REQUESTED BU T LSEQ CARDS DO NOT EXIST FOR SID = %1 User information: Check the LSEQ entries. *** USER FATAL MESSAGE 4672 (TA1NLE). 4672.0 PIN FLAG(S) IS(ARE) SPECIFIED FOR ONE OR MORE NONLINEAR CBEAM ELEMENT ENTRIES. USER INFORMATION : IN NONLINEAR ANALYSIS, THE USE OF PIN FLAGS ON NONLINEAR BEAM ELEMENTS IS NOT SUPPORTED. User information: Either remove the pin flags for nonlinear elements or make the problem linear.

287 *** USER WARNING MESSAGE 4672 (TA1A ) 4672.1 PIN FLAG(S) IS(ARE) SPECIFIED FOR ONE OR MORE CBEAM P - ELEMENT ENTRIES. USER INFORMATION: IN P ELEMENT ANALYSIS, THE USE OF PIN - FLAGS ON BEAM P ELEMENTS IS NOT SUPPORTED. - *** USER WARNING MESSAGE 4672 (TA1A) 4672.2 ALL - - FIED ON A MATCID CARD. NO THE ENTRY HAS BEEN SPECI NEED FOR OTHER MATCID CARDS. THE CIDS ON ALL OTHER MATCID CARDS WILL BE IGNORED. *** USER WARNING MESSAGE 4673 . 4673.0 AT LEAST ONE SOLID ELEMENT IGNORES NONLINEAR MATERIAL DATA BECAUSE SELECTED OPTION IS NOT AVAILABLE. User information: For nonlinear analysis, solid elements with nonlinear material properties may not have midside nodes and their integration network may not be 3 or THREE. See the PSOLID entry description in Section 5 of the NX NASTRAN Quick Referenc e Guide. Otherwise only a linear solution is possible. *** USER FATAL MESSAGE 4674 . 4674.0 E IS TOO LARGE FOR ELEMENT =%1 *** USER WARNING MESSAGE 4675 . 4675.0 EXCESSIVE INCREMENTAL LOAD IS APPLIED IN ELEMENT ID = %1 REDUCE THE LOAD INC REMENT BY A FACTOR OF %2 FOR BETTER SOLUTION . User information: This message is issued if the number of subincrements (m) in the plasticity routine is required to be greater than 25. The number of subincrements is determined by * Y + 1 ) m = lnt ( F / FSTRESS Where F is the value of yield function, Y is the yield stress, FSTRESS is the user input, on NLPARM entry. The program continues execution with the number of subincrements(m) reset to 10. Use smaller load increments. USER FATAL MESSAGE 4676 . *** 4676.0 ERROR EXCEEDS %1 PERCENT OF YIELD STRESS IN ELEMENT ID=%2 User information: The error in the yield function will be corrected if it is within (FSTRESS*100) %. This message will be issued if the error is greater than this. Ta ke smaller load increments or specify a larger error tolerance in the FSTRESS field on the NLPARM entry. All output requests are honored for subcases processed prior to this message; then execution is terminated.

288 - UP TABLE LOOK 4678.0 NEGATIVE VALUE OF CREEP MODEL PARAMETER IN RESULTS IN ELEMENT ID = %1 *** USER WARNING MESSAGE 4678 (HMAT1) 4678.1 TABLE LOOK - UP ON TABLE ID %1 FOR MATERIAL ID %2 RESULTS IN A NEGATIVE VALUE OF A MATERIAL PROPERTY FOR ELEMENT ID =%3 . THIS MATERIAL PROPERTY WILL BE SET TO 0.0 . USER ACTION: MAKE SURE THE TABLE CANNOT RETURN NEGATIVE VALUES BY INTERPOLATION OR BY EXTRAPOLATION. User information: Creep parameters must be positive for table supplied data. The program sets the value to zero and continues. C heck the table values of creep parameters. ZERO DERIVATIVE ENCOUNTERED IN CREEP LAW TYPE 300 FOR 4679.0 ELEMENT ID = %1 User information: Unsolvable nonlinear equation in creep law type 300. The program sets the value to 10 - 6 and continues. Check the creep data. Reduce t for creep. *** USER WARNING MESSAGE 4680 4680.0 SEMAP DATA BLOCK DOES NOT EXIST. *** USER WARNING MESSAGE 4680 4680.1 INPUT FILES TO TABPT ARE PURGED. User information: "PURGED" means "does not exist". *** USER WARNING MESSAGE 4680 4680.2 LISTFL DATA BLOCK DOES NOT EXIST. *** USER FATAL MESSAGE 4681 4681.0 INSUFFICIENT MEMORY FOR GPSTR2 MODULE TO SORT OGS1 DATA ON EXT GRID ID. User information: In order to sort OGS1 data on external grid ID, GPSTR2 must store a table of size 2 x (no. of grids in surface) in open core. The above message is issued if amount of open core will not accommodate this table. Increase memory request for the job. *** USER FATAL MESSAGE 4682, 4 682.0 HARMONICS SET SPECIFIED FOR ANALYSIS INCONSISTENT WITH SPECIFIED SYMMETRY OPTION. User information: All of the harmonics specified by the user with the HARMONICS command are excluded from the analysis by the symmetr y option specified on

289 the DSYM command. Note that the AA and SS options omit all odd harmonics. The AS and SA options omit all even harmonics. *** USER FATAL MESSAGE 4683 4683.0 %1 MATRIX NEEDED FOR EIGENVALUE ANALYSIS User information: The eigensolution module was given a purged (that is, nonexistent) mass or stiffness matrix. Common causes include the deletion of mass density input on MATi entries, user restart errors in the superelement selection solution sequences, or when the auto feature of generalized - dynamic reduction (GDR) determines that there are no natural frequencies below FMAX. It therefore sets the number of generalized coordinates to zero. This condition can be detected from UIM 4181. An avoidance is on the DYNRED Bulk Data entry. Provide mass matrix to increase FMAX matrix generating data by any of several means including a mass density type DMIG entries. - entry on material entries, concentrated masses, and g Possibly no mass matrix is defined. Check for the follow ing: RHO entry on MATi NSM entry on element properties (i.e., PSHELL, PBAR) CONMi or CMASSi The program requires at least one of the above to compute the mass matrix. - sectional properties may also lead to this error but Incorrect cross up as another error. typically show *** USER FATAL MESSAGE 4683, 4683.1 DIFF. STIFFNESS MATRIX NEEDED FOR EIGENVALUE ANALYSIS User information: The eigensolution module was given a purged (that is, nonexistent) mass or stiffness matrix. Common causes include the deletion of mass density input on MATi entries, user restart errors in the superelement - selection feature of generalized solution sequences, or when the auto dynamic reduction (GDR) determines that there are no natural frequencies erefore sets the number of generalized coordinates to below FMAX. It th zero. This condition can be detected from UIM 4181. An avoidance is to increase FMAX on the DYNRED Bulk Data entry. Provide mass matrix generating data by any of several means including a mass densit y entry on material entries, concentrated masses, and g - type DMIG entries. Possibly no mass matrix is defined. Check for the following: RHO entry on MATi NSM entry on element properties (i.e., PSHELL, PBAR) CONMi or CMASSi The program requires at lea st one of the above to compute the mass matrix. Incorrect cross - sectional properties may also lead to this error but typically show up as another error. *** USER FATAL MESSAGE 4690 4690.0 ON BCTPARM %1 THE GEOMANG VALUE OF %2 IS OUTSIDE THE VALID RANGE OF 0.0 - 180.0 DEGREES

290 *** USER FATAL MESSAGE 4690 4690.1 THE MATRIX/TABLE %1 IS REQUIRED IN A CONTACT/GLUE ANALYSIS *** SYSTEM FATAL MESSAGE 4690 4690.2 DATABASE ERROR WHILE READING DATA BLOCK %1 *** USER FATAL MESSAGE 4690 4690.3 INSUFFICENT MEMORY ALLOCATED FOR THE CONTACT/GLUE ANALYSIS USER ACTION: INCREASE MEMORY REQUEST AND RERUN. *** USER FATAL MESSAGE 4690 4690.4 NO CONTACT/GLUE PAIRS DEFINED FOR CONTACT/GLUE SET %1 CONTACT SET MAY NOT EXIST *** SYSTEM FATAL MESSAGE 4690 4690.5 ERROR COMPUTING CONTACT FACE TERRITORY BOUNDING BOX *** USER FATAL MESSAGE 4690 4690.6 ELEMENT %1 SPECIFIED IN CONTACT REGION %2 DOESN'T EXIST OR IS INVALID. CONTACT SURFACE ELEMENTS MUST BE SHELL OR SOLID ELEMENTS *** USER FATAL MESSAGE 4690 4690.7 CANNOT FIND A CONTACT FACE FOR ELEMENT %1 WITH THE BSURF(S) GRID POINTS *** USER FATAL MESSAGE 4690 4690.8 NO SHELL ELEMENTS FOUND FOR BCPROP REGION %1 *** SYSTEM FATAL MESSAGE 4690 4690.9 ERROR ENCOUNTERED IN RETRIEVING CONTACT ELEMENT DATA *** USER WARNING MESSAGE 4690 4690.10 ALL CONTACT ELEMENTS HAVE BECOME INACTIVE. THE STIFFNESS MATRIX MAY BECOME SINGULAR WHICH WILL RESULT IN ERRORS FURTHER IN THE ANALYSIS *** USER FATAL MESSAGE 4690 4690.11 GAP ORIENTATION UNDEFINED FOR GAP %1 *** USER FATAL MESSAGE 4690 4690.12 LINEAR CONTACT/GLUE ANALYSIS NOT POSSIBLE WITH P ELEMENTS *** USER FATAL MESSAGE 4690 4690.13 NO SURFACES DEFINED FOR CONTACT/GLUE REGION %1 *** USER FATAL MESSAGE 4690 4690.14 CONTACT/GLUE REGION %1 IS UNDEFINED *** USER FATAL MESSAGE 4690 4690.15

291 ERROR RETRIEVING INTEGRATION POINT DATA *** USER FATAL MESSAGE 4690 4690.16 error computing face rotation matrix *** SYSTEM FATAL MESSAGE 4690 4690.17 error computing hitting point x,y,z *** SYSTEM FATAL MESSAGE 4690 4690.18 error computing jacobian determinant at hitting point *** SYSTEM FATAL MESSAGE 4690 4690.19 error creating contact element *** SYSTEM WARNING MESSAGE 4690 4690.20 The gap between glue faces of some elements in gap pair %1 between regions % 2 and %3 seems overly large. The largest values are listed in the table below: *** USER INFORMATION MESSAGE 4690 4690.21 Refinement with glue using shell elements not permitted. Refinement turned off. *** USER INFORMATION MESSAGE 4690 4690.22 No contact elements formed for contact region %1. Check contact definition. You may need to increase the search distance. *** USER INFORMATION MESSAGE 4690 4690.23 Contact pair %1 Region %2 with %3 faces has %4 refined faces %5 refined faces were reset to unrefined *** SYSTEM FATAL MESSAGE 4690 4690.24 Shell element %1 is defined twice in the same region in BSURF data *** SYSTEM WARNING MESSAGE 4690 4690.25 Solid element %1 with face containing grids %2 %3 %4 is defined twice in the same region in BSURFS data *** SYSTEM WARNING MESSAGE 4690 4690.26 Solid element %1 with face containing grids %2 %3 %4 %5 is defined twice in the same region in BSURFS data *** SYSTEM INFORMATION MESSAGE 4690 4690.27 %1 duplicate contact faces removed from the face list *** USER INFORMATION MESSAGE 4690 4690.28 - node element faces is not permitted. Refinement with missing mid efinement turned off. R *** USER INFORMATION MESSAGE 4690 4690.29 Using CSTRAT=1 in the BCTPARM card may avoid all elements from becoming inactive. *** USER WARNING MESSAGE 4690 4690.30 USER SPECIFIED A VALUE FOR NCHG EXCEEDS 0.1. THIS HIGH

292 VALUE OF NCHG (> 10%) COULD AFFECT THE CONVERGENCE AND IN TURN THE ACCURACY OF THE CONTACT SOLUTION. *** USER WARNING MESSAGE 4690 4690.31 USER HAS SPECIFIED PENTYP=2 BUT THE VALUES OF PENN AN D/OR PENT APPEAR TO BE LOW FOR CONTACT SET %1. THIS MAY LEAD TO SINGULARITIES IN THE SOLUTION OR PROBLEMS WITH CONVERGENCE. *** USER WARNING MESSAGE 4690 4690.32 USER HAS SPECIFIED PENTYP=2 BUT THE VALUE OF PENN CONTACT SET %1. APPEARS TO BE LOW FOR THIS MAY LEAD TO SINGULARITIES IN THE SOLUTION OR PROBLEMS WITH CONVERGENCE. *** USER WARNING MESSAGE 4690 4690.33 USER HAS SPECIFIED PENTYP=2 BUT THE VALUE OF PENN AND/OR PENT APPEARS TO BE LOW FOR GLUE SET %1. THIS MAY LEAD TO S INGULARITIES IN THE SOLUTION. *** USER INFORMATION MESSAGE 4690 4690.34 USER HAS SELECTED AUTO PENALTY OPTION. NORMAL AND TANGENTIAL PENALTY FACTOR VALUES USED ARE: PENN = %1 PENT = %2 *** USER FATAL MESSAGE 4690 4690.35 RUN TERMINATED BECAUSE NUMBER OF OUTER LOOP ITERATIONS EXCEEDED. CONTACT SOLUTION DID NOT CONVERGE. CONSIDER MODIFYING THE BCTPARM PARAMETERS FOR A POSSIBLE CONVERGED SOLUTION. *** USER FATAL MESSAGE 4690 4690.36 USER HAS SPECIFIED A PENGLUE VALU E LESS THAN ZERO FOR GLUE SET %1. THIS MAY LEAD TO SINGULARITIES IN THE SOLUTION. *** USER FATAL MESSAGE 4690 4690.37 LINEAR CONTACT DOES NOT SUPPORT INERTIA RELIEF. *** USER FATAL MESSAGE 4690 4690.38 CONTACT SET ID %1 IS REFERENCED BY BOTH BCTSET AND BCTADD CARDS. CONTACT SET ID NEEDS TO BE UNIQUE BETWEEN THE TWO CARDS. *** USER FATAL MESSAGE 4690 4690.39 GLUE SET ID %1 IS REFERENCED BY BOTH BGSET AND BGADD CARDS.

293 GLUE SET ID NEEDS TO BE UNIQ UE BETWEEN THE TWO CARDS. *** SYSTEM WARNING MESSAGE 4690 4690.40 Could not compute penalty factor. Penauto option if selected will be ignored. PENN = 10.0 and PENT = 1.0 will be used. *** SYSTEM WARNING MESSAGE 4690 4690.41 COULD NOT RETRIEVE THE MATERIAL ID FOR AN ELEMENT. AVERAGE MODULUS VALUE WILL BE USED FOR CONTACT PAIR %1. *** SYSTEM WARNING MESSAGE 4690 4690.42 COULD NOT FIND THE ELASTICITY MODULUS FOR AN ELEMENT.AVERAGE MODULUS VALUE WILL BE USED FOR AIR %1 CONTACT P *** USER FATAL MESSAGE 4690 4690.43 ERROR ENCOUNTERED WHILE PROCESSING PAIR DATA FOR CONTACT/GLUE SET %1. *** USER FATAL MESSAGE 4690 4690.44 ERROR ENCOUNTERED WHILE PROCESSING PARAMETER DATA FOR CONTACT/GLUE SET %1. *** SYSTEM WARNING MESSAGE 4690 4690.45 ERROR ENCOUNTERED WHILE CALCULATING DEPTH. PENAUTO WILL BE RESET TO 0 FOR CONTACT PAIR %1. *** USER FATAL MESSAGE 4690 4690.46 NOT ALL ELEMENTS DEFINED BY GLUE REGION %1 ARE ACOUSTIC ELEMENTS PLEASE CHECK INPUT DATA *** USER FATAL MESSAGE 4690 4690.47 - ACOUSTIC THE GLUE SET %1 CONTAINS ACOUSTIC AND NON ELEMENTS FOR ACOUSTIC GLUE SET, THE SOURCE AND TARGET REGIONS SHOULD BOTH POINT TO ACOUSTIC ELEMENTS MESSAGE 4690 *** SYSTEM WARNING 4690.48 COULD NOT COMPUTE THE ELASTICITY MODULUS. AVERAGE MODULUS WILL BE USED FOR EACH CONTACT PAIR. *** USER FATAL MESSAGE 4690 4690.49 THE PARAMETER %1 POINTS TO TWO OR MORE BCTPARM PARAMETERS. USE THE FULL PARAMETER NAME INSTEAD TO AVOID ANY ERRORS. *** USER WARNING MESSAGE 4690 4690.50 ONE OR MORE HITTING AND TARGET ELEMENT FACES INCLUDED IN GLUE/CONTACT DEFINITION SHARE COMMON NODES. GLUE/CONTACT STIFFNESS COMPUTED MAY BE DIFFERENT THAN WHEN THE H ITTING AND TARGET FACES DO NOT SHARE

294 ANY COMMON NODES. *** USER WARNING MESSAGE 4690 4690.51 THE GLOBAL PARAMETER %1 HAS BEEN DEFINED IN A LOCAL %2 CARD WITH A CSID VALUE OF %3. THIS PARAMETER DEFINITION WILL BE IGNORED FOR THIS LOCAL CARD. *** SYSTEM WARNING MESSAGE 4690 4690.52 FOR GLUE ELEMENT ID=%1, THE PROJECTION OF GLUE POINT ONTO THE SURFACE CANNOT BE FOUND OR LIES OUTSIDE THE SURFACE. GLUE STIFFNESS WILL NOT BE FORMED FOR THIS GLUE ELEMENT. *** SYSTEM FATAL MESSAGE 4690 4690.53 ERROR OCCURRED WHILE COMPUTING FREE FACES FOR SOLID ELEMENTS FOR REGION %1. User information: This error might be caused by memory allocation failure. This routine allocates temporary memory over and on top of open core. Redu cing open core memory request might help. Contact SIEMENS PLM for support. *** USER WARNING MESSAGE 4690 4690.54 User has specified PENTYPE=2 but has not entered any values for PENN or PENT. PENAUTO will be used with PENTYP=1 for contact set %1. *** USER FATAL MESSAGE 4690 4690.55 CONTACT/GLUE SET %1 DEFINED ON BCTADD/BGADD CARD %2 DOES NOT HAVE A CORRESPONDING BCTSET/BGSET DEFINITION *** SYSTEM FATAL MESSAGE 4690 4690.56 ERROR ENCOUNTERED WITH SPOINTS AND ITERATIVE SOLVER. USER ACTION: EITHER USE SPARSE SOLVER OR RENUMBER THE SPOINT ID TO A VALUE GREATER THAN THE MAXIMUM GRID ID. *** USER INFORMATION MESSAGE 4690 4690.57 REFINE = 1 is not permitted. Refinement is set to 2. *** USER FATAL MESSAGE 4690 4690.58 NO SOLID ELEMENTS FOUND FOR BCPROPS REGION %1 *** USER WARNING MESSAGE 4690 4690.59 NO SOLID ELEMENTS WITH PID %1 FOUND FOR BCPROPS REGION %2 *** USER WARNING MESSAGE 4690 4690.60 NO SHELL ELEMENTS WITH PID %1 FOUND FOR BCPROP REGION %2 *** USER FATAL MESSAGE 4690 4690.61

295 REGION ID %1 IS REFERENCED BY A BSURF/BSURFS CARD AND A BLSEG CARD. REGION ID HAS TO BE UNIQUE WITH RESPECT TO ALL OTHER BSURF, BSURFS, BCPROP, BCPROPS AND BLSEG ENTRIES. USER FATAL MESSAGE 4690 *** 4690.62 ERROR ENCOUNTERED WHILE PROCESSING A BSURF/BSURFS CARD. *** USER FATAL MESSAGE 4690 4690.63 NODES %1 AND %2 DEFINING AN EDGE SEGMENT ON THE BLSEG CARD DO NOT BELONG TO THE SAME ELEMENT. *** SYSTEM FATAL MESSAGE 4690 4690.64 SHELL NORMAL COULD NOT BE COMPUTED FOR GRID POINT %1 DEFINED ON THE BLSEG CARD. *** USER FATAL MESSAGE 4690 4690.65 NO SURFACES OR EDGES DEFINED FOR CONTACT/GLUE REGION %1 *** SYSTEM FATAL MESSAGE 4690 4690.66 SH ELL THICKNESS COULD NOT BE COMPUTED FOR GRID POINT %1 DEFINED ON THE BLSEG CARD. CHECK TO SEE IF THIS GRID BELONGS TO AN ELEMENT THAT IS PART OF CURRENT SUPERELEMENT. *** USER WARNING MESSAGE 4690 4690.67 ONE OR MORE EDGE SEGMENTS INCLUDED IN GLUE DEFINITION HAVE SHELL OFFSETS - DEFINED. SHELL OFFSETS WILL BE IGNORED IN AN EDGE SURFACE CONNECTION. *** USER WARNING MESSAGE 4690 4690.68 GLUE PAIR ID HAS AN EDGE - SURFACE GLUE CONNECTION IN A HEAT TRANSFE R ANALYSIS. GLUE STIFFNESS WILL NOT BE GENERATED FOR THIS PAIR. *** USER FATAL MESSAGE 4690 4690.69 REGION ID %1 IS REFERENCED BY A BCPROP AND BCPROPS CARD. REGION ID HAS TO BE UNIQUE WITH RESPECT TO ALL OTHER BSURF, BSURFS, BCPROP, BCPROPS AND BLSEG ENTRIES. *** USER FATAL MESSAGE 4690 4690.70 REGION ID %1 IS REFERENCED BY A BLSEG CARD AND

296 BCPROP/BCPROPS CARD. REGION ID HAS TO BE UNIQUE WITH RESPECT TO ALL OTHER BSURF, BSURFS, BCPROP, BCPROPS AND BLSEG ENTRIES. *** USER FATAL MESSAGE 4690 4690.71 ERROR ENCOUNTERED WHILE PROCESSING A BLSEG CARD. *** USER FATAL MESSAGE 4690 4690.72 ERROR ENCOUNTERED WHILE PROCESSING A BCPROPS/BCPROP CARD. *** USER WARNING MESSAGE 4690 4690.73 MISSING OR ZERO SEARCH DISTANCE VALUE ENTERED FOR GLUE PAIR %1. DEFAULT SEARCH DISTANCE VALUE OF 10.0 COULD BE TOO LARGE. IT IS POSSIBLE UNINTENDED SURFACES COULD GET GLUED TOGETHER. CHECK THE GAP SUMMARY TABLE IF PRINTED FOR LARGE GAPS BETWEEN HITTING AND TARGET FACES THAT ARE GLUED TOGETHER. *** USER FATAL MESSAGE 4690 4690.74 NON - UNIQUE REGION ID FOUND. REGIONS IDS IN CONTACT AND GLUE SHOULD BE UNIQUE BETWEEN BSURF, BSURFS, BCPROP, BCPROPS AND BLSEG ENTRIES. USER FATAL MESSAGE 4690 *** 4690.75 GRID POINT %1 USED IN EDGE - SURFACE GLUE DEFINITION IS NOT A PART OF A SHELL GRID. *** USER WARNING MESSAGE 4690 4690.76 ONE OR MORE FACES INCLUDED IN GLUE DEFINITION HAS SHELL OFFSETS SPECIFIED. SHELL OFFSETS WILL BE IGNO RED IN A GLUE CONNECTION. *** USER WARNING MESSAGE 4690 4690.77 WHEN REQUESTING ASET REDUCTION IN LINEAR CONTACT, THE SAME CONTACT SET MUST BE SPECIFIED IN EACH SUBCASE. THE SPC, MPC AND BGSET SETS MUST ALSO BE THE SAME IN ALL SUBCASES. PRELOADED BOLTS ARE NOT PERMITTED. THE SOLUTION WILL CONTINUE WITHOUT ASET REDUCTION. *** USER FATAL MESSAGE 4690 4690.78 CONTACT/GLUE ENCOUNTERED INTERNAL ERROR %1. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT.

297 SYSTEM FATAL MESSAGE 4690 *** 4690.79 ERROR CALCULATING GRID NORMALS FOR A FACE or EDGE SEGMENT. *** USER FATAL MESSAGE 4690 4690.80 INVALID EDGE DEFINITION REGION SPECIFIED FOR REGION ID %1. *** USER WARNING MESSAGE 4690 4690.81 NO EDGE SEGMENTS FOUND FOR REGION ID %1. *** USER WARNING MESSAGE 4690 4690.82 ASET REDUCTION IN LINEAR CONTACT IS ONLY AVAILABLE IN SOLUTION 101. SOLUTION WILL CONTINUE WITHOUT ASET REDUCTION. *** USER WARNING MESSAGE 4690 4690.83 ASET RE DUCTION IN LINEAR CONTACT USING THE PARAMETER CNTASET IS NOT AVAILABLE IF THE USER HAS SPECIFIED ASET/ASET1 ENTRIES. SOLUTION WILL CONTINUE WITHOUT CONTACT ASET REDUCTION. *** USER INFORMATIONAL MESSAGE 4690 4690.84 AUTO INERTIA RELIEF(INREL= - 2) MAY RESULT IN ALL CONTACT ELEMENTS BECOMING INACTIVE SINCE THE INITIAL GEOMETRY OF THE SOURCE AND TARGET ENDS OF THE ACTIVE CONTACT ELEMENTS ARE NOT IN CLOSE PROXIMITY TO EACH OTHER. THE DISTANCE BETWEEN THE SOURCE AND TARGE T LOCATIONS OF THE ACTIVE CONTACT ELEMENTS EXCEEDS THAT ALLOWED BY SMALL DISPLACEMENT THEORY. CONSIDER ADJUSTING THE GRID LOCATIONS OF THE MODEL IN THE AREA WHERE ACTIVE CONTACT IS OCCURRING. *** USER FATAL MESSAGE 4690 4690.85 ITION REGION SPECIFIED FOR ELEMENT ID INVALID EDGE DEFIN %1 IN REGION ID %2. *** USER WARNING MESSAGE 4690 4690.86 Element %1 is defined more than once in the same region in BEDGE data *** USER INFORMATION MESSAGE 4690 4690.87 %1 duplicate edges removed from the edge list *** USER WARNING MESSAGE 4690 4690.88 - EDGE GLUE CONNECTION IS NOT SUPPORTED IN A HEAT EDGE TRANSFER ANALYSIS. GLUE STIFFNESS WILL NOT BE GENERATED FOR GLUE PAIR %1. E 4690 *** USER FATAL MESSAG 4690.89 EDGE - EDGE CONTACT DEFINED IN PAIR %1 IS NOT SUPPORTED FOR SHELL ELEMENT

298 TYPES SUCH AS CQUAD4, CQUAD8, CTRIA3, CTRIA6, CQUADR AND CTRIAR. *** USER FATAL MESSAGE 4690 4690.90 EDGE SURFACE CONTACT DEFINED IN PAIR %1 IS CURRENTLY - NOT SUPPORTED. *** USER FATAL MESSAGE 4690 4690.91 SYMMETRIC SOLIDS, PLANE STRESS AND PLANE STRAIN AXI - ELEMENTS DEFINED IN CONTACT/GLUE PAIR %1 ARE CURRENTLY NOT SUPPORTED IN Y - Z PLANE. *** USER WARNING MESSAGE 4690 469 0.92 LARGE PENETRATIONS DETECTED IN CONTACT PAIR %1. ENSURE THAT THE MODEL IS SUFFICIENTLY CONSTRAINED. *** USER FATAL MESSAGE 4690 4690.93 CYCAXIS CARD NOT FOUND. FOR A SOL401 CYCLIC SYMMETRY IS NEEDED TO DEFINE GLOBAL ANALYSIS, CYCAXIS CARD CYCLIC ANALYSIS AXIS. *** USER INFORMATION MESSAGE 4690 4690.94 The Contact Average Normal option AVGNORM is turned OFF due to use of the legacy contact search algorithm. Define SYSTEM(499)=1 to use the current contact search algorithm or DO NOT specify SYSTEM(499). *** USER INFORMATION MESSAGE 4690 4690.95 SINGLE POINT CONSTRAINT CONDITION DEFINED FOR FOLLOWING CYCLIC TARGET NODES ON %1 SET WILL BE IGNORED FOR CYCLIC ANALYSIS. NODE ID %1 SET ID *** USER INFORMATION MESSAGE 4690 (CYC_MPC) 4690.96 SPC CONSTRAINTS ADDED FOR HARMONIC %1 FOR SHARED NODES BETWEEN CYCLIC SOURCE AND TARGET FACE: NODE ID DOF'S CONSTRAINED *** USER FATAL MESSAGE 4690 4690.97 NO MPC RELATIONSHIPS FORMED FOR THE CYCSET RE GIONS. PLEASE CHECK THE CYCSET AND CYCAXIS CARD TO ENSURE ACCURACY OF REGION INFORMATION. *** USER FATAL MESSAGE 4690 4690.98 COORDINATE SYSTEM %1 SPECIFIED ON %2 CARD IS NOT DEFINED ON ANY CORD2C CARD. *** USER FATAL MESSAGE 4690 4690.99 COORDINATE SYSTEM %1 SPECIFIED ON %2 CARD ISNOT DEFINED AS A CYLINDRICAL COORDINATE SYSTEM. FOR CYCLIC

299 ANALYSIS, THE COORDINATE SYSTEMS DEFINED ON EITHER CYCAXIS OR CYCSET CARD ARE REQUIRED TO BE CYLINDRICAL. *** USER FATAL MESSAGE 4691 4691.0 ERR OR IN CHBDY CARD%1 THE FIRST TWO GRID POINTS MUST DETERMINE A LINE IN THE X - Z PLANE WHICH IS NOT PARALLEL TO THE X AXIS. THE X COORDINATES MUST BOTH BE POSITIVE. User information: This error may also occur if the REV option is used for TYPE on the CHBD Y Bulk Data entry, and the IVIEW field is not blank. Set IVIEW (Field 9). *** USER FATAL MESSAGE 4692 4692.0 THE TABLE %1 IS REQUIRED IN A RANDOM ANALYSIS *** SYSTEM FATAL MESSAGE 4692 4692.1 DATABASE ERROR WHILE READING DATA BLOCK %1 *** USER FATAL MESSAGE 4692 4692.2 INSUFFICENT MEMORY ALLOCATED FOR THE RANDOM ANALYSIS *** USER WARNING MESSAGE 4692, 4692.3 AN XY - OUTPUT REQUEST FOR POINT OR ELEMENT ID%1 - %2 CURVE IS BEING PASSED OVER. THE ID COULD NOT BE - FOUND IN DATA BLOCK%3 *** SYSTEM WARNING MESSAGE 4692, 4692.4 EOF ENCOUNTERED WHILE READING DATA BLOCK %1 IN SUBROUTINE RAND2 User Information: This warning is usually a good indication that an invalid node or element id was specified on the XYPLOT and/or XYPUNCH cards. Investigate the output requests. *** USER WARNING MESSAGE 4692 4692.5 NO RANDPS BULK DATA ENTRY REFERENCED BY CASE CONTROL RANDOM %1 FOR THIS DATA RECOVERY PASS. information: User A RANDOM Case Control entry is attempting to reference RANDPS Bulk Data entries which do not exist. This may be OK if this is a multiple subcase analysis and the current data recovery pass does not generate random results. *** USER WARNING MESSAGE 4693 4693.1 AVERAGE MODULUS COULD NOT BE COMPUTED AS MATRIX/TABLE %1 COULD NOT BE LOCATED OR DOES NOT EXIST.

300 A VALUE OF 1.0E+12 WILL BE USED INSTEAD. THIS VALUE CAN BE OVER WRITTEN BY SYSTEM CELL 687. *** USER WARNING MESS AGE 4693 4693.2 FRICTION IS CURRENTLY NOT SUPPORTED BY INTERFACE TYPE=5. COEFFICIENT OF FRICTION WILL BE RESET TO 0.0. *** USER WARNING MESSAGE 4693 4693.3 GLUE FORMULATION FOR LINEAR SOLIDS COULD RESULT IN OVERLY STIFF BEHAVIOR IN BENDING. PLEASE REVIEW THE RESULTS FOR ACCURACY. THE FOLLOWING APPROACHES CAN BE USED AS A WORK AROUND IN THIS CASE. 1. TURN OFF REFINEMENT AND USE INTORD=1. 2. USE PARABOLIC SOLIDS IN THE VICINITY OF THE GLUE. 3. SURFACE COAT THE LINEAR SOLID ELEMENT FACES WITH SHELLS AND DEFINE GLUE BETWEEN SHELL REGIONS. ***USER FATAL MESSAGE 4696, 4696.0 MODE ACCELERATION RECOVERY REQUESTED BUT LLL MATRIX NOT AVAILABLE. ***USER FATAL MESSAGE 4696, 4696.1 MODE ACCELERATION RECOVERY REQUESTED BUT UHF MATRIX NOT AVAILABLE. ***USER FATAL MESSAGE 4696, 4696.2 MODE ACCELERATION RECOVERY REQUESTED BUT KHH MATRIX NOT AVAILABLE. ***USER FATAL MESSAGE 4696, 4696.3 MODE ACCELERATION RECOVERY REQUESTED BUT MHH MATRIX NOT AVAILABLE. ***USER FATAL MESSAGE 4696, 4696.4 MODE ACCELERATION RECOVERY REQUESTED BUT PHDHF MATRIX NOT AVAILABLE. ***USER FATAL MESSAGE 4696, 4696.5 MODE ACCELERATION RECOVERY REQUESTED BUT UD1 OUTPUT MATRIX NOT AVAILABLE. *** USER FATAL MESSAGE 4697 (XSBFF) 4697.0 THE BELOW BULK DATA FREE FIELD ENTRY HAS MORE THAN TEN FIELDS SPECIFIED. (ENTRY IGNORED). %1 User information: A free field Bulk Data entry had more than ten fields specified. Only ten fields are allowed on a free field Bulk Data entry. *** USER WARNING MESSAGE 4698. 4698.0 STATISTICS FOR DECOMPOSITION OF MATRIX %1. THE FOLLOWING DEGREES OF FREEDOM HAVE FACTOR

301 DIAGONAL RATIOS GREATER THAN %2 OR HAVE NEGATIVE TERMS ON THE FACTOR DIAGONAL. USER INFORMATION: THIS MESSAGE MAY BE IGNORED IF NO GRID POINT IDS OR HIGH RATIO MESSAGES APPEAR IN THE TABLE ON THE NEXT PAGE. User information: During decomposition, the degrees of freedom listed have pivot ratios that are that are greater than maxratio or are negative. dom are not part of a mechanism Verify that the degrees of free and that elements do not have excessive stiffness. In superelement analysis this condition causes run termination. PARAM,BAILOUT may be used to continue the run. See the NX NASTRAN Numerical Methods User's Guide. *** USER WARNING MESSAGE 4699 (XSBFF) 99.0 46 THE FREE FIELD BULK DATA ENTRY BELOW HAS A REAL FIELD WITH MORE THAN 8 CHARACTERS. SOME PRECISION MAY BE LOST. %1 User information: The Bulk Data entry replicator reads the first eight fields of an entry, then discards any that may remain. This may lead to unintended results. Check all entries generated by the replicator if this message appears. *** USER FATAL MESSAGE 5000 (EFD2D) 5000.0 NEGATIVE OR ZERO RADIUS DETECTED FOR CFLUID2 ELEMENT %1 *** USER FATAL MESSAGE 5001 (EFD3D) 5001.0 NEGATIVE OR ZERO RADIUS DETECTED FOR CFLUID3 OR CFLUID4 ELEMENT %1 *** USER FATAL MESSAGE 5002 (EFD4D) 5002.0 INTERIOR ANGLE GREATER THAN OR EQUAL TO 180 DEGREES FOR ELEMENT %1 *** USER FATAL MESSAGE 5003 (TA1BND) 5003.0 THE BEND RADIUS RB IS A NEGATIVE NUMBER CREATING ILLEGAL GEOMETRY FOR ELEMENT = %1 User information: nt has been improperly specified The orientation of the CBEND eleme (see the remarks on the CBEND entry). Correct the CBEND element geometric or orientation vector data. *** USER FATAL MESSAGE 5004 (TA1BND) 5004.0 THE ARC SUBTENDED BY THE BEND ELEMENT = %1 HAS EXCEEDED AN ARC OF 1 80 DEGREES. User information: The orientation of the CBEND element has been improperly specified

302 (see the remarks on the CBEND entry). Correct the CBEND element geometric or orientation vector data. *** USER FATAL MESSAGE 5005 (APPEND) 5005.0 INVALID VALUE OF OPTION PARAMETER DETECTED %1 User information: The user, in calling a module, has specified an option that does not exist. Change the option parameter in the DMAP statement. *** USER FATAL MESSAGE 5006 (APPEND) 5006.0 S HAVE DIFFERENT RECORD TYPES INPUT FILE User information: One of the input files was a matrix and the other was not. *** USER FATAL MESSAGE 5007 5007.0 INPUT MATRICES ARE OF DIFFERENT DATA TYPES User information: ta types, e.g., one contains The matrices involved are of different da real data and another contains integer data. *** USER FATAL MESSAGE 5007 5007.1 INPUT MATRICES ARE OF DIFFERENT DATA TYPES. THIS MAY BE CAUSED BY USING THE AUTOMATIC MODEL PARTITIONER FOR A VERY SMALL MODEL. USER ACTION: IF THE MODEL HAS LESS THAN 100 GRID POINTS, PLEASE REMOVE DMP FROM THE SUBMITTAL LINE. User information: The matrices involved are of different data types, e.g., one contains real data and another contains integer data. *** US ER FATAL MESSAGE 5008 5008.0 THE INPUT MATRICES HAVE DIFFERENT NUMBERS OF ROWS User information: One of the input matrices has a larger number of rows than the other(s), thereby preventing the requested matrix calculation. *** USER FATAL MESSAGE 5009 5009.0 IN CALL TO %1, UGX MATRIX OF WRONG SIZE User information: The number of columns in the UGX matrix is not evenly divisible by the number of columns in the UG matrix. As a result, the UGX matrix cannot be divided into submatrices for the DSVG3 rou tine. Check the generation sequence for the UGX matrix. *** USER INFORMATION MESSAGE 5010 5010.0 STURM SEQUENCE DATA FOR EIGENVALUE EXTRACTION. TRIAL EIGENVALUE = %1, CYCLES = %2 NUMBER OF EIGENVALUES BELOW THIS VALUE = %3 User information: This message is automatic output during eigenvalue extraction. This can be used, along with the list of eigenvalues, to identify the modes

303 found. See the NX NASTRAN Numerical Methods User's Guide. *** USER FATAL MESSAGE 5018 5018.0 STA MODULE TERMINATED - ECT PURGED D *** USER FATAL MESSAGE 5019 5019.0 DSTA MODULE TERMINATED EPT PURGED - *** USER FATAL MESSAGE 5020 5020.0 DSTA MODULE TERMINATED - EST PURGED *** USER FATAL MESSAGE 5021 5021.0 - CASECC PURGED DSTA MODULE TERMINATED *** USER FATAL MESSAGE 5022 5022.0 - DSTA MODULE TERMINATED EDT PURGED *** USER FATAL MESSAGE 5024 5024.0 - DSTA MODULE TERMINATED UGV PURGED *** USER FATAL MESSAGE 5025 5025.0 - LAMA PURGED DSTA MODULE TERMINATED User information: The LAMA data block contains a list of natural frequencies and may be purged because no eigenvalues were computed or the data block was not properly recovered on restart. *** USER FATAL MESSAGE 5026 5026.0 XCASECC PURGED DSTA MODULE TERMINATED - *** USER FATAL MESSAGE 5028 5028.0 -- DSTA MODULE PRELOC UNABLE TO OPEN EDT TABLE TERMINATED IN DSTA User information: Send run to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 5029 5029.0 ** NO DSCONS CARDS ON EDT TABLE ** DSTA MODULE TERMINATED IN DSTA System information: Required user data. Check bulk data input. *** SYSTEM FATAL MESSAGE 5030 5030.0 ** NO DVAR CARDS ON EDT TABLE ** DSTA MODULE TERMINATED IN DSTA *** SYSTEM FATAL MESSAGE 5031 5031.0 ** NO DVSET CARDS ON EDT TABLE ** DSTA MODULE TERMINATED IN DSTA ***SYSTEM FATAL MESSAGE 5032 5032.0 NOT ENOUGH OPEN CORE FOR DSCONS PROCES SING --- DSTA MODULE TERMINATED IN DSTA System information: Increase Region. Memory requirements for DSTA module are discussed in

304 Section 15.9. *** SYSTEM FATAL MESSAGE 5033 5033.0 DSTA NOT ENOUGH OPEN CORE FOR DVAR PROCESSING --- MODULE TERMINATED IN DSTA *** SYSTEM FATAL MESSAGE 5034 5034.0 DSTA UNEXPECTED EOR READING DVAR CARDS OFF EDT --- MODULE TERMINATED IN DSTA System information: Send run to SIEMENS PLM SOFTWARE CUST OMER SUPPORT. *** SYSTEM FATAL MESSAGE 5035 5035.0 NOT ENOUGH OPEN CORE FOR DVAR PROCESSING*** DSTA MODULE TERMINATED IN DSTA System information: Increase Region. Memory requirements for DSTA module are discussed in Section 15.9. *** SYSTEM FATAL MESSAGE 5036 5036.0 NOT ENOUGH OPEN CORE FOR DVSET PROCESSING DSTA MODULE TERMINATED IN DSTA System information: Increase Region. Memory requirements for DSTA module are discussed in Section 15.9. *** SYSTEM FATAL MESSAGE 5037 5037.0 DSTA UNEXPECTED EOR READING DVSET CARDS OFF EDT -- MODULE TERMINATED IN DSTA System information: Increase Region. Memory requirements for DSTA module are discussed in Section 15.9. *** SYSTEM FATAL MESSAGE 5038 5038.0 ET PROCESSING*** DSTA NOT ENOUGH OPEN CORE FOR DVS MODULE TERMINATED IN DSTA System information: Increase Region. Memory requirements for DSTA module are discussed in Section 15.9. *** SYSTEM FATAL MESSAGE 5039 5039.0 UNEXPECTED EOR READING CASECC DSTA MODULE TERMINATED IN DSTA System information: Increase Region. Memory requirements for DSTA module are discussed in Section 15.9. *** SYSTEM FATAL MESSAGE 5041 5041.0 NOT ENOUGH OPEN CORE FOR TABLE 4 -- DSTA MO DULE TERMINATED IN DSTA11 System information: Increase Region. Memory requirements for DSTA module are discussed in

305 Section 15.9. *** SYSTEM FATAL MESSAGE 5042 5042.0 DVAR ID=%1 NOT FOUND CODING LOGIC ERROR DSTA -- -- MODULE TERMINATED IN DSTA11 ystem information: S Required user data. Check bulk data input. *** SYSTEM FATAL MESSAGE 5043 5043.0 NOT ENOUGH OPEN CORE FOR TABLE 2 -- DSTA MODULE TERMINATED IN DSTA11 System information: Increase Region. Memory requirements for DSTA module are discussed in Section 15.9. *** SYSTEM FATAL MESSAGE 5044 5044.0 -- -- DSTA CODING LOGIC ERROR DSCONS ID= %1 NOT FOUND MODULE TERMINATED IN DSTA11 System information: equirements for DSTA module are discussed in Increase Region. Memory r Section 15.9. *** SYSTEM FATAL MESSAGE 5045 5045.0 NOT ENOUGH OPEN CORE TO HOLD DSCONS POINTERS DSTA MODULE TERMINATES IN DSTA13 System information: e are discussed in Increase Region. Memory requirements for DSTA modul Section 15.9. *** SYSTEM FATAL MESSAGE 5046 5046.0 UNEXPECTED EOR WHILE READING SCR1 DSTA MODULE TERMINATED IN DSTA13 System information: Send run to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 5047 5047.0 UNEXPECTED EOR READING SCR1 DSTA MODULE TERMINATED IN DSTA13 System information: Send run to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER WARNING MESSAGE 5048 5048.0 TABLE 9 DOES NOT CONTAIN AN ENTRY FOR EID %1 THIS MEANS THAT A DSCONS CARD POINTS TO A NON - EXISTANT EID DSTA MODULE IS IN ROUTINE DSTA13 TABLE 9 DOES NOT CONTAIN AN ENTRY FOR EID %1 User information: Element referenced is not in model. *** SYSTEM FATAL MESSAGE 5049 5049.0 DSCONS CARD WITH ID OF %1 HAS INVALID TYPE= %2

306 FOR STATICS ONLY DISP, STRESS, OR FORCE ALLOWED -- DSTA MODULE TERMINATED IN DSTA13 User information: Use input error. ***SYSTEM FATAL MESSAGE 5050 5050.0 DSCONS CARD WITH ID OF %1 HAS INVALID TYPE= %2 = %3 DSTA FOR STATICS ONLY DISP, STRESS, OR FORCE ALLOWED -- MODULE TERMINATED IN DSTA13 ***USER WARNING MESSAGE 5051 5051.0 TABLE 9 DOES NOT CONTAIN AN ENTRY FOR EID %1 - THIS MEANS THAT A DSCONS ENTRY REFERENCES A NON EXISTENT EID DSTA MODULE IS IN ROUTINE DSTA13 ***USER WARNING MESSAGE 5052 5052.0 TABLE 9 CONTAINS THE IBID=IBID ENTRY FOR ID %1 BUT NOT THE IBID=0, MUST BE CODING LOGIC ERROR DSTA MODULE IS IN ROUTINE DSTA13 User information: Send run to SIEMENS PLM SOFTWAR E CUSTOMER SUPPORT. ***SYSTEM FATAL MESSAGE 5054 5054.0 NOT ENOUGH OPEN CORE TO HOLD DSCONS POINTERS DSTA MODULE TERMINATED IN DSTA14 System information: Increase Region. Memory requirements for DSTA module are discussed in Section 15.9. ***SYSTEM FATAL MESSAGE 5055 50 55.0 NOT ENOUGH OPEN CORE TO HOLD DVAR POINTERS DSTA MODULE TERMINATED IN DSTA14 System information: Increase Region. Memory requirements for DSTA module are discussed in Section 15.9. ***SYSTEM FATAL MESSAGE 5056 5056.0 UNEXPECTED EOR WHILE READING A DSCONS CARD DSTA MODULE TERMINATED IN DSTA14 System information: Send run to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. ***USER WARNING MESSAGE 5057 5057.0 IBID= 0 ENTRY NOT FOUND FOR EID= %1 IN TABLE 9 THIS MEANS A DSCONS CARD REFERENCES NON - EXISTENT EID - DSTA MODULE IS IN ROUTINE DSTA14 User information: Element referenced is not in model. ***SYSTEM FATAL MESSAGE 5059 5059.0 UNEXPECTED EOR WHILE READING A DVAR CARD DSTA

307 MODULE TERMINATED IN DSTA14 System information: Send run to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. ***SYSTEM FATAL MESSAGE 5061 5061.0 NOT ENOUGH OPEN CORE TO HOLD 2 * NO. OF DSCONS + 3 * NO. OF DVARS NDSCON= %1DVAR= %2BIDTOT= %3BUF5= %4 DSTA MODULE TERMINATED IN DSTA14 System information: Increase Region. Memory requirements for DSTA module are discussed in Section 15.9. ***SYSTEM FATAL MESSAGE 5062 5062.0 ER TABLE 2(SCR2) HAS CODING LOGIC ERROR, DSCONS POINT MORE DSCONS IDS THAN TABLE 11(SCR8) CURRENT DSCONS ID FROM TABLE2 = %1 DSTA MODULE TERMINATED IN DSTA14 System information: Required user data. Check bulk data input. ***SYSTEM FATAL MESSAGE 5064 5064.0 DSCONS ID DOES NOT MATCH MODE ID FOUND IN LAMA TABLE PTER= %1D= %2 Z(PTER)= %3 TB9BEG= %4NWDLA= %5 LAMA RECORD NO. 2 %6 %7 DSTA MODULE TERMINATED IN DSTA14 ***SYSTEM FATAL MESSAGE 5065 5065.0 UNEXPECTED END OF FILE READING LAMA TABLE DSTA MODU LE TERMINATED IN DSTA14 System information: Send run to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. ***SYSTEM FATAL MESSAGE 5066 5066.0 TYPE= %1 ON DSCONS CARD INVALID DSTA MODULE TERMINATED IN DSTA14 System information: User input error. ***SYSTEM FATAL MESSAGE 5067 5067.0 UNEXPECTED EOR WHILE READING DSCONS CARDS DSTA MODULE TERMINATED IN DSTA18 System information: Send run to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. ***SYSTEM FATAL MESSAGE 5068 5068.0 NOT ENOUGH OPEN CORE TO H OLD 4* # OF MODE NUMBERS ---- #MODE NUMBERS= %1 - DSTA MODULE TERMINATED IN DSTA18 ***SYSTEM FATAL MESSAGE 5069 5069.0 NUMBER OF OPEN CORE WORDS= %1 NOT ENOUGH TO HOLD ONE

308 CASE CONTROL RECORD -- DSTA MODULE TERMINATED IN DSTA1A System information: crease Region. Memory requirements for DSTA module are discussed in In Section 15.9. ***SYSTEM FATAL MESSAGE 5070 5070.0 SET2 CARD ID= %1 NOT FOUND IN CASE CONTROL DSTA MODULE TERMINATED IN DSTA1A -- System information: Required user data. Check bulk data input. ***USER WARNING MESSAGE 5071 5071.0 SET ID %1 REFERENCED ON SET2 CARD NOT FOUND IN CASE -- CONTROL DSTA MODULE IS IN DSTA1B User information: Required user data. Check bulk data input. ***SYS TEM FATAL MESSAGE 5072 5072.0 -- DSTA MODULE NOT ENOUGH OPEN CORE TO HOLD DSCONS ID'S TERMINATED IN DSTA1B System information: Increase Region. Memory requirements for DSTA module are discussed in Section 15.9. ***SYSTEM FATAL MESSAGE 5073 5073.0 NOT ENOUGH OPEN CORE TO HOLD TABLE 4 POINTERS FOR DVAR CARDS MODULE DSTA TERMINATED IN DSTA1D --- System information: Increase Region. Memory requirements for DSTA module are discussed in Section 15.9. ***SYSTEM FATAL MESSAGE 5074 5074.0 UGH OPEN CORE TO HOLD TABLE 2 POINTERS FOR NOT ENO DSCONS CARDS MODULE DSTA TERMINATED IN DSTA1D --- System information: Increase Region. Memory requirements for DSTA module are discussed in Section 15.9. ***SYSTEM FATAL MESSAGE 5075 5075.0 --- MODULE DSTA NO OPEN CORE LEFT TO PROCESS TABLE 1 TERMINATED IN DSTA1D System information: Increase Region. Memory requirements for DSTA module are discussed in Section 15.9. ***SYSTEM FATAL MESSAGE 5076 5076.0 NOT ENOUGH OPEN CORE TO HOLD DSCONS POINTER TABLE DSTA MODULE TERMINATED IN DSTA1E

309 System information: Increase Region. Memory requirements for DSTA module are discussed in Section 15.9. ***SYSTEM FATAL MESSAGE 5077 5077.0 NOT ENOUGH OPEN CORE T O HOLD DSCONS POINTER TABLE DSTA MODULE TERMINATED IN DSTA3 System information: Increase Region. Memory requirements for DSTA module are discussed in Section 15.9. ***SYSTEM FATAL MESSAGE 5078 5078.0 NOT ENOUGH OPEN CORE TO HOLD TABLE 3 - DSTA MODULE TERMINATED IN DSTA3 System information: Increase Region. Memory requirements for DSTA module are discussed in Section 15.9. ***SYSTEM FATAL MESSAGE 5079 5079.0 NOT ENOUGH OPEN CORE TO HOLD DVAR POINTER TABLE DSTA MODULE TERMINATED IN DSTA5 System information: Increase Region. Memory requirements for DSTA module are discussed in Section 15.9. ***SYSTEM FATAL MESSAGE 5080 5080.0 NOT ENOUGH OPEN CORE TO HOLD DVSET POINTER TABLE DSTA MODUL E TERMINATED IN DSTA5 System information: Increase Region. Memory requirements for DSTA module are discussed in Section 15.9. ***SYSTEM FATAL MESSAGE 5081 5081.0 -- NOT ENOUGH OPEN CORE TO HOLD DVAR CARD DSTA MODULE TERMINATED IN DSTA5 System information: Increase Region. Memory requirements for DSTA module are discussed in Section 15.9. ***SYSTEM FATAL MESSAGE 5082 5082.0 -- NOT ENOUGH OPEN CORE TO HOLD DVSET ENTRY FOR ONE VID DSTA MODULE TERMINATED IN DSTA5 : System information Increase Region. Memory requirements for DSTA module are discussed in Section 15.9. *** USER FATAL MESSAGE 5083 (DSTA5). 5083.0 A DVAR ENTRY WITH BID OF %1 REFERENCES NON - EXISTENT ENTRY DVSET WITH VID OF %2 User information: Required user dat a. Check Bulk Data input.

310 NOT ENOUGH OPEN CORE TO HOLD TABLE 6 DSTA MODULE 5084.0 TERMINATED IN DSTA6 System information: Increase Region. Memory requirements for DSTA module are discussed in Section 15.9. FATAL MESSAGE 5085 ***SYSTEM 5085.0 CODING LOGIC ERROR, CHECK LENGTH CALCULATION FOR MODULE DSTA TERMINATED IN DSTA7 ---- TABLE 6 System information: Send run to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. ***SYSTEM FATAL MESSAGE 5086 5086.0 OR ECT LOCATE IDS %1 -- MODULE NO MATCH FOUND IN GPTA1 F DSTA TERMINATED IN DSTA7 System information: Send run to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 5086 (DOM2C) 5086.1 NO MATCH FOUND IN GPTA1 FOR ECT LOCATE IDS %1 System information: Send run to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. ***SYSTEM FATAL MESSAGE 5087 5087.0 ECT ENTRY LENGTH FOR ELEMENT TYPE %1 IS %2 --- PROGRAM LIMIT IS 350 -- MODULE DSTA TERMINATED IN DSTA7 System information: MER SUPPORT. Send run to SIEMENS PLM SOFTWARE CUSTO *** SYSTEM FATAL MESSAGE 5087 (DOM2C) 5087.1 ECT ENTRY LENGTH FOR ELEMENT TYPE %1 IS %2 --- PROGRAM LIMIT IS 350 System information: Send run to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. ***SYSTEM FATAL MESSAGE 5088 5088.0 UNEXPECTED EOF WHILE READING ECT TABLE MODULE DSTA TERMINATED IN DSTA7 System information: Send run to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. ***SYSTEM FATAL MESSAGE 5089 5089.0 TABLE 7 LENGTH OF %1 EXCEEDS OPEN CORE OF %2 WORDS -- MODULE DSTA TERMINATED IN DSTA7 System information: Increase Region. Memory requirements for DSTA module are discussed in Section 15.9. ***SYSTEM FATAL MESSAGE 5090 5090.0 NOT ENOUGH OPEN CORE TO HOLD TABLE 8 -- MODULE DSTA TERMINATED IN DSTA8A System information:

311 Increase Region. Memory requirements for DSTA module are discussed in Section 15.9. ***SYSTEM FATAL MESSAGE 5091 5091.0 -- EOF ENCOUNTERED ON EPT DSTA MODULE TERMINATED IN DSTA8B System information: Send run to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. ***SYSTEM FATAL MESSAGE 5093 5093.0 TABLE 5 ENTRY NOT FOUND IN TABLE 8 --- MUST BE PROGRAM -- DSTA MODULE LOGIC ERROR TERMINATED IN DSTA9A USER ACTION: PLEASE SEND THIS RUN TO SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 5093 (DSAB5A) 5093.1 TABLE 1 ENTRY NOT FOUND IN TABLE 4. IT MUST BE PROGRAM LOGIC ERROR. USER ACTION: PLEASE SEND THIS RUN T O SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. System information: Send run to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. ***SYSTEM FATAL MESSAGE 5094 5094.0 NOT ENOUGH OPEN CORE TO HOLD AN EPT ENTRY DSTA MODULE TERMINATED IS DSTA9A System information: Increase Region. Memory requirements for DSTA module are discussed in Section 15.9. ***SYSTEM FATAL MESSAGE 5095 5095.0 NOT ENOUGH OPEN CORE TO HOLD 2 EPT ENTRIES DSTA MODULE TERMINATED IS DSTA9A System information: rements for DSTA module are discussed in Increase Region. Memory requi Section 15.9. ***SYSTEM FATAL MESSAGE 5096 5096.0 NOT ENOUGH OPEN CORE TO HOLD TABLE 7 -- DSTA MDOULE TERMINATED IN DSTA9B System information: ussed in Increase Region. Memory requirements for DSTA module are disc Section 15.9. ***SYSTEM FATAL MESSAGE 5097 5097.0 NOT ENOUGH OPEN CORE TO HOLD TABLE 3 -- DSTA MODULE TERMINATED IN DSTA9B System information: Increase Region. Memory requirements for DSTA module are discussed in Section 15.9. ***SYSTEM FATAL MESSAGE 5098 5098.0

312 NOT ENOUGH OPEN CORE TO HOLD EPT ENTRY -- DSTA MODULE TERMINATED IN DSTA9B System information: Increase Region. Memory requirements for DSTA module are discussed in Section 15.9. ***SYSTEM FATAL MESSAGE 5099 5099.0 UNEXPECTED EOR READING EST TABLE -- DSTA MODULE TERMINATED IN DSTA9B System information: Increase Region. Memory requirements for DSTA module are discussed in Section 15.9. ***SYSTEM FATAL MESSAGE 5100 5100.0 ORE TO HOLD TABLE 13 -- DSTA MODULE NOT ENOUGH OPEN C TERMINATED IN DSTACC System information: Increase Region. Memory requirements for DSTA module are discussed in Section 15.9. ***SYSTEM FATAL MESSAGE 5101 5101.0 --- -- DSTA MODULE TERMINATED IN DSTACC NO OPEN CORE LEFT System information: Increase Region. Memory requirements for DSTA module are discussed in Section 15.9. ***SYSTEM FATAL MESSAGE 5102 5102.0 NOT ENOUGH OPEN CORE TO HOLD DISP SET -- DSTA MODULE TERMINATED IN DSTACC System information: Increase Region. Memory requirements for DSTA module are discussed in Section 15.9. ***SYSTEM FATAL MESSAGE 5103 5103.0 NO OPEN CORE LEFT -- DSTA MODULE TERMINATED IN DSTACC --- System information: Increase Region. Memory requirements for DSTA mo dule are discussed in Section 15.9. ***SYSTEM FATAL MESSAGE 5104 5104.0 -- DSTA MODULE NOT ENOUGH OPEN CORE TO HOLD STRESS SET TERMINATED IN DSTACC System information: Increase Region. Memory requirements for DSTA module are discussed in 15.9. Section ***SYSTEM FATAL MESSAGE 5105 5105.0 CODING LOGIC ERROR TABLE 13 TYPE %1 NOT VALID FOR - STATICS -- DSTA MODULE TERMINATED IN DSTACC System information: Send run to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT.

313 ***SYSTEM FATAL MESSAGE 5106 5106.0 -- NO OPEN CORE LEFT --- DSTA MODULE TERMINATED IN DSTACC System information: Increase Region. Memory requirements for DSTA module are discussed in Section 15.9. ***SYSTEM FATAL MESSAGE 5107 5107.0 FORCE SET -- DSTA MODULE NOT ENOUGH OPEN CORE TO HOLD TERMINATED IN DSTACC System information: Increase Region. Memory requirements for DSTA module are discussed in Section 15.9. ***USER WARNING MESSAGE 5108 5108.0 UGV HAS MORE CONDITIONS THAN CASECC HAS SUBCASES THUS LAST CASECC SUBCASE USED AS MODEL FOR REMAINING CASEDS RECORDS. -- DSTA MODULE EXECUTING IN DSTACC ***SYSTEM FATAL MESSAGE 5109 5109.0 -- DSTA MODULE UNEXPECTED EOR WHILE READING CASECC TERMINATE D IN DSTACC System information: Send run to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. ***SYSTEM FATAL MESSAGE 5110 5110.0 UNEXPECTED EOR WHILE READING DVAR CARDS -- DSTA MODULE TERMINATED IN DSTACO System information: RE CUSTOMER SUPPORT. Send run to SIEMENS PLM SOFTWA ***SYSTEM FATAL MESSAGE 5111 5111.0 -- UNEXPECTED EOR WHILE READING CASECC DSTA MODULE TERMINATED IN DSTACO System information: Send run to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. ***SYSTEM FATAL MESSAGE 5112 5112.0 UNEXPECTED EOF WHILE READING CASECC -- DSTA MODULE TERMINATED IN DSTACO System information: Send run to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. ***SYSTEM FATAL MESSAGE 5113 5113.0 INSUFFICIENT OPEN CORE FOR LIST OF MODE ID'S FROM TABLE 18 -- NUMBER W ORDS AVAILABLE= %1 DSTA MODULE TERMINATED IN DSTAES System information: Increase Region. Memory requirements for DSTA module are discussed in Section 15.9. ***USER FATAL MESSAGE 5114 5114.0

314 PROBLEM LIMITATION OF 66 TEMPERATURE SETS AS BEEN EXCEEDED. DSTA MODULE TERMINATED IN DSTAET -- ***USER FATAL MESSAGE 5114 5114.1 PROBLEM LIMITATION OF 66 TEMPERATURE SETS HAS BEEN EXCEEDED. -- DSTA MODULE TERMINATED IN DSTAEC ***SYST EM FATAL MESSAGE 5115 5115.0 UNEXPECTED END OF RECORD READING TABLE ETT -- DSTA MODULE TERMINATED IN DSTAET System information: Send run to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. ***SYSTEM FATAL MESSAGE 5116 5116.0 TEMPERATURE SET ID. IN DATA RECORD NOT FOUND IN HEADER RECORD TEMP(1)= %1 TLIST(I)= %2 %3 %4 %5 %6 %7 %8 %9 %10 %11 %12 %13 %14 %15 %16 %17 %18 %19 %20 %21 -- DSTA MODULE TERMINATED IN DSTAET System information: Send run to SIEMENS P LM SOFTWARE CUSTOMER SUPPORT. ***SYSTEM FATAL MESSAGE 5117 5117.0 UNEXPECTED END OF RECORD READING TABLE ETT -- DSTA MODULE TERMINATED IN DSTAET System information: Send run to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. ***SYSTEM FATAL M ESSAGE 5118 5118.0

315 UNEXPECTED END OF RECORD READING TABLE ETT -- DSTA MODULE TERMINATED IN DSTAET System information: Send run to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. ***SYSTEM FATAL MESSAGE 5119 5119.0 TEMP SET ID. IN DATA RECORD NOT FOUND IN HEADER RCD. -- DSTA MODULE TERMINATED IN DSTAET System information: Send run to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. ***SYSTEM FATAL MESSAGE 5120 5120.0 UNEXPECTED END OF FILE READING TABLE ETT -- DSTA MOD ULE TERMINATED IN DSTAET System information: Send run to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. ***SYSTEM FATAL MESSAGE 5121 5121.0 DSTA NOT ENOUGH OPEN CORE TO HOLD DSCONS POINTERS -- MODULE TERMINATED IN DSTARO System information: Increase Region. Memory requirements for DSTA module are discussed in Section 15.9. ***SYSTEM FATAL MESSAGE 5122 5122.0 UNEXPECTED EOR WHILE READING DSCONS CARDS -- DSTA MODULE TERMINATED IN DSTARO System information: WARE CUSTOMER SUPPORT. Send run to SIEMENS PLM SOFT ***SYSTEM FATAL MESSAGE 5123 5123.0 NOT ENOUGH OPEN CORE TO HOLD DVAR POINTERS DSTA -- MODULE TERMINATED IN DSTACO System information: Increase Region. Memory requirements for DSTA module are discussed in Section 15.9. ***SYSTEM FATAL MESSAGE 5124 5124.0 NOT ENOUGH OPEN CORE TO HOLD DSCONS POINTERS DSTA MODULE TERMINATED IN DSTA18 System information: Increase Region. Memory requirements for DSTA module are discussed in Section 15.9. ***USER WARNING MESSAGE 5125 5125.0 FIRST NON - ZERO VALUE IN FILE 102 COLUMN= %1 IS IN ROW %2, SHOULD BE IN ROW %3 -- MODULE DSMA CONTINUING *** USER WARNING MESSAGE 5125 5125.1 %1TH NON - ZERO (IN ROW %2 AND COLUMN %3) IGNORED

316 WARNING MESSAGE 5126 ***SYSTEM 5126.0 FILE %1 SUBCASE %2 DOES NOT MATCH FILE DSPT2 SUBCASE %3 DSMA MODULE CHECK YOUR DMAP FOR CORRECT FILE %4 -- TERMINATED ***SYSTEM WARNING MESSAGE 5127 5127.0 FILE 102 GRID ID.%1 DOES NOT MATCH FILE DSPT2 GRID ID.%2 -- DSMA MODULE CHECK YOUR D MAP FOR CORRECT FILE 102 TERMINATED ***SYSTEM WARNING MESSAGE 5129 5129.0 FILE %1 ELEMENT ID. %2 DOES NOT MATCH FILE DSPT2 ELEMENT ID. %3 -- CHECK YOUR DMAP FOR CORRECT FILE %4 DSMA MODULE TERMINATED WARNING MESSAGE 5132 ***SYSTEM 5132.0 UNEXPECTED EOR WHILE READING %1 -- DSMA MODULE TERMINATED System information: Send run to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. ***SYSTEM WARNING MESSAGE 5133 5133.0 UNEXPECTED EOR DURING FWDREC ON %1 DSMA MODULE -- TERMINATE D System information: Send run to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. ***SYSTEM WARNING MESSAGE 5142 5142.0 DSMA MODULE TERMINATED FILE DSPT2 IS PURGED -- ***SYSTEM WARNING MESSAGE 5143 5143.0 -- DSMA MODULE TERMINATED FILE %1 IS PURGED *** USER FATAL MESSAGE 5146 5146.0 IN GPSPEN OF GPSTR1. MUST BE A CODING ERROR, SINCE EMG SHOULD HAVE FOUND GEOMETRY ERROR ELEMENT ID= %1 ***SYSTEM FATAL MESSAGE 5147 5147.0 LOGIC ERROR, READ COUNTER IF1 = 0 -- UTILITY MERGER TERMINATED ***SYSTEM FATAL MESSAGE 5148 5148.0 LOGIC ERROR, READ COUNTER IF2 = 0 -- UTILITY MERGER TERMINATED ***USER WARNING MESSAGE 5149 5149.0 NO PROPERTY ID'S REFERENCED ON DVSET CARDS WERE FOUND IN ELEMENT PROPERTY TABLE (EPT). DSTA MODULE IS IN SUBROUTINE DSTA9A User information: Check property IDs on DVSET entries for valid IDs.

317 ***USER WARNING MESSAGE 5149 (DSAB5A) 5149.1 NO PROPERTY IDS REFERENCED ON DVSET CARDS WERE FOUND IN ELEMENT PROPERTY TABLE EPT. ***USER FATAL MESSAGE 5151 5151.0 IN GPSHEX ROUTINE OF GPSTR1 ,MUST BE A CODING ERROR SINCE GEOMETRY SHOULD HAVE BEEN CHECKED IN EMG ROUTINES FOR HEXA ELEMENT %1 ***USER FATAL MESSAGE 5151 5151.1 IN GPSECS ROUTINE OF GPSTR1 ,MUST BE A CODING ERROR SIN CE GEOMETRY SHOULD HAVE BEEN CHECKED IN EMG ROUTINES %1 ***SYSTEM FATAL MESSAGE 5152 5152.0 -- UNEXPECTED END OF RECORD READING TABLE ETT DSTA MODULE TERMINATED IN DSTAEC System information: Send run to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. ***SYSTEM FATAL MESSAGE 5153 5153.0 TEMPERATURE SET ID. IN DATA RECORD NOT FOUND IN HEADER RECORD TEMP(1)= %1 TLIST(I)= %2 %3 %4 %5 %6 %7 %8 %9 %10 %11 %12 %13 %14 %15 %16 %17 %18 %19 %20 %21 -- DSTA MODULE TERMINATED IN DSTAEC ***SYSTEM FATAL MESSAGE 5154 5154.0 UNEXPECTED END OF RECORD READING TABLE ETT -- DSTA MODULE TERMINATED IN DSTAEC System information:

318 Send run to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. ***SYSTEM FATAL MESSAGE 5155 5155.0 DSTA -- UNEXPECTED END OF RECORD READING TABLE ETT MODULE TERMINATED IN DSTAEC System information: Send run to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. ***SYSTEM FATAL MESSAGE 5156 5156.0 TEMP SET ID. IN DATA RECORD NOT FOUND IN HEADER RCD. -- DSTA M ODULE TERMINATED IN DSTAEC ***SYSTEM FATAL MESSAGE 5157 5157.0 -- DSTA MODULE UNEXPECTED END OF FILE READING TABLE ETT TERMINATED IN DSTAEC *** SYSTEM FATAL MESSAGE 5164 (DSVG1D) 5164.0 DATA BLOCKS %1 AND %2 ARE INCONSISTENT. *** USER FATAL MESSAGE 5165 (DSVGPD) 5165.0 ELEMENT TYPE = %1 (%2) ELEMENT ID = %3 DOES NOT EXIST IN ESTDVF DATA BLOCK *** USER FATAL MESSAGE 5165 (DVSGPD) 5165.1 ELEMENT TYPE = %1 (%2), DOES NOT EXIST IN ESTDVF/ESTDVB DATA BLOCK *** USER FATAL MESSAGE 5165 (DVSGPD) 5165.2 ELEMENT TYPE = %1 (%2) HAS MISS MATCH INFORMATION IN ESTDVF AND ESTDVB DATA BLOCK *** USER FATAL MESSAGE 5172 (DSDJ1D) 5172.0 THE VARIATIONAL ELEMENT ID IN %1 INCONSISTENT WITH THE IN %2, MODULE DSVG1 IS VARIATIONAL ELEMENT ID TERMINATED. User information: Inconsistent variational element ID between XKDICT and DSPT1 data sets. Check XKDICT and DSPT1 data blocks. Send run to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER WARNING MESSAGE 51 74 (DSVG1D) 5174.0 FOR MODE NUMBER %1 GENERALIZED MASS IS EQUAL TO ZERO. THE CORRESPONDING DESIGN SENSITIVITY GRADIENTS SET TO ZERO. *** USER FATAL MESSAGE 5181. (NLSL3D) 5181.0 ELEMENT WITH ID = %1 HAS A GRID POINT OPPOSITE TO THOSE OF A FACE RECEIVING A PRESSURE LOAD WHICH IS EVIDENTLY IN THE SAME PLANE AS THIS FACE. User information: The solid element is so distorted that it is impossible to find the inward direction for pr essure loads. This can happen with incorrect grid geometry, or excessive deflections with geometric nonlinear option.

319 Fix model or reduce load increments. *** USER FATAL MESSAGE 5182. (NLSL3D) 5182.0 ELEMENT ID = %1 CID =%2, N1, N2, N3 =%3 LOAD DIRECTION VECTOR WHEN TRANSFORMED TO BASIC CO - ORDINATES AT A GAUSS POINT HAS A ZERO LENGTH. User information: The user supplied N vector or the PLOAD4 Bulk Data entry was nonzero but became zero when transformed to basic. This is a program error erflow. or und *** USER WARNING MESSAGE 5183. (DRMS2 - 2) 5183.0 OUTPUT DATA BLOCK CORRESPONDING TO INPUT MODAL SOLUTION DATA BLOCK %1 IS NOT PRESENT. INPUT DATA BLOCK THUSLY IGNORED. User information: the corresponding Since the output data block was purged, the data in input data block was not used. *** USER WARNING MESSAGE 5184. (DRMS2 4) - 5184.0 INVALID INPUT DATA DETECTED IN DATA BLOCK %1. PROCESSING STOPPED FOR THIS DATA BLOCK. - 1) *** USER WARNING MESSAGE 5185. (DRMS2B 5185.0 THE AMOUNT OF DATA IS NOT CONSISTENT FOR EACH EIGENVALUE IN DATA BLOCK %1 PROCESSING OF THIS DATA BLOCK TERMINATED. User information: Send run to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. - 2) *** USER WARNING MESSAGE 5186. (DRMS2A 5186.0 - ID RECORDS OF DATA BLOCK A CHANGE IN WORD 2 OF THE OFP %1 HAS BEEN DETECTED. PROCESSING OF THIS DATA BLOCK HAS BEEN TERMINATED. *** USER INFORMATION MESSAGE 5187. (DRMS1 - 3) 5187.0 INSUFFICIENT MEMORY, ADDITIONAL %1 WORDS ARE NEEDED. USER INFORMATION MESSAGE 5187. (D9ALTOP) *** 5187.1 INSUFFICIENT MEMORY, ADDITIONAL %1 WORDS ARE NEEDED. USER ACTION: INCREASE SPECIFIED MEMORY. - 1) *** USER INFORMATION MESSAGE 5188. (DRMS2 5188.0 MODULE DRMS2 TERMINATED WITH VARIABLE IERROR = %1 *** USER WARNING MESSAGE 5189. (DRMS2A - 3) 5189.0 ILLEGAL MAJOR OR MINOR OFP - ID IDENTIFICATIONS = %1 DETECTED IN DATA BLOCK%2. PROCESSING OF SAID DATA BLOCK DISCONTINUED. 3) *** USER WARNING MESSAGE 5190. (DRMS2B - 5190.0 DATA BLOCK%1 MAY NOT BE F ULLY COMPLETED DUE TO A

320 MEMORY INSUFFICIENCY OF APPROXIMATELY%2 DECIMAL WORDS. *** USER WARNING MESSAGE 5191. (DRMS2B - 2) 5191.0 ID RECORDS OF DATA BLOCK - A CHANGE IN WORD 2 OF THE OFP %1 HAS BEEN DETECTED. PROCESSING OF THIS DATA BLOCK HAS BEEN TE RMINATED. *** USER WARNING MESSAGE 5193, 5193.0 PARTITION FILE %1 IS OF SIZE%2 ROWS BY%3 COLS. PARTITIONING VECTORS INDICATE THAT THIS PARTITION SHOULD BE OF SIZE%4 ROWS BY%5 COLUMNS FOR A SUCCESSFUL MERGE. USER WARNING MESSAGE 5194, *** 5194.0 THE FORM PARAMETER AS GIVEN TO THE MERGE MODULE IS INCONSISTENT WITH THE SIZE OF THE MERGED MATRIX, HOWEVER IT HAS BEEN USED. FORM =%1 SIZE =%2 ROWS BY%3 COLUMNS. *** USER WARNING MESSAGE 5195, 5195.0 REQUESTED VALUE OF %1%2 %3USED BY %4. LOGICAL CHOICE IS%5 *** SYSTEM FATAL MESSAGE 5196, 5196.0 ATTEMPT TO RECOVER PLASTIC - STRAIN VS SLOPE FOR ELEMENT%1 MATERIAL%2 WHEN NONE FORMULATED. System information: o TABLES1 which does not exist. This message is issued if MATS1 refers t This error is also issued if PLASTIC is specified with TID and the first data point is not at the origin. Check MATS1 and TABLES1 entries to ensure that proper tables exist. ****USER FATAL MESSAGE 5197 (MPRO ) 5197.0 MATRIX MCHI3 IS SINGULAR. User information: Module MPRO attempted to decompose matrix MCHI3 which was singular. The location of the fluid coordinate system must not touch any element. It should be at the center of fluid. *** USER FATAL MESSAGE 5199 (XSBFF) 5199.0 THE BULK DATA FREE FIELD ENTRY BELOW HAS AN INTEGER OR A CHARACTER FIELD WITH MORE THAN EIGHT CHARACTERS. %1 User information: The bulk data free field formatter will not accept integer or character fields with more tha n eight characters, since it only generates single field entries. This can also occur when the line length exceeds 72 characters (note that commas count as characters).

321 NOT POSSIBLE TO 5202.0 PERFORM TEMPERATURE CORRECTION FOR ELEMENT ID = %1 A S TEMPERATURE IS ZERO . User information: The value of the absolute temperature must be greater than zero for temperature corrections in the creep process. The program ignores temperature corrections and continues. Check the "RT" field on the CREEP en try and the PARAM,TABS Bulk Data entry. To reduce the amount of output generated, this message is printed for the first element only while the error may exist for others. *** USER WARNING MESSAGE 5203 5203.0 ON THE SEMAP DATA BLOCK HAS BEEN MARKED N EXECUTABLE - BY MODULE SEP1. *** USER FATAL MESSAGE 5203 . 5203.1 IMPLAUSIBLE CREEP LAW OF TYPE 300 IS USED . User information: The value of d must be less than 2 on the CREEP entry. *** USER FATAL MESSAGE 5214, 5214.0 GRAV OPTION ON LOADCYH CARD ILLEGAL FOR BUCKLING *** USER FATAL MESSAGE 5215, 5215.0 RFORCE OPTION ON LOADCYHCARD ILLEGAL FOR BUCKLING *** USER FATAL MESSAGE 5216, 5216.0 GROUP %1 DID NOT REFERENCE ANY GRID POINTS User information: No grids were found in the specified group either directly with the GRID keyword, or indirectly via the PROP or ELEM keywords. *** USER FATAL MESSAGE 5217 *** , 5217.0 AN EXTRA POINT ID%1 DUPLICATES A GRID OR SCALAR POINT ID User information: ile processing the external grids in Module DPD, duplicate grid Wh numbers were found. *** USER INFORMATION MESSAGE 5218 (WILVCD) 5218.1 EIGENVALUE APPROACHING INFINITY AT %1TH MODE. EIGENVECTORS WILL NOT BE COMPUTED BEYOND THIS POINT. ion: User informat The MGIV, MHOU, AGIV, and AHOU methods substitute a very large number for eigenvalues that approach machine infinity. If eigenvectors are computed for these artificial values, they may be numerical noise, or they may cause overflows. Eigenvector c omputation is halted at the first machine infinity instead even if you requested eigenvectors in this range. *** USER INFORMATION MESSAGE 5218 (CLASDD) 5218.2 %1 INFINITE ROOTS AND %2 INDETERMINATE ROOTS HAVE BEEN

322 FOUND, FOR A PROBLEM SIZE OF %3. EIGENSOLUTIONS ARE NOT PROVIDED FOR INFINITE OR INDETERMINATE ROOTS. *** USER FATAL MESSAGE 5219 5219.0 FORM 3 MATRIX INPUT TO SMPYAD MODULE. USE MATMOD OPTION 27 FIRST. User information: Prior to Version 63, a special diagonal matrix could be i nput via DMI entries. It could be used properly only by the ADD, MPYAD, and MATPRN modules. This capability has been removed from the first two modules. Use MATMOD Option 27 to convert the matrix to Form 6. *** USER FATAL MESSAGE 5219 5219.1 RM 3 MATRIX INPUT TO DMPYAD MODULE. USE MATMOD FO OPTION 27 FIRST. User information: Prior to Version 63, a special diagonal matrix could be input via DMI entries. It could be used properly only by the ADD, MPYAD, and MATPRN modules. This capability has b een removed from the first two modules. Use MATMOD Option 27 to convert the matrix to Form 6. *** USER FATAL MESSAGE 5219 (ADD) 5219.2 FORM 3 MATRIX INPUT TO ADD MODULE. USE MATMOD OPTION 27 FIRST. User information: Prior to Version 63, a special diagonal matrix could be input via DMI entries. It could be used properly only by the ADD, MPYAD, and MATPRN modules. This capability has been removed from the first two modules. Use MATMOD Option 27 to convert the matrix to Form 6. *** USER WARNING MESSAGE 5219 5219.3 THE MATRIX MULTIPLICATION COULD HAVE A BETTER PERFORMANCE WITH METHOD ONE STORAGE 4, WHICH IS SELECTED BY SYSTEM(671)=1. User information: set system(671)=1 for better performance. * ** USER WARNING MESSAGE 5219 5219.4 UNABLE TO SELECT MPYAD METHOD ONE STORAGE 4 DUE TO LARGE MATRIX DIMENSION. PERFORMANCE MAY BE DEGRADED. User information: increase system(670) to enable MPYAD method one storage 4. *** USER WARNING MESSAGE 5219 5219.5

323 UNABLE TO SELECT MPYAD METHOD ONE STORAGE 4 DUE TO LIMITED MEMORY. PERFORMANCE MAY BE DEGRADED. User information: increase memory setting to enable MPYAD method one storage 4. *** USER FATAL MESSAGE 5220 (SEP1A) 5220.0 GRID NO. %1 APPEARS MORE THAN ONCE ON CSUPER ENTRY WITH SSID = %2 *** USER FATAL MESSAGE 5220 (SEPEXT) 5220.1 GRID OR SCALAR ID=%1 APPEARS MORE THAN ONCE ON EXTRN BULK DATA ENTRY WITH SUPERELEMENT ID=%2. *** USER WARNING MESSAGE 5221. 5221.0 STATISTICS FOR DECOMPOSITION OF MATRIX %1. THE FOLLOWING DEGREES OF FREEDOM HAVE NULL COLUMNS. User information: Module DCMP tried to decompose a matrix which was singular. That matrix had null columns and the associated gri d point numbers and degrees of freedom are printed out. *** USER INFORMATION MESSAGE 5222 , 5222.0 %1 COUPLED SOLUTION ALGORITHM USED. User information: The modal methods use uncoupled solution algorithms, if possible. The uncoupled algorithms are considerably more economical than the coupled algorithms. Coupled algorithms are required when any of the following effects are present: transfer functions, DMIG requests type, element damping, and PARAM,G. - of the p Consider the use of modal dampin g (TABDMP1 entry) to reduce the cost of your analysis. *** SYSTEM FATAL MESSAGE 5224 (XSEM) 5224.0 THE LINK SPECIFICATION TABLE HAS DIRECTED EXECUTION TO LINK %1 HOWEVER, THIS LINK DOES NOT CALL MODULE %2 System information: The "new" module has been incorrectly installed in the specified link or the problem is being run on a mismatched set of LINKS of NX NASTRAN. Report the problem to the programmer responsible for the generation of the failing link. MESSAGE 5225 (XSEM) *** SYSTEM FATAL 5225.0 THIS MODULE %1 CANNOT BE FOUND IN THIS LINK %2 OR ANY OTHER LINK. *** USER FATAL MESSAGE 5225 (SB46RD) 5225.1 ATTEMPT TO OPERATE ON THE SINGULAR MATRIX IN SUBROUTINE SB46RD.

324 User information: This message is preceded by the l isting of the grid point ID and degrees of freedom for any null columns. ATTEMPT TO OPERATE ON THE SINGULAR MATRIX %1 IN 5225.2 SUBROUTINE DCMP. User information: This message is preceded by the listing of the grid point ID and degrees of freedom for any null columns. *** USER FATAL MESSAGE 5226 (IFS5P) 5226.0 ILLEGAL INDEPENDENT DEGREES OF FREEDOM FOR RIGID ELEMENT %1 SORTED COUNT %2 User information: - set degrees - of - Rigid elements (excluding the RROD) must have six n freedom. *** USER FATAL MESSAGE 5227 (IFS5P) 5227.0 ILLEGAL DEPENDENT DEGREES OF FREEDOM FOR RIGID ELEMENT %1 SORTED COUNT %2 User information: The rigid element listed has picked an illegal component for a dependent degree of freedom. See Section 5 of t he NX NASTRAN Quick Reference Guide. *** USER WARNING MESSAGE 5229 5229.0 INPUT FILE TO MODULE %1 PURGED. MODULE RETURNS WITH PURGED OUTPUT. User information: The matrix to be decomposed is not present. Any module that depends on the output of this module will also have purged input. *** SYSTEM FATAL MESSAGE 5230, 5230.0 ELEMENT NUMBER OUTSIDE RANGE OF POSSIBLE NONLINEAR ELEMENTS. System information: The index passed to the new element type subroutine which unpacks e Block Data information determined that no data exists. th *** SYSTEM FATAL MESSAGE 5231, 5231.0 INCONSISTENT LENGTH ON NONLINEAR APPENDAGE DETECTED FOR ELEMENT %1 System information: The length encode with the EST file for the length of an element appendage did not match that decode from the Block Data. *** USER FATAL MESSAGE 5232 (XSBFF) 5232.0 THE BELOW REPLICATOR ENTRY HAS AN ILLEGAL VALUE. THE VALUE MUST BE AN INTEGER GREATER THAN 0. %1 User information:

325 The replicator count on the replicator entry must be an integer, greater than zero. *** USER INFORMATION MESSAGE 5236, 5236.0 THE FREQUENCY RANGE HAS BEEN SPLIT INTO %1 SUBREGIONS. User information: The ov erall frequency range for eigenanalysis is split into several smaller ranges when using the SINV option to calculate modes and frequencies. *** USER INFORMATION MESSAGE 5237, 5237.0 THE NEGATIVE FREQUENCY RANGE HAS BEEN SPLIT INTO %1 SUBREGIONS. User information: The overall frequency range for eigenanalysis has been split into several smaller ranges. This message occurs only for buckling analysis. *** USER INFORMATION MESSAGE 5238, 5238.0 NUMBER OF ROOTS IN THE DEFINED FREQUENCY RANGE IS GREATER THAN 600. User information: More than 600 roots are in the desired frequency range, which is greater than the maximum allowed using SINV. Decrease the size of the frequency range. *** USER INFORMATION MESSAGE 5239, 5239.0 BISECTING IN THE %1 - %2 INTERVAL ON LAMBDA. User information: - yy is cut The frequency subregion encompassing eigenvalues xx in half in order to find the remaining roots. *** USER INFORMATION MESSAGE 524 0, 5240.0 THE BISECTION VALUE IS : %1 FREQUENCY:%2 User information: The selected value is midway between the lowest and highest frequencies in the frequency subregion. *** USER INFORMATION MESSAGE 5241, 5241.0 MISSING ROOT(S) IN THE %1 - %2 INTERVAL ON LAMBDA. User information: The Sturm sequence check has indicated that roots are missing in the frequency range, and they cannot be found by further bisectioning. If the run terminates with missing roots, decre ase the frequency range. *** USER INFORMATION MESSAGE 5242, 5242.0 THE ROOT FOUND IS NOT THE LOWEST ONE ABOVE FMIN. User information: The Sturm sequence check indicates that at least one unfounded root exists between FMIN and the lowest frequenc y root found. Set FMAX close to the lowest frequency found, so that the lower roots can

326 be found. *** SYSTEM FATAL MESSAGE 5243 (SEQGP) 5243.0 NO GRID POINT (GEOM1) OR SCALAR POINT (GEOM2) GEOMETRY DATA AVAILABLE. System information: Both the G EOM1 (the first input file) for gridpoint geometry and the GEOM2 (the second input file) for scalar point geometry are either purged or contain no geometry data as input to the sequencer module SEQP. *** USER WARNING MESSAGE 5244. (GPFDR) 5244.0 HAS IGNORED DATA FROM THE %1 MATRIX (%2 X %3 ) DUE TO INCOMPATIBILITY WITH THE UGV MATRIX (%4 X %5 ) User information: The UG, PG, QG matrices are processed in synchronization. Incompatible sizes for these matrices which happens for some solution seque nces causes obscure terminations. An incompatible QG may be caused by grounded CELASi elements in a model with no constraints. Check whether GPFDR is supported for the solution sequence being used. SUBCASE%1, LOAD CAS%2 5246.0 S AN IDENTICAL ELEMENT ID%4 IN EACH ELEMENT TYPE%3, HA INPUT FILE. THE NUMBER OF WORDS %1 IN %2 FILE RECORD %3 IS 5247.0 INCORRECT. System information: Files being read do not agree with expected format. Check that correct files are being input to MERGEOFP. ELEMENT NAMES NOT FOUND IN ALPHABETICAL SORT WITHIN 5248.0 SUBCASE/LOADCASE IN%1 DATA BLOCK. System information: Check that the correct input files are being supplied to MERGEOFP. This error has also been observed when restart parameters LOOPID and UBID are not set properly. S --- , *** SYSTEM WARNING MESSAGE 5249 5249.0 ELEMENT WITH ELEMENT TYPE %1 NOT FOUND IN TABLE OF ELEMENTS /GPTA1 /. *** USER FATAL MESSAGE 5250, 5250.0 RAISING A NEGATIVE NUMBER TO A NON - INTEGER EXPONENT IS NOT ALLOWED. User information: The DIAGONAL module allows raising terms in matrices to non - integer exponents with the WHOLE option. Whenever the matrix terms are negative, the exponentiation fails. The PARAMR module performs a similar function with real parameters and the POWER option. These special applications may be performed by alternate DMAP modules depending upon the exponentiation the user wishes.

327 This can also be issued if the time incre ment is too large in transient - specify a smaller time increment. response *** SYSTEM FATAL MESSAGE 5251 (ADG) 5251.0 INSUFFICIENT OPEN CORE FOR DOWNWASH MATRIX GENERATION. *** SYSTEM FATAL MESSAGE 5252 (ADG) 5252.0 INCORRECT FORM OF INPUT DATA BLOCK %1 (FILE %2) FOR DOWNWASH MATRIX GENERATION IN ADG MODULE. System information: Check AESURF entries for references to undefined coordinate systems. Check AELIST entries for references to nonexistent boxes. Also, box identification numbers on the AELIST entry should be greater than all grid identification numbers. *** SYSTEM FATAL MESSAGE 5253 (ADG) 5253.1 INCORRECT FORM OF AESTAT ,AESURF, AEROS OR AELIST CARD IN EDT. System information: Check the aforementioned Bulk Data entries for correctness. *** SYSTEM FATAL MESSAGE 5254 (OPTGPH) 5254.0 UNABLE TO OPEN GEOM1. *** SYSTEM FATAL MESSAGE 5254 (ADG) 5254.1 UNABLE TO OPEN THE INPUT DATABLOCK EDT. USER FATAL MESSAGE 5255 (ADG) *** 5255.0 THE REQUIRED INPUT DATA BLOCK %1 (FILE %2) DOES NOT EXIST (IS PURGED). *** USER FATAL MESSAGE 5256 (ADG) 5256.0 NO AESTAT ENTRIES WERE FOUND IN THE EDT. USER INFORMATION: AESTAT ENTRIES ARE REQUIRED TO ODY MOTIONS. DEFINE RIGID B *** USER FATAL MESSAGE 5257 5257.0 DIVERG BULK DATA ENTRY WITH ID %1 DOES NOT EXIST. *** USER FATAL MESSAGE 5257 (ASGPRD) 5257.1 TRIM BULK DATA ENTRY WITH ID %1 DOES NOT EXIST. *** USER FATAL MESSAGE 5257 (AELOOP) 5257.3 TRIM BULK DATA ENTRY WITH ID %1 DOES NOT EXIST. *** USER WARNING MESSAGE 5258, 5258.0 UNSUPPORTED NOLINI CARD ENCOUNTERED FOR SET%1 IN NON - LINEAR TRANSIENT. User information: The Nonlinear Transient Module NLTRD does not support the NFTUBE and NOLIN5 entries. *** USER WARNING MESSAGE 5260 (SDP) 5260.0

328 DIVISION BY ZERO, USING MACH NUMBER, REFERENCE SPAN, CHORD, OR AREA User information: The AEROS entry or the TRIM entry includes a zero value for one of the above parameters. Check input parameters. *** USER FATAL MESSAGE 5264 (ASGLAB) 5264.0 TRIM/AELINK BULK DATA ENTRY REFERENCES LABEL %1 WHICH IS UNDEFINED ON AN AESTAT, AESURF OR AEPARM ENTRY. *** USER FATAL MESSAGE 5264 (UXVGEN) 5264.1 UXVEC BULK DATA ENTRY R EFERENCES LABEL %1 WHICH IS UNDEFINED ON AN AESTAT, AESURF OR AEPARM ENTRY. *** USER FATAL MESSAGE 5265 (ASG) 5265.0 TOO LITTLE DATA ON TRIM OR AELINK BULK DATA ENTRIES. *** USER FATAL MESSAGE 5266 (ASGPRD) 5266.0 TOO MUCH DATA ON TRIM OR AELINK BULK DATA ENTRIES. *** USER FATAL MESSAGE 5267 (ASGLD) 5267.0 ZXX MATRIX IS SINGULAR. TRIM AND AELINK ENTRIES SPECIFY AN INADEQUATE CONSTRAINT SET. *** USER WARNING MESSAGE 5269 (ASDR) 5269.0 REQUESTED ASDR OUTPUT SET%1 IS NOT PRESENT User information: The output set identified on the APRES or AEROF entry is not present. Modify the ID requested on the AEROF or APRES entry, or supply an output set with an ID matching the on on the AEROF or A PRES entry. *** USER FATAL MESSAGE 5270 (ETETD) 5270.0 ZERO ELEMENT VOLUME DETECTED FOR ELEMENT WITH ID = %1 User information: This message occurs when a zero volume is calculated for the TETRA TETRA has all element using the four corner points. Probably the four points lying on a plane. Geometry must be corrected. *** USER FATAL MESSAGE 5271 (ETETD) 5271.0 FOR TETRA ELEMENT ID = %1, THE RATIO OF LONGEST EDGE TO SHORTEST ALTITUDE EXCEEDS %2 TH USER ACTION: THE TOLERANCE MAY BE ADJUSTED WI TETRAAR KEYWORD ON THE NASTRAN STATEMENT. User information: This occurs as a warning when there is a folded or shallow CTETRA element. Results are suspect because the aspect ratio is not favorable. If region being modeled is important, remeshing may be needed. *** USER FATAL MESSAGE 5272 5272.0 PLASTICITY MODULUS MUST BE LESS THAN THE ELASTICITY

329 MODULUS FOR TABLE ID %1. User information: strain curve in the plastic Ensure that the slope of the stress - region does not exceed the elasticity modulus. Check the stress strain curve for the specific Table ID. - *** USER FATAL MESSAGE 5273 (EPYRGC) 5273.0 ZERO ELEMENT VOLUME DETECTED FOR ELEMENT WITH ID = %1 User information: This message occurs when a zero volume is calculated for the PYRAMID element using the five corner points. Probably the PYRAMID has all five points lying on a plane. Geometry must be corrected. *** USER FATAL MESSAGE 5273 (EPYRGC) 5273.1 ZERO QUAD AREA DETECTED FOR PRYAMID ELEMENT WITH ID = %1 User information: This message occurs when a zero quad area is calculated for the PYRAMID element. Geometry must be corrected. *** USER INFORMATION MESSAGE 5274, 5274.0 THE ACTUAL TIME OF EIGENVECTOR GENERATION IS:%1 User information: The time spent in the major operations of the real eigensolution module are output. Note that the number of eigenvectors requested has a large effect on solution cost. *** USER INFORMATION M ESSAGE 5274, 5274.1 THE ACTUAL TIME OF EIGENVALUE ITERATION IS:%1 User information: The time spent in the major operations of the real eigensolution module are output. Note that the number of eigenvectors requested has a large effect on solution cost. *** USER INFORMATION MESSAGE 5274, 274.2 5 THE ACTUAL TIME OF PARALLEL MHOUSEHOLDER TRIDIAGONALIZATION IS:%1 User information: The time spent in the major operations of the real eigensolution module are output. Note that the number of eigenvectors requested has a large effect on solution cost. *** USER INFORMATION MESSAGE 5274, 5274.3 THE ACTUAL TIME OF MHOUSEHOLDER TRIDIAGONALIZATION IS:%1 User information: are output. Note that the number of eigenvectors requested has a large effect on solution cost.

330 *** USER INFORMATION MESSAGE 5274, 5274.4 THE ACTUAL TIME OF PARALLEL HOUSEHOLDER TRIDIAGONALIZATION IS:%1 User information: are output. Note that the number of eigenvectors request ed has a large effect on solution cost. *** USER INFORMATION MESSAGE 5274, 5274.5 THE ACTUAL TIME OF HOUSEHOLDER TRIDIAGONALIZATION IS:%1 User information: are output. Note that the number of eigenvectors requested has a large effect on solution cost. *** USER INFORMATION MESSAGE 5274, 5274.6 THE ACTUAL TIME OF MGIVENS TRIDIAGONALIZATION IS:%1 User information: are output. Note that the number of eigenvectors requested has a large effect on solution cost. *** USER INFORMATION MESSAGE 5274, 274.7 5 THE ACTUAL TIME OF GIVENS TRIDIAGONALIZATION IS:%1 User information: are output. Note that the number of eigenvectors requested has a large effect on solution cost. USER INFORMATION MESSAGE 5274. *** 5274.8 SPILL OCCURRED FOR THIS PROBLEM AT COLUMN NUMBER :%1 . *** SYSTEM WARNING MESSAGE 5275 --- 5275.0 ***** MRGOFP NEEDS MAXTYP INCREASED ABOVE%1 ***** *** USER WARNING MESSAGE 5276 (EQD8D) 5276.0 OO MUCH CURVATURE AND MAY YIELD ELEMENT %1 HAS T POOR ANSWERS. USER ACTION: THE TOLERANCE MAY BE ADJUSTED WITH Q8T6_ANG KEYWORD ON THE NASTRAN STATEMENT. User information: The element listed has an angle greater than a tolerance between normals to some corner grid poin ts. The default value for the tolerance is 30 degrees. This can lead to excessively low stiffness. Use a finer mesh size to reduce the angles between the normals. ***USER FATAL MESSAGE 5278, 5278.0 INPUT FILE,%1 NOT PROPER OR TAPE BIT NOT SET. FBS CHKPT OPTION CANNOT EXECUTE. ***USER INFORMATION MESSAGE 5279, 5279.0 FBS RESTARTED AT COLUMN NUMBER %1 ***USER INFORMATION MESSAGE 5280, 5280.0 FBS CHECKPOINT ON %1,PASS%2 COMPLETE, LAST CO L NBR =%3

331 *** USER WARNING MESSAGE 5281 (FA1PKE) 5281.0 THE PK METHOD OF FLUTTER ANALYSIS HAS FOUND REDUCED FREQUENCY VALUES OUTSIDE THE RANGE OF REDUCED FREQUENCIES USED FOR INTERPOLATION. User information: The MKAEROi entry has reduced frequency values specified for interpolation. If complex eigenvalues are found that have an associated reduced frequency outside the range on the MKAEROi entries then convergency may not be obtained. If it fails to converge and the k is outside the range the remaining eigenvalue will be skipped. Increase the range of reduced frequency on the MKAEROi entries. *** USER FATAL MESSAGE 5288, 5288.0 NO ROOT EXISTS ABOVE FMIN. User information: the eigenproblem of finding any number of This message occurs when roots above FMIN is expected, but the Sturm number indicates that there is no root above FMIN. Reduce FMIN in order to attempt to find a root. *** USER FATAL MESSAGE 5289 (WRGMTD) 5289.0 DEPENDENT DEGREE OF - FREEDOM GRID ID =%1 AND - COMPONENT =%2 APPEARS ON MORE THAN ONE MPC OR RIGID ELEMENT ENTRY. User information: An MPC entry or rigid element entry lists the same dependent grid point more than once. *** USER FATAL MESSAGE 5289 (WRGMTD) 5289.1 AN MPC OR RIGID ELEMENT BULK DATA ENTRY WITH DEPENDENT DEGREE - FREEDOM GRID ID =%1 AND - OF COMPONENT =%2 CONTAINS AN INDEPENDENT DEGREE OF - FREEDOM -- GRID ID =%3 AND - COMPONENT =%4 THAT IS SPECIFIED MORE THAN ONCE. -- User information: - OF No DEGREE FREEDOM m ay be specified more than once on the same - entry. List each independent grid point once per entry. *** USER FATAL MESSAGE 5289 (WRGMTD) 5289.2 AN MPC OR RIGID ELEMENT BULK DATA ENTRY WITH DEPENDENT DEGREE - - FREEDOM GRID ID =%1 AND OF COMPONENT =%2 IS ALSO SPECIFIED AS AN INDEPENDENT DEGREE - OF - FREEDOM. User information: No DEGREE - OF - FREEDOM may be specified more than once on the same entry. *** USER FATAL MESSAGE 5289 (WRGMTD) 5289.3

332 AN MPC OR RIGID ELEMENT BULK DATA ENTRY WITH DEPENDENT DE - OF - FREEDOM GRID ID =%1 AND GREE COMPONENT =%2 SET VALUE OF %3 WHICH IS NEARLY ZERO AND IS HAS AN M - LIKELY TO CAUSE NUMERICAL ERRORS. OVERRIDE WITH EXTREME CAUTION WITH SYSTEM CELL 461. User information: of - freedom for m Select a different degree set - - *** USER WARNING MESSAGE 5289 (WRGMTD) 5289.4 AN MPC OR RIGID ELEMENT BULK DATA ENTRY WITH - OF - FREEDOM GRID ID =%1 AND DEPENDENT DEGREE COMPONENT =%2 - HAS AN M SET VALUE OF %3 AND MAY CREATE NUMERICAL PROBLEMS. User information: egree - of - freedom for m Select a different d set - *** USER FATAL MESSAGE 5290 (GPSP) 5290.0 EXTERNAL ID =%1 DOF =%2 IS IN THE Q - SET, BUT HAS A STIFFNESS TERM BEFORE REDUCTION. User information: The q - set is reserved for generalized coordinates. In superelement s, each superelement must have a unique set of variables analysi set. Remove any elements connected to q - specified for its q - set points and provide a unique set of degrees of freedom for each superelement on of parameter that has generalized coordinates. See also the descripti ERROR in Section 6 of the NX NASTRAN Quick Reference Guide. *** USER WARNING MESSAGE 5291 (GPSP) 5291.0 EXTERNAL ID %1, REFERENCED ON AN SPCOFFI ENTRY, DOES NOT EXIST. *** USER INFORMATION MESSAGE 5293 5293.1 FOR DATA BLOCK %1 LOAD SEQ. NO. EPSILON EXTERNAL WORK EPSILONS LARGER THAN %2 ARE FLAGGED WITH ASTERISKS User information: One line of output is printed for each static loading condition. - Small values of EPSILON are due to accumulated round Large off error. values of EPSILON indicate possible singularities in the stiffness matrix. See Section 9.5.1. *** USER INFORMATION MESSAGE 5293 (SSM10D) 5293.3 ERROR RATIO FOR LARGEST EPSILON VALUE IN FIRST TEN SOLUTIONS: LOAD SEQ. NO. EPSILON EXTERNAL WO RK EPSILONS LARGER THAN %1 ARE FLAGGED WITH ASTERISKS *** USER INFORMATION MESSAGE 5293 (SSM10D) 5293.4

333 LOAD SEQ. NO. EPSILON EXTERNAL WORK EPSILONS LARGER THAN %1 ARE FLAGGED WITH ASTERISKS User information: One line of output is printed for each static loading condition. Small values of EPSILON are due to accumulated round off error. Large - values of EPSILON indicate possible singularities in the stiffness matrix. See Section 9.5.1. *** USER I NFORMATION MESSAGE 5293 (SSM10D) 5293.5 ERROR RATIO(S) FOR FIRST %1 SOLUTIONS: LOAD SEQ. NO. EPSILON EXTERNAL WORK EPSILONS LARGER THAN %2 ARE FLAGGED WITH ASTERISKS *** USER INFORMATION MESSAGE 5293 5293.11 FOR DATA BLOCK %1 RNAL WORK LOAD SEQ. NO. EPSILON EXTE User information: One line of output is printed for each static loading condition. - off error. Large Small values of EPSILON are due to accumulated round values of EPSILON indicate possible singularities in the stiffness .5.1. matrix. See Section 9 *** USER INFORMATION MESSAGE 5293 5293.13 FOR DATA BLOCK %1 LOAD SEQ. NO. EPSILON EXTERNAL WORK User information: One line of output is printed for each static loading condition. - off error. Large Small values of EPSILON are due to accumulated round values of EPSILON indicate possible singularities in the stiffness matrix. See Section 9.5.1. *** USER FATAL MESSAGE 5297 (EDTL) 5297.0 1, 105, 114, AND DEFORM LOAD IS ONLY APPLICABLE TO SOL 10 200 WITH STATICS OR BUCKLING ANALYSIS TYPE. User information: Use SPCD to apply enforced displacements in solution sequences for which DEFORM does not apply. *** USER WARNING MESSAGE 5298 (EDTL) 5298.1 M LOAD SET %1 UNDEFINED THERMAL OR DEFOR *** USER FATAL MESSAGE 5298, 5298.2 ILLEGAL KSYM OPTION ENCOUNTERED IN MODULE %1. *** SYSTEM FATAL MESSAGE 5299. 5299.0 I/O ERROR WHEN WRITING FINAL STARTING BLOCK *** SYSTEM FATAL MESSAGE 5299. 5299.1 UNRECOVERABLE TERMINATION FROM LANCZOS ITERATION INTERNAL ERROR CODE = %1 USER ERROR RETURN = %2

334 *** SYSTEM FATAL MESSAGE 5299. 5299.2 IMPROPER PARAMETER SPECIFICATION FOR LANCZOS *** SYSTEM FATAL MESSAGE 5299. 5299.3 TRUST REGION OVERFLOW IN BLOCK SHIFTED LANCZOS. *** SYSTEM FATAL MESSAGE 5299. 5299.4 RESTORATION OF FACTORIZATION ERROR *** SYSTEM FATAL MESSAGE 5299. 5299.5 FACTORIZATION ERROR ON THREE CONSECUTIVE SHIFTS *** SYSTEM FATAL MESSAGE 5299. 5299.6 INSUFFICIENT STORAGE FOR BLOCK SHIFTED LANCZOS. WORKSPACE AVAILABLE = %1 WORKSPACE REQUIRED = %2 *** SYSTEM FATAL MESSAGE 5299. 5299.7 STARTING BLOCK COMPUTATION ERROR *** SYSTEM FATAL MESSAGE 5299. 5299.8 FACTORIZATION ERROR AT A BOUNDARY SHIFT. POTENTIAL FIXES: IF LOWER BOUND IS ZERO USE A SMALL NEGATIVE VALUE. IF LOWER BOUND IS A SMALL NEGATIVE VALUE DECREASE IT. ELIMINATE MASSLESS MECHANISMS THE MODEL MAY CONTAIN. *** SYSTEM FATAL MESSA GE 5299 (LANCZ). 5299.9 INSUFFICIENT STORAGE FOR BLOCK SHIFTED LANCZOS. WORKSPACE AVAILABLE = %1 WORKSPACE REQUIRED = %2 *** USER FATAL MESSAGE 5400 (REIGL) 5400.0 INCORRECT RELATIONSHIP BETWEEN FREQUENCY LIMITS. SYSTEM FATAL MESSAGE 5401 (REIGL) *** 5401.0 LANCZOS METHOD IS UNABLE TO FIND ALL EIGENVALUES IN RANGE. ACCEPTED EIGENVALUES AND ADDITIONAL ERROR MESSAGES MAY BE LISTED ABOVE. A POSSIBLE CAUSE IS THE OCCURENCE OF HIGH MAXRATIOS ABOVE. USER ACTION: RERUN WITH ANOT HER METHOD OR ANOTHER SETTING ON EIGRL ENTRY OR CHECK MODEL FOR MECHANISMS IF HIGH MAXRATIOS EXIST. System information: This message can be issued if insufficient memory is available for Lanczos with sparse decomposition. It can also be issued if UFM 5 299 occurs. See the NX NASTRAN Numerical Methods User's Guide. This condition can be related to the occurrence of UWM 5411. *** SYSTEM WARNING MESSAGE 5401 (LANCZ). 5401.1 LANCZOS METHOD IS UNABLE TO FIND ALL EIGENVALUES IN RANGE. ACCEPTED EIGEN VALUES AND ADDITIONAL ERROR MESSAGES

335 MAY BE LISTED ABOVE. USER ACTION: RERUN WITH ANOTHER METHOD OR DIFFERENT SETTINGS FOR F1, F2, AND/OR NDES. System information: This message can be issued if insufficient memory is available for Lanczos with sparse d ecomposition. It can also be issued if UFM 5299 occurs. See the NX NASTRAN Numerical Methods User's Guide. This condition can be related to the occurrence of UWM 5411. ***USER WARNING MESSAGE 5402 ---- 5402.0 THE PROBLEM HAS AN EMPTY STIFFNESS MATRIX. User information: The problem requires a stiffness matrix. Verify that property entries are specified correctly. CPU TIME AT START OF LANCZOS ITERATION%1 5403.0 User information: iterations may be executed during one application Since several Lanczos of the Lanczos method (each shift is followed by at least one iteration), this information is given to measure the time required for the individual iterations. *** USER INFORMATION MESSAGE 5403 (LNNRIGL) 5403.1 BREAKDOWN OF CPU USAGE DURING LANCZOS ITERATIONS: OPERATION REPETITIONS TIMES (SEC): MAXIMUM MINIMUM AVERAGE TOTAL FBS (BLOCK SIZE=%1) %2 %3 %4 %5 %6 MATRIX - VECTOR MULTIPLY %7 %8 %9 %10 %11 SHIFT AND FACTOR %12 %13 %14 %15 %16 RUN %17 %18 %19 %20 %21 LANCZOS *** USER INFORMATION MESSAGE 5403 (CLASDD) 5403.2 BREAKDOWN OF CPU USAGE DURING COMPLEX LANCZOS ITERATIONS: OPERATION REPETITIONS TIMES (SEC): AVERAGE TOTAL SHIFT AND FACTOR %1 %2 %3 MATRIX - VECTOR MULTIPLY & FBS %4 %5 %6 REORTHOGONALIZATION %7 %8 %9 SOLVE BLOCK TRIDIAGONAL PROBLEM %10 %11 %12 EIGENVECTORS AND RESIDUALS %13 %14 %15 *** USER WARNING MESSAGE 5404, 5404.0 NEGATIVE MODAL MASS TERM IS ENCOUNTERED DURING INVERSE ITERATION PROCESS ABORTED. User informa tion: The modal mass matrix should have unit diagonal terms (for mass normalization). Negative terms may indicate negative eigenvalues. If these negative terms are computational zeroes (rigid - body modes, for example), then the negative terms are accept able. If the negative terms are finite values, there may be a modeling problem.

336 TERMINATION MESSAGE : ERROR %1 OCCURRED DURING 5405.0 ITERATION. User information: This message marks the breakdown of the inverse iteration process. See the NX NAST RAN Numerical Methods User's Guide for additional values and actions. Y Value User Action 11 File open error in interface; This error should not occur; - see GINO error message. report error to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. in post pro - 12 File open error This error should not occur; - processing; see GINO error report error to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. message. 13 File read error; see GINO This error should not occur; - error message. report error to SIEMENS PLM SOFTWARE CUSTOME R SUPPORT. 21 Insufficient space for block - Increase memory - size = 1. 22 Three consecutive factorizations Possible ill - conditioning; - failed at a shift. check model. - 23 Lanczos internal table overflow Specify smaller internal; due to enormous numbe r of shifts. may be necessary to have several runs. 31 Internal error in Lanczos (REIGL) This error should not occur; - module. report error to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. - - conditioning; 32 No convergence in solving the Possible ill nal problem. check model. tridiago - 33 Too many eigenvalues found; Check the orthogonality of the inconsistency between roots eigenvectors; if it is good, found and sturm number. then igoring this warning. *** USER WARNING MESSAGE 5406 (LNCR8D) 5406.0 NO CONVERGENCE IN SOLVING THE TRIDIAGONAL PROBLEM. User information: This message signals eigensolution problems in the Lanczos method. There is possible ill - conditioning; check your model. *** SYSTEM FATAL MESSAGE 5406 (LNNHERR) 5406.1 INTERNAL FAILURE IN THE LANCZOS PROCEDURE: TRIDIAGONAL QL PROCEDURE FAILED TO CONVERGE. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 5407 (LNCS1D) 5407.0 INERTIA (STURM SEQUENCE) COUNT DISAGREES WITH THE NUMBER OF MODES ACTUALLY COMPUTED IN A (PARTIAL)

337 INTERVAL USER ACTION: THE FOLLOWING CHANGES TO THE EIGRL CARD MAY HELP TO SOLVE THIS PROBLEM 1. INCREASE MAXSET. 2. IF F1 IS GIVEN AS ZERO, LEAVE IT BLANK. 3. IF F1 AND F2 ARE BOTH GIVEN, LEAVE F2 BLANK AND SPECIF Y A VALUE FOR ND. *** SYSTEM WARNING MESSAGE 5407 (LNCCKD) 5407.1 INERTIA (STURM SEQUENCE) COUNT DISAGREES WITH THE NUMBER OF MODES ACTUALLY COMPUTED IN A (PARTIAL) INTERVAL System information: This message shows a serious problem. Spurious modes were found in the Lanczos method. Check the multiplicity of the roots given in the interval. See the NX NASTRAN Numerical Methods User's Guide. *** SYSTEM WARNING MESSAGE 5408. 5408.0 FACTORIZATION FAILED. SHIFT CHANGED TO %1 System information: No user action to be taken. This message occurs only for the Lanczos method. *** USER INFORMATION MESSAGE 5409 (NL2CON) 5409.0 *** INTERNAL DEGREES OF FREEDOM FOR %1 ELEMENT(S) FAILED TO CONVERGE User information: Reduce the load increment. *** USER FATAL MESSAGE 5410 (IFP7) 5410.0 PBCOMP AND PBEAM IDENTIFICATION %1 WAS DUPLICATED User information: Property identification numbers for the PBCOMP and PBEAM entries must be unique. Check bulk data and ensure that PIDS for PBCOMP and PBEAM entries are not duplicated. *** USER FATAL MESSAGE 5410 5410.1 DUPLICATE PROPERTY ID NUMBERS = %1 FOR PSOLID AND PLSOLID OR PSHELL AND PLPLANE NE AND PGPLSN OR PSHELL OR PSOLID AND PCOMPS OR PPLA AND PCOMPG1 ARE NOT PERMITTED. *** USER WARNING MESSAGE 5411 5411.0 NEGATIVE TERM ON DIAGONAL OF MASS(VIBRATION) OR STIFFNESS(BUCKLING) MATRIX DETECTED. ROW NUMBER = %1 VALUE = %2 User information: The message is given fr om the REIGL module which performs a necessary (but not sufficient) check on the positive semi - definiteness of the

338 indicated matrix. Look for evidence of negative mass, such as minus signs on input. Negative terms on the factor of the indicated matrix must be removed for correct answers. Something has caused a negative term on the diagonal of the mass or stiffness matrix. Look for explicitly defined negative mass and/or stiffness terms. Also, check the continuation entries on the PBEAM entry. An inc orrect entry for the SO field may lead to improper mass definition. For example, if SO is set to NO at a particular X/XB location, the continuation entry for defining four stress locations on the cross section (C, D, E, F) is not used. If SO is NO but t he C, D, E, and F points are entered in error, negative mass terms can result if either E1 or E2 entries are entered. The offending DOF can be traced using the USET tables. The Lanczos method gives wrong answers for indefinite matrices. The of negative diagonal terms indicates a subclass of indefinite existence matrix. See the NX NASTRAN Numerical Methods User's Guide for more information. *** USER FATAL MESSAGE 5412 5412.0 IMPLAUSIBLE NONLINEAR ELASTIC MATERIAL USED STRESS = %1 STRAIN = %2 STRESS = %3 STRAIN = %4 User information: If the product of the stress and the strain is negative, this fatal message will result. *** USER FATAL MESSAGE 5413 (IFP7) 5413.0 XCEED PRODUCT OF MOMENTS OF INERTIA I1 AND I2 SHOULD E THE SQUARE OF I12 FOR PBCOMP ENTRY WITH PID %1 User information: This limitation is consistent with the existing beam. If the condition is not enforced the stiffness matrix for the generated beam element will be ill - defined. l2, and l12 on the PBCOMP entry. Check values of l1, *** SYSTEM FATAL MESSAGE 5414 (IFP9) 5414.0 ABNORMAL END OF PBEAML RECORD ENCOUNTERED ON DATA BLOCK %1 *** SYSTEM FATAL MESSAGE 5414 (IFP9) 5414.1 ABNORMAL END OF PBARL RECORD ENCOUNTERED ON DATA BLOCK %1 System information: End of record encountered where there should not be any. Could be hardware or computer system problem. Print the data block to see if it is plausible. If no hardware error suspected, send run to SIEMENS PLM SOFTWARE CUSTOMER SUPPORT . *** USER INFORMATION MESSAGE 5414 (IFP7) 5414.2

339 NO ELEMENTS REFERENCE PBCOMP BULK DATA ENTRIES. *** SYSTEM FATAL MESSAGE 5415 (IFP7) 5415.0 ABNORMAL END OF PBCOMP RECORD ENCOUNTERED ON DATA BLOCK %1 *** USER FATAL MESSAGE 5416 (EQDRD) 5416.0 CONGRUENCY IS NOT PERMITTED FOR NONLINEAR ANALYSIS. CHECK QUADR ELEMENT WITH ID=%1 *** USER FATAL MESSAGE 5416. (EQD4D) 5416.1 CONGRUENCY IS NOT PERMITTED FOR NONLINEAR ANALYSIS. CHECK QUAD4 ELEMENT WITH ID =%1 *** USER FATAL MESSAGE 5417 (EQDRD) 5417.1 THICKNESS SPECIFIED FOR QUADR ELEMENT WITH ID=%1 RESULTS IN COMPUTED ZEROS. User information: Moment of inertia is a function of thickness cubed. If thickness specified is too small, moment of inertia terms are computed to be zeros. This error is computer dependent because computed zeros are a function of machine precision. Increase the thickness. *** USER FATAL MESSAGE 5417. (EQD4D) 5417.2 SPECIFIED FOR QUAD4 ELEMENT WITH THICKNESS ID=%1RESULTS IN COMPUTED ZEROS. *** USER FATAL MESSAGE 5418 (IFS4P) 5418.0 ILLEGAL DUPLICATION ON RANDPS ENTRIES. User information: This message is issued if J, K, and X are all duplicated on the next RANDPS entry. This can also occur if there are additional RANDPS entries in the Bulk Data that are not referenced in Case Control. Remove the extra RANDPS entries from the Bulk Data. *** USER FATAL MESSAGE 5419 (TA1C) 5419.0 GENEL CARD %1 CONTAINS DUPLICATE GRID AND COMPONENT ID NUMBERS *** USER FATAL MESSAGE 5419 (GP2) 5419.1 GENEL CARD ID=%1 MISSING DATA *** USER FATAL MESSAGE 5419 (MODGM2) 5419.2 STRUCTURAL ELEMENT %1 ID =%2 IS ATTACHED TO A FLUID ID =%3 GRID POINT *** USER INFORMATIONAL MESSAGE 5419 (GP2) 5419.3 NUMBER OF SHELL ELEMENTS WITH THICKNESS SCALING =%1 *** USER FATAL MESSAGE 5419 (MODGM2) 5419.4 FLUID ELEMENT %1 ID =%2 IS ATTACHED TO A STRUCTURAL GRID POINT ID =%3

340 SYSTEM WARNING MESSAGE 5420 (SEP2) *** 5420.0 SUPERELEMENT %1 HAS NO EXTERIOR POINTS. *** USER FATAL MESSAGE 5421 5421.0 THE VALUES FOR M2GG, B2GG, K2GG, P2G, K42GG, AND A2GG MUST BE REAL User information: When K2GG, B2GG, M2GG, K42GG, A2GG, or P2G is used, no complex DMIG entries may exist in the Bulk Data, even if they are not used. The only avoidance is to enter the complex matrix as two real matrices, one containing the real terms and the other contai ning the imaginary terms, and then adding them via DMAP. *** USER WARNING MESSAGE 5422 . 5422.0 PLATE ELEMENTS WITH ALL MIDSIDE NODES DELETED GIVE POOR RESULTS. *** USER FATAL MESSAGE 5423 (SMPYAD) 5423.0 ATTEMPT TO MULTIPLY OR ADD INCOMPA TIBLE MATRICES COLS ROW FORM TYPE NZWD DENS *** USER FATAL MESSAGE 5423 --- 5423.1 ATTEMPT TO ADD INCOMPATIBLE MATRICES, (SADD5) ATTEMPT TO ORTHOGONALIZE INCOMPATIBLE MATRICES 5423.2 ID COLS ROWS FORM TYPE NZWD DENS TRAILER FOR %1 IS %2 TRAILER FOR %3 IS %4 *** USER FATAL MESSAGE 5423 --- 5423.3 ATTEMPT TO MULTIPLY INCOMPATIBLE MATRICES COLS ROWS FORM TYPE NZWD DENS TRAILER FOR %1 IS%2 TRAILER FOR %3 IS%4 TRAILER FOR %5 IS%6 TRANSPOSE FLAG IS%7 *** USER FATAL MESSAGE 5423 --- 5423.4 ATTEMPT TO ADD INCOMPATIBLE MATRICES, (FRSAD5) *** USER FATAL MESSAGE 5423 (SDR4B) 5423.5 ATTEMPT TO MERGE INCOMPATIBLE MATRICES ID COLS ROWS FORM TYPE NZWD DENS TRAILER FOR %1 IS%2 TRAILER FOR %3 IS%4 * ** SYSTEM FATAL MESSAGE 5423 (MTMD34) 5423.6 ATTEMPT TO COMBINE INCOMPATIBLE MATRICES ID COLS ROWS FORM TYPE NZWD DENS TRAILER FOR %1 IS%2 TRAILER FOR %3 IS%4

341 *** SYSTEM FATAL MESSAGE 5423 (SDR4BA) 5423.7 ATTEMPT TO MERGE INCOMPATIBLE MATRICES ID COLS ROWS FORM TYPE NZWD DENS TRAILER FOR %1 IS%2 TRAILER FOR %3 IS%4 TRAILER FOR %5 IS%6 TRAILER FOR %7 IS%8 *** SYSTEM FATAL MESSAGE 5423 (APPEND) 5423.8 ATTEMPT TO APPEND INCOMPATIBLE MATRICES ID COLS ROWS FORM TYPE NZWD DENS TRAILER FO R %1 IS%2 TRAILER FOR %3 IS%4 *** SYSTEM FATAL MESSAGE 5423 (SSG3A) 5423.9 INPUT MATRICES ARE INCOMPATIBLE THE NUMBER OF ROWS OF MATRIX %1 IS %2 THE NUMBER OF ROWS OF MATRIX %3 IS %4 *** USER FATAL MESSAGE 5424. (GP3C) 5424.0 PLOADX1 LOAD SET =%1 REFERENCES ELEMENT ID =%2 WHICH WAS NOT FOUND AMONG THE TRIAX6 OR THE HYPERELASTIC TRIAX AND QUADX ELEMENTS IN THE PROBLEM. *** USER FATAL MESSAGE 5424. (GP3C) 5424.1 PLOADE1 LOAD SET =%1 REFERENCES ELEMENT ID =%2 WHICH WAS N OT FOUND AMONG THE CPLSTN3, CPLSTN4, CPLSTN6, CPLSTN8, CPLSTS3, CPLSTS4, CPLSTS6, CPLSTS8 ELEMENTS. *** USER FATAL MESSAGE 5425. (GP3C) 5425.0 PLOADX1 LOAD SET =%1. TRIAXFD ELEMENT%2 DOES NOT CONTAIN GRID%3 AS A CORNER GRID *** USER FATAL MESSAGE 5425. (GP3C) 5425.1 PLOADX1 LOAD SET =%1. TRIAX6 ELEMENT%2 DOES NOT CONTAIN GRID%3 AS A CORNER GRID *** USER FATAL MESSAGE 5425. (GP3C) 5425.2 PLOADX1 LOAD SET =%1. QUADXFD ELEMENT%2 DOES NOT CONTAIN GRID%3 AS A CORNER GRID *** USER FATAL MESSAGE 5425. (GP3C) 5425 .3 PLOADX1 LOAD SET =%1. TRIAXI6 ELEMENT%2 DOES NOT CONTAIN GRID%3 AS A CORNER GRID *** USER FATAL MESSAGE 5425. (GP3C) 5425.4 PLOADX1 LOAD SET =%1. TRIAXI3 ELEMENT%2 DOES NOT CONTAIN GRID%3 AS A CORNER GRID *** USER FATAL MESSAGE 5425. (GP3C) 5425.5 PLOADX1 LOAD SET =%1. QUADAX8 ELEMENT%2 DOES NOT CONTAIN GRID%3 AS A CORNER GRID

342 *** USER FATAL MESSAGE 5425. (GP3C) 5425.6 PLOADX1 LOAD SET =%1. QUADAX4 ELEMENT%2 DOES NOT CONTAIN GRID%3 AS A CORNER GRID *** USER WARNING MESSAGE 5426, 5426.0 DEFORM BULK DATA CARDS REFERENCED BY DEFORM CASE CONTROL COMMAND ARE NOT DEFINED. THE REQUEST FOR STRESSES AND/OR FORCES IS IGNORED. *** USER INFORMATION MESSAGE 5427 -- 5427.0 ENTERING LINK 16 DUMMY MODULE #1 *** -- *** USER INFORMATION MESSAGE 5428 5428.0 ENTERING LINK 16 DUMMY MODULE #2 *** *** USER FATAL MESSAGE 5429 (REIGL) 5429.0 INSUFFICIENT TIME TO FINISH LANCZOS ITERATION. ESTIMATED TIME TO COMPLETE LANCZOS RUN IS %1 SECOND(S). User information: There is not enough time remaining to complete the analysis based on an estimate of how long the Lanczos iteration will take. Increase the value on the TIME statement in the Exec utive Control Section and rerun. In order to ensure that the run can be competed, overestimate the TIME value and do not rely on estimates or on actual times from a similar model. *** USER FATAL MESSAGE 5430 (APD2) 5430.0 CAERO2 ENTRY ID = %1 THAT REFERENCES THE PAERO2 ENTRY ID = %2, HAS EITHER AN INCONSISTENT USE FOR THIi OR THNi OR, THE LTH2 FIELD IS REQUIRED. *** USER FATAL MESSAGE 5431 (APD2) 5431.0 THI1 AND THN1 REQUIRED FOR CAERO2 %1 *** USER FATAL MESSAGE 5432 (APD2) 5432.0 CAERO2 BODY ENTRY ID = %1 THAT REFERENCES THE PAERO2 ENTRY ID = %2, THAT REFERENCES THE AEFACT ENTRY ID = %3, DOES NOT HAVE ENOUGH SLENDER ELEMENTS. USER INFORMATION: AT LEAST 2 SLENDER ELEMENTS ARE REQUIRED. *** USER FATAL MESSAGE 5438 *** 5438.0 FOLLOWER FORCES ARE NOT ALLOWED WITH ENFORCED MOTIONS. User information: The direction vector of an enforced motion is constant within a subcase. Hence, a TLOADi entry which selects an enforced motion cannot refer to a follower force load. Modify the offending TLOADi entry. *** USER WARNING MESSAGE 5440 (EXPMSG) 5440.0

343 AUTHORIZATION EXPIRES WITHIN%1 MONTHS *** USER WARNING MESSAGE 5443 (ULANDD): 5443.0 DYNAMIC MATRIX IS SINGULAR AT THE SHIFT OF %1. User information: This is a diagnostic message issued when performing a complex eigenvalue analysis with Lanczos. See the NX NASTRAN Numerical Analysis User's Guide. *** USER WARNING MESSAGE 5443 (PTNLSP): 5443.1 E1 MATRIX IS SINGULAR. *** USER WARNING MESSAGE 5443 5443.2 DYNAMIC MATRIX IS SINGULAR AT THE SHIFT OF %1 *** USER INFORMATION MESSAGE 5444 5444.0 REQUIRED NUMBER OF ROOTS HAVE BEEN FOUND. User information: This is a diagnostic message issued when performing a compl ex eigenvalue analysis with Lanczos. *** USER INFORMATION MESSAGE 5445 (ULANCZ): 5445.0 MORE ROOTS THAN REQUIRED HAVE BEEN FOUND AT THIS SHIFT. User information: This is a diagnostic message issued when performing a complex eigenvalue with Lanczos. analysis *** USER INFORMATION MESSAGE 5445 5445.1 NO ROOTS FOUND AT ALL. **** USER FATAL MESSAGE 5446 5446.0 COMPLEX LANCZOS NEEDS %1 K MORE CORE WORDS User information: You need to supply more memory. *** USER INFORMATION MESSAGE 5447 (ULANRD): 5447.0 LANCZOS PROCESS FINISHED AT STEP %1 OF THE SHIFT OF %2. *** USER WARNING MESSAGE 5447: 5447.1 LANCZOS PROCESS ABORTED AT STEP %1 OF THE SHIFT OF %2. User information: This indicates a breakdown in the Lanc zos method. See Chapter 7 in the NX NASTRAN Numerical Methods User's Guide. *** USER WARNING MESSAGE 5448 (ULANRD): 5448.0 CANNOT FIND START VECTORS ORTHOGONAL TO PREVIOUSLY CALCULATED SUBSPACE AT THE SHIFT OF %1. User information: When a new s hift is started, the starting vectors are orthogonalized with respect to the already accepted eigenvectors of the earlier shifts (other orthogonalization). The message occurs if this process

344 fails. **** USER FATAL MESSAGE 5449 5449.0 UNEXPECTED EOF ENCOUNTERED %1 **** USER FATAL MESSAGE 5450 5450.0 UNEXPECTED WORD COUNT%1 %2 User information: This should not normally occur. This is associated with input/output , operations. You should clean your disk (remove unnecessary files) verify database allocations, and perform similar functions related to disk I/O. **** USER WARNING MESSAGE 5451 5451.0 NO ROOTS FOUND AT THIS SHIFT. User information: See the NX NASTRAN Numerical Methods User's Guide. **** USER WARNING MESSAGE 5452 5452.0 NO ROOTS ACCEPTED AT THIS SHIFT. User information: See the NX NASTRAN Numerical Methods User's Guide. *** USER INFORMATION MESSAGE 5453 (ULANCZ): 5453.0 FEWER ROOTS THAN REQUIRED HAVE BEEN FOUND AT THIS SHIFT. User inf ormation: This is a diagnostic message issued when performing a complex eigenvalue analysis with Lanczos. See the NX NASTRAN Numerical Methods User's Guide. *** USER INFORMATION MESSAGE 5453 5453.1 FEWER ROOTS THAN REQUIRED HAVE BEEN FOUND. *** SYSTEM FATAL MESSAGE 5454 (FRD2C) 5454.0 INCOMPATIBLE MATRICES USER INFORMATION: PROBABLE CAUSE IS DATA BLOCK QHHL IS NOT THE SAME ORDER AS KHH. User information: If a restart is performed where MHH, BHH, and KHH are redetermined n the number of eigenvalues, the H - set will change and with a change i QHH must be reformed in the AMP module. Re execute the AMP module by deleting the PARAM, SKPAMP entry. - *** USER INFORMATION MESSAGE 5455 *** 5455.0 INITIAL EQUILIBRIUM IS NOT SATISFIED. User information: In a nonlinear transient run using the adaptive time increment with the "STATIC" option, the initial equilibrium condition (F(u) = P is not satisfied. Examine TLOADi Bulk Data entries for an inadvertent specification of Po 0, or TIC entr ies for an inadvertent specification of uo 0.

345 *** USER FATAL MESSAGE 5456 (NMEVD) 5456.0 VALUE OF YOUNG'S MODULUS (E) IS LESS THAN OR EQUAL TO ZERO. User information: The effective strain is undefined unless E > 0. The computation cannot proceed without the effective strain. The error may be in the default value on a MAT1 entry or in the tabular data on a TABLEM1 entry. An extrapolated value obtained from the tabular data may be out of bounds. *** USER FATAL MESSAGE 5457 (EQDRD) 5457.0 NONLINEAR ANALYSIS IS NOT SUPPORTED FOR QUADR ELEMENT. User information: The PSHELL entry referenced by a CQUADR element may not contain references to MATS1 entries in the MIDi fields. Replace this element with the CQUAD4 element. *** US ER FATAL MESSAGE 5457 (Q4_MATXD) 5457.1 NONLINEAR ANALYSIS IS NOT SUPPORTED FOR NEW QUAD4 ELEMENT. User information: The PSHELL entry referenced by a CQUAD4 element may not contain references to MATS1 entries in the MIDi fields. Replace this element with the old CQUAD4 element. *** USER FATAL MESSAGE 5457 (T3_MATXD) 5457.2 NONLINEAR ANALYSIS IS NOT SUPPORTED FOR NEW TRIA3 ELEMENT. User information: The PSHELL entry referenced by a TRIA3 element may not contain references to MATS1 entries in the MID i fields. Replace this element with the old TRIA3 element. *** USER INFORMATION MESSAGE 5458, 5458.0 MODIFIED GIVENS METHOD IS FORCED BY USER . User information: The exact text of this message depends on the METHOD field on the selected EIGR Bulk Data entry. This message indicates the eigensolution status (all eigenvalues found, not all found, etc.). *** USER INFORMATION MESSAGE 5458, 5458.1 MODIFIED HOUSEHOLDER METHOD IS FORCED BY USER . User information: The exact te xt of this message depends on the METHOD field on the selected EIGR Bulk Data entry. This message indicates the eigensolution status (all eigenvalues found, not all found, etc.). *** USER INFORMATION MESSAGE 5458, 5458.2 MODIFIED GIVENS METHOD IS AUTOMATICALLY SELECTED .

346 User information: The exact text of this message depends on the METHOD field on the selected EIGR Bulk Data entry. This message indicates the eigensolution status (all eigenvalues found, not all found, etc.). *** USER INFORMATION MESSAGE 5458, 5458.3 MODIFIED HOUSEHOLDER METHOD IS AUTOMATICALLY SELECTED . User information: The exact text of this message depends on the METHOD field on the selected EIGR Bulk Data entry. This message indicates the (all eigenvalues found, not all found, etc.). eigensolution status *** USER INFORMATION MESSAGE 5458, 5458.4 REGULAR GIVENS METHOD IS SELECTED . User information: The exact text of this message depends on the METHOD field on the selected EIGR Bulk Data entry. This message indicates the eigensolution status (all eigenvalues found, not all found, etc.). *** USER INFORMATION MESSAGE 5458, 5458.5 REGULAR HOUSEHOLDER METHOD IS SELECTED . User information: The exact text of t his message depends on the METHOD field on the selected EIGR Bulk Data entry. This message indicates the eigensolution status (all eigenvalues found, not all found, etc.). *** USER INFORMATION MESSAGE 5458, 5458.6 QL HOUSEHOLDER METHOD IS AUTOMATICALLY SELECTED . User information: Based upon automatic selection criteria the eigensolution was changed to this method. To turn off this automatic selection, please set Lanczos method system cell 359 to 0. In the case of an original selection, setting the NE field to zero on the READ DMAP line will also turn off this automatic option. *** USER FATAL MESSAGE 5459 (ELTPRT) 5459.0 NONUNIQUE ELEMENT ID NUMBER DETECTED. %1 ELEMENT ID =%2 DUPLICATES A %3 ELEMENT. *** USER WARNING MESSAGE 5460 (IFS5P) 5460.0 ON PSOLID ENTRY PID=%1 FULL OR 1 IS SPECIFIED IN THE "ISOP" FIELD AND BLANK, 0, OR BUBBLE IS SPECIFIED IN THE "IN" FIELD. USER INFORMATION: 1. THE "ISOP" FIELD WILL BE RESET TO 0. 2. IF THIS ENTRY IS REFERENCED BY CHEXA OR CPENTA ELEMENTS WITH MIDSIDE NODES, THEN THE "IN" FIELD WILL BE RESET TO 3. User information: For CPENTA and CHEXA elements, when bubble function option is requested,

347 only reduced integration scheme is allowed . *** USER WARNING MESSAGE 5460 (IFS5P) 5460.1 FOR PSOLID ENTRY PID=%1, A VALUE OF TWO OR 2 HAS BEEN SPECIFIED IN THE "IN" FIELD. USER INFORMATION: IF THIS ENTRY IS REFERENCED BY CHEXA OR CPENTA ELEMENTS WITH MIDSIDE NODES IN NONLINEAR STRUCTURAL ANALYSIS, THEN THE "IN" FIELD WILL BE RESET TO 3. User information: For CPENTA and CHEXA elements with midside nodes in nonlinear structural analysis, only 3x3x3 integration and equivalent is allowed. *** USER FATAL MESSAGE 5461 . 5461.0 ELEMEN T ID =%1 HAS SINGULAR INTERPOLATION FUNCTION, SCHEME TO REDUCE THE RANK OF THE SHEAR STRAINS FAILED. User information: Least square technique used in weight reduced integration method fails if the elements has singular interpolation function. *** USER WARNING MESSAGE 5462 (IFS5P) 546 2.0 OPTIONS IN PSOLID ID = %1 FOR FLUID ELEMENT ARE NOT ALLOWED. DEFAULT VALUES WILL BE TAKEN. *** USER FATAL MESSAGE 5463 (TA1BND) 5463.0 RADIUS SPECIFIED FOR THE BEND ELEMENT =%1 IS LESS THAN HALF THE DISTANCE BETWEEN ITS TWO END POINTS. User information: Only a physically plausible radius should be used for the CBEND element. *** USER FATAL MESSAGE 5464 . 5464.0 ELEMENT %1 HAS ZERO MASS DENSITY OR BULK MODULUS. CHECK MATERIAL PROPERTIES. *** USER WARNING MESSAGE 5465 (DDRMM) 5465.0 SOLUTION FOR SUBCASE %1 IS MISSING, THEREFORE IT WILL NOT BE PROCESSED. USER INFORMATION: IF MORE THAN ONE RESIDUAL STRUCTURE SUBCASE IS SPECIFIED, THE RESULT OF THE FIRST SUBCASE WILL BE CALCULATED IN THIS SOLUTION SEQUENCE. User information: Only one residual structure subcase is allowed in the superelement solution sequences which perform transient analysis. See Section 3.6. *** USER FATAL MESSAGE 5466 (SDP) 5466.0 UND EFINED COORDINATE SYSTEM ID = %1 IS REFERENCED BY THE AEROS BULK DATA ENTRY

348 User information: Define referenced coordinate system ID in Bulk Data. *** USER FATAL MESSAGE 5467 5467.0 CONNECTION POINT G%1 OF CRAC3D ELEMENT %2 IS REQUIRED FINED BUT NOT DE User information: At least one of the required connection points has not been specified on the element entry. See Section 5 of the NX NASTRAN Quick Reference Guide. *** USER FATAL MESSAGE 5467 5467.2 CONNECTION POINT G%1 OF CRAC2D ELEMENT %2 IS REQUIRED BUT NOT DEFINED User information: At least one of the required connection points has not been specified on the element entry. See Section 5 of the NX NASTRAN Quick Reference Guide. USER FATAL MESSAGE 5468 (DUM9D) *** 5468.0 ILLEGAL GEOMETRY IN CRAC3D ELEMENT%1 User information: Only some of the connection points between G37 and G46 inclusive are defined. Supply missing grids on CRAC3D entry or do not specify any. See Section 5 of the NX NASTRAN Quick Reference Guide. *** USER FATAL MESSAGE 5469 (DUM9D) 5469.0 IN CRAC3D ELEMENT%1 CONNECTION POINT G%2 IS REQUIRED IF CONNECTION POINT G%3 IS SPECIFIED User information: On the element card, only one of a pair of connection points is specified. This rule applies to connection points G11 through G18 and G29 through G36. For example, if G11 is specified, then G29 must also be specified. See Section 5 of the NX NASTRAN Quick Reference Guide. *** USER FATAL MESSAGE 5470 5470.0 THE SPECIFIED CONNECTIVITY ON THE CRAC3D ELEMENT %1 IS NOT CONSISTENT WITH THE SYMMETRIC HALF CRACK OPTION User information: See Section 5 of the NX NASTRAN Quick Reference Guide. *** USER FATAL MESSAGE 5470 5470.2 THE SPECIFIED CONNECTIVITY ON T HE CRAC2D ELEMENT%1 IS NOT CONSISTENT WITH THE SYMMETRIC HALF CRACK OPTION User information: See Section 5 of the NX NASTRAN Quick Reference Guide. *** USER FATAL MESSAGE 5470 (DM9NS) 5470.4 THE SPECIFIED CONNECTIVITY ON THE CRAC3D ELEMENT%1 IS

349 N OT CONSISTENT WITH THE SYMMETRIC HALF CRACK OPTION User information: See Section 5 of the NX NASTRAN Quick Reference Guide. *** USER FATAL MESSAGE 5470 (DM8NS) 5470.6 THE SPECIFIED CONNECTIVITY ON THE CRAC2D ELEMENT%1 IS NOT CONSISTENT WITH THE SYMMETRIC HALF CRACK OPTION User information: See Section 5 of the NX NASTRAN Quick Reference Guide. *** USER FATAL MESSAGE 5471 5471.0 IN CRAC3D ELEMENT %1, TWO OR MORE CONNECTION POINTS ARE EITHER COINCIDENT OR COLLINEAR FATAL MESSAGE 5471 *** USER 5471.2 IN CRAC2D ELEMENT %1, TWO OR MORE CONNECTION POINTS ARE EITHER COINCIDENT OR COLLINEAR *** USER WARNING MESSAGE 5472 5472.0 IN CRAC3D ELEMENT%1, THE CRACK ANGLE, WHICH IS COMPUTED TO BE%2, IS TOO LARGE *** USER WARNING MESSAGE 5472 5472.2 IN CRAC2D ELEMENT %1, THE CRACK ANGLE, WHICH IS COMPUTED TO BE %2, IS TOO LARGE *** USER WARNING MESSAGE 5472 (DM9NS) 5472.4 IN CRAC3D ELEMENT %1, THE CRACK ANGLE, WHICH IS COMPUTED TO BE %2, IS TOO LARGE *** USER WARNING MESSAGE 5472 (DM8NS) 5472.6 IN CRAC2D ELEMENT%1, THE CRACK ANGLE, WHICH IS COMPUTED TO BE%2, IS TOO LARGE *** USER WARNING MESSAGE 5473 5473.0 IN CRAC3D ELEMENT %1, THE LOCATION OF MIDSIDE NODES CAUSES EXTREME DISTORTION IN THE BASIC PEN TAHEDRONS OF THE ELEMENT *** USER WARNING MESSAGE 5473 5473.2 IN CRAC2D ELEMENT %1, THE LOCATION OF MIDSIDE NODES CAUSES EXTREME DISTORTION IN THE BASIC TRIANGLES OF THE ELEMENT *** USER WARNING MESSAGE 5474 5474.0 IN CRAC3D ELEMENT %1, AN INTERIOR ANGLE OF THE BASIC PENTAHEDRONS IS EXTREMELY OBTUSE OR ACUTE User information: This may also be caused by poorly located midside nodes. *** USER WARNING MESSAGE 5474 5474.2 IN CRAC2D ELEMENT %1, AN INTERIOR ANGLE OF THE BASIC TRIANGLES IS EXTREMELY OBTUSE OR ACUTE User information:

350 This may also be caused by poorly located midside nodes. *** USER INFORMATION MESSAGE 5475.0 ALL QUAD4 ELEMENTS WILL USE THE NEW QUAD4 FORMULATION. USER INFORMATION MESSAGE *** 5475.1 ALL QUAD4 ELEMENTS WILL BE TREATED AS NEW QUADR ELEMENTS. *** USER INFORMATION MESSAGE 5475.2 ALL QUADR ELEMENTS WILL USE THE OLD QUADR FORMULATION. *** USER INFORMATION MESSAGE 5475.3 ALL QUADR ELEMENTS WILL BE TREATED AS NEW QUAD4 ELEMENTS. *** USER INFORMATION MESSAGE 5475.4 ALL QUADR ELEMENTS WILL BE TREATED AS OLD QUAD4 ELEMENTS. *** USER INFORMATION MESSAGE 5475.5 N. ALL TRIA3 ELEMENTS WILL USE THE NEW TRIA3 FORMULATIO *** USER INFORMATION MESSAGE 5475.6 ALL TRIA3 ELEMENTS WILL BE TREATED AS NEW TRIAR ELEMENTS. *** USER INFORMATION MESSAGE 5475.7 ALL TRIAR ELEMENTS WILL USE THE OLD TRIAR FORMULATION. *** USER INFORMATION MESSAGE 5475.8 ALL TRIAR ELEMENTS WILL BE TREATED AS NEW TRIA3 ELEMENTS. *** USER INFORMATION MESSAGE 5475.9 ALL TRIAR ELEMENTS WILL BE TREATED AS OLD TRIA3 ELEMENTS. *** USER FATAL MESSAGE 5476.0 QUAD4 ELEMENT %1 HAS ZERO DIAGONAL LENGTH. *** USER FATAL MESSAGE 5476.1 QUADR ELEMENT %1 HAS ZERO DIAGONAL LENGTH. *** USER FATAL MESSAGE 5476.2 THE ASPECT RATIO FOR QUAD4 ELEMENT %1 IS %2 WHICH EXCEEDS THE MAXIMUM ALLOWED VALUE OF %3. *** USER FATAL MESSAGE 5476.3 THE ASPECT RATIO FOR QUADR ELEMENT %1 IS %2 WHICH EXCEEDS THE MAXIMUM ALLOWED VALUE OF %3. *** USER FATAL MESSAGE 5476.4 QUAD4 ELEMENT ID =%1,

351 THE X - AXIS OF MATERIAL COOR. HAS NO PROJECTION PLANE; USE Y ON THE ELEMENT XY - - AXIS INSTEAD. *** USER FATAL MESSAGE 5476.5 QUADR ELEMENT ID =%1, AXIS OF MATERIAL COOR. HAS NO PROJECTION THE X - - - AXIS INSTEAD. PLANE; USE Y ON THE ELEMENT XY *** USER FATAL MESSAGE 5476.6 QUAD4 ELEMENT %1 HAS ZERO VOLUME. *** USER FATAL MESSAGE 5476.7 QUADR ELEMENT %1 HAS ZERO VOLUME. *** USER FATAL MESSAGE 5476.8 THE PERCENTAGE OF NEGATIVE VOLUME FOR QUAD4 ELEMENT %1 IS %2, WHICH EXCEEDS THE MAXIMUM ALLOWED PERCENTAGE OF %3. *** USER FATAL MESSAGE 5476.9 THE PERCENTAGE OF NEGATIVE VOLUME FOR QUADR ELEMENT %1 IS %2, WHICH EXCEEDS THE MAXIMUM ALLOWED PERCENTAGE OF %3. *** USER FATAL MESSAGE 5476.10 QUAD4/TRIA3 ELEMENT %1 HAS SINGULAR JACOBIAN (BAD GEOMETRY). *** USER FATAL MESSAGE 5476.11 QUADR/TRIAR ELEMENT %1 HAS SINGULAR JACOBIAN (BAD GEOMETRY). *** USER FATAL MESSAGE 5476.12 QUADR ELEMENT %1, THERE IS SINGULARITY IN THE BUBBLE FUNCTION PROCESSING. THE BUBBLE FUNCTION CORRECTION WAS SKIPPED. *** USER FATAL MESSAGE 5476.13 QUAD4/QUADR ELEMENT ID=%1, HAS ILLEGAL MAXIMUM NUMBER OF NODES. *** USER FATAL MESSAGE 5476.14 QUAD4/QUADR ELEMENT %1 HAS ZERO EDGE LENGTH. *** USER FATAL MESSAGE 5476.15 TRIA3/TRIAR ELEMENT %1 HAS ZERO EDGE LENGTH. *** USER FATAL MESSAGE 5476.16 TRIA6 ELEMENT %1 HAS ZERO EDGE LENGTH. *** USER FATAL MESSAGE 5476.17 QUAD8 ELEMENT %1 HAS ZERO EDGE LENGTH. *** USER FATAL MESSAGE 5476.18 QUAD4/QUADR ELEMENT ID=%1 HAS BAD GEOMETRY SUCH

352 THAT NORMAL VECTOR TO THE MID IT IS UNABLE TO DEFINE THE - PLANE. *** USER FATAL MESSAGE 5476.19 TRIA3/TRIAR ELEMENT ID=%1 HAS BAD GEOMETRY SUCH THAT IT IS UNABLE TO DEFINE THE NORMAL VECTOR TO THE MID - PLANE. *** USER FATAL MESSAGE 5476.20 TRIA6 ELEMENT ID=%1 HAS BAD GEOMETRY SUCH THAT IT IS UNABLE TO DEFINE THE NORMAL VECTOR TO THE MID - PLANE. *** USER FATAL MESSAGE 5476.21 QUAD8 ELEMENT ID=%1 HAS BAD GEOMETRY SUCH THAT IT IS UNABLE TO DEFINE THE NORMAL VECTOR TO THE MID - PLANE. *** USER FATAL MESSAGE 5476.22 THE WARPING FACTOR FOR QUAD4/QUADR ELEMENT ID=%1 IS %2, WHICH EXCEEDS THE MAXIMUM ALLOWED VALUE OF %3. *** USER FATAL MESSAGE 5476.23 THE WARPING FACTOR FOR TRIA3/TRIAR ELEMENT ID=%1 IS %2, WHICH EXCEEDS THE MAXIMUM ALLOWED VALUE OF %3. *** USER FATAL MESSAGE 5476.24 THE WARPING FACTOR FOR TRIA6 ELEMENT ID=%1 IS %2, WHICH EXCEEDS THE MAXIMUM ALLOWED VALUE OF %3. *** USER FATAL MESSAGE 5476.25 THE WARPING FACTOR FOR QUAD8 ELEMENT ID=%1 IS %2, WHICH EXCEEDS THE MAXIMUM ALLOWED VALUE OF %3. *** USER FATAL MESSAGE 5476.26 QUAD4/QUADR ELEMENT %1 HAS ZERO DIAGONAL LENGTH. *** USER FATAL MESSAGE 5476.27 DIAGONAL LENGTH. TRIA3/TRIAR ELEMENT %1 HAS ZERO *** USER FATAL MESSAGE 5476.28 TRIA6 ELEMENT %1 HAS ZERO DIAGONAL LENGTH. *** USER FATAL MESSAGE 5476.29 QUAD8 ELEMENT %1 HAS ZERO DIAGONAL LENGTH. *** USER FATAL MESSAGE 5476.30 QUAD4/QUADR ELEMENT ID=%1 HAS BAD GEOMETRY SUCH THAT IT IS UNABLE TO DEFINE THE NORMAL VECTORS AT CONNECTED GRID POINTS. *** USER FATAL MESSAGE 5476.31

353 TRIA3/TRIAR ELEMENT ID=%1 HAS BAD GEOMETRY SUCH THAT IT IS UNABLE TO DEFINE THE NORMAL VECTORS AT CONNECTED GRID POINTS. *** USER FATAL MESSAGE 5476.32 TRIA6 ELEMENT ID=%1 HAS BAD GEOMETRY SUCH THAT IT IS UNABLE TO DEFINE THE NORMAL VECTORS AT CONNECTED GRID POINTS. *** USER FATAL MESSAGE 5476.33 QUAD8 ELEMENT ID=%1 HAS BAD GEOMETRY SUCH THAT IT IS UNABLE TO DEFINE THE NORMAL VECTORS AT CONNECTED GRID POINTS. *** USER FATAL MESSAGE 5476.34 QUAD4/QUADR ELEMENT %1 HAS ZERO THICKNESS. *** USER FATAL MESSAGE 5476.35 TRIA3/TRIAR ELEMENT %1 HAS ZERO THICKNESS. *** USER FATAL MESSAGE 5476.36 TRIA6 ELEMENT %1 HAS ZERO THICKNESS. *** USER FATAL MESSAGE 5476.37 QUAD8 ELEMENT %1 HAS ZERO THICKNESS. *** USER FATAL MESSAGE 5476.38 QUAD4/QUADR ELEMENT %1 HAS INCOMPLETELY DEFINED THICKNESS. *** USER FATAL MESSAGE 5476.39 TRIA3/TRIAR ELEMENT %1 HAS INCOMPLETELY DEFINED THICKNESS. *** USER FATAL MESSAGE 5476.40 TRIA6 ELEMENT %1 HAS INCOMPLETELY DEFINED THICKNESS. *** USER FATAL MESSAGE 5476.41 QUAD8 ELEMENT %1 HAS INCOMPLETELY DEFINED THICKNESS. *** USER FATAL MESSAGE 5476.42 QUADR ELEMENT %1 HAS SINGULAR JACOBIAN (BAD GEOMETRY). *** USER FATAL MESSAGE 5476.43 TRIAR ELEMENT %1 HAS SINGULAR JACOBIAN (BAD GEOMETRY). *** USER FATAL MESSAGE 5476.44 ELEMENT ID=%1, THE SHEAR MODULUS IS NOT DEFINED FOR TRANSVERSE SHEAR. THE SHEAR STIFFNESS IS IGNORED. *** USER FATAL MESSAGE 5476.45 TRIA3 ELEMENT ID =%1, THE X - AXIS OF MATERIAL COOR. HAS NO PROJECTION ON THE ELEMENT XY - PLANE; USE Y - AXIS INSTEAD.

354 *** USER FATAL MESSAGE 5476.46 TRIAR ELEMENT ID =%1, THE X - AXIS OF MATERIAL COOR. HAS NO PROJECTION PLANE; USE Y AXIS INSTEAD. - ON THE ELEMENT XY - *** USER WARNING MESSAGE 5476.47 TRIA3 ELEMENT ID =%1 THE OFF - PLANE SHEAR FLEXIBILITY MATRIX IS SINGULAR; THE SHEAR STIFFNESS IS IGNORED. *** USER WARNING MESSAGE 5476.48 TRIAR ELEMENT ID =%1 THE OFF PLANE SHEAR FLEXIBILITY MATRIX IS SINGULAR; - THE SHEAR STIFFNESS IS IGNORED. *** USER WARNING MESSAGE 5476.49 TRIAR ELEMENT %1, THERE IS SINGULARITY IN THE BUBBLE FUNCTION PROCESSING. THE BUBBLE FUNCTION CORRECTION WAS SKIPPED. *** USER FATAL MESSAGE 0 5476.5 TRIA3 ELEMENT %1 HAS ZERO VOLUME. *** USER FATAL MESSAGE 5476.51 TRIAR ELEMENT %1 HAS ZERO VOLUME. *** USER WARNING MESSAGE 5476.52 ELEMENT ID = %1 UNABLE TO DETERMINE THE ELEMENT TYPE ASSOCIATED WITH PLOAD4 DATA. CQUADR/CTRIAR ELEMENTS WILL BE PROCESSED AS CQUAD4/CTRIA3. *** USER WARNING MESSAGE 5477 (EQDRD) 5477.0 COUPLING BETWEEN BENDING AND MEMBRANE IS NOT SUPPORTED FOR QUADR ELEMENT. User information: The MID4 field on the PSHELL bu lk data entry and the ZOFFS field on the QUADR bulk data entry must be blank. *** USER WARNING MESSAGE 5477. 5477.1 COUPLING BETWEEN BENDING AND MEMBRANE IS NOT SUPPORTED FOR TRIAR ELEMENT. *** USER FATAL MESSAGE 5478. (TQDRD) 5478.0 FOR ELEMENT WITH ID =%1 THE JACOBIAN MATRIX IS SINGULAR. *** USER FATAL MESSAGE 5479. 5479.0 FOR ELEMENT WITH ID =%1 THE INTERNAL STRAIN MODES ARE SINGULAR. User information: Check material property entries referenced by this element for correctness.

355 *** SYSTEM FATAL MESSAGE 5480. 5480.0 FOR ELEMENT WITH ID =%1 *** THE EXTRAPOLATION MATRIX IS SINGULAR. User information: This indicates a logic error in the program. ontact SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. C *** USER WARNING MESSAGE 5481 (EQDRD) 5481.0 BUCKLING ANALYSIS IS NOT SUPPORTED FOR QUADR ELEMENT. User information: Differential stiffness, which is computed in a geometric nonlinear or buckling ana lysis, is not available for this element. Replace this element with the CQUAD4 or CTRIA3 element. *** USER WARNING MESSAGE 5481. 5481.1 BUCKLING ANALYSIS IS NOT SUPPORTED FOR TRIAR ELEMENT. User information: Differential stiffness, which is computed in a geometric nonlinear or buckling analysis, is not available for this element. Replace this element with the CQUAD4 or CTRIA3 element. *** USER FATAL MESSAGE 5481. 5481.2 NONLINEAR ANALYSIS IS NOT SUPP ORTED FOR QUADR ELEMENT. *** USER FATAL MESSAGE 5482 (EQDRD) 5482.0 HEAT TRANSFER ANALYSIS IS NOT SUPPORTED FOR QUADR ELEMENT. User information: The solution sequence requested on the Executive Control statement SOL is a heat transfer sequence o r the HEAT keyword is specified on the NASTRAN or APP statements. *** SYSTEM FATAL MESSAGE 5483, (TA1H) 5483.0 ROUTINE NEEDS TO BE UPDATED, IT DOES NOT SUPPORT ELEMENTS WITH GRIDS MORE THAN =%1 *** SYSTEM FATAL MESSAGE 5483, 5483.1 *** ELEMENT TIMING TABLE IN *** SEQCT ROUTINE NEEDS TO BE UPDATED, IT DOES NOT SUPPORT ELEMENT TYPE GREATER THAN =%1 System information: Contact SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 5483, (BLDECT), 5483.2 ROUTINE NEEDS TO BE UPDATED, IT DOES NOT SUPPORT ELEMENTS WITH GRIDS MORE THAN =%1 *** USER WARNING MESSAGE 5484, 5484.0 TABRND1 CARD, ID = %1, DEFINED (OR EXTRAPOLATED TO) NEGATIVE AUTO SPECTRAL DENSITIES. THEY WERE RESET TO ZERO.

356 USER WARNING MESSAGE 5484, *** 5484.1 GRID %1 IN REFERENCED SET DOESN'T EXIST. RANDOM RESULTS PROCESSING CONTINUES. *** USER INFORMATION MESSAGE 5484, 5484.2 RANDOM PROCESSING ABORTED DUE TO INSUFFICIENT MEMORY - INCREASE MEMORY VALUE BY %1 WORDS *** USER FATAL MESSAGE 5485, 5485.0 NO SOLUTION IS AVAILABLE TO PERFORM A RESTART. *** USER FATAL MESSAGE 5486 (SSG1A) 5486.0 NO STATIC LOAD SUBCASE IS SPECIFIED FOR A BUCKLING SOLUTION *** USER FATAL MESSAGE 5486 (SSG1) 5486.1 ILLEGAL USE OF RFORCE2 BULK DATA LOADING. ONLY VALID FOR SOLUTION 101 ROTOR DYNAMICS. *** USER WARNING MESSAGE 5487 5487.0 ORIENTATION VECTOR DEFINED FOR THE ELEMENT ID =%1 IS NEARLY PARALLEL, IT MAY GIVE POOR RESULTS. *** USER FATAL MESSAGE 5488 (NLINIT) 5488.0 THE CONTROLLED INCREMENTS METHOD MAY NOT BE USED WITHOUT LOAD INCREMENTS. *** USER WARNING MESSAGE 5489 (CASE) 5489.0 THE CONTROLLED INCREMENTS METHOD MAY NOT BE USED WITH CREEP. THE STANDARD ITERATION METHOD HAS BEEN SUBSTITUTED. *** USER WARNING MESSAGE 5489.1 (CASE) 5489.1 THE COMPUTATION OF THE ELEMENT STRAIN ENERGY IS TURNED OFF. THE - INTOUT - ENTRY ON THE NLPARM CARD MUST BE SET TO YES FOR ALL SUBCASES WHEN PARAM,LGDISP>0. OTHERWISE, INCORRECT STRAIN ENERGIES WILL RESULT. *** USER FATAL MESSAGE 5490 (INRELF) 5490.0 THE NUMBER OF SUPERELEMENT EIGENVECTORS %1 IS LESS THAN OR EQUAL TO THE NUMBER OF DEGREES OF FREEDOM, %2, ON THE SESUP BULK DATA ENTRY. USER ACTION: INC REASE THE NUMBER OF EIGENVECTORS DESIRED ON THE EIGR OR EIGRL BULK DATA ENTRY, OR DECREASE THE NUMBER OF DEGREES OF FREEDOM ON THE SESUP BULK DATA ENTRY. *** USER WARNING MESSAGE 5491 (EQD4D) 5491.0 BAD GEOMETRY FOR QUAD4 ELEMENT ID =%1 THE TAPER OF %2 EXCEEDS THE MAXIMUM VALUE OF %3

357 USER ACTION: THE TOLERANCE MAY BE ADJUSTED WITH Q4TAPER KEYWORD ON THE NASTRAN STATEMENT. User information: Bad geometry can cause incorrect answers for CQUAD4 elements. The the element is in a non bad geometry warning may be neglected if - critical part of the model, or if the element stress is constant. If the element is in a critical part of the model, you are advised to refine your model so these bad geometries do not occur. Skew and taper are representative of the amount that a CQUAD4 deviates from being rectangular. Skew is the angle between the lines that join opposite midsides. When this angle is less than 30 degrees the message is issued. For no skew this angle is 90 degrees. lows: Connect opposite grid points and compute Taper is computed as fol the area of the enclosed triangles. Ji is 1/2 of the area associated with grid i and the adjacent grids of the enclosed triangle. Ja is 1/4 - Ja)/Ja) exceeds 0.5 then the message is issued. of J1+J2+J3+J4. If ABS((Ji (The equation equals 0.0 if there is no taper.) Another way to think of taper is the ratio of the areas on the two sides of a diagonal; if the ratio is greater than 3, then the taper test fails. Note that these tests concern only geometry, and are made prior to the analysis. Another useful test, made after the analysis, is the stress discontinuity calculation. *** USER WARNING MESSAGE 5491 (EQD4D) 5491.1 BAD GEOMETRY FOR QUAD4 ELEMENT ID =%1 THE SKEW ANGLE %2 IS LESS THAN THE MINIMUM VALUE OF %3 DEGREES. USER ACTION: THE TOLERANCE MAY BE ADJUSTED WITH Q4SKEW KEYWORD ON THE NASTRAN STATEMENT. *** USER WARNING MESSAGE 5491 (ETR3D) 5491.2 BAD GEOMETRY FOR TRIA3 ELEMENT ID =%1 THE SMALLEST ANGLE,%2 IS LESS THAN THE MINIMUM VALUE OF %3 DEGREES. USER ACTION: THE TOLERANCE MAY BE ADJUSTED WITH T3SKEW KEYWORD ON THE NASTRAN STATEMENT. *** USER INFORMATION MESSAGE 5491 (EQDGED) 5491.3 BAD GEOMETRY FOR QUAD ELEMENT WITH ID =%1 THE SKEW ANGLE%2 IS LESS THAN THE RECOMMENDED MINIMUM VALUE OF 30 DEGREES. *** USER INFORMATION MESSAGE 5491 (EQDGED) 5491.4 BAD GEOMETRY FOR QUAD ELEMENT WITH ID =%1 THE TAPER OF%2 EXCEEDS THE RECOMMENDED MAXIMUM VALUE OF 0.5 . USER FATAL MESSAGE 5492 (OPTGPE) *** 5492.0 AN UNDEFINED DVID ID =%1 HAS BEEN REFERENCED BY A DVGRID BULK DATA CARD WITH A DVID =%2 USER ACTION: CHECK THE DVGRID AND GRID BULK DATA

358 CARDS *** USER FATAL MESSAGE 5492 (DSAJ1) 5492.1 AN UNDEFINED GRID ID =%1 HAS BEEN REFERENCED BY A DVGRID BULK DATA CARD WITH A DVID =%2 USER ACTION: CHECK THE DVGRID AND GRID BULK DATA CARDS *** USER WARNING MESSAGE 5494, 5494.0 ONLY THE FIRST 50 MESSAGES HAVE BEEN PRINTED. *** US ER WARNING MESSAGE 5494, 5494.1 - CORRELATION NO RANDT1 BULK DATA REFERENCED; AUTO WILL NOT BE CALCULATED. *** USER WARNING MESSAGE 5494, 5494.2 CALCULATIONS FOR ACOUSTIC POWER PSD WILL IGNORE ALL RANDPS BULK DATA ENTRIES - DIAGONAL TERMS (I.E. I .NE. J). THAT DEFINE OFF *** USER WARNING MESSAGE 5495, 5495.0 REQUESTED RESPONSE DATA OF ( %1 %2 ) BY RCROSS CARD IS MISSING. RCROSS CARD IS: RCROSS = %3 RTYPE1 = %4 ,ID1 = %5 ,COMP1 = %6 ,RTYPE2 = %7 ,ID2 = %8 ,COMP2 = %9 ,CURIV = %10 IT IS NEITHER COMPUTED NOR BELONGS TO CURRENT SUPERELEMENT. RCROSS REQUEST FOR THIS CARD IS IGNORED. *** USER WARNING MESSAGE 5495, 5495.1 REQUESTED RESPONSE DATA OF ( %1 ) BY RCROSS/RCROSSC CARD IS MISSING. IT IS NEITHER COMPUTED N OR BELONGS TO CURRENT SUPERELEMENT. *** USER WARNING MESSAGE 5495, 5495.2 REQUESTED RESPONSE DATA OF ( %1 %2 ) BY BOTH RCROSS AND RANDPS CARDS IS MISSING IN SOME SUBCASE(S). RCROSS CARD IS: RCROSS = %3 RTYPE1 = %4 ,ID1 = %5 ,COMP1 = %6 ,RTYPE2 = %7 ,ID2 = %8 ,COMP2 = %9 ,CURIV = %10 THE MISSING DATA IS RELATED TO THE FOLLOWING SUBCASE(S) ( ONLY UP TO TEN OF THEM ARE PRINTED ): SUBCASE(S): %11, %12, %13, %14, %15, %16, %17, %18, %19, %20 RCROSS REQUEST FOR THIS CARD IS IGNORED. *** USER WARNING MESSAGE 5495, 5495.3 REQUESTED COMPONENT CODE %1 OF RESPONSE DATA ( %2 %3 ) BY RCROSS CARD IS INCORRECT. RCROSS CARD IS: RCROSS = %4

359 RTYPE1 = %5 ,ID1 = %6 ,COMP1 = %7 ,RTYPE2 = %8 ,ID2 = %9 ,COMP2 = %1 0 ,CURIV = %11 RCROSS REQUEST FOR THIS CARD IS IGNORED. *** USER WARNING MESSAGE 5495, 5495.4 REQUESTED RESPONSE DATA OF ( %1 %2 ) BY RANDPS CARDS IS MISSING IN SUBCASE %3. RCROSS CARD IS: RCROSS = %4 %8 ,ID2 = %9 RTYPE1 = %5 ,ID1 = %6 ,COMP1 = %7 ,RTYPE2 = ,COMP2 = %10 ,CURIV = %11 RCROSS REQUEST FOR THIS CARD IS IGNORED. *** USER WARNING MESSAGE 5495, 5495.5 REQUESTED RCROSS OR RCROSSC BULK DATA ENTRY OF %1 BY RCROSS CASE CONTROL ENTRY IS MISSING. RCROSS REQUEST FOR THIS CARD IS IGNORED. *** USER WARNING MESSAGE 5495, 5495.6 COMPOSITE ELEMENTS CANNOT BE REFERENCED ON A RCROSS BULK DATA ENTRY; USE RCROSSC. RCROSS REQUESTS FOR ELEMENT NUMBER %1 WILL BE IGNORED. *** U SER WARNING MESSAGE 5495, 5495.7 REQUESTED RESPONSE DATA OF ( %1 %2 %3 ) BY RCROSSC CARD IS MISSING. RCROSSC CARD IS: RCROSSC = %4 RTYPE1 = %5 ,ID1 = %6 ,COMP1 = %7 ,PLY1 = %8 , RTYPE2 = %9 ,ID2 = %10 ,COMP2 = %11 ,PLY2 = %12 ,CURIV = %13 IT IS NEITHER COMPU TED NOR BELONGS TO CURRENT SUPERELEMENT. RCROSS REQUEST FOR THIS CARD IS IGNORED. *** USER WARNING MESSAGE 5495, 5495.8 REQUESTED RESPONSE DATA OF ( %1 %2 %3 ) BY BOTH RCROSSC AND RANDPS CARDS IS MISSING IN SOME SUBCASE(S). RCROSSC CARD IS: RCROSSC = %4 RTYPE1 = %5 ,ID1 = %6 ,COMP1 = %7 ,PLY1 = %8 , RTYPE2 = %9 ,ID2 = %10 ,COMP2 = %11 ,PLY2 = %12 ,CURIV = %13 THE MISSING DATA IS RELATED TO THE FOLLOWING SUBCASE(S) ( ONLY UP TO TEN OF THEM ARE PRINTED ): , %19, %20, %21, %22, %23 SUBCASE(S): %14, %15, %16, %17, %18 RCROSS REQUEST FOR THIS CARD IS IGNORED. *** USER WARNING MESSAGE 5495, 5495.9 NON - COMPOSITE ELEMENTS CANNOT BE REFERENCED ON A RCROSSC BULK DATA ENTRY; USE RCROSS. RCROSSC REQUESTS FOR ELEMENT NUMBER %1 WILL BE IGNORED.

360 *** USER WARNING MESSAGE 5495, 5495.10 REQUESTED COMPONENT CODE %1 OF RESPONSE DATA ( %2 %3 %4 ) BY RCROSSC CARD IS INCORRECT. RCROSSC CARD IS: RCROSSC = %5 RTYPE1 = %6 ,ID1 = %7 ,COMP1 = %8 ,PLY1 = %9 , RTYPE2 = %10 ,ID2 = %11 ,COMP2 = %12 ,P LY2 = %13 ,CURIV = %14 RCROSS REQUEST FOR THIS CARD IS IGNORED. *** USER FATAL MESSAGE 5497 (APD3) 5497.0 PLANFORM GEOMETRY FOR CAERO3 ID = %1 IS IN ERROR. USER ACTION: CHECK LEADING EDGE SWEEP ANGLE OR CONTROL SURFACE HINGE LINE. *** USER FATAL MESSAGE 5498 (APD2) 5498.0 CAERO2 ENTRY ID = %1 NOT INPUT IN Z,ZY,Y SEQUENCE *** USER FATAL MESSAGE 5499 (APD2) 5499.0 ASSOCIATED BODY ID = %1 REFERENCED ON PAERO1 ENTRY %2 COULD NOT BE FOUND. *** SYSTEM FATAL MESSAGE 5500 (DSAB3) 5500.0 NO MATCH FOUND IN GPTA1 FOR ECT LOCATE IDS%1 *** SYSTEM FATAL MESSAGE 5501 (DSAB3) 5501.0 --- ECT ENTRY LENGTH FOR ELEMENT TYPE %1 IS %2 PROGRAM LIMIT IS 350 *** USER WARNING MESSAGE 5502 (DSAL1) 5502.0 GRID ID = %1 REFERENCED ON A DRESP1 ENTRY COULD NOT BE FOUND. USER INFORMATION : THIS IS NOT RECOMMENDED AND MAY INDICATE A USER INPUT ERROR. RESULTS FOR OTHER RESPONSES ARE NOT AFFECTED. *** USER FATAL MESSAGE 5503 (DSAD13) 5503.0 ELEM NO. %1 PL Y NO. %2 REFERENCED ON A DRESP1 ENTRY COULD NOT BE FOUND. USER ACTION: CHECK THE ELEMENT IDS REQUESTED ON THE DRESP1 ENTRY. IF A CFAILURE RESPONSE TYPE IS REQUESTED, CHECK THAT THE CORRESPONDING PCOMP AND MAT1 BULK DATA ENTRIES HAVE BEEN CORRECTLY SPECI FIED. USER INFORMATION : USE OF UNREFERENCED ELEMENTS IS NOT RECOMMENDED AND MAY INDICATE A USER INPUT ERROR. RESULTS FOR OTHER RESPONSES ARE NOT AFFECTED. *** USER FATAL MESSAGE 5503 (DSAB5D) 5503.1 RECORD ID = %1 IS OUT OF SYNC ON DATA BLOCK NU MBR %2 AN DSAB5D SYSTEM ERROR USER ACTION: PLEASE SEND THIS RUN TO SIEMENS PLM SOFTWARE CUSTOMER SUPPORT.

361 *** USER FATAL MESSAGE 5506 5506.0 TRANSVERSE SHEAR MATERIAL MATRIX IS SINGULAR FOR PCOMP %1 *** SYSTEM FATAL MESSAGE 5507 (DSABET) 5507.0 TEMPERATURE SET ID. IN DATA RECORD NOT FOUND IN HEADER RECORD TEMP(1)=%1 TLIST(I)= %2 %3 %4 %5 %6 %7 %8 %9 %10 %11 %12 %13 %14 %15 %16 %17 %18 %19 %20 %21 *** USER FATAL MESSAGE 5511 (D SACTC) 5511.0 PROBLEM LIMITATION OF 66 TEMPERATURE SETS AS BEEN EXCEEDED. *** SYSTEM FATAL MESSAGE 5512 (DSACTC) 5512.0 TEMPERATURE SET ID. IN DATA RECORD NOT FOUND IN HEADER RECORD TEMP(1)= %1TLIST(I)=%2 %3 %4 %5 %6 %7 %8 %9 %10 %11 %12 %13

362 %14 %15 %16 %17 %18 %19 %20 %21 *** SYSTEM FATAL MESSAGE 5514 (DSAE) 5514.0 ELEMENT TYPE DOES NOT MATCH *** SYSTEM FATAL MESSAGE 5516 (DSAE) 5516.0 TABLE DIBIDG IS PURGED USER ACTION: VERIFY THAT THIS TABLE IS NOT PURGED *** USER WARNING MESSAGE 5532 (WEIGHT) 5532.0 RHO OF MAT CARD IS LESS THAN OR EQUAL TO ZERO User information: See Error Report 3557 in Chapter 17. *** USER FATAL MESSAGE 5535 (DSAW) 5535.0 THIS IS A NONSUPPORTED ELEMENT TYPE ELEMENT TYPE = %1 , PLEASE SEE USER INFORMATION: PROGRAM MANUAL VOL.1 EST DATABLOCK FOR ELEMENT TYPE *** SYSTEM WARNING MESSAGE 5535 (HBDY2) 5535.1 ELEMENT TYPE = %1 IS NOT SUPPORTED BY THIS MODULE. *** SYSTEM FATAL MESSAGE 5536 (DSMRG9) 5536.0 THE OBJECTIVE FUNCTION HAS NOT BEEN DEFINED FOR THIS RUN *** USER WARNING MESSAGE 5537 (DOPR3L) 5537.0 ELEMENT DEFORMATION SETS ARE NOT ACCOUNTED FOR PROPERLY IN SENSITIVITY CALCULATIONS. WRONG ANSWERS MAY RESULT FOR CALCULATED RESPONSES. *** USER FATAL MESSAGE 5554 (DSABET) 555 4.0 PROBLEM LIMITATION OF 66 TEMPERATURE SETS HAS BEEN EXCEEDED. *** USER FATAL MESSAGE 5601 (SDSA) 5601.0 A DESOBJ ENTRY CANNOT BE FOUND. ONE MUST BE DEFINED FOR THE DESIGN MODEL. *** USER FATAL MESSAGE 5602. (SDSA) 5602.0 DESOBJ ENTRY ID=%1 REFERENCES EXTERNAL SUPERELEMENT ID=%2 USER INFORMATION: DESOBJ ENTRY MAY ONLY REFERENCE A PRIMARY OR AN IMAGE SUPERELEMENT *** USER FATAL MESSAGE 5603. (SDSA) 5603.0 DESOBJ ENTRY ID=%1 REFERENCE S AN UNDEFINED

363 SUPERELEMENT *** USER FATAL MESSAGE 5605. (SDSAA) 5605.0 SUPERELEMENT MAP DOES NOT CONTAIN ELEMENT IDS FOR SEID =%1 *** USER FATAL MESSAGE 5606. (SDSAB) 5606.0 NO DRESP1 ENTRIES CAN BE FOUND IN DATABLOCK EDOM. USER ACTION: SPECIFY AT LEAST ONE DRESP1 ENTRY. *** USER FATAL MESSAGE 5607. (SDSAB) 5607.0 NO DRESP1 ENTRIES CAN BE FOUND FOR SUPERELEMENT ID=%1 - SYNTHETIC RESPONSES WITH DRESP2 - USER ACTION: SPECIFY AT LEAST A SINGLE DRESP1 DIRECT RESPONSE FOR THIS SUPERELEMENT *** USER FATAL MESSAGE 5608 (SDSAC) 5608.0 %1 ENTRY ID=%2 REFERENCES AN UNDEFINED DRESP1 ENTRY ID=%3 *** USER FATAL MESSAGE 5609 (SDSAC) 5609.0 DRESP2 ENTRY ID=%1 REFERENCES DRESP1 IDS THAT BELONG TO DIFFERENT SUPERELEMENTS. USER ACTION : MAKE SURE ALL DRESP1 IDS REFERENCED ON A DRESP2 REFER TO GID/EID OF A SINGLE SE. *** USER WARNING MESSAGE 5610 (DSAW) 5610.0 THE MASS DEFINED ON CMASSI BULK DATA ENTRIES DOES NOT CONTRIBUTE TO THE WEIGHT RESPONSE AND WILL BE IGNORED IN THE DESIGN SENSITIVITY AND OPTIMIZATION ANALYSIS. USER ACTION: DRESP2 SYNTHETIC RESPONSES CAN BE USED TO INCLUDE THE EFFECTS OF MASS CHANGES ON THE WEIGHT. *** USER FATAL MESSAGE 5612 (DOPR2B) 5612.0 ZERO GRID PERTURBATION IS PR ESCRIBED BY ALL DESIGN VARIABLES. USER ACTION: CHECK DVGRID BULK DATA ENTRIES FOR ZERO GRID PERTURBATION. PROGRAMMER INFORMATION: INPUT MATRIX DESVEC IS NULL. *** USER FATAL MESSAGE 5613 (DMPR) 5613.0 A DRESPI ENTRY DOES NOT EXIST IN THE BULK DAT A. USER INFORMATION: AT LEAST ONE DRESP1 OR DRESP2 MUST BE PRESENT IN THE DESIGN MODEL. *** USER FATAL MESSAGE 5615 (DMPRB) 5615.0 A DRESP2 ENTRY ID=%1 REFERENCES AN UNDEFINED DRESP1 ENTRY ID =%2 *** USER FATAL MESSAGE 5616 (DMPRB) 5616.0 DRESP2 ENTRY ID =%1 REFERENCES DRESP1 ENTRIES WHICH HAVE INCONSISTENT RESPONSE TYPES.

364 User information: When referencing DRESP1 entries, each referenced entry must have the same RTYPE and PTYPE. *** USER FATAL MESSAGE 5617. (SDSAB) 5617.0 THE SU PERELEMENT ID SPECIFIED ON THE DESOBJ BULK DATA ENTRY DOES NOT EXIST ON THE REFERENCED DRESP1 BULK DATA ENTRY. USER ACTION: VERIFY THE DESOBJ AND DRESP1 ENTRIES. *** USER FATAL MESSAGE 5618. (DPR3CN) 5618.0 CONSTRAINT ID =%1 ON RESPONSE ID =%2 APPEARS MORE THAN ONCE. IF FREQUENCY RESPONSE JOB, CONSTRAINT ALSO SHARES LOWFQ and/or HIGHFQ WITH DUPLICATE. USER ACTION: ENSURE THAT SUCH DUPLICATE CONSTRAINTS ARE REMOVED FROM INPUT. USER FATAL MESSAGE 5619. (SDSAB) *** 5619.0 A WEIGHT OR VOLUME RESPONSE IS REQUESTED FOR COLLECTOR SUPERELEMENT =%1 IN DRESP1 BULK DATA ENTRY =%2 USER ACTION: ENSURE THE SUPERELEMENT CONTAINS AT LEAST ONE ELEMENT WITH VOLUME. 20 (DSAJ1) *** USER FATAL MESSAGE 56 5620.0 AN UNDEFINED DESIGN VARIABLE ID =%1 HAS BEEN REFERENCED BY A DVGRID BULK DATA ENTRY WHICH HAS A GRID ID =%2 *** USER FATAL MESSAGE 5621 (DOM11K) 5621.0 THREE POINTS REFERENCED BY CORD2I ENTRY ID =%1 HAVE BECOME COLLINEAR USER ACTION: REEXAMINE DESIGN TASK SPECIFICATION USER INFORMATION X Y Z *** USER FATAL MESSAGE 5621 (DOM11J) 5621.1 THREE POINTS REFERENCED BY CORD1I ENTRY ID =%1 HAVE BECOME COLLINEAR. USER ACTION: REEXAMINE DESIGN TASK SPECIFICATION RMATION USER INFO GRID ID X Y Z *** USER FATAL MESSAGE 5622 (DSAJ) 5622.0 FOR AN EXTERNAL AUXILIARY MODEL: THE AUXILIARY DISPLACEMENT MATRIX OR THE DVSHAP BULK DATA ENTRY IS MISSING. USER ACTION: CHECK FOR THE EXISTENCE OF DVSHAP ENTRIES AND YOUR DATABASE FILE REFERENCED ON THE DBLOCATE STATEMENT.

365 *** USER FATAL MESSAGE 5623 (DSAJ) 5623.0 AN UNDEFINED DESIGN VARIABLE ID =%1 HAS BEEN REFERENCED BY A DVSHAP/DVBSHAP BULK DATA ENTRY. *** USER FATAL MESSAGE 5624 (DSAJ2) 5624.0 THE %1TH COLUMN OF THE DIRECT INPUT BASIS VECTOR MATRIX IS NULL. *** USER FATAL MESSAGE 5625 (DSAJ) 5625.0 AN UNDEFINED BASVEC COLUMN ID =%1 HAS BEEN REFERENCED BY A DVSHAP/DVBSHAP BULK DATA ENTRY. *** USER FATAL MESSAGE 5626 (DSAD13) 5626.0 ITEM CODE %1 REFERENCED ON DRESP1 ENTRY %2 WITH RTYPE = %3 IS INVALID FOR ELEMENT TYPE %4 %5. USER ACTION: CHECK THE SPECIFIED ITEM CODE WITH THOSE LISTED IN APPENDIX A OF THE NX NASTRAN QUICK REFERENCE GUIDE. *** USER FATAL MESSAGE 5627 (DSAD17) 5627.0 MORE THAN FIFTY INVALID ITEM CODES HAVE BEEN DETECTED *** USER FATAL MESSAGE 5628 (DSAD17) 5628.0 DRESP1 ID = %1 IS FOR RTYPE = %2 AND ELEMENT ID = %3. THE RESPONSE COULD NOT BE FOUND, EITHER BECAUSE THE ELEMENT DOES NOT EXIST OR SE THE RESPONSE TYPE IS NOT AVAILABLE FOR THE BECAU ASSOCIATED ELEMENT TYPE. *** USER FATAL MESSAGE 5629 (DSAD1C) 5629.0 THERE ARE DRESP1 ENTRIES FOR RESPONSE TYPE = %1 BUT THERE ARE NO CORRESPONDING OUTPUT RESPONSES. USER ACTION: CHECK THAT THE %2 ID'S LISTED ON THE DRESP1 ENTRIES EXIST. *** USER FATAL MESSAGE 5902. (DSAR) 5902.0 ZERO OR NEGATIVE TIME STEP ENCOUNTERED. *** USER FATAL MESSAGE 5903. (DSAR) 5903.0 INCONSISTENT DATA DETECTED FOR UG AND TOLA USER ACTION: VERIFY NUMBER OF SOLUTION VECTORS IN UG ARE THREE TIMES THE NUMBER OF TIME STEPS IN TOLA. *** SYSTEM FATAL MESSAGE 6001 (RSTART) 6001.0 ERROR IN OPENING THE DATABASE TRANSACTION FILE (DBRQUE). GINO FILE NAME = %1 USER ACTION: SEND THIS RUN TO SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM WARNING MESSAGE 6002 (ZREAD) 6002.0 FOR DATA BLOCK=%1, TYPE = UNSTRUCTURED, MATRIX, OR VECTOR IS NOT SUPPORTED.

366 PROGRAMMER ACTION : USE PROPER ROUTINES. *** USER FATAL MESSAGE 6002 (RSTART) 6002.1 RESTART DOES NOT SUPPORT TYPE = UNSTRUCTURED, FOUND ON DATA BLOCK %1 *** USER FATAL MESSAGE 6003 (RSTART) 6003.0 TOO MANY INPUT DATA BLOCKS STARTING WITH BLOCK %1 User information: There are two possible inpu t modes into the RESTART module. In neither of them are all three of the input data block slots to be filled. *** SYSTEM WARNING MESSAGE 6004 (TMALOC) 6004.0 DATA BLOCK %1 IS NOT DEFINED IN THE NDDL *** USER FATAL MESSAGE 6006 (DTIIN) 6006.0 - GINO FILE NUMBER %2 NOT FOUND INPUT DATA BLOCK %1 *** USER WARNING MESSAGE 6007 (DTIIN) - 6007.0 OUTPUT DATA BLOCK %1 - GINO FILE NUMBER %2 ALREADY APPEARS AS A DTIIN OUTPUT BLOCK ON THIS CARD *** US ER WARNING MESSAGE 6007 (DMIIN) - 6007.1 - OUTPUT DATA BLOCK %1 GINO FILE NUMBER %2 ALREADY APPEARS AS A DMIIN OUTPUT BLOCK ON THIS CARD *** SYSTEM FATAL MESSAGE 6009 (IFP1CP) 6009.0 THE NUMBER OF UNIQUE CASE CONTROL PARAMETERS EXCEEDS THE CURRENT LIMIT OF %1. USER ACTION: REDUCE THE NUMBER OF CASE CONTROL PARAMETERS *** SYSTEM FATAL MESSAGE 6010 (PVTCCP) 6010.0 THE MAXIMUM ALLOWABLE SIZE OF THE PARAMETER VALUE TABLE (PVT) HAS BEEN EXCEEDED. USER INFORMATION: THE PARAMETER VALUE DEFAULT TABLE (PVTS)WAS BEING MERGED INTO THE PARAMETER VALUE TABLE (PVT). THE MAXIMUM SIZE OF THE PVT TABLE IS %1 WORDS. USER ACTION: REDUCE THE NUMBER OF UNIQUE BULK DATA, CASE CONTROL, AND NDDL PA RAMETERS *** SYSTEM FATAL MESSAGE 6010 (IFPCCP) 6010.1 THE MAXIMUM ALLOWABLE SIZE OF THE PARAMETER VALUE DEFAULT TABLE (PVTS) HAS BEEN EXCEEDED. USER INFORMATION: THE NDDL PARAMETER DEFAULT VALUES WERE BEING %1 INTO THE PARAMETER VALUE DEFAULT TAB LE (PVTS). THE MAXIMUM SIZE OF THE PVTS TABLE IS %2 WORDS. USER ACTION: REDUCE THE NUMBER OF UNIQUE BULK DATA, CASE CONTROL, AND NDDL PARAMETERS *** SYSTEM FATAL MESSAGE 6010 (IFPCCP) 6010.2

367 THE MAXIMUM ALLOWABLE SIZE OF THE PARAMETER VALUE DEFAULT TABLE (PVTS) HAS BEEN EXCEEDED. USER INFORMATION: THE CASE CONTROL PARAMETERS WERE BEING %1 INTO THE PARAMETER VALUE DEFAULT TABLE (PVTS). THE MAXIMUM SIZE OF THE PVTS TABLE IS %2 WORDS. USER ACT ION: REDUCE THE NUMBER OF UNIQUE BULK DATA, CASE CONTROL, AND NDDL PARAMETERS *** SYSTEM FATAL MESSAGE 6010 (IFPCCP) 6010.3 THE MAXIMUM ALLOWABLE SIZE OF THE PARAMETER VALUE DEFAULT TABLE (PVTS) HAS BEEN EXCEEDED. USER INFORMATION: THE BULK DATA P ARAMETERS WERE BEING LOADED INTO THE PARAMETER VALUE DEFAULT TABLE (PVTS). THE MAXIMUM SIZE OF THE PARAMETER VALUE DEFAULT TABLE IS %1 WORDS. USER ACTION: REDUCE THE NUMBER OF UNIQUE BULK DATA, CASE CONTROL, AND NDDL PARAMETERS *** USER FAT AL MESSAGE 6011 (IPVDFT) 6011.0 THE MAIN SUBDMAP VPS TYPE OF PARAMETER %1 DIFFERS FROM THE TYPE DETERMINED FROM PARAM CARD DEFINITION. USER INFORMATION: VPS TYPE IS %2. PARAM TYPE IS %3. *** USER FATAL MESSAGE 6011 (IFPCCP) 6011.1 THE NDDL DEFAULT TYPE OF PARAMETER %1 DIFFERS FROM THE TYPE DETERMINED FROM PARAM CARD DEFINITION. USER INFORMATION: NDDL TYPE IS %2. PARAM TYPE IS %3. *** SYSTEM FATAL MESSAGE 6012 (IFPDRV) 6012.0 THE MAXIMUM ALLOWABLE SIZE OF THE PARAMETER VALUE TABLE (PVT) HAS BEEN EXCEEDED. USER INFORMATION: THE PVT TABLE WAS BEING CREATED FROM BULK DATA PARAM ENTRIES. THE MAXIMUM SIZE OF THE PVT TABLE IS %1 WORDS. USER ACTION: REDUCE THE NUMBER OF UNIQUE BULK DATA PARAMETERS. *** SYSTEM FATAL MESSAGE 6013 (IFSEQU) 6013.0 THE EQUATION INDEX TABLE HAS EXCEEDED THE MAXIMUM NUMBER OF EQUATIONS ALLOWED FOR THE %1 BLOCK. USER INFORMATION: THE MAXIMUM NUMBER OF EQUATIONS IS: 0.5 * SYSBUF - 1 EQUATIONS, OR %2 IN THIS RUN *** SYSTEM WARNING MESSAGE 6014 (MODTRL) 6014.0 UNABLE TO WRITE TRAILER FOR FILE %1 *** SYSTEM FATAL MESSAGE 6015, 6015.0 PREMAT TABLE LOGIC ERROR ... *** USER INFORMATION MESSAGE 6016 (PRTPRM) 6016.0 NO PARAMETERS EXIST IN THE VPS OF REQUESTED SUBDMAP

368 *** USER INFORMATION MESSAGE 6017 (PRTPRM) 6017.0 SUBDMAP %1 IS NOT IN CURRENT SUBDMAP CALLING CHAIN. *** USER INFORMATION MESSAGE 6018 (PRTPRM) 6018.0 PARAMETER NAMED %1 IS NOT IN THE VPS OF SUBDMAP %2. *** USER INFORMATION MESSAGE 6019 (PRTPRM) 6019.0 %1 THE SECOND PRTPARM PARAMETER VALUE IS IMPROPER. - - *** USER INFORMATION MESSAGE 6020 (PRTPRM) 6020.0 THE PRTPARM DIAGNOSTIC %1 IS NOT IN TABLE. *** USER INFORMATION MESSAGE 6021 (PVT) 6021.0 NULL INPUT DATA BLOCKS ARE BEING USED FOR PVT. *** USER WARNING MESSAGE 6022 (PVT) 6022.0 - - FILE ENCOUNTERED PROCESSING AN UNEXPECTED END OF INPUT DATA BLOCK 102. USER INFORMATION: IT WILL BE PROCESSED AS IF PURGED. *** USER WARNING MESSAGE 6023 (PVT) 6023.0 AN ATTEMPT WAS MADE TO REDEFINE THE TYPE OF THE BULK DATA OR CASE CONTROL PARAME TER %1. USER INFORMATION: THE ATTEMPT AT REDEFINITION IS IGNORED. *** SYSTEM FATAL MESSAGE 6024 (PVT) 6024.0 - - HAS OVERFLOWED THE PARAMETER VARIABLE TABLE PVT USER ACTION: REDUCE NUMBER OF BULK DATA AND/OR CASE CONTROL PARAM CARDS. *** SYSTEM FATAL MESSAGE 6025 (PVT) 6025.0 INSUFFICIENT OPEN CORE TO READ CASE CONTROL DATA *** USER WARNING MESSAGE 6027 (XEQUIV) 6027.0 ATTEMPT TO EQUIVALENCE PRIMARY DATABLOCK %1, WHICH DOES NOT EXIST. User information: This warning message can occur for many reasons. It has been seen in user DMAPs or DMAP alters where datablocks are being stored permanently on the database. If an EQUIV is done on one of these stored datablocks, and the qualifiers for that datablock ar e not set, then this message can occur. A more confusing case occurs when all qualifiers for a permanent datablock are not TYPEd as NDDL parameters, or are not passed into the current subDMAP. When an EQUIV is attempted, the UWM 6027 can occur. Be sure that ALL qualifiers that were set when the primary was stored are still set when the equivalence is attempted. *** SYSTEM WARNING MESSAGE 6028 (XMESAG) 6028.0 PARAMETER NUMBER %1 WAS NOT FOUND IN THE VPS *** SYSTEM FATAL MESSAGE 6029 (XQALVL) 6029.0 ATTEMPT TO LOAD FUNCTION NAME FROM INVALID ADDRESS

369 PROGRAMMER INFORMATION: ADDRESS POINTER = %1 *** SYSTEM FATAL MESSAGE 6029 (XQALVL) 6029.1 EXISTENT VPS VARIABLE ATTEMPT TO LOAD VALUE FROM NON - PROGRAMMER INFO RMATION: VPS ADDRESS POINTER = %1 *** SYSTEM FATAL MESSAGE 6030 (XQASVL) 6030.0 TEMPORARY VALUE IN ATTEMPT TO STORE (STOR) NON - TEMPORARY STORAGE ARRAY PROGRAMMER INFORMATION: TEMPORARY ADDRESS POINTER = %1 *** SYSTEM FATAL MESSAGE 6031 (XQASVL) 6031.0 UNABLE TO STORE (STOR) TEMPORARY VALUE IN TEMPORARY STORAGE ARRAY PROGRAMMER INFORMATION: TEMPORARY ADDRESS POINTER = %1 *** SYSTEM FATAL MESSAGE 6032 (XQALVL) 6032.0 UNDEFINED OPERAND DETECTED IN INSTRUCTION %1 PROGRAMMER INFORMATION: OPERAND POINTER = %2 *** SYSTEM FATAL MESSAGE 6033 (XQALVL) 6033.0 ATTEMPT BY INSTRUCTION %1 TO OPERATE ON NON - EXISTENT VPS VARIABLE *** SYSTEM FATAL MESSAGE 6033 (XQALVL) 6033.1 ATTEMPT BY INSTRUCTION %1 TO OPERATE ON NON - EXISTENT TEMPORARY VARIABLE *** SYSTEM FATAL MESSAGE 6034 (XQAROS) 6034.0 ATTEMPT BY INSTRUCTION %1 TO PERFORM LOGICAL LOGICAL VALUE OPERATION ON NON - *** SYSTEM FATAL MESSAGE 6034 (XQAROS) 6034.1 ATTEMPT BY INSTRUCTION %1 TO PERFORM RELATIONAL OPERATION ON LOGICAL VALUE *** SYSTEM FATAL MESSAGE 6034 (XQAROS) 6034.2 ATTEMPT BY INSTRUCTION %1 TO PERFORM CHARACTER - CHARACTER VALUE OPERATION ON NON *** SYSTEM FATAL MESSAGE 6034 (XQAROS) 6034.3 ATTEMPT BY INSTRUCTION %1 TO PERFORM ARITHMETIC NUMERIC VALUE OPERATION ON NON - *** SYSTEM FATAL MESSAGE 6035 (XQAROS) 6035.0 ATTEMPT TO RAISE NEGATIVE %1 BASE TO A FRACTIONAL EXPONENT *** SYSTEM FATAL MESSAGE 6036 (XQAROS) 6036.0 ATTEMPT TO DIVIDE BY %1 ZERO *** USER/SYSTEM FATAL/WARNING/INFORMATION MESSAGE 6036.1 6036 (EVLMSG)

370 DIVIDE BY ZERO WAS DETECTED *** SYSTEM FATAL MESSAGE 6037 (XQAROS) 6037.0 OMPARE COMPLEX ATTEMPT BY INSTRUCTION %1 TO C EXPRESSIONS WITH RELATIONAL OPERATOR *** SYSTEM FATAL MESSAGE 6038 (XQAROS) 6038.0 INVALID BLANK COMMON POINTER. PROGRAMMER INFORMATION: BLANK COMMON POINTER VALUE = %1 *** SYSTEM FATAL MESSAGE 6039 (XQALVL) 6039.0 ATTEMPT BY INSTRUCTION %1 TO ASSIGN VALUE TO NON - VPS VARIABLE *** SYSTEM FATAL MESSAGE 6040 (XQAROS) 6040.0 UNABLE TO ASSIGN (==) VALUE TO SPECIFIED VPS/DATABASE VARIABLE *** SYSTEM FATAL MESSAGE 6041 (XQALVL) 6041.0 ATTEMPT BY INSTRUCTION %1 TO LOAD VALUE OF A NON - EXISTENT VPS OR DATABASE VARIABLE INTO THE ARGUMENT STORAGE ARRAY PROGRAMMER INFORMATION: VPS/DATABASE POINTER = %2 *** SYSTEM FATAL MESSAGE 6041 (XQALVL) 6041.1 ATTEMPT BY INSTRUCTION %1 TO LOAD VA LUE OF A NON - EXISTENT TEMPORARY VARIABLE INTO THE ARGUMENT STORAGE ARRAY PROGRAMMER INFORMATION: TEMPORARY POINTER VALUE = %2 *** SYSTEM FATAL MESSAGE 6041 (XQALVL) 6041.2 ATTEMPT BY INSTRUCTION %1 TO LOAD VALUE FROM AN INVALID ADDRESS INTO THE ARGUMENT STORAGE ARRAY PROGRAMMER INFORMATION: ADDRESS VALUE = %2 *** SYSTEM FATAL MESSAGE 6042 (XQAROS) 6042.0 ATTEMPT TO PERFORM %1 OPERATION %2 BETWEEN %3 AND %4 DATA *** SYSTEM FATAL MESSAGE 6043 (XQAROS) 6043.0 UNABLE TO EVALUATE EXPR ESSIONS OF OSCAR TYPE %1 *** SYSTEM FATAL MESSAGE 6044 (XQASVL) 6044.0 ATTEMPT BY INSTRUCTION %1 TO STORE A NON - ARGUMENT VALUE IN THE ARGUMENT STORAGE ARRAY PROGRAMMER INFORMATION: ARGUMENT POINTER VALUE = %2 *** SYSTEM FATAL MESSAGE 6045 (XQASVL) 6045.0 UNABLE TO STORE ARGUMENT VALUE IN ARGUMENT STORAGE ARRAY DURING %1 INSTRUCTION *** SYSTEM FATAL MESSAGE 6046 (XQFUNC) 6046.0

371 ATTEMPT TO OPERATE ON NON - EXISTENT FUNCTION ARGUMENT *** USER FATAL MESSAGE 6047 (XQFNC2) 6047.0 ILLEGAL %1 ARGUMENT GIVEN FOR %2 FUNCTION. *** SYSTEM FATAL MESSAGE 6048 (XQFNC7) 6048.0 SQRT FUNCTION ATTEMPTED ON NEGATIVE %1 VALUE. *** SYSTEM FATAL MESSAGE 6048 (XQFNC5) 6048.1 ZERO %1 VALUE MOD FUNCTION ATTEMPTED ON *** SYSTEM FATAL MESSAGE 6048 (XQFNC5) 6048.2 COMMON LOGARITHM FUNCTION ATTEMPTED ON INVALID %1 VALUE. *** SYSTEM FATAL MESSAGE 6048 (XQFNC5) 6048.3 DEFINED BASE LOGARITHM FUNCTION ATTEMPTED ON - USER INVALID %1 VALUE. *** SYSTEM FATAL MESSAGE 6048 (XQFNC5) 6048.4 NATURAL LOGARITHM FUNCTION ATTEMPTED ON INVALID %1 VALUE. *** SYSTEM FATAL MESSAGE 6048 (XQFNC2) 6048.5 ARC HYPERBOLIC SINE FUNCTION ATTEMPTED ON INVALID %1 VALUE. *** SYSTEM FATAL MESSAGE 6048 (XQFNC2) 6048.6 ARC HYPERBOLIC COSINE FUNCTION ATTEMPTED ON INVALID %1 VALUE. *** SYSTEM FATAL MESSAGE 6048 (XQFNC1) 6048.7 ARC SINE FUNCTION ATTEMPTED ON INVALID %1 VALUE. *** SYSTEM FATAL MESSAGE 6048 (XQFNC1) 6048.8 ARC COSINE FUNCTION ATTEMPTED ON INVALID %1 VALUE. *** SYSTEM FATAL MESSAGE 6049 (XQFNC4) 6049.0 NON - CHARACTER CONSTANT/VARIABLE FOUND, WHERE CHARACTER CONSTANT/VARIABLE EXPECTED IN FUNCTION INDEXSTR. *** USER WARNING MESSAGE 6050 6050.0 TH E ATTEMPT TO WRITE VALUE INTO /SYSTEM/ CELL %1 HAS FAILED USER INFORMATION: THE SYSTEM CELL NUMBER IS OUTSIDE THE VALID RANGE. THE %2 ATTEMPT IS IGNORED. *** USER WARNING MESSAGE 6050 6050.1 THE ATTEMPT TO READ VALUE FROM /SYSTEM/ CELL %1 HAS FAILED USER INFORMATION: THE SYSTEM CELL NUMBER IS OUTSIDE THE VALID RANGE. THE %2 ATTEMPT IS IGNORED. *** USER WARNING MESSAGE 6051 6051.0 THE ATTEMPT TO TURN ON DIAG %1 HAS FAILED

372 USER INFORMA TION: THE DIAG REQUESTED IS OUTSIDE THE VALID RANGE OF DIAGS. THE %2 ATTEMPT IS IGNORED. *** USER WARNING MESSAGE 6051 (XQFNC3) 6051.1 THE ATTEMPT TO TURN OFF DIAG %1 HAS FAILED USER INFORMATION: THE DIAG REQUESTED IS OUTSIDE THE VALID RANGE OF DIAGS. THE %2 ATTEMPT IS IGNORED. *** USER WARNING MESSAGE 6052 6052.0 INVALID DIAG WORD WRITE REQUEST FOR DIAG WORD %1 USER INFORMATION: ONLY 2 DIAG WORDS EXIST IN THE PROGRAM WO RD 1 DIAGS 1 THROUGH 32 (ASSUMED WHEN ERROR - OCCURS) - DIAGS 33 THROUGH 64 WORD 2 *** USER WARNING MESSAGE 6052 (XQFNC4) 6052.1 INVALID DIAG WORD READ REQUEST FOR DIAG WORD %1 USER INFORMATION: ONLY 2 DIAG WORDS EXIST IN THE PROGRAM - DI AGS 1 THROUGH 32 (ASSUMED WHEN ERROR WORD 1 OCCURS) WORD 2 - DIAGS 33 THROUGH 64 *** SYSTEM FATAL MESSAGE 6059 (DIOMSG) 6059.0 NO ERROR MESSAGE EXISTS FOR DIOMSG INTERNAL CODE NUMBER %1 CALLED FROM %2 *** USER FATAL MESSAGE 6060 (DBC) 6060.0 *** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 DATA BASE UNIT %3 IS OUT OF RANGE. *** USER WARNING MESSAGE 6061 (DBC) 6061.0 *** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 DATA BASE %3 NOT OPENED, NO ACTION TAKEN. *** USER WARNING MESSAGE 6061 (DBC) 6061.1 *** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 DATA BASE %3 OPENED FOR READONLY, NO ACTION TAKEN. *** USER WARNING MESSAGE 6061 (DBC) 6061.2 *** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 THE FOLLOWING LOGICAL FIL E WAS LEFT OPEN AT DATABASE CLOSE, FORCE CLOSING %3 *** USER WARNING MESSAGE 6061 (DBC) 6061.3 *** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 THE FOLLOWING LOGICAL FILE WAS OPEN AT THE TIME A PURGE WAS REQUESTED NO PURGE ACTION WAS TAKEN FOR LOG ICAL FILE %3

373 *** SYSTEM FATAL ERROR 6062 (DBC) 6062.0 *** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 BLOCK REQUEST FROM DATA BASE UNIT %3, WHICH IS CLOSED. *** SYSTEM FATAL ERROR 6062 (DBC) 6062.1 *** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 BLOCK %3 REQUESTED FROM DATA BASE UNIT %4, WHICH IS OPEN FOR READONLY. *** SYSTEM FATAL ERROR 6062 (DBC) 6062.2 *** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 INSUFFICIENT SPACE ALLOCATED FOR DATA BA SE UNIT %3. *** SYSTEM FATAL ERROR 6062 (DBC) 6062.3 *** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 OVERFLOW OF DICTIONARY PRIMARY INDEX FOR DATA BASE UNIT %3. User information: Try adding a RECL keyword to the ASSIGN DBC card with a value greater than the default of 1024. *** SYSTEM FATAL ERROR 6062 (DBC) 6062.4 *** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 BUFFER LOCKING PROBLEMS ON POOL FOR DATA BASE UNIT %3, BLOCK %4 POSSIBLE MULTIPLE LOGICAL FILES ASSIGNED TO THE SAME D ATA RELATION. *** SYSTEM FATAL ERROR 6062 (DBC) 6062.5 *** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 FREE BUFFER POOL SPACE EXHAUSTED, REDUCE NUMBER OF LOGICAL FILES OR INCREASE SPACE. *** SYSTEM FATAL ERROR 6062 (DBC) 6062.6 *** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 LOGIC ERROR, DICTIONARY PRIMARY BLOCK ON DEAD CHAIN FOR DATA BASE %3. *** SYSTEM FATAL ERROR 6062 (DBC) 6062.7 *** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 UNABLE TO FIND ENTRY %3 ON SI BLOCK %4, W HICH HAD BEEN PREVIOUSLY FOUND. DISK ERROR OR MEMORY OVER WRITE ASSUMED. *** SYSTEM FATAL ERROR 6062 (DBC) 6062.8 *** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 UNABLE TO FIND ENTRY %3 ON PI BLOCK %4, WHICH HAD BEEN PREVIOUSLY FOUND. DISK ERROR OR MEMORY OVER WRITE ASSUMED. *** SYSTEM FATAL ERROR 6062 (DBC) 6062.9 *** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2

374 PROGRAMMING ERROR. LENGTH OF DICTIONARY ENTRIES CHANGED, BUT CLOSGR NOT INFORMED. *** SYSTEM FATAL ERROR 6062 (DBC) 6062.10 *** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 DICTIONARY OR DICTIONARY NAME FOR FILE %3 CORRUPTED. UNABLE TO CLOSE DATA BLOCK. *** SYSTEM FATAL ERROR 6062 (DBC) 6062.11 *** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 LOGICAL DATA BASE %3 IS MISSING DDL WITH SWAP CONDITION %4. *** SYSTEM FATAL ERROR 6062 (DBC) 6062.12 *** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 LOGICAL DATA BASE %3 IS MISSING THE BLOCK NUMBER FOR DDL VERSION %4. *** SYSTEM FATAL ERROR 6062 (DBC) 6062.13 *** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 OBJECT %3 ENTRY LENGTH AND DATA DEFINITION IS INCONSISTENT FOR HETEROGENOUS OPERATIONS. TRANSMIT AND RECEIVE MUST BE USED TO MIGRATE XDB BETWEEN PLATFORMS. *** SYSTEM WARNING MESSAGE 6063 (DBCMSG) 6063.0 NO ERROR MESSAGE EXISTS FOR DBCMSG INTERNAL CODE NUMBER %1 CALLED FROM %2. *** USER WARNING MESSAGE 6064 (DBC) 6064.0 *** DBCMSG WARNING MESSAGE %1 FROM SUBROUTINE %2 %3 ELEMENT %4 HAS BEEN UPDATED. *** SYSTEM WARNING MESSAGE 6064 (DBC) 6064.1 *** DBCMSG WARNING MESSAGE %1 FROM SUBROUTINE %2 %3 IS AN INVALID OPTION OR KEYWORD. *** SYSTEM WARNING MESSAGE 6064 (DBC) 6064.2 *** DBCMSG WARNING MESSAGE %1 FROM SUBROUTINE %2 FORTRAN LOGICAL UNIT %3 HAS NOT BEEN ASSIGNED. *** SYSTEM WARNING MESSAGE 6064 (DBC) 6064.3 *** DBCMSG WARNING MESSAGE %1 FROM SUBROUTINE %2 FORTRAN LOGICAL UNIT %3 IS NOT DEFINED AS A DBC MODULE DATA BASE UNIT. *** SYSTEM WARNING ME SSAGE 6064 (DBC) 6064.4 *** DBCMSG WARNING MESSAGE %1 FROM SUBROUTINE %2 %3 PROPERTY %4 HAS BEEN UPDATED. *** SYSTEM WARNING MESSAGE 6064 (DBC) 6064.5 *** DBCMSG WARNING MESSAGE %1 FROM SUBROUTINE %2 COORDINATE SYSTEM TRANSFORMATION %3 HAS BEEN UPDATED.

375 *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.0 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 UNABLE TO OPEN OUTPUT RELATION %3 RETURN CODE =%4. ) *** SYSTEM WARNING MESSAGE 6065 (DBC 6065.1 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 PREMATURE END OF FILE ENCOUNTERED READING ECT. *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.2 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 ELEMENT %3 GRID POSITION %4 CONTAINS AN INVALID INTERNAL INDEX. *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.3 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 MISSING %3 LOGICAL FILE %4 FOR SEID %5, DBSET %6. *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.4 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 BAD TRAILER FOR %3 LOGICAL FILE %4 FOR SEID %5, DBSET %6. *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.5 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 INCONSISTENT GEOMETRY TRAILERS DETECTED FOR SEID %3, DBSET %4. *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.6 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 INSUFFICIENT MEMORY TO PROCESS RELATIONAL REQUIREMENTS. *** SYSTEM WARNING MES SAGE 6065 (DBC) 6065.7 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 OPEN FAILURE FOR %3 LOGICAL FILE %4 FOR SEID %5, DBSET %6. *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.8 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 PREMATURE EOF FOR %3 LOGICAL FILE %4 FOR SEID %5, DBSET %6. *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.9 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 PREMATURE EOR FOR %3 LOGICAL FILE %4 FOR SEID %5, DBSET %6. *** SYSTEM WARNING M ESSAGE 6065 (DBC) 6065.10 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 DATA BASE PURGE PROBLEM FOR RELATION %3 RETURN CODE = %4. *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.11 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 DATA BASE WRITE RELATION PROBLEM FOR %3 RETURN CODE = %4.

376 *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.12 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 UNABLE TO OPEN INPUT RELATION %3 RETURN CODE = %4. *** SYSTEM WARNING MESSAGE 606 5 (DBC) 6065.13 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 SEQUENTIAL READ PROBLEMS FOR RELATION %3 RETURN FLAGS = %4. *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.14 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 ELEMENT %3 WAS A %4 AND IS CURRENTLY A %5 UPDATE MODE DOES NOT ALLOW FOR ELEMENTS TO CHANGE TYPES. *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.15 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 MEMORY LOAD PROBLEM FOR %3 FOR SEID %4, DBSET %5. *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.16 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 LIST ALIGNMENT PROBLEMS PROCESSING %3 FOR SEID %4, DBSET %5. *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.17 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 EXTERNAL GRID ID %3 DOES NOT MEET UPDATE ASSUMPTIONS, CHECK MODEL BEFORE PROCEEDING. *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.18 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 AT CODE DETECTED, WANTED %3, INVALID OFP FILE FORM ENCOUNTERED %4. *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.19 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 SOLUTION APPROACH CODE %3 IS NOT SUPPORTED. *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.20 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 DATA BASE READ RELATION PROBLEM FOR %3 RETURN CODE = %4. *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.21 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 OUTPUT LIST SYNCHRONIZATION PROBLEM FOR %3 VALUE = %4, POSITION = %5. *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.22 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 SORT - 2 STATIC SOLUTION RECOVERY IS NOT SUPPORTED. *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.23 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2

377 FORM UPDATE FOR RELATION %3 INVALID, OLD FORM %4 NEW FORM %5. *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.24 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 INVALID MODE DETECTED FOR OPTION %3, MODE = %4. *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.25 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 LIST AREA EXCEEDED, CURRENT SIZE IS 500 TERMS. *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.26 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 CONFLICT DETECTED WITH SEID AS PARAMETER AND PATH QUALIFIER PARAMETER IS %3, PATH QUALIFIER IS %4. *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.27 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 RELATION %3 HAS LENGTHENED FROM ASSUMED DEFINITION. *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.28 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 EXTERNAL ELEMENT IDENTIFICATION %3 CAN NOT BE LOCATED IN EQEXIN TABLE. *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.29 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 P - ELEMENT TYPE %3 IS UNKNOWN. *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.30 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 - ELEMENT TYPE %3 LENGTH HAS CHANGED ASSUMED VALUE. P *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.31 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 CONVECTIVE COORDINATE SYSTEMS ARE NOT SUPPORTED. *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.32 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 AN UNKNOWN ELEMENT TYP E HAS BEEN ENCOUNTERED. *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.33 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 ELEMENT %3 WAS PREVIOUSLY %4 AND IS CURRENTLY A %5 THE DBC MODULES ASSUMPTIONS ARE UNIQUE ELEMENT IDENTIFICATIONS WITHIN A SUPERE LEMENT OR RESIDUAL STRUCTURE. *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.34 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 OUTPUT LIST PROCESSING IS NOT SUPPORTED FOR ACCESS APPROACH %3.

378 *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.35 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 31 BIT ACCESS KEY WILL BE EXCEEDED, GRID/ELEMENT INDEX %3 QUALIFIER FACTOR %4. USER ACTION: SUPPLY PARAM,DBCDIAG,4 TO DETERMINE DBC TRANSLATIONAL FAILURE POINT. THEN CONTACT NX NASTRAN REPRESENTATIVE FOR PO SSIBLE AVOIDANCE. *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.36 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 OUTPUT LIST DOES NOT MATCH EXISTING IN THE DATABASE, MERGE/RESTART OPERATION IMPOSSIBLE. *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.37 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 THE CURRENT OUTPUT LIST LENGTH =%3 EXCEEDS PRESET LIST FACTOR OF %4. USER ACTION: CHECK RC FILE FOR DBCFACT (SYSTEM(274)=1) USING PRE V70.5 TRANSLATION CONVENTIONS. *** SYSTEM WARNING MESSAGE 6065 (DBC) 65.38 60 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 ELEMENT %3, SIL %4, CAN NOT BE LOCATED IN CONNECTION LIST, ELEMENT IGNORED. *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.39 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 THE AEROELASTIC CONFIGURATION NAME %3 CAN NOT BE RESOLVED. *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.40 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 THE AEROELASTIC CONFIGURATION NAME %3 DID NOT M ATCH PREVIOUSLY STORED AT PATH %4. *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.41 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 THE MATRICES SUPPLIED DO NOT HAVE CONFORMABLE SIZES; ROWS COLUMNS OR PRECISION. *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.42 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 MATRIX ROW CONSISTENCY CHECK FALUIRE; MATRIX %3 TABLE %4. *** SYSTEM WARNING MESSAGE 6065 (DBC) 6065.43 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 MATRIX COLUMN CONSISTENCY CHECK FALUIRE; MATRIX %3 TABLE %4. *** SYSTEM WARNING MESSAGE 6066 (DBC) 6066.0

379 *** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2 THE DBC MODULE HAS BEEN TERMINATED BECAUSE OF THE ABOVE FATAL DBC ERROR. USER INFORMATION: SUBSEQUENT DBC CALLS WILL NOT BE EXECUTED, AND THE DATABASE CONVERSION IS INCOMPLETE. *** USER FATAL MESSAGE 6067 (IFS3P) 6067.0 MAXIMUM LIMIT OF 40 PLIES EXCEEDED ON THE PSOLIDL BULK DATA ENTRY PID = %1 USER ACTION: CHECK AND MODIFY THE PSOLIDL BULK DATA ENTRY *** SYSTEM FATAL MESSAGE 6069 (LFBSS) 6069.0 SYMMETRIC LEFT HANDED FBS IS CALLED TO SOLVE A COMPLEX SINGLE OR DOUBLE PRECISION SYSTEM WITH CHOLESKY FACTOR System information: This option is not supported. *** SYSTEM FATAL MESSAGE 60 70 (LFBSS) 6070.0 ERROR IN READING THE FACTOR IN SYMMETRIC LEFT HANDED - FBS *** SYSTEM FATAL MESSAGE 6072 (LFBSU) 6072.0 INCORRECT PIVOTING INSTRUCTIONS IN UNSYMMETRIC FACTOR DURING A LEFT - HANDED FBS System information: See the NX NASTRAN Numerical Methods User's Guide. *** SYSTEM FATAL MESSAGE 6073 (LFBSU) 6073.0 ERROR IN READING THE FACTOR IN UNSYMMETRIC LEFT - HANDED FBS *** SYSTEM FATAL MESSAGE 6074 (LFBTIM) 6074.0 ERROR IN READING THE FACTOR IN LEFT - HAN DED FBS System information: See the NX NASTRAN Numerical Methods User's Guide. *** USER WARNING MESSAGE 6080 (TMALOC) 6080.0 THE TIMING CONSTANTS DATA BLOCK TIMEBLK NOT FOUND ON THE DELIVERY DATABASE FOR: MACHINE = %1 CONFIG = %2 OPERASYS = %3 OPERALEV = %4 SUBMODEL= %5 LOADING DEFAULT TIMING CONSTANTS DATA BLOCK FOR: MACHINE = %6 CONFIG = %7 OPERASYS = %8 OPERALEV = %9 SUBMODEL= %10 MODULE TIMING ESTIMATES INACCURATE AND MAY CAUSE INEFFICIENT JOB EXECUT ION USER ACTION: ADD TIMEBLK TO DELIVERY FILE OR USE NASTRAN STATEMENT TO SPECIFY THE MACHINE (SEE CONFIGURATION AND OPERATION GUIDE FOR THE

380 MACHINE ). *** USER WARNING MESSAGE 6080 (TMALOC) 6080.1 D ON THE TIMING CONSTANTS DATA BLOCK TIMEBLK NOT FOUN THE DELIVERY DATABASE FOR: MACHINE = %1 CONFIG = %2 OPERASYS = %3 OPERALEV = %4 SUBMODEL= %5 LOADING DEFAULT TIMING CONSTANTS DATA BLOCK FOR: MACHINE = %6 CONFIG = %7 OPERASYS = %8 OPERALEV = %9 SUBMODEL= %10 MODULE TIMING ESTIMATES INACCURATE AND MAY CAUSE INEFFICIENT JOB EXECUTION USER ACTION: ADD TIMEBLK TO DELIVERY FILE OR USE THE EMAS STATEMENT TO SPECIFY THE MACHINE (SEE MSC.EMAS INSTALLATION PROCEDURE). *** USER WARNING MESSAGE 6080 (SETKRN) 6080.2 THE TIMING CONSTANTS DATA BLOCK T IMEBLK NOT FOUND ON THE DELIVERY DATABASE FOR: MACHINE = %1 CONFIG = %2 OPERASYS = %3 OPERALEV = %4 SUBMODEL = %5 ZERO TIMING CONSTANTS BEING USED MODULE TIMING ESTIMATES INACCURATE AND MAY CAUSE INEFFICIENT JOB EXECUTION USER ACTION: ADD TIMEBLK TO DE LIVERY FILE OR USE NASTRAN STATEMENT TO SPECIFY THE MACHINE (SEE CONFIGURATION AND OPERATION GUIDE FOR THE MACHINE). *** USER WARNING MESSAGE 6080 (SETKRN) 6080.3 THE TIMING CONSTANTS DATA BLOCK TIMEBLK NOT FOUND ON THE DELIVERY DATABASE FOR: MACHINE = %1 CONFIG = %2 OPERASYS = %3 OPERALEV = %4 SUBMODEL = %5 ZERO TIMING CONSTANTS BEING USED MODULE TIMING ESTIMATES INACCURATE AND MAY CAUSE INEFFICIENT JOB EXECUTION USER ACTION: ADD TIMEBLK TO DELIVERY FILE OR USE THE EMAS STATEMENT TO SPECIFY THE MACHINE (SEE MSC.EMAS INSTALLATION PROCEDURE). *** USER WARNING MESSAGE 6080 (SETKRN) 6080.4 THE TIMING CONSTANTS DATA BLOCK TIMEBLK NOT FOUND ON THE DELIVERY DATABASE FOR: MACHINE = %1 CONFIG = %2 OPERASYS = %3 OPERALEV = %4 SUBMODEL = %5 AN OLD VERSION TIMING CONSTANTS BEING USED MODULE TIMING ESTIMATES INACCURATE AND MAY CAUSE INEFFICIENT JOB EXECUTION

381 USER ACTION: ADD TIMEBLK TO DELIVERY FILE OR USE THE EMAS STATEMENT TO SPECIFY THE MACHINE HE (SEE CONFIGURATION AND OPERATION GUIDE FOR T MACHINE). *** USER FATAL MESSAGE 6081 (TIMTS3) 6081.0 VALUE OF P2 CANNOT BE LESS THAN 64 *** USER FATAL MESSAGE 6082 (TIMTS7) 6082.0 THE RETURNED TIME NEEDED TO DO THE TASK CANNOT BE EQUAL TO THE VALUE ZERO. USER ACTION: INCREASE THE VALUE OF P1 FOR TIMTS7 *** USER FATAL MESSAGE 6082 (TIMTS3) 6082.1 THE RETURNED TIME NEEDED TO DO THE TASK CANNOT BE EQUAL TO THE VALUE ZERO. USER ACTION: INCREASE THE VALUE OF P1 FOR TIMTS3 *** USER FATAL MESSAGE 6083 (TIMTS4) 6083.0 THE RETURNED TIME NEEDED TO DO THE TASK CANNOT BE EQUAL TO THE VALUE ZERO. USER ACTION: INCREASE THE VALUE OF P1 FOR TIMTS4 *** SYSTEM FATAL MESSAGE 6084 (TIMTS5) 6084.0 ERROR IN MPYAD METHOD SELECTION, MPYAD CALLED FORM WITHIN TIMTS5 USER ACTION: EXECUTION OF TIMTS5 IS OPTIONAL AND CAN BE DELETED FROM THE TIMETEST RUN *** USER FATAL MESSAGE 6127 6127.0 *** MAT2, MAT9 OR MAT11 CARD MAY NOT BE COMBINED WITH NLELAST TYPE ON MATS1. *** USER FATAL MESSAGE 6133 (DFMNRS/D) 6133.0 SINGULAR MATRIX IN SPARSE DECOMPOSITION AT ROW = %1 USER ACTION: CHECK MODEL User information: This message is often followed by UFM 4645, UWM 4646, or UWM 4648. *** USER FATAL MESSAGE 6133 6133.1 SINGULAR MATRIX IN SPARSE DECOMPOSITION USER ACTION: CHECK MODEL User information: This message is often followed by UFM 4645, UWM 4646, or UWM 4648. *** USER FATAL MESSAGE 6134 (DFMNRS/D) 6134.0 MATRIX IS NOT POSITIVE D EFINITE IN SPARSE DECOMPOSITION AT ROW = %1 USER ACTION: CHECK MODEL User information: This message is often followed by UFM 4645, UWM 4646, or UWM 4648. *** USER FATAL MESSAGE 6134 6134.1

382 MATRIX IS NOT POSITIVE DEFINITE IN SPARSE DECOMPOSITION USER ACTION: CHECK MODEL User information: This message may be issued if the FBS module is using a sparse method to solve factors which are not decomposed by the sparse method. This message can also be caused by a compatibility or database integrity problem. *** USER WARMING MESSAGE 6134 6134.2 MAT2 MID=%1 MATRIX IS NOT POSITIVE DEFINITE USER ACTION: CHECK MODEL *** USER WARNING/FATAL MESSAGE 6136 (DFMNRS/D) 6136.0 INSUFFICIENT CORE FOR NUMERIC PHASE OF SPARSE DECOMPOSITION. ION: INCREASE CORE BY %1 WORDS USER ACT *** USER WARNING/FATAL MESSAGE 6136 (DFMNRS/D) 6136.1 INSUFFICIENT CORE FOR NUMERIC PHASE OF SPARSE DECOMPOSITION. USER ACTION: INCREASE CORE BY AN ESTIMATED %1 K WORDS. WARNING: THE ABOVE NUMBER IS ONLY AN ESTIMATE, THE ACTUAL CORE SIZE NEEDED MAY BE HIGHER. *** USER WARNING/FATAL MESSAGE 6136 (DFMSAP) 6136.3 INSUFFICIENT CORE FOR SYMBOLIC PHASE OF SPARSE DECOMPOSITION. USER ACTION: INCREASE CORE BY %1 K WORDS. User information: If this message is issued in the symbolic phase, the memory estimate is not necessarily conservative and even more memory may be required (although this estimate is fairly accurate for Version 68). Also, the memory increase required i s only for the symbolic phase. It is not unusual for the decomposition phase to require more memory than the symbolic phase. To increase the chances for a successful run, increase the memory even more than the amount indicated in this message. After th e run is complete, determine the amount of memory actually used and use this as a guideline for similar runs in the future. The user information message is written if SYSTEM(166) = 1 (that is, if there is not enough memory for sparse decomposition, then switch to regular decomposition). *** USER WARNING/FATAL MESSAGE 6136 6136.4 INSUFFICIENT CORE FOR NUMERIC PHASE OF SPARSE DECOMPOSITION. USER ACTION: INCREASE CORE BY %1 K WORDS *** USER WARNING/FATAL MESSAGE 6136 6136.5 INSUFFICIENT CORE FOR NUMERIC PHASE OF SPARSE DECOMPOSITION.

383 USER ACTION: INCREASE CORE BY AN ESTIMATED %1 K WORDS BUT NOTE THAT IT IS ONLY AN ESTIMATE AND THE ACTUAL CORE SIZE NEEDED MAY BE HIGHER. *** USER INFORMATION MESSAGE 6137 (DFMN) 6137.0 INPUT MATRIX TO DECOMPOSITION HAS %1 SINGULARITIES. SEE FOLLOWING MESSAGES FOR DETAILS. *** USER WARNING MESSAGE 6137 6137.1 INPUT MATRIX IS RANK DEFICIENT, RANK = %1. USER ACTION: CHECK MODEL User information: One of your matrices is singular. See the NX NASTRAN Numerical Methods User's Guide. for a discussion of singularity. *** USER INFORMATION MESSAGE 6137 (FRDSMP) 6137.2 INPUT MATRIX TO DECOMPOSITION IS SINGULAR AT COLUMN %1. *** USER FATAL MESSAGE 6138 (DFMSB) 6138.0 INSUFFICIENT CORE FOR SPARSE FBS USER ACTION: INCREASE CORE BY %1 WORDS User information: See UFM 6136. *** USER FATAL MESSAGE 6138 (UFBSS) 6138.1 INSUFFICIENT CORE FOR SPARSE UNSYMMETRIC FBS USER ACTION: INCREA SE CORE BY %1 WORDS *** USER INFORMATION MESSAGE 6142 (FA2) 6142.0 THE K OR KE METHOD OF FLUTTER ANALYSIS HAS FOUND A ROOT THAT HAS NO PHYSICAL INTERPRETATION. - G AND V - F NOTE THAT TO OBTAIN PHYSICALLY MEANINGFUL V PLOTS, XMIN,XMAX,YMIN,YMAX VALUES MUST BE EXPLICITLY SET IN THIS CASE. *** SYSTEM FATAL MESSAGE 6143 (DUPART) 6143.0 THE SIZES OF THE INPUT MATRICES AND THE DOF SETS ARE INCOMPATIBLE. SPECIFICALLY: *** SYSTEM FATAL MESSAGE 6144 (PARTN1) 6144.0 CES AND PARTITIONING THE SIZES OF THE INPUT MATRI VECTORS ARE INCOMPATIBLE. SPECIFICALLY: *** SYSTEM FATAL MESSAGE 6146 6146.0 ELEMENT TYPE =%1 IS NOT SUPPORTED IN ACOUSTIC ANALYSIS. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: GP5 MODULE FAILED TO RECOGNIZE THIS ELEMENT TYPE CHECK GPTABD ROUTINE. *** SYSTEM FATAL MESSAGE 6146, (GP0B), 6146.15

384 ELEMENT TYPE =%1 IS NOT SUPPORTED IN P - ELEMENT ANALYSIS. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOM ER SUPPORT. PROGRAMMER INFORMATION: GP0 MODULE FAILED TO RECOGNIZE THIS ELEMENT TYPE CHECK GPTABD ROUTINE. *** SYSTEM FATAL MESSAGE 6147 (GP5I), 6147.0 AN INCORRECT ELEMENT FACE CONNECTION TABLE HAS BEEN CREATED. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: ELEMENT FACE CONNECTION TABLE BUILDING PROCEDURE FAILED IN GP5I ROUTINE. *** SYSTEM FATAL MESSAGE 6147 6147.1 AN INCORRECT ELEMENT FACE CONNECTION TABLE HAS BEEN CREATED. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: ELEMENT FACE CONNECTION TABLE BUILDING PROCEDURE FAILED IN GP5A ROUTINE. *** USER WARNING MESSAGE 6148, 6148.0 NO ACOUSTIC ELEMENTS FOUND IN THE BULK DATA. USER A CTION: CHECK PSOLID DATA, MAKE SURE FIELD 8 CONTAINS BCD WORD (PFLUID) FOR SELECTED ACOUSTIC ELEMENTS. *** USER FATAL MESSAGE 6149, 6149.0 THREE OR MORE FLUID GRID POINTS HAVE IDENTICAL COORDINATES. USER ACTION: CHECK GRIDS AND/OR SET1 BULK DATA ENTRIES WHICH ARE REFERENCED ON PANEL OR ACMODL ENTRIES. *** USER FATAL MESSAGE 6150, 6150.0 FOUND GRID POINTS WITH IDENTICAL COORDINATES, WHICH ARE NOT CLASSIFIED AS FLUID OR STRUCTURAL GRIDS. USER ACTION: CHECK GRIDS AND/OR SET1 BULK DATA ENTRIES WHICH ARE REFERENCED ON PANEL OR ACMODL ENTRIES. *** USER WARNING MESSAGE 6151, 6151.0 ACOUSTIC COUPLING MATRIX WILL NOT BE CREATED FOR FACE =%1 OF ELEMENT ID =%2 ,BECAUSE ITS FLUID GRID POINTS DO NOT HAVE CORRESPONDING STRUCTURAL GRID POINTS.

385 USER ACTION: IF COUPLING IS DESIRED, THEN CHECK GRID POINT DATA. *** USER WARNING MESSAGE 6151, 6151.1 ACOUSTIC COUPLING MATRIX WILL NOT BE CREATED FOR FACE =%1 OF ELEMENT ID =%2 ,BECAUSE ALL ITS STRUCTURAL GRID POINTS DO NOT LIE INSIDE THE FLUID BOUNDARY POINTS. USER ACTION: IF COUPLING IS DESIRED, THEN CHECK GRID POINT DATA. *** USER WARNING MESSAGE 6151, 6151.2 SET1/SET3 ID =%1 IS NOT UNIQUE. USER ACTION: MAKE ALL SET1/SET3 ID NUMBERS UNIQUE. *** USER WARNING MESSAGE 6151, 6151.3 ACOUSTIC COUPLING MATRIX WILL NOT BE CREATED FOR FACE =%1 OF ELEMENT ID =%2 ,BECAUSE ITS FLUID GRID POINTS DO NOT HAVE CORRESPONDING STRUCTURAL GRID POINTS. USER ACTION: IF COUPLING IS DESIRED, THEN CHECK GRID POINT DATA. *** USER WARNING MESSAGE 6152, 6152.0 ACOUSTIC COUPLING MATRIX IS NOT CREATED FOR THIS MODEL. USER ACTION: IF COUPLING IS DESIRED, THEN CHECK INPUT DATA. *** USER FATAL MESSAGE 6153. 6153.0 NO FLUID OR STRUCTURAL GRIDS ARE REFERENCED ON SET1 ENTRIES. USER ACTION: CHECK SET1 ENTRIES REFERENCED BY ACMODL ENTRIES. *** SYSTEM FATAL MESSAGE 6154. 6154.0 GRID ID = %1 DOES NOT EXIST IN THE BGPDT TABLE. USER ACTION : CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: CHECK INTERNAL GRID ID TO EXTERNAL GRID ID CONVERSION LOGIC IN %2 ROUTINE. *** SYSTEM FATAL MESSAGE 6154. 6154.2 GRID ID =%1 DOES NOT EXIST IN THE EQEXIN TABLE. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: CHECK INTERNAL GRID ID TO EXTERNAL GRID ID CONVERSION LOGIC IN GP5B ROUTINE. *** USER FATAL MESSAGE 6155. 6155.0

386 SET1/SET3 ID =%1 DOES NOT EXIST. CK ALL SET1/SET3 DATA REFERENCED BY USER ACTION: CHE PANEL ENTRIES. *** USER FATAL MESSAGE 6155. 6155.1 SET1 ID =%1 DOES NOT EXIST. USER ACTION: CHECK ALL SET1 DATA REFERENCED BY ACMODL ENTRIES. *** USER FATAL MESSAGE 6156, 6156.0 THERE ARE NO FLUID ELEMENTS IN CONTACT WITH STRUCTURAL ELEMENTS. USER ACTION: CHECK INPUT DATA. *** SYSTEM FATAL MESSAGE 6157, 6157.0 THE THIRD OUTPUT DATA BLOCK OF GP5 CANNOT NOT BE PURGED WHEN MULTIPLE PANEL CAPABILITY IS REQUESTED. *** USER FATAL MESSAGE 6158. 6158.0 A SET1 OR SET3 BULK DATA ENTRY WAS NOT SUPPLIED. *** USER FATAL MESSAGE 6158. 6158.1 A SET1 BULK DATA ENTRY WAS NOT SUPPLIED. *** SYSTEM FATAL MESSAGE 6159 (GP5DA), 6159.0 INTERMEDIATE FACE SORTING PROCESS FAILED. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6160 (GP5ED), 6160.0 ELEMENT ID =%1 HAS A FACE ON THE FLUID/STRUCTURE BOUNDARY WHICH SUGGESTS THAT GRID9 IS NOT WELL DEFINED. THE GEOMETRY LIES ON THE SAME PLANE AS THE FACE. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: CHECK THE PROCEDURE OBTAINING GRID9. *** USER FATAL MESSAGE 6161, 6161.0 PANEL DATA DOES NOT EXIST. USER ACTION: CHECK INPUT DATA. *** USER FATAL MESSAGE 6162, 6162.0 GRID ID =%1 REFERENCED THROUGH (ALL) OPTION ON AN ACMODL ENTRY DOES NOT LIE ON THE FLUID/STRUCTURE BOUNDARY. *** USER WARNING MESSAGE 6163, 6163.0 THERE ARE NO ELEMENT FACES CORRESPONDING TO THE PANEL NAME =%1 USER ACTION: CHECK GRID IDS DEFINED FOR THIS PANEL.

387 *** USER FATAL MESSAGE 6164, 6164.0 THERE ARE NO FLUID ELEMENTS IN CONTACT WITH STRUCTURAL ELEMENTS. FOR PANEL ID = %1 USER ACTION: CHECK PANEL BULK DATA ENTRY. *** USER FATAL MESSAGE 6165 (MODEPT) 6165.0 THERE EXISTS A DIFFERENT NUMBERS OF TERMS IN RESISTANCE REACTANCE AND WEIGHTING FUNCTION TABLES IDS = %1 RESPECTIVELY. *** USER FATAL MESSAGE 6167 (MODEPT) 6167.0 THE TABLEDI ID = %1 ENTRY REFERENCED BY A PACABS ENTRY IS NOT A TABLED1 ENTRY. USER INFORMATION: THE PACABS ENTRY SHOULD ONLY REFERENCE A TABLED1 ENTRY. *** USER FATAL MESSAGE 6168 (MODEPT) 6168.0 THE BULK DATA T ABLED1 ENTRIES, ID =%1 HAS NO ACCEPTABLE VALUES BELOW CUTOFF FREQUENCY. *** USER FATAL MESSAGE 6168 (MODEPT) 6168.1 THE BULK DATA TABLED1 ENTRIES, ID =%1 HAS NO ACCEPTABLE VALUES BELOW CUTOFF FREQUENCY. *** USER FATAL MESSAGE 6169, 6169.0 FOUND TWO OR MORE STRUCTURAL GRID POINTS WITH IDENTICAL COORDINATES WHICH LIE ON THE FLUID/STRUCTURE BOUNDARY. USER ACTION: CHECK GRIDS AND/OR SET1 CARDS WHICH BELONG TO PANEL OR ACMODL CARDS. *** USER WARNING MESSAGE 6170 (MODEPT) 6170.0 LEAST S QUARE FIT PROCESS HAS RESULTED IN A NEGATIVE MASS VALUE =%1 NO MASS MATRIX WILL BE GENERATED. *** USER WARNING MESSAGE 6170 (MODEPT) 6170.1 LEAST SQUARE FIT PROCESS HAS RESULTED IN A NEGATIVE DAMPING VALUE =%1 NO DAMPING MATRIX WILL BE GENERATED. *** USER WARNING MESSAGE 6170 (MODEPT) 6170.2 LEAST SQUARE FIT PROCESS HAS RESULTED IN A NEGATIVE STIFFNESS VALUE =%1 NO STIFFNESS MATRIX WILL BE GENERATED. *** USER FATAL MESSAGE 6171 (APD5) 6171.0 WRONG NUMBER OF WORDS OR ENTRY NOT FOUND FOR AEFACT ID = %1 ASSOCIATED WITH CAERO5 ID = %2 *** USER FATAL MESSAGE 6171 (APD4) 6171.1 WRONG NUMBER OF WORDS OR ENTRY NOT FOUND FOR AEFACT

388 ID = %1 ASSOCIATED WITH CAERO4 ID = %2 *** USER FATAL MESSAGE 6171 (APD3) 6171.2 WRONG NUMBER OF WORDS OR ENTRY NOT FOUND FOR AEFACT ID = %1 ASSOCIATED WITH CAERO3 ID = %2 *** USER FATAL MESSAGE 6171 (APD2) 6171.3 WRONG NUMBER OF WORDS OR ENTRY NOT FOUND FOR AEFACT ID = %1 ASSOCIATED WITH THE PAE RO2 ENTRY THAT IS REFERENCED BY CAERO2 ENTRY ID = %2 *** USER FATAL MESSAGE 6172 (APD5) 6172.0 THE NUMBER OF CAOCI ENTRIES ON PAERO5 ENTRY ID = %1 MUST EQUAL THE NUMBER OF STRIPS SPECIFIED ON CAERO5 ENTRY ID = %2 USER FATAL MESSAGE 6173. (EQD4D) *** 6173.0 PLATE ELEMENTS MAY NOT BE OFFSET UNLESS BOTH MID1 AND MID2 ARE SUPPLIED. IF OFFSETS ARE DESIRED FOR PLATES, SPECIFY MID1 AND MID2. TINY MODULUS MAY BE SUPPORTED IF DESIRED. User information: Offsets were specified on t he shell connection Bulk Data entry, CQUAD4, CTRIA3, CQUAD8, or CTRIA6, in field ZOFFS. Since offsets produce coupling between membrane and bending stiffness, then the PSHELL entry must include a specification of membrane and bending stiffness in fields MID1 and MID2, respectively. *** USER WARNING MESSAGE 6173. 6173.1 THE SPECIFICATION OF OFFSET VECTORS GIVES WRONG RESULTS IN SOLUTION SEQUENCES THAT COMPUTE DIFFERENTIAL STIFFNESS: LINEAR BUCKLING ANALYSIS PROVIDED IN SOLS 5, 16, 105, 200, AND GEOMETRIC NONLINEAR ANALYSIS PROVIDED IN SOLS 106, 129, 153, AND 159 WITH PARAMETER,LGDISP,1. *** USER FATAL MESSAGE 6173. 6173.2 THE SPECIFICATION OF OFFSET VECTORS GIVES WRONG RESULTS IN SOLUTION SEQUENCES LINEAR BUCKLING THAT COMPUTE DIFFERENTIAL STIFFNESS: ANALYSIS PROVIDED IN SOLS 5, 16, 105, 200, AND GEOMETRIC NONLINEAR ANALYSIS PROVIDED IN SOLS 106, 129, 153, AND 159 WITH PARAMETER,LGDISP,1. NOTE: An override capability is available through System Cell (463) = 1 which will allow the an alysis to continue with a differential stiffness that is computed with ZERO offset. *** USER WARNING MESSAGE 6173. 6173.3

389 *** THE SYSTEM CELL 463 HAS BEEN ACTIVATED *** THE DIFFERENTIAL STIFFNESS WILL BE COMPUTED WITH A ZERO OFFSET. NOTE: THE SPECIFICATION OF OFFSET VECTORS GIVES WRONG RESULTS IN SOLUTION SEQUENCES THAT COMPUTE DIFFERENTIAL STIFFNESS: LINEAR BUCKLING ANALYSIS PROVIDED IN SOLS 5, 16, 105, 200, AND GEOMETRIC NONLINEAR ANALYSIS PROVIDED IN SOLS 106, 129, 153, AND 159 WITH P ARAMETER,LGDISP,1. *** USER FATAL MESSAGE 6173. 6173.4 THE SPECIFICATION OF OFFSET VECTORS GIVES WRONG RESULTS IN SOLUTION SEQUENCES THAT COMPUTE DIFFERENTIAL STIFFNESS: LINEAR BUCKLING ANALYSIS PROVIDED IN SOLS 5, 16, 105, 200, AND GEOMETRIC NON LINEAR ANALYSIS PROVIDED IN SOLS 106, 129, 153, AND 159 WITH PARAMETER,LGDISP,1. NOTE: (1) An override capability is available through System Cell (463) = 1 which will allow the analysis to continue with a differential stiffness that is computed with ZERO offset. (2) The CTRIAR and CQUADR elements do support differential stiffness with shell offsets. However, the CTRIAR and CQUADR are not supported in geometric nonlinear analysis. The CTRIA3 and CQUAD4 elements can automatically be converted to CTR IAR and CQUADR through SYSTEM CELL (370) = 5. Be aware that loading conditions that generate follower forces should not be used with shell offset. Use PARAM,FOLLOWK,NO if follower boundary conditions are specified. More information is available in the remarks section of the Quick Reference Guide for CQUAD4 and CTRIA3. *** USER WARNING MESSAGE 6173. 6173.5 THE SPECIFICATION OF OFFSET VECTORS SHOULD NOT BE USED WITH LOADING CONDITIONS THAT GENERATE FOLLOWER FORCES. USE PARAM,FOLLOWK,NO R BOUNDARY IF FOLLOWE CONDITIONS ARE SPECIFIED. *** USER WARNING MESSAGE 6173 6173.6 *** SHELL ELEMENTS WITH OFFSET GIVE WRONG RESULTS IN LINEAR BUCKLING ANALYSIS PROVIDED IN SOLS 5, 16, 105, 200. RESULTS COMPUTED IN GEOMETRIC NONLINEAR

390 ANALYSIS (SOLS 106, 129, 153, AND 159 WITH PARAMETER,LGDISP,1) ARE CORRECT IF THE SOLUTION CONVERGES. NOTE: (1) AN ALTERNATIVE IS TO REMODEL WITHOUT USING SHELLS WITH OFFSET. (2) The CTRIAR and CQUADR elements do support differential stiffness with sh ell offsets. However, the CTRIAR and CQUADR are not supported in geometric nonlinear analysis. The CTRIA3 and CQUAD4 elements can automatically be converted to CTRIAR and CQUADR through SYSTEM CELL (370) = 5. *** USER FATAL MESSAGE 6174. 6174.0 *** BEAM ELEMENTS WITH OFFSET GIVE WRONG RESULTS WITH NONLINEAR SOLUTIONS 106/129 BECAUSE THE OFFSET VECTOR REMAINS PARALLEL TO ITS ORIGINAL ORIENTATION. NOTE: (1) REMODEL WITHOUT USING BEAMS WITH OFFSET. System Cell (463) = 1 which (2) An override capability is available through will allow the analysis to continue. The use of this System Cell in the context of a geometric nonlinear analysis with PARAM,LGDISP,1 may generate incorrect results. Loading conditions that generate follower forces should n ot be used with the System Cell (463). Use PARAM,FOLLOWK,NO if follower boundary conditions are specified. *** USER FATAL MESSAGE 6174. 6174.1 *** CQUAD4 ELEMENTS WITH OFFSET GIVE WRONG RESULTS WITH MATERIAL NONLINEAR SOLUTIONS 106/129 (MATS1,CRE EP) BECAUSE THE OFFSET VECTOR REMAINS PARALLEL TO ITS ORIGINAL ORIENTATION. NOTE: (1) REMODEL WITHOUT USING SHELLS WITH OFFSETS. *** USER FATAL MESSAGE 6174. 6174.2 *** CTRIA3 ELEMENTS WITH OFFSET GIVE WRONG RESULTS WITH MATERIAL NONLINEAR SOLUTIONS 106/129 (MATS1,CREEP) BECAUSE THE OFFSET VECTOR REMAINS PARALLEL TO ITS ORIGINAL ORIENTATION. NOTE: (1) REMODEL WITHOUT USING SHELLS WITH OFFSETS. QUAD4 ELEMENT WITH ID =%1 HAS AN INTERIOR ANGLE POSSIBLY GREATER THAN OR EQUAL

391 180 DEGREES. *** USER FATAL MESSAGE 6174. 6174.3 *** CQUAD4 ELEMENT %1 WITH OFFSET GIVE WRONG RESULTS WITH NONLINEAR SOLUTIONS (106/129) WHEN COMBINED WITH THERMAL LOADS. NOTE: (1) REMODEL WITHOUT USING SHELLS WITH OFFSETS. *** USER FATAL MESSAGE 6174. 6174.4 *** CTRIA3 ELEMENT %1 WITH OFFSET GIVE WRONG RESULTS WITH NONLINEAR SOLUTIONS (106/129) WHEN COMBINED WITH THERMAL LOADS. NOTE: (1) REMODEL WITHOUT USING SHELLS WITH OFFSETS. *** USER FATAL MESSAGE 6175 (ASGPRD) 6175.0 A TRIM VARIABLE WITH TRIM ID = %1, LABEL = %2 IS CONSTRAINED MORE THAN ONCE. USER ACTION: CHECK TRIM AND AELINK BULK DATA ENTRIES. *** USER FATAL MESSAGE 6176 (EQDRD) 6176.0 ZOFFS FOR QUADR ELEMENT ARE NOT SUPPORTED *** USER FATAL MESSAGE 6176 (ETRRD) 6176.1 ZOFFS FOR TRIAR ELEMENT ARE NOT SUPPORTED *** USER FATAL MESSAGE 6176. (TTRRD) 6176.2 ZOFF IS NOT SUPPORTED FOR TRIAR ELEMENT. *** USER FATAL MESSAGE 6177 (APD0) 6177.0 THE AEROS BULK DATA ENTRY, IN FIELD 3, ILLEGALLY REFERENCES A SPHERICAL OR CYLINDRICAL COORDINATE SYSTEM. *** USER FATAL MESSAGE 6177 (APD0) 6177.1 THE AERO AND AEROS BULK DATA ENTRIES, IN FIELD 2, SPHERICAL OR CYLINDRICAL ILLEGALLY REFERENCE A COORDINATE SYSTEM. *** USER FATAL MESSAGE 6177 (APD0) 6177.2 THE AERO BULK DATA ENTRY, IN FIELD 2, ILLEGALLY REFERENCES A SPHERICAL OR CYLINDRICAL COORDINATE SYSTEM. *** USER FATAL MESSAGE 6177 (APD0) 6177.3 THE AER OS BULK DATA ENTRY, IN FIELD 2, ILLEGALLY REFERENCES A SPHERICAL OR CYLINDRICAL COORDINATE SYSTEM. *** USER FATAL MESSAGE 6178 (APD0) 6178.0 AERO AND AEROS BULK DATA ENTRIES MUST REFER TO THE SAME COORDINATE SYSTEM ID FOR THE AERODYNAMIC COORDINATE SYSTEM.

392 *** USER FATAL MESSAGE 6179 (APD0) 6179.0 AERO AND AEROS BULK DATA ENTRIES MUST HAVE SAME SYMMETRY CONDITIONS. *** USER FATAL MESSAGE 6180 (APDCST) 6180.0 CAERO 1, 3, 4 OR 5 BULK DATA ENTRY %1 HAS A ZE RO PANEL SURFACE AREA. USER INFORMATION: X12 AND X43 ARE MEASURED ALONG THE X AXIS OF AERODYNAMIC COORDINATE SYSTEM. USER ACTION: CHECK THE COORDINATE DATA IN THIS ENTRY TOGETHER WITH THE AERODYNAMIC COORDINATE SYSTEM. *** USER FATAL MESSAGE 6181 (SMPYAD) 6181.0 THE LAST INPUT MATRIX MUST BE UNTRANSPOSED USER INFORMATION: THE TRANSPOSE FLAG PARAMETER CORRESPONDING TO THE LAST INPUT MATRIX IN THE SMPYAD MODULE SPECIFICATION IS NOT ZERO WHICH IS THE USER ACTION: ASSURE THAT THIS FLAG IS ZERO, DEFAULT *** USER FATAL MESSAGE 6182 (ADG) 6182.0 *** USER FATAL MESSAGE 6183 (MBAMG) 6183.0 IMPROPER MACH BOX CONTROL POINTS, SINGULAR MATRIX RESULTED *** USER FATAL MESSAGE 6184 (MBAMG) 6184.0 GENERATION OF BOXES FAILED WITH MACH BOX *** USER FATAL MESSAGE 6185 (PSTAMG) 6185.0 MACH NUMBER %1 WAS NOT FOUND IN THE PISTON THEORY ALPHA ARRAY *** USER INFORMATION MESSAGE 6186 (NCONVG) 6186.0 *** SOLUTION HAS CONVERGED *** *** USER INFORMATION MESSAGE 6187 (NCONVG) 6187.0 BISECTION METHOD IS ACTIVATED DUE TO LARGE INCREMENTAL ROTATIONS AT ITERATION NO. %1 *** USER INFORMATION MESSAGE 6187 (NCONVG) 6187.1 *** BISECTION METHOD IS NOW ACTIVATED *** FORMATION MESSAGE 6187 (NCONVG) *** USER IN 6187.2 *** BISECTION METHOD IS ACTIVATED BY LINE CONTACT. *** USER INFORMATION MESSAGE 6188 6188.0 *** INITIAL ARC LENGTH IS %1 User information: The initial arc - length is printed when the NLITER module is first executed and the arc<#0106>length method is used. A new arc - length is printed when the arc length changes due to bisection. It is also printed after a converged solution, when the arc length may change due to restoration after bisection, or due to the

393 DESITER field on the NLPCI entry. *** USER INFORMATION MESSAGE 6188 (NLITER) 6188.1 *** ARC LENGTH RATIO IS %1 *** USER INFORMATION MESSAGE 6189 (NL2CON) 6189.0 *** REPEAT ITERATION, STOPPING AT LOWEST ERROR User information: length increment has already This is issued when the time/load/arc - reached its minimum limit and the solution has not converged, though the maximum number of iterations has been performed. If the best iteration is not the last iteration, a reiteration i s done to obtain the best solution. *** USER INFORMATION MESSAGE 6189 (NCONVG) 6189.1 *** BEST ATTAINABLE SOLUTION HAS BEEN FOUND *** *** USER FATAL MESSAGE 6190 (NLITER) 6190.0 *** MAXIMUM NUMBER OF CONTROLLED INCREMENTS (MXINC) HAS BEEN EXCEEDED *** User information: - In the arc length control methods, the number of solution steps actually completed in a subcase is usually different from that specified by the user. Therefore, its limit is controlled by MXINC. No action is necessary if the solutions exceed the desired extent. Otherwise, increase the value of MXINC on the NLPCI entry. *** USER INFORMATION MESSAGE 6191 (NL2CON) 6191.0 *** EXIT FROM NLTRD2 DUE TO DIVERGING SOLUTION LIMIT *** User information: The solution has diverged twice consecutively during the iteration. Change the stiffness matrix update strategy (Method) or increase the divergence criterion value of MAXDIV on the NLPARM or TSTEPNL entry. Alternatively, increase NINC on the NLPARM entr y or decrease DT on the TSTEPNL entry. *** USER INFORMATION MESSAGE 6191 (NCONVG) 6191.1 *** FIRST DIVERGING SOLUTION *** *** USER INFORMATION MESSAGE 6191 (NCONVG) 6191.2 *** SECOND DIVERGING SOLUTION *** SYSTEM INFORMATION MESSAGE 6191 (NLTCON) *** 6191.3 *** EXIT FROM NLTRD DUE TO DIVERGING SOLUTION LIMIT *** System information: The solution has diverged twice consecutively during the iteration. Change the stiffness matrix update strategy (Method) or increase th e divergence criterion value of MAXDIV on the NLPARM or TSTEPNL entry. Alternatively, increase NINC on the NLPARM entry or decrease DT on the TSTEPNL entry. *** USER FATAL MESSAGE 6191 (NLTCON) 6191.4

394 *** EXIT FROM NLTRD DUE TO DIVERGING SOLUTIO N LIMIT ON FIRST TIME STEP *** *** USER INFORMATION MESSAGE 6192 6192.0 *** NO ROOT CASE HAS BEEN ENCOUNTERED *** User information: The quadratic equation which contains the load factor increment as the unknown variable does not have any real ro ots. A special algorithm specifically developed for this case will be automatically activated. *** USER INFORMATION MESSAGE 6193 (NL2CON) 6193.0 *** MAXIMUM NUMBER OF BISECTIONS OR MINIMUM TIME STEP HAS BEEN REACHED. User information: In nonlinear transient analysis, the minimum allowable time step has been reached. In nonlinear static analysis, with Newton's method, the minimum allowable load step has been reached or, with the - length method, the minimum allowable arc length has been reached. arc Change the stiffness matrix update strategy (METHOD) or increase the value of MAXBIS on the NLPARM or TSTEPNL entry. Alternatively, increase NINC on the NLPARM entry or decrease DT on the TSTEPNL entry. *** USER INFORMATION M ESSAGE 6193 (NCONVG) 6193.1 *** MAXIMUM NUMBER OF BISECTIONS OR MINIMUM LOAD STEP HAS BEEN REACHED. User information: In nonlinear transient analysis, the minimum allowable time step has been reached. In nonlinear static analysis, with Newton's method, the m inimum allowable load step has been reached or, with the - arc length method, the minimum allowable arc length has been reached. Change the stiffness matrix update strategy (METHOD) or increase the vely, value of MAXBIS on the NLPARM or TSTEPNL entry. Alternati increase NINC on the NLPARM entry or decrease DT on the TSTEPNL entry. *** USER INFORMATION MESSAGE 6193 6193.2 *** MAXIMUM NUMBER OF BISECTIONS OR MINIMUM ARC LENGTH HAS BEEN REACHED. User information: In nonlinear transient analysis, the minimum allowable time step has been reached. In nonlinear static analysis, with Newton's method, the minimum allowable load step has been reached or, with the arc - length method, the minimum allowable arc length has been reached. Change the stiffness matrix update strategy (METHOD) or increase the value of MAXBIS on the NLPARM or TSTEPNL entry. Alternatively, increase NINC on the NLPARM entry or decrease DT on the TSTEPNL entry. *** USER INFORMATION MESSAGE 6194 (NL2CON) 6194.0

395 *** STOPPED ITERATIONS DUE TO REACHING MAXIMUM ITERATION LIMIT WITHOUT CONVERGENCE *** User information: For insufficient time, increase the value on the TIME Executive Control statement. For maximum iterations, change the stiffness matrix update strat egy (METHOD) or increase the value of MAXITER on the NLPARM or TSTEPNL entry. *** USER INFORMATION MESSAGE 6194 6194.1 *** STOPPED ITERATIONS DUE TO INSUFFICIENT TIME REMAINING *** User information: For insufficient time, increase the value on the TIME Executive Control statement. For maximum iterations, change the stiffness matrix update strategy (METHOD) or increase the value of MAXITER on the NLPARM or TSTEPNL entry. *** USER WARNI NG MESSAGE 6194 (NLTCON) 6194.2 *** STOPPED ITERATIONS DUE TO REACHING MAXIMUM ITERATION LIMIT WITHOUT CONVERGENCE *** User information: For insufficient time, increase the value on the TIME Executive Control statement. For maximum iterations, change the stif fness matrix update strategy (METHOD) or increase the value of MAXITER on the NLPARM or TSTEPNL entry. *** USER WARNING MESSAGE 6195 (NLITER) 6195.0 - SOLUTION HAS REGRESSED TO AN EARLIER LOAD STEP. (BACK UP COEFFICIENT =%1) User information: This message is issued for the Arc - Length method (See NLPARM entry) only. Change the iteration strategy for the RIKS and MRIKS method. The program will automatically activate a different root selection procedure for the Crisfield method. * ** USER FATAL MESSAGE 6196 (NLITER) 6196.0 REGRESSION HAS OCCURRED WITH BOTH ROOT - SELECTION ALGORITHMS IN CRISFIELD'S METHOD User information: The program has returned to a converged solution in a prior loop using rithm will automatically both available algorithms. The bisection algo be activated if the absolute value of MAXBIS is greater than 0. *** USER INFORMATION MESSAGE 6197 (NLITER) 6197.0 SOLUTION AT THIS STEP IS DISCARDED. SOLUTION WILL BE ATTEMPTED WITH A DIFFERENT ROOT SELECTION PROCEDURE. - U ser information: This message is issued for the Crisfield method (See NLPARM entry) only. *** USER FATAL MESSAGE 6198 (MPYAD) 6198.0

396 ALL MPYAD METHODS HAVE BEEN DESELECTED. USER INFORMATION: METHODS MAY BE DESELECTED INTERNALLY BY THE MODULE AND/OR BY THE USER VIA SYSTEM CELL 66. USER ACTION: CHECK THE VALUE OF SYSTEM CELL 66, OR DO NOT SET THE CELL. *** SYSTEM FATAL MESSAGE 6199 (MPYSC2) 6199.0 INSUFFICIENT CORE AVAILABLE FOR MATRIX MULTIPLY. CODE=%1 PROGRAMMER INFORMATION: ERROR USER ACTION: INCREASE MEMORY BY %2 WORDS. User information: This message comes from the sparse multiply method when the memory estimate based on the trailer information is exceeded during the actual execution of the operation. * ** USER FATAL MESSAGE 6200. 6200.0 TEMPERATURE(INITIAL) COMMAND IS NOT SPECIFIED IN CASE CONTROL. BOTH TEMPERATURE(LOAD) AND TEMPERATURE(INITIAL) MUST BE SPECIFIED IN NONLINEAR STATIC SOLUTION FOR THERMAL LOADS. User information: Insert a TEMPERATURE(INITIAL) command above the subcase level in the case control and the corresponding temperature values on TEMPij entries in the bulk data. TEMPERATURE(MATERIAL) or TEMPERATURE(BOTH) will cause this error. *** USER FATAL MESSAGE 6201, (UFBSS) 6201.0 SPARSE UNSYMMETRIC FBS CANNOT BE PERFORMED WHEN THE FACTOR TYPE AND THE RIGHT HAND SIDE TYPE ARE NOT THE SAME USER ACTION: DO NOT SELECT THE SPARSE DECOMPOSITION AND FBS METHODS UNDER THESE CIRCUMSTANCES. *** USER FATAL MESSAGE 6202 6202.0 ELECTED MULTIPOINT CONSTRAINT SET AND/OR RIGID THE S ELEMENTS PRODUCE A SINGULAR RMM MATRIX. THIS MAY BE CAUSED BY A CIRCULAR DEPENDENCY IN WHICH A DEGREE OF FREEDOM IS INDIRECTLY DEPENDENT UPON ITSELF. *** SYSTEM FATAL MESSAGE 6203 (CEAD) 6203.0 INCOMPATIBLE MATRICES ARE DETECTED IN COMPLEX EIGENVALUE ANALYSIS USER INFORMATION: CHECK THE SIZES OF THE MATRIX INPUTS TO THIS MODULE. ALSO CHECK FOR THE PRESENCE OF NON - ZERO K (ALWAYS REQUIRED), M OR B FOR EIGENVALUE

397 ANALYSIS (AT LEAST ONE REQUIRED), OR M AND B MATRICES WITH THE SVD METHOD (NOT ALLOWED). *** USER INFORMATION MESSAGE 6204 *** 6204.0 %1 SECONDS REQUIRED TO DECOMPOSE MATRIX. User information: A matrix decomposition has been performed within the NLTRD2 module. The time required for this decomposition is provided for the user's information. *** USER INFORMATION MESSAGE 6204 *** 6204.1 %1 SECONDS REQUIRED TO DECOMPOSE MATRIX. User information: A matrix decomposition has been performed within the NLTRD3 module. required for this decomposition is provided for the user's The time information. *** USER FATAL MESSAGE 6205 6205.0 BEAM ELEMENT %1 IS USING WARPING WITHOUT TORSIONAL STIFFNESS User information: If warping degrees of freedom (SA,SB) are supplied on the CBEAM data card, then warping is used. Torsional stiffness (JA on PBEAM data card) must be greater than zero if warping is used. *** USER WARNING MESSAGE 6206 (GP5), 6206.0 MORE THAN ONE A CMODL ENTRY HAS BEEN FOUND, ONLY THE FIRST ENTRY WILL BE USED. USER ACTION: CHECK INPUT DATA. *** USER WARNING MESSAGE 6207 (GP5), 6207.0 AN ACMODL ENTRY WAS NOT FOUND. A NONMATCHING MESH IS ASSUMED. USER ACTION: CHECK INPUT DATA. *** USER WARNING MESSAGE 6207 (GP5) 6207.1 THE FIELD NORMAL ON THE ACMODL CARD SHOULD NOT BE BLANK IF THE ABS SEARCH METHOD IS TO BE USED. RESETTING THE ABS SEARCH METHOD TO REL AND USING 0.2 AS THE DEFAULT FOR THIS FIELD E 6207 (GP5) *** USER WARNING MESSAG 6207.2 WHEN FSET/SSET ENTRY IS SPECIFIED FOR THE ACCELERATED SEARCH METHOD, THE CORRESPONDING INFOR FIELD MUST BE SPECIFIED AS ELEMENTS. IGNORING THE FSET/SSET ENTRIES *** USER FATAL MESSAGE 6207 (GP5) 6207.3 UNABLE TO ADD/DELETE THE FSET /SSET SET1 ELEMENTS. USER ACTION: CHECK INPUT DATA AND/OR CONTACT SIEMENS

398 PLM SOFTWARE CUSTOMER SUPPORT. *** USER WARNING MESSAGE 6207 (GP5) 6207.4 THE FIELD INTOL ON THE ACMODL CARD SHOULD NOT BE BLANK IF THE ABS SEARCH METHOD IS TO BE USED. RESETTING THE RESETTING INTOL TO BE THE SAME AS THE FIELD NORML *** USER WARNING MESSAGE 6207 (GP5) 6207.5 WHEN USING ACCELERATED SEARCH METHOD, THE FSET AND SSET FIELDS CANNOT BOTH BE BLANK WHEN INFOR IS S ET TO ELEMENTS. THE INFOR FIELD WILL BE IGNORED *** USER FATAL MESSAGE 6207 (GP5) 6207.6 DUPLICATE DEFINITION FOUND FOR PANEL NAMED %1. USER ACTION: REMOVE DUPLCIATE PANEL DEFINITION. *** USER FATAL MESSAGE 6208 (GP5K), 6208.0 IN THE NONMATCHING ALGORITHM NO STRUCTURAL GRIDS HAVE BEEN FOUND ON THE FLUID SURFACE. USER ACTION: CHECK GRID POINT ENTRIES. *** USER WARNING MESSAGE 6209 (ACMG), 6209.0 THERE ARE NO ELEMENT FACES CORRESPONDING TO THE PANEL NAME =%1 CHECK GRID IDS. DEFINED FOR THIS PANEL. *** SYSTEM FATAL MESSAGE 6210 (ACMG), 6210.0 AN INTERNAL TABLE HAS BEEN INCORRECTLY CREATED. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: MODULE FAILED TO CONVERT INTERNAL GRID I D TO SIL NO. (TABLE2)%1 *** SYSTEM FATAL MESSAGE 6210 (ACMG), 6210.1 AN INTERNAL TABLE HAS BEEN INCORRECTLY CREATED. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: MODULE FAILED TO CONVERT INTERNAL GRID ID TO SIL NO. (EQACST)%1 *** SYSTEM FATAL MESSAGE 6210 (ACMG), 6210.2 AN INTERNAL TABLE HAS BEEN INCORRECTLY CREATED. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGR AMMER INFORMATION: MODULE FAILED TO CONVERT INTERNAL GRID ID TO SIL NO. (TABLE1)%1 *** SYSTEM FATAL MESSAGE 6210 (ACMG), 6210.3 AN INTERNAL ERROR OCCURRED WHILE TRYING TO INITIALIZE ACOUSTICS SHARED LIBRARY LIBNXAC

399 USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: MODULE FAILED ACDATA_INIT *** SYSTEM FATAL MESSAGE 6210 (ACMG), 6210.4 AN INTERNAL ERROR OCCURRED WHILE INVOKING FUNCTION IN ACOUSTICS SHARED LIBRARY LIBNXAC USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: RETURN CODE FROM ACOUSTICS SHARED LIBRARY = %1 *** SYSTEM FATAL MESSAGE 6210 (ACMG), 6210.5 AN INTERNAL ERROR OCCURRED IN ROUTINE ACMG_DIRECT USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: FAILED IN GETECTLEN FUNCTION. RETURN CODE = %1 *** SYSTEM FATAL MESSAGE 6210 (ACMG), 6210.6 AN INTERNAL ERROR OCCURRED IN PROCESSING TABLE %1 USER ACTION: CONTACT SIEMENS PLM SOFTWAR E CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6211 (ACMG), 6211.0 A NORMAL TABLE HAS BEEN INCORRECTLY CREATED. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM WARNING MESSAGE 6212 (GPFRBI), 6212.0 THE CASE CONTROL DATA BLOCK HAS THE WRONG RECORD COUNT FOR BLK1 APPROACH. *** SYSTEM WARNING MESSAGE 6213 (GPFRBI), 6213.0 %1 CASE CONTROL RECORDS DETECTED FOR BRANCH %2 WHERE ONE WAS EXPECTED. *** USER INFORMATION MESSAGE 6214 (WILVCD) 6214.1 FEWER THAN REQUESTED VECTORS CALCULATED DUE TO INSUFFICIENT TIME User information: This information message occurs in the READ module when there is an insufficient time to compute eigenvectors. Resubmit the job with increased time limit (TIME). *** USER FATAL MESSAGE 6215 (NCONVG) 6215.0 THE VALUE OF EUI=%1 HAS OVERFLOWED. This information message occurs in the NLITER module when the value EUI has overflowed. Check model and structural units (length, for ce, stress, time, etc.). *** USER FATAL MESSAGE 6215 (NCONVG) 6215.1

400 THE VALUE OF EPI=%1 HAS OVERFLOWED. This information message occurs in the NLITER module when the value EPI has overflowed. Check model and structural units (length, force, stress, time, etc.). *** USER FATAL MESSAGE 6215 (NCONVG) 6215.2 THE VALUE OF EWI=%1 HAS OVERFLOWED. This information message occurs in the NLITER module when the value EWI has overflowed. Check model and structural units (length, force, stress, time, etc.). *** USER FATAL MESSAGE 6215 (NCNVMD) 6215.3 THE ELEMENT TEMPERATURE=%1 ON ELEMENT %2 HAS OVERFLOWED. This information message occurs in the NLITER module when the element temperature has overflowed. Check model and structural units (length, force, stress, time, etc.). *** USER FATAL MESSAGE 6216 *** 6216.0 THE UNSUCCESSFUL MATRIX DECOMPOSITION CAUSED THE ANALYSIS TO FAIL. A POSSIBLE REASON IS THAT FOR RADIATION PROBLEMS, THE DECOMPOSITION OF AN UNSYMMETRIC MATRIX REQUIRES THAT THERE BE NO NULL COLUMNS. NULL COLUMNS CAN RESULT WHEN UNCONNECTED GRID POINTS ARE PRESENT. *** USER WARNING MESSAGE 6226 (RECTND), 6226.0 NATURAL COORDINATE CONVERGENCE FAILED AFTER FIVE ITERATIONS. USER INFORMATION : NATURAL COORD INATES (XI,ETA,ZETA) OF THE GRID POINT (X,Y,Z)= %1%2%3 ARE SET TO (0,0,0). *** USER FATAL MESSAGE 6227 (MBAMG) 6227.0 REQUESTED MACH NUMBER = %1 IS LESS THAN THE MACH BOX REQUIREMENT OF MACH > 1.0 *** USER FATAL MESSAGE 6228 (DLAMBY) 6228.0 REQUESTED MACH NUMBER = %1 IS GREATER THAN THE DOUBLET LATTICE REQUIREMENT OF MACH < 1.0 *** USER FATAL MESSAGE 6229 (CY1CCT) 6229.0 THE LOADSET CASE CONTROL COMMAND AND LSEQ BULK DATA ENTRY MAY NOT BE SPECIFIED IN STATIC ANALYSIS WITH CYCLIC SYM METRY. USER ACTION: REPLACE LOADSET/LSEQ COMBINATIONS WITH THE EQUIVALENT LOAD/LOADCYI COMBINATIONS. *** USER FATAL MESSAGE 6230 (CYCL1) 6230.0 *** USER WARNING MESSAGE 6231 (CY1CCT) 6231.0

401 BOUNDARY CONDITIONS IN SUBCASE%1 ARE DIFFERENT THAN THOSE IN THE FIRST SUBCASE. SUBCASE 1 SPC=%2 AND MPC=%3 SUBCASE%4 SPC=%5 AND MPC=%6 USER INFORMATION: ONLY ONE BOUNDARY CONDITION IS PERMITTED FOR ALL SUBCASES IN CYCLIC SYMMETRY ANALYSIS. THEREFORE, THE CONDITIONS IN THE FIRST SUBCASE WILL BE USED FOR ALL SUBCASES. *** USER INFORMATION MESSAGE 6232 (MODEPT) 6232.0 THE PROPERTIES BELOW WILL BE USED FOR THE FOLLOWING ACOUSTIC ABSORBER PROPERTY ENTRIES (PACABS) PID DAMPING(B) STIFFNESS(K) MASS(M ) ---------------------------------------------------------- *** USER INFORMATION MESSAGE 6233 (MODEPT) 6233.0 THE PROPERTIES BELOW WILL BE USED FOR THE FOLLOWING ACOUSTIC BARRIER PROPERTY ENTRIES (PACBAR) PID RESONANT STIFFNESS(K) RESONANT FREQUENCY(F) ------------------------------------------------------ *** USER WARNING MESSAGE 6234 (MAT) 6234.0 G13, G23 AND/OR G33 ARE NONZERO ON MAT2 ENTRY ID= %1 WHICH IS REFERENCED IN THE MID3 FIELD OF A PSHELL ENTRY. THEY WILL BE IGNORED, SHEAR FLEXIBILITY IS SET TO ZERO. User information: This can occur when the PSHELL entry references a MAT2 entry in the MID3 field and either G13, G23, or G33 is nonzero. See Error Report 3664. *** USER FATAL MESSAGE 6234 (MAT) 6234.1 FOR MATERIAL ID %1 WITH ELEMENT ID %2, AN ILLEGAL COMBINATION OF MATERIAL PROPERTY VALUES HAS RESULTED IN A VIOLATION OF THE FOLLOWING CRITERION: 1.0 - NU12*NU21 MUST BE GREATER THAN 0.0.THE VALUE OF NU21 = N U12*E2/E1. *** USER FATAL MESSAGE 6234 (MAT) 6234.2 FOR MATERIAL ID %1 WITH ELEMENT ID %2, THE POISSON'S RATIOS DEFINED ON THE MAT11 CARD RESULTED IN A VIOLATION OF THE FOLLOWING CRITERION: 1.0 - NU12*NU21 - NU23*NU32 - 2*NU21*NU32*NU13 MUST B E NU13*NU31 - GREATER THAN 0.0. THE VALUES OF NU21 = NU12*E2/E1, NU32 = NU23*E3/E2 AND NU31 = NU13*E3/E1. *** USER FATAL MESSAGE 6234 (MAT) 6234.3 FOR MATERIAL ID %1 WITH ELEMENT ID %2, THE SHEAR MODULUS MUST BE GREATER THAN 0.0. *** USER WARNING MESSAGE 6235 (IFP7) 6235.0

402 PBCOMP ENTRY=%1 IS MISSING THE SPECIFICATION OF LUMPED AREAS FOR THE BEAM CROSS SECTION. User information: One cause is that fewer than four stress output points are specified. EBEMD) *** USER FATAL MESSAGE 6236 ( 6236.0 PBCOMP FOR ENTRY =%1 SPECIFIES SECTION=0 (WHICH IS THE DEFAULT) YET IT ALSO SPECIFIES DATA FOR LUMPED AREAS. *** USER FATAL MESSAGE 6236 (EBARZ) 6236.1 PRODUCT OF MOMENTS OF INERTIA I1 AND I2 SHOULD EXCEED THE SQUARE OF I12 FOR PBAR OF ELEMENT %1 IN SOL 401 *** USER WARNING MESSAGE 6237 (PLOT) 6237.0 *** CONTOUR PLOTS ARE REQUESTED FOR COMPLEX RESULTS. THIS IS NOT SUPPORTED. *** USER WARNING MESSAGE 6238 (IFSEQU) 6238.0 THE FIRST %1 EQUATION OF ID NUMBER = %2 HAS BEEN DEFINED WITH NO PARAMETERS IN ITS ARGUMENT LIST. *** USER FATAL MESSAGE 6239 (IFSEQU) 6239.0 THE FIRST %1 EQUATION OF ID NUMBER = %2 HAS BEEN DEFINED WITH NO ARGUMENT LIST. *** USER FAT AL MESSAGE 6240 (IFSEQU) 6240.0 ARGUMENT NUMBER %1 (%2) OF THE %3 EQUATION WITH ID NUMBER = %4 HAS BEEN PREVIOUSLY USED AS AN ARGUMENT IN THIS EQUATION *** USER FATAL MESSAGE 6241 (IFSEQU) 6241.0 FUNCTION %1 DEFINED IN THE %2 EQUATION WITH ID NUMBER = %3 HAS BEEN PREVIOUSLY USED AS AN ARGUMENT IN THIS EQUATION USER INFORMATION: THIS ERROR MAY BE CAUSED WHEN THE FUNCTION NAME BEGINS IN FIELD 2 INSTEAD OF FIELD 3 *** USER FATAL MESSAG E 6242 (NLINIT) 6242.0 ENFORCED DISPLACEMENTS CAN NOT BE USED WITH ARC - LENGTH METHODS. USER ACTION: REMOVE NLPCI BULK DATA ENTRY OR ENFORCED DISPLACEMENTS. *** USER WARNING MESSAGE 6243 (REIG). 6243.1 THE DEGREE OF FREEDOM (D.O.F) REQUESTED FOR POINT N ORMALIZATION HAS NOT BEEN SPECIFIED ON THE EIGR OR EIGB ENTRY USER INFORMATION: THE D.O.F PRECEDING THE REQUESTED D.O.F. IN THE INTERNAL SEQUENCE LIST WILL BE USED *** USER WARNING MESSAGE 6244 (STDCON), 6244.0 THERE IS STRFIELD DISCONTINUITY REQUEST IN SUBCASE %1 BUT NO MATCHING SURFACE OR VOLUME ID ON GPSTRESS

403 COMMAND. USER ACTION: CHECK STRFIELD COMMAND. *** USER WARNING MESSAGE 6244 (STDCON), 6244.1 THERE IS STRESS DISCONTINUITY REQUEST IN SUBCASE %1 BUT NO MATCHING SURFACE OR VOLUME ID ON GPSTRESS COMMAND. USER ACTION: CHECK STRFIELD COMMAND. *** SYSTEM WARNING MESSAGE 6245 (STDCON), 6245.0 ANALYSIS TYPE =%1 IS NOT SUPPORTED IN ERROR ANALYS IS. USER ACTION: USE STATIC ANALYSIS WITH STRESS REQUEST. *** USER WARNING MESSAGE 6246 (STDCON), 6246.0 ELSDCON SET %1 NOT FOUND IN CASECC SUBCASE %2 USER ACTION: CHECK ELSDCON REQUEST. *** USER WARNING MESSAGE 6246 (STDCON), 6246.1 GPSDCON SET %1 NOT FOUND IN CASECC SUBCASE %2 USER ACTION: CHECK GPSDCON REQUEST. *** USER WARNING MESSAGE 6246 (STDCON), 6246.2 NO OUTPUT STRESS REQUEST FOR SUBCASE =%1 SO NO STRESS DISCONTINUITY CALCULATED USER ACTION: CHECK ELSTRESS REQUEST. *** USER WARNING MESSAGE 6246 (STDCON), 6246.3 STRFIELD SET %1 NOT FOUND IN CASECC SUBCASE %2 USER ACTION: CHECK STRFIELD REQUEST. *** SYSTEM WARNING MESSAGE 6247 (STDCON), 6247.0 THERE IS AN INCONSISTENT POINTER TABLE FOR SCR4 FILE. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: CHECK POINTER TABLE 4 FOR SCR3 FILE *** SYSTEM WARNING MESSAGE 6247 (STDCON), 6247.1 THERE IS AN INCONSISTENT POINTER TABLE FOR SCR3 FILE. USER ACTION: CONTACT SI EMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: CHECK POINTER TABLE 3 FOR SCR3 FILE *** SYSTEM WARNING MESSAGE 6247 6247.2 THERE IS AN INCONSISTENT POINTER TABLE FOR SCR3 FILE. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: CHECK POINTER TABLE 2 FOR SCR3 FILE *** SYSTEM WARNING MESSAGE 6247 (STD2GD/S), 6247.5 THERE IS AN INCONSISTENT POINTER TABLE FOR SCR5 FILE.

404 USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: CHECK POINTER TABLE 5 FOR SCR5 FILE *** SYSTEM WARNING MESSAGE 6247 (STD2HD/S), 6247.6 THERE IS AN INCONSISTENT POINTER TABLE FOR SCR4 FILE. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: CHECK POINTER TABLE 5 FOR SCR4 FILE *** SYSTEM WARNING MESSAGE 6247 (STD2HD/S), 6247.7 ELEMENT %1 NOT FOUND IN SURFACE/VOLUME DISCONTINUITY LIST *** SYSTEM WARNING MESSAGE 6248 (STDCON), 6248.0 EXTERNAL GRID ID=%1 COULD NOT BE FOUND IN THE EQEXIN FILE. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: CHECK EQEXIN DATA FILE. *** SYSTEM WARNING MESSAGE 6249 (STD2EX) 6249.0 ERROR ANALYSIS OUTPUT CAPABILI TY IS NOT SUPPORTED FOR ELEMENT TYPE =%1 USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: THIS ROUTINE HAS FAILED TO RECOGNIZE ABOVE ELEMENT TYPE. GRID POINT STRESS DATA FOR THE SURFACE/VOLUME ID=%1 6250.0 COULD NOT BE FOUND IN THE EGPST FILE. USER ACTION: CHECK STRFIELD REQUEST FOR THIS ID. *** SYSTEM WARNING MESSAGE 6251 (STD2EX), 6251.0 IMPROPER OES1 FILE FOUND. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. CHECK OES1 FILE INPUT. PROGRAMMER INFORMATION: *** SYSTEM WARNING MESSAGE 6251 (STD2EX), 6251.1 IMPROPER ECT FILE FOUND. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: CHECK ECT FILE INPUT. USER WARNING MESSAGE 6252 (STD2HD/S), *** 6252.0 THERE IS NO STRESS OUTPUT FOR THE ELEMENT ID.=%1 USER ACTION: REQUEST ELEMENT STRESS OUTPUT. *** SYSTEM WARNING MESSAGE 6253 (STDCON), 6253.0

405 STRFIELD REQUEST IN SUBCASE =%1 IGNORED SINCE GPDCT IS PURGED. P ROGRAMMER INFORMATION: CHECK GPDCT FILE INPUT *** SYSTEM WARNING MESSAGE 6253 (STDCON), 6253.1 STRFIELD REQUEST IN SUBCASE =%1 IGNORED SINCE ELDCT IS PURGED. PROGRAMMER INFORMATION: CHECK ELDCT FILE INPUT *** SYSTEM WARNING MESSAGE 6253 (STDCON), 6253.2 GRID POINT STRESS DISCONTINUITY REQUEST IN SUBCASE %1 IGNORED SINCE OGDS1 IS PURGED. PROGRAMMER INFORMATION: CHECK OGDS1 FILE INPUT *** SYSTEM WARNING MESSAGE 6253 (STDCON), 6253.3 ELEMENT STRESS DISCONTINUI TY REQUEST IN SUBCASE %1 IGNORED SINCE OEDS1 IS PURGED. PROGRAMMER INFORMATION: CHECK OEDS1 FILE INPUT ***USER FATAL MESSAGE 6254 (TIMTS9) 6254.0 ILLEGAL DTI ENTRY INPUT FOR TIMETEST MODULE PROGRAMMER INFORMATION: NUMBER OF SPECIFIED BREAK POINTS FOR KERNEL %1 EXCEEDS %2 ***USER FATAL MESSAGE 6255 (TIMTS9) 6255.0 ILLEGAL DTI ENTRY INPUT FOR TIMETEST MODULE PROGRAMMER INFORMATION: SEE ENTRY NUMBER %1 E 6256 (TIMTS9) ***USER FATAL MESSAG 6256.0 ILLEGAL DTI ENTRY INPUT FOR TIMETEST MODULE PROGRAMMER INFORMATION: SEE ENTRY FOR KERNEL %1 ***USER FATAL MESSAGE 6257 (TIMTS9) 6257.0 ILLEGAL DTI ENTRY INPUT FOR TIMETEST MODULE PROGRAMMER INFORMATION: KERNEL NAME %1 NOT FOUND ON THE LIST ***USER FATAL MESSAGE 6258 (TIMTS9) 6258.0 ILLEGAL DTI ENTRY INPUT FOR TIMETEST MODULE PROGRAMMER INFORMATION: KERNEL NAME %1 HAS USER SPECIFIED BREAK POINTS THAT ARE LESS THAN OR EQUAL TO 1 ***USER FATAL MESSAGE 6259 (TIMTS9) 6259.0 ILLEGAL DTI ENTRY INPUT FOR TIMETEST MODULE PROGRAMMER INFORMATION: KERNEL %1 HAS USER SPECIFIED BREAK POINTS THAT ARE NOT IN ASCENDING ORDER BY AT LEAST AN INCREMENT OF TWO ***SYSTEM FATAL MESSAGE 6260 (TIMT9F) 6260.0 LOGIC ERROR IN TIMETEST 9. PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. ***USER FATAL MESSAGE 6261 (TIMTS6) 6261.0 ILLEGAL DTI ENTRY INPUT FOR TIMETEST MODULE

406 PROGRAMMER INFORMATION: NOT ALL KERNELS TESTED IN TIMTS9, THEREFORE RESULTS ARE NOT WRITTEN TO THE OUTPUT DATA BLOCK ***SYSTEM FATAL MESSAGE 6262 (TIMTS6) 6262.0 ERROR WHILE READING FILE1=%1 ***USER FATAL MESSAGE 6263 (TIMTS9) 6263.0 ILLEGAL DTI ENTRY INPUT FOR TIMETEST MODULE PROGRAMMER INFORMATION: BREAK POINTS ABOVE %1 CANNOT BE CONSIDERED FOR KERNEL %2 *** USER FATAL MESSAGE 6264 (TABFM4). 6264.0 ILLEGAL INPUT SPECIFIED ON DTI,ESTDATA BULK DATA ENTRY: %1%2 TIMING ESTIMATES WILL BE WRONG. TYPE IS SPECIFIED IN ALL USER ACTION: ASSURE PROPER FIELDS. ***USER FATAL MESSAGE 6265 (DYNAM0) 6265.0 THE FACTOR FILE IN THIS RUN HAS BEEN CREATED USING AN OLDER VERSION OF THE PROGRAM IN WHICH SPARSE SOLUTION IS NOT SUPPORTED FOR THIS SOLUTION SEQUENCE USER ACTION: DO NO T USE THE RESTART CAPABILITY IN THIS RUN *** USER FATAL MESSAGE 6267, 6267.0 CONTROL POINT NO.%1ON PANEL NO.%2 ALIGNS WITH THE EDGE OF BOX NO.%3ON PANEL NO.%4 **** USER INFORMATION MESSAGE 6269 (MPYABT) 6269.0 THERE EXISTS INSUFFICIENT MEMORY FOR TRIPLE MULTIPLY. THEREFORE, TWO EQUIVALENT MPYAD OPERATIONS WILL BE PERFORMED USER ACTION: IF TRIPLE MULTIPLY METHOD IS DESIRED, THEN INCREASE MEMORY SIZE BY=%1 WORDS *** USER FATAL MESSAGE 6270 (RCARD) 6270.0 FIELD 2 OF THE FOLLOWING %1 ENTRY CONTAINS AN INVALID CHARACTER. USER INFORMATION: 1. ENTRY: %2 2. FIELD 2: %3 *** USER FATAL MESSAGE 6270 (RCARD) 6270.1 FIELD 2 OF THE FOLLOWING %1 ENTRY CONTAINS EMBEDDED BLANKS. USER INFORMATION: 1. ENTRY: %2 2. FIELD 2: %3

407 *** USER FATAL MESSAGE 6270 (RCARD) 6270.2 THE FOLLOWING %1 ENTRY IS INVALID; LARGE FIELD IS NOT SUPPORTED. *** USER FATAL MESSAGE 6271 (PRJVER) 6271.0 PARAMETER NO. %1 OF "PROJVER" DMAP MODULE IS ILLEGAL. *** USER FATAL MESSAGE 6273 (PRJVER) 6273.0 THE "SET" OPTION IS BEING REQUESTED IN THE "PRJVER" EXISTENT - SUBROUTINE FOR A DELETED OR NON PROJECT/VERSION. USER INFORMATION: PROJECT ID=%1, VERSION ID=%2, STATUS="%3" *** USER FATAL MESSAGE 6 274 (PRJVER) 6274.1 PROJECT ID OF %1 CANNOT BE FOUND IN THE "PROVER" TABLE. *** USER FATAL MESSAGE 6274 6274.2 PROJECT - NO %1 OF DBSNO %2 CANNOT BE FOUND IN THE "PROVER" TABLE. *** USER FATAL MESSAGE 6274 (VWHCPJ) 6274.4 PROJECT - ID %1 OF DBSNO%2 CANNOT BE FOUND IN THE "PROVER" TABLE. *** SYSTEM FATAL MESSAGE 6275 (PRJVER) 6275.0 ERROR DETECTED IN THE "PROVER" TABLE. *** SYSTEM FATAL MESSAGE 6276 (PRJVER) 6276.0 CURRENT PROJECT ID OF %1 AND VERSION ID OF %2 COULD NOT BE FOUND IN THE 2ND RECORD OF "PROVER" TABLE. *** USER WARNING MESSAGE 6277 (KSHERD), 6277.0 THE EFFECTIVENESS FACTOR F%1=%2 FOR SHEAR ELEMENT ID. =%3 GIVES THE EFFECTIVE AREA GREATER THAN TH E ACTUAL AREA. USER ACTION: CHECK EFFECTIVENESS FACTOR F%4 ON PSHEAR ENTRY. *** USER FATAL MESSAGE 6278 (MTMD23) 6278.0 THE BULK DATA ENTRY SELECTED BY THE CASE CONTROL COMMAND %1 = %2 WAS NOT FOUND *** USER WARNING MESSAGE 6279 (IFS6P) 6279.0 THE DOPTPRM ENTRY SPECIFIES A DELP = %1. USER INFORMATION : DELP > 1.0 MAY PRODUCE POOR RESULTS. *** USER INFORMATION MESSAGE 6280 (NCONVG) 6280.0 AN EXCESSIVE NUMBER OF STIFFNESS MATRIX UPDATES HAS ERGENCE CONDITIONS. ACTIVATED DIV *** USER FATAL MESSAGE 6281 (SEP2D) 6281.0 NO SUBCASES ARE SPECIFIED FOR THE RESIDUAL STRUCTURE. IN A STATIC ANALYSIS, AT LEAST ONE SUBCASE MUST BE

408 SPECIFIED FOR THE RESIDUAL STRUCTURE. *** USER FATAL MESSAGE 6282 (XSELOADS) 6282.0 - PROCESSING TERMINATED. CASECC PURGED *** USER FATAL MESSAGE 6282 (XSELOADS) 6282.1 GEOM3 PURGED - PROCESSING TERMINATED. *** USER FATAL MESSAGE 6284 (APD0) 6284.0 USER INFORMATION: GRID ID = %1 IS LISTE D MORE THAN ONCE ON SET1 BULK DATA ENTRY ID = %2. USER ACTION: REMOVE THE DUPLICATE GRID FROM THE SET1 ENTRY. *** USER FATAL MESSAGE 6285 (VNASIN) 6285.0 CHBDY%1 DOES NOT REFERENCE A PHBDY ENTRY. *** USER WARNING MESSAGE 6286 (ZREAD) 6286.0 THE NDDL DESCRIPTION OF DATA BLOCK=%1, RECORD=%2,DOES NOT HAVE AN EITHER/OR TO MATCH OPT=%3. ITEMS ARE ASSUMED TO BE UNDEFINED. USER INFORMATION: PROBABLE CAUSE IS WRONG NDDL DESCRIPTION CODED, OR , WRONG GENERIC DATABLOCK USED (E.G. OES INSTEAD OF OE F). *** SYSTEM WARNING MESSAGE 6287 (F04SUM) 6287.0 FORTRAN UNIT=%1 CANNOT BE REWOUND BECAUSE IT IS REWINDABLE DEVICE. LOCATED ON A NON - USER INFORMATION: DIAG 49 PROCESSING IS TERMINATED. USER ACTION: ASSIGN THE UNIT TO A REWINDABLE (TAPE/DISK) F ILE AND RERUN JOB. *** USER FATAL MESSAGE 6288 6288.0 UNABLE TO CONVERGE WITH ITERATIVE METHOD. *** USER FATAL MESSAGE 6288 (SITDRD) 6288.1 UNABLE TO CONVERGE WITH ITERATIVE METHOD. USER ACTION: INCREASE MAXIMUM NUMBER OF ITERATIONS OR USE DIRECT METHOD. *** SYSTEM WARNING MESSAGE 6288 (SDRVP) 6288.4 UNABLE TO CONVERGE WITH ITERATIVE METHOD. *** USER WARNING MESSAGE 6290 6290.0 TABFM6 SUPPORTS ONLY TYPES TABLE AND CASECC. ANOTHER TYPE WAS FOUND ON DATA BLOCK %1. *** SYSTEM WARNING MESSAGE 6291 (DDRMM) 6291.0 OUTPUT DATA BLOCK CORRESPONDING TO INPUT MODAL SOLUTION DATA BLOCK %1 IS NOT PRESENT. INPUT DATA BLOCK THUSLY IGNO RED. *** SYSTEM WARNING MESSAGE 6292 (DDRMM) 6292.0 INVALID INPUT DATA DETECTED IN DATA BLOCK %1.

409 PROCESSING STOPPED FOR THIS DATA BLOCK. - 1 TO SKIP USE OF MODULE DDRMM. USE PARAM,DDRMM, *** USER FATAL MESSAGE 6293 (DSAD16) 6293.0 GRID NO. %1 REFERENCED ON A DRESP1 ENTRY COULD NOT BE FOUND. USER ACTION : USE OF UNREFERENCED GRIDS IS NOT RECOMMENDED AND MAY INDICATE A USER INPUT ERROR, RESULTS FOR OTHER RESPONSES ARE NOT AFFECTED. *** SYSTEM FATAL MESSAGE 6294 (ACMG), 6294.0 COUPLING CONTRIBUTION FOR THIS FLUID ELEMENT ID =%1 CAN NOT BE COMPUTED. USER ACTION: CHECK THE GEOMETRY OF THE STRUCTURAL ELEMENT IN THE VICINITY OF THIS ELEMENT. *** USER FATAL MESSAGE 6295 (GIGTKG) 6295.0 USER INFORMATION: SPLINE3 %1 FOR CAERO %2 HAS ILLEGAL COMPONENT %3 *** SYSTEM FATAL MESSAGE 6296 (qmatr) 6296.0 UNABLE TO LOCATE A MEMBER OF DATABLOCK %1 (FILE %2) WITH ATTRIBUTES: *** SYSTEM FATAL MESSAGE 6296 6296.1 UNABLE TO LOCATE %1 IN DATA BLOCK %2 (FILE %3). *** SYSTEM FATAL MESSAGE 6297 (EMG) 6297.0 INCORRECT VALUE %1 HAS BEEN SPECIFIED FOR THE 22ND PARAMETER. *** SYSTEM FATAL MESSAGE 6297 (DSAH) 6297.1 INCORRECT VALUE %1 HAS BEEN SPECIFIED FOR THE FIRST PARAMETER. *** USER FATAL MESSAGE 6298 (PSTA) 6298.0 THE LEADING EDGE IS NOT SUPERSONIC: M=%1 AND SECANT LAMBDA=%2. USER INFORMATION: WHEN USING PISTON THEORY WITH A SWEEP CORRECTION (NTHRY=2), THE LEADING EDGE MUST BE SUPERSONIC; THAT IS, THE MACH NUMBER MUS T BE GREATER THAN THE SECANT OF THE SWEEP ANGLE. USER ACTION: INCREASE THE MACH NUMBER OR USE AN ALTERNATIVE AERODYNAMIC THEORY ( MACH BOX OR ZONA ). *** USER FATAL MESSAGE 6300 (FA1PKI) 6300.0 SINGULAR MATRIX FOR INTERPOLATION IN %1 USER ACTION: CHECK K VALUES INPUT ON THE MKAEROI ENTRIES, PARTICULARLY FOR DUPLICATE VALUES. *** USER FATAL MESSAGE 6301 (DSAD14) 6301.0 DIVERGENCE ROOT NO.%1 REQUESTED FOR MACH %2 EXCEEDS

410 %3, THE NUMBER OF ROOTS EXTRACTED AT THIS MACH NUMBER. US ER ACTION: DELETE THE DRESP1 ENTRY WITH DIVERGENCE SINCE IT DOES NOT AFFECT THE DESIGN. *** SYSTEM FATAL MESSAGE 6302 (DSASRT) 6302.0 INSUFFICIENT SPACE TO PROCESS GPTABD INFORMATION. PROGRAMMER INFORMATION: THE DSASRT PLACES A LIMIT OF %1 ON THE NUMBER OF ELEMENT TYPES. NASTRAN CURRENTLY SUPPORTS %2 TYPES. *** USER INFORMATION MESSAGE 6303 (BGICA) 6303.0 NO BCONP BULK DATA ENTRIES ARE SPECIFIED. *** USER FATAL MESSAGE 6303 (BGICA) 6303.1 NO BLSEG AND BSURF BULK DATA ENTRIES ARE SPECIFIED. *** SYSTEM FATAL MESSAGE 6304 6304.0 %1 RECORD CANNOT BE LOCATED. *** USER INFORMATION MESSAGE 6305 (BGCAU1) 6305.0 GRID ID = %1 DEFINED IN BOUTPUT ENTRY ID = %2 IS NOT A SLAVE NODE *** USER FATAL MESSAGE 6305 (BGFRCR) 6305.1 %1 ENTRY ID = %2 WHICH IS REFERRED IN BCONP ENTRY ID =%3 IS UNDEFINED. *** USER INFORMATION MESSAGE 6306 (BGCORA) 6306.0 NO BWIDTH BULK DATA ENTRIES ARE SPECIFIED, DEFAULT WIDTH VALUE OF UNITY WILL BE USED. *** USER INFORMATION MESSAGE 6306 (BGFRCR) 6306.1 NO BFRIC BULK DATA ENTRIES ARE SPECIFIED, DEFAULT VALUES WILL BE USED. *** USER INFORMATION MESSAGE 6306 (BGWIDR) 6306.2 WIDTHS ARE NOT SPECIFIED FOR SLAVE ID = %1 DEFAULT VALUES OF UNITY ARE ASSUMED FOR ALL THE SLAVE SEGMENTS. *** USER INFORMATION MESSAGE 6307 (BGPENR) 6307.0 THE MAGNITUDE OF F0 IS CHANGED TO ZERO FOR BNPEN ENTRY ID = %1. *** USER INFORMATION MESSAGE 6307 (BGPENR) 6307.1 THE MAGNITUDE OF C0 IS CHANGED TO ZERO FOR BNPEN ENTRY ID = %1. *** USER FATAL MESSAGE 6308 (BGCOCL) 6308.0 SLAVE REGION ID = %1 SPECIFIED IN BCONP ENTRY ID = %2 IS NOT DEFINED. *** USER FATAL MESSAGE 6308 (BGCOCL) 6308.1 MASTER REGION ID = %1 SPECIFIED IN BCONP ENTRY ID = %2 IS

411 NOT DEFINED. *** USER FATAL MESSAGE 6309 (BGCOCL) 6309.0 SLAVE REGION ID = %1 REFERRED IN BCONP ENTRY ID = %2 IS NOT UNIQUE. *** USER FATAL ME SSAGE 6309 (BGCOCL) 6309.1 MASTER REGION ID = %1 REFERRED IN BCONP ENTRY ID = %2 IS NOT UNIQUE. *** USER FATAL MESSAGE 6309 (BGLSCW) 6309.2 BOTH SLAVE AND MASTER CAN NOT BE CLOSED FOR A - BCONP ENTRY ID = %1 SYMMETRIC CONTACT REGION USER FATAL MESSAGE 6309 (BGLSCW) *** 6309.3 LINE REGION ID = %1 REFERRED IN BCONP ENTRY ID = %2 DOES NOT HAVE UNIQUE GRID POINTS. *** USER FATAL MESSAGE 6309 (BGLSCW) 6309.4 LINE REGION ID = %1 REFERRED IN BCONP ENTRY ID = %2 CAN ND GRID POINTS. NOT HAVE SAME FIRST AND SECO *** USER FATAL MESSAGE 6309 (BGLSCW) 6309.5 GRID POINT ID = %1 REFERRED IN BOTH SLAVE AND MASTER REGIONS FOR BCONP ENTRY ID = %2 USER ACTION : DO NOT INCLUDE A GRID POINT IN SLAVE AND MASTER REGIONS. USER FATAL MESSAGE 6310 (BGCOCL) *** 6310.0 SLAVE BLSEG ENTRY ID = %1 REFERRED IN BCONP ENTRY ID = %2 HAS ONLY ONE GRID POINT FOR THE SYMMETRIC CASE. USER ACTION : SLAVE BLSEG ENTRY SHOULD HAVE AT LEAST TWO GRID POINTS FOR THE SYMMETRIC CASE. *** USER FATAL MESSAGE 6310 (BGCOCL) 6310.1 MASTER BLSEG ENTRY ID = %1 REFERRED IN BCONP ENTRY ID = %2 HAS ONLY ONE GRID POINT. USER ACTION : MASTER BLSEG ENTRY SHOULD HAVE AT LEAST TWO GRID POINTS. *** USER FATAL MESSAGE 6311 (BGCOCL) 6311.0 INCONSISTENT BCONP ENTRY ID = %1 HAS SLAVE BLSEG ENTRY ID = %2 AND MASTER BSURF ENTRY ID = %3. *** USER FATAL MESSAGE 6311 (BGCOCL) 6311.1 INCONSISTENT BCONP ENTRY ID = %1 HAS SLAVE BSURF ENTRY ID = %2 AND MASTER BLSEG ENTRY ID = %3. *** USER FATAL MESSAGE 6312 (BGCOCL) 6312.0 SLAVE GRID POINT =%1 AND THE CORRESPONDING MASTER GRID POINTS = %2%3 OF BCONP ENTRY ID = %4 DO NOT LIE IN THE SPECIFIED SLIDE LINE PLANE.

412 *** USER WARNING MESSAGE 6313 (BGSRCD) 6313.0 SLAVE GRID POINT =%1 HAS ZERO LENGTH MASTER SEGMENT WITH GRID POINTS =%2%3. *** USER FATAL MESSAGE 6314 (BGSRCD) 6314.0 INITIAL PENETRATION = %1 OF SLAVE GRID POINT = %2 INTO %4 IS NOT ALLOWED. MASTER SEGMENT = %3 - *** USER WARNING M ESSAGE 6315 (BGSRCD) 6315.0 COORDINATES OF SLAVE GRID POINT =%1 ARE CHANGED TO %2 %3 %4 FROM %5 %6 %7 TO PRECLUDE PENETRATION. *** SYSTEM FATAL MESSAGE 3200 (BGTPEN) 6316.0 SURFACE CONTACT FOR THE BCONP ENTRY ID = %1 IS NOT SUPPORTED. *** USER FATAL MESSAGE 6319 (STPDA) 6319.0 MACH NUMBER %1 WAS NOT SPECIFIED ON AN AEFACT BULK DATA ENTRY %2 USER INFORMATION: A MACH NUMBER LISTED ON A MKAEROI ENTRY CANNOT BE FOUND ON AN AEFACT ENTRY REFERENCED BY A PAERO4 ( STRIP THEORY ) BULK DATA ENTRY. *** USER INFORMATION MESSAGE 6320 (SITDRV) 6320.0 SOLUTION WAS CONTINUED BECAUSE EXTERNAL CONVERGENCE CRITERION WAS PASSED. *** USER FATAL MESSAGE 6321 (DOPR1B) 6321.0 THE INDEPENDENT DESIGN VARIABLE ID %1 APPEARS MORE THAN ONCE ON THE DLINK ENTRY ASSOCIATED WITH DEPENDENT DESIGN VARIABLE ID %2 USER ACTION: REMOVE THE DUPLICATE REFERENCE TO THE INDEPENDENT DESIGN VARIABLE. *** USER FATAL MESSAGE 6321 (DOPR1B) 6321.1 THE DESVAR ENTRY ID %1 REFERENCES A DDVAL ENTRY ID %2 THAT IS NOT SPECIFIED IN THE BULK DATA. USER ACTION: REMOVE THE DDVAL ENTRY FROM DESVAR ENTRY OR ADD A DDVAL ENTRY. *** SYSTEM FATAL MESSAGE 6324 (PEDGED) 6324.0 THE TWO SILS FOR EDGE ID=%1 ARE BOTH ZERO. R USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOME SUPPORT. *** SYSTEM FATAL MESSAGE 6328 (EMGSIL) 6328.0 THE SIL FOR GRID ID=%1 IS %2 WHICH IS NOT POSITIVE. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 6329 6329.0

413 THE DETERMINANT OF JACOBIAN IS ZERO AT GAUSS POINT: X=%1 Y=%2 USER ACTION: CHECK GEOMETRY OF ELEMENT ID=%3. OTHERWISE, CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 6329 (SHTRPD) 6329.2 BAD GEOMETRY CONDITION AT GAUSS POINT :%1 USER ACTION: CHECK GEOMETRY OF ELEMENT ID=%2. OTHERWISE, CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6329 (SHPSHD) 6329.3 THE DETERMINANT OF JACOBIAN IS ZERO AT GAUSS POINT: 1, Y=%2 FOR ELEMENT ID=%3. X=% USER ACTION: CHECK GEOMETRY OF THIS FACE. OTHERWISE, CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 6329 (SDPS1D) 6329.4 THE DETERMINANT OF JACOBIAN IS ZERO AT GAUSS POINT: X=%1 Y=%2 USER ACTION: CHECK GEOMETRY OF ELEMENT ID=%3. OTHERWISE, CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 6329 (PTERMD) 6329.5 THE DETERMINANT OF JACOBIAN IS ZERO AT GAUSS POINT: X=%1 Y=%2 Z=%3 USER ACTION: CHECK GEOMETRY OF ELEMENT ID=%4. OTHERWISE, CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6329 (PFACED) 6329.6 THE DETERMINANT OF JACOBIAN IS ZERO AT GAUSS POINT: X=%1 FOR FACE ID=%2. USER ACTION: CHECK GEOME TRY OF THIS FACE. OTHERWISE, CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6329 (PEDGED) 6329.7 THE DETERMINANT OF JACOBIAN IS ZERO AT GAUSS POINT: X=%1 FOR EDGE ID=%2. USER ACTION: CHECK GEOMETRY OF THIS EDGE. OTHERWISE, CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 6329 (JACTD) 6329.8 THE DETERMINANT OF JACOBIAN IS ZERO AT GAUSS POINT: X=%1 Y=%2 Z=%3 USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 6329 6329.12 THE DETERMINANT OF JACOBIAN IS ZERO AT GAUSS POINT:

414 X=%1 Y=%2 USER ACTION: CHECK GEOMETRY OF ELEMENT ID=%3. OTHERWISE, CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 6329 (EMGPSD) 6329.15 THE DETERMI NANT OF JACOBIAN IS ZERO AT GAUSS POINT: X=%1 Y=%2 Z=%3 USER ACTION: CHECK GEOMETRY OF ELEMENT ID=%4. OTHERWISE, CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 6329 6329.16 THE DETERMINANT OF JACOBIAN IS ZERO AT GAUSS POINT: =%1 USER ACTION: CHECK GEOMETRY OF ELEMENT ID=%2. OTHERWISE, CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 6329 (EBMVLD) 6329.18 THE DETERMINANT OF JACOBIAN IS ZERO AT GAU SS POINT: X=%1 Y=%2 USER ACTION: CHECK GEOMETRY OF ELEMENT ID=%3. OTHERWISE, CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 6329 (BMPPMD) 6329.19 THE CURVATURE OF ARC AT GAUSS POINT %1 FOR THE BEAM ELEMENT %2 IS ZERO. USER ACTION: CHECK GEOMETRY OF ELEMENT OTHERWISE, CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 6329 (BMPPMD) 6329.20 THE SLOPE OF ARC AT GAUSS POINT %1 FOR THE BEAM ELEMENT %2 IS ZERO. USER ACTION: CHECK GEOMETRY OF ELEMENT OTHERWISE, CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6331 (PSHBUT) 6331.0 INADMISSIBLE CASE NUMBER=%1 FOR BUBBLE FUNCTIONS TRIAP SHELL ELEMENT. USER ACTION: CONTACT SIEMENS PLM S OFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6331 (PSHBUB) 6331.1 INADMISSIBLE CASE NUMBER=%1 FOR BUBBLE FUNCTIONS QUADP SHELL ELEMENT. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6331 (PFAC4L) 6331.2 LOGIC ERROR: LOOP =%1, IERROR=%2 USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER

415 SUPPORT. *** SYSTEM FATAL MESSAGE 6331 (ETREPL) 6331.3 LOGIC ERROR: LOOP =%1 IS GREATER THAN 21 FOR THE TRIA ELEMENT. ION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER USER ACT SUPPORT. *** SYSTEM FATAL MESSAGE 6331 (ETREPL) 6331.4 LOGIC ERROR: NUMBER OF FUNCTIONS USED =%1 IS GREATER THAN THE MAX FUNCTIONS =%2. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6331 (ETREPL) 6331.5 LOGIC ERROR: MAX FUNCTIONS =%1 FOR WHICH SPACE IS RESERVED IS LESS THAN 1. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6331 (ETEPL) 6331.6 LOGIC ERROR: LOOP =%1 IS GREATER THAN 21 FOR THE PENTA ELEMENT. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6331 (EPEPL) 6331.7 LOGIC ERROR: GRID SIL VALUES FOR QUADRILATERAL FACE ARE NOT UNIQUE. S PLM SOFTWARE CUSTOMER USER ACTION: CONTACT SIEMEN SUPPORT. *** SYSTEM FATAL MESSAGE 6331 (AAAAAAAA) 6331.8 LOGIC ERROR: ELEMENT TYPE = %1 (ELEMENT ID =%2) IS NOT A - ELEMENT TYPE. SUPPORTED P USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6331 (BUBITT) 6331.9 INADMISSIBLE CASE NUMBER=%1 FOR BUBBLE FUNCTIONS QUADP/TRIAP SHELL ELEMENT. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6331 (EMGMID) 6331.10 LOGIC ERROR: L1 =%1, L2=%2, L3=%3 USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6331 (JACPD) 6331.11 LOGIC ERROR: ZERO POLYNOMIAL COEFFICIENT *** SYSTEM FATAL MESSAGE 6333 (EQNINC) 6333.0

416 DEQIND DATA BLOCK HAS A LENGTH OF %1 WHICH IS NOT A MULTIPLE OF %2. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6334 (EQNINC) 6334.0 THE DEQATN ENTRY ID=%1 CAN NOT BE FOUND IN THE DEQIND DATA BLOCK. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6334 (FCEN4D) 6334.1 THE DEQATN ENTRY ID=%1 CAN NOT BE FOUND IN THE EQUATION POOL. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. SER FATAL MESSAGE 6334 (EMGPTD) *** U 6334.2 THE DEQATN ENTRY ID=%1 CAN NOT BE FOUND IN THE DEQIND DATA BLOCK. USER ACTION: CHECK TEMPF ENTRY SPECIFICATION. *** SYSTEM FATAL MESSAGE 6335 (EQNINC) 6335.0 ERROR DETECTED IN DEQATN TABLE. PROGRAMMER INFORMATION: LENGTH OF RECORD=%1, LENGTH OF HEADER=%2 USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER WARNING MESSAGE 6336 (EQNINC) 6336.0 THE NUMBER OF ARGUMENTS IN THE DEQATN ENTRY ID=%1 IS %2. IT IS SUPPOSED TO BE %3. USER INFORMATION: USER ACTION: CHECK NX NASTRAN USERS MANUAL FOR THE BULK DATA ENTRY THAT REFERS TO THIS DEQATN ENTRY. *** SYSTEM FATAL MESSAGE 6338 (GIFACD) 6338.0 LOGIC ERROR: IERR=%1, N=%2, J=%3, X=%4 USER ACTION: CONTACT SIEMENS PLM SO FTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6341 (PEDGED) 6341.0 NFUN=%1 OBTAINED FROM PEDGEL SUBROUTINE IS INCONSISTENT WITH (PEDGE - 1)=%2 FROM SLT RECORD. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. SYSTEM FATAL MESSAGE 6341 (EMSPPD) *** 6341.1 NFUN=%1 FOR KEDGE=%2 OBTAINED FROM EQEPL SUBROUTINE IS INCONSISTENT WITH (PEDGE - 1)=%3 FROM EHT RECORD. *** SYSTEM FATAL MESSAGE 6341 (EMBPPD) 6341.2

417 NFUN=%1 FOR KEDGE=%2 OBTAINED FROM EBEPL SUBROUTINE IS INCONSIS - 1)=%3 FROM EHT RECORD. TENT WITH (PEDGE *** SYSTEM FATAL MESSAGE 6341 (PF3SPD) 6341.3 NFUN=%1 FOR KDOFTP=%2 OBTAINED FROM %3 SUBROUTINE IS - INCONSISTENT WITH (PEDGE 1)=%4 FROM SLT RECORD. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 6342 (PFACED) 6342.0 FOR FACE ID=%1 ONLY ONE OF THE FIELDS: FEQNID, FTABID, AND F1 THROUGH F9 CAN BE USED TO SPECIFY THE PFACE LOAD. USER ACTION: CHECK PFACE ENTRY FOR THIS FACE. DGED) *** USER FATAL MESSAGE 6342 (PE 6342.1 FOR EDGE ID=%1 ONLY ONE OF THE FIELDS: FEQNID, FTABID, AND F1 THROUGH F4 CAN BE USED TO SPECIFY THE PEDGE LOAD. USER ACTION: CHECK PEDGE ENTRY FOR THIS EDGE. *** USER FATAL MESSAGE 6342 (FCEN3D) 6342.2 FOR FACE ID=%1 ON GMBC LOAD ID=%2 SPC ID=%3 ONLY ONE OF THE FIELDS: IDEQN, IDTAB, AND D1 THROUGH D6 CAN BE USED TO SPECIFY THE ENFORCED DISPLACEMENT. USER ACTION: CHECK THE BCFACE OR BCSURF ENTRIES *** USER FATAL MESSAGE 6342 (EMGPTD) 6342.3 ELEMENT ID=%1 ONLY ONE OF THE FIELDS: FEQNID, FTABID, FOR AND F1 THROUGH F4 CAN BE USED TO SPECIFY THE TEMPERATURE. USER ACTION: CHECK TEMPF ENTRY SPECIFICATION. *** USER FATAL MESSAGE 6342 (EGENDD) 6342.4 FOR EDGE ID=%1 ON GMBC LOAD ID=%2 SPC ID=%3, ONLY ONE OF THE FIELDS: IDEQN, IDTAB, AND D1 THROUGH D4 CAN BE USED TO SPECIFY THE ENFORCED DISPLACEMENT. USER ACTION: CHECK THE BCEDGE, BCCURVE, BCFACE OR BCSURF ENTRIES *** USER FATAL MESSAGE 6342 (FCEN4D) 6342.5 FOR FACE ID=%1 ON GMBC LOAD ID=%2 SPC ID=%3 ONLY ONE OF THE FIELDS: IDEQN, IDTAB, AND D1 THROUGH D9 CAN BE USED TO SPECIFY THE ENFORCED DISPLACEMENT. USER ACTION: CHECK THE BCFACE OR BCSURF ENTRIES. *** USER FATAL MESSAGE 6343 (PFACED) 6343.0 NO METHOD CAN BE FOUND ON THE PFACE ENTRY ID=%1 TO DEFINE THE LOAD. USER ACTION: CHECK PFACE ENTRY FOR THIS FACE.

418 *** USER FATAL MESSAGE 6343 (PEDGED) 6343.1 NO METHOD CAN BE FOUND ON THE PEDGE ENTRY ID=%1 TO DEFINE THE LOAD. USER ACTION: CHECK PEDG E ENTRY FOR THIS EDGE. *** SYSTEM FATAL MESSAGE 6345 6345.0 MDOFS OF KDOFTP=%1 IS EQUAL TO %2 WHICH IS LESS THAN THE MINIMUM ALLOWABLE VALUE OF 3. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 6349 (PFTBLS) 6349.0 TABLE3D ID=%1 REQUIRES THE SPECIFICATION OF AT LEAST 4 POINTS. *** USER FATAL MESSAGE 6350 (PFTBLI) 6350.0 THE TABLE3D ENTRY ID=%1 DOES NOT EXIST. *** SYSTEM FATAL MESSAGE 6352 (%1) 6352.0 LOGIC ERROR: KERROR=%1. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6352 (AAAAAA) 6352.1 LOGIC ERROR: KERROR=%1, IAPP=%2 USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6352 (PFUNSD) 6352.2 LOGIC ERROR: ILLEGAL VALUE FOR IOPT OR NMAX. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: IOPT=%1 NMAX=%2 *** SYSTEM FATAL MESSAGE 6352 (AAAAAAAA) 6352.3 OR=%1, GID=%2 LOGIC ERROR: KERR PROGRAMMER INFORMATION: THE PARENT SUBROUTINE IS %3 USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6352 (REMENT) 6352.4 LOGIC ERROR: KERROR=%1 USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: RECORD NAME = %2 *** SYSTEM FATAL MESSAGE 6352 (BMPEED) 6352.5 LOGIC ERROR: KERROR=%1. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: KDOFTP=%2 DOFSIL= %3

419 SYSTEM FATAL MESSAGE 6352 (ADPVAL) *** 6352.6 LOGIC ERROR: KERROR=%1 PROGRAMMER INFORMATION: OPTION=%2 USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6352 6352.7 LOGIC ERROR: KERROR=%1, ADAPT ID=%2. USER ACTION: CONTA CT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER INFORMATION MESSAGE 6352 6352.8 SYSTEM(228)=%1 HAS BEEN SPECIFIED TO USE %2 METHOD FOR - ESTIMATE. ADAPTIVITY ERROR *** SYSTEM FATAL MESSAGE 6352 (ELPOLY) 6352.9 LOGIC ERROR: KERROR=%1. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: KPTYPE=%2, NPTYPE=%3. *** SYSTEM FATAL MESSAGE 6352 (ELPOLY) 6352.10 LOGIC ERROR: KERROR=%1. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMM ER INFORMATION: KGEFB=%2, NGEFB=%3. *** SYSTEM FATAL MESSAGE 6352 (ELVOLD) 6352.11 LOGIC ERROR: KERROR=%1. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: LTAB=%2, NELEM=%3, NWD=%4, KPTYPE=%5. *** SYSTEM FATAL MESSAGE 6352 (ELVOLD) 6352.12 LOGIC ERROR: KERROR=%1. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: KPTYPE=%2 IS NOT SUPPORTED. *** SYSTEM FATAL MESSAGE 6352 (ELVOLW) 6352.13 LOGIC ERROR: KERROR=%1. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: KPTYPE=%2, IVOLX=%3 *** SYSTEM FATAL MESSAGE 6352 (ELVOLW) 6352.14 LOGIC ERROR: KERROR=%1. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: KPTYPE=%2, LVOLX=%3, NWD=%4, NELEM=%5

420 *** SYSTEM FATAL MESSAGE 6352 (ELVOLW) 6352.15 LOGIC ERROR: KERROR=%1. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: KPTYPE=%2 *** SYSTEM FATAL MESSAGE 6352 (%1) 6352.16 LOGIC ERROR: KERROR=%2. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: KCOL=%3 IS NOT SUPPORTED. THE PARENT SUBROUTINE IS %4 *** SYSTEM FATAL MESSAGE 6352 (EMGPGD) 6352.17 LOGIC ERROR : JXGAUS(1..3) = %1 JW = %2 USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6352 (ADPOLY) 6352.18 LOGIC ERROR: KERROR=%1. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INF ORMATION: III=%2%3%4, IP123=%5, GEFB=%6, KORDER=%7, EID=%8 *** SYSTEM FATAL MESSAGE 6352 (ADPSAV) 6352.19 LOGIC ERROR: KERROR=%1. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: IERRN=%2, LERRN=%3, NWERRN=%4 SH OULD ALL BE POSITIVE. *** SYSTEM FATAL MESSAGE 6352 (ADPSAV) 6352.20 LOGIC ERROR: KERROR=%1. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: IPVALN=%2, LPVALN=%3, NWPVALN=%4 SHOULD ALL BE POSITIVE. *** SYSTEM FATAL MESSAGE 6352 (ADPSAV) 6352.21 LOGIC ERROR: KERROR=%1. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: LERRN=%2 IS NOT A MULTIPLE OF NWERRN=%3 *** SYSTEM FATAL MESSAGE 6352 (ADPSAV) 6352.22 LOGIC ERROR: KERROR=%1. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: NVIEWX=%2, NWVIEW=%3,

421 LVIEWX=%4, KPTYPE=%5 *** SYSTEM FATAL MESSAGE 6352 (ADPVLN) 6352.23 LOGIC ERROR: KERROR=%1. USER ACTION: CONTACT SI EMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: NPMRG=%2, NWPMRG=%3, LPMRT=%4 *** SYSTEM FATAL MESSAGE 6352 (ADPVLN) 6352.24 LOGIC ERROR: KERROR=%1. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: NPVAL)=%2, NWPVAL=%3, LPVALO=%4 *** SYSTEM FATAL MESSAGE 6352 (ADPVLN) 6352.25 LOGIC ERROR: KERROR=%1. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: EID=%2 CAN NOT BE FOUND IN THE PVALN TABLE. *** SYSTEM FATAL MESSAGE 6352 (ADPWHY) 6352.26 LOGIC ERROR: KERROR=%1. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: THE PARENT SUBROUTINE IS %2 *** SYSTEM FATAL MESSAGE 6352 (ADPWHY) 6352.27 LOGIC ERROR: KERROR=%1 . USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: EID=%2 IS MISSING FROM THE ERRNEW TABLE. PROGRAMMER INFORMATION: THE PARENT SUBROUTINE IS A8 *** SYSTEM FATAL MESSAGE 6352 (ESTBLD) 6352.28 LOGIC ERROR: KERROR=%1. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: MAXLST=%2 IS SMALLER THAN %3=%4 *** SYSTEM FATAL MESSAGE 6352 (TETIND) 6352.29 LOGIC ERROR: 1 USER ACTION: CONTACT SIEMENS PLM SOFTWARE C USTOMER SUPPORT. PROGRAMMER INFORMATION: GROUP NO = %1, REF. TO INTEGRATION POINT = %2 DOES NOT EXIST *** SYSTEM FATAL MESSAGE 6352 (TETIND) 6352.30

422 LOGIC ERROR: 2 USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. N: IC = %1 IS NOT EQUAL TO NC = %2 PROGRAMMER INFORMATIO *** SYSTEM FATAL MESSAGE 6352 (TETIND) 6352.31 LOGIC ERROR: 3 USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: IN = %1 IS NOT EQUAL TO N = %2 *** SYSTEM FATAL MESSAGE 6352 (GETPVD) 6352.32 LOGIC ERROR: 4 USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: RULE %1 IS NOT INSTALLED. *** USER INFORMATION MESSAGE 6353 (EGENDD) 6353.0 ENFORCED DISPLACEMENT VECTOR IS NULL FOR COMPONENT=I OF EDGE GENERATED BY GRID %1 AND %2 IN FACE ID=%3 ON GMBC LOAD ID=%4 AND SPC ID=%5. *** USER INFORMATION MESSAGE 6353 (EGENDD) 6353.1 ENFORCED DISPLACEMENT VECTOR IS NULL FOR COMPONENT=I OF EDGE ID=%1 ON GMBC LOAD ID=%2 AND SPC ID=%3. *** USER WARNING MESSAGE 6353 (FCUCND) 6353.2 ENFORCED DISPLACEMENT VECTOR FOR COMPONENT=%1 OF FACE ID=%2 ON GMBC LOAD ID=%3 AND SPC ID=%4 IS NULL. *** SYSTEM FATAL MESSAGE 6354 (FCEN3D) 6354.0 ALL COMPONENTS FOR FACE ID=%1 IN FCEND RECORD ARE ZERO. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6354 (EGENDD) 6354.1 ALL COMPONENTS OF EDGE ID=%1 IN EGEND RECORD ARE ZERO. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6355 (FCEN3D) 6355.0 GRID ID(S) IN GPSIL ARRAY AND FCEND TABLE ARE NOT CONSISTENT. USER ACTION: CONTACT SI EMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: GP IN FCEND:%1 %2 GP IN GPSIL:%3 %4 *** SYSTEM FATAL MESSAGE 6355 (EGENDD) 6355.1

423 GRID ID(S) IN GPSIL ARRAY AND EGEND TABLE ARE NOT CONSISTENT. ARE CUSTOMER USER ACTION: CONTACT SIEMENS PLM SOFTW SUPPORT. PROGRAMMER INFORMATION: GP IN EGEND:%1 GP IN GPSIL:%2 *** SYSTEM FATAL MESSAGE 6355 (FCEN4D) 6355.2 GRID ID(S) IN GPSIL ARRAY AND FCEND TABLE ARE NOT CONSISTENT. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: FCEND:%1 %2 GPSIL:%3 %4 *** USER FATAL MESSAGE 6357 6357.0 NO GRID POINTS FOUND *** USER WARNING MESSAGE 6359 (PREMAT) 6359.0 MAT2 OR MAT9 ENTRY COMBINED WITH ISOTROPIC CREEP FORMULATION MAY PRODUCE INCORRECT RES ULTS. *** USER INFORMATION MESSAGE 6361 (ULANCZ) 6361.0 UNSYMMETRIC REAL LANCZOS DIAGNOSTICS. -- *** SYSTEM INFORMATION MESSAGE 6361 6361.1 REIGL MODULE DIAGNOSTICS THESE DIAGNOSTICS ARE REQUESTED BY MSGLVL = %1 ON THE EIGRL ENTRY. INITIAL PROBLEM SPECIFICATION DEGREES OF FREEDOM = %2 MESSAGE LEVEL = %3 LEFT END POINT = %4 NUMBER OF MODES = %5 OUTPUT UNIT = %6 RIGHT END POINT = %7 MODE FLAG = %8 SIZE OF WORKSPACE = %9 CENTER FREQUENCY = %10 PROBLEM TYPE = %11 MAXIMUM BLOCK SIZ E = %12 ACCURACY REQUIRED = %13 SHIFTING SCALE = %14 *** USER INFORMATION MESSAGE 6361 (CLASDD) 6361.2 COMPLEX LANCZOS DIAGNOSTICS. THIS DIAGNOSTICS IS REQUESTED BY DIAG12. INITIAL PROBLEM SPECIFICATION DEGREES OF FREEDOM = %1 ACCURACY REQUIRED = %2 REQUESTED MODES = %3 NUMBER OF SHIFTS = %4 DAMPING MODE FLAG = %5 SIZE OF WORKSPACE = %6

424 *** SYSTEM FATAL MESSAGE 6362, (EVLFCE), 6362.0 THE ENFORCED DISPLACEMENT VALUE OF THE GRIP POINT WHICH BELONG S TO THE FACE ID = %1 DOES NOT EXIST. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER ACTION: CHECK ENFORCED DISPLACEMENT VECTOR ROUTINE. *** SYSTEM FATAL MESSAGE 6363, (EVLFCE), 6363.0 THE ENFORCED DISPLACEMENT VECTOR COL UMN DOES NOT EXIST FOR FACE ID = %1 FOR COMPONENT = %2 USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER ACTION: CHECK ENFORCED DISPLACEMENT VECTOR ROUTINE (IERROR=%3). *** SYSTEM FATAL MESSAGE 6363, (EVLEDG), 6363.1 THE ENFORCED DISPLACEMENT VECTOR COLUMN DOES NOT EXIST FOR EDGE ID = %1 FOR COMPONENT = %2 USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER ACTION: CHECK ENFORCED DISPLACEMENT VECTOR ROUTINE (IERROR=%3). SYSTEM FATAL MESSAGE 6364, (EVLFCE), *** 6364.0 THE ENFORCED DISPLACEMENT VECTOR LENGTH DOES NOT MATCH WITH THE CALCULATED VALUE FOR THE FACE ID = %1 USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER ACTION: CHECK ENFORCED DISPLACEMENT ROUTINE. VECTOR *** SYSTEM FATAL MESSAGE 6364, (EVLEDG), 6364.1 THE ENFORCED DISPLACEMENT VECTOR LENGTH DOES NOT MATCH WITH THE CALCULATED VALUE FOR THE EDGE ID = %1 USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. ENFORCED DISPLACEMENT PROGRAMMER ACTION: CHECK VECTOR ROUTINE. *** SYSTEM FATAL MESSAGE 6365, (EVLFCE), 6365.0 THE COMPONENT: %1 IS INVALID FOR FACE ID = %2 USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER ACTION: CHECK SPCDE/SPCDF RECORDS.

425 *** USER FATAL MESSAGE 6367, (POLYD), 6367.0 GRID IDS =%1 ARE VERY CLOSE TO EACH OTHER USER ACTION: CHECK GRID ENTRIES. *** USER FATAL MESSAGE 6367, (POLYD), 6367.1 GRID OR POINT ID =%1 FOR ELEMENT ID =%2 IS UNDEFINED. *** USER FATAL MESSAGE 6367, (OPTGPC) 6367.2 GRID OR POINT ID =%1 FOR FEEDGE/FEFACE ID = %2 IS UNDEFINED. *** USER FATAL MESSAGE 6367, (EVLPND), 6367.3 GRID OR POINT ID =%1 FOR FEEDGE ID =%2 IS UNDEFINED. *** USER FATAL MESSAGE 6369, (GP0DA), 6369.0 THE SELECTED ADAPT SET ID =%1 CANNOT BE FOUND. USER ACTION: CHECK ADAPT AND PSET BULK DATA ENTRIES. *** USER FATAL MESSAGE 6370, (POLYD), 6370.0 FINAL EDGE OR FACE TABLE IS INVALID. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 6370, (GP0P4) 6370.1 INVALID DATA *** USER FATAL MESSAGE 6370, (GP0P4), 6370.2 FINAL ELEMENT PROPERTY TABLE CREATED IN GP0D IS INVALID. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 6370, 6370.9 FINAL EDGE OR FACE TABLE CREATED IN GP0DA IS INVALID. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 6371, (GP0DA), 6371.0 BOTH THE ADAPT AND PSET ENTRIES ARE PRESENT. USER INFORMATION : EITHER THE ADAPT OR PSET ENTRY MAY BE SPECIFIED BUT NOT BOTH. *** SYSTEM FATAL MESSAGE 6374, 6374.0 - ELEMENT ELEMENT TYPE =%1 IS NOT SUPPORTED IN P ANALYSIS. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: GP0 MODULE FAILED TO RECOGNIZE THIS ELEMENT TYPE CHECK GPTABD ROUTINE. *** SYSTEM FATAL MESSAGE 6375, (GP0E), 6375.0 THE FINAL EDGE OR FACE TABLE CREATED IN GP0D IS INVALID. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT.

426 *** SYSTEM FATAL MESSAGE 6376, (GP0E), 6376.0 THE FINAL EDGE TABLE CREATED IN GP0H IS INVALID. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6376, (GP0E), 6376.1 THE FINAL TABLE 2 CREATED IN GP0E IS INVALID. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6376, (GP0DE), 6376.2 TABLE 2 CREATED IN GP0DA IS INVALID. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. USER FATAL MESSAGE 6376 (CIFGRI) *** 6376.3 THE GMBNDC BOUNDARY ID = %1 REFERENCED BY GMINTC ELEMENT ID = %2 HAS AN UNDEFINED P - ELEMENT EDGE BETWEEN GRID ID = %3 AND GRID ID = %4. *** SYSTEM FATAL MESSAGE 6376, (CIECHT), 6376.4 THE FINAL TABLES CREATED IN THE %1 ROUTINE IS INVALID. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6376, (CSFFAC), 6376.5 THE EDGE TABLE CREATED IN THE %1 ROUTINE IS INVALID. USER ACTION: CONTACT SIEMENS P LM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 6377, (GP0H), 6377.0 THE GRID POINTS SPECIFIED ON FEFACE BULK DATA ENTRY ID = %1 DO NOT DEFINE A VALID THREE OR - FOUR SIDED FACE OF ANY P ELEMENT. USER ACTION: CHECK FEFACE AND/OR SET ENTRIES. *** USER FATAL MESSAGE 6379, (GP0F), 6379.0 THE FEEDGE ID = %1 REFERENCED BY %2 IS UNDEFINED. *** USER WARNING MESSAGE 6379, (GP0F), 6379.1 THE %1 ID=%2 ASSOCIATED WITH GMSURF ID=%3 HAS NO ASSOCIATED FEFACE, THUS LOAD WILL BE IGNORED. *** USER WARNING MESSAGE 6379, (GP0F), 6379.2 THE %1 ID=%2 ASSOCIATED WITH GMCURV ID=%3 HAS NO ASSOCIATED FEEDGE, THUS LOAD WILL BE IGNORED. *** USER WARNING MESSAGE 6379, (CSFFAC), 6379.3 THE FACE ID =%1 SPECIFIED ON GMBNDS BULK DATA ENTRY ID = %2 DOES NOT DEFINE A VALID FACE OF ANY P - ELEMENT.

427 USER ACTION: CHECK FEFACE AND/OR SET ENTRIES. *** USER WARNING MESSAGE 6379, (CSFSRF), 6379.4 THE SURFACE ID =%1 SPECIFIED ON GMBNDS BULK D ATA ENTRY ID =%2 DOES NOT DEFINE A VALID FACE OF ANY P - ELEMENT. THE GRID ID =%1 SPECIFIED ON GMBNDS BULK DATA ENTRY ID 6379.5 =%2 DOES NOT BELONG TO THE P - ELEMENT BOUNDARY. USER ACTION: CHECK GMBNDS AND/OR FEFACE ENTRIES. USER ACTION: CHECK FEFAC E AND/OR SET ENTRIES. *** USER FATAL MESSAGE 6380, (GP0F), 6380.0 THE FEFACE ID = %1 REFERENCED BY %2 IS UNDEFINED. *** USER FATAL MESSAGE 6381, 6381.0 THE FEFACE CORRESPONDING TO GMSURF ID = %1 REFERENCED BY %2 IS UNDEFINED. *** USER FATAL MESSAGE 6381, 6381.1 THE FEEDGE CORRESPONDING TO GMCURV ID = %1 REFERENCED BY %2 IS UNDEFINED. *** USER FATAL MESSAGE 6381, (GP0F), 6381.2 INVALID THE GMCURV OR GMSURF ID =%1 REFERENCED BY GMLOAD ID =%2 IS UNDEFINED. USER FATAL MESSAGE 6381, (GBCSF), *** 6381.4 THE GMSURF ID = %1 REFERENCED BY %2 IS UNDEFINED. *** USER FATAL MESSAGE 6381, (GBCCE), 6381.6 THE GMCURV ID = %1 REFERENCED BY %2 IS UNDEFINED. *** SYSTEM FATAL MESSAGE 6382, (GP0F), 6382.0 THE FINAL GRIDN TABLE CREATED IN GP0D IS INVALID. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 6385, (GSPCCE), 6385.0 THE FEEDGE ID = %1 REFERENCED BY %2 IS UNDEFINED. , (GSPCSF), *** USER FATAL MESSAGE 6386 6386.0 THE FEFACE ID = %1 REFERENCED BY %2 IS UNDEFINED. *** SYSTEM FATAL MESSAGE 6387, (GSPCSF), 6387.0 FINAL GRIDN TABLE CREATED IN GP0DA IS INVALID. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. USER INFORMATION MESSAGE 6388, (GP0), *** 6388.0 ADAPT CASE CONTROL ENTRY EXIST, HOWEVER THERE ARE NO P - ELEMENTS IN THE DECK. *** USER INFORMATION MESSAGE 6388, (GP0), 6388.1 ADAPT CASE CONTROL ENTRY EXIST, HOWEVER PVAL AND/OR PSET ENTRY DOES NOT EXIST

428 *** USER FATAL MESSAGE 6389, (GP0H), 6389.0 THERE ARE DUPLICATE FACE ENTRIES WITH ID =%1. *** USER FATAL MESSAGE 6390, (GP0I), 6390.0 ELEMENT ID =%1 TYPE HEXA20 OR PENTA15 AND/OR TETRA10 ARE NOT SUPPORTED IN P - ELEMENT ANALYSIS. USER ACTION: CHE CK ELEMENT CONNECTION ENTRY OR SET ENTRY. *** USER FATAL MESSAGE 6391, (GP0H), 6391.0 THE GMSURF ID = %1 REFERENCED BY %2 ID =%3 IS UNDEFINED. *** USER FATAL MESSAGE 6392 , (EVLPND), 6392.0 POINT ID =%1 FOR FEEDGE ID =%2 HAS AN ILLEGAL LOCATION. *** USER FATAL MESSAGE 6392 , (EVLPND), 6392.1 POINT IDS =%1 FOR FEEDGE ID =%2 HAVE ILLEGAL LOCATIONS. *** USER FATAL MESSAGE 6394, (GP0I), 6394.0 FEFACE/FEEDGE ID = %1 REFERENCED BY ELEMENT TYPE %2 ID = %3 USER INFORMATION: THIS ELEMENT TYPE CANNOT REFERENCE AN FEEDGE OR FEFACE ENTRY. *** USER FATAL MESSAGE 6395, (MRGCOR), 6395.0 THE GRID POINTS SPECIFIED ON FEFACE ENTRY ID =%1 DO NOT DEFIN E A VALID EDGE OF ANY P - ELEMENT. *** USER FATAL MESSAGE 6395, (GP0I), 6395.1 THE GRID POINTS SPECIFIED ON FEEDGE BULK DATA ENTRY ID = %1 DO NOT DEFINE A VALID EDGE OF ANY P ELEMENT. - USER ACTION: CHECK FEEDGE AND/OR SET ENTRIES. *** USER FATAL MESSAGE 6397, (GP0I), 6397.0 THE GMCURV ID = %1REFERENCED BY FEEDGE ID = %2 IS UNDEFINED. *** SYSTEM FATAL MESSAGE 6398, (MRGCOR), 6398.0 PRELIMINARY EDGE TABLE CREATED IN GP0B IS INVALID. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SU PPORT. *** USER FATAL MESSAGE 6399, (MRGCOR), 6399.0 FOR EDGE ID%1 CIDS PROVIDED BY FEFACE ID =%2 ARE DIFFERENT. USER ACTION: CHECK FEFACE ENTRIES *** USER FATAL MESSAGE 6399, (MRGCOR), 6399.1 FOR THE EDGE (G1 - G2) =%1 - %2 CIDS%3,%4 PROVIDED BY FEFACE ENTRIES ARE DIFFERENT. USER ACTION: FOR SUCH CASE EITHER PROVIDED FEEDGE ENTRY FOR THAT EDGE, OR CHECK CIDS IN FEFACE ENTRIES. *** USER FATAL MESSAGE 6399, (MRGCOR), 6399.2

429 FOR THE EDGE (G1 - G2) =%1,%2 THERE ARE TWO INTERSECTING SURFACES.%3,%4 USER ACTION: FOR SUCH CASE PROVIDE FEEDGE ENTRY FOR THAT EDGE. *** USER FATAL MESSAGE 6400, (GP0I), 6400.0 THERE ARE DUPLICATE FEEDGE ENTRIES WITH ID = %1. *** SYSTEM FATAL MESSAGE 6402, (BCEDG), 6402.0 THE FINAL EDGE OR FACE TABLE CREATED IN GP0F IS INVALID. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 6403 (GECINT) 6403.0 THE GMBNDC BOUNDARY ID = %1 REFERENCED BY %2 ID = %3 IS UNDEFINED. *** USER FATAL MESSAGE 6403 (CIFEDG) 6403.1 THE BOUNDARY GMBNDC ID = %1 REFERENCED BY GMINTC ID = %2 HAS AN UNDEFINED FEEDGE ID = %3. *** USER FATAL MESSAGE 6403 (CIFEDG) 6403.2 THE GMBNDC BOUNDARY ID = %1 REFERENCED BY GMINTC ELEMENT ID = %2 IS NOT CONTINUOUS AT GRID ID = %3. *** USER FATAL MESSAGE 6403, (CIFCRV), 6403.3 THE GMBNDC ID = %1 REFERENCED BY %2 ID =%3 IS NOT CONTINUOUS AT GRID ID=%4. *** USER FA TAL MESSAGE 6403, (BCEDG), 6403.4 THE FEEDGE ID = %1 REFERENCED BY %2 ID =%3 IS UNDEFINED. *** USER FATAL MESSAGE 6403, (CSFSRF), 6403.5 THE GMBNDS ID = %1 REFERENCED BY %2 ID =%3 DOES NOT DEFINE A VALID FACE OF ANY P ELEMENT. - USER ACTION: CHECK GMBNDS ENTRIES. *** USER FATAL MESSAGE 6403 (GESINT) 6403.6 THE GMBNDS BOUNDARY ID = %1 REFERENCED BY %2 ID = %3 IS UNDEFINED. *** USER FATAL MESSAGE 6404, (BCFAC), 6404.0 THE FEFACE ID = %1 REFERENCED BY %2 ID =%3 IS UNDEFINED. *** SYSTEM FATAL MESSAGE 6405, (GP3D), 6405.0 THE GEOM3 TABLE CONTAINS AN INVALID TEMPF RECORD SET ID = %1 USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. SYSTEM FATAL MESSAGE 6406 (GP4) *** 6406.0 GRID POINT ID= %1 ON AN SPCP/SPCDP ENTRY HAS COMPONENT= %2 GREATER THAN MAX. NDOF= %3

430 USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER ACTION: CHECK SPCP/SPCDP ENTRIES CREATED IN GP0 MODULE. *** SYSTEM FATAL MESSAGE 6407, (MDGM4F), 640 7.0 ENFORCED DISPLACEMENT VECTOR LENGTH DOES NOT MATCH WITH THE CALCULATED VALUE FOR THE FEEDGE/FEFACE ID = %1 USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: CHECK ENFORCED DISPLACEMENT VECTOR ROUTINE. *** SYSTEM FATAL MESSAGE 6408 (TA1A) 6408.0 NO ELEMENT HIERARCHICAL DATA FOR THE ELEMENT ID =%1 WAS FOUND. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. ACTION: CHECK EHT TABLE. PROGRAMMER *** SYSTEM WARNING MESSAGE 6409, (TPUSET) 6409.0 - ELEMENT USET PRINT, SIL TABLE MUST EXIST AS A THIRD FOR P INPUT TO TABPRT MODULE. *** SYSTEM INFORMATION MESSAGE 6410 (IFP8). 6410.0 BEGIN PROCESSING OF MATHP ENTRY ID =%1 System information: This message is issued when the curve - fitting algorithm is activated to produce the material constants for hyperelastic materials based on Data entry is experimental data. An image of the produced MATHP Bulk printed after this message. *** SYSTEM FATAL MESSAGE 6411 (LSQRS). 6411.0 SINGULAR VALUE DECOMPOSITION DID NOT CONVERGE. System information: This message is issued by the Singular Value Decomposition (SVD) method which is used by the curve - fitting algorithm for the hyperelastic material constants. The message occurs when the SVD fails to converge, which may be caused by an error in the experimental data. Check the input in the TABLES1 Bulk Data entries for errors. *** SYSTEM FATAL MESSAGE 6411 (LNNHERR) 6411.1 INTERNAL FAILURE IN THE LANCZOS PROCEDURE: SVD QL PROCEDURE FAILED TO CONVERGE. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. RANK DEFICIENCY HAS BEEN DETECTED IN DATA BLOCK %1 6412.0 RANK DEFICIENCY HAS BEEN DETECTED IN DATA BLOCK P 6412.1

431 THAT IS THE PRODUCT OF THE MATRIX %1 BY %2 *** SYSTEM WARNING MESSAGE 6412 6412.6 RANK DEFICIENCY HAS BEEN DETECTED. RANK =%1. FULL RANK =%2 User information: This message is issued by t he Singular Value Decomposition (SVD) method fitting algorithm for the hyperelastic which is used by the curve - material constants. The message occurs when the least squares problem for estimation of the material parameters is rank deficient, i.e., the rank is less than the number of material parameters (full rank). This message may be issued for either distortional (Aij) or volumetric (Di) parameter fitting. - The program will proceed to find a non unique solution. However, it is best to try to avoid rank deficiency by providing more experimental data for curve fitting or lowering the order of the strain energy polynomial, NA or ND in the MATHP Bulk Data entry. *** USER WARNING/FATAL MESSAGE 6413 6413.0 INSUFFICIENT MEMORY FOR THE SYMBOLIC PHASE OF SPARSE DECOMPOSITION. USER ACTION : INCREASE MEMORY BY AN ESTIMATED %1 WORDS. THE EXACT MEMORY REQUIREMENT FOR THE SYMBOLIC PHASE MAY BE OBTAINED BY INCREASING MEMORY BY AT LEAST %2 WORDS. *** USER WARNING/FATAL MESSAGE 6413 6413.1 INSUFFICIENT MEMORY FOR THE SYMBOLIC PHASE OF SPARSE DECOMPOSITION. USER ACTION : INCREASE MEMORY BY AN ESTIMATED %1 WORDS. *** USER WARNING/FATAL MESSAGE 6413 (DFMSYN) 6413.2 INSUFFICIENT MEMORY FOR THE SYMBOLIC P HASE OF SPARSE DECOMPOSITION (BEND). USER ACTION : INCREASE MEMORY BY AN ESTIMATED %1 WORDS. *** USER WARNING/FATAL MESSAGE 6413 (DFMSYN) 6413.3 INSUFFICIENT MEMORY FOR THE SYMBOLIC PHASE OF SPARSE DECOMPOSITION (METIS). USER ACTION : INCREASE MEMORY BY AN ESTIMATED %1 WORDS. *** SYSTEM FATAL MESSAGE 6414 (TRD2CD) 6414.0 THE FACTOR MATRIX (FIST=%1) CANNOT BE USED WITH THE SPARSE METHOD. USER INFORMATION: THE FACTOR MATRIX WAS PROBABLY OBTAINED VIA THE RESTART OR DBLOCATE FMS STATEMENT

432 OF A DATABASE CREATED IN A PRIOR VERSION OF THE PROGRAM. USER ACTION: RECOMPUTE THE FACTOR MATRIX IN THIS VERSION OF THE PROGRAM. *** SYSTEM INFORMATION MESSAGE 6415 (DFNSB) 6415.0 MORE EFFICIENT PROCESSING IN FBS MAY BE PO SSIBLE BY SETTING SYSTEM(146) TO 2, 3 OR 4 WHICH WILL RESPECTIVELY MULTIPLY THE FBS MEMORY ALLOCATION FOR THE FACTOR BY 2, 3 OR 4 *** USER WARNING MESSAGE 6417 (SQD41D) 6417.0 THE (%1) OPTION FOR STRESSES IS NOT AVAILABLE FOR NONLINEAR MATERIAL OR COMPOSITE ELEMENTS. USER INFORMATION: STRESS (CENTER) WILL BE APPLIED TO THOSE ELEMENTS. User information: CUBIC refers to corner output for element STRESS, STRAIN, and FORCE. Corner output is not available for nonlinear analysis, so only center sses are computed for nonlinear CQUAD4 elements. stre *** USER WARNING MESSAGE 6418 (SDR2A) 6418.0 THE %1 OPTION FOR STRAINS OVERRIDES ALL OTHER OPTIONS IN THE FORCE COMMANDS. User information: CUBIC refers to corner output for element STRESS, STRAIN, and FORCE. When corner output is selected for CQUAD4 elements, only one output type -- CORNER or CENTER -- is available in the entire run, regardless of output request (STRESS, STRAIN, and FORCE) and subcase. The hierarchy is as follows: 1. STRESS in th e first subcase determines the request type (CENTER or CORNER). 2. STRESS above the subcase level determines the type. 3. STRAIN in the first subcase determines the type. 4. STRAIN above the subcase level determines the type. case determines the type. 5. FORCE in the first sub 6. FORCE above the subcase level determines the type. The second (and successive) subcases are not used to determined output type (CENTER or CORNER). *** USER WARNING MESSAGE 6418 (SDR2A) 6418.1 THE %1 OPTION FOR STRESS ES OVERRIDES ALL OTHER OPTIONS IN STRAIN AND FORCE COMMANDS. User information: CUBIC refers to corner output for element STRESS, STRAIN, and FORCE. When corner output is selected for CQUAD4 elements, only one output type -- CORNER or CENTER -- is availabl e in the entire run, regardless of output request (STRESS, STRAIN, and FORCE) and subcase. The hierarchy is as follows:

433 1. STRESS in the first subcase determines the request type (CENTER or CORNER). 2. STRESS above the subcase level determines the typ e. 3. STRAIN in the first subcase determines the type. 4. STRAIN above the subcase level determines the type. 5. FORCE in the first subcase determines the type. 6. FORCE above the subcase level determines the type. are not used to determined The second (and successive) subcases output type (CENTER or CORNER). *** USER WARNING MESSAGE 6418 (SDR2A) 6418.2 THE %1 OPTION FOR STRESS CARD OVERRIDES ALL OTHER OPTIONS ON THE STRAIN CASE CONTROL CARD. *** USER FATAL MESSAGE 6419 6419.0 THE NUMBER OF GAUSS POINTS IN %1 DIRECTION IS GREATER THAN THE MAXIMUM ALLOWED (%2). USER ACTION: CHECK THE "IN" FIELD OF THE PSOLID ENTRY FOR ELEMENT ID = %3. *** USER FATAL MESSAGE 6419 (TBEMPD) 6419.2 THE NUMBER OF GAUSS POINTS %1 GREATER THAN THE MAXIMUM ALLOWED (%2). USER ACTION: CHECK THE "IN" FIELD OF THE PSOLID ENTRY FOR ELEMENT ID = %3. *** USER FATAL MESSAGE 6419 (PGAUSS) 6419.3 - DIRECTION = %2 IS THE NUMBER OF GAUSS POINTS IN %1 GREATER THAN THE MAXIMUM ALLOWED (%3). USER ACTION: CHECK THE "IN" FIELD OF THE %4 ENTRY FOR ELEMENT ID = %5. *** USER FATAL MESSAGE 6419 6419.4 THE NUMBER OF GAUSS POINTS IN %1 DIRECTION IS GREATER THAN THE MAXIMUM ALLOWED (%2). USER ACTION: CHECK THE "IN" FIELD OF THE PSOLID ENTRY FO R ELEMENT ID = %3. *** USER FATAL MESSAGE 6419 (EBEMPD) 6419.6 THE NUMBER OF GAUSS POINTS %1 GREATER THAN THE MAXIMUM ALLOWED (%2). USER ACTION: CHECK THE "IN" FIELD OF THE PSOLID ENTRY FOR ELEMENT ID = %3. *** USER WARNING MESSAGE 6419 (TA1) 6419.7 IN=2 OPTION ON TETRAS WITH MID - SIDE NODES IS NOT ALLOWED. IN=3 WILL BE USED INSTEAD. *** USER WARNING MESSAGE 6419 (TA1) 6419.8 IN=3 OPTION ON HEXAS OR PENTAS WITHOUT MIDSIDE NODES IS NOT ALLOWED FOR NONLINEAR ANA LYSIS. IN=0 WILL BE

434 USED INSTEAD. *** USER FATAL MESSAGE 6420 (GONCED) 6420.0 ELEMENT ID = %1 REFERENCES A MATERIAL ID = %2 WHICH DOES NOT IDENTIFY A MAT1, MAT9 OR MAT11 ENTRY. *** USER WARNING MESSAGE 6422 (FA2) 6422.0 THE EIGENVECTOR CORRESPONDING TO THE EIGENVALUE %1,%2 IS NOT AVAILABLE. USER ACTION: REQUEST ADDITIONAL ROOTS ON THE NDJ FIELD OF THE EIGC BULK DATA ENTRY. *** USER FATAL MESSAGE 6423 (DIAGON) 6423.0 THE "WHOLE" OPTION OF THE DIAGONAL MODULE CANNO T BE PERFORMED ON A SPARSE FACTOR MATRIX *** SYSTEM FATAL MESSAGE 6424 (UFBSS) 6424.0 THE NUMBER OF ROWS IN THE LOAD VECTOR AND THE FACTOR MATRIX ARE INCOMPATIBLE LOAD VECTOR ROWS = %1 FACTOR MATRIX ROWS = %2 *** SYSTEM FATAL MESSAGE 6425 (EMA). 6425.0 THE KDICTP TABLE AND KDICTP TRAILER ARE INCONSISTENT. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT *** SYSTEM FATAL MESSAGE 6425 (MIRROD). 6425.1 THE KDICTP AND SILS TABLES ARE INCONSISTENT. USER AC TION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT *** USER FATAL MESSAGE 6426 (RMG2) 6426.0 THE CAVITY ID=%1 REFERENCES UNDEFINED RADIATION MATRIX. USER INFORMATION: THE RADIATION MATRIX MUST BE DEFINED RADLST/RADMTX BULK DATA ENTRIES. ON EITHER RADCAV OR *** USER WARNING MESSAGE 6427 (VIEW) 6427.0 VIEW FACTORS WILL NOT BE COMPUTED FOR RADIATION CAVITY ID=%1 BECAUSE A RADIATION MATRIX IS ALREADY DEFINED. USER INFORMATION: THE RADIATION MATRIX IS DEFINED ON RADMTX BULK DATA ENTRIES. RADLST OR *** SYSTEM WARNING MESSAGE 6428 (ZREAD) 6428.0 LOGIC ERROR -- CALLING SUBROUTINE SPECIFIED NEGATIVE ARRAY LENGTH. PROGRAMMER ACTION : CHECK OPEN CORE METHOD. *** USER WARNING MESSAGE 6430 (ZREAD) 6430.0 MULTIPLE READ PROBLEM IN DATA BLOCK=%1, RECORD=%2 : ARRAY OR UNDEF ITEM IS MORE THAN 100 WORDS.

435 USER ACTION : SPLIT ARRAY OR UNDEF INTO GROUPS SMALLER THAN 100 WORDS. *** USER WARNING MESSAGE 6431 (ZREAD) 6431.0 LOCK=%2, RECORD=%3, A COUNT ITEM AT OFFSET=%1,IN DATA B WITH AN NDDL NAME=%4,CONFLICTS WITH THE ACTUAL NAME=%5. USER INFORMATION : PROBABLE CAUSE IS TOO LITTLE/MUCH DATA ON RECORD=%6. USER ACTION : CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM WARNING MESSAGE 643 2 (ZREAD) 6432.0 THE ITEM NAMES WITH (C) OPTION OF DATA BLOCK=%1, RECORD=%2,HAVE EXCEEDED THE MAXIMUM NUMBER OF %3 PROGRAMMER INFORMATION: PROBABLE CAUSE IS MISMATCH OF NDDL AND ZREAD LIMIT. PROGRAMMER ACTION: : INTRODUCE A BLOCK DATA FOR BOTH ROUTINES. *** SYSTEM WARNING MESSAGE 6433 (ZREAD) 6433.0 - ITEM "TCODE" OF DATA BLOCK=%1, THE DECODED C RECORD=%2, EXCEEDS NORMAL LIMITS "J"=%3 "I"=%4. PROGRAMMER INFORMATION: PROBABLE CAUSE IS WRONG POSITION OF TABLE CODE, OR EARLIER RESET OF (C) ITEMS. *** USER WARNING MESSAGE 6434 (ZREAD) 34.0 64 THE LENGTH OF THE DATA IN DATA BLOCK=%1, RECORD=%2, IS LONGER THAN DESCRIBED IN THE NDDL. USER INFORMATION: IF YOU USED INPUT2, CHECK FOR A NAME MISMATCH. IF YOU MODIFIED THE NDDL CHECK YOUR MODIFICATIONS. USER ACTION : CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM WARNING MESSAGE 6435 (ZREAD) 6435.0 DURING A SECOND READ OF DATA BLOCK=%1, RECORD=%2, AN ERROR OCCURRED. PROGRAMMER INFORMATION: PROBABLE CAUSE IS "EMARK" VARIABLE OVERWRITTEN , OR A REQUEST TO READ THE 3 WORD HEADER OF IFP BLOCK OCCURRED. *** USER FATAL MESSAGE 6437, (MAT) 6437.0 MATHP ENTRY ID = %1 IS SPECIFIED FOR ELEMENT ID = %2, WHICH IS NOT A FINITE DEFORMATION ELEMENT. User information: This message is issued when a hyperelastic material (MATHP) is referenced

436 by an element which is not a finite deformation element. For instance, any element which does not have a PLSOLID or PLPLANE property entry reference. *** USER FATAL MESSAGE 6438, (MAT) 6438.0 MATHP ENTRY ID = %1 CAN NOT BE FOUND FOR FINITE DEFORMATION (HYPERELASTIC) ELEMENT ID = %2. USER ACTION : SPECIFY MATHP ENTRY WITH ID = %3. User information: This message is issued if a PLSOLID or PLPLANE property entry, for a hype relastic element, does not reference a MATHP entry. --- *** USER INFORMATION MESSAGE 6439 (UDSFA) 6439.0 ACTUAL MEMORY AND DISK SPACE REQUIREMENTS FOR SPARSE UNSYM. DECOMPOSITION User information: This message is issued in the .F04 file after dec omposition. It tells how much memory and desk space were actually required. *** USER INFORMATION MESSAGE 6439 (DFMSA) --- 6439.2 ACTUAL MEMORY AND DISK SPACE REQUIREMENTS FOR SPARSE SYM. DECOMPOSITION User information: This message is issued in the .F04 file after decomposition. It tells how much memory and desk space were actually required. *** USER INFORMATION MESSAGE 6439 (DISDCM1) 6439.3 ACTUAL MEMORY AND DISK SPACE REQUIREMENTS FOR DISTRIBUTED SPARSE SYM. D ECOMPOSITION *** USER FATAL MESSAGE 6440 6440.0 ELEMENT %1 REFERS TO AN INVALID PROPERTY ENTRY. USER ACTION: SPECIFY APPROPRIATE PROPERTY ENTRY. *** USER FATAL MESSAGE 6441 (DOPR1Z) 6441.0 DEQATN ENTRY ID = %1, HAS TOO MANY OR TOO FEW ARGUMENTS. USER INFORMATION: THE DEQATN ENTRY HAS %2 ARGUMENTS BUT THE REFERENCING DVPREL2 ENTRY ID = %3 SPECIFIES %4 DESIGN VARIABLES AND %5 DTABLE CONSTANTS. R OF USER ACTION: MODIFY THE INPUT SO THAT THE NUMBE DESIGN VARIABLES PLUS THE NUMBER OF DTABLE CONSTANTS IS EQUAL TO THE NUMBER OF DEQATN ARGUMENTS. *** USER FATAL MESSAGE 6442 (DOPR3J) 6442.0 DEQATN %1, WHICH HAS %2 ARGUMENTS, IS REFERENCED BY A DRESP2 ENTRY %3 WHICH HAS %4 ARGUMENTS. USER A CTION: MODIFY THE INPUT SO THAT THE NUMBER OF ARGUMENTS ON THE DEQATN BULK DATA ENTRY

437 EQUALS THE SUM OF THE NUMBER OF DESIGN VARIABLES, DTABLE CONSTANTS, RESPONSES AND NODES ON THE CORRESPONDING DRESP2 BULK DATA ENTRY. *** USER WARNING MESSAGE 6443 (SQD41D) 6443.0 NO CORNER STRESSES, FORCES, OR STRAINS WILL BE COMPUTED FOR QUAD4 ELEMENT ID = %1 BECAUSE ONE OR MORE OF ITS CORNER THICKNESSES IS ZERO. USER INFORMATION: ALSO, GRID POINT STRESSES WILL BE INCORRECT AT THOSE CORNERS. User information: When requesting corner output for CQUAD4 elements, all membrane thicknesses at the four grid points must be greater than zero. If any thickness is zero, then stresses, forces, and strains are element computations not computed for that element. Subsequent -- -- will not such as gridpoint stresses and stress discontinuities have results from the offending elements. *** USER WARNING MESSAGE 6444 (INPTYP) 6444.0 THE FILE ASSIGNED TO UNIT =%1 CONTAINS DATA THAT IS INCONSISTENT WITH FORM = %2 USER INFORMATION: 1. THIS MAY BE CAUSED BY: A. THE FILE IS ACTUALLY A FORTRAN %3 FILE. B. THE FILE MAY NOT BE A VALID %4 FILE C. THE FILE HAS BEEN MISPOSITIONED BY A PREVIOUS FORTRAN I/O STATEMENT 2. AN ASSIGN FILE MANAGEMENT STATEMENT WAS %5 TO ASSIGN THE FILE PROGRAMMER INFORMATION: THE FILE DOES NOT CONTAIN A %6 *** USER WARNING MESSAGE 6445 (INPTYP) 6445.0 A FORTRAN %1 READ ERROR HAS OCCURRED WHILE PROCESSING UNIT = %2 USER INFORMATION: THE FILE %3 SPECIFIED IN AN ASSIGN FILE MANAGEMENT STATEMENT USER ACTION: VERIFY THE FILE ASSIGNMENT AND CONTENTS OR CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: FORTRAN IOSTAT CODE = %4 *** USER WARNING MESSAGE 6445 (INPTT4) 6445.1 A FORTRAN %1 READ ERROR HAS OCCURRED WHILE PROCESSING UNIT = %2 USER INFORMATION: THE FILE WAS SPECIFIED IN AN ASSIGN FILE MANAGEMENT STATEMENT USER ACTION: VERIFY THE FILE ASSIGNMENT AND CONTENTS OR CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. VERIFY DATA AND FORTRAN FORMAT SPECIFICATION.

438 PROGRAMMER INFORMATION: FORTRAN IOSTAT CODE = %3 *** USER FATAL MESSAGE 6445 (INPTYP1) 6445.2 BIT FILE. - THE FILE SPECIFIED USING UNIT = %1 IS A 64 USER INFORMATION: THIS FILE CANNOT BE OPENED IN AN LP - 64 ILP32 ENVIRONMENT OR USER ACTION: VERIFY THE FILE CONTENTS OR CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 6445 (INPTYP1) 6445.3 THE FILE SPECIFIED USING UNIT = %1 IS OF TYPE UNKNOWN. PENED IN AN LP - USER INFORMATION: THIS FILE CANNOT BE O 64 OR ILP32 ENVIRONMENT USER ACTION: VERIFY THE FILE CONTENTS OR CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 6445 (INPTYP1) 6445.4 THE FILE SPECIFIED USING UNIT = %1 IS A 64 - BIT OP2 FILE AND SWAPPING. NEEDS BYTE USER INFORMATION: THIS FILE CANNOT BE BYTE SWAPPED IN ILP64 ENVIRONMENT USER ACTION: VERIFY THE FILE CONTENTS OR CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM WARNING MESSAGE 6446 (INPTYP) 6446.0 A FORTRAN %1 READ ERROR HAS OCCURRED PROCESSING STRING VARIABLE %2 USER INFORMATION: FORTRAN IOSTAT CODE = %3 STRING IS = %4 *** USER INFORMATION MESSAGE 6447 (SITDRV) 6447.0 ITERATIVE SOLVER DIAGNOSTIC OUTPUT *** USER INFORMATION MESSAGE 6447 (SITDR3) 6447.2 ITERATIVE SOLVER DIAGNOSTIC OUTPUT *** SYSTEM INFORMATION MESSAGE 6447 (SDRVP) 6447.4 DISTRIBUTED PARALLEL ITERATIVE SOLVER DIAGNOSTIC OUTPUT *** USER INFORMATION MESSAGE 6448 6448.0 SOLUTION CONVERGED WITH ITERATIVE METHOD. *** SYSTEM INFORMATION MESSAGE 6448 (SDRVP) 6448.4 SOLUTION CONVERGED WITH ITERATIVE METHOD. *** USER INFORMATION MESSAGE 6449: 6449.0 INTERNAL CONVERGENCE CRITERION WAS NOT PASSED FOR LOAD NUMBER %1 *** SYSTEM INFORMATION MESSAGE 6449 6449.2 INT ERNAL CONVERGENCE CRITERION WAS NOT PASSED FOR %1 RHS(S) OUT OF %2. (PLEASE SEE FIRST %3 LOAD(S) FOLLOWING USER INFORMATION

439 MESSAGE 5293 BELOW) *** SYSTEM INFORMATION MESSAGE 6449 (SDRVP) 6449.7 PROBLEM TOO SMALL FOR COMPUTING OPTIMAL COMMUNICATION PATTERN. SWITCHED TO REGULAR PATTERN. *** USER INFORMATION MESSAGE 6449 (SUCGRD): 6449.8 INTERNAL CONVERGENCE CRITERION WAS NOT PASSED FOR %1 RHS(S) OUT OF %2. (PLEASE SEE FIRST %3 LOAD(S) FOLL OWING USER INFORMATION MESSAGE 5293 BELOW *** USER WARNING MESSAGE 6450 (OUTPT4) 6450.0 THE SELECTION OF THE ASCII FORMAT OPTION IN THE OUTPUT4 MODULE FOR DATABLOCK %1 MAY RESULT IN NUMERIC TRUNCATION. USER INFORMATION: G USED IS %2 1. THE FORTRAN FORMAT BEIN 2. THE DEFAULT FORTRAN FORMAT IS (1P,5E16.9) 3. THE FIFTH PARAMETER OF THE OUTPUT4 MODULE CAN BE USED TO INCREASE THE NUMBER OF SIGNIFICANT DIGITS. USER ACTION: 1. IF THE NUMBER OF SIGNIFICANT DIGITS IS ACCEPTABLE, THEN NO ACTION IS REQUIR ED. 2. IF ADDITIONAL SIGNIFICANT DIGITS ARE REQUIRED, THEN INCREASE THE VALUE OF THE FIFTH PARAMETER, AND RERUN THE JOB. User information: This message is issued if the internal precision is greater than you want more the requested output precision for OUTPUT4. If precision, increase the value of the fifth parameter in the OUTPUT4 module and rerun the job. *** SYSTEM FATAL MESSAGE 6451 (SITDRV) 6451.0 ITERATIVE SOLVER HAS BEEN REQUESTED TO SOLVE A SYSTEM WITH PURGED MATRIX. SYSTEM FATAL MESSAGE 6452 (SITDRV) *** 6452.0 THE INPUT MATRICES TO THE ITERATIVE SOLVER ARE INCOMPATIBLE IN THE NUMBER OF ROWS. *** SYSTEM FATAL MESSAGE 6453 (SITDRV) 6453.0 THE INPUT MATRICES TO THE ITERATIVE SOLVER ARE DIFFERENT TYPES. USER ACTION: USE DIRECT SOLUTION METHOD AS IN SOLVE, SSG3 OR FBS MODULES. *** USER FATAL MESSAGE 6454 (IFP8). 6454.0 NEGATIVE GROUND SHEAR MODULUS HAS BEEN OBTAINED. USER ACTION: REVISE EXPERIMENTAL DATA AND/OR ORDER OF POLYNOMIAL.

440 User informati on: - This message is issued if A10+A01 obtained from the curve fitting algorithm is negative. The experimental data and/or the order of the strain energy polynomial should be modified. *** USER FATAL MESSAGE 6455 (BGCAU2) 6455.0 CONTACT REGION ID = %1 SELECTED BY THE BOUTPUT CASE CONTROL COMMAND IN SUBCASE NUMBER %2 OR THE BOUTPUT BULK DATA ENTRY IS UNDEFINED. *** USER FATAL MESSAGE 6456 (BGCOCL) 6456.0 SAME ID IS SPECIFIED FOR SLAVE = %1 AND MASTER = %2 REGIONS IN BCONP ENTRY ID = %3. *** USER WARNING MESSAGE 6457 6457.0 NO BOUTPUT CASE CONTROL REQUESTS WERE FOUND AND - Y PLOT REQUESTS FOR BOUT CANNOT BE THEREFORE ANY X PROCESSED. USER ACTION: SPECIFY THE BOUTPUT CASE CONTROL FOR THE DESIRED SLAVE NODES. *** USER FATA L MESSAGE 6458 (DSAD11) 6458.0 THE REQUESTED EIGENVALUE OR BUCKLING LOAD FACTOR ID %1 IS GREATER THAN THE NUMBER OF MODES THAT WERE COMPUTED USER ACTION: CHECK THE MODE ID SPECIFIED ON THE DRESP1 ENTRY AND THE FREQUENCY RANGE AND/OR NUMBER OF TORS SPECIFIED ON THE EIGR/EIGB/EIGRL DESIRED EIGENVEC ENTRY *** USER FATAL MESSAGE 6459 (TA1BSH) 6459.0 BUSH ELEMENT ID = %1 WITH NONCOINCIDENT CONNECTING NODES REQUIRES THE SPECIFICATION OF ORIENTATION VECTOR OR CID FIELDS ON THE CBUSH ENTRY, UNLESS ONLY AXIAL PROPERTIES ARE SPECIFICED IN PBUSH ENTRY. *** USER FATAL MESSAGE 6459, (EGAPD) 6459.1 GAP ELEMENT ID = %1 WITH COINCIDENT CONNECTING NODES REQUIRES THE SPECIFICATION OF CID FIELD ON THE CGAP ENTRY. *** USER FATAL MESSAGE 6459 (IFS1P) 6459.2 BUSH ELEMENT ID = %1 WITH COINCIDENT CONNECTING NODES REQUIRES THE SPECIFICATION OF CID FIELD ON THE CBUSH ENTRY. *** USER FATAL MESSAGE 6459 (EBS1D) 6459.3 BUSH1D ELEMENT ID = %1 WITH COINCIDENT CONNECTING GRIDS REQUIRES THE SPECIFICATION OF CID FIELD ON THE CBUSH1D ENTRY.

441 *** USER FATAL MESSAGE 6459 (SBS11D) 6459.4 FORCE CALCULATION ON BUSH1D ELEMENT ID = %1 WAS NOT AD. PERFORMED. USE STRESS OPTION INSTE *** SYSTEM FATAL MESSAGE 6460 (UDSFRD) 6460.0 ERROR IN OUT OF FRONT PIVOT LOGIC USER ACTION: PLEASE SEND THIS RUN TO SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER WARNING MESSAGE 6461 (NLINIT) 6461.0 NLPARM SET%1 LOAD(P) CONVERGENCE OPTION IS REMOVED WHEN NO LOAD INCREMENT EXISTS. THE WORK(W) CONVERGENCE OPTION HAS BEEN SUBSTITUTED IF NONE SUPPLIED. *** USER WARNING MESSAGE 6462 (RMG2) 6462.0 BOLTZMANN CONSTANT IS ZERO RADIATIVE - --- STEFAN COU PLINGS NULLIFIED. *** USER WARNING MESSAGE 6463 (RMG2) 6463.0 - AF MATRIX (HREE) ASSUMED IN RADMTX. %1SYMMETRIC SCRIPT *** USER INFORMATION MESSAGE 6464 (DOM12E) 6464.0 RUN TERMINATED DUE TO MAXIMUM NUMBER OF DESIGN CYCLES = %1. *** USER INFORMATION MESSAGE 6464 (DOM12E) 6464.1 RUN TERMINATED DUE TO PARAMETER OPTEXIT = %1. *** USER INFORMATION MESSAGE 6464 (DOM12E) 6464.2 RUN TERMINATED DUE TO SOFT CONVERGENCE AT CYCLE NUMBER = %1. *** USER INFORMATION MESSAGE 6464 (DOM12E) 6464.3 RUN TERMINATED DUE TO HARD CONVERGENCE TO AN OPTIMUM AT CYCLE NUMBER = %1. *** USER INFORMATION MESSAGE 6464 (DOM12E) 6464.4 RUN TERMINATED DUE TO HARD CONVERGENCE TO A BEST CLE NUMBER = %1. COMPROMISE INFEASIBLE DESIGN AT CY *** USER INFORMATION MESSAGE 6464 (DOM12E) 6464.5 RUN TERMINATED DUE TO CASE CONTROL COMMAND DSAPRT(END=SENSITIVITY). *** USER INFORMATION MESSAGE 6464 (DOM12E) 6464.6 RUN TERMINATED DUE TO POOR GEOMETRY OR POOR PROPERTIES. SEE FATAL MESSAGES PRINTED ABOVE FOR INFORMATION. *** SYSTEM FATAL MESSAGE 6465 6465.0 DIVISION BY ZERO WAS ENCOUNTERED BY THE ITERATIVE SOLVER. *** SYSTEM FATAL MESSAGE 6466 (SBUT5) 6466.0

442 FOR THE %1 INPUT ALL TERMS IN COLUMN NUMBER = %2 ARE NULL. *** SYSTEM FATAL MESSAGE 6466 (SBUT2) 6466.1 FOR THE %1 INPUT ALL TERMS IN COLUMN NUMBER = %2 ARE NULL. *** SYSTEM FATAL MESSAGE 6466 (SBDCD ) 6466.3 ALL TERMS IN ROW NUMBER = %1 ARE NULL. *** SYSTEM FATAL MESSAGE 6467: 6467.0 A NULL COLUMN WAS ENCOUNTERED AT COLUMN NUMBER = %1 IN THE PRECONDITIONER MATRIX. NULL COLUMN WAS ENCOUNTERED AT COLUMN NUMBER =%1 A 6467.4 DURING ORTHOGONALIZATION *** USER FATAL MESSAGE 6468 (GETCOL) 6468.0 CASE CONTROL SPECIFIED A STATSUB OR IC(STATSUB) ENTRY ID=%1. NO SUBCASE ENTRIES WITH THAT ID WERE FOUND. USER INFORMATION : PROB ABLE CAUSE IS MISMATCH IN CASE CONTROL. USER ACTION : SPECIFY A MATCHING SUBCASE/STATSUB *** USER FATAL MESSAGE 6468 (GETCOL) 6468.1 CASE CONTROL SPECIFIED BOTH A STATSUB AND AN IC(STATSUB) ENTRY IN THE SAME SUBCASE. ONLY ONE IS ALLOWED. USER ACTION : REMOVE EITHER THE STATSUB OR IC(STATSUB) ENTRY. *** USER WARNING MESSAGE 6469 (GP4) 6469.0 CASE CONTROL COMMAND SUPORT1 ID=%1 REFERENCES UNDEFINED SUPORT1 ENTRIES. USER INFORMATION : PROBABLE CAUSE IS SUPERELEMENT THE SUPORT1 COMMAND. SUBCASES CONTAINING ONLY THE RESIDUAL STRUCTURE SUBCASES SHOULD CONTAIN THE SUPORT1 COMMAND. ANOTHER CAUSE MAY BE NO VALID SUPORT1 ENTRIES IN THE BULK DATA. *** SYSTEM INFORMATION MESSAGE 6470 (REIGL0) 6470.0 MORE EFFICIENT PROCESSING IN LANCZO S EIGENSOLUTION MAY BE POSSIBLE BY INCREASING THE BUFFER SIZE OR BY INCREASING THE VALUE OF SYSTEM CELL 199. THE PRODUCT OF THESE TWO VALUES SHOULD BE AT LEAST %1 WORDS. IF SYSTEM CELL 199 IS ALREADY ZERO INCREASE MEMORY *** SYSTEM FATAL MESSAGE 6470 (SSMR0D) 6470.1 THE MASS MATRIX HAS MORE TERMS PER COLUMN THAN CAN

443 FIT IN A BUFFER. INCREASE THE BUFFER SIZE OR THE VALUE OF SYSTEM CELL 199 SUCH THAT THE PRODUCT OF THESE TWO VALUES IS AT LEAST %1 WORDS. *** SYSTEM FATA L MESSAGE 6471 (NLITER) 6471.0 THE BOUNDARY CONDITION SPECIFIED BY THE SPC AND/OR MPC CASE CONTROL COMMAND IN THE CURRENT SUBCASE IS DIFFERENT FROM THE PREVIOUS SUBCASE. THIS IS NOT - ALLOWED IF THE CURRENT SUBCASE REQUESTS THE ARC LENGTH METHOD. USER ACTION : R EMOVE THE NLPCI BULK DATA ENTRY. *** USER INFORMATION MESSAGE 6472 6472.0 NASTRAN SYSTEM(173)>0 IS SPECIFIED. A VALUE OF 1 BLOCKS BOTH THE OFFSET AND SKEW FIXES (GIVING PRE VERSION 68 STIFFNESS) AND A VALUE 2 BLOCKS THE SKEW FIX 8 - 70.5 STIFFNESS). (GIVING VERSION 6 *** USER INFORMATION MESSAGE 6472. (EQD4D) 6472.1 NASTRAN SYSTEM(170)=1 IS SPECIFIED. THEREFORE, THE DIFFERENTIAL STIFFNESS FOR QUAD4 AND TRIA3 ELEMENTS IS COMPUTED USING THE PRE - VERSION 68 METHOD. USER FATAL MESSAGE 6473 (DOM9P2) *** 6473.0 THERE IS INSUFFICIENT DATA TO PERFORM OPTIMIZATION. USER INFORMATION: THE PROBABLE CAUSE IS NO DESOBJ COMMAND IS SPECIFIED IN CASE CONTROL. *** USER FATAL MESSAGE 6474 (IFS6P) 6474.0 SPECIFIED PARAMETER THE DOPTPRM ENTRY HAS ALREADY NAME = %1. USER INFORMATION : YOU MAY SPECIFY A PARAMETER ONLY ONCE. *** USER FATAL MESSAGE 6474 (IFS6P) 6474.1 THE DOPTPRM ENTRY SPECIFIES AN INVALID PARAMETER NAME = %1. USER INFORMATION : CHECK FOR THE PROPER SPELLING OF THE PARAMETER NAME. *** USER FATAL MESSAGE 6474 (IFS10P) 6474.2 THE BCPARA ENTRY HAS ALREADY SPECIFIED PARAMETER NAME = %1. USER INFORMATION : YOU MAY SPECIFY A PARAMETER ONLY ONCE. *** USER FATAL MESSAGE 6474 (IFS10P) 6474.3 THE BCPARA ENTRY SPECIFIES AN INVALID PARAMETER NAME = %1.

444 USER INFORMATION : CHECK FOR THE PROPER SPELLING OF THE PARAMETER NAME. *** USER WARNING MESSAGE 6475 (OUTPT4) 6475.0 DATABLOCK %1 IS A SPARSE FACTOR MATRIX AND WILL NOT BE WRITTEN TO THE OUTPUT4 FILE. USER INFORMATION: THE SPARSE FACTOR MATRIX FORMAT IS NOT SUPPORTED BY THE OUTPUT4 MODULE. *** USER WARNING MESSAGE 6475 (OUTPN2) 6475.1 DATABLOCK %1 IS A SPARSE FA CTOR MATRIX AND WILL NOT BE WRITTEN TO THE OUTPUT2 FILE IN NEUTRAL FORMAT. USER INFORMATION: THE SPARSE FACTOR MATRIX FORMAT IS NOT SUPPORTED BY THE OUTPUT2 MODULE IN NEUTRAL FORMAT. *** USER WARNING MESSAGE 6475 (MATPRT) 6475.2 SPARSE FACTOR MATRIX AND WILL NOT BE DATABLOCK %1 IS A OUTPUT BY THE MATPRT MODULE. USER INFORMATION: THE SPARSE FACTOR MATRIX FORMAT IS NOW SUPPORTED BY THE MATPRN MODULE. *** USER WARNING MESSAGE 6475 (OUTPT4C) 6475.3 DATABLOCK %1 IS A COMPLEX MATRIX AND WILL NOT BE WRITTEN TO THE OUTPUT2 FILE IN AMLS FORMAT USER INFORMATION: COMPLEX MATRICIES WILL NOT BE OUTPUT TO THE AMLS FORMAT OUTPUT FILE *** USER WARNING MESSAGE 6475 (OUTPT4C) 6475.4 DATABLOCK %1 IS A COMP LEX MATRIX AND WILL NOT BE WRITTEN TO THE OUTPUT2 FILE IN AMLS FORMAT USER INFORMATION: COMPLEX MATRICIES WILL NOT BE OUTPUT TO THE AMLS FORMAT OUTPUT FILE *** USER FATAL MESSAGE 6476 (DOPR4) 6476.0 DESVAR ENTRY ID = %1 IS REFERENCED BY SHAPE VARIABLES (DVGRID/DVSHAP/DVBSHAP) AND PROPERTY VARIABLES (DVPREL1/DVPREL2) USER INFORMATION: THE CAPABILITY FOR A DESIGN VARIABLE TO MODIFY BOTH SHAPE AND PROPERTY VARIABLES IS NOT SUPPORTED. *** USER FATAL MESSAGE 64 77 (GIGGKG) 6477.0 FOR SPLINE ENTRY %1 THE FIRST CHORDWISE INTERPOLATED AERODYNAMIC BOX IS AFT OF THE LAST BOX. USER INFORMATION: THE INTERPOLATED SET OF AERODYNAMIC BOXES MUST FORM A TRAPEZOID. THE VALUES IN FIELDS 4 AND 5 ON THE SPLINE ENTRY DO NOT SPECIFY A SET OF BOXES. *** USER FATAL MESSAGE 6478. (AXMPR1) 6478.0

445 A CASE CONTROL WITH ENTRY AUXMODEL = %1 REFERENCES AN UNDEFINED BULK DATA SECTION WITH KEYWORD AUXMODEL=%2 *** SYSTEM FATAL MESSAGE 6479 (D9ALTOP/D9SIEPX) 6479.0 ARTIFICIAL VARIABLE ACCOUNTING AT FAULT. USER ACTION: CONTACT CUSTOMER SUPPORT. *** USER INFORMATION MESSAGE 6480 (REIGLA) 6480.0 EXTERNAL IDENTIFICATION TABLE FOR DECOMPOSITION MESSAGES FOR MATRIX %1 ROW NUMBER = GRID ID + COMPONENT %2%3%4 r information: Use This message is output from the REIGL module when using sparse decomposition to convert the internal (row number oriented) diagnostic messages to external (grid and component) form. ITION EXTERNAL IDENTIFICATION TABLE FOR DECOMPOS 6480.1 MESSAGES FOR MATRIX %1 ROW NUMBER = GRID ID + COMPONENT User information: This message is output from the REIGL module when using sparse decomposition to convert the internal (row number oriented) diagnostic messages to external (grid and compon ent) form. *** SYSTEM INFORMATION MESSAGE 6481 (SOLVIT) 6481.0 DATA BLOCK %1 IS AN UNSYMMETRIC MATRIX. USER INFORMATION: BLOCK INCOMPLETE CHOLESKY PRECONDITIONING IS AVAILABLE FOR SYMMETRIC MATRICES ONLY, SWITCHED TO JACOBI PRECONDITIONING. *** USER INFORMATION MESSAGE 6481 (SITDRV) 6481.1 DATA BLOCK %1 IS AN UNSYMMETRIC MATRIX. USER INFORMATION: USER GIVEN PRECONDITIONING IS AVAILABLE FOR SYMMETRIC MATRICES ONLY, SWITCHED TO JACOBI PRECONDITIONING. *** USER INFORMATION MESSAGE 6481 (SITDRV) 6481.2 DATA BLOCK %1 IS AN UNSYMMETRIC MATRIX. USER INFORMATION: REDUCED INCOMPLETE CHOLESKY PRECONDITIONING IS AVAILABLE FOR SYMMETRIC MATRICES ONLY, SWITCHED TO JACOBI PRECONDITIONING. *** USER INFORMATION MESSAGE 6481 (SITDRV) 6481.3 DATA BLOCK %1 IS A COMPLEX MATRIX. USER INFORMATION: REDUCED INCOMPLETE CHOLESKY

446 PRECONDITIONING IS AVAILABLE FOR REAL ARITHMETIC ONLY, SWITCHED TO JACOBI PRECONDITIONING. *** SYSTEM FATAL MESSAGE 648 1 (SITDRD) 6481.4 DATA BLOCK %1 IS AN UNSYMMETRIC MATRIX. USER INFORMATION: INSIDE THE MODULE, THE ITERATIVE SOLVER IS AVAILABLE FOR SYMMETRIC MATRICES ONLY. %1 IS UNSYMMETRIC 6481.5 USER INFORMATION: ORTHOGONALIZATION IS AVAILABLE FOR SYMMETRIC M MATRI CES ONLY *** USER INFORMATION MESSAGE 6481 (FRRD2) 6481.6 DATA BLOCK %1 IS AN UNSYMMETRIC MATRIX. USER INFORMATION: BLOCK INCOMPLETE CHOLESKY PRECONDITIONING IS AVAILABLE FOR SYMMETRIC MATRICES ONLY, SWITCHED TO CHOLESKY PRECONDITIONING. *** USER INFORMATION MESSAGE 6481 (FRRD1D) 6481.7 DATA BLOCK %1 IS AN UNSYMMETRIC MATRIX. USER INFORMATION: BLOCK INCOMPLETE CHOLESKY PRECONDITIONING IS AVAILABLE FOR SYMMETRIC MATRICES ONLY, SWITCHED TO CHOLESKY PRECONDITIONING. R INFORMATION MESSAGE 6481 (FREQ) *** USE 6481.8 DATA BLOCK %1 IS AN UNSYMMETRIC MATRIX. USER INFORMATION: USER GIVEN PRECONDITIONING IS AVAILABLE FOR SYMMETRIC MATRICES ONLY, SWITCHED TO CHOLESKY PRECONDITIONING. *** USER INFORMATION MESSAGE 6481 (FREQ) 6481.9 DATA BLOCK %1 IS AN UNSYMMETRIC MATRIX. USER INFORMATION: BLOCK INCOMPLETE CHOLESKY PRECONDITIONING IS AVAILABLE FOR SYMMETRIC MATRICES ONLY, SWITCHED TO CHOLESKY PRECONDITIONING. *** SYSTEM FATAL MESSAGE 6481 (SITDRV) 6481.10 TIVE SOLUTION IS AVAILABLE FOR DISTRIBUTED ITERA SYMMETRIC MATRICES ONLY. USER ACTION: SWITCH TO SERIAL EXECUTION. *** SYSTEM INFORMATION MESSAGE 6481 (SITDRV) 6481.11 DISTRIBUTED ITERATIVE SOLUTION IS AVAILABLE FOR JACOBI PRECONDITIONING ONLY. SWITCHED TO JACOBI PRECONDITIONING. *** USER FATAL MESSAGE 6482 (DOPR3R) 6482.0 FOR SUBCASE %1, THE ANALYSIS TYPE IS %2 BUT THE %3 COMMAND REFERENCES AN INCOMPATIBLE

447 DRESP1 ENTRY WITH RID = %4 AND RTYPE = %5. *** USER FATAL MESSAGE 6482 (DOPR3R) 6482.1 THE DESGLB COMMAND REFERENCES AN INCOMPATIBLE DRESP1 ENTRY WITH RID = %1 AND RTYPE = %2. USER INFORMATION: THE DESGLB COMMAND CAN ONLY REFERENCE TO GLOBAL QUANTITIES WHICH ARE NOT ASSOCIATED WITH A SUBCASE, SUCH AS WEIGHT OR VOLUME. DESGLB WITH DESSUB. USER ACTION: REPLACE *** USER FATAL MESSAGE 6483 (EQDGED) 6483.0 ELEMENT ID = %1 HAS CONNECTING GRIDS THAT MAY NOT FORM A PLANE PARALLEL TO - Y PLANE OF THE CID COORDINATE SYSTEM ON THE THE X PLPLANE ENTRY. USER FATAL MESSAGE 6483 (CQUADX, CTRIAX) *** 6483.1 ELEMENT ID = %1 HAS CONNECTING GRIDS THAT MAY NOT FORM A PLANE PARALLEL TO Z PLANE. THE X - *** USER FATAL MESSAGE 6483 (CPLSTNi, CPLSTSi) 6483.2 ELEMENT ID = %1 HAS CONNECTING GRIDS THAT MAY NOT FORM A PLAN E PARALLEL TO THE X - Z PLANE. *** USER FATAL MESSAGE 6483 (CQUADX, CTRIAX) 6483.3 ELEMENT ID = %1 HAS CONNECTING GRIDS THAT MAY NOT FORM A PLANE PARALLEL TO Y PLANE. THE X - *** USER FATAL MESSAGE 6483 (CPLSTNi, CPLSTSi) 6483.4 ELEMENT ID = %1 HAS CONNECTING GRIDS THAT MAY NOT FORM A PLANE PARALLEL TO THE X Y PLANE. - *** USER FATAL MESSAGE 6483 (TA1PLN) 6483.5 ELEMENT TYPE = %1 WHICH IS IN XZ - PLANE AND ELEMENT TYPE = %2 WHICH IS IN XY - PLANE ARE MIXED. USER FATAL MESSAGE 6483 (TA1PLN) *** 6483.6 ELEMENT ID = %1 IS NOT DEFINED CORRECTLY. IT IS NEITHER IN - PLANE NOR IN XY - PLANE. XZ ***SYSTEM FATAL MESSAGE 6485 (DFBS) 6485.0 SPARSE DECOMPOSITION CANNOT BE USED IN CONJUNCTION WITH LEFT HANDED FBS. USER ACTION: DO NOT USE THE SPARSE DECOMPOSITION IN THIS PROBLEM OR MODIFY THE DMAP TO REPLACE THE LEFT HANDED FBS BY A TRANSPOSE OPERATION FOLLOWED BY A REGULAR FBS.

448 *** SYSTEM FATAL MESSAGE 6486 (CSEDGD) 6486.0 D=%1 MAXIMUM NDOF IS NOT EQUAL TO 3 OR 6 FOR EDGE I PROGRAMMER INFORMATION: ELEMENT TYPE=%2 AND ELEMENT ID=%3 USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6487 (CSFCTD) 6487.0 EDGE DOES NOT EXIST FOR GRID1 = %1 AND GRID2 = %2 IN MEDGE TABLE. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 6490 (WRGMTD) 6490.0 FATAL ERRORS HAVE OCCURRED WHILE PROCESSING MPC AND RIGID ELEMENT ENTRIES. PROGRAMMER INFORMATION: SIL NUMBER %1 DOES NOT EXIST IN THE DEPENDEN T SIL TABLE. *** USER FATAL MESSAGE 6491, (CIDTRD) 6491.0 THE INPUT COORDINATE SYSTEM=%1 SPECIFIED ON THE GM%2=%3 BULK DATA ENTRY IS NOT A RECTANGULAR SYSTEM. USER INFORMATION: FOR THIS GROUP, THE COORDINATE SYSTEM MUST BE RECTANGULAR. *** USER FATAL MESSAGE 6492 (GP1CCV) 6492.0 COORDINATE SYSTEM ID=%1 IS DEFINED MORE THAN ONCE. USER INFORMATION: ALL GMCORD, CORD3G AND CORDIJ ENTRIES MUST HAVE UNIQUE IDENTIFICATION NUMBERS. *** USER FATAL MESSAGE 6493 (GP1CVG) 6493.0 THE FEFACE %1 SPECIFIED ON THE GMCORD %2 BULK DATA ENTRY IS NOT DEFINED. *** USER FATAL MESSAGE 6493 (GP1CVG) 6493.1 THE FEEDGE %1 SPECIFIED ON THE GMCORD %2 BULK DATA ENTRY IS NOT DEFINED. *** USER FATAL MESSAGE 6493 (CONVGM) 6493.2 THE GMSU RF %1 SPECIFIED ON THE GMCORD %2 BULK DATA ENTRY IS NOT DEFINED. *** USER FATAL MESSAGE 6493 (CONVGM) 6493.3 THE GMCURV %1 SPECIFIED ON THE GMCORD %2 BULK DATA ENTRY IS NOT DEFINED. *** USER FATAL MESSAGE 6494 (DBINIT) 6494.0 GEOMEVAL OR BE AMEVAL OR DRESP3 IS NOT SPECIFIED ON THE CONNECT FMS STATEMENT. *** SYSTEM FATAL MESSAGE 6495 (DBINIT) 6495.0 UNABLE TO CONNECT TO GEOMETRY EVALUATOR SPECIFIED ON THE CONNECT FMS STATEMENT.

449 *** SYSTEM WARNING MESSAGE 6496, (ERGAPI) 6496.0 THE LIST OF DIAGNOSTIC MESSAGES PRINTED ABOVE IS NOT COMPLETE. USER ACTION: CHECK THE ENTIRE MODEL FOR SIMILAR ERRORS. *** USER FATAL MESSAGE 6497 (TRNJFD) 6497.0 THE POINT AT: X=%1 Y=%2 Z=%3, IN THE BASIC COORDINATE SYSTEM COULD NOT BE LOCATED O N FEFACE ID=%4. *** USER FATAL MESSAGE 6497 (TRNJED) 6497.1 THE POINT AT: X=%1 Y=%2 Z=%3, IN THE BASIC COORDINATE SYSTEM COULD NOT BE LOCATED ON FEEDGE ID=%4. *** USER WARNING MESSAGE 6498 (DOPR1) 6498.0 SPOT OR GCMMA CANNOT BE USED FOR OTHER JOBS THAN TOPOLOGY OPTIMIZATION. SETTING SDO AS ALGORITHM. *** USER FATAL MESSAGE 6499 (DOM9) 6499.0 THE OPTIMIZATION ALGORITHM HAS ENCOUNTERED AN ERROR THAT MAKES FURTHER PROGRESS IMPOSSIBLE. SEE MESSAGES ABO VE. *** USER FATAL MESSAGE 6499 (DISOP) 6499.1 THE OPTIMIZATION ALGORITHM HAS ENCOUNTERED AN ERROR THAT MAKES FURTHER PROGRESS IMPOSSIBLE. SEE MESSAGES ABOVE. *** USER FATAL MESSAGE 6499.2 (DOM94) 6499.2 DATA SEGMENT WITH %1=%2 NOT FOUND IN %3 DATABLOCK. *** USER FATAL MESSAGE 6499.3 (dom9p6) 6499.3 DATA RECORD WITH %1=%2 NOT FOUND IN %3 DATABLOCK. *** USER FATAL MESSAGE 6500 (%1) 6500.0 MULTIPLE SUBCASES WITH DIFFERENT METHOD COMMANDS AND/OR SPC/MPC/SUPORT COMMANDS HAVE BEEN SPECIFIED WITH P - ELEMENTS IN NORMAL MODES ANALYSIS. USER INFORMATION: ONLY ONE BOUNDARY CONDITION AND ONE METHOD COMMAND PER RUN IS ALLOWED. WARNING MESSAGE 6501 *** USER 6501.0 THE ADAPT=%1 COMMAND IN SUBCASE %2 IS DIFFERENT FROM THAT OF THE FIRST SUBCASE. USER INFORMATION: ONLY ONE ADAPT COMMAND SHOULD BE SPECIFIED. ADAPT=%3 OF THE FIRST SUBCASE WILL BE USED. *** USER INFORMATION MESSAGE 6502 (ADAPT) 6502.0 THE CURRENT SUPERELEMENT (ID =%1) REQUIRES NO FURTHER P - ADAPTIVE ANALYSIS BECAUSE %2.

450 *** USER INFORMATION MESSAGE 6502 (ADAPT) 6502.1 ADAPTIVE ANALYSIS TERMINATED BECAUSE %1. - P *** USER INFORMA TION MESSAGE 6502 (ADAPT) 6502.2 THE CURRENT SUPERELEMENT (ID =%1) REQUIRES NO FURTHER ADAPTIVE ANALYSIS BECAUSE P - %2. USER INFORMATION: MAXIMUM ITERATION IS %3 WHICH IS SPECIFIED ON ADAPT BULK DATA ENTRY ID = %4 *** USER INFORMATION MESSAGE 6503 (%1) 6503.0 - ADAPTIVE AN ADAPT BULK DATA ENTRY IS NOT SPECIFIED. P ANALYSIS WILL NOT BE PERFORMED. *** USER INFORMATION MESSAGE 6504 (%1) 6504.0 THE ADAPT = %1 CASE CONTROL COMMAND REFERENCES AN UNDEFINED ADAPT BULK DATA ENTR Y. ADAPTIVE ANALYSIS WILL NOT BE PERFORMED. P - *** USER WARNING MESSAGE 6505 (%1) 6505.0 PART %1 ON ADAPT BULK DATA ENTRY ID = %2 SPECIFIES ERRTOL=%3 WHICH IS NOT SUPPORTED. USER INFORMATION: ERRTOL=0.1 WILL BE USED. *** USER WARNING MESSAGE 6505 (AAAAAAAA) 6505.1 PART %1 ON ADAPT BULK DATA ENTRY ID = %2 SPECIFIES ERREST=%3 WHICH IS NOT SUPPORTED. USER INFORMATION: ERREST=1 WILL BE USED. *** USER WARNING MESSAGE 6506 (%1) 6506.0 PART %1 ON ADAPT BULK DATA ENTRY ID = %2 SPECIFIES ERREST=0 AND TYPE=%3 USER INFORMATION: NO ERROR ESTIMATE IS PERFORMED AND - VALUES ARE NOT CHANGED FOR THIS PART. P *** USER WARNING MESSAGE 6507 (ADPMRG) 6507.0 THE MAXIMUM P VALUE=%1 SPECIFIED FOR DIRECTION #%2 AND ELEMENT ID=%3 IS LESS THAN THE STARTING P VALUE=%4. THE MAXIMUM VALUE WILL BE USED FOR THE STARTING VALUE. USER INFORMATION: THE MAXIMUM P VALUE IS SPECIFIED ON PVAL BULK DATA ENTRY ID=%5 THE STARTING P VALUE IS SPECIFIED ON PVAL BULK DATA ENTRY ID=%6 USER WARNING MESSAGE 6507 (ADPMRG) *** 6507.1 THE MINIMUM P VALUE=%1 SPECIFIED FOR DIRECTION #%2 AND ELEMENT ID=%3 IS GREATER THAN THE STARTING P VALUE=%4. THE MINIMUM VALUE WILL BE USED FOR THE STARTING VALUE. USER INFORMATION: THE MINIMUM P VALUE IS SPECIFIED ON PVAL BULK DATA ENTRY ID=%5

451 THE STARTING P VALUE IS SPECIFIED ON PVAL BULK DATA ENTRY ID=%6 *** USER WARNING MESSAGE 6508 (ADPVAL) 6508.0 TWO PVAL BULK DATA ENTRIES WITH ID=%1 REFERENCE THE ELEMENT ID=%2 BUT SPECIFY A DIFFERENT COORDINATE (CID=%3 AND %4). SYSTEM. *** USER FATAL MESSAGE 6509 (ADPVAL) 6509.0 THE SETTYP FIELD (%1) ON PVAL ENTRY ID = %2 IS NOT VALID. USER INFORMATION: ONLY %3 AND %4 ARE ALLOWED. *** USER INFORMATION MESSAGE 6510 (ADPVAL) 6510.0 NO VALID ELEMENTS CAN BE FOUND IN SET %1 WHICH IS REFERENCED BY A PVAL BULK DATA ENTRY ID=%2. *** USER FATAL MESSAGE 6511 (%1) 6511.0 ADAPT BULK DATA ENTRY ID = %1 REFERENCED BY AN ADAPT CASE CONTROL DOES NOT EXIST. ONTROL AND ADAPT OR USER ACTION: CHECK ADAPT CASE C PSET BULK DATA ENTRIES. *** SYSTEM FATAL MESSAGE 6512 (GETREC) 6512.0 RECORD %1 CAN NOT BE FOUND IN THE %2 DATA BLOCK (GINO ID=%3). USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. USER FATAL MESSAGE 6513 (GETSDF) *** 6513.0 %1 BULK DATA ENTRY ID=%2 REFERENCES SET %3 WHICH IS NOT SPECIFIED, OR THE SET CONTAINS IDENTIFICATION NUMBERS WHICH ARE NOT VALID. USER INFORMATION: THE SET STATEMENT(S) MUST BE T(POST)" PROCEEDED BY A "SETS DEFINITION" OR "OUTPU STATEMENT. *** USER WARNING MESSAGE 6514 (SDRPOP) 6514.0 THE DATAREC=%1 CASE CONTROL COMMAND REFERENCES UNDEFINED OUTPUT BULK DATA ENTRY. USER INFORMATION: THE DATAREC COMMAND WILL BE IGNORED. *** SYSTEM FATAL MESSAGE 6517 6517.0 THE %1 - P ELEMENT ID ON VIEWTB RECORD IS %2 IS DIFFERENT FROM THAT OF THE EST RECORD USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6517 (AAAAAAAA) 6517.2 THE %1 ELEMENT ID ON VIEWTB RECORD IS %2 IS DIFFERENT FROM THAT OF THE EST RECORD (%3) USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER

452 SUPPORT. *** SYSTEM FATAL MESSAGE 6517 (SBEMPD) 6517.3 P ELEMENT ID ON VIEWTB RECORD IS %2 IS DIFFEREN - THE %1 T FROM THAT OF THE EST RECORD USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6518 (%1) 6518.0 FOR %1 ELEMENT ID OF %2, THE NUMBER OF DEGREES - OF - FREEDOM = %3 IS GREATER THAN THE LENGTH OF THE DISPLACEMENT VECTOR = %4. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6519 (VIEWP) 6519.0 LENGTH OF %1 RECORD IN %2 DATA BLOCK IS INCORRECT. PROGRAMMER INFORMATION: LENGTH%3 = %4 WHICH IS NOT MULTIPLES OF %5 USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER WARNING MESSAGE 6520 (VIEWP) 6520.0 THE NEXT VU%1 IDENTIFICATION NUMBER=%2 IS LESS THAN OR EQUAL TO GNMAX=SYSTE M(179)=%3. USER INFORMATION: THE VALUE OF %4 WILL BE USED FOR THE STARTING ID NUMBER. *** USER WARNING MESSAGE 6520 6520.1 THE NEXT VU%1 IDENTIFICATION NUMBER=%2 IS GREATER THAN ITS MAXIMUM NUMBER=%3. USER INFORMATION: THE MAXIMUM NUMBER IS IGNORED. USER ACTION: ADJUST THE STARTING AND MAXIMUM NUMBERS WITH THE NASTRAN STATEMENT SYSTEM CELLS %4 AND %5. *** USER WARNING MESSAGE 6520 (DVIEWP) 6520.2 THE NEXT VU%1 IDENTIFICATION NUMBER=%2 IS LESS T HAN OR EQUAL TO GNMAX=SYSTEM(179)=%3. USER INFORMATION: THE VALUE OF %4 WILL BE USED FOR THE STARTING ID NUMBER. *** USER WARNING MESSAGE 6521 (VIEWP) 6521.0 PARAMETER NUMBER %1 (%2=%3) OF VIEWP MODULE IS TOO SMALL WHEN PROCESSING %4 ELEMENT %5. USER INFORMATION: A JUMP VALUE OF %6 IS USED TO AVOID DUPLICATE VIEW %7 ID'S. *** USER WARNING MESSAGE 6521 (DVIEWP) 6521.1 PARAMETER NUMBER %1 (%2=%3) OF DVIEWP MODULE IS TOO SMALL WHEN PROCESSING %4 ELEMENT %5. USER INFORMATION: A JUMP VALUE OF %6 IS USED TO AVOID DUPLICATE VIEW %7 ID'S.

453 *** USER FATAL MESSAGE 6522 (VIEWP) 6522.0 THE NEXT VU%1 IDENTIFICATION NUMBER=%2 IS TOO SMALL. USER ACTION: SPECIFY A DIFFERENT STARTING VALUE WITH THE NASTRAN SYSTEM(% 3) STATEMENT. USER INFORMATION: ITS VALUE SHOULD BE GREATER THAN %4 *** USER FATAL MESSAGE 6523 (%1) 6523.0 THE OUTRCV=%1 CASE CONTROL REFERENCES AN UNDEFINED OUTRCV BULK DATA ENTRY. *** USER WARNING MESSAGE 6524 (%1) 6524.0 ELEMENT ID=%1 IS REFERENCED BY MORE THAN ONE OUTRCV BULK DATA ENTRY WITH ID=%2 THE OUTRCV ENTRY WHICH REFERENCES SET %3 WILL BE USED FOR THE ELEMENT. *** USER WARNING MESSAGE 6525 (%1) 6525.0 OUTRCV BULK DATA ENTRY ID=%1 SPECIFIES A METHOD (%2) WH ICH IS NOT SUPPORTED. USER INFORMATION: METHOD=DIRECT WILL BE USED. *** USER FATAL MESSAGE 6526 (ADPVAL) 6526.0 THE ADAPT=%1 CASE CONTROL COMMAND REFERENCES UNDEFINED PVAL ENTRY ID=%2. *** USER FATAL MESSAGE 6526 (ADPVAL) 6526.1 THE ADAPT=%1 CASE CONTROL COMMAND REFERENCES AN UNDEFINED PSET BULK DATA ENTRY. *** USER FATAL MESSAGE 6526 (AAAAAAAA) 6526.2 THE ADAPT=%1 CASE CONTROL COMMAND REFERENCES UNDEFINED PVAL ENTRY ID=%2. *** SYSTEM WARNING MESSAGE 6527. (D RMH3) 6527.0 TABLE %1 INDICATES THAT MATRIX%2 SHOULD HAVE %3 ROWS THE MATRIX TRAILER INDICATES %4 ROWS; - DATA BLOCKS THE MATRIX AND TABLE ARE INCOMPATIBLE SKIPPED *** SYSTEM WARNING MESSAGE 6528. (DRMH3) 6528.0 MATRIX %1 SHOULD BE REAL FOR SOLUTION TYPE %2 *** SYSTEM WARNING MESSAGE 6528. (DRMH3) 6528.1 MATRIX %1 SHOULD BE COMPLEX FOR SOLUTION TYPE %2 *** USER INFORMATION MESSAGE 6529. (DRMH3A) 6529.0 COLUMN LABEL DATA BLOCK (109) IS WRONG TYPE, A COMPLEX LAMA TABLE SHOULD HAVE BEEN SUPPLIED FOR SLTYPE %1; DRMH3 ABORTING. *** SYSTEM WARNING MESSAGE 6529. (DRMH3A) 6529.1 COLUMN LABEL DATA BLOCK (109) IS WRONG TYPE. A LAMA TABLE SHOULD HAVE BEEN SUPPLIED FOR SLTYPE %1

454 *** USER WARNING MESSAGE 6530. (DRMH3E) 6530.0 DRMH3 DATA BLOCK %1 IS AN UNKNOWN TYPE (%2) DATA BLOCK IS SKIPPED. *** SYSTEM INFORMATION MESSAGE 6530. (DRMH3A) 6530.4 %1 IS AN UNKNOWN SOLUTION TYPE (PARAMETER 1) DEFAULT TYPE (STATICS) SUBSTITUTED *** SYSTEM INFORMATION MESSAGE 6531. (DRMH3C) 6531.0 MATRIX %1 HAS MORE MODES (%2) THAN CASE CONTROL RECORDS (%3) THE LAST CASE CONTROL RECORD WILL BE USED FOR REMAINING MODES *** USER INFORMATION MESSAGE 6531. (DRMH3B) 6531.1 MNS (%2) THAN CASE CONTROL MATRIX %1 HAS MORE COLU RECORDS (%3) THE LAST CASE CONTROL RECORD WILL BE USED FOR REMAINING COLUMNS. *** SYSTEM WARNING MESSAGE 6532. (DRMH3E) 6532.0 THE CASE CONTROL RECORD DOES NOT FIT IN OPEN CORE. PROBABLY WRONG CASECC TRAILER INFO DRMH3 PROCESSING TERMINATED. *** USER WARNING MESSAGE 6533. (DRMH3E) 6533.0 - THE COMPLEX FORMAT REQUEST MADE FOR REAL DATA FORMAT REQUEST IS IGNORED *** USER WARNING MESSAGE 6533. (DRMH3D) 6533.1 REAL FOR MAT REQUEST MADE FOR COMPLEX DATA THE - FORMAT REQUEST IS IGNORED *** USER WARNING MESSAGE 6533. 6533.2 REAL/IMAG OR MAG/PHASE FORMAT REQUEST MADE FOR REAL - THE FORMAT REQUEST IS IGNORED DATA *** USER INFORMATION MESSAGE 6534. (DRMH3C) 6534.0 MATRIX %1 HAS MORE MODES (%2) THAN LAMA TABLE (%3) FREQ = 0.0 WILL BE USED FOR REMAINING MODES *** SYSTEM WARNING MESSAGE 6536. (DRMH3E) 6536.0 MATRIX %1 COLUMNS (%2) DOES NOT MATCH PRODUCT OF CASE CONTROL R ECORDS (%3) AND TERMS IN TIME POINT LIST (%4). DATA BLOCK IGNORED *** USER WARNING MESSAGE 6536. (DRMH3E) 6536.1 NUMBER OF COLUMNS FOR MATRIX %1= (%2) AND IS NOT AN EVEN MULTIPLE OF 3. DATA BLOCK IGNORED *** SYSTEM WARNING MESSAGE 6536. (DRMH3D) 6536.2 MATRIX %1 COLUMNS (%2) DOES NOT MATCH PRODUCT OF CASE CONTROL RECORDS (%3) AND TERMS IN FREQUENCY LIST (%4)

455 *** SYSTEM WARNING MESSAGE 6536. (DRMH3D) 6536.3 NUMBER OF MATRIX COLUMNS FOR MATRIX %1(%2) IS NOT AN EVEN MULTIPLE OF THE NUMBER OF SUBCASES (%3), DATA BLOCK IS NOT PROCESSED *** SYSTEM WARNING MESSAGE 6536. (DRMH3D) 6536.4 NUMBER OF MATRIX COLUMNS FOR MATRIX %1(%2) IS NOT AN EVEN MULTIPLE OF THE FREQUENCY LIST (%3) *** USER INFORMATION MESSAGE 6537 (%1) 6537.0 ERRSEC=%1 (SYSTEM CELL 200) IS NOT WITHIN THE RANGE OF %2 THROUGH %3. THE DEFAULT VALUE OF %4 WILL BE USED. USER INFORMATION MESSAGE: ERRSEC IS USED AS NUMBER OF DIVIDING SECTION FOR INCREASING P VALUES. - ** USER WARNING MESSAGE 6538 (SDRPOI) * 6538.0 - ELEMENT %1=%2 IN SUBCASE ID=%3 IS NOT ALLOWED IN P OUTPUT REQUESTS. THE ALL OPTION IS ASSUMED. USER INFORMATION: THE DATAREC CASE CONTROL COMMAND AND OUTPUT BULK DATA ENTRY CAN BE USED TO SPECIFY SETS OF ELEMENTS FO R SPECIFIC PRINT/PUNCH/PLOT REQUESTS. *** USER WARNING MESSAGE 6539 (IFS6P) 6539.0 THE VALUES SPECIFIED ON MAT10 ENTRY ID= %1 DO NOT OBEY THE EQUATION: BULK = RHO*(C**2). USER INFORMATION: ONLY TWO OF THE THREE VALUES HAVE TO BE SPECIFIED AND THE UNSPECIFIED VALUE WILL THEN COMPUTED FROM THE EQUATION ABOVE. *** USER FATAL MESSAGE 6539 (IFS6P) 6539.1 INCOMPLETE DATA FOR MAT10 ENTRY ID= %1. ATLEAST TWO ENTRIES OUT OF BULK MODULUS, MASS DENSITY AND SPEED OF SOUND MUST BE SPECIFIED. *** USER FATAL MESSAGE 6539 (IFS6P) .2 6539 REAL VALUED INPUT IS REQUIRED FOR BULK MODULUS FIELD OF THE MAT10 CARD %1. *** USER FATAL MESSAGE 6539 (IFS6P) 6539.3 REAL VALUED INPUT IS REQUIRED FOR MASS DENSITY FIELD OF THE MAT10 CARD %1. *** USER FATAL MESSAGE 6539 (IFS6P) 6539.4 REAL VALUED INPUT IS REQUIRED FOR SPEED OF SOUND FIELD OF THE MAT10 CARD %1. *** USER FATAL MESSAGE 6539 (IFSMATPOR) 6539.5 THE VALUE OF TORTUOSITY SPECIFIED IN THE MATPOR BULK DATA ENTRY MUST BE GREATER THAN 1 .0.

456 *** USER FATAL MESSAGE 6539 (IFSMATPOR) 6539.6 THE VALUE OF FLUID DENSITY SPECIFIED IN THE MATPOR BULK DATA ENTRY MUST BE GREATER THAN 0.0. *** USER FATAL MESSAGE 6539 (IFSMATPOR) 6539.7 THE SPEED OF SOUND IN THE FLUID SPECIFIED IN THE MATPOR BULK DATA ENTRY MUST BE GREATER THAN 0.0. *** USER FATAL MESSAGE 6539 (IFSMATPOR) 6539.8 THE GAMMA, PRANDTL NUMBER OR DYNAMIC VISCOSITY SPECIFIED IN THE MATPOR BULK DATA ENTRY MUST BE GREATER THAN 0.0. *** USER FATAL MESSAGE 6539 (IFSMATPOR) 6539.9 THE FLOW RESISTIVITY SPECIFIED IN THE MATPOR BULK DATA ENTRY MUST BE EQUAL TO OR GREATER THAN 0.0. *** USER FATAL MESSAGE 6539 (IFSMATPOR) 6539.10 THE POROSITY SPECIFIED IN THE MATPOR BULK DATA ENTRY MUST BE GREATER THAN 0.0 AND LESS THAN OR EQUAL TO 1.0. *** USER FATAL MESSAGE 6539 (IFSMATPOR) 6539.11 THE CHARACTERISTIC VISCOUS/THERMAL LENGTH SPECIFIED IN THE MATPOR BULK DATA ENTRY MUST BE GREATER THAN 0.0. *** SYSTEM WARNING MESSAGE 6540(REIGLC) 6540.0 THE GRID POINT IDENTIFICATION NUMBER AND THE COMPONENT NUMBER CANNOT BE DETERMINED FOR THE DECOMPOSITION MESSAGES ABOVE. TABLE AS USER ACTION: SPECIFY THE EQEXINS, SILS AND USET INPUT TO THE REIGL MODULE. *** SYSTEM FATAL MESSAGE 6541 (%1) 6541.0 VUELEM ID =%1 EXCEEDS THE MAXIMUM ALLOWED INTEGER ID =%2 IN SYSTEM CELL (183). USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. SYSTEM FATAL MESSAGE 6541 (AAAAAAAA) *** 6541.1 VUGRID ID =%1 EXCEEDS THE MAXIMUM ALLOWED INTEGER ID =%2 IN SYSTEM CELL (181). USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 6541 (VIEWP) 6541.2 VUELEM ID =%1 EXCEEDS THE M AXIMUM ALLOWED INTEGER ID =%2 IN THE SYSTEM CELL (183). USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 6541 (VIEWP) 6541.3 VUGRID ID =%1 EXCEEDS THE MAXIMUM ALLOWED INTEGER ID

457 =%2 IN THE SYSTEM CELL (181). ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER USER SUPPORT. *** SYSTEM FATAL MESSAGE 6541, 6541.4 ADAPTIVE GRID ID =%1 EXCEEDS THE MAXIMUM ALLOWED INTEGER ID =%2 IN SYSTEM CELL (179). USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 6541 (DVIEWP) 6541.7 VUELEM ID =%1 EXCEEDS THE MAXIMUM ALLOWED INTEGER ID =%2 IN THE SYSTEM CELL (183). USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 6541 (DVIEWP) 6541.8 VUELEM ID =%1 EXCEEDS THE MAXIMUM ALLOWED INTEGER ID =%2 IN THE SYSTEM CELL (181). USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 6541 (APD0) 6541.9 USER INFORMATION: AERO GRID ID %1 EXCEEDS THE MAXIMUM IN SYSTEM CELL (%3). ALLOWED INTEGER ID %2 USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 6543, (GP0I), 6543.0 THERE ARE NO VALID P - ELEMENTS IN THE UNION OF ALL SET ENTRIES REFERENCED BY ADAPT ID =%1. *** USER FATAL ME SSAGE 6544, (GP0I), 6544.0 THE EDGE WITH GRIDS ID =%1,%2 ON P - ELEMENT ID =%3 IS SHARED BY - ELEMENT WITH MID SIDE GRID. AN H - ELEMENT AND USER ACTION: REMOVE MID SIDE GRID FROM H VERIFY GEOMETRY. *** USER FATAL MESSAGE 6545 (DOPR3) 6545.0 A DESGLB = %1 COMMAND APPEARS AT THE SUBCASE LEVEL. USER ACTION: EITHER REPLACE THE DESGLB COMMAND WITH A DESSUB COMMAND OR PLACE THE DESGLB REQUEST ABOVE THE FIRST SUBCASE. *** USER FATAL MESSAGE 6545.1 (DOCR23) 6545.1 DRSPAN RELATED DRESP2/3 RES PONSE %1 IS NOT REFERENCED VIA DESGLB OR DESOBJ CASE CONTROL USER ACTION: REFERENCE DRSPAN RELATED DRESP2/3 BY WAY OF DESGLB OR DESOBJ CASE CONTROL *** USER FATAL MESSAGE 6546 (EQUDFD) 6546.0

458 THE CID FIELD ON PLPLANE ENTRY IS SPECIFIED FOR CQUADX ELEMENT ID = %1. USER ACTION: SET CID TO ZERO OR LEAVE BLANK. *** USER FATAL MESSAGE 6546 (ETRIFD) 6546.1 THE CID FIELD ON PLPLANE ENTRY IS SPECIFIED FOR CTRIAX ELEMENT ID = %1. USER ACTION: SET CID TO ZERO OR LEAVE BLANK. *** USER WARNING MESSAGE 6547 (RCARD) 6547.0 THE SEQGP/SEQEP ENTRY HAS MORE THAN ONE DECIMAL POINT IN THE SEQID FIELD. USER INFORMATION: SEQID WILL BE TRUNCATED AT THE SECOND DECIMAL POINT FROM THE LEFT. FOR EXAMPLE, 1.9.2.6 BECOMES 1.9 TAL MESSAGE 6548 (SFUPFC) *** SYSTEM FA 6548.0 INSUFFICIENT LOCAL WORKING ARRAY FOR SPARSE MATRIX FORWARD BACKWARD SUBSTITUTION. - PROGRAMMER INFORMATION: CHECK THE SECOND ORDER EQUATION ON IC2 IN SPUPFC. *** SYSTEM FATAL MESSAGE 6548 (SFUPBC) 6548.1 INSUFFICIENT LOCAL WORKING ARRAY FOR SPARSE MATRIX FORWARD - BACKWARD SUBSTITUTION. PROGRAMMER INFORMATION: CHECK THE SECOND ORDER EQUATION ON IC2 IN SFUPBC. *** SYSTEM WARNING MESSAGE 6549 (SFMG68) 6549.0 LED %2, FOR THE VERSION %1 SPARSE FACTOR MATRIX CAL RECORD 0 IS INCOMPLETE. *** SYSTEM WARNING MESSAGE 6550 (SFMG68) 6550.0 FOR THE VERSION %1 SPARSE FACTOR MATRIX CALLED %2, THE MATRIX SIZE IN THE TRAILER IS INCONSISTENT WITH RECORD 1. *** SYSTEM FATAL MESSAGE 6551 (INPTX2) 6551.0 %1 WAS DETECTED ON UNIT %2 DURING BINARY %3 PROCESSING *** SYSTEM FATAL MESSAGE 6551 (INPTX2) 6551.1 ON SINGLE PRECISION OR ILP64 PLATFORM, DOUBLE PRECISION IS NOT SUPPORTED. DOUBLE PRECISION ON ILP64 IS EQUIVALENT TO QUAD PRECISION ON LP64/ILP32. CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 6552 (IFS6P) 6552.0 THE DOPTPRM ENTRY DOES NOT SPECIFY A PARAMETER NAME. USER INFORMATION : THIS ENTRY HAS CHANGED FOR VERSION 68. YOU MUST SPECIFY A PARAMETER NAME AND A VALUE. *** USER FATAL MESSAGE 6552 (IFS10P) 6552.1 THE BCPARA ENTRY DOES NOT SPECIFY A PARAMETER NAME.

459 USER INFORMATION : YOU MUST SPECIFY A PARAMETER NAME AND A VALUE. *** USER FATAL MESSAGE 6553 (DOPR3R) 6553.0 RESPONSE HAS BEEN INVOKED BY THE DESSUB COMMAND A %1 IN SUBCASE %2, WHICH IS NOT THE FIRST SUBCASE. USER INFORMATION: %3 RESPONSES MUST BE INVOKED EITHER ABOVE THE SUBCASE LEVEL OR IN THE FIRST SUBCASE. *** USER FATAL MESSAGE 6554 (DOPR2A) 6554.0 FOR AN INTERNAL AUXILIARY MODEL: THE INTERNAL AUXILIARY MODEL, THE AUXILIARY DISPLACEMENT MATRIX, OR A DVBSHAP BULK DATA ENTRY IS MISSING. USER ACTION: CHECK FOR THE EXISTENCE OF THE AUXILIARY CASE CONTROL SECTION, AUXILIARY MODEL BULK DATA DVBSHAP ENTRIES. SECTION AND *** USER FATAL MESSAGE 6555 (DOPR2A) 6555.0 BOTH DVBSHAP AND DVSHAP ENTRIES ARE SPECIFIED, WHICH IS NOT ALLOWED. USER ACTION: USE DVBSHAP ENTRIES FOR AN INTERNAL AUXILIARY MODEL OR DVSHAP ENTRIES FOR AN EXTERNAL AUXILIARY MODEL. *** USER FATAL MESSAGE 6557 (AXCDFD) 6557.0 STRAIN SINGULARITY WAS ENCOUNTERED IN HYPERELASTIC ELEMENT %1 IN THE SOLUTION PHASE. *** USER WARNING MESSAGE 6558 (DSADMS) 6558.0 A DRESP1 ENTRY DEFINES A MARGIN OF SAFETY AS A RESPONSE FOR ELEMENT TYPE %1, ELEMENT ID = %2, AND COMPONENT = %3. THE REQUESTED RESPONSE IS NOT AVAILABLE. USER INFORMATION: THIS PROBABLY INDICATES THAT THE OF THE ELEMENT STRESS IS ZERO OR HAS THE OPPOSITE SIGN LIMIT STRESS. HOWEVER, IT COULD INDICATE THAT THE REQUIRED STRESS LIMITS HAVE NOT BEEN SPECIFIED ON THE MATERIAL PROPERTY BULK DATA ENTRY. *** USER FATAL MESSAGE 6559 (MODEPT) 6559.0 THE TABLEDI ID = %1 ENTRY REFERENCED BY A PACABS ENTRY ONTAINS ZERO OR NEGATIVE VALUES FOR FREQUENCY (XI). C USER INFORMATION: FREQUENCY VALUES SPECIFIED ON THE TABLEDI ENTRY MUST BE GREATER THAN ZERO. *** USER WARNING MESSAGE 6560 (GPST1T) 6560.0 THE MAXIMUM NUMBER OF MESSAGES HAVE BEEN ISSUED BY THE G RID POINT STRESS PROCESSOR (%1 MODULE). *** SYSTEM FATAL MESSAGE 6561 (ULANDD): 6561.0

460 DURING REAL UNSYMMETRIC LANCZOS EIGENVALUE EXTRACTION, A READ ERROR WAS ENCOUNTERED IN READING THE TRIDIAGONAL FILE %1. *** SYSTEM FATAL MESSAGE 6562 (ULANDD): 6562.0 DURING REAL UNSYMMETRIC LANCZOS EIGENVALUE EXTRACTION, CONVERGENCE FAILED FOR ONE OR MORE EIGENVALUES. ERROR IN QL ITERATION, STEP %1 *** SYSTEM FATAL MESSAGE 6563 (ULANFD): 6563.0 DURING REAL UNSYMMETRIC LANCZOS EIGENVALUE EXTRACTION, A FACTOR ERROR WAS ENCOUNTERED, ERROR TYPE = %1 *** SYSTEM FATAL MESSAGE 6564 (ULANXD): 6564.0 DURING REAL UNSYMMETRIC LANCZOS EIGENVALUE EXTRACTION, A NULL COLUMN WAS ENCOUNTERED WHILE READING THE MATRIX FROM FILE %1. *** USER FATAL MESSAGE 6565 (UEIGL): 6565.0 THE SIXTH OUTPUT DATA BLOCK WHICH IS REQUIRED IS PURGED. USER ACTION: CHECK UEIGL DMAP CALL. *** SYSTEM FATAL MESSAGE 6566 (UEIGL): 6566.0 THE MASS AND THE DIVERGENCE M ATRICES DO NOT EXIST FOR REAL UNSYMMETRIC LANCZOS. USER ACTION: EITHER THE MASS OR THE DIVERGENCE MATRIX IS REQUIRED. *** SYSTEM FATAL MESSAGE 6567 (UEIGL): 6567.0 THE INPUT MATRICES TO THE REAL UNSYMMETRIC LANCZOS MODULE REQUIRE A COMPLEX EIGENVALUE EXTRACTION EIGENVALUE SOLUTION. USER ACTION: USE THE COMPLEX LANCZOS (CEAD) MODULE. *** SYSTEM WARNING MESSAGE 6568 (ULANCZ): 6568.0 DURING REAL UNSYMMETRIC EIGENVALUE EXTRACTION, MORE ROOTS THAN EXIST HAVE BEEN FOUND. *** USER WARNING MESSAGE 6569 (ULANCZ): 6569.0 DURING REAL UNSYMMETRIC EIGENVALUE EXTRACTION, NO ROOTS HAVE BEEN FOUND. *** USER INFORMATION MESSAGE 6570 (ULANCZ): 6570.0 DURING REAL UNSYMMETRIC EIGENVALUE EXTRACTION, ALL ROOTS REQUIRED HAVE BEEN FOUND. *** USER INFORMATION MESSAGE 6570 (ULANCZ): 6570.1 DURING REAL UNSYMMETRIC EIGENVALUE EXTRACTION, ALL ROOTS REQUIRED AT THIS SHIFT HAVE BEEN FOUND.

461 *** USER FATAL MESSAGE 6571 (DOPR1B) 6571.0 GN DESVAR ENTRY %1 IS LISTED AS THE DEPENDENT DESI VARIABLE ID ON MORE THAN ONE DLINK ENTRY USER ACTION: REMOVE THE DUPLICATE REFERENCE TO THE DESVAR ENTRY. *** SYSTEM FATAL MESSAGE 6571 (%1) 6571.1 A MISSING OR DUMMY SUBROUTINE HAS BEEN CALLED. *** USER WARNING MESSAGE 6572 (TASNP2) 6572.0 A TOTAL OF%1 SNORM BULK DATA ENTRIES ARE IGNORED, BECAUSE THE REFERENCED GRID POINT(S) DO NOT CONNECT TO A SHELL ELEMENT. USER INFORMATION : THE FOLLOWING IS THE LIST OF THE ENTRIES THAT ARE IGNORED. *** USER WARNING MESSAGE 6572 (TASN) 6572.1 A TOTAL OF%1 SNORM BULK DATA ENTRIES ARE IGNORED, BECAUSE THE REFERENCED GRID POINT(S) DO NOT CONNECT TO A SHELL ELEMENT. USER INFORMATION : THE FOLLOWING IS THE LIST OF THE FIRST %2 ENTRIES THAT ARE IGNORED. %3 %4 %5 %6 %7 BECAUSE OF INSUFFICIENT CORE MEMORY AVAILABLE, 6573.0 PARALLEL EMA HAS BEEN ABORTED SEQUENTIAL EMA WILL BE USED BECAUSE P - VERSION ELEMENTS ARE PRESENT, PARALLEL EMA 6573.1 HAS BEEN DESELECTED SEQUENTIAL EMA WILL BE USED BECAUSE HALF MATRIX WAS REQUESTED WITH SYSTEM(215)=1, 6573.2 PARALLEL EMA HAS BEEN DESELECTED SEQUENTIAL EMA WILL BE USED BECAUSE OF AVAILABLE CPU AND/OR SYSTEM(107) VALUE 6573.3 CHOSEN, PARALLEL EMA HAS BEEN DESELECTED SEQUENTIAL EMA WILL BE USED REVERTING TO FULL MATRIX FORM BECAUSE ASYMMETRY OF 6575.0 ELEMENT MATRICES VERSION ELEMENT LEVEL SPILL HAS BEEN ACTIVATED P - 6576.0 *** SYSTEM FATAL MESSAGE 6577 (REIGL) 6577.0 FOURTH INPUT DATA BLOCK (CASE CONTROL) IS PURGED A ND FIFTH PARAMETER VALUE (SET ID) IS ZERO IN REIGL MODULE. USER INFORMATION: SET ID MUST BE GREATER THAN ZERO IF

462 CASE CONTROL IS NOT PROVIDED AS INPUT TO MODULE. *** SYSTEM FATAL MESSAGE 6577 (LANCZOS) 6577.1 THE FIFTH INPUT DATA BLOCK (CASE CONTR OL) IS PURGED AND THE SIXTH PARAMETER'S VALUE (SET ID) IS LESS THAN ZERO IN THE LANCZOS MODULE. USER INFORMATION: THE SET ID MUST BE GREATER THAN ZERO IF CASE CONTROL IS NOT PROVIDED AS INPUT TO THE MODULE. SYSTEM FATAL MESSAGE 6577 (LNNRIGL) *** 6577.2 FOURTH INPUT DATA BLOCK (CASE CONTROL) IS PURGED AND FIFTH PARAMETER VALUE (SET ID) IS ZERO IN READ MO DULE. USER INFORMATION: SET ID MUST BE GREATER THAN ZERO IF CASE CONTROL IS NOT PROVIDED AS INPUT TO MODULE. *** SYSTEM FATAL MESSAGE 6578 (REIGL) 6578.0 REIGL MODULE PARAMETER NUMBER %1 IS OUT OF BOUNDS *** SYSTEM FATAL MESSAGE 6578 (LANCZOS) 6578.1 LANCZOS MODULE PARAMETER NUMBER %1 IS OUT OF BOUNDS *** SYSTEM FATAL MESSAGE 6578 (LANCZOS) 6578.2 THE FIRST PARAMETER (IPROB) MUST BE 'MODES *** SYSTEM FATAL MESSAGE 6578 (LNNRIGL) 6578.3 LNNRIGL MODULE PARAMETER NUMBER ii IS OUT OF BOUNDS ALL COLUMNS OF MATRIX %1 ARE NULL 6579.0 %1 IS NOT POSITIVE SEMIDEFINITE MATRIX 6580.0 MATRIX %1 IS NOT POSITIVE SEMIDEFINITE 6580.1 PERFORMING M - ORTHOGONALIZATION: MATRIX MODIFIED 6581.0 - GRAM SCHMIDT ALGORITHM PERFORMING HOUSEHOLDER ORTHOGONALIZATION 6581.1 THE NUMBER OF ROWS OF THE INPUT MATRIX %1 ARE LESS 6582.0 THAN THE NUMBER OF COLUMNS - SCHMIDT ORTHOGONALIZATION IS The MATRIX MODIFIED GRAM 6583.0 BEING PERFORMED WITH RESPECT TO AN IDENTITY MATRIX. USER INFORMATION: THE HOUSEHOLDER METHOD OF MAY BE BETTER. ORTHOGONALIZATION *** USER FATAL MESSAGE 6584 (RFORCD) 6584.0 RFORCE ENTRY REFERENCES COORDINATE SYSTEM %1 WHICH IS NOT DEFINED FOR THIS SUPERELEMENT. *** USER FATAL MESSAGE 6584 (RFORCD) 6584.1 RFORCE ENTRY REFERENCES COORDINATE SYSTEM %1 WHICH IS NOT DEFINED IN THE MAIN BULK DATA SECTION.

463 *** USER WARNING MESSAGE 6584 (RFORCD) 6584.2 METHOD = 1 IS SPECIFIED ON THE RFORCE ENTRY IN COMBINATION WITH P - ELEMENTS. USER INFORMATION: METHOD = 1 DOES NOT YIELD CORRECT - - LUMPED) RESULTS WITH P ELEMENTS AND/OR CONSISTENT(NON MASS. *** USER FATAL MESSAGE 6584 (GRAVD) 6584.3 GRAV ENTRY REFERENCES COORDINATE SYSTEM %1 WHICH IS NOT DEFINED FOR THIS SUPERELEMENT. *** USER FATAL MESSAGE 6584 (GRAVD) 584.4 6 GRAV ENTRY REFERENCES COORDINATE SYSTEM %1 WHICH IS NOT DEFINED IN THE MAIN BULK DATA SECTION. *** USER FATAL MESSAGE 6584 (ACCEL) 6584.5 ACCEL ENTRY REFERENCES COORDINATE SYSTEM %1 WHICH IS NOT DEFINED IN THE MAIN BULK DATA SECTION. *** USER FATAL MESSAGE 6584 (ACCEL1) 6584.6 ACCEL1 ENTRY REFERENCES COORDINATE SYSTEM %1 WHICH IS NOT DEFINED IN THE MAIN BULK DATA SECTION. *** USER FATAL MESSAGE 6584 (IFS1P) 6584.7 ACCEL AND ACCEL1 LOADS ARE NOT SUPPORTED FOR SOL 601 OR SOL 701 *** USER WARNING MESSAGE 6585 (MDSPC7) 6585.0 CONSTRAINTS (SPC ENTRIES) HAVE BEEN CREATED FOR THE RADIAL DEGREES OF FREEDOM WHICH ARE LOCATED ON THE AXIS OF AXISYMMETRY AND ALSO CONNECTED TO A CQUADX OR CTRIAX ELEMENT. *** USER FATAL MESSAGE 6586 (NQUDFD) 6586.0 NONZERO RADIAL DISPLACEMENTS WERE COMPUTED AT GRID POINT %1 LOCATED ON THE AXIS OF AXISYMMETRY. USER ACTION: SPECIFY CONSTRAINT S (I.E., SPC/SPC1 ENTRIES) FOR THOSE RADIAL DEGREES OF FREEDOM. *** SYSTEM FATAL MESSAGE 6587 (SEP1A) 6587.0 GRID ID = %1 FOR PRESSURE ELEMENT IS MISSING IN EQEXIN TABLE. *** USER FATAL MESSAGE 6588 (SEP1A) 6588.0 CSUPER %1 REFERENCES PRIMARY SUPERELEMENT %2 WHICH IS UNDEFINED. *** SYSTEM FATAL MESSAGE 6589 6589.0 LOGIC ERROR USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6589 6589.2 LOGIC ERROR %1

464 USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT *** SYSTEM FATAL MESSAGE 6589 6589.3 LOGIC ERROR %1 USER INFORMATION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6589 (SEP1A) 6589.4 LOGIC ERROR 19713 USER INFORMATION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. SE ID DOWNSTREAM ID PROCESS ORDER LEVEL TABLE SECON TABLE *** USER FATAL MESSAGE 6590 (SEP2R) 6590.0 RIGID ELEMENT %1 REFERENCES UNDEFINED GRID POINT %2. *** USER FATAL MESSAGE 6591 (SEP2RP) 6591.0 RIGID ELEMENT %1, SUPERELEMENT %2, DEFINES DEPENDENT EXTERIOR POINTS. *** USER FATAL MESSAGE 6593 (SEP1C) 6593.0 CSUPEXT ENTRY REFERENCES UNDEFINED SUPERELEMENT %1 *** USER FATAL MESSAGE 6594 (SEP1C) 6594.0 CSUPER %1 REFERENCES GRID POINTS IN SUPERELEMENTS %2 AND %3. *** USER FATAL MESSAGE 6595 (SEP1C) 6595.0 FIELD 2 ON CSUPER %1 IS ILLEGAL. *** USER WARNING MESSAGE 6596 (SEP1C) 6596.0 SUPERELEMENT %1 SPECIFIED ON SEFINAL COMMAND DOES NOT EXIST AND IS IGNORED. *** USER FATAL MESSAGE 6597 (SEP1C) 6597.0 SUPERELEMENT CONNECTIVITY DOES NOT OBEY SPECIFIED RULES. ORIGINAL SUPERELEMENT CONNECTION TABLE FOLLOWS USER FATAL MESSAGE 6598 (SEP1C) *** 6598.0 SECONDARY SUPERELEMENT %1 CANNOT BE PROCESSED AFTER PRIMARY SUPERELEMENT %2 *** USER FATAL MESSAGE 6599 (SEP1C) 6599.0 DUPLICATE ELEMENT IDS %1 %2 AND %3 %4 *** USER FATAL MESSAGE 6599 (SEPUEC) 6599.1 DUPLICATE ELEMENT IDS %1 %2 AND %3 %4 IN SUPERELEMENT %5 *** USER FATAL MESSAGE 6600 (ebard) 6600.0 ON CBAR=%1 THE AREA IS ZERO WHILE K1 AND/OR K2 ARE NONZERO

465 USER INFORMATION: DURING OPTIMIZATION, THE AREA MAY BE OPTIMIZED TO A ZERO VALUE. ACTION: INCREASE PMIN OR DVPREL1 OR DVPREL2 ENTRY USER OR LEAVE K1 AND K2 UNSPECIFIED. *** USER FATAL MESSAGE 6600 (IFS1P) 6600.1 ON PBAR ENTRY=%1 THE AREA IS ZERO WHILE K1 AND/OR K2 ARE NONZERO USER ACTION: SPECIFY A NONZERO AREA OR LEAVE K1 AND K2 UN SPECIFIED. *** USER FATAL MESSAGE 6601 (TA1A) 6601.0 A %1 ELEMENT REFERENCES UNDEFINED ELEMENT %2. *** USER FATAL MESSAGE 6602 (TA1A) 6602.0 ON CHBDYE ELEMENT%1 THE SIDE%2 IS INCONSISTENT WITH %3 ELEMENT %4. *** SYSTEM WARNING MESSAGE 6603 (MAKMSG) 6603.0 %1 TABLE CONVERSION REQUESTED BUT NO INPUT TABLE SUPPLIED BY PARAMETER LIST SPECIFICATIONS. *** SYSTEM WARNING MESSAGE 6604 (MAKMSG) 6604.0 %1 TABLE CONVERSION REQUESTED BUT NO INPUT TABLE SUPPLIED AS INPUT DATABLOCK, CHECK FILES VERSUS PARAMETER ORDER. *** SYSTEM WARNING MESSAGE 6605 (MAKMSG) 6605.0 CSTM CONVERSION WITH CONVECTIVE COORDINATE SYSTEMS ALSO REQUIRES THE BGPDT TABLE FOR C OMPLETENESS. *** SYSTEM WARNING MESSAGE 6606 (MAKMSG) 6606.0 A SIMULATION OF GPL RECORD 2 IS BEING CONSTRUCTED. *** SYSTEM WARNING MESSAGE 6607 (MAKMSG) 6607.0 %1 TABLE GENERATION REQUIRES ROOT DATA BLOCKS OF EQEXIN OR SIL AND GPL. *** SYSTEM WARNING MESSAGE 6608 (MAKMSG) 6608.0 CONVERSION OF CONVECTIVE COORDINATE SYSTEM %1 HAS DETECTED A MISSING EXTERNAL GRID IDENTIFICATION. *** SYSTEM WARNING MESSAGE 6609 (MAKMSG) 6609.0 CONVERSION OF EST SIL VALUES FOR ELEMENT %1 ENCOUN TERED A MISSING INDEX OF %2 *** SYSTEM WARNING MESSAGE 6610 (MAKMSG) 6610.0 CONVERSION OF NX NASTRAN V68 EST CONTAINING P - ELEMENTS CAN NOT BE DISTINTLY PERFORMED. *** SYSTEM WARNING MESSAGE 6611 (MAKMSG) 6611.0 CONVERSION OF EST CONTAINING HEAT TRANSFER ELEMENTS IS NOT SUPPORTED. **** SYSTEM WARNING MESSAGE 6612 (MAKRPL) 6612.0

466 THE ROOT DATA BLOCK TYPE %1 IS NOT KNOWN, THE DATA BLOCK INFORMATION WILL BE IGNORED. **** SYSTEM WARNING MESSAGE 6613 (MAKRPL) 6613.0 THE CONTENT OF ROOT DATA BLOCK TYPE %1 APPEARS TO BE NULL, NO CONVERSION WILL BE PERFORMED. *** (USER/SYSTEM) FATAL MESSAGE 6614 (DOMCB) 6614.0 THE DESIGNED DIMENSIONS FOR PBARL/PBEAML ENTRY = %1 ARE INCONSISTE NT AND PRODUCE BAR/BEAM SECTION PROPERTIES THAT ARE UNATTAINABLE. *** SYSTEM FATAL MESSAGE 6614 (DOMCB) 6614.1 THE DESIGNED DIMENSIONS FOR PBARL/PBEAML ENTRY = %1 ARE INCONSISTENT AND PRODUCE BAR/BEAM SECTION PROPERTIES THAT ARE UNATTAINABLE. US ER ACTION: THE INCONSISTENT DIMENSIONS HAVE MOST LIKELY BEEN PRODUCED WHEN THE OPTIMIZER WAS ATTEMPTING TO OVERCOME A VIOLATED CONSTRAINT. IF AN INITIALLY FEASIBLE DESIGN CAN BE PRODUCED, THE FATAL MESSAGE SHOULD NOT OCCUR. *** SYSTEM FATAL MESSAGE 6615 (BLEMSG) 6615.0 LOGIC ERROR ENCOUNTERED IN BEAM LIBRARY SUBROUTINE. PROGRAMMER INFORMATION: SUBNAM = %1 ERROR NUMBER = %2 SECTION TYPE = %3 USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESS AGE 6616 (DOPR1Z) 6616.0 DVPREL2 ENTRY ID = %1, REFERENCES A PBARL/PBEAML PROPERTY TYPE, WHICH IS NOT ALLOWED. USER INFORMATION: THE BEAM LIBRARY DIMENSIONS CAN ONLY BE DESIGNED USING THE DVPREL1 ENTRY. *** SYSTEM INFORMATION MESSAGE 6621 6621.0 FOR LANCZOS EIGENVALUE ANALYSIS, METHOD WILL BE USED *** SYSTEM INFORMATION MESSAGE 6621 (REIGL) 6621.1 THE PARALLEL LANCZOS METHOD IS DESELECTED AND SEQUENTIAL LANCZOS METHOD WILL BE USED BECAUSE OF AVAILABLE NUMBER OF CPUS AND/OR USER DESELECTION. (SEE PARALLEL KEYWORD ON NASTRAN STATEMENT). *** SYSTEM INFORMATION MESSAGE 6621 (REIGL) 6621.2 THE PARALLEL LANCZOS METHOD IS DESELECTED AND SEQUENTIAL LANCZOS METHOD WILL BE USED BECAU SE NON - SPARSE DECOMPOSITION IS SELECTED. (SEE SPARSE KEYWORD ON NASTRAN STATEMENT).

467 *** SYSTEM INFORMATION MESSAGE 6621 (REIGL) 6621.3 THE PARALLEL LANCZOS METHOD IS DESELECTED AND SEQUENTIAL LANCZOS METHOD WILL BE USED BECAUSE NUMBER OF SEGMENTS=1. (SEE SYSTEM CELL 197 ON NASTRAN STATEMENT OR NUMS FIELD ON EIGRL ENTRY). *** SYSTEM INFORMATION MESSAGE 6621 (REIGL) 6621.4 THE PARALLEL LANCZOS METHOD IS DESELECTED AND SEQUENTIAL LANCZOS METHOD WILL BE USED WITH ONE SEGMENT BECAUSE UPPER FREQUENCY LIMIT IS NOT SPECIFIED ON EIGRL ENTRY. *** SYSTEM INFORMATION MESSAGE 6621 (REIGL) 6621.5 THE PARALLEL LANCZOS METHOD IS DESELECTED AND SEQUENTIAL LANCZOS METHOD WILL BE USED ES IS SPECIFIED BECAUSE THE NUMBER OF DESIRED EIGENVALU ON EIGRL ENTRY. *** SYSTEM INFORMATION MESSAGE 6621 (REIGL) 6621.6 FOR LANCZOS EIGENVALUE ANALYSIS METHOD WILL BE USED WITH ONE SEGMENT BECAUSE UPPER FREQUENCY LIMIT IS NOT SPECIFIED ON EIGRL ENTRY. SYSTEM CELL 199 = %1 FORCES MASS MATRIX TO BE LOADED IN 6622.0 MEMORY. *** USER FATAL MESSAGE 6624 (IFP9) 6624.0 SEE INFORMATION MESSAGES ABOVE *** USER WARNING MESSAGE 6625 (VIEW) 6625.0 MORE THAN 30 PAIRS OF GLOBAL VIEW FACTORS ARE SPECIFIED FOR RADIATION CAVITY ID=%1. USER INFORMATION: THE EXTRA PAIRS OF GLOBAL VIEW FACTORS ARE IGNORED. *** USER INFORMATION MESSAGE 6626, (MODGM1), 6626.0 GRID ID = %1 THE DISPLACEMENT COORDINATE SYSTEM OF THE IS MODIFIED TO CID =%2 TO MATCH THE CORRESPONDING %3 ID =%4 CONSTRAINT COORDINATE SYSTEM. USER ACTION: IF THIS IS NOT DESIRE, SPECIFY A COORDINATE SYSTEM ID IN THE CD FIELD OF GRID ENTRY. *** SYSTEM WARNING MESSAGE 6627 (LANCZ ) 6627.0 %1 %1 6628.0 SCALER ELEMENT ID =%1 SPECIFIES A CONNECTION TO ITSELF. *** USER FATAL MESSAGE 6629 (TA1BSH) 6629.0 BUSH ELEMENT ID = %1 HAS INFINITESIMAL LENGTH USER ACTION : SPECIFY CID FIELD ON THE CBUSH ENTRY. *** USER FATAL MESSAGE 6629 (EBSH3D) 6629.1 BUSH ELEMENT ID = %1 IS SPECIFIED WITH A ORIENTATION

468 VECTOR WHICH IS INFINITESIMAL OR PARALLEL TO AXIS AB. *** USER FATAL MESSAGE 6631 (EASFD) 6631.0 TWO GRID POINTS ARE COINCIDENT OR THREE GRID POINTS ARE COLLINEAR FOR ELEMENT ID = %1 *** USER FATAL MESSAGE 6632 (EASFD) 6632.0 THE NORM OF IMPEDANCE IS TOO SMALL FOR ELEMENT ID = %1 IN FREQUENCY = %2 *** USER FATAL MESSAGE 6633, (MODGM1), 6633.0 FOR GRID ID = %1 CONSTRAINT COORDINATE SYSTEMS SPECIFIED ON THE CIDBC FIELD OF THE %2 ENTRY ID =%3 AND %4 ENTRY ID =%5 ARE NOT THE SAME. USER ACTION: EXPLICITLY DEFINE COORDINATE SYSTEM ID IN NTRY, THE CD FIELD OF THE GRID E WHICH OVERRIDES THE CIDBC FIELD. *** SYSTEM FATAL MESSAGE 6634 (SSM7D) 6634.0 INSUFFICIENT MEMORY AS DESCRIBED IN THE FATAL MESSAGE BELOW. USER ACTION: INCREASE MEMORY OR SPECIFY A BLOCK SIZE OF 1 ON THE EIGRL ENTRY OR THE LANCZOS DMAP MODULE SPECIFICATION. *** SYSTEM FATAL MESSAGE 6635 (TABLD) 6635.0 INVALID INPUT FOR TABLE INTERPOLATION. TABLE ID = %1 FOR LOGARITHMIC X - AXIS, VALUE = %2 USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM WARNING MESSAGE 6636 6636.0 THE FOLLOWING DIAGNOSTIC(S) ARE ISSUED BY THE LANCZOS MODULE. *** SYSTEM WARNING MESSAGE 6636 (LNCTRD) 6636.4 NO MODES EXIST IN THE INTERVAL SPECIFIED (0.0 TO %1 HZ). *** SYSTEM WARNING MESSAGE 6636 (LNCTRD) 6636.5 NO MODES EXIST IN THE INTERVAL SPECIFIED (%1 TO %2 HZ). *** SYSTEM WARNING MESSAGE 6636 (LNCTRD) 6636.6 THERE ARE ONLY %1 MODES BELOW %2 HZ. *** SYSTEM WARNING MESSAGE 6636 (LNCTRD) 6636.7 NO MODES EXIST ABOVE %1 HZ. *** USER WARNING MESSAGE 6637 (TASNP2) 6637.0 THE SPECIFIED VALUE FOR PARAM SNORM IS %1 DEGREES USER INFORMATION : THE PROGRAM WILL USE A VALUE OF %2 DEGREES. *** SYSTEM FATAL MESSAGE 6638 (DOP1c1) 6638.0 THE %1 SECTION TYPES IN GROUP %2 EXCEED THE LIMIT OF %3

469 FOR USER DEFINED BEAM LIBRARIES. USER ACTION: REDUCE THE NUMBER OF SECTION TYPES. *** SYSTEM FATAL MESSAGE 6640 (SSM5D): 6640.0 ITERATIVE SOLVER IS NOT AVAILABLE FOR LANCZOS SUPERMODULE. R ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER USE SUPPORT. PROGRAMMER INFORMATION: IOPTI = %1 *** SYSTEM FATAL MESSAGE 6641 (SK11RD) 6641.0 ERROR IN READING K11 MATRIX FOR ITERATIVE SOLVER INSIDE STATICS MODULE. NUMBER OF INDICES AND ERMS ARE INCOMPATIBLE IN COLUMN %1 NUMBER OF NZ T NUMBER OF INDICES: %2 NUMBER OF NZ TERMS: %3 *** SYSTEM FATAL MESSAGE 6641 (SCALRD): 6641.1 ERROR IN READING K11 MATRIX FOR ITERATIVE SOLVER INSIDE STATICS SUPERMODULE. NUMBER OF INDICES AND NUMBER OF NZ TERMS ARE INCOMPATIBLE IN COLUMN %1 NUMBER OF INDICES: %2 NUMBER OF NZ TERMS: %3 *** USER INFORMATION MESSAGE 6642 (SSM9D) 6642.0 ERROR RATIO(S) FOR FIRST %1 MODES: *** USER INFORMATION MESSAGE 6643 (SSM9D) 6643.0 ERROR RATIO FOR LARGEST EPSILON VALUE IN FIRST TEN MODES MODES: *** SYSTEM FATAL MESSAGE 6644 (DOM10) 6644.0 DESCYCLE, THE FIRST PARAMETER IN THE DOM10 MODULE HAS AN INVALID VALUE OF %1. PROGRAMMER INFORMATION: VALID VALUES OF DESCYCLE ARE 1 OR - A POSITIVE INTEGER, - 2. *** USER WARNING MESSAGE 6644 (FRPROD) 6644.1 SOME OR ALL COMPUTED EXCITATION FREQUENCIES ARE OUTSIDE THE RANGE F1 AND F2 FOR %1 BULK DATA ENTRY WITH ID =%2 THESE C OMPUTED EXCITATION FREQUENCIES ARE IGNORED. *** USER WARNING MESSAGE 6645 (FRSRTD) 6645.0 FREQ3, FREQ4, AND/OR FREQ5 ENTRIES ARE PRESENT IN A DIRECT FREQUENCY RESPONSE ANALYSIS; THEY WILL BE IGNORED. *** USER FATAL MESSAGE 6647 (FRSRTD) 6647.0 EXCITATION FREQUENCIES CAN NOT BE COMPUTED. BECAUSE FREQUENCIES ARE NOT AVAILABLE. *** USER FATAL MESSAGE 6647 (FRSRTD) 6647.1 EXCITATION FREQUENCIES CAN NOT BE COMPUTED. BECAUSE FREQUENCIES ARE NOT AVAILABLE.

470 U SER ACTION: PROVIDE FREQ, FREQ1 OR FREQ2 CARDS *** USER WARNING MESSAGE 6648 (FRPROD) 6648.0 THE NUMBER OF FREQUENCIES SPECIFIED ON THE FREQ4 ENTRY ID = %1 IS NOT AN ODD NUMBER. USER INFORMATION : AN EXTRA FREQUENCY WILL BE INCLUDED. *** SYSTEM WARNING MESSAGE 6650 (SSM2) 6650.0 IMPROPER SET SPECIAL DEFINITION. *** SYSTEM WARNING MESSAGE 6651 (SSM2) 6651.0 IMPROPER USET TABLE READING. *** USER FATAL MESSAGE 6652 (SSM3D) 6652.0 DIFFERENT NUMBER OF LOAD VECTORS AND ENFORCED DI SPLACEMENT VECTORS IN STATICS MODULE NUMBER OF LOAD VECTORS = %1 NUMBER OF ENFORCED DISPLACEMENT VECTORS = %2 *** USER WARNING MESSAGE 6653 6653.0 ONLY ONE LOAD VECTOR IS ALLOWED WITH THE ITERATIVE SOLVER THE FIRST ONE WILL BE USED AND THE OTHERS IGNORED *** SYSTEM FATAL MESSAGE 6653 (SITDRD) 6653.1 INSIDE THE MODULE, THE ITERATIVE SOLVER IS NOT AVAILABLE FOR MULTIPLE LOAD CASES. *** USER WARNING MESSAGE 6654 (DOM9PR) 6654.0 RESET TO 1 (DIRECT) BECAUSE THE DESIGN APRCOD HAS BEEN VARIABLES ARE POTENTIALLY ZERO. USER INFORMATION: APRCOD IS SET ON THE DOPTPRM BULK DATA ENTRY. APRCOD VALUES OF 2 OR 3 CAUSE A DIVIDE BY ZERO ERROR WHEN THE DESIGN VARIABLE VALUE IS ZERO. *** USER WARNING MESSAGE 6654 (DISPR) 6654.1 APRCOD HAS BEEN RESET TO 1 (DIRECT) BECAUSE THE DESIGN VARIABLES ARE POTENTIALLY ZERO. USER INFORMATION: APRCOD IS SET ON THE DOPTPRM BULK DATA ENTRY. APRCOD VALUES OF 2 OR 3 CAUSE A DIVIDE BY ZERO ERROR WHEN THE DESIGN VARIABLE VALUE IS ZERO. *** USER FATAL MESSAGE 6655 (LANCZ) 6655.0 THE CASE CONTROL COMMAND METHOD=%1 REFERENCES AN UNSPECIFIED EIGRL BULK DATA ENTRY. USER ACTION: SUPPLY AN EIGRL ENTRY. PROGRAMMER ACTION: ALTERNATIVELY, SET THE SIXTH PARAMETER TO THE LANCZOS MODULE (SET ID) TO A NEGATIVE INTEGER AND SUPPLY EIGRL VALUES TO THE

471 LANCZOS MODULE DIRECTLY AS PARAMETERS SEVEN THROUGH THIRTEEN. *** USER FATAL MESSAGE 6656 (MODTRK) 6656.0 THE TRACKED SUBSET %1 OF MODES FROM A PREVIOUS DESIGN CY CLE CAN NOT BE FOUND. USER ACTION: CALL SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 6657 (MTD0RD) 6657.0 NO DRESP1 BULK DATA ENTRIES WERE SPECIFIED FOR PURPOSES OF MODE TRACKING. USER WARNING MESSAGE 6658 (MTD0RD) *** 6658.0 THERE ARE NO DRESP1 RESPONSES MATCHING THE MODES SPECIFIED FOR MODE TRACKING. *** USER FATAL MESSAGE 6660 (VIEW) 6660.0 THE RADIATION MATRIX FOR RADIATION CAVITY ID=%1 DEFINED ON RADLST OR RADMTX BULK DATA ENTRIES HAS WRONG FORMAT OR DATA. USER INFORMATION: THE RADIATION MATRIX MUST BE SPECIFIED COMPLETELY. *** USER INFORMATION MESSAGE 6661 (VIEWP) 6661.0 THE CURRENT SUPERELEMENT DOES NOT CONTAIN ANY P - ELEMENTS. RMATION MESSAGE 6661 (SDR2AA) *** USER INFO 6661.1 - ELEMENTS. THE CURRENT MODEL DOES NOT CONTAIN ANY P *** USER FATAL MESSAGE 6662 (IFP6CD) 6662.0 ONE OR MORE MAT1 ENTRIES SPECIFY ZERO FOR YOUNG'S MODULUS , E. USER INFORMATION: MAT1 ENTRIES REFERENCED BY PCOMP ENTRIES MUST HAVE A YOUNG'S MODULUS GREATER THAN ZERO. *** SYSTEM WARNING MESSAGE 6663 (FRRD1D) 6663.0 THE SOLUTION FOR FREQUENCY %1 (HZ) DID NOT CONVERGE USING THE ITERATIVE SOLVER. USER INFORMAT ION: THE RESULTS FOR THIS FREQUENCY SHOULD BE INSPECTED FOR VALIDITY. USER ACTION: RERUN THE JOB ONLY FOR THIS FREQUENCY WITH A HIGHER MAXIMUM NUMBER OF ITERATIONS (INCREASE ITSMAX ON ITER BULK DATA ENTRY) OR USING THE DIRECT METHOD (SET ITER=0 ON THE % 2 STATEMENT). *** SYSTEM INFORMATION MESSAGE 6664. (DRMH1C) 6664.0 ELEMENT NUMBER %1 TYPE %2 IS NOT SUPPORTED BY MODULE DRMH1.

472 ***0 USER FATAL MESSAGE 6664 (AXMPR2) 6664.1 AUXILIARY MODEL ID=%1 HAS A %2 BULK DATA ENTRY WITH A DUPLICATE ID=%3. USER INFORMATION: THE IDENTIFICATION NUMBER FOR THIS ENTRY MUST BE UNIQUE WITH RESPECT TO ANY SIMILAR ENTRY TYPE IN THE PRIMARY MODEL BULK DATA. *** SYSTEM WARNING MESSA GE 6665 (GP4) 6665.0 NOT ENOUGH BUFFER SPACE WAS RESERVED TO READ THE SUPORT1 BULK DATA ENTRIES. %1 WORDS ALLOCATED PROGRAMMER INFORMATION: PROBABLE CAUSE IS TOO SMALL A SPACE ALLOCATED. PROGRAMMER ACTION: SPECIFY MAXX TO BE GREATER THAN TWO SYSBUFS. *** SYSTEM WARNING MESSAGE 6670 (SEQPRT) 6670 .0 - SUFFICIENT MEMORY IS NOT AVAILABLE TO RESEQUENCE P ELEMENT HIERARCHICAL GRID POINTS IN ORDER TO OBTAIN MAXIMUM EFFICIENCY DURING MATRIX DECOMPOSITION. USER ACTION: INCREASE MEMORY USING THE MEM KEYWORD E NASTRAN COMMAND OR ON TH THE HICORE KEYWORD ON THE NASTRAN STATEMENT. *** USER INFORMATION MESSAGE 6671 (MATMOD): 6671.0 FOR MATMOD OPTION 10 (COMPLEX CONJUGATE) THE INPUT DATA BLOCK %1 IS REAL (TYPE = %2). USER INFORMATION: THE INPUT DATA BLOCK WILL BE COPIED TO THE OUTPUT DATA BLOCK. *** USER INFORMATION MESSAGE 6672 (MTD1RD) 6672.0 THE NUMBER OF DEGREES OF FREEDOM IN THE ANALYSIS SET (A - SET) HAVE CHANGED FROM THE PREVIOUS DESIGN CYCLE. MATION: ALL DEGREES OF FREEDOM WILL BE USED. USER INFOR *** USER FATAL MESSAGE 6673 (MTD1RD) 6673.0 THE NUMBER OF DEGREES OF FREEDOM (G - SET) HAS CHANGED FROM THE PREVIOUS DESIGN CYCLE. *** USER FATAL MESSAGE 6674 (MTD1RD) 6674.0 MODTRAK BULK DATA ENTRY WITH SID =%1 CANNOT BE FOUND. *** USER INFORMATION MESSAGE 6675 (MTD1RD) 6675.0 LOWRNG = %1 ON THE MODTRAK BULK DATA ENTRY IS GREATER THAN THE LOWEST DRESP1 MODE %2. LOWRNG WILL AUTOMATICALLY BE REDUCED TO %3. *** USER INFORMATION MESSAGE 6676 (MTD1RD) 6676.0 HIGHRNG = %1 ON THE MODTRAK BULK DATA ENTRY IS LOWER THAN THE HIGHEST

473 DRESP1 MODE %2. HIGHRNG WILL AUTOMATICALLY BE INCREASED TO %3. RUN TERMINATED DUE TO MODE TRACKING FAILURE. SEE USER 6677.0 FATAL MESSAGE 6677 (MTFTRD) PRINTED ABOVE FOR INFORMATION. *** USER FATAL MESSAGE 6677 (MTFTRD) 6677.1 MODES CANNOT BE TRACKED: IN ORDER TO TRACK THESE MODES, IT MAY BE APPROPRIATE TO: 1. REDUCE M OVE LIMITS (DELP,DPMIN,DELX,DELXV,DXMIN), OR 2. DECREASE THE FILTERING PARAMETER, MTFILTER, OR 3. BOTH 1 AND 2 THE PUNCH FILE MAY CONTAIN UPDATED DRESP1 ENTRIES FROM A PREVIOUS DESIGN CYCLE, WITH 'EIGN IN FIELD 7 WRITTEN TO CORRESPOND WITH THE POSITION S OF THE SUCCESSFULLY TRACKED MODES (OUTPUT OF UPDATED DRESP1 ENTRIES IS CONTROLLED BY BULK DATA PARAMETER DESPCH. SEE QUICK REFERENCE GUIDE FOR ITS DETAILED DESCRIPTION). THESE DRESP1 ENTRIES CAN BE USED TO RESTART FROM THE FICATIONS 1, 2, OR 3, ABOVE. LAST DESIGN, WITH ANY OF MODI FOLLOWING ARE THE CORRESPONDING NEW POSITIONS OF THE 6678.0 SWITCHING DESIGNED MODES: *** USER FATAL MESSAGE 6679 (MTMCRD) 6679.0 TWO OR MORE MODES ARE NEARLY IDENTICAL, WHICH MAKES TRACKING THE MODES NOT POSSIBLE. USER ACTION: RERUN USING A SMALLER VALUE ON ONE OR MORE OF THE FOLLOWING: 1) DELXV PARAMETER OF THE DESVAR BULK DATA ENTRY 2) DELP PARAMETER OF THE DOPTPRM BULK DATA ENTRY 3) DELX PARAMETER OF THE DOPTPRM BULK DATA ENTRY *** USE R INFORMATION MESSAGE 6681 (SEQRS). 6681.0 THE MULTIPLE MINIMUM DEGREE METHOD OF RESEQUENCING WAS EXECUTED, HOWEVER, NO DECOMPOSITION ESTIMATES WERE COMPUTED. USER ACTION: IF ESTIMATES ARE REQUIRED, THEN SPECIFY SYSTEM(222)=1 ON THE NASTRAN STATEMENT. *** USER INFORMATION MESSAGE 6681 (SEQRS). 6681 .1 THE NESTED DISSECTION METHOD OF RESEQUENCING WAS EXECUTED, HOWEVER, NO DECOMPOSITION ESTIMATES WERE COMPUTED. USER ACTION: IF ESTIMATES ARE REQUIRED, THEN SPECIFY SYSTEM(222)=1 ON THE NASTRAN STATEMENT. *** USER INFORMATION MESSAGE 6681 (SEQRS). 6681.2 THE GIBBS - KING METHOD OF RESEQUENCING WAS EXECUTED,

474 HOWEVER, NO DECOMPOSITION ESTIMATES WERE COMPUTED. USER ACTION: IF ESTIMATES ARE REQUIRED, THEN SPECIFY SYSTEM(222)=1 ON THE NASTRAN STATEMENT. *** USER INFORMATION MESSAGE 6681 (SEQRS). 6681.3 THE WAVEFRONT METHOD OF RESEQUENCING WAS EXECUTED, HOWEVER, NO DECOMPOSITION ESTIMATES WERE COMPUTED. USER ACTION: IF ESTIMATES ARE REQUIRED, THEN SPECIFY SYSTEM(222)=1 ON THE NASTRAN STATEMENT. *** USER INFORMATION MESSAGE 6682 (FRRDR1) 682.0 6 NOT MODAL FREQUENCY RESPONSE, FALL BACK TO FRRD1. *** USER INFORMATION MESSAGE 6682 (FRRDR1) 6682.1 FALL BACK TO FRRD1 DUE TO THE STRUCTURE OF MATRIX %1. *** USER INFORMATION MESSAGE 6682 (FRRDR1) 6682.2 UNCOUPLED SOLUTION NEEDED, FALL BACK TO FRRD1. *** USER INFORMATION MESSAGE 6682 (FRRDR1) 6682.3 OUT OF MEMORY. USER ACTION: ADD %1 WORDS TO RUN AGAIN. *** USER INFORMATION MESSAGE 6682 (FRDPRE) 6682.4 DUPLICATE MODES FOUND. FALL BACK TO FRRD1. *** USER INFORMATION MESSAGE 6682 (FRDPRE) 6682.5 RIGID MODES FOUND. FALL BACK TO FRRD1. USER ACTION: FOR BETTER PERFORMANCE, ALTER EIGRL CARD OR ADD PARAM LFREQ TO AVOID RIGID MODES. *** USER INFORMATION MESSAGE 6682 (FRDSMP) 6682.6 NEEDS %1 ADDITIONAL WORDS OF MEMORY TO USE IN - CORE FRRD1 WITH PARALLEL=%2. FALL BACK TO NXN85 FRRD1. USER ACTION: FOR BETTER PERFORMANCE, INCREASE MEMORY TO USE PARALLEL IN CORE FRRD1. - *** USER INFORMATION MESSAGE 6682 (FRDSMP) 6682.7 NEEDS %1 ADDITIONAL WORDS OF MEMORY TO USE IN - CORE FRRD1 WITH PARALLEL=%2. FALL BACK TO USE IN - RALLEL=%3. CORE FRRD1 WITH PA USER ACTION: INCREASE MEMORY FOR BETTER PERFORMANCE IN FRRD1. *** USER INFORMATION MESSAGE 6682 (FRDGPU) 6682.8 FRDGPU FAILED. FALL BACK TO FRRD1. *** USER INFORMATION MESSAGE 6682 (FRDGPU) 6682.9 FRDGPU NEEDS MORE MEMORY FOR LOADS. FALL BACK TO FRRD1. *** USER INFORMATION MESSAGE 6682 (FRDSMP) 6682.10 MATRICES IN FRRD1 ARE SPARSE. FOR BETTER PERFORMANCE,

475 %1 IS SELECTED. *** USER INFORMATION MESSAGE 6682 (FRDGPU3) 6682.11 - DITIONAL WORDS OF MEMORY TO USE IN NEEDS %1 AD CORE FRRD1 WITH PARALLEL=%2. FALL BACK TO USE IN - CORE FRDGPU WITH PARALLEL=%3. USER ACTION: INCREASE MEMORY FOR BETTER PERFORMANCE IN FRDGPU. *** USER INFORMATION MESSAGE 6682 (FRDGPU3) 6682.12 NEEDS %1 ADDITIONAL WORDS OF MEMORY TO USE IN - CORE FRDGPU WITH PARALLEL=%2. FALL BACK TO NXN85 FRRD1. USER ACTION: FOR BETTER PERFORMANCE, INCREASE MEMORY TO USE PARALLEL IN - CORE FRDGPU. *** USER FATAL MESSAGE 6683 (FRRD1A) 6683.0 ALL COMPUTED EX CITATION FREQUENCIES ARE OUTSIDE THE RANGE F1 AND F2 FOR FREQ4 AND/OR FREQ5 BULK DATA ENTRIES, OR THERE ARE NO FREQi BULK DATA ENTRIES SPECIFIED. PROGRAMMER INFORMATION: INPUT FILE 4 DOES NOT EXIST. *** USER FATAL MESSAGE 6684 (DOPR3A) 6684.0 NOR MAL MODES RTYPE = EIGN AND RTYPE = FREQ HAVE BEEN SELECTED BY DRESP1 ENTRIES IN THE SAME RUN. USER ACTION: USE EITHER OF THEM BUT NOT BOTH ON DRESP1 ENTRIES. *** SYSTEM INFORMATION MESSAGE 6687 (SOLVIT) 6687.0 ALTERNATIVE CONVERGENCE CRITERION IS NOT AVAILABLE - VERSION PROBLEMS. FOR P USER INFORMATION: CRITERION SWITCHED TO REGULAR CONVERGENCE |R|/|B|. *** USER FATAL MESSAGE 6688 (CONSSD) 6688.0 ELEMENT %1 ON RSSCON BULK DATA ENTRY %2 IS OF ELEMENT TYPE %3 WHICH CANNOT BE REFERENCED AS A SOLID ELEMENT ON AN RSSCON. *** USER FATAL MESSAGE 6688 (CONSSD) 6688.1 ELEMENT TYPE %1 ATTACHED TO SOLID ELEMENT %2 ON RSSCON BULK DATA ENTRY %3 CANNOT BE REFERENCED AS A SHELL ELEMENT ON AN RSSCON. *** USER FATAL MESSAGE 6688 (SECNSD) 6688.2 ELEMENT %1 HAS GRID POINTS THAT CANNOT BE LOCATED *** USER FATAL MESSAGE 6689 (GP4RS2) 6689.0 BULK DATA RSSCON %1 ELEMENT %2 CONNECTED TO ELEMENT %3 IS AN INCOMPLETE ATTACHMENT. ONLY A SUBSET OF THE SHELL G RID AND EDGE DEGREES OF

476 FREEDOM ARE CONSTRAINED *** USER FATAL MESSAGE 6689 (CONSSD) 6689.1 RSSCON NUMBER %1 CANNOT CONNECT %2 ELEMENT %3 TO %4 ELEMENT %5 USER ACTION: CHECK GEOMETRY *** USER FATAL MESSAGE 6689 (SECNS2) 6689.2 BULK DATA RSSCON %1 ELEMENT %2 CONNECTED TO ELEMENT %3 IS AN INCOMPLETE ATTACHMENT. *** USER FATAL MESSAGE 6690 (EDGEPD) 6690.0 THE SHELL ELEMENT GRID POINT ID %1 DOES NOT LIE BETWEEN SOLID GRID POINT IDS %2 AND %3. USER ACTION: CHECK CONNECTIVITY ON THE RSSCON BULK DATA ENTRY. *** USER FATAL MESSAGE 6692 (RSSCND) 6692.0 FEEDGE BULK DATA ENTRY %1 SPECIFIED ON RSSCON BULK DATA ENTRY %2 IS NOT DEFINED. *** USER FATAL MESSAGE 6692 (GP4RSS) 6692.1 SOLID ELEMENT %1 SPECIFIED ON A RSSCON BULK DATA ENTRY IS NOT DEFINED. *** USER FATAL MESSAGE 6692 (GP4RS1) 6692.2 SHELL ELEMENT ID %1 SPECIFIED ON RSSCON BULK DATA ENTRY %2 WITH SOLID ELEMENT %3 IS NOT DEFINED. *** USER FATAL MESSAGE 6692 (%1) 6692.3 RSSCON NUMBER %1 CANNOT CONNECT AN EDGE OF %2 ELEMENT %3 TO %4 ELEMENT %5 *** USER FATAL MESSAGE 6692 (%1) 6692.4 RSSCON NUMBER %2 CANNOT CONNECT AN EDGE OF SHELL ELEMENT %3 TO SOLID ELEMENT %4 ATAL MESSAGE 6692 (SEPMEP) *** USER F 6692.5 ELEMENT %1 SPECIFIED ON RSSCON ENTRY %2 IS NOT DEFINED. *** USER FATAL MESSAGE 6692 (GP4RS1) 6692.6 BULK DATA ENTRY RSSCON CAN NOT FIND ELEMENT IDS, USER ACTION: CHECK SUPERELEMENT STRUCTURE. *** USER FATAL MESSAGE 6693 (GP4RS3) 6693.0 GRID POINT %1 WHICH IS REFERENCED ON RSSCON BULK DATA ENTRY ID = %2 IS NOT DEFINED. *** USER FATAL MESSAGE 6694 (GP4RS4) 6694.0 RSSCON CAUSES CONFLICTING ROTATIONAL CONSTRAINTS AT SHELL GRID POINT %1 *** USER FATAL MESSAGE 6695 (%1) 6695.0 RSSCON NUMBER %1 WILL MPC ONLY GRID %2 OF %3 ELEMENT %4 TO %5 ELEMENT %6

477 IT WILL NOT MPC GRID%7; THE CORNER SHELL GRIDS MUST LIE ON OPPOSITE EDGES OF A FACE OF THE SOLID ELEMENT. *** USER FATAL MESSAGE 6695 (GP4RCD) 6695.1 RSSCON %1 CANNOT CONNECT SHELL GRID POINT %2 : USER ACTION, CHECK THE GEOMETRY *** SYSTEM FATAL MESSAGE 6696 (RSSCND) 6696.0 RSSCON BULK DATA ENTRY %1 WITH FEEDGE ID %2 REFERS TO FEEDGE WITH %3 INSTEAD OF THE %4 REQUIRED DEGREES OF FREED OM. *** SYSTEM FATAL MESSAGE 6697 (RSSCND) 6697.0 RSSCON BULK DATA ENTRY %1 HAS EDGES WITH INCONSISTENT POLYNOMIAL ORDERS %2 %3 %4. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 6697 (RSSCND) 6697.1 AUTOMPC CANNOT BE USE IN CONJUNCTION WITH RSSCON ELEMENT %1 *** SYSTEM FATAL MESSAGE 6698 (TWOEDG) 6698.0 CANNOT FIND COMMON GRID AMONG %1 %2 %3 %4 ON ELEMENT ID %5. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. A SINGLE PRECISION INPUT MATRIX %1 CANNOT BE PROCESSED 6699.0 ON THIS TYPE MACHINE WHICH IS DOUBLE PRECISION. A DOUBLE PRECISION INPUT MATRIX %1 CANNOT BE PROCESSED 6699.1 ON THIS TYPE MACHINE WHICH IS SINGLE PRECISION. *** USER WARNING MESSA GE 6700 (FRRD2) 6700.0 A FREQUENCY RESPONSE SOLUTION AT THIS EXCITATION FREQUENCY IS NOT POSSIBLE. USER INFORMATION: NO SOLUTION WAS POSSIBLE AT THIS FREQUENCY DUE TO A POSSIBLE SINGULARITY IN THE COMBINED STIFFNESS, MASS, AND DAMPING MATRIX. *** USER WARNING MESSAGE 6700 (FRRD2) 6700.1 A FREQUENCY RESPONSE SOLUTION AT EXCITATION FREQUENCY=0.0 IS NOT POSSIBLE. USER INFORMATION: THE LIKELY CAUSE IS UNRESTRAINED RIGID BODY MODES. NO SOLUTION WAS ATTEMPTED AT FREQUENCY=0.0 *** USER WARNING MESSAGE 6701 (IFS1P) 6701.0 BIT, SA, AND SB ARE SPECIFIED FOR CBEAM ELEMENT %1.

478 USER INFORMATION: SA,SB WILL BE IGNORED. *** USER WARNING MESSAGE 6701 6701.1 THE MAXIMUM GAP OF %1 BETWEEN A BOUNDARY AND TC INTERFACE ELEMENT EXCEEDS THE TOLERANCE ON THE PIN ENTRY. USER INFORMATION: THE BOUNDARY IS DEFINED ON GMBNDC BULK DATA ENTRY=%2 AND INTERFACE ELEMENT ON GMINTC BULK DATA ENTRY=%3. *** USER WARNING MESSAGE 6701 (EIFOED) 6701.3 THE MAXIMUM GAP OF %1 BETWEEN A BOUNDARY AND INTERFACE ELEMENT EXCEEDS THE TOLERANCE ON THE PINTS ENTRY. USER INFORMATION: THE BOUNDARY IS DEFINED ON GMBNDS BULK DATA ENTRY=%2 AND INTERFACE ELEMENT ON GMINTS BULK DATA ENTRY=%3. *** USER WAR NING MESSAGE 6702 (EINPED) 6702.2 A BOUNDARY END POINT DOES NOT MATCH THE CORRESPONDING INTERFACE ELEMENT END POINT. USER INFORMATION: THE BOUNDARY IS DEFINED ON GMBNDC BULK DATA ENTRY=%1 AND INTERFACE ELEMENT ON GMINTC BULK DATA ENTRY=%2. *** USER WARNING MESSAGE 6702 (EINOED) 6702.3 A BOUNDARY END POINT DOES NOT MATCH THE CORRESPONDING INTERFACE ELEMENT END POINT. USER INFORMATION: THE BOUNDARY IS DEFINED ON GMBNDC BULK DATA ENTRY=%1 AND INTERFACE ELEMENT ON GMINTC BULK DATA ENTRY=%2. *** USER WARNING MESSAGE 6702 (EIFOED) 6702.4 SOME POINTS ON THIS INTERFACE ELEMENT DO NOT COINCIDE WITH POINTS ON A BOUNDARY. USER INFORMATION: THE BOUNDARY IS DEFINED ON GMBNDS BULK DATA ENTRY=%1 AND INTERFACE ELEMENT ON GMINTS BULK DATA ENTRY=%2. *** SYSTEM FATAL MESSAGE 6703 (SSMB1D) 3.0 670 INTERNAL POINTER ERROR: BAD FRONT SIZE CALCULATIONS ON SPLIT 2X2. FRONT ARRAY WILL CONTAIN INVALID TERMS. *** USER WARNING MESSAGE 6703 (EINPED) 6703.1 THE LENGTH OF AN ELEMENT'S EDGE ON A BOUNDARY IS SMALL ENOUGH TO CAUSE NUMERICAL INSTABILITY. USER INFORMATION: THE BOUNDARY IS DEFINED ON GMBNDC BULK DATA ENTRY=%1 AND INTERFACE ELEMENT ON GMINTC BULK DATA ENTRY=%2. *** USER WARNING MESSAG E 6703 (EINOED) 6703.2

479 THE LENGTH OF AN ELEMENT'S EDGE ON A BOUNDARY IS SMALL ENOUGH TO CAUSE NUMERICAL INSTABILITY. USER INFORMATION: THE BOUNDARY IS DEFINED ON GMBNDC BULK DATA ENTRY=%1 AND INTERFACE ELEMENT ON GMINTC BULK DATA ENTRY=%2. *** SY STEM FATAL MESSAGE 6704 (DFMFCD) 6704.0 LOGIC ERROR%1 IN NUMERIC PHASE OF SPARSE DECOMPOSITION. USER ACTION: INCREASE MEMORY BY%2 WORDS. *** SYSTEM FATAL MESSAGE 6704 (DFMFRS) 6704.1 MEMORY OVERFLOW OF FRONT IN NUMERIC PHASE OF SPARSE DECOMPOSITION. USER ACTION: USE AN ALTERNATE SOLVER FOR ADDITIONAL DIAGNOSTICS. *** SYSTEM WARNING MESSAGE 6705 (DFMAGC) 6705.0 LOGIC ERROR 2 IN SYMBOLIC PHASE OF SPARSE DECOMPOSITION USER INFORMATION: PERFORMANCE MAY BE DEGRADED AND/OR MORE MEMORY MAY BE REQUIRED IF THE MATRIX HAS NOT BEEN RESEQUENCED PROPERLY *** SYSTEM WARNING MESSAGE 6705 (DFMASK) 6705.2 LOGIC ERROR 3 IN SYMBOLIC PHASE OF SPARSE DECOMPOSITION USER INFORMATION: PERFORMANCE MAY BE DEGRADED AND/OR MORE MEMORY MAY BE HE MATRIX HAS NOT BEEN RESEQUENCED REQUIRED IF T PROPERLY *** SYSTEM WARNING MESSAGE 6705 (DFMSYA) 6705.3 LOGIC ERROR 1 IN SYMBOLIC PHASE OF SPARSE DECOMPOSITION. USER INFORMATION: PERFORMANCE MAY BE DEGRADED AND/OR MORE MEMORY MAY BE REQUIRED IF THE MATRIX HAS NOT BEEN RESEQUENCED PROPERLY. *** SYSTEM FATAL MESSAGE 6706 (PARAML) 6706.0 PARAML OPTION P1=%1 IS NOT VALID. *** SYSTEM FATAL MESSAGE 6707 (PARAML) 6707.0 THE PARAML MODULE WITH P1=DTI DETECTS A STRING RECORD. *** USER FATAL MESSAGE 6708 (EBTMPD) 6708.0 CBEAM ELEMENT %1 DOES NOT HAVE ITS TEMPERATURE SPECIFIED ON TEMP, TEMPD, TEMPF OR TEMPRB BULK DATA ENTRIES. USER INFORMATION: P - VERSION CBEAM ELEMENTS CAN ONLY HAVE THEIR TEMPERATURES SO SPECIFIED.

480 THE FIFTH INPUT DMAP PARAMETER ( VECTOR DEPENDENCY 6709.0 TOLERANCE ) IS GREATER THAN ONE. USER INFORMATION: RESULTS MAY BE IMPLAUSIBLE. *** SYSTEM FATAL MESSAGE 6710 (TAFF) 6710.0 THE %1 INPUT PARAMETER TO MODULE TAFF REFERENCES AN UNDEFINED LO AD SET ID. *** SYSTEM FATAL MESSAGE 6710 (KFRFC) 6710.1 AN UNDEFINED LOAD SET ID %1 HAS BEEN INPUT TO SUBROUTINE %2 . This message may be generated by the subroutine KFRFC when the case control LOAD card references only SPCD cards. If this is the case, this message can be ignored as there are no follower forces associated with SPCD loading. *** SYSTEM WARNING MESSAGE 6711 (TAFF) 6711.0 THE INTERNAL ELEMENT ID = %1 EXCEEDS THE UP PER LIMIT DEFINED BY SYSTEM CELL(183). *** SYSTEM FATAL MESSAGE 6712 (SBUT7) 6712.0 TOTAL NUMBER OF BIC RECORDS TO BE WRITTEN ON SCRATCH (NRCA+NRCU = %1) IS LARGER THAN MAXIMUM NUMBER ALLOWED (MAXBLK = %2). USER ACTION: INCREASE MEMORY SIGNIFICAN TLY. *** SYSTEM FATAL MESSAGE 6713 (SBUT7) 6713.0 THE MATRIX NEEDS TO BE UPDATED AT THIS STAGE, HOWEVER, THE BIC RECORD NUMBER TO BE READ (NBLOCK = %1) IS GREATER THAN THE NUMBER OF BIC RECORDS IN THE MATRIX (NRECA = %2). USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6713 (SBUT33) 6713.1 ERROR IN WRITING TO MATRIX SCRATCH FILE (ISTAT = %1). BLOCK %2 DOES NOT BELONG TO MATRIX WHICH HAS ONLY %3 BLOCKS. USER ACTION: PLEAS E CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6713 (SBUT33) 6713.2 ERROR IN WRITING TO FACTOR SCRATCH FILE (ISTAT = %1). BLOCK %2 DOES NOT BELONG TO FACTOR. FACTOR BLOCKS SHOULD BE IN THE RANGE %3 TO %4. USER ACTION: P LEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6713 (SBUT34) 6713.3 ERROR IN READING FROM MATRIX SCRATCH FILE (ISTAT = %1). BLOCK %2 DOES NOT BELONG TO MATRIX WHICH HAS ONLY %3 BLOCKS.

481 USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6713 (SBUT34) 6713.4 ERROR IN READING FROM FACTOR SCRATCH FILE (ISTAT = %1). BLOCK %2 DOES NOT BELONG TO FACTOR. %4. FACTOR BLOCKS SHOULD BE IN THE RANGE %3 TO USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6713 (SBUT34) 6713.5 ERROR IN SPILL LOGIC WHILE READING FROM FACTOR SCRATCH FILE (ISTAT = %1). BLOCK %2 SHOULD BE IN MEMORY THE FIRST SPILLED BLOCK IS %3. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6713 (SBUT34) 6713.6 | ERROR IN SPILL LOGIC WHILE READING FROM MATRIX SCRATCH FILE (ISTAT = %1). BLOCK %2 SHOUL D | BE IN MEMORY THE FIRST SPILLED BLOCK IS %3. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 6714 (FA1) 6714.0 FLUTTER ENTRY ID = %1 WITH METHOD = PKNL REFERENCES FLFACT ENTRIES WHICH DO NOT HAVE THE S AME NUMBER OF DENSITY RATIOS, MACH NUMBERS AND VELOCITIES *** USER FATAL MESSAGE 6714 (dopr3b) 6714.1 dresp1 entry = %1 WITH METHOD = PKNL REFERENCES FLFACT ENTRIES WHICH DO NOT HAVE THE SAME NUMBER OF DENSITY RATIOS, MACH NUMBERS AND VELOCITIES *** SYSTEM WARNING MESSAGE 6715 6715.0 THERE IS A ZERO DIAGONAL TERM IN COLUMN %1 OF DATA BLOCK %2 WHICH WILL BE REPLACED BY 1.0 IN THE PRECONDITIONER. USER ACTION: IT MAY BE BETTER TO USE CHOLESKY PRECONDITIONING (PRECOND=C ON ITER BULK DATA ENT RY) OR THE DIRECT SOLVER (ITER=NO ON NASTRAN STATEMENT) FOR THIS PROBLEM. *** SYSTEM FATAL MESSAGE 6715 6715.2 THERE IS A ZERO DIAGONAL TERM IN COLUMN %1 OF DATA BLOCK %2. USER ACTION: THE CONJUGATE GRADIENT METHOD CANNOT BE USED FOR THIS PROBLEM . USE THE DIRECT METHOD BY SPECIFYING ITER=NO ON THE NASTRAN STATEMENT. *** SYSTEM WARNING MESSAGE 6715 6715.4

482 THERE IS A ZERO DIAGONAL TERM IN COLUMN %1 OF DATA BLOCK %2 WHICH WILL BE REPLACED BY 1.0 IN THE PRECONDITIONER. USER ACTION: IT MAY BE BETTER TO USE CHOLESKY PRECONDITIONING (PRECOND=C ON ITER BULK DATA ENTRY) OR THE DIRECT SOLVER (ITER=NO ON NASTRAN STATEMENT) FOR THIS PROBLEM. *** USER FATAL MESSAGE 6715 6715.6 THERE IS NO DYNAMIC VISCOSITY SPECIFIED ON T HE MAT4 ENTRY FOR CONVM ELEMENT %1. USER INFORMATION: FORCED CONVECTION ELEMENTS REQUIRE SPECIFICATION OF DYNAMIC VISCOSITY ON A MAT4 ENTRY IF ON THE PCONVM ENTRY THE REYNOLDS NUMBER CONVECTION EXPONENT IS GREATER THAN THE PRANDTL NUMBER CONVECTION EXPO NENT. *** USER FATAL MESSAGE 6716 (NCNVMD) 6716.0 THERE IS NO THERMAL CONDUCTIVITY SPECIFIED ON THE MAT4 ENTRY FOR CONVM ELEMENT %1. USER INFORMATION: FORCED CONVECTION ELEMENTS REQUIRE CONDUCTIVITY ON A MAT4 ENTRY IF ON THE PCONVM ENTRY THE PRAN DTL NUMBER CONVECTION EXPONENT IS GREATER THAN ZERO IF FORM=0 AND GREATER THAN ONE IF FORM=1 . *** SYSTEM FATAL MESSAGE 6718 (FRSAD5) 6718.0 READ ERROR ON MERGED INDEX FILE %1 *** SYSTEM FATAL MESSAGE 6719 6719.0 MATRICES HAVE DIFFERING NUMBERS OF COLUMNS: [A] = %1 x %2 [B] = %3 x %4 [C] = %5 x %6 [D] = %7 x %8 *** SYSTEM FATAL MESSAGE 6719 6719.1 MATRICES HAVE DIFFERING NUMBERS OF ROWS: [A] = %1 x %2 [B] = %3 x %4 [C] = %5 x %6 [D] = %7 x %8 *** USER WARNING MESSAGE 6720 (REIGL) 6720.0 FOR LANCZOS EIGENVALUE ANALYSIS, THERE IS AN INCORRECT RELATIONSHIP BETWEEN SEGMENT BOUNDARIES. A HEURISTIC DISTRIBUTION WILL BE USED. *** USER FATAL MESSAGE 6721 (XSBFF) 6721.0 THE BULK DATA ENTRY FOLLOWIN G CONTAINS BOTH ENTRY DUPLICATOR AND FIELD REPLICATOR INFORMATION. USER INFORMATION: BULK ENTRY: %1 THE REPLICATOR INFORMATION ON THIS ENTRY IS IGNORED AND EXISTING REPLICATOR INFORMATION, IF ANY, HAS BEEN RESET IN ORDER TO RUN THE JOB, EITHER:

483 A. SP ECIFY NASTRAN MESH IN THE FILE MANAGEMENT SECTION B. REPLACE THE ENTRY WITH TWO ENTRIES: THE FIRST ENTRY CONTAINS REPLICATOR FIELDS, AND THE SECOND ENTRY CONTAINS THE ENTRY DUPLICATOR. *** USER WARNING MESSAGE 6722 (EPLDXD) 6722.0 THE DIRECTION V ECTOR OF PLOADX1 LOADING TYPE IS NOT NORMAL TO SURFACE. USER INFORMATION : FOLLOWER FORCE STIFFNESS DOES NOT INCLUDE THE EFFECTS OF THE COMPONENT TANGENTIAL TO THE SURFACE. *** USER WARNING MESSAGE 6722 (EPLDE) 6722.1 THE DIRECTION VECTOR OF PLOADE1 LOADING TYPE IS NOT NORMAL TO SURFACE. USER INFORMATION : FOLLOWER FORCE STIFFNESS DOES NOT INCLUDE THE EFFECTS OF THE COMPONENT TANGENTIAL TO THE SURFACE. *** SYSTEM FATAL MESSAGE 6723 6723.0 POSITIVE DIAGONAL ELEMENT IN SCALAR ROW %1 NON - USER ACTION: INCREASE IPAD VALUE ON BULK DATA ENTRY ITER. *** USER FATAL MESSAGE 6723 6723.1 NON - POSITIVE DIAGONAL ELEMENT IN SCALAR ROW %1 USER ACTION: INCREASE IPAD VALUE ON BULK DATA CARD ITER. *** USER FATAL MESSAGE 6724 6724.0 TOO MANY RESTARTS. USER ACTION: INCREASE IPAD VALUE ON BULK DATA CARD ITER. *** SYSTEM FATAL MESSAGE 6724 6724.1 TOO MANY RESTARTS. USER ACTION: INCREASE IPAD VALUE ON BULK DATA ENTRY ITER. * ** USER INFORMATION MESSAGE 6725 (SB2RM) 6725.0 NEGATIVE PIVOTING TERM IN SCALAR ROW %1. IC - PRECONDITIONING HAS BEEN RESTARTED. *** SYSTEM INFORMATION MESSAGE 6726 6726.0 INTERNAL ITERATIVE LOOP DOES NOT CONVERGE. USER ACTION: INCREASE VALUE OF IPAD PARAMETER. *** SYSTEM FATAL MESSAGE 6727 (SB50CD) 6727.0 INCOMPATIBLE DISTRIBUTION OF THE LEFT STACK. *** SYSTEM FATAL MESSAGE 6728 (SB51RD) 6728.0 ZERO PIVOTING ELEMENT IN ROW %1. *** SYSTEM FATAL MESSAGE 6731 (SPCGRD) 6731.0

484 ZERO DIAGONAL TERM IN ROW %1. ***USER WARNING MESSAGE 6731 6731.1 ROW%1 OF LOWER TRIANGULAR FACTOR HAS DIAGONAL TERM = 0( OR .LT. 0 IF CHOLESKY ) *** SYSTEM FATAL MESSAGE 6732 6732.0 ZERO DIAGONAL ELEMENT IN SCALAR ROW %1 . *** SYSTEM FATAL MESSAGE 6733 (SBUT14) 6733.0 EMPTY MINIMUM DEGREE=2. *** SYSTEM FATAL MESSAGE 6734 (SBUT14) 6734.0 INVALID DEGREE = %1 OF NODE %2 FROM DEGREE 2 QUEUE. *** SYSTEM FATAL MESSAGE 6735 (SBUT14) 6735.0 INCONSISTENCY: LAST ELEMENT OF DEGREE %1 IS %2, WHILE %3 HAS NO SUBSEQUENT NODES. *** SYSTEM FATAL MESSAGE 6736 (SBUT14) 6736.0 INCONSISTENCY: FIRST ELEMENT OF DEGREE %1 IS %2, WHILE %3 HAS NO PRECEDENT NODES. *** SYSTEM FATAL MESSAGE 6737 (SBUT14) 6737.0 INCONSISTENT DEGREE %1 *** SYSTEM FATAL MESSAGE 6738 (SBUT14) 6738.0 INCONSISTENT FIRST NODE %1 OF DEGREE %2 *** SYSTEM FATAL MESSAGE 6739 (SBUT14) 6739.0 INVALID NODE IMIND = %1 (K = %2) - %4 (%5 NODES) SEARCHED LEVEL RANGE IS %3 DEPTH %6 MINIMUM DEGREE %7 NUM. UNORDERED %8 *** SYSTEM FATAL MESSAGE 6740 (SBUT7) 6740.0 ERROR WHILE READING BIC RECORD %1 FROM SCRATCH FILE %2. INSTEAD OF THE REQUESTED %3 WORDS, ONLY %4 WERE READ. *** SYSTEM FATAL MESSAGE 6740 (SBUT34) 6740.1 ERROR WHILE READING BIC RECORD %1 FROM SCRATCH FILE %2. END OF FILE WAS ENCOUNTERED BY THIS READ OPERATION. *** SYSTEM FATAL MESSAGE 6741 (SBUT18) 6741.0 NEGATIVE LENGTH OF OPEN CORE ARRAY: %1 USER ACTION: INCREASE MEMORY. *** SYSTEM FATAL MESSAGE 6742 (SBUT2) 6742.0 INVALID INPUT VECTOR LFRAGM. *** SYSTEM FATAL MESSAGE 6743 (SBUT2) 6743.0 INPUT DESCRIPTOR CONTAINS AN ERROR.

485 *** SYSTEM FATAL MESSAGE 6744 (SBUT3) 6744.0 INCONSISTENCY IN INPUT DATA: MATRIX DIMENSION IS %1 BY DESCRIPTOR AND %2 BY MATRIX TRAILER. *** SYSTEM FATAL MESSAGE 6745 (SBUT3): 6745.0 INVALID INPUT DESCRIPTOR TYPE. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6746 (SBUT6) 6746.0 SCALAR MODE IS NOT VALID FOR COMPLEX PROBLEMS. *** SYSTEM FATAL MESSAGE 6747 (SBUT6) 6747.0 - OF - CORE BRANCH. GRF11F IS NOT ERROR IN SYMBOLIC OUT AVAILABLE. WARE USER ACTION: PLEASE CONTACT SIEMENS PLM SOFT CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6748 (SBUT6) 6748.0 - OF - CORE BRANCH. GRF13F IS NOT ERROR IN SYMBOLIC OUT AVAILABLE. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 6749 (GECINT) 6749.0 THE GMINTC ELEMENT ID = %1 ONLY CONNECTS GMBNDC BOUNDARY ID = %2. *** USER FATAL MESSAGE 6749 (GESINT) 6749.1 THE GMINTS ELEMENT ID = %1 ONLY CONNECTS GMBNDC BOUNDARY ID = %2. *** USER FATAL MESSAGE 6750 (GECINT) 6750.0 THE GMINTC ELEMENT ID = %1 CONNECTS GMBNDC BOUNDARY ID = %2 TO ITSELF. *** USER FATAL MESSAGE 6750 (GESINT) 6750.1 THE GMINTS ELEMENT ID = %1 CONNECTS GMBNDC BOUNDARY ID = %2 TO ITSELF. *** USER WARNING MESSAGE 6751 (GP4RS3) 6751.0 FIELDS %1 ON RSSCON BULK DATA ENTRY ID %2 DUPLICATE FIELDS ON A PREVIOUS ENTRY. THESE FIELDS WILL BE IGNORED. *** USER INFORMATION MESSAGE 6752 (GP4RS3) 6752.0 THE ROTATIONAL CONSTRAINTS FOR SHELL GRID POINTS %1 AND %2 WILL BE AVERAGED BECAUSE SOLID GRID POINT %3 IS SPECIFIED MORE THAN ONCE ON RSSCON BULK DATA ENTRIES. *** USER FATAL MESSAGE 6753 (EINPED) 6753.0 THE DIRECTION FROM THE INITIAL TO THE FINA L GRID OF GMBNDC BOUNDARY ID = %1 IS OPPOSITE THE DIRECTION

486 OF GMINTC ELEMENT ID = %2. *** USER FATAL MESSAGE 6754 (GP1C) 6754.0 NO GRID POINTS DEFINED FOR CORD1I ENTRIES IN SUPERELEMENT %1 *** USER FATAL MESSAGE 6755 (SEP1X) 6755.0 CERTAIN SUPERELEMENT RELATED BULK DATA ENTRIES MAY NOT APPEAR IN MAIN BULK DATA SECTION. USER INFORMATION: ONE OR MORE OF THE FOLLOWING ENTRIES APPEAR IN THE MAIN BULK DATA SECTION. %1 %2 %3 %4 %5 %6 *** USER FATAL MESSAGE 6755 (IFPVAL) 6755.1 1 SUPERELEMENT RELATED BULK DATA ENTRIES MAY NOT % APPEAR IN %2 BULK DATA SECTIONS. USER INFORMATION: ONE OR MORE OF THE FOLLOWING %3 BULK DATA ENTRIES APPEAR IN THE %4 BULK DATA SECTION: WITH SEID = %5 *** SYSTEM FATAL MESSAGE 6756 (SEP1X) 6756.0 THE MAXIMUM NUMBER OF SUPERELEMENTS IS LIMITED TO 32767, WHICH HAS BEEN EXCEEDED. *** USER FATAL MESSAGE 6757 (SEP1X) 6757.0 SUPERELEMENTS ARE DEFINED BUT NO BOUNDARY POINTS WERE DETECTED BETWEEN THE SUPERELEMENTS. *** USER FATAL MESSAGE 6758 (SEPRSC) 6758.0 GRID POINT %1 IS REFERENCED ON THE EXTERN ENTRY BUT IS NOT CONNECTED TO THE DOWNSTREAM SUPERELEMENT. *** USER WARNING MESSAGE 6758 (SEPEXT) 6758.1 THE FOLLOWING GRID OR SCALAR POINTS ARE REFERENCED ON K DATA ENTRY FOR SUPERELEMENT %1 THE EXTRN BUL BUT ARE NOT CONNECTED TO THE DOWNSTREAM SUPERELEMENT. *** USER FATAL MESSAGE 6759 (SEP2MP) 6759.0 SCALAR POINT %1 IS SPECIFIED WITH A NONZERO DEGREE OF FREEDOM ON THE EXTERN ENTRY. *** USER FATAL MESSAGE 6760 (SEP2MP) 6760.0 EXTRN GRID %1 NOT LOCATED AS PART OF THE SUPERELEMENT BOUNDARY. *** SYSTEM FATAL MESSAGE 6761 (SEP2X) 6761.0 SUPERELEMENT %1 CAN NOT BE FOUND IN THE SEMAP. *** SYSTEM FATAL MESSAGE 6762 (SEP2X) 6762.0 BOUNDARY %1(%2) NOT FOUND IN THE SEMAP RECORD 2. *** USER WARNING MESSAGE 6763 (SEPAQN) 6763.0

487 OMITi ENTRIES ARE SPECIFIED FOR SUPERELEMENT %1 USER INFORMATION: THE OMITi ENTRIES WILL BE IGNORED. *** USER FATAL MESSAGE 6764 (SEPAQN) 6764.0 THE VALUE SPECIFIED FOR USER PARAMETER NQSET - SET GENERATION) EXCEEDS THE MAXIMUM (AUTOMATIC Q ALLOWED PER SUPERELEMENT. *** USER FATAL MESSAGE 6765 (SEPAQN) 6765.0 - SET THE VALUE SPECIFIED FOR NQSET (AUTOMATIC Q GENERATION) ON THE SENQSET ENTRY EXCEEDS MAXIMUM ALLOWED PER SUPERELEMENT. *** USER WARNING MESSAGE 6766 (SEPBLK) 6766.0 THE SEBULK ENTRY FOR COLLECTOR SUPERELEMENT %1 ALSO REFERENCES A PRIMARY SUPERELEMENT. *** USER FATAL MESSAGE 6767 (SEPBLK) 6767.0 COLLECTOR SUPER ELEMENT %1 IS ALSO DEFINED AS A PRIMARY SUPERELEMENT VIA THE BEGIN SUPER, SESET, OR SEELT ENTRIES. *** USER FATAL MESSAGE 6768 (SEPBLK) 6768.0 THE SEBULK ENTRY FOR MIRROR SUPERELEMENT %1 DOES NOT REFERENCE A PRIMARY SUPERELEMENT. USER FATAL MESSAGE 6768 (SEPBLK) *** 6768.1 SEBULK ENTRY FOR EXTERNAL SUPERELEMENT %1 DOES NOT REFERENCE A PRIMARY SUPERELEMENT. *** USER FATAL MESSAGE 6768 (SEPBLK) 6768.2 THE SEBULK ENTRY FOR REPEATED SUPERELEMENT %1 DOES NOT REFERENCE A PRIMARY SUPERELEMENT. *** USER FATAL MESSAGE 6769 (SEPBLK) 6769.0 MIRRORED SUPERELEMENT %1 REFERENCES AN UNDEFINED PRIMARY SUPERELEMENT. *** USER FATAL MESSAGE 6769 (SEPBLK) 6769.1 REPEATED SUPERELEMENT %1 REFERENCES AN UNDEFINED PRIMARY SUPERELEME NT. *** USER FATAL MESSAGE 6770 (SEPBLK) 6770.0 MIRRORED SUPERELEMENT %1 REFERENCES AN UNDEFINED SEMPLN ENTRY. *** SYSTEM FATAL MESSAGE 6771 (SEPES3) 6771.0 MAIN BULK ELEMENT %1 DID NOT RESOLVE TO A SUPERELEMENT INDEX *** USER FATAL MESSAGE 6772 (SEPET1) 6772.0 SUPERELEMENT %1 IS DEFINED IN BOTH THE MAIN BULK DATA SECTION AND IN A PARTITIONED BULK DATA SECTION, OR IN A DBLOCATED SECTION.

488 *** USER FATAL MESSAGE 6773 (SEPET2) 6773.0 THE ELEMENT ID THRU RANGES ON THE SEELT ENTRIES OVERLAP BETWEEN SUPERELEMENT %1 GRID %2 AND SUPERELMENT %3 GRID %4. *** USER WARNING MESSAGE 6774 (SEPET3) 6774.0 ONE OR MORE ELEMENTS HAVE CONFLICTS BETWEEN GRID/SESET ENTRY SPECIFICATIONS, STARTIN G WITH %1 ELEMENT %2 REFERENCE GRID %3 *** USER FATAL MESSAGE 6775 (SEPLOC) 6775.0 THE SELOC ENTRY IS UNDEFINED FOR SUPERELEMENT %1 *** USER FATAL MESSAGE 6775 (SEPLOC) 6775.1 THE SEMPLN ENTRY IS UNDEFINED FOR SUPERELEMENT %1. *** USER FATAL MESSAGE 6776 (SEPLOC) 6776.0 BAD GEOMETRY ENCOUNTERED FOR SEMPLN ENTRY AND SUPERELEMENT %1 USER INFORMATION: RETURN CODE =%2. 1: GRID POINTS APPEAR TO BE COINCIDENT. 2: ATTACHMENT DOES NOT APPEAR TO BE CONGRUENT. 3: GRID POINTS APPEAR TO BE N OT COPLANAR. *** USER FATAL MESSAGE 6777 (SEPLOC) 6777.0 FOR SELOC ENTRY PROCESSING, GRID OR POINT %1 CANNOT BE FOUND FOR SUPERELEMENT %2. *** USER WARNING MESSAGE 6778 (SEPMA1) 6778.0 %1 ENTRY FOR SUPERELEMENT %2 CONFLICTS WITH MANUAL BOUNDARY CONNECTION SELECTION ON THE SEBULK ENTRY. *** USER WARNING MESSAGE 6779 (SEPMAB) 6779.0 THE SEID FIELD ON THE GRID ENTRIES IS SPECIFIED IN ED PARTITIONED ENTRIES SUBSTRUCTURE %1 WILL BE IGNOR *** USER FATAL MESSAGE 6780 (SEPSUP) 6780.0 INVALID METHOD SPECIFIED FOR SEARCH FOR OVER - RIDE PARAMETER. *** SYSTEM FATAL MESSAGE 6780 6780.1 FILE POSITIONING ERROR, MEMORY SEID %1 FILE SEID %2 USER FATAL MESSAGE 6781 (SEPMC1) *** 6781.0 SUPERELEMENT %1 REFERENCES ITSELF ON SECONCT ENTRY *** USER FATAL MESSAGE 6782 (SEPMC2) 6782.0 THE FOLLOWING GRIDS OR SCALAR POINTS SPECIFIED ON SECONCT ENTRIES COULD NOT BE LOCATED IN SUPERELEMENT %1 %2 *** USER FATAL MESSAGE 6783 (SEPMC2) 6783.0 THE SECONCT ENTRY SPECIFIED BETWEEN SUPERELEMENTS %1,

489 %2 AND GRIDS %3, %4 IS NOT WITHIN TOLERANCE. ACCEPTANCE TOLERANCE %5, GRID VECTOR TOLERANCE %6 *** USER FATAL MESSAGE 6784 (SEPMC2) 6784.0 SECONCT BETWEEN SUPERELEMENTS %1, %2 AND GRIDS %3, %4 ARE NOT OF THE SAME TYPE. *** USER FATAL MESSAGE 6785 (SEPMC3) 6785.0 THE SECONCT ENTRY SPECIFIES A CONFLICT BETWEEN SUPERELEMENT %1 GRID %2 AND SUPERELEMENT %3 GRIDS %4. SYSTEM FATAL MESSAGE 6786 (SEPMEP) *** 6786.0 SUPERELEMENT %1 DURING CONVERSION LOOP WAS NOT LOCATED IN MEMORY RESIDENT TABLE, LOGIC ERROR. *** USER FATAL MESSAGE 6787 (SEPMM2) 6787.0 GRID %1 IN SUPERELEMENT %2 IS SPECIFIED ON BOTH SEEXCLD S. AND SECONCT ENTRIE *** USER FATAL MESSAGE 6788 (SEPMM3) 6788.0 THE FOLLOWING GRID POINTS IN SUPERELEMENT %1 ARE SPECIFIED ON BOTH SEEXCLD AND SEBNDRY ENTRIES. *** USER FATAL MESSAGE 6788 (SEPMSF) 6788.1 SUPERELEMENT %1 GRID %2 AND SUPERELEMENT %3 GRID %4 HAVE CONFLICTING MANUAL DIRECTIVES. *** USER FATAL MESSAGE 6789 (SEPMQ1) 6789.0 GRID %1 REFERENCED IN %2 ENTRY IN SUPERELEMENT %3 USER INFORMATION: ONLY SCALAR POINTS MAY BE REFERENCED ON %4 ENTRIES *** USER FATAL MESSAGE 6790 (SEPO21) 6790.0 THE FOLLOWING SUPERELEMENTS ARE DETACHED: %1 %2 %3 %4 %5 %6 %7 %8 %9 %10 %11 %12 %13 %14 %15 %16

490 USER FATAL MESSAGE 6790 (SEPMQ1) *** 6790.1 GRID POINT %1 SPECIFIED ON %2 IS NOT DEFINED FOR SUPERELEMENT %3. *** SYSTEM FATAL MESSAGE 6791 (SEPO22) 6791.0 QSET %1 TO THE LOCAL SEMAP ALIGNMENT FAILURE FOR AUTO - MEMORY TABLE. *** USER WARNING MESSAGE 6792 (SEPOMT) 6792.0 THE PERMANENT SET CONSTRAINT SPECIFICATION FOR BOUNDARY GRID %1 IN SUPERELEMENT %2 IS DIFFERENT FROM THE UPSTREAM SUPERELEMENT. USER INFORMATION: THE PERMANENT SET CONSTRAINTS WILL BE UNIONED. FATAL MESSAGE 6793 (SEPRSC) *** SYSTEM 6793.0 THE GENERATION OF SUPERELEMENT BOUNDARY GRIDS IS COLLIDING WITH THE GENERATION OF Q - SET IDENTIFICATION NUMBERS. *** USER FATAL MESSAGE 6794 (SEPSEB) 6794.0 DUPLICATE BOUNDARY POINTS DETECTED CONNECTING TO SUPERELEMENT % 1 AT GRID %2 FROM DOWNSTREAM %3. LIST FOLLOWS: *** USER FATAL MESSAGE 6794 (SEPSEB) 6794.1 DUPLICATE BOUNDARY POINTS DETECTED IN UPSTREAM SUPERELEMENT %1 WHILE SEARCHING %2 AT GRID %3. LIST FOLLOWS: SYSTEM WARNING MESSAGE 6795 (SEPSEB) *** 6795.0 NO BOUNDARY GRID POINTS WERE FOUND FOR SUPERELEMENT %1 *** USER WARNING MESSAGE 6796 (SEPSEQ) 6796.0 %1 ENTRY FOR GRID %2 IN SUPERELEMENT %3 CONFLICTS WITH SESET/GRID ENTRIES. *** USER WARNING MESSAGE 6797 (SEPSET) 6797.0 NO GRID POINTS SPECIFIED ON SESET ENTRIES FOR SUPERELEMENT %1 CAN BE FOUND. *** USER WARNING MESSAGE 6798 (SEPTRE) 6798.0 BOTH DTI,SETREE AND SETREE ENTRIES ARE SPECIFIED. USER INFORMATION: THE DTI,SETREE ENTRY WILL BE IGNORED. *** USER FATAL MESSAGE 6800 (SEPTRE) 6800.0 SUPERELEMENT %1 DEFINED IN MAIN BULK DATA SECTION IS UPSTREAM OF PARTITIONED BULK DATA SUPERELEMENT %2 *** USER WARNING MESSAGE 6801 (SEPTRE) 6801.0 ERRORS ENCOUNTERED IN THE SETREE, OR DTI,SETREE ENTRY. USER INFORMATION: A SINGLE LEVEL TREE WILL BE ASSUMED.

491 *** SYSTEM FATAL MESSAGE 6802 (SEPSUP) 6802.0 SUPERELEMENT %1 HAS FAILED TO AUTOMATICALLY DERIVE A SEARCH KEY. FOR REASONABLE GEOMETRY USER ACTION: REVIEW MODEL - RIDE PARAMETER AND/OR AND SELECT SEARCH KEY VIA OVER REVIEW GRID POINT LOCATIONS FOR REASONABLE GEOMETRY *** USER FATAL MESSAGE 6803 (BNDSP3) 6803.0 ENFORCED DISPLACEMENTS ON SUPERELEMENT BOUNDARY POINTS ARE DETECTED AND S HOWN IN THE TABLE BELOW. USER ACTION: MOVE THOSE SPCD OR SPC ENTRIES THAT ARE APPLIED ON BOUNDARY POINTS TO THE BULK DATA SECTION OF THE DOWNSTREAM SUPERELEMENT. *** SYSTEM FATAL MESSAGE 6804 (BNDSP3) 6804.0 THE DISPLACEMENT COORDINATE SYSTEM (CD FIELD ON GRID ENTRY) SPECIFIED FOR BOUNDARY GRID ID %1 B IN SUPERELEMENT %2 IS NOT CONGRUENT WITH DISPLACEMENT COORDINATE SYSTEMS IN OTHER CONNECTING SUPERELEMENTS. *** USER FATAL MESSAGE 6805 (BNDSP4) 6805.0 BOUNDARY GRID ID = %1 B AND COMPONENT = %2 IS SPECIFIED ON AN SPCI ENTRY IN MORE THAN ONE SUPERELEMENT. USER INFORMATION: THE COMPONENTS OF BOUNDARY GRID POINTS CAN ONLY BE SPECIFIED ONCE ON SPCI ENTRIES. ) *** USER FATAL MESSAGE 6805 (BNDSP4 6805.1 BOUNDARY GRID ID = %1 B IS SPECIFIED ON AN SPCI ENTRY IN MORE THAN ONE SUPERELEMENT. USER INFORMATION: THE BOUNDARY GRID POINTS CAN ONLY BE SPECIFIED ONCE ON SPCI ENTRIES. *** SYSTEM FATAL MESSAGE 6806 (CURV) 6806.0 RETURNED ERROR CONDITION %1, LOC CODE = %2, IN SUBROUTINE CURV%3, FILE NUM = %4 (NOTE ADDITIONAL MESSAGES.) *** USER WARNING MESSAGE 6807 (CURVIT) 6807.0 LOCAL INTERPOLATION USING INDEPENDENT VALUES WITHIN RANGE OF THE %1 - TH SORTED ORDER INVOLVED WITH RESPECT TO MATERIAL COORDINATE GRID ID SYSTEM ID = %2 CAN NOT BE COMPLETED. ILL - CONDITION MAY HAVE RESULTED FROM ALIGNMENT OF INDEPENDENT VALUE COORDINATES. OUTPUT FOR THE GRID ID IN QUESTION WILL NOT APPEAR. *** USER WARNING MESSAGE 6808 (TAFEST) 6808.0 METHOD %1 IS SPECIFIED ON THE RFORCE %2 BULK DATA ENTRY FOLLOWER FORCE EFFECTS ARE NOT COMPUTED FOR METHOD

492 %1. USER ACTION : SPECIFY METHOD=2 ON THE RFORCE ENTRY. *** USER FATAL MESSAGE 6809 (DOPR1I) 6809.0 REL%1 ENTRY %2 REFERENCES A DESIGN VARIABLE FOR A DVP TAPERED BEAM BUT ONLY ONE END IS SPECIFIED ON THE REFERENCED PBEAM ENTRY. USER ACTION: SPECIFY BOTH ENDS A AND B ON THE PBEAM ENTRY FOR A TAPERED BEAM. *** SYSTEM WARNING MESSAGE 6810 (WRTTR L) 6810.0 ATTEMPT TO WRITE MATRIX TRAILER ON %1 WITH TRAILER WORD 7 GREATER THAN MBIT= %2. PROGRAMMER INFORMATION: THE TRAILER WORD 7 NEEDS TO BE INITIALIZED TO ZERO AND NOT MBIT TO HAVE THE DENSITY AUTOMATICALLY COMPUTED. *** USER FATAL MESSAGE 6813 (A?) 6813.0 FUNCTION NAME '%1' HAS BEEN USED ON BOTH SIDES OF THE SAME EQUAL SIGN *** SYSTEM FATAL MESSAGE 6814 (SBSYM2) 6814.0 REPEATED INDEX %1 AT FULL ROW %2 (NEW %3), 2ND PART. *** SYSTEM FATAL MESSAGE 6814 (SBSY M2) 6814.1 REPEATED INDEX %1 AT FULL ROW %2 (NEW %3), 1ST PART. *** SYSTEM FATAL MESSAGE 6814 (SBSYM1) 6814.2 REPEATED INDEX %1 AT FULL ROW %2 (NEW %3), 2ND PART. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6814 (SBSYM1) 6814.3 REPEATED INDEX %1 AT FULL ROW %2 (NEW %3), 1ST PART. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6815 (SBSYM2) 6815.0 FINAL MF = %1 # %2. SYSTEM FATAL MESSAGE 6816 (SBSYM5) *** 6816.0 CRITICAL AMOUNT OF FREE SPACE AT THE BEGINNING OF PROCESSING ROW %1. *** SYSTEM FATAL MESSAGE 6817 (SBSYM2) 6817.0 ROW INDEX = %1 IS OUT OF RANGE, L = %2, IL=LBLEN+%3. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6818 6818.0 INCORRECT PERMUTATION VECTOR (DOUBLE - REFERENCE). USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT.

493 SYSTEM FATAL MESSAGE 6818 *** 6818.1 - REFERENCE). INCORRECT PERMUTATION VECTOR (OUT USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6818 (SBSYM6) 6818.2 INVALID PERMUTATION PROCEDURE, B=%1 < L=%2. USER ACTION: PLE ASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6818 6818.5 INCORRECT STRUCTURE OF THE PERMUTATION VECTOR. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. SYSTEM FATAL MESSAGE 6818 (SBSYM3) *** 6818.8 INVALID PERMUTATION PROCEDURE, B=%1 < L=%2. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6819 (SBSYM6) 6819.0 SPECIFIED BUFFER LENGTH = %1 IS TOO SMALL FOR A SINGLE ROW OF FACTOR MATRIX (NEEDS %2 WORDS). USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6819 (SBSYM6) 6819.1 SPECIFIED BUFFER LENGTH = %1 IS TOO SMALL FOR A SINGLE ROW OF INPUT MATRIX (NEEDS %2 WORDS). USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6820 (SBSYM6) 6820.0 INCORRECT STORAGE OF INFORMATION ABOUT RECORDS OF FACTOR FILE: L = %1, NRECU = %2. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6821 (SBSYM6) 6821.0 THE LIST IS TOO LONG AT RECORD %1. THE OVERLAP IS %2 WORDS. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 6822 (SBSYM5) 22.0 68 EMPTY DIAGONAL BLOCK IN ROW %1. *** SYSTEM FATAL MESSAGE 6823 (SBMEM) 6823.0 INSUFFICIENT MEMORY IN SYMBOLIC PHASE OF ITERATIVE SOLVER. USER ACTION: INCREASE MEMORY BY AT LEAST %1 K WORDS. *** USER WARNING MESSAGE 6824 (SITDRV) 6824.0

494 REDUCED INCOMPLETE CHOLESKY (RIC) PRECONDITIONING FOR MODELS WITH MULTI POINT CONSTRAINTS WAS - REQUESTED FOR THE ITERATIVE SOLVER. USER ACTION: FOR FASTER CONVERGENCE INCLUDE THE ITRICA.V69 ALTER FROM THE SSSALTE R LIBRARY. *** USER FATAL MESSAGE 6825 (DPD6) 6825.0 ACOUSTIC GRID POINT, ID= %1 ON A YOU HAVE SPECIFIED A NON - DAREA ENTRY ID = %2 WHICH IS SPECIFIED ON AN ACSRCE ENTRY. THE DAREA ENTRY MAY HAVE BEEN GENERATED AUTOMATICALLY FROM AN LSEQ ENTRY. *** USER FATAL MESSAGE 6826 (PLOD4D) 6826.0 ELEMENT ID = %1 CID =%2 N1, N2, N3 =%3 LOAD DIRECTION VECTOR WHEN TRANSFORMED TO BASIC COORDINATES AT A GAUSS POINT HAS A ZERO LENGTH. *** USER FATAL MESSAGE 6827 (TAFEST) 6827.0 %1,HAS A GRID POINT OPPOSITE TO THOSE ELEMENT WITH ID = OF A FACE RECEIVING A PRESSURE LOAD, WHICH IS EVIDENTLY IN THE SAME PLANE AS THIS FACE. *** USER WARNING MESSAGE 6828 (ETETD) 6828.0 THE FACES OF CTETRA ELEMENT ID=%1 ARE INTERSECTING BETWEEN THE ELEMENT'S EDGES DUE TO BAD MIDSIDE NODE LOCATIONS. USER ACTION: CORRECT THE ELEMENT'S GEOMETRY IF HIGH GRADIENTS ARE EXPECTED. USER INFORMATION: JACOBIAN AT A GRID ID=%2 IS NEGATIVE. *** SYSTEM WARNING MESSAGE 6829 (UDSFB) 6829.0 UNSYMMETRIC FACTOR TRAILE R INFORMATION IS INCORRECT. THIS MAY LEAD TO POOR PERFORMANCE IN THE MCE1 MODULE *** SYSTEM FATAL MESSAGE 6830 (%1) 6830.0 THE FIRST INPUT MATRIX IS NOT SQUARE. *** SYSTEMS FATAL MESSAGE 6831 6831.0 INTERNAL LOGIC ERROR. INVALID VARIABLE STORE CODE SUPPLIED USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: LCODE VALUE = %1 *** SYSTEMS FATAL MESSAGE 6831 (XQALVL) 6831.1 INTERNAL LOGIC ERROR. INVALID VARIABLE LOAD CODE SUPPLIED USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. PROGRAMMER INFORMATION: LCODE VALUE = %1

495 *** SYSTEMS FATAL MESSAGE 6831 (XQAERR) 6831.2 INTERNAL LOGIC ERROR. INVALID INTERNAL ERROR %1 NUMBER SUPPLIED ONTACT SIEMENS PLM SOFTWARE CUSTOMER USER ACTION: C SUPPORT. PROGRAMMER INFORMATION: %2 VALUE = %3 *** SYSTEM INFORMATION MESSAGE 6832 (DBFBS) 6832.0 LOCAL PARAMETERS AND TIMINGS FOR THE DISTRIBUTED PARALLEL FBS LOCAL MEMORY AVAILABLE =%1 K WORDS LOCAL MEMORY USED =%2 K WORDS NUMBER OF GIVEN RHS(S) =%3 NUMBER OF SOLVED RHS(S) =%4 NUMBER OF PROCESSORS =%5 TREE SCAN CPU TIME =%6 SECONDS TREE SCAN ELAPSED TIME =%7 SECONDS SCAT. RHS CPU TIME =%8 SECONDS SCAT. RHS ELAPSED TIME =%9 SECONDS FORWARD PASS CPU TIME =%10 SECONDS FORWARD PASS ELAPSED TIME =%11 SECONDS BACKWARD PASS CPU TIME =%12 SECONDS BACKWD. PASS ELAPSED TIME =%13 SECONDS COLL. PHASE CPU TIME =%14 SECONDS COLL. PHASE ELAPSED TIME =%15 SECONDS TOTAL CPU TIME =%16 SECONDS TOTAL ELAPSED TIME =%17 SECONDS *** SYSTEM INFORMATION MESSAGE 6889 (PNPERF) 6889.0 RESULTS OF THE DISTRIBUTED PARALLEL METHOD PERFORMANCE TESTS REQUESTED BY NASTRAN SYSTEM(166)=1024 FOLLOW. *** SYSTEM INFORMATIO N MESSAGE 6890 (PDDRV) 6890.0 ADDITIONAL DIAGNOSTIC INFORMATION FOR DISTRIBUTED PARALLEL SPARSE DECOMPOSITION REQUESTED BY NASTRAN SYSTEM(166)=%1. *** SYSTEM FATAL MESSAGE 6891 (SITDR3) 6891.0 ILLEGAL VALUE FOR THE REGULARIZATION PARAMETER: %1. USER ACTION: SYSTEM(241) ON THE NASTRAN ENTRY NEEDS TO HAVE ONE OF THE FOLLOWING VALUES: 0, [ - 1050, - 1009] OR [1009,1050]. PLEASE MODIFY THE DATA DECK. *** USER FATAL MESSAGE 6892 (SEPMEP) 6892.0 RSSCON ENTRY %1 REFERENCES ELEMENTS SPECIFIED IN TWO DIFFERENT SUPERELEMENTS. ELEMENT %2 IS DEFINED IN SUPERELEMENT %3 AND ELEMENT %4 IN SUPERELEMENT %5. USER ACTION: SPECIFY AN SEELT ENTRY TO PLACE ELEMENTS IN A SINGLE SUPERELEMENT.

496 *** USER FATAL MESSAGE 6893 (SEPPGD) 6893.0 UPERELEMENT (SUPER=%1) BULK DATA IN THE PARTITIONED S SECTION GRID POINT ID=%2 IS REFERENCED ON A RSSCON ID=%3 AND ALSO ON A %4 ENTRY. THE GRID POINT WILL HAVE TO BE MOVED TO SATISFY RIGID BODY REQUIREMENTS. USER ACTION: REPLACE THE CORD1_ ENTRY WITH A CORD2_ ENTRY OR CREAT E A COINCIDENT GRID ENTRY AND REFERENCE ITS ID ON THE CORD1_ ENTRY. *** USER FATAL MESSAGE 6893 (SEPPGD) 6893.1 IN THE MAIN BULK DATA SECTION GRID POINT ID=%1 IS REFERENCED ON A RSSCON ID=%2 AND ALSO ON A %3 ENTRY. THE GRID POINT WILL HAVE TO BE MOVED TO SATISFY RIGID BODY REQUIREMENTS. USER ACTION: REPLACE THE CORD1_ ENTRY WITH A CORD2_ ENTRY OR CREATE A COINCIDENT GRID ENTRY AND REFERENCE ITS ID ON THE CORD1_ ENTRY. *** USER FATAL MESSAGE 6893 (SEPPGD) 2 6893. IN THE PARTITIONED SUPERELEMENT (SUPER=%1) BULK DATA SECTION GRID POINT ID=%2 IS REFERENCED ON A RSSCON ID=%3 AND ALSO ON A %4 ENTRY. THE GRID POINT WILL HAVE TO BE MOVED TO SATISFY RIGID BODY REQUIREMENTS. USER ACTION: CREATE A COINCIDENT POINT ENTRY AND REFERENCE ITS ID ON THE %5 ENTRY. *** USER FATAL MESSAGE 6893 (SEPPGD) 6893.3 IN THE MAIN BULK DATA SECTION GRID POINT ID=%1 IS REFERENCED ON A RSSCON ID=%2 AND ALSO ON A %3 ENTRY. THE GRID POINT WILL VE TO BE MOVED TO SATISFY RIGID BODY REQUIREMENTS. HA USER ACTION: CREATE A COINCIDENT POINT ENTRY AND REFERENCE ITS ID ON THE %4 ENTRY. *** USER FATAL MESSAGE 6894 (SEPEXT) 6894.0 FOR EXTERNAL SUPERELEMENT ID=%1, SCALAR POINT ID=%2 HAS AN ILLEGAL COMPONENT DESIGNATED ON THE EXTRN BULK DATA ENTRY. *** USER FATAL MESSAGE 6895 (SEPEXT) 6895.0 GRID OR SCALAR POINT ID=%1 REFERENCED ON THE EXTRN EXTERNAL SUPERELEMENT ID=%2 BULK DATA ENTRY FOR IS NOT DEFINED BY A GRID OR SPOINT BULK DATA ENTRY. *** SYSTEM INFORMATION MESSAGE 6902 (SQFREQ) 6902.0 DISTRIBUTED MEMORY PARALLEL FREQUENCY RESPONSE NUMBER OF FREQUENCY DOMAINS = %1 NUMBER OF FREQUENCIES ON LOCAL PR OCESSOR (ID=%2) = %3

497 *** SYSTEM INFORMATION MESSAGE 6902 (DPERFM) 6902.1 PERFORMANCE SUMMARY TABLE FOR DISTRIBUTED MEMORY FREQUENCY RESPONSE NUMBER OF FREQUENCY DOMAINS = %1 NUMBER OF FREQUENCIES = %2 PROCESSOR # FREQ. CPU (SEC) ELAPSED (SEC) ------- --------- --------- ------------- *** SYSTEM FATAL MESSAGE 6903 (SEDR) 6903.0 - ELEMENT ANALYSIS. MIRROR IMAGES ARE NOT SUPPORTED IN P *** SYSTEM FATAL MESSAGE 6904 (SEP4) 6904.0 LOGIC ERROR%1 *** SYSTEM FATAL MESSAGE 6905 (SEMA) 6905.0 ALL UPSTREAM SUPERELEMENTS HAVE BEEN EXCLUDED FROM ASSEMBLY IN SUPERELEMENT %1 *** SYSTEM WARNING MESSAGE 6907 (SEP4) 6907.0 CASECC REFERENCES UNDEFINED SUPERELEMENT%1. RECORD IS IGNORED. *** USER WARNING MESSAGE 6907 (SEP4) 6907.1 %1 REQUEST REFERENCES UNDEFINED SUPERELEMENT%2 *** USER FATAL MESSAGE 6907 (SEP3) 6907.2 - TYPE COMMAND (SEALL,SEMG,etc..) REQUEST REFERENCES SE UNDEFINED SUPERELEMENTS. USER ACTION: CHECK THE SE - TYPE COMMAND AND RE FERENCED SET COMMANDS. *** SYSTEM INFORMATION MESSAGE 6908 (FREQ) 6908.0 DISTRIBUTED MEMORY PARALLEL FREQUENCY RESPONSE IS DISABLED BECAUSE ZERO PROCESSORS WERE SELECTED (WITH SYSTEM(231)=0). SOLUTION WILL PROCEED WITH THE SEQUENTIAL SOLVER. *** SYSTEM INFORMATION MESSAGE 6908 (FREQ) 6908.1 DISTRIBUTED MEMORY PARALLEL FREQUENCY RESPONSE IS DISABLED BECAUSE FREQUENCY DEPENDENT MATERIALS ARE PRESENT. SOLUTION WILL PROCEED WITH THE SEQUENTIAL SOLVER. SYSTEM INFORMATION MESSAGE 6908 (FREQ) *** 6908.2 DISTRIBUTED MEMORY PARALLEL FREQUENCY RESPONSE IS DISABLED BECAUSE THE ITERATIVE SOLVER IS SELECTED (WITH SYSTEM(216)=1). SOLUTION WILL PROCEED WITH THE SEQUENTIAL SOLVER. *** SYSTEM WARNING MESSAGE 69 08 (PNNAME) 6908.3 CANNOT DETERMINE THE PROCESSOR NAME *** USER INFORMATION MESSAGE 6908 (FREQ) 6908.4 DISTRIBUTED MEMORY PARALLEL FREQUENCY RESPONSE

498 REQUIRES NUMDOM (NUMBER OF FREQUENCY DOMAINS) TO BE EQUAL TO THE NUMBER OF PROCESSORS. HOWEVER, THIS RUN SPECIFIES NUMDOM = %1, BUT THE NUMBER OF PROCESSORS IS EQUAL TO %2. USER INFORMATION: the program will use a value of %2 for NUMDOM to create the parallel frequency domains. *** USER INFORMATION MESSAG E 6909 (APD0) 6909.0 THE VALUES SPECIFIED FOR REFC ON THE AERO AND AEROS BULK DATA ENTRIES ARE DIFFERENT. *** USER FATAL MESSAGE 6910 (FA1) 6910.0 A VELOCITY OF ZERO IS SPECIFIED ON FLFACT BULK DATA ENTRY ID=%1 WHICH IS REFERENCED BY A FLUTTER ENTRY THAT SPECIFIES THE PK METHOD. *** SYSTEM WARNING MESSAGE 6911 (QCBFIN) 6911.0 THE DBVIEW HAS YIELDED MORE THAN ONE DATA BLOCK %1. THE PROGRAM WILL SELECT THE "FIRST" DATA BLOCK FOUND. PROGRAMMER ACTION: TO FIND THE DUPLICATES, SPECIFY THE WHERE CLAUSE FROM THE DBVIEW STATEMENT ON THE DBDICT STATEMENT AND THEN MODIFY THE WHERE CLAUSE ON THE DBVIEW STATEMENT TO REMOVE THE DUPLICATES. PROGRAMMER INFORMATION: DATA BLOCK 1: FISTNO =%2 PVAP TR = %3 DATA BLOCK 2: FISTNO =%4 PVAPTR = %5 *** SYSTEM FATAL MESSAGE 6912 (SEDR) 6912.0 THE BASIC GRID POINT DEFINITION TABLE NAMED %1 AND THE DISPLACEMENT MATRIX NAMED %2 FOR SUPERELEMENT %3 ARE INCONSISTENT. USER ACTION: IF THIS IS AN EXTERNA L SUPERELEMENT DATA RECOVERY, ENSURE THAT THE BGPDTS TABLE AND NOT THE EQEXINS TABLE IS DBLOCATE'D. PROGRAMMER INFORMATION: THE NUMBER OF DEGREES OF FREEDOM IN THE BASIC GRID POINT DEFINITION TABLE IS %4. THE NUMBER OF DEGREES OF FREEDOM IN THE DISPLACE MENT MATRIX IS %5. *** SYSTEM FATAL MESSAGE 6913 (OUTPX2) 6913.0 INDEXED MATRIX %1 COLUMN FILE (%2) IS CORRUPTED AT THE END OF THE FILE. USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 6914, (RAND5A), 6914.0 RANDPS ID =%1 REFERENCES UNDEFINED SUBCASE ID = %2 USER ACTION: CORRECT RANDPS ENTRY OR SUBCASE

499 COMMAND. PROBLEM COULD BE DUE TO CHANGE IN FREQUENCIES OR SDAMPING DEFINITIONS WITHIN REFERENCED SUBCASES. *** USER FATAL MESSAGE 6915 (GP1C) 6915.0 COORDINATE SYSTEM %1 IS DEFINED BY THREE COLLINEAR POINTS IN SUPERELEMENT %2 *** SYSTEM INFORMATION MESSAGE 6916 (DFMSYN) 6916.0 DECOMP ORDERING METHOD CHOSEN: BEND, ORDERING METHOD USED: AMF *** SYSTEM INFORMATION MESSAGE 6916 (DFMSYN) 6916.1 DECOMP ORDERING METHOD CHOSEN: BEND, ORDERING METHOD USED: BEND *** SYSTEM INFORMATION MESSAGE 6916 (DFMSYN) 6916.2 UNABLE TO EXECUTE METIS REORDERING BECAUSE THE MATRIX DENSITY IS TOO HIGH: %1 %. RDERING METHOD CHOSEN: METIS, ORDERING DECOMP O METHOD USED: MMD *** SYSTEM INFORMATION MESSAGE 6916 (DFMSYN) 6916.3 DECOMP ORDERING METHOD CHOSEN: DEFAULT, ORDERING METHOD USED: METIS *** SYSTEM INFORMATION MESSAGE 6916 (DFMSYN) 6916.4 DECOMP ORDERING METHOD CHOSEN: METIS, ORDERING METHOD USED: METIS *** SYSTEM INFORMATION MESSAGE 6916 (DFMSYN) 6916.5 UNABLE TO EXECUTE METIS REORDERING BECAUSE THE MATRIX DENSITY IS TOO HIGH: %1 %. DECOMP ORDERING METHOD CHOSEN: DEFAULT, ORDERING METHOD USED: MMD *** SYSTEM INFORMATION MESSAGE 6916 (DFMSYN) 6916.6 UNABLE TO EXECUTE METIS REORDERING BECAUSE THE MATRIX DENSITY IS TOO HIGH: %1 %. DECOMP ORDERING METHOD CHOSEN: METIS, ORDERING METHOD USED: MMD SYSTEM INFORMATION MESSAGE 6916 (DFMSYN) *** 6916.7 DECOMP ORDERING METHOD CHOSEN: MMD, ORDERING METHOD USED: MMD *** SYSTEM INFORMATION MESSAGE 6916 (DFMSYN) 6916.8 DECOMP ORDERING METHOD CHOSEN: DEFAULT, ORDERING METHOD USED: BEND SYSTEM INFORMATION MESSAGE 6916 (DFMSYN) *** 6916.9 INCREASE MEMORY BY AT LEAST %1 WORDS TO ENABLE METIS. DECOMP ORDERING METHOD CHOSEN: DEFAULT, ORDERING METHOD USED: MMD

500 *** SYSTEM INFORMATION MESSAGE 6916 (DFMSYN) 6916.10 INCREASE MEMORY BY AT LEAST %1 WORDS TO ENABLE METIS. DECOMP ORDERING METHOD CHOSEN: METIS, ORDERING METHOD USED: MMD *** SYSTEM INFORMATION MESSAGE 6916 (DFMSYN) 6916.11 DECOMP ORDERING METHOD CHOSEN: METIS, ORDERING METHOD USED: MMD *** SYSTEM INFORMATION MESSAGE 6916 (DFMSYN) 6916.12 DECOMP ORDERING METHOD CHOSEN: DEFAULT, ORDERING METHOD USED: MMD *** SYSTEM INFORMATION MESSAGE 6916 (DFMSYN) 6916.13 MALLOC FAILED INSIDE METIS. DECREASING THE MEMORY INCREASE THE MEMORY AVAILABLE GIVEN TO THE JOB WILL FOR MALLOC. DECOMP ORDERING METHOD CHOSEN: METIS, ORDERING METHOD USED: MMD *** SYSTEM INFORMATION MESSAGE 6916 (DFMSYN) 6916.14 MALLOC FAILED INSIDE METIS. DECREASING THE MEMORY GIVEN TO THE JOB WILL INCREASE THE MEM ORY AVAILABLE FOR MALLOC. DECOMP ORDERING METHOD CHOSEN: DEFAULT, ORDERING METHOD USED: MMD *** SYSTEM INFORMATION MESSAGE 6916 (DFMSYN) 6916.15 METIS ERROR. DECOMP ORDERING METHOD CHOSEN: METIS, ORDERING METHOD USED: MMD SYSTEM INFORMATION MESSAGE 6916 (DFMSYN) *** 6916.16 METIS ERROR. DECOMP ORDERING METHOD CHOSEN: DEFAULT, ORDERING METHOD USED: MMD *** SYSTEM FATAL MESSAGE 6916 (DFMSYN) 6916.17 MALLOC FAILED INSIDE EXTREME. USER ACTION: DECREASE THE MEMORY GIVEN TO THE JO B IN ORDER TO INCREASE THE MEMORY AVAILABLE FOR MALLOC OR USE METIS OR GRID BASED MMD REORDERING by RE - SUBMITTING THE JOB WITH ONE OF THE FOLLOWING VALUES FOR SYSTEM(206): SYSTEM(206)=1 (GRID BASED MMD) SYSTEM(206)=8 (GRID BASED METIS) OR 9 (SELECTS BEST OF THE TWO ABOVE) SYSTEM(206)= *** USER FATAL MESSAGE 6917 (TAB) 6917.0 FOR TABLED1 OR TABLEM1 ENTRY ID = %1; AN X - VALUE = %2 CAUSES EXPONENTIAL EXTRAPOLATION OF Y - VALUE, WITH NUMERIC OVERFLOW.

501 USER ACTION: AMEND TABLE TO AVOID BALLOONING EXPONENTIAL EXTRAPOLATION BEYOND TABLE LIMITS. *** SYSTEM FATAL MESSAGE 6918 (MATMOD) 6918.0 FOR MATMOD OPTION %1 AN INVALID VALUE %2 IS SPECIFIED FOR THE TYPE (2ND PARAMETER) THE VALID VALUES ARE 1 OR 2 FOR REAL 3 OR 4 FOR COMPLEX AND 0 (DEFAULT) FOR OPPOSITE TYPE THAN INPUT TYPE. *** SYSTEM FATAL MESSAGE 6918 (MATMOD) 6918.1 FOR MATMOD OPTION%1 AN INVALID VALUE %2 IS SPECIFIED FOR THE PRECISION (3RD PARAMETER) THE VALID VALUES ARE 1 FOR SINGLE PRECISION 2 FOR DOUBLE PRECISION, AND 0 (DEFAULT) FOR MACHINE PRECISION. *** SYSTEM FATAL MESSAGE 6919 (MATMOD) 6919.0 ILLEGAL VALUE %1 FOR OPTION (FIRST PARAMETER). IT MUST BE GREATER THAN ZERO AND LESS THAN %2. *** SYSTEM FATAL MESSAGE 6920 (MATMOD) 6920.0 FOR MATMOD OPTION %1, THE COLUMN NUMBER %2 IS INVALID. IT MUST BE GREATER THAN ZERO AND LESS THAN %3. *** SYSTEM FATAL MESSAGE 6921 (MATMOD) 6921.0 - OF - FREEDOM CODE %1 IS FOR MATMOD OPTION 3, THE DEGREE INVALID. *** SYSTEM FATAL MESSAGE 6922 (MATMOD) 6922.0 FOR MATMOD OPTION 8, THE TYPE OF MATRIX %1 IS INVALID. *** SYSTEM WARNING MESSAGE 6923 (MODTRL) 6923.0 ILLEGAL VALUE %1 IS SPECIFIED FOR PARAMETER %2 THE VALUE WILL BE IGNORED. *** SYSTEM FATAL MESSAGE 6924 (MODTRL) 6924.0 AN ATTEMPT TO MODIFY THE TYPE AND/OR PRECISION OF MATRIX %1. USER ACTION: 1. IN ORDER TO CHANGE THE PRECISION OF A MATRIX, USE ADD5. IF THE NEW PRECISION DOES NOT MATCH THE MACHINE PRECISION THEN SPECIFY PUTSYS(NEW PR ECISION,55) BEFORE ADD5. FOR EXAMPLE, A. SINGLE TO DOUBLE ON A DOUBLE WORD MACHINE: - ADD5 SINGLE,,,,/DOUBLE $ B. DOUBLE TO SINGLE ON A DOUBLE - WORD MACHINE: PUTSYS(1,55) $ ADD5 DOUBLE,,,,/SINGLE $ PUTSYS(2,55) $ *** SYSTEM FATAL MESSAGE 6925 (MODTRL) 6925.0 AN ATTEMPT TO MODIFY THE DENSITY OF MATRIX%1.

502 *** SYSTEM WARNING MESSAGE 6926 (MTMD34) 6926.0 ATTEMPT TO CONVERT %1 MATRIX %2 AND %3 INPUT MATRIX %4 INTO A %5 MATRIX. INPUT MATRICES NEED TO BE THE SAME TYPE. *** SYSTEM FATAL MESSAGE 6927 (MTMD34) 6927.0 ATTEMPT TO CONVERT REAL MATRIX %1 INTO A COMPLEX MATRIX. USER ACTION: USE THE ADD OR ADD5 MODULE; FOR EXAMPLE: ADD %2,/%3//(0.0,1.0) $ *** SYSTEM FATAL MESSAGE 6928 (MTMD34) 6928.0 ATTEMPT TO CONVERT %1 %2 INPUT MATRIX %3 TO A %4 %5 MATRIX. *** SYSTEM INFORMATION MESSAGE 6929. (EMGPOM) 6929.0 MATRIX DATA FOR DATA BLOCK %1 IS BEING COMPUTED FOR ELEMENT WITH ID=%2 HOWEVER WILL NOT BE OUTPUT AS THIS DATA BLOCK IS PURGED OR NOT REQUESTED. *** SYSTEM FATAL MESSAGE 6930. (EMGPOM) 6930.0 - EMGPOM - FOR ELEMENT ID = %1 INCORRECT CALL MADE TO FILE TYPE = %2 ERROR PATH LOC CODE = %3 *** SYSTEM FATAL MESSAGE 6931. (EMGPOM) 6931.0 CONGRUENCY IS IMPLIED FOR ELEMENT ID = %1 - HOWEVER THIS IS THE FIRST ELEMENT OF ITS TYPE FOR FILE - TYPE = %2 *** SYSTEM FATAL MESSAGE 6932. (EMGPOM) 6932.0 THE DEGREES OF FREEDOM OR THE OUTPUT FORMAT HAS CHANGED BETWEEN ELEMENT - IDS OF THE SAME TYPE FOR FILE TYPE = %1 ELEMENT ID = %2 %3%4%5 %6 - *** SYSTEM FATAL MESSAGE 6933. (EMGPOM) 6933.0 - MATRIX HAS BEEN SENT TO - ONLY E - AND NO LOC - EMGPOM CODE POINTER EXISTS TO MATRIX DATA. ELEMENT - ID = %1 FILE TYPE = %2 *** SYSTEM FATAL MESSAGE 6934. (EMGPOM) 6934.0 FOR ELEMENT ID = %1 AND FILE TYPE = %2 EMGPRO DETERMINES A DIFFERENT COUNT OF ACTIVE CONNECTION SILS THAN DOES CALLER OF EMGPOM EMGPRO COUNT = %3 CALLING ROUTINE COUNT = %4 *** SYSTEM FATAL MESSAGE 6935. (EMGPOM) 6935.0 ELEMENT ID = %1 FILE TYPE = %2%3%4%5%6%7 - INCONSISTENT NUMBER OF COLUMNS OR TERMS SENT BY ELEMENT ROUTINE FOR PACKING OUT BY EMGPOM, OR INVALID INFORM - OUFORM COMBINATION.

503 *** SYSTEM FATAL MESSAGE 6936 (PARAML) 6936.0 ILLEGAL VALUE OF, %1, SPECIFIED FOR THE SECOND PARAMETER. THE VALUE MUST BE GREATER THAN - 3. *** USER FATAL MESSAGE 6937. (MDCASE) 6937.0 STATIC AEROELASTIC SUBCASES MUST PRECEDE ANY STATICS SUBCASE USER ACTION:MOVE ANY SUBCASES WITH ANALYSIS=SAER O BEFORE SUBCASES WITH ANALYSIS=STATICS IN CASE CONTROL *** SYSTEM WARNING MESSAGE 6938 6938.0 SERIOUS BREAKDOWN IN BLOCK COMPLEX LANCZOS USER ACTION: CHANGE SETTING OF EIGC BULK DATA ENTRY *** SYSTEM INFORMATION MESSAGE 6938 6938.1 MILD BREAKDOWN IN BLOCK COMPLEX LANCZOS *** SYSTEM WARNING MESSAGE 6938 6938.2 BREAKDOWN IN BLOCK LANCZOS METHOD USER ACTION: ENABLE BLOCK AUGMENTATION *** SYSTEM WARNING MESSAGE 6938 6938.3 MAXIMUM BLOCK SIZE HAS BEEN REACHED *** SYSTEM WARNING MESSAGE 6938 6938.4 MAXIMUM BLOCK SIZE REACHED IN BLOCK LANCZOS USER ACTION: INCREASE MAXIMUM BLOCK SIZE *** SYSTEM FATAL MESSAGE 6939 6939.0 UNABLE TO READ EIGENVECTORS FROM SCRATCH FILE USER ACTION: CLEAN UP DISK DEVICE *** SYSTEM FATAL MESSAGE 6939 6939 .1 UNABLE TO READ LANCZOS VECTORS FROM SCRATCH FILE USER ACTION: CLEAN UP DISK DEVICE *** SYSTEM INFORMATION MESSAGE 6940 6940.0 SPILL OCCURRED WHEN CALCULATING LANCZOS VECTORS. %1 OUT OF A TOTAL OF %2 LANCZOS VECTORS HAVE BEEN STORED OUT OF CORE. USER ACTION: TO PREVENT SPILL, INCREASE OPEN CORE SIZE BY AT LEAST %3 WORDS *** SYSTEM INFORMATION MESSAGE 6940 6940.1 SPILL OCCURRED WHEN CALCULATING PHYSICAL EIGENVECTORS. USER ACTION: TO PREVENT SP ILL, INCREASE MAXIMUM BLOCK SIZE BY AT LEAST %1 *** SYSTEM INFORMATION MESSAGE 6941 6941.0 INVARIANT SUBSPACE DETECTED IN BLOCK LANCZOS *** SYSTEM WARNING MESSAGE 6942, (RAND5) 6942.0

504 FOR SUBCASE ID = %1 FREQUENCY %2 AT POINT %3 DOF %4 THE DISPLACEMENT IS LARGE ENOUGH TO CAUSE NUMERIC OVERFLOW IN RANDOM ANALYSIS. USER INFORMATION: THIS DISPLACEMENT IS SET TO ZERO FOR THE PURPOSE OF CALCULATING THE POWER SPECTRAL DENSITY. USER ACTION: CHECK MODEL OR REMOVE ABOVE FREQU ENCY. *** SYSTEM WARNING MESSAGE 6942, (RAND5) 6942.1 FOR SUBCASE ID = %1 FREQUENCY %2 AT POINT %3 DOF %4 THE DISPLACEMENT IS SMALL ENOUGH TO CAUSE NUMERIC UNDERFLOW IN RANDOM ANALYSIS. USER INFORMATION: THIS DISPLACEMENT IS SET TO ZERO FOR THE P URPOSE OF CALCULATING THE POWER SPECTRAL DENSITY. USER ACTION: CHECK MODEL OR REMOVE ABOVE FREQUENCY. *** USER FATAL MESSAGE 6943 (IFP6) 6943.0 THE MAT2 ID=%1, GENERATED BY A PCOMP ENTRY HAS THE SAME ID AS A USER SUPPLIED MAT2 ENTRY. USER INFORMATION: CHANGE THE ID OF THE USER SUPPLIED MAT2 ENTRY. *** SYSTEM FATAL MESSAGE 6944. (MKSPL) 6944.0 AELIST ENTRY ID = %1 THAT IS REFERENCED ON SPLINE%2 ENTRY ID=%3 DOES NOT EXIST. *** USER FATAL MESSAGE 6944 (ADG) 6944.1 AELIST E NTRY ID = %1 THAT IS REFERENCED ON AESURF ENTRY ID = %2 DOES NOT EXIST. *** SYSTEM FATAL MESSAGE 6945. (APD0) 6945.0 AERO ANALYSIS TYPE (AERTYP) PARAMETER HAS AN ILLEGAL VALUE: %1 USER INFORMATION: LEGAL AERO ANALYSIS TYPES (AERTYP) ARE %2, %3, %4. ***USER FATAL MESSAGE 6946. (TRD1G) 6946.0 TIC BULK DATA ENTRY %1 REFERENCES MODAL COORDINATE %2 WHICH IS > THE NUMBER OF MODES. ***SYSTEM FATAL MESSAGE 6947. (FBSUB) 6947.0 LOGIC ERROR 10. ***USER FATAL MESSAGE 6948. (TRD1G) 6948.0 TIC BULK DATA ENTRY %1 REFERENCES A NON - MODAL COORDINATE. THIS TIC IS REFERENCED BY AN IC(MODAL) CASE CONTROL ENTRY, SO IT MUST CONTAIN ONLY MODAL COORDINATES.

505 ***USER FATAL MESSAGE 6949. (TRD1G) 6949.0 TIC BULK DATA ENTRY %1 REFERENCES A MODAL COORDINATE. THIS TIC IS REFERENCED BY AN IC(PHYSICAL) CASE CONTROL ENTRY, SO IT MUST NOT CONTAIN ANY MODAL COORDINATES. ***SYSTE M FATAL MESSAGE 6952. (FMSPUT) 6952.0 HEADER TYPE %1 MAY NOT HAVE DATA RECORDS USE HEADER TYPE %2 FOR SINGLE DATA RECORD %3 FOR MULTIPLE DATA RECORDS ***SYSTEM FATAL MESSAGE 6953. (FMSPUT) 6953.0 HEADER TYPE %1 IS INVALID USE HEADER TYPE %2 FOR SINGLE DATA RECORD %3 FOR MULTIPLE DATA RECORDS ***SYSTEM FATAL MESSAGE 6954. (FMSPUT) 6954.0 MISSING %1 INPUT DATA RECORD(S) FOR PREVIOUS HEADER. ***SYSTEM FATAL MESSAGE 6955. (FMSPUT) 6955.0 FOUND %1 EXTRA INPUT DA TA RECORD(S) FOR PREVIOUS HEADER. - *** SYSTEM FATAL MESSAGE 6959. (GCPD 1) 6959.0 - ID = %1 SIL = %2 CAN NOT BE FOUND IN LIST OF FOR ELEMENT SILS OF DICTIONARY ENTRY. *** SYSTEM FATAL MESSAGE 6960. 6960.0 OUTPUT FORM =%1 FOUND IN DICTIONARY HEADER IS CURRENTLY NOT ACCEPTABLE FOR ELEMENT ID = %2 *** SYSTEM FATAL MESSAGE 6961. 6961.0 LOGIC ERROR AT LOC =%1 FOR ELEMENT ID =%2 *** USER FATAL MESSAGE 6962, (MATGEN - 3) 6962.0 ILLEGAL VALUE FOR OPTION PARAMETER = %1 *** USER FATAL MESSAGE 6962, (MATGEN - 4) 6962.1 ILLEGAL VALUE FOR PARAMETER %1 = %2 *** USER WARNING MESSAGE 6963, (MATGEN - 11) 6963.0 UNABLE TO GENERATE NULL MATRIX OF A - SET SIZE SINCE A - SET IS EMPTY. *** USER WARNING MESSAGE 6964, (MATGEN - 11) 6964.0 ILLEGAL COMBINATION OF PARAMETER OPTION. P3 AND P4 MAY NOT BOTH BE ZERO. 11) *** USER WARNING MESSAGE 6965, (MATGEN - 6965.0 USET SET SELECTED BY PARAMETER P4 IS EMPTY. OUTPUT MATRIX PURGED. *** USER WARNING MESSAGE 6965, (MATGEN - 11) 6965.1 USET SET SELECTED BY PARAMETER P3 IS EMPTY. OUTPUT

506 MATRIX PURGED. 11) *** USER WARNING MESSAGE 6966, (MATGEN - 6966.0 SET SPECIFIED BY P4 IS NOT A LEGITIMATE SUBSET OF THE SET SPECIFIED BY P3. OUTPUT MATRIX PURGED. ***USER FATAL MESSAGE 6967, (MATMOD - 17) 6967.0 EITHER USET BIT POSITION OR PATRN SET MUST BE SPECIFIED WHEN USING MATMOD OPTION 17. 17) ***USER WARNING MESSAGE 6968, (MATMOD - 6968.0 NO GRID OR SCALAR POINTS IN SELECTED SET. PARTITIONING VECTOR NULL. ***USER FATAL MESSAGE 6969, (MATMOD - 17) 6969.0 PARTN SET %1 HAS BEEN SELECTED BUT HAS NOT BEEN DEFINED. ***USER WARNING MESSAGE 6970, (MATMOD - 17) 6970.0 NO PARTN SET SELECT ED AS INDICATED BY PARAMETER SETFLG. CHECKING USET BIT PARAMETER. 14) *** USER WARNING MESSAGE 6971, (MATMOD - 6971.0 UNABLE TO USE RELATIVE FILTER ON MATRIX %1 BECAUSE ITS FORM IS NON - SQUARE. *** USER FATAL MESSAGE 6972. (MATMOD 26) - 6972.0 NO PROCESSING OF DATA BLOCK %1 WILL BE PERFORMED BECAUSE ITS DENSITY IS ZERO. *** USER FATAL MESSAGE 6973 (ASGNCD) 6973.0 THERE ARE MORE SUPPORTED DEGREES OF FREEDOM THAN CAN BE CONTROLLED BY CONTROL SURFACES. ALGORITHM USER INFORMATION: THE NONLINEAR TRIM ASSUMES THAT CONTROL SURFACES CAN CONTROL ROTATIONS ABOUT UP TO THREE AXES. THE NUMBER OF SUPPORTED DEGREES OF FREEDOM MINUS THE NUMBER OF FREE AESTAT BULK DATA ENTRIES IS FOUR OR GREATER. USER ACTION : SPECIFY ADDITIONAL AESTAT ENTRIES OR ER SUPPORTED DEGREES OF FREEDOM. FEW *** USER FATAL MESSAGE 6974 (ASGNCD) 6974.0 THE CONTROL SURFACES CANNOT PARTICIPATE IN THE REQUESTED TRIM TASK. USER INFORMATION: THE NONLINEAR TRIM ALGORITHM HAS FOUND THAT THERE ARE FREE CONTROL SURFACES, BUT NO DEGRESS OF FREEDOM FOR THEM TO CONTROL. USER ACTION : SPECIFY FEWER AESTAT ENTRIES OR MORE SUPPORTED DEGREES OF FREEDOM. *** USER FATAL MESSAGE 6975 (ASGNCD) 6975.0

507 A SUPPORTED DEGREE OF FREEDOM IS NOT AFFECTED BY ANY CONTROL SURFACE. INFORMATION: AN EXAMPLE IS AN AIRPLANE THAT IS USER FREE TO ROLL WITH NO CONTROL SURFACE AFFECTING THE ROLL AXIS. USER ACTION : ADD ADDITIONAL CONTROL SURFACES OR REMOVE THE SUPPORTED DEGREE OF FREEDOM. *** USER FATAL MESSAGE 6976 (ASGPRD) 6976.0 HD BULK DATA ENTRY ID = %1 THAT IS REFERENCED BY CSSC THE CSSCHD CASE CONTROL COMMAND DOES NOT EXIST. USER ACTION : PROVIDE THE REQUIRED CSSCHD BULK DATA ENTRY. *** USER FATAL MESSAGE 6977 (PRESCH) 6977.0 THE DATA DEFINED ON THE AEFACT BULK DATA ENTRY ID = %1 ASSOCIATED WITH CSSCHD ID = %2 AND AESURF ID = %3 IS INCONSISTENT. USER INFORMATION: THERE ARE %4 MACH NUMBERS SPECIFIED AND %5 ANGLES OF ATTACK WITH THE REQUIREMENT. THERE SHOULD BE %6 TERMS ON THE ASSOCIATED AEFACT ID = %7, BUT THERE ARE %8 TERMS. *** SYSTEM FATAL MESSAGE 6978 (SB11RD) 6978.0 RECORD LENGTH IS NOT ENOUGH TO STORE THE %1 BLOCK ROW OF PRECONDITIONER. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 9006 (SB53RD) .0 6979 MAXIMUM PERMUTED BLOCK ROW LENGTH = %1 EXCEEDS THE RECORD LENGTH = %2. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 9007 (SB85RD) 6980.0 LARGEST BLOCK ROW OF THE INITIAL MATRIX (%1 WORDS) EXCEEDS THE SPECIFIED MAXIMUM RECORD LENGTH (%2 WORDS). USER ACTION: PLEASE SET RECLEN=%3 (OR A HIGHER VALUE) ON THE ITER BULK DATA ENTRY. *** SYSTEM FATAL MESSAGE 9008 (SB85RD) 6980.1 LARGEST BLOCK ROW OF THE PRECONDITIONER (%1 WORDS) EXCEEDS THE SPECIFIED MAXIMUM RECORD LENGTH (%2 WORDS). USER ACTION: PLEASE SET RECLEN=%3 (OR A HIGHER VALUE) ON THE ITER BULK DATA ENTRY. *** USER FATAL MESSAGE 6981 (NBS1D) 6981.0 BUSH1D ELEMENT ID = %1 REFERENCES UNDEFINED EQUATION

508 ID = %2. *** SYSTEM FATAL MESSAGE 6982 6982.0 LOGIC ERROR. THERE SEEMS TO BE MORE TERMS IN COLUMNS OF THE DATA MATRIX THEN THE NUMBER OF EIGENVALUES =%1 *** SYSTEM FATAL MESSAGE 6983 (DRMH3F) 6983.0 PROGRAMMING ERROR; THE INPUT MAP TABLE HAS INCONSISTENT ELEMENT IDS AND CONSTANTS ELEMENT LIST: ELTYPE = %1 ID = %2 CONSTANT LIST: ELTYPE = %3 ID = %4 INCORRECT NUMBER OF WORDS BEING REQUESTED FOR 6984.0 - 2 ROUTINE. TRANSMISSION TO AND BY PHASE EMENT ID =%1, WORDS THIS CALL =%2, TOTAL=%3 EL *** SYSTEM FATAL MESSAGE 6985 6985.0 PREVIOUS ELEMENT - ID =%1 - 1 OUTPUT DID NOT REQUEST CORRECT NUMBER OF PHASE WORDS. *** SYSTEM FATAL MESSAGE 6986 6986.0 - ID =%1 LOGIC ERROR. ELEMENT INCORRECT NUMBER OF STRESS OR FORCE WORDS ARE BEING OUTPUT BY A PHASE - 2 ELEMENT ROUTINE. SF CODE =%2 *** SYSTEM FATAL MESSAGE 6987 6987.0 EXECUTION CONTINUING HOWEVER ANY STRESS OR FORCE OUTPUT REQUESTS WILL BE IGNORED. *** USER FATAL MESSAGE 6988 (MKSPL) 6988.0 SPLINE %1 ENTRY ID = %2 REFERENCES A CAERO2 ENTRY ID = %3 WHICH IS NOT ALLOWED. USER ACTION: THIS TYPE OF SPLINE IS NOT APPROPRIATE FOR USE WITH SLENDER BODIES, USE A LINEAR (BEAM) SPLINE. *** USER FATAL MESS AGE 6989 (ADGHMK) 6989.0 BOX ID = %1, DEFINED ON AELIST ENTRY ID = %2 ON AESURF ENTRY ID = %3, DOES NOT EXISTS. *** USER FATAL MESSAGE 6990 (ADGHMK) 6990.0 DUPLICATE BOX ID = %1 FOUND ON CONTROL SURFACES 1 (AELIST ENTRY ID = %2) and 2 (AELIST ENTRY ID = %3) ON AESURF ENTRY ID = %4. USER INFORMATION: NO OVERLAPPING CAN OCCURRED ON TWO CONTROL SURFACES DEFINED ON THE SAME AESURF ENTRY. *** SYSTEM WARNING MESSAGE 6991, (NORMM) 6991.0 NORM MODULE HAS COMPUTED A MAX VALUE WHICH E XCEEDS THE SINGLE PRECISION FORMAT. USER INFORMATION: THE VALUE IS %1 THE THIRD OUTPUT PARAMETER IS SET TO 0.0E0.

509 USER ACTION: USE THE FIFTH PARAMETER TO OUTPUT THE PROPER VALUE. *** USER FATAL MESSAGE 6991 (JINTG) 6991.1 ASE CONTROL JINTG PROCESSING JINTEG CARD MISSING IN C TERMINATED. *** SYSTEM INFORMATION MESSAGE 6993 (ASGNLD/S) 6993.0 CONTROL SURFACE LIMITS ARE EXCEEDED. USER INFORMATION: CONSTRAINED OPTIMIZATION WILL BE PERFORMED. *** SYSTEM FATAL MESSAGE 6994. 6994.0 SHAPE FUNCTION ROUTINE SHPTQD IS CALLED FOR UNKNOWN TYPE *** USER WARNING MESSAGE 6995, 6995.0 DTI UPDATE DATA OUT OF RANGE. %1 %2 %3 ***USER WARNING MESSAGE 6996 6996.0 DVAR BULK DATA ENTRY ID = %1 REQUESTED VIA SET2 CANNOT BE FOUND. ***USER WARNING MESSAGE 6996 6996.1 DSCONS BULK DATA ENTRY ID = %1 REQUESTED VIA SET2 CANNOT BE FOUND. **** USER WARNING MESSAGE 6997, 6997.0 GRIDS %1 AND %2 ARE GENERATED INTERNALLY IN CRAC3D ELEMENT ID= %3 *** SYSTEM FATAL MESSAGE 6998 (FMSFIO) 6998.0 FORTRAN UNIT 2 USED FOR FMS IS NOT INITIALIZED. *** SYSTEM FATAL MESSAGE 6999 (FMSFIO) 6999.0 FORTRAN UNIT %1 USED FOR FMS DOES NOT HAVE A CORRESPONDING VALUE IN FORUNT ARRAY. *** USER WARNING MESSA GE 7001 (DOPR1B) 7001.0 FOR DESVAR ENTRY ID = %1 THE USER INITIAL VALUE = %2 WHILE THE COMPUTED VALUE = %3 THE USER SUPPLIED VALUE ON THE DESVAR ENTRY IS OVERRIDDEN BY THE COMPUTED VALUE FROM THE DLINK ENTRY *** USER FATAL MESSAGE 7002 (DOPR1B) 7002.0 NO DESVAR ENTRIES ARE SPECIFIED IN THE BULK DATA. *** USER FATAL MESSAGE 7002 (DOPR1B) 7002.1 NO DESVAR ENTRIES ARE SPECIFIED IN THE BULK DATA. *** USER FATAL MESSAGE 7003 (IFS6P) 7003.0 THE DVPREL%1 ID = %2 BULK DATA ENTRY REFERS TO A FREQ UENCY DEPENDENT PROPERTY,

510 BUT NO RELEVANT FREQUENCY (Field 9) HAS BEEN ASSOCIATED WITH THIS PROPERTY. *** USER FATAL MESSAGE 7004.0 (IFS6P) 7004.0 IN %1 CARD WITH ID = %2, THE FIELD %3 MUST BE %4. *** USER FATAL MESSAGE 7004.1 (IFS6P) 7004.1 IN %1 CARD, THE FIELD %2 MUST BE %3. *** USER FATAL MESSAGE 7004.2 (IFS6P) 7004.2 IN %1 CARD WITH ID = %2, THE VALUE OF FIELD %3 IS NOT SUPPORTED *** USER WARNING MESSAGE 7004.3 (IFS6P) 7004.3 ONLY A SINGLE %1 CARD IS ALLOWED IN THE BULK DATA SECTION, CARD WITH ID %2 WILL BE IGNORED. *** USER FATAL MESSAGE 7008 (DOPR1B) 7008.0 THE NUMBER OF DLINK ENTRIES EXCEEDS THE NUMBER OF DESVAR ENTRIES. USER INFORMATION: THE NUMBER OF DEPENDENT DE SIGN VARIABLES MUST BE LESS THAN THE TOTAL NUMBER OF DESIGN VARIABLES. *** USER FATAL MESSAGE 7011 (DOPR1B) 7011.0 DLINK ENTRY %1 REFERENCES DESVAR ENTRY %2 WHICH DOES NOT EXIST. *** USER FATAL MESSAGE 7015 (DOPR1Z) 7015.0 THE FIELD DVID = %1 ON DVPREL2 ID =%2 IS NOT REFERENCED ON A DESVAR ENTRY. *** USER FATAL MESSAGE 7015 (DOPR1Z) 7015.1 THE FIELD DVID = %1 ON DVCREL2 ID =%2 IS NOT REFERENCED ON A DESVAR ENTRY. *** USER FATAL MESSAGE 7015 (DOPR1Z) 7015.2 THE FIELD DVID = %1 ON DVMREL2 ID =%2 IS NOT REFERENCED ON A DESVAR ENTRY. *** USER FATAL MESSAGE 7015 (DOPR1C) 7015.3 THE FIELD DVID %1 ON DVPREL1 ENTRY ID = %2 IS NOT REFERENCED ON A DESVAR ENTRY. *** USER FATAL MESSAGE 7015 (DOPR1C ) 7015.4 THE FIELD DVID %1 ON DVCREL1 ENTRY ID = %2 IS NOT REFERENCED ON A DESVAR ENTRY. *** USER FATAL MESSAGE 7015 (DOPR1C) 7015.5 THE FIELD DVID %1 ON DVMREL1 ENTRY ID = %2 IS NOT REFERENCED ON A DESVAR ENTRY. *** USER FATAL MESSAGE 7023 (DOPR3C) 7023.0 THERE ARE %1 ENTRIES BUT NO DEQATN ENTRIES.

511 *** USER FATAL MESSAGE 7028 (DOPR3C) 7028.0 THE LABEL = %1 ON %2 ENTRY ID = %3 CANNOT BE FOUND ON the DTABLE ENTRY. *** USER FATAL MESSAGE 7028 (DOPR1Z) 7028.1 THE LABEL = %1 ON DVPREL2 ENTRY ID =%2 CANNOT BE FOUND ON THE DTABLE ENTRY. *** USER FATAL MESSAGE 7052 (DOMPTC) 7052.0 ILLEGAL PROPERTY TYPE %1 IS REFERENCED ON %2 ENTRY %3. *** USER FATAL MESSAGE 7052 (DOMPNTF) 7052.1 %1 ENTRY %2 REFERENC ES AN ILLEGAL COMBINATION OF PROPERTY TYPE %3 AND PROPERTY NAME %4. *** USER FATAL MESSAGE 7052 (DOMPNTF) 7052.2 %1 ENTRY %2 REFERENCES AN UNSUPPORTED COMBINATION OF PROPERTY TYPE %3 AND PROPERTY NAME %4. *** USER FATAL MESSAGE 7053 (DVPCHK) 7053.0 DVPREL %1 ENTRY %2 WITH PTYPE= %3 REFERENCES A POSITIVE FID %4. USER ACTION: REPLACE THE FID WITH A NEGATIVE NUMBER. *** USER FATAL MESSAGE 7054 (DVPCHK) 7054.0 THE PROPERTY NAME %1 REFERENCED ON DVPREL%2 ENTRY %3 CAN NOT BE DESIGNED. *** USER FATAL MESSAGE 7055 (DVPCHK) 7055.0 DVPREL %1 ENTRY %2 WITH PTYPE= %3 REFERENCES AN FID %4 THAT CAN NOT BE DESIGNED. *** USER FATAL MESSAGE 7055 (DOPR1C) 7055.1 %1 ENTRY %2 SPECIFIES PROPERTY NAME = %3 THAT IS NOT SPECIFIED ON PBEAM ENTRY %4. USER ACTION: CHECK %5 AND PBEAM ENTRIES. *** USER FATAL MESSAGE 7055 (DOPR1Z) 7055.2 %1 ENTRY %2 SPECIFIES FID = %3 THAT IS NOT SPECIFIED ON PBEAM ENTRY %4. USER ACTION: CHECK %5 AND PBEAM ENTRIES. ***USER FATAL MESSAGE 7057, DOMPTA. 7057.0 ILLEGAL PROPERTY ENTRY NAME %1 *** USER FATAL MESSAGE 7076 (DOPR3I) 7076.0 DRESP1 ENTRY ID = %1 REFERENCES A %2 BULK DATA ENTRY ID found. = %3 WHICH cannot be *** USER FATAL MESSAGE 7076 (DOPR3B) 7076.1 DRESP1 BULK DATA ENTRY OF ID %1 REFERENCES A %2 BULK DATA ENTRY OF ID %3 WHICH DOES NOT EXIST. *** USER FATAL MESSAGE 7076 (DOPR3I) 7076.2 THE DWEIGHT RESPONSE ON THE DRESP1 CARD CAN ONLY BE

512 USED WITH TOPOLOGY OPTIMIZATION. *** USER FATAL MESSAGE 7077 (%1) 7077.0 DRESP1 ENTRY ID = %1 SPECIFIES A ROOT NUMBER = %2 WHICH IS GREATER THAN THE ENTRY ID = NROOT = %3 ON THE associated DIVERG BULK DATA %4. *** USER FATAL MESSAGE 7078 (DOPR3I) 7078.0 DRESP1 ENTRY ID = %1 SPECIFIES A MACH NUMBER = %2 WHICH IS NOT LISTED ON THE ASSOCIATED DIVERG BULK DATA ENTRY ID = %3. *** SYSTEM FATAL MESSAGE 7081 (DOPR3I) 7081.0 DRESP1 ENTRY id = %1 INVOKES A %2 RESPONSE TYPE IN SUBCASE ID = %3. but THE REQUIRED %4 SET CASE CONTROL command cannot be found. *** USER FATAL MESSAGE 7084 (DOPR3B) 7084.0 DRESP1 BULK DATA ENTRY OF ID %1 REFERENCES A TRIM VARIABLE OF ID %2 WHICH CAN NOT BE FOUND. USER INFORMATION: THE TRIM VARIABLE ID MUST REFER TO AN AESTAT OR AESURF BULK DATA ENTRY. *** USER FATAL MESSAGE 7085 (DOPR3I) 7085.0 THE DENSITY RATIO OF %1 CANNOT BE FOUND IN THE FLFACT BULK DATA ENTRY ID = %2. USER INFORMATION: EVERY DENSITY RATIO LISTED ON THE FLFACT REFERENCED BY THE DRESP1 ENTRY MUST APPEAR IN THE FLFACT REFERENCED BY THE FLUTTER ENTRY. *** USER FATAL MESSAGE 7086 (DOPR3I) 7086.0 THE MACH NUMBER OF %1 CAN NOT BE FOUND IN THE FLFACT ULK DATA ENTRY OF ID %2. B USER INFORMATION: EVERY MACH NUMBER LISTED ON THE FLFACT REFERENCED BY THE DRESP1 ENTRY MUST APPEAR IN THE FLFACT REFERENCED BY THE FLUTTER ENTRY. *** USER FATAL MESSAGE 7087 (DOPR3I) 7087.0 FOUND IN THE FLFACT BULK THE VELOCITY OF %1 CAN NOT BE DATA ENTRY OF ID %2. USER INFORMATION: EVERY VELOCITY LISTED ON THE FLFACT REFERENCED BY THE DRESP1 ENTRY MUST APPEAR IN THE FLFACT REFERENCED BY THE FLUTTER ENTRY. *** USER FATAL MESSAGE 7088 (DSAD14) 7088.0 THE FLUTTER MODE OF %1 REQUESTED ON A SET1 ENTRY IS GREATER THAN %2, THE NUMBER OF EXTRACTED MODES. USER INFORMATION: SET1 IS REFERENCED BY DRESP1 BULK DATA WITH RTYPE = FLUTTER. *** SYSTEM FATAL MESSAGE 7088 (DOPR3I) 7088.1

513 MODE NO. %1 ASSOCIATED WITH FLUTTER DRESP1 ID = %2 EXCEEDS %3, THE NUMBER OF MODES AVAILABLE FROM THE ANALYSIS. *** USER FATAL MESSAGE 7102 (DOPR3Z) 7102.0 DCONSTR ID = %1 APPEARS MORE THAN ONCE ON DCONADD ENTRY %2. *** USER INFORMATION MESSAGE 7103 (DOPR3) 7103.0 NO DCONSTR ENTRIES ARE SPECIFIED IN THE BULK DATA. *** USER FATAL MESSAGE 7104 (DOPR3F) 7104.0 NO DCONSTR ENTRIES CAN BE FOUND WITH THE DESGLB = %1. *** USER FATAL MESSAGE 7104 (DOPR3F) 7104.1 NO DCONSTR ENTRIES CAN BE FOUND WITH THE DESSUB = %1. *** USER FATAL MESSAGE 7105 (DOPR3F) 7105.0 NO DCONSTR ID = %1 ENTRY CAN BE FOUND FOR DCONADD ENTRY ID = %2. *** SYSTEM FATAL MESSAGE 7114 (DOM2B) 7114.0 LESS THAN 3 WORDS IN AN EPT RECORD *** USER FATAL MESSAGE 7115 (DOM2B) 7115.0 PTYPE %1%2 IS NOT SUPPORTED *** SYSTEM FATAL MESSAGE 7116 (DOM2B) 7116.0 LESS THEN 2 WORDS IN A PSHELL ENTRY, PID = %1 *** SYSTEM FATAL MESSAGE 7116 (DOM2B) 7116.1 LESS THAN 2 WORDS IN A PCOMP ENTRY, PID = %1 *** SYSTEM FATAL MESSAGE 7119 (DOM2B) 7119.0 INCORRECT ENTRY LENGTH AT PTYPE = %1%2 PID = %3 *** USER FATAL MESSAGE 7124 (DOPR3B) 7124.0 PTYPE %1 ON DRESP1 ID=%2 IS NOT DEFINED IN THE ANALYSIS MODEL *** USER FATAL MESSAGE 7125 (DOPR3G/DSECAS) 7125.0 SUBCASE %1 ,SUBSPAN ID = %2 REFERENCES AN UNDEFINED SET. *** USER FATAL MESSAGE 7125 (DSECAS) 7125.1 DRSPAN SET MAY NOT CONTAIN ALL DRESP1. *** USER FATAL MESSAGE 7125 (DSECAS) 7125.2 DRSPAN SET %1 NOT FOUND. *** USER FATAL MESSAGE 7125 (DSECAS) 7125.3 DRSPAN ID %1 REPEATED IN SUBCASES %2 AND %3 *** USER FATAL MESSAGE 7126 (CHKPNL) 7126.0 ERP CASE CONTROL FOR SUBCASE %1 REFERENCES NON - EXISTENT or DISREGARDED SET %2 *** USER FATAL MESSAGE 7126 (CHKPNL) 7126.1 ERP RELATED [ SET %1 = ALL ] NOT VALID. USE [ ERP(...) = ALL ]

514 *** USER FATAL MESSAGE 7126 (CHKPNL) 7126.2 NO ERP RELATED PANELS IN INPUT DECK FOR SUBCASE %1 *** USER FATAL MESSAGE 7126 (CHKPNL) 7126.3 SET %1 ENTRY %2%3 IS NOT A VALID ALPHANUMERIC DEFINED PANEL LABEL. *** USER FATAL MESSAGE 7127 (DOPR3B) 7127.0 DRESP1 BULK DATA ENTRY OF ID %1 REFERENCES PTYPE %2 PID %3 THERE ARE NO ELEMENTS CORRESPONDING TO THIS COMBINATION. *** USER FATAL MESSAGE 7127 (DOPR3B) 7127.1 DRESP1 BULK DATA ENTRY OF ID %1 REFERENCES PTYPE %2 WITH INCORRECT LAMINA NUMBER %3 *** USER FATAL MESSAGE 7128 (DOPR3K) 7128.0 CANNOT SPAWN CONSTRAINT %1 ON RESPONSE %2 FOR ANALYSIS TYPE %3 User Information: Check for wrong analysis type, or response specified for a single frequency. You may need to use constant bounds for the constraint instead of tables. *** USER FATAL MESSAGE 7129 (DOPR3K) 7129.0 CONSTRAINT %1 LB > UB FROM TABLE(S) AT FREQUENCY %2 LOWER BOUND IS %3 BUT UPPER BOUND IS %4 User Information: is indicated. Data entry error Constraint lower bounds should not be greater than constraint upper bounds. *** USER FATAL MESSAGE 7137 (DOPR3C) 7137.0 ON %1 entry ID = %2, DVID = %3 IS NOT DEFINED BY A DESVAR entry. *** USER FATAL MESSAGE 7139 (DOPR3C) 7139.0 ON %1 entry ID = %2, DRESP1 ID = %3 DOES NOT REFERENCE AN EXISTING DRESP1 ENTRY. *** USER FATAL MESSAGE 7139 (DOPR3N) 7139.1 ON DRESP2 entry ID = %1, DRESP2 ID = %2 DOES NOT REFERENCE AN EXISTING DRESP2 ENTRY. *** USER FATAL MESSAGE 7141 7141.0 DRESP2 ENTRY ID = %1 REFERENCES DRESP1 ENTRIES WITH IDS = %2 AND %3. THESE DRESP1 ENTRIES HAVE DIFFERENT RTYPES AND AT LEAST ONE OF THE ENTRIES HAS MORE THAN ONE ASSOCIATED RESPONSE. USER INFORMATION: IF A DRESP2 EN TRY SPANS RESPONSE TYPES, THEN EACH ASSOCIATED DRESP1 ENTRY MUST GENERATE A SINGLE RESPONSE.

515 *** USER FATAL MESSAGE 7141 7141.1 %1 ENTRY ID = %2 REFERENCES DRESP1 ENTRIES WITH IDS = %3 AND %4. THESE DRESP1 ENTRIES HAVE DIFFERENT RTYPES AND AT LEAST ONE OF THE ENTRIES HAS MORE THAN ONE ASSOCIATED RESPONSE. USER INFORMATION: IF A %5 ENTRY SPANS RESPONSE TYPES, THEN EACH ASSOCIATED DRESP1 ENTRY MUST GENERATE A SINGLE RESPONSE. *** US ER FATAL MESSAGE 7142 7142.0 DRESP2 ENTRY ID = %1 REFERENCES DRESP1 ENTRIES WITH IDS = %2 AND %3. THESE DRESP1 ENTRIES HAVE A DIFFERENT NUMBER OF RESPONSES. USER INFORMATION: DRESP1 ENTRIES REFERENCED BY A DRESP2 ENTRY MUST HAVE THE SAME NUMBER OF RESPONSES *** USER FATAL MESSAGE 7142 (DOPR3J/DPR3J1) 7142.1 %1 ENTRY ID = %2 REFERENCES DRESP1 = %3 AND DRESP2 ID = %4. THESE REFERENCED ENTRIES HAVE A DIFFERENT NUMBER OF RESPONSES. USER INFORMATION: DRESP1 AND DRESP2 ENTRIES REFERENCED BY A %5 ENTRY MUST HAVE THE SAME NUMBER OF RESPON SES *** USER FATAL MESSAGE 7142 7142.2 %1 ENTRY ID = %2 REFERENCES DRESP2 ENTRIES WITH IDS = %3 AND %4. THESE REFERENCED ENTRIES HAVE A DIFFERENT NUMBER OF RESPONSES. USER INFORMATION: DRESP2 ENTRIES REFERENCED BY A %5 ENTRY MUST HAVE THE SAME NUMBER OF RESPONSES. *** USER FATAL MESSAGE 7142 7142.3 %1 ENTRY ID = %2 REFERENCES DRESP1 ENTRIES WITH IDS = %3 AND %4. THESE DRESP1 ENTRIES HAVE A DIFFERENT NUMBER OF ESPONSES. R USER INFORMATION: DRESP1 ENTRIES REFERENCED BY A %5 ENTRY MUST HAVE THE SAME NUMBER OF RESPONSES. *** USER FATAL MESSAGE 7143 (DOPR3H) 7143.0 DRESP2 ID = %1 IS REFERENCED BY MORE THAN ONE DCONSTR ENTRY IN SUBCASE = %2. USER INFORMATION: IMPOSING CONFLICTING CONSTRAINTS ON A RESPONSE WILL IMPEDE OPTIMIZATION AND MUST BE AVOIDED.

516 *** USER FATAL MESSAGE 7143 (DOPR3H) 7143.1 DRESP1 ENTRY ID = %1 IS REFERENCED BY MORE THAN ONE DCONSTR ENTRY IN SUBCASE = %2. USER INFORMATION: THE IMPOSITION OF CONFLICTING CONSTRAINTS ON A RESPONSE WILL IMPEDE OPTIMIZATION AND MUST BE AVOIDED. *** USER FATAL MESSAGE 7144 (DOPR3H) 7144.0 SUBCASE ID = %1 IMPOSES A DCONSTR ON UNDEFINED DRESPI ID = %2. *** USE R FATAL MESSAGE 7145 (DOPR3H) 7145.0 THE SUBSPAN COMMAND IN SUBCASE %1 REFERENCES DRESP1 ENTRY ID = %2 WHICH INVOKES MULTIPLE RESPONSES. USER INFORMATION: DRESP1 ENTRIES REFERENCED BY A SUBSPAN REQUEST MUST BE A SCALAR QUANTITY. USER FATAL MESSAGE 7145 (DPSP23) *** 7145.1 OF THE %1 DRESP1 IN DRESP2/3 RESPONSE ID %2, ONLY %3 WERE FOUND TO BE DRSPAN RELATED. USER INFORMATION: ALL DRESP1 IN A DRSPAN RELATED DRESP2/3 SHOULD BE DRSPAN RELATED. *** USER FATAL MESSAGE 7145 (DPSP23) 7145.2 MISMATCH BETWEEN NUMBER OF DRESP1 IN DRESP2/3 RESPONSE ID %1 AND THE NUMBER OF DRSPAN RELATED DRESP1 FOUND FOR THIS DRESP2/3. USER INFORMATION: THIS MAY HAPPEN WITH INCONSISTENT OR REPEATED DRSPAN DEFINITIONS. *** USER FATAL MESSAGE 7146 (DOPR3H) 7146.0 SUBCASE ID = %1 REFERS TO AN UNDEFINED DRESP1 ID = %2 VIA A SUBSPAN SET COMMAND. *** USER FATAL MESSAGE 7147 (DPR3H1) 7147.0 THE DESOBJ COMMAND WITH ID = %1 REFERENCES A %2 ENTRY WHICH IN TURN REFERENCES DRESP1 ID = %3 WHICH INVOKES MULTIPLE RESPONSES. USER INFORMATION: THE DRESP1 ENTRIES INVOLVED IN DEFINING THE OBJECTIVE MUST BE SCALAR QUANTITIES. *** USER FATAL MESSAGE 7147 (DPR3H2) 7147.1 THE DESOBJ COMMAND WITH ID = %1 REFERENCES A %2 ENTRY WHICH IN TURN RE FERENCES DRESP2 ID = %3 WHICH INVOKES MULTIPLE RESPONSES. USER INFORMATION: THE DRESP2 ENTRY INVOLVED IN DEFINING THE OBJECTIVE MUST BE SCALAR QUANTITIES. *** USER FATAL MESSAGE 7148 (DOPR3H) 7148.0 THE DESOBJ COMMAND WITH ID = %1 REFERENCES A DRESP1

517 ENTRY WHICH INVOKES MULTIPLE RESPONSES. USER INFORMATION: DRESP1 ENTRIES INVOLVED IN DEFINING THE OBJECTIVE MUST BE SCALAR QUANTITIES. *** USER FATAL MESSAGE 7149 (DOPR3H) 7149.0 THE DESOBJ COMMA ND WITH ID = %1 REFERS TO AN UNDEFINED DRESPI ENTRY. USER INFORMATION: THE DESOBJ COMMAND REFERENCES A DRESP1 OR DRESP2 BULK DATA ENTRY WHICH MUST EXIST *** USER FATAL MESSAGE 7168 (DOPR3J) 7168.0 EQID %1 REFERENCED ON DRESP2 %2 IS NOT PRESENT ON A DEQATN ENTRY. *** USER FATAL MESSAGE 7168 (DOPR1Z) 7168.1 EQID %1 REFERENCED ON DVPREL2 %2 IS NOT PRESENT ON A DEQATN ENTRY. *** USER FATAL MESSAGE 7168 (DOPR1Z) 7168.2 EQID %1 REFERENCED ON DVCREL2 %2 IS NOT PRESENT ON A DEQATN ENTRY. *** USER FATAL MESSAGE 7168 (DOPR1Z) 7168.3 EQID %1 REFERENCED ON DVMREL2 %2 IS NOT PRESENT ON A DEQATN ENTRY. *** USER FATAL MESSAGE 7190 (DOPR1I) 7190.0 PTYPE %1 DEFINED ON A %2 %3 ENTRY CAN NOT BE FOUND ON A PROPERTY ENTRY. USER ACTION: DELETE THE %4 ENTRY OR INCLUDE AN ADDITIONAL PROPERTY ENTRY. *** USER FATAL MESSAGE 7190 (DOP1c1) 7190.1 PTYPE %1 DEFINED ON A DVPREL1 ENTRY CAN NOT BE FOUND ON A PROPERTY ENTRY. USER ACTION: DELETE THE DVPREL1 ENTRY OR INCLUDE AN ITIONAL PROPERTY ENTRY. ADD *** USER FATAL MESSAGE 7193 (DOPR1I) 7193.0 PID=%1 OF PTYPE %2 ON A %3 %4 ENTRY, IS NOT DEFINED ON A PROPERTY ENTRY. USER ACTION: CHECK %5 AND PROPERTY ENTRIES. *** USER FATAL MESSAGE 7196 (DOPR1I) 7196.0 FID=%1 SPECIFIED ON A %2 %3 ENTRY WITH PTYPE= %4 AND PID= %5 IS INVALID. USER ACTION: CORRECT THE FID FIELD ON THE %6 ENTRY. *** USER WARNING MESSAGE 7196 (DOPR1I) 7196.1 THE PROPERTY NAME 'D' SPECIFIED ON A %1 %2 ENTRY WILL BE IGNORED BECAUSE PW ELD ENTRY %3 DEFINES A RIGID BODY BEHAVIOR. *** USER FATAL MESSAGE 7196 (DOPR1I) 7196.2

518 PROPERTY VALUE vs. FREQUENCY TABLES NEED TO BE DESIGNED FOR AT LEAST TWO FREQUENCIES. USER ACTION: MAKE SURE THAT THE TABLE IS DESIGNED AT A MINIMUM OF TWO FRE QUENCIES. *** USER FATAL MESSAGE 7197 (DOPR1I) 7197.0 PTYPE=%1 PID=%2 PROPERTY NAME=%3 IS DEFINED MORE THAN ONCE BY %4 %5 ENTRY. USER INFORMATION: DESIGNED PROPERTIES ON %6 MUST BE UNIQUE. *** USER FATAL MESSAGE 7200 (MDG2PAT) 7200.0 INSUFFICIENT MEMORY TO GENERATE WELD ELEMENTS *** USER FATAL MESSAGE 7200 (MDG2PAT) 7200.1 PWELD/PFAST NOT DEFINED FOR CWELD/CFAST ELEMENT %1 *** USER FATAL MESSAGE 7200 (MDG2PAT) 7200.2 TOO MANY ELEMENTS IN PATCH FOR CWELD/CFAST ELEMENT %1 *** USER FATAL MESSAGE 7200 (MDG2PAT) 7200.3 GHA/GHB POINTS LAY OUTSIDE OF PATCH FOR CWELD/CFAST ELEMENT %1 *** USER FATAL MESSAGE 7200 (MDG2PAT) 7200.4 ANGLE OF %1 BETWEEN SHELL ELEMENTS FOR CWELD/CFAST %2 EXCEEDS THE LIMIT OF %3 *** USER FATAL MESSAGE 7200 (MDG2PAT) 7200.5 DISTANCE BETWEEN GS AND GA/B OF %1 FOR CWELD/CFAST %2 EXCEEDS THE LIMIT OF %3 *** USER INFORMATION MESSAGE 7200 (MDG2PAT) 7200.6 CWELD/CFAST ELEMENT %1 HAS %2 DUPLICATE GRIDS BETWEEN THE TWO PATCHES *** USER FATAL MESSAGE 7200 (MDG2PAT) 7200.7 INSUFFICIENT MEMORY FOR CWELD/CFAST ELEMENT PROCESSING *** USER FATAL MESSAGE 7200 (MDG2SPPD) 7201.0 NO SHELL ELEMENT FOUND FOR CWELD/CFAST ELEMENT %1 DEFINED AS PARTPAT USING PID %2 *** USER FATAL MESSAGE 7200 (EPCSMD) 7201.1 CWELD/CFAST ELEMENT %1 CONNECTS TO GRID %2 WHICH HAS A DISPLACEMENT COORDINATE SYSTEM WHICH IS NOT CURRENTLY SUPPORTED *** USER FATAL MESSAGE 7200 (MDG2SPPD) 7201.2 CWELD/CFAST ELEMENT %1 CANNOT BE FORMED USING PARTPAT AS ONLY ELEMENT %2 MEETS THE PROJECTION AND PID CRITERIA

519 *** USER FATAL MESSAGE 7200 (MDG2WREFD) 7202.0 CWELD/CFAST ELEMENT %1 HAS ZERO LENGTH VECTOR *** USER FATAL MESSAGE 7220 (DOPR3T) 7220.0 ON %1 entry ID = %2, DVPREL1 ID = %3 DOES NOT REFERENCE AN EXISTING DVPREL1 ENTRY. *** USER FATAL MESSAGE 7220 (DOPR3T) 7220.1 %1 ENTRY ID = %2 SPECIFIES A DNODE GRID ID =%3 AND COMPONENT =%4 COMBINATION WHICH DOES NOT EXIST. USER ACTION: MAKE SURE THE GRID AND COMPONENT ARE DEFINED IN THE ANALYSIS MODEL. *** USER FATAL MESSAGE 7220 (DOPR3T) 7220.2 ON %1 entry ID = %2, DVCREL1 ID = %3 DOES NOT REFERENCE AN EXISTING DVCREL1 ENTRY. *** USER FATAL MESSAGE 7220 (DOPR3T) 7220.3 ON %1 entry ID = %2, DVMREL1 ID = %3 DOES NOT REFERENCE AN EXISTING DVMREL1 ENTRY. *** USER FATAL MESSAGE 7220 (DOPR3T) 7220.4 ON %1 entry ID = %2, DVPREL2 ID = %3 DOES NOT REFERENCE AN EXISTING DVPREL2 ENTRY. *** USER FATAL MESSAGE 7220 (DOPR3T) 7220.5 ON %1 entry ID = %2, DVCREL2 ID = %3 DOES NOT REFERENCE AN EXISTING DVCREL2 ENTRY. 220 (DOPR3T) *** USER FATAL MESSAGE 7 7220.6 ON %1 entry ID = %2, DVMREL2 ID = %3 DOES NOT REFERENCE AN EXISTING DVMREL2 ENTRY. *** user FATAL MESSAGE 7251 (DOPR4) 7251.0 THERE ARE NO PROPERTY OR SHAPE VARIABLES SPECIFIED IN THE DESIGN MODEL. USER INFORMATION: PROPERTY VARIABLES ARE SPECIFIED ON DVPREL1 AND DVPREL2 BULK DATA ENTRIES. SHAPE VARIABLES ARE SPECIFIED ON DVGRID ENTRIES OR INPUT DIRECTLY. *** SYSTEM FATAL MESSAGE 7300 (FMSFIO) 7300.0 FORTRAN UNIT%1 USED FOR FMS HAS BEEN CLOS ED AND DELETED. *** SYSTEM FATAL MESSAGE 7301 (FMSFIO) 7301.0 CANNOT OPEN FORTRAN UNIT %1 USED FOR FMS. *** SYSTEM FATAL MESSAGE 7301 (FMSFIO) 7301.1 CANNOT CLOSE FORTRAN UNIT %1 USED FOR FMS. SYSTEM FATAL MESSAGE 7302 (LNNP1AD) *** 7302.0 ORDER OF EIGENPROBLEM IS NON - POSITIVE

520 NORDER: %1 *** SYSTEM FATAL MESSAGE 7303 (LNNP1AD) 7303.0 INSUFFICIENT STORAGE FOR BLOCK SHIFTED LANCZOS. WORKSPACE AVAILABLE = %1 WORKSPACE REQUIRED = %2 *** SYSTEM FATAL MESSAGE 7304 (LNNP1AD) 7304.0 IMPROPER PARAMETER SPECIFICATION FOR EIGENPROBLEM DESCRIPTION OF PROBLEM TYPE NOT RECOGNIZED INPUT: %1 *** SYSTEM FATAL MESSAGE 7304 (LNNP1AD) 7304.1 IMPROPER PARAMETER SPECIFICATION FOR EIGENPROBLEM LEFT END POINT EQUALS RIGHT END POINT INPUT: %1 *** SYSTEM FATAL MESSAGE 7304 (LNNP1AD) 7304.2 IMPROPER PARAMETER SPECIFICATION FOR EIGENPROBLEM DESCRIPTION OF WHICH EIGENVALUES TO FIND NOT RECOGNIZED INPUT: %1 *** SYSTEM FATAL MESSAGE 7304 (LNNP1AD) 7304.3 IMPROPER PARAMETER SPECIFICATION FOR EIGENPROBLEM HIGHEST EIGENVALUES REQUESTED IN AN INTERVAL SPANNING ZERO - OR - HIGHEST EIGENVALUES REQUESTED IN A NON FINITE INTERVAL - - OR INTERVAL ALL EIGENVALUES REQUESTED IN A NON FINITE WHICH : %1 LEFT END POINT : %2 RIGHT END POINT: %3 *** USER INFORMATION MESSAGE 7304 (LNNP2CD) 7304.4 THE REQUESTED FREQUENCY RANGE EXCLUDES PART OF A CLUSTER OF EIGENVALUES. THIS MAY PRODUCE UNSTABLE RESULTS IN FREQUENCY OR TRANSIENT RESPONSE. THE NUMBER OF ROOTS HAS BEEN INCREASED TO INCLUDE THE ENTIRE CLUSTER. REQUESTED NUMBER OF ROOTS: %1 ADDITIONAL ROOTS IN CLUSTER: %2 *** USER WARNING MESSAGE 7304 (LNNP2CD) 7304.5 THE UPPER END OF THE FREQUENCY RANGE CUTS INTO A CLUSTE R OF EIGENVALUES. FREQUENCY OR TRANSIENT RESPONSE USING THIS MODAL ANALYSIS MAY PRODUCE UNSTABLE RESULTS.

521 REQUESTED NUMBER OF ROOTS: %1 ADDITIONAL ROOTS IN CLUSTER: %2 USER ACTION: INCREASE ND ON THE EIGRL CARD BY THE SPECIFIED OOTS, SPECIFY V2 AND LEAVE ND NUMBER OF ADDITIONAL R BLANK, OR SET SYSTEM(509)=1. *** SYSTEM FATAL MESSAGE 7305 (LNNP1AD) 7305.0 NOT ENOUGH TIME TO BEGIN EIGENANALYSIS *** USER FATAL MESSAGE 7306, 7306.0 ATTEMPT TO PUNCH MORE THAN 99999 DMIG ENTRIES - CONTINUATION FIELD OVERFLOW. *** USER FATAL MESSAGE 7307, 7307.0 ILLEGAL VALUE FOR PARAMETER P4. DMIG TYPOUT = %1 REQUESTED FOR INPUT MATRIX OF TYPE %2 *** USER FATAL MESSAGE 7307, 7307.1 ILLEGAL VALUE FOR PARAMETER P13. BLANK NAME NOT ALLOWED. *** USER INFORMATION MESSAGE 7308 (NL2NON) 7308.0 MODIFIED NOLIN1 REQUESTED BY USER *** SYSTEM FATAL MESSAGE 7309. 7309.0 NLEMGD CALLED FOR ELEMENT TYPE =%1 SHOULD NOT HAVE HAPPENED. *** USER INFORMATION MESSAGE 7310 (OFPH09) 7310.0 REFERENCE GRID %1 WAS NOT FOUND. ORIGIN OF ASSEMBLY BASIC COORDINATE SYSTEM WILL BE USED AS REFERENCE LOCATION. *** USER INFORMATION MESSAGE 7310 (VECPRN) 7310.1 ORIGIN OF SUPERELEMENT BASI C COORDINATE SYSTEM WILL BE USED AS REFERENCE LOCATION. *** USER INFORMATION MESSAGE 7310 (VECPRN) 7310.2 REFERENCE GRID %1 WAS NOT FOUND FOR VECPLOT OPERATION. ORIGIN OF SUPERELEMENT BASIC COORDINATE SYSTEM WILL BE USED AS REFERENCE LOCATION. *** USER INFORMATION MESSAGE 7310 (VECPRN) 7310.3 ORIGIN OF SUPERELEMENT BASIC COORDINATE SYSTEM WILL BE USED AS REFERENCE LOCATION. RESULTANTS ABOUT ORIGIN OF SUPERELEMENT BASIC COORDINATE SYSTEM IN SUPERELEMENT BASIC SYSTEM COORDINATES. *** USER INFORMATION MESSAGE 7310 (VECPRN) 7310.4 REFERENCE GRID %1 WAS NOT FOUND FOR VECPLOT

522 OPERATION. ORIGIN OF SUPERELEMENT BASIC COORDINATE SYSTEM WILL BE USED AS REFERENCE LOCATION. RESULTANTS ABOUT ORIGIN OF SUPERELEMENT BASIC PERELEMENT BASIC SYSTEM COORDINATE SYSTEM IN SU COORDINATES. *** USER INFORMATION MESSAGE 7310 (VECPRN) 7310.5 ORIGIN OF ASSEMBLY BASIC COORDINATE SYSTEM WILL BE USED AS REFERENCE LOCATION. *** USER INFORMATION MESSAGE 7310 (VECPRN) 7310.6 REFERENCE GRID %1 WAS NOT FOUND FOR VECPLOT OPERATION. ORIGIN OF ASSEMBLY BASIC COORDINATE SYSTEM WILL BE USED AS REFERENCE LOCATION. *** USER INFORMATION MESSAGE 7311 7311.0 PID=%1 REQUEST PARALLEL PROCESSING FOR PCOPY MODULE. RS AVAILABLE=%2 NUMBER OF PROCESSO NUMBER OF PROCESSORS APPLIED=%3 *** USER FATAL MESSAGE 7312 (RDINIC) 7312.0 SCR300 SHOULD NOT BE USED AS A DBSET NAME, IT IS A SUBSET OF SCRATCH DBSET. *** USER INFORMATION MESSAGE 7313 (REIGL0) 7313.0 DESPITE NEGATIVE SYSTEM CELL 199 VALUE %1 CHOSEN MASS MATRIX WILL NOT BE LOADED IN MEMORY. DECREASE ABSOLUTE VALUE OF MASSBUF OR INCREASE MEMORY *** USER INFORMATION MESSAGE 7314 (REIGL0) 7314.0 MASS MATRIX IS NOT LOADED IN MEMORY WITH %1 GINO FFERS. BU EITHER INCREASE MAGNITUDE OF SYSTEM CELL 199 OR SET TO ZERO TO FORCE IN MEMORY *** USER INFORMATION MESSAGE 7315 (REIGL0) 7315.0 MASS MATRIX IS FORCED IN MEMORY PER USER REQUEST MEMORY REDUCED BY %1 WORDS USER INFORMATION MESSAGE 7316 (REIGL0) *** 7316.0 MASS MATRIX IS LOADED IN MEMORY PER USER REQUEST WITH %1 GINO BUFFERS. MEMORY REDUCED BY %2 WORDS *** SYSTEM FATAL MESSAGE 7317. 7317.0 INCORRECT NUMBER OF WORDS BEING TRANSMITTED FROM PHASE - 1 ROUTINE FOR ELE MENT ID =%1 WORDS THIS CALL =%2 ENTRY SIZE SHOULD =%3 *** SYSTEM FATAL MESSAGE 7318. 7318.0 PREVIOUS ELEMENT - ID TO ID =%1 DID NOT OUTPUT CORRECT

523 NUMBER OF PHASE - 1 WORDS. *** SYSTEM FATAL MESSAGE 7319. 7319.0 INCORRECT CALL MADE TO SDR2WT UTILITY FOR ELEMENT ID =%1, PARM =%2 ***SYSTEM FATAL MESSAGE 7321. 7320.0 INCONSISTENT DATA DETECTED BETWEEN THE OES1A LAMINATE STRAIN AND OEF1A ELEMENT FORCE DATABLOCKS ***USER INFORMATION MESSAGE 7321 7321.0 DATA RECOVERY FOR SUPERELEMENT %1 IS NOW INITIATED. *** USER FATAL MESSAGE 7322 (SEP2D) 7322.0 SUBCASES FOR SUPERELEMENT %1 CONTAIN A MIXTURE OF - ZERO LOAD SEQUENCE NUMBERS. ZERO AND NON *** USER FATAL MESSAGE 7323 (SEP2D) 7323.0 SUBCASES FOR SUPERELEMENT %1 HAS A LOAD SEQUENCE NUMBER = %2 WHICH IS OUT OF ORDER. *** USER FATAL MESSAGE 7324 (SEP2D) 7324.0 SUBCASES FOR SUPERELEMENT %1 HAS A LOAD SEQUENCE NUMBER =%2 WHICH IS GREATER THAN NUMBER OF LOADS. *** USER INFORMATION MESSAGE 7325 7325.0 PROCESSING OF RESIDUAL STRUCTURE IS NOW INITIATED. *** USER INFORMATION MESSAGE 7325 7325.1 PROCESSING OF SUPERELEMENT %1 IS NOW INITIATED. *** USER INFORMATION MESSAGE 7326 7326.0 %1 SPARSE FACTOR MATRIX %2 IS MIGRATED TO V68 SPARSE FACTOR MATRIX FORMAT. *** SYSTEM FATAL MESSAGE 7327 (USTSIL) 7327.0 INCONSISTENT MAPPING DETECTED BETWEEN SIL TABLE AND USET RECORD. *** SYSTEM FATAL MESSAGE 7327 (FIXSIL) 7327.1 INCONSISTENT MAPPING LENGTH DETECTED IN SILD RECORD. *** SYSTEM FATAL MESSAGE 7328 (USTSIL) 7328.0 SET %1 CANNOT BE LOCATED IN USET MAPPING RECORD. *** SYSTEM WARNING MESSAGE 7329 (MTGN12) 7329.0 OND TO AVERAGE STRING LENGTH GIVEN DOES NOT CORRESP THE OTHER PROPERTIES OF THE MATRIX. *** USER WARNING MESSAGE 7330 (TIMTS3) 7330.0 UNABLE TO FIND A MATCHING MACH AND/OR KONFIG! MACHINE DESCRIPTION SECTION FILLED WITH BLANKS. *** SYSTEM FATAL MESSAGE 7331 (FMSGET) 7331.0 OUTPUT RECORD NUMBER %1 GIVEN RECORD TYPE %2 IS MISMATCHED FOR %3 DATA RECORD.

524 %4%5 *** SYSTEM FATAL MESSAGE 7333 (FMSPUT) 7331.1 INPUT RECORD NUMBER %1 HAS EXCEEDED TOTAL NUMBER OF RECORDS DEFINED ON THE HEADER. CONTENT OF HEADER RECORD: "%2"%3 *** SYSTEM FATAL MESSAGE 7332 (FMSGET) 7332.0 OUTPUT RECORD NUMBER %1 REQUESTED NUMBER OF DATA %2 HAS EXCEEDED RECORD SIZE FOR %3 DATA RECORD. %4%5 *** SYSTEM FATAL MESSAGE 7332 (FMSGET) 7333.0 OUTPUT RECORD NUMBER %1 HAS EXCEEDED TOTAL NUMBER OF RECORDS DEFINED ON HEADER. CONTENT OF HEADER RECORD: %2%3 *** SYSTEM FATAL MESSAGE 7334 (FMSGET) 7334.0 END OF FILE HIT WHILE READING RECORD NUMBER %1 OF %2 DATA RECORD. RD: CONTENT OF HEADER RECO %3%4 *** SYSTEM FATAL MESSAGE 7335 (FMSGET) 7335.0 HEADER TYPE %1 MAY NOT HAVE DATA RECORDS CONTENT OF HEADER RECORD: %2%3 *** SYSTEM FATAL MESSAGE 7336 (FMSPUT) 7336.0 INVALID DATA TYPE FOUND IN HEADER, TYPE = %1 CONTENT OF HEADER RECORD: "%2"%3 *** SYSTEM FATAL MESSAGE 7337 (FMSPUT) 7337.0 INPUT RECORD NUMBER %1 GIVEN RECORD TYPE %2 IS MISMATCHED FOR %3 DATA RECORD. "%4"%5 SYSTEM FATAL MESSAGE 7338 (FMSPUT) *** 7338.0 INPUT RECORD NUMBER %1 GIVEN AMOUNT OF DATA %2 IS MISMATCHED FOR %3 DATA RECORD. CONTENT OF HEADER RECORD: "%4"%5 *** USER FATAL MESSAGE 7339 (NLTINT) 7339.0 METHOD = AUTO OR TSTEP ON THE TSTEPNL BULK DATA ENTR Y IS SPECIFIED ALONG WITH CBUSH1D ELEMENTS(S). THIS IS NOT ALLOWED. USER ACTION: SPECIFY METHOD = ADAPT ON THE TSTEPNL ENTRY.

525 *** USER FATAL MESSAGE 7339 (NLTINT) 7339.1 METHOD = AUTO OR TSTEP ON THE TSTEPNL BULK DATA ENTRY IS SPECIFIED ALONG WITH CBUSH ELEMENTS(S) AND EITHER PBUSHT OR PARAM LGDISP=1. THIS IS NOT ALLOWED. USER ACTION: SPECIFY METHOD = ADAPT ON THE TSTEPNL ENTRY. *** SYSTEM FATAL MESSAGE 7340 (LNNHERR) 7340.0 ERROR HANDLER (LNNHERR) USED IMPROPERLY MODE = %1 FROM %2 *** SYSTEM FATAL MESSAGE 7340 (LNNHERR) 7340.1 ERROR HANDLER (LNNHERR) MESSAGE LIMIT EXCEEDED ONE OR MORE MESSAGES SUPPRESSED *** SYSTEM FATAL MESSAGE 7340 (LNNHERR) 7340.2 WARNING REPORTED BY SUBROUTINE %1 (IER= %2) USER INFORMATION:%3 *** SYSTEM FATAL MESSAGE 7340 (LNNHERR) 7340.3 INPUT ARGUMENT ERROR REPORTED BY SUBROUTINE %1 (IER= %2) USER INFORMATION:%3 *** SYSTEM FATAL MESSAGE 7340 (LNNHERR) 7340.4 INPUT ARGUMENT ERROR REPORTED BY SUBROUTINE %1 %2 WORDS OF WORKING STORA GE NEEDED (IER= %3) USER INFORMATION:%4 *** SYSTEM FATAL MESSAGE 7340 (LNNHERR) 7340.5 PROCESS ERROR REPORTED BY SUBROUTINE %1 (IER= %2) USER INFORMATION:%3 *** SYSTEM FATAL MESSAGE 7340 (LNNHERR) 7340.6 ABOVE CALLED BY SUBROUTINE %1 (IER= %2) USER INFORMATION:%3 *** SYSTEM FATAL MESSAGE 7340 (LNNHERR) 7340.7 ABOVE CALLED BY SUBROUTINE %1 ERROR WAS UNEXPECTED (IER =%2) USER INFORMATION:%3 *** SYSTEM FATAL MESSAGE 7340 (LNNRIGL) 7340.8 STAGE ERROR. *** SYSTEM FATAL MESSAGE 7340 (LNNRIGL) 7340.9 ILLEGAL PROBLEM TYPE SPECIFICATION. *** SYSTEM FATAL MESSAGE 7340 (LNNRIGL) 7340.10 ILLEGAL FINITE ENDPOINTS. *** SYSTEM FATAL MESSAGE 7340 (LNNRIGL) 7340.11 REQUESTED HIGHEST MODES IN INTERVAL SPANNING ZERO. *** SYSTEM FATAL MESSAGE 7340 (LNNRIGL) 7340.12

526 INSUFFICIENT DYNAMIC MEMORY FOR FACTORIZATION. *** SYSTEM FATAL MESSAGE 7340 (LNNRIGL) 7340.13 INTERNAL ERROR DURING FACTORIZATION. *** SYSTEM FATAL MESSAGE 7340 (LNNRIGL) 7340.14 NOT ENOUGH TIME TO GET STARTED. *** SYSTEM FATAL MESSAGE 7340 (LNNRIGL) 7340.15 STARTING BLOCK I/O ERROR. *** SYSTEM FATAL MESSAGE 7340 (LNNRIGL) 7340.16 AL SAVE/RESTART I/O ERROR ON FACTORIZATION SEQUENTI FILES. *** SYSTEM FATAL MESSAGE 7340 (LNNRIGL) 7340.17 I/O ERROR ON FACTORIZATION WORD ADDRESSABLE FILES. *** SYSTEM FATAL MESSAGE 7340 (LNNRIGL) 7340.18 I/O ERROR OPENING FIRST SEQUENTIAL FILE. SYSTEM FATAL MESSAGE 7340 (LNNRIGL) *** 7340.19 I/O ERROR OPENING SECOND SEQUENTIAL FILE. *** SYSTEM FATAL MESSAGE 7340 (LNNRIGL) 7340.20 I/O ERROR OPENING DIRECT ACCESS FILE. *** SYSTEM FATAL MESSAGE 7340 (LNNRIGL) 7340.21 INSUFFICIENT STORAGE ENCOUNTERED BY SUBROUTINE HDSER1. *** SYSTEM FATAL MESSAGE 7340 (LNNRIGL) 7340.22 TRIDIAGONAL QL DID NOT CONVERGE. *** SYSTEM FATAL MESSAGE 7340 (LNNRIGL) 7340.23 NUMBER OF COMPUTED EIGENVALUES EXCEED ALLOCATED STORAGE. *** SYSTEM FATAL MESSAGE 7340 (LNNRIGL) 7340.24 I/O ERROR ENCOUNTERED DURING HDSER1. *** SYSTEM FATAL MESSAGE 7340 (LNNRIGL) 7340.25 SVD QL DID NOT CONVERGE. *** SYSTEM FATAL MESSAGE 7340 (LNNRIGL) 7340.26 GRAM - SCHMIDT DID NOT CONVERGE. *** SYSTEM FATAL MESSAGE 7340 (LNNRIGL) 7340.27 -- REPEATED SINGULAR MATRIX - POSED PROBABLY ILL PROBLEM. *** SYSTEM FATAL MESSAGE 7340 (LNNRIGL) 7340.28 NUMBER OF TRUST REGION EXCEED ALLOCATED STORAGE. *** SYSTEM FATAL MESSAGE 7340 (LNNRIGL) 7340.29 FACTORIZATION RESTORATION ERROR. *** SYSTEM FATAL MESSAGE 7340 (LNNRIGL) 7340.30

527 INCONSISTENT TREATMENT OF NUMBER OF EIGENVALUES IN FINITE INTERVAL. *** SYSTEM FATAL MESSAGE 7340 (LNNRIGL) 7340.31 COULD NOT COMPUTE ZERO EIGENVALUES FOR A BUCKLING CASE. *** SYSTEM FATAL MESSAGE 7340 (LNNRIGL) 7340.32 I/O ERROR CLOSING FIRST SEQUENTIAL FILE. *** SYSTEM FATAL MESSAGE 7340 (LNNRIGL) 7340.33 I/O ERROR CLOSING SECOND SEQUENTIAL FILE. *** SYSTEM FATAL MESSAGE 7340 (LNNRIGL) 7340.34 UNKNOWN INTERNAL ERROR OCCURRED. *** USER FATAL MESSAGE 7341 (SEPMA1) 7341.0 THE SEIDA FIELD ON THE %1 BULK DATA ENTRY REFERENCES A NON PARTITIONED SUPERELEMENT ID=%2. - *** USER FATAL MESSAGE 7342 (PREMAT) 7342.0 THE FIRST POINT (X1,Y1) SPECIFIED ON THE TABLES1 BULK DATA ENTRY ID = %1 IS NOT LOCATED - STRAIN CURVE. AT THE ORIGIN OF THE STRESS *** USER FATAL MESSAGE 7343, 7343.0 THE ERROR VALUE FOR RBE3 ELEMENT %1 IS %2, WHICH EXCEEDS THE TEST CRITERION OF %3. USER INFORMATION: THE RECIPROCAL CONDITION NUMBER OF THE EQUILIBRIUM MATRIX IS %4. USER ACTION: ADD MORE DOFS TO THE CONNECTED POINTS TO 6 RIGID BODY MODES INSURE THAT THEY CAN CONSTRAIN ALL OF THE ELEMENT. *** SYSTEM WARNING MESSAGE 7344 (DFMFRD) 7344.0 IFLAG =%1 PIVOT%2 HAS DIFFERENT SIGN FROM THE PREVIOUS ONE *** SYSTEM FATAL MESSAGE 7345 (FIXSIL) 7345.0 - SET SIL ID%1 CANNOT BE LOCATED IN SILD MAPPING RECORD. G *** SYSTEM WARNING MESSAGE 7346 (SEPLT3) 7346.0 SUPERELEMENT ID = %1 CONTAINS INVALID DATA INFORMATION. (DATA TYPE = %2 COLUMN SIZE = %3 LUSET = %4 GSIZE= %5) *** SYSTEM WARNING MESSAGE 7347 (SEPLT3) 7347.0 ROW NUMBER %1 EXCEEDED MAXIMIUM SIZE %2 *** SYSTEM FATAL MESSAGE 7348 7348.0 NUMBER OF GRID ID - S CONTAINED IN TEMPERATURE SET %1 EXCEEDS NUMBER OF GRID POINTS DEFINED *** SYSTEM FATAL MESSAGE 7349 7349.0 TEMPERATURE TYPE =%1

528 IS NOT YET IMPLEMENTED. ELEMENT TYPE CONCERNED = %2 *** USER FATAL MESSAGE 7350. 7350.0 TEMPP2 DATA MAY NOT BE USED FOR ELEMENTS OF THE TYPE WHICH ID = %1 IS OF. *** SYSTEM INFORMATION MESSAGE 7353 (PXINIT) 7353.0 PID =%1 REQUEST INITIALIZA TION THE EXECUTIVE AREAS FOR %2 PARALLEL PROCESSES *** SYSTEM WARNING MESSAGE 7354 7354.0 IN TIME_TEST_4 UNABLE TO FIND A MATCHING MACH AND/OR KONFIG! MACHINE DESCRIPTION SECTION FILLED WITH BLANKS. *** SYSTEM FATAL MESSAGE 7355 (ISHELL) 7355.1 ISHELL PROCESSING FAILED. FACILITY NOT AVAILABLE ON THIS PLATFORM. PROGRAM NAME IS '%1', TIMEOUT (SYS275) VALUE IS %2. *** USER FATAL MESSAGE 7355 (ISHELL) 7355.2 ISHELL PROCESSING FAILED. NO PROGRAM NAME SPECIFIED OR PROGRAM NAME IS BLANK. PROGRAM NAME IS '%1', TIMEOUT (SYS275) VALUE IS %2. *** USER FATAL MESSAGE 7355 (ISHELL) 7355.3 ISHELL PROCESSING FAILED. REQUESTED PROGRAM COULD NOT BE FOUND. PROGRAM NAME IS '%1', TIMEOUT (SY S275) VALUE IS %2. *** SYSTEM FATAL MESSAGE 7355 (ISHELL) 7355.4 ISHELL PROCESSING FAILED. SIGNAL HANDLING FAILED WHILE ATTEMPTING TO RUN SPECIFIED PROGRAM. PROGRAM NAME IS '%1', TIMEOUT (SYS275) VALUE IS %2. *** SYSTEM FATAL MESSAGE 7355 (ISHELL) 7355.5 ISHELL PROCESSING FAILED. UNABLE TO CREATE A NEW PROCESS. SYSTEM LIMITS MAY HAVE BEEN EXCEEDED. PROGRAM NAME IS '%1', TIMEOUT (SYS275) VALUE IS %2. *** USER FATAL MESSAGE 7355 (ISHELL) 7355.6 ISHELL PROCESSING FAILED. PROGRAM HAS TIMED OUT. PROGRAM NAME IS '%1', TIMEOUT (SYS275) VALUE IS %2. *** SYSTEM FATAL MESSAGE 7355 (ISHELL) 7355.7 ISHELL PROCESSING FAILED. UNEXPECTED STATUS RETURNED WHILE WAITING FOR PROGRAM COMPLETION. PROGRAM NAME IS '%1', TI MEOUT (SYS275) VALUE IS %2. *** SYSTEM FATAL MESSAGE 7355 (ISHELL) 7355.8

529 ISHELL PROCESSING FAILED. ACCESS DENIED TO REQUESTED PROGRAM OR IT IS NOT EXECUTABLE. PROGRAM NAME IS '%1', TIMEOUT (SYS275) VALUE IS %2. *** SYSTEM FATAL MESSAGE 7355 (ISHELL) 7355.9 ISHELL PROCESSING FAILED. UNABLE TO ACQUIRE DYNAMIC MEMORY TO HOLD COMPLETE COMMAND (MALLOC FAILED). PROGRAM NAME IS '%1', TIMEOUT (SYS275) VALUE IS %2. *** SYSTEM FATAL MESSAGE 7355 (ISHELL) 7355.10 CESSING FAILED. ISHELL PRO UNABLE TO CREATE COMMUNICATIONS PIPE WITH REQUESTED PROGRAM. PROGRAM NAME IS '%1', TIMEOUT (SYS275) VALUE IS %2. *** SYSTEM WARNING MESSAGE 7355 (ISHELL) 7355.11 ISHELL PROCESSING FAILED. REFINED FAILED. UNABLE TO REFINE WITH POLYNAST. PROGRAM NAME IS '%1', TIMEOUT (SYS275) VALUE IS %2. *** SYSTEM FATAL MESSAGE 7355 (ISHELL) 7355.12 ISHELL PROCESSING FAILED. UNKNOWN ERROR ENCOUNTERED WHILE RUNNING PROGRAM. PROGRAM NAME IS '%1', T IMEOUT (SYS275) VALUE IS %2. *** SYSTEM FATAL MESSAGE 7356 (GICOMD) 7356.0 SPLINE %1 FAILED TO CONVERGE IN EIGEN ANALYSIS. UNABLE TO OBTAIN A LEAST SQUARES PLANE. USER ACTION: USE TPS METHOD. *** SYSTEM INFORMATION MESSAGE 7357 (GICOMD) 7357.0 SPLINE %1 IS COMPRISED OF A SET OF COPLANAR GRID POINTS. TPS METHOD REVERTS TO IPS FOR THIS CASE. *** USER FATAL MESSAGE 7358 (GICOMD) 7358.0 SPLINE %1 IS COMPRISED OF A SET OF COLLINEAR GRID POINTS. USER ACTION: MODIFY THE GRIDS SO THEY ARE NOT COLLINEAR. *** SYSTEM INFORMATION MESSAGE 7358 (GICOMD) 7358.1 SPLINE %1 IS COMPRISED OF A SET OF COLLINEAR GRID POINTS. USER INFORMATION: SMOOTHING PARAMETER DZ MAY ALLOW SOLUTION. *** USER FATAL MESSAGE 7359 (GICOMD) 7359.0 SPLINE %1 CONNECTS TO ONLY ONE STRUCTURAL GRID POINT. USER ACTION: ADD GRID POINTS OR USE SPLINE2 WITH COUPLED ROTATIONS. *** USER INFORMATION MESSAGE 7360 (DOIT) 7360.0 UNABLE TO PROCESS USER SPECIFIED EXTENSION.

530 COMMAND PROCESSOR NOT FOUND FOR EXTENSION '%1' PROCESSOR NAME IS '%2'. *** USER INFORMATION MESSAGE 7361 (DOIT) 7361.0 UNABLE TO ACQUIRE DYNAMIC MEMORY TO HOLD EXTENSIONS TABLE. SPACE REQUESTED IS %1 BYTES. INTERNAL TABLE WILL BE USED. *** USER INFORMATION MESSAGE 7362 (DOIT) 7362.0 THE COMPLETE ISHELL COMMAND IS: %1 *** SYSTEM FATAL MESSAGE 7363 (FGNFRD) 7363.0 ERROR READING THE FACTOR MATRIX WITH %1. REQUESTED %2 COLUMNS, READ %3 COLUMNS. LE BY SETTING USER ACTION: DESELECT THE SUPERMODU PARAM,SM,NO IN THE BULK DATA SECTION. *** SYSTEM FATAL MESSAGE 7364 (STATICS) 7364.0 THE SUPERMODULES ARE NOT AVAILABLE WHEN THE FULL DMAP IS EXECUTED ON EACH NODE. USER ACTION: SET SLAVE=YES ON THE SUBMITTAL LINE. *** SYSTEM WARNING MESSAGE 7365 (DISOFN) 7365.0 ENCOUNTERED BAD KEY VALUE WHILE READING %1 FROM PARALLEL NODE %2 USER INFORMATION: 1. CHECK TO SEE IF FILE IS CORRECT OFP FILE TYPE. PROGRAMMERS INFORMATION: KEY = %3 *** SYSTEM WARNING MESSAGE 7366 ( DISOFG) 7366.0 UNABLE TO TRANSFER DATABLOCK %1 FROM PARALLEL NODE %2 UNSUPPORTED OFP FILE TYPE %3 *** USER FATAL MESSAGE 7367 (MKCNT) 7367.0 THE CONTROL DEVICE DEFINED ON AE%1 ENTRY ID = %2 SPECIFIES LABEL INTERCPT. USER INFORMATION: THE LABEL INTERCPT IS A RESERVED LABEL AND CANNOT BE USED FOR ANY CONTROL DEVICES. USER ACTION: RENAME THE LABEL ON CONTROL DEVICE AE%3 ENTRY ID= %4. *** USER WARNING MESSAGE 7368 (ADGDJX) 7368.0 W2GJ WEIGHTING MATRIX HAS %1 COLU MNS. USER INFORMATION: ONLY ITS FIRST COLUMN IS BEING USED AS THE (SINGLE) INTERCEPT EFFECT IN THE DOWNWASH MATRIX. *** USER FATAL MESSAGE 7369 (ADGDJX) 7369.0 W2GJ WEIGHTING MATRIX IS OF SIZE %1 COLUMN(S) BY %2 ROWS.

531 USER INFORMATION: ITS NUMBER OF ROWS SHOULD BE EQUAL - SET SIZE %3. TO THE J USER ACTION: INPUT THE W2GJ WEIGHTING MATRIX WITH ITS NUMBER OF ROWS EQUALS TO %4. *** USER FATAL MESSAGE 7370 (CEAD) 7370.0 INVALID METHOD = "%1" IS SPECIFIED FOR THE 4TH PARAMETER OF THE CEAD MODULE. USER INFORMATION: VALID METHODS ARE "CLAN", "HESS", AND "SVD". *** SYSTEM FATAL MESSAGE 7371 (FREQ) 7371.0 INSUFFICIENT SPACE FOR PROCESSOR MAP AND PERFORMANCE DATA. MCORE = %1, NUMBER OF PROCESSORS = %2. USER ACTION: LIMIT NUMBER OF PROCESSORS PARTICIPATING IN THE RUN TO %3. *** USER FATAL MESSAGE 7372 (APD1) 7372.0 THE DATA DEFINED ON THE AEFACT ENTRY ID = %1 ASSOCIATED WITH CAERO%2 ENTRY ID = %3 IS INCONSISTENT. USER INFORMATION: THE MINIMUM AND MAXIMUM PARAMETRIC COORDINATES CANNOT BE EQUAL. *** SYSTEM FATAL MESSAGE 7373 (MKCSTA) 7373.0 COORDINATE SYSTEM DATA BLOCKS ARE OF INCOMPATIBLE PRECISIONS TO BE MERGED. STRUCTURAL CSTM IS %1 PRECISION. AERO CSTM IS %2 PRECISION. *** SYSTEM FATAL MESSAGE 7374 (MKCSTA) 7374.0 BOTH INPUT COORDINATE SYSTEMS AND OUTPUT COORDINATE SYSTEMS DATA BLOCKS ARE NOT PURGED. USER INFORMATION: IF THE OUTPUT COORDINATE SYSTEMS DATABLOCK IS NOT PURGED, ONE OF THE INPUT DATA BLOCKS MUST BE PURGED. *** SYSTEM FATAL MESSAGE 7175 (MKCSTA) 7375.0 STRUCTURAL CSTM SHOULD BE ADDED ONLY ONCE TO CSTMA. *** SYSTEM FATAL MESSAGE 7376 (MKCSTA) 7376.0 COORDINATE SYSTEM ID %1 WAS FOUND IN BOTH COORDINATE SYSTEMS TABLES BUT DOES NOT DESCRIBE THE SAME COORDINATE SYSTEM. USER INFORMATION: COORDINATE SYSTEMS TABLES TO MERGE WITH CONFLICTED COORDINATE SYSTEMS IDS ARE NOT HANDLE AT THIS TIME. USER ACTION: INPUT COORDINATE SYSTEM IDS TO ALLOW UNIQUESS AMONG AREO AND STRUCTURAL MODELS COMBINED *** SYSTEM FATAL MESSAGE 7377 (ADCSTM) 7377.0 GINO FILE TO STORE %1 RECORD IS NOT PROVIDED. PROGRAMMER INFORMATION: ADCSTM UTILITY IS CALLED BY

532 %2 PROGRAMMER ACTION: PRIOR TO CALL THE ADCSTM UTILITY, PROVIDE THREE OPEN - WRITE GINO FILES. - TO *** SYSTEM FATAL MESSAGE 7378 (ADCSTM) 7378.0 INPUT CSTM PRECISION %1 IS INVALID. PROGRAMMER INFORMATION: THE CSTM PRECISION SHOULD BE 1 or 2. ADCSTM UTILITY IS CALLED BY %2 *** SYSTEM FATAL MESSAGE 7379 (ADCSTM) 7379.0 INPUT COORDINATE SYSTEM %1 OF CONVECTIVE TYPE %2 HAS NO INDICES. PROGRAMMER INFORMATION: ADCSTM UTILITY IS CALLED BY %3 PROGRAMMER ACTION: PROVIDE THE INDICES TO BUILD A CONVECTIVE COORDINATE SYSTEM. *** SYSTEM FATAL MESSAGE 7380 (MKCSTA) 7380.0 COORDINATE SYSTEM ID %1 WAS FOUND IN BOTH COORDINATE SYSTEMS DATA BLOCKS TO MERGE BUT DOES NOT DESCRIBE THE SAME COORDINATE SYSTEM. USER INFORMATION: COORDINATE sYSTEM DATA BLOCKS TO MERGE CAN NOT HAVE CONFLICTED COORDINATE SYSTEMS IDS. * SYSTEM INFORMATION MESSAGE 7382 (CLASDD) ** 7382.0 LARGEST NORMALIZED RESIDUAL FOR COMPLEX EIGENSOLUTION IS %1 *** USER WARNING MESSAGE 9002 (GPJAC) 7383.0 %1 ELEMENT ID =%2 HAS INVERTED GEOMETRY ON A %3. - USER INFORMATION: THIS CONDITION CAN CAUSE NON PHYSICAL RESULTS. *** USER FATAL MESSAGE 9002 (GPJAC) 7383.1 %1 ELEMENT ID =%2 HAS INVERTED GEOMETRY ON A %3. USER INFORMATION: THIS CONDITION CAN CAUSE NON - PHYSICAL RESULTS. *** USER FA TAL MESSAGE 7384 (DOPR3N) 7384.0 DRESP2 ENTRY ID = %1 REFERENCES ITSELF. *** USER FATAL MESSAGE 7385 (DOPR1C) 7385.0 THE PROPERTY NAME (FIFTH FIELD) ON DVPREL1 ENTRY ID = %1 CONTAINS INTEGER DATA FOR A PBEAML PROPERTY ENTRY. USER ACTION: FOR PBEAML ENTRIES, SPECIFY CHARACTER STRINGS SUCH AS DIM1, DIM2, etc. *** USER WARNING MESSAGE 7386.0 (CLASDD) 7386.0 THE ND FIELD (NUMBER OF DESIRED ROOTS) ON THE EIGC BULK DATA ENTRY IS BLANK OR IS SET TO ZERO.

533 USER ACTION: VERIFY THAT ND IS SET CORRECTLY. ND MUST BE SET IN FIELD 8 OF THE EIGC BULK DATA ENTRY. IF A CONTINUATION ENTRY IS USED, ND MUST BE SET IN FIELD 8 OF EACH CONTINUATION ENTRY. USER INFORMATION: THE NUMBER OF DESIRED ROOTS WILL BE HICH IS TWICE THE INITIAL BLOCK SIZE. SET TO %1, W *** USER WARNING MESSAGE 7386.1 (CLASDD) 7386.1 THE 6TH PARAMETER OF THE CEAD MODULE (NUMBER OF DESIRED ROOTS) IS NOT SPECIFIED OR IS SET TO ZERO. USER INFORMATION: THE NUMBER OF DESIRED ROOTS WILL BE SET TO % 1, WHICH IS TWICE THE INITIAL BLOCK SIZE. *** USER WARNING MESSAGE 7386.2 (LNNRIGL) 7386.2 THE ND, V1, AND V2 FIELDS ON THE EIGRL BULK DATA ENTRY ARE ALL BLANK OR SET TO ZERO. USER ACTION: VERIFY THAT ND,V1, AND V2 ARE SET IN THE APPROPRIATE FIELDS: V1 MUST BE SET IN FIELD 3, V2 MUST BE SET IN FIELD 4, AND ND MUST BE SET IN FIELD 5 OF THE EIGRL BULK DATA ENTRY. USER INFORMATION: THE NUMBER OF DESIRED ROOTS (ND) %1. WILL BE SET TO *** USER WARNING MESSAGE 7386.3 (LNNRIGL) 7386.3 THE ND, F1, AND F2 FIELDS ON THE EIGR BULK DATA ENTRY ARE ALL BLANK OR SET TO ZERO. USER ACTION: VERIFY THAT ND,F1, AND F2 ARE SET IN THE APPROPRIATE FIELDS: F1 MUST BE SET IN FIELD 4, F2 MUST BE SET IN FIELD 5, AND ND MUST BE SET IN FIELD 7 OF THE EIGR BULK DATA ENTRY. USER INFORMATION: THE NUMBER OF DESIRED ROOTS (ND) WILL BE SET TO %1. *** USER WARNING MESSAGE 7386 (LNNRIGL) 7386.4 THE 8TH, 9TH, AND 11TH PARAMETERS OF THE READ MODULE (F1,F2, AND ND RESPECTIVELY) ARE NOT SPECIFIED OR ARE SET TO ZER O. USER INFORMATION: THE NUMBER OF DESIRED ROOTS (ND) WILL BE SET TO %1. *** USER WARNING MESSAGE 7386 (LNNRIGL) 7386.5 NO UPPER FREQUENCY SPECIFIED FOR HIERARCHIC DMP. HEURISTIC UPPER FREQUENCIES WILL BE USED FOR EACH SEGMENT. USER ACTION: FOR BEST PERFORMANCE WITH HIERARCHIC DMP, SPECIFY AN UPPER FREQUENCY V2 AND LEAVE ND BLANK. *** USER WARNING MESSAGE 7386 (LNNRI GL) 7386.6 THE DESIRED NUMBER OF ROOTS (ND) HAS BEEN SPECIFIED FOR

534 FDMODES. IF THERE ARE CONSIDERABLY MORE THAN ND ROOTS IN THE SPECIFIED INTERVAL, POOR LOAD BALANCE MAY RESULT. USER ACTION: FOR BEST PERFORMANCE WITH FDMODES, LEAVE ND BLANK. SPECIFY AN UPPER FREQUENCY V2 AND *** USER WARNING MESSAGE 7386 (LNNRIGL) 7386.7 NO UPPER FREQUENCY SPECIFIED FOR FDMODES. HEURISTIC UPPER FREQUENCIES WILL BE USED FOR EACH SEGMENT. USER ACTION: FOR BEST PERFORMANCE WITH FDMODES, SPECIFY AN UPPER FREQUENCY V2 AND LEAVE ND BLANK. *** SYSTEM FATAL MESSAGE 7387 (SITDRV) 7387.0 DISTRIBUTED PARALLEL PROCESSING HAS BEEN REQUESTED WITH PURGED PARTITIONING INFORMATION. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7388 (SITDRV) 7388.0 NUMBER OF LOCAL ROWS IS INCONSISTENT BETWEEN SYSTEM MATRIX AND PARTITIONING INFORMATION. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7389 (DDSMAP) 7389.0 THE GLOBAL ROW NUMBER %1 ASSIGNED TO LOCAL ROW NUMBER %2 IS OUT OF RANGE. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7390 (DDSMAP) 7390.0 AN EEQIND INDEX FOR THE GLOBAL ROW NUMBER %1 IS OUT OF . RANGE USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7391 (DDSMAP) 7391.0 THE ID OF ONE OF THE PROCESSORS SHARING GLOBAL ROW NUMBER %1 IS OUT OF RANGE. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUST OMER SUPPORT. *** SYSTEM FATAL MESSAGE 7392 (DDSMAP) 7392.0 THIS PROCESSOR (LPID = %1) IS NOT A SHAREHOLDER OF ROW %2 IN ITS LOCAL KFF. THE GLOBAL ROW NUMBER IS %3. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7393 (DDSMAP) 7393.0 THE GLOBAL ROW NUMBER %1 IS NOT SHARED BY ANY PROCESSOR. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE

535 CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7394 (DDSMAP) 7394.0 SET %1, THE L - SET %2 AND - OCAL A THE SIZE OF THE LOCAL O THE LOCAL F - SET %3 DO NOT MATCH. A POSSIBLE REASON IS THAT THE LOCAL O - SET DOFS ARE NOT - SET DOFS. NUMBERED AFTER THE LOCAL A USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. SYSTEM FATAL MESSAGE 7395 (DDSMAP) *** 7395.0 - SET. INCONSISTENCY IN PARTITIONED A USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7396 (DDSMAP) 7396.0 THE GLOBAL ROW NUMBERS %1 AND %2 ASSIGNED TO LOCAL ROW NUMBERS %3 AND %4 ARE NOT IN ASCENDING ORDER. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7397 (DDSMAP) 7397.0 THE GLOBAL A - SET INDICES %1 AND %2 ASSIGNED TO LOCAL A - SET INDICES %3 AND %4 ARE NOT DING ORDER. IN ASCEN USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7398 (DDSMAP) 7398.0 TRANSLATION TO GLOBAL A - SET INDEX FAILED FOR LOCAL ROW INDEX %1. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. - SET INDEX TRANSFORMATION IN DISDCMP HAS TO BE GLOBAL A CHANGED. *** SYSTEM FATAL MESSAGE 7399 (DFMFRD) 7399.0 PREDICTIVE SYMBOLIC PIVOTING CORRUPTED THE PERMUTATION ORDER FOR THE D OFS TO BE DECOMPOSED. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7400 (DFMFRD) 7400.0 ERROR DURING NUMERIC ASSEMBLY OF INCORE STACK ELEMENT. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOME R SUPPORT. *** SYSTEM FATAL MESSAGE 7401 (DFMFRD) 7401.0 ERROR DURING NUMERIC ASSEMBLY OF OUT - OF - CORE STACK ELEMENT.

536 USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7402 (DFMFRD) 7402.0 ERROR DURING NUMERIC ASSEMBLY OF MATRIX ROWS. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7403 (DFMFRD) 7403.0 FRONT INDICES IN SCHUR COMPLEMENT ARE NOT IN ASCENDING ORDER. USER ACTION: PLEASE CONTA CT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7404 (DFMFRD) 7404.0 DEGREE OF FREEDOM %1 IS WRITTEN TO SCHUR COMPLEMENT, BUT SHOULD HAVE BEEN DECOMPOSED. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7405 (DFMFRD) 7405.0 ACTUAL AND REQUESTED NUMBER OF DOFS TO BE DECOMPOSED AND NOT TO BE DECOMPOSED DO NOT MATCH. NTOTPV: %1, N - ICOMP: %2 NSCHUR: %3, ICOMP : %4 USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT . *** SYSTEM FATAL MESSAGE 7406 (DFMFRD) 7406.0 NUMBER OF ASSEMBLED DEGREES OF FREEDOM %1 AND NUMBER OF DEGREES OF FREEDOM IN LOCAL MATRIX %2 DO NOT MATCH. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7407 (DFMSA) 7407.0 PARTITIONING VECTOR FOR PARTIAL DECOMPOSITION IS INCORRECT. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM INFORMATION MESSAGE 7408 (DFMSYN) 7408.0 SINCE SYSTEM(285) WAS SET BY THE USER TO A VALUE - IN RE - DIFFERENT FROM 5 ON THE NASTRAN ENTRY, FILL ORDERING WAS SKIPPED IN THE SYMBOLIC PHASE OF SPARSE DECOMPOSITION. *** USER WARNING MESSAGE 7409 (DOPR1J) 7409.0 EQUATION: E = 2*(1+NU)*G MAY BE VIOLATED FOR MAT1 ENTRY ID = %1 REFERRED BY DVMREL1 AND/OR DVMREL2 ENTRIES. USER INFORMATION: THE CORRESPONDING SENSITIVITY COEFFICIENTS MAY BE INACCURATE.

537 USER ACTION: LEAVE AT LEAST ONE OF THE THREE VALUES (E, G, NU) BLA NK AND UNREFERRED BY A DVMREL1/DVMREL2 ENTRIES *** USER WARNING MESSAGE 7409 (DOPR1J) 7409.1 EQUATION: BULK = RHO*C**2 MAY BE VIOLATED FOR MAT10 ENTRY ID = %1 REFERRED BY DVMREL1 AND/OR DVMREL2 ENTRIES. USER INFORMATION: THE CORRESPONDING SENSITIV ITY COEFFICIENTS MAY BE INACCURATE. USER ACTION: LEAVE AT LEAST ONE OF THE THREE VALUES (BULK, RHO, C) BLANK AND UNREFERRED BY A DVMREL1/DVMREL2 ENTRIES *** SYSTEM FATAL MESSAGE 7410 (DISDAF) 7410.0 PROGRAMMER ERROR IN PANEL TO PROCESSOR ASSIGNMENT CALCULATION. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7411 (DISDAF) 7411.0 PROGRAMMER ERROR IN INTERNAL LIST CALCULATION (FLLST). USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 7412 (SEQP) 7412.0 MODEL PARTITIONING WAS REQUESTED BY SETTING %1 = %2, HOWEVER, THE NUMBER OF PROCESSORS REQUESTED IS %3. USER ACTION: 1. DESELECT THE DOMAI N DECOMPOSITION METHOD BY SETTING OLDSEQ TO A VALID VALUE FOR - 1 THRU 8) OR SERIAL RUNS ( 2. SPECIFY MORE PROCESSORS TO PARTICIPATE IN THE RUN. *** SYSTEM FATAL MESSAGE 7413 (DISDCM1) 7413.0 PROGRAMMER ERROR: LENGTH OF HEADER OF STACK FACTOR DATA STRUCTURE IS INSUFFICIENT. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7414 (DISDCM1) 7414.0 PROGRAMMER ERROR: NGASET OR NCORE EXCEED MAXINT. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7415 (DISDRF) 7415.0 SIZE OF CURRENT PANEL EXCEEDS MAXIMUM VALUE. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. EM FATAL MESSAGE 7416 (DISDRF) *** SYST 7416.0 PROGRAMMER ERROR: INVALID NPIV VALUE. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE

538 CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7417 (DISDRF) 7417.0 PROGRAMMER ERROR: ERROR WHEN PUSHING NEW INCORE STACK ELEMENT. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7418 (DISDRF) 7418.0 INTERNAL STACK FOR DISTRIBUTED DECOMPOSITION IS FULL. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7419 (DISDFO) 7419.0 PROGRAMMER ERROR: %1 MORE WORDS NEEDED FOR MERGING INDICES OF STACK ELEMENTS. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7420 (DISDFO) 7420.0 PROGRAMMER ERROR: %1 BIGGER THAN NGASET. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7421 (SEQP) 7421.0 %1 CARDS ARE PRESENT IN THE BULK DATA SECTION. THEY ARE NOT SUPPORTED BY THE DOMAIN DECOMPOSITI ON METHOD. USER ACTION: PLEASE TAKE ONE OF THE FOLLOWING ACTIONS: 1. DESELECT THE DOMAIN DECOMPOSITION METHOD BY REMOVING DMP= FROM THE SUBMITTAL LINE. 2. REMOVE ALL CARDS OF THAT TYPE FROM THE BULK DATA SECTION. *** SYSTEM FATAL MESSAGE 7 422 (DISDFM) 7422.0 PROGRAMMER ERROR: UNABLE TO FIND ALL STACK ELEMENTS. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7423 (SEQP) 7423.0 A MALLOC INSIDE THE AUTOMATIC MODEL PARTITIONER WAS UNSUCCESSFUL IN ALLOCATING %1 K BYTES IN MEMORY. USER ACTION: DECREASE MEMORY GIVEN ON THE NX NASTRAN SUBMITTAL LINE. REPEAT DECREASE! *** SYSTEM FATAL MESSAGE 7424 (SEQP) 7424.0 PROCESSOR %1 DID NOT READ THE %2 RECORD FROM BNDFIL, IT READ THE RECORD OF DOMAIN %3 INSTEAD. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7425 (DISDLR) 7425.0 GETSEG RETURNED %1 TERMS, BUT %2 TERMS WERE EXPECTED.

539 USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7426 (DISDLR) 7426.0 RECEIVED %1 WORDS, BUT %2 WORDS WERE EXPECTED. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7427 (DISEQI) 7427.0 LOCAL TO GLOBAL MAP ENTRIES FOR LOC SET ARE NOT IN AL A - ASCENDING ORDER. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7428 (DISERD) 7428.0 PROGRAMMER ERROR %1. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7429 (DISERD) 7429.0 PROGRAMMER ERROR: NUMBER OF ROWS IN CURRENT PANEL %1 IS BIGGER THAN THE MAXIMUM EXPECTED VALUE %2. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7 430 (DISERD) 7430.0 PROGRAMMER ERROR: ACTUAL UPDATE RANK IS 0. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7431 (DISMRD) 7431.0 BLOCK SIZE %1 IS NOT SUPPORTED YET. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7432 (DISMRD) 7432.0 ERROR READING NEXT FRONT. NFRONT = %1, NROWS = %2. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. * SYSTEM FATAL MESSAGE 7433 (SEQP) ** 7433.0 THE NUMBER OF GLOBAL BOUNDARY GRID POINTS DIFFERS ON EQUATION MAP (%1) AND ON BOUNDARY FILE (%2). USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7434 (DISMRD) 7434.0 %1 FRONT INDEX %2 IS OUT OF RANGE OR NOT IN ORDER. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7435 (DISMRD) 7435.0 ERROR IN SKIPPING ROWS IN CURRENT FRONT.

540 USER ACTION: PLEASE CONTACT SIEMENS PLM S OFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7436 (DISMRD) 7436.0 SET INDEX %2 DO - FRONT INDEX %1 AND CURRENT GLOBAL A NOT MATCH. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. SYSTEM FATAL MESSAGE 7437 (DISMRD) *** 7437.0 READ %1 TERMS, BUT %2 TERMS WERE %3. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7438 (DISPRD) 7438.0 PIVOTING REQUIRED. USER ACTION: 1. CHECK MODEL, OR 2. USE P ARAM,HLPMETH,1, OR 3. CHANGE TO SERIAL EXECUTION. *** SYSTEM FATAL MESSAGE 7439 (DISSTI) 7439.0 FRONT SIZE IN SCHUR COMPLEMENT (INPUT DATA BLOCK KTT) IS BIGGER THAN EXPECTED. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7440 (DDFBRD) 7440.0 ERROR IN ASSIGNMENT OF PANEL %1 IN FRONT %2 TO PROCESSOR %3. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7441 (DDFBRD) 7441.0 SIZE MISMATCH IN PANEL %1 OF FRONT %2. EXPECTED DIMENSIONS ARE %3 AND %4, ACTUAL DIMENSIONS ARE %5 AND %6. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7442 (DDFBRD) 7442.0 NUMBER OF TERMS READ IN PAN EL %1 IS %2, BUT %3 WERE EXPECTED. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7443 (SEQP) 7443.0 THE PARTITIONING VECTOR CREATED TO SPECIFY THE LOCAL BOUNDARY GRIDS IS INCONSISTENT WITH THE NUMBER OF DEGREES OF FREEDOM ON THE LOCAL BOUNDARY (%1). THE NUMBER OF NONZERO TERMS IN THE PARTITIONING VECTOR IS %2. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE

541 CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7444 (D DFBRD) 7444.0 ERROR IN TPTR OR IPTR VALUE. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7445 (DDFBSA) 7445.0 WRONG FRONT IDENTIFIER IN RECORD NO. %1 OF DISTRIBUTED SPARSE FACTOR DESCRIPTION DATA BLOCK. USE R ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7446 (DDFBSA) 7446.0 ACTUAL FRONT SIZE %1 OF FRONT %2 IS ILLEGAL (MAXIMUM FRONT SIZE IS %3). USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7447 (DDFBSA) 7447.0 - 6 OF RECORD %1 IN CONSISTENCY ERROR(S) IN WORDS 3 DISTRIBUTED SPARSE FACTOR DESCRIPTION BLOCK. PROGRAMMER INFORMATION: %2, %3, %4, %5. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7448 (DDFBSA) 7448.0 WRONG GLOBAL PANEL IDENTIFIER %1 IN PANEL %2 OF FRONT %3. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7449 (DDFBSA) 7449.0 - 8 OF PANEL %1 IN RECORD CONSISTENCY ERROR(S) IN WORDS 1 %2 OF DISTRIBUTED SPARSE FACTOR DESCRIPTION BLOCK. PROGRAMMER INFORMATION: %3, %4, %5, %6, %7, %8, %9, %10. USER ACTION: PLEASE CONTACT SIEMENS PLM S OFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7450 (DDFBSA) 7450.0 ILLEGAL RECORD TERMINATION IN RECORD NO. %1 OF DISTRIBUTED SPARSE FACTOR DESCRIPTION DATA BLOCK. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7451 (DDFBSA) 7451.0 UNEXPECTED END OF DISTRIBUTED SPARSE FACTOR DESCRIPTION DATA BLOCK. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7452 (DDFDRV) 7452.0

542 SIZE OF LOCAL A - SET IS INCONSISTENT BETWEEN TRAILER OF EQMAP DATA BLOCK AND UABAR DATA BLOCK. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7453 (DDFDRV) 7453.0 SIZE OF LOCAL A - SET IN TRAILER AND DATA OF EQMAP DATA BLOCK DO NOT MATCH. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7454 7454.0 - SIZE OF GLOBAL A - SET HAS UNEXPECTED SET PLUS GLOBAL O VALUE. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7455 (DDFDRV) 7455.0 INCONSISTENCY IN DISTRIBUTED SPARSE FACTOR DESCRIPTION DATA BLOCK. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7456 (DDFDRV) 7456.0 PROGRAMMER ERROR IN NWRKSP VALUE. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7457 (DDFFRD) 7457.0 FIRST PANEL OF FRONT %1 HAS WRONG SIZE %2, EXPECTED SIZE IS %3. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7458 (DDFFRD) 7458.0 ERROR IN IPRANK VALUE %1 OR IOFF VALUE %2. IPOWNF IS %3. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7459 (SEQP) 7459.0 THE %1 OUTPUT DATABLOCK OF %2 IS PURGED, UNABLE TO OUTPUT PARTITIONING VECTOR FOR HIGH LEVEL PARALLEL EXECUTION. USER ACTION: PLEASE CHECK THE DMAP CALL TO %2 IF YOU INCLUDED AN ALTER OR CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7460 (SEQP) 7460.0 THE FIRST INPUT DATABLOCK TO SEQP (GEOM1) IS PURGED. USER ACTION: PLEASE CHECK THE DMAP CALL TO SEQP IF YOU INCLUDED AN ALTER OR CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT.

543 *** SYSTEM FATAL MESSAGE 7461 (SEQWRT) 7461.0 CURRENTLY ONLY %1 DOMAINS/PROCESSORS CAN BE HANDLED BY THE AUTOMATIC MODEL PART ITIONER. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7462 (DDFFRD) 7462.0 LENGTH OF MESSAGE RECEIVED FOR TRIANGULAR SOLVE OR UPDATE IS %1, BUT %2 WAS EXPECTED. USER ACTION: PLEASE CONTACT SIEMENS PL M SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7463 (DDFFRD) 7463.0 SIZE MISMATCH IN BLOCK TO BE SOLVED. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7464 (DDFFRD) 7464.0 MISMATCH IN IOFF2 AND IBASIS VALUES. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER INFORMATION MESSAGE 7465 (SEQWRT) 7465.0 STATISTICS FROM AUTOMATIC MODEL PARTITIONER THE NUMBER OF DOMAINS CREATED USING %1 IS %2 E NUMBER OF GRID POINTS IN THE GLOBAL BOUNDARY IS %3 TH THE NUMBER OF ELASTIC ELEMENTS IN THE RESIDUAL IS %4 THE NUMBER OF RIGID ELEMENTS IN THE RESIDUAL IS %5 DOMAIN ID # INTERNAL GRID POINTS # EXTERNAL GRID POINTS # OF ELEMENTS ------- ---------------------- ------------- --------- --------------- *** SYSTEM FATAL MESSAGE 7467 (SEQELM) 7467.0 ELEMENT TYPE %1 CANNOT BE HANDLED BY MODEL PARTITIONER. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. SYSTEM FATAL MESSAGE 7467 (SEQEXT) *** 7467.1 ASET AND ASET1 ENTRIES CANNOT BE HANDLED BY MODEL PARTITIONER. USER ACTION: PLEASE REMOVE ASET AND ASET1 ENTRIES FROM YOUR BULK DATA. *** SYSTEM FATAL MESSAGE 7468 (SEQELM) 7468.0 INSUFFICIENT MEMORY TO READ GRI D POINTS CONNECTED TO ELEMENT TYPE %1. USER ACTION: INCREASE MEMORY BY AT LEAST %2 K WORDS. *** SYSTEM FATAL MESSAGE 7469 (DDFMRG) 7469.0 INCORRECT NUMBER OF NONZERO TERMS %1 IN PANEL %2 OF FRONT %3.

544 USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7470 (DDFMRG) 7470.0 FRONT SIZE %1, PANEL SIZE %2 AND NEXT ROW %3 DO NOT MATCH FOR PANEL %4 OF FRONT %5. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE C USTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7471 (SEQELM) 7471.0 ELEMENT TYPE %1 HAS MORE THAN %2 GRID POINTS WHICH CANNOT BE HANDLED BY THE AUTOMATIC MODEL PARTITIONER. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7472 (DDFMRG) 7472.0 FRONT INDEX MISMATCH IN PANEL %1 OF FRONT %2. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7473 (DDFMRG) 7473.0 OWNER MISMATCH IN FIRST PANEL OF FRONT %1. US ER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7474 (SEQELM) 7474.0 ELEMENT CUT IN AUTOMATIC MODEL PARTITIONER: NODE %1 OF THE BOUNDARY DOES NOT BELONG TO %2, HOWEVER, ANOTHER NODE OF THIS ELEMENT DOES BELONG TO THIS DOMAIN. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7475 (DDFMRG) 7475.0 MEMORY SHORTAGE WHEN UNPACKING PANEL %1 OF FRONT %2. USER ACTION: P LEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7476 (DDFMRG) 7476.0 NUMBER OF TERMS %1 IN COLUMN %2 OF PANEL %3 IN FRONT %4 IS WRONG. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7477 (DDFMRG) 7477.0 INTERNAL ERROR UNPACKING PANEL %1 IN FRONT %2. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7478 (DDFMRG) 7478.0 INTERNAL ERROR IN COLUMN NUMBERING IN FRONT.

545 U SER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 7479 (SEQP) 7479.0 STRUCTURE analysis is not supported with DOMAIN - FLUID DECOMPOSITION. USER ACTION: PLEASE SWITCH TO ACMS OR RUN IN SERIAL. *** SYSTEM FATAL MESSAGE 7480 (SEQORD) 7480.0 INCONSISTENT NUMBER OF GRID POINTS ON THE BOUNDARY: THE INPUT TO THE SUBROUTINE IS %1, HOWEVER, %2 WHERE COMPUTED. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. GE 7481 (GETSEG) *** SYSTEM FATAL MESSA 7481.0 REQUESTED STACK ELEMENT DOES NOT EXIST. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7482 (GETSEG) 7482.0 PROGRAMMER ERROR: INCONSISTENCY IN GETSEG CALL. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7483 (SEQORD) 7483.0 ALL BOUNDARY GRID POINTS HAVE TO BE ON TOP OF THE ID() ARRAY WHICH IS NOT THE CASE HERE! GRIDPOINT %1 OUT OF %2 BELONGS TO DOMAIN %3 BUT NOT THE THE BOUNDARY. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7484 (GETSEG) 7484.0 REQUESTED SERVICE NOT SUPPORTED YET. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER INFORMA TION MESSAGE 7485 (SEQEXT) 7485.0 THE AUTOMATIC MODEL PARTITIONER SUBDIVIDED THE MODEL INTO %1 DOMAINS BUT %2 DOMAINS WERE REQUESTED. USER INFORMATION: EACH PROCESSOR WILL EXECUTE SERIALLY INSTEAD OF PARALLEL. USER ACTION: REQUEST FEWER DOMAINS. *** USER INFORMATION MESSAGE 7485 (SEQP) 7485.1 THE AUTOMATIC MODEL PARTITIONER SUBDIVIDED THE MODEL INTO %1 DOMAINS BUT %2 DOMAINS WERE REQUESTED. USER INFORMATION: THE PARTITIONING WILL BE RE - DONE ASKING TO PARTITION THE MODEL INTO %3 DOMAINS. * ** SYSTEM FATAL MESSAGE 7486 (GETSTJ) 7486.0 MAP FOR REQUESTED STACK ELEMENT DOES NOT EXIST.

546 USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7487 (GETSTJ) 7487.0 THIS CODE BRANCH IS NOT SUPPORTED YET. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7488 (GETSTJ) 7488.0 FOR STACK ELEMENT %1 ACTUAL FRONT SIZE %2 DOES NOT MATCH STACK INFO (%3). USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7489 (SEQP) 7489.0 INSUFFICIENT MEMORY FOR MODEL PARTITIONING. USER ACTION: INCREASE MEMORY BY AT LEAST %1 K %2. *** SYSTEM FATAL MESSAGE 749 0 (SEQP) 7490.0 ERROR IN MEMORY MANAGEMENT INSIDE THE AUTOMATIC MODEL PARTITIONER. %1. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7490 (SEQP) 7490.1 ERROR IN MEMORY MANAGEMENT INSIDE THE AUTOMATIC MODEL PARTITIONER. USER ACTION: INCREASE MEMORY BY AT LEAST %1 K WORDS. *** SYSTEM FATAL MESSAGE 7491 (DISDAF) 7491.0 INSUFFICIENT SPACE FOR INTERNAL LIST %1. SOFTWARE USER ACTION: PLEASE CONTACT SIEMENS PLM CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7492 (PRESOL) 7492.0 INCONSISTENT VALUE FOR NUMBER OF LOCAL GRIDPOINTS ON PROCESSOR %1: ACCORDING TO SIL TABLE, THE NUMBER OF LOCAL GRIDPOINTS IS %2 ACCORDING TO GEQMAP, THE NUMBER OF LOCAL GRI DPOINTS IS %3 USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7493 (PRESOL) 7493.0 INSUFFICIENT MEMORY AVAILABLE TO CREATE THE EXTENDED EQUATION MAP. USER ACTION: PLEASE INCREASE MEMORY BY AT LEAST %1 K WORDS. *** SYSTEM FATAL MESSAGE 7494 (PRESIL) 7494.0

547 LOCAL GRID POINT %1 HAS %2 DEGREES OF FREEDOM. CURRENTLY THE DOMAIN DECOMPOSITION METHOD CAN HANDLE ONLY GRID POINTS WITH 6 DEGREES OF FREEDO M. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7495 (PRESIL) 7495.0 INCONSISTENT NUMBER OF LOCAL ACTIVE DEGREES OF FREEDOM ON PROCESSOR %1: NUMBER OF LOCAL DEGREES OF FREEDOM = %2 6 * NUMBER OF ACTIVE GRID POINTS = %3 USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7496 (PREMAP) 7496.0 COLUMN %1 IN THE O SET OF PROCESSOR %2 IS A NULL - COLUMN. THIS CANNOT BE HANDLED BY THE DOMAIN DE COMPOSITION METHOD. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7497 (PREMAP) 7497.0 DEGREE OF FREEDOM %1 IS MARKED NON - ACTIVE ON PROCESSOR %2, HOWEVER, ON A DIFFERENT PROCESSOR IT WAS MARKED ACTIVE. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7498 (PRELGM) 7498.0 INSUFFICIENT WORK SPACE AVAILABLE FOR TMPIND(). PROCESSOR %1 NEEDS TO RECEIVE %2 WORDS FROM PROCESSOR %3, HOWEVER, ONLY %4 WORDS ARE AVAILABLE IN TMPIND(). USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7499 (PRELGM) 7499.0 INSUFFICIENT WORK SPACE AVAILABLE FOR IWORK() TO BUILD THE EXTENDED EQUATION MAP ON PROCESSOR %1. WORK SPACE AVAILABLE IS %2 WORDS BUT %3 WORDS ARE NEEDED. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7500 (PRELGM) 7500.0 INCONSISTENCY OF DEGREES OF FREEDOM FOR THE F - SET ON PROCESSO R %1: DEGREES OF FREEDOM FROM RESORD ARRAY IS %2, BUT DEGREES OF FREEDOM IN LOCAL F - SET IS %3. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE

548 CUSTOMER SUPPORT. *** USER FATAL MESSAGE 7501 (DOPR3I) 7501.0 THE DSNOKD PARAMETER IS SET TO %1 AND THERE ARE MULTIPLE BUCKLING DESIGN SUBCASES WHICH CONTAIN DIFFERENT STATSUB REQUESTS: %2 AND %3. THIS IS NOT SUPPORTED. USER ACTION: SET DSNOKD TO 0.0 OR USE THE SAME STATSUB REQUEST FOR ALL BUCKLING DESIGN SUBCASES. *** USER FATAL MESSAGE 7501.1 (DOPR3I) 7501.1 MULTIPLE CMPLNCE RESPONSES DEFINED FOR SUBCASE %1. ONLY ONE CMPLNCE RESPONSE IS ALLOWED PER SUBCASE. *** SYSTEM INFORMATION MESSAGE 7502 (DSDJ1D/S) 7502.0 THERE ARE %1 ACTIVE SOLUTION VECTORS, OF WHICH %2 CAN BE STORED IN MEMORY. IN ORDER TO STORE ALL VECTORS IN MEMORY FOR IMPROVED PERFORMANCE, INCREASE MEMORY BY %3K WORDS. *** SYSTEM FATAL MESSAGE 7503 (SQMPC) 7503.0 LOGIC ERROR IN THE AUTOMATIC MODEL PARTITIONER. PROGRAMMER INFORMATION: GRID POINT ID %1 WHICH IS SPECIFIED AS THE DEPENDENT GRID POINT ON AN MPC ENTRY IS ALSO ASSIGNED TO A DOMAIN BOUNDARY. USER ACTION: TRY TO RUN WITH A DIFFERENT NUMBER OF PROCESSORS OR CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7503 (SQRBAR) 7503.1 LOGIC ERROR IN THE AUTOMATIC MODEL PARTITIONER. PROGRAMMER INFORMATION: ALL DEPENDENT GRID POINTS OF RIGID ELEMENT ID %1 WERE ASSIGNED TO A DOMAIN BOUN DARY. USER ACTION: TRY TO RUN WITH A DIFFERENT NUMBER OF PROCESSORS OR CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7503 (SQRBAR) 7503.2 LOGIC ERROR IN THE AUTOMATIC MODEL PARTITIONER. PROGRAMMER INFORMATION: ALL DEPEND ENT GRID POINTS OF RIGID ELEMENT ID %1 WERE ASSIGNED TO A DOMAIN BOUNDARY. ALSO ALL GRIDS CONNECTED TO THIS RIGID ELEMENT WERE ASSIGNED TO A DOMAIN BOUNDARY. USER ACTION: TRY TO RUN WITH A DIFFERENT NUMBER OF STOMER PROCESSORS OR CONTACT SIEMENS PLM SOFTWARE CU SUPPORT. *** SYSTEM FATAL MESSAGE 7504 (SQRBE1) 7504.0 LOGIC ERROR IN THE AUTOMATIC MODEL PARTITIONER.

549 PROGRAMMER INFORMATION: NO DEPENDENT GRID POINTS OF %1 BELONG TO A DOMAIN, HOWEVER, THEY DO NOT ALL BELONG TO THE BOUNDARY EITHER. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7505 (SQRBE1) 7505.0 LOGIC ERROR IN THE AUTOMATIC MODEL PARTITIONER. PROGRAMMER INFORMATION: AFTER CHECKING ALL RIGID F ELEMENT %2 ELEMENTS OF THIS TYPE, GRIDPOINT %1 O BELONGS TO DOMAIN %3, HOWEVER, IT WAS INITIALLY ASSIGNED TO %4. THIS INDICATES THAT THIS GRIDPOINT MAY BE A DEPENDENT GRID OF 2 DIFFERENT RIGID ELEMENTS. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** S YSTEM FATAL MESSAGE 7506 (SQRROD) 7506.0 LOGIC ERROR IN THE AUTOMATIC MODEL PARTITIONER. PROGRAMMER INFORMATION: INVALID NUMBER (DEPROD = %1) FOR SPECIFYING THE DEPENDENT GRID OF RROD %2. THE NUMBER SHOULD BE EITHER 1 OR 2. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7507 (SQRTRP) 7507.0 LOGIC ERROR IN THE AUTOMATIC MODEL PARTITIONER. PROGRAMMER INFORMATION: GRIDPOINTS OF RTRPLT %1 BELONG TO DOMAINS %2 AND %3. THIS CANNOT BE HANDLED YET. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7510 (SQRTRP) 7508.0 LOGIC ERROR IN THE AUTOMATIC MODEL PARTITIONER. PROGRAMMER INFORMATION: ALL GRIDPOINTS OF RTRPLT %1 BELONG TO A DIFFERENT DOMAIN ( %2, %3 AND %4). USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** SYSTEM FATAL MESSAGE 7509 (PRELRD) 7509.0 LOGIC ERROR IN DISTRIBUTED MAP PREPARATION MODULE. PROGRAMMER INFORMATION: INCONSISTENT LOCAL A - SET. SIZE OF LOCAL A - SET FROM PARTITIONING VECTOR CREATED IN PRESOL IS %1, HOWEVER, SIZE OF LOCAL A - SET FROM THE EQUATION MAP IS %2. USER ACTION: PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT.

550 *** USER FATAL MESSAGE 7510 (DOM9P4D) 7510.0 THE MAXIMUM INTEGER VALUE HAS BEEN EXCEEDED. USER INFORMATION: THE MAXIMUM INTEGER NUMBER ALLOWED ON YOUR MACHINE IS %1. HOWEVER, DOT HAS IDENTIFIED THAT THE SIZE OF YOUR OPTIMIZATION PROBLEM, NDV =%2, NCON = %3, IS SO LARGE THT IT CAUSES MAXIMUM INTEGE R OVERFLOW. USER ACTION: REDUCE SIZE OF DESIGN MODEL. *** SYSTEM FATAL MESSAGE 7511 (BIOCPY) 7511.0 INVALID CALL TO BIOCPY. %1 VALUE (= %2) IS OUT OF RANGE. FILE COPY REQUEST NOT DONE. *** SYSTEM FATAL MESSAGE 7512 (BIOCPY) 7512.0 ILE IS NOT OPEN. FILX = %1. INPUT F FILE IS '%2'. FILE COPY REQUEST NOT DONE. *** SYSTEM FATAL MESSAGE 7513 (BIOCPY) 7513.0 INPUT FILE RECORD LENGTH DOES NOT MATCH NSBUF3 VALUE. FILX = %1. FILE IS '%2'. FILE RECL = %3, NSBUF3 RECL = %4. FILE COPY REQUEST NOT DONE. *** SYSTEM FATAL MESSAGE 7514 (BIOCPY) 7514.0 OUTPUT FILE IS OPEN BUT ITS RECORD LENGTH DOES NOT MATCH INPUT FILE RECL VALUE. INPUT FILX = %1, OUTPUT FILX = %2. INPUT FILE IS '%3'. OUTPUT FILE IS '%4'. INPUT FILE RECL = %5, OUTPUT FILE RECL = %6. FILE COPY REQUEST NOT DONE. *** SYSTEM FATAL MESSAGE 7515 (BIOCPY) 7515.0 - ONLY. FILX = %1. OUTPUT FILE IS OPENED READ FILE IS '%2'. FILE COPY REQUEST NOT DONE. *** SYSTEM FATAL MESSAGE 7516 (BIOCPY) 7516.0 UNABLE TO CREATE OUTPUT FILE. FILX = %1. FILE IS '%2'. FILE COPY REQUEST NOT DONE. *** SYSTEM FATAL MESSAGE 7517 (BIOCPY) 7517.0 TRUNCATE OF OPEN OUTPUT FILE FAILED. FILX = %1. FILE IS '%2'. FILE COPY REQUEST NOT DONE. *** SYSTEM FATAL MESSAGE 7518 (BIOCPY) 7518.0 UNABLE TO OBTAIN DYNAMIC BUFFER SPACE FOR FILE COPY.

551 WORDS REQUESTED = %1. FILE COPY REQUEST NOT DONE. *** SYSTEM FATAL MESSAGE 7519 (BIOCPY) 7519.0 ERROR ENCOUNTERED READING INPUT FILE. FILX = %1. FILE IS '%2'. FILE COPY REQUEST TERMINATED. *** SYSTEM FATAL MESSAGE 7520 (BIOCPY) 7520.0 ERROR ENCOUNTERED WRITING OUTPUT FILE. FILX = %1. FILE IS '%2'. FILE COPY REQUEST TERMINATED. *** USER FATAL MESSAGE 7521 (GP3) 7521.0 LOAD BULK DATA ENTRY WITH SID=%1 REFERENCES A DEFORM OR TEMP* BULK DATA ENTRY WITH SID=%2 . USER INFORMATION: DEFORM AND TEMP* BULK DATA ENTRIES ARE REQUESTED BY THE DEFORM AND TEMPERATURE CASE CONTROL COMMANDS. *** USER FATAL MESSAGE 7522 (GP3) 7522.0 DEFORM AND TEMP* BULK DATA ENTRY HAVE THE SAME SID=%1 . USER INFORMATION: DEFORM AND TEMP* BULK DATA ENTRIES MUST BE UNIQUE WITH RESPECT TO EACH OTHER. *** USER FATAL MESSAGE 7523 (SEPMAB) 7523.0 SUPERE LEMENT %1 IS DEFINED ON THE SEBULK BULK DATA ENTRY BUT NO GEOMETRY WAS FOUND. USER ACTION: CHECK BEGIN SUPER COMMANDS AND/OR DATA BASE ASSIGNMENTS FOR THIS SUPERELEMENT. *** USER FATAL MESSAGE 7524 (DOP1C2) 7524.0 DVPREL1 ENTRY %1 SPECIFIES A PBEAML DIMENSION THAT IS NOT SPECIFIED ON PBEAML ENTRY %2. USER ACTION: CHECK DVPREL1 AND PBEAML ENTRIES. *** USER FATAL MESSAGE 7525 (DOPR3A) 7525.0 DRESP1 ENTRY ID = %1 REFERENCES A RTYPE=ESE WHICH IS NOT SUPPORTED F OR SHAPE OPTIMIZATION. *** USER FATAL MESSAGE (ASGPD/S) 7526.0 AN INVALID TRIM TASK HAS BEEN POSED. THERE ARE %1 FREE AESTAT DEGREES OF FREEDOM BUT ONLY %2 SUPPORTED DEGREES OF FREEDOM. USER ACTION: SPECIFY A VALID TRIM TASK BY EITHER ADDING SUPP ORTED DEGREES OF FREEDOM OR BY REDUCING THE NUMBER OF FREE AESTAT DEGREES OF FREEDOM. *** USER FATAL MESSAGE (ASGPD/S) 7526.1 AN INVALID TRIM TASK HAS BEEN POSED. THERE ARE %1 FREE

552 AERODYNAMIC DEGREES OF FREEDOM BUT ONLY %2 SUPPORTED DEGREES OF FREEDOM AND THERE ARE NO REDUNDANT CONTROL SURFACES. USER ACTION: SPECIFY A VALID TRIM TASK BY A COMBINATION OF ADDING SUPPORTED DEGREES OF FREEDOM, ADDING REDUNDANT CONTROL SURFACES AND/OR REDUCING THE NUMBER OF FREE AESTAT DEGREES OF FREEDOM. *** SYSTEM FATAL MESSAGE 7527 (SEQEXT) 7527.0 THE AUTOMATIC MODEL PARTITIONER DID NOT ASSIGN ANY GRID POINTS TO THE BOUNDARY. USER INFORMATION: THE DOMAIN DECOMPOSITION METHOD CANNOT CONTINUE WITHOUT A BOUNDARY. IF YOUR MODEL IS DISJOINT, DESELECT THE USER ACTION: DOMAIN DECOMPOSITION METHOD BY REMOVING DMP= FROM THE SUBMITTAL LINE. IF YOUR MODEL IS NOT DISJOINT, PLEASE CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. A "=ALL" OUTPUT REQUEST HAS BEEN FOUND FOR DI SP, VELO, 7528.0 ACCE, STRESS OR FORCE TYPE OUTPUT. USER INFORMATION: MORE ECONOMICAL DATA RECOVERY IS POSSIBLE WHEN A LIMITED OUTPUT SET IS SELECTED. *** SYSTEM FATAL MESSAGE 7529 (TAFGPE) 7529.0 SPILL LOGIC ERROR FORMING GPECT TABLE, REASON = %1 PROGRAMMER INFORMATION: HERE IS A LIST OF POSSIBLE REASONS: 1 - CONTROL TABLE NOT ALLOCATED, EST ESTIMATES WRONG - CONTROL TABLE EXHAUSTED BUILD LOOP 2 - CONTROL TABLE EXHAUSTED FLUSHING LAST MEMORY 3 LOAD - INSUFFICIENT MEMORY BLOCK FRAGMENTS FOR JO 4 IN USER ACTION: FOR REASON 1:3 TURN OFF FOLLOWER FORCES IF POSSIBLE FOR REASON CODE 4, CHANGE MODULE DEFAULT PARAMETER POSITION 5, TO HIGHER VALUE THAN 10. *** USER FATAL MESSAGE 7530 (DOPFSDD) 7530.0 THERE FULLY STRESSED DESIGN HAS BEEN REQUESTED, BUT ARE NO ELEMENT BASED CONSTRAINTS. *** USER WARNING MESSAGE 7531 (DOP3V1) 7531.0 NO DESIGNED PROPERTIES IN FULLY STRESSED DESIGN. *** USER FATAL MESSAGE 7530 (ASG) 7532.0 SENSITIVITY ANALYSIS HAS BEEN REQUESTED THAT IS ASSOCIATED WITH NONLINEAR STATIC AEROELASTIC TRIM ANALYSIS.

553 USER INFORMATION: THIS CAPABILITY IS NOT SUPPORTED. USER ACTION: EITHER REMOVE THE REQUEST OR SPECIFY A LINEAR STATIC AEROLEASTIC ANALYSIS. *** USER WARNING MESSAGE 7533 (PFACED/S, PEDGED/S), 7 533.0 %1 %2 IS PART OF A SOLID ELEMENT AND DOES NOT HAVE ROTATIONAL DEGREES OF FREEDOM. USER INFORMATION: DISTRIBUTED MOMENT LOADS WILL BE IGNORED. *** USER FATAL MESSAGE 7536 (GP3A) 7536.0 E FOLLOWING NON - UNIQUE SID/EXCITATION - ID PAIRS HAVE TH -- BEEN SPECIFIED IN LSEQ BULK DATA ENTRIES (USER ACTION: AVOID THE NEED FOR NON UNIQUE - - ID PAIRS BY USING SID/EXCITATION AND REFERENCING APPROPRIATE COMBINATION LOAD BULK DATA) SYSTEM WARNING MESSAGE 7537 (REIG) *** 7537.0 PERTURBED MASS MATRIX IS USED FOR EIGENSOLUTION. PERTURBATION FACTOR USED = %1 *** USER WARNING MESSAGE 7538 (REIG) 7538.0 NUMBER OF EIGENVECTORS IS BEING REDUCED FROM %1 TO %2 DUE TO RANK DEFICIENCY OF THE MAS S MATRIX. *** SYSTEM WARNING MESSAGE 7539 (DFMSJ) 7539.0 RANK OF MASS MATRIX = %1 *** SYSTEM FATAL MESSAGE 7540 (GP1D and 7540.0 SECNV1/SECNV2/SECNV3) INVALID RETURN FROM CALL TO SUBROUTINE %1 RETURN CODE = %2 *** SYSTEM FATAL MESSAGE 7541 (GP1D and 7541.0 SECNV1/SECNV2/SECNV3) INVALID RETURN FROM CALL TO SUBROUTINE %1 WHILE PROCESSING %2 BULK DATA ENTRY %3 FOR POINT ID %4 RETURN CODE = %5 *** SYSTEM FATAL MESSAGE 7542 (GP1D) 7542.0 ILLEGAL COORDINATE SYSTEM ID %1 ENCOUNTERED WHILE PROCESSING DAREA BULK DATA ENTRY %2 FOR %3 POINT ID %4 *** USER INFORMATION MESSAGE 7543 (GP1D) 7543.0 DAREA BULK DATA ENTRIES FOR GRID AND SCALAR POINTS WILL NOT BE CONVERTED TO EQUIVALENT FORCE / MOMENT / SLOAD ENTRIES BECAUSE OF THE PRESENCE OF LSEQ BULK DATA ENTRIES *** USER FATAL MESSAGE 30000 (DSAD13) 7544.0 DRESP1 ID %1 IS A CFAILURE RESPONSE WITH ITEM CODE 8:

554 MAXIMUM FAILURE INDEX. USER INFORMATION: THIS RESPONSE IS ONLY VALID FOR THE FINAL PLY BUT IS BEING APPLIED TO PLY NUMBER %2 USER ACTION: RESTRICT THE ITEM CODE 8 REQUEST TO THE FINAL PLY *** USER FATAL MESSAGE 30001 (DSAD13) 7544.1 DRESP1 ID %1 IS A CFAILURE RESPONSE WITH ITEM CODE 7: INTERLAMINAR STRESS/STRAIN. USER INFORMATION: THIS RESPONSE IS BEING APPLIED TO PLY NUMBER %2, WHICH IS THE FINAL PLY. INTERLAMINAR STRESS/STRAIN RESPONSES ARE NOT AVAILABLE FOR THE FINAL PLY USER ACTION: DO NOT APPLY ITEM CODE 7 TO THE FINAL PLY *** USER WARNING MES SAGE 7545 (MDG2SW) 7545.0 A CORRESPONDING CWELDG ENTRY CANNOT BE FOUND WITH THE SAME SPOT WELD GRID ID AS SPECIFIED ON CWELDG ENTRY ID=%1. USER INFORMATION: THE SHELL PORTION OF THIS ELEMENT WILL BE CREATED BUT NOT THE SPOT WELD PORTION. *** USER FATAL MESSAGE 7546 (MDG2SW) 7546.0 ON CWELD ENTRY ID=%1, WITH FORM=ALIGN, THE GA (OR GB) GRID ID=%2 IS NOT A VERTEX GRID OF A SHELL ELEMENT. *** USER FATAL MESSAGE 7546 (MDG2SE) 7546.1 ON CWELD ENTRY ID=%1, WITH FORM=ELEMID, THE SHID1 (OR SHID2)=%2 IS NOT A SHELL ELEMENT. *** USER INFORMATION MESSAGE 7547 (MDG4SW) 7547.0 - TO - SHELL FOR PWELD ENTRY ID=%1, THE SPOT WELD CONNECTION WILL BE SET TO FLEXIBLE (BEHV=_F) BECAUSE CTYP=HINGE OR BOLT . *** USER INFORMATION MESSAGE 7548 (MDG4SW) 7548.0 FOR PWELD ENTRY ID=%1, THE SPOT WELD WILL BE SET TO RIGID (BEHV=R_) BECAUSE MTYP=EQUI. *** USER FATAL MESSAGE 7549 (SEPWLD) 7549.0 FOR CWELD ENTRY ID=%1, THE PROJECTION OF GS GRID ID=%2 ONTO THE SURFACE CANNOT BE FOUND OR LIES OUTSIDE THE SURFACE. *** USER FATAL MESSAGE 7550 (MDG4SW) 7550.0 FOR PWELD ENTRY ID=%1, THE DIAMETER OF THE SPOT WELD IS NOT GREATER THAN ZERO. USER I NFORMATION: IF BEHV=FF OR FR, THEN THE DIAMETER

555 MUST BE SPECIFIED. *** USER FATAL MESSAGE 7551 (BNDSP3) 7551.0 BOUNDARY GRID %1B, WHICH INHERITS AN UPSTREAM COORDINATE SYSTEM ID=%2, IS NOT TOTALLY CONSTRAINED FOR EITHER ALL TRANSLATIONS OR ALL ROT ATIONS. USER ACTION: DEFINE A COINCIDENT GRID AND COORDINATE SYSTEM IN THE DOWNSTREAM SUPERELEMENT. *** USER INFORMATION MESSAGE 7551 (BNDSP3) 7552.0 BOUNDARY GRID %1B WILL INHERIT ITS CONTRAINTS FROM UPSTREAM SUPERELEMENT(S). *** USER INFORMATION MESSAGE 7551 (BNDSP3) 7552.1 BOUNDARY GRID %1B WILL INHERIT ITS CONTRAINTS FROM UPSTREAM SUPERELEMENT(S). CONTRAINTS ARE APPLIED TO AN IMPLICIT BOUNDARY AND THUS SPCFORCE OUTPUT WILL NOT BE AVAILABLE. USER INFORMATION: SPCFORCES WILL NOT BE RE FLECTED IN THE GPFORCE, SPCFORCE MAXIMA, AND SPCFORCE RESULTANT OUTPUTS. USER ACTION: DEFINE A CONCIDENT GRID IN THE DOWNSTREAM SUPERELEMENT FOR OUTPUT RECOVERY. *** USER INFORMATION MESSAGE 7553 (GP1D) 7553.0 A TOTAL OF %1 DAREA BULK DATA ENTRIES FOR GRID AND SCALAR POINTS HAVE BEEN CONVERTED TO EQUIVALENT FORCE / MOMENT / SLOAD ENTRIES (AS APPROPRIATE) User information: Set NASTRAN SYSTEM(320) = n to request details of the first n of such conversions (set n to a very large value to request de tails of all such conversions) Set NASTRAN SYSTEM(320) = 1 to suppress all such conversions - altogether *** USER INFORMATION MESSAGE 7553 (SECNVG) 7553.1 A TOTAL OF %1 %2 BULK DATA ENTRIES HAVE BEEN CONVERTED TO EQUIVALENT %3 ENTRIES User information: Set NASTRAN SYSTEM(350) = n to request details of the first n of such conversions (set n to a very large value to request details of all such conversions) Set NASTRAN SYSTEM(350) = - 1 to suppress all such conversions altogether *** USER INFORMATION MESSAGE 7553 (SECNVG) 75 53.2 A TOTAL OF %1 %2 AND %3 %4 BULK DATA ENTRIES HAVE BEEN CONVERTED TO EQUIVALENT %5 ENTRIES User information:

556 Set NASTRAN SYSTEM(350) = n to request details of the first n of such conversions very large value to request details of all such conversions) (set n to a 1 to suppress all such conversions Set NASTRAN SYSTEM(350) = - altogether *** USER INFORMATION MESSAGE 7553 (SECNVG) 7553.3 A TOTAL OF %1 %2 BULK DATA ENTRIES, WHICH EMPLOY A THIRD GRID P OINT TO DEFINE THE ORIENTATION VECTOR, HAVE BEEN MODIFIED BY REPLACING THOSE GRID POINTS BY EQUIVALENT VECTOR COORDINATES User information: Set NASTRAN SYSTEM(350) = n to request details of the first n of such modifications to request details of all such modifications) (set n to a very large value - Set NASTRAN SYSTEM(350) = 1 to suppress all such modifications altogether *** USER FATAL MESSAGE 7554 (R3CGRT) 7554.0 DRESP3 ENTRY %1 SPECIFIES AN UNDEFINED RESPONSE TYPE %2 GROUP = %3. FOR EXTERNAL RESPONSE USER INFORMATION : MAKE SURE THAT THE RESPONSE TYPE NAME ON THE DRESP3 ENTRY MATCHES THE RESPONSE TYPE SPECIFICED IN THE SERVER ROUTINE. *** USER INFORMATION MESSAGE 7555 7555.0 FINITE ELEMENT GEOMETRY CHECK RESULTS EXCEED TOLERANCE L EVELS FOR THE FOLLOWING ELEMENTS. USER ACTION: USE THE GEOMCHECK (EXECUTIVE CONTROL STATEMENT) KEYWORD=VALUE TO CHANGE TOLERANCE VALUES IF DESIRED. User information: Element Geometry test tolerance levels and message limits can be changed by the GEOMCHE CK Executive Control statement. The following keywords are available: - to modify the CQUAD4/CQUADR skew angle test tolerance. Q4_SKEW - Q4_TAPER to modify the CQUAD4/CQUADR taper ratio test tolerance. - Q4_WARP to modify the CQUAD4/CQUADR warping coef ficient test tolerance. Q4_IAMAX - to modify the CQUAD4/CQUADR maximum interior angle test tolerance. Q4_IAMIN - to modify the CQUAD4/CQUADR minimum interior angle test tolerance. T3_SKEW - to modify the CTRIA3/CTRIAR skew angle test tolerance. T3_IAMA - to modify the CTRIA3/CTRIAR maximum interior angle test X tolerance. TET_AR - to modify the CTETRA aspect ratio test tolerance.

557 TET_EPLR - to modify the CTETRA edge node point length ratio test tolerance. to modify the CTETRA determinant of the Jacobian matrix test TET_DETJ - tolerance. TET_DETG to modify the CTETRA determinant of the vertex points - Jacobian matrix test tolerance. to modify the CHEXA aspect ratio test tolerance. HEX_AR - - est HEX_EPLR to modify the CHEXA edge node point length ratio t tolerance. - to modify the CHEXA determinant of the Jacobian matrix test HEX_DETJ tolerance. - HEX_WARP to modify the CHEXA face warping coefficient test tolerance. - BEAM_OFF to modify the CBEAM offset length ratio test tolerance. - to mod ify the CBAR offset length ratio test tolerance. BAR_OFF - to limit the number of messages that are generated. MSGLIMIT MSGTYPE to modify the severity level of the test. - *** USER INFORMATION MESSAGE 7555 7555.1 FINITE ELEMENT GEOMETRY CHECK RESULTS EXCEED TOLERANCE LEVELS FOR THE FOLLOWING ELEMENTS. *** USER INFORMATION MESSAGE 7555 7555.2 FINITE ELEMENT GEOMETRY CHECK RESULTS EXCEED TOLERANCE LEVELS FOR THE FOLLOWING ELEMENTS. USER ACTION: USE THE GEOMC HECK (EXECUTIVE CONTROL STATEMENT) KEYWORD=VALUE TO CHANGE TOLERANCE VALUES IF DESIRED. User information: Element Geometry test tolerance levels and message limits can be changed by the GEOMCHECK Executive Control statement. The following keywords are a vailable: QDX_SKEW to modify the CQUADX4/8 skew angle test tolerance. - QDX_TAPR to modify the CQUADX4/8 taper ratio test tolerance. - QDX_IAMX to modify the CQUADX4/8 maximum interior angle test - tolerance. QDX_IAMN - to modify the CQUADX4/8 minimum interior angle test tolerance. - to modify the CQUADX4/8 aspect ratio test tolerance. QDX_AR - QDX_EPLR to modify the CQUADX4/8 edge node point length ratio test tolerance. TRX_IAMN - to modify the TRIAX3/6 maximum interior angle test tolerance. TRX_IA - to modify the TRIAX3/6 maximum interior angle test MX tolerance. TRX_AR - to modify the TRIAX3/6 aspect ratio test tolerance. TRX_EPLR - to modify the TRIAX3/6 edge node point length ratio test tolerance.

558 MSGLIMIT - to limit the number of messages tha t are generated. - MSGTYPE to modify the severity level of the test. *** USER INFORMATION MESSAGE 7555 7555.3 FINITE ELEMENT GEOMETRY CHECK RESULTS EXCEED TOLERANCE LEVELS FOR THE FOLLOWING ELEMENTS. *** USER FATAL MESSAGE 7555 7555.4 FINITE ELEMENT QUALITY CHECKS FAILED. USER ACTION: REVIEW THE QUALITY CHECK RESULTS AND ADJUST TOLERANCE VALUES IF DESIRED. User information: *** USER INFORMATION MESSAGE 7555 7555.5 FINITE ELEMENT GEOMETRY CHECK RESULTS EXCEED OR THE FOLLOWING ELEMENTS. TOLERANCE LEVELS F USER ACTION: USE THE GEOMCHECK (EXECUTIVE CONTROL STATEMENT) KEYWORD=VALUE TO CHANGE TOLERANCE VALUES IF DESIRED. THE LONGEST TO SHORTEST EDGE HEIGHT RATIO IN THE STACKING DIRECTION OF COMPOSITE SOLID ELEMENT SHOULD BE NO LESS THAN 1.0. *** USER INFORMATION MESSAGE 7555 7555.6 FINITE ELEMENT GEOMETRY CHECK RESULTS EXCEED TOLERANCE LEVELS FOR THE FOLLOWING ELEMENTS. USER ACTION: USE THE GEOMCHECK (EXECUTIVE CONTROL STATEMENT) KEYWORD=VALUE TO CHANGE TOLERANCE ESIRED. VALUES IF D User information: Element Geometry test tolerance levels and message limits can be changed by the GEOMCHECK Executive Control statement. The following keywords are available: to modify the CQUAD8 skew angle test tolerance. Q8_SKEW - to modify the CQUAD8 taper ratio test tolerance. Q8_TAPER - - Q8_IAMAX to modify the CQUAD8 maximum interior angle test tolerance. Q8_IAMIN to modify the CQUAD8 minimum interior angle test tolerance. - - to modify the CQUAD8 aspect ratio test tolerance. Q8_AR Q8 _EPLR - to modify the CQUAD8 edge node point length ratio test tolerance. - to limit the number of messages that are generated. MSGLIMIT - to modify the severity level of the test. MSGTYPE *** USER INFORMATION MESSAGE 7555 7555.7 FINITE ELEMENT GEOMETRY CHECK RESULTS EXCEED TOLERANCE LEVELS FOR THE FOLLOWING ELEMENTS. *** USER INFORMATION MESSAGE 7555 7555.8 FINITE ELEMENT GEOMETRY CHECK RESULTS EXCEED TOLERANCE LEVELS FOR THE FOLLOWING ELEMENTS.

559 USER ACTION: USE THE GEOMC HECK (EXECUTIVE CONTROL STATEMENT) KEYWORD=VALUE TO CHANGE TOLERANCE VALUES IF DESIRED. User information: Element Geometry test tolerance levels and message limits can be changed by the GEOMCHECK Executive Control statement. The following keywords are a vailable: to modify the CTRIA6 maximum interior angle test tolerance. TA6_IAMX - to modify the CTRIA6 minimum interior angle test tolerance. - TA6_IAMN TA6_AR - to modify the CTRIA6 aspect ratio test tolerance. - to modify the CTRIA6 edge node TA6_EPLR point length ratio test tolerance. - to limit the number of messages that are generated. MSGLIMIT MSGTYPE - to modify the severity level of the test. *** USER INFORMATION MESSAGE 7555 7555.9 FINITE ELEMENT GEOMETRY CHECK RESULTS EXCEED LEVELS FOR THE FOLLOWING ELEMENTS. TOLERANCE *** USER FATAL MESSAGE 7556 (SEPMAB) 7556.0 SUPERELEMENT %1 HAS BOTH INTERIOR STRUCTURAL AND FLUID GRID POINTS. USER ACTION: REASSIGN GRID POINTS AND/OR ELEMENTS SO THAT THE SUPERELEMENT'S INTERIOR AND EXTERIOR POINTS ARE ALL FLUID OR ITS INTERIOR POINTS ARE ALL STRUCTURAL. *** User FATAL MESSAGE 7557 (SEQWRT) 7557.0 THE FOLLOWING GRID POINT IDS ARE REFERENCED ON BULK DATA ENTRIES THAT ARE NOT SUPPORTED IN AUTOMATIC IT SUPERELEMENTS IF - OF POSSESSES DEPENDENT DEGREES FREEDOM. THE - UNSUPPORTED ENTRIES ARE: DPHASE, DELAY, TIC, SUPORT, SUPORT1, CBUSH, AND CAABSF USER ACTION: REMOVE THE GRIDS FROM ALL UNSUPPORTED ENTRIES OR REASSIGN THE DEPENDENT DEGREES OF - FREEDOM - TO INDEPENDENT DEGRE ES - OF - FREEDOM. GRIDPOINTS: ----------- *** SYSTEM WARNING MESSAGE 7558 (RWELDD) 7558.0 FOR SPOT WELD GRID GS ID=%1 THE CONSTRAINT EQUATIONS ARE INCOMPLETE. THE CONSTRAINT FOR COMPONENT %2 CANNOT BE GENERATED BECAUSE THERE ARE NOT ENOUGH UNCONSTR AINED DEGREES OF FREEDOM AVAILABLE FOR THE M - SET. *** SYSTEM FATAL MESSAGE 7558 (RWELDD) 7558.1 AN ERROR OCCURED PROCESSING SPOT WELD ELEMENT ID=%1 .

560 VERIFY THE NODAL CONNECTIVITY IS VALID. *** USER WARNING MESSAGE 7558 (RWELDD) 7558.2 THE PROJECTION OF GA TO THE ELEMENT FOR WELD ID=%1 FALLS OUTSIDE THE ELEMENT BY %2 PERCENT *** USER INFORMATION MESSAGE 7559 (TRLGCD/S and FRRD1A) 7559.0 THIS %1 RESPONSE ANALYSIS INVOLVES THE FOLLOWING TYPES OF EXCITATION -- *** USER FATAL MESSAGE 7559 (FRRD1A) 7559.2 %1 BULK DATA WITH SID= %2 CONTAINS A MISSING OR INVALID BULK DATA REFERENCE. *** USER WARNING MESSAGE 7559 (FRRD1A) 7559.3 AVAILABLE MEMORY IS LESS THAN THE MEMORY NEEDED TO HOLD LOADS AT DIFFERENT FREQUENCIES/TIMES INTERVALS. THIS WILL IMPACT PEFORMANCE AS SPILL LOGIC WILL BE USED. PLEASE INCREASE MEMORY BY %1 WORDS TO HOLD THE LOADS INCORE *** USER FATAL MESSAGE 7560 (DSAD11) 7560.0 MODE %1, WHICH IS SPECIFIED ON A DRES P1 ENTRY, HAS AN EIGENVALUE OF %2 WHICH IS LESS THAN (OR EQUAL TO) 0.0. USER INFORMATION: THIS MODE COULD BE A RIGID BODY MODE. USER ACTION: REVIEW LIST OF REAL EIGENVALUES AND SELECT ONLY ELASTIC MODE NUMBER FOR ATTA FIELD (FIELD 7) ON DRESP1. *** SYSTEM FATAL MESSAGE 7561 (APD2) 7561.0 THE NUMBER OF INTERFERENCE GROUPS EXCEEDS THE MAXIMUM NUMBER %1 ALLOWED. *** SYSTEM FATAL MESSAGE 7562 (MAPGEN) 7562.0 THE SIZE OF THE MAPPING MATRIX CREATED IS %1 BY %2. IT SHOULD BE %3 BY %4. *** SYSTEM FATAL MESSAGE 7563 (SEP2MT) 75 63.0 POINT IDS %1 AND %2, WHICH ARE SPECIFIED ON THE DMIG BULK DATA ENTRY WITH NAME=%3, ARE INTERIOR TO DIFFERENT SUPERELEMENTS. *** SYSTEM FATAL MESSAGE 7564 (MTMD36) 7564.0 ERROR OCCURRED WHILE ATTEMPTING TO READ ASSOCIATED INDEX FOR FILE %1. *** USER FATAL MESSAGE 7565 (SEQP) 7565.0 NTIPS=%1 IS NOT DIVISIBLE BY THE NUMBER OF PROCESSORS=%2. USER ACTION: MODIFIY THE VALUE OF NTIPS OR THE NUMBER

561 OF PROCESSORS. *** USER WARNING MESSAGE 7566 (SEQP) 6.0 756 THE FOLLOWING COMBINATION OF PARAMETER VALUES IS NOT VALID: NTIPS = %1, TIPSCOL = %2, ZCOLLCT = %3. USER INFORMATION: VALID SETTINGS REQUIRE TIPSCOL*ZCOLLCT <= NTIPS. THEREFORE, TIPSCOL AND ZCOLLCT HAVE BEEN CHANGED TO A VALUE OF 2. *** USER FATAL MESSAGE 7567 (SEQP) 7567.0 THE SUPER CASE CONTROL COMMAND HAS BEEN SPECIFIED. USER INFORMATION: THE SUPER COMMAND IS NOT PERMITTED WITH THE AUTOMATIC MODEL PARTITIONER. D REWRITE THE SUBCASES USER ACTION: CONSOLIDATE AN WITHOUT THE SUPER COMMAND. *** USER WARNING MESSAGE 7567 (SEQMRB) 7567.1 THE SUPORT OR SUPORT1 BULK DATA ENTRY HAS BEEN SPECIFIED ALONG WITH ACMS. USER INFORMATION: THE SUPORT AND SUPORT1 ENTRIES WILL BE IGNORED. *** USER FATAL MESSAGE 7568 (SECNV1 and SECNV2) 7568.0 POINT ID %1 REFERENCED ON THE %2 BULK DATA ENTRY %3 IS NOT A GRID POINT *** USER FATAL MESSAGE 7568 (SECNV3) 7568.1 POINT ID %1 REFERENCED ON THE FOLLOWING %2 BULK DATA ENTRY %3 IS NOT A GRID POINT *** USER FATAL MESSAGE 7569 (DOPR1B) 7569.0 INITIAL VALUE ON DESVAR ENTRY ID = %1 IS OUTSIDE THE RANGE OF DISCRETE VALUES SPECIFIED ON DDVAL ENTRY ID = %2. USER ACTION: CHANGE THE INITIAL VALUE ON THE DESVAR ENTRY OR THE DISCRETE VALUES ON DDVAL ENTRY. *** USER INFORMATION MESSAGE 7570 ( VECPLX ) 7570.0 RESULTS OF RIGID BODY CHECKS OF MATRIX %1%2 %3%4 FOLLOW: PRINT RESULTS IN ALL SIX DIRECTIONS AGAINST THE LIMIT OF %5 DIRECTION STRAIN ENERGY PASS/FAIL --------- --------- ------------- 1 %6 %7 2 %8 %9 3 %10 %11 4 %12 %13 5 %14 %15 6 %16 %17

562 SOME POSSIBLE REASONS MAY LEAD TO THE FAILURE: 1. CELASI ELEMENTS CONNECTING TO ONLY ONE GRID POINT; COINCIDENT POINTS; 2. CELASI ELEMENTS CONNECTING TO NON - COLLINEAR DOF; 3. CELASI ELEMENTS CONNECTING TO NON - 4. IMPROPERLY DEFINED DMIG MATRICES; *** USER INFORMATION MESSAGE 7570 ( VECPLX ) 7570.1 RESULTS OF RIGID BODY CHECKS OF MATRIX %1%2 %3%4 FOLLOW: LIMIT OF PRINT RESULTS IN ALL SIX DIRECTIONS AGAINST THE %5 DIRECTION STRAIN ENERGY PASS/FAIL ------------- --------- --------- 1 %6 %7 2 %8 %9 3 %10 %11 4 %12 %13 5 %14 %15 6 %16 %17 SOME POSSIBLE REASONS MAY LEAD TO THE FAILURE: 1. MULTIPOINT CONSTRAINT EQUATIONS WHICH DO NOT SATISFY RIGID BODY MOTION; - 2. RBE3 ELEMENTS FOR WHICH THE INDEPENDENT DEGREE OF - - FREEDOM CANNOT DESCRIBE ALL POSSIBLE RIGID - BODY MOTIONS. *** USER INFORMATION MESSAGE 7570 ( VECPLX ) 7570.2 RESULTS OF RIGID BODY CHECKS OF MATRIX %1%2 %3%4%5%6 FOLLOW: PRINT RES ULTS IN ALL SIX DIRECTIONS AGAINST THE LIMIT OF %7 DIRECTION STRAIN ENERGY PASS/FAIL ------------- --------- --------- 1 %8 %9 2 %10 %11 3 %12 %13 4 %14 %15 5 %16 %17 6 %18 %19 SOME POSSIBLE REASONS MAY LEAD TO THE FAILURE: 1. MPC EQUATIONS WHICH DO NOT SATISFY RIGID BODY - MOTION; 2. RBE3 ELEMENTS FOR WHICH THE INDEPENDENT DOF CANNOT DESCRIBE ALL POSSIBLE RIGID BODY MOTIONS; - 3. PARAM,AUTOSPC HAS OVER - CONSTRAINED THE MODEL. *** USER INFORMATION MESSAGE 7570 ( VECPLX ) 7570.3

563 RESULTS OF RIGID BODY CHECKS OF MATRIX %1%2 %3%4 FOLLOW: PRINT RESULTS IN ALL SIX DIRECTIONS AGAINST THE LIMIT OF %5 DIRECTION STRAIN ENERGY PASS/FAIL --------- ------------- --------- 1 %6 %7 2 %8 %9 3 %10 %11 4 %12 %13 5 %14 %15 6 %16 %17 POSSIBLE REASONS MAY LEAD TO THE FAILURE: SOME - 1. CONSTRAINTS WHICH PREVENT RIGID BODY MOTION. *** USER INFORMATION MESSAGE 7570 ( VECPLX ) 7570.4 RESULTS OF RIGID BODY CHECKS OF MATRIX %1%2 %3%4 FOLLOW: LIMIT OF PRINT RESULTS IN ALL SIX DIRECTIONS AGAINST THE %5 DIRECTION STRAIN ENERGY PASS/FAIL --------- --------- ------------- 1 %6 %7 2 %8 %9 3 %10 %11 4 %12 %13 5 %14 %15 6 %16 %17 SOME POSSIBLE REASONS MAY LEAD TO THE FAILURE: IF THE MODEL HAS PASSED THE PREVIOUS CHECKS FOR THE G - SET AND - SET, N THEN: 1. THE MODEL IS NOT INTENDED TO BE FREE - FREE WHICH INDICATES THAT THE MODEL IS PROPERLY CONSTRAINED TO GROUND; 2. THE REFERENCE GRID POINT (GRID=GID ON THE GROUNDCHECK COMMAND) IS LOCATED TOO FAR FROM THE MODEL'S CENTER OF GRAVITY. IT IS RECOMMENDED THAT THE REFERENCE GRID POINT BE LOCATED AS CLOSE AS POSSIBLE TO THE MODEL'S CENTER OF GRAVITY OF THE MODEL (SEE THE GRID POINT WEIGHT GENERATOR OUTPUT); 3. PARAM,AUTOSPC,YES CONSTRAINS NEAR - SINGULAR DEGREES OF - FREEDOM. WHEN A - FINITE ELEMEN T MODEL WITH AUTOSPC FAILS THE A - SET CHECK, IT IS NOT EVIDENT

564 THAT GROUNDING HAS OCCURRED. THE USE OF PARAM,SNORM WILL NOT ELIMINATE THE SPURIOUS FAILURE. *** USER FATAL MESSAGE 7571 (DRESP3) 7571.0 N THE NUMBER OF CHARACTERS IN THE USRDATA FIELD O DRESP3 ENTRY %1 IS %2 WHICH EXCEEDS THE MAXIMUM NUMBER OF %3 CHARACTERS. *** SYSTEM FATAL MESSAGE 7572 (DFMSYN) 7572.0 A LOGIC ERROR was encountered IN THE SYMBOLIC PHASE OF THE SPARSE DECOMPOSITION (EXTREME REORDERING). USER ACTION: USE METIS OR GRID BASED MMD REORDERING TO AVOID THE ERROR. - RE SUBMIT THE JOB WITH ONE OF THE FOLLOWING VALUES FOR SYSTEM(206): SYSTEM(206)=1 (GRID BASED MMD) SYSTEM(206)=8 (GRID BASED METIS) OR SYSTEM(206)=9 (SELECTS BEST OF THE TWO ABOVE) *** SYSTEM FATAL MESSAGE 7572 (DFMSYN) 7572.1 AN OVERFLOW ERROR was encountered IN THE SYMBOLIC PHASE OF THE SPARSE DECOMPOSITION (EXTREME REORDERING). - SUBMIT THE JOB WITH THE ILP64 VERSION OF USER ACTION: RE NASTRAN. OR USE A DIFFERENT RE - ORDER ING SCHEME VIA SYSTEM(206). *** USER FATAL MESSAGE 7573 (MKAEF1) 7573.0 AN AEFORCE BULK DATA ENTRY REFERENCES %1 ENTRY ID = %2 WHICH IS UNDEFINED. *** USER FATAL MESSAGE 7573 (MKAEF1) 7573.1 AN AEFORCE BULK DATA ENTRY REFERENCES %1 ENTRY ID = %2 WHICH IS UNDEFINED. *** USER FATAL MESSAGE 7574 (MKAEF1) 7574.0 THERE IS AEFORCE/STRUCT BULK DATA ENTRY, BUT NO REFERENCED UXVEC OR FORCEI/MOMENTI BULK DATA ENTRY. MESSAGE 7575 (IFS4P) *** USER FATAL 7575.0 TEMPP3 BULK DATA CARD IS NO LONGER AVAILABLE. USER ACTION: USE TEMPP1. *** SYSTEM WARNING MESSAGE 7576 (LDNSSEL) 7576.0 UNABLE TO LOAD NSERVER_SELECT CLAUSE(S) FROM FILE. USER INFORMATION: CLAUSE(S) WILL BE IGNORED. USER ACTION: RE ENTER CLAUSES OR CONTACT SIEMENS PLM - SOFTWARE CUSTOMER SUPPORT. *** SYSTEM WARNING MESSAGE 7577 (NSAINDX) 7577.0 UNABLE TO PROCESS NSERVER_SELECT CLAUSE %1. USER INFORMATION: CLAUSE WILL BE IGNORED.

565 USER ACTION: CHECK SYNTAX, INCR EASE MEMORY. *** SYSTEM WARNING MESSAGE 7803 (NSAINDX) 7578.0 CORRUPT NSERVER_SELECT MEMORY STORAGE AREA. USER INFORMATION: CLAUSE(S) WILL BE IGNORED. USER ACTION: REMOVE EXISTING CLAUSE(S) AND RE - ENTER. *** USER WARNING MESSAGE 7579 (NSASELK) 7579.0 RELATION CLAUSE NOT FOUND IN NSERVER_SELECT %1 NSERVER_SELECT IGNORED. USER ACTION: ADD RELATION *** USER WARNING MESSAGE 7580 (NSASELK) 7580.0 USE EITHER RECORDNO=%1 OR ELTYPE=%2 BUT NOT BOTH ON: NSERVER_SELECT IGNORED. USER INFORMATI USER ACTION: CHANGE RELATION *** USER WARNING MESSAGE 7581 (NSSELWH) 7581.0 NSERVER_SELECT WHERE CLAUSE STARTING WITH %1 IS TOO LONG. USER INFORMATION: WHERE CLAUSE IS IGNORED. USER ACTION: REDUCE WHERE CLAUSE SIZE TO LESS THAN %2 CHARACTERS *** SYSTEM FATAL MESSAGE 7582 (..various..) 7582.0 INTERNAL LOGIC ERROR. LOCW OFFSET VALUE TOO LARGE FOR 32 BIT INTEGER. - ERROR INFORMATION: %1 INVALID OFFSET VALUE: %2 USER ACTION: CONTACT SIEMENS PLM SOFTWARE CUSTOMER SUPPORT. *** USER FATAL MESSAGE 7583 (IFP6) 7583.0 THE REFERENCED MATi BULK DATA ENTRY ID =%1 IS GREATER THAN 400000000. USER INFORMATION: WHEN PCOMP BULK DATA ENTRIES ARE USE THE MATi IDs MUST BE LESS THAN 400000000. *** USER WARNING MESSAGE 7584 (MPFGPL) 7584.0 THE CASE CONTROL SECTION DOES NOT CONTAIN A DEFINITION FOR SET ID %1. User Information: Panel grid mode participation factor processing will be skipped for this set. *** USER WARNING MESSAGE 7585 (MPFSTR) 7585.0 GRID ID %1 SPECIFIED FOR PANEL %2%3 IS NOT A MEMBER OF THE A - SET IN THE STRUCTURAL MODEL. User Information: No Mode participation factors will be computed.

566 *** USER WARNING MESSAGE 7586 (PARAML) 7586.0 E PARAML MODULE WITH DMI OPTION IS OVERFLOWING TH WITH A VALUE OF %1. USER ACTION: REPLACE THE PARAML MODULE WITH THE SCALAR MODULE FOR THIS PURPOSE. User Information: The SCALAR module is able to extract double precision terms which allow numbers in this range. *** USER WARNING MESSAGE 7586 (PARAML) 7586.1 THE PARAML MODULE WITH DMI OPTION IS OVERFLOWING WITH A VALUE OF (%1,%2). USER ACTION: REPLACE THE PARAML MODULE WITH THE SCALAR MODULE FOR THIS PURPOSE. User Information: The SCALAR module is able to extract double precision terms which allow numbers in this range. *** USER WARNING MESSAGE 7586 (PRMLXY) 7586.2 - INVALID VALUE OF, %1%2, IS SPECIFIED FOR THE TYPE OF Y VALUE IN X Y PLOT COMMANDS. - User Information: The legitimate values are listed as follows: ACCE : Acceleration in the physical set BOUT : Slideline contact output DISP : Displacement in the physical set FMPF : Fluid modal participation factor FORC : Element force FPRE : Fluid pressure Grid modal participation factor GMPF : Panel LMPF : Load modal participation factor - point force of constraint MPCF : Multiple NFOR : Nonlinear applied load OLOA : Applied load PMPF : Panel modal participation factor PRES : Pressure SACC : Acceleration in the so lution set SDIS : Displacement in the solution set SMPF : Structural modal participation factor SPCF : Single - point force of constraint STRA : Element strain STRE : Element stress SVEL : Velocity in the solution set VELO : Velocity in the physical s et VG : Flutter analysis

567 *** USER WARNING MESSAGE 7586 (PRMLXY) 7586.3 - INVALID VALUE OF, %1%2, IS SPECIFIED FOR THE TYPE OF Y Y PLOT COMMANDS. VALUE IN X - *** USER WARNING MESSAGE 7587 (GKAM) 7587.0 THE MODESELECT CASE CONTROL COMMAND FOR %1 IS IGNORED IN THIS MODAL %2 ANALYSIS AS IT REFERENCES BOTH AN UNDEFINED SET %3 AND NON - EXISTENT %1 MODE %3 *** USER INFORMATION MESSAGE 7588 (GKAM) 7588.0 BASED ON THE MODESELECT CASE CONTROL COMMAND OR T HE USER PARAMETERS LMODES, LFREQ OR HFREQ, ONLY %1 OF THE %2 COMPUTED %3 MODES (MODES %4 THROUGH %5) WILL BE USED IN THIS MODAL %6 ANALYSIS *** USER INFORMATION MESSAGE 7589 (GKAM) 7589.0 BASED ON THE MODESELECT CASE CONTROL COMMAND, ONLY THE FOL LOWING %1 OF THE %2 COMPUTED %3 MODES WILL BE USED IN THIS MODAL %4 ANALYSIS -- *** USER FATAL MESSAGE 7590. 7590.0 CWELD ELEMENT ID %1 CONNECTS TO A SURFACE WHICH HAS AN INTERIOR ANGLE POSSIBLY GREATER THAN OR EQUAL TO 180 DEGREES. *** USER FATAL MESSAGE 7591 (STPDA) 7591.0 A PAERO4 (STRIP THEORY) BULK DATA ENTRY USES THE PRANDTL GLAUERT - COMPRESSIBILITY CORRECTION (CLA= - 1) AND SPECIFIES A SUPERSONIC MACH NUMBER OF %1 ON THE ACCOMPANYING %2 ENTRY. WITH THE SWEEP S RESULTS IN A CONFIGURATION ANGLE OF %3 DEGREES, THI WHERE THE PRANDTL - GLAUERT CORRECTION IS NOT APPLICABLE. USER INFORMATION: THE CLA = - 1 OPTION IS ONLY APPLICABLE AT SUBSONIC SPEEDS. IF STRIP THEORY IS TO BE USED SUPERSONICALLY, SET CLA=1 OR CLA=0 WITH NCIRC .NE. 0 *** USER FATAL MESSAGE 7592 (A?) 75 92.0 ERROR CODE %1 HAS OCCURRED IN THE NONLINEAR AERO DATABASE INTERPOLATOR. *** USER FATAL MESSAGE 7592 (A?) 7592.1 ERROR CODE %1 HAS OCCURRED IN THE NONLINEAR AERO DATABASE INTERPOLATOR. THERE ARE DUPLICATE STATES IN THE DATABASE OVER WHICH

568 INTERPOLATION IS NEEDED. USER ACTION: REMOVE THE DUPLICATE STATES. *** USER FATAL MESSAGE 7592 (A?) 7592.2 ERROR CODE %1 HAS OCCURRED IN THE NONLINEAR AERO DATABASE INTERPOLATOR. FEW STATES TO INTERPOLATE OVER THE THERE ARE TOO DIMENSIONALITY OF THE SPACE. USER ACTION: INCREASE THE NUMBER OF POINTS TO SPAN THE SPACE, OR REMOVE OR CONSTRAIN SOME DIMENSIONS FROM THE INTERPOLATION. *** USER FATAL MESSAGE 7592 (A?) 7592.3 ERROR CODE %1 HAS OCCURRED IN THE NONLINEAR AERO DATABASE INTERPOLATOR. THE INTERPOLATION MATRIX BG IS SINGULAR. USER ACTION: REDEFINE THE SET OF HARD POINTS BY EITHER ADDING OR DELETING SOME INSTANCES. *** USER FATAL MESSAGE 7592 (A?) 7592.4 ERROR CODE %1 HAS OCCURRED IN THE NONLINEAR AERO DATABASE INTERPOLATOR. THE INTERPOLATION MATRIX A3 IS SINGULAR. USER ACTION: REDEFINE THE SET OF HARD POINTS BY EITHER ADDING OR DELETING SOME INSTANCES. *** USER FATAL MESSAGE 7592 (A?) 7592.5 OR CODE %1 HAS OCCURRED IN THE NONLINEAR AERO ERR DATABASE INTERPOLATOR. A PARAMETER (DIMENSION) IN THE INTERPOLATION HAS ONLY A SINGLE KNOWN VALUE, BUT YOU HAVE REQUESTED INTERPOLATION TO A DIFFERENT VALUE. USER ACTION: FIX VALUES OF CONSTANTS AT THE DATAB ASE VALUE, OR ADD ADDITIONAL STATES TO ALLOW INTERPOLATION. *** USER FATAL MESSAGE 7592 (A?) 7592.6 ERROR CODE %1 HAS OCCURRED IN THE NONLINEAR AERO DATABASE INTERPOLATOR. THE NONLINEAR DATABASE INTERPOLATION FAILED TO FIND A WITH THE MINIMUM 2 VALUES PER USABLE SET OF STATES PARAMETER. USER ACTION: ADD ADDITIONAL STATES TO THE DATABASE. *** USER FATAL MESSAGE 7592 (A?) 7592.7 ERROR CODE %1 HAS OCCURRED IN THE NONLINEAR AERO DATABASE INTERPOLATOR. THERE IS AN INADEQUATE SET OF STATES TO PERFORM THE INTERPOLATION.

569 USER ACTION: ADD ADDITIONAL STATES TO THE DATABASE. *** USER FATAL MESSAGE 7592 (A?) 7592.8 ERROR CODE %1 HAS OCCURRED IN THE NONLINEAR AERO DATABASE INTERPOLATOR. THERE IS AN IN ADEQUATE SET OF STATES IN THE SECONDARY SEARCH. USER ACTION: ADD ADDITIONAL STATES TO THE DATABASE. *** USER WARNING MESSAGE 7593 (MDG2SP) 7593.0 THE MSET FIELD IS SPECIFIED OFF ON PWELD ENTRY ID %1 FOR CWELD ELEMENT ID %2. USER INFORMATION: MSET IS RESET TO ON BECAUSE MSET=OFF IS ONLY AVAILABLE WHEN TWO SURFACE PATCHES ARE CONNECTED. *** USER WARNING MESSAGE 7594 (MDG2SW) 7594.0 TWO SURFACE PATCHES WHICH ARE CONNECTED BY CWELD ELEMENT ID %1 SHARE THE SAME GRID ID %2. USER INFORMATION: THE CWELD ELEMENT WILL BE IGNORED BECAUSE IT CONNECTS TWO SURFACE PATCHES WHICH ARE ALREADY CONNECTED THROUGH AT LEAST ONE COMMON GRID. USER ACTION: TO ENSURE THE ELEMENT IS NOT IGNORED THEN CORRECT THE CONNECTIVITY OR SET MSET TO ON ON THE REFERENCED PWELD ENTRY. *** SYSTEM FATAL MESSAGE 7595 (CHKCOME) 7595.0 REQUIRED INPUT DATA BLOCK SEMAP MISSING FROM CHKCOME DMAP COMMAND. *** USER FATAL MESSAGE 7596 (FRRD1A) 7596.0 AN ENFORCED VELOCITY OR ACCELERATION IS SPECIFIED AT ZERO FREQUENCY. USER ACTION: REMOVE THE ZERO FREQUENCY FROM THE SELECTED FREQi BULK DATA ENTRY. *** USER FATAL MESSAGE 7596 (FRRD1A) 7596.1 THE ACSRCE BULK DATA ENTRY AND THE RLOAD/TLOAD ENTRY P OINT TO THE SAME FREQUENCY DEPENDENT TABLES USER ACTION: CHANGE THE TABLE ID FOR ACSCRE OR RLOAD/TLOAD AND MAKE IT UNIQUE *** USER WARNING MESSAGE 7597 (PQVOLD) 7597.0 ELEMENT ID = %1 REFERENCED BY GMQVOL ENTRY WITH LID = %2 IS UNDEFINED. USER AC TION: CHECK GMQVOL ENTRY TO ENSURE THAT SPECIFIED ELEMENT EXISTS. *** USER WARNING MESSAGE 7598 (MTMD40) 7598.0 READ ERROR ON INPUT DATA BLOCK.

570 *** SYSTEM FATAL MESSAGE 7599 (CHKCOMG) 7599.0 REQUIRED INPUT DATA BLOCK SGPDT MISSING FROM CHKCOMG DMAP COMMAND. *** SYSTEM FATAL MESSAGE 7600 (CHKCOMG) 7600.0 REQUIRED INPUT DATA BLOCK EQEXINS MISSING FROM CHKCOMG DMAP COMMAND. *** SYSTEM FATAL MESSAGE 7601 (CHKCOME) 7601.0 REQUIRED OUTPUT DATA BLOCK SEELEMS MISSING FROM CHKCOME DMAP COMMAND. *** USER WARNING MESSAGE 7602 (DOPR1I) 7602.0 ON PROPERTY ENTRY %1 WITH PID=%2 AND PROPERTY NAME=%3, THE PROPERTY VALUE %4 IS GREATER THAN THE MAXIMUM PMAX VALUE %5 SPECIFIED ON THE %6 %7 ENTRY. USER ACTION: MODIFY THE PROPERTY ENTRY ON THE %8 ENTRY ACCORDINGLY. USER INFORMATION: STARTING THE DESIGN WITH INFEASIBLE PROPERTIES WILL IMPEDE THE DESIGN PROCESS. *** US ER WARNING MESSAGE 7602 (DOPR1I) 7602.1 ON PROPERTY ENTRY %1 WITH PID=%2 AND PROPERTY NAME=%3, THE PROPERTY VALUE %4 IS LESS THAN THE MINIMUM PMIN VALUE %5 SPECIFIED ON THE %6 %7 ENTRY. USER ACTION: MODIFY THE PROPERTY ENTRY ON THE %8 ENTRY ACCORDINGLY. USER INFORMATION: STARTING THE DESIGN WITH INFEASIBLE PROPERTIES WILL IMPEDE THE DESIGN PROCESS. *** USER FATAL MESSAGE 7602 (DOPR1I) 7602.2 ON PROPERTY ENTRY %1 WITH PID=%2 AND PROPERTY NAME=%3, THE PROPERTY VALUE %4 IS GREATER THAN THE MAXIMUM PMAX VALUE %5 SPECIFIED ON THE %6 %7 ENTRY. USER INFORMATION: STARTING THE DESIGN WITH INFEASIBLE PROPERTIES WILL IMPEDE THE DESIGN PROCESS. USER ACTION: 1. MODIFY THE PROPERTY ENTRY ON THE %8 ENTRY ACCORDINGLY, OR 2. USE PLVIOL ,1 ON DOPTPRM TO FORCE THE DESIGN PROCESS TO PROCEED WITH INFEASIBLE PROPERTIES (MAY PRODUCE LESS DESIRABLE RESULTS) *** USER FATAL MESSAGE 7602 (DOPR1I) 7602.3 ON PROPERTY ENTRY %1 WITH PID=%2 AND PROPERTY NAME=%3, THE PROPERTY VALUE %4 IS LESS THAN THE MINIMUM PMIN VALUE %5 SPECIFIED ON THE %6 %7 ENTRY.

571 USER INFORMATION: STARTING THE DESIGN WITH INFEASIBLE PROPERTIES WILL IMPEDE THE DESIGN PROCESS. USER ACTION: 1. MODIFY THE PROPERTY ENTRY ON THE %8 ENTRY ACCORDINGLY, OR PTPRM TO FORCE THE DESIGN PROCESS 2. USE PLVIOL,1 ON DO TO PROCEED WITH INFEASIBLE PROPERTIES (MAY PRODUCE LESS DESIRABLE RESULTS) *** SYSTEM FATAL MESSAGE 7603 (CHKCOME) 7603.0 INSUFFICIENT MEMORY FOR CHKCOME DMAP COMMAND. *** USER FATAL MESSAGE 7604 (DOPR1I) 7604.0 A DESIGNED PROPERTY DIFFERS FROM THE VALUE PROVIDED ON THE PROPERTY ENTRY BY MORE THAN %1. USER ACTION: MODIFY EITHER THE PROPERTY ENTRY, THE %2 %3 ENTRY OR PTOL ON THE DOPTPRM ENTRY. E 7605 (CHKCOMG) *** SYSTEM FATAL MESSAG 7605.0 INSUFFICIENT MEMORY FOR CHKCOMG DMAP COMMAND. *** SYSTEM FATAL MESSAGE 7606 (CHKCOMG) 7606.0 REQUIRED OUTPUT DATA BLOCK SEGRIDS MISSING FROM CHKCOMG DMAP COMMAND. *** SYSTEM FATAL MESSAGE 7607 (COMBOUT) 7607.0 COMBOUT MODULE REQUIRES 2 INPUT DATA BLOCKS. *** SYSTEM FATAL MESSAGE 7608 (COMBOUT) 7608.0 REQUIRED OUTPUT DATA BLOCK OUTC MISSING FROM COMBOUT DMAP COMMAND. *** SYSTEM FATAL MESSAGE 7609 (COMBO