Messages
The messages are listed sequentially in ascending sequence by
their message Number. Each Message entry is made up of the
message Number, its Text, and Class, an expanded
Explanation, a brief System Action, and suggested Operator
and Network Administrator Responses.
The Explanation
is an extended description of the condition or
conditions that created the message situation. The Explanation
may also contain a description of Network Director processing
associated with the message.
The System Action describes what Network Director will do
automatically as a result of the message being issued.
The Responses are intended to aid
the network user and/or Network Administrator in how to
respond to the condition represented by the message.
The Class is a logical grouping of the messages by
their functional impact. The Class Codes, their numeric values,
and their meanings are:
| Class |
Meaning |
Color |
| I (20) |
Internal Message Class, a Network Director
logical error has occurred. |
Red |
| R (40) |
Reply Message Class, a message that is used to
reply to a Network Administrator request. |
Yellow |
| C (50) |
Change Message Class, used to group
messages that identify some type of a state change (application
availability, etc.). |
Turquoise |
| S (60) |
Security Message Class, used to group
messages associated with network element
security related messages. |
White |
| G (80) |
General Message Class, decribes events that are
of an informational nature. |
Blue |
| D (90) |
Debug Message Class, used to group
messages permitting an intermediate level of diagnosis of
Network Director operations. |
Red |
| T (100) |
Trace Messages, internal logical trace messages |
Green |
Message Classes
Variable information is represented in the text of a message
by a string in a non-bold font representing
the variable information that will be inserted.
These values will be filled in at execution time by
Network Director with appropriate values.
Many of the variable items in the messages are filled in as a result
of the generalized variable processor embedded within Network Director.
See Variables in the Network Administrator's Guide
for additional information.
The contents of any message may be modified by editing the message
text and modifying it. It is possible to change any of the text
to another string of characters. You may also remove variable tokens,
but you must remove the last token first.
For example, you cannot
affect the order of the replacement tokens within the message
text.
The variable tokens will be represented in the message by dollar signs
"$" for alphanumeric
variables and pound signs "#" for numeric values.
Network Director variables may be removed, inserted, or moved as desired with
no adverse impact.
Network Director also stores these extended descriptions for the messages in the
External File. You can access the descriptions by entering
HELP TNDxxxx, where xxxx is the message number that you would like
additional information about.
You can enter this INFO command whenever your terminal is connected
to the INFO facility or any other screen that accepts the HELP
command.
You can update the individual characteristics of a message
interactively from Network Administration via the SHOW MESSAGES
processor. This mechanism will allow you to update the message text
and class as discussed in this manual.
The SHOW MESSAGES processor will also allow you to specify
additional special handling characteristics for the message.
It is possible to have an individual message written to the OS
log (WTL) and to have Network Director force an internal abend when the message
is issued. See the topic "Error Message Attributes" in the
Network Administrator's Guide for additional information.
The following messages are associated with
and issued by Network Director's
nucleus that operates as an individual job or virtual machine
in the operating system.
- TND0001I
- Storage wait under DFB [name]
- Explanation:
- A DFB attempted to conditionally
acquire storage and storage management could not
allocate it. The DFB was placed into a wait state
pending storage availability.
- System Action:
- Network Director will wait the DFB internally until storage becomes available.
- Operator Response:
- None.
- Network Adminstrator Response:
- Storage wait conditions will significantly
impact the throughput of Network Director.
Allocate additional virtual storage to Network Director.
- TND0002I
- Storage Allocation has failed - DFB [name]
- Explanation:
- An unconditional allocation of storage
has failed. There was no more operating system storage
available and all the storage pools are full.
- System Action:
- Abnormal termination 133 will be issued.
- Operator Response:
- None.
- Network Adminstrator Response:
- Allocate additional storage to Network Director.
- TND0003I
- Storage Allocation has failed
- Explanation:
- Same as TND0002 except the storage
shortage occurred when storage management was not
executing under the control of a DFB.
- System Action:
- Abnormal termination 133 will be issued.
- Operator Response:
- None.
- Network Adminstrator Response:
- Restart Network Director with additional virtual storage allocated.
- TND0004I
- Attempt to free Control Block is ignored
- Explanation:
- Storage Management received a request to
free a Control Block from the CB pool. This storage
pool is not recoverable and the request has been
ignored.
- System Action:
- Network Director will continue to operate.
- Operator Response:
- None.
- Network Adminstrator Response:
- This represents an internal logic error
within Network Director. Contact NRS Technical Support.
- TND0005I
- Free address is not on a proper boundary
- Explanation:
- Storage Management was able to locate the
free address within the proper GSA, but it wasn't on
the proper boundary within the block.
- System Action:
- The request has been ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- This is an indication of an internal logic
error. Contact NRS Technical Support.
- TND0006I
- [name] attempting to free an invalid address
[address] - offset [displacement]
- Explanation:
- Storage Management received an address to
free that could not be located as a valid address to
free.
- System Action:
- If RECOVERY=YES is in effect, the request is ignored and
processing continues. If RECOVERY=NO is in effect, a U0144 abend
is issued.
- Operator Response:
- None.
- Network Adminstrator Response:
- Contact NRS Technical Support.
- TND0007C
- Network Director [version number]
- Initialization is in progress
- Explanation:
- INIT successfully opened the output LOG
file and initialization is underway.
- System Action:
- Network Director will process the Configuration Parameters.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0008G
- [input parameter image]
- Explanation:
- This message contains the exact text
contained in a Configuration Parameter statement.
- System Action:
- The Parameter Statement is processed.
- Operator Response:
- None.
- Network Adminstrator Response:
- General Information.
- TND0009G
- Processing Parameter Deck
- Explanation:
- PARM is about to begin the processing of
the input Parameter Deck.
- System Action:
- Initialization continues.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0010G
- The [statement name]
statement is not valid as a Configuration Parameter
- Explanation:
- You have used a parameter statement that
is not allowed within the Parameter Deck. ACF2, APPLICATION,
DEFAULT, GLOBALS, GROUP, PROFILE, RELOAD, TERMINAL, and USER
are valid.
- System Action:
- The statement is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Remove the statement from the Parameter
Deck. It will be ignored for this execution.
- TND0011G
- This[statement] ( [statement name] )
is already defined
- Explanation:
- The first replacement value represents a
Statement Identifier whose Name (the second
replacement value) has been already defined.
- System Action:
- The statement is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Remove one of the duplicate definitions.
The second definition attempt is ignored.
- TND0012G
- This [statement] ([name])
with Extension [extension] is already defined
- Explanation:
- Replacement value 1 is a Statement
Identifier whose Name (replacement value 2) combined
with Extension (replacement value 3) has already been
defined.
- System Action:
- The statement is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Remove one of the duplicate definitions.
The second and subsequent definitions will be ignored.
- TND0013G
- [text string] is an unidentified statement or command
- Explanation:
- Network Director could not locate a
Statement Identifier with replacement value one's
value.
- System Action:
- The statement is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the specification or spelling of the
Statement Identifier. This message may also result
when you have forgotten to provide the continuation
characters (",") on a previous statement.
- TND0014G
- A name must be provided for the
[statement name] statement
- Explanation:
- The referenced statement type requires a
positional "name".
- System Action:
- The statement is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Provide a name for the statement.
- TND0015G
- Text [text string] is not a valid statement
identifier
- Explanation:
- When parsing a Parameter image, the
character string that should represent a statement
identifier cannot be identified as a valid statement.
- System Action:
- The statement is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the spelling of the Statement
Identifier. Insure that this message has not been
created through a missing continuation character
string.
- TND0016G
- The statement name is missing
- Explanation:
- The current Parameter image does not have
a statement name present as a positional parameter.
- System Action:
- The statement is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Provide a statement name and try it again.
- TND0017G
- [text string] identifies multiple statements - Ignored
- Explanation:
- You did not specify a sufficient number
of characters to uniquely identify the statement
utilizing Network Director abbreviation rules.
- System Action:
- The request is rejected.
- Operator Response:
- None.
- Network Adminstrator Response:
- Expand the number of characters used to
identify the statement to at least the minimum required
to uniquely identify the statement.
- TND0018G
- [statement name] is invalid during [phase]
processing
- Explanation:
- The statement entered (replacement value
1) cannot be used during this phase (replacement value
2) of execution.
- System Action:
- The statement is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Issue the statement at the proper point in processing.
- TND0019G
- Keyword or positional parameter specified incorrectly
- Explanation:
- A keyword or positional parameter must
terminate on the record image that initiates it.
Network Director was unable to locate a terminator for
the keyword on the parameter statement.
- System Action:
- The keyword or positional parameter is
ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the keyword or positional parameter and try it again.
- TND0020G
- The parameter value extends too far
- Explanation:
- While scanning for the values terminator
character, Network Director encountered the end of
the current parameter statement.
- System Action:
- The current operand is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the specification and try it again.
- TND0021G
- This statement has no positional operands - operand
ignored
- Explanation:
- A positional operand was encountered and
the current statement has no positional operands
defined.
- System Action:
- The current operand is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Investigate
for proper usage of the continuation string on a prior
record image or a missing value on a keyword.
- TND0022G
- Keyword [operand] is ambiguous within the
[statement name] statement
- Explanation:
- The keyword specified by replacement
value 1 is not unique within the statement identified
by replacement value 2.
- System Action:
- The keyword is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Expand the number of characters used to identify the keyword.
- TND0023G
- [text string] is an unrecognized keyword
- Explanation:
- Replacement value 1 represents a keyword
that is not defined as valid for the current statement.
- System Action:
- The operand is be ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the spelling of the keyword or
associate it with the proper statement.
- TND0024G
- The [operand] operand has an invalid length
- Explanation:
- The number of characters used to
represent the value for the specified keyword is too
large.
- System Action:
- The keyword is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Reduce the number of characters specified to
within the maximum specified under the keyword syntax.
- TND0025I
- PARMS is executing in an unidentified mode
- Explanation:
- PARMS does not recognize the WAE that has
been passed to it as belonging to DECK, OPER, or PARM.
- System Action:
- The current statement will not be processed correctly.
- Operator Response:
- None.
- Network Adminstrator Response:
- Contact NRS Technical Support.
- TND0026G
- Invalid use of [operand] operand
- Explanation:
- The parameter specified as replacement
value 1 cannot be used during this phase of
Network Director's execution.
- System Action:
- The parameter is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Evaluate the reason for attempting to
utilize the operand.
- TND0027G
- [statement name] has an invalid DAY specification
- Explanation:
- The first three characters of one of the
DAY parameters does not match a valid day
specification. The first three characters must exactly
match a day of the week.
- System Action:
- The current specification is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the specification for the next
execution attempt.
- TND0028G
- DAY specification must be at least three characters
- Explanation:
- The DAY operand was provided a value that
was less than three characters in length.
- System Action:
- The specification is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the specification.
- TND0029G
- TIME values must be 5 characters in length (HH:MM)
- Explanation:
- A TIME specification did not have the
proper number of characters specified for it to be
valid.
- System Action:
- The operand is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the specification by expressing it
in the HH:MM format.
- TND0030G
- The TIME value is in improper format (HH:MM)
- Explanation:
- The TIME specification must be made up of
2 two character numeric values separated by a colon.
- System Action:
- The specification is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the specification.
- TND0031G
- The PFKEY operand has an invalid value
- Explanation:
- The PFKEY value must be specified as 1-24, 01-24,
PF1-PF24, or PF01-PF24.
- System Action:
- The value is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the specification and try again.
- TND0032G
- [operand] has an invalid numeric value specified
- Explanation:
- The value for the numeric operand
identified in replacement value 1 is not made up of
numbers and/or valid short hand specifications (S,M,H,
K, or D).
- System Action:
- The value is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the value specifying a valid number.
- TND0033G
- INITIAL-DATA variable specification is invalid
- Explanation:
- The first character after INITIAL-DATA
was a "&", which indicates a special variable, but the
rest of the variable was unidentified.
- System Action:
- The specification is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Modify the specification to one of the
supported INITIAL-DATA variables.
- TND0034G
- The value for INITIAL-STATUS is invalid
- Explanation:
- The operands value was not ASIS or HELD.
- System Action:
- The operand is ignored. The default for
INITIAL-STATUS remains ASIS.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the specification.
- TND0035G
- The UPDATES operand must be YES or NO
- Explanation:
- An invalid operand value was provided for
UPDATES.
- System Action:
- The current attempt is ignored. The default
for UPDATES remains in effect.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the specification.
- TND0036G
- The COMMANDS operand must be YES, NO, DROP,
DISC, RESET, FLASH, or LOGON
- Explanation:
- An invalid operand value was provided for
the COMMANDS operand.
- System Action:
- The operand value is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the COMMANDS specification.
- TND0037G
- IDENTIFICATION= must be YES or NO
- Explanation:
- You provided an invalid value for the
IDENTIFICATION operand.
- System Action:
- The default condition for this operand
remains unchanged.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the specification.
- TND0038G
- [text string] is an invalid value for MESSAGES=
- Explanation:
- Each MESSAGES operand value must be BROADCASTS, NOTES, or MEMOS).
- System Action:
- The invalid operand is ignored.
The default for this operand remains unchanged.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the specification.
- TND0039G
- The PROFILE name exceeds eight characters
- Explanation:
- The name operand on the PROFILE statement
is too long.
- System Action:
- The operand is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the PROFILE operand specification.
- TND0040G
- The second PROFILE operand value is invalid
- Explanation:
- The second value in the PROFILE keyword must be
VIEW, CHANGE, or NO).
- System Action:
- The value is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the specification to one of the
valid values.
- TND0041G
- [operand] must have storage or disk specified
- Explanation:
- The BROADCASTS, MEMOS, or NOTES operand
did not have a valid first operand value.
- System Action:
- The operand is ignored. The default remains unchanged.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the operand specification and try it again.
- TND0042G
- The CONSOLE operand must have a YES or NO value
- Explanation:
- An invalid value was provided on the
CONSOLE operand.
- System Action:
- The current attempt is ignored. The default
condition will remain in effect.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the specification and try it again.
- TND0043G
- The NSI operand requires a YES or NO value
- Explanation:
- An invalid value was provided for the NSI
operand.
- System Action:
- The NSI operand is ignored. The default will remain in effect.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the value and try it again.
- TND0044G
- RPLS= must be specified greater than zero
- Explanation:
- The RPLS operand was provided with a zero
value, which is invalid.
- System Action:
- The RPLS default value will be used and this specification is
ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the RPLS specification.
- TND0045G
- Invalid SECURITY value specified
- Explanation:
- The value specified with the SECURITY
operand was unrecognized.
- System Action:
- SECURITY=NONE remains in effect.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the operand value and try it again.
- TND0046G
- The TERMINATE operand value is incorrect
- Explanation:
- An invalid value was provided as an
operand of the TERMINATE operand.
- System Action:
- The current attempt to modify the default is
ignored and the default remains in effect.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the specification.
- TND0047G
- VTAMOPER has an invalid value
- Explanation:
- An unacceptable value was provided as a
value for the VTAMOPER operand.
- System Action:
- The operand is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the operand value and try it again.
- TND0048G
- SELECTIONS= [value]
- Explanation:
- This is issued in response to a DISPLAY
statement and represents the current setting of the
SELECTIONS operand for the displayed control block or
network element.
- System Action:
- None.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0049G
- The PFKEY is undefined - update the Profile
- Explanation:
- You have pressed a 3270 Pfkey that is not
currently assigned a value in your Profile, or your
Profile is currently undefined.
- System Action:
- The PFKEY is ignored.
- Operator Response:
- Issue the PROFILE command to update the Profile with
the desired value.
- Network Adminstrator Response:
- If the operator is not authorized access to the profile, you
should update the appropriate PROFILE definition for the user.
- TND0050G
- The ACQUIRE value is invalid
- Explanation:
- An invalid value was provided for the ACQUIRE operand.
- System Action:
- The specification is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the operand specification.
- TND0051G
- Invalid positional parameter value for [statement name]
statement
- Explanation:
- The value for the positional parameter is
not one of the acceptable values for the statement
specified in replacement value 1.
- System Action:
- The parameter is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the syntax utilized and try it again.
- TND0052G
- The LOGO text exceeds a maximum of [numeric value]
- Explanation:
- The number of bytes required to hold the
LOGO extended value exceeds the maximum permitted by Network Director.
- System Action:
- The LOGO is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Reduce the size of the LOGO to be within the
specified number of bytes.
- TND0053C
- Termination is complete
- Explanation:
- This informational message is issued
immediately prior to Network Director closing the LOG DCB/DTF.
- System Action:
- Control is returned to the operating system.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0054C
- Termination Stage Two beginning
- Explanation:
- Network Director is entering its
second stage of termination processing.
- System Action:
- All pending disk i/o is complete and termination will continue.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0055G
- The errors detected should be corrected during execution
- Explanation:
- Network Director detected one or more
errors associated with the initial Parameter Deck.
- System Action:
- Network Director will complete initialization.
- Operator Response:
- None.
- Network Adminstrator Response:
- Errors that were encountered can be
corrected during execution from an authorized Network Administrator's terminal
via the SHOW command.
- TND0056G
- Keyword [operand] has a null operand
- Explanation:
- The value provided for the keyword
specified via replacement value 1 has a zero length.
- System Action:
- The operand is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the keywords value.
- TND0057C
- [element] [name] has been HELD
- Explanation:
- The TARGET operand that was provided for
this
network element
was not valid or was missing
altogether.
- System Action:
- The definition is placed into a HELD status.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the TARGET specification and then
RELEASE the
network element
- TND0058G
- APPLICATION [application name] for
[network element name] has not been defined
- Explanation:
- The network element specified in
replacement value 2 was authorized an APPLICATION
(replacement value 1) that was not defined via an
APPLICATION statement.
- System Action:
- The authorized application is eliminated
for the network element.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the availability of the APPLICATION definition.
- TND0059G
- The [network element] PROFILE
[profile name] does not exist
- Explanation:
- The network element identified with
replacement value 1 had a PROFILE specification
(replacement value 2) that was not described via a
PROFILE statement.
- System Action:
- The PROFILE operand is set to the default.
- Operator Response:
- None.
- Network Adminstrator Response:
- Define the PROFILE identified by the operand.
- TND0060C
- Initialization is complete
- Explanation:
- This message is issued after the Configuration Parameters
have been scanned and Network Director's environment is ready for the dispatcher.
- System Action:
- Network Director's dispatcher will now receive control.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0061T
- Dispatching [DFB name] at [offset]
in [CSECT name] priority [value]
- Explanation:
- Issued by the dispatcher each time a DFB
is dispatched and if the internal TRACE is on.
- System Action:
- None.
- Operator Response:
- None.
- Network Adminstrator Response:
- Informational only.
- TND0062T
- Entering Operating System WAIT
- Explanation:
- Issued by the dispatcher each time the
operating system WAIT is invoked and if the internal
TRACE is on.
- System Action:
- The WAIT SVC is issued.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0063T
- Posted awake
- Explanation:
- Issued by the dispatcher whenever
Network Director has been POSTed and dispatched by the
operating system. This is issued only when the
internal TRACE is on.
- System Action:
- Network Director will now dispatch one or more DFBs.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0064S
- The External File failed to [activity]
- Explanation:
- Issued when the OPEN or CLOSE operation
against the External File has failed.
- System Action:
- The External File may no longer be usable.
- Operator Response:
- None.
- Network Adminstrator Response:
- Investigate the return codes associated with
the failure and correct the problem.
- TND0065S
- The ACB return code is [numeric value]
- Explanation:
- An ACB based operation received a nonzero return code.
- System Action:
- Dependent upon the return code and operation underway.
- Operator Response:
- None.
- Network Adminstrator Response:
- Evaluate the reason for the return code and
take appropriate action.
- TND0066S
- The External File is already OPEN
- Explanation:
- An attempt was made to OPEN the External
File when it was already OPEN.
- System Action:
- The OPEN command is ignored and the External File remains OPEN.
- Operator Response:
- None.
- Network Adminstrator Response:
- None, the External File is already OPEN.
- TND0067S
- Time Stamp in the VTOC differs from the catalog entry
- Explanation:
- There is an error associated with the
External File and its VSAM Catalog entry.
- System Action:
- The External File may not be usable.
- Operator Response:
- None.
- Network Adminstrator Response:
- Take appropriate action to correct the
synchronization of the VSAM Catalog with the physical
volume containing the External File.
- TND0068S
- External File not properly CLOSED (run VERIFY)
- Explanation:
- The External File was not properly closed.
- System Action:
- The External File may not be available.
- Operator Response:
- None.
- Network Adminstrator Response:
- Execute IDCAMS VERIFY to resynchronize the
External File.
- TND0069S
- The External File is not defined in Job Control
- Explanation:
- The OS DD statement or DOS ASSGN is
missing from Network Director's execution job step
JCL or Job Control.
- System Action:
- The External File is not available for usage.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the JCL.
- TND0070S
- Insufficient virtual storage available for work areas
- Explanation:
- A VSAM operation could not obtain
sufficient storage to accomplish a Network Director
request.
- System Action:
- The External File may not be available.
- Operator Response:
- None.
- Network Adminstrator Response:
- The REGION= or SIZE= operand will require adjustment.
- TND0071S
- The specified External File PASSWORD is invalid
- Explanation:
- The VSAM-PASSWORD value provided did not
match the password associated with the External File.
- System Action:
- The External File facilities are unavailable.
- Operator Response:
- None.
- Network Adminstrator Response:
- Provide the proper password.
- TND0072S
- The External File is already CLOSED
- Explanation:
- An attempt to CLOSE the External File was
made when it was already CLOSED.
- System Action:
- The CLOSE operation is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- None, the External File is already closed.
- TND0073I
- Invalid EXECUTE form on VSAM Control Block Macro
- Explanation:
- An internal error within Network Director
has occurred during processing of a VSAM
Control Block.
- System Action:
- The VSAM request will not be performed.
- Operator Response:
- Contact the Network Administrator.
- Network Adminstrator Response:
- Contact NRS Technical Support.
- TND0074S
- Register Zero is [numeric value]
- Explanation:
- A VTAM/VSAM error has occurred and this
is the value in register zero.
- System Action:
- None, this is an informational message.
- Operator Response:
- None.
- Network Adminstrator Response:
- Evaluate this value along with others also
displayed to interpret what has occurred.
- TND0075G
- The Control Block at the specified address is wrong type
- Explanation:
- An internal error associated with a VSAM
based request has occurred.
- System Action:
- The VSAM operation will not be processed properly.
- Operator Response:
- None.
- Network Adminstrator Response:
- Contact NRS Technical Support.
- TND0076G
- Specified work area is too small for requested VSAM
fields
- Explanation:
- An internal error associated with VSAM processing has occurred.
- System Action:
- The requested operation will not be carried out.
- Operator Response:
- None.
- Network Adminstrator Response:
- Contact NRS Technical Support.
- TND0077G
- Target VSAM Control Block is already being operated on
- Explanation:
- Network Director attempted to use the same VSAM control block twice.
- System Action:
- The VSAM operation will not be performed properly
- Operator Response:
- None.
- Network Adminstrator Response:
- Contact NRS Technical Support.
- TND0078G
- VSAM work area did not begin on a fullword boundary
- Explanation:
- Network Director provided VSAM with a control block on an improper boundary.
- System Action:
- The VSAM operation will not be performed.
- Operator Response:
- None.
- Network Adminstrator Response:
- Contact NRS Technical Support.
- TND0079I
- The specified VSAM RPL is already active
- Explanation:
- Network Director attempted to reuse the same VSAM RPL twice.
- System Action:
- The requested VSAM operation will not be performed.
- Operator Response:
- None.
- Network Adminstrator Response:
- Contact NRS Technical Support.
- TND0080C
- VSAM [operation] RPL error, R15:
[numeric value], FDBK: [numeric value]
- Explanation:
- A VSAM activity identified by replacement text 1 received a return
code whose register 15 value and feedback values are as displayed.
- System Action:
- Execution continues, the VSAM activity may have completed normally.
- Operator Response:
- None.
- Network Adminstrator Response:
- Research the return codes for significance.
- TND0081S
- Record type: [control block name],
associated with [network element name]
- Explanation:
- The VSAM activity that failed was
associated with the type of Network Director control block
identified in replacement value 1. The basic key for
the record is identified in replacement value 2.
- System Action:
- Execution continues, the operation may have failed.
- Operator Response:
- None.
- Network Adminstrator Response:
- Utilize this message with TND0080 to
evaluate the cause of the difficulty.
- TND0082S
- End of External File encountered
- Explanation:
- A GET operation has completed with the
indication that the end of the External File was hit.
- System Action:
- A "not found" condition is returned to the caller.
- Operator Response:
- None.
- Network Adminstrator Response:
- None, unless a record should have been located.
- TND0083I
- Attempted STORE of VSAM record with duplicate key
- Explanation:
- Network Director attempted to store an EFR with a key value
identical to another already present in the External File.
- System Action:
- The new record will not have been stored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Contact NRS Technical Support.
- TND0084S
- Error detected during VSAM Key Sequence check
- Explanation:
- A VSAM based error has occurred within the External File.
- System Action:
- At least one External File record is improperly stored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Validate that the External File has been
properly maintained with Access Method Services. Contact NRS Technical Support.
- TND0085S
- VSAM record not found
- Explanation:
- An attempt to locate an EFR on the External File was unsuccessful.
- System Action:
- A "not found" condition is returned to the calling CSECT.
- Operator Response:
- None.
- Network Adminstrator Response:
- None required unless the record should have been located.
- TND0086G
- Control Interval already in exclusive hold by another
user
- Explanation:
- Competitive update within the External
File has created the condition where two users are
attempting to update the same VSAM CI at the same time.
- System Action:
- The second and subsequent attempts are rejected.
- Operator Response:
- Wait a few moments and retry the operation.
- Network Adminstrator Response:
- Contact NRS Technical Support.
- TND0087G
- Insufficient space on DASD for VSAM to extend the file
- Explanation:
- VSAM attempted to acquire an additional
extent for the External File and the available volumes
did not contain enough space.
- System Action:
- The External File can no longer be used to store new information.
- Operator Response:
- Contact the Network Administrator.
- Network Adminstrator Response:
- Allocate additional space to VSAM.
- TND0088G
- Insufficient virtual storage to complete the request
- Explanation:
- VSAM was unable to satisfy a Network Director
request due to a lack of available virtual storage.
- System Action:
- The request is not processed normally.
- Operator Response:
- None.
- Network Adminstrator Response:
- Increase the storage available to Network Director and VSAM.
- TND0089S
- All VSAM strings are tied up
- Explanation:
- VSAM was unable to acquire a string in order to process a request.
- System Action:
- Network Director will automatically retry the activity.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0090G
- GET for UPDATE missing before ERASE or PUT with UPDATE
- Explanation:
- Network Director has violated a basic VSAM principle.
- System Action:
- The request will not be completed properly.
- Operator Response:
- None.
- Network Adminstrator Response:
- Contact NRS Technical Support.
- TND0091I
- Attempted to change prime VSAM key during UPDATE
- Explanation:
- An attempt has been made to update a primary VSAM key.
- System Action:
- The request being processed is not completed normally.
- Operator Response:
- None.
- Network Adminstrator Response:
- Contact NRS Technical Support.
- TND0092I
- RPL options are not in a valid combination
- Explanation:
- The VSAM RPL contains an invalid combination of options.
- System Action:
- The VSAM request has not been processed.
- Operator Response:
- None.
- Network Adminstrator Response:
- Contact NRS Technical Support.
- TND0093S
- Invalid VSAM record length
- Explanation:
- An attempt was made to operate with a record length that is invalid.
- System Action:
- The operation is not completed properly.
- Operator Response:
- None.
- Network Adminstrator Response:
- Contact NRS Technical Support.
- TND0094I
- Invalid INQUIRE request [numeric value] - rejected
- Explanation:
- Network Director has issued an
internal VTAM INQUIRE and it is not in the proper format.
- System Action:
- The internal request is rejected.
- Operator Response:
- None.
- Network Adminstrator Response:
- Contact NRS Technical Support.
- TND0095C
- The VTAM ACB failed to [operation]
- Explanation:
- A major operation (OPEN or CLOSE) failed against the VTAM ACB.
- System Action:
- The status of the External File is unchanged.
- Operator Response:
- None.
- Network Adminstrator Response:
- Locate the related return codes and feedback
values to evaluate the reason for the error.
- TND0096S
- Insufficient virtual storage to accomplish OPEN
- Explanation:
- The VTAM ACB could not be opened due to a
shortage of virtual storage.
- System Action:
- The ACB remains closed.
- Operator Response:
- None.
- Network Adminstrator Response:
- Increase the amount of storage available to Network Director.
- TND0097C
- Invalid VTAM PASSWORD specified - check GLOBALS PASSWORD=
- Explanation:
- The VTAM ACB open failed because of an invalid PASSWORD.
- System Action:
- The ACB remains closed. Termination may occur as dictated by the
TERMINATE operand.
- Operator Response:
- None.
- Network Adminstrator Response:
- Supply the proper password on the GLOBALS PASSWORD operand.
- TND0098S
- VTAM has not been generated into this system
- Explanation:
- The VTAM ACB OPEN failed because you do
not have VTAM generated within your operating system.
- System Action:
- The External File will not be available.
- Operator Response:
- None.
- Network Adminstrator Response:
- Network Director requires VTAM to utilize the External File facilities.
- TND0099C
- VTAM is terminating - GLOBALS
TERMINATE= controls the DIRECTOR
- Explanation:
- VTAM is not executing normally and the
OPEN can not be successfully processed. This may also
occur in DOS systems where Network Director is running at a higher
priority than VTAM.
- System Action:
- Network Director will not be able to initialize.
- Operator Response:
- None.
- Network Adminstrator Response:
- Investigate the problem with VTAM.
- TND0100C
- APPLID [APPL name] is not defined to VTAM or is
currently deactivated
- Explanation:
- The VTAM APPL definitions do not contain a definition for Network Director
that matches the APPLID specification on the GLOBALS statement.
- System Action:
- Network Director will respond as required by the TERMINATE operand.
- Operator Response:
- None.
- Network Adminstrator Response:
- Create or activate the VTAMLST entry for Network Director with ACF/VTAM.
- TND0101C
- GLOBALS APPLID= [appl name]
does not define a VTAM APPL
- Explanation:
- There is no entry in the VTAM Definitions for Network Director.
- System Action:
- Network Director responds as dictated by the TERMINATE operand.
- Operator Response:
- None.
- Network Adminstrator Response:
- Provide an ACF/VTAM APPL major node definition for Network Director to use.
- TND0102S
- APPLID [appl name]
is currently being used by another application
- Explanation:
- The value provided on the GLOBALS APPLID
operand has also been assigned to another VTAM
subsystem. It is not possible for Network Director to
share the definition at the same time.
- System Action:
- Network Director cannot communicate with terminals and will respond as
instructed via the TERMINATE operand.
- Operator Response:
- None.
- Network Adminstrator Response:
- Assign an individual definition for Network Director.
- TND0103S
- The VTAM ACB is already CLOSED
- Explanation:
- An attempt was made to CLOSE the VTAM ACB and it is already CLOSED.
- System Action:
- None, the ACB is already closed.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0104G
- At CLOSE, there are unreceived operator commands queued
- Explanation:
- Network Director's Program Operator
facility had commands queued for it when the ACB was CLOSED.
- System Action:
- Termination continues as dictated by the TERMINATE operand.
- Operator Response:
- None.
- Network Adminstrator Response:
- Informational only.
- TND0105S
- Some terminals were not disconnected, VTAM error
- Explanation:
- VTAM was not successful at disconnecting one or more terminals.
- System Action:
- Processing continues.
- Operator Response:
- None.
- Network Adminstrator Response:
- Investigate VTAM errors.
- TND0106I
- Invalid execute form on VTAM manipulative macro
- Explanation:
- Network Director violated a general rule for VTAM manipulative macros.
- System Action:
- Network Director will attempt to continue to process.
- Operator Response:
- None.
- Network Adminstrator Response:
- Contact NRS Technical Support.
- TND0107G
- A VTAM manipulative macro"s parameter list is corrupted
- Explanation:
- A parameter list used by VTAM to manipulate control blocks
has been modified.
- System Action:
- Processing continues.
- Operator Response:
- None.
- Network Adminstrator Response:
- Contact NRS Technical Support.
- TND0108I
- Attempted to modify or interrogate a field that is
nonexistent
- Explanation:
- A MODCB or SHOWCB request specified an invalid field.
- System Action:
- The current DFB will fail, but general processing continues.
- Operator Response:
- None.
- Network Adminstrator Response:
- Contact NRS Technical Support.
- TND0109G
- Insufficient storage to manipulate the control block
- Explanation:
- A virtual storage shortage has occurred during VTAM processing.
- System Action:
- The current operation will not complete normally.
- Operator Response:
- None.
- Network Adminstrator Response:
- Increase the virtual storage available to Network Director.
- TND0110I
- Attempted to modify an active VTAM RPL
- Explanation:
- Network Director attempted to utilize a Control Block that was already in use.
- System Action:
- The current activity will fail.
- Operator Response:
- None.
- Network Adminstrator Response:
- Contact NRS Technical Support.
- TND0111I
- Invalid VTAM work area alignment
- Explanation:
- A VTAM work area is not on a proper boundary.
- System Action:
- The current operation will fail
- Operator Response:
- None.
- Network Adminstrator Response:
- Contact NRS Technical Support.
- TND0112S
- DOS EXEC statement is missing the SIZE operand
- Explanation:
- DOS VTAM requires that the SIZE operand be present on the JOB card.
- System Action:
- VTAM functions cannot be performed correctly.
- Operator Response:
- None.
- Network Adminstrator Response:
- Provide the SIZE operand as instructed in
the appropriate VTAM manuals.
- TND0113S
- Invalid attempt to execute in DOS REAL mode
- Explanation:
- DOS VTAM does not allow the partition to be REAL.
- System Action:
- Network Director will terminate.
- Operator Response:
- None.
- Network Adminstrator Response:
- Do not execute Network Director in REAL mode.
- TND0114S
- SIZE operand value is too small
- Explanation:
- The SIZE operand specified is not sufficient for VTAM.
- System Action:
- Network Director cannot operate normally.
- Operator Response:
- None.
- Network Adminstrator Response:
- Increase the value specified and restart Network Director.
- TND0115S
- Message [name] will now expire at
[time] on [date]
- Explanation:
- The terminal operator extended the expiration of the identified
message to the new time and date.
- System Action:
- The message will now expire at the new time and date.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0116C
- Sense: X"[hex byte]" Modifier:. X"
[hex byte]" User:X"[hex bytes]" LU:.
[luname]
- Explanation:
- Network Director has received the identified Sense code from the named LU.
- System Action:
- Dependent upon the sense code and session status.
Network Director will attempt to interpret the
Sense meaning with further interpretive messages.
- Operator Response:
- None.
- Network Adminstrator Response:
- Interpret the sense codes by looking them up in the appropriate
Messages and Codes or SNA Reference Summary
manual.
- TND0117S
- The Logical Unit is not available
- Explanation:
- This interpretive message indicates that
the LU involved in the last VTAM request is currently
not defined or is inactive within the network. This may
occur when defining an APPLICATION with an invalid TARGET.
- System Action:
- No action is taken.
- Operator Response:
- None.
- Network Adminstrator Response:
- The error may not be serious. Evaluate the
reason for the not available status.
- TND0118S
- RVI received from BI-SYNC device [luname]
- Explanation:
- An unexpected RVI was received from the
device indicated in replacement value 1.
- System Action:
- Network Director will retry the operation.
- Operator Response:
- None.
- Network Adminstrator Response:
- Validate that the device is properly operational.
- TND0119S
- BI-SYNC device [luname] sent SENSE information
- Explanation:
- Network Director received sense information from the
device identified in replacement value 1.
- System Action:
- Dependent upon the sense code values.
- Operator Response:
- None.
- Network Adminstrator Response:
- Investigate the sense code meanings.
- TND0120S
- Temporary storage shortage or resource is unavailable
- Explanation:
- VTAM could not process the request due to a storage shortage.
- System Action:
- The request will be retried.
- Operator Response:
- None.
- Network Adminstrator Response:
- Check VTAM's buffer usage conditions if the problem persists.
This can also indicate difficulties in cross domain links.
- TND0121S
- Device [luname] error lock set -
reset required
- Explanation:
- A device has been set into the error lock
condition and requires a reset.
- System Action:
- Network Director waits for a change in the device.
- Operator Response:
- Place the device into an operational status.
- Network Adminstrator Response:
- None.
- TND0122S
- [luname] is not usable or powered off
- Explanation:
- The device specified with replacement
text 1 is not available because it has been turned off
or otherwise removed from availability.
- System Action:
- Network Director waits for the device to become operational.
- Operator Response:
- Power on or make the device operational.
- Network Adminstrator Response:
- None.
- TND0123S
- Test Request received from [luname]
- Explanation:
- VTAM received a TEST REQUEST from the device.
- System Action:
- The last screen is rewritten.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0124S
- Device [luname] is being deactivated
- Explanation:
- The device will no longer be available as a network element.
- System Action:
- None.
- Operator Response:
- None.
- Network Adminstrator Response:
- Activate the device when ready.
- TND0125S
- Contention on line with terminal [luname]
- Explanation:
- There is heavy usage of the line the
connects to the terminal specified in replacement text 1.
- System Action:
- The system continues to service all requests delivered properly.
- Operator Response:
- None.
- Network Adminstrator Response:
- Investigate performance of the identified line.
- TND0126S
- VTAM/NCP are incompatible
- Explanation:
- The software versions of the NCP and VTAM are incompatible.
- System Action:
- Operation continues, but may not be proper.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the situation and retry.
- TND0127G
- Permanent channel or link failure - [luname]
has been lost
- Explanation:
- The identified device has been lost due to
a failure associated with a VTAM link or channel failure.
- System Action:
- The device will not operate properly.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the link failure.
- TND0128S
- NCP has shut down - [luname] lost
- Explanation:
- Because the NCP has terminated, the identified device has been lost.
- System Action:
- Any users logged on will be logged off of the corresponding device.
- Operator Response:
- None.
- Network Adminstrator Response:
- Restart the NCP.
- TND0129S
- Start Data Traffic (SDT) failed to [luname]
- Explanation:
- During OPNDST the VTAM SDT has failed.
- System Action:
- The device is placed on the Inactive List.
- Operator Response:
- None.
- Network Adminstrator Response:
- No activity can occur between the device and
Network Director. Correct the problems associated with the failed SDT and retry.
- TND0130S
- Data traffic is not allowed - SDT not issued
- Explanation:
- An attempt to initiate output has failed
because there has not been a SDT command issued yet.
- System Action:
- The current output is discarded.
- Operator Response:
- None.
- Network Adminstrator Response:
- This is probably related to TND0129.
Correct the problem associated with the failed SDT.
- TND0131S
- Invalid LU or APPL name for INQUIRE
- Explanation:
- Network Director issued INQUIRE for an invalid LU or APPL name.
- System Action:
- The LU or APPLICATION is identified as unusable.
- Operator Response:
- None.
- Network Adminstrator Response:
- This can legitimately occur if a TARGET
operand of an APPLICATION statement specifies an
invalid APPL value (undefined to VTAM).
- TND0132S
- CLSDST PASS isn"t authorized - The Director
requires it
- Explanation:
- Network Director attempted to forward
ownership of a terminal to another VTAM application and
discovered that the authorization to pass ownership has
not been assigned to Network Director with the VTAM APPL statement.
- System Action:
- The requested session will not be started.
- Operator Response:
- Contact the Network Administrator.
- Network Adminstrator Response:
- To enable this facility within
Network Director you should insure that the AUTH operand of the
VTAM APPL statement includes the PASS attribute.
- TND0133S
- Network Director is not authorized for SEND/RCVCMD
- Explanation:
- Network Director attempted to SEND a
command to VTAM and discovered that it has not been
authorized for Program Operator activities.
- System Action:
- VTAM Operator command will not be processed.
- Operator Response:
- None.
- Network Adminstrator Response:
- If you would like to utilize the Program
Operator facilities within Network Director
(VTAMOPER) you must provide the SPO attribute on the
VTAM APPL definition statement.
- TND0134S
- Syntax error in Operator reply
- Explanation:
- The reply sent to VTAM in response to a prompt was not in the
proper format.
- System Action:
- None.
- Operator Response:
- Issue the reply with the correct syntax.
- Network Adminstrator Response:
- None.
- TND0135S
- SEND/RCVCMD processor is inactive
- Explanation:
- VTAM cannot process any Program Operator
commands because its command processor is not available.
- System Action:
- VTAM operator commands will not operate properly
- Operator Response:
- None.
- Network Adminstrator Response:
- Enable the facility within VTAM.
- TND0136S
- The VTAM operator command is invalid
- Explanation:
- The command issued via the Program
Operator facility is not recognized by VTAM.
- System Action:
- None.
- Operator Response:
- Correct the syntax and retry the command.
- Network Adminstrator Response:
- None.
- TND0137G
- This option is not available yet
- Explanation:
- You have issued a request that is defined
within Network Director, but not yet implemented.
- System Action:
- The current request is ignored.
- Operator Response:
- Make use of documented facilities only.
- Network Adminstrator Response:
- Contact North Ridge Software, Inc. if you are interested in
option availability.
- TND0138G
- [statement] [name] cannot be located
- Explanation:
- The named control block could not be
located during DISPLAY or dynamic deck modification.
- System Action:
- The DISPLAY request is terminated.
- Operator Response:
- Check that you have specified the control
block identifier correctly.
- Network Adminstrator Response:
- None.
- TND0139S
- Unauthorized access by system console - contact the Network Administrator
- Explanation:
- The console operator has attempted to
access Network Director and it is not authorized to do so.
- System Action:
- The request is rejected.
- Operator Response:
- Contact the Network Administrator.
- Network Adminstrator Response:
- If the user should have console access,
allocate a TERMINAL named OPERATOR and provide an
APPLICATIONS= operand exactly as you would for another
terminal.
VM installations using SMSG will require a TERMINAL definition that
matches the issuing machine's virtual name.
- TND0140C
- LOSTERM entered with [numeric value]
reason code for NIB [luname]
- Explanation:
- The terminal named in replacement value 2
was lost due to the reason code displayed as replacement value 1.
- System Action:
- The session is terminated via a CLSDST. Network Director will queue a
request for the device (SIMLOGON).
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0141G
- Contact with the TERMINAL has been lost (VARY OFF, etc)
- Explanation:
- The terminal named in associated message
TND0140G was lost because of a VARY OFF type activity.
- System Action:
- The session is broken.
- Operator Response:
- None.
- Network Adminstrator Response:
- Investigate why the device was varied offline.
- TND0142G
- An unconditional TERMINATE SELF was received
- Explanation:
- The device named by TND0140G issued a TERMINATE SELF sequence.
- System Action:
- A CLSDST (UNBIND) operation is executed.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0143G
- Contact with the LU may be recoverable
- Explanation:
- The device caused LOSTERM to be driven,
but the LU may be recoverable and usable.
- System Action:
- Network Director will attempt to restart the session.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0144G
- Conditional TERMINATE SELF
- Explanation:
- The device is attempting to terminate the connection.
- System Action:
- The request is rejected by Network Director.
- Operator Response:
- None.
- Network Adminstrator Response:
- Investigate why the device or its operator
were attempting to terminate the connection.
- TND0145G
- TEST REQUEST received from local non-SNA device
- Explanation:
- The device named in the TND0140G message struck the TEST REQUEST key.
- System Action:
- A simulated CLEAR key is executed.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0146C
- Closing VTAM ACB
- Explanation:
- Issued by the dispatcher whenever Network Director is closing the VTAM ACB.
- System Action:
- CLOSE is issued against the VTAM ACB.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0147G
- [DFB name] primed for ABEND during quick termination
- Explanation:
- A STOP IMMEDIATE command was received and
Network Director is about to ABEND the named DFB to expedite termination.
- System Action:
- Termination continues.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0148G
- DFB [name] is abnormally terminating
- Explanation:
- The dispatcher is abnormally terminating the named DFB.
- System Action:
- The DFB is detached and associated resources freed.
- Operator Response:
- None.
- Network Adminstrator Response:
- During normal processing any DFB ABEND
should be considered a loss of service within the
network. This will normally cause a device to enter an
inactive state. The device should still be usable by
striking the RESET - CLEAR keys
or the SNA ATTN (SIGNAL) key. DFB abnormal termination will occur
"normally" as a result of a disrupting network connection (LOSTERM,
RELREQ, etc.).
- TND0149T
- The [name] DFB is terminating
- Explanation:
- This message is issued whenever a DFB has
reached termination point and the TRACE is on.
- System Action:
- None, dispatching continues.
- Operator Response:
- None.
- Network Adminstrator Response:
- None, DFB terminations of this type will
occur constantly within a single execution of Network Director.
- TND0150C
- Terminal [luname], device type x"
[hex byte]" is an unsupported device type
- Explanation:
- Network Director cannot currently
support the device type named in the second replacement
value and identified with the LU name identified in the
first replacement value.
- System Action:
- The device has no output scheduled to it.
- Operator Response:
- None.
- Network Adminstrator Response:
- Determine the device type and verify that the BIND image matches.
- TND0151G
- The value [text string]
is not a valid command for the Editor
- Explanation:
- During an attempt at modifying the
default PFKEY assignments on a PROFILE screen the
terminal operator provided a command name that is not
currently known to Network Director.
- System Action:
- The PFKEY setting will not be effective.
- Operator Response:
- Correct the value specified and strike enter.
- Network Adminstrator Response:
- None.
- TND0152S
- Unauthorized attempt to VIEW the PROFILE at [luname]
by [network element]
- Explanation:
- The network element identified by the
replacement text values attempted to look at the
contents of the PROFILE and was not authorized to do so.
- System Action:
- The PROFILE request is not honored.
- Operator Response:
- None.
- Network Adminstrator Response:
- This should be considered a security
violation unless the Network Administrator should have
authorized the VIEW operation via the PROFILE operand.
- TND0153S
- TERMINAL [luname] has an unsupported line size
of [numeric value]
- Explanation:
- A terminal has attempted connection to Network Director and its
presentation space line size specifies a value other than 80 or 132.
- System Action:
- No output transmission will be scheduled.
- Operator Response:
- None.
- Network Adminstrator Response:
- Network Director does not currently support devices with
the displayed line size.
- TND0154I
- Invalid attribute [hex byte]
encountered for [luname]
- Explanation:
- Network Director was translating logical attributes to actual
attributes and encountered an invalid value.
- System Action:
- No output transmission will be scheduled.
- Operator Response:
- None.
- Network Adminstrator Response:
- This represents an internal logic error. Contact NRS Technical Support.
- TND0155I
- TERMINAL [luname] input field is not located
in logical buffer
- Explanation:
- The DFB is using the logical buffer
mapping facility and a field present in the physical
input stream could not be located in the logical
buffer.
- System Action:
- Processing continues, but the input may not have been processed.
- Operator Response:
- None.
- Network Adminstrator Response:
- Contact NRS Technical Support.
- TND0156I
- An input field from [luname]
is larger than its receiving logical field
- Explanation:
- A DFB using logical buffer mapping
received a field larger than it was prepared to accept.
- System Action:
- The field is truncated.
- Operator Response:
- None.
- Network Adminstrator Response:
- Contact NRS Technical Support.
- TND0157I
- Unidentifiable field in ID area of terminal [luname]
- Explanation:
- An input field present in the data stream
was in the ID area of the screen and was not one of the
current Network Director fields.
- System Action:
- The input is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Contact NRS Technical Support.
- TND0158S
- RECEIVE-ANY DFB (INPUT) terminating due to VTAM
termination
- Explanation:
- VTAM has presented INPUT with feedback
indicating its termination and the INPUT DFB is
terminating itself.
- System Action:
- The INPUT DFB will terminate.
- Operator Response:
- None.
- Network Adminstrator Response:
- None. Network Director will attach
the INPUT DFBs when the VTAM ACB is opened again.
- TND0159C
- NSI is not enabled
- Explanation:
- The RECEIVE-ANY RPL was satisfied with an
input from NSI and NSI should not be transmitting any
data because NSI=NO is in effect.
- System Action:
- The NSI request will be rejected.
- Operator Response:
- None.
- Network Adminstrator Response:
- Set NSI=YES if Network Director should process requests originating from the
NSI.
- TND0160I
- Data received from an unidentified NIB, ARG [session id]
, LU [luname]
- Explanation:
- Data was received from a device without a matching ANE allocated.
- System Action:
- Network Director will attempt to locate the NIB for the device using the
luname. If it cannot, the data is rejected and the RECEIVE-ANY
is placed back up.
- Operator Response:
- None.
- Network Adminstrator Response:
- Contact NRS Technical Support.
- TND0161S
- Input arrived for [luname]
before prior input was processed
- Explanation:
- INPUT received from the device named as
replacement value 1 arrived before its prior input was
successfully processed.
- System Action:
- The input just received will be discarded.
- Operator Response:
- Wait for response to previous input.
- Network Adminstrator Response:
- This is typically caused by the terminal operator striking
RESET and another AID key.
- TND0162R
- Errors in the operator command prohibit execution
- Explanation:
- One or more errors were encountered
during the parsing of a operator command. The errors
prohibited proper execution of the request.
- System Action:
- The request has not been processed.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the syntax or the request and try it again.
- TND0163C
- [DFB name] has been scheduled for abnormal termination
- Explanation:
- The named DFB will be abended as a result
of an operator CANCEL command or an internal forced termination.
- System Action:
- The identified DFB will be terminated.
- Operator Response:
- None.
- Network Adminstrator Response:
- RELEASE the terminal to restore the initial Director
screen.
- TND0164S
- TERMINAL [luname] is now active
- Explanation:
- The device named in replacement value 1
is now active as a network element.
- System Action:
- The default output screen is sent to the device.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0165S
- Id [id] - [user name] is now active at
[luname]
- Explanation:
- The USER named in replacement value 1 is
now active at the identified device.
- System Action:
- An updated selection screen will be sent to the user.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0166S
- Id [id] - [user name] has logged off of
[luname]
- Explanation:
- The USER named in replacement value 1 is
no longer active at the identified device.
- System Action:
- The network element is no longer associated with the user.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0167G
- Input from Locked device [luname]
has been ignored
- Explanation:
- The named LU provided input to Network Director
at the same time that Network Director was
attempting to write to the device. This may occur on
remote devices when Network Director is attempting to
accomplish an unsolicited write (Status update or
Broadcast message) at the same time as the terminal
operator is pressing a function key.
- System Action:
- The input is ignored.
- Operator Response:
- Make your request again when the keyboard is freed.
- Network Adminstrator Response:
- None.
- TND0168S
- Security Violation - [id]
attempted to use TERMINAL [luname]
- Explanation:
- The USER or GROUP named as replacement
value 1 has attempted to use the TERMINAL named as
replacement value 2 and is not authorized to do so.
- System Action:
- Network Director will count this attempt
as one of the TRIES at the named TERMINAL.
- Operator Response:
- Correct your spelling of the userid and/or password.
- Network Adminstrator Response:
- Check that the user accessing the system is properly authorized.
- TND0169S
- Security Violation - attempt to use TERMINAL
[luname] was rejected
- Explanation:
- A TERMINAL named as replacement value 1
was attempting to access the network and it is not
authorized to do so.
- System Action:
- The access attempt is rejected.
- Operator Response:
- Use a different device.
- Network Adminstrator Response:
- The attempt has been rejected and counted
against any outstanding TRIES counter.
- TND0170S
- Userid [id] at TERMINAL [luname]
is out of authorized time intervals
- Explanation:
- The network element identified was
attempting to utilize the network and the associated
TIME and/or DAY parameters did not authorize the use.
- System Action:
- The access attempt is rejected.
- Operator Response:
- Wait until the proper time of day to use the system.
- Network Adminstrator Response:
- The attempt has been rejected and counted as
one of the TRIES.
- TND0171S
- USER [id] is not authorized to use TERMINAL
[luname]
- Explanation:
- The USER identified by replacement value
1 has not been authorized by the TERMINAL USERS=
statement to utilize the TERMINAL named by replacement value 2.
- System Action:
- The user's signon attempt is rejected.
- Operator Response:
- Use an authorized terminal.
- Network Adminstrator Response:
- Investigate the security violation.
- TND0172S
- GROUP [name] at TERMINAL [luname]
is out of authorized time intervals
- Explanation:
- The identified GROUP at the identified
TERMINAL has violated its related TIME and DAY specifications.
- System Action:
- The access attempt is rejected.
- Operator Response:
- Use the system only at authorized intervals.
- Network Adminstrator Response:
- Investigate the security violation.
- TND0173S
- GROUP [name] is not authorized to use TERMINAL
[luname]
- Explanation:
- The GROUP identified by replacement value
1 has not been authorized by the TERMINAL USERS=
statement to utilize the TERMINAL named by replacement value 2.
- System Action:
- Access is rejected.
- Operator Response:
- Use an authorized terminal only.
- Network Adminstrator Response:
- Investigate the security violation.
- TND0174S
- Logon at TERMINAL [luname] failed - attempt
[numeric value]
- Explanation:
- A network element at the TERMINAL named
unsuccessfully identified itself.
- System Action:
- The logon attempt has been rejected.
- Operator Response:
- Correct why the logon has failed.
This is typically caused by the network user
not knowing the proper ID or PASSWORD.
- Network Adminstrator Response:
- None.
- TND0175S
- TERMINAL [luname] was placed on the inactive
list due to Security violations
- Explanation:
- The named device exceeded its associated
TRIES counter (the consecutive number of times logon can be attempted)
or the system security package has revoked/suspended the userid.
- System Action:
- The device is placed on the Inactive List for Security Reasons.
- Operator Response:
- Contact the Network Administrator.
- Network Adminstrator Response:
- Investigate who was attempting to utilize the device.
Issue the RELEASE NET= command to reactivate the device.
- TND0176G
- Input received from [luname] on Inactive List was
ignored
- Explanation:
- The VTAM RECEIVE-ANY DFB (INPUT) received
data from a device that was on the inactive list.
- System Action:
- The input is discarded.
- Operator Response:
- Contact the Network Administrator.
- Network Adminstrator Response:
- If the device should
be active, remove the device from the Inactive List
via a RELEASE NETWORK-ELEMENT=xxxx Administrator command.
- TND0177G
- This [network element]
([name]) is already defined
- Explanation:
- The named element has been defined twice.
- System Action:
- The second definition is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the inconsistency and try it again.
- TND0178G
- The SELECTIONS operand is invalid
- Explanation:
- An invalid value was provided for the SELECTIONS operand.
- System Action:
- The operand is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the specification.
- TND0179G
- The [operand] operand is not supported for this
Operating System
- Explanation:
- You have attempted to activate an operand that is not supported for
the operating system specified on GLOBALS OPSYS=.
- System Action:
- The operand is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Make sure the OPSYS= value is set correctly. Contact North Ridge Software, Inc. for more
information about the specific function and its availability for your
operating system.
- TND0180S
- USER [id] attempted logon at USER=NO device
[luname]
- Explanation:
- The USER identified attempted to use the
device named as replacement value 2 and it is not
authorized for USER access.
- System Action:
- The logon attempt is rejected.
- Operator Response:
- You cannot logon to the device you are using.
- Network Adminstrator Response:
- Investigate the security violation.
- TND0181C
- Rplexit already in use for [luname] - the
SIMLOGON has been bypassed
- Explanation:
- An attempt to issue a SIMLOGON for a device has failed due to
a prior usage of the RPLEXIT logic within Network Director.
- System Action:
- The SIMLOGON is not issued.
- Operator Response:
- None.
- Network Adminstrator Response:
- Contact NRS Technical Support.
- TND0182G
- Operand value truncated to [numeric value]
characters
- Explanation:
- A value provided for an operand exceeded
the maximum allowable number of characters.
- System Action:
- The operand is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the specification and issue the command again.
- TND0183G
- The SSI operand must be specified YES, NO, or EXTENDED
- Explanation:
- The value provided for the SSI operand was not acceptable.
- System Action:
- The operand is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the specification and issue the command statement again.
- TND0184G
- [text string]
is an unidentified command or application
- Explanation:
- The entry on the Command line did not
identify an authorized application and was not one of
Network Director's internal commands.
- System Action:
- The command is ignored.
- Operator Response:
- Correct the request and try it again.
- Network Adminstrator Response:
- None.
- TND0185G
- Too many selections were chosen via modified field
technique
- Explanation:
- You have modified two or more fields on the Selection
Screen and Network Director did not know which one you intended to select.
- System Action:
- The selection screen remains on your terminal.
- Operator Response:
- Make your selection again.
- Network Adminstrator Response:
- None.
- TND0186G
- Please make your selection from one of the displayed
choices
- Explanation:
- You attempted to use the Cursor Placement
technique to make a selection, but the cursor was not
in a valid position or Network Director could not
identify the type of selection request you intended.
- System Action:
- The selection screen remains on your terminal.
- Operator Response:
- Position the cursor and try again.
- Network Adminstrator Response:
- None.
- TND0187G
- Modified field received did not identify a valid selection
- Explanation:
- The input stream contained an input field
that Network Director could not identify.
- System Action:
- The input is ignored.
- Operator Response:
- Network Director will restore the last screen.
- Network Adminstrator Response:
- None.
- TND0188G
- Please select one of the displayed choices
- Explanation:
- Network Director did not detect an attempt to make a selection.
- System Action:
- The selection screen remains on the terminal.
- Operator Response:
- Utilize one of the facilities provided to make a selection.
- Network Adminstrator Response:
- None.
- TND0189G
- Application [name] is not currently available
- Explanation:
- You have attempted to select an
application that is not currently accepting terminal sessions.
- System Action:
- The selection cannot be made at this time.
- Operator Response:
- Make another selection or wait for the
desired application to become available.
- Network Adminstrator Response:
- None.
- TND0190G
- You are not authorized to Delete message [name]
- Explanation:
- An attempt was made to delete a message that the user
did not own or was not the only destination for (a Group,
Application, or Wild Characters would cause this).
- System Action:
- The delete request is ignored.
- Operator Response:
- Only the originator of the message can delete it.
- Network Adminstrator Response:
- None.
- TND0191I
- Page overflow displaying Primary Message Menu
- Explanation:
- Network Director could not collect all
the messages you are currently associated with
into your Message Index. The capacity of the MIX is set as a function
of the MX pool size (set via the GLOBALS STORAGE-POOLS operand).
- System Action:
- Network Director will display those that will fit into the MIX.
- Operator Response:
- Reduce the number of messages you are
involved with by deleting some.
- Network Adminstrator Response:
- If appropriate, increase the capacity of the MIX by increasing
the size of the MX storage pool (i.e. doubling the MX pool size will
double the capacity of the MIX).
- TND0192G
- Invalid Message Action Code [character] was
used
- Explanation:
- The named Action Code is not a valid Message Action Code.
- System Action:
- The action is ignored.
- Operator Response:
- Correct the Action Code and strike the ENTER key.
- Network Adminstrator Response:
- None.
- TND0193I
- The input data field is not recognizable
- Explanation:
- Network Director could not identify the input data field that it received.
- System Action:
- The input may not be processed correctly.
- Operator Response:
- Make your request again modifying the proper fields.
- Network Adminstrator Response:
- None.
- TND0194G
- Please set the Name, To, and Type fields (Site optional)
- Explanation:
- You attempted to edit a new message from the
Message panel, but neglected to properly fill in the required fields.
- System Action:
- The request is ignored.
- Operator Response:
- Fill in the required fields by tabbing to the appropriate fields.
- Network Adminstrator Response:
- None.
- TND0195G
- The required fields with invalid values prohibit
execution
- Explanation:
- Network Director cannot continue
execution because one or more required fields have not
successfully had their values specified.
- System Action:
- The request is bypassed.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the errors and restart Network Director.
- TND0196C
- [network element] [name] is now active
- Explanation:
- The named application or site target system is
now active and accepting work.
- System Action:
- The network application or node is now available for use.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0197C
- [network element] [name] is down
- Explanation:
- The named application or site is no longer
available for selection.
- System Action:
- The application or site is marked unavailable.
- Operator Response:
- Wait for it to come back up to make it
eligible for use.
- Network Adminstrator Response:
- None.
- TND0198C
- Application [name] is in the Wait condition
- Explanation:
- The named application is up, but it is
not currently accepting logons.
- System Action:
- The APPLICATION status is updated on appropriate screens.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0199C
- Control is being given to [name]
(Version [version number] )
- Explanation:
- Initialization is complete and normal
dispatching is about to begin. Terminals will now be
capable of connection to Network Director.
- System Action:
- Network Director will OPEN the VTAM ACB and accept terminal sessions.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0200G
- The ending time must be greater than the starting time
- Explanation:
- A TIME specification expressed an ending
time for a time interval that was less than the starting time.
- System Action:
- The specification is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the specification.
- TND0201G
- ------------ Parameter Deck scan complete --------------
- Explanation:
- Network Director has successfully processed the initial
Configuration Parameters.
- System Action:
- Initialization will continue.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0202S
- [luname] released due to VTAM Release Request
- Explanation:
- The named LU has been released because
another VTAM application subsystem requested the device.
- System Action:
- Network Director will CLSDST the device.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0203G
- The internal function of [name]
is not available - it has been HELD
- Explanation:
- You defined one of Network Director's
internal functions that is not yet implemented.
- System Action:
- It has been placed into a HELD status and
will not be available for Selection.
- Operator Response:
- Select another activity.
- Network Adminstrator Response:
- None.
- TND0204G
- ----------- Parameter Deck Scan Beginning -------------
- Explanation:
- Network Director is about to begin
the processing of the initialization Configuration Parameters.
- System Action:
- Initialization proceeds.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0205S
- Unauthorized Password entered at [luname]
by USER [id]
- Explanation:
- The USER named in replacement value 2
attempted to logon to the system using an incorrect password.
- System Action:
- The access attempt is rejected.
The attempt will count against any outstanding TRIES parameter.
- Operator Response:
- None.
- Network Adminstrator Response:
- Investigate the possible security violation.
- TND0206G
- [character string]
- Explanation:
- This message is reserved for use in installation exit points
where your installation may desire to issue a message to you that
is included in the LOG file.
- System Action:
- The response should be determined by the individual that
has designed and implemented the exit that issued the message.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0207S
- Activity not allowed for Message
[name] at [luname]
- Explanation:
- A network element attempted to operate on
a Message in a manner that is not authorized
(Initiating a Broadcast message when not permitted is
an example).
- System Action:
- The request is rejected.
- Operator Response:
- Perform any authorized activity.
- Network Adminstrator Response:
- None.
- TND0208G
- Operator Services HELD - CONSOLE=NO in effect
- Explanation:
- You have specified the option that disables communications
with the main console. The internal function that normally
handles the operator's console has been disabled.
- System Action:
- The OPER DFB will not be operational.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0209G
- Opening the VTAM ACB
- Explanation:
- Network Director is about to open the VTAM ACB that will identify it to VTAM.
- System Action:
- The OPEN is performed.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0210G
- The VTAM ACB is already OPEN
- Explanation:
- An attempt has been made to OPEN the VTAM
ACB when it was already open.
- System Action:
- The OPEN attempt is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0211C
- TERMINATE AUTO requests termination (VTAM ACB is
closed)
- Explanation:
- Network Director has closed the VTAM
ACB and is about to terminate execution based upon the
setting of the GLOBALS TERMINATE operand.
- System Action:
- Network Director exits the operating system.
- Operator Response:
- None.
- Network Adminstrator Response:
- Set GLOBALS TERMINATE=OPERATOR or TERMINATE=RETRY if you would
like Network Director to remain active during VTAM restarts.
- TND0212I
- Manipulative VTAM Macro error
- Explanation:
- An internal macro manipulation error has occurred.
- System Action:
- The internally requested function will not be performed.
- Operator Response:
- None.
- Network Adminstrator Response:
- Contact NRS Technical Support.
- TND0213C
- R15:[dec] X('[hex]') RTNCD:.
[dec] X('[hex]') FDBK2:
[dec] X('[hex]') for [luname] [macro type]
- Explanation:
- A VTAM non zero return code has occurred
during the execution of the request for the identified device.
- System Action:
- The response is a function of the RPL return codes.
- Operator Response:
- None.
- Network Adminstrator Response:
- Refer to other related messages for
additional information describing the error in detail.
The ACF/VTAM Programming manual contains a more detailed
description of the return code meanings.
- TND0214C
- TARGET [applid] for APPLICATION
[name] is undefined to VTAM
- Explanation:
- The value provided as the TARGET= operand
(replacement value 1) for the APPLICATION named as
replacement value 2 is not currently defined to VTAM.
- System Action:
- The APPLICATION will be placed into a HELD
status.
- Operator Response:
- None.
- Network Adminstrator Response:
- You should correct the specification and RELEASE the APPLICATION.
- TND0215S
- Logical Unit [luname] not found
- Explanation:
- The LU named as replacement value 1 is unknown to VTAM.
- System Action:
- The operation cannot be performed by VTAM.
- Operator Response:
- None.
- Network Adminstrator Response:
- This is simply an interpretation of a VTAM
RPL based error typically associated with an
incorrectly identified APPLICATION TARGET.
- TND0216I
- NIB missing for device [luname]
- Explanation:
- Network Director was attempting to
locate a NIB for the specified device and was unable to
locate it within the partition/address space.
- System Action:
- The RU being processed will be ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Contact NRS Technical Support.
- TND0217G
- Establishing session for [luname] -
Subarea: [subarea number] Netid:. [netid]
- Explanation:
- The identified device has established a session with Network Director for the
first time during this execution of Network Director.
- System Action:
- Session establishment continues.
- Operator Response:
- None.
- Network Adminstrator Response:
- None, this message in informational.
- TND0218C
- [control block] definition for [identifier]
has been deleted
- Explanation:
- You issued a D ((Delete) prefix command against the identified
control block from the SHOW processor's menu.
- System Action:
- The control block has been eliminated from Network Director's control blocks.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0219G
- LU [luname] is an unsupported LU type
- Explanation:
- Network Director supports only LUs
processing with LU type 0, 1, 2, 3, and 6.
- System Action:
- The device is rejected by Network Director
- Operator Response:
- None.
- Network Adminstrator Response:
- Verify that the BIND image properly reflects the device.
- TND0220G
- Your attempt to logon is not currently valid
- Explanation:
- The terminal operator has probably not provided a
valid combination of ID area fields to allow access to
occur. This is the message issued to the terminal
operator regardless of the exact reason his logon has
failed.
- System Action:
- The access attempt is rejected.
- Operator Response:
- Correct the contents of the fields in the ID area and press ENTER.
- Network Adminstrator Response:
- Additional information about why the logon
failed is present in the log.
- TND0221I
- The MONITOR value is invalid
- Explanation:
- An invalid value has been specified on the MONITOR operand.
- System Action:
- The value is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the specification to a valid MONITOR value of
YES, NO, or DOWN.
- TND0222G
- ID-AREA must be specified as YES or NO - default
unchanged
- Explanation:
- You have provided an invalid value for the ID-AREA= operand.
- System Action:
- The specification is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the specification.
- TND0223G
- ACQUIREd TERMINALs may not be specified with wild
characters
- Explanation:
- The ACQUIRE=YES operand was utilized on a
TERMINAL statement whose name contained one or more wild characters.
Network Director must be able to specifically
identify the TERMINAL to VTAM in order to support the
ACQUIRE operand.
- System Action:
- The ACQUIRE=YES specification is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the specification to eliminate the wild characters if the
ACQUIRE=YES operand is required.
- TND0224R
- Operator input: [input character string]
- Explanation:
- Network Director received the text
specified in replacement value 1 from the operator's
console (OS STOP/MODIFY, DOS MSG facility, or VM SMSG facility).
- System Action:
- The input request will be processed.
- Operator Response:
- Wait for the response.
- Network Adminstrator Response:
- None.
- TND0225C
- APPLICATION [name] with TARGET
[applid] is not defined to VTAM
- Explanation:
- The named APPLICATION with the specified
TARGET has been placed into a HOLD status because VTAM
does not have a definition for the TARGET value.
- System Action:
- The APPLICATION is HELD
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the TARGET specification and RELEASE the APPLICATION.
- TND0226C
- [DFB name] terminating because of VTAM errors
- Explanation:
- The named network element's DFB is
terminating because of the previous VTAM errors.
- System Action:
- DFB termination continues.
- Operator Response:
- None.
- Network Adminstrator Response:
- Identify the cause of the problem and RELEASE the network element.
- TND0227G
- Lu [luname] - [id] - [user name]
has selected [application name]
- Explanation:
- The named network element was forwarded
to the named TARGET after a successful selection was made.
- System Action:
- The device is CLSDST PASSed to the subsystem.
- Operator Response:
- You may now continue work in the subsystem of your choice.
- Network Adminstrator Response:
- None.
- TND0228C
- Closing VSAM ACB
- Explanation:
- The External File is about to be CLOSED.
- System Action:
- CLOSE will be issued against the VSAM ACB.
- Operator Response:
- None.
- Network Adminstrator Response:
- The facilities associated with the External
File may not be fully available after CLOSE.
- TND0229G
- The VSAM ACB is already OPEN
- Explanation:
- An attempt was made to OPEN the External File and
it was already open.
- System Action:
- The OPEN request is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0230G
- OPENing the VSAM ACB
- Explanation:
- The External File is about to be opened.
- System Action:
- OPEN is issued against the VSAM ACB.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0231G
- The Network Element will be logged off
- Explanation:
- The LU requested a conditional terminate and logoff has been
scheduled.
- System Action:
- Network Director is internally logging the Network Element off.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0232S
- NSI session from [applid] has been rejected
- Explanation:
- The named NSI user has had a session
rejected by Network Director. This is typically because NSI=NO is in effect.
- System Action:
- The session is rejected.
- Operator Response:
- None.
- Network Adminstrator Response:
- Modify the NSI operand if NSI should be active.
- TND0233G
- Message [name] is not associated with
[network element]
- Explanation:
- While Deleting the named message for the
named network element, DELE could not locate the message.
- System Action:
- The delete request is ignored.
- Operator Response:
- If the message is still displayed on the menu, contact the Network Administrator.
- Network Adminstrator Response:
- Issue the DISPLAY MESSAGES command to see if the message exists.
If it does not and continues to appear on the messages menu,
contact NRS.
- TND0234G
- Blank parameter image ignored
- Explanation:
- The parameter processor received a
statement image that contained no statements or operands.
- System Action:
- The statement is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Place an asterisk "*" in the first column of comments.
- TND0235G
- [text string] is not a valid AUTHORIZATION operand
- Explanation:
- The value specified must be one of the valid Network Director statements.
- System Action:
- The operand is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct or eliminate the AUTHORIZATION value.
- TND0236C
- This device has been disabled - contact the Network Administrator
- Explanation:
- The device has been placed onto the
Inactive List due to the user at the device exceeding
the TRIES value attempting to identify himself (logon)
or the system security package has revoked/suspended the userid.
See the discussion under TND0807 for additional information.
- System Action:
- The device will no longer be usable by the device operator.
- Operator Response:
- Contact the Network Administrator.
- Network Adminstrator Response:
- The terminal may be activated by the
RELEASE NETWORK-ELEMENT=xxxxx Administrator Command.
- TND0237S
- Logons exceeded, logged on at
[luname list]
- Explanation:
- You attempted to logon to a terminal with
a userid that was already in use at
more than the maximum number of devices.
- System Action:
- Your attempt to logon is rejected.
- Operator Response:
- Use another Id or logoff
at another terminal
prior to attempting to use the one you are at.
- Network Adminstrator Response:
- If the user should be capable of logging on to additional
devices, set the MAXIMUM operand to a larger value.
- TND0238C
- [luname] - [id] has disconnected
- Explanation:
- The identified network element has issued the
DISConnect or DROP command from the Command Line.
- System Action:
- The session is terminated (CLSDST).
- Operator Response:
- Use USS commands to communicate with ACF/VTAM.
- Network Adminstrator Response:
- None.
- TND0239G
- Command line commands must begin in position 1
- Explanation:
- You modified the command line, but did not
begin the modification in position one of the command line.
- System Action:
- The command is ignored.
- Operator Response:
- Issue the command from position 1.
- Network Adminstrator Response:
- None.
- TND0240G
- MSGID must be specified as YES or NO
- Explanation:
- The GLOBALS MSGID operand must be either YES or NO.
- System Action:
- The operand is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the operand's value and issue the command again.
- TND0241G
- SYNTAX-SCAN must be specified as YES or NO
- Explanation:
- The GLOBALS SYNTAX-SCAN operand must be either YES or NO.
- System Action:
- The value specified is ignored.
- Operator Response:
- Correct the operand's value and issue the command again.
- Network Adminstrator Response:
- None.
- TND0242G
- The EXTENSION operand is no longer supported on the
PROFILE statement
- Explanation:
- The Extension operand is invalid on the PROFILE statement.
- System Action:
- The operand is ignored.
- Operator Response:
- Remove the operand from the definition.
- Network Adminstrator Response:
- None.
- TND0243G
- SYNTAX-SCAN complete - termination underway
- Explanation:
- You specified SYNTAX-SCAN=YES and Network Director
has completed the scan of the Configuration Parameters.
- System Action:
- Termination will occur.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0244D
- INQUIRE for [target] being issued for
[type]
- Explanation:
- Network Director is about to query the status of the identified ACF/VTAM
target (APPLICATION or SITE).
- System Action:
- The INQUIRE will be issued.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0245G
- The NEW-PASSWORD value must be YES, NO, VERIFY or
VALIDATE
- Explanation:
- You have specified the NEW-PSWD operand on the GLOBALS statement
and the provided value is invalid.
- System Action:
- The specification is ignored.
- Operator Response:
- None.
- Network Adminstrator Response:
- Correct the specification to one of the available values and
try again.
- TND0246G
- The New Password and Verify values do not match
- Explanation:
- You have attempted to set a new password, but you did not
type exactly the same value in the Verify: field of the ID area.
- System Action:
- The new password setting is not accepted.
- Operator Response:
- You must enter the identical values into the New Password and
Verify fields in addition to
retyping your password in the Password field.
- Network Adminstrator Response:
- None.
- TND0247G
- This is an unsupported combination of Display operands
- Explanation:
- You issued a Combined Display request
with a combination of operands that are not currently supported.
- System Action:
- The DISPLAY request is rejected.
- Operator Response:
- Correct the DISPLAY statement and issue it again.
- Network Adminstrator Response:
- None.
- TND0248G
- Log buffer trace initiated
- Explanation:
- The internal LOG manager has just
activated the logging facility associated with the LOGSIZE parameter.
- System Action:
- All Network Director issued messages will now be collected into the LOG queue
(as indicated via the LOG parameter).
- Operator Response:
- None.
- Network Adminstrator Response:
- None. Entries in the LOG may be displayed
from an authorized Administrator's terminal.
- TND0249G
- Input: [input character string]
- Explanation:
- The input character string was entered from an authorized
Network Administrator (may be via the console, from SMSG, etc.).
- System Action:
- The command will be parsed and executed, as necessary.
- Operator Response:
- None. Network Director's response to the input will be placed into the LOG
and returned to the requesting location (as necessary).
- Network Adminstrator Response:
- None.
- TND0250G
- [network element] [name] has been defined
- Explanation:
- The named network entity has been
established within Network Director's control blocks.
- System Action:
- The control block has been generated
dynamically and now may be utilized.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0251G
- [network element] [name] change(s) have been processed
- Explanation:
- The named network entity has had one or more changes processed.
- System Action:
- The requested modifications have been processed into the appropriate
control blocks.
- Operator Response:
- None.
- Network Adminstrator Response:
- The changes are immediately available for
usage within the network.
- TND0252C
- The PARM's GLOBALS operand(s) have been set
- Explanation:
- The operating system parameters specified on the PARM=
operand have been processed.
- System Action:
- The values will now apply to Network Director execution.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0253G
- The LOG is already enabled - the LOGSIZE operand has
been ignored
- Explanation:
- A Network Administrator attempted to modify or activate the LOG buffer.
- System Action:
- Network Director has ignored the request.
Honoring the request would cause loss of all the
current LOG data.
- Operator Response:
- None.
- Network Adminstrator Response:
- The LOGSIZE will become effective with the next Network Director initialization.
- TND0254G
- [network element] [name]
- Explanation:
- Issued to provide a general identifier
for a control block that has been requested via a
Specific Display request made with the DISPLAY statement.
- System Action:
- The rest of the related information will immediately follow in
the LOG.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0255G
- TARGET=[applid1] [applid2]
- Explanation:
- Describes the value(s) present on a
APPLICATION statement for the TARGET operand.
- System Action:
- None.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0256G
- INITIAL-FUNCTION=[data string]
- Explanation:
- Is the first function that will be performed in the target subsystem.
- System Action:
- None.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0257G
- [numeric value] Terminals and [numeric value]
Users currently connected
- Explanation:
- Identifies the number of terminals and
users currently connected to a particular subsystem.
- System Action:
- None.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0258G
- Application [name] - Target [applid]
is [status]
- Explanation:
- Is the response to a DISPLAY APPLICATIONS
request and shows the names and current status of all
defined applications.
- System Action:
- One line per defined APPLICATION is displayed.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0259G
- Profile [name]
- Explanation:
- Provides the leading entry for a DISPLAY PROFILE request.
- System Action:
- None. Remaining operands will follow this message in the LOG.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0260G
- Group [name] currently has [numeric value]
users
- Explanation:
- Displays the number of network elements
currently associated with a specific GROUP definition.
- System Action:
- None.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0261G
- Terminal [luname] Extension [value]
currently has [numeric value] active
- Explanation:
- Displays the number of network elements
currently associated with a specific TERMINAL
definition.
- System Action:
- None.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0262G
- DFB [name] is [status] at
[offset] in [CSECT name]
priority [value]
- Explanation:
- Is the response to the DISPLAY DFBS
request. Each executing DFB is identified by
replacement text 1 and its general status in replacement value 2.
- System Action:
- None.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0263G
- User [name] Extension [value]
currently has [numeric value] active
- Explanation:
- Identifies the number of network elements
currently associated with the named USER definition.
- System Action:
- None.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0264G
- GLOBALS APPLID=[applid]
- Explanation:
- Is the first message in response to a
DISPLAY GLOBALS request. Replacement text 1 is the
current value associated with the VTAM APPLID.
- System Action:
- None.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0265G
- BROADCAST-AREA=[numeric value]
- Explanation:
- Displays the current size of the Broadcast Area (in lines).
- System Action:
- None.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0266G
- [operand]=([storage media],[expiration value]).
- Explanation:
- Identifies the general characteristics
for one of the message types (MEMO, NOTE, or
BROADCAST). Replacement text 1 identifies the message
type, replacement text 2 is the storage medium (DISK or
STORAGE), and replacement text 3 is the duration for
timed expiration in seconds.
- System Action:
- None.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0267G
- CONSOLE=[value]
- Explanation:
- Displays whether the operating system
console interface is enabled (YES) or not (NO).
- System Action:
- None.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0268G
- LINE-COUNT=[numeric value]
- Explanation:
- Displays the current maximum lines per
page Network Director will place on the output printer log.
- System Action:
- None.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0269G
- LOG=[value]
- Explanation:
- Displays the current setting of the LOG
value. Messages with a message class equal to or less
than this value will be placed into the LOG and will be
available for viewing via Network Administration.
- System Action:
- None.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0270G
- LOGSIZE=[numeric value]
- Explanation:
- Displays the current value of the number
of bytes allocated to contain the storage LOG.
- System Action:
- None.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0271G
- NAME=[character string]
- Explanation:
- Is the text that will be used in the
upper left hand corner of all Network Director screens with the
short title present.
- System Action:
- None.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0272G
- NSI=[value]
- Explanation:
- Describes whether the NSI interface is enabled (YES)
or disabled (NO).
- System Action:
- None.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0273G
- OPSYS=[value]
- Explanation:
- Identifies the Operating System that Network Director is executing in.
- System Action:
- None.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0274G
- PASSWORD=[non displayable]
- Explanation:
- Displays the current value for the password.
- System Action:
- None.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0275G
- RPLS=[numeric value]
- Explanation:
- Is the number of RECEIVE-ANY RPLS that
Network Director will maintain to acquire input from the network.
- System Action:
- None.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0276G
- SECURITY=[value]
- Explanation:
- Identifies the installation's security
package to manage the passwords associated with network users.
- System Action:
- None.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0277G
- SMF=[SMF number]
- Explanation:
- Displays the current SMF record number
that Network Director will use to record statistical type information (OS only).
- System Action:
- None.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0278G
- TERMINATE=[value]
- Explanation:
- Identifies whether Network Director
will terminate when VTAM does (AUTO) or only when the
system operator indicates it should (OPERATOR or RETRY).
- System Action:
- None.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0279G
- TIMER=([min],[max])
- Explanation:
- Displays the current settings for the dispatcher's Wait cycles.
- System Action:
- None.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0280G
- TRACE=[numeric value]
- Explanation:
- Displays the current value in bytes of the internal trace buffer.
- System Action:
- None.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0281G
- VTAMOPER=[value]
- Explanation:
- Displays whether Network Director is honoring
VTAM operator commands from the Network Administration
screen (YES) or not (NO).
- System Action:
- None.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0282G
- TSSVM Div: [division] Dept:.
[department] Name: [name]
- Explanation:
- Displays the information extracted from TopSecret/VM about the network
element.
- System Action:
- None.
- Operator Response:
- None.
- Network Adminstrator Response:
- None.
- TND0283G
- VS