SNAX/APC Configuration and Management Manual

SCF Commands for SNAX/APC
SNAX/APC Configuration and Management Manual—138787
8-7
ABORT TPI Command
•
A SESSION object can be aborted while it is in the STARTING state.
•
If all of a dynamic PTNR-LUs sessions are deactivated, the dynamic PTNR-LU and
all of its subordinate PTNR-MODEs will be removed from the local LU.
Examples
-> ASSUME PROCESS $APC1
-> ABORT SESSION LU01.CICSLU62.LU62BIND.013A
-> ASSUME PTNR-MODE $APC1.LU01.CICSLU62.LU62BIND
-> ABORT SESSION 013A
-> ABORT SESSION $APC1.LU01.CICSLU62.LU62BIND.013A
ABORT TPI Command
The ABORT TPI command stops the target transaction program instance and removes it
from the SNAX/APC process.
Considerations
•
The ABORT TPI command can only be issued when the target TPI object is in the
STARTING state.
•
You cannot use the SUB ONLY parameter with this command-object pair, because
you cannot abort subordinate conversations.
•
As a result of the ABORT TPI command, the received (queued) remote ATTACH
request is rejected with sense data %H084B6031 (Transaction Program Not
Available–Retry Allowed). This removes the CONV object (currently in the
STARTING state) from the SNAX/APC process.
•
When the ABORT TPI command stops the target transaction program instance and
deletes it from the SNAX/APC process, any outstanding TP-READY verbs are
returned with the following return code:
IPC-RETURN-CODE = RC-IPC-SERVICE-DENIED
IPC-RETURN-CODE-DETAIL = RC-TPI-ABORTED
Examples
-> ASSUME PROCESS $APC1
-> ABORT TPI LU01.ACCT.003A
-> ASSUME LU $APC1.LU01.ACCT
-> ABORT TPI 003A
-> ABORT TPI $APC1.LU01.ACCT.003A
ABORT TPN Command
The ABORT TPN command places the target TPN object in the STOPPED state and
inhibits its further use.