Femap ошибка 316

ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2

PARAMETER NO. %3 NEEDS PARAMETER NAME

User information:

The parameter is not in correct format.

POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2

PARAMETER NO. %3 NEEDS PARAMETER NAME

BULK DATA PARAM CARD ERROR — MUST NOT DEFINE PARAMETER NAMED %1.

User information:

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

user cannot set the value of the parameter with name %1 on a PARAM

entry in Bulk Data.

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.

POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2

VALUE NEEDED FOR PARAMETER NO. %3

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

referenced module.

POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2

ILLEGAL INPUT DATA BLOCK SPECIFICATION.

ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2

ILLEGAL OUTPUT DATA BLOCK SPECIFICATION.

POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2

ILLEGAL OUTPUT DATA BLOCK SPECIFICATION.

ERROR IN DMAP INSTRUCTION NO. %1, ILLEGAL CHARACTER IN DMAP INSTRUCTION NAME.

User information:

The name of a module must be alpha-numeric characters, the first

character being alphabetic. Special characters are not allowed.

For example DMAP names like «8MOD» or «SETI=2» are not allowed..

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.

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.

ARRAY NAMED %1 OVERFLOWED

AT DMAP INSTRUCTION NO. %2.

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.

See the NX NASTRAN DMAP Module Dictionary.

POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2

INCONSISTENT LENGTH USED FOR PARAMETER NAMED %3

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.

POSSIBLE 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.

SYMBOL «%1» IS UNDEFINED

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.

POSSIBLE 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.

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.

EXTRANEOUS ‘ELSE’ / ‘ELSEIF’ STATEMENT AT INSTRUCTION %1

DATABLOCK NAMED %1 MUST BE DEFINED PRIOR TO THIS INSTRUCTION

USER ACTION: CHECK FOR CORRECT SPELLING, OR MISSING TYPE STATEMENT, AND RERUN.

User information:

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.

ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2

DATA BLOCK NAMED %3 MUST BE DEFINED PRIOR TO THIS INSTRUCTION

POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2

DATA BLOCK NAMED %3 MUST BE DEFINED PRIOR TO THIS INSTRUCTION

ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2

DATA BLOCK NAMED %3 IS NOT REFERENCED IN SUBSEQUENT FUNCTIONAL MODULE

POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2

DATA BLOCK NAMED %3 IS NOT REFERENCED IN SUBSEQUENT FUNCTIONAL MODULE

CANNOT FIND DATA BLOCK NAMED %1 ON DATA POOL TAPE

System information:

The contents of /XDPL/ do not match contents of Pool Tape.

ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2

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.

POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2

PARAMETER NAMED %3 HAS AN INCONSISTENT USER AUTHORIZATION

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.

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.

LABEL NAMED %1 NOT REFERENCED

User information:

LABEL name appears only in a LABEL instruction. It is not necessary

to reference a LABEL.

ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2

DATA BLOCK NAMED %3 MUST BE DEFINED PRIOR TO THIS INSTRUCTION

POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2

DATA BLOCK NAMED %3 MUST BE DEFINED PRIOR TO THIS INSTRUCTION

CANNOT TRANSLATE DMAP INSTRUCTION NO. %1

System information:

Error in subroutine XSCNDM.

CANNOT FIND DATA BLOCK NAMED %1 ON OLD PROBLEM TAPE

ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2

WARNING ONLY — MAY NOT BE ENOUGH FILES AVAILABLE FOR MODULE REQUIREMENTS

FILES NEEDED = %3 FILES AVAILABLE = %4

POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2

WARNING ONLY — MAY NOT BE ENOUGH FILES AVAILABLE FOR MODULE REQUIREMENTS

FILES NEEDED = %3 FILES AVAILABLE = %4

NOT ENOUGH CORE FOR GPI TABLES.

System information:

The user must break up DMAP program.

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.

ERROR IN ALTER DECK — CANNOT FIND END OF DMAP INSTRUCTION

User information:

The user should check the ALTER part of the Executive Control Section.

TABLES INCORRECT FOR REGENERATING DATA BLOCK %1

System information:

File Name Table and MED Table used by routine XFLDEF are wrong. The

user can compensate by altering OUT and IN module(s) which regenerate

the data block.

ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2

PARAMETER NAMED %3 ALREADY HAD VALUE ASSIGNED PREVIOUSLY

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 assigned it

a value.

«%1» IS INVALID

ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2

DATA BLOCK NAMED %3 ALREADY APPEARED AS OUTPUT OR WAS USED AS INPUT BEFORE BEING DEFINED

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

INCORRECT REENTRY POINT

ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2

THIS INSTRUCTION CANNOT BE FIRST INSTRUCTION OF LOOP

POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2

THIS INSTRUCTION CANNOT BE FIRST INSTRUCTION OF LOOP

ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2

DATA SET %3 IS ALWAYS REGENERATED, THEREFORE IT WILL NOT BE CHECKPOINTED

POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2

DATA SET %3 IS ALWAYS REGENERATED, THEREFORE IT WILL NOT BE CHECKPOINTED

MPL TABLE (MODULE PROPERTIES LIST) IS INCORRECT

System information:

The error is in common block /XGP12/.

MPL TABLE (MODULE PROPERTIES LIST) IS INCORRECT

DECIMAL LOCATION RELATIVE TO MPL(1) = %1,MODULE NAME = %2

CANNOT FIND JUMP OSCAR ENTRY NEEDED FOR THIS RESTART

NOT ENOUGH OPEN CORE FOR XGPIBS ROUTINE

System information:

Additional core memory is required to compile DMAP or rigid format.

NAMED COMMON /XLINK/ IS TOO SMALL

System information:

There must be one word in LINK table for every entry in MPL.

INCORRECT FORMAT IN ABOVE CARD

User information:

The link specification updated data (DIAG 28, 29, 30) is incorrect.

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.

DUPLICATE MPL NAME ENCOUNTERED. NAME = %1

THE OSCAR REGION OF OPEN CORE IS INSUFFICIENT FOR DMAP CODE EXPANSION

PROGRAMMER INFORMATION: LOSCAR = %1

ENDIF AT DMAP STATEMENT # %1 IS MISSING AN IF THEN STATEMENT

IF THEN AT DMAP STATEMENT # %1 IS MISSING AN ENDIF STATEMENT

AN EXTRA «ELSE» STATEMENT EXISTS AT DMAP STATEMENT %1

%1 AT DMAP NO. %2 IS ILLEGALLY BRANCHING INTO OR OVERLAPS AN «IF THEN», «DO WHILE», OR «REPT»

ATTEMPT TO JUMP BACKWARDS AT DMAP STATEMENT %1

NO MATCHING DO WHILE FOR ENDDO AT DMAP STATEMENT %1

INSUFFICIENT CORE AVAILABLE FOR DO WHILE PROCESSING IN DMAP COMPILER

DMAP STRUCTURE HAS MISMATCHED NUMBER OF IF THEN AND ENDIF STATEMENTS

THE NUMBER OF %1 STATEMENTS IS LESS THEN THE NUMBER OF %2 STATEMENTS.

SUBDMAP STATEMENT PARAMETER %1 NOT DEFINED

TYPE STATEMENT PARAMETER %1 NOT IN VPS TABLE

MUST BE A CODE LOGIC ERROR FOR THIS TO HAPPEN

SYNTAX ERROR IN ABOVE DO WHILE STATEMENT

PARAMETER SYNTAX ERROR IN ABOVE STATEMENT. PARAMETER IS %1 — ERROR CODE = %2

User information:

If the value of a parameter 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.

If a parameter field is left blank on a CALL subDMAP statement, then

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.

THE PARAMETER NAMED %1 IS UNDEFINED

PARAMETER SYNTAX ERROR IN ABOVE STATEMENT IN PARAMETER POSITION NUMBER %1

ELSE AT DMAP STATEMENT # %1 APPEARS BEFORE AN ELSE IF THEN STATEMENT

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.

DATABLOCK %1 IS DECLARED APPEND ON A FILE STATEMENT

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.

THE ABOVE CARD HAS AN INCORRECT FORMAT.

ERROR CODE= %1

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

INSUFFICIENT STORAGE SPACE FOR NDDL DEFINED QUALIFIERS — NUMBER OF QUALIFIERS CURRENTLY LIMITED TO %1

INSUFFICIENT OPEN CORE TO HOLD NDDL DATA BLOCK DESCRIPTION FOR %1

—AVAILABLE OPEN CORE WORDS IS %2

INSUFFICIENT STORAGE SPACE FOR NDDL PATH CARDS

—STORAGE SPACE LIMITED TO %1 PATH CARDS

‘PATH=’ KEYWORD NOT FOUND ON NDDL DATA BLOCK STATEMENT FOR %1

NDDL PATH NAME = %1 ON DATA BLOCK STATEMENT FOR %2 HAS NOT BEEN DEFINED

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

NDDL PATH NAME = %1 ON DATA BLOCK STATEMENT FOR %2 HAS NOT BEEN DEFINED

NO NDDL DEPENDENCY CARDS FOUND

A QUALIFIER NAMED %1 USED ON A PATH CARD HAS NOT BEEN DEFINED

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.

THE PVA TABLE EXCEEDS THE MAXIMUM ALLOWABLE SIZE OF %1.

PROGRAMMER ACTION: INCREASE THE SIZE OF PVATB ARRAY.

INVALID LOGICAL ASSIGNMENT ATTEMPTED IN NDDL DESCRIPTION

INVALID ASSIGNMENT OF TRUE OR FALSE ATTEMPTED IN NDDL DESCRIPTION

THE DATA BLOCK DESCRIPTION FOR %1 IS MISSING THE ‘LOCATION= KEYWORD

LOCATION PARAMETER= %1 IS UNDEFINED FOR PARAMETER= %2

LOCATION PARAMETER= %1 IS UNDEFINED FOR DATA BLOCK= %2

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

THE NDDL TABLES INITIALIZED BY SUBROUTINE XCSA ARE BAD.

CHECK THE RECORD AND OPTIONS OF OPENS (I.E. WRT, WRTREW)

THE LIMIT ON THE NUMBER OF NDDL PARAMETERS HAS BEEN EXCEEDED.

USER INFORMATION: THE CURRENT LIMIT IS = %1

*** ERROR IN DATA BLOCK %1

*** ERROR IN DATA BLOCK %1 — RECORD %2

*** YOU MAY NOT SPECIFY TYPE=%3 FOR AN ARRAY

*** ERROR IN DATA BLOCK %1 — RECORD %2

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.

NDDL ‘PARAMETER’ DEFINITION TABLE NOT FOUND

User information:

Insert ACQUIRE NDDL or ACQUIRE NDDLOLD in FMS.

NDDL ‘QUALIFIER’ DEFINITION TABLE NOT FOUND

User information:

Insert ACQUIRE NDDL or ACQUIRE NDDLOLD in FMS.

NDDL ‘DATABLOCK’ DEFINITION TABLE NOT FOUND

User information:

Insert ACQUIRE NDDL or ACQUIRE NDDLOLD in FMS.

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.

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 SOFTWARE CUSTOMER SUPPORT.

DUMP OF BAD FIRST RECORD:

%3

%4

%5

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 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 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).

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 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

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).

A ‘TYPE’ STATEMENT DEFINES A QUALIFIER/PARAMETER %1 IN SUBDMAP %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

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).

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

arguments in the subDMAP.

SUBDMAP %1 CALLED BY SUBDMAP %2 CANNOT BE FOUND IN DATA BASE.

CALL STATEMENT %1 IN SUBDMAP %2 HAS A PARAMETER THAT DOES NOT MATCH CALLED SUBDMAP IN AUTHORIZATION CODE.

USER INFORMATION:

PARAMETER IS NUMBER %3

AUTHORIZATION CODE IS : %4

AUTHORIZATION CODE SHOULD BE: %5

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-COMPLEX S.P., ,6-COMPLEX D.P., 7-LOGICAL)

LENGTH IS : %6

LENGTH SHOULD BE : %7

SUBDMAP %1 CANNOT BE FOUND IN DATA BASE, —- MUST BE CODE LOGIC ERROR.

USER ACTION: SEND RUN TO SIEMENS PLM SOFTWARE CUSTOMER SUPPORT.

END-OF-FILE HIT WHILE READING SUBDMAP %1 —MUST BE CODE LOGIC ERROR.

USER ACTION: SEND RUN TO SIEMENS PLM SOFTWARE CUSTOMER SUPPORT.

