Messages that begin with RAAC are issued from Program Generator and appear on the message line on ISPF panels.
Choose one of the selection options listed on this panel.
You must enter a valid DB2 subsystem ID. This is the subsystem used to execute SQL, to start QMF, to obtain QMF profile information, and to compile and run programs.
You (or your administrator) must run the HPO Configuration Dialog for the specified DB2 subsystem.
The command that you entered on the command line is not valid.
The input to the generation process must be either a query, a query and form combination, or a linear procedure. Specify only one of these input sources.
A program cannot be generated from a form only. You must also specify a query.
The only acceptable values for the specified flag are yes or no.
You must enter a data set name for the specified type of object (query, form, procedure, source code, or load module). It may or may not already contain the specified data.
QMF requires that data sets into which queries and procedures are exported have RECFM = F and LRECL = 79.
You cannot specify a member name for the data set because it is a sequential data set.
The member name that you entered does not conform to PDS member naming rules.
QMF requires that data sets into which forms are exported have RECFM = V and LRECL between 161 and 7290.
You must specify the name of a sequential data set or a partitioned data set.
Your QMF profile can be keyed by either your TSO logon ID or by your primary DB2 authorization ID. Enter the desired value.
Enter a valid QMF translation value. 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). If you enter *, the configuration default translation will be used.
Any changes that you made to the default parameter settings have been discarded.
Any changes that you made to the default parameter settings will be saved in your ISPF profile.
The previous export command was bypassed due to your cancel command. The object that was to be exported is assumed to not exist in the specified data set.
The post-generation CLIST named RAAPOSTG did not run successfully.
Program Generator is starting a QMF session to export objects.
QMF is exporting the query, form, or procedure. After the export finishes, the specified data set and member will contain the object.
The previous export command failed due to an error condition. Common reasons for this are that the QMF object does not exist or that there is a problem with the specified data set and member. See QMF Messages and Codes for more information on the specified error number. In addition, the DSQDEBUG file may contain more information.
The previous export command was successful. The specified data set and member now contain the QMF object.
A previous export of the specified object failed (or was canceled). Consequently, you cannot process the report for that object.
The data set specified for the object cannot be found or is empty. Consequently, you cannot process the report for that object.
The PDS member specified for the object cannot be found. Consequently, you cannot process the report for that object.
Program Generator is parsing the procedure to build a list of the reports that it runs.
If you specify a partitioned data set, you must also specify a member name.
You must specify a report list row number or the word "PROC" as an argument to this command. For example, specify COMPILE 1 or COMPILE PROC.
You specified an invalid argument with this command. You must specify a report list row number or the word "PROC" as an argument to this command. For example, specify COMPILE 1 or COMPILE PROC.
Too many arguments were specified with this command. You must specify exactly one report list row number or the word "PROC" as an argument to this command. For example, specify COMPILE 1 or COMPILE PROC.
The row number that you specified as an argument to this command is either less than 1 or greater than the number of rows in the report list.
You must enter an 8 character (or less) name to be used as the plan name for the program.
The plan name that you entered does not conform to plan naming rules.
To browse the specified object, set this flag to B. To edit the object, set this flag to E. To do neither, set this flag to N.
The data set or member to be browsed contains no data.
The member to be browsed does not exist.
The browse session failed due to a severe ISPF error.
The data set or member is in use and therefore cannot be edited.
The member to be edited does not exist.
The edit session failed due to a severe ISPF error.
Program Generator did not find any substitution variables in the query or the form, so there are none to edit. Normal processing will continue.
Any variable value changes that you made were discarded.
You can generate OS/VS COBOL, VS COBOL II, COBOL for MVS, or COBOL for OS/390 programs. Choose the one desired for this generation.
You can generate programs to run either in MVS batch, TSO, CICS, or as a stored procedure under DB2. Choose the one desired for this generation.
If you set this flag to T, the generated program will connect to DB2 via the TSO attachment facility. If you set it to C, the generated program will connect to DB2 via the call attachment facility (CAF). If you set it to C, the generated program will connect to DB2 via the Recoverable Resource Manager Services attachment facility (RRSAF). This flag is ignored for CICS programs, which always connect to DB2 via the CICS attachment facility.
You must specify a table name when generating a program that will SAVE DATA to a DB2 table or ERASE a DB2 table.
The specified option is not allowed with data layer programs.
You can only specify a print program when you are generating a display program. The program that you enter will be invoked when a user enters the PRINT command from the display program.
You cannot edit a program until it is generated.
The specified option is not allowed with CICS programs.
The pre-generation CLIST named RAAPREG did not run successfully.
The specified option is not allowed with TSO or CICS print programs.
Program Generator bypassed the generation process due to your cancel command.
Program Generator is generating the program. When it is finished, the specified output data set and member will contain the source code.
The program has been generated in the specified data set and member.
If you enter P, the program will be compiled by invoking DB2I, which will lead you through a series of panels to invoke the compilation process. If you enter N, the program will be compiled immediately by invoking the DSNH command online. If you enter B, JCL will be tailored to perform the compile in batch.
You can compile OS/VS COBOL, VS COBOL II, COBOL for MVS, and COBOL for OS/390 programs using this facility.
The specified option is not allowed with TSO print programs.
Enter the value to use for the VALIDATE parameter to the BIND PLAN command. See DB2 Application Programming and SQL Guide for more information on this parameter. If the SQL in the program you are compiling refers to any DB2 tables that do not exist at compile time, you must specify RUN for the BIND to succeed.
Load modules can only be created as members of partitioned data sets. You cannot specify a sequential data set as the target for the program.
A severe ISPF error occurred when issuing the LMINIT service.
A severe ISPF error occurred when issuing the LMOPEN service.
The program was not compiled due to your cancel command.
Program Generator is preparing the program online. If the process completes successfully, the program will be ready to run.
An error occurred during the online compile. The return code is included in this message. More information should be written to your terminal during the compile. In addition, see the discussion of the DSNH command in DB2 Command and Utility Reference for more information about the compile, including how to locate the output from each step.
You can only run programs from a partitioned data set.
If you leave the load library blank, Program Generator assumes that the program to be run exists within one of the load libraries allocated to your TSO session. If you leave the program ID blank, Program Generator displays a member list (from the specified load library). You can select the program to run from this list. If you specify both the load library and the program ID, the program is run from the specified load library (the program must exist in the specified library). You cannot leave both of these fields blank.
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 or CANCEL commands.
The program was not run due to your cancel command.
The program is running. Please wait for the first page of the report to be displayed.
An error occurred while running the program. The return code is included in this message.
When using temporary data sets to export queries, forms, or procedures, you cannot specify a member name. The temporary data set that Program Generator creates will be a sequential data set.
The program name that you entered does not conform to program naming rules.
You can only run batch or TSO programs using this facility.
The specified option is required with TSO print programs.
TSO print programs always read their input from a file written by the display program, rather than reading from DB2. Because of this, a print program can only be specified for a display program if the display program writes data to a file.
Program Generator has submitted JCL to either compile or run a program.
An error occurred while submitting JCL to either compile or run a program. Additional information may be written to the terminal by TSO.
TSO display programs that have a corresponding print program cannot use the HPO/Runtime feature.
When running a program, you can optionally specify the language the program was written in. This allows Program Generator to allocate the appropriate system libraries to the run (i.e., the appropriate COBOL runtime library).
Program Generator does not support non-SELECT SQL in CICS programs.
Data layer programs are required to use static SQL.
The single quote character (') is not allowed in compile or link edit options. Remove the character.
You must generate the program in the specified row of the report list before you can generate a proc program that runs it.
The program in the specified row of the report list was generated in a different language than the proc program. All programs run by a proc program must be written in the same language as the proc program.
The program in the specified row of the report list was generated for a different environment than the proc program. All programs run by a proc program must be written for the same environment as the proc program.
The program in the specified row of the report list was generated to use a different attachment facility than the proc program. All programs run by a proc program must be written to use the same attachment facility as the proc program.
You cannot specify a temporary data set (*TEMP) for a query, form, or procedure data set unless the object is to be exported.
You cannot specify a temporary data set (*TEMP) for the data set entered in this field.
An error occurred while creating a temporary data set. Additional error messages may be written to the terminal.
No objects matching the specified owner and name were found in the database.
You must select one and only one object from each displayed column.
The character entered in the selection field was not recognized.
The JCL was not generated due to your cancel command.
You must specify a partitioned data set name for the DBRM library. Sequential data sets are not allowed.
An unexpected error was encountered.
Expand your region size.
The specified data set could not be found. You must specify the name of a data set that exists and is catalogued.
You cannot specify the member name as part of the data set name. For example, PDS.LIBRARY(MEM) is invalid. On the Set Default Parameters panel, you can leave the member field blank, and Program Generator will automatically build a member name from the object name. On all other panels, you must specify a member.
This message may appear while Program Generator is connecting to the specified DB2 subsystem. Check the return code (RC) and reason code (REASON) in DB2 Messages and Codes. Also check that the DB2 subsystem ID that you entered is correct.
Program Generator could not open the specified data set. Verify that the data set exists, that you have permission to read it, etc.
An error occurred while reading the specified data set. Verify that the data set exists, that you have permission to read it, etc.
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.
You may only specify a linear procedure as input. Procedures with logic are not supported.
Object names must follow QMF object name syntax. The owner can be 8 characters or less and name can be 18 characters or less. A period should be used to delimit the owner and name.
The specified procedure referred to too many reports. See "Program Generator specifications" for the maximum number of reports supported.
The specified query referred to too many substitution variables. See "Program Generator specifications" for the maximum number of substitution variables supported.
Program Generator did not find any reports when parsing the specified procedure. Each PRINT REPORT command in a procedure corresponds to a report. Also, each RUN QUERY command without a succeeding PRINT REPORT command corresponds to a report.
An SQL error occurred while reading the Q.OBJECT_DIRECTORY table to build an object selection list. Enter the HELP command to obtain more information about the error.
An SQL error occurred while accessing the report registration tables (Q.REPORTS and Q.REPORT_VARIABLES). Enter the HELP command to obtain more information about the error.
An SQL error occurred while retrieving the current SQLID. This is generally indicative of an unrecoverable error (for example, the application plan has been bound incorrectly). Enter the HELP command to obtain more information about the error.
This message may appear while Program Generator is connecting to DB2. Check the return code (RC) and reason code (REASON) in DB2 Messages and Codes. Enter the HELP command to obtain more information about the error.
You cannot connect to the specified location from this DB2 subsystem. Enter the HELP command to obtain more information about the error and check with your system or database administrator.
An error occurred while trying to allocate the RAAOUT DD to the specified output data set. This allocation uses the disposition specified on the Set Default Parameters panel.
You must specify the disposition to use for the output data set when generating source code.
This message may appear while Program Generator is disconnecting from the specified DB2 subsystem. Check the return code (RC) and reason code (REASON) in DB2 Messages and Codes.
You must select one of the specified bind types.
For report programs, specifying 1 indicates that only a package should be bound from the program's DBRM. Specifying 2 indicates that only a plan should be bound from the program's DBRM. Specifying 3 indicates that a package should be bound from the program's DBRM, and then a plan should be bound, including the package. Specifying 4 indicates that no bind should be performed.
For proc programs, specifying 1 indicates that a plan should be bound with a PKLIST that references all of the referenced report programs' packages. Specifying 2 indicates that a plan should be bound that includes all of the report programs' DBRMs. Specifying 3 indicates that a plan should be bound with a PKLIST that references the referenced report programs' packages (for those that have packages bound) as well as including the referenced report programs' DBRMs (for those that do not have packages bound). Specifying 4 indicates that no bind should be performed.
In order to bind a package, a collection ID in which to bind it must be specified. Your user ID (or the bind OWNER) must have the DB2 privilege to bind packages in the collection ID that you specify.
The specified collection ID has invalid syntax.
In order to bind a plan for a proc program that includes only a PKLIST that references the report programs' packages, all of the report programs must have packages bound.
When saving data, if it is determined that the target table already exists, a decision must be made regarding what to do with any data that might already exist in the table. If you specify to replace the existing data, it is deleted before saving the new data. If you specify to append to the existing data, it is not deleted. If you specify to prompt for the action, different behavior occurs depending on whether the program is a batch program or a TSO program. For batch programs, a positional parameter can be passed in the PARM field at runtime to indicate the desired disposition (R for replace or A for append). For TSO programs, a prompt panel is displayed, prompting the user for the desired disposition. Prompting is not supported for CICS programs; the save data action for CICS programs must be replace or append.
Enter S to specify that all SQL used in saving data should be static SQL, or D to specify that it should be dynamic SQL. If the program uses dynamic SQL in all other contexts, the save data SQL must also be dynamic.
Using dynamic SQL for saving data allows the save data table name, when unqualified, to be qualified with the user ID of the user at runtime, rather than the plan or package OWNER or QUALIFIER parameter.
Enter T to specify that all of the host variables used by the program will be specified on a single input record, separated by a specific delimiter character. Enter C to specify that each host variable will be specified on a separate input record (in which case no delimiter character is used).
The specified type of options do not apply when generating programs from queries that do not use the SQL verb SELECT. As a result, the display of the options pop-up window has been suppressed.
The specified type of options do not apply when generating data layer programs. As a result, the display of the options pop-up window has been suppressed.
If you are running a report program, which expects to read host variable input from the DD named HOSTVARS, enter H. If you are running a proc program, which expects to read host variable input from the DD named PROCVARS, enter P.
The specified type of options do not apply unless generating programs for the batch environment which also use host variables (excluding data layer programs). As a result, the display of the options pop-up window has been suppressed.
Your request to cancel entry of host variable values has been accepted.
All of the selected options pop-up windows have been displayed. Press Enter to generate the program.
In order to use the special value *USERPROF to specify that the target table space for the save data table should be retrieved from the QMF profile of the user at runtime, the SQL used to save data must be dynamic. If dynamic SQL is not desired, the table space value must be changed from *USERPROF.
TSO programs can use the TSO attachment facility or the call attachment facility (CAF) to connect to DB2. You must select one of these two values.
TSO programs can use the TSO attachment facility or the call attachment facility (CAF) to connect to DB2. You must select one of these two values.
The specified type of options do not apply unless generating data layer programs. As a result, the display of the options pop-up window has been suppressed.
Part of the generation process for data layer programs requires Program Generator to parse the input SQL statement. Program Generator was unable to parse the current statement, and therefore cannot generate a data layer program from it. This error indicates an unexpected internal parsing error in Program Generator.
Data layer programs can only be generated in VS COBOL II, COBOL for MVS, or COBOL for OS/390. OS/VS COBOL is not supported.
A token was found while parsing the procedure data set that exceeded the maximum length. The maximum length for a token in a procedure is 256.
An invalid token was found while parsing the procedure data set. Verify that the data set contains a valid linear procedure.
An unbound variable was found while parsing the procedure data set. Verify the procedure in the data set, possibly replacing variables with constants.
The data set specified in the IMPORT command in the procedure data set is invalid.
A syntax error was found while parsing the procedure data set.
Variable values must be 55 characters or less.
Verify the specified procedure data set. Make sure that variable assignments are complete. Do not leave any assignments incomplete, such as RUN QUERY (FORM=.
A positive integer value was expected. A non-integer or an integer that is too large was found.
A RUN command was found that did not reference a query name or QUERY.
An invalid value for the DATETIME parameter of the PRINT command was found. See QMF Reference for legal values.
An invalid value for the PAGENO parameter of the PRINT command was found. See QMF Reference for legal values.
An illegal continuation line was found while parsing the procedure data set.
A command was found while parsing the procedure data set that exceeds the maximum procedure command length.
The host variable name that you entered is too long. The length of COBOL identifiers is limited to 30 characters. You must specify a shorter variable name.
When specifying data type CHAR, you must specify a length within parentheses directly after the data type, for example: VAR1 CHAR(3). When specifying data type DECIMAL, you may optionally specify a precision or precision and scale after the data type, for example: VAR1 DECIMAL(5) or VAR1 DECIMAL(7,2). The precision must be less than or equal to 15 and the scale must be less than or equal to the precision.
Valid data types are INTEGER, SMALLINT, DECIMAL(p,s), DECIMAL(p), DECIMAL, FLOAT, CHAR(n), VARCHAR(n), DATE, TIME, and TIMESTAMP.
When specifying a host variable name, enter a colon (:) followed by the variable name. For example,:VAR1.
One or more host variables have the same name. Note that the following suffixes may be added to the names entered on the Edit Variables panel: -I, -L, -C. You must change one or more of the names to eliminate the conflict.
You must supply a data type for each host variable specified.
When you are generating a program in batch from a query or form that uses variables, Program Generator reads values for those variables from the RAAVARS DD. Make sure that the RAAVARS DD is defined and has the correct format.
A record read from the RAAVARS DD had an invalid format. Each record must be of the form &VARNAME=VARVALUE
A host variable name was specified in the format :=tbcreator.tbname.colname, but there is no column with the given name in the specified table. You must specify a valid column name.
A host variable name was specified in the format :=tbcreator.tbname.colname, but there is no column with the given name in the specified table. You must specify a valid column name.
An unexpected internal error occurred while trying to resolve conflicts in the names of host variables by appending numeric suffixes to the host variable names.
The indicated host variable name is too long. The maximum length that may be specified is 25 characters. This limit allows for the addition of standard name prefixes and suffixes generated by Program Generator.
The use of the host variable name syntax :=tbcreator.tbname.colname to automatically create a host variable suitable for use with the named database column is only supported when Program Generator is able to parse the input SQL statement. This error indicates an unexpected internal parsing error in Program Generator.
An error occurred while allocating the specified data set. Additional TSO messages written to the terminal should contain more information about the cause of the error.
The specified data set has been allocated.
You must select the units in which the primary and secondary space allocation for the data set will be expressed.
You must enter a valid number greater than zero for the primary space quantity.
You must enter a valid number greater than or equal to zero for the number of directory blocks. Entering a zero will result in the allocation of a sequential data set. Entering a value greater than zero will result in the allocation of a partitioned data set (PDS).
The data set has not been allocated.
You must enter a valid number greater than or equal to zero for the secondary space quantity.
You must enter a valid number greater than zero for the number of directory blocks.
The values that you entered on the Enter Host Variable Values pop-up window have been saved. Press Enter to continue generating the JCL.
You must specify the name of a partitioned data set.
In order to specify a member name in this field, you must also specify a data set name in the preceding field.
The specified option is not allowed with stored procedure programs.
The generated CREATE PROCEDURE statement was executed successfully, creating the stored procedure definition in the database. Note that the stored procedure cannot be called until the program is compiled and the resulting load module placed in the appropriate load library for the desired WLM address space.
The specified form data set contains a form that has QMF warnings or errors. To determine what the warnings or errors are, display the form in QMF, and enter the CHECK command.
The specified form data set does not contain a valid QMF form.
Program Generator does not support user edit routines (Uxxxx and Vxxxx) with CICS programs.
Program Generator does not support the ACROSS and CALC usage codes with standalone programs.
The specified form data set does not contain a valid QMF form.
You attempted to replace a substitution variable with a host variable. However, that variable is used in the form. All substitution variables in form text must be replaced with literals when generating a program that uses the HPO/Runtime feature.
The exported form contains form detail variation, which Program Generator does not support.
Program Generator does not support the xPCT usage codes with CICS programs.
You must specify what additional output parameters (if any) should be generated in the stored procedure program. If you enter 1, no such parameters are generated. If you enter 2, one additional output parameter (named ERROR_MESSAGE) is added to the generated program to receive a single line of error message text if any error occurs. If you enter 3, an additional output parameter (named SQL_ERROR_MESSAGE) is added to the generated program to receive detailed SQL error message text if any SQL error occurs.
An error occurred while parsing the query. One possible cause (of many) for this is that substitution variables in the query have not been replaced with values. Make sure that all variables have been replaced by constants, literals, or host variables (with data types).
A token which exceeds the maximum token length was found while parsing the query.
An invalid name was found while parsing the query.
An invalid hexadecimal string constant (e.g., x'40F') was found while parsing the query.
You must specify how the stored procedure will interact with any security resources outside of DB2. If you enter D, such interaction is performed in the context of the authorization ID associated with the address space in which the stored procedure is running. If you enter U, such interaction is performed in the context of the authorization ID invoking the stored procedure. If you enter D, such interaction is performed in the context of the authorization ID that executed the CREATE PROCEDURE statement for the stored procedure.
You must specify how special register values are initialized when the stored procedure executes. If you enter I, the values of special registers are inherited from the environment in which the stored procedure executes. If you enter D, the values of special registers are initialized to default values.
Invalid characters were found while parsing the query.
The query refers to a table that does not exist. Either there is a preceding query in the procedure that performs a CREATE TABLE for the nonexistent table, or there is a preceding SAVE DATA command that creates the nonexistent table. In either case, you must generate the program that performs the CREATE TABLE or SAVE DATA before you can generate this program.
The ASU time limit that you specify for the stored procedure must be numeric. If you enter 0, no limit is applied.
Stored procedure programs use only packages, not plans. Consequently, you must enter 1 to bind a package for the program, or 4 to skip the bind at this time.
Stored procedure programs can only be generated in COBOL for MVS or COBOL for OS/390. OS/VS COBOL and VS COBOL II are not supported.
An error occurred while parsing a query that contains a UNION clause. An invalid token was found when expecting the type of token specified in the message.
An error has occurred while parsing the input query. Verify that the query is actually a valid SQL statement (for example, by running it from QMF) or correct any errors in it. If the problem persists, this is indicative of an unexpected internal parsing error in Program Generator.
An error has occurred while parsing the input query. Verify that the query is actually a valid SQL statement (for example, by running it from QMF) or correct any errors in it. If the problem persists, this is indicative of an unexpected internal parsing error in Program Generator.
An error has occurred while parsing the input query. Verify that the query is actually a valid SQL statement (for example, by running it from QMF) or correct any errors in it. If the problem persists, this is indicative of an unexpected internal parsing error in Program Generator.
An error has occurred while parsing the input query. Verify that the query is actually a valid SQL statement (for example, by running it from QMF) or correct any errors in it. If the problem persists, this is indicative of an unexpected internal parsing error in Program Generator.
An error has occurred while parsing the input query. Verify that the query is actually a valid SQL statement (for example, by running it from QMF) or correct any errors in it. If the problem persists, this is indicative of an unexpected internal parsing error in Program Generator.
An error has occurred while parsing the input query. Verify that the query is actually a valid SQL statement (for example, by running it from QMF) or correct any errors in it. If the problem persists, this is indicative of an unexpected internal parsing error in Program Generator.
An error has occurred while parsing the input query. Verify that the query is actually a valid SQL statement (for example, by running it from QMF) or correct any errors in it. If the problem persists, this is indicative of an unexpected internal parsing error in Program Generator.
An error has occurred while parsing the input query. Verify that the query is actually a valid SQL statement (for example, by running it from QMF) or correct any errors in it. If the problem persists, this is indicative of an unexpected internal parsing error in Program Generator.
An error has occurred while parsing the input query. Verify that the query is actually a valid SQL statement (for example, by running it from QMF) or correct any errors in it. If the problem persists, this is indicative of an unexpected internal parsing error in Program Generator.
An error has occurred while parsing the input query. Verify that the query is actually a valid SQL statement (for example, by running it from QMF) or correct any errors in it. If the problem persists, this is indicative of an unexpected internal parsing error in Program Generator.
An error has occurred while parsing the input query. Verify that the query is actually a valid SQL statement (for example, by running it from QMF) or correct any errors in it. If the problem persists, this is indicative of an unexpected internal parsing error in Program Generator.
An error has occurred while parsing the input query. Verify that the query is actually a valid SQL statement (for example, by running it from QMF) or correct any errors in it. If the problem persists, this is indicative of an unexpected internal parsing error in Program Generator.
An error has occurred while parsing the input query. Verify that the query is actually a valid SQL statement (for example, by running it from QMF) or correct any errors in it. If the problem persists, this is indicative of an unexpected internal parsing error in Program Generator.
An error has occurred while parsing the input query. Verify that the query is actually a valid SQL statement (for example, by running it from QMF) or correct any errors in it. If the problem persists, this is indicative of an unexpected internal parsing error in Program Generator.
An error has occurred while parsing the input query. Verify that the query is actually a valid SQL statement (for example, by running it from QMF) or correct any errors in it. If the problem persists, this is indicative of an unexpected internal parsing error in Program Generator.
An error has occurred while parsing the input query. Verify that the query is actually a valid SQL statement (for example, by running it from QMF) or correct any errors in it. If the problem persists, this is indicative of an unexpected internal parsing error in Program Generator.
An error has occurred while parsing the input query. Verify that the query is actually a valid SQL statement (for example, by running it from QMF) or correct any errors in it. If the problem persists, this is indicative of an unexpected internal parsing error in Program Generator.
An error has occurred while parsing the input query. Verify that the query is actually a valid SQL statement (for example, by running it from QMF) or correct any errors in it. If the problem persists, this is indicative of an unexpected internal parsing error in Program Generator.
An error has occurred while parsing the input query. Verify that the query is actually a valid SQL statement (for example, by running it from QMF) or correct any errors in it. If the problem persists, this is indicative of an unexpected internal parsing error in Program Generator.
An error has occurred while parsing the input query. Verify that the query is actually a valid SQL statement (for example, by running it from QMF) or correct any errors in it. If the problem persists, this is indicative of an unexpected internal parsing error in Program Generator.
An error has occurred while parsing the input query. Verify that the query is actually a valid SQL statement (for example, by running it from QMF) or correct any errors in it. If the problem persists, this is indicative of an unexpected internal parsing error in Program Generator.
An error has occurred while parsing the input query. Verify that the query is actually a valid SQL statement (for example, by running it from QMF) or correct any errors in it. If the problem persists, this is indicative of an unexpected internal parsing error in Program Generator.
An error has occurred while parsing the input query. Verify that the query is actually a valid SQL statement (for example, by running it from QMF) or correct any errors in it. If the problem persists, this is indicative of an unexpected internal parsing error in Program Generator.
An error has occurred while parsing the input query. Verify that the query is actually a valid SQL statement (for example, by running it from QMF) or correct any errors in it. If the problem persists, this is indicative of an unexpected internal parsing error in Program Generator.
An error has occurred while parsing the input query. Verify that the query is actually a valid SQL statement (for example, by running it from QMF) or correct any errors in it. If the problem persists, this is indicative of an unexpected internal parsing error in Program Generator.
An error has occurred while parsing the input query. Verify that the query is actually a valid SQL statement (for example, by running it from QMF) or correct any errors in it. If the problem persists, this is indicative of an unexpected internal parsing error in Program Generator.
An error has occurred while parsing the input query. Verify that the query is actually a valid SQL statement (for example, by running it from QMF) or correct any errors in it. If the problem persists, this is indicative of an unexpected internal parsing error in Program Generator.
An error has occurred while parsing the input query. Verify that the query is actually a valid SQL statement (for example, by running it from QMF) or correct any errors in it. If the problem persists, this is indicative of an unexpected internal parsing error in Program Generator.
An error has occurred while parsing the input query. Verify that the query is actually a valid SQL statement (for example, by running it from QMF) or correct any errors in it. If the problem persists, this is indicative of an unexpected internal parsing error in Program Generator.
An error has occurred while parsing the input query. Verify that the query is actually a valid SQL statement (for example, by running it from QMF) or correct any errors in it. If the problem persists, this is indicative of an unexpected internal parsing error in Program Generator.
An error has occurred while parsing the input query. The use of table locators was encountered, which is not supported by Program Generator.
An error has occurred while parsing the input query. The use of three-part table names was encountered, which is not supported by Program Generator.
An error has occurred while parsing the input query. Verify that the query is actually a valid SQL statement (for example, by running it from QMF) or correct any errors in it. If the problem persists, this is indicative of an unexpected internal parsing error in Program Generator.
An error has occurred while parsing the input query. Verify that the query is actually a valid SQL statement (for example, by running it from QMF) or correct any errors in it. If the problem persists, this is indicative of an unexpected internal parsing error in Program Generator.
An error has occurred while parsing the input query. The use of transition tables was encountered, which is not supported by Program Generator.
An error has occurred while parsing the input query. Verify that the query is actually a valid SQL statement (for example, by running it from QMF) or correct any errors in it. If the problem persists, this is indicative of an unexpected internal parsing error in Program Generator.
The user-specified host variable exit specified on the Set Default Parameters panel returned a non-zero return code. Investigate this exit CLIST to determine the cause of the error.
A host variable exit was specified on the Set Default Parameters panel to customize the declaration and use of host variables in the generated program. However, Program Generator encountered an error while parsing the input query, and as a result, cannot apply the exit.
The user-specified column exit specified on the Set Default Parameters panel returned a non-zero return code. Investigate this exit CLIST to determine the cause of the error.
A column exit was specified on the Set Default Parameters panel to customize the appearance of column names in the generated program. However, Program Generator encountered an error while parsing the input query, and as a result, cannot apply the exit.
The user-specified table exit specified on the Set Default Parameters panel returned a non-zero return code. Investigate this exit CLIST to determine the cause of the error.
The executable exit module with the specified name could not be loaded. Program Generator searches for this member in the following locations:
Verify that the correct module name was entered on the Set Default Parameters panel and that a module with that name exists in one of the above locations.
An SQL error identified by the specified SQL code has occurred while parsing the input query and retrieving information about one of the tables referenced by the query. Verify that the correct table is referenced by the query, that the table exists, and that you have authority to read from it, and try the operation again.
An error has occurred while parsing the input query. Verify that the query is actually a valid SQL statement (for example, by running it from QMF) or correct any errors in it. If the problem persists, this is indicative of an unexpected internal parsing error in Program Generator.
An error has occurred while parsing the input query. Verify that the query is actually a valid SQL statement (for example, by running it from QMF) or correct any errors in it. If the problem persists, this is indicative of an unexpected internal parsing error in Program Generator.
The query contains an SQL error, indicated by SQLCODE. Enter the HELP command to obtain more information about the error.
The query contains an SQL error, indicated by SQLCODE. Enter the HELP command to obtain more information about the error.
You may not specify a form for this query because it is not a SELECT query.
The query exceeds the maximum length for SQL statements. See "Program Generator specifications" for the maximum length of an SQL statement.
An unexpected DB2 error occurred. This is usually indicative of an unrecoverable error.
The number of columns in the SELECT clause of the query must exactly match the number of columns referred to in the form. This message is also produced if you specify a form that makes use of column definitions.
An unexpected column type was received from DB2.
An error occurred while executed the specified SQL statement(s). Press F1 to see more detailed SQL error message text.
The skeleton code data set contains an invalid control code. Verify that the installation process was successful and complete.
The nesting of )IF's in the skeleton code data set is too great. The maximum nesting level is 10.
An )ELSEIF was found in the skeleton code data set without a preceding )IF.
An )ELSE was found in the skeleton code data set without a preceding )IF.
An )ENDIF was found in the skeleton code data set without a preceding )IF.
The end of the skeleton code data set was reached while processing was still within an )IF or )LOOP.
When reading data from or writing data to a sequential file, the LRECL of the DATAIN or DATAOUT DD must be at least as large as the total length of the columns in the SELECT clause and their associated null indicators.
The skeleton code data set contains an invalid construct. Verify that the installation process was successful and complete.
The skeleton code data set contains an invalid construct. Verify that the installation process was successful and complete.
An )ENDLOOP was found in the skeleton code data set without a preceding )LOOP.
An )ENDLOOP was found in the skeleton code data set without an )ENDIF to terminate an )IF within the loop.
The skeleton code data set contains an invalid construct. Verify that the installation process was successful and complete.
The specified option is not supported with the GENERAL or GENERAL WITH NULLS parameter style.
Enter the limit on processor time, in CPU service units, that a single invocation of the stored procedure can run. If you enter 0, no limit is applied.
You must enter a value for the specified field.
You must specify what result sets, if any, should be returned by the stored procedure. If you enter D, the data retrieved by the program is returned. If you enter R, the report generated by the program is returned. If you enter B, both the data and report are returned. If you enter N, no result sets are returned.
You must specify how the stored procedure will receive input parameters. If you enter D, the DB2SQL parameter style will be used. If you enter G, the GENERAL parameter style will be used. If you enter N, the GENERAL WITH NULLS parameter style will be used. See the documentation for the DB2 product you are using for more information about stored procedure parameter styles.
You must specify how the stored procedure will execute. Enter M to have the stored procedure execute as a main program or S to have it execute as a subroutine. See the documentation for the DB2 product you are using for more information about stored procedure program types.
The program was not registered due to your cancel command.
You must specify a report owner when creating a report.
You must specify a valid primary or secondary SQLID for the owner of the report. You may also specify an owner of the form T=tranid where tranid is a valid CICS transaction identifier.
You must specify a report name when creating a report.
You cannot register a program until you generate it.
T he program has been registered by creating a row in the Q.REPORTS table and (optionally) rows in the Q.REPORT_VARIABLES table. You can now run the program from the End User Facility.
You must enter a valid primary or secondary SQLID.
Choose one of the selection options listed on this panel.
No reports matching the specified owner and name were found in the database.
A report with the specified owner and name already exists in the database. Specify a different owner or name.
The report was not created due to your cancel command.
The report was not updated due to your cancel command.
The only acceptable values for this field are yes or no.
You must specify a program name for the report.
You can specify either the appropriate COBOL dialect or QMF (for a QMF report) as the language for the report. Choose the one desired for this registration.
You can specify either batch, TSO or CICS as the environment for the report. Choose the one desired for this registration.
You can specify TSO (the TSO attachment facility), CAF (the call attachment facility), or RRSAF (the Recoverable Resource Manager Services attachment facility) as the attachment facility for this report. Choose the one desired for this registration. This field is ignored for CICS programs, which always connect to DB2 via the CICS attachment facility.
You must enter an integer greater than or equal to -1 (greater than or equal to zero when specifying the LRECL of the report's host variable file).
Report names may not contain spaces.
The report was not dropped due to your cancel command.
Legal line commands when editing host variables are D (delete), I (insert), and R (repeat). Each may be followed by a number specifying a repetition factor.
You must specify a name for each of the report's variables.
You must specify a data type for each of the report's variables.
The specified report was created in the database.
The specified report was dropped from the database.
The specified report was updated in the database.
Batch programs must either print a report or present no report, or must be a data layer program.
TSO programs must either print a report, display a report, or do neither.
CICS programs must either print a report or display a report.
The program specified is an online print program and therefore cannot be invoked directly from a proc program.
You can generate programs that use either static or dynamic SQL. Select the type desired for this generation.
A CICS transaction identifier must be no more than four characters long.
You cannot enter a value in this field when registering a QMF report.
You must set environment to TSO when registering a QMF report. The End User Facility does not support QMF reports in CICS or in batch.
The variable name that you entered for the report is invalid. Variable names cannot contain the colon (:) or ampersand (&) characters.
You must enter the name of a partitioned data set for the EXEC library.
You must specify a name for this program/plan.
The name you specified cannot be used as a program/plan name.
Program Generator is now processing the report list row identified in the message text.
You must specify job cards and other JCL information to generate JCL to either compile or run a program.
Any changes that you made to the options in the current pop-up window have been discarded.
Enter H to generate a program which uses the HPO call attachment module (AACAF), or D to generate a program which uses the DB2 call attachment module (DSNALI).
Enter the page width (from 22 to 999) to use when generating the report.
Enter the page length (from 1 to 999, or CONT) to use when generating the report. Entering CONT specifies that the report should be generated without any page breaks.
You must enter a positive integer.
You can only register a report that runs a QMF query or procedure if you are running QMF Version 3 Release 1 or higher.
When generating a batch program from a query that does not use the SQL verb SELECT, you must specify that the program produces no report or is a data layer program.
When generating a TSO or CICS program from a query that does not use the SQL verb SELECT, you must specify that the program produces no report.
The specified program is a data layer program, and as such, cannot be called by a proc program.
Enter the number of REPORTnn DDs written by the report, or -1 if unknown or not applicable.
Enter the type of program.
QMF reports must be either print or display programs.
The specified type of options do not apply unless generating stored procedure programs. As a result, the display of the options pop-up window has been suppressed.
When generating a stored procedure program, you must specify that the program produces no report.
The specified option is not allowed with stored procedure programs.
The specified type of options do not apply unless generating stored procedure programs. As a result, the display of the options pop-up window has been suppressed.
Program Generator only supports stored procedures that run in a WLM-managed address space. DB2 requires that WLM stored procedures use the RRS attachment facility. You must enter R to select RRSAF.
Stored procedure programs do not have the capability to prompt the user for the action to take when saving data. As a result, you must enter R to replace any existing data or A to append to any existing data.