Improve CQS design to access IMS Logger Structure

Following the MVS System Logger's current design, reported by pmr 23734,228,631, the ASYNC logger calls to a CF Logger structure result in extra SRB schedule and processing for the logging explorers. Now that we are aware of this, if the logger calls end up in ASYNC processing due to the additional time/distance required to access the CF remotely, then the logging explorers running distant from the Logger structure is at a disadvantage for CPU processing (and therefore elpased time) in comparison to the other logging explorers running near from the Logger structure on the same parallel sysplex. Besides of the overhead on the z/OS image side, there are negative effects for the Coupling Facility, because the logging explorers running distant from the Logger structure have to perform more XCF requests due to a loop around the IXLLIST REQUEST=WRITE to make sure the list authority (timestamp) at the time the block is written to the structure has a timestamp newer than the list authority already on the list entry. This could cause multiple accesses to the CF within a single ixgwrite. NewAuthority is set to the current timestamp each time through the loop. So, when ixgwrites are coming from multiple systems to the same structure, the system with the quickest write time will have fewer passes through the IXLLIST loop.

Being the IMS CQS (Common Queue Server) a logging explorer, in order to reduce the overhead caused to the IMS transactions, running distant from the Logger structure and to the Coupling Facility, it is extremely important to change the current IMS CQS design improving its code to meet the asymmetric sysplex needs.So this new RFE is to request a CQS enhancement in order to verify the possibility of a design change in the way of getting a good list authority (timestamp) avoiding negative impacts for the IMS transactions running distant from the Logger structure and for the respective Coupling Facility.