This message is part of a group of messages that VTAM® issues in response to a DISPLAY
CONVID command. A complete description of the message group follows.
IST1040I CONVERSATION(S) FOUND FOR applname
IST1007I PARTNER = partner, LOGMODE = logmode
IST1008I CONVID = convid, STATUS = status, ETIME = etime
IST2161I BLOCKED TIME = btime
IST1009I SID = sid, HPDT = hpdtvalue
IST924I ------------------------------------------------------------
IST1007I PARTNER = partner, LOGMODE = logmode
IST1008I CONVID = convid, STATUS = status, ETIME = etime
IST2161I BLOCKED TIME = btime
IST1009I SID = sid, HPDT = hpdtvalue
IST924I ------------------------------------------------------------
⋮
IST314I END
Message IST1040I provides the name
of the LU 6.2 application program, applname, specified
on the operator command. Messages IST1007I, IST1008I, IST2161I, and
IST1009I provide information concerning an individual conversation
with the LU 6.2 application program. Message IST924I is used as a
line separator to separate the different individual conversations
found for the LU 6.2 application program.
applname is
the name of the LU 6.2 application program specified in the operator
command.
partner is the name of the partner
LU for which DISPLAY information was requested.
logmode is
the logon mode name for which DISPLAY information was requested.
convid is
the conversation identifier for the specified application program
and its partner LU.
status is the status
of the conversation. Possible values are: If the
status value
ends with
/D, deallocation is pending for the conversation.
The
/D modifier applies to persistent sessions only. If the
status value
ends with
/B, the conversation is blocked due to session level
pacing. If the
status value ends with
/V,
the conversation is blocked due to virtual route pacing. If the status
ends with
/H, the conversation is blocked due to HPR backpressure.
- Status
- Meaning
- E_CONV
- Half-duplex end conversation; the conversation is being deallocated.
- F_SR
- Full-duplex send/receive; the application program is capable of
sending data to and receiving data from the partner LU.
- F_SO
- Full-duplex send only; the application program has received a
deallocation request from the partner LU. The application program
can send data to the partner LU and is expected to send a deallocation
request to end the conversation.
- F_RO
- Full-duplex receive only; the application program has sent a deallocation
request to the partner LU. The application program can receive data
from the partner LU and is expecting to receive a deallocation request
to end the conversation.
- FP_SR_L
- Full-duplex pending send/receive log; the application program
has received an error notification accompanied by error log data.
After the application receives the data, the conversation will return
to a SEND/RECEIVE state.
- FP_RO_L
- Full-duplex pending receive only log; the application program
has received an error notification accompanied by error log data.
After the application receives the data, the conversation will return
to a RECEIVE_ONLY state.
- FP_RS_L
- Full-duplex pending reset log; the end of the conversation is
pending receipt of error log data. After the application program receives
the error log data, the conversation will enter a RESET state.
- F_R_FM5
- Full-duplex receive FMH-5; the conversation is in a SEND/RECEIVE
state, but there is an FMH-5 waiting to be received. After the application
program receives the FMH-5, the conversation becomes usable.
- P_ALOC
- Pending allocation state; the application has reserved a session
and conversation, but an FMH-5 has not been processed on the conversation.
- P_DEAL
- Half-duplex pending deallocation; the application program is waiting
for the partner LU to confirm the receipt of data.
- P_E_LOG
- Half-duplex pending end conversation log; the end of the conversation
is pending the receipt of error log data.
- P_R_LOG
- Half-duplex pending receive log; the application program can receive
error log data that does not precede the end of the conversation.
- P_SEND
- Half-duplex pending send; the application program has received
data and the change direction command. The conversation will be placed
in SEND state following the acceptance of data and a subsequent SEND
operation.
- R_CFM
- Half-duplex receive confirmation; the application program is expected
to reply to a confirmation request.
- R_CFM_D
- Half-duplex receive confirmation deallocate; the application program
is expected to reply to a confirmation request that will also change
the state to deallocate.
- R_CFM_S
- Half-duplex receive confirmation send; the application program
is expected to reply to a confirmation request and has also received
a change direction command, implying that the application program
will be placed in a SEND state after the confirmation.
- R_FMH5
- Half-duplex receive FMH-5; the conversation is in a RECEIVE state,
but there is an FMH-5 waiting to be received. After the application
program receives the FMH-5, the conversation will become usable.
- RECEIVE
- Half-duplex receive; the application program is expecting information
from the partner LU.
- RESET
- Full-duplex or half-duplex reset; the conversation has been deallocated.
- SEND
- Half-duplex send; the application program is capable of sending
data to or requesting confirmation from the partner LU.
etime is the elapsed
time, in minutes, since the last API operation was performed on the
conversation. If the elapsed time is greater than 99999, the value
of etime is 99999.
btime is
the elapsed time, in minutes, since the conversation went into a blocked
state due to session level pacing, virtual route pacing, or HPR backpressure.
If the elapsed time is greater than 99999, the value of btime is 99999.
sid is
the session identifier for the conversation.
hpdtvalue will
be either YES or NO indicating whether high performance data transfer
(HPDT) services were available on the session, used by the conversation,
at the time the session was established.