FM/Db2 messages

Shows the version and release information for File Manager.

Shows the full component name for File Manager.

Shows the abbreviated component name for File Manager.

Shows the short component name for File Manager.

Shows the product name and copyright information for File Manager, Db2® component.

An ISPF error was encountered issuing a PQUERY service for panel name panel name.

FM/Db2 attempted to access the Db2® catalog table Db2 catalog table name. The access failed because Db2 catalog table name does not exist.

FM/Db2 attempted to access the Db2® catalog table Db2 catalog table name. The access failed. Access to Db2 catalog table name is essential to complete the current FM/Db2 function.

FM/Db2 attempted to access column column name of Db2® catalog table Db2 catalog table name. The access failed. SELECT access to column column name of Db2 catalog table name is essential to complete the current FM/Db2 function.

Auditing is required, browse functions are subject to audit. Auditing options are specified in either the FMN2POPT module, or externally using a security product such as RACF®. See See File Manager for z/OS® Customization Guide for more information. This message is displayed on the "Db2® connection Information" pop-up panel.

Auditing is required, browse functions are not subject to audit. Auditing options are specified in either the FMN2POPT module or externally, using a security product such as RACF®. See See File Manager for z/OS® Customization Guide for more information. This message is displayed on the "Db2® connection Information" pop-up panel.

Auditing is required, and auditing records are written to SMF, browse functions are subject to audit. Auditing options are specified in either the FMN2POPT module or externally, using a security product such as RACF®. See See File Manager for z/OS® Customization Guide for more information. This message is displayed on the "Db2® connection Information" pop-up panel.

Auditing is required, and auditing records are written to SMF, browse functions are not subject to audit. Auditing options are specified in either the FMN2POPT module or externally, using a security product such as RACF®. See See File Manager for z/OS® Customization Guide for more information. This message is displayed on the "Db2® connection Information" pop-up panel.

FM/Db2 component does not write audit records. Auditing options are specified in either the FMN2POPT module, or externally using a security product such as RACF®. See See File Manager for z/OS® Customization Guide for more information. This message is displayed on the "Db2® connection Information" pop-up panel.

Auditing within FM/Db2 is controlled using SAF rules, defined using a security product such as RACF®. Auditing options are specified in either the FMN2POPT module or externally, using a security product such as RACF®. See See File Manager for z/OS® Customization Guide for more information. This message is displayed on the "Db2® connection Information" pop-up panel.

Auditing within FM/Db2 is controlled using SAF rules, defined using a security product such as RACF®. These rules specifically prevent the writing of audit records by FM/Db2. Auditing options are specified in either the FMN2POPT module or externally, using a security product such as RACF®. See See File Manager for z/OS® Customization Guide for more information. This message is displayed on the "Db2® connection Information" pop-up panel.

Demand auditing is in effect, browse functions are subject to audit. Demand auditing means that an audit report is automatically printed at the end of the current editor session. Auditing options are specified in either the FMN2POPT module or externally, using a security product such as RACF®. See See File Manager for z/OS® Customization Guide for more information. This message is displayed on the"Db2® connection Information" pop-up panel.

Demand auditing is in effect, browse functions are not subject to audit. Demand auditing means that an audit report is automatically printed at the end of the current editor session. Auditing options are specified in either the FMN2POPT module, or externally using a security product such as RACF®. See See File Manager for z/OS® Customization Guide for more information. This message is displayed on the "Db2® connection Information" pop-up panel.

Auditing is optional and initially off, browse functions are subject to audit. Auditing options are specified in either the FMN2POPT module, or externally using a security product such as RACF®. See See File Manager for z/OS® Customization Guide for more information. This message is displayed on the"Db2® connection Information" pop-up panel.

Auditing is optional and initially off, browse functions are not subject to audit. This message is displayed on the "Db2® connection Information" pop-up panel.

Auditing is optional and the current value is set based on the user ISPF profile. Browse functions are subject to audit. Auditing options are specified in either the FMN2POPT module or externally, using a security product such as RACF®. See See File Manager for z/OS® Customization Guide for more information. This message is displayed on the "Db2® connection Information" pop-up panel.

Auditing is optional and the current value is set based on the user ISPF profile. Browse functions are not subject to audit. Auditing options are specified in either the FMN2POPT module, or externally using a security product such as RACF®. See See File Manager for z/OS® Customization Guide for more information. This message is displayed on the "Db2® connection Information" pop-up panel.

Auditing is optional and audit records are written to SMF. The audit option is initially off, and browse functions are subject to audit. Auditing options are specified in either the FMN2POPT module, or externally using a security product such as RACF®. See See File Manager for z/OS® Customization Guide for more information. This message is displayed on the "Db2® connection Information" pop-up panel.

Auditing is optional and audit records are written to SMF. The audit option is initially off, browse functions are not subject to audit. Auditing options are specified in either the FMN2POPT module, or externally using a security product such as RACF®. See See File Manager for z/OS® Customization Guide for more information. This message is displayed on the "Db2® connection Information" pop-up panel.

Auditing is optional and audit records are written to SMF. The current value for the audit option is set based on the user ISPF profile, browse functions are subject to audit. Auditing options are specified in either the FMN2POPT module, or externally using a security product such as RACF®. See See File Manager for z/OS® Customization Guide for more information. This message is displayed on the "Db2® connection Information" pop-up panel.

Auditing is optional and audit records are written to SMF. The current value for the audit option is set based on the user ISPF profile, browse functions are not subject to audit. Auditing options are specified in either the FMN2POPT module, or externally using a security product such as RACF®. See See File Manager for z/OS® Customization Guide for more information. This message is displayed on the "Db2® connection Information" pop-up panel.

Demand auditing is in effect, audit records are written to SMF, browse functions are subject to audit. Demand auditing means that an audit report is automatically printed at the end of the current editor session. Auditing options are specified in either the FMN2POPT module, or externally using a security product such as RACF®. See See File Manager for z/OS® Customization Guide for more information. This message is displayed on the "Db2® connection Information" pop-up panel.

Demand auditing is in effect, audit records are written to SMF, browse functions are not subject to audit. Demand auditing means that an audit report is automatically printed at the end of the current editor session. Auditing options are specified in either the FMN2POPT module, or externally using a security product such as RACF®. See See File Manager for z/OS® Customization Guide for more information. This message is displayed on the "Db2® connection Information" pop-up panel.

A Db2® abend occurred during processing for the current function. The File Manager subtask responsible for connection to Db2® has been terminated, and a new subtask established. Any uncommitted changes made by the FM/Db2 function prior to the abend will have been backed out.

This message is issued when a Db2® object name has been entered on a function entry panel, but Db2® reports that the object name does not exist. Db2® SSID is the name of the currently connected Db2® sub-system. The function cannot be processed until the reason for the error is determined and corrected.

This message is issued when a Db2® location value has been entered on a function entry panel, but Db2® reports that the location cannot be found. Location is the name of the location value that could not be located. The function cannot be processed until the reason for the error is determined and corrected.

This message is issued when a Db2® object name has been entered on a function entry panel, but Db2® reports that the object name does not exist. Db2 SSID is the name of the currently connected Db2® sub-system. Location is the value entered in the LOCATION entry field. The function cannot be processed until the reason for the error is determined and corrected.

This message is issued when a Db2® object name has been entered on a function entry panel, but Db2® reports that the object name does not exist. The Db2® object name contains two or more consecutive spaces, which may be valid, but more likely indicates the cause of the error.

This message is issued by the Db2® utilities function when an object not found condition is encountered. Some Db2® utilities require a table as input, and will not process a view, synonym or other objects.

File Manager attempted to allocate a temporary data set, in which to store SQL or some other information. The allocation attempt failed, the most likely explanation is that the UNIT parameter specified on the "Set Temporary Data Set Allocation Options" panel is invalid. This system option panel is accessed using 0.0.8 from the FM/Db2 main menu panel.

This message appears at the bottom of a File Manager/Db2 editor session, when a row count value (example 100) was specified on the editor function entry panel, and FM/Db2 read that many rows into the editor session without reaching the end of the Db2® object.

This is an internal error message, indicating a problem with the processing of the Db2® attachment.

This is an internal error. FM/Db2 attempted to access the JESCT however the pointer was zero.

FM/Db2 could not find any Db2® systems defined on the current z/OS® system.

This message may be issued during Db2® subsystem selection when a name with a wildcard (example DSN*) is entered in the Db2® SSID field on the FM/Db2 main menu. No matching Db2® systems were found.

Db2® system Db2 SSID is not defined on the local z/OS® system. This message may be issued in response to an attempt to change the currently connected Db2® system using a command like SSID XXXX.

The Db2® system or group Db2 SSID is defined on the local z/OS® system but is inactive (stopped).