A ‘TYPE’ STATEMENT DEFINES A VARIABLE %1 IN SUBDMAP %2

WHICH IS DEFINED AS BOTH A QUALIFIER AND A PARAMETER IN THE ‘NDDL’

A ‘TYPE’ STATEMENT DEFINES A CHARACTER QUALIFIER/PARAMETER %1 IN SUBDMAP %2

WHICH DOES NOT MATCH THE CHARACTER LENGTH IN THE ‘NDDL’

MAIN SUBDMAP (%1) IS NOT IN THE DATA BASE

USER ACTION: CHECK SOL STATEMENT FOR CORRECT SOLUTION REQUEST

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

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

THE EXTERNAL SUBDMAP CALLS FOR %1 (MAIN) SUBDMAP WILL BE SATISFIED BY OBJECTS FROM EDSOBJ DBSET

OBJECT FILE FOR SUBDMAP %1 IS EMPTY.

USER ACTION: RECOMPILE THIS SUBDMAP.

DATABLOCK %1 IS REFERENCED ON A TYPE DB STATEMENT AND THE SUBDMAP STATEMENT.

USER ACTION: REMOVE THE REFERENCE FROM THE SUBDMAP STATEMENT OR THE TYPE DB STATEMENT.

User information:

If a datablock is on the SUBDMAP statement, 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.

NO ERROR MESSAGE EXISTS FOR XGPIMW INTERNAL CODE NUMBER %1

NO ERROR MESSAGE EXISTS FOR XGPIDG INTERNAL CODE NUMBER %1

NO ERROR MESSAGE EXISTS FOR PRXMSG INTERNAL CODE NUMBER %1 CALLED FROM %2 DURING %3 %4 PROCESSING

NO ERROR MESSAGE EXISTS FOR NDDMSG INTERNAL CODE NUMBER %1 CALLED FROM %2

NO ERROR MESSAGE EXISTS FOR LNKMSG INTERNAL CODE NUMBER %1 CALLED FROM %2

NO ERROR MESSAGE EXISTS FOR CEPMSG INTERNAL ERROR CODE %1 CALLED FROM %2

%1 %2 NOT FOUND IN %3 VPS TABLE.

UNABLE TO ADD %1 CONSTANT %2 TO %3 VPS TABLE

TYPE CODE %1 IS CURRENTLY NOT IMPLEMENTED IN THE %2 EXPRESSION PARSER

NULL CHARACTER %1 AT POSITION %2 OF %3 %4

SYNTAX ERROR IN STRING CONSTANT AT POSITION %1 OF %2 %3

SYNTAX ERROR DETECTED IN STRING AT POSITION %1 OF %2 %3

CHARACTER = %4

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

following the sign—make sure that there is a zero between the

sign and the decimal point.

INVALID %1 PRECISION CONSTANT AT POSITION %2 OF %3 %4

INVALID CHARACTER DETECTED IN COMPLEX CONSTANT AT POSITION %1 OF %2 %3

MULTIPLE SIGN DETECTED IN COMPLEX CONSTANT AT POSITION %1 OF %2 %3

EMBEDDED BLANKS DETECTED IN COMPLEX NUMBER AT POSITION %1 OF %2 %3

CHARACTER STRING EXCEEDS 80 CHARACTERS AT POSITION %1 OF %2 %3

%1 PRECEDED BY %2 AT POSITION %3 OF %4 %5

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

BINARY OPERATORS CANNOT BE THE FIRST SYMBOL FOUND IN AN ARITHMETIC OR LOGICAL EXPRESSION

VARIABLE NAME EXCEEDS 8 CHARACTERS AT POSITION %1 OF %2 %3.

VARIABLE NAME IS TRUNCATED TO %4.

RESULTANT PROCESSING MAY BE INCORRECT OR AMBIGUOUS.

THE %1 OSCAR %2 ADDRESS POINTER (%3) IS INVALID

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).

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

(example: real-single precision). If not, there are expressions to

convert from one type (example: integer) to another

(example: real-single precision).

ASSIGNMENT OF %1 VALUE TO %2 VARIABLE IS ILLEGAL IN %3 %4S.

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).

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

(example: real-single precision). If not, there are expressions to

convert from one type (example: integer) to another

(example: real-single precision).

NON-NUMERIC %1 USED IN EXPONENTIATION OPERATION DURING %2 %3 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 precision). If not, there are expressions to

convert from one type (example: integer) to another

(example: real-single precision).

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 precision). If not, there are expressions to

convert from one type (example: integer) to another

(example: real-single precision).

MIXED MODE USAGE BY THE ARITHMETIC OPERATOR %1 IS INVALID DURING %2 %3 PROCESSING.

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 are expressions to

convert from one type (example: integer) to another

(example: real-single precision).

THE %1 OPERATOR %2 CANNOT BE USED BETWEEN %3 AND %4 OPERANDS

DURING %5 %6 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 precision). If not, there are expressions to

convert from one type (example: integer) to another

(example: real-single precision).

THE %1 OPERATOR CANNOT BE USED ON %2 VALUES IN A %3 %4

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).

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.

THE KEYWORD %1 WAS USED AS A VARIABLE AT POSITION %2 OF %3 %4

NO INFORMATION AVAILABLE TO PROCESS ON %1 %2

THE FUNCTION %1 WAS NOT FOUND IN LIBRARY FUNCTION TABLE DURING %2 %3 PROCESSING.

THE NUMBER OF ARGUMENTS IN THE ARGUMENT LIST FOR %1 IS %2 THAN THE %3 %4 ARGUMENTS %5

NUMBER OF ARGUMENTS SPECIFIED WAS %6

%1 ARGUMENT FORMAT FOR FUNCTION %2 NOT DEFINED IN LIBRARY FUNCTION TABLE

%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 WITH %6 = %7

%1 OCCURRED DURING PROCESSING OF %2 STACK DURING %3 %4 PROCESSING.

PROGRAMMER INFORMATION: STACK POINTER = %5 WITH %6 = %7

SYNTAX ERROR DETECTED WHILE PROCESSING %1 PRECISION CONSTANT IN A %2 %3.

USER ACTION: CORRECT SYNTAX FOR %4 PRECISION CONSTANT AND RESUBMIT RUN.

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.

FROM XRCARD ABOVE.

DATA ERROR IN FIELD UNDERLINED.

THE MESSAGES ABOVE ARE FROM CRCARD.

BULK DATA ENTRY %1 CONTAINS INCONSISTENT DATA. SORTED ENTRY COUNT = %2

User information:

One or more of the Poisson’s ratios on a MAT3 entry is greater than 1.0.

ONE OR MORE GRID ENTRIES HAVE DISPLACEMENT COORDINATE SYSTEM ID OF -1

User information:

Coordinate system identification numbers of -1 indicate fluid grid

point in coupled fluid-structure analysis.

See Chapter 24 of NX NASTRAN Users Guide.

IFP MODULE CANNOT OPEN GINO FILE %1

System information:

Unexpected nonstandard return from OPEN.

READ LOGICAL RECORD ERROR.

System information:

Short record encountered. Bulk Data entries occupy 20 words.

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.

ILLEGAL NAME FOR BULK DATA ENTRY %1

User information:

See Section 5 of the NX NASTRAN Quick Reference Guide.

BULK DATA ENTRY %1 NOT ALLOWED IN %2 APPROACH.

User information:

See Section 5 of the NX NASTRAN Quick Reference Guide.

BULK DATA ENTRY %1 IMPROPER IN %2 APPROACH.

User information:

See Section 5 of the NX NASTRAN Quick Reference Guide.

BULK DATA ENTRY %1 NOT ALLOWED IN SAME DECK WITH AXIC CARD.

User information:

See Section 5 of the NX NASTRAN Quick Reference Guide.

%1 AND %2 ENTRIES ARE NOT ALLOWED IN THE SAME BULK DATA SECTION.

User information:

Use one or the other of the above bulk data entries, but not both.

NON-UNIQUE FIELD 2 ON BULK DATA ENTRY %1%2 SORTED ENTRY COUNT = %3

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 entries with the GID=2 in the same run.)

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.

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

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

variable in a real or integer field, such as using the letter O when

the number 0 is intended.

ILLEGAL NUMBER OF WORDS ON BULK DATA ENTRY %1%2 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

variable 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 immediately follow the previous bulk data

entry.

INVALID CALL FROM IFP : K = %1

System information:

Code error, machine failure, or cell is being destroyed.

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

make sure the number of entries is even.

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 format

make sure the number of entries is even.

THE PRECONDITIONER OPTION %1 SPECIFIED ON THE ITER ENTRY IS INVALID.

USER ACTION: CHECK BULK DATA CARD ITER.

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.

ILLEGAL DATA 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 format make

sure the number of entries is even.

ILLEGAL DATA ON BULK DATA ENTRY %1 ON SORTED ENTRY COUNT %2

USER INFORMATION:

%3 ID %4 EXCEEDS MAXIMUM VALUE ALLOWED %5.

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

Quick Reference Guide. If you are using the large field format make

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.

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.

BAD DATA OR FORMAT OR NON-UNIQUE NAME FOR DTI %1 SORTED CARD COUNT = %2

User information:

See Bulk Data entry description in Section 5 of the NX NASTRAN

Quick Reference Guide.

NO ROOM IN /XDPL/ FOR DTI %1

System information:

Overflow of Data Pool Table. See Chapter 2 of the NX NASTRAN

Programmer’s Manual.

IFP READING EOF ON NPTP.

System information:

Unexpected EOF encountered while attempting to read a bulk data entry.

ERROR ENCOUNTERED PROCESSING BULK DATA.

PROGRAMMER ACTION:INCREASE THE NUMBER OF LIST(S) MXLIST BY %1 WORDS.

ERROR ENCOUNTERED PROCESSING BULK DATA.

PROGRAMMER ACTION:INCREASE THE DEPTH OF THE LIST(S) MXDEEP BY APPROXIMATELY %1 WORDS.

IFP ERROR%1. LAST ENTRY PROCESSED IS %2.

SORTED ENTRY COUNT = %3

System information:

Code error in IFP or XSORT.

NON-UNIQUE PARAM NAME -%1-

User information:

All names of parameters must be unique.

ILLEGAL ENTRY TO IFS1P.

ILLEGAL ENTRY TO IFS8P.

ILLEGAL ENTRY TO IFS7P.

ILLEGAL ENTRY TO IFS6P.

ILLEGAL ENTRY TO IFS5P.

ILLEGAL ENTRY TO IFS4P.

ILLEGAL ENTRY TO IFS3P.

ILLEGAL ENTRY TO IFS2P.

ILLEGAL ENTRY TO IFS1P.

System information:

IFP code error detected in IFS1P, IFS2P, IFS3P, IFS4P, IFS5P, IFS6P.

INTERNAL ERROR IN IFS11P.

ILLEGAL ENTRY TO IFS11P.

ILLEGAL ENTRY TO IFS10P.

BLANK ENTRIES ENCOUNTERED WILL BE IGNORED.

User information:

Blank Bulk Data entries are ignored by NASTRAN.

BAD DATA OR FORMAT OR NON-UNIQUE NAME. DMI %1 SORTED CARD COUNT = %2

User information:

See Bulk Data entry description in Section 5 of the NX NASTRAN

Quick Reference Guide.

NO ROOM IN /XDPL/ FOR DMI %1

System information:

Overflow of Data Pool Table. See Chapter 2 of the NX NASTRAN

Programmer’s Manual.

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.

ONLY ONE(1) AXIC ENTRY ALLOWED.

User information:

See Bulk Data entry description in Section 5 of the NX NASTRAN

Quick Reference Guide.

NO ROOM IN MEMORY FOR PARAM ENTRIES.

System information:

Change overlay or increase core size.

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.

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.

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.

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.

THE EXPRESSION IN A CONVERT CLAUSE EQUATION HAS INVALID SYNTAX

*** USER ACTION:

1. REWRITE THE CONVERT CLAUSE EQUATION USING CORRECT SYNTAX

2. RESUBMIT RUN.

THE EXPRESSION IN A WHERE CLAUSE EQUATION HAS INVALID SYNTAX

*** USER ACTION:

1. REWRITE THE WHERE CLAUSE EQUATION USING CORRECT SYNTAX

2. RESUBMIT RUN.

THE VARIABLE ON THE LEFT-SIDE OF A CONVERT CLAUSE EQUATION WAS NOT FOUND IN THE PRIMARY DATABASE QUALIFIER TABLE

