Messages that begin with RAAQ are issued from the Query Analyzer online facility and appear on the message line on ISPF panels and within a QMF session.
You (or your administrator) must run the HPO Configuration Dialog for the specified DB2 subsystem.
You must enter a valid DB2 subsystem ID.
Choose one of the selection options listed on this panel.
You may analyze a query that exists in a data set or you may enter ad hoc query text in the space provided. You cannot leave both of these areas blank.
You may analyze a query that exists in a data set or you may enter ad hoc query text in the space provided. Only one of these sources can be selected at a time.
An error occurred while trying to allocate QMFHPO.SRAASKEL to your session.
You must fill in at least one of these fields for the job card. If only one line is required for the job card, use the first line.
To edit the JCL after it is generated, set this flag to E. To submit the JCL automatically after it is generated, set this flag to S. To bypass JCL generation and job submission, enter the END command.
An error occurred while editing the generated JCL. Check with your system administrator and make sure that you are authorized to create and allocate temporary data sets.
You must specify the name of a data set that exists and is catalogued. JCL will be generated and written to this data set.
You must specify the name of a sequential data set or a partitioned data set.
You cannot specify a member name for the data set because it is a sequential data set.
If you specify a partitioned data set, you must also specify a member name.
The data set that you specify must have a record length of either 79 or 80. No other record length is supported.
An unexpected error was encountered. Your query was not analyzed, but processing will continue.
Any changes that you made to the default parameter settings will be saved in your ISPF profile.
The named REXX program could not be found. Make sure that the library containing the EXEC is allocated to your session.
Any changes that were just made to the default parameter settings have been discarded due to your cancel command.
The member specified is not found in the data set. Check that you have entered the name correctly and that the member exists.
If you specify table space name, then you must also specify a database name. You can, however, specify a database without a table space.
The generated JCL will reside in a temporary data set that is created automatically. An error occurred while creating the data set. Associated error messages may be written to the terminal.
The specified data set could not be found. You must specify the name of a data set that exists and is catalogued.
An error occurred while Query Analyzer either was connecting to DB2 or opening its application plan. In either case, query analysis will be bypassed, and your session will continue normally.
An error occurred while Query Analyzer was disconnecting from DB2. Query analysis was performed, and your session will continue normally.
You (or your administrator) must run the HPO Configuration Dialog for the current DB2 subsystem. Query analysis will not be performed, but your session will continue normally.
A PLAN_TABLE does not exist and no database/table space for creating one is specified in the active resource group. As a result, a PLAN_TABLE cannot be created and query analysis will be bypassed.
Non-SELECT SQL is ignored by Query Analyzer.
The query could not be processed by the EXPLAIN command. Either a PLAN_TABLE does not exist or there is an error in the query. Your session will continue normally.