FM/Db2 is already connected to Db2® system Db2 SSID. This message may be issued in response to an attempt to change the currently connected Db2® system using a command like SSID XXXX.

A call to the Db2® RRSAF attachment failed. Db2 SSID is the currently connected Db2® system; function is the failing RRSAF function and reason is the failing reason code.

A Db2® system has not been specified. FM/Db2 must connect to a Db2® system before it can perform useful work.

A Db2® SSID value was specified, but it does not uniquely identify a Db2® system. An example is DSN*.

The specified Db2® SSID value Db2 SSID is inactive.

This message is displayed on various selection lists, including the Db2® subsystem selection panel. Row value 1 is the first row shown on the display and there are a total of Row value 2 rows available for display.

A character other than "S" or "/ " was entered against an entry on the Db2® subsystem selection panel. The only valid characters for selecting an entry are "S" or "/ ".

An attempt was made to select Db2® system Db2 SSID from the Db2® subsystem selection panel. This Db2® system is not currently active.

The user pressed the EXIT PF key on the Db2® subsystem selection menu without making any selection. The FM/Db2 main menu is re-displayed. FM/Db2 is not connected to any Db2® system.

The user issued the REFRESH primary command on the Db2® subsystem selection list panel. The list of Db2® systems displayed is refreshed.

The user issued a SHOW Db2 SSID command on the Db2® subsystem selection list panel. The list of Db2® systems that match the SSID specification are displayed. The SSID value specified may include wild cards, example DSN*.

A command to change the currently connected Db2® SSID was issued on a panel where the command is not available.

A command to change the currently connected Db2® system was issued without an operand.

A Db2® server name was entered in the location field on a FM/Db2 function entry panel. While the Db2® server name is defined as a remote Db2® server at the local Db2® system, this server is not a Db2® UDB for z/OS® system. FM/Db2 only supports remote connections to Db2® UDB for z/OS® servers.

A Db2® server name was entered in the location field on a FM/Db2 function entry panel. The version of the remote Db2® system is Db2 version. Connection to this version of Db2® is not supported.

This is an internal error. During MVS™ token initialization an unsupported version of z/OS® was detected. It is not possible to run FM/Db2 against this version of z/OS®, or its predecessors.

This is an internal error. A call to function failed with return code return code.

An attempt was made to run FM/Db2, without correctly specifying a Db2® SSID name, or without first connecting to a Db2® system.

FM/Db2 attempted to call the Db2® CAF interface with function function. The call failed with return code return code and reason code reason code.

FM/Db2 attempted to load the Db2® interface module module name. The load failed with abend code abend code and reason reason code.

FM/Db2 is not currently connected to any Db2® subsystem.

FM/Db2 is connected to Db2® system Db2 SSID. The version of this Db2® system is Db2 VRM indicator.

The FM/Db2 plan names are Plan name 1 and Plan name 2.

This message user specified description appears in the" About Db2®" popup panel. The user specified description is the value specified in the FMN2SSDM macro, DESC parameter for the appropriate Db2® system.

This message is issued when an attempt is made to connect to a Db2® system at an unsupported version/maintenance level. The level of Db2® system Db2 SSID is Db2 level 1. The minimum supported level is Db2 level 2.

A ISPF PQUERY service for panel DSNEPRI was issued, the request failed.

An attempt was made to change the current SQLID on Db2® system Db2 SSID to Db2 authid. The attempt failed. The usual reason for this is that the FM/Db2 user is not authorized to use Db2 authid.

An attempt was made to change the current SQLID to Db2 authid. The attempt failed. The usual reason for this is that the FM/Db2 user is not authorized to use Db2 authid.

This message is used to display the audit status for the currently connected Db2® system, and appears on the "About Db2®" pop-up panel.

A call to the CAF interface, function function for Db2® system Db2 SSID failed with RC return code and reason reason code. The reason is that the nominated Db2® system does not exist.

A call to the CAF interface, function function for Db2® system Db2 SSID failed with RC reason code and reason reason code. The reason is that the nominated Db2® system is not active.

A call to the CAF interface, function function for Db2® system Db2 SSID failed with RC return code and reason reason code. The likely reason is that the FM/Db2 user is not authorized to connect to the nominated Db2® system.

A call to the CAF interface, function function for Db2® system Db2 SSID failed with RC return code and reason reason code. The reason is that FM/Db2 has not been installed on Db2® system Db2 SSID.

FM/Db2 attempted to load module module name. The attempt failed. The cause is an installation error; the File Manager load library is not available to the FM/Db2 user.

FM/Db2 loaded the FMN2POPT module, the contents are corrupt and unusable.

An attempt was made to connect to Db2® system Db2 SSID. This Db2® system is marked "Unavailable" in the FMN2POPT installation module. The Db2® system cannot be used.

FM/Db2 attempted to call the CAF interface, function function. An error occurred, RC return code and Reason reason code. The cause is an incompatibility (release level mismatch) between the Db2® and call attachment code.

FM/Db2 connected to Db2 SSID which is at version and release Release. The minimum supported Db2® version/release for this version of FM/Db2 is Minimum Release, which is greater than Release.

An attempt was made to connect to Db2 SSID which is at version and release Release. The maximum supported Db2® version/release for this version of FM/Db2 is Maximum Release, which is less than Release. The connection is not established and the Db2® system cannot be accessed. All versions of software are designed to work with a limited set (of version and release levels) of other software.

FM/Db2 attempted to connect to remote Db2® server Db2 location name. The connection failed with SQLCODE SQL error code.

A location nickname was not defined in the FMN2POPT module.

A location nickname was specified, but no location, to which the nickname refers, was specified.

Refer to the long message.

FM/Db2 attempted to load data module FMN2DATA. The attempt failed. FM/Db2 cannot operate without this module.

FM/Db2 attempted to load data module FMN2DENU. The attempt failed. FM/Db2 cannot operate without this module

FM/Db2 attempted to attach the subtask responsible for Db2® access. The attempt failed with RC return code. FM/Db2 cannot operate without the subtask for consistency.

FM/Db2 attempted to access Db2 SSID and received a communications error SQL error code.

FM/Db2 (in batch) connected to Db2® server server name. The connect information indicates that the Db2® server is not a Db2® UDB for z/OS® server. Connection is only supported to Db2® UDB for z/OS® servers.

FM/Db2 attempted to set the DECFLOAT ROUNDING MODE, the attempt failed with return code return code.

The FMN2POPT installation module is used to specify the Db2® systems that FM/Db2 can connect to. The File Manager for z/OS® Customization Guide recommends defining an FMN2SSDM macro entry for every Db2® system that FM/Db2 will connect to. The FMN2POPI macro includes a CONNECT option, the default setting is DEFINED. When CONNECT=DEFINED is in effect, FM/Db2 will only attempt connection to Db2® systems that have an FMN2SSDM entry in the FMN2POPT. An attempt to connect to a Db2® system with no FMN2SSDM entry results in this error.

The user exited the Db2® subsystem selection panel without selecting a Db2® subsystem or group

The user exited the Db2® subsystem selection panel without selecting a Db2® subsystem or group. FM/Db2 is not currently connected to any Db2® subsystem or group.

A Db2® command that produced large amounts of output was entered. Db2® has limited the amount of output produced, resulting in truncation.

FM/Db2 was not connected to any Db2® system, and the user typed a new value in the SQLID field on the FM/Db2 main menu. It is not possible to change the current SQLID without first being connected to some Db2® system.

This message appears in the Db2® subsystem selection display against any Db2® system that has no FMN2SSDM macro entry in the FMN2POPT.

A File Manager/Db2 batch job attempted to load the Db2® interface module name. The LOAD abended with Abend code abend code, reason reason code.

A File Manager/Db2 batch job attempted to access Db2® catalog table table name.. The access failed with SQLCODE-204 (object not found).

A File Manager/Db2 batch job attempted to access Db2® catalog table table name. The access failed with SQLCODE-551 (insufficient authority).

A File Manager/Db2 batch job attempted to access column column in Db2® catalog table table name. The access failed with SQLCODE-206 error. The column column is not defined in table table name.

A Db2® Abend occurred while running a File Manager/Db2 batch job. The Db2® Abend code is abend code, the reason code is reason code and the Db2® module that was accessed is name. The batch job ends and any uncommitted operations are backed out.

The SQL Reverse Engineering function (GEN command) failed with reason return code.

The REXX exec FMN2INEX can be used to invoke FM/Db2 by an external call. The exec requires various parameters, including a function code that indicates which FM/Db2 function to run. The function code provided was invalid.

FM/Db2 was invoked from an external application. In this situation it is not possible to change the currently connected Db2® SSID.

FM/Db2 was invoked from an external application. In this situation it is not possible to issue Db2® commands.

A File Manager/Db2 batch job encountered an error attempting to use the CAF attachment.

