All documentation

InfoQuest — Getting Started

Designing and running ad-hoc queries and reports across mainframe data with InfoQuest's GUI client.

Last updated December 11, 2009

What InfoQuest does

InfoQuest puts a Windows GUI on top of Q-LINK so business and IT users can design, generate, and run ad-hoc queries and reports against mainframe data — without writing Q-Language and without knowing the underlying file structures. InfoQuest reads metadata, lets you pick records and fields, build selection criteria visually, and submits the report to Q-LINK for execution.

Designing a query

  1. Pick the data source — the available subschemas, RDMS schemas, MAPPER datasets, TIP and SFS files all appear in a single tree
  2. Select the records and fields you want returned
  3. Build selection criteria with point-and-click expressions (operator, value, and AND/OR grouping)
  4. Order and group results, choose totals/subtotals, and pick a layout (tabular, columnar, or custom)
  5. Run the report — InfoQuest generates the Q-Language behind the scenes and executes it through Q-LINK

Saving and reusing reports

Reports are stored as report definitions, not as one-off output. Re-run a saved report any time, parameterize selection criteria so the same definition can produce monthly variations, and export the result to a file or printer.

Connectivity

InfoQuest connects to the host through the same WinQ UTS settings used by the rest of the eXpress family. See the WinQ UTS Configuration documentation under I-QU ReorgComposer for the full list of options — they apply identically here.

Note: If you change the connection type (HLC, DCP-as-router, or HGS), update WinQ UTS Configuration before launching InfoQuest, or the connection will fall back to the previous endpoint.