Filter
Top Products
CEMT SET CONNECTION
circumstances. It erases recovery information
and may compromise data integrity for units of
work that have updated resources on remote
systems.
Examples of circumstances in which you might need to
use it are:
You need to discard a connection, or issue a SET
CONNECTION ENDAFFINITY command, and it is
not possible for the quiesce protocols with the
partner system to be completed. (Neither action is
possible for an APPC connection if recovery data is
outstanding.)
An operational or logic error results in a logname
mismatch for the connection. The connection state
must be reset to allow the exchange lognames
process to complete.
Note: If you specify NORECOVDATA you cannot
specify COMMIT, BACKOUT, FORCEUOW,
RESYNC, or NOTPENDING.
NOTpending (
appc and cics-to-cics mro only
)
specifies, for either of the following kinds of connection,
that the normal resynchronization process is to be
overridden:
A connection to a CICS Transaction Server for
OS/390 partner that has performed an initial start
A connection to a pre-CICS Transaction Server for
OS/390 partner that has performed a cold start.
NOTPENDING forces all in-doubt units of work
(according to the transaction definition) that were created
by the connection before the initial (or cold) start of the
partner. It also forgets any resyncs (waitforget
UOW-links) that are outstanding for the connection, and
created before the initial (or cold) start of the partner.
The PENDING condition indicates the existence of
recovery information (either shunted UOWs or decisions
remembered for the partner) on a connection that has
experienced a lognames mismatch with its partner. For a
CICS Transaction Server for OS/390 partner, a
lognames mismatch indicates that the partner has
performed an initial start. For a pre-CICS Transaction
Server for OS/390 partner, a lognames mismatch
indicates that the partner has performed a cold start. In
either case, the recovery protocol has been corrupted by
a loss of log data at the partner.
It is not possible to set a connection to NOTPENDING
state (forcing in-doubt and erasing NOFORGET UOWs)
until this system has made contact with the partner and
received a new logname from it.
Decisions for a whole connection can be forgotten, but
that does not affect the memory of a decision for any
other connection involved in the UOW.
Notes:
1. If you specify NOTPENDING you cannot specify
COMMIT, BACKOUT, FORCEUOW, RESYNC, or
NORECOVDATA. For advice on which option to
use, see page 166.
2. NOTPENDING has no effect on MRO connections
to pre-CICS Transaction Server for OS/390
systems. However, the cold start of a pre-CICS
Transaction Server for OS/390 MRO partner causes
the SET CONNECTION NOTPENDING function to
be performed automatically, session by session.
The exchange lognames function and the
resynchronization function are described in the
CICS
Intercommunication Guide
and the
Systems Network
Architecture—LU6.2 Reference: Peer Protocols
manual.
OUtservice
The system is out of service; that is, it is not available
for use.
For an MRO connection, all sessions are placed out of
service (immediately if PURGE is specified, or when
tasks have terminated if it is not) and the following
occurs:
If the connection is currently ACQUIRED, the
sessions are broken (quiesced). The connection
cannot be used until it is once again placed
INSERVICE.
If the connection is currently RELEASED, the status
of the connection is set OUTSERVICE and it cannot
be used until it is INSERVICE again.
The status of the underlying sessions for a
connection is always the same as that for the
connection itself.
For an ISC system, the following occurs:
LU6.1 system—all underlying sessions owned by
the system are released and placed out of service:
immediately if PURGE or FORCEPURGE is
specified; or when tasks have terminated if neither
PURGE nor FORCEPURGE is specified.
If the response to an INQUIRE CONNECTION
command shows OUTSERVICE, it does not imply
that the connection has been explicitly set as SET
OUTSERVICE; in particular circumstances, you
cannot reinstall this connection.
APPC system—this option is valid only if the system
is released. All sessions owned by the ISC system
are then out of service and released.
PUrge (
vtam only and irc only
)
Transactions running on the connected system are
abnormally terminated. Transactions are terminated only
if system and data integrity can be maintained. A
transaction is not purged if its definition specifies
SPURGE=NO.
Chapter 11. Master terminal CEMT 165