DB2 graphic QMF Version 8

RAAC messages

Messages that begin with RAAC are issued from Program Generator and appear on the message line on ISPF panels.

RAAC002E
Please select one of the options listed below
Explanation:

Choose one of the selection options listed on this panel.

RAAC003E
DB2 subsystem ID cannot be left blank
Explanation:

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.

RAAC004E
DB2 subsystem * not configured
Explanation:

You (or your administrator) must run the HPO Configuration Dialog for the specified DB2 subsystem.

RAAC005E
Unrecognized command
Explanation:

The command that you entered on the command line is not valid.

RAAC006E
Specify one of query, query and form, or procedure
RAAC007E
Specify only one of query, query and form, or procedure
Explanation:

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.

RAAC008E
Cannot specify form without query
Explanation:

A program cannot be generated from a form only. You must also specify a query.

RAAC009E
* flag must be "Y" (yes) or "N" (no)
Explanation:

The only acceptable values for the specified flag are yes or no.

RAAC010E
* data set name cannot be left blank
Explanation:

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.

RAAC011E
QMF requires RECFM = F and LRECL = 79
Explanation:

QMF requires that data sets into which queries and procedures are exported have RECFM = F and LRECL = 79.

RAAC012E
Member name not allowed for sequential data sets
Explanation:

You cannot specify a member name for the data set because it is a sequential data set.

RAAC013E
Member name has invalid syntax
Explanation:

The member name that you entered does not conform to PDS member naming rules.

RAAC014E
QMF requires RECFM = V and LRECL between * and 7290
Explanation:

QMF requires that data sets into which forms are exported have RECFM = V and LRECL between 161 and 7290.

RAAC015E
Data set must have DSORG = PS or PO
Explanation:

You must specify the name of a sequential data set or a partitioned data set.

RAAC016E
Profile key must be "T" (TSOID) or "P" (PRIMEID)
Explanation:

Your QMF profile can be keyed by either your TSO logon ID or by your primary DB2 authorization ID. Enter the desired value.

RAAC017E
Translation must be a valid QMF translation value or "*"
Explanation:

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.

RAAC018I
Default values not saved; Cancel request honored
Explanation:

Any changes that you made to the default parameter settings have been discarded.

RAAC019I
Default values will be saved
Explanation:

Any changes that you made to the default parameter settings will be saved in your ISPF profile.

RAAC020I
Previous QMF command not issued; Cancel request honored
Explanation:

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.

RAAC021E
Post-generation CLIST RAAPOSTG RC = *
Explanation:

The post-generation CLIST named RAAPOSTG did not run successfully.

RAAC022I
Starting QMF; Please wait...
Explanation:

Program Generator is starting a QMF session to export objects.

RAAC023I
Exporting object from QMF; Please wait...
Explanation:

QMF is exporting the query, form, or procedure. After the export finishes, the specified data set and member will contain the object.

RAAC024E
Previous export command failed; QMF error *
Explanation:

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.

RAAC025I
Previous QMF export command was successful
Explanation:

The previous export command was successful. The specified data set and member now contain the QMF object.

RAAC026E
* does not exist due to export failure
Explanation:

A previous export of the specified object failed (or was canceled). Consequently, you cannot process the report for that object.

RAAC027E
* data set does not exist, has been migrated, or is empty
Explanation:

The data set specified for the object cannot be found or is empty. Consequently, you cannot process the report for that object.

RAAC028E
* member * does not exist in PDS
Explanation:

The PDS member specified for the object cannot be found. Consequently, you cannot process the report for that object.

RAAC029I
Parsing procedure; Please wait...
Explanation:

Program Generator is parsing the procedure to build a list of the reports that it runs.

RAAC030E
Member name cannot be left blank for PDS
Explanation:

If you specify a partitioned data set, you must also specify a member name.

RAAC031E
Missing argument
Explanation:

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.

RAAC032E
Invalid argument
Explanation:

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.

RAAC033E
Too many arguments
Explanation:

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.

RAAC034E
Argument out of range
Explanation:

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.

RAAC035E
Plan name cannot be left blank
Explanation:

You must enter an 8 character (or less) name to be used as the plan name for the program.

RAAC036E
Plan name has invalid syntax
Explanation:

The plan name that you entered does not conform to plan naming rules.

RAAC037E
Review flag must be "B" (browse), "E" (edit), or "N" (none)
Explanation:

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.

RAAC038E
Browse failed; Data set or member is empty
Explanation:

The data set or member to be browsed contains no data.

RAAC039E
Browse failed; Member * not found
Explanation:

The member to be browsed does not exist.

RAAC040E
Browse failed; Severe error
Explanation:

The browse session failed due to a severe ISPF error.

RAAC041E
Edit failed; Member or data set in use
Explanation:

The data set or member is in use and therefore cannot be edited.

RAAC042E
Edit failed; Member * not found
Explanation:

The member to be edited does not exist.

