Valid on z/OS and z/ VSE.
Use the TRANSACTIONS keyword to confine ACIDs to using a specific transaction, or subset of the transactions, available within that facility.
For purposes of LCF protection, facility entities USER77 through USER221 are not considered unique.
The TRANSACTIONS keyword is inclusive in that it confines an ACID to using specific transactions for a facility. See the XTRANSACTIONS keyword to determine how to allow an ACID to use all but a specific list of transactions for a facility.
This keyword has the following format:
TSS ADDTO(acid) TRANSACTIONS(facility,(transactions[(G)])
Specifies the facility.
Specifies the transaction, or subset of the transactions, available within a facility.
Size: 1 to 8 characters
Capacity: 1 to 30 transaction names or prefixes per command.
This keyword is used with:
This example confines a group of CICS clerks to a set of transactions:
TSS ADDTO(PROF1) TRANSACTIONS(CICSP,(CPO1,CPO2,CPO3))
The letter G next to the transaction prefix indicates that the ACID is confined to using transactions beginning with the prefix specified. The following command indicates that ACID EJ001 is confined to using transactions prefixed by CPO.
TSS ADDTO(EJ001) TRANSACTIONS(CICSP,(CPO(G)))
This example removes the TRANSACTIONS restriction:
TSS REMOVE(EJ001) TRANSACTIONS(CICSP,(CPO(G)))
For purposes of LCF protection, facility entities USER77 through USER221 are not considered unique. For example, if userxxx in the following command is chosen from USER77 through USER221, then the command will affect all facilities from USER77 through USER221.
TSS ADDTO(USER1)TRANSACTIONS(userxxx,(TRAN1))
If useryyy is a different facility chosen from USER77 through USER221, then both facilities userxxx and useryyy is affected by the LCF definition shown above or the definition shown next.
TSS ADDTO(USER1) TRANSACTIONS(useryyy,(TRAN2))
|
Copyright © 2009 CA Technologies.
All rights reserved.
|
|