IBM OS manual Using the IBM Cross System Product, ENQUEUEs/DEQUEUEs, Shared storage, SPI commands

Page 66

Using the IBM Cross System Product

The following information about the IBM Cross System Product (CSP) 4GL application generator concentrates on tests carried out running CSP 3.3, but in general the information also applies to later releases of CSP.

There are two components to CSP:

vCSP/AD (Application Development) is used to develop the applications

vCSP/AE (Application Environment) is the run-time environment for application execution.

If you use the IBM Cross System Product to develop your applications and, in particular, use CSP/AE as the run-time environment for the applications, the Reporter report will contain a large number of transaction groups. These groups are created because of the way that CSP/AE uses EXEC CICS commands, and in many cases do not cause real affinities.

Affinity analysis for a CICS region containing CSP 3.3 applications

When CSP 3.3 is used to develop and execute CICS pseudoconversational applications, the main CSP affinity is LUNAME/PCONV TS queue affinity, which can be dealt with either by CICSPlex SM or by a queue-owning region (QOR). The only other real affinity likely to be encountered is the use of non-read-only CSP shared tables, and the scope of this affinity depends on the tables and applications involved.

CSP internally uses these CICS resources and commands in the following ways. They can cause transaction affinities, and these appear in the Transaction Affinities Utility report.

ENQUEUEs/DEQUEUEs

are used to serialize the loading of CSP tables and applications from VSAM ®les called ALFs (application load ®les). They are also used to serialize writing messages to TD destination CSMT.

Shared storage

When a CSP application or table or map from an ALF has completed loading, it is copied to shared storage. Note that some of these tables may be de®ned by the application developer as SHARED and made resident by the CSP utility program ALFUTIL. Such tables may be shared between applications, and may be updated.

Temporary storage queues

CSP allows division of applications into 'segments'. This is just another name for a pseudoconversational application. CSP uses TS to save state data between transactions in the pseudoconversation, building the TS queue name from the termid to ensure uniqueness.

SPI commands

are used to inquire on system attributes such as the version and release of CICS in use, to set up and share a user exit global work area (GWA), and to obtain ®le characteristics of the ALFs.

50 CICS Transaction Affinities Utility Guide

Page 65 Page 67
Image 66
Page 65 Page 67
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 Bibliography Cics Transaction Server for OS/390Cics books for Cics Transaction Server for OS/390 CICSPlex SM books for Cics Transaction Server for OS/390 Other Cics booksSummary of changes Xiv Cics Transaction Affinities Utility Guide Introducing transaction affinities Affinities, see the Cics Application Programming GuideRequesting region Routing regionTarget region Benets of dynamic routing What does dynamic routing cost?Transaction affinities Affinity relations Inter-transaction affinityTransaction-system affinity GlobalAffinity lifetimes Cics programming techniques for transaction affinitySuspect programming techniques Safe programming techniquesUnsafe programming techniques Avoiding the effects of transaction affinityProtecting applications from one another What next? Introducing the Transaction Affinities Utility Important noteAffinity utility program components Commands detected by the Transaction Affinities Utility Scanner component Detector componentWhat is detected Detector componentsWhat is not detected Worsening of transaction affinities relationsControlling the Detector How the affinity data is collectedSaving affinity data Affinity data Vsam les Control record Vsam leBuilder component Detector performanceReporter component Report presenting the affinity data in a readable formIntroducing the Transaction Affinities Utility Cics Transaction Affinities Utility Guide Preparing to use the affinity utility program Creating the Vsam lesEstimating the size of the MVS data space and Vsam les Dening the Vsam les to Cics #termidsPreparing to use the affinity utility program Cics Transaction Affinities Utility Guide Running the Scanner Creating a summary reportAffmod DD statement Creating a detailed report Cics Transaction Affinities UtilityContents of a detailed report Is an example of a detailed report produced by the Scanner Cics Transaction Affinities Utility Guide Running the Detector Changing the stateChanging the options Displaying the Detector control screen CAFF01When you can start collecting affinity data Starting the collection of affinity dataWhen you can resume collecting affinity data Pausing the collection of affinity dataWhen you can pause affinity data collection Resuming the collection of affinity dataWhen you can stop collecting affinity data Stopping the collection of affinity dataChanging the Detector options CAFF02Restore data on start „1… The control options Perform periodic savesTransid prex „4… Last update by useridSize of dataspace „2… Detect affinity typesDetector errors Cics Transaction Affinities Utility Guide CAUAFF1, CAUAFF2, and CAUAFF3 DD statements Running the ReporterRequesting a report from the Reporter Caucntl DD statementsOutput from the Reporter Cmdgrps DD statementTrangrps DD statement Affinity report System„3… Affinities reports „1… Incorrect affinity types„2… Affinity types reported TrangroupAffinity RecoverableCommand LifetimeBTS Task Producing affinity transaction group denitionsTerminal Total Transactions Using the affinity report Afflifesystem Descaddress CWARemove false affinities Understanding the affinitiesModifying affinity transaction groups Remove affinity relation worseningCompressing affinity data ENQUEUEs/DEQUEUEs Using the IBM Cross System ProductSPI commands Shared storageDetailed affinity analysis ENQUEUE/DEQUEUEGetmain Shared SPI commands Cics Transaction Affinities Utility Guide Running the Builder DSPSIZE=16numberCONTEXT=plexname Syntax for input to the Builder Repgrps DD statementAffgrps DD statement Builder input syntax Header statements Output from the BuilderCombined affinity transaction group denitions Combining basic affinity transaction groups Relation a Relation B Resultant relation C Data sets processed report Empty transaction groups reportGroup merge report Error report Sample group merge reportSample error report Cics Transaction Affinities Utility Guide Appendix A. Details of what is detected ENQ/DEQTS commands Load HOLD/RELEASEAddress CWA CANCEL/DELAY/POST/START SPI commands Wait commandsCics Transaction Affinities Utility Guide Reporter output Scanner outputExamples Example 2±VS Cobol Which occurs for the rst Move Move Logon or System when Pconv expected Cobol affinitiesUnrecognized Transids Cics Transaction Affinities Utility Guide Appendix D. Diagnostics Detector table manager diagnosticsFunction code values Table identier values Reason code values Reason code values Detector Cafb request queue manager diagnosticsDate formatter diagnostics This sectionIndex Bappl Vsam Cics Transaction Affinities Utility Guide Sending your comments to IBM Ibmr IBM
Top Page Image Contents