Overview of Cooperative Viewing

CA DRAS enables cooperative report viewing from a Windows-based viewer. This product is middle-ware that runs as a started task on the mainframe. CA DRAS communicates with a CA View agent on one end and with Windows-based viewers such as CA Output Management Web Viewer on the other.
view122
CA DRAS enables cooperative report viewing from a Windows-based viewer. This product is middle-ware that runs as a started task on the mainframe. CA DRAS communicates with a CA View agent on one end and with Windows-based viewers such as CA Output Management Web Viewer on the other.
DRAS - the Distributed Repository Access System
-- A distributed relational database server that provides access to data in a large variety of formats residing on different media.
CA DRAS provides a uniform, consistent view of data throughout the enterprise. CA DRAS treats all the data as relational tables, regardless of the original format or storage medium.
Cooperative Processing/Cooperative Viewing
-- This is the ability to view or print a z/OS-based report from a windows application or web browser.
Client Applications
or
Clients
-- These terms apply to the CA Viewing solutions that work with CA DRAS and CA View to provide the cooperative viewing process.
Cooperative viewing is currently available with the following viewing solutions:
  • CA Output Management Web Viewer
  • CA Output Management Document Viewer
Repository Agent or Agents
-- Agent code is for CA View. This code processes the requests received from CA DRAS. When the Client makes a request through CA DRAS, the Agents send that request to the repository and pass back its response.
Cooperative Processing
To successfully connect the desktop client to the CA View database, several key elements need to be properly installed and configured.
The following illustration shows how the workflow is processed and where each solution fits into what is called
cooperative processing
.
The following steps provide a basic view of how cooperative processing works to provide end-user access to reports residing in a z/OS-based report repository. See CA DRAS Operations for a related diagram.
  1. The Client initiates a request using an initial login or a report data request from CA Output Management Web Viewer.
  2. An SQL request is formatted by the Client API and passed through CA Common Services, Common Communications Interface (CAICCI).
    The Common Communications Interface uses the TCP/IP communication protocol to pass the request from the Windows environment, through CAICCI/PC, to the z/OS-platform running the Common Communication Interface (CCITCP) task.
  3. CA DRAS receives the request from the Common Communications Interface (CAICCI) and passes it on to the CA View Agent API for interpretation. The Agent API formats the request and passes it to CA View for processing.
  4. The request is validated and processed in CA View. Once processed, it is returned to an SQL format and passed back to CA DRAS.
  5. CA DRAS processes and packages the response and passes it back through the Common Communications Interface to the Viewer system, where it is processed and displayed to the Client.
SMF Record Layouts
The Type 6 External Writer SMF record is optional and is created if the startup parameter SMF= is set to YES. The z/OS Type 6 record format definition can be found in the assembler language macro SYS1.MACLIB(IFASMFR).
In a Cross Memory Services (XMS) session, SMF records can also be created. The creation and record type number is controlled by the XMS startup parameter SMFSESS=. The record format definition can be found in the assembler language macro CAI.CVDEMAC(EBCSMFU1).
  • The format of the XMS session SMF record does not follow the same header conventions as the CA View Metrics SMF records.
  • CA Deliver can also create SMF records.