IBM OS manual Cancel/Delay/Post/Start

Page 84

 

v The LOAD and FREEMAIN protocol applies only to programs de®ned as

 

RELOAD(YES). Note that HOLD is irrelevant, as CICS Program Control never

 

sees the FREEMAIN, or knows the storage location of the individual task's copy,

 

and so cannot release the program at task end. This implies that all LOADs must

 

be examined as they are all effectively LOAD HOLDs.

v The affinity relation may be GLOBAL, BAPPL, LUNAME, or USERID.

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

 

However, the Detector always worsens LOGON and SIGNON to SYSTEM,

 

because of limitations in the way that this affinity is detected.

 

v Commands in error are ignored, because there is no load address on which to

 

match LOAD with FREEMAIN, so no data is collected.

 

LOADs with no SET option are ignored, because no load address is returned, so

 

no data is collected.

 

v A LOAD/FREEMAIN affinity is considered to be initiated from a terminal if the

 

LOAD is initiated from a terminal. Whether the FREEMAIN was so initiated or not

 

is irrelevant.

 

v Any unmatched LOADs are also reported if they have never matched by the time

 

a Detector stop occurs. They are output in a separate report section. Note that

 

on a start with restore data, they are not restored and are deleted from the

 

affinity ®le.

 

Scanner differences: Scanner ®nds all instances of LOAD and all instances of

 

FREEMAIN.

CANCEL/DELAY/POST/START

v The affinity here is between the transaction that issues the DELAY, POST or START command and the transaction that issues the CANCEL command via REQID. The match is on REQID.

v In order for another task to CANCEL a DELAY, REQID must be explicitly speci®ed on the DELAY command. If no REQID is speci®ed on a DELAY command, it cannot be canceled, and therefore cannot be detected.

 

In order for another task to CANCEL a START or POST, it is not necessary to

 

specify REQID on the command because CICS supplies a unique REQID that

 

may be used (unless START speci®es NOCHECK). So only START commands

 

that do not both specify NOCHECK and omit REQID, and all POST commands,

 

are detected.

 

v Further, data is not collected for commands that expire on entry to Interval

 

Control, because they cannot be canceled (because an element control interval

 

(ICE) is not created). DELAY and POST commands get an EXPIRED response.

 

For START commands there is no such response; so 'expired on entry' is

 

deduced if INTERVAL(0) was speci®ed. This detects most 'expired on entry'

 

STARTs, but not all.

 

v START, DELAY, and POST commands in error are ignored, so no data is

 

collected.

 

v CANCEL commands that omit REQID are ignored because they cannot cancel

 

another task. CANCEL commands that return a NOTFND response are also

 

ignored because the ICE must have expired and the CANCEL must have failed.

 

No data is collected for these.

 

v REQIDs are assumed to be unique; that is, there are no simultaneous pairs of

 

START/CANCEL using the same REQID. Having such a pair violates CICS

 

programming guidelines, and the results from CICS are unpredictable.

v The affinity relation for START may be GLOBAL, BAPPL, LUNAME, or USERID.

68 CICS Transaction Affinities Utility Guide

Page 83 Page 85
Image 84
Page 83 Page 85
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 Inter-transaction affinity Transaction-system affinityAffinity relations GlobalAffinity lifetimes Cics programming techniques for transaction affinitySafe programming techniques Unsafe programming techniquesSuspect 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 leDetector performance Reporter componentBuilder 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 dataPausing the collection of affinity data When you can pause affinity data collectionWhen you can resume collecting affinity data 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 saves„4… Last update by userid Size of dataspaceTransid prex „2… Detect affinity typesDetector errors Cics Transaction Affinities Utility Guide Running the Reporter Requesting a report from the ReporterCAUAFF1, CAUAFF2, and CAUAFF3 DD statements Caucntl DD statementsOutput from the Reporter Cmdgrps DD statementTrangrps DD statement Affinity report System„1… Incorrect affinity types „2… Affinity types reported„3… Affinities reports TrangroupRecoverable CommandAffinity LifetimeProducing affinity transaction group denitions TerminalBTS Task Total TransactionsUsing the affinity report Afflifesystem Descaddress CWAUnderstanding the affinities Modifying affinity transaction groupsRemove false affinities Remove affinity relation worseningCompressing affinity data Using the IBM Cross System Product SPI commandsENQUEUEs/DEQUEUEs 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 Detector Cafb request queue manager diagnostics Date formatter diagnosticsReason code values This sectionIndex Bappl Vsam Cics Transaction Affinities Utility Guide Sending your comments to IBM Ibmr IBM

OS specifications

IBM OS, or IBM Operating System, refers to a family of operating systems developed by IBM to support its hardware architectures. IBM has produced a range of OS versions tailored for different computing needs, such as mainframes, servers, and personal computers. Among the most notable operating systems in IBM's portfolio are OS/2, z/OS, and AIX, representing a blend of innovation and reliability that has defined IBM's reputation in the computing world.

One of the defining features of IBM OS is its robust multitasking capabilities. Both z/OS, predominantly used in IBM's mainframe environments, and AIX, the Unix-based system for IBM Power Systems, support multiple users and processes simultaneously. This ability allows organizations to run numerous applications in parallel efficiently, maximizing resource utilization and improving productivity.

In terms of security, IBM OS incorporates advanced features aimed at protecting data and maintaining integrity. z/OS offers multifactor authentication, data encryption, and a security model that adheres to the latest regulatory requirements. AIX provides Secure Virtualization, which enhances isolation and security in cloud environments, essential for enterprises handling sensitive information.

Another key characteristic is the adaptability of IBM OS to modern technologies. For instance, z/OS is designed to integrate with cloud computing, open source, and DevOps practices. This adaptability supports organizations in modernizing their infrastructure while retaining the stability associated with IBM solutions. AIX similarly supports containerization and virtualization, which are critical for optimizing resource usage in dynamic computing environments.

IBM's commitment to scalability is evident across its OS offerings. Organizations leveraging z/OS can handle enormous workloads and transactional volumes, making it a preferred choice for industries like finance and telecommunications. AIX also supports scalability, allowing businesses to expand their computing resources as demands grow without significant downtime.

The availability of development tools and environments is another noteworthy aspect of IBM OS. With robust IDEs and programming languages support, developers can create and deploy applications smoothly. This assists businesses in streamlining their development processes and improving time-to-market for innovative solutions.

In summary, IBM OS encompasses a suite of operating systems characterized by multitasking, security, adaptability to modern technologies, scalability, and comprehensive development support. These features have cemented IBM's position as a leader in enterprise solutions, allowing organizations across various industries to thrive in an increasingly digital world.
Top Page Image Contents