The SQLID command was issued to change the current SQLID. However the specified SQLID is already the current SQLID.

The SQLID command was issued without an operand.

The SQLID command was issued from a panel where the command is not supported.

In a File Manager/Db2 editor session of a Unicode encoded object, the conversion between CCSID CCSID 1 and CCSID CCSID 2 failed.

A command to change the current SQLID was issued. The command succeeded, the current SQLID is now SQLID.

A Db2® rollback was issued. This message appears in audit log reports.

A Db2® commit was issued. This message appears in audit log reports.

In a File Manager/Db2 editor session of a Unicode-encoded object, the conversion between CCSID CCSID 1 and CCSID CCSID 2 failed. The CUNLCNV system service, used to perform the conversion, issued return code return code and reason code reason code.

Processing on the FM/Db2 main menu panel includes the capability to change the current SQLID by typing a new value in the SQLID field, followed by the user pressing enter to validate the change. The ISPF short cut prefix ('=') can be used to navigate to some other FM/Db2 function. However, the use of this short cut bypasses the normal panel processing, and is therefore not supported.

An invalid character was entered against an entry in an object selection list. The only characters that may be used to select the entry are 'S' and '/'.

An invalid character was entered against an entry in an object selection list. The only characters that may be used to select the entry are 'S' and '/'.

This command is issued by the Basic SQL Prototyping function. An invalid command was entered in the 'S' (Selection) field. The only valid characters that may be used are as shown in the long message.

This message is issued by FM/Db2 functions that are executed in batch, when a Db2® object name does not exist. OBJIN appears when an input Db2® object name does not exist, for example print, copy and export. OBJOUT appears when an output Db2® object name does not exist, for example copy, import and data create.

This message is issued by FM/Db2 functions that are executed in batch, when the specified Db2® object name returns multiple Db2® objects. OBJIN appears when the location appears in an input Db2® object name, for example print, copy and export. OBJOUT appears when the location appears in an output Db2® object name, for example copy, import and data create.

This message is issued by FM/Db2 functions that are executed in batch, when a Db2® location, specified as part of a Db2® object name, does not exist. OBJIN appears when the location appears in an input Db2® object name, for example print, copy and export. OBJOUT appears when the location appears in an output Db2® object name, for example copy, import and data create.

FM/Db2 connected to Db2 SSID, which is at Db2® version or release release. The maximum supported Db2® version or release for the current version of FM/Db2 is Maximum release, which is less than release. The connection to this Db2® system is not supported.

A command to change the currently connected Db2® system was issued, however the value entered for the desired Db2® system is too long. Valid Db2® SSIDs are 1-4 characters in length.

An error was encountered during execution of aStatement type SQL statement. The failing SQLCODE is SQLCODE.

A File Manager/Db2 batch function encountered an error during execution of an SQL statement. The formatted SQL error messages is shown in SQL error message.

FM/Db2 attempted to connect to a remote Db2® server name, This may have been entered in the location field of various FM/Db2 function entry panels. The connection attempt failed with SQLCODE SQLCODE. The connection is not established and no operations at the remote Db2® server are possible until the reason for the connection failure is resolved.

This message is issued by the FM/Db2 Object list utility when the user changes the value in the location field on the function entry panel and presses ENTER. FM/Db2 attempts to connect to the new location value (or to reconnect to the local server, if the new value is blank). When the Db2® version or release for the previously connected Db2® system is different to the newly connected Db2® system, it is possible that the list of Db2® object types requires changes. The object list request is processed in two steps:

1. Updating the list of objects and showing this message.
2. Displaying the list of objects for the selected object type.

A Db2® server name, including wild cards, was entered in the Location field on the FM/Db2 Object List utility function entry panel. There are no Db2® server names that match the wild card specification.

FM/Db2 detected a serious internal error and issued an internal ABEND to prevent further processing. The internal abend code is Abend Code

A command to change the currently connected Db2® SSID (for example SSID XXXX) was issued on a panel where the command is not available. The reason for this is that a File Manager/Db2 function is active.

An attempt was made to change the current SQLID, using the SQLID command. The user is not authorized to use Db2® authid Db2 authid. The attempt to change the current SQLID fails, the existing value for SQLID is retained.

A Db2® object name was entered in the Owner or Name fields on a File Manager/Db2 function entry panel. The values entered refer to an ALIAS defined at the local Db2® server, however this ALIAS refers to another ALIAS. Recursive ALIASes are not supported.

An attempt was made to use data sampling, however the use of Db2 scrollable cursors has been disabled by the product installer. Data sampling requires the use of Db2 scrollable cursors so the requested operation cannot be performed.

This message is issued by the FM/Db2 editor, when operating in Large mode. Count shows the row number of the first row currently displayed (in TABL display mode), or the currently displayed row (in SNGL display mode). Large editor mode is explained at length in FM/Db2 editor sessions. Large editor mode is selected when the user enters 0 (also *, ALL) in the "Row count" field of a File Manager/Db2 function that uses the editor to display the result table.

This message is issued by the FM/Db2 editor when the data is first displayed. The user specified a table locking option (not recommended) on the 7th Editor Options panel. When FM/Db2 attempted to lock the table, the operation failed.

This message is issued by the FM/Db2 editor (only for edit) when an explicit Db2® COMMIT has been issued. The Db2® COMMIT finalizes any pending changes made in the current editor session.

This message is issued by the FM/Db2 editor (only for edit) when an explicit Db2® COMMIT has been issued. The Db2® COMMIT finalizes any pending changes made in the current editor session. The FM/Db2 editor processes changes data in an editor session on a row-by-row basis. It is therefore possible for some, but not all, changes to have been committed.

The user entered the INDEXINF primary command in a File Manager/Db2 editor session, and the prior state of the toggle was off. When the data is displayed in SNGL mode, an additional column appears on the left of the display, showing the columns that are part of keys (indexes) defined against the table.

The user entered the INDEXINF primary command in a File Manager/Db2 editor session, and the prior state of the toggle was on. See also message FMNDB155.

This message is issued by the FM/Db2 editor when the user presses the PF key assigned to CANCEL, or types CANCEL, within the editor session. The current FM/Db2 editor session ends and an explicit Db2® ROLLBACK is issued. Any changes made after the last Db2® COMMIT are lost.

An attempt was made to edit an auxiliary table. This action is not supported.

This message is issued by the FM/Db2 editor when the data is first displayed. It shows the number of rows that have been fetched from Db2® and loaded into the current editor session. It indicates that the user specified a non zero "row count" value, that the specified number of rows has been loaded into the editor, and that the end of the Db2® object or result table was not reached.

This message is issued by the FM/Db2 editor when there is insufficient memory available to load all the rows of a Db2® object or result table into memory. The editor operation cannot proceed.

This message is issued by the FM/Db2 editor when processing a Db2® object, or result, table that has at least one column with the TIME data type. In addition, the FM/Db2 system options are set to display TIME columns in USA format. This format truncates the seconds part of any TIME value, making it impossible to distinguish between, for example, 09:13:52 and 09:13:00. For this reason it may be impossible to update or change data for this table.

This message is issued by the FM/Db2 editor when an attempt is made to edit a Db2® object that is marked as COPY PENDING. The Db2® object being edited is stored in table space table space name in database name. It is not possible to change Db2® tables while they are in COPY PENDING status. COPY PENDING status can be set for a Db2® object after, for example, an initial data load, using the Db2® utilities, when certain utility options are specified.

This message is issued by the template editor, or Column Selection, or Edit panel, when a syntax error is detected in the user-specified WHERE clause.

This message is issued by the template editor, or Column Selection/Edit panel, when the WHERE clause specifies an invalid column name. The reason is that the column name does not exist in the Db2® object or result table being processed.

This message is issued by the template editor, or Column Selection/Edit panel, when the WHERE clause contains an open quoted string. Examples of open quoted strings are:

1. WHERE EMPNO = '
2. WHERE EMPNO ="

This message is issued by the template editor, or Column Selection and Edit panel, during validation of a user specified WHERE clause. The validation process used by FM/Db2 is to prepare a SELECT statement against the Db2® object being processed after appending any user specified WHERE clause. The prepare can fail for many reasons, for example syntax errors and incorrect column names. The prepare step may also fail for other reasons, in which case the failing SQLCODE is returned to the user for action.

This message is displayed when the data for a new related edit session is first displayed, and the new table is a dependent table.

This message is displayed when the data for a new related edit session is first displayed, and the new table is a parent table.

This message is displayed when the data for a new related edit session is first displayed, and the new table is a dependent table.

This message is issued at the end of a File Manager/Db2 editor session. It indicates that a Db2® COMMIT has been issued to finalize any pending changes to the Db2® object being processed.

The user typed an invalid value in the Format field in a File Manager/Db2 editor session.

