Quick Ref Installation and Usage
Overview of Quick Ref
- Purpose: Quick Ref is used to look up specific error messages and solutions.
Usage of Quick Ref
- Accessing Quick Ref:
- Command to invoke:
QW - Use
R to select options for looking up items. - Type
Quick Ref in the command line to access error messages directly from logs.
- Error Message Retrieval:
- Example: Accessing errors such as dollar codes (390, 395).
- Provides an explanation of job names and return codes.
- Includes operator responses required for different error messages.
System Actions for Errors
- Response Protocol:
- Different error messages might require different responses from operators.
- Some errors will instruct to consult the systems programmer or contact support (e.g., IBM).
- Logs and Dumps:
- Users may need to capture logs/dumps to provide to IBM for deeper analysis.
Installation Process of Quick Ref
- Prerequisites:
- Upload the new database to the relevant LPAR (Logical Partition) in production or test environment.
- Two essential files: Database file and Library Rex Exec for guidance on installation.
- Installation Steps:
- Execute command:
tso ex <Rex exec file>. - Importance of enclosing dataset names in ticks to avoid search errors.
- Volume Management:
- Keep track of the data volume for installation to avoid space issues during the process.
- Example volume usage:
TST LB7. - Allocate data sets automatically during installation to minimize manual input.
Quick Ref Installation Breakdown
- Full Install Option:
- Always opt for a full installation to ensure all data sets and load libraries are appropriately set up for new releases.
- Naming Conventions:
- Use high-level qualifiers and follow naming rules for versions (e.g.,
quick ref R89 for version 8.9).
Manual Verification and Examples
- Reviewing Allocated Data Sets:
- Monitor loaded members during installation.
- Screen prompts indicate successful loading or errors encountered during the process.
- Installation Assistance Dialog:
- Can assist in the installation and address testing procedures.
- Invocation command:
qw to access MVS Quick Ref.
Software Versioning and Updates
- Version Transition: Review commands for previous versions and confirm database accuracy.
- Key Files for Licensing:
- Maintain consistency in license key files during upgrades (e.g., maintaining
QuickRef R80). - Update accordingly for major version upgrades (e.g., from 8.0 to 9.x).
Conclusion and Future Installations
- Considerations for Future Products:
- Products like JCL Plus or IOF have more complex install protocols, involving additional jobs.
- Each installation requires observation of specific jobs that help in unpacking and assembling data sets effectively.
- Collaboration and Support:
- Guidance provided to novice users on installation processes, ensuring they are well-prepared and supported through practical experience.