Explanation
VTAM® issues
this message when the command failed for the specified reason.
If
a network-qualified name was entered on the command line, VTAM issues nodename in
the form netid.name.
reason indicates
the cause of the failure and can be one of the following:
- ALSNAME NOT GIVEN
- A MODIFY TRACE,TYPE=GPT command was entered for nodename.
No ALSNAME was specified, and a default ALSNAME could not be determined
because of one of the following:
- The adjacent link station list for nodename contains
no entries.
- The adjacent link station list for nodename contains
two or more entries (other than ISTAPNPU).
- ALSNAME NOT VALID
- A MODIFY TRACE,TYPE=GPT command was entered for nodename.
The adjacent link station name (ALSNAME) that was either specified
or used by default was not in a valid state when the command was entered.
If ISTAPNPU was used by default because it was the only entry in the
adjacent link station list, then this is the reason the command failed.
ISTAPNPU is the name of the generic APPN adjacent link station. A
real adjacent link station name must be specified for the command
to succeed.
- ARM REJECTED
- A MODIFY TRACE command or TRACE start option was specified with
the value TYPE=QDIOSYNC. An Arm request was initiated and the reply
indicates that the OSA-Express2 or later adapter supports the QDIOSYNC
function, but an error occurred while attempting to arm the OSA-Express2
or later adapter.
- CDRSC IS DYNAMIC
- nodename is a dynamic cross-domain resource;
this is not valid for the TRACE command you entered.
- CDRSC NOT ACTIVE
- Giveback processing or internal delete for node nodename failed. VTAM found a predefined CDRSC to
be not active, and VTAM was
not able to transfer the active sessions from the LU to the CDRSC.
- CDRSC NOT ALLOCATED
- Giveback processing or internal delete for node nodename failed. VTAM has insufficient resources
to allocate a cross-domain resource or does not support a dynamic
CDRSC and was not able to transfer the active sessions from the LU
to a CDRSC.
- DEACTIVATE PENDING
- VTAM rejected a VARY INACT,
TYPE=GIVEBACK or VARY REL, TYPE=GIVEBACK command because a logical
unit subordinate to nodename has LU-LU sessions
and is pending deactivation.
- EXIT IS NOT FOUND
- The operator entered a DISPLAY EXIT command for a VTAM installation-wide exit which could not
be located.
- INSTALL EXIT REJECT
- The operator entered a MODIFY ENCR command for nodename,
and VTAM rejected the MODIFY ENCR
command because of user-written routines related to the GENKEY function.
- INSTALL PROGRAM
- A MODIFY ENCR command was entered for nodename and the cryptographic
facility is not supported by this host.
- ISTLSXCF NOT ACTIVE
- Another node in the sysplex attempts to establish a connection
with an XCF node, but the connection is not established because the
dynamic local SNA major node, ISTLSXCF, is not in an active state.
- ISTLSXCF NOT FOUND
- Another node in the sysplex attempts to establish a connection
with an XCF node, but the connection is not established because the
dynamic local SNA major node, ISTLSXCF, does not exist.
- ISTTRL NOT FOUND
- Another node in the sysplex attempts to establish a connection
with an XCF node, but the connection is not established because the
TRL major node, ISTTRL, does not exist.
- MACLNTH NOT VALID
- The operator entered a MODIFY SECURITY command with a MACLNTH
value that is not valid. The MACLNTH value is dependent on the most
recent specification of MACTYPE. The MACTYPE value might have been
specified on a MODIFY SECURITY command or on the APPL definition statement.
- MACTYPE NOT VALID
- The operator entered a MODIFY SECURITY command with a MACTYPE
value that is not valid with the most recent specification of MACLNTH.
The MACLNTH value might have been specified on a previous MODIFY SECURITY
command or on the APPL definition statement.
- MODEL LU NOT VALID
- The operator entered a DISPLAY LUGROUPS command for nodename.
Model LU nodename was not found in the LUGROUP
specified on the GROUP operand of the DISPLAY LUGROUPS command.
- MODULE LOAD FAILED
- Attempt to load XCF modules fails.
- MUST BE APPLICATION
- The operator entered a MODIFY ENCR command or MODIFY SECURITY
command for nodename for one of the following purposes:
- To set the encryption level to CONDITIONAL
- To set the values of MACLNTH or MACTYPE.
MACLNTH, MACTYPE, and the CONDITIONAL encryption level are
valid only if nodename is an application program.
- MUST BE MORE SECURE
- The operator entered a MODIFY ENCR command or MODIFY SECURITY
command for nodename to lower (make less secure)
the level of cryptographic session for the logical unit or application
program indicated by nodename. The level of cryptographic
session for a logical unit or application program can only be raised
(made more secure). For example, if you have defined an LU as selective,
you cannot modify it to optional. You can modify
it to required.
- NODE KEY UNDEFINED
- The operator entered a MODIFY ENCR command or a MODIFY SECURITY
command for nodename, and the node nodename does
not have a properly defined cryptographic key in the cryptographic
key data set.
- NOT SUPPORTED
- A MODIFY TRACE command or TRACE start option was specified with
the value TYPE=QDIOSYNC. When the OSA-Express2 or later adapter was
contacted, it was discovered that it does not support the QDIOSYNC
function.
- PROGRAM NOT ACTIVE
- The Cryptographic Facility is not available to process a MODIFY
ENCR command.
- RESOURCE NOT VALID
- The operator entered a MODIFY SECURITY command with the CKEY operand
for nodename, but nodename is
not a device type LU.
- RESOURCES NOT FOUND
- The operator entered a VARY ACQ or a VARY REL command, but it
had no effect on the NCP.
Either all the resources were acquired
or released already, or the OWNER specified on the command did not
match any of the owner names specified on the NCP's resources. Two
different networks cannot share the same native resources.
- RTP PU NOT VALID
- A VARY ACT command for an RTP PU is issued. This is a dynamic
PU and activates automatically if RTP is supported. A VARY ACT of
a RTP PU is invalid.
- SECURITY DATA ERROR
- VTAM detected a mismatch
of the encrypted security data fields during the XID exchange. This
mismatch may be caused by one of the following:
- An unauthorized subarea dial physical unit attempted to establish
a connection over a switched line.
- The PRTCT operand was absent.
- The correct password was not coded for both the caller and receiver.
- One of the subarea nodes is of a level that does not support call
security verification.
- SECURITY ERROR
- A security error occurred while VTAM was
processing the command command.
- STORAGE SHORTAGE
- The operator entered a MODIFY ENCR command for nodename and
the VTAM address space has
insufficient storage.
- SUPPORT UNAVAILABLE
- The security manager is not available or the resource class APPCLU
is not active.
- SYSPLEX JOIN FAILED
- VTAM is attempting to join
the sysplex, but a nonzero return code is sent from MVS™.
- SYSPLEX UNAVAILABLE
- VTAM is attempting to join
the sysplex, but the sysplex is not active.
- VTAM ABEND
- One of the following occurred:
- VTAM abended while processing
a MODIFY PROFILES command.
- VTAM abended while processing
a MODIFY ENCR command for nodename. The error may
be due to the improper cleanup of the cryptographic facility (that
is, the operator cancelled the cryptographic facility via the CANCEL
command).
- XCF BUILD FAILED
- A VARY ACT command fails for a dynamic local SNA major node.
- XCF PU NOT FOUND
- A D TRL,XCFCP=cp_name command was issued for nodename.
The nodename is the CP name specified in the display command. The
associated dynamic PU for that CP was not located.
- XCF TRLE NOT FOUND
- One of the following occurred:
- A D,TRL,XCFCP=cpname command was issued for nodename.
The nodename is the CP name specified in the display command. The
associated dynamic TRLE for that CP was not located.
- A V,NET,ACT,ID=ISTLSXCF command was issued. An XCF connection
is in the process of being deactivated and an activation request is
received. The dynamic TRLE which is required for activation does not
exist.
System action
The command is not completed. Processing continues.
- CDRSC IS DYNAMIC or CDRSC NOT ALLOCATED
- LU nodename remains known to VTAM in an inactive state with active sessions.
- FUNCTION NOT OPERATIONAL, NOT SUPPORTED, or ARM REJECTED
- The command is not executed.
- INSTALL PROGRAM
- Install Cryptographic Facility.
- SECURITY DATA ERROR
- VTAM terminates the switched
connection and deactivates the PU.
- SECURITY ERROR or SUPPORT UNAVAILABLE
- VTAM does not refresh the
profiles and continues to use the profiles that are in storage.
Operator response
The
reason determines
the response:
- ALSNAME NOT GIVEN
- Enter a DISPLAY ID command for nodename to
determine the correct adjacent link station, and reenter the command.
- ALSNAME NOT VALID
- Enter a DISPLAY ID command for nodename to
determine the correct adjacent link station, and reenter the command.
The state (active or inactive) of the PU with which the independent
LU is associated must be as follows:
- Active if it has been dynamically reconfigured in the NCP
- Active if it is on an NCP switched line
- Active or inactive if it is on an NCP nonswitched line.
- CDRSC IS DYNAMIC or CDRSC NOT ALLOCATED
- Activate a CDRSC major node that defines a CDRSC with nodename.
- DEACTIVATE PENDING
- Wait until all subordinate nodes have completed deactivation and
try the command again.
- ISTLSXCF NOT ACTIVE
- Enter a VARY,ACT,ID=ISTLSXCF to activate ISTLSXCF.
- MACLNTH NOT VALID
- Try the command again with a valid value for MACLNTH.
- MACTYPE NOT VALID
- Try the command again with a valid value for MACTYPE.
- MODEL LU NOT VALID
- Check that nodename is correct and try the
command again. If problems persist, save the system log for
problem determination.
- NOT SUPPORTED
- Issue the DISPLAY NET,TRL,TRLE=trlename command to display
the active OSA-Express2 or later TRLE. Look for message IST1716I or
message IST2263I in the response. The OSA CODE LEVEL field is at the
end of these messages. Record this value for the system programmer.
- PROGRAM NOT ACTIVE
- Make sure the Cryptographic Facility is installed and operational.
- RESOURCE NOT VALID
- Check that nodename is correct and try the
command again. If problems persist, save the system log for
problem determination.
- RESOURCES NOT FOUND
- Verify that all of the NCP resources have been acquired or released
or that the OWNER specified on the command matches the owner name
specified on the resources to be acted upon.
- SECURITY DATA ERROR
- Monitor the console for further occurrences of this message. If VTAM continues to issue this message,
use the VARY ANS command to take the line out of answer mode.
- SECURITY ERROR
- Try the command again. If VTAM continues
to issue this message, contact the security administrator.
- STORAGE SHORTAGE
- If VTAM continues to issue
this message, enter the DISPLAY BFRUSE command. Issue the DISPLAY
STORUSE command to display storage usage for storage pools. Save
the system log and request a dump for problem determination.
- VTAM ABEND
- Save the system log and dump for problem determination.
If
the error was due to the improper cleanup of the cryptographic facility,
enter the STOP command to stop the cryptographic facility, and save
the system log for problem determination.
- XCF PU NOT FOUND
- Check the CP name specified on the parameter XCFCP to ensure it
is correct and try the command again. Issue a DISPLAY TRL,CONTROL=XCF
to determine whether any XCF TRLEs exist. Issue a DISPLAY ID=ISTLSXCF
to determine whether an associated dynamic PU exists for the connection.
- XCF TRLE NOT FOUND
- Check the CP name specified on the parameter XCFCP to ensure it
is correct and try the command again. Issue a DISPLAY TRL,CONTROL=XCF
to determine whether any XCF TRLEs exist.
- All other reasons
- Save the system log for problem determination.
System programmer response
The
reason determines
the response:
- ARM REJECTED
- Perform the following traces to help you determine the cause of
the rejection:
- A CCW trace of the TRLE read and write control channels taken
at the time of the first attempt to arm the adapter. This trace will
show the Arm request being written and the Arm reply being read. Use
a CCW trace data length of 256 bytes.
- A CTRACE using the VTAM and
VTAMDATA options.
- A VTAM internal trace using
the CIA and CIO options.
- CDRSC IS DYNAMIC
- Reenter the TRACE command with a resource that is not a dynamic
cross-domain resource. You cannot trace a dynamic cross-domain resource.
- CDRSC NOT ALLOCATED
- Take VTAM down, and restart
it so that it supports dynamic CDRSCs.
- EXIT IS NOT FOUND
- Make sure the VTAM installation-wide
exit that could not be found has been installed on your system.
- INSTALL EXIT REJECT
- GENKEY failed with RETURN CODE 16 from the common cryptographic
architecture product (CCA) or the IBM® Cryptographic
Unit Support product (CUSP).
For further information, see the
documentation for the cryptographic facility that you are using.
- MODEL LU NOT VALID
- Check the definition of nodename to ensure
that it is correct.
- MUST BE APPLICATION
- Make sure nodename is the correct node name.
If nodename is the correct name, see z/OS Communications Server: SNA Operation for more information on valid encryption
levels. Otherwise, reenter the MODIFY ENCR command with the correct
value for nodename.
- MUST BE MORE SECURE
- If you want to lower the cryptographic session level of a node,
you must redefine the system definition cryptographic option in SYS1.VTAMLST
and reactivate the major node that contains nodename.
- NODE KEY UNDEFINED
- Define the cryptographic key for node nodename in
the cryptographic key data set. For information about defining cryptographic
keys, see the z/OS Cryptographic Services ICSF System Programmer's
Guide and the z/OS Communications Server: SNA Network Implementation
Guide.
- NOT SUPPORTED
- The OSA code level determined by the operator indicates the OSA
processor code level of the OSA-Express2 or later adapter. That value
will show that the OSA-Express2 or later processor code level is insufficient.
You must upgrade to a level that supports QDIOSYNC to use the function.
- SECURITY DATA ERROR
- Verify that all nodes involved in the dial process are at a level
that supports call security verification. The passwords used to verify
the identity of the caller and the receiver must match. See the PRTCT
keyword on the PU statement in the switched major node definition.
- STORAGE SHORTAGE
- If this error occurs often, review the VTAM storage allocation. Increase storage as
required.
- SYSPLEX JOIN FAILED
- Trace the return code from MVS.
Verify that the sysplex environment exists and restart VTAM.
- VTAM ABEND
- See the z/OS Communications Server: SNA Diagnosis Vol
1, Techniques and Procedures for information on the abend procedure. If
you cannot determine the cause of the problem from the output provided
or need additional assistance, contact the IBM software support center.
If the error
was due to the improper cleanup of the cryptographic facility, start
the cryptographic facility if it is not already started.
- XCF BUILD FAILED
- Restart VTAM with full
XCF support.
- XCF PU NOT FOUND
- Verify that XCF support is active for this VTAM.
- XCF TRLE NOT FOUND
- Verify that XCF support is active for this VTAM.
For all other reasons,
no further action is recommended.
Routing code
Descriptor code