THE VARIABLE ON THE LEFT-SIDE OF A WHERE CLAUSE EQUATION WAS NOT FOUND IN THE PRIMARY DATABASE QUALIFIER TABLE

MORE THAN ONE %1 ENTRY EXISTS. ONLY ONE IS ALLOWED.

User information:

Make sure only one such entry exists.

THE LAST X-VALUE ON %1 ENTRY ID = %2

IS MISSING A CORRESPONDING Y-VALUE. THE

LAST X-VALUE WILL BE IGNORED.

User information:

There has to be an even number of entries. If there is an odd number,

then this message is issued and the last value ignored.

SUBCASE %1 DOES NOT INCLUDE AN ANALYSIS CASE CONTROL COMMAND.

USER INFORMATION: AN ANALYSIS COMMAND MUST BE SPECIFIED FOR EACH SUBCASE.

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.

SUBCASE %1 CONTAINS THE ANALYSIS = %2 COMMAND BUT LACKS THE REQUIRED METHOD CASE CONTROL COMMAND.

USER ACTION: FOR MULTIDISCIPLINARY ANALYSES THAT REQUIRE A NORMAL MODES OR BUCKLING SOLUTION,

THE METHOD COMMAND MUST BE SPECIFIED AT THE subcase LEVEL OR ABOVE THE SUBCASE LEVEL.

THERE ARE %1 MODAL TRANSIENT SUBCASES.

USER INFORMATION: ONLY ONE MODAL TRANSIENT SUBCASE IS PERMITTED WHEN PERFORMING MULTIDISCIPLINARY ANALYSIS.

THERE ARE MULTIPLE DESGLB COMMANDS IN THE CASE CONTROL SECTION.

USER INFORMATION: ONLY ONE DESGLB COMMAND IS PERMITTED.

THERE ARE MULTIPLE DESOBJ COMMANDS IN THE CASE CONTROL SECTION.

USER INFORMATION: ONLY ONE DESOBJ COMMAND IS PERMITTED.

DESGLB COMMAND = %1 IN SUBCASE = %2 IS DIFFERENT THAN THE PREVIOUS SUBCASE

USER INFORMATION: SPECIFY THE DESGLB COMMAND ABOVE THE SUBCASE LEVEL.

FACE TYPE %1 IS INVALID ON THE QHBDY ENTRY.

AN AREA FACTOR IS SPECIFIED FOR AN INAPPROPRIATE FACE TYPE = %1.

USER INFORMATION: AREA FACTOR IS PERMITTED FOR TYPE = POINT AND LINE ONLY.

AN INVALID, OR NO, AREA FACTOR IS SPECIFIED FOR FACE TYPE = %1.

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.

THERE ARE %1 COMPLEX EIGENVALUE SUBCASES.

USER INFORMATION: ONLY ONE COMPLEX EIGENVALUE SUBCASE, DCEIG OR MCEIG, IS PERMITTED IN SOL 200.

THE FOLLOWING GRID OR SCALAR POINTS ARE SPECIFIED MORE THAN ONCE ON THE BULK DATA ENTRY SHOWN BELOW:

THE FOLLOWING GRID/SCALAR POINT — COMPONENT IS SPECIFIED MORE THAN ONCE ON THE BULK DATA ENTRY SHOWN BELOW:

AXIC FILE RECORD FOR ENTRY(%1) NOT OF LENGTH = TO ENTRY MULTIPLES + 3. RECORD HEADER =%2

%1 ID = %2 IS OUTSIDE THE PERMISSIBLE RANGE: 1 THROUGH 9999.

MINIMUM PROBLEM REQUIRES %1 ENTRY, NONE FOUND.

RING ID =%1 ON ENTRY TYPE (%2) IS OUTSIDE THE ALLOWABLE RANGE: 1 THROUGH %3.

INCONSISTENCY, AXIC TRAILER BIT IS ON, BUT RECORD COULD NOT BE FOUND BY LOCATE. RECORD HEADER =%1

HARMONIC NUMBER =%1 ON ENTRY TYPE (%2) IS OUTSIDE THE ALLOWABLE RANGE: 0 THROUGH %3.

INCONSISTENT ERROR READING BALANCE OF %1%2 ENTRIES.

RECORD INCONSISTENCY FOR %1%2 ENTRIES

SPCAX OR MPCAX ENTRY HAS A SETID = 101 OR 102.

USER INFORMATION: 101 AND 102 ARE SPECIAL SETS RESERVED FOR SINE AND COSINE SETS.

RINGAX ENTRY WITH RING ID = %1 HAS A ZERO RADIUS SPECIFIED.

ENTRY TYPE %1 HAS BAD COMPONENT SPECIFICATION OF %2

AXIC TRAILER BIT ON BUT LOCATE CAN NOT FIND POINTAX OR SECTAX ENTRY.

AN INVALID BULK DATA ENTRY HAS BEEN SPECIFIED FOR AXI-SYMMETRIC CONICAL SHELL ANALYSIS

THE ELEMENT ITERATIVE SOLVER CAN ONLY BE USED IN LINEAR STATICS. SWITCHING TO SPARSE MATRIX METHOD.

NO ORIENTATION IS SPECIFIED FOR CHBDYP ELEMENT %1

THE LOWER RANGE FREQUENCY ,F1, IS LESS THAN 0.0 HZ.

THE UPPER RANGE FREQUENCY ,F2, IS LESS THAN THE LOWER RANGE FREQUENCY.

THE FREQUENCY SPREAD ,FSPD, ON FREQ4 ENTRY %1 IS LESS THAN OR EQUAL TO 0.0 OR GREATER THAN 1.0.

THE NUMBER OF FREQUENCIES ,NFM, ON FREQ4 ENTRY %1 IS LESS THAN 1.

ONE OR MORE FRACTIONS ,FRI, ON FREQ5 ENTRY %1 ARE LESS THAN 0.0

FIELD %1 ON EIGRL ENTRY, SID = %2 IS SPECIFIED MORE THAN ONCE.

FIELD %1 ON EIGC ENTRY, SID = %2 IS SPECIFIED MORE THAN ONCE.

%1

THE COMMA-DELIMITED FREE-FIELD FORMAT IS NOT ALLOWED 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.

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.

ON MAT8 ID = %1, ONLY ONE 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.

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.

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.

A REQUESTED %1 FILE WAS NOT FOUND.

FILE ‘%2’

IS INCLUDED IN FILE ‘%3’

AT RECORD NUMBER %4.

THE INCLUDE REQUEST IS SKIPPED.

NO FILE NAME SPECIFIED ON %1 STATEMENT.

STATEMENT IS INCLUDED IN FILE ‘%3’

AT RECORD NUMBER %4.

THE INCLUDE REQUEST IS SKIPPED.

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.

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.

THE COMPILER HAS BECOME LOST, DURING PROCESSING OF THE ABOVE TYPE CARD

USER ACTION: NOTIFY SIEMENS PLM SOFTWARE CUSTOMER SUPPORT AS SOON AS POSSIBLE.

THE COMPILER HAS BECOME LOST, DURING PROCESSING OF THE ABOVE SUBDMAP CARD

USER ACTION: NOTIFY SIEMENS PLM SOFTWARE CUSTOMER SUPPORT.

THE COMPILER HAS BECOME LOST, DURING PROCESSING OF THE ABOVE %1 CAR

** USER ACTION: 1. NOTIFY SIEMENS PLM SOFTWARE CUSTOMER SUPPORT AS SOON AS POSSIBLE.

2. CHANGE %2 STATEMENT TO %3 STATEMENTS

THE NUMBER OF DATA BLOCKS ON THE %1 CARD EXCEEDS THE MAXIMUM (%2 ) ALLOWED

NUMBER OF NDDL PARAMETERS EXCEEDS THE MAXIMUM ALLOWED OF %1

NUMBER OF PARAMETER ARGUMENTS EXCEEDS THE MAXIMUM ALLOWED OF %1

%1 WAS DETECTED WHEN %2 WAS EXPECTED

USER ACTION: ADD CORRECT %3 AND RECOMPILE

%1 WAS DETECTED WHEN THE SUBDMAP NAME WAS EXPECTED

USER ACTION: ADD SUBDMAP NAME AND RECOMPILE

%1 WAS DETECTED WHEN %2 WAS EXPECTED

USER ACTION: ADD CORRECT %3 AND RECOMPILE

USER INFORMATION: VALID SCOPE IDENTIFIERS ARE «NDDL» AND » »

%1 WAS DETECTED WHEN %2 WAS EXPECTED

USER ACTION: ADD CORRECT %3 AND RECOMPILE

USER INFORMATION: VALID PARAMETER TYPE CODES ARE «I», «RS», «CHAR», «RD», «CS», «CD», «LOGI», «RX», OR «CX»

%1 WAS DETECTED WHEN %2 WAS EXPECTED

USER ACTION: ADD CORRECT %3 AND RECOMPILE

USER INFORMATION: VALID AUTHORIZATION CODES ARE «Y», «N», OR » »

%1 WAS DETECTED WHEN %2 WAS EXPECTED

USER ACTION: ADD CORRECT %3 AND RECOMPILE

USER INFORMATION: VALID IDENTIFIER KEYWORDS ARE «PARM» AND «DB»

A NUMERIC VALUE WAS DETECTED WHEN A DELIMITER, DATA BLOCK NAME, PARAMETER NAME, OR END-OF-CARD WAS EXPECTED

USER ACTION: REMOVE NUMERIC VALUE FROM SUBDMAP STATEMENT AND RECOMPILE

A NON-%1 DELIMITER WAS DETECTED WHERE A %2 DELIMITER IS REQUIRED

A NON-SLASH DELIMITER WAS DETECTED WHERE A SLASH DELIMITER IS REQUIRED

USER ACTION: REPLACE NON-SLASH DELIMITER WITH A SLASH, 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.

THE NUMBER OF WORDS ALLOCATED FOR PROCESSING THIS SUBDMAP’S %1 HAS BEEN EXCEEDED. THE MAXIMUM IS %2 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

INVALID DATA TYPE CODE %1.

VALID DATA TYPE CODES ARE «I», «RS», «CHAR», «RD», «CS», «CD», «LOGI», «RX», OR «CX»

INVALID PARAMETER TYPE CODE %1.

VALID PARAMETER TYPE CODES ARE «I», «RS», «CHAR», «RD», «CS», «CD», «LOGI», «RX», OR «CX»

INVALID IDENTIFIER KEYWORD %1.

VALID IDENTIFIER KEYWORDS ARE «PARM» AND «DB»

INVALID USER AUTHORIZATION CODE %1.

VALID AUTHORIZATION CODES ARE «Y», «N», OR » »

INVALID VARIABLE SCOPE IDENTIFIER %1.

VALID SCOPE IDENTIFIERS ARE «NDDL» AND » »

INVALID PARAMETER CLOSE OPTION CODE %1.

VALID PARAMETER OPERATION CODES ARE 1 (REWIND), 2 (CLOSE/KEEP), AND 3 (CLOSE/DELETE)

INVALID PARAMETER OPERATION CODE %1.

VALID PARAMETER OPERATION CODES ARE «OPEN» OR «CLOSE»

INVALID INTERNAL NDDL DATA CODE %1 PROCESSING RECORD %2 OF DATABLOCK %3

VALID INTERNAL NDDL DATA CODES ARE 1 THROUGH 10

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 «SAMEAS» APPEAR AFTER THE REFERENCED «SAMEAS» RECORD

USER AUTHORIZATION FIELD IS MISSING ON ABOVE TYPE STATEMENT

User information:

All «TYPE PARM» statements require a «Y» or «N» authorization code.

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.

THE PARAMETER %1 IS IGNORED BECAUSE IT HAS BEEN PREVIOUSLY DEFINED IN A TYPE DMAP STATEMENT

DEFAULT VALUE IGNORED FOR NDDL TYPED PARAMETER — DEFAULTS MUST BE SET IN NDDL DECK

THE VALUE ASSIGNED TO ONE OF THE PARAMETERS ON THIS TYPE STATEMENT IS INCONSISTENT WITH REQUESTED %1 TYPE CODE

THE ‘%1’ VALUE ASSIGNED TO THE PARAMETER %2 ON THIS TYPE STATEMENT IS INCONSISTENT WITH REQUESTED ‘%3’ TYPE CODE

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 ARRAY DIMENSION FOR PARAMS

