Control Data Corporation CYBER 170 Series Operator's Manual page 214

-
!
Q
0)
Q
~
W
(TI
0)
Q
Q
t'4
MESSAGE
FATAL CIO ERROR STATUS.
FATAL MAINFRAME ERROR.
FCN CSaaaa DSbbbb.
FIELD LENGTH EXCEEDED FOR LOCKS.
FIELD LENGTH EXCEEDED FOR USERS.
FILE BUSY PFN- fi1enam
UN-
usernam.
FILE DBID EMPTY.
FILE DBID NOT FOUND.
SIGNIFICANCE
A TAF CIO operation returned a fatal error
status which aborted TAF.
One or more of the following has occurred.
CSU address parity error
CSU fault
PP stop on CM read error
PP stop on PP parity error
- Double bit SECDED error
LCME double bit SECDED error (CYBER
176
only)
Operator message indicating that a function
reject error has occurred during an express
deadstart dump.
aaaa Channel converter status
bbbb Controller status
TAF does not have enough initialization
field length for allocating lock tables.
TAF does not have enough initialization
field length for allocating file control
tables.
Informative message indicating that MCS
attempted to attach the named file.
fi1enam File name
usernam User name
TAF requires at least one xxJ file and at
least one occurrence of xx (the data base
identifier) in the DBID file.
If TAF data manager is not being used, this
file may be redundant.
The file DBID is either not present or
incorrectly declared as an indirect access
file, or the TAF user index in MOD VAL does
not match the default TAF user index
(default value of
16).
ACTION
Inform site analyst.
Inform site analyst and
customer engineer. (For
further explanation and
procedures, refer to
sic
Register Error
Detection, Appendix F.)
Press carriage return to
retry the dump operation.
Decrease the locks
parameter on the CRM
statement, increase
the TAF initialization
field length, or inform
site analyst.
Decrease the users
parameter on the CRM
statement, increase
the TAF initialization
field length, or inform
site analyst.
None.
Refer to the NOS
Installation Handbook
for data manager
initialization
parameters.
Inform site analyst.
ROUTINE
TAF
1MB
EDD
TAF
TAF
MCS·
TAF
TAF