The user entered the name of a Db2® object in the "Owner" and "Name" fields on a File Manager/Db2 function entry panel. FM/Db2 attempted to resolve the name and the attempt failed. The reason this message is issued is described in the following example:Alias ALIAS is defined, this refers to OBJECT. However, OBJECT does not exist. The user enters ALIAS in the "Owner" and "Name" fields on a File Manager/Db2 function entry panel. FM/Db2 resolves the ALIAS name to OBJECT. However, the latter does not exist, resulting in this error message.

This message is issued by either the FM/Db2 export, or FM/Db2 UNLOAD utilities when:

1. The Db2® object being processing has a TIME data type column.
2. The "External Format for TIME Data Type Columns" system option is set to"Db2® DSNHDECP setting".
3. The DSNHDECP setting for TIME columns is 'USA'.

This message is issued by the FM/Db2 copy utility when:

1. The Db2® object being processing has a TIME data type column.
2. The"External Format for TIME Data Type Columns" system option is set to "Db2® DSNHDECP setting".
3. The DSNHDECP setting for TIME columns is 'USA'.

This message is issued by the FM/Db2 editor when it receives an SQLCODE-911 error attempting to change data for a row that was modified by the user. Db2® detected a deadlock with another task and resolved the situation by rolling back the changes for the FM/Db2 user. This means that any changes made since the last Db2® COMMIT point have been lost. In this situation there is no guarantee that the data displayed in the FM/Db2 editor still reflects the data stored in Db2®. It is best to cancel the current editor session and restart.

The initialization process for the related edit session failed. Each related edit session is effectively a new invocation of FM/Db2. Once started the user can use ISPF commands to switch between the different logical sessions. During the invocation process a REXX EXEC, FMN2RESS, is called. However, this REXX EXEC may not be accessible when LIBDEFs are used to define the FM/Db2 libraries.

This message is issued by the FM/Db2 editor when processing a view that cannot be updated. While the user selected the edit (as opposed to view/browse) to process the object, no edit operations are possible. To avoid any possible confusion the edit session has been converted to browse.

This message is issued by the FM/Db2 editor when the data for a view is first displayed. The user has set a table locking option in the editor options. This is not recommended. Only tables can be explicitly locked, therefore the attempt to lock the view failed.

The object being processed by the FM/Db2 editor is a read-only view, although it does have one or more columns marked as updateable.

The object being edited contains one or more columns marked as not updateable in the Db2® catalog SYSIBM.SYSCOLUMNS.UPDATES = 'Y'. These columns will appear in the editor session as protected fields. One reason for this message is when edit is used to display the data from a Db2® catalog table.

The user entered an alias name in the "Owner" and "Name" fields on a File Manager/Db2 function entry panel. FM/Db2 resolved the alias name to another alias name defined at a remote location. This is not supported. After resolution, any alias name entered must refer to an actual Db2® object defined either locally, or remotely.

The user entered the RE (Related edit) command in a File Manager/Db2 editor session. The object being edited is a view; related edit functionality is only available for tables. The operation cannot be performed.

This message is issued by the FM/Db2 editor when processing a Db2® object with graphic data type columns that is encoded in Unicode. In this situation it is possible for data corruption to occur when processing data for these columns and initializing the field contents. To avoid this situation, the INSERT, REPEAT, and COPY commands are disabled.

This message is issued by the FM/Db2 editor when processing a Db2® object with graphic data type columns that is encoded in Unicode. In this situation it is possible for data corruption when processing data for these columns. To avoid this possibility, changes to graphic data type columns are not supported.

There is a conflict between options selected on the 7th Editor options panel. The "read-only" option implies that no Db2® locks are required when processing the SQL SELECT statement. However, the Concurrency options "Read stability keep locks" and "Repeatable read keep locks" imply that Db2® should take and keep locks while processing the SQL SELECT statement.

An internal statement buffer overflow was detected while building an SQL statement to update a table. The operation cannot be performed. This condition should not occur during processing of typical Db2® objects. It might occur when processing Db2® objects with very many column names (the maximum is 750), and with many "long" column names. The maximum length for a column name is 30 characters.

The user made an invalid change to the "Initial display format" editor option, and then pressed the PF key assigned to END, or typed END. The invalid value is discarded and the editor options panel is redisplayed.

The user made an invalid change to the "Concurrency" editor option, and then pressed the PF key assigned to END, or typed END. The invalid value is discarded and the editor options panel is redisplayed.

The user made an invalid change to the "Enter key usage" editor option, and then pressed the PF key assigned to END, or typed END. The invalid value is discarded and the editor options panel is redisplayed.

The user specified the same character for the "Input" and "Display" string delimiters on the 5th Editor options panel. While most characters can be used, the characters that are used must be distinct.

The user specified the same character for the "Input" and "Display" Null column indicators on the 5th Editor options panel. While most characters can be used, the characters that are used must be distinct.

The user specified the same character for the "Input" Null column indicator and "Input" String delimiter. While most characters can be used, the characters that are used must be distinct.

The user specified the same character for the "Display" Null column indicator and "Input" String delimiter. While most characters can be used, the characters that are used must be distinct.

The user specified the same character for the "Input" Null column indicator and "Display" String delimiter. While most characters can be used, the characters that are used must be distinct.

The user specified the same character for the "Display" Null column indicator and "Display" String delimiter. While most characters can be used, the characters that are used must be distinct.

This message is issued by the FM/Db2 Object List utility in various circumstances when a requested command cannot be performed. The reason the command cannot be performed is that the object is at a remote location. Certain SQL commands, for example GRANT and REVOKE, may only be issued when connected to the local Db2® server.

The LISTCAT line command was issued against a Db2® catalog object. For example, a table or index space. This command cannot be issued against Db2® catalog objects.

This message is issued by the FM/Db2 Object functions. For a column defined with the DECFLOAT data type, a value other than 16 or 34 was entered in the 'PR' column.

This message is issued by the FM/Db2 Object functions. When defining the data type for a column, an invalid, or unsupported, data type value was entered.

This message is issued by the FM/Db2 Object functions. The value entered for a length, precision or scale is invalid.

This message is issued by the FM/Db2 Object functions. The combination of scale and precision values entered is invalid.

In the FM/Db2 editor, a change command was issued that included a field reference, or references. The target column for the change is not updateable, meaning that the proposed change is not possible.

This message is issued by the FM/Db2 editor. The user entered a value start position in the "Start position" field on the Db2® Edit panel. When FM/Db2 attempted to skip to the nominated start position, it reached the end of the result table. The number of rows in the result table is number or rows.

This message is issued by the FM/Db2 editor when clustered sampling is selected in the editor options. When FM/Db2 attempted to skip to the nominated start position, determined by the value in the "start position field", and the value in the "Initial skip count fields", it reached the end of table. The number of rows in the result table is number of rows (n).

When binding a copy of a package, the collection and COPY collection values must be different.

The 'B' (Browse) command was issued against an image copy entry displayed by the FM/Db2 Object List Utility. The browse command can only be entered against entries associated with an image copy data set stored on DASD (disk). The command cannot be processed.

The DBRM command was entered against an entry in a PLAN table. The command is only valid when the entry is associated with an application plan; that is the APPLNAME column for the row is non blank. The command cannot be processed.

The PACKage command was entered against an entry in a PLAN table. The command is only valid when the entry is associated with a package; that is the COLLID column for the row is non blank. The command cannot be processed.

The PACKage command was entered against an entry in a PLAN table. The command is only valid when the entry is associated with a DBRM; that is the PROGNAME column for the row is non blank. The command cannot be processed.

This message is issued in various places in the FM/Db2 Object List Utility. A value was entered for a field where an ordinary SQL Identifier is required. An example is a Db2® authid used as an "Owner" or SQLID.

A value entered for a buffer pool is invalid. List shows the valid values that can be entered.

The "CON" command (Show table constraints) was issued against a list of tables in the FM/Db2 Object List utility. This command is not valid when connected to a Db2® version 7, or earlier system. The currently connected Db2® system is at Db2 VRM indicator, which is less than '0800'. The command cannot be executed.

This message is issued in various contexts by the FM/Db2 Object List utility. An example is issuing the VS (Show view SQL) against a entry in a list of Db2® tables/views/aliases, when the entry is not a view.

This message is issued in various contexts by the FM/Db2 Object List utility when processing a list of functions. The row against which the line command was entered is of the wrong function type. The command is not applicable to that type of function.

A command was issued to upgrade a PLAN_TABLE, however the table was already at the correct level. No action was taken.

This message is issued in various contexts by the FM/Db2 Object List utility when processing a list of columns. The row against which the line command was entered is of the wrong type. For example, the command applies only to columns defined with a user-defined (DISTINCT) data type. The command cannot be executed.

