Explanation
This message is the first in a group of messages
that VTAM® issues after the
completion of a VARY ACT command when a BFSESSINFO request unit (RU)
is received during SSCP takeover processing. This message group indicates
that VTAM now owns two type
2.1 link stations in the direction of the same logical unit
luname for
one or more of the sessions described by the BFSESSINFO RU. A complete
description of the message group follows.
IST1419I DUPLICATE SESSION INFORMATION REPORTED FOR luname
IST1420I UNABLE TO ASSOCIATE THE FOLLOWING SESSION(S) WITH puname
IST873I PLU SLU SID STATUS
IST874I netid.pluname netid.sluname sessionid status
[IST874I netid.pluname netid.sluname sessionid status]
IST314I END
IST1419I - luname is the network-qualified name of the
independent logical unit.
IST1420I - puname is the name of the type 2.1 link station
(takeover physical unit) that is associated with the BFSESSINFO RU.
IST873I - This message is a header message for the information displayed
in message IST874I.
IST874I - pluname is the network-qualified primary session
partner name.
- sluname is the network-qualified secondary
session partner name.
- sessionid is the session identifier. For additional
information on the session, enter a DISPLAY SESSIONS,SID=sessionid command.
- status is the session status. See the z/OS Communications Server: IP and SNA Codes for a description of possible session initiation
and termination states.
Status modifiers will not display in the status field
of this message group. Enter a DISPLAY SESSIONS,SID=sessionid command
to obtain this information.
System action
Subsequent messages will be issued if errors
are encountered while processing the BFSESSINFO RU. If no errors are
encountered during BFSESSINFO RU processing, session states are not
changed. However, certain session and problem determination information
will not be available until the link that was taken over is given
back to the original owning SSCP.
Operator response
Save the system log for problem determination.
Since
certain session and problem determination information will not be
available until the link that was taken over is given back to the
original owning SSCP, information such as luname, puname,
and sessionids of the affected sessions should
be saved. This information may be useful if, for example, puname is
about to be deactivated because system information indicates that
no logical units are currently using it.
Entering a DISPLAY
command for
puname may not show all of the logical
units that are currently using the PU. Therefore, saving the information
in this message group will enable you to DISPLAY specific logical
units and/or sessions to determine whether the PU is currently in
use.
Notes: - When a DISPLAY ID=luname command is entered
with SCOPE=ALL, all sessions involving luname are
displayed. Sessions that use type 2.1 adjacent link stations are displayed
in groups, following message IST1081I indicating the adjacent link
station (PU) being used for those sessions.
However, sessions
that were listed in the IST1419I message group during an SSCP takeover
will not be displayed following message IST1081I for puname in
message IST1420I.
- When a DISPLAY ID=puname command is entered
with SCOPE=ALL, a list of logical units that are currently using that
PU are displayed following message IST355I.
However, some of the
logical units that are using puname may not be
displayed, if the only sessions using puname are
sessions that were displayed in the IST1419I message group during
an SSCP takeover.
For an explanation of SSCP takeover, see the z/OS Communications Server: SNA Network Implementation
Guide.
System programmer response
Routing code
Descriptor code