12.07.2015 Views

eTrust CA-Top Secret Security for z/OS and OS ... - SupportConnect

eTrust CA-Top Secret Security for z/OS and OS ... - SupportConnect

eTrust CA-Top Secret Security for z/OS and OS ... - SupportConnect

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

The SYSPLEX XCF FunctionThe SYSPLEX XCF FunctionThe XCF function within a sysplex environment allows communication betweenall systems in the sysplex. The main function is the message routing capability.Any system within the sysplex can "join" a group <strong>and</strong> send <strong>and</strong> receive messagesfrom each of the other members within the same group. For example, if systemA wanted to send a message to all other systems in the group it can do so byissuing a send message to the Coupling Facility. The Coupling Facility is thenresponsible <strong>for</strong> posting or notifying all other "joined" systems within the groupthat a message is waiting <strong>for</strong> them. Each notified system is then responsible <strong>for</strong>receiving the message that was sent. The actions per<strong>for</strong>med by the receivingsystem depend on the content of the message.<strong>eTrust</strong> <strong>CA</strong>-<strong>Top</strong> <strong>Secret</strong> <strong>and</strong> the SYSPLEX XES FunctionThe XES data-sharing feature lets you define a primary <strong>and</strong> an alternate Liststructure in the Coupling Facility.If this feature is enabled, <strong>eTrust</strong> <strong>CA</strong>-<strong>Top</strong> <strong>Secret</strong> attempts to obtain the requesteddata from the Coupling Facility be<strong>for</strong>e any physical I/O is per<strong>for</strong>med. If therequested data is obtained from the Coupling Facility no I/O is per<strong>for</strong>med. Thussaving the time from having to do the actual I/O to the database. If you areusing the <strong>CA</strong>CHE facility with <strong>eTrust</strong> <strong>CA</strong>-<strong>Top</strong> <strong>Secret</strong>, the cache call is per<strong>for</strong>medprior to any call to the Coupling Facility. If the data is found in the <strong>CA</strong>CHE, nocalls to the Coupling Facility or the I/O to the database are per<strong>for</strong>med.Whenever direct physical I/O is requested to the <strong>eTrust</strong> <strong>CA</strong>-<strong>Top</strong> <strong>Secret</strong> database,a number of decisions must be made. It is important that any updating of anyrecord is reflected on the database prior to the Coupling Facility. Most importantis the need to obtain the data from the Coupling Facility when a direct READ of arecord is requested. If any record is being updated, a lock to the CouplingFacility is issued to prevent the same record from being updated in the CouplingFacility by another <strong>eTrust</strong> <strong>CA</strong>-<strong>Top</strong> <strong>Secret</strong> system. The <strong>Security</strong> File ENQ recordshows which system is currently holding the lock <strong>and</strong> a time stamp indicates thetime the lock was placed.A List structure allows <strong>eTrust</strong> <strong>CA</strong>-<strong>Top</strong> <strong>Secret</strong> to optimally control what is placedin the Coupling Facility <strong>and</strong> the maintenance of the data once it is there. Theprimary List structure, defined by the systems programmer, is used to hold allthe data <strong>for</strong> the <strong>eTrust</strong> <strong>CA</strong>-<strong>Top</strong> <strong>Secret</strong> database. The optional alternate Liststructure is used in the case that something happens to the primary list structure.If no alternate is defined, <strong>and</strong> the primary is unavailable, <strong>eTrust</strong> <strong>CA</strong>-<strong>Top</strong> <strong>Secret</strong>defaults to its current I/O processing.Using the Sysplex Coupling Facility 3–3

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!