FOUND BCD VALUE WHEN EXPECTING DELIMITER, DURING PROCESSING OF %1 CARD

FOUND NUMERIC VALUE WHEN EXPECTING DELIMITER, DURING PROCESSING OF %1 CARD

FOUND END-OF-CARD WHEN EXPECTING DELIMITER, DURING PROCESSING OF %1 CARD

FOUND BCD VALUE WHEN EXPECTING DELIMITER OR END-OF-CARD, DURING PROCESSING OF ABOVE %1 CARD

FOUND NUMERIC VALUE WHEN EXPECTING DELIMITER OR END-OF-CARD, DURING PROCESSING OF ABOVE %1 CARD

FOUND NUMERIC VALUE WHEN EXPECTING DATA BLOCK NAME, DURING PROCESSING OF %1 CARD

FOUND END-OF-CARD WHEN EXPECTING DATA BLOCK NAME, DURING PROCESSING OF %1 CARD

FOUND NUMERIC VALUE WHEN EXPECTING DATA BLOCK NAME OR DELIMITER, DURING PROCESSING OF %1 CARD

FOUND END-OF-CARD WHEN EXPECTING DATA BLOCK NAME OR DELIMITER, DURING PROCESSING OF ABOVE %1 CARD

FOUND NUMERIC VALUE WHEN EXPECTING PARAMETER NAME, DURING PROCESSING OF %1 CARD

FOUND END-OF-CARD WHEN EXPECTING PARAMETER NAME, DURING PROCESSING OF %1 CARD

FOUND NUMERIC VALUE WHEN EXPECTING PARAMETER NAME, DELIMITER, OR END-OF-CARD, WHILE PROCESSING %1 CARD

DMAP INSTRUCTION %1 NOT FOUND IN DMAP LIBRARY

** USER ACTION: NOTIFY SIEMENS PLM SOFTWARE CUSTOMER SUPPORT.

%1 DMAP INSTRUCTION REQUIRES AT LEAST TWO DATA BLOCKS

NO DATA BLOCK NAME(S) SPECIFIED ON THIS %1 CARD

DATA BLOCK NAME(S) AND PARAMETER NAME NOT DELIMITED BY ‘/’ ON %1 CARD

NO PARAMETER NAME SPECIFIED ON THIS %1 CARD

EXTRANEOUS DATA FOUND AFTER PARAMETER NAME, BUT BEFORE DELIMITER OR END-OF-CARD.

DATA IS IGNORED FOR THIS %1 STATEMENT

USE OF ‘S,Y’, ‘S,N’, ‘V,N’, OR ‘V,Y’ IS INVALID FOR PARAMETERS USED ON %1 STATEMENTS

** USER ACTION: REMOVE INVALID SYNTAX AND RERUN

USE OF ‘S’ OR ‘V’ IS INVALID FOR PARAMETERS USED ON %1 STATEMENTS

** USER ACTION: REMOVE INVALID SYNTAX AND RERUN

FOR COMPILATION PURPOSES %1 WILL BE USED AS THE PARAMETER NAME FOR THIS %2 STATEMENT

THE FOLLOWING PHYSICAL FILE DOES NOT EXIST

%1

THIS FILE IS A PART OF THE 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,

then all of these files must be available for all runs using the

database set. Also, see Error Reports 3652 in section 17.2 of NX NASTRAN Referenece Manual.

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.

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.

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 CONTINUATIONS IS 6 CARD IMAGES, OR 432 CHARACTERS.

THE FOLLOWING KEYWORD(S) ARE ILLEGAL FOR THE %1 COMMAND

%2

THE FOLLOWING KEYWORD(S) ARE ILLEGAL FOR THE SOL EXECUTIVE CONTROL COMMAND

%1

THE FOLLOWING KEYWORD(S) ARE ILLEGAL FOR THE COMPILE EXECUTIVE CONTROL COMMAND

%1

THE FOLLOWING KEYWORD(S) ARE ILLEGAL FOR THE DBUPDATE EXECUTIVE CONTROL COMMAND

%1

THE FOLLOWING KEYWORD(S) ARE ILLEGAL FOR THE SECURITY COMMAND

%1

THE FOLLOWING KEYWORD(S) ARE ILLEGAL FOR THE RESTART COMMAND

%1

THE FOLLOWING KEYWORD(S) ARE ILLEGAL FOR THE PROJECT COMMAND

%1

THE FOLLOWING KEYWORD(S) ARE ILLEGAL FOR THE INIT EXECUTIVE CONTROL COMMAND

%1

THE FOLLOWING KEYWORD(S) ARE ILLEGAL FOR THE DBFIX COMMAND

%1

THE FOLLOWING KEYWORD(S) ARE ILLEGAL FOR EXPAND EXECUTIVE CONTROL COMMAND

%1

THE FOLLOWING KEYWORD(S) ARE ILLEGAL FOR DBDIR EXECUTIVE CONTROL COMMAND

%1

THE FOLLOWING KEYWORD(S) ARE ILLEGAL FOR THE DBCLEAN EXECUTIVE CONTROL COMMAND.

%1

THE FOLLOWING KEYWORD(S) ARE ILLEGAL OR REPEATED ON THE %1 BULK ENTRY

%2

THE FOLLOWING KEYWORD(S) ARE ILLEGAL FOR THE %1 COMMAND.

%2

THE LOPBLK TABLE HAS EXCEEDED ITS MAXIMUM %1 NUMBER OF ENTRIES

USER INFORMATION: THIS TABLE CONTAINS THE SCRATCH 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 LOPMAX.

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.

DMAP LINE NUMBER K1 IS OUT OF RANGE. LAST DMAP LINE NUMBER IS:%1

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

characters than are allowed based on either the «TYPE PARM» statement

or in the NDDL. Any characters beyond the defined length will be

truncated.

C,N AND C,Y CONSTANT FORMATS ARE NO LONGER SUPPORTED.

%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

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.

INSUFFICIENT OPEN CORE AVAILABLE TO STORE DBENTRY OF THE LOCATED DATA BASE

INSUFFICIENT OPEN CORE AVAILABLE TO STORE THE REMAINING TRAILER RECORDS.

USER INFORMATION: THE REMAINING RECORDS HAVE BEEN TRUNCATED.

INSUFFICIENT OPEN CORE AVAILABLE TO COPY NDDL TABLES TO THE PRIMARY DATA BASE

UNABLE TO LOCATE PARAMETER NUMBER %1 IN VPS FOR INSTRUCTION %2

UNEXPECTED END-OF-FILE ON OSCAR TRAILERS DURING PROCESSING OF THE CROSS REFERENCE

UNEXPECTED END-OF-FILE FOUND DURING PROCESSING OF CROSS REFERENCE.

OPEN CORE OVERFLOW IN CROSS REFERENCE. CROSS REFERENCE TERMINATED.

LOGIC ERROR. TYPE VARIABLE %1 IS NOT VALID

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.

ERROR IN PARSING DBVIEW DMAP STATEMENT.

ERROR IN PROCESSING DBVIEW DMAP STATEMENT. OVERFLOW IN DBVIEW OSCAR TRAILER RECORD.

USER ACTION: PLEASE NOTIFY SIEMENS PLM SOFTWARE CUSTOMER SUPPORT.

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.

LINKAGE OF THE SOLUTION SEQUENCE HAS FAILED BECAUSE THE OBJECT FILE FOR SUBDMAP %1 WAS NOT FOUND ON THE %2 DBSET.

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.

ERROR ATTEMPTING TO %1 A FILE (LOGICAL= %2) FOR DBSET SCRATCH WITH READ AND WRITE PRIVILEGES.

USER ACTION: CHECK 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 corresponding 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

database by two jobs is acceptable.

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.

ERROR ATTEMPTING TO CREATE A FILE (LOGICAL= %1) FOR DBSET %2 WITH READ AND WRITE PRIVILEGES.

USER ACTION: CHECK THE AVAILABLE/ALLOCATED SPACE AND THE PRIVILEGES GRANTED THIS ACCOUNT.

ERROR ATTEMPTING TO OPEN A FILE (LOGICAL= %1) FOR DBSET %2 WITH READ PRIVILEGE.

USER ACTION: CHECK THE READ PRIVILEGE GRANTED THIS FILE.

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.

ERROR ATTEMPTING TO CREATE A PHYSICAL FILE WITH READ_ONLY OPTION.

USER INFORMATION: LOGICAL FILE = %1 OF DBSET %2

THE FILE ASSIGNMENT TABLE (DBSPACE) CONTAINS NO INFORMATION FOR THE %1 DBSET.

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.

DBMAP FILE NOT IN FIST. UNABLE TO OPEN FOR DBSET = %1

DBDIR FILE NOT IN FIST. UNABLE TO OPEN FOR DBSET = %1

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 LSTDBN = %4 DBSET = %5

THE DATABASE WITH DBSNO=%1 DOES NOT CONTAIN A COMPILED NDDL.

THE DBSNO NUMBERS ARE PRINTED NEAR THE TOP OF THE EXECUTION SUMMARY TABLE.

THE DATABASE NUMBER (IDBSNO)=%1 BEING USED IN THIS RUN DOES NOT HAVE ENOUGH INFORMATION TO START FROM.

THE DATABASE WITH DBSNO=%1 DOES NOT CONTAIN A COMPILED NDDL.

THE DBSNO NUMBERS ARE PRINTED NEAR THE TOP OF THE EXECUTION SUMMARY TABLE.

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

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

A DBSET ON THE %1 DATABASE HAS A BUFFSIZE 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

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

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 THIS RUN.

USER ACTION: ADD THE FOLLOWING KEYWORD TO THE NASTRAN CARD: BUFFSIZE=%2

SHORT RECORD ENCOUNTERED IN TRANSACTION FILE (%1).

USER INFORMATION: THIS INDICATES THAT THE DATABASE HAS BEEN DESTROYED AND IS IRRECOVERABLE.

USER ACTION: DELETE AND RE-GENERATE THE DATABASE.

THE TRANSACTION TABLE HAS EXCEEDED AVAILABLE OPEN CORE.

USER ACTION: RE-SUBMIT THIS JOB WITH A LARGER HICORE AND WITH ALL DBSETS ATTACHED TO CLEAN UP THE TRANSACTION FILE

USER INFORMATION: SEE THE EXECUTION SUMMARY FILE FOR THE LIST OF UNATTACHED DBSETS.

THE PHYSICAL FILE ASSIGNED TO THE %1 DBSET ALREADY EXISTS.

USER ACTIONS: DELETE THE FOLLOWING FILE AND RESUBMIT THE JOB.

%2

THE FOLLOWING PHYSICAL FILE NAME EXCEEDS THE MAXIMUM NUMBER OF CHARACTERS ALLOWED.

%1

USER INFORMATION: THE CURRENT LIMIT IS %2 CHARACTERS.

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.

THE NUMBER 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 files 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.

THE LINK TABLE FOR SUBDMAP %1 DOES NOT EXIST.

USER ACTIONS:

1. ENSURE THAT THE SUBDMAP IS THE APPROPRIATE MAIN SUBDMAP

2. ENSURE THAT THE SUBDMAP WAS LINKED PROPERLY.

USER INFORMATION: THE LINK TABLE IS DESCRIBED UNDER THE LINK STATEMENT.

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.

ATTEMPT TO WRITE FILE ASSIGNMENT (DBSPACE) TABLE TO MASTER DBSET FAILED.

THE CORE-RESIDENT FILE ASSIGNMENT (DBSPACE) TABLE IS EMPTY

USER ACTION: SEND RUN TO SIEMENS PLM SOFTWARE CUSTOMER SUPPORT

PROGRAMMER INFORMATION: VALUES OF INTEREST

DBSTOP = %1 DBSBOT = %2 LSTDBS = %3

IF THE ABOVE VALUES SEEM UNREASONABLE THEN /XSPACE/ COMMON BLOCK HAS BEEN OVERWRITTEN

THE MAXIMUM NUMBER OF CALLS WITHIN %1 MAIN SUBDMAP HAS BEEN EXCEEDED.

USER INFORMATION: THE MAXIMUM NUMBER OF CALLS IN THIS VERSION IS %2

User information:

Combine subDMAPs in order to alleviate this problem.

THE MAXIMUM NUMBER OF CALLS WITHIN %1 MAIN SUBDMAP HAS BEEN EXCEEDED.

