Explanation
VTAM® issues
this message as part of a group of messages when a resource requests
a session, and the session initiation request fails for one of the
reasons listed below. The first message in the group is IST663I.
Message
IST664I, which is part of the IST663I message group, shows the names
of the partners for which a session could not be established.
The
combination of
resource and
reason may
be any of the following:
- ADJSSCP TABLE
- UNDEFINED
- COS NAME cosname
- UNDEFINED
- LOGMODE NAME logmode
- UNDEFINED
- RESOURCE luname
- UNDEFINED
- RESOURCE luname
- NOT ACTIVE
- RESOURCE luname
- UNSTABLE (device-type LUs only)
- RESOURCE luname
- DISABLED
- RESOURCE luname
- QUIESCING
- RESOURCE luname
- BLOCKING LOGONS (for application PLUs only)
- STORAGE
- NOT AVAILABLE
luname is displayed when
resource is
RESOURCE.
luname is
the real name of the LU or application that was in error. If the
SLU is not known,
***NA*** is displayed for
luname.
- If a network-qualified name was entered on the command line, VTAM issues luname as
a network-qualified name in the form netid.name.
- If luname is the SLU, the resource is undefined,
not active, disabled, or quiescing.
- If luname is the PLU, the resource is undefined,
not active, disabled, quiescing, or blocking logons.
- For cosname, no COS (Class of Service) entry
with that name has been defined. cosname is blank
if the default Class of Service was used.
- For logmode, the logon mode is not valid for
the SLU because:
- The logon mode is not in the logon mode table for the SLU in the VTAM definition statements.
- No logon mode table is associated with the SLU, and the logon
mode is not included in the default logon mode table.
- No valid logon mode table is associated with the SLU, and no default
logon mode table exists.
- If logmode is not provided or contains blanks,
IST264I is still issued. ***NA*** is displayed for logmode.
System action
VTAM rejects
the session initialization request. The session setup fails.
Operator response
Follow the appropriate action:
- If the required resource is UNDEFINED, enter a VARY ACT
command to activate the resource major node in which the resource
is defined.
- If the required resource is NOT ACTIVE, enter a VARY ACT
command to activate the resource. If the resource is an application
program, start it.
- If the required resource is UNSTABLE, it may be going through
some type of error recovery process. This can be due to ERP,
an INOP, or session termination. Display the resource and try
the request again after it has recovered.
- If the required resource is DISABLED and it is a device
type LU, check to determine whether it is powered on.
- If the required resource is DISABLED and it is an application
program, start the application program or ensure that the application
has issued SETLOGON START.
- If the required resource is an application program and is QUIESCING,
SETLOGON QUIESCE is in effect. The application program is shutting
down and cannot accept new sessions unless VTAM closes and reopens the ACB.
- If the required resource is an application program, and the ACB
was opened with MACRF=NLOGON, it is BLOCKING LOGONS. The only
LU-LU sessions allowed for the application program are those initiated
by the application program itself using OPNDST OPTCD=ACQUIRE.
- For a LOGMODE problem, verify that the resource specified
the correct logon mode on the request. You can use the DISPLAY ID
command to determine the table identified for the resource. You can
use the MODIFY TABLE command to change the logon mode table name associated
with a resource.
- If STORAGE is NOT AVAILABLE, wait a short time and
reenter the command. 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 dump for problem determination.
System programmer response
- For a COS problem, verify that you have defined the Class
of Service.
- For a LOGMODE problem, either correct the logon mode table
currently assigned to the SLU or assign a different logon mode table
that does contain the correct mode.
- For a STORAGE problem, allocate more storage to the pageable
system queue area (SQA). For insufficient storage errors, you might
want to redefine your buffer pool or CSA limits. If the start option
cannot be modified using the MODIFY VTAMOPTS command, you must modify
the VTAM start options file
(ATCSTRxx) and restart VTAM to use the start option.
Routing code
Descriptor code