Before you begin
InfoQuest installs on the Unisys 2200 host with COMUS and pairs with a Windows client (InfoQuest Client). Confirm Q-LINK is installed at the minimum required configuration, and review the supported software levels for your Exec, COBOL, COMUS, and Q-LINK releases before starting.
- Migration notes apply when moving from level 4R1 or 5R5 — review them first
- Q-LINK minimum configuration must be in place; InfoQuest runs reports through Q-LINK
- Have the InfoQuest Product License Information sheet on hand for CONFIGURE
COMUS install sequence
- REGISTER InfoQuest with COMUS to record the product
- CONFIGURE InfoQuest for BUILD/INSTALL — fill in license information, environmental parameters, and execution parameters
- Run the COMUS BUILD command, supplying any permanent SGSs your site requires
- Run the COMUS INSTALL command to place the product files
- Configure InfoQuest for execution and complete post-installation steps
Product and support files
- INFOQ*IQ$VIEW. — view definitions
- INFOQ*IQ$DBM. — database mapping
- IQ$DEMO*ORDERFILE. and IQ$DEMO*ORDERHIST. — demo data files for validation
MAPPER administration
If you use InfoQuest's MAPPER mode, generate the MAPPER types, set up the InfoQuest Department, perform initial user registration, and run the run-registration and installation runs (an octal H-type run number is required).
Initial maintenance
- Initialize the InfoQuest files
- Run External Configuration to set the configuration selections that apply to your site
- Validate using the demo application — first via InfoQuest Client, then via any other InfoQuest components in use
Note: Applying changes after install: COMUS change format is preferred; TCF change format is supported for sites that need it. See the appendix in the printed guide for the exact syntax.