RAAC043E
Edit failed; Severe error
Explanation:

The edit session failed due to a severe ISPF error.

RAAC044I
No variables found in query or form.I
Explanation:

Program Generator did not find any substitution variables in the query or the form, so there are none to edit. Normal processing will continue.

RAAC045I
Variable values not saved; Cancel request honored
Explanation:

Any variable value changes that you made were discarded.

RAAC046E
Dialect must be "1" (OS/VS COBOL), "2" (VS COBOL II), "3" (COBOL for MVS), or "4" (COBOL for OS/390)
Explanation:

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.

RAAC047E
Environment must be "B" (batch), "T" (TSO), "C" (CICS), or "S" (stored procedure)
Explanation:

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.

RAAC048E
Attachment Facility must be "T" (TSO attachment facility), "C" (call attachment facility), or "R" (Recoverable Resource Manager Services attachment facility)
Explanation:

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.

RAAC049E
Table name cannot be left blank
Explanation:

You must specify a table name when generating a program that will SAVE DATA to a DB2 table or ERASE a DB2 table.

RAAC050E
* must be "N" (no) with data layer program
Explanation:

The specified option is not allowed with data layer programs.

RAAC051E
Print program can only be specified with display program
Explanation:

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.

RAAC052E
Program must be generated before it can be edited
Explanation:

You cannot edit a program until it is generated.

RAAC053E
* flag must be "N" (no) with CICS program
Explanation:

The specified option is not allowed with CICS programs.

RAAC054E
Pre-generation CLIST RAAPREG RC = *
Explanation:

The pre-generation CLIST named RAAPREG did not run successfully.

RAAC055E
* flag must be "N" (no) with TSO or CICS print program
Explanation:

The specified option is not allowed with TSO or CICS print programs.

RAAC056I
Generation was bypassed; Cancel request honored
Explanation:

Program Generator bypassed the generation process due to your cancel command.

RAAC057I
Generating program; Please wait...
Explanation:

Program Generator is generating the program. When it is finished, the specified output data set and member will contain the source code.

RAAC058I
Program * has been generated
Explanation:

The program has been generated in the specified data set and member.

RAAC059E
Compile type must be P (prompted), N (non-prompted), or B (batch)
Explanation:

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.

RAAC060E
Dialect must be "1" (OS/VS COBOL), "2" (VS COBOL II), "3" (COBOL for MVS), or "4" (COBOL for OS/390)
Explanation:

You can compile OS/VS COBOL, VS COBOL II, COBOL for MVS, and COBOL for OS/390 programs using this facility.

RAAC061E
* flag must be "N" (no) with TSO print program
Explanation:

The specified option is not allowed with TSO print programs.

RAAC062E
Validate parameter must be "BIND" or "RUN"
Explanation:

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.

RAAC063E
Target data set must be a PDS
Explanation:

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.

RAAC064E
Error issuing LMINIT on data set
Explanation:

A severe ISPF error occurred when issuing the LMINIT service.

RAAC065E
Error issuing LMOPEN on data set
Explanation:

A severe ISPF error occurred when issuing the LMOPEN service.

RAAC066I
Program not compiled; Cancel request honored
Explanation:

The program was not compiled due to your cancel command.

RAAC067I
Invoking online compile; Please wait...
Explanation:

Program Generator is preparing the program online. If the process completes successfully, the program will be ready to run.

RAAC068E
Online compile error; RC = *
Explanation:

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.

RAAC069E
Load library must be a PDS
Explanation:

You can only run programs from a partitioned data set.

RAAC070E
Load library and program ID cannot both be left blank
Explanation:

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.

RAAC071E
Not all job cards may be left blank
Explanation:

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.

RAAC072E
Flag must be "E" (edit) or "S" (submit)
Explanation:

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.

RAAC073I
Program not run; Cancel request honored
Explanation:

The program was not run due to your cancel command.

RAAC074I
Running program; Please wait...
Explanation:

The program is running. Please wait for the first page of the report to be displayed.

RAAC075E
Run error; RC = *
Explanation:

An error occurred while running the program. The return code is included in this message.

RAAC076E
Member cannot be specified with temporary data set
Explanation:

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.

RAAC077E
Program name has invalid syntax
Explanation:

The program name that you entered does not conform to program naming rules.

RAAC078E
Environment must be "B" (batch) or "T" (TSO)
Explanation:

You can only run batch or TSO programs using this facility.

RAAC079E
* flag must be "Y" (yes) with TSO print program
Explanation:

The specified option is required with TSO print programs.

RAAC080E
Print program can only be specified if Write flag is "Y"
Explanation:

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.

RAAC081I
JCL submitted
Explanation:

Program Generator has submitted JCL to either compile or run a program.

RAAC082E
Error submitting JCL
Explanation:

An error occurred while submitting JCL to either compile or run a program. Additional information may be written to the terminal by TSO.

RAAC083E
Print program can only be specified if HPO/Runtime flag is "N"
Explanation:

TSO display programs that have a corresponding print program cannot use the HPO/Runtime feature.

RAAC084E
Dialect must be blank, "1" (OS/VS COBOL), "2" (VS COBOL II), "3" (COBOL for MVS), or "4" (COBOL for OS/390)
Explanation:

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).

RAAC085E
Environment must be "B" (batch) or "T" (TSO) with non-SELECT SQL
Explanation:

Program Generator does not support non-SELECT SQL in CICS programs.

RAAC086E
SQL type must be "S" (static) with data layer program
Explanation:

Data layer programs are required to use static SQL.

RAAC087E
Illegal character (') in options
Explanation:

The single quote character (') is not allowed in compile or link edit options. Remove the character.

RAAC088E
Program * not generated yet
Explanation:

You must generate the program in the specified row of the report list before you can generate a proc program that runs it.

RAAC089E
Program * has different dialect than proc program
Explanation:

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.

RAAC090E
Program * has different environment than proc program
Explanation:

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.

RAAC091E
Program * uses different attachment facility than proc program
Explanation:

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.

RAAC092E
Temporary data set only allowed when exporting
Explanation:

You cannot specify a temporary data set (*TEMP) for a query, form, or procedure data set unless the object is to be exported.

RAAC093E
Temporary data set not allowed in this field
Explanation:

You cannot specify a temporary data set (*TEMP) for the data set entered in this field.

RAAC094E
Error creating temporary data set
Explanation:

An error occurred while creating a temporary data set. Additional error messages may be written to the terminal.

RAAC095E
No matching objects found
Explanation:

No objects matching the specified owner and name were found in the database.

RAAC096E
Select one and only one object
Explanation:

You must select one and only one object from each displayed column.

RAAC097E
Use "S" to select an object
Explanation:

The character entered in the selection field was not recognized.

RAAC098E
JCL not generated; Cancel request honored
Explanation:

The JCL was not generated due to your cancel command.

RAAC099E
DBRM library must be a PDS
Explanation:

You must specify a partitioned data set name for the DBRM library. Sequential data sets are not allowed.

RAAC100E
Unexpected internal error *
Explanation:

An unexpected error was encountered.

RAAC101E
Memory exhausted
Explanation:

Expand your region size.

RAAC102E
Data set does not exist or has been archived/migrated
Explanation:

The specified data set could not be found. You must specify the name of a data set that exists and is catalogued.

RAAC103E
Cannot specify member name in this field
Explanation:

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.

RAAC104E
Error connecting to DB2 * (RC=* REASON=*)
Explanation:

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.

RAAC105E
Could not open data set *
Explanation:

Program Generator could not open the specified data set. Verify that the data set exists, that you have permission to read it, etc.

RAAC106E
Error reading data set *
Explanation:

An error occurred while reading the specified data set. Verify that the data set exists, that you have permission to read it, etc.

RAAC107E
Error writing data set *
Explanation:

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.

RAAC108E
Procedures with logic are not supported
Explanation:

You may only specify a linear procedure as input. Procedures with logic are not supported.

RAAC109E
Qualified object name too long
Explanation:

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.

RAAC110I
Too many reports in procedure
Explanation:

The specified procedure referred to too many reports. See "Program Generator specifications" for the maximum number of reports supported.

RAAC111E
Too many variables in query
Explanation:

The specified query referred to too many substitution variables. See "Program Generator specifications" for the maximum number of substitution variables supported.

RAAC112E
No reports in procedure
Explanation:

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.

RAAC113E
SQL error reading Q.OBJECT_DIRECTORY
Explanation:

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.

RAAC114E
SQL error accessing registration tables
Explanation:

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.

RAAC115E
SQL error retrieving current SQLID
Explanation:

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.

RAAC116E
Error opening plan * (RC=* REASON=*)
Explanation:

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.

RAAC117E
Error connecting to location; SQLCODE = *
Explanation:

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.

RAAC118E
Error allocating RAAOUT DD to *
Explanation:

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.

RAAC119E
Disposition must be "OLD", "SHR", or "MOD"
Explanation:

You must specify the disposition to use for the output data set when generating source code.

RAAC120E
Error disconnecting from DB2 * (RC=* REASON=*)
Explanation:

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.

RAAC121E
Bind type must be 1, 2, 3 or 4
Explanation:

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.

RAAC122E
Collection ID must be specified when binding a package
Explanation:

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.

RAAC123E
Collection ID contains invalid characters
Explanation:

The specified collection ID has invalid syntax.

RAAC124E
All reports must have packages bound to specify this bind type
Explanation:

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.

RAAC125E
Save data action must be "R" (replace), "A" (append), or "P" (prompt)
Explanation:

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.

RAAC126E
Save data SQL type must be "S" (static) or "D" (dynamic)
Explanation:

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.

RAAC127E
Host variable format must be "T" (tabular) or "C" (columnar)
Explanation:

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).

RAAC128I
* options do not apply to non-SELECT queries
Explanation:

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.

RAAC129I
* options do not apply to data layer programs
Explanation:

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.

RAAC130E
Host variable DD must be "H" (HOSTVARS) or "P" (PROCVARS)
Explanation:

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.

RAAC131I
* options apply only to batch programs which use host variables
Explanation:

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.

RAAC132E
Host variable values not accepted; Cancel request honored
Explanation:

Your request to cancel entry of host variable values has been accepted.

RAAC133I
Options set; Press Enter to generate program
Explanation:

All of the selected options pop-up windows have been displayed. Press Enter to generate the program.

RAAC134E
Save data SQL type must be "D" (dynamic) when table space is *USERPROF
Explanation:

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.

RAAC135E
Attachment facility must be "T" (TSO attachment facility) or "C" (call attachment facility) for TSO program
Explanation:

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.

RAAC136E
Attachment facility must be "T", "TSO", "C", or "CAF" for TSO program
Explanation:

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.

RAAC137I
* options apply only to data layer programs
Explanation:

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.

RAAC138E
Data layer programs can only be generated from queries which can be parsed
Explanation:

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.

RAAC139E
Dialect must be "2" (VS COBOL II), "3" (COBOL for MVS), or "4" (COBOL for OS/390) with a data layer program
Explanation:

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.

RAAC200E
Token too long at line * of *
Explanation:

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.

RAAC201E
Invalid quoted value at line * of *
Explanation:

An invalid token was found while parsing the procedure data set. Verify that the data set contains a valid linear procedure.

RAAC202E
Unbound variable at line * of *
Explanation:

An unbound variable was found while parsing the procedure data set. Verify the procedure in the data set, possibly replacing variables with constants.

RAAC203E
Invalid DSN in IMPORT at line * of *
Explanation:

The data set specified in the IMPORT command in the procedure data set is invalid.

RAAC204E
Syntax error at line * of *
Explanation:

A syntax error was found while parsing the procedure data set.

RAAC205E
Variable value too long at line * of *
Explanation:

Variable values must be 55 characters or less.

RAAC206E
Missing variable value at line * of *
Explanation:

Verify the specified procedure data set. Make sure that variable assignments are complete. Do not leave any assignments incomplete, such as RUN QUERY (FORM=.

RAAC207E
Integer value out of range at line * of *
RAAC208E
Bad integer value at line * of *
Explanation:

A positive integer value was expected. A non-integer or an integer that is too large was found.

RAAC209E
No query name for RUN at line * of *
Explanation:

A RUN command was found that did not reference a query name or QUERY.

RAAC210E
Bad value for DATETIME at line * of *
Explanation:

An invalid value for the DATETIME parameter of the PRINT command was found. See QMF Reference for legal values.

RAAC211E
Bad value for PAGENO at line * of *
Explanation:

An invalid value for the PAGENO parameter of the PRINT command was found. See QMF Reference for legal values.

RAAC212E
Unexpected continuation at line * of *
Explanation:

An illegal continuation line was found while parsing the procedure data set.

RAAC213E
Command too long at line * of *
Explanation:

A command was found while parsing the procedure data set that exceeds the maximum procedure command length.

RAAC214E
Variable name is too long
Explanation:

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.

RAAC215E
Invalid length for variable * with * type
Explanation:

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.

RAAC216E
Unrecognized type * for variable *
Explanation:

Valid data types are INTEGER, SMALLINT, DECIMAL(p,s), DECIMAL(p), DECIMAL, FLOAT, CHAR(n), VARCHAR(n), DATE, TIME, and TIMESTAMP.

RAAC217E
Empty variable name
Explanation:

When specifying a host variable name, enter a colon (:) followed by the variable name. For example,:VAR1.

RAAC218E
Variable naming conflict
Explanation:

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.

RAAC219E
Missing variable type
Explanation:

You must supply a data type for each host variable specified.

RAAC220E
Error opening RAAVARS DD
Explanation:

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.

RAAC221E
Invalid record in RAAVARS DD
Explanation:

A record read from the RAAVARS DD had an invalid format. Each record must be of the form &VARNAME=VARVALUE

RAAC222E
Column does not exist in table
Explanation:

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.

RAAC222E
Column does not exist in table
Explanation:

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.

RAAC223E
Unable to resolve host variable name conflicts
Explanation:

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.

RAAC224E
Host variable name too long
Explanation:

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.

RAAC225E
Query cannot be parsed; host variables matched to columns are not allowed
Explanation:

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.

RAAC226E
Data set allocation error
Explanation:

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.

RAAC227I
Data set allocated
Explanation:

The specified data set has been allocated.

RAAC228E
Space units must be "C" (cylinders), "T" (tracks), or "B" (blocks)
Explanation:

You must select the units in which the primary and secondary space allocation for the data set will be expressed.

RAAC229E
Primary space quantity must be a positive integer
Explanation:

You must enter a valid number greater than zero for the primary space quantity.

RAAC230E
Directory blocks must be a positive integer or zero
Explanation:

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).

RAAC232I
Data set not allocated; Cancel request honored
Explanation:

The data set has not been allocated.

RAAC233E
Secondary space quantity must be a positive integer or zero
Explanation:

You must enter a valid number greater than or equal to zero for the secondary space quantity.

RAAC234E
Directory blocks must be a positive integer
Explanation:

You must enter a valid number greater than zero for the number of directory blocks.

RAAC235I
Host variable values accepted; Press Enter to continue
Explanation:

The values that you entered on the Enter Host Variable Values pop-up window have been saved. Press Enter to continue generating the JCL.

RAAC236E
Data set must have DSORG = PO
Explanation:

You must specify the name of a partitioned data set.

RAAC237E
Member name cannot be specified without data set name
Explanation:

In order to specify a member name in this field, you must also specify a data set name in the preceding field.

RAAC238E
* flag must be "N" with stored procedure program
Explanation:

The specified option is not allowed with stored procedure programs.

RAAC239I
CREATE PROCEDURE statement executed successfully
Explanation:

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.

RAAC301E
Exported form has warnings or errors
Explanation:

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.

RAAC302E
Exported form is incomplete
RAAC303E
Invalid record type * at record * of *
RAAC304E
Unexpected T record at record * of *
RAAC305E
Invalid T record at record * of *
RAAC306E
Unexpected V record at record * of *
RAAC307E
Invalid V record at record * of *
RAAC308E
Unexpected R record at record * of *
RAAC309E
Error reading column info at record * of *
RAAC310E
Invalid form value at record * of *
RAAC311E
Invalid BREAK usage code at record * of *
Explanation:

The specified form data set does not contain a valid QMF form.

RAAC312E
Environment must be "B" (batch) or "T" (TSO) for user edit codes
Explanation:

Program Generator does not support user edit routines (Uxxxx and Vxxxx) with CICS programs.

RAAC313E
HPO/Runtime must be "Y" (yes) for * usage code
Explanation:

Program Generator does not support the ACROSS and CALC usage codes with standalone programs.

RAAC314E
Invalid form variable at record * of *
Explanation:

The specified form data set does not contain a valid QMF form.

RAAC315E
Host variables not supported in form text
Explanation:

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.

RAAC316E
Unsupported use of form detail variation
Explanation:

The exported form contains form detail variation, which Program Generator does not support.

RAAC317E
Environment must be "B" (batch) or "T" (TSO) for * usage code
Explanation:

Program Generator does not support the xPCT usage codes with CICS programs.

RAAC318E
Diag Parameters must be "1" (none), "2" (error message), or "3" (error and SQL messages)
Explanation:

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.

RAAC400E
Unexpected SQL parsing error
Explanation:

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).

RAAC403E
SQL parsing error: token too long
Explanation:

A token which exceeds the maximum token length was found while parsing the query.

RAAC405E
SQL parsing error: invalid SQL object name
RAAC406E
SQL parsing error: SQL object name too long
RAAC407E
SQL parsing error: "*" invalid as SQL object name
Explanation:

An invalid name was found while parsing the query.

RAAC408E
SQL parsing error: invalid hexadecimal string constant
Explanation:

An invalid hexadecimal string constant (e.g., x'40F') was found while parsing the query.

RAAC410E
Security must be "D" (DB2), "U" (User), or "F" (Definer)
Explanation:

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.

RAAC411E
Special Registers must be "I" (Inherit) or "D" (Default)
Explanation:

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.

RAAC412E
SQL parsing error: invalid lexical token
Explanation:

Invalid characters were found while parsing the query.

RAAC413E
Program in row * with * must be generated first
Explanation:

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.

RAAC414E
ASU Time Limit must be numeric
Explanation:

The ASU time limit that you specify for the stored procedure must be numeric. If you enter 0, no limit is applied.

RAAC415E
Bind Type must be "1" (package) or "4" (no bind) with stored procedure program
Explanation:

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.

RAAC416E
"3" (COBOL for MVS) or "4" (COBOL for OS/390) with stored procedure program
Explanation:

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.

RAAC417E
SQL parsing error: expected *
Explanation:

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.

RAAC420E
SQL parsing error: the number of columns specified in the correlation clause does not match the number of columns in the table
Explanation:

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.

RAAC421E
SQL parsing error: the column * was found in more than one table
Explanation:

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.

RAAC422E
SQL parsing error: the FETCH FIRST n ROWS clause was specified more than once
Explanation:

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.

RAAC423E
SQL parsing error: the FOR FETCH ONLY clause was specified more than once
Explanation:

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.

RAAC424E
SQL parsing error: the FOR UPDATE clause was specified more than once
Explanation:

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.

RAAC425E
SQL parsing error: the QUERYNO clause was specified more than once
Explanation:

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.

RAAC426E
SQL parsing error: the WITH clause was specified more than once
Explanation:

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.

RAAC427E
SQL parsing error: the WITH HOLD clause was specified more than once
Explanation:

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.

RAAC428E
SQL parsing error: the WITH RETURN clause was specified more than once
Explanation:

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.

RAAC429E
SQL parsing error: the OPTIMIZE FOR clause was specified more than once
Explanation:

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.

RAAC430E
SQL parsing error: no function by the name * having compatible arguments was found in the function path
Explanation:

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.

RAAC431E
SQL parsing error: the FOR UPDATE and ORDER BY clauses were both specified
Explanation:

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.

RAAC432E
SQL parsing error: an internal error occurred at line *
Explanation:

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.

RAAC433E
SQL parsing error: invalid parameters to arithmetic operator
Explanation:

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.

RAAC434E
SQL parsing error: * is an unrecognized data type
Explanation:

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.

RAAC435E
SQL parsing error: invalid parameters to CONCAT operator
Explanation:

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.

RAAC436E
SQL parsing error: incompatible types in expression list
Explanation:

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.

RAAC437E
SQL parsing error: invalid identifier *
Explanation:

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.

RAAC438E
SQL parsing error: invalid scalar function parameter
Explanation:

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.

RAAC439E
SQL parsing error: invalid use of parameter markers
Explanation:

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.

RAAC440E
SQL parsing error: invalid use of "*"
Explanation:

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.

RAAC441E
SQL parsing error: an invalid lexical token was found beginning at "*"
Explanation:

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.

RAAC442E
SQL parsing error: labeled duration missing value
Explanation:

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.

RAAC443E
SQL parsing error: no SELECT clause was found
Explanation:

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.

RAAC444E
SQL parsing error: no subselect was found in a full select
Explanation:

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.

RAAC445E
SQL parsing error: parameter markers used on both sides of operator
Explanation:

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.

RAAC446E
SQL parsing error: column * was not found in any table
Explanation:

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.

RAAC447E
SQL parsing error: the token * is unexpected; expected tokens may include: *
Explanation:

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.

RAAC448E
SQL parsing error: the token is unexpected; expected tokens may include: *
Explanation:

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.

RAAC449E
SQL parsing error: a column in the ORDER BY clause was not found in any table
Explanation:

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.

RAAC450E
SQL parsing error: table locators are not supported
Explanation:

An error has occurred while parsing the input query. The use of table locators was encountered, which is not supported by Program Generator.

RAAC451E
SQL parsing error: three-part table names are not supported
Explanation:

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.

RAAC452E
SQL parsing error: row value expression invalid in the current context
Explanation:

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.

RAAC453E
SQL parsing error: the FOR UPDATE and FOR FETCH ONLY clauses were both specified
Explanation:

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.

RAAC454E
SQL parsing error: transition tables are unsupported
Explanation:

An error has occurred while parsing the input query. The use of transition tables was encountered, which is not supported by Program Generator.

RAAC455E
SQL parsing error: unrecognized statement type
Explanation:

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.

RAAC457E
Host variable exit * return code = *
Explanation:

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.

RAAC458E
Unable to map host variables due to previous query parsing error
Explanation:

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.

RAAC459E
Column exit * return code *
Explanation:

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.

RAAC460E
Unable to map column names due to previous query parsing error
Explanation:

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.

RAAC461E
Table exit * return code *
Explanation:

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.

RAAC462E
Exit module * could not be loaded
Explanation:

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.

RAAC463E
SQL parsing error: SQL code *
Explanation:

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.

RAAC464E
SQL parsing error: the ON ROLLBACK RETAIN CURSORS clause was specified more than once
Explanation:

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.

RAAC465E
SQL parsing error: the ON ROLLBACK RETAIN LOCKS clause was specified more than once
Explanation:

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.

RAAC500E
Error preparing SQL statement; SQLCODE = *
Explanation:

The query contains an SQL error, indicated by SQLCODE. Enter the HELP command to obtain more information about the error.

RAAC501E
Error describing SQL statement; SQLCODE = *
Explanation:

The query contains an SQL error, indicated by SQLCODE. Enter the HELP command to obtain more information about the error.

RAAC502E
SQL statement not SELECT; Form not allowed
Explanation:

You may not specify a form for this query because it is not a SELECT query.

RAAC503E
SQL statement too long
Explanation:

The query exceeds the maximum length for SQL statements. See "Program Generator specifications" for the maximum length of an SQL statement.

RAAC504E
Invalid column count after DESCRIBE
Explanation:

An unexpected DB2 error occurred. This is usually indicative of an unrecoverable error.

RAAC505E
Number of columns in form inconsistent with query
Explanation:

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.

RAAC506E
Unrecognized column type * from DESCRIBE
Explanation:

An unexpected column type was received from DB2.

RAAC507E
Error executing SQL statement; SQLCODE = *
Explanation:

An error occurred while executed the specified SQL statement(s). Press F1 to see more detailed SQL error message text.

RAAC600E
Invalid control statement at line * of *
Explanation:

The skeleton code data set contains an invalid control code. Verify that the installation process was successful and complete.

RAAC601E
Too many )IF's at line * of *
Explanation:

The nesting of )IF's in the skeleton code data set is too great. The maximum nesting level is 10.

RAAC602E
Unexpected )ELSEIF at line * of *
Explanation:

An )ELSEIF was found in the skeleton code data set without a preceding )IF.

RAAC603E
Unexpected )ELSE at line * of *
Explanation:

An )ELSE was found in the skeleton code data set without a preceding )IF.

RAAC604E
Unexpected )ENDIF at line * of *
Explanation:

An )ENDIF was found in the skeleton code data set without a preceding )IF.

RAAC605E
Unexpected EOF in *
Explanation:

The end of the skeleton code data set was reached while processing was still within an )IF or )LOOP.

RAAC606E
Specified LRECL is too small; Must be at least *
Explanation:

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.

RAAC607E
Illegal nested )COPY at line * of *
Explanation:

The skeleton code data set contains an invalid construct. Verify that the installation process was successful and complete.

RAAC608E
Loop too long at line * of *
RAAC609E
Illegal nested loop at line * of *
Explanation:

The skeleton code data set contains an invalid construct. Verify that the installation process was successful and complete.

RAAC610E
Unexpected )ENDLOOP at line * of *
Explanation:

An )ENDLOOP was found in the skeleton code data set without a preceding )LOOP.

RAAC611E
Unterminated )IF in loop at line * of *
Explanation:

An )ENDLOOP was found in the skeleton code data set without an )ENDIF to terminate an )IF within the loop.

RAAC612E
Unrecognized )COPY target at line * of *
Explanation:

The skeleton code data set contains an invalid construct. Verify that the installation process was successful and complete.

RAAC613E
* flag must be "N" (no) with parameter style "G" (GENERAL) or "N" (GENERAL WITH NULLS)
Explanation:

The specified option is not supported with the GENERAL or GENERAL WITH NULLS parameter style.

RAAC614E
ASU time limit must be a positive integer, or 0 to specify no limit
Explanation:

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.

RAAC616E
* cannot be left blank
Explanation:

You must enter a value for the specified field.

RAAC617E
Result Sets must be "D" (data), "R" (report), "B" (both), or "N" (neither)
Explanation:

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.

RAAC618E
Parameter Style must be "D" (DB2SQL), "G" (GENERAL), or "N" (GENERAL WITH NULLS)
Explanation:

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.

RAAC619E
Program Type must be "M" (main) or "S" (subroutine)
Explanation:

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.

RAAC700E
Program not registered; Cancel request honored
Explanation:

The program was not registered due to your cancel command.

RAAC701E
Report owner cannot be left blank
Explanation:

You must specify a report owner when creating a report.

RAAC702E
Report owner must be valid SQLID
Explanation:

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.

RAAC703E
Report name cannot be left blank
Explanation:

You must specify a report name when creating a report.

RAAC704E
Program must be generated before it can be registered
Explanation:

You cannot register a program until you generate it.

RAAC705I
Program has been registered
Explanation:

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.

RAAC706E
Invalid SQLID
Explanation:

You must enter a valid primary or secondary SQLID.

RAAC707E
Please select one of the actions listed below
Explanation:

Choose one of the selection options listed on this panel.

RAAC709E
No matching report(s)
Explanation:

No reports matching the specified owner and name were found in the database.

RAAC710E
Report already exists
Explanation:

A report with the specified owner and name already exists in the database. Specify a different owner or name.

RAAC711I
Report not created; Cancel request honored
Explanation:

The report was not created due to your cancel command.

RAAC712I
Report not updated; Cancel request honored
Explanation:

The report was not updated due to your cancel command.

RAAC713E
Field must be "YES" or "NO"
Explanation:

The only acceptable values for this field are yes or no.

RAAC714E
Program name cannot be left blank
Explanation:

You must specify a program name for the report.

RAAC715E
Dialect must be "1", "OS/VS COBOL", "2", "VS COBOL II", "3", "COBOL for MVS", "4", "COBOL for OS/390", "Q", or "QMF"
Explanation:

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.

RAAC716E
Environment must be "B", "BATCH", "T", "TSO", "C", or "CICS"
Explanation:

You can specify either batch, TSO or CICS as the environment for the report. Choose the one desired for this registration.

RAAC717E
Attachment facility must be "T", "TSO", "C", "CAF", "R", or "RRSAF"
Explanation:

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.

RAAC718E
Invalid LRECL value
Explanation:

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).

RAAC719E
Invalid character in report name
Explanation:

Report names may not contain spaces.

RAAC720I
Report not dropped; Cancel request honored
Explanation:

The report was not dropped due to your cancel command.

RAAC721E
Unrecognized line command
Explanation:

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.

RAAC722E
Variable name cannot be left blank
Explanation:

You must specify a name for each of the report's variables.

RAAC723E
Variable type cannot be left blank
Explanation:

You must specify a data type for each of the report's variables.

RAAC724I
Report created
Explanation:

The specified report was created in the database.

RAAC725I
Report dropped
Explanation:

The specified report was dropped from the database.

RAAC726I
Report updated
Explanation:

The specified report was updated in the database.

RAAC727E
Program type must be "P" (print), "N" (no report), or "L" (data layer) with batch program
Explanation:

Batch programs must either print a report or present no report, or must be a data layer program.

RAAC728E
Program type must be "P" (print), "D" (display), or "N" (no report) with TSO program
Explanation:

TSO programs must either print a report, display a report, or do neither.

RAAC729E
Program type must be "P" (print), "D" (display), or "N" (no report) with CICS program
Explanation:

CICS programs must either print a report or display a report.

RAAC730E
Program * is online print program
Explanation:

The program specified is an online print program and therefore cannot be invoked directly from a proc program.

RAAC731E
SQL type must be "S" (static) or "D" (dynamic)
Explanation:

You can generate programs that use either static or dynamic SQL. Select the type desired for this generation.

RAAC732E
Invalid transaction identifier
Explanation:

A CICS transaction identifier must be no more than four characters long.

RAAC733E
Field must be left blank when dialect is "QMF"
Explanation:

You cannot enter a value in this field when registering a QMF report.

RAAC734E
Environment must be "TSO" when dialect is "QMF"
Explanation:

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.

RAAC735E
Invalid variable name
Explanation:

The variable name that you entered for the report is invalid. Variable names cannot contain the colon (:) or ampersand (&) characters.

RAAC736E
EXEC library must be a PDS
Explanation:

You must enter the name of a partitioned data set for the EXEC library.

RAAC737E
Program/plan name cannot be left blank
Explanation:

You must specify a name for this program/plan.

RAAC738E
Program/plan name has invalid syntax
Explanation:

The name you specified cannot be used as a program/plan name.

RAAC739I
Processing report list row *
Explanation:

Program Generator is now processing the report list row identified in the message text.

RAAC740I
Specify batch job information for *
Explanation:

You must specify job cards and other JCL information to generate JCL to either compile or run a program.

RAAC741I
Options not saved; Cancel request honored
Explanation:

Any changes that you made to the options in the current pop-up window have been discarded.

RAAC743E
CAF module usage must be "H" (HPO CAF) or "D" (DB2 CAF)
Explanation:

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).

RAAC744E
Report width must be between 22 and 999, inclusive
Explanation:

Enter the page width (from 22 to 999) to use when generating the report.

RAAC745E
Report length must be "CONT" or between 1 and 999, inclusive
Explanation:

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.

RAAC746E
LRECL must be a positive integer
Explanation:

You must enter a positive integer.

RAAC747E
Registration of QMF reports only supported with QMF 3.1 and higher
Explanation:

You can only register a report that runs a QMF query or procedure if you are running QMF Version 3 Release 1 or higher.

RAAC748E
Program type must be "N" (no report) or "L" (data layer) for batch program with non-SELECT query
Explanation:

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.

RAAC749E
Program type must be "N" (no report) for TSO or CICS program with non-SELECT query
Explanation:

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.

RAAC750E
Program * is a data layer program
Explanation:

The specified program is a data layer program, and as such, cannot be called by a proc program.

RAAC751E
Number of report files must be an integer greater than or equal to -1
Explanation:

Enter the number of REPORTnn DDs written by the report, or -1 if unknown or not applicable.

RAAC752E
Program type must be "P" (print), "D" (display), "N" (no report), "L" (data layer), or "R" (proc)
Explanation:

Enter the type of program.

RAAC753E
Program type must be "P" (print) or "D" (display) when dialect is "QMF"
Explanation:

QMF reports must be either print or display programs.

RAAC754I
* options apply only to stored procedure programs
Explanation:

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.

RAAC755E
Program Type must be "N" (no report) with stored procedure programs
Explanation:

When generating a stored procedure program, you must specify that the program produces no report.

RAAC756E
* flag must be "N" (no) with stored procedure program
Explanation:

The specified option is not allowed with stored procedure programs.

RAAC757I
* options apply only to stored procedure programs
Explanation:

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.

RAAC758E
Attachment Facility must be "R" (RRSAF) with stored procedure program
Explanation:

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.

RAAC759E
Action must be "R" (replace) or "A" (append) with stored procedure program
Explanation:

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.


Go to the previous page Go to the next page

Downloads | Library | Support | Support Policy | Terms of use | Feedback
Copyright IBM Corporation 1982,2004 Copyright IBM Corporation 1982, 2004
timestamp Last updated: March, 2004