Messages that begin with RAAX are primarily issued from the HPO Configuration Dialog and common functions.
Choose one of the selection options listed on this panel.
You must enter a valid DB2 subsystem ID. This selects the subsystem to be configured.
The configuration parameters were not saved due to your cancel command. Previous values remain in effect.
You must enter a value in this field. There is no default value.
Enter one of these supported QMF versions and releases. If your QMF version and release is higher than 8.1 enter 8.1.
Enter the default value to use for Translation for this QMF installation. Valid values are ENGLISH, UPPERCASE, FRANCAIS CANADIEN, SIMPLIFIED CHINESE, T-CHINESE, DANSK, FRANCAIS, DEUTSCH, ITALIANO, NIHONGO, HANGEUL, PORTUGUES, ESPANOL, SVENSKA, FRANCAIS (SUISSE), and DEUTSCH (SCHWEIZ).
The specified data set could not be found. You must specify the name of a data set that exists and is catalogued.
The only acceptable values for this flag are yes or no.
Enter the prefix of the names of the CICS libraries at your site. This field is validated by checking for the existence of either a CICS .LOADLIB library or a .SDFHLOAD library.
The configuration parameters are being saved in QMFHPO.SRAALOAD. Please wait while the library is updated.
A severe error occurred while issuing a TSO command to save the configuration parameters. Additional information may be written to your terminal.
An error occurred writing a temporary data set used as input to the assembler.
To build the configuration module, an assembler program is created and assembled automatically. All errors encountered during the assemble process are considered severe. If an error occurs, you will browse the output from the assemble (which will contain more information about the error).
To build the configuration module, an assembler program is created, assembled, and link-edited automatically. If an error occurs, you will browse the output from the link-edit (which will contain more information about the error).
The configuration parameters have been saved.
The application plans and packages cannot be bound until the subsystem is configured (by selecting option 1 from the HPO Configuration Dialog Selection Menu).
The selected plans are being bound online. Please wait for this process to finish. Status information will be written to your terminal as the bind proceeds.
The plans were successfully bound.
An error occurred while binding the selected plans. More information should have been written to your terminal. If not, try binding the plans in batch.
You must not specify a member in this field. The name of a partitioned data set (PDS) is expected. Enter a name without specifying a member.
You must enter the name of a data set that has the DCB characteristics listed. Either specify the name of an existing data set with the proper characteristics, or enter the name of a nonexistent data set which you will subsequently be allowed to create online.
Enter the units for the following space allocations for the data set to be created.
Enter a quantity (in the units specified in the previous field) for the primary or secondary space allocation for the data set.
The specified data sets have been created with the proper DCB information and the specified space allocations.
Enter one of these supported DB2 versions and releases. If your DB2 version and release is higher than 8.1, enter 8.1.
You must enter a member name with a data set name in this field.
The specified data set is invalid. You must enter the name of a VSAM file. The specified data set is invalid.
SQL text cannot be logged without logging activity. If you specify an SQL text log, you must also specify an activity log.
You must enter the name of a data set that has the DCB characteristics listed. Either specify the name of an existing data set with the proper characteristics, or enter the name of a nonexistent data set which you will subsequently be allowed to create online.
You must specify a number for the CPU time threshold value.
No configuration information was found for the specified DB2 subsystem. Proceeding with the configuration process will create it. Configuration values from the last subsystem configured will be carried forward as default values.
The command that you entered on the command line is not valid.
You did not select any plans on the Bind Application Plans panel.
The IEV90 assembler has been detected on the system. In this case, saving the configuration parameters in the foreground is not supported. You must use the batch option.
You did not select any packages on the Bind Packages panel.
The packages for the components that you selected are being bound online. Please wait for this process to finish. Status information will be written to your terminal as the bind proceeds
The packages for the components you selected have been successfully bound.
An error occurred while binding the packages for the selected components. More information should have been written to your terminal. If not, try binding the packages in batch.
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.
When you are using a temporary data set for generated JCL, you cannot specify a member name. The temporary data set created will be a sequential data set.
You must specify the name of a sequential data set or a partitioned data set.
The member name that you entered does not conform to PDS member naming rules.
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.
The specified data set could not be opened. Verify that the data set exists, that you have permission to read it, etc.
The specified data set could not be edited. Verify that the data set exists, that you have permission to read it, etc.
JCL to save configuration information, bind plans, or bind packages has been submitted.
An error occurred while submitting JCL. Additional information may be written to your terminal by TSO.
An error occurred while writing the specified data set. Verify that the data set is not full, that you have permission to write it, etc.
An error occurred reading the specified data set. Verify that the data set exists, that you have permission to read it, etc.
The skeleton data set contains an invalid control code. Verify that the installation process was successful and complete.
The nesting of )IF's in the skeleton data set is too great. The maximum nesting level is 10. Verify that the installation process was successful and complete.
An )ELSEIF was found in the skeleton data set without a preceding )IF. Verify that the installation process was successful and complete.
An )ELSE was found in the skeleton data set without a preceding )IF. Verify that the installation process was successful and complete.
An )ENDIF was found in the skeleton data set without a preceding )IF. Verify that the installation process was successful and complete.
The end of the skeleton data set was reached while processing was still within an )IF or )LOOP. Verify that the installation process was successful and complete.
The skeleton data set contains an invalid construct. Verify that the installation process was successful and complete.
An )ENDLOOP was found in the skeleton data set without a preceding )LOOP. Verify that the installation process was successful and complete.
An )ENDLOOP was found in the skeleton data set without an )ENDIF to terminate an )IF within the loop. Verify that the installation process was successful and complete.
The selected plans were not bound due to your cancel request.
The packages for the selected components were not bound due to your cancel request.
You must specify the name of a data set with the specified DCB characteristics.
You must specify either F to perform the selected action online at your terminal while you wait, or B to generate JCL to perform the selected action in batch.
You cannot specify a temporary data set (*TEMP) in this field.
An unknown error occurred while allocating work data sets to perform the selected action online. Try selecting batch mode for the action.
The system has overridden the DCB characteristics of a work data set needed to perform the selected action online. This is most likely the result of automatic selection of block size for allocated data sets. Try selecting batch mode for the action.
The option that you selected has not been installed
A severe ISPF error occurred when issuing the LMINIT service.
A severe ISPF error occurred when issuing the LMOPEN service.
Neither the RAACGUI or the RAARM module could be located in QMFHPO.SRAALOAD. This probably indicates an error unloading the distribution tape.
Certain QMF data sets are required to be allocated to your TSO session to run QMF. This message indicates that some of the required data sets are not allocated to your session. Although QMF may operate successfully, some functions require these data set allocations. See Installing QMF on MVS to determine the required data set allocations for QMF.
Either RAAXPR or RAAXTB is missing from the capital SRAALOAD library.
Either the registration (RAAXPR) or trial (RAAXTB) module contains an invalid key.
Enter the number of additional log data sets to be allocated. In environments that support large numbers of simultaneous QMF users, adding additional log data sets can eliminate file contention by spreading the activity logging I/O across multiple files. Entering 0 results in no additional log data sets. A value of 5, for example, would allocate an additional 5 TSO activity and SQL log data sets. These data sets are created from the base file names you explicitly provide for the TSO activity and SQL text log data sets, and are processed automatically by HPO. A value greater than 0 should be considered on heavily utilized QMF systems.
Additional log data sets will be named by appending a numeric suffix to the explicit names entered previously on the panel. As a result, the explicit names entered must be no longer than 34 characters.
An error occurred while allocating the specified data set. Additional messages written to the terminal may include more information about the error.
This message, written to the system log, indicates that the specified user running the specified program has encountered an abend condition. Contact product support.
This message, written to the system log, indicates that the specified program is terminating prematurely. Other error messages written to the user terminal or system log contain more information about the cause of the premature termination. Contact product support.