A data management procedure, called Error Correction Information System (ECIS), is described. The purpose of this system is to implement the rapid transmittal of error information between the NASTRAN Systems Management Office (NSMO) and the NASTRAN user community. The features of ECIS and its operational status are summarized. The mode of operation for ECIS is compared to the previous error correction procedures. It is shown how the user community can have access to error information much more rapidly when using ECIS. Flow charts and time tables characterize the convenience and time saving features of ECIS

Rogers, J. L., Jr.

Rosser, D. C., Jr.

English

NASA Technical Reports Server

THENASTRANERRORCORRECTIONI FORMATIONSYSTEM(ECIS)
David C. Rosser, Jr.
and
JamesL. Rogers, Jr.
NASALangley Research Center
SUMMARY
A new data managementprocedure, called Error Correction Information System(ECIS), is described, The purpose of this system is to implement the rapid trans-
mittal of error information between the NASTRANSystemsManagementOffice (NSMO)
and the NASTRANuser community. This paper summarizesthe features of ECIS and
its operational status. The modeof operation for ECIS is compared to the pre-
vious error correction procedures. It is shownhow the user community can have
access to error information muchmore rapidly whenusing ECIS. Flow charts and
time tables characterize the convenience and time-saving features of ECIS.
INTRODUCTION
In the past, NASTRANusers have been severely restricted in their access to
NASTRANerror information. Access has been via telephone, correspondence, the
NASTRANewsletter, and Software Problem Report (SPR)Log. Although many times
temporary and permanent fixes were given to the originator of the SPR, these fixes
were frequently not available to the entire NASTRANuser community until a new
version of NASTRANwas released. In an effort to improve user access to NASTRAN
error information, NSMOhas initiated ECIS (ref. i) on a commercial network,
using an established data base managementsystem (refs. 2 and 3).
THEERRORCORRECTIONI FORMATIONSYSTEM
ECIS is a positive step by the NSMOto provide the NASTRANuser community
with an expedient information storage and retrieval system for SPR's. This
system will support the two-way transmittal of information and SPRfixes among
the user community, NSMO,and the maintenance contractor on a daily basis.
493
https://ntrs.nasa.gov/search.jsp?R=19750023441 2020-03-19T21:27:48+00:00Z
Organization
The system consists of two distinct data bases. The first data base is the
User Con_entdata base (Table i). The User CommentData Base has three purposesI
The first and major purpose is for the two-way transmittal of information be-
tween NSMO and the user community. Through this data base the user can make
general comments, describe difficulties, or submit an SPR. The second purpose I
is bookkeeping. Each time a user accesses this data base, the user's NAME,
ORGANIZATION, DATE, and TIME OF DAY should be entered. From this information,
NSMO can compile statistics on use of the system. The third purpose of th_s
data base is for NSMO to respond to users. NSMO accesses the User Comment Data
Base daily, records the user comments or problems, and then updates the data
base with an acknowledgment, a solution to the problem, or an explanation of
NSMO's plans with respect to the user's specific problem. Then the user can
access the data base and learn that NSMO has received the data and what solu-
tions or alternatives are available.
The second data base (Table 2), called ECIS, consists of information and
updates pertinent to all active SPR's. When a new SPR is discovered, it is givez
a number and all known information about the SPR (shown in Table 2) is entered
into the data base in the same manner as in the SPR Log. As the SPR is pro-
cessed, a temporary fix, if available, and a permanent fix, whendetermined,
are added to the SPR in the data base. This gives all users simultaneous access
to all active SPRs with their current updates.
The system is accessible by users through CYBERNET, a national computer net.
work maintained by Control Data Corporation. The resources needed to utilize
ECIS are (i) a copy of NASA TM X-72651, (2) a desk-top, interactive computer
terminal, and (3) a contract with Control Data Corporation for computer time
on the CYBERNET System.
Querying ECIS
Software support for ECIS is a Data Base Management System called System
2000. System 2000 manages all definition, accessing, updating, quering, and
retrieving of information to and from the data base. System 2000 organizes the
data in a data base as an Element or a Repeating Group. The element consists of
a name standing for data within the data tables. Each element has a name and a
number which are synonymous as can be seen in Table 2. For example, if the user
wants an output statement which prints SPR number and user name, he types "PRINT
SPR NUMBER, USER NAME" or "PRINT CI, C2". SPR NIIMBER is synonymous with CI and
USER NAME is synonymous with C2 in the ECIS data base.
The Repeating Group (RG) allows elements to take on multiple values. For
each SPR entered into the data base, there will be only one SPR NUMBER but there
might be several SUBROUTINE data items entered indicating which subroutines need
modification. The name used for a Repeating Group is for definition only and
_94
les not take on data values. For example, in Table 2 the only function of the
epeating Group described as PERMANENTFIXES is to define PERMFIX IBM, PERM
_X CDC,and PERMFIX UNIVACas elements which mayhave multiple values.
ECIS retrieval commandsrange from the very simple to the very complex.
he retrieval commandsare in the form of PRINT (Something), or PRINT (Something)
_ERE(Certain Conditions Exist). The quantity and form of the output is con-
rolled entirely by the user through proper definition and ordering used in the
etrieval commands.
There are two general forms of output statement: The first is of the form
INT (Print Clause) and the second is of the form PRINT (Print Clause) WHERE
_ondition Clause).
r The print clause is the simplest form used in obtaining output from the
ata base. The print clause is only a list of data base items the user wants
.
!rlnted. The data can be printed in any order or number by listing in the print
lause each item wanted and in the order wanted. The only restriction is that
ch item must be called
[_finitione of the by its proper name or element number as shown in theECIS data base in Table 2. If data from Repeating Groups (RG)
re included in the print clause, the name must be preceded with a (, BY ENTRY ,)
erator.
Examples:
PRINT SPRNUMBER:
PRINT SPR NUMBER, USER NAME, SUBROUTINE:
PRINT C2, SPR NUMBER, C3, LEVEL FOUND:
PRINT CI, BY ENTRY, SUBROUTINE:
PRINT CI, C3, C4, C2:
The condition clause can take many forms, such as AND, OR EQUAL (EQ), NOT
:QUAL (NE), GREATER THAN (GT), LESS THAN (LT), LESS THAN OR EQUAL TO (LE),
;REATER THAN OR EQUAL TO (GE), EXISTS, AND FALLS. If data for repeating groups
is included in a where clause, it must be preceded by an ENTRY HAS operator.
Examples:
PRINT SPR NUMBER WHERE SPR NUMBER EQ 395:
PRINT CI WHERE C7 EXISTS:
PRINT CI WHERE LEVEL FOUND GE 15.1:
PRINT USER NAME WHERE SPRNUMBER LT i000
OR SPR NUMBER GT 200, AND USER NAME NE
ROSSER, AND USER ORGANIZATION EXISTS:
PRINT CI, BY ENTRY, C34 WHERE C6 FALLS AND
ENTRY HAS MODULE EQ SDR2:
There are two special cases which may be needed by some users: the PRINT
_NTRY and the PRINT ENTRY WHERE (Condition Clause). The PRINT ENTRY command
;ill print out the entire data base. This command however will cause excessive
_rintout. If all of this information is desired, it is suggested that the SPR
495
Log be purchased from COSMIC. The PRINT ENTRY WHERE command can be used to
print one or many entire entries with one command. For instance, if one wanteq
the entire entries for all SPR's submitted by a particular user, he would typel
!
PRINT ENTRY WHERE USER NAME EQ WALL, JAMES
Several sample problems with user entries and system responses are given
in Appendix A.
POTENTIAL OF ECIS
The old method of communicating and processing NASTRAN SPR's is diagramed
in figure i. The process began by the user mailing an inconsistency and its
documentation (listing, dump, deck, etc.) to NSMO. NSMO then determined what
caused the inconsistency. It may have been a user error, a previously reporte_
error, or an SPR. NSMO then responded to the user by mail, possibly with a
temporary fix. If enough documentation was sent to aid in correcting the erro_
the SPR was forwarded to the maintenance contractor. The maintenance contract_
then recorded the error in the SPR Log, coded a fix, and implemented the fix
into a new level of NASTRAN.
The disadvantage with this method was that there was no feasible way to
rapidly distribute this error information to the entire user community. The
old system for distribution of error information included the NASTRAN Newslett_
(once every 6 months), the NASTRAN SPR Log (once every 8 months), or a new lev_
of NASTRAN (once every 12-24 months). With over 1200 SPR's and 500 users on t_
mailing list, it was not feasible to mail a copy of the errors or fixes to eacl
user as they became available. Thus the time span for receipt of error correc-
tion information was quite long. Minimum times are shown in figure 2. Note
that long periods of time elapsed between the determination of a fix and its
availability to the user community.
The new process for handling NASTRAN SPR's, with ECIS, is diagramed in
figure 3. This method differs from the old method in that the user can imme-
diately determine if the inconsistency is a reported SPR by examining ECIS.
If it is a reported SPR and a temporary or permanent fix exists, the user can
implement the fix into NASTRAN. If the SPR has not been reported, the user cal
report the error through ECIS and mail the appropriate documentation to NSMO.
This way, the entire user community will have knowledge that the error exists.
This method then proceeds the same as the old method except for one important
difference. With the new method, any time a temporary or permanent fix is foul
it is immediately put into ECIS and becomes available to the entire user commu
nity.
Once ECIS is accepted by the NASTRAN user community, the time spans from
submission of error to receipt of fix are expected to greatly decrease, as sho,
in figure 4. With ECIS, all users could have knowledge of an SPR within one d
a temporary fix in one week, and a permanent fix in one month. These time spa
are minimum time spans and are not meant to imply that all SPR's will be solve,
within this new time frame.
496
This procedure does, however, give all users immediate knowledge of the
xistence of a new problem, therefore eliminating the time and effort of many
_sers responding to an SPRwhich is already being worked on or solved. If a
fix is available, the user will save both time and computer cost normally spent
lin debugging NASTRANor redesigning the problem. Thus, significant savings in
computer time and manpoweris expected when ECISbecomesan integral part of
NASTRAN.
STATUSOFECIS
ECISwas originally created by inputting all SPR's from the SPRLog into the
_ata base. To reduce storage costs and extraneous material, all SPR's corrected
before the release of Level 15 of NASTRANwere deleted from ECIS. Continuing
iefforts are being made to increase the readability and efficiency of ECIS. New
SPR's, temporary fixes, and permanent fixes are frequently being added. The sta-
Itus of individual SPR's is updated as the SPRis fixed. Whenthe code to imple-
ment a fix to an SPRis integrated into an archive version of NASTRAN,the number
of that version is put into the LEVELFIXEDcomponentof ECIS. Once that fix is
_erified as correct, the STATUSCODEcomponentfor that SPRis updated to FIN
_nd the fix is placed in the PERMFIX components. At present, there have been
1202 SPR's reported to NSMO. The status of ECIS is:
• 587 SPR's
• 25 SPR's with permanent fixes
• 54 SPRVswith temporary fixes
• 275 SPR's with a level fixed entry
• 164 SPR's with a status code of FIN
• 30 SPR's classified as previously reported errors
CONCLUDINGREMARKS
By utilizing an organized procedure for storing, updating, and retrieving
large volumes of data, an Error Correction Information System (ECIS) has been
Ideveloped for NASTRAN.This system supports the two-way transmittal of NASTRAN
information, errors, and error corrections between the user and the NASTRAN
iSystemsManagementOffice; ECIS can be accessedby telephone through any desk-
top interactive computer terminal.
i
ECIS shows promise of greatly reducing the long times that heretofore have
been needed to disseminate error correction information to the user community.
Users of ECIS will have all SPR's, user information, and updates available on
demand and fixes will be installed in the ECIS data base as they are devised.
497
APPENDIXA
SAMPLEPROBLEMS
io Problem:
Entry:
Response:
Print all information for a particular SPR.
Print entry where C1 EQ 1190:
SPR NUMBER = 1190
USER NAME = WINTER, RON
USER ORGANIZATION = TENNESSEE EASTMAN
COMPUTER = IBM 360
LEVEL FOUND = 15.10
DATE REPORTED = 04/02/1975
OPERATING SYSTEM = OCC
PRIORITY = 2.00
RIGID FORMAT = 1,0
MODULE = RBMG2
SUBROUTINE = SDCOMP
STATUS CODE = CKC
ERROR CODE = SOFTWARE ERROR
DESCRIBE ERROR = SPILL PROBLEM IN RBMG2 CAUSES SYSTEM
FAILURE
o Problem:
Entry:
Response:
Find all SPR's associated with a particular user,
Print SPR number where user name EQ Walz, Joe:
SPR NUMBER = 731
SPR NUMBER = 954
SPR NUMBER = 978
SPR NUMBER = 1006
SPR NUMBER = 1067
SPRNUMBER = 1068
o Problem:
Entry:
Same as example 2 with C values substituted for element names.
Print CI where C2 EQ Walz, Joe:
498
Response:
SAMPLEPROBLEMS(Cont' d. )
SPRNUMBER= 731
SPRNUMBER= 954
SPRNUMBER= 978
SPRNUMBER= 1006
SPRNUMBER= 1067
SPRNUMBER= 1068
Problem:
Entry:
Response:
Find all SPR_sreported in a particular time frame,
Print SPRNumberwhere C7GE01/01/69 and C7 LT 01/01/70:
SPRNUMBER= 13
SPRNJ/MBER= 69
SPRNUMBER= 115
Problem:
Entry:
Response:
Find all SPR's reported between two levels of NASTRAN.
Print CI where C6 GT15.5 and C6LT 15.7:
SPRNUMBER= 528
SPRNUMBER= 752
SPRNUMBER= 777
SPRNUMBER= 870
SPRNIIMBER= 881
SPRNUMBER= 883
SPRNUMBER= 884
SPRNUMBER= 896
SPRNUgmER= 973
SPRNUMBER= 986
SPRNUMBER= 987
SPRNUMBER= 988
SPRNUMBER= 989
SPRNUMBER= 993
SPRNUMBER= 1007
SPRNUMBER= 1020
SPRNUMBER= 1049
SPR_ER = 1065
Problem:
Entry:
Print the SPRnumber and the description of any SPRthat failed
in a particular subroutine of a particular module.
Print CI, by entry, C34where entry has C16 EQTRHTand entry
has C18 EQTRHTIA:
499
Response:
SAMPLEPROBLEMS(Cont'd.)
SPR UMBER= 986
DESCRIBERROR= SEVERALERRORSAREPRESENTWITHRESPECT
DESCRIBERROR= TOTHEUSEOFQVECTCARDSIN HEATTRANSFER
DESCRIBERROR= ANALYSIS.
DESCRIBERROR= FORIDENTICALBULKDATA,QVECTLOADSARE
DESCRIBERROR= APPLIEDDURINGA NON-LINEARSTEADSTATE
DESCRIBERROR= ANALYSIS,BUTNOTDURINGA TRANSIENTRUN.
SPRNUMBER= 1044
DESCRIBERROR= THIS PROBLEMRANSUCCESSFULLY,FOLLOWING
DESCRIBERROR= WHICHTWOOF THETEMPCARDSUSEDTODEFINE
DESCRIBERROR= SET500 WEREREMOVED,LEAVINGONLYTHE
DESCRIBERROR= TEMPDCARDTODEFINETHESET.
SPRNUMBER= 1083
DESCRIBERROR= A TRANSIENTHEATTRANSFERPROBLEMSTOPPED
DESCRIBERROR= IN MODULETRHTWITHA USERABENDOF680.
DESCRIBERROR= SUBR. TRHIA WAS TO CONTAIN 3 ERRORS IN
DESCRIBE ERROR = THE CODE.
o Problem:
Entry:
Response:
Print the SPR number, description, and temporary fix for a p_
ticular module that has a temporary fix.
Print CI, by entry, C34, by entry, C36 where entry has C16 E(
SMPI and entry has C36 exists:
SPR NUMBER = i001
DESCRIBE ERROR = AN OMIT CARD WAS ADDED TO A PREVIOUSLY
DESCRIBE ERROR = OPERATIONAL TRANSIENT PROBLEM, AND THE
DESCRIBE ERROR = ABOVE ERROR OCCURRED.
DESCRIBE TEMP FIX = ALTER 65,65
DESCRIBE TEMP FIX = SMPI HUSET, HKFF,,,/NGO, HKAA,HKOO,
DESCRIBE TEMP FIX = HLOO,HUOO,,,,,$
o Problem:
Entry:
Response:
Print the SPR number and permanent fix for a particular modu
that has a permanent fix.
Print CI, by entry, C39 where entry has C16 EQ XYTRAN and e_
has C39 exists:
SPR NUMBER = 1072
PERM FIX CDC = TEST
PERM FIX CDC = CARD
PERM FIX CDC = CARD
PERM FIX CDC = CARD
PERM FIX CDC = CARD
PERM FIX CDC = CARD
ALTER FOR LEVEL 15.5
*INDENT SI072L79
*INSERT RAND5.222
LLIST=LLIST-5*(II-ICDONE+I)
*DELETE RAND5.225
*COMPLETE RAND5
5OO
So Problem:
Entry:
Response:
SAMPLE PROBLEMS (Cont'd.)
Find the number of SPR's now in ECIS
Tally/all/Cl:
ELEMENT- SPR NUMBER
MINIMUM- 13
MAXIMUM- 9006
594 UNIQUE VALUES
594 OCCURRENCES
501
REFERENCES
io Rosser, David C., Jr.: The Design and Use of an Error Correction Inform
tion System for NASTRAN. NASA TM X-72651, 1974. J
o The Information Network Division of Computer Science Corporation: Syst_
2000 Reference Manual, E00209-01, 1973.
o CYBERNET Service Control Data Corporation: System 2000 Level 2 User In-
formation Manual, 86604500, 1974. i
502
TABLEi
DEFINITIONOF USER COMMEMTDATABASE
1" USERNAT
2" USERORGANIZATION
3" DATE
4" TIMEOF DAY
5" USERCOMMENTS(RG)
6" COMMENTS
7* NSMOCOMMENTS(RG)
8" NSMO
5o3
m_
0
t_4
,..J
1.1..
j..-
5o_
Jf
AZ
Q
Z
_mne
in
OmmO
5P'
tmmO
tJ
W
A
V
z
5O5
/ -
_L __W
lJ
0
_8
ILl z
m
,0'--
:OL. I.I.
E
L
I
i
uJ
t
!
t
i
t
u _
_ w
_ w
Z
Z
W
i_-
<_
c_
o
o
..c
0
I
_J
506
0 o0
I
0_
\
\
<
Z_
0
Z
0
t..r-I
ZrJ_
t
/
r..t.l
i
[-_
ZO
r..=l [-_
8
0
I _ i-.l [-._
r_z
0
7_
.,-I
,--I
u_
0
"0
0
<
Z
0
0
12u
N
._
._
I
_07
-1 1
i
LLI_
_.-L L.LJ
r
/ ....
;_.C:
;_-(..
L J,::: ' "
_-r_
;El--
xl
,,,_<
i --r- LLJI
/_ _
/ LLI o<';
I _ LJ.J
C_t_lOLl--
LIJI, II _" --J
|
(_J
LL
X
E
Idm
:_ "-) '_L_
L_. :El
_-* LLI!
_O.-J
LLI _3
LJJ _::1
rYEL
'T
ILLJ LLJ/
zE
• W
LL! Xl
LL! El
t---O
0
__1
__1
_3
ffl
r./?
Z
z
-_1
,-_
=:
0
0
_J
Z
I
508
[-_ _ r._
i-1
X_
Z_
t
°_
m_
1.1
°_=1
Z
o
[-_
°_
I
°_,,I
509


The NASTRAN Error Correction Information System (ECIS)

Abstract

Similar works

Full text

Available Versions

NASA Technical Reports Server