USER INFORMATION: THE MAXIMUM NUMBER OF CALLS IN THIS VERSION IS 50

THE DBSET %1 IS NOT PART OF ANY DATA BASE ATTACHED TO THIS RUN, INDICATING IT WAS NOT ALLOCATED FOR THIS RUN.

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 MASTER dbset

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.

If you are sure they are, there is a System Cell (135 or TSTAMP) that

turns off this checking.

THE LOGICAL NAME %1 WAS ASSIGNED TO THE FOLLOWING PHYSICAL FILE, WHICH DOES NOT EXIST.

%2

%3

USER ACTION: CHECK FILE ASSIGNMENTS.

ERROR ATTEMPTING TO CLOSE THE FOLLOWING PHYSICAL FILE NAME:

%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.

ERROR ATTEMPTING TO OPEN DATA BLOCK FILE NUMBER %1

USER ACTION: CONTACT CUSTOMER SUPPORT

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 COMMANDS CANNOT EXIST PRIOR TO THEIR ASSIGNMENTS.

THE %1 FOR SUBDMAP %2 HAS BEEN REPLACED BY THE CURRENT ONE ON %3 DBSET

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.

THE LOGICAL NAME %1 ASSIGNED TO A PHYSICAL FILE NAME OF THE %2 DATA BASE, DOES NOT EXIST.

USER INFORMATION: PHYSICAL FILE NAME = %3

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

THE FOLLOWING LOGICAL NAME, PART OF THE %1 DATA BASE, HAS A NULL TIME STAMP.

USER INFORMATION: LOGICAL NAME = %2

THE REQUESTED LOGICAL NAME %1 WAS NOT ASSIGNED.

USER ACTION: CHECK FILE ASSIGNMENTS.

User information:

This error may be issued if the LOGICAL keyword on DBLOCATE

references a reserved logical name such as DBC, PUNCH, etc.

JOB TERMINATED DUE TO ABOVE ERROR(S)

JOB TERMINATED DUE TO ENDJOB OPTION.

JOB TERMINATED DUE TO NOEXE OPTION ON SOL CARD OR NOGO OPTION ON COMPILER CARD.

JOB TERMINATED DUE TO LACK OF SOL CARD IN EXECUTIVE CONTROL SECTION.

JOB TERMINATED DUE TO ABOVE ERRORS IN THE DMAP/NDDL LINKAGE EDITOR (LINKER)

JOB TERMINATED DUE TO ABOVE ERRORS IN THE DMAP COMPILER (XGPI)

JOB TERMINATED DUE TO ABOVE ERRORS IN THE NDDL COMPILER.

JOB TERMINATED DUE TO ABOVE ERRORS IN THE NDDL AND DMAP COMPILERS.

JOB TERMINATED DUE TO LACK OF SOL, COMPILE, OR LINK CARDS IN THE EXECUTIVE CONTROL SECTION.

JOB TERMINATED DUE TO ABOVE ERROR(S) IN THE FILE MANAGEMENT SECTION.

JOB TERMINATED DUE TO ABOVE ERRORS IN THE LCLDBS/DBLOCATE

JOB TERMINATED DUE TO ENDJOB OPTION

JOB TERMINATED DUE TO ABOVE ERROR(S) IN THE %1 STATEMENT PROCESSOR.

NO %1 DATA HAS BEEN UNLOADED FROM THE DATABASE TO UNIT %2.

%1 PARAMETER(S) HAVE BEEN UNLOADED FROM THE DATABASE TO UNIT %2 IN %3 FORMAT.

%1 DATABLOCK(S) HAVE BEEN UNLOADED FROM THE DATABASE TO UNIT %2 IN %3 FORMAT.

NO %1 DATA HAS BEEN LOADED TO THE DATABASE FROM UNIT %2.

%1 PARAMETER(S) HAVE BEEN LOADED TO THE DATABASE FROM UNIT %2 IN %3 FORMAT.

%1 DATABLOCK(S) HAVE BEEN LOADED TO THE DATABASE FROM UNIT %2 IN %3 FORMAT.

NO DATA HAS BEEN LOCATED ON THE %1 DATABASE.

%1 PARAMETER(S) HAVE BEEN LOCATED ON THE %2 DATABASE.

System information:

This is an information message which results when using DBLOCATE.

%1 DATABLOCK(S) HAVE BEEN LOCATED ON THE %2 DATABASE.

System information:

This is an information message which results when using DBLOCATE.

NO DATA HAS BEEN LOCATED ON THE PRIMARY DATABASE.

%1 PARAMETER(S) HAVE BEEN LOCATED ON THE PRIMARY DATABASE.

%1 DATABLOCK(S) HAVE BEEN LOCATED ON THE PRIMARY DATABASE.

NO DATA HAS BEEN DELETED ON THE PRIMARY DATABASE.

%1 PARAMETER(S) HAVE BEEN DELETED ON THE PRIMARY DATABASE.

%1 DATABLOCK(S) HAVE BEEN DELETED ON THE PRIMARY DATABASE.

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.

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.

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.

THE QUALIFIER NAME %1 CANNOT BE FOUND IN THE PATH TABLE

THE KEY USED IN CREATING THE DBVIEW DATA BLOCK WAS NOT FOUND.

USER ACTION: SEND RUN TO SIEMENS PLM SOFTWARE CUSTOMER SUPPORT.

THE PATH USED IN CREATING THE LOCATE DATA BLOCK WAS NOT FOUND.

THE QUALIFIER USED IN SEARCHING FOR DATA BLOCKS WAS NOT FOUND.

USER ACTION: SEND RUN TO SIEMENS PLM SOFTWARE CUSTOMER SUPPORT.

THE PATH USED IN CREATING THE LOCATE DATA BLOCK WAS NOT FOUND.

USER ACTION: SEND RUN TO SIEMENS PLM SOFTWARE CUSTOMER SUPPORT.

THE LENGTH OF THE STRING WHICH HOLDS THE QUALIFIERS 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

2) NWLEN = %4

3) STRING =

THE TEMPORARY VPS TABLE USED IN PROCESSING USER-SUPPLIED EQUATIONS HAS OVERFLOWED.

USER ACTIONS: SIMPLIFY EQUATION AND NOTIFY SIEMENS PLM SOFTWARE CUSTOMER SUPPORT.

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.

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

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.

YOU HAVE SELECTED A BUFFER SIZE OF %1 FOR 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.

YOU HAVE SELECTED A BUFFER SIZE OF %1 FOR THE 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.

SUBDMAP %1 WILL BE LINKED.

I/O ERROR ENCOUNTERED READING %2 FILE. IOSTAT = %1.

USER ACTION: CHECK STATUS OF FILE OR FILESYSTEM.

FILE IS ‘%3’

ERROR MESSAGE IS ‘%4’

INTERNAL LOGIC ERROR ENCOUNTERED. INCLUDE PROCESSING FOUND INVALID HANDLE.

HANDLE VALUE IS %1.

THE VIEW NAME AND DATABLOCK NAME ARE IDENTICAL ON THE DBVIEW %1 = %1 STATEMENT.

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

Section 3.1 for valid characters.

CONTROL CARD %1 DUPLICATED

User information:

The statement preceding Message 506 cannot be input more than once.

ILLEGAL SPECIFICATION OR FORMAT ON PRECEDING CARD

User information:

Executive control statements cannot have equal (=) signs.

PROBLEM TAPE MUST BE ON PHYSICAL TAPE FOR CHECK POINTING

CHECKPOINT DICTIONARY EXCEEDS CORE SIZE — REMAINING RESTART CARDS IGNORED

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.

NDDL SEQUENCE EXCEEDS CORE SIZE — REMAINING NDDL INSTRUCTIONS IGNORED

OLD PROBLEM TAPE IS MISSING AND IS NEEDED FOR RESTART

END INSTRUCTION MISSING IN DMAP SEQUENCE

User information:

DMAP sequence must end with END control card. (END must begin in column 1.)

ID CARD MUST PRECEDE ALL OTHER CONTROL CARDS

User information:

ID statement must come before all other statements except the

NASTRAN and FMS statements. Although the ID statement is documented

as being an optional comment statement, if it is used, it must be

before all other Executive Control statements.

CONTROL CARD %1 IS MISSING

SPECIFY A SOLUTION OR A DMAP SEQUENCE, BUT NOT BOTH

NEITHER A VALID SOL CARD NOR A DMAP SEQUENCE WAS INCLUDED

CHECKPOINT DICTIONARY OUT OF SEQUENCE — REMAINING RESTART CARDS IGNORED

THE VALUE ASSIGNED TO THE DOMAIN SOLVER OPTION %1 IS INVALID OR MISSPELLED.

THE %1 DOMAIN SOLVER METHOD IS INVALID OR MISSPELLED.

THE DOMAIN SOLVER OPTION %1 IS INVALID OR MISSPELLED.

THE DOMAIN SOLVER OPTION %1 IS NOT SUPPORTED FOR THE %2 METHOD.

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.

THE SELECTED COMBINATION OF DOMAIN SOLVER METHODS %1 IS NOT SUPPORTED

IN THE %2 SOLUTION SEQUENCE.

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.

THE %1 DOMAIN SOLVER METHOD IS NOT SUPPORTED IN A %2 RUN.

THE NUMBER OF DOMAINS SPECIFIED FOR THE FDMODES DOMAIN SOLVER METHOD—NUMDOM=%2—EXCEEDS THE MAXIMUM LIMIT OF %1.

USER INFORMATION: NUMDOM WILL BE RESET TO %1.

THE NUMBER OF DOMAINS HAS NOT BEEN SPECIFIED.

USER INFORMATION: FOR SERIAL EXECUTION OF THE %1 DOMAIN SOLVER METHOD, NUMDOM MUST BE SPECIFIED.

NO TEXT AVAILABLE FOR MESSAGE %1

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

command descriptions, Section 4 of the NX NASTRAN Quick Reference

Guide, and spell your request correctly.

This occurs for SURFACE and VOLUME commands that are not in the

OUTPUT(POST) section.

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.

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.

THE ABOVE CARD HAS A NON-INTEGER IN AN INTEGER FIELD.

User information:

Consult the Case Control command descriptions, Section 4 of the

NX NASTRAN Quick Reference Guide, for legal values.

A SYMSEQ OR SUBSEQ CARD APPEARS WITHOUT A SYMCOM OR 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.

INVALID USE OF TEMPERATURE DEPENDENT MATERIALS OCCURS AT THE SUBCASE LEVEL. ONLY ONE SUCH CARD IS

ALLOWED PER PROBLEM OR PER SUPERELEMENT.

A REPCASE CARD MUST BE PRECEDED BY A SUBCASE CARD

User information:

A REPCASE subcase is an attempt to reoutput the previously computed

case; therefore, it cannot be the first subcase.

THE SET ID SPECIFIED ON THE ABOVE CARD MUST BE DEFINED PRIOR TO THIS CARD.

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

of the subcase it is in.

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.

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

the Case Control command descriptions, Section 4 of the NX NASTRAN

Quick Reference Guide. For example, only real data can follow SUBSEQ

and SUBCOM commands—not integers.

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 OUTPUT(PLOT)

or OUTPUT(XYOUT) delimiter commands.

DUPLICATE KEYWORDS ENCOUNTERED ON ABOVE CARD.

THE ABOVE SET CONTAINS -EXCEPT- WHICH IS NOT PRECEDED BY -THRU-.

User information:

Only identification numbers included by the THRU keyword may be expected.

Simplify the SET request.

THE ABOVE SET IS BADLY SPECIFIED.

User information:

Simplify the SET list.

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 format. Give the SET a correct

integer name.

-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.

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.

INVALID DESCRIBER ON RIGID CASE CONTROL CARD.

USER INFORMATION: THE VALID DESCRIBERS ARE LINEAR AND LAGRANGE

THE RIGID CASE CONTROL CARD MUST COME BEFORE THE FIRST SUBCASE CARD

THE UNIT KEYWORD IS MISSING FROM THE MBDEXPORT OP4 COMMAND

WHEN THE RMAXMIN CARD IS USED FOR SOLUTION SEQUENCE 101, ALL SUBCASES

MUST MAKE IDENTICAL OUTPUT REQUESTS. THIS RUN CONTAINS DIFFERENT

OUTPUT REQUESTS FOR STRESS.

THE RMAXMIN REQUEST HAS BEEN DISABLED FOR THIS RUN.

WHEN THE RMAXMIN CARD IS USED FOR SOLUTION SEQUENCE 101, ALL SUBCASES

