NX Nastran DMAP Programmer's Guide - Kxcad.net

746
DATABLK
Describes data blocks used for NDDL access
Remarks:
1. In general, the data block completely describes all possible records of a data block.
At any given instance, some or even all of the records that comprise the
description may not physically exist in any given data block.
2. For UNDEF items, DEPENdencies are not checked and for transfer of data
between machine types they are considered integer zero.
Examples:
1. The simplest DATABLK statement might be of the form:
DATABLK,INDATA,PATH=DMS,LOCATION=DBDN,EOF
A more complex specification of a DATABLK statement is of the form:
DATABLK,GEOM4S,TYPE=TABLE,PATH=PEIDI,LOCATION=IFPX,SAMEAS,
GEOM4,EOF
In the above statement, SAMEAS,GEOM4 specifies that GEOM4S has the same
data block description specified under the DATABLK,GEOM4 statement.
2. Consider the following:
DATABLK ,EQEXIN,TYPE=TABLE,PATH=PEIDI,LOCATION=IFPX,
RECORD=HEADER,NAME(2),CHAR4,EOR,
RECORD=EXT2INT,
GRIDID,I,INTERNAL,I,
EOR,
RECORD=EXT2SIL,
GRIDID,I,TENXSIL,I,EOR,EOF
The NAME(2) above represents a two word item with each word four characters
in length. The RECORD=EXT2INT gives this particular record the record-name
EXT2INT. In the record named EXT2INT there are two integer items called
GRIDID and INTERNAL. These two groups are repeated until the EOR is
encountered.
A simple ENTRY ... ENDENTRY grouping is:
RECORD=MAT9(2603,26,300),
MID,I,
ENTRY=GEES,
G(21),RS,
ENDENTRY,
RHO,RS,...,
EOR,
In the above example, the Gs were grouped into an ENTRY-ENDENTRY group
called GEES with 21 entries. The group items can be accessed as a whole group
or as individual members. Also note the (2603,26,300) entry. Internally, for many
records, NX Nastran sees the describer (2603,26,300), rather than the record name
(e.g., MAT9).