Logging a Session Off
A particular session can be logged off by entering the following command transid:
where:
|
Syntax element . . . |
Is a . . . |
|
sessnum |
decimal number that identifies the session to be logged off. |
|
n |
digit (0 to 9). |
|
xxxx |
four‑character TDPID. |
The sequence of events is as follows:
1 The DLGF transaction logs off a session on the Teradata Database.
2 Uncommitted database changes are rolled back but DLGF does not terminate the CICS transaction or free any buffers or other storage associated with the transaction’s session.
3 The next time the transaction attempts to access the Teradata Database, the transaction is informed that the session no longer exists.
4 The Teradata session‑related storage, which is associated with the transaction, is released only when the transaction is terminated.
5 If more than one TDP is active and a particular TDP is identified, the session is logged off from that TDP.
6 Although each session number within each TDP is unique, several TDPs may have sessions that have the same session numbers, causing a possible conflict during logoff.
The TDPID resolves this ambiguity.
Note: The session number arguments for all transactions changed to decimal (from hexadecimal) in release 3.1 of this interface.