MUST MAKE IDENTICAL OUTPUT REQUESTS. THIS RUN CONTAINS DIFFERENT

OUTPUT REQUESTS FOR DISPLACEMENT.

THE RMAXMIN REQUEST HAS BEEN DISABLED FOR THIS RUN.

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.

IC(TZERO) IS ONLY VALID FOR SOLUTION SEQUENCE 112

(SEMTRAN); IT WILL BE IGNORED FOR THIS SOLUTION.

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.

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.

TOO LARGE ID ON PRECEDING SUBCASE TYPE CARD. ALL ID-S 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.

SUBCOM SUBCASE DOES NOT HAVE A SUBSEQ CARD.

User information:

A SUBCOM SUBCASE must contain a SUBSEQ command to define the

linear combination coefficients.

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

one for buckling. Both a load and a method selection cannot appear

in the same subcase.

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 must be unique.

ECHO CARD HAS REPEATED OR UNRECOGNIZABLE SPECIFICATION DATA. REPEATED SPECIFICATIONS WILL BE IGNORED.

UNRECOGNIZABLE SPECIFICATIONS WILL BE TREATED AS SORT.

User information:

See Section 4 of the NX NASTRAN Quick Reference Guide.

ECHO CARD WITH -NONE- SPECIFICATION HAS ADDITIONAL SPECIFICATIONS WHICH WILL BE IGNORED.

User information:

See Section 4 of the NX NASTRAN Quick Reference Guide.

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).

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.

INCONSISTENT 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.

SERST CASE CONTROL ENTRY SUPPORTS KEYWORDS SEMI OR SEDR ONLY

WRONG FORMAT OF DATA FOR THE EVEN FIELD ON CONTOUR CARD

THE TRIM AND DIVERG COMMANDS MAY NOT BE SPECIFIED IN THE SAME SUBCASE.

THE TYPE USED ON AN ANALYSIS CASE CONTROL ENTRY IS INVALID.

A SPACE IS REQUIRED BETWEEN THE SET COMMAND AND THE SET ID.

YOU MAY NOT SPECIFY BOTH MAX AND MIN FOR OBJECTIVE

THE DEFAULT VALUE OF MIN WILL BE USED.

YOU MAY NOT SPECIFY THIS CASE CONTROL ENTRY AT THE

SUBCASE LEVEL.

CSSCHD=ALL IS NOT ALLOWED.

USER INFORMATION: SPECIFY CSSCHD=NONE OR CSSCHD=n WHERE n IS A CONTROL SURFACE SCHEDULE ID.

THE ABOVE CASE CONTROL COMMAND OR KEYWORD, %1, IS AMBIGUOUS.

USER ACTION: SPECIFY EITHER %2 OR %3

AERO SYMMETRY CASE CONTROL COMMAND: %1 SPECIFIES AN ILLEGAL VALUE: %2

USER INFORMATION: LEGAL VALUES ARE: ANTISYMMETRIC, ASYMMETRIC, AND SYMMETRIC.

THE NUMBER OF %1 COEFFICIENTS, %2 , HAS EXCEEDED THE MAXIMUM ALLOWABLE %3 .

NONLINEAR CASE CONTROL CARD NOT VALID IN SOLUTION SEQUENCE %1 .

IT WILL BE IGNORED.

MODALE NOT VALID IN SOLUTION SEQUENCE %1 .

TSTEP IN SUBCASE IS IGNORED.

THE USE OF TEMP(MAT) OR TEMP(BOTH) IS NOT ALLOWED WHEN SYS(440)=0.

WHEN SYS440 = 0, TEMP(INIT) MUST BE SPECIFIED ABOVE THE SUBCASE LEVEL

FOR ALL LINEAR SOLUTIONS.

IF TEMPERATURE DEPENDENT MATERIAL PROPERTIES ARE 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 TEMP(LOAD) OR TEMP(INIT)

IS SPECIFIED, THE MATERIAL PROPERTIES ASSOCIATED WITH THE PCOMP/PCOMPG WILL

BE RE-EVALUATED WHEN NEEDED.

NSM MUST BE SPECIFIED ABOVE THE SUBCASE LEVEL.

THE OUTPUT(POST) AND SETS DEFINITION COMMANDS CANNOT BE SPECIFIED AT THE SAME TIME.

ILLEGAL OR UNRECOGNIZABLE OPTION SPECIFIED ON THE ABOVE MAXMIN STATEMENT.

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

INVALID CASE CONTROL COMMAND STRUCTURE DETECTED ON ABOVE %1 ENTRY.

USER INFORMATION: A DESCRIBER NAME WAS EXPECTED, BUT NOT FOUND.

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.

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.

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.

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.

DETECTED A PREMATURE END OF THE CASE CONTROL COMMAND %1 PROCESSING DESCRIBER %2.

USER INFORMATION: THE DESCRIBER IS IGNORED.

DETECTED A PREMATURE END OF THE CASE CONTROL COMMAND %1 PROCESSING DESCRIBER %2.

USER INFORMATION: THE DESCRIBER IS IGNORED.

INVALID HOLLERITH VALUE %3 SPECIFIED FOR %1 CASE CONTROL DESCRIBER %2.

USER INFORMATION: VALID VALUES ARE: ALL (-1) AND NONE (0)

INVALID HOLLERITH VALUE %3 SPECIFIED FOR %1 CASE CONTROL DESCRIBER %2.

USER INFORMATION: VALID VALUES ARE: NONE (-1) AND ALL (0)

INVALID HOLLERITH VALUE %3 SPECIFIED FOR %1 CASE CONTROL DESCRIBER %2.

USER INFORMATION: VALID VALUES ARE: ALL (-1) AND NOPRINT (-2)

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)

INVALID HOLLERITH VALUE %3 SPECIFIED FOR %1 CASE CONTROL DESCRIBER %2.

USER INFORMATION: VALID VALUES ARE: YES AND NO

INVALID HOLLERITH VALUE %3 SPECIFIED FOR %1 CASE CONTROL DESCRIBER %2.

USER INFORMATION: VALID VALUES ARE: PEAK AND RMS

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

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), IMAGINARY (30), PHASE (40)

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)

INVALID CASE CONTROL DESCRIBER %2 SPECIFIED ON %1 COMMAND.

USER INFORMATION: VALID DESCRIBERS ARE:

ARF, ARS, FEPS, FLUIDMP, GRIDFMP, GRIDMP, OUTFMP, OUTSMP, O2E, PANELMP, PSORT, SEPS, STRUCTMP

INVALID CASE CONTROL DESCRIBER %2 SPECIFIED ON %1 COMMAND.

USER INFORMATION: VALID DESCRIBERS ARE:

FLUIDSE, HFREQ, HFREQFL, LFREQ, LFREQFL, LMODES, LMODESFL

INVALID CASE CONTROL DESCRIBER %2 SPECIFIED ON %1 COMMAND.

USER INFORMATION: VALID DESCRIBERS ARE:

ACOUT, ACSYM, ASCOUP, PREFDB, SKINOUT, AGGPCH, SFEF70

INVALID INTEGER VALUE %3 SPECIFIED FOR %1 CASE CONTROL DESCRIBER %2.

USER INFORMATION: VALID VALUES ARE:

-1 = ALL

0 = NONE

>0

INVALID INTEGER VALUE %3 SPECIFIED FOR %1 CASE CONTROL DESCRIBER %2.

USER INFORMATION: VALID VALUES ARE:

-1 = NONE

0 = ALL

>0

INVALID INTEGER VALUE %3 SPECIFIED FOR %1 CASE CONTROL DESCRIBER %2.

USER INFORMATION: VALID VALUES ARE:

-2 = NOPRINT

-1 = NONE

0 = ALL

>0

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), AND 2 (ASCENDING)

AND ONE OF THE FOLLOWING,

0 (DEFAULT), 10 (ABSOLUTE), 20 (REAL), 30 (IMAGINARY), 40 (PHASE)

INVALID INTEGER VALUE %3 SPECIFIED FOR %1 CASE CONTROL DESCRIBER %2.

USER INFORMATION: VALID VALUES ARE:

-1 = NO

0 = YES

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

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:

FLUIDSE, HFREQ, HFREQFL, LFREQ, LFREQFL, LMODES, LMODESFL

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:

ACSYM, ACOUT, ASCOUP, PREFDB

INVALID NUMERIC DATA TYPE SPECIFIED ON %1 CASE CONTROL DESCRIBER %2.

USER INFORMATION: REQUIRED DATA TYPE IS REAL.

INVALID NUMERIC DATA TYPE SPECIFIED ON %1 CASE CONTROL DESCRIBER %2.

USER INFORMATION: REQUIRED DATA TYPE IS INTEGER.

INVALID DATA TYPE SPECIFIED ON %1 CASE CONTROL DESCRIBER %2.

USER INFORMATION: REQUIRED DATA TYPE IS REAL.

INVALID DATA TYPE SPECIFIED ON %1 CASE CONTROL DESCRIBER %2.

USER INFORMATION: REQUIRED DATA TYPE IS HOLLERITH

THE UNIT NUMBER ON THE ABOVE CARD HAS NOT BEEN DEFINED ON AN

ASSIGN COMMAND OR IS AN INVALID VALUE.

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 case 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 OUTPUT2=’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.

TEMP(MATERIAL) AND TEMP(BOTH) ARE NOT ALLOWED FOR ADVANCED NONLINEAR.

USE TEMP(INIT) AND TEMP(LOAD) INSTEAD.

ADAMSMNF AND MBDEXPORT CASE CONTROL COMMANDS BOTH EXIST

OR MULTIPLE MBDEXPORT CASE CONTROL COMMANDS EXIST.

ONLY ONE IS ALLOWED.

ABOVE PARAM CARD IS NOT ALLOWED IN THE CASE CONTROL.

INVALID RESULTS MAY OCCUR. PLEASE MOVE IT TO THE BULK DATA.

ONLY 1 OUTPUT MEDIUM MAY BE SPECIFIED ON THE EXTSEOUT CASE

CONTROL ENTRY.

EXTID=SEID IS REQUIRED ON THE EXTSEOUT CASE CONTROL ENTRY

WHENEVER ASMBULK, EXTBULK, DMIGPCH, OR MATOP4 ARE SPECIFIED.

A VALID UNIT NUMBER IS REQUIRED ON THE EXTSEOUT CASE CONTROL ENTRY

WHEN DMIGOP2 OR MATOP4 ARE SPECIFIED (I.E. SPECIFY DMIGOP2=UNIT OR

MATOP4=UNIT).

THE EXTSEOUT CASE CONTROL ENTRY IS NOT SUPPORTED IN THIS SOLUTION

SEQUENCE.

IC CASE CONTROL IS NOT VALID FOR THIS SOLUTION SEQUENCE;

IT WILL BE IGNORED.

THE DIFFK KEYWORD IS NOT VALID FOR THIS SOLUTION SEQUENCE;

IT WILL BE IGNORED.

THE STATSUB KEYWORD IS NOT VALID FOR THIS SOLUTION SEQUENCE;

IT WILL BE IGNORED.

STATSUB AND STATSUB,DIFFK CANNOT BOTH APPEAR IN THE SAME EXECUTION.

STATSUB AND IC(STATSUB) CANNOT BOTH APPEAR IN THE SAME SUBCASE.

DIFFK KEYWORD WITHOUT STATSUB KEYWORD IS MEANINGLESS.

DIFFK KEYWORD WILL BE IGNORED.

PHYSICAL, MODAL, STATSUB AND TZERO KEYWORDS CANNOT BE SPECIFIED

ON THE SAME IC ENTRY. ONLY ONE IS ALLOWED.

EQUAL SIGN MISSING.

IC(MODAL) IS ONLY VALID FOR SOLUTION SEQUENCE 112

(SEMTRAN); IT WILL BE IGNORED FOR THIS SOLUTION.

THE VALUE OF EXTID MUST BE >0 AND <= 999999 WHEN USING

DMIGSFIX=EXTID.

ABOVE CARD DOES NOT BEGIN WITH A NON-NUMERIC WORD.

User information:

XYPLOT commands must begin with character data.

%1 IS NOT RECOGNIZED ON ABOVE CARD.

User information:

Unrecognized XYPLOT command.

ILLEGAL VALUE SPECIFIED.

User information:

See Section 13.3 of NX NASTRAN Reference Manual.

%1 CONTRADICTS PREVIOUS DEFINITION.

User information:

Conflicting requests on an XYPLOT command.

%1 DELIMITER ILLEGALLY USED.

User information:

XYPLOT error; see Section 13.3 of NX NASTRAN Reference Manual.

%1 IS ILLEGAL IN STATEMENT.

User information:

XYPLOT error; see Section 13.3 of NX NASTRAN Reference Manual.

%1 IS ILLEGAL IN STATEMENT.

User information:

XYPLOT error; see Section 13.3 of NX NASTRAN Reference Manual.

%1 IS ILLEGAL IN STATEMENT.

User information:

XYPLOT error; see Section 13.3 of NX NASTRAN Reference Manual.

TOO MANY SUBCASES. MAXIMUM = 200 ON ANY ONE XY-OUTPUT COMMAND CARD.

User information:

No more than 200 subcases are allowed on an XYPLOT request command.

SUBCASE-ID IS LESS THAN 1 OR IS NOT IN ASCENDING ORDER.

User information:

Subcases must be positioned in ascending order.

%1 = POINT OR ELEMENT ID IS ILLEGAL (LESS THAN 1).

User information:

XYPLOT error; see Section 13.3 of NX NASTRAN Reference Manual.

NEGATIVE OR ZERO COMPONENTS ARE ILLEGAL.

User information:

XYPLOT error; see Section 13.3 of NX NASTRAN Reference Manual.

ALPHA-COMPONENTS ARE NOT PERMITTED FOR STRESS OR FORCE XY-OUTPUT REQUESTS.

%1 COMPONENT NAME NOT RECOGNIZED.

User information:

XYPLOT error; see Section 13.3 of NX NASTRAN Reference Manual.

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 characters.

Any characters in columns 73 and on are ignored in the XYPLOT section.

TYPE OF CURVE WAS NOT SPECIFIED. (E.G. DISPLACEMENT, STRESS, ETC.).

User information:

XYPLOT error; see Section 13.3 of NX NASTRAN Reference Manual.

MORE THAN 2 OR UNEQUAL NUMBER OF COMPONENTS FOR ID-S WITHIN A SINGLE FRAME.

User information:

XYPLOT error; see Section 13.3 of NX NASTRAN Reference Manual.

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.

INSUFFICIENT CORE FOR SET TABLE.

User information:

Reduce the number of requests or increase memory. Six words are

used for each frame.

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.

COMPONENT VALUE = %1 IS ILLEGAL FOR AUTO OR PSDF VECTOR REQUESTS.

User information:

XYPLOT error; see Section 13.3 of NX NASTRAN Reference Manual.

COMPONENT VALUE = %1 IS ILLEGAL FOR VECTOR TYPE SPECIFIED.

User information:

XYPLOT error; see Section 13.3 of NX NASTRAN Reference Manual.

THE ABOVE COMMAND MUST END WITH ONE INTEGER VALUE.

THE NUMBER OF SUBDMAPS BEING COMPILED EXCEEDS THE MAXIMUM ALLOWED NUMBER OF %1 FOR THIS VERSION.

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 condsidered valid,

since it would not match the current NDDL.

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 solution.

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:

When compiling a user-supplied SUBDMAP, the SUBDMAP must always begin

with a SUBDMAP statement.

THE «SOUIN=» COMPILE OPTION AND INLINE DMAP CANNOT BOTH BE SPECIFIED

THE «SOUIN=» DBSET CANNOT BE A «SCRATCH» DBSET

THE COMPILE COMMAND CANNOT RESTORE SOURCE FROM %1 DBSET, SINCE THIS IS A DATA BASE INITIALIZATION RUN

USER ACTION: CHECK SPELLING 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.

NO INFORMATION TO PROCESS ON THE PROJECT KEYWORD

NO INFORMATION TO PROCESS ON SOL STATEMENT

NO INFORMATION TO PROCESS ON THE COMPILE EXECUTIVE COMMAND

EXTRANEOUS DATA FOUND ON %1 STATEMENT.

NO INFORMATION TO PROCESS ON SECURITY COMMAND

PROJECT ID MUST BE ENCLOSED IN SINGLE QUOTES

MISSING PROJECT ID ON PROJECT COMMAND

NO INFORMATION TO PROCESS ON LINK CARD

NO INFORMATION TO PROCESS ON INIT STATEMENT

NO INFORMATION TO PROCESS ON EXPAND STATEMENT

NO INFORMATION TO PROCESS ON ASSIGN COMMAND.

NO INFORMATION TO PROCESS ON ACQUIRE STATEMENT.

END-OF-FILE ENCOUNTERED WHILE READING NDDL.

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

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.

AN UNRECOGNIZABLE NDDL NAME APPEARS ON THE ACQUIRE STATEMENT

USER INFORMATION: THE VALID NAMES ARE NDDLOLD AND NDDL FOR THE OLD AND THE NEW SOLUTION SEQUENCES, RESPECTIVELY.

RECL SPECIFICATION IS NOT REQUIRED FOR %1 LOGICAL NAME.

USER INFORMATION: ASSIGNED RECL OF %2 WORDS IS REPLACED BY SYSTEM DEFAULT RECL OF 1024 WORDS.

RECL SPECIFICATION IS NOT REQUIRED FOR %1 LOGICAL NAME.

USER INFORMATION: RECL IS IGNORED.

RECL SPECIFICATION IS NOT REQUIRED FOR WRITING DATA BASE FILES.

USER INFORMATION: RECL IS IGNORED.

FORM SPECIFICATION IS NOT REQUIRED FOR WRITING DATA BASE FILES.

USER INFORMATION: FORM IS IGNORED.

UNIT SPECIFICATION IS NOT REQUIRED FOR %1 LOGICAL NAME.

USER INFORMATION: UNIT IS IGNORED.

UNIT SPECIFICATION IS NOT REQUIRED FOR WRITING DATA BASE FILES.

USER INFORMATION: UNIT IS IGNORED.

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.

FORM SPECIFICATION IS MISSING ON THIS ASSIGN CARD.

STATUS SPECIFICATION IS MISSING ON THIS ASSIGN CARD.

RECL SPECIFICATION IS MISSING ON THIS ASSIGN CARD.

UNIT SPECIFICATION IS MISSING ON THIS ASSIGN CARD.

SIZE SPECIFICATION IS MISSING ON THIS ASSIGN CARD.

THE SECURITY KEYWORD IS MISSING ON THE RESTART COMMAND.

USER ACTION: REMOVE THE PARENTHESES, IF NO SECURITY IS DEFINED IN THIS DATA BASE.

THE SECURITY KEYWORD IS MISSING ON THE DBDIR COMMAND.

REMOVE PARENTHESES IF NO SECURITY CODE DEFINED IN THIS DATA BASE

THE SECURITY KEYWORD IS MISSING ON THE DBCLEAN COMMAND.

USER ACTION: REMOVE THE PARENTHESES, IF NO SECURITY CODE DEFINED IN THIS DATA BASE

THE EXPAND STATEMENT IS MISSING THE KEYWORD «LOGICAL=»

THE DBDIR COMMAND IS MISSING KEYWORD «VERSION=» ID

THE DBCLEAN COMMAND IS MISSING THE KEYWORD «VERSION=» ID

ILLEGAL FORM KEYWORD.

USER INFORMATION: THE VALID FORM KEYWORDS ARE: FORMATTED OR UNFORMATTED.

INVALID STATUS KEYWORD.

USER INFORMATION: THE VALID STATUS KEYWORDS ARE: OLD OR NEW.

LOGICAL NAME EXCEEDS MAXIMUM NUMBER OF CHARACTERS ALLOWED.

USER INFORMATION: MAXIMUM CHARACTER LENGTH IS 8.

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.

%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

«last» and the specification of «PROJECT=*» VERSION=LAST» will be

conflicting.

THE ABOVE DMAP MODULE 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.

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

«last» and the specification of «PROJECT=*» VERSION=LAST» will be

conflicting.

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=*)

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.

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

as WHERE(PROJECT=*,VERSION=*); otherwise, the default for VERSION is

«last» and the specification of «PROJECT=*» VERSION=LAST» will be

conflicting.

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 specification of «PROJECT=*» VERSION=LAST» will be

conflicting.

%1 STATEMENT 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.

%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. 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.

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.

PROJECT ID HAS 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 specification of «PROJECT=*» VERSION=LAST» will be

conflicting.

LOGICAL= 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.

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.

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 specification of «PROJECT=*» VERSION=LAST» will be

conflicting.

SIZE SPECIFICATION IS NOT NECESSARY FOR THIS MACHINE.

USER INFORMATION: SIZE IS IGNORED.

THE EQUAL SIGN IS MISSING AFTER THE LOGICAL KEYWORD

THE EQUAL SIGN IS MISSING AFTER THE LOGICAL KEYWORD

THE EQUAL SIGN IS MISSING AFTER THE SYS KEYWORD.

THE LIST OF LOGICAL NAMES MUST BE IN ENCLOSED PARENTHESES

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.

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.

THE LOGICAL NAME SPACE OR MEM REQUEST IS MISSING A CLOSING PARENTHESIS.

USER ACTION : VERIFY THAT THE STATEMENT DOES NOT EXTEND BEYOND COLUMN 72.

THE LOGICAL NAME SPACE REQUEST IS MISSING A CLOSING PARENTHESIS

THE BUFFSIZE FOR USROBJ CANNOT BE CHANGED FROM THE MACHINE DEFAULT.

USER INFORMATION: BUFFSIZE PARAMETER IGNORED.

SYNTAX ERROR IN COMPILE EXECUTIVE COMMAND

USER INFORMATION: CHECK SYNTAX AND FORMAT OF COMPILE CARD

SYNTAX ERROR IN LINK EXECUTIVE COMMAND

USER INFORMATION: CHECK SYNTAX AND FORMAT OF LINK CARD

INVALID USE OF NSM OCCURS AT THE SUBCASE LEVEL.

ONLY ONE SUCH CARD IS ALLOWED PER PROBLEM OR PER SUPERELEMENT.

THE MODIFIED AND UNMODIFIED KEYWORDS ARE NO LONGER VALID ON THE RESTART COMMAND.

THE RESTART VERSION ID IS NOT DEFINED ON THE RESTART COMMAND.

A RESTART 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.

THE FORTRAN UNIT NUMBER SPECIFIED ON FMS COMMAND MUST BE AN INTEGER

UNIT=%1

THE VALUE SPECIFIED FOR %1 MUST BE AN INTEGER

%2=%3

THE VALUE SPECIFIED FOR DBUPDATE CARD HAS A BAD INTEGER FORMAT %1

THE VALUE SPECIFIED FOR VERSION IS NOT AN INTEGER.

THE VALUE IS %1

THE SPACE SPECIFIED FOR LOGICAL NAME %1 MUST BE AN INTEGER

SPACE DEFINED IS %2

THE VALUE OF THE SPECIFIED CLUSTER SIZE IS NOT AN INTEGER

THE VALUE IS %1

THE VALUE SPECIFIED FOR BUFFSIZE IS NOT AN INTEGER

THE VALUE IS %1

THE BUFFSIZE SPECIFIED FOR «MEM» MUST BE AN INTEGER

MEM=%1

THE VALUE SPECIFIED FOR RAM SIZE MUST BE AN INTEGER

%1=%2

SPACE SPECIFIED FOR LOGICAL NAME %1 MUST BE INTEGER

SPACE DEFINED IS %2

THE VALUE SPECIFIED FOR FORMAT IS NOT AN INTEGER

THE VALUE IS %1

THE VALUE SPECIFIED FOR VERSION IS NOT AN INTEGER

THE VALUE IS %1

THE VALUE SPECIFIED FOR VERSION IS NOT AN INTEGER

THE VALUE IS %1

THE VALUE SPECIFIED FOR RECL IS NOT AN INTEGER.

THE VALUE IS %1

THE VALUE SPECIFIED FOR UNIT IS NOT AN INTEGER.

THE VALUE IS %1

THE VALUE SPECIFIED FOR SIZE IS NOT AN INTEGER.

THE VALUE IS %1

THE FORTRAN UNIT NUMBER SPECIFIED ON AN INPUTT4 STATEMENT MUST BE AN INTEGER GREATER THAN 0.

UNIT SPECIFIED=%1

CANNOT OPEN FILE SPECIFIED IN THE IN4AMLS DMAP.

ERROR CODE RETURNED =%1

CANNOT CLOSE FILE SPECIFIED IN THE IN4AMLS DMAP.

ERROR CODE RETURNED =%1

THE FILE NAME MUST BE DEFINED FOR LOGICAL %1

THE LOGICAL NAME %1 IS NOT USER ASSIGNABLE.

UNIT NUMBER %1 HAS ALREADY BEEN ASSIGNED TO THE LOGICAL NAME %2

THE LOGICAL NAME %1 HAS ALREADY BEEN ASSIGNED TO THE FOLLOWING PHYSICAL FILE:

%2

ILLEGAL USAGE OF DBSET KEYWORD %1

ILLEGAL USAGE OF SCRATCH KEYWORD %1

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.

%1 IS AN INVALID EXPAND CARD KEYWORD

USER INFORMATION: THE VALID KEYWORDS FOR THE EXPAND STATEMENT ARE:

«MASTER», «DBALL», «USROBJ», «USRSOU», «OBJSCR», «DBSET_NAME», AND «SCRATCH»

THE MAXIMUM NUMBER OF DBSETS ASSIGNABLE TO THIS RUN HAS BEEN EXCEEDED

USER INFORMATION: THE MAXIMUM NUMBER ALLOWED IS %1

THE MAXIMUM NUMBER OF LOGICALS THAT CAN BE ASSIGNED WITH THE EXPAND COMMAND HAS BEEN EXCEEDED.

USER INFORMATION: THE MAXIMUM NUMBER ALLOWED IS %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

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 DEFAULT 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.

NO MORE THAN TEN DBCLEAN COMMANDS ARE ALLOWED.

NO MORE THAN ONE %1 COMMAND IS ALLOWED.

WHEN THE PROJECT ID ON THE DBCLEAN CARD HAS NOT BEEN DEFINED, A DELETION WITH «BLANK» PROJECT ID WILL BE ASSUMED.

THE PROJECT CARD HAS TO BE DEFINED PRIOR TO THE DBCLEAN CARD, WHEN DELETIONS OF THE CURRENT PROJECT ID ARE DESIRED.

WHEN THE PROJECT ID ON THE RESTART CARD HAS NOT BEEN DEFINED, A RESTART WITH «BLANK» PROJECT 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.

ONLY ONE %1 COMMAND IS FUNCTIONAL. THE OTHERS ARE IGNORED

DIRECTORY OUTPUT FORMAT OF FIRST DBDIR COMMAND WILL OVERWRITE THE CURRENT DBDIR COMMAND

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.

%1 CARDS IN DATA BASE INITIALIZATION RUNS ARE IGNORED.

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.

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 ABOVE THE EXECUTIVE CONTROL SECTION.

THE %1 CARD IS NO LONGER SUPPORTED IN THE EXECUTIVE CONTROL SECTION.

THE %1 CARD IS NO LONGER SUPPORTED IN THE EXECUTIVE CONTROL 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 Management

Section does not begin in column one.

THE %1 CARD IS NO LONGER SUPPORTED IN THE EXECUTIVE CONTROL SECTION.

USER INFORMATION: THE BEGIN STATEMENT IN THE EXECUTIVE CONTROL SECTION HAS BEEN REPLACED BY THE SUBDMAP DMAP

STATEMENT. SEE USER MANUAL SECTION 5.

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.

THE READ EXECUTIVE COMMAND IS NO LONGER A VALID COMMAND, OR IT IS NOT SUPPORTED IN THIS VERSION

THE ABOVE SOL CARD CONTAINS A DBSET VALUE EXCEEDING 8 CHARACTERS

VALUE = %1

INVALID SOLUTION SEQUENCE REQUESTED.

USER INFORMATION: VALID SOL NUMBERS ARE:

UNEXPECTED END-OF-RECORD DETECTED ON SCRATCH FILE %1

USER INFORMATION: THE SCRATCH FILE CONTAINING THE COMPILE STATEMENTS HAS PROBABLY BEEN DESTROYED.

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

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

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

%10

%11

%12

END-OF-FILE ENCOUNTERED WHILE READING SUBDMAP SOURCE

USER INFORMATION: SUBDMAP FILE MUST BE EMPTY

END-OF-FILE ENCOUNTERED ON UNIT %1. THE INPUT FILE IS 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 «ENDJOB» OR A NON-FMS CARD.

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.

END-OF-RECORD ENCOUNTERED WHILE READING SUBDMAP SOURCE

USER INFORMATION: SUBDMAP SOURCE IS MISSING AN «END» STATEMENT

COMPILE CARD SYNTAX ERROR. MISSING «=» OR NAME FOLLOWING EQUAL SIGN

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 ACTION: DELETE THIS FILE AND RESUBMIT THE JOB.

THE «END» STATEMENT IS MISSING FROM THE SUBDMAP SOURCE.

USER INFORMATION: THE «END» STATEMENT MARKS THE END OF EACH SUBDMAP.

NUMBER OF ASSIGNED PHYSICAL UNITS HAS BEEN EXCEEDED THE LIMIT =%1

THERE IS NO REQUEST FOR PROCESSING OF THE TIME STAMP BLOCK.

IT IS ASSUMED FOR ANY EXISTING MASTER DBSET THAT:

1. THE DEFAULT BUFFER SIZE =%1

2. THE DEFAULT CLUSTER SIZE = 1

THE MAXIMUM NUMBER OF DBLOCATE DATABASES HAS BEEN EXCEEDED. MAXIMUM NUMBER NUMBER ALLOWED =%1

LOGIC ERROR.

USER ACTION : SEND RUN TO SIEMENS PLM SOFTWARE CUSTOMER SUPPORT.

SUBDMAP %1 HAS GENERATED ONE OR MORE FATAL ERROR(S) (SEE ABOVE MESSAGES)—NOGO = %2

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.

VERSION = %1 PROJECT = %2 OF THIS DATA BASE IS NOT VALID FOR RESTART PURPOSES.

User information:

This can occur in a run when a user’s DMAP sequence and SYTEM cell

125 has not been set to 1. If this is the case, insert PUTSYS(1,125)

into the DMAP sequence.

A CIRCULAR DEPENDENCY CONDITION WAS FOUND WHILE PROCESSING %1

User information:

Examine the DEPEN statements and make the appropriate modifications.

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.

Some statements may be executed before these modules (arithmetic

assignments/expressions). Put misplaced module after IFP1 module.

THE DBSET NAME «%1» SPECIFIED ON A DBSETDEL STATEMENT DOES NOT EXIST.

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.

THE DBSETDEL STATEMENTS HAVE MORE THAN %1 DBSET NAMES.

A DBSETDEL STATEMENT SPECIFIES «%1» DBSET WHICH SHOULD NOT BE DELETED.

THE SIZE OF THE OSCAR FOR A SINGLE SUBDMAP HAS A LIMIT OF %1 WORDS WHICH HAS BEEN EXCEEDED FOR

THIS SUBDMAP (%2 WORDS REQUIRED).

USER ACTION: PARTITION THIS SUBDMAP INTO SMALLER SUBDMAPS.

THE OBJECT FOR THIS SUBDMAP IS NOT COMPATIBLE WITH THIS VERSION OF NASTRAN.

USER ACTION: RECOMPILE THIS SUBDMAP.

NUMBER OF CHARACTERS SPECIFIED FOR PARAMETER %1 EXCEEDS THE ALLOWABLE LIMIT OF 80.

DATA BLOCK «%1» IS A DBVIEW NAME AND IS SPECIFIED AS INPUT OR OUTPUT IN A CALL STATEMENT. THIS IS NOT ALLOWED.

THE VIEWNAME %1 IS REFERENCED ON MORE THAN ONE DBVIEW STATEMENTS.

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

A SYNTAX ERROR WAS DETECTED WHILE PROCESSING A %1 CLAUSE ON A %2 STATEMENT.

USER INFORMATION: ITEM BEING PROCESSED IS %3

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.

THE OFFSET ON ALTER/MALTER STRING%1 RESULTS IN A NEGATIVE LINE NUMBER.

NO MATCH WAS FOUND FOR STRING%1.

DMAP LINE NUMBER K1 IS GREATER THAN DMAP LINE NUMBER K2.

DMAP LINE NUMBER K1 OVERLAPS PREVIOUS ALTER.

PREVIOUS LINE NUMBER: %1 PREVIOUS K1:%2 PREVIOUS K2:%3

ALTER: %4

THE INLINE SUBDMAP %1 CANNOT BE SEARCHED FOR ALTER/MALTER STRINGS.

USER ACTION: COMPILE THE SUBDMAP AND APPLY THE ALTERS IN SEPARATE RUNS.

THE FOLLOWING MALTER STATEMENTS WERE NOT FOUND IN THE DMAP SOURCE FILES:

THERE IS A SYNTAX ERROR IN %1 OF %2 STATEMENT.

STRING1 IS NOT SPECIFIED ON THE MALTER STATEMENT ABOVE.

COMPILATION OF REGULAR EXPRESSION FAILED WITH RETURN CODE:%1

SUBDMAP %1 IS SPECIFIED ON MORE THAN ONE COMPILE STATEMENT WITH DIFFERENT SOUIN REQUESTS.

USER ACTION: SPECIFY SAME SOUIN ON THE COMPILE STATEMENTS.

THE VALUE SPECIFIED FOR OCCURRENCE ON THE %1 STATEMENT IS LESS THAN ZERO.

USER INFORMATION: THE VALUE FOR OCCURRENCE MUST BE AN INTEGER GREATER THAN ZERO.

SOLUTION SEQUENCE%1 HAS BEEN %2

USER ACTION: USE A VERSION OF NX NASTRAN PRIOR TO VERSION 69.

SOLUTION SEQUENCE%1 HAS BEEN %2

USER ACTION: USE SOL %3.

SPECIFY PARAM, CHECKOUT, YES IN THE BULK DATA.

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.

SOLUTION SEQUENCE%1 HAS BEEN %2

USER ACTION: USE SOL %3.

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.

SOLUTION SEQUENCE%1 HAS BEEN %2

USER INFORMATION: ALTERNATE SOLUTION SEQUENCE%3 WILL BE EXECUTED.

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.

SOLUTION SEQUENCE%1 HAS BEEN %2

USER ACTION: USE A VERSION OF NX NASTRAN PRIOR TO VERSION 69.

SOLUTION SEQUENCE%1 HAS BEEN %2

USER ACTION: USE SOL %3.

SPECIFY PARAM, CHECKOUT, YES IN THE BULK DATA.

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.

SOLUTION SEQUENCE%1 HAS BEEN %2

USER ACTION: USE SOL %3.

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.

SOLUTION SEQUENCE%1 HAS BEEN %2

USER INFORMATION: ALTERNATE SOLUTION SEQUENCE%3 WILL BE EXECUTED.

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.

DBSET %1 IS ALREADY SPECIFIED ON AN INIT STATEMENT.

USER INFORMATION: ONLY ONE INIT STATEMENT MAY BE SPECIFIED PER DBSET.

«NDDLOLD» IS NO LONGER AVAILABLE.

USER INFORMATION: «NDDL» WILL BE USED INSTEAD.

THE FOLLOWING ALTER STATEMENT INSERTS AFTER THE END STATEMENT.

THE FMS STATEMENT %1 IS NOT UNIQUE.

USER ACTION: SPECIFY EITHER %2 OR %3

INVALID CHARACTER «%1»

OPERAND IS MISSING BEFORE «%1»

THE EQUAL SIGN IS MISSING IN A %1 %2

THE EQUAL SIGN IS MISSING BEFORE «%1»

EXTRA CHARACTERS ARE SPECIFIED ON DEFINE STATEMENT «%1»

OPERATOR IS MISSING BEFORE «%1»

RIGHT PARENTHESIS IS UNBALANCED AT «%1»

RIGHT PARENTHESIS IS MISSING AFTER «%1»

THE DIAG%1 EXECUTIVE CONTROL STATEMENT IS INVALID.

USER INFORMATION: THE DIAG NUMBER MUST BE GREATER THAN ZERO AND LESS THAN 65.

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.

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.

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.

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 SUBCASE%4

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.

AN XY-OUTPUT REQUEST FOR POINT OR ELEMENT ID%1 — %2- 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.

AN XY-OUTPUT REQUEST FOR FLUID POINT ID%1 -%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.

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.

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.

COMPONENT =COMPONENT =%1 FOR ID=%2 IS NULL. THIS COMPONENTS CURVE NOT OUTPUT.