Control-D/Page On Demand Components

Control‑D/WebAccess Server acts as a client component that communicates with the Control‑D Application Server. The Control‑D/WebAccess Server client and the Control‑D Application Server communicate over SNA and TCP/IP networks.

The following figure illustrates how Control‑D/Page On Demand is processed using the Control‑D Application Server on the mainframe and Control‑D/WebAccess Server as the client or a workstation:

The workflow under Control‑D/Page On Demand is as follows:

• A user who needs to view centrally archived reports logs in to Control‑D/WebAccess Server.
• The user is presented a list of reports that were downloaded in batch format according to predefined criteria.
• The user can sort the list of reports, as described in Optional Wish WD3368, in the IOADFLTS member of the IOA DOC library.
• The user requests report retrieval from the central repository (that is, in the mainframe under Control‑D or Control‑V).

  A communication process is established (through SNA using APPC or through TCP/IP protocol) in the background between the PC and the MVS mainframe.

  Logon to the mainframe is enabled using the Mainframe Logon User ID and MF password fields in the Communication Setup dialog box in Control‑D/WebAccess Server.

  User Exit IOAX016 and security module IOASE16 are provided to control access to the mainframe through the IOA Gateway. For more information, see the INCONTROL for z/OS Security Guide, and Chapter 9, "Exits."

  Once logon to the mainframe is established, the Control‑D Application Server processes all the requests of the Control‑D/WebAccess Server client.

• The user specifies selection criteria for the mainframe reports. Reports can be retrieved from the Control‑D Active User file, the Control‑V Migrated User file, or both. Indexed reports can be retrieved by index name and value.
• An additional communication process is initialized between the PC and the mainframe.

  User Exit CTDX024 and security module CTDSE24 are provided to control access to Control‑D and Control‑V mainframe reports. For more information, see Chapter 9, "Exits," and the INCONTROL for z/OS Security Guide.

• In Control‑D/WebAccess Server, the list of reports based on the selection criteria are listed in the Report list. These criteria can be modified as required using the standard Control‑D/WebAccess Server filter.
• The list of reports can be sorted, as described in Optional Wish WD3368, in the IOADFLTS member of the IOA DOC library.

The user then selects the required reports for viewing.

The retrieval request is transferred from Control‑D/WebAccess Server to the Control‑D Application Server on the mainframe. The Control‑D Application Server retrieves the report pages and transfers them to Control‑D/WebAccess Server for further processing. On the Control‑D/WebAccess Server client or workstation, Control‑D/Page On Demand uses a caching mechanism whereby pages that have already been retrieved do not need to be retrieved again from the mainframe.

• The Notification facility enables the user to create and update notes and annotations to Control‑D and Control‑V reports. These notes are kept on the mainframe and are accessible through the Control‑D and Control‑V Online Interface and through Control‑D/WebAccess Server using Control‑D/Page On Demand.
• Any report can be retrieved and viewed using Control‑D/WebAccess Server.

For details about using this feature, see the documentation for Control‑D/WebAccess Server for Windows, version 3.21 or later.