IBM OS manual SPI commands, Wait commands

Page 85

v Lifetime can be PCONV, LOGON, SIGNON, ACTIVITY, PROCESS, SYSTEM, or

 

PERMANENT. The PROTECT option determines whether SYSTEM or

 

PERMANENT would be used. However, the Detector always worsens LOGON

 

and SIGNON to SYSTEM or PERMANENT, because of limitations in the way that

 

this affinity is detected.

The affinity relation for DELAY and POST may be GLOBAL, BAPPL, LUNAME,

 

or USERID.

v Lifetime can be only SYSTEM, PROCESS, ACTIVITY, or PCONV. If the affinity

 

relation is LUNAME or USERID, the lifetime must be PCONV because neither

 

DELAY nor POST exist beyond task termination.

 

v If the transaction speci®ed on a START or CANCEL command is de®ned as

 

remote, or a remote SYSID was speci®ed on the command so that the command

 

is function shipped to a remote CICS region, no data is collected. (It is not

 

possible to function ship POST or DELAY commands.)

 

v A CANCEL affinity is considered to be initiated from a terminal if the START,

 

DELAY or POST is initiated from a terminal. Whether the CANCEL was so

 

initiated or not is irrelevant.

 

Scanner differences: Scanner detects all instances of POST, all instances of DELAY

 

REQID, all instances of CANCEL REQID, and all instances of START that either

 

omit NOCHECK or specify REQID or specify TERMID (because of RETRIEVE

 

WAIT affinity).

 

SPI commands

 

v The commands included here are INQUIRE, SET, CREATE, DISCARD, ENABLE,

 

DISABLE, EXTRACT EXIT, COLLECT STATISTICS, PERFORM, and RESYNC.

v CBTS BROWSE COMMANDS are treated as inquire COMMANDS.

 

v The affinity here is not an affinity between transactions, but rather an affinity with

 

the system on which the command was issued; that is, a transaction-system

 

affinity. Such affinities do not generate transaction affinity groups, because it does

 

not generally make sense to dynamically route such transactions.

 

v The use of these commands does require reporting, however, because the

 

system programmer should be aware of the transactions and programs that issue

 

such commands.

 

Scanner differences: None.

WAIT commands

vThe affinity here is really an inter-transaction affinity between the issuer of the WAIT EVENT, WAIT EXTERNAL, or WAITCICS command, and one or more posters. However, the poster of the ECB(s) associated with the WAIT command cannot be detected, because this is not performed via the CICS API. Only half the affinity can be detected.

vThis means affinity transaction groups cannot be created, because the affinity degenerates to an affinity with the system on which the WAIT command was issued; that is, a transaction-system affinity.

vThe use of WAIT commands does require reporting, however, because the system programmer should be aware of the transactions and programs that issue such commands, and should attempt to locate the posters and so create the correct inter-transaction affinity groups.

Scanner differences: None.

Appendix A. Details of what is detected 69

Page 84 Page 86
Image 85
Page 84 Page 86
Contents IBM Page IBM Third edition March Contents Appendix A. Details of what is detected Reporter output Scanner output Examples Vi Cics Transaction Affinities Utility Guide Vii Trademarks Preface Argument zero Cics Transaction Server for OS/390 BibliographyCics books for Cics Transaction Server for OS/390 Other Cics books CICSPlex SM books for Cics Transaction Server for OS/390Summary of changes Xiv Cics Transaction Affinities Utility Guide Affinities, see the Cics Application Programming Guide Introducing transaction affinitiesRouting region Requesting regionTarget region What does dynamic routing cost? Benets of dynamic routingTransaction affinities Transaction-system affinity Inter-transaction affinityAffinity relations GlobalCics programming techniques for transaction affinity Affinity lifetimesUnsafe programming techniques Safe programming techniquesSuspect programming techniques Avoiding the effects of transaction affinityProtecting applications from one another What next? Important note Introducing the Transaction Affinities UtilityAffinity utility program components Commands detected by the Transaction Affinities Utility Detector component Scanner componentDetector components What is detectedWorsening of transaction affinities relations What is not detectedHow the affinity data is collected Controlling the DetectorSaving affinity data Control record Vsam le Affinity data Vsam lesReporter component Detector performanceBuilder component Report presenting the affinity data in a readable formIntroducing the Transaction Affinities Utility Cics Transaction Affinities Utility Guide Creating the Vsam les Preparing to use the affinity utility programEstimating the size of the MVS data space and Vsam les #termids Dening the Vsam les to CicsPreparing to use the affinity utility program Cics Transaction Affinities Utility Guide Creating a summary report Running the ScannerAffmod DD statement Cics Transaction Affinities Utility Creating a detailed reportContents of a detailed report Is an example of a detailed report produced by the Scanner Cics Transaction Affinities Utility Guide Changing the state Running the DetectorChanging the options CAFF01 Displaying the Detector control screenStarting the collection of affinity data When you can start collecting affinity dataWhen you can pause affinity data collection Pausing the collection of affinity dataWhen you can resume collecting affinity data Resuming the collection of affinity dataStopping the collection of affinity data When you can stop collecting affinity dataCAFF02 Changing the Detector options„1… The control options Perform periodic saves Restore data on startSize of dataspace „4… Last update by useridTransid prex „2… Detect affinity typesDetector errors Cics Transaction Affinities Utility Guide Requesting a report from the Reporter Running the ReporterCAUAFF1, CAUAFF2, and CAUAFF3 DD statements Caucntl DD statementsCmdgrps DD statement Output from the ReporterTrangrps DD statement System Affinity report„2… Affinity types reported „1… Incorrect affinity types„3… Affinities reports TrangroupCommand RecoverableAffinity LifetimeTerminal Producing affinity transaction group denitionsBTS Task Total TransactionsAfflifesystem Descaddress CWA Using the affinity reportModifying affinity transaction groups Understanding the affinitiesRemove false affinities Remove affinity relation worseningCompressing affinity data SPI commands Using the IBM Cross System ProductENQUEUEs/DEQUEUEs Shared storageENQUEUE/DEQUEUE Detailed affinity analysisGetmain Shared SPI commands Cics Transaction Affinities Utility Guide DSPSIZE=16number Running the BuilderCONTEXT=plexname Repgrps DD statement Syntax for input to the BuilderAffgrps DD statement Builder input syntax Output from the Builder Header statementsCombined affinity transaction group denitions Combining basic affinity transaction groups Relation a Relation B Resultant relation C Empty transaction groups report Data sets processed reportGroup merge report Sample group merge report Error reportSample error report Cics Transaction Affinities Utility Guide ENQ/DEQ Appendix A. Details of what is detected Load HOLD/RELEASE TS commandsAddress CWA CANCEL/DELAY/POST/START Wait commands SPI commandsCics Transaction Affinities Utility Guide Scanner output Reporter outputExamples Example 2±VS Cobol Which occurs for the rst Move Move Cobol affinities Logon or System when Pconv expectedUnrecognized Transids Cics Transaction Affinities Utility Guide Detector table manager diagnostics Appendix D. DiagnosticsFunction code values Table identier values Reason code values Date formatter diagnostics Detector Cafb request queue manager diagnosticsReason code values This sectionIndex Bappl Vsam Cics Transaction Affinities Utility Guide Sending your comments to IBM Ibmr IBM
Top Page Image Contents