The 'COM' (COMMENT) line command was issued against a row in a list of sequences displayed by the FM/Db2 Object List Utility. A comment cannot be specified for sequences that represent internal sequence objects used by Db2®. The command cannot be executed.

The user issued the 'LC' (LISTCAT) command against an entry in a list on the Recovery Information panel in the FM/Db2 object list utility that did not have an associated data set. The Recovery Information panel shows all the rows in the SYSIBM.SYSCOPY catalog table. Only rows that represent full and incremental image copies are suitable targets for the LISTCAT command.

This message is issued by the FM/Db2 object list utility when the user has entered values in the "Additional selection criteria" section of the panel. This section of the panel can be used to add a simple predicate to the SQL being generated. For example, when listing tables, show only tables that have an EDITPROC. This can be achieved by setting Column=EDPROC; Operator= ≠ Value = ". The expression entered resulted in SQLCODE-199, and cannot be processed.

The user entered a value in a Location field on a File Manager/Db2 function entry panel. The attempt to connect to this remote server failed with SQLCODE-950.

This message is issued by the Explain Utilities functions when the user issues the 'L' (List plan table rows) command, but the plan table owner.PLAN_TABLE does not exist. The operation cannot be performed.

This message is issued when a generated SQL statement contains a syntax error, specifically an open quoted string. The SQL statement cannot be executed.

The user issued the 'RT' (Recover TOCOPY) command against an entry in a list on the Recovery Information panel in the FM/Db2 object list utility that did not have an associated data set. The Recovery Information panel shows all the rows in the SYSIBM.SYSCOPY catalog table. Only rows that represent full and incremental image copies are suitable targets for the RT command.

This message is issued by a File Manager/Db2 function entry panel when the user specifies "Previous" for the Template usage option. However, no template has been previously saved for the current Db2® object.

This message is issued by a File Manager/Db2 function entry panel when the user specifies a template data set name for a Db2® object, and that the specified template should be used. However, the specified template is not a valid FM/Db2 template. There are different types of File Manager templates, depending on the source of the template. A base template cannot be used to describe a Db2® object.

This message is issued by a File Manager/Db2 function entry panel when the user specifies a template data set name for a Db2® object, and that the specified template should be used when processing the Db2® object. The specified template was successfully loaded, compared against the Db2® object and found to contain a valid description of the Db2® object.

This message is issued by a File Manager/Db2 function entry panel when the user specifies a template data set name for a Db2® object, and that the specified template should be used when processing the Db2® object. When FM/Db2 compared the template specified by the user with the template generated by FM/Db2, using the information in the Db2® catalog, differences were found. The "Template not matched" panel is typically shown before this message; the user pressed PF3 on the "Template not matched" panel. In most cases this error means that the template in the user-specified data set refers to a different Db2® object to that specified on the function entry panel. See also message FMNDB304.

This message is issued by a File Manager/Db2 function entry panel when the user specifies a template data set name for a Db2® object, and when the user specifies the template should be used when processing the Db2® object. When FM/Db2 compared the template specified by the user with the template generated by FM/Db2, using the information in the Db2® catalog, differences were found. The "Template not matched" panel is typically shown at the same time as this message.

This message is issued by a File Manager/Db2 function entry panel when the user specifies a template data set name for a Db2® object, and that the specified template should be used when processing the Db2® object. When FM/Db2 compared the template specified by the user with the template generated by FM/Db2, using the information in the Db2® catalog, differences were found. The user canceled the template merge process.

This message is issued when an attempt is made to access Owner.DSN_STATEMNT_TABLE. The user-defined table does not exist, the operation cannot be performed.

This message is issued when an attempt is made to access Owner.DSN_FUNCTION_TABLE. The user-defined table does not exist, the operation cannot be performed.

The user entered a command to process a LOB or XML column. The row number specified as part of the command is invalid. You can use cursor positioning to specify the row in which the column of interest is located - in which case a row number is not required. If cursor positioning is not used a row number is required. This message can be issued when an invalid value (not a number) is specified for the row number.

The user entered a command to process a LOB or XML column. The row number specified as part of the command is invalid because it does not exist in the current editor session. The command cannot be processed.

The user entered a command to process a LOB or XML column. The cursor was positioned within the data area of the display and FM/Db2 attempted to use cursor positioning to identify the column and row of interest. The column where the cursor is located in not a LOB or XML column. The command cannot be processed.

The user entered the J prefix command in a File Manager edit or view session. This command is only available in a File Manager/Db2 component editor session when processing a LOB, that is in a view or edit session initiated using the LOBVIEW or LOBEDIT command. The command cannot be processed.

The user entered the SP prefix command in a File Manager edit or view session. This command is only available in a File Manager/Db2 component editor session when processing a LOB, that is in a view or edit session initiated using the LOBVIEW or LOBEDIT command. The command cannot be processed.

A change command was entered with a target column that is a LOB (CLOB, BLOB or DBCLOB) or XML column. This is not supported

The user entered a SELECT statement using FM/Db2 options 4.1-4.4. The result table for the SELECT statement includes either LOB or XML columns. Display of the result table is not supported, the operation cannot be performed.

The user attempted to process a Db2® object containing XML columns using the FM/Db2 editor. The target Db2® system is not at Db2® V10 new function mode (or later). Display of the Db2® object is not supported, the operation cannot be performed.

This message is issued when an attempting to save changes made in a File Manager/Db2 LOB editor session. The total length of the LOB data exceeds the maximum size for the LOB column. The changes made in the LOB editor session cannot be saved.

The user issued a command to process a LOB column (LOBLEN, LOBBRWS, LOBVIEW or LOBEDIT). The field reference provided does not identify a LOB column. The command cannot be processed.

The user issued a command to process a LOB column (LOBLEN, LOBBRWS, LOBVIEW or LOBEDIT), using cursor positioning to identify the row and LOB column of interest. The column identified is not a LOB column. The command cannot be processed.

The user issued the LOBLEN command. The length of the column identified is Length. Row number is the row number for the row that includes the identified column. Field Ref is the field reference value entered in the LOBLEN command.

The user issued a command to process a LOB column (LOBLEN, LOBBRWS, LOBVIEW or LOBEDIT), however the Db2® object being processed does not include any LOB columns. The command cannot be processed.

The user issued the LOBVIEW command from a File Manager/Db2 browse session. The only LOB-related commands that are available in a File Manager/Db2 browse session are LOBLEN and LOBBRWS. The command cannot be processed.

The user issued the LOBEDIT command from either a File Manager/Db2 browse, or a FM/Db2 view session. The only LOB-related commands that are available in a File Manager/Db2 browse session are LOBLEN and LOBBRWS. The only LOB-related commands that are available in File Manager/Db2 view session are LOBLEN, LOBBRWS and LOBVIEW. The command cannot be processed.

This message is issued when the data for a LOB column is initially displayed by the FM/Db2 LOB editor. There is no data in the LOB column.

A command to process an XML column (XMLBRWS, XMLVIEW or XMLEDIT) was issued. These commands are not available when using the FM/CICS interface.

The user issued a command to process a LOB column (LOBLEN, LOBBRWS, LOBVIEW or LOBEDIT), however the template for the object has been modified so that all LOB columns are not displayed. The command cannot be processed.

The LOBEDIT command was issued against a BLOB column. Edit of BLOB data is not supported. The command cannot be processed.

The user issued a command to process an XML column (XMLLEN, XMLBRWS, XMLVIEW or XMLEDIT). The field reference provided does not identify an XML column. The command cannot be processed.

The user issued a command to process an XML column (XMLLEN, XMLBRWS, XMLVIEW or XMLEDIT), using cursor positioning to identify the row and XML column of interest. The column identified is not an XML column. The command cannot be processed.

The user issued the XMLLEN command. The length of the column identified is Length. Row number is the row number for the row that includes the identified column. Field Ref is the field reference value entered in the XMLLEN command.

The user issued a command to process an XML column (XMLLEN, XMLBRWS, XMLVIEW or XMLEDIT), however the Db2® object being processed does not include any XML columns. The command cannot be processed.

The user issued the XMLVIEW command from a File Manager/Db2 browse session. The only XML-related commands that are available in File Manager/Db2 browse session are XMLLEN and XMLBRWS. The command cannot be processed.

The user issued the XMLEDIT command from either a File Manager/Db2 browse, or a FM/Db2 view session. The only XML-related commands that are available in a File Manager/Db2 browse session are XMLLEN and XMLBRWS. The only LOB-related commands that are available in a File Manager/Db2 view session are XMLLEN, XMLBRWS and XMLVIEW. The command cannot be processed.

The FMAP command was issued against a LOB (CLOB, BLOB, or DBCLOB) or XML column. This is not supported.

The user issued a command to process an XML column (XMLLEN, XMLBRWS, XMLVIEW or XMLEDIT), however the template for the object has been modified so that all XML columns are not displayed. The command cannot be processed.

This message is issued in response to an attempt to save changes made in an XML editor session. There is a syntax error in the XML document that will prevent the updated document being saved in the Db2® object. Line indicates the line number where the syntax error is located. The XML document cannot be saved until the syntax error is correcte.

The SQL command was issued in the template editor after a condition has been specified using the "Row Selection Criteria" panel. Expressions issued using the SQL command and the "Row Selection Criteria" panel are mutually exclusive, saving an expression entered using the SQL command causes an expressions entered using the "Row Selection Criteria" panel to be discarded.

An attempt was made to de-select columns in the template for a Db2 object specified in the FM/Db2 data create utility. This is not supported.

An attempt was made to use a template with de-selected columns with a Db2 object specified in the FM/Db2 data create utility. This is not supported.

A command was issued in an FM/Db2 editor sessions, operating in Large edit mode, that would have added a row to the editor session. Examples: INSERT, COPY, REPEAT, and GET. This is not supported.

This message is issued by the FM/Db2 Advanced SELECT Prototyping function, when the user exits the syntax diagram for a code fragment without making any choice.

This message is issued by the FM/Db2 Advanced SELECT Prototyping function when the user presses a PFKey assigned to a command (for example INSRPT, assigned to PF5 by default), however the cursor was not located on an applicable syntax element. The command cannot be performed.

This message is issued by the FM/Db2 Advanced SELECT Prototyping function when the user presses a PFKey assigned to a command (for example INSRPT, assigned to PF5 by default), however the cursor was not located on an applicable syntax element. Some commands are only applicable to repeatable syntax elements. The command cannot be performed.

This message is issued by the FM/Db2 Advanced SELECT Prototyping function when the user exits a data entry syntax element without entering a value. An example is the "table" option of the "table reference clause". A Db2® table name, such as DSN8x10.EMP is required.

This message is issued by the FM/Db2 Advanced SELECT Prototyping function when the user enters a scroll command (or presses a PFKey assigned to a scroll command), however there is not data to scroll.

This message is issued by the FM/Db2 Advanced SELECT Prototyping function when the user enters a scroll down command (or presses a PFKey assigned to scroll down), however there the last line of the generated statement is already visible. No further scrolling is possible.

This message is issued by the FM/Db2 Advanced SELECT Prototyping function when the user enters a scroll up command (or presses a PFKey assigned to scroll up), however there the first line of the generated statement is already visible. No further scrolling is possible.

This message is issued by the FM/Db2 Advanced SELECT Prototyping function. The SELECT statement being generated changed as a result of user input. The display of the generated statement was automatically scrolled to show the last part of the statement.

This message is issued by the FM/Db2 Advanced SELECT Prototyping function. The length of the generated SQL statement exceeds 32765 bytes, which is the limit for the function. Execution of the statement is expected to fail and should not be attempted. Note that while Db2® supports SQL statements up to 2M-1 the limit of 32K-2 is imposed by File Manager under ISPF.

This message is issued by the FM/Db2 Advanced SELECT Prototyping function, when the user attempted to add a repeat separator (for example AND, OR), however no repeatable items have been selected.

This message is issued by the FM/Db2 Advanced SELECT Prototyping function. The user entered the EXECUTE command; or pressed the PFKey assigned to EXECUTE, however no SELECT statement has been generated.

This message is issued by the FM/Db2 Advanced SELECT Prototyping function. An attempt was made to insert a repeat separator, however there is no repeat separator for the last repeated element.

This message is issued by the FM/Db2 Enter, Execute and Explain SQL function. The user entered the EXECUTE command; however the SQL Statement input area is blank.

This message is issued by the FM/Db2 Enter, Execute and Explain SQL function, when the user has entered an SQL statement that cannot be dynamically prepared/executed. An example is 'CONNECT TO server', which can only be coded in an application program. This statement cannot be dynamically prepared and executed. The operation cannot be performed.

This message is issued by FM/Db2 functions after the successful execution of some SQL statement. Statement type is SELECT, INSERT, and so on. Cost is the timer on value returned by Db2® when the SQL statement was prepared, giving a relative estimate of cost of executing the statement.

This message is issued by the FM/Db2 Enter, Execute, and Explain SQL function after successful execution of multiple SQL statements. Count is the number of SQL statements that were executed. The statements may be of different types. Costis the total of the timer on values returned by Db2® when each SQL statement was prepared.

This message is issued by the FM/Db2 Enter, Execute and Explain SQL function when execution of some SQL statement fails. Depending on the type of error, the cursor is placed at the start of the failing SQL statement, or on the token within the SQL statement considered to be in error.

This message is issued by the FM/Db2 Enter, Execute, and Explain SQL function after the user exits from an ISPF editor session displayed in response to the SQL command. Within the ISPF editor, session changes may be made to the SQL statement. However, the statement must be entered in columns 1-72, inclusive. Any data entered in columns 73-80 is truncated (discarded).

This message is issued by the FM/Db2 Enter, Execute and Explain SQL function after the user exits from an ISPF editor session displayed in response to the SQL command. Not all of the SQL statement entered in the ISPF editor session could be copied to the display area for the FM/Db2 Enter, Execute, and Explain SQL function. The statement is too long.

This message is issued by the FM/Db2 Advanced SELECT Prototyping function. The user entered the SQL command; however there was no SQL to display in an ISPF editor session. The SQL command cannot by processed.

This message is issued by the FM/Db2 Edit/Execute SQL (Data Set) function. Neither the "Edit data set", nor the "Execute SQL from data set" options have been selected.

This message is issued by the FM/Db2 Enter, Execute, and Explain SQL function when an SQL statement other than a SELECT, DELETE, or UPDATE is processed. Statement type is the type of statement (Example SET) and Action indicates the type of operation. For example, "executed".

This message is issued by the FM/Db2 Enter, Execute, and Explain SQL function when multiple SQL statements are processed. count is the type of statement and Action indicates the type of operation. For example, "executed".

This message is issued by the FM/Db2 Enter, Execute, and Explain SQL function, after multiple SQL statements were processed. The execution of at least one SQL statement failed, however count statements were processed successfully.

This message is issued by the FM/Db2 Basic SELECT Prototyping function. The user attempted to execute the SQL SELECT statement. However, the SELECT statement is incomplete and cannot be executed. There are no columns specified in the SELECT clause.

This message is issued by the FM/Db2 Basic SELECT Prototyping function. The user entered a value in the 'Op' (Operator) column for a column, but no value was entered in the corresponding 'Value' column. A value is required to construct a valid WHERE clause, which has the form: COLUMN operator value.

This message is issued by the FM/Db2 Basic SELECT Prototyping function. The user entered an invalid value in the 'LOp' (Logical Operator) column for a column. The LOp column is used to specify a logical operator. This is used between any WHERE clause predicates specified for the SQL statement being prototyped.

This message is issued by the FM/Db2 Basic SELECT Prototyping function. The user entered an invalid value in the 'Op' (Operator) column for a column. The Op column is used to specify a comparison operator. This is used in the WHERE clause predicate being added to the SQL statement being prototyped.

This message is issued by the FM/Db2 Enter, Execute, and Explain SQL function. The user entered the EXPLAIN command. However, there was no SQL statement in the "SQL Statement" area of the panel. The EXPLAIN command requires an SQL statement to process.

This message is issued by the FM/Db2 Enter, Execute, and Explain SQL function. The user entered the EXPLAIN command. However, the SQL statement entered is not "explainable".

This message is issued by the FM/Db2 Enter, Execute, and Explain SQL function. The user entered a DELETE SQL statement, and the statement was executed. However, Db2® reported that no rows were deleted.

This message is issued by the FM/Db2 Enter, Execute, and Explain SQL function. The user entered an UPDATE SQL statement, and the statement was executed. However, Db2® reported that no rows were updated.

This message is issued by the FM/Db2 Enter, Execute, and Explain SQL function. The execution of an SQL statement was halted because it exceeds values set by the SQL predictive governor. In this situation a warning pop-up panel is displayed, and the user elected to CANCEL execution of the statement.

This message is issued by the FM/Db2 Edit/Execute SQL (Data Set) function. The input data set contains a CONNECT SQL statement. This statement cannot be dynamically prepared and executed. It can only be embedded in an application program. The statement cannot be executed.

This message is displayed by the FM/Db2 Editor, when using clustered sampling.

This message is displayed by the FM/Db2 Editor, when using clustered sampling.

This message is displayed by the FM/Db2 Editor, when using random sampling.

This message is displayed by the FM/Db2 Editor, when using random sampling.

This message is displayed by the FM/Db2 Editor, when processing LOB data.

This message is displayed by the FM/Db2 Editor, when processing XML data.

This message is issued by the FM "Db2 Utilities" function. The user selected an index created with the 'COPY NO' option for copy. This is not allowed.

This message is issued by the FM "Db2 Utilities" function. The user entered change limit values for a table space defined with 'TRACKMOD NO'. This is not allowed.

This message is issued by the FM "Db2 Utilities" function. The user is attempting to recover either a table space, or index. When FM/Db2 retrieved a list of entries from SYSIBM.SYSCOPY, no rows were returned. This might occur when wildcard values for database name and table and index space name were specified on the function entry panel. There are no matching table and index spaces. Another possibility is that there are matching table and index spaces, but no suitable image copies are available for these objects, so the RECOVER utility cannot execute.

This message is issued by the FM "Db2 Utilities" function. Change limit values for the COPY utility are expressed as percentage values (0-100 inclusive). The value entered is out of range.

This message is issued by the FM "Db2 Utilities" function. The CANCEL PFKey or CANCEL command was used when processing for a LOAD utility job, using a File Manager template, was incomplete.

This message is issued by the FM "Db2 Utilities" function. Processing for a Db2® LOAD utility completed normally.

This message is issued by the FM/Db2 "OPTIONS Options" panel. The user selected a processing option of 4 "Options to be included", but did not select any of the available options. At least one option must be selected.

This message is issued by the FM/Db2 Unload utility. During mapping between the columns of the source object and fields of the output template, a mismatch for column Column name, and the corresponding field, has been detected. Column name is defined as NOT NULL. However, the target field has an associated null field indicator.

This message is issued by the FM/Db2 "OPTIONS Options" panel. The user selected a processing option of 3 ('KEY'), but did specify a key value.

This message is issued by the FM/Db2 Unload utility, when the user presses the PFKey assigned to CANCEL (or types the CANCEL command), prior to completion of the function.

This message is issued by the FM/Db2 Unload utility, when the function completes normal processing.

This message is issued during FM/Db2 options initialization. An error was encountered when storing values in an ISPF table in the user ISPF profile.

This message is issued during FM/Db2 options initialization. An error was encountered when storing values in an ISPF table in the user's ISPF profile.

This message is issued by the FM/Db2 Unload utility. A problem has been detected when mapping columns of the Db2® object to corresponding fields in the File Manager (base) template for the unloaded data.

This message is issued by the FM/Db2 Unload utility. This is a "should not occur" error.

This message is issued by the FM/Db2 Unload utility. A problem has been detected when processing the mapping for a Db2® null indicator for column column name.

This message is issued when there is a problem generating a JCL deck using ISPF file tailoring. This is a "should not occur" error under normal circumstances.

This message is issued during FM/Db2 options processing. Once cause of this error is a missing options module (FMN2POPT), or no definitions for the current Db2® subsystem.

This message is issued during FM/Db2 Options processing. When processing TEMPLATE, LISTDEF, or OPTIONS, no options had previously been saved in the user's ISPF profile. The option values have been initialized based on any values set in the FMN2POPT (installation) module.

This message is issued during FM/Db2 Options processing. When processing the connection to a Db2® subsystem, the combination of CONNECT=ANY (FMN2POPI macro parameter) and no FMN2SSDM macro entry for the Db2® subsystem was detected. In this situation there can be no installation settings for TEMPLATE, LISTDEF, and OPTIONS options (since there is no FMN2SSDM macro entry where these settings are defined). The FM/Db2 defaults are used to initialize the option values.

This is a "should not occur" error. The FMN2POPT module in use is out-of-date and should be reassembled with the latest macro versions.

The user selected the 'LISTDEF' specification on the FM/Db2 "Db2® Utilities" function entry panel. However, no value was entered in the "LISTDEF name" field. The use of a LISTDEF specification requires a non-blank LISTDEF name.

This is a message insert used by the FM/Db2 Unload utility when preparing JCL.

This is a message insert used by the FM/Db2 Unload utility when preparing JCL.

This is a message insert used by the FM/Db2 Unload utility when preparing JCL.

This is a message insert used by the FM/Db2 Unload utility when preparing JCL.

This message may be issued when exiting the ISPF edit session used to specify a WHERE clause in the FM/Db2 template editor (Column Selection/Edit panel). The WHERE clause exceeds the maximum allowable length of 32767 bytes, and cannot be processed.

This message is issued by the FM/Db2 Basic SELECT Prototyping function. When using an explicit table correlation reference (example #n, n=1, 2 ..) the n must not be greater than the number of Db2® objects entered when the function was first started. "n" must also be a numeric value, example #F is invalid.

This message is issued by the FM/Db2 Basic SELECT Prototyping function. A qualified column name was entered in the "Value" column, presumably to indicate a join between two columns. The table correlation reference is valid but the column name is not.

This message is issued by the FM/Db2 Basic SELECT Prototyping function. A value entered in the "Value" column matches more than one column name in the Db2® objects selected for prototyping. A table correlation reference needs to be used to remove any ambiguity.

This message is issued by the FM/Db2 Basic SELECT Prototyping function. A value entered in the "Value" column matches a column name in a Db2® object selected for prototyping. There are two interpretations for the value entered:

1. A comparison between the column and a string constant.
2. A join between the column and the column name entered.

This message is issued by the FM/Db2 DB2 UNLOAD utility when the DB2 NOPAD option is selected. The NOPAD option can result in UNLOAD data with varying lengths, the format for these records cannot be described using a File Manager template.

An attempt was made to browse the contents of a DBRM member using the FM/Db2 object list utility. The member specified in the Db2 catalog table could not be found.

This message is issued in response to the RESET command entered on a File Manager/Db2 options panel. The values on the panel have been reset to the default values.

This message is issued in response to the RESET command, entered on a File Manager/Db2 options panel. The RESET operation failed, this is a "should not occur" error.

This message is issued by the FM/Db2 copy utility to indicate that copy operations are in progress.

This message is issued by the FM/Db2 copy utility to give an indication of progress for the current copy operation. number of rows is the number of rows that have been processed.

This message is issued by the FM/Db2 copy utility, at the completion of the copy operation, to report the number of rows copied from source Db2 object to target Db2 object. This message indicates that there were no duplicate key or referential integrity errors encountered.

This message is issued by the FM/Db2 copy utility, at the completion of the copy operation, to report the number of rows copied. insert string contains additional information, typically messages FMNDB504, FMNDB505, or FMNDB507.

This message is issued by the FM/Db2 copy utility, at the completion of the copy operation, to report the number of duplicate row errors that were ignored. This message may be issued as part of message FMNDB503.

This message is issued by the FM/Db2 copy utility, at the completion of the copy operation, to report the number of referential integrity, or constraint errors that were encountered. This message may be issued as part of message FMNDB503.

This message is issued by the FM/Db2 copy utility, at the completion of the copy operation, to report the number of duplicate rows that were updated. This message may be issued as part of message FMNDB503.

The user terminated the FM/Db2 copy function by issuing the CANCEL command, typically by pressing the PF12 PFKey (assigned to CANCEL by default).

This message is issued by the FM/Db2 copy utility when the current copy operation was terminated because of errors. A Db2® ROLLBACK is issued automatically in this situation, and all copy operations are backed out.

The same Db2® object name was specified on the "from" and "to" panels of the FM/Db2 copy utility. Copy from an object to itself is not supported. The Copy operation was canceled.

FM/Db2 is set-up to write audit records to SMF for the current function. A failure occurred while attempting to write an audit record to SMF. The BPX1SMF call resulted in return code return code and reason code reason code, both expressed in decimal. The current FM/Db2 function is terminated.

FM/Db2 detected an SQL statement greater than the 32K-2 limit, which is applicable to Db2® versions prior to Db2® version 8. The SQL statement cannot be executed.

FM/Db2 detected an SQL statement greater than the 2M (2097152) limit, which is applicable to Db2® versions 8, and later. The SQL statement cannot be executed.

This message appears on some FM/Db2 options panels to indicate that the global options are being processed. FM/Db2 offers two levels of option settings for most functions. These are:

1. Global options, selected using option 0 from the FM/Db2 main menu. These options are saved in the ISPF profile data set for the user in the ISPF PROFILE pool, and persist between each FM/Db2 session.
2. Local options, selected from the function entry panel ("Edit options"). These options persist until the user exits the current FM/Db2 function, and overrides any Global options that may be in effect. See the File Manager User's Guide for Db2® Data for a full explanation.

An invalid value for the "default high level qualifier" field was specified, followed by an attempt to leave the panel. The invalid value has been discarded.

An invalid value for one of the "Display width for varying columns" fields was entered on the "Object List Options (2 of 2)" panel, followed by an attempt to leave the panel. The invalid value (or values) has been discarded.

This is a message insert used in the FM/Db2 audit report utility. SQLCODE is the SQLCODE associated with an SQL statement, which might have affected 1 or more rows. row count shows the number of rows, as reported by Db2®, that were affected by the SQL statement. For SQL statements that affect Db2® objects subject to referential integrity constraints, the row count value does not show rows affected in objects other than the primary object affected by the SQL statement./

This is a message insert used in the FM/Db2 audit report utility. count shows the number of SQL statements issued by the FM/Db2 function that might affect Db2® privileges, typically GRANT and REVOKE.

This message is issued at the end of a File Manager/Db2 export function. The number of rows exported, count the Db2® object from which the rows were exported, source Db2 object and the output file name that contains the exported data, file name are shown.

This message is issued by the FM/Db2 export utility. The current FM/Db2 export function is canceled and the FM/Db2 export function entry panel is redisplayed.

This message is issued by the FM/Db2 export utility to indicate that export operations are in progress.

The user canceled the import operation, by pressing the END or CANCEL PFkey.

This message is issued by the FM/Db2 import utility to indicate that import operations are in progress.

This is a message insert, used in the FM/Db2 audit report utility.

This message is issued by the FM/Db2 data create utility. row count is the number of rows that were inserted (created) in the output Db2® object output Db2 object name.

• duplicate count is the number of rows that could not be inserted because of duplicate key (SQLCODE-803) errors.
• error count is the number of rows that could not be inserted because of errors other than duplicate key errors.

The user canceled the FM/Db2 data create function, typically be pressing the PF key assigned to CANCEL.

This message is issued by the FM/Db2 data create utility to indicate that data create operations are in progress.

The current FM/Db2 data create function has been terminated because of errors. No rows have been created in the output Db2® object because a Db2® ROLLBACK statement was issued, and this backed out all uncommitted changes. Prior to the error condition that caused the function to be terminated, row count rows had been inserted into the output Db2® object.

The FM/Db2 import utility, executing in batch mode, did not import row count rows because of duplicate key (SQLCODE-803) errors.

The FM/Db2 import utility, executing in batch mode, did not import row count rows because of unspecified SQL errors.

The FM/Db2 import utility, executing in batch mode, did not import row count rows because the corresponding input record was dropped as part of the record selection process.

The FM/Db2 import utility, executing in batch mode, did not import row count rows because the corresponding input record was dropped as part of the associated REXX procedure processing.

The FM/Db2 data create utility, executing in batch mode, did not create row count rows because Db2® raised a duplicate key error (SQLCODE-803) when FM/Db2 attempted to insert the newly created row in the target Db2® object.

The FM/Db2 data create utility, executing in batch mode, did not create row count rows because Db2® raised an error (other than SQLCODE-803) when FM/Db2 attempted to insert the newly created row in the target Db2® object.

The FM/Db2 import utility, executing in batch mode, updated row count rows. Only columns that are not part of any unique index key are updated.

The FM/Db2 import utility, executing in batch mode, attempted to update existing rows after the insert operation for the record failed with SQLCODE-803 (duplicate key error). The update operation failed.

This message is issued by the FM/Db2 import utility, when executed online. It summarises the statistics for the import operation just completed. This message is issued when the "update existing rows" option is selected, and when no rows were inserted, or updated. row count is the number of rows imported or updated. In this case, 0.

• duplicate row count is the number of records that generated SQLCODE-803 (duplicate key) errors.
• duplicate error count is the number of records for which the update of an existing row failed.
• error row count is the number of records that generated errors other than SQLCODE-803 for the INSERT operation.
• dropped record count is the number of records that were not considered (dropped) as a result of record selection.
• Rexx drop count is the number of records that were dropped via the user-specified REXX procedure.

This message is issued by the FM/Db2 import utility at the completion of the import process. Row count rows were successfully imported.

This message is issued by the FM/Db2 import utility at the completion of the import process. One or more rows were not successfully imported. The import for Row count rows was rolled back.

Upon completion of the FM/Db2 import (DBI), this message is displayed showing the statistics when rows were inserted into the Db2 object.

Upon completion of the FM/Db2 import (DBI), this message is displayed showing the statistics when rows were updated in the Db2 object.

Upon completion of the FM/Db2 import (DBI), this message is displayed showing the statistics when rows were inserted or updated in the Db2 object.

Row count of duplicate rows in error.

This message is issued by either the FM/Db2 export, or FM/Db2 UNLOAD utilities. The template editor was used to deselect all columns, followed by an attempt to execute the function with the modified template. Since a File Manager/Db2 function requires at least one selected column to proceed, all columns are automatically selected and this message is issued.

The FM/Db2 import utility was used to import data into a Db2® view. The Db2® view refers to more than one Db2® table, or refers to one or more views. Import to this type of view is not supported. The import operation is canceled.

The FM/Db2 import utility was used with an input template that has field names that do not match any of the columns in the target Db2® object. The automatic field mapping process used by FM/Db2, cannot reliably determine which fields in the input template correspond with columns in the target Db2® object. Manual mapping of each field in the input template to a column in the target Db2® object is required.

An invalid value was entered in the "Max duplicates" field of the "Copy Options" panel. The valid values are "ALL"or an integer in the range 0-2147483647, inclusive.

A SELECT statement was entered using one of the FM/Db2 functions that allow free-form SQL statements to be processed. When FM/Db2 uses the editor to display the result table from SELECT statement, edit operations may not be possible for free-form SQL statements. This message occurs when the conditions listed in the message are not met. For tables with unique indexes defined, FM/Db2 can use the values in the columns that comprise the unique index to uniquely identify any row of the table. However, this requires that every column in the unique index key is represented in the result table. If reliable edit is not possible, FM/Db2 converts the edit session to browse to avoid any possibility of data corruption.

An attempt was made to update data in the row of a result table for an SQL statement entered using FM/Db2 options 4.2, 4.3, or 4.4. The update failed because Db2® rejected the update. There are various reasons why this error may occur, including editing the result table for a join. The update operation cannot be performed.

An attempt was made to delete a row of a result table for an SQL statement entered using FM/Db2 options 4.2, 4.3, or 4.4. The update failed because Db2® rejected the delete. There are various reasons why this error may occur, including editing the result table for a join. The update operation cannot be performed.

A SELECT statement was entered using FM/Db2 options 4.3, or 4.4, and possibly other options. The SELECT statement includes Db2® parameter markers ('?'). While the use of Db2® parameter markers is valid when using, for example, an application programming language, the use of Db2® parameter markers in SELECT statements processed by FM/Db2 is invalid.

FM/Db2 detected a data type in the Db2® object being edited that is not currently supported. To avoid the possibility of data corruption, FM/Db2 has substituted browse for edit.

FM/Db2 detected one or more XML columns in the object being processed by the current FM/Db2 function (editor, copy, import, export, and print). XML columns are not supported. The function cannot be performed, and processing is terminated.

A File Manager/Db2 import was specified with a non-zero "Max duplicate" count. During the processing of the input data, the number of duplicate row errors reached the specified "Max duplicate" value. The import operation if canceled.

FM/Db2 does not support the processing of Db2® objects with LOB columns. The function cannot be performed and processing is terminated.

This message is issued by the FM/Db2 import utility when there is a mismatch between the template describing the input data, and the data format option for the import data set. The import cannot be processed, and the import is canceled. The type of template specified is template type, which will be one of the following: Db2® Unload; Db2® DSNTIAUL; User defined; Base; FM/Db2 SQLDA; Other. (long).

The FM/Db2 export function can be used to generate a Db2® utility job that will run the Db2® UNLOAD utility for a Db2® table. When this option is selected, the format of the output data is determined by Db2®. Therefore, the data format must be set to '2' (Db2® unload format). The data format for the output data set is specified on the first export options panel, selected using the "edit options" field on the Export function entry panel

The FM/Db2 export utility was executed with an execution option of '3' (Batch, using Db2® unload). The output data set specified on the export 'To' panel, is a partitioned data set includes a member name. While the FM/Db2 export utility can export data in Db2® unload format to a member of a partitioned data set, this is not supported by the Db2® UNLOAD utility.

The FM/Db2 export utility was executed with an execution option of '3' (Batch, using Db2® unload). The output data set specified on the export 'To' panel, is not a sequential data set. While the FM/Db2 export utility can export data in Db2® unload format to non-sequential data sets, the only data set type supported by the Db2® UNLOAD utility is sequential.

An SQL statement and query number value were entered on the "Enter, Execute and Explain SQL" panel (FM/Db2 option 4.3). A query number is only required when the EXPLAIN primary command is issued.

The "Delete existing rows" option was specified for a File Manager/Db2 import. When FM/Db2 attempted to delete all rows from the target Db2® object, Db2® rejected the operation. The import cannot proceed and the import is canceled. No data has been imported.