FM/Db2 messages

FMNDA001

IBM® File Manager for z/OS® Version 14 Release 1

Shows the version and release information for File Manager.

No action required. Informational message.

FMNDA002

IBM® File Manager for z/OS® Db2® Component

Shows the full component name for File Manager.

No action required. Informational message.

FMNDA003

IBM® File Manager/Db2

Shows the abbreviated component name for File Manager.

No action required. Informational message.

FMNDA004

Db2® Component

Shows the short component name for File Manager.

No action required. Informational message.

FMNDA009

IBM® File Manager for z/OS® Version 14 Release 1 Db2 Component Licensed Materials - Property of IBM® and/or HCL5655-Q42Copyright IBM® Corporation 2001, 2017 - All Rights Reserved. Copyright HCL Technologies Ltd. 2017, 2023 - All Rights Reserved. Trademark of International Business Machines

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

No action required. Informational message.

FMNDA011

Panel panel name error. (short). PQUERY error processing ISPF panel panel name. (long)

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

This is a File Manager internal error. Contact IBM® Support for assistance.

FMNDA012

Installation error. Db2® catalog table Db2 catalog table name is not available. Some FM/Db2 functions will be inoperative. Contact your Systems Programmer.

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

File Manager Db2® component requires access to various Db2® catalog tables for correct and optimal functionality. This message indicates an installation related problem. It is possible to define views of the Db2® catalog tables with a user-specified owner (example SYSIBMV), in place of the actual owner, (SYSIBM). One cause of this error is the use of a user-specified owner, but the views of the Db2® catalog tables with the user-specified owner do not exist (have not been created). Check the CATOWNER parameter, FMN2POPI macro in the FMN2POPT module. Check that views of the Db2® catalog tables, (for example SYSIBMV.SYSTABLES) exist. See Preparing to customize FM/Db2 in the File Manager for z/OS® Customization Guide for more information.

FMNDA013

Installation error. SELECT access to Db2® catalog table Db2 catalog table name is required, but is not available. Some FM/Db2 functions will be inoperative. Contact your Systems Programmer.

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 requires SELECT access to various Db2® catalog tables for correct and optimal functionality. This message indicates an installation problem; specifically that the Db2® authid used by the FM/Db2 user does not have SELECT access to the Db2® catalog table Db2 catalog table name. See Preparing to customize FM/Db2 in the File Manager for z/OS® Customization Guide, and to point 8 in "Grant access to the Db2® catalogs", for more information. SELECT access to Db2 catalog table name needs to be GRANTed to the FM/Db2 user who encountered the error.

FMNDA014

Installation error. Access to column column name in Db2® catalog table Db2 catalog table name is required, but is not available. Some FM/Db2 functions will be inoperative. Contact your Systems Programmer.

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.

FM/Db2 requires access to various Db2® catalog tables for correct and optimal functionality. This message indicates an installation related problem, specifically that the Db2® authid used by the FM/Db2 user does not have SELECT access on column column name in Db2® catalog table Db2 catalog table name. See Preparing to customize FM/Db2 in the File Manager for z/OS® Customization Guide, and to point 8 in the checklist "Grant access to the Db2® catalogs - required". SELECT access to column column name of Db2 catalog table name needs to be GRANTed to the FM/Db2 user who encountered the error.

FMNDA020

REQUIRED, BROWSE AUDITED

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.

No action required.

FMNDA021

REQUIRED, BROWSE NOT AUDITED

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.

No action required.

FMNDA022

REQUIRED, SMF, BROWSE AUDITED

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.

No action required.

FMNDA023

REQUIRED, SMF, BROWSE NOT AUDITED

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.

No action required.

FMNDA024

None

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.

No action required.

FMNDA025

SAF-RULE CONTROLLED

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.

No action required.

FMNDA026

SAF-RULE CONTROLLED, AUDITING NOT ALLOWED

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.

No action required.

FMNDA027

DEMAND, BROWSE AUDITED

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.

No action required.

FMNDA028

DEMAND, BROWSE NOT AUDITED

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.

No action required.

FMNDA030

OPTIONAL, OFF, BROWSE AUDITED

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.

No action required.

FMNDA031

OPTIONAL, OFF, BROWSE NOT AUDITED

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.

No action required.

FMNDA032

OPTIONAL, PROFILE, BROWSE AUDITED

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.

No action required.

FMNDA033

OPTIONAL, PROFILE, BROWSE NOT AUDITED

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.

No action required.

FMNDA034

OPTIONAL, SMF, OFF, BROWSE AUDITED

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.

No action required.

FMNDA035

OPTIONAL, SMF, OFF, BROWSE NOT AUDITED

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.

No action required.

FMNDA036

OPTIONAL, SMF, PROFILE, BROWSE AUDITED

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.

No action required.

FMNDA037

OPTIONAL, SMF, PROFILE, BROWSE NOT AUDITED

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.

No action required.

FMNDA038

DEMAND, SMF, BROWSE AUDITED

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.

No action required.

FMNDA039

DEMAND, SMF, BROWSE NOT AUDITED

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.

No action required.

FMNDA040

Recovered from Db2® abend (short). FM/Db2 has recovered from an abend in Db2®. The FM/Db2 function that was executing when the Db2® abend occurred has been terminated. (long)

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.

Document information about the function being used when the abend occurs. If the problem occurs again notify your System Programmer. If there is no Db2-related problem that might explain the abend, contact IBM® Support.

FMNDA050

Object not found (ID) (Short). No Db2® object of the appropriate type matches the combination of object details entered in Db2® system ID. Press Help for more information (Long).

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.

Press the the Help Pfkey (PF1 by default) twice to show, in order, the long message (see above) and the extended help, which is a panel. The information on the help panel is shown below.
  • The specified Db2® object does not exist:
    • Is the spelling correct?
    • Are you connected to the correct Db2® system?
  • There was an uppercase/lowercase mismatch.

    The Translate Db2® object name option is OFF, if the name that was entered contains lower case characters, it may not be recognized. To change the Translate Db2® object name option select option 0.0.2.

  • If no OWNER was specified, FM/Db2 used authid to qualify the name.
  • A synonym name was specified, but the owner of the synonym is not authid.

    A synonym name is only recognized when the current SQLID and the synonym owner match.

  • The object name specified is too long to be displayed on the function entry panel. If you used EXPAND to enter a long name in a field, you must use EXPAND again to clear all parts of the name. Clearing the field on the function entry panel only sets the visible part of the field to spaces.
Read the information on the panel and consider the various causes of the error in turn until the cause is determined.

FMNDA051

Invalid location (Short). Location LOC is not defined in SYSIBM.LOCATIONS at the local server (Long).

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.

You can enter * in the location field and press Enter to show a list of locations defined at the local server. This feature may not be available if the product installer has chosen to disable it. If you cannot determine the reason why the entered location value is invalid contact your Db2® administrator for assistance.

FMNDA052

Object not found (Short). No Db2® object at location LOC matches the combination of object details entered at Db2® system ID. Press Help for more information. Object not found (short).

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.

Press the Help PFkey (PF1 by default) twice to show, in order, the long message (see above) and the extended help, which is a panel. The information on the help panel is shown below:

Possible reasons why Db2® could not find this object include:

  • The specified Db2® object does not exist:
    • Is the spelling correct?
    • Have you specified the correct location?
  • There was an uppercase/lowercase mismatch. The Translate Db2® object name option is OFF, if the name that was entered contains lower case characters, it may not be recognized. To change the Translate Db2® object name option select option 0.0.2.
  • If no OWNER was specified, FM/Db2 used authid to qualify the name.
  • A synonym name was specified, but the owner of the synonym is not specified.

    A synonym name is only recognized when the current SQLID and the synonym owner match.

  • The object name specified is too long to be displayed on the function entry panel. If you used EXPAND to enter a long name in a field, you must use EXPAND again to clear all parts of the name. Clearing the field on the function entry panel only sets the visible part of the field to spaces.

Read the information on the panel and consider the various causes of the error in turn until the cause is determined.

FMNDA053

Check name (spaces) (Short). The Db2® object name cannot be found. There are two or more consecutive spaces in the object name, this might indicate unwanted text in the non-visible parts of a scrollable field. Place the cursor on the object name field and press the Expand PF key to verify the contents. (long).

A value entered in a name field has two or more consecutive spaces, for example: ABC  FG. The name field is an ISPF scrollable field, allowing up to 128 characters to be entered, however not all characters are displayed. It is possible that unwanted information has been entered in the part of the field that is not displayed. Because FM/Db2 validates the DB2® name based on the entire contents of the field, Object not found errors will occur.

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.

Place the cursor on the object name field and press the PFKey assigned to EXPAND (PF4 by default) to show the complete field contents. If the EXPAND key is not available you can type the EXPAND command on the command line, position the cursor on the object name field and press ENTER to show the complete field contents. Remove any spurious data and retry the operation.

FMNDA054

Check owner (spaces) (Short). The Db2® object name cannot be found. There are two or more consecutive spaces in the object owner, this might indicate unwanted text in the non-visible parts of a scrollable field. Place the cursor on the object owner field and press the Expand PF key to verify the contents.

A value entered in an owner field has two or more consecutive spaces, for example: ABC  FG. The owner field is an ISPF scrollable field, allowing up to 128 characters to be entered, however not all characters are displayed. It is possible that unwanted information has been entered in the part of the field that is not displayed. Because FM/Db2 validates the DB2® owner based on the entire contents of the field, Object not found errors will occur.

Place the cursor on the object owner field and press the PFKey assigned to EXPAND (PF4 by default) to show the complete field contents. If the EXPAND key is not available you can type the EXPAND command on the command line, position the cursor on the object owner field and press ENTER to show the complete field contents. Remove any spurious data and retry the operation.

FMNDA055

No Db2® TABLE matches the value entered. It is possible a Db2® object (eg view) that matches the name entered exists - however the selected Db2® utility supports Db2® tables ONLY. (long).

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.

Use the FM/Db2 object list utility to display information about the Db2® object. Determine whether the object exists, and determine the type of the object (table, view etc). Consult the Db2® utilities manual for the appropriate version of Db2® to determine which object types may be used.

FMNDA100

Alloc. error -unit (short).The attempt to allocate a temporary data set for the SQL statement failed. UNIT unit is invalid. Check the temporary data set allocation option values. (long).

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.

Check the value specified for the UNIT parameter on the "Set Temporary Data Set Allocation Options" panel. Remove any value and retry the operation. If this resolves the problem, contact your system's programmer for advice on valid/invalid UNIT values.

FMNDA997

**** Limit of Rows Retrieved ****

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.

No action required. Informational message.

FMNDA998

Internal Logic Error (module name) - message

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

Contact IBM® Support.

FMNDB000

JESCT not available (short). JESCT control block currently not available for Db2® subsystem selection. (long).

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

Contact IBM® Support.

FMNDB001

No Db2® subsystems (short). No Db2® Subsystems have been defined on this system. File Manager Db2 component can not run on this system. (long).

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

If there are Db2® systems defined on the current z/OS® system, contact IBM® Support.

FMNDB002

SSID Db2 SSID not matched (short). No Db2® Subsystems matching Db2 SSID are defined on this system. (long).

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.

No action required. Informational message. Clear the Db2® SSID entirely to show all Db2® systems.

FMNDB003

Db2 SSID not defined to z/OS® (short) . Db2® Subsystem/Group Db2 SSID is not defined to the local z/OS® system. (long).

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.

Check that Db2 SSID is correctly specified. Correct the name and try again.

FMNDB004

SSID Db2 SSID not active (short). Db2® subsystem/group Db2 SSID is not currently active. (long).

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

FM/Db2 cannot connect to inactive Db2® systems. Determine the reason why the Db2® system is inactive. When the Db2® system is started, attempt the connection again.

FMNDB005

Already connected (short). FM/Db2 is currently connected to Db2® system Db2 SSID. (long).

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.

None if Db2 SSID was correctly specified. Otherwise, check the Db2® SSID, make appropriate corrections, and try again.

FMNDB006

Cannot connect to Db2® Db2 SSID, RRSAF function RC &RC. Reason reason code.

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.

This error indicates an installation error. Confirm that the RRSAF attachment is required. You will typically find that the CAF attachment meets all your requirements. The Db2® attachment used by FM/Db2 is specified in the FMN2POPT module. See See File Manager for z/OS® Customization Guide for a detailed explanation. Ensure that the appropriate Db2® interface module (DSNRLI) is accessible to FM/Db2. If these actions fail to resolve the problem, contact IBM® Support.

FMNDB007

A Db2® Subsystem has not been specified.

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

Use the "Db2® SSID" field on the FM/Db2 main menu to specify the name of a Db2® system.

FMNDB008

Subsystem Db2 SSID does not identify a uniquely active Db2® subsystem

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

Specify an unambiguous value.

FMNDB009

Db2® subsystem Db2 SSID is not currently active on this system.

The specified Db2® SSID value Db2 SSID is inactive.

Take action to start the Db2® system. When the Db2® system is active, retry the operation.

FMNDB010

Row Row value 1 of Row value 2

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.

No action required. Informational message.

FMNDB011

Invalid selection (short). Enter "S" or "/ " to select the required Db2® subsystem. (long).

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 "/ ".

Use either "S" or "/ " to select the required entry.

FMNDB012

SSID Db2 SSID not active (short). Selected Db2® subsystem Db2 SSID is not currently active on this system. (long).

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

Determine why the Db2® system is inactive and take action to start it. When the Db2® system is active, retry the operation.

FMNDB013

Selection terminated (short) Db2® subsystem selection was terminated with the EXIT PF key command. File Manager Db2® is not currently connected to any Db2® subsystem. (long)

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.

No action required. Informational message. It is necessary to connect to a Db2® system before performing any FM/Db2 functions.

FMNDB014

Display refreshed (short). List of Db2® Subsystems has been refreshed using current information. (long).

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

No action required. Informational message.

FMNDB015

SSID Db2 SSID displayed (short). Db2® Subsystems matching Db2 SSID are displayed. (long).

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

No action required. Informational message.

FMNDB016

Command not active (short). The command to change the Db2® subsystem is not available from this panel. (long).

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

The currently connected Db2® SSID can only be changed when no FM/Db2 function is active. Return to a function-entry, or menu panel, and reissue the command.

FMNDB017

SSID name required (short). Enter the Db2® subsystem name that FM/Db2 should connect to. (long).

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

The command to change the currently connected Db2® system requires an operand, the Db2® SSID of the Db2® system to which connection is desired. Reissue the command with the required Db2® system SSID as the operand.

FMNDB018

Invalid remote server (short). Remote server Db2 server name is not a Db2® UDB for z/OS® system. Connection to remote servers that are not Db2® UDB for z/OS® servers is not supported. (long).

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.

Connection to this remote Db2® server is not supported. Specify another name.

FMNDB019

Version Db2 version invalid (short). The remote Db2® version/release is Db2 version. Connection is supported for Db2® Version 9 and later systems only. (long).

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.

Connection to this remote Db2® server is not supported. Specify another name.

FMNDB020

Operating System is unsupported. Can not run File Manager Db2 component.

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.

Ensure that the host operating system is at a level specified in the Program Directory. If you believe that the host operating system is at a supported level, contact IBM® Support.

FMNDB021

Error in function Callable Service Routine, Return code return code.

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

Contact IBM® Support.

FMNDB022

Db2® Subsystem not set (short). Error invoking File Manager Db2 component. Db2® Subsystem has not been set. (long).

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

If the message occurs in batch, check that the Db2® SSID value is correctly specified in the JCL. If this fails to resolve the problem, start FM/Db2 online and regenerate the batch JCL. If the batch job still fails contact IBM® Support. If the message occurs online, return to the FM/Db2 main menu and enter the name of a valid Db2® SSID in the Db2® SSID field, press Enter to connect.

FMNDB023

Cannot connect to Db2® Db2 SSID, CAF function RC return code, Reason reason code.

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.

This message usually indicates an installation or set up problem. The most likely causes are:

  1. Not binding the FM/Db2 plan (FMN2PLAN) by default.
  2. Specifying an incorrect Db2® plan name in the FMN2POPT module.

See See File Manager for z/OS® Customization Guide for more information.

FMNDB024

Unable to load Db2® Interface module module name. Abend Code abend code-reason code. Check STEPLIB/LINKLIST for Db2® load libraries.

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

This is probably a customization or setup problem. If the Abend is 806 (module not found):

  1. Check that the Db2® load library has been correctly specified in the FMN2SSDM macro for the Db2® system in question.
  2. If the FMN2POPT module does not include the Db2® load library names for the Db2® system, check any applicable STEPLIB/JOBLIB and LINKLIST for the Db2® load library. The Db2® load library must reside in a library that is accessible using the standard search order for the LOAD macro.

For other abends refer to point (1) as a starting point. If this fails to resolve the problem, contact IBM® Support.

FMNDB025

Not currently connected to a Db2® subsystem.

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

No action required. Informational message. It will be necessary to connect to a Db2® system prior to performing any FM/Db2 functions.

FMNDB026

Subsystem: Db2 SSID, Db2® release: Db2 VRM indicator.

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

No action required. Informational message. issued in a File Manager/Db2 batch job.

FMNDB027

FM/Db2 plans: Plan name 1, Plan name 2

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

No action required. Informational message. issued in a File Manager/Db2 batch job.

FMNDB028

Description: user specified description.

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.

No action required. Informational message.

FMNDB029

Db2 SSID executing Db2® level Db2 level 1. Minimum supported level is Db2 level 2.

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.

Connection to the Db2® system is not supported. See See File Manager for z/OS® Customization Guide and See User's Guide and Reference for information on supported Db2® versions, for the version of FM/Db2 in use.

FMNDB030

Db2I unavailable (short). Unable to start Db2I. Check STEPLIB/LINKLIST for Db2® libraries. (long).

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

This error indicates an installation or setup problem. Ensure that the Db2® libraries are available to the FM/Db2 user. The recommended way to do this is to code the Db2® libraries in the FMN2SSDM macro entry for each Db2® system that will be accessed by FM/Db2. See See File Manager for z/OS® Customization Guide for more information.

FMNDB031

SQL ID not authorized (short). You are not authorized to use the SQL user ID Db2 authid on Db2® Subsystem Db2 SSID. (long).

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.

Consult with either the Db2® or Security Administrator as to the reason why access to Db2 authid is not available.

FMNDB032

You are not authorized to use the SQL user ID 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.

Consult with either the Db2® or Security Administrator as to the reason why access to Db2 authid is not available.

FMNDB033

Auditing: Audit status :

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

No action required. Informational message.

FMNDB034

No Db2® subsystem with name Db2 SSID. CAF function RC return code, Reason reason code.

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.

Check the Db2® system name and try again.

FMNDB035

Db2® group/subsystem Db2 SSID is not active, CAF function RC return code, Reason reason code.

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.

Start the Db2® system. Retry the operation.

FMNDB036

Not authorized to connect to Db2 SSID, CAF function function RC return code, Reason reason code.

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.

Consult with either the Db2® or Security Administrator as to the reason why the FM/Db2 user is not authorized to connect to the Db2® system Db2 SSID.

FMNDB037

FM/Db2 not installed on Db2 SSID, CAF function function RC return code, Reasonreason code.

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.

Verify that FM/Db2 is installed on Db2® system Db2 SSID. Retry the operation.

FMNDB038

Unable to load options module module name. Probable installation error.

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.

Check the allocation of the FM/Db2 load library using, for example, 'TSO ISRDDN&' (under ISPF). Ensure that module name is located in a load library accessible to the FM/Db2 user.

FMNDB039

FMN2POPI module invalid (short). The internal structure of FMN2POPT is invalid. Probable installation error. (long).

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

The FMN2POPT module was assembled using an older version of FM/Db2. Reassemble the FMN2POPT module, paying attention to the SYSLIB statements in the JCL, to ensure the correct versions of the FM/Db2 macros are used. Retry the operation.

FMNDB040

SSID Db2 SSID not available (short). Installation settings prevent the selection of Db2® subsystem/group Db2 SSID. (long).

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.

Select another Db2® system.

FMNDB041

Incompatible connection already active, CAF function, RC return code, Reasonreason code.

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.

This is an installation error. Check the specification of the Db2® libraries in the FMN2POPT, FMN2SSDM macro for the appropriate Db2® system, with attention to the Version/maintenance level of these libraries compared with the Version/maintenance level of the Db2® system.

FMNDB042

Db2 SSID Release Minimum Release (short). Db2 SSID executing Db2® level Release. The minimum supported level of Db2® for this release of File Manager is Minimum Release. FM/Db2 may operate successfully with Db2® Version 8, however no support will be provided for any Version 8 specific problems that may be encountered.

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.

No action required. Informational message. FM/Db2 should operate without issues. However should a problem be encountered that is specific to Db2® version 8, no support will be available.

FMNDB043

Db2 SSIDReleaseMaximum Release (short). Db2 SSID executing Db2® level Release. This version and release of File Manager does not currently support connection to Db2® Maximum Release (or later) subsystems.

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.

Contact IBM® Support for information about more recent versions of FM/Db2 which may support the Db2® version/release of Db2 SSID.

FMNDB044

Communications error (short). FM/Db2 encountered an SQL error SQL error code attempting to access the Db2® system at Db2 location name. This indicates that the remote Db2® system is not available, or that there was a security related problem. (long).

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

Look up SQL error code in the Db2® messages and codes manual and take the action indicated. This error indicates a set up problem. One possibility is incorrect DRDA® definitions for Db2® location name at the local Db2® server.

FMNDB045

Not defined.

A location nickname was not defined in the FMN2POPT module.

Check the FMN2SSDM definitions in the FMN2POPT module and add the location nickname to the appropriate entry.

FMNDB046

Defined but no location specified.

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

Check the FMN2SSDM macro for the currently connected Db2® system. Ensure that both a location and location nickname are specified.

FMNDB047

Authorization error (short). FM/Db2 encountered an SQL error (-725) attempting to access the Db2® system at Remote location name. This can occur when the user has changed the SQLID at the local Db2® system, but the user does not have authority to use this SQLID at the remote Db2® system. (long).

Refer to the long message.

Ensure that the user has access to the remote Db2® system Remote location name using the currently set Db2® SQLID.

FMNDB048

FMN2DATA load failed (short). Unable to load FMN2DATA module. Probable installation error. (long).

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

This is a customization or set up problem. Check that FMN2DATA is present in the load libraries accessible to the FM/Db2 user. This module is normally located in the SFMNMOD1 library.

FMNDB049

FMN2DENU load failed (short). Unable to load FMN2DENU module. Probable installation error. (long).

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

This is a customization or setup problem. Check that FMN2DENU is present in the load libraries accessible to the FM/Db2 user. This module is normally located in the SFMNMOD1 library.

FMNDB050

ATTACH of FM/Db2 subtask program failed with return code return code.

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.

This is an internal error. Retry the operation. If the problem persists check for installation related problems and contact IBM® Support.

FMNDB051

Communications error (SQLCODE=SQL error code) accessing Db2 SSID.

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

Look up SQL error code in the Db2® messages and codes manual and take the action indicated.

FMNDB052

Db2® server server name is not a Db2® UDB for z/OS® server, code=return 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.

Specify the name of a Db2® UDB for z/OS® server only.

FMNDB053

SET DECFLOAT ROUNDING MODE failed with return code return code.

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

Check that the Db2® system is operational. If the problem persists contact IBM® Support.

FMNDB054

SSID Db2® SSID not defined (short). There is no definition (FMN2SSDM macro entry) for Db2® subsystem or group Db2 SSID in the FM/Db2 installation module (FMN2POPT). Contact the person who installed FM/Db2. (long).

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.

There are two usual approaches for resolving this error:

  1. Add an FMN2SSDM macro entry for every Db2® system that FM/Db2 will access to the FMN2POPT, as recommended in the File Manager for z/OS® Customization Guide.
  2. Specify CONNECT=ANY in the FMN2POPI macro in the FMN2POPT. While this will allow FM/Db2 to attempt connection to ANY Db2® system, it does not necessarily remove the need to define an FMN2SSDM macro entry for every Db2® system that FM/Db2 will connect to. See the File Manager for z/OS® Customization Guide for detailed setup information.

FMNDB055

Selection canceled (short). Db2® subsystem selection was canceled. Connection to the previously connected Db2® system has been re-established.

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

No action required. This is an informational message.

FMNDB056

Selection canceled (short). Db2® subsystem selection was canceled. File Manager Db2® is not currently connected to any Db2® subsystem.

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.

No action required. This is an informational message. It will be necessary to connect to a Db2® system prior to performing any FM/Db2 functions.

FMNDB057

Db2® limits the output returned from a Db2® command. This limit has been reached and the output has been truncated.

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

No action required. This is an informational message. Refine the Db2® command to be more specific.

FMNDB058

You cannot change the SQLID until FM/Db2 is connected to a Db2® subsystem or group.

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.

Change the Db2® SQLID back to the default value, typically the user TSO logon ID. Now enter a valid Db2® SSID in the Db2® SSID field and press Enter to establish connection to the Db2® system. When the connection is successful, attempt to change the Db2® SQLID.

FMNDB059

** not defined in installation module.

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

No action required. This is an informational message. Refer to File Manager for z/OS® Customization Guide for detailed information about how to code entries in the FMN2POPT module.

FMNDB060

Unable to load Db2® Interface modulename. Abend Code abend code-reason code. Check STEPLIB/LINKLIST for Db2® load libraries.

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.

Check the STEPLIB or JOBLIB statement in the batch job. Ensure that the appropriate Db2® load library is included. If the batch job was generated using FM/Db2 online, the Db2® libraries are automatically included, as specified in the FMN2SSDM macro entry in the FMN2POPT for the appropriate Db2® system. This will not occur if there is no FMN2SSDM macro entry for the Db2® system, or if the Db2® libraries are not included in the FMN2SSDM macro.

FMNDB061

Catalog table table name is missing.

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

If views of the Db2® catalog are in use (CATOWNER=xxxx in the FMN2POPI macro, FMN2POPT module, xxxx is not SYSIBM) then ensure that the appropriate view xxxx.table name has been created.

FMNDB062

No select access to catalog table table name.

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

Ensure that the Db2® authid associated with the batch job has SELECT access to table table name.

FMNDB063

Cannot access column in catalog table table name.

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.

If views of the Db2® catalog are in use (CATOWNER=xxxx in the FMN2POPI macro, FMN2POPT module, xxxx is not SYSIBM) then ensure that the appropriate view xxxx.table name has been created. Further, ensure that column column is included in view xxxx.table name.

FMNDB064

Db2® Abend Code abend code-reason code accessing name. Notify your systems programmer.

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.

Look up the Db2® Abend code and reason code in the DB2 for z/OS Messages and Codes. In most cases this type of error indicates an error with the batch job (for example, the wrong Db2® libraries being specified). Check the specification of the Db2® libraries in the FMN2SSDM macro entry for the appropriate Db2® system (FMN2POPT module). See the File Manager for z/OS® Customization Guide online function, use FM/Db2 to regenerate the batch JCL and retry the operation.

FMNDB065

GEN command failed (short). The FM/Db2 GEN command failed - RC=return code. Please see your Systems Support staff for assistance. (long).

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

Possible failures include space related abends (x37) for the data sets used by the GEN code. If this is the case there will be an associated abend issued. Respond to the Abend by deleting and recreating the data set with more space, and retry the operation.

FMNDB066

No SSID parameter was passed to FMN2INEX. The last connected Db2® subsystem, if any, is used. Check that the connected Db2® subsystem is, in fact, what was intended.

The REXX EXEC FMN2INEX can be used to invoke FM/Db2 by an external call. The REXX EXEC requires various parameters, including the Db2® SSID of the Db2® system that FM/Db2 should connect to. This was not provided.

Check the method used to invoke the FMN2INEX exec and ensure that a Db2® SSID is provided.

FMNDB067

Invalid option code (short). The option code passed to FMN2INEX is either invalid or not supported. The option code has been discarded. (long).

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.

The function codes that may be passed to File Manager for z/OS® Customization Guide. Ensure that a supported function code is specified.

FMNDB068

Command not active (short). The command to change the Db2® subsystem is not available when FM/Db2 is invoked remotely. (long).

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

No action required. Informational message.

FMNDB069

Command not available (short). Db2® commands cannot be issued when FM/Db2 has been started remotely. (long).

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

No action required. Informational message.

FMNDB070

Possible causes - Missing/invalid FMN2POPT module, eg invalid plan name.

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

The usual causes of this error are:

  1. FM/Db2 is not installed on the target Db2® system.
  2. The FMN2POPT module in use specifies an invalid plan name, perhaps the specified plan does not exist, or the plan exists but is invalid.

FMNDB071

Current® SQLID (short). The current SQLID is the value specified. (long).

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

No action required. Informational message.

FMNDB072

SQLID value required (short). The SQLID command requires a value. Enter the new SQLID after the SQLID keyword, eg ''SQLID FRANK''. (long).

The SQLID command was issued without an operand.

Specify, for example, the desired SQLID after the SQLID command:

SQLID FRED

FMNDB073

SQLID cmd not available (short). The SQLID command is not available from this panel. (long).

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

Return to a higher level panel , for example a function entry panel, or menu panel, and reissue the command.

FMNDB074

UNICODE conversion error codepage CCSID 1 to codepage CCSID 2.

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

One reason for this error is that the z/OS® Unicode translation service for the specified CCSID pair has not been set up. Contact your System Programmer. If this does not solve the problem, contact IBM® Support.

FMNDB075

SQLID = SQLID (short). The current SQLID has been changed toSQLID. (long).

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

No action required. Informational message.

FMNDB076

*** Rollback occurred. Transactions since start of session or last commit have been backed out. ***

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

No action required. Informational message.

FMNDB077

A Db2® commit has been issued.

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

No action required. Informational message.

FMNDB078

UNICODE conversion error. UNICODE conversion error from codepage CCSID 1 to codepage CCSID 2. Return code return code, reason code reason code from CUNLCNV routine.

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.

One reason for this error is that the z/OS® Unicode translation service for the specified CCSID pair has not been set up. Contact your System Programmer. If this does not resolve the problem, contact IBM® Support.

FMNDB079

Change SSID first (short). An attempt to navigate to a File Manager/Db2 function was made while simultaneously changing the Db2® SSID. This is not supported. First change the Db2® SSID and then navigate to the required function. (long).

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.

The use of '=' is not supported within File Manager for z/OS® Customization Guide for Db2® data. In situations where a change in SQLID is required to execute some FM/Db2 function, first change the SQLID, then navigate to the required function.

FMNDB091

Invalid selection (short). Enter 'S' or '/' to select the required object type. (long).

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 '/'.

Use one of the characters indicated to select the object.

FMNDB092

Invalid selection (short). Enter 'S' or '/' to select the required line command. (long).

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 '/'.

Use one of the characters indicated to select the object.

FMNDB093

Invalid selection (short). Valid selections are 'S', '/', 'A', 'D', 'U', 'UO' and 'UW'. (long).

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.

Use one of the character or characters shown in the long message to select the column.

FMNDB094

OBJIN|OBJOUT Db2® object not found.

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.

Correct the Db2® object name, re-submit the batch job.

FMNDB095

OBJIN|OBJOUT Db2® object name error. The name specified returned multiple Db2® objects.

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.

Correct the Db2® object name to specify a less generic Db2® object name, re-submit the batch job.

FMNDB096

OBJIN|OBJOUT Db2® location not found.

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.

Determine the failing Db2® location value. Ensure that this Db2® location is accessible from the Db2® system specified in the PARM statement, re-submit the batch job.

FMNDB098

Db2 SSID; executing Db2® level release. Maximum supported level is Maximum release.

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.

Contact IBM® Support for information about which versions of FM/Db2 support Db2® systems at version or release release.

FMNDB099

Invalid Db2® SSID (short). The Db2® SSID is too long. Specify a 1-4 character value. (long).

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.

Check the Db2® SSID that was specified; make corrections. Retry the operation.

FMNDB100

SQLCODE SQLCODE. Statement type (short). SQLCODE SQLCODE was encountered while issuing a Statement type statement.

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

Look up the failing SQLCODE in the DB2 for z/OS Messages and Codes manual. If the message was issued when processing a user-specified SQL statement, make adjustments to the statement and retry the operation.

FMNDB101

SQL error message

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.

Look up the failing SQLCODE in the Db2® Messages and Codes manual. If the message was issued when processing a user-specified SQL statement, make adjustments to the statement and retry the operation.

FMNDB107

Remote server not found (short). FM/Db2 encountered an SQL error SQLCODE attempting to access the Db2® system at Db2 remote server. This might indicate that the remote Db2® system is not available or does not exist. Check the definitions in SYSIBM.LOCATIONS. (long).

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.

Look up SQLCODE in the DB2 for z/OS Messages and Codes manual and follow the recommended course of action. This error can occur in the following situations (non-exhaustive list):

  1. DRDA® definition problems.
  2. The remote Db2® system does not exist, is not active, is not available.
  3. Communication problems.

FMNDB108

Different Db2® release (short). The release level of the local Db2® system is different to the release level of the Db2® system which you have just accessed. The choice of Db2® object types has been refreshed to show those object types supported on the remote or local system. Press ENTER again to get the requested list. (long).

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.

Ensure that the requested object type is still valid at the new Db2® system. Press Enter again to see the information for the requested object types.

FMNDB109

No matching locations (short). The location name specification does not match any locations defined to the local Db2® server. (long).

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.

Check the location specification and retry the operation. Use * in the location field to list all possible locations.

FMNDB110

Internal error (ABEND) Abend code. Function terminated.

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

This is an internal error. The list of File Manager internal abend codes is not documented for external use. Record details of the circumstances that lead to the Abend, including the Abend code, and contact support.

FMNDB118

Function active (short). The command to change the Db2® subsystem is not available while a File Manager/Db2 function is in progress.

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.

Exit the current FM/Db2 function by returning to a function entry panel, or menu panel. Reissue the command to change the Db2® system.

FMNDB119

Db2 authid not authorized (short). You are not authorized to use the Db2 authid on Db2® Subsystem Db2 SSID. (long).

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.

The rules governing the use of Db2® authids can be complex, depending on whether an external security server is used to control Db2® authorizations and whether a Db2® authorization exit is in use. In most cases a user needs SYSADM authority or similar to use other SQLIDs. Contact either your Db2® System Administrator, or the site Security Administrator for assistance.

FMNDB120

Inactivity time-out (Short). The editor session ended because of inactivity. Any uncommitted changes have been rolled back. Contact your System's Administrator for more information.

There is a site-imposed limit on how long an FM/Db2 editor session can be inactive before it is canceled. This limit has been exceeded. The current editor session has been canceled, any uncommitted changed have been rolled back.
None.

FMNDB145

Recursive alias (short). The object name entered is an alias that refers to an alias defined at the current server, which is not permitted. Specify an alias name that refers to an object, that is, not an alias. (long).

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 ALIAS that refers to a Db2® object (Table/View/Synonym) is supported. Resolve the ALIAS to the point where the name entered refers to an actual object and specify that value. Alternatively, specify the target object name directly.

FMNDB147

Data sampling requires that FM/Db2 use a Db2 scrollable cursor, however, the use of Db2 scrollable cursors was disabled by the product installer. The operation cannot be performed. (long)

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.

None.

FMNDB149

Count of unknown

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.

No action required. Informational message. In Large editor mode the number of rows in the result table is not available until the user scrolls to the end of the Db2® object. After the user scrolls to the end of the Db2® object, 'unknown' is replaced with the number of rows in the Db2® object/result table.

FMNDB150

Table locking disabled (short). Table locking was requested but failed, as can occur with eg catalog tables. (long).

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.

No action required. Informational message. This message can be issued when a Db2® catalog table is selected for edit.

FMNDB153

Commit issued (short). All pending changes to the database have been successfully committed. (long).

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.

No action required. Informational message.

FMNDB154

Commit issued (Errors) (short). Successful changes committed, unsuccessful changes remain pending. (long).

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.

No action required. Informational message. Use the 'e' prefix command to identify rows that are in error. If in doubt as to which changes have been made, exit the current editor session and restart.

FMNDB155

Key information on (short). Key and index information will be displayed in single format (long).

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.

No action required. Informational message.

FMNDB156

Key information off (short). Key and index information will not be displayed in single format (long).

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.

No action required. Informational message.

FMNDB157

Rollback issued (short). A Db2® rollback has been issued. Any uncommitted changes are lost. (long).

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.

No action required. Informational message.

FMNDB158

Auxiliary Table (short). Edit or browse of an auxiliary table is not possible. (long).

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

No action required. Informational message. Only base Db2® objects can be edited.

FMNDB159

count rows fetched.

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.

No action required. Informational message. Not all the rows in the Db2® table have been loaded into the FM/Db2 editor. Consequently, any edit operations apply only to those rows loaded.

FMNDB160

Insufficient storage (short). There was insufficient virtual storage to edit/browse this object. Use the Rows to Retrieve option or specify a row selection criteria to limit the amount of data retrieved from Db2®. (long).

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.

Review Restricting the data that FM/Db2 loads from Db2, covering memory usage by the FM/Db2 editor. There are various options for resolving this issue, including (non-exhaustive list):

  1. Increase the TSO Region Size.
  2. Use the FM/Db2 editor in "Large" mode, to minimize memory usage.
  3. Specify a lower "row count"value.
  4. Use record selection criteria, WHERE clause, to reduce the number of rows that might be loaded.

FMNDB161

Warning: USA time format (short). The Db2® object being edited contains at least 1 column with the TIME data type and the system options are set to display these columns in USA format (for example, HH:MM AM|PM You may not be able to delete or update rows in this Db2® object because of the loss of information associated with the use of this format. See the Systems Options tutorial for more information. (long).

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.

If edit operations are required for this table, consider changing the FM/Db2 system options to display TIME columns in either ISO or JIS formats, both of which show the full seconds value. For more information about the TIME display formats supported by Db2®, see the DB2 for z/OS SQL Reference.

FMNDB163

Copy Pending (short). Updates are not allowed to tablespace table space name in database name because the tablespace is marked as COPY PENDING. In order to edit the table you should cancel the current edit session, then take action to remove the copy pending status. One way to do this is to run the Db2® COPY utility. See the Db2® Administration Guide for a full explanation. (long).

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.

The recommended way to remove the COPY PENDING status is to run the Db2® COPY utility against the Db2® object. Consult your Db2® System Administrator for the best way to proceed.

FMNDB164

Syntax error (short). The WHERE clause contains a syntax error. (long).

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.

Examine the WHERE clause for any possible errors. You can copy the complete SQL to either the clipboard, or a temporary data set, and then use an SQL processor such as FM/Db2 options 4.3, 4.4, or SPUFI to execute the statement. Any SQL errors for the statement will also be reported.

FMNDB165

Invalid column name (short). The WHERE clause contains an invalid column name, column name. (long).

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.

Check the WHERE clause and locate any occurrences of column name. Ensure that this column name is one of the columns in the Db2® object, or result table. Retry the operation.

FMNDB166

Open quoted string (short). The WHERE clause contains an open quoted string. (long).

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 ="
Check the WHERE clause, and count the number of apostrophes and double quotation marks. An odd number for either indicates a problem. Make corrections and retry the operation. The rules for quoted strings can be found in the DB2 for z/OS SQL Reference.

FMNDB167

SQLCODE SQLCODE (short). Execution of the SQL statement will result in SQLCODE SQLCODE. (long).

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.

Look up the SQLCODE in the DB2 for z/OS Messages and Codes manual and respond as directed.

FMNDB170

Dependent rows (short). This related edit session shows only those rows that would be affected by the change to parent table Parent table name. The foreign key columns are marked with a K in the scale line, and are shown on the left of the display in table display format. In general, the foreign key value must be changed, or the row deleted, for the operation on the parent table to proceed.

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

The reason for editing a dependent table is to resolve foreign key values that are preventing the deletion of the corresponding primary key in the parent table. In some situations the dependent edit session will show all rows, not just those with the foreign key values that match the primary key value in the parent table.

FMNDB171

Parent table (short). In this related edit session the primary key columns are marked with a P in the scale line and are shown on the left of the display (table display format). You can use the IP prefix command to insert a new row with the primary key set to the foreign key value entered in the edit session of dependent table dependent table. (long).

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

The reason for editing the parent table is to add a new primary key, so that a row in a dependent table with a new foreign key, that matches the primary key, can be added.

FMNDB173

All rows (short). This related edit session shows all rows of the table. Parent table parent table name is subject to a self referencing constraint such that deleting or changing a primary or parent key value may result in the recursive deletion of other rows in the parent table. FM/Db2 cannot determine which rows in table dependent table name will be affected by such an operation. (long).

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

The reason for editing a dependent table is to resolve foreign key values that are preventing the deletion of the corresponding primary key in the parent table.

FMNDB174

Commit issued (short). A Db2® commit has been issued. (long).

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.

No action required. Informational message.

FMNDB175

Invalid value (short). Valid values are TABL and SNGL. There are no unformatted edit modes in FM/Db2. (long).

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

Check the value that was entered. There are two display modes when using the FM/Db2 editor:

  1. TABL (Can be abbreviated to T, TA, TAB).

    In this mode each horizontal line on the screen shows one row of data from the Db2® object or result table being processed.

  2. SNGL (Can be abbreviated to S, SN, SNG).

    In this mode the data for a single row of the Db2® object or result table being processed is displayed. The data for each column is shown, with the column name on the left and the data for that column on the right.

FMNDB176

Object/Alias not found (short). The specified object or alias was not found in the catalog, or the target of an alias does not exist.

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.

Determine why the Db2® Object Name does not exist.

FMNDB177

Warning: USA time format (short). The Db2® object being exported contains at least 1 column with the TIME data type and the system options are set to externalize these columns in USA format (HH:MM AM|PM). The exported data will not contain seconds information because of the loss of information associated with the use of this format. See the Systems Options tutorial for more information. (long).

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 is an informational message. As noted in the long message text, in this situation the exported data for the TIME columns will lose any seconds value. If this is intended or desired, then no action is required. When no loss of information is required, consider changing the "External Format for TIME Data Type Columns" value to either 'ISO' or 'JIS', both of which include the seconds information.

FMNDB178

Warning: USA time format (short). The Db2® object being copied contains at least 1 column with the TIME datatype and the system options are set to externalize these columns in USA format (HH:MM AMPM). The data copied to the target table will not contain second's information because of the loss of information associated with the use of this format. See the Systems Options tutorial for more information. (long).

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 is an informational message. As noted in the long message text, in this situation the copied data for the TIME columns will lose any seconds value. If this is intended or desired then no action is required. When no loss of information is required, consider changing the "External Format for TIME Data Type Columns" value to either 'ISO' or 'JIS', both of which include the seconds information.

FMNDB179

Cancel recommended (short). Db2® has rolled back the current unit of work (SQLCODE -911) because of a deadlock with another task. ALL UNCOMMITTED CHANGES made during the current edit session have been lost. Consequently, the data displayed in the current edit session may not reflect the current state of the Db2® table. It is recommended that you cancel the current edit session and restart with a fresh copy of the data. (long).

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.

Cancel the current edit session and restart. Make a change to a single row and attempt to save the change. If the SQLCODE-911 reoccurs, contact your Db2® System Administrator for assistance in determining why a deadlock is occurring.

FMNDB180

Related edit failed (short). Initialization of the related edit session failed. The reason is that the product has not been installed correctly. If LIBDEFs are used to allocate the File Manager Db2 component libraries, the related edit session exec, FMN2RESS, should be installed in the same library as the exec used to allocate the libraries for, and start, the first File Manager Db2 component session. Refer to the File Manager Customization Guide for further information. (long).

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.

Contact the person who installed FM/Db2.

FMNDB181

Browse substituted (short). The object being edited is a read-only view. In Db2® parlance a read-only view is any view that has at least one column marked as not updateable in the catalog. For this view every column is marked as not updateable. Consequently no edit operations of any kind are possible, and browse has been substituted for edit. (long).

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.

No action required. Informational message.

FMNDB182

Table locking failed (short). Table locking was requested but failed. The object being edited is a view, and views cannot be explicitly locked. (long).

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.

No action required. Informational message. Table locking should be avoided because of the potential for deadlocks.

FMNDB183

Read-only view (short). The object being edited is a read-only view. In Db2® parlance a read-only view is any view that has at least one column marked as not updateable in the catalog. For this view at least one column is marked as updateable. Those columns that are not updateable are protected. Some edit operations may fail. (long).

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.

This is an informational message. It is possible to successfully edit some read-only views, even though some columns of the view cannot be updated. However, attempting to edit a read-only view is not advisable. Edit the underlying tables directly.

FMNDB184

Non-updateable columns (short). The table being edited contains at least one column marked as not updateable in the Db2® catalog. This can occur when editing Db2® catalog tables. The not updateable columns are protected. Some edit operations may fail. (long).

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.

This is an informational message. You will not be able to change the data for those columns marked as not updateable. It may also not be possible to delete or insert rows.

FMNDB185

Recursive alias (short). The object name entered is an alias that refers to an alias at a remote location, which is not permitted. Specify the alias name at the remote server directly. (long).

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.

Enter the target Db2® object name directly, or ensure that any alias used refers directly to a Db2® object.

FMNDB186

Not available (View) (short). The RE command is not available when editing a Db2® view. Edit the Db2® table directly to access related table edit processing. (long).

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.

If related edit processing is required, ensure that all objects referred to are tables.

FMNDB187

Command not available (short). Commands such as INSERT, REPEAT and COPY are not available in this edit session. The data for the Db2® object is stored in UNICODE format, but there is no conversion routine for graphic data type columns. (long).

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.

No action required. Informational message.

FMNDB188

The Db2® object being edited is stored in a UNICODE-encoded table space, and the object contains MBCS (mixed byte character set) data (GRAPHIC data type columns). The current application encoding scheme is not a known MBCS CCSID. Changing the GRAPHIC data type columns is not supported. (long).

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.

No action required. Informational message.

FMNDB189

Incompatible options (short). Read-only access can only be selected with concurrency options that do not specify that locks will be kept, that is all options except 4 "Read stability keep locks" and 6 "Repeatable read keep locks". (long).

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.

In all but exceptional cases the Concurrency option should be set to "Uncommitted read" or "No with clause". If a concurrency option that requires locks is required, do not specify the "Read-only access" option.

FMNDB190

Statement overflow (short). The SQL statement needed to update the table is too long. (long).

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.

Collect information including the DDL used to create the Db2® object being processed. Contact IBM® Support.

FMNDB191

Changes discarded (short). The invalid change to the Initial Display option has been discarded. (long).

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.

No action required. Informational message. After making changes to the options, press ENTER to validate the changes before attempting to exit the panel.

FMNDB192

Changes discarded (short). The invalid change to the Concurrency option has been discarded. Enter one of the listed values for the Concurrency option. (long).

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.

No action required. Informational message. After making changes to the options, press ENTER to validate the changes before attempting to exit the panel.

FMNDB193

Changes discarded (short). The invalid change to the Enter key usage option has been discarded. Enter one of the listed values for the Enter key usage option. (long).

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.

No action required. Informational message. After making changes to the options, press ENTER to validate the changes before attempting to exit the panel.

FMNDB194

Use unique characters (short). The character used to indicate the "String delimiter (display)" must be different to the character used to indicate the "String delimiter (input)". Select a different character. (long).

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.

Ensure that the characters specified for the "Input" and "Display" indicators and delimiters are unique.

FMNDB195

Use unique characters (short). The character used to indicate the;"Null column display indicator" must be different to the character used to indicate the "Null column input indicator" Select a different character. (long).

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.

Ensure that the characters specified for the "Input" and "Display" indicators and delimiters are unique.

FMNDB196

Use unique characters (short). The character used to indicate the "Null column input indicator" must be different to the character used to indicate the "String delimiter (input)". Select a different character. (long).

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.

Ensure that the characters specified for the "Input" and "Display" indicators and delimiters are unique.

FMNDB197

Use unique characters (short). The character used to indicate the "Null column display indicator" must be different to the character used to indicate the "String delimiter (input)". Select a different character (long).

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.

Ensure that the characters specified for the "Input" and "Display" indicators and delimiters are unique.

FMNDB198

Use unique characters (short). The character used to indicate the "Null column input indicator" must be different to the character used to indicate the "String delimiter (display)". Select a different character (long).

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.

Ensure that the characters specified for the "Input" and "Display" indicators and delimiters are unique.

FMNDB199

Use unique characters (short). The character used to indicate the "Null column display indicator" must be different to the character used to indicate the "String delimiter (display)". Select a different character. (long).

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.

Ensure that the characters specified for the "Input" and "Display" indicators and delimiters are unique.

FMNDB206

Not on remote object (short). The requested function can not be performed on an object at a remote location. (long).

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.

Connect to the remote Db2® server directly and reissue the command.

FMNDB208

Not on catalog object (short). The requested function can not be performed on a Db2® catalog object. (long).

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.

No action required. Informational message.

FMNDB210

Invalid value (short). The valid values are 16, for an 8 byte number with 16 digit coefficient, or 34 for a 16 byte number with 34 digit coefficient. (long).

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.

Enter either 16 for an 8-byte number, or 34 for a 16-byte number.

FMNDB215

Unsupported data type (short). This File Manager Db2® function does not support columns of the specified data type. Supported data types are List of data types. (long).

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.

Check that the data type entered is spelled correctly. The list of supported data types is shown in the long version of the message. Press the PF key assigned to HELP, PF1 by default, to access. Check that the data type is supported by the version of Db2® in use. For example, the DECFLOAT data type is not supported at Db2® version 8.

FMNDB216

Length error (short). The specified length, precision, or scale is not valid for the data type of the column. (long).

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

Check the value entered. Consult the DB2 for z/OS SQL Referencemanual for detailed information on the permissible values for data type lengths, and the scale and precision values that may be specified.

FMNDB217

Scale > precision (short). The scale of a decimal must be less than or equal to the precision of the number. (long).

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

For Decimal numbers the precision can be 1 to 31, inclusive. The scale for a number can be 0 to p, where p is the precision of the number.

FMNDB220

Non updateable field (short). A field reference in a change command refers to a column that is not updateable. (long).

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.

Ensure that the field reference identifies a column that can be changed. Non updateable columns are shown as protected fields in the editor display.

FMNDB223

Start too large (short). The start position (start position) is larger than the number of rows (number of rows) in the result table.

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.

Informational message. Reduce the start position value to at least number of rows and retry the operation.

FMNDB224

Start out of range (short). The first sample row is at row row number, which is larger than the number of rows, number of rows, in the result table. Reduce the start position and/or initial skip count values.

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

Informational message. Reduce either or both of the "start positions" and "Initial skip count" (i) values, so that s+i+1 <=n.

FMNDB240

Invalid collection (short). The collection must be different from the COPY collection. (long).

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

Specify different values.

FMNDB242

DASD data set required (short). This command can only be used on a row where DSNAME refers to a DASD data set. (long).

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.

Issue the command against an image copy data set with a non blank device type. The device type must not be a tape type.

FMNDB245

No plan (short). The command is only valid when application plan is non-blank. (long).

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.

Ensure that the APPLNAME column value is non blank.

FMNDB246

No collection (short). The command is only valid when collection is non-blank. (long).

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.

Ensure that the COLLID column value is non blank.

FMNDB247

No DBRM (short). The command is only valid when DBRM is non-blank. (long).

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.

Ensure that the PROGNAME column value is non blank.

FMNDB250

Invalid SQL identifier (short). The value entered is not a valid SQL ordinary identifier. (long).

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.

An SQL ordinary identifier cannot include characters other than A-Z, 0-9, _ ,and the national characters, and must not begin with a digit. See the Db2® SQL Reference manual for a precise definition. Refer to the Appendix "Limits in Db2® for z/OS®", for a complete list of valid values for various types of Db2® items.

FMNDB270

Invalid buffer pool (short). Valid buffer pool names are: List. (long).

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

Compare the value entered against the values in List. Change the value entered to match one of the values in List. Retry the operation.

FMNDB271

Db2® version invalid (short). Table constraints are only available when connected to a Db2® Version 8 or later system. Current® Db2® version is Db2 VRM indicator. (long).

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.

No action required. Informational message.

FMNDB272

Not valid for object (short). "line command" is not a valid command for this type of object. (long).

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.

Ensure that the command entered is appropriate for the type of object shown in the row.

FMNDB273

Not valid for function (short). "Line command" is only valid for external user-defined functions. (long).

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.

The type of function is shown in the "Type of Routine" column. Enter the command against a row showing a function of the appropriate type.

FMNDB274

No upgrade done (short). The PLAN_TABLE was already at the correct level. (long).

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

No action required. Informational message.

FMNDB275

Not valid for column (short). "Line command" is not a valid command for this type of column. List of types. (long).

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.

No action required. Informational message. List of types contains information about the types of columns that the command can be issued against.

FMNDB276

Not valid for column (short). Line command is not a valid command for 'identity column' type sequence objects. (long).

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.

No action required. Informational message.

FMNDB289

Data set required (short) This command can only be used on a row where DSNAME refers to a data set. (long).

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.

No action required. Informational message. Ensure that the selected row represents either a full or incremental copy. The command may still fail if, for example, the data set has been deleted.

FMNDB292

Invalid criteria (short). The criteria specified in the Additional Selection Criteria fields produced an invalid SQL SELECT statement WHERE clause. Db2® returned an SQL code of -199 to the SQL statement "SQL STATEMENT". (long).

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.

Look up SQLCODE-199 in the DB2 Administration Tool for z/OS User's Guide and Reference, modify the predicate, and retry the operation.

FMNDB295

Invalid location (short). The location name is invalid or is not defined to the Db2® subsystem. (long).

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.

Look up SQLCODE-950 in the Db2® SQL Messages and Codes manual. The most likely explanation is that the value entered does not appear in column SYSIBM.LOCATIONS.LOCATIONS at the local Db2® server. If the value is incorrect then amend it and retry the operation. If the value is correct contact the person responsible for maintaining DRDA® definitions for your Db2® systems.

FMNDB296

No plan table (short). Plan table owner.PLAN_TABLE does not exist. (long).

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.

The PLAN_TABLE is a user-defined table. The explain utilities allow an "owner" value to be specified. Check that this value is not preventing access to the user's PLAN_TABLE. All PLAN_TABLE entries can be listed using the FM/Db2 Object List utility. If the PLAN_TABLE does not exist, use the 'C' command to create it.

FMNDB298

Incomplete quoted string (short). You entered an incomplete quoted string. Db2® returned an SQL code of -010 to the SQL statement SQL Statement. (long).

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

Examine the SQL statement to determine the source of the open quoted string. Modify the values entered to avoid the problem, retry the operation.

FMNDB299

Not COPY FULL (short). The RT command is only valid against an image copy entry. (long).

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.

Ensure that the row selected represents either a full or incremental image copy.

FMNDB300

No previous template has been used with this Db2® object. (long).

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.

You can generate and save a template for the current Db2® object using the "Generate/Replace" template usage option. Once a template has been successfully saved, use the "Previous" option to access the template, without needing to enter a template data set name or member.

FMNDB301

Invalid FM/Db2 template (short). The specified template does not represent a FM/Db2 template. Specify a valid FM/Db2 template. (long).

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.

You can generate and save a template for the current Db2® object using the "Generate/Replace" template usage option. Once a template has been successfully saved, you can access it and possibly modify it using the "Edit template" option on the appropriate FM/Db2 function entry panel.

FMNDB302

FM/Db2 template loaded (short). File Manager Db2 component template has been successfully loaded. (long).

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.

No action required. Information message.

FMNDB303

Template not loaded (short). Loading of FM/Db2 template canceled by user. Row selection criteria for the template must be revised before proceeding. (long).

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.

Resolve the reason for the difference between the data set template and the Db2® object, and retry the operation. Note that FM/Db2 always generates a template for any Db2® object and compares this with any user-specified template; with the former template considered to be correct. There are many reasons why the two templates may be inconsistent (for example, Different Db2® objects; Object dropped changed and recreated).

FMNDB304

Template mismatch (short). The selected template does not match the Db2® object. Press ENTER to replace selected template, or PF3/END to select another template or processing option. (long).

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.

There are two choices: 1. Press PF3 to cancel the current function. You may then attempt to resolve why the specified template data set does not match the Db2® object and retry the operation. 2. Press ENTER to replace the template in the data set with a correct version for the Db2® object. Any customization stored in the data set template will be lost. Note that FM/Db2 always generates a template for any Db2® object and compares this with any user-specified template; with the former template considered to be correct. There are many reasons why the two templates may be inconsistent (for example, Different Db2® objects; Object dropped changed and recreated).

FMNDB305

Template not updated (short). Loading of File Manager Db2 component template canceled by user as the specified template does not match the Db2® object. Specify another template or processing option. (long).

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.

No action required. Informational message.

FMNDB310

No statement table (short). Plan table Owner.DSN_STATEMNT_TABLE does not exist. (long).

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.

Create the table using the FM/Db2 Explain Utilities function. After populating the table using the EXPLAIN command, retry the operation.

FMNDB311

No function table (short). Plan table Owner.DSN_FUNCTION_TABLE does not exist. (long).

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.

Create the table using the FM/Db2 Explain Utilities function. After populating the table using the EXPLAIN command, retry the operation.

FMNDB330

Invalid row number (short). Either a row number has not been specified, or a specified value is invalid (long).

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.

Check the syntax for the command and re-issue it.

FMNDB331

Row Row not found (short). The specified row number Row does not exist in the Db2® object, or result table. (long).

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.

Check the row number value and ensure that it is between 1 and the maximum number of rows in the current editor session.

FMNDB332

Not on XML/LOB column (short). The cursor is not positioned on an XML/LOB column. (long).

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.

Check the cursor position and ensure that it is located on a column of the appropriate type for the command.

FMNDB333

J command invalid (short). The J command is only valid in a File Manager/Db2 editor session of a LOB. (long).

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.

None - informational message.

FMNDB334

SP command invalid (short). The SP command is only valid in a File Manager/Db2 editor session of a LOB. (long).

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.

None - informational message.

FMNDB335

Large table mode is not available when the object being processed contains LOB or XML columns. Specify a row count greater than zero to process this Db2® object. (long).

This message is issued on the FM/Db2 editor function entry panel when:
  1. The user enters the name of a Db2® object that contains a LOB or XML column.
  2. The row count value is set to 0 (also * or ALL).
This combination is not supported. Large editor mode is not available when the Db2® object contains LOB or XML columns.

Change the row count to specify a positive integer value.

FMNDB336

Non-updateable field (short). LOB (BLOB, CLOB, DBCLOB) and XML fields cannot be altered using the CHANGE command. Use LOBEDIT or XMLEDIT to display, and possibly change, the contents of LOB/XML columns.

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

Use the LOBEDIT or XMLEDIT commands to edit the LOB/XML data.

FMNDB337

LOB/XML Columns (short). The result table for the SELECT statement contains either LOB or XML columns. Display of the result table is not supported. Use Browse, View or Edit of the Db2® object containing the LOB/XML columns to display, and possibly change, LOB and XML data. (long)

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.

To display and possibly change LOB or XML data, use the FM/Db2 editor functions (Browse, View or Edit) and specify the Db2® object name that contains the LOB or XML columns.

FMNDB338

XML Columns (short). Edit of objects with XML columns is only supported when the target Db2® system is at Db2® V10 NFM. The function cannot be performed.(long)

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.

To display and possibly change XML data, the target Db2® system must be at Db2® V10 new function mode, or later.

FMNDB339

Length error Len (short). The maximum length of the LOB Len has been exceeded. Either reduce the amount of data or cancel out of the LOB editor session. (long).

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.

Either reduce the size of the LOB data, or issue the CANCEL command to abandon any changes made. You can use the TE command in the originating editor session to see the maximum length for the LOB. You can use the LOBLEN command in the originating editor session to show the current length for a LOB column.

FMNDB340

Not a LOB column (short). The field reference does not identify a LOB column. (long).

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.

Check the field reference entered as part of the command and ensure that it identifies a LOB column. Re-issue the command.

FMNDB341

Not a LOB column (short). The column at the cursor position is not a LOB column. (long).

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.

Ensure that the cursor is located within the bounds for a LOB column. Re-issue the command.

FMNDB342

LOB Length = Length (short). The length of the LOB data (Row number = Row number, REF# = Field Ref) is Length. (long).

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.

None - informational message.

FMNDB343

No LOB columns (short). The Db2® object does not contain any LOB columns. (long).

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.

None - informational message.

FMNDB344

LOBVIEW not available (short). LOBVIEW is not available. You may only view a LOB column from a view or edit session (not browse) of the parent table. (long).

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.

Use the LOBBRWS command instead. If LOBVIEW is required exit the editor session and re-invoke the editor using either the view or edit function.

FMNDB345

LOBEDIT not available (short). LOBEDIT is not available. You may only edit a LOB column from an edit session (not browse or view) of the parent table. (long).

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.

Use one of the available commands as documented in the explanation. If LOBEDIT is required exit the editor session and re-invoke the editor using either the edit function.

FMNDB346

Empty LOB (short). The LOB has no data. (long).

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.

None - informational message.

FMNDB347

Command not supported (short). XML fields cannot be browsed, viewed, or edited under CICS. (long)

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

None.

FMNDB348

No matching columns (short). The Db2® object contains LOB columns, however there are no selected LOB columns. You can use the TEdit command to change the selection status for a column. (long).

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.

Issue the Tedit command to display the Column Selection/Edit panel (Template editor). Change the Selection status of the LOB column of interest and save the resulting changes. Re-issue the command.

FMNDB349

BLOB edit not supported (short). Edit of a binary large object column is not supported. (long).

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

None - informational message.

FMNDB350

Not an XML column (short). The field reference does not identify an XML column. (long).

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.

Check the field reference entered as part of the command and ensure that it identifies an XML column. Re-issue the command.

FMNDB351

Not an XML column (short). The column at the cursor position is not an XML column. (long).

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.

Ensure that the cursor is located within the bounds for an XML column. Re-issue the command.

FMNDB352

XML Length = Length (short). The length of the XML data (Row number = Row number, REF# = Field Ref) is Length. (long).

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.

None - informational message.

FMNDB353

No XML columns (short). The Db2® object does not contain any XML columns. (long).

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.

None - informational message.

FMNDB354

XMLVIEW not available (short). XMLVIEW is not available. You may only view an XML column from a view or edit session (not browse) of the parent table. (long).

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.

Use the XMLBRWS command instead. If XMLVIEW is required exit the editor session and re-invoke the editor using either the view or edit function.

FMNDB355

XMLEDIT not available (short). XMLEDIT is not available. You may only edit an XML column from an edit session (not browse or view) of the parent table. (long).

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.

Use one of the available commands as documented in the explanation. If XMLEDIT is required exit the editor session and re-invoke the editor using either the edit function.

FMNDB356

Invalid target column (Short). FMAP cannot be used with BLOB, CLOB, DBCLOB, or XML columns. (Long).

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

None.

FMNDB358

No matching columns (short). The Db2® object contains XML columns, however there are no selected XML columns. You can use the TEdit command to change the selection status for a column. (long).

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.

Issue the Tedit command to display the Column Selection/Edit panel (Template editor). Change the Selection status of the XML column of interest and save the resulting changes. Re-issue the command.

FMNDB359

Error line Line (short). The Db2® XML parser reported an error on or near line Line. (long).

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.

Locate the specified line number, correct the syntax error and attempt to exit the XML edit session again. If it is not possible to resolve the error issue the CANCEL command to abandon any changes made.

FMNDB360

Invalid target column (short). FMAP cannot be used when the column cannot be updated, for example, columns defined with the GENERATED attribute

The FMAP editor primary command was issued against a column with the GENERATED attribute. This is not supported.
None.

FMNDB362

Null XML column (short). The XML column has the NULL value (long).

The XMLEDIT command was issued against an XML column. The XML column has the Db2® null value.
None.

FMNDB363

Unable to process (short). The object being edited does not include all columns of any unique indexes defined on the base table. FM/Db2 is unable to uniquely identify rows in the result table using SQL - this is required for XMLedit functionality (long).

An XML edit operation was issued against an XML column. The object being processed is a Db2® view. The columns in the view do not include all columns of any unique indexes defined on the view's base table. In this situation FM/Db2 cannot uniquely identify rows in the result table, which is required for the XML editor's functionality. The command cannot be processed.
Retry the operation using the base table to which the view refers.

FMNDB364

Unable to process (short). An attempt to obtain the RID value for the row failed. The RID value is required for XMLedit functionality (long).

An XML edit operation was issued against an XML column. The object being processed is a Db2® view. FM/Db2 attempted to extract the RID value for the row containing the XML document to be processed. This operation failed. The command cannot be processed.
Retry the operation using the base table to which the view refers.

FMNDB367

LOB column(s) (short). Import/Copy of tables containing LOB (BLOB, CLOB or DBCLOB) columns is not supported (long).

An attempt was made to import or copy data containing LOB (BLOB, CLOB or DBCLOB) columns. This is not supported.
None.

FMNDB368

XML column(s) (short). Import/Copy of tables containing XML columns is not supported (long).

An attempt was made to import or copy data to a table containing XML columns. This is not supported.
None.

FMNDB370

Warning: Saving changes to the SQL statement invalidates any expression previously entered using the "Row Selection Criteria" panel. (Long).

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.

Informational message. In general, the SQL panel is intended for expressions that cannot be entered using the "Row Selection Criteria" panel, or for users who are comfortable entering native SQL.

FMNDB371

Not allowed. (Short). You cannot de-select columns when creating data using the FM/Db2 data create function. When a row is inserted, every column of the object is affected. (Long).

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.

Ensure that every column of the template is selected.

FMNDB372

De-selected columns (Short). You may not de-select columns when creating data using the FM/Db2 data create function. When a row is inserted, every column of the object is affected. (Long).

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.

Ensure that every column of the template is selected.

FMNDB373

Command not available (Short). Commands such as INSERT, REPEAT, COPY, and GET are not available when the editor is operating in large mode. (Long).

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.

When editing in Large Table mode, you cannot insert new rows.

FMNDB400

Incomplete clause (short). The syntax clause just exited is not yet complete. (long).

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.

No action required. Informational message.

FMNDB401

Command command ignored (short). You entered the Command command but the cursor was not on a syntax element. (long).

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.

No action required. Informational message.

FMNDB402

Command command ignored (short). You entered the Command command with the cursor on a syntax element but the element is not in a repeat group. (long).

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.

No action required. Informational message.

FMNDB403

No data entered (short). No data was entered for the data entry syntax element. (long).

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.

No action required. Informational message. If this element is a required part of the SQL syntax you will need to enter a valid value to be able to complete the SQL SELECT statement.

FMNDB404

Statement empty (short). You entered a scroll command but there is no generated statement data. (long).

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.

No action required. Informational message.

FMNDB405

End of data (short). The last line of the generated statement is already displayed. (long).

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.

No action required. Informational message.

FMNDB406

Top of data (short). The first line of the generated statement is already displayed. (long).

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.

No action required. Informational message.

FMNDB407

Autoscrolled (short). The generated statement has changed, and the statement generation area has been scrolled to bring the end of the data into view. (long).

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.

No action required. Informational message.

FMNDB408

Statement too long (short). The length of the generated statement exceeds the maximum length allowed for the target system: execution failure expected. (long).

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.

Cancel the current operation and restart.

FMNDB409

Repeat separator invalid (short). A repeat separator cannot be entered because no elements of the repeat item have been selected. (long).

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.

Select at least one repeatable item before attempting to insert a repeat separator.

FMNDB410

Nothing to execute (short). The EXECUTE command cannot be executed because no statement has been generated for execution. (long).

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.

Use the prototyping facilities to generate a SELECT statement prior to attempting execution.

FMNDB411

Repeat separator invalid (short). There is no repeat separator associated with the last repeated element. (long).

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.

No action required. Informational message. If in doubt consult the syntax diagram for SELECT in the Db2® SQL Reference manual.

FMNDB412

Nothing to execute (short). The EXECUTE command cannot be executed because no statement has been entered for execution. (long).

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.

No action required. Informational message.

FMNDB413

Invalid statement type (short). An invalid statement or a statement that is not dynamically executable was found in the statement entry area. (long).

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.

Consult the Db2® SQL Reference manual for information about those statements that can/cannot be dynamically prepared/executed.

FMNDB414

Statement type statement executed (SQL cost Cost)

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.

No action required. Informational message.

FMNDB415

count statements executed (SQL cost Cost).

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.

No action required. Informational message.

FMNDB419

Execution error (short). SQL execution failed. The cursor is placed on the start of the failing statement, or for a syntax error, on the token in error.

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.

For syntax errors, the cursor location is at the failing token as determined by the Db2® syntax parser. The actual error may be earlier in the statement. Example: SELECT FROM DSN8810.EMP gives SQLCODE-104 and the cursor is located on the period in "DSN8810.EMP". The actual error is the omission of '*' after the SELECT keyword. Consult the Db2® SQL Reference manual for the statement type for the syntax diagram for that statement.

FMNDB420

Data truncated (short). Data found beyond column 72 in the SQL edit session has been discarded. (long).

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

Examine the SQL statement to determine where the truncation occurred and make corrections.

FMNDB421

SQL too long (short). The SQL data returned from the SQL edit session was too large for the execution buffer. Some lines have been discarded. (long).

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.

You may be able to circumvent this problem by using less lines to code the SQL statement in the ISPF editor session. For example, by removing some of the white space in the statement.

FMNDB422

Nothing to edit (short). There is no SQL statement for the SQL command to edit. (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.

Enter some part of the SQL SELECT statement before entering the SQL command.

FMNDB423

Select an option (short). Either edit or execute must be selected. (long).

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.

You must select one, or both of the "Edit data set" and "Execute SQL from data set" options to use this function.

FMNDB424

Statement type statement Action.

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

No action required. Informational message.

FMNDB425

count statements Action

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

No action required. Informational message.

FMNDB426

SQL execution failed (count statement(s) executed successfully).

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.

Examine the list of SQL statements processed to determine whether the failure to execute a statement (or statements) is appropriate.

FMNDB427

No columns selected (short). The EXECUTE command cannot be executed because no columns have been selected from which to retrieve data. (long).

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.

You need to specify at least one column in the SELECT statement, for the statement to be executable. Select a column by typing 'S' next to the entry for the column, or use 'ALL' to select all columns.

FMNDB429

Value required (short). A value must be entered to build a where clause predicate. (long).

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.

Enter a value appropriate for the column being included in the WHERE clause.

FMNDB431

Invalid operator (short). Enter a valid logical operator: AND, OR, NOT, NOR. NOT represents AND NOT and NOR represents OR NOT. (long).

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.

Enter one of the values shown in the long version of the message; the default value is 'AND', selected automatically when no value is specified.

FMNDB432

Invalid operator (short). Enter a valid expression operator: =, ≠,<,>,≤, >,IN, NI, LI, NL. LI represents the SQL LIKE operator, NL represents NOT LIKE, and NI represents NOT IN. (long).

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.

Enter one of the values shown in the long version of the message; the default value is '=', selected automatically when no value is specified.

FMNDB433

Invalid margins (short). The left margin must be less than or equal to the right margin, and both values must be greater than zero. (long).

This message is issued by the FM/Db2 Edit/Execute SQL (Data Set) function. The user entered values in the "First column" and "Last column" fields that are invalid. Suggested values are:
  • (First column) and 72 (Last column), corresponding to the margins when editing a fixed-block data set with logical record length of 80 and an ISPF profile setting of 'NUMBER ON STD'.
  • (First column) and 80 (Last column), corresponding to the margins when editing a fixed-block data set with logical record length of 80 and an ISPF profile setting of 'NUMBER OFF'.
Consider the recommended values outlined in the explanation. Any values entered should meet the following requirement: 0 < first <=last <=logical record length, where:
  • First is the value entered in the "First column" field.
  • Last is the value entered in the "Last column" field.
  • Logical record length is the LRECL for the data set being edited. You can use ISPF option 3.2 to determine the LRECL for a data set. To enhance the usability of the data set, the value for last should be significantly larger than the value for first.

FMNDB434

Nothing to explain (short). The EXPLAIN command cannot be executed because no statement has been entered for explanation. (long).

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.

Enter an SQL statement in the "SQL Statement" area of the panel and reissue the EXPLAIN command.

FMNDB435

Invalid statement type (short). An invalid statement or a statement that is not explainable was found in the statement entry area. (long).

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

Not every SQL statement is "explainable". See the Db2® SQL Reference manual description of the EXPLAIN statement, for a detailed explanation of which SQL statements are explainable. SELECT, MERGE, INSERT, and some types of UPDATE and DELETE statements are considered" explainable".

FMNDB436

Statement executed, no rows deleted.

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.

No action required. Informational message.

FMNDB437

Statement executed, no rows updated.

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.

No action required. Informational message.

FMNDB438

SQL execution halted (short). Execution of the SQL statement was halted because the user pressed CANCEL on the predictive governor. (long).

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.

No action required. Informational message.

FMNDB439

CONNECT stmt. Invalid (short). A CONNECT statement cannot be executed. This statement can only be specified within an application program. (long).

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.

Remove the CONNECT statement and retry the operation.

FMNDB440

VIEW (clustered sampling)

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

No action required. Informational message.

FMNDB441

TABLE (clustered sampling)

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

No action required. Informational message.

FMNDB442

VIEW (random sampling)

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

No action required. Informational message.

FMNDB443

TABLE (random sampling)

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

No action required. Informational message.

FMNDB444

LOB

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

No action required. Informational message.

FMNDB445

XML

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

No action required. Informational message.

FMNDB450

Copy not allowed (short). The index has not been defined with COPY YES, so it cannot be selected for copying. (long).

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.

You can only copy a Db2® index when it was originally created with the 'COPY YES' option. See the Db2® Utilities Guide and Reference for more information.

FMNDB451

Chng limits not allowed (short). Change limits cannot be specified because the table space has not been defined with TRACKMOD YES. (long).

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.

You can only specify change limit values for the Db2® COPY utility when the table space was defined with 'TRACKMOD YES'. See the Db2® Utilities Guide and Reference for more information.

FMNDB453

Cannot recover object (short). Either the Db2® object specified does not exist in the Db2® catalog, or no SYSCOPY entries exist for the Db2® object. (long).

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.

No action required. Informational message.

FMNDB454

Invalid change limit (short). The change limit must be an integer value between 0 and 100. (long).

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.

Specify a value in the range 0-100 inclusive. See the Db2® Utilities Guide and Reference for more information.

FMNDB455

Function canceled (short). Load utility processing was canceled by user. (long).

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.

No action required. Informational message.

FMNDB456

Function completed (short). Load utility processing has completed. (long).

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

No action required. Informational message.

FMNDB457

Choose at least one item (short). For the given processing option, you must choose at least one item. (long).

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.

Select one or more of options: 'PREVIEW', 'LISTDEFDD', 'TEMPLATEDD', and 'EVENT'.

FMNDB458

Null indicator mismatch (short). The source Db2® column Column name is not nullable and yet the corresponding target data set field is associated with a nullable field. (long).

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 usually indicates a mapping problem. The target field for a column defined as "NOT NULL" should not have a null field indicator. Check the target template copybook or template definition and make changes. Retry the operation.

FMNDB459

Enter required field (short). The field where the cursor is positioned is mandatory. (long).

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.

Specify a key value in the field indicated by the cursor position.

FMNDB460

Function canceled (short). Unload table utility processing was canceled by user. (long).

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.

No action required. Informational message.

FMNDB461

Function completed (short). Unload utility processing has completed. (long).

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

No action required. Informational message.

FMNDB462

Settings failure (short). The TEMPLATE, LISTDEF, or OPTIONS settings for the current subsystem may be incorrect. (long).

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.

Logoff completely, logon again, and retry the operation. If the problem persists, try deleting all FMN2* members from the user ISPF profile data set. If this fails to resolve the problem contact IBM® Support.

FMNDB463

Setting failure (short). When you return from another subsystem, the changes that you made to LISTDEF, TEMPLATE, or OPTIONS settings may not be restored. (long).

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.

Logoff completely, logon again, and retry the operation. If the problem persists, try deleting all FMN2* members from the user ISPF profile data set. If this fails to resolve the problem contact IBM® Support.

FMNDB464

Null indicator mismatch (short). A null indicator byte maps to field name field name (column number), but the name does not contain 'NULL'. (long).

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.

Refer to the online tutorial topic "Null indicator byte processing", accessed as follows: 3.9.7.1.7 (Utilities > Utilities > Unload Utility > Unload (table) > Null indicator byte processing. Briefly, when using a File Manager (base) template to describe the format for the UNLOAD data set, it is possible to use a field with length > 1 byte for a Db2® null indicator. However, the field name must include the string 'NULL' to be automatically mapped.

FMNDB465

Null indicator mismatch (short). A null indicator byte maps to the byte before the first field. (long).

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

Check the template for the target (unload) data set is appropriate for the Db2® object being unloaded. Consider using a File Manager/Db2 template generated from the source object to map the unloaded data. If both of these techniques fail to resolve the problem, contact IBM® Support.

FMNDB467

Null indicator mismatch (short). The null indicator byte column name maps to field field name (column number) which is mapped already to another table column. (long).

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.

Refer to the online tutorial topic "Null indicator byte processing accessed as follows: 3.9.7.1.7 (Utilities > Utilities > Unload Utility > Unload (table) > Null indicator byte processing. Briefly, a field in the template for the unload data set can only be mapped to a single column, or Db2® null indicator.

FMNDB468

Utility service failed (short). FM/Db2 initiated an unload table utility operation from export. However, the unload table utility failed to initialize properly. (long).

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.

Contact the person responsible for installing and maintaining FM/Db2. Possible causes of this error include setup-related issues such as the SFMNSLIB library not being available to the FM/Db2 user.

FMNDB469

Settings failed (short). The TEMPLATE, LISTDEF, or OPTIONS settings (for subsystem Db2 SSID.) cannot be loaded or the associated settings could not be found. (long).

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.

Contact the person who is responsible for installing/maintaining FM/Db2. Defining FMN2SSDM macro entries for every Db2® system accessed by FM/Db2 is a required installation and customization step. Contact IBM® Support if analysis shows no obvious problem in the FMN2POPT module.

FMNDB470

Init install settings (short). The installation-defined settings for this subsystem are used to set options TEMPLATE, LISTDEF, and OPTIONS. (long).

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.

No action required. Informational message.

FMNDB471

Init FM/Db2 settings (short). The installation defined setting for this subsystem is: CONNECT = ANY. The FM/Db2 defaults are used for options TEMPLATE, LISTDEF, and OPTIONS. (long).

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.

No action required. Informational message. The File Manager Customization Guide lists as a required step that an FMN2SSDM macro entry should be defined for every Db2® system that FM/Db2 may connect to.

FMNDB472

Init FM Db2 settings (short). FM Db2 default settings for options TEMPLATE, LISTDEF, and OPTIONS are used. Your installation defined settings uses an old version of the FMN2SDDM macro. (long).

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.

Contact the person responsible for installing or maintaining FM/Db2. Reassemble the FMN2POPT module using the directions in the File Manager Customization Guide. Carefully check the SYSLIB DD statement to ensure that the current version of SFMNSAM1 libraries is in use, and check the SYSLMOD DD statement to ensure that the output module is located in the appropriate library.

FMNDB473

Must provide name (short). A LISTDEF name must be provided when specification LISTDEF is selected. (long).

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.

Enter a valid LISTDEF name, and retry the operation; or change the specification to"Object name".

FMNDB474

//* NULLABLE COLUMN MAPPING

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

No action required. This message may be issued when documenting the mapping of nullable Db2® columns in the Db2® object to corresponding fields in the template for the unloaded data.

FMNDB477

//* F (FOOTNOTE) -

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

No action required. This message may be issued when documenting the mapping of nullable Db2® columns in the Db2® object to corresponding fields in the template for the unloaded data.

FMNDB478

//* * = FIELD CORRESPONDING TO NULL INDICATOR BYTE IS LARGER

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

No action required. This message may be issued when documenting the mapping of nullable Db2® columns in the Db2® object to corresponding fields in the template for the unloaded data.

FMNDB479

//* THAN ONE BYTE. INDICATOR MAPS TO LAST BYTE.

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

No action required. This message may be issued when documenting the mapping of nullable Db2® columns in the Db2® object to corresponding fields in the template for the unloaded data.

FMNDB480

WHERE clause too long (short). The WHERE clause is longer than 32767 bytes, and cannot be processed. Specify a shorter WHERE clause. (long).

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.

Specify a shorter WHERE clause. Remove any redundant "white space" in the clause and retry the operation.

FMNDB481

Invalid reference (short). The correlation reference Reference is invalid. Valid values are #1 - Maximum reference inclusive. (long).

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.

Correct the table correlation reference, and retry the operation.

FMNDB482

Invalid column name (short). Column name is not a column of the referenced table. (long).

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.

Check the value entered for spelling or other errors. Check that the column name is a column of the table indicated by the table correlation reference.

FMNDB483

Ambiguous reference (short). This column name appears in more than one of the selected tables. Use a correlation reference, eg #1.COLNAME to identify the required. (long).

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.

Precede the column name with a table correlation reference, example #n., where "n" is a positive integer.

FMNDB484

Ambiguous input (short). The value specified is a column name, but can also be interpreted as a constant. To specify a constant enclose the value in quotation marks. To specify a column use a correlation reference, eg #1.COLNAME. (long).

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.

Depending on context, either enclose the value in quotation marks (to indicate the first interpretation shown above) or precede to the column name with a table correlation reference (example #n.) to indicate the second interpretation above.

FMNDB487

NOPAD specified (Short). The DB2 UNLOAD NOPAD option is specified. FM/Db2 cannot generate a template that describes the data that will be unloaded. (Long).

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.

Informational message. If a template is required for the INLOAD data, do not select the DB2 NOPAD option.

FMNDB489

Member not found (Short). The DBRM member cannot be found in the data set recorded in the Db2 catalog. This can happen when members are deleted from a DBRM library after the bind was executed.

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.

Informational message. This situation can occur if the member containing the DBRM is deleted after the BIND command was issued.

FMNDB490

Parameters have been reset to defaults.

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.

No action required. Informational message.

FMNDB491

RESET command failed.

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.

Exit FM/Db2 completely. Start FM/Db2 again, and retry the operation. If the problem recurs, check for ISPF-related problems such as a full user ISPF profile data set. If there are no obvious external problems, contact IBM® Support.

FMNDB500

Copying...

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

No action required. Informational message.

FMNDB501

number of rows rows

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.

No action required. Informational message.

FMNDB502

number of rows(s) copied (short). Number of rows row(s) copied from Db2® object source Db2 objectto target Db2 object

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.

No action required. Informational message.

FMNDB503

number of rows row(s) copied. insert string

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.

No action required. Informational message.

FMNDB504

count duplicate row(s) ignored.

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.

No action required. Informational message.

FMNDB505

count RI/Constraint errors.

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.

No action required. Informational message.

FMNDB507

count duplicate row(s) updated.

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.

No action required. Informational message.

FMNDB510

Function canceled (short). Copy function was canceled by user. (long).

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

No action required.

FMNDB511

Rollback completed (short) Copy of source Db2 object to target Db2 object was rolled back due to errors.

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.

Determine why the copy operation was terminated, resolve the error condition, and retry the operation.

FMNDB512

Copy canceled (short) Output object target Db2 object cannot be same as input object source Db2 object.

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.

Specify different source or target Db2® objects, and retry the operation.

FMNDB519

Audit failure (short) Auditing to SMF failed - function terminated. BPX1SMF RC=return code (Dec) REASON CODE=reason code (Dec)

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.

This error usually indicates a set-up problem. Possible reason for an auditing failure to SMF are:
  1. The userid does have READ access to the SAF FACILITY class profile BPX.SMF.
  2. The FMN2POPT module does not have a valid number specified for the SMFNO parameter.
Consult the systems programmer for assistance in resolving the cause of the error.

FMNDB520

SQL statement too long (short) The SQL statement is > 32K-2 in length. The maximum length for an SQL statement for Db2® versions 6 or 7 is 32765 characters. The statement cannot be executed. (long)

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.

Simplify the SQL statement, and retry the operation.

FMNDB521

SQL statement too long (short) The SQL statement is > 2M in length. The maximum length for an SQL statement for Db2® versions 8 or later is 2097152 characters. The 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.

Simplify the SQL statement, and retry the operation.

FMNDB600

Global Settings

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.

No action required. Informational message.

FMNDB601

Changes discarded (short) Invalid changes to the default high level qualifier have been discarded. (long)

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.

Examine the value for "default high level qualifier" and re-enter the desired value. Press Enter to validate the value, prior to leaving the panel.

FMNDB602

Changes discarded (short) Invalid changes to the display width values have been discarded. (long).

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.

Use the field level help for each field (place the cursor on the field, press the HELP key, PF1 by default) to determine the valid values for each field. After entering a new value, press ENTER to validate the values, prior to leaving the panel.

FMNDB757

SQLCODE=SQLCODE, row count row(s) affected.

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

No action required.

FMNDB765

Privilege statements: count

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.

No action required.

FMNDB800

count rows exported (short) countrow(s) exported from Db2® object source Db2 object to file file name. (long).

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.

No action required.

FMNDB801

Export canceled (short) Export function was canceled by the user, or error encountered while processing the copybook. (long).

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.

If the user pressed the END or CANCEL PFkeys on the export "To" panel, none. If the user pressed ENTER on the export "To" panel, examine any copybook or template specified for the export data set for errors.

FMNDB802

Exporting...

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

No action required. Informational message.

FMNDB803

count rows imported (short) count rows imported, from file input file name to Db2® object target Db2 object. duplicate count duplicate rows not imported. error count rows in error not imported. selection count rows dropped via record selection. REXX drop count rows dropped by REXX proc. (long).

This message is issued at the end the FM/Db2 import utility, and shows summary statistics for the import operation.
  • count is the number of rows imported.
  • duplicate count is the number of duplicate row errors that were encountered. The record that caused the duplicate row error has not been imported.
  • error count is the number of records that generated errors other than a duplicate row error. The record that caused the error has not been imported.
  • selection count is the number of records (rows) that were dropped as a result of record selection.
  • REXX drop count is the number of records (rows) that were dropped because of user-specified processing in the REXX procedure. The same information is presented on the "Import Report" panel. This message is issued when the Update option for duplicate key errors is not selected on the import options panel.

No action required.

FMNDB804

Import canceled (short) Import function was canceled by the user. (long).

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

No action required. Informational message.

FMNDB805

Importing...

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

No action required. Informational message.

FMNDB806

Rollback completed (short) Import of import file name to target Db2 object was rolled back due to errors. count rows rolled back. duplicate count duplicate rows not imported. updated count duplicate rows updated. not updated count duplicate rows not updated. error count rows in error not imported. drop count rows dropped by record selection. REXX drop count rows dropped by REXX procedure. Note, that PF12/CANCEL on SQL error panel will skip each row in error.

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

No action required.

FMNDB807

row count rows created (short) row countrows created, in Db2® object output Db2 object name. duplicate count duplicate rows not created. error count in error not created.

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.

No action required. Informational message. If there are multiple duplicate key errors, you can edit the template for those columns that form part of the unique index keys to specify a pattern to be used when creating values for that column.

FMNDB808

Create canceled (short) Create function was canceled by the user.

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

No action required. Informational message.

FMNDB809

Creating...

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

No action required. Informational message.

FMNDB810

No rows created (short) Create of row count rows was rolled back due to error. Note that PF12/CANCEL on SQL error panel will skip each row in error.

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.

If the function was executed online, the failing operation will have produced an SQL error, displayed to the user in the SQL error pop-up panel. Look up the SQLCODE shown and respond as indicated.

FMNDB811

row count duplicate rows not imported.

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

This is one of several messages that may be issued by the FM/Db2 import utility when run in batch mode. If duplicate key errors were not expected, examine the input data to determine why the errors occurred.

FMNDB812

row count row(s) in error not imported.

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

This is one of several messages that may be issued by the FM/Db2 import utility when run in batch mode. The presence of this message usually indicates a problem with the input data, which should be examined to determine why the errors occurred.

FMNDB813

row count row(s) dropped via record selection.

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.

This is one of several messages that may be issued by the FM/Db2 import utility when run in batch mode. When record selection criteria, or a REXX exec, is specified for the input template, this message indicates that one or more records did not meet the record selection criteria, or were dropped as part of the REXX procedure processing. If no REXX procedure was specified this message may indicate a mismatch between the input data and its associated template.

FMNDB814

row count row(s) dropped via REXX proc.

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.

This is one of several messages that may be issued by the FM/Db2 import utility when run in batch mode. The user response depends on context. It may be reasonable for records to be dropped. If, however, records should not be dropped as part of the REXX procedure processing, examine the input data to determine why the records were dropped.

FMNDB815

row count duplicate row(s) not created.

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.

This is one of several messages that may be issued by the FM/Db2 data create utility when run in batch mode. The user response depends on context. Db2® will always reject rows that violate uniqueness constraints. When many duplicate row errors are received consider adjusting the input parameters to avoid duplicate values for any index columns.

FMNDB816

row count row(s) in error not created.

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.

This is one of several messages that may be issued by the FM/Db2 data create utility when run in batch mode. This message usually indicates an error. Db2® may reject the insert of a row for many reasons. Note, that the SQL error issued by Db2® is NOT SQLCODE-803. Duplicate row errors are reported separately. Examples of error SQLCODEs that might result in this message include: -530, -531, and -532 (referential integrity errors).

FMNDB817

row count existing rows(s) updated.

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.

This is one of several messages that may be issued by the FM/Db2 import utility, when run in batch mode. The user response depends on context. In most cases, the update of existing rows is best. If, however, the import operation is not expected to cause duplicate key errors (SQLCODE-803), compare the input records and Db2® object, to discover why there are duplicates.

FMNDB818

row count existing rows(s) not 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 is one of several messages that may be issued by the FM/Db2 import utility, when run in batch mode. This message usually indicates an error. Db2® may reject the update of a row for many reasons. Examples of error SQLCODEs that might result in this message include -530, -531, and -532 (referential integrity errors).

FMNDB819

row count import/updt(d) (short) row count rows imported, from file input data set name to Db2® object target Db2 object name. duplicate row count duplicate rows updated. duplicate error count duplicate rows not updated. error row count rows in error not imported. dropped record count rows dropped by record selection. Rexx drop count rows) dropped by REXX procedure.

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 when no rows were inserted, and no rows were updated. The user response depends on context. If insert or updates were expected, examine the input data to determine why no records were processed.

FMNDB820

Import complete. Row count row(s) imported.

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

Informational message.

FMNDB821

Rollback complete. Row count row(s) rolled back.

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.

Informational message.

FMNDB822

Row count rows imported (Short). Row count rows imported, from file input data set name to Db2 object output object name. duplicate row count duplicate rows updated. Duplicate error count duplicate rows not updated. error row count rows in error not imported. dropped record count rows dropped by record selection. Rexx drop count rows dropped by REXX procedure (Long).

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

Informational message.

FMNDB823

update row count rows updated (Short). update row count duplicate rows imported from file input data set name and updated in object output object name. duplicate error count duplicate rows not updated. row count rows imported. error row count rows in error not imported. dropped record count rows dropped by record selection. Rexx drop count rows dropped by REXX procedure (Long).

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

Informational message.

FMNDB824

Rows imported/updated (Short).row count rows imported from file input data set name to Db2 object output object name. duplicate row count duplicate rows updated. duplicate error count duplicate rows not updated. error row count rows in error not imported. dropped record count rows dropped by record selection. Rexx drop count rows dropped by REXX procedure (Long).

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.

Informational message.

FMNDB825

duplicate row count duplicate row errors.

Row count of duplicate rows in error.

Informational message.

FMNDB826

All columns selected (short) No columns were selected in the template for Db2 object name. Processing cannot proceed without at least one selected column. FM/Db2 has automatically selected all columns for processing.

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.

No action required. Informational message. By default, all columns of a Db2® object are selected for processing. While it is valid to deselect some of the columns in the Db2® object, it is invalid to deselect all columns, since this results in a "no-operation" condition.

FMNDB827

Import to view failed (short) The import operation has been canceled. Import to a view is only supported if the view is defined directly on a table. Repeat the operation using the actual table that the view refers to.

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.

In general, import to a Db2® view defined as "SELECT * FROM Db2 table name" is supported. Import to views that refer to multiple Db2® tables, or views, is not supported. Where possible, use the FM/Db2 import utility with a table name, rather than a dependent view.

FMNDB828

Remapping required (short) No columns in the target table are mapped to any fields in the input template. This can occur if the column names in the target object are different to the field names in the input template. Edit the template for the target object to set the mapping between columns/fields in the target/input templates.

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.

This message may be issued in the situation where the wrong input file template is specified for a File Manager/Db2 import function. Advanced usage of the FM/Db2 import utility allows individual mapping of each column in the target Db2® object to a corresponding field of the input template. The column and field names need not match, nor the relative positions of the columns in the Db2® object and fields in the input record. If this is the intended usage, use the template editor ("edit template mapping") to set the relationship between columns and fields, and retry the operation.

FMNDB829

Invalid value (short) The valid values are ALL or a number in the range 0-2147483647. (long).

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.

Correct the invalid value.

FMNDB831

Browse substituted (short) The Db2® result table is not updateable, specifically because not all columns of the first table named in the from clause are present, nor are all columns of any unique index(es) defined on this table. Browse has been substituted for edit. (long).

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.

No action required. Informational message. If edit operations of the result table are required, the preferred method is to edit the Db2® object directly.

FMNDB832

Update not possible (short) FM/Db2 cannot update the data in the row(s) marked with =INERR. This error may occur attempting to edit the result table from an arbitrary select statement entered using option 4.2, 4.3 or 4.4. You should cancel the current edit session and then edit the underlying Db2® object directly.

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.

If edit operations of the result table are required, the preferred method is to edit the Db2® object directly.

FMNDB833

Delete not possible (short) FM/Db2 cannot delete the data in the row(s) marked with =INERR. This error may occur attempting to edit the result table from an arbitrary select statement entered using option 4.2, 4.3 or 4.4. You should cancel the current edit session and then edit the underlying Db2® object directly.

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.

If edit operations of the result table are required, the preferred method is to edit the Db2® object directly.

FMNDB835

Parameter marker invalid (short) The SELECT statement contains one or more "?". Db2® interprets these as parameter markers, resulting in an SQL error. Replace the "?" with constants and rerun the statement.

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.

Locate the Db2® parameter markers in the SELECT statement. Replace each occurrence with a constant of the appropriate type. Rerun the statement.

FMNDB836

Browse substituted (short) This version of FM/Db2 does not support new Db2® data types introduced with Db2® version 9. Browse has been substituted for edit. (long).

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.

Determine which column has the unsupported data type. Contact IBM® Support for information about later versions of FM/Db2 which support the new data type.

FMNDB837

XML column(s) (short) This version of FM/Db2 does not support the XML data type introduced with Db2® version 9. The function cannot be performed.

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.

Specify a Db2® object that does not include XML columns.

FMNDB838

Duplicate count reached (short) The specified duplicate count was reached. The import has been canceled. (long).

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.

The "Max duplicate" count value is specified on the Import Options panel, selected using the "edit options" field on the Import function entry panel. The response depends on the context of when duplicate row errors are expected. Rerun the import after increasing the "Max duplicate" value. When duplicate row errors are not expected, examine the input data to determine why duplicate row errors are occurring.

FMNDB839

Unable to process (short) The Db2® object contains one or more LOB columns. There is insufficient memory available for FM/Db2 to process data from this object, because of the large size of the LOB column(s). Refer to the Edit Tutorial, General information, Restrictions for additional information on how to avoid this problem.

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

Specify a Db2® object that does not include LOB columns.

FMNDB840

Format not for template (short) The Data Format is not compatible with that used to create the template. Template is template type.

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 data format for the input data set is specified on the Import options panel, selected using the "edit options" field on the Import function entry panel. The value specified must match the actual data format of the input data. It must also match the type of template specified in the template, or copybook, specified on the import function entry panel. Verify that the specified template correctly describes the input data. Determine the data format of the input data, use that information to set the appropriate data format value on the Import options panel, and retry the import operation.

FMNDB849

Incompatible options (short) The data format must be 2 (Db2® unload format) when execution option 3 (Batch, using Db2® UNLOAD) is selected. (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

Adjust the data format option as indicated, and retry the operation. Note, that it is also possible to use the FM/Db2 export function to export data in "Db2® unload format", without running a Db2® batch job. If this is what is intended, set the execution option on the first export options panel to either '1' (online) or '2' (batch), and retry the operation.

FMNDB850

Must be sequential file (short) The Db2® UNLOAD utility does not support unload of data to a partitioned data set. (long).

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.

Specify a sequential file (Data set organization of PS), rather than a partitioned data set (Data set organization of PO), for the output data set. Retry the operation.

FMNDB851

Must be sequential file (short) The Db2® UNLOAD utility requires that the unload data set be a sequential file (DSORG=PS).

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.

Check the type for the output data set specified for the Db2® unload operation on the FM/Db2 export 'To' panel. Ensure that a sequential file (Data set organization of PS) is specified. Retry the operation.

FMNDB852

Not required (short) A query number value is only required with the EXPLAIN primary command. (long).

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.

Remove the query number and retry the operation. If the intention was to EXPLAIN the SQL statement, type 'EXPLAIN' on the command line, and press Enter.

FMNDB853

Delete failed (short) The deletion of all rows from the Db2® object failed - the import function has been canceled. (long).

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.

There are many reasons why Db2® might reject a 'DELETE * FROM object name' statement, including referential integrity errors, locking problems, and unavailable resources. Retry the operation. If the problem persists, issue the 'DELETE * FROM object name' directly using FM/Db2 options 4.3, 4.4, or Db2® SPUFI. If the operation fails, use the SQLCODE to determine the cause of the failure.

FMNDB855

row count rows+hdr exported (short) Row countrow(s) and column header row exported from Db2® object object nameto file data set name. (long).

This message is issued by the FM/Db2 export function and is specific for an export with CSV format and the "Include column headers" option selected. FM/Db2 exported row count rows from Db2® object object name to data set data set name. The first row exported is a header row, containing the names of the Db2® columns in place of the data for those columns.

No action required. Informational message.

FMNDB856

Invalid character ' or " (short) The Delimited Variables (CSV) separator cannot contain either a single quote (') or double quote ("). Choose another value. (long).

The user entered a value in the "Separator character" field on the second FM/Db2 Export options panel. This field is used to enter a one or two character value for the separator character in "delimited variables (CSV)" export format. The value entered contains either a single or double quote, which is not supported.

The delimited variables (CSV, comma separated variables) format is loosely defined. In situations where the default separator character (comma) is inappropriate, FM/Db2 allows the specification of a one, or two, character alternative value. The separator value cannot include either a single quotation mark or double quotation mark, because this causes syntactical ambiguity when the exported data also includes single or double quotation marks, either within the data, or inserted to encapsulate the data. Select another value.

FMNDB858

Must be numeric, >0 (short) The value entered must be an integer in the range 1-2147483647. (long).

A value entered in the "start position" field on the editor function entry panel, or the "create count" field on the data create function entry panel, is invalid. A numeric value is required, which must be a positive integer in the range 1-2147483647, inclusive.

Correct the value, retry the operation.

FMNDB859

Must be numeric, >=0 (short) The value entered must be an integer in the range 0-2147483647. You can specify 0, * or ALL to indicate all rows. (long).

The value entered in a field on a File Manager/Db2 function entry panel is invalid. A numeric value is required, which must be a non-negative integer in the range 0-2147483647, inclusive. This message is issued for various "row count" input fields. A value of * and ALL can also be entered as synonyms for 0. These values indicate that there is no limit to the number of rows or records to be processed.

Correct the value, retry the operation.

FMNDB890

Db2® subsystem Db2 SSID not defined to z/OS®?.

This message is issued by a File Manager/Db2 batch job, when connection to Db2® system Db2 SSID failed. One reason for this message being issued is that D2 SSID does not exist (has not been defined to the local z/OS® system). This might occur in sites running multiple LPARs with shared DASD, where Db2® systems are available on some,but not other, z/OS® systems.

Check that the Db2® SSID specified as a parameter is defined to the z/OS® system where the batch job was executed. If this is not the problem, look up Db2® error code '00F30006' in the Db2® Codes manual and proceed as directed for that error.

FMNDB900

Own authorization ID (short) An authorization ID cannot grant a privilege to itself. (long).

This message is issued by the FM/Db2 privileges function, in the situation where "An authorization ID or a role attempted to execute a GRANT statement in which that ID itself appears as one of the entries in the list of 'grantee' authorization IDs or role names".

Respond as for SQLCODE-554. The usual remedy is to remove the user current Db2® authid/role from the list of target Db2® authids/roles.

FMNDB903

Identifier too long (short) The identifier is too long. See the SQL Reference for information about the maximum lengths for identifiers. Db2® returned an SQL code of -107 for SQL statement SQL statement. (long).

This message is issued when an SQL statement contains an identifier that is too long. When connected to Db2® V8 systems or later, this error is unlikely, given the large maximum lengths for most Db2® identifiers, compared to the corresponding Db2® V7 values.

Respond as for SQLCODE-107

FMNDB904

Not authorized (short) Your authorization ID does not have the authority to change the privileges for this object. Db2® returned an SQL code of -551 for SQL statement SL statementlong)

This message is issued by the FM/Db2 Object Privileges utility. The Db2® authorization IDs for the current user do not have the authority to change (GRANT or REVOKE) for the object.

Respond as for SQLCODE-551. See your Db2® System Administrator.

FMNDB905

Object not found (short) The specified Db2® object does not exist. Db2® returned an SQL code of -204 for the SQL statement SL statement long)

This message is issued by the FM/Db2 Object Privileges utility. The Db2® object for which the privileges are to be changed could not be found (SQLCODE-204).

Respond as for SQLCODE-204. Check the Db2® object name.

FMNDB907

Cannot be revoked (short) You cannot revoke the specified privilege because the revokee does not possess the privilege or because the specified Db2® authid did not grant the privilege. Db2® returned an SQL code of -556 for SQL statement SL Statement. (long).

This message is issued by the FM/Db2 Object Privileges utility. The privilege cannot be revoked.

Respond as for SQLCODE-556. Refer to the SQL Codes manual, for the appropriate version of Db2®, for a detailed list of possible causes of this error.

FMNDB909

Not authorized (short) Your authorization ID does not have the privilege to issue a REVOKE statement with the BY clause. Db2® returned an SQL code of -552 for SQL statement SL statement.long

This message is issued by the FM/Db2 Object Privileges utility. The privilege cannot be revoked.

Respond as for SQLCODE-552.

FMNDB910

Privilege conflict (short) One or more privileges conflict with one or more other privileges. (long).

This message is issued by the FM/Db2 Object Privileges utility. An example that causes this error is selecting the 'ALL' option for a privilege, as well as one or more of the individual privileges that are included when 'ALL' is specified.

Correct the specification of the privileges to be processed. In general selecting the 'ALL' option means that you should deselect all of the privileges that are included when 'ALL' is specified.

FMNDB911

Not required (short) This field should be blank for the specified option. (long).

On the "Alter Table - VALIDPROC" panel, the "type of VALIDPROC" is set to 1, and a value is also specified for "program name". A value for "program name" is only required when the "type of VALID-PROC" is set to 2.

Check the "type of VALIDPROC" specification. If NULL is the intended specification, remove the value from the "program name" field, and retry the operation. If the intention is to add a program name, change the "type of VALIDPROC" specification to 2, and retry the operation.

FMNDB913

Invalid option (short) The selected option is not one of the listed values or the object type is not supported on the remote Db2® system you specified. This error can occur when you try to list certain Db2® objects on a remote Db2® system that is at an earlier release of Db2® than the system to which you are connected.

This message is issued by the FM/Db2 Object Privileges utility. The value entered in the "object type" field is invalid. The request cannot be processed.

The valid options for the "Object type" field are listed on the panel. Specify one of the values listed (1-15 inclusive).

FMNDB914

Different Db2® release (short) The release level of the remote Db2® system is different than the release level of the Db2® system to which you are connected. The choice of Db2® object types has been refreshed to show those object types supported on the remote system. Press ENTER again to get the requested list. (long).

This message is issued by the FM/Db2 Object List and Object Privileges utilities when the user enters a remote location value. FM/Db2 connects to the specified location and compares the Db2® version of the remote location against the version of the currently connected Db2® system. When the values are different this message is issued.

No action required. Informational message. Press enter to refresh the list of available object types.

FMNDB915

Empty table (short) The Db2® object contains no rows, or no rows match the specified row selection criteria. (long).

This message is issued by the FM/Db2 editor when the result table for an object or select statement contains no rows.

No action required. Informational message.

FMNDB916

Excluded rows shadow is off. There are no unexcluded rows to display. (long).

In a File Manager/Db2 editor session, the shadow-line for excluded-rows has been turned off, and there are no rows to display. Note, that when the excluded-row shadow-line has been turned off, the string 'SHAD' appears immediately to the left of "Format", at the top right of the display, in TABL mode. For those familiar with ISPF shadow lines, the FM/Db2 editor allows the display of the shadow-line indicator to be suppressed, using a command like "SHADOW X OFF". This is not supported in the ISPF editor. Excluded lines are always indicated with a shadow-line. When excluded-row shadow-lines are turned off and when all of the rows in the current editor session are shadow-lines, the editor display appears as though there are no rows in the table (no shadow-line indicator). This message is displayed to alert the user to the fact that there are rows in the result table, even though there are no lines displayed.

No action required. Informational message. You can turn on the shadow-line indicator with "SHADOW X ON".

FMNDB917

No rows to display.

In a File Manager/Db2 editor session, the shadow-line for excluded-rows is turned on, and there are no rows to display. See also the message description for FMNDB916. This message is typically issued when edit operations have deleted all rows from the current editor session.

No action required. Informational message.

FMNDB918

Excluded rows shadow is off. Either no unexcluded rows to display, or no rows match the filter specification. (long).

In a File Manager/Db2 object list/privileges display, the shadow-line for excluded-rows has been turned off, and there are no rows to display. Note, that when the excluded-row shadow line has been turned off the string 'SHAD' appears immediately to the left of "Format", at the top right of the display, in TABL mode. The FM/Db2 object list/privileges utilities use the FM/Db2 editor to display lists of objects and privileges. When a filter value is specified for any column, the editor display is adjusted to show only those rows that match the filter value for that column. Any nonmatching rows are converted to excluded-rows, and these rows do NOT produce a shadow-line. This occurs regardless of the current setting for the excluded-row shadow-line. For those familiar with ISPF shadow-lines, the FM/Db2 editor allows the display of the shadow-line indicator to be suppressed, using a command like "SHADOW X OFF". This is not supported in the ISPF editor. Excluded-lines are always indicated with a shadow-line. When all of the rows in the current display are shadow-lines, the editor display appears as though there are no rows object list/privilege display (no shadow-line indicator). This message is displayed to alert the user to the fact that there are rows in the object list/privilege display, even though there are no lines displayed. This message is displayed when either:

  • A filter value entered for a column results in no matches, or;
  • When all rows are excluded.

No action required. Informational message.

FMNDB919

No rows to display, or no rows match the filter specification. (long).

In a File Manager/Db2 object/privileges display, the shadow-line for excluded-rows is turned on, and there are no rows to display. The FM/Db2 object list/privileges utilities use the FM/Db2 editor to display lists of objects and privileges. See also the message description for FMNDB918. This message is displayed when a filter value entered for a column results in no matches.

No action required. Informational message.

FMNDB921

No rows match key (short) There are no rows in the parent table that match the foreign key value. This can occur when a foreign key column(s) has the NULL value. (long).

A related edit session of a parent table has no rows that match a foreign key in a dependent table.

No action required. As noted in the long message text, this condition can occur when a foreign key value in the dependent table is NULL.

FMNDB922

No rows match key (short) There are no rows in the dependent table that match the primary/parent key value. (long).

A related edit session of a dependent table has no rows with a foreign key that match the primary or parent key value in the parent table.

No action required. A parent/primary key value may exist for which there are no corresponding rows (in terms of foreign key value) in the dependent table.

FMNDB923

Already granted warning (short) At least one of the authid(s) or role(s) already possesses the privilege(s) from the grantor.

This message is issued by the FM/Db2 Object privileges utility when a GRANT statement returns an SQLCODE+562. This is a warning condition indicating that the GRANT has already been executed for one or more privilege/authid/role combination. The execution of the SQL statement is successful. Any privileges previously held by the target Db2® authids/roles from the grantor are retained (not changed). Any new privileges specified have been successfully GRANTed.

No action required. When there are multiple Db2® authids or roles as target for the GRANT, or multiple privileges being GRANTed, it is not possible to determine which privileges were previously available.

FMNDB924

Grant option warning (short) The WITH GRANT OPTION was ignored for one or more of the privilege(s). (long).

A GRANT statement generated by the FM/Db2 privileges utility was executed. The statement included the "WITH GRANT OPTION' clause. Db2® returned SQLCODE+558. This is a warning condition indicating that the "WITH GRANT OPTION" clause is redundant. The GRANT statement was successfully executed. An example of an operation that results in this warning condition is attempting to grant the SYSADM privilege to a Db2® authid, with "WITH GRANT OPTION". The FM/Db2 privileges Grant panels allow either 'Y', or 'G', to be specified against the various Db2® privileges; 'Y' corresponds to "GRANT" while 'G' corresponds to "GRANT" and "WITH GRANT OPTION".

No action required.

FMNDB925

Not authorized (short) Your authorization ID does not have the authority to GRANT|REVOKE the privilege type system privilege. Db2® returned an SQL code of -552 for SQL statement SL statement.

The FM/Db2 privileges utility attempted to execute SQL statement SL statement. Execution failed with Db2® returning SQLCODE -552, which indicates that the user does not have the authority to execute the statement.

This is an error condition. Consult with your Db2® security administrator to obtain the necessary Db2® authority to execute the statement.

FMNDB926

Own authorization ID (short) An authorization ID cannot revoke a privilege from itself. (long).

The FM/Db2 privileges utility was used to issue a REVOKE statement. Execution of the statement failed with Db2® returning SQLCODE-555. This error is issued when the REVOKE statement would have the effect of removing a privilege from a Db2® authid or role that is possessed by the same Db2® authid or role. This is not supported.

Examine the grantees and remove the Db2® authid or role that corresponds to the current Db2® authid or role of the user.

FMNDB927

Invalid name (short) The name is invalid. A database/table space/plan name must be an SQL ordinary identifier - no lower case characters. See the SQL Reference manual for a definition. Db2® returned an SQL code of -113 for SQL statement SQL statement.

A database/table space/plan name entered using the FM/Db2 object privileges utility is invalid. An SQL ordinary identifier is required. See the SQL Reference for a definition. An ordinary identifier is an uppercase letter, followed by zero or more characters, each of which is an uppercase letter, a digit, or the underscore character.

Correct the name and retry the operation.

FMNDB928

Insufficient authority (short). You cannot revoke this privilege. The current SQLID (D2 authid)does not have SYSADM or SYSCTRL authority. You can only revoke a privilege when the current SQLID (Db2 authid) originally granted the privilege. (long).

The FM/Db2 privileges utility was used to attempt to issue a REVOKE statement. The user current Db2® authid D2 authid, is different to the Db2® authid originally used to grant the privilege. While it is possible to revoke a privilege originally granted by another Db2® authid, this requires SYSADM or SYSCTRL authority, which the current Db2 authid does not have. The statement cannot be executed.

In general, without either SYSADM or SYSCTRL authority, you will be unable to revoke Db2® privileges granted by another Db2® authid. Consult with your Db2® Security Administrator to obtain the necessary Db2® authority to execute the statement.

FMNDB939

LOB limit exceeded (short). A Db2® internal limit for the size of a LOB has been exceeded. Look up the SQLCODE-904 issued previously and respond as appropriate.

Db2® reported an SQLCODE-904 error when an attempt was made to add data to a LOB. This error is specific to the XML editor. The current editor session is terminated and the current unit of work is rolled back. Any changes made since the last explicit SAVE are lost.

An SQL error pop-up panel is displayed before this message is issued. Look up the reason code in the message and respond as appropriate. You might need to increase the Db2® installation value LOBVALA, specified in DSNTIJUZ.

FMNDB940

Invalid PIECESIZE (short). PIECESIZE in Klobytes|Megabytes|Gigabytes must be a multiple of 2 between mn value and mx value. (long).

An invalid value was entered for "piecesize" on the "Create Index: Type" panel (Db2® Object Functions). mn value and mx value show the minimum and maximum values that can be used for the specified space-multiplier, which will be either kilobytes, megabytes, or gigabytes.

Select an integer value between the two values shown that is a power of 2. For kilobytes, valid values are: 256, 512, 1024, .. 67,108,864. For Megabytes valid values are: 1, 2, 4 .. 65,536. For Gigabytes, valid values are: 1, 2, 4 .. 64.

FMNDB941

Invalid combination (short) A VCAT name cannot be specified with a storage group name, primary, or secondary space requirements, or the ERASE option.

An invalid combination of values was entered when attempting to create a table space, or index, using the Db2® Object Functions. When creating either a table space, or index, a VCAT name can be specified, indicating that space allocation is under user control. Otherwise, the VCAT name must be blank, and a storage group name can be specified, indicating that space allocation is controlled by Db2®. In the latter case, primary and secondary space values may also be entered.

Decide whether a VCAT name or storage group name is appropriate. In the former case do not specify any of: storage group name, primary or secondary space allocation values. In the latter case do not specify a VCAT name value.

FMNDB942

Storage group required (short) Primary and secondary space requirements, and the ERASE option can only be specified if a storage group name is also specified. (long)

An invalid combination of values was entered when attempting to create an index using the Db2® Object Functions. Either:

  1. One or more non-blank values have been specified for "Primary space" or "Secondary space" on the "Create Index:Allocation" panel. However the "Storage group name" value is blank. You must enter a "storage group name" if you intend to specify space allocation values.
  2. One or more non-blank values have been specified for "Primary space", "Secondary space", or "Erase data" on the "Create Index: Partitions" panel. However, the "Storage group name" value is blank. You must enter a "storage group name" if you intend to specify space allocation or an "Erase data" value."

Enter a valid storage group name. Alternatively do not specify "Primary space" "Secondary space" or "Erase data" values.

FMNDB943

Invalid selection (short) Select or deselect columns using the character ''S''. Order columns explicitly in the key|indexusing numerics.

An invalid character was entered in either the Create Table, or Create Index functions, of the Db2® Objects utility.

You can select a column by typing an 'S' in the appropriate field. All other letters are invalid. If a column has previously been selected, you deselect it by typing 'S' in the appropriate field. Once a column has been selected, you can enter any numeric (1, 2, 3, and so on) to specify the order of the columns in the index, or key. On the "Create Table: Unique Constraints " panel you can also select a column by typing any numeric in the appropriate field, and deselect a column by removing the number in the appropriate field.

FMNDB944

Already used (short). Order number number was already set for column column name on row row number of the display.

An invalid number was entered in either the "Create Table" or "Create Index" functions of the Db2® Objects utility. When defining an index, or key with multiple columns, the order of the columns in the index, or key, is specified using numbers. Thus, for an index comprising three columns (COL4, COL7 and COL10), you would enter the numbers 1, 2 and 3 (in some combination) against those three columns.

The number for the column has already been used for another column. Determine which columns should be in the index or key, then assign a unique number to each column. The column with the lowest used number will be the first column in the index or key, followed by the column with next-lowest-used number, and so on.

FMNDB945

Maximum partitions (short). The insert (I) or repeat (R) command cannot be executed because the maximum number of partitions allowed by Db2® has already been defined. (long).

The user issued the 'I' or 'R' command against the 254th row on the "Create Index: Partitions" panel of the Db2® Objects utility. The maximum number of partitions that can be defined is 254 (Db2® version 7), so extra partitions cannot be added.

No action required.

FMNDB946

Invalid value (short). Enter one of the listed values: list of valid values. (long).

An invalid value was entered for a field in the Db2® Objects function. list of valid values contains the acceptable values for the field in error.

Specify a value shown in list of valid values.

FMNDB947

Set columns/partitions (short). You must use option 2 to select the columns comprising the index and option 5 to define the partitions before assigning partition values. (long).

The user selected option 6 on the "Create Index" panel of the Db2® Objects function. Either the columns that should comprise the index, or the partitions for the index, have not been defined. Both tasks must be completed before partition values may be assigned.

Select option 2 to confirm that the columns that should comprise the index have been identified; then select option 5 to define the partitions for the new index.

FMNDB948

IT:Define &$ITEM:TE &$ITEM---17 T:You must use option &$OPTN to define the &$ITEM for the &$OBJ :TE T:before using this option.:TE

T

I

FMNDB949

Table not found (short). The table to be indexed was not found in the Db2® catalog. (long).

The user entered a table name on the "Create Index" panel of the Db2® Objects function. That table name does not exist on the current server.

Check the table name for spelling mistakes. You can use the FM/Db2 Object List utility to show all table names defined at the current Db2® server if required. Correct the table name and retry the operation.

FMNDB950

Set partition values (short) Partitions have been defined for this index using option 5. You must set partition values using option 6 before you can define the index.

This message is issued by the "Create Index" dialog (Db2® Object Functions). For a partitioned index, the number of partitions is set using option 5 (Partitions). Once the partitions are defined, you also need to set the maximum values for each partition using option 6 (Partition values). The index cannot be created until the partition values have been specified.

If a partitioned index is required, select option 6 (Partition values), and specified appropriate values. If a non-partitioned index is required, select option 5 (Partitions), and delete all but one partition entry.

FMNDB951

Update partition values (short) The column selections or partition definitions have changed since the partition values were set. You must reset the partition values using option 6 before you can define the index.

This message is issued by the "Create Index" dialog (Db2® Object Functions). Partition values have been set for all partitions and columns previously specified. However, a subsequent change has invalidated the partition values. There are two possibilities:

  1. The columns specified for the new index have changed (columns added or deleted).
  2. The partitions specified using option 5 (Partitions) have changed. The index cannot be created until the partition values have be specified.

If a partitioned index is required, select option 6 (Partition values) and specified appropriate values. If a non-partitioned index is required, select option 5 (Partitions) and delete all but one partition entry.

FMNDB952

Conflicting selection (short) value 1 > is not valid because value 2.

This message is issued in many places within the Db2® Object Function dialog. The SQL syntax used to create the object has restrictions on the use of both value 1 and value 2. In most cases you can resolve the error by specifying either value 1 or value 2, but not both. The Object cannot be created until the conflicting selections are resolved.

Determine which of the two selections is appropriate and remove the unwanted selection. Retry the operation. If the appropriate choice cannot be determined, refer to the SQL Reference manual for the appropriate version of Db2®.

FMNDB953

Errors retained (short) Invalid data has been saved because the CANCEL command was entered in response to an input verification message. The statement type statement may be invalid if executed: return to the previous panel and correct the error, or return to the panel name panel and start from the beginning.

This message is issued in many places within the Db2® Object Function dialog. An invalid value was entered on an option panel for the current CREATE or DROP function, followed by the user pressing CANCEL (PF12 by default) to return to the option selection panel for the current CREATE or DROP function. The invalid value is unresolved and may cause problems if an attempt is made to executed the current CREATE or DROP function.

In most cases the problem can be resolved by reselecting the previous option panel (where CANCEL was entered), and correcting the invalid values entered there. If this does not resolve the problem, return to the Db2® Object Functions panel and restart the operation.

FMNDB954

No suitable rows (short). The current table definition does not contain columns specified as not null. Use option 2 to define not null columns before defining :primary/unique keys. (long).

This message is issued by the "Create Table" dialog (Db2® Object Functions). The user selected the "unique constraints" option after previously defining columns for the new table using option 1 (Columns). A column can only be included in a unique constraint key if it is defined as NOT NULL, and none of the columns currently defined for the new table meet this requirement.

Select option 2 (Nulls/Default values) and set the Null status for each column as appropriate. You will need to specify either NN (NOT NULL) or ND (NOT NULL WITH DEFAULT) for at least one column to be able to specify a unique constraint for the new table.

FMNDB955

No suitable rows (short). The current table definition does not contain any non-ROWID, non-LOB columns specified as not null, nor any identity columns. Use option 2 to define not null columns, or option 8 to define identity columns before defining primary/unique keys. (long).

This message is issued by the "Create Table" dialog (Db2® Object Functions). The user selected the "unique constraints" option after previously defining columns for the new table using option 1 (Columns). A column can only be included in a unique constraint key if it is defined as NOT NULL, and none of the columns currently defined for the new table meet this requirement. This message is issued when there are columns defined as ROWID, or CLOB/DBCLOB, BLOB.

Select option 2 (Nulls/Default values), and set the Null status for each column as appropriate. You will need to specify either NN (NOT NULL) or ND (NOT NULL WITH DEFAULT) for at least one column to be able to specify a unique constraint for the new table. You can also define numeric columns as INDENTITY columns using option 8 (Generate values). An IDENTITY column can be included in a unique constraint.

FMNDB956

Too many selections (short). You have already selected Max column count columns for this key, which is the maximum allowed by Db2®. (long).

This message is issued by the "Create Table" dialog (Db2® Object Functions), usually when defining columns to be included in the primary key, or other unique constraint defined for the table. Max column count is 64 for Db2® for z/OS® versions 8 - 10 inclusive.

Reduce the number of columns in the primary key or unique constraint.

FMNDB957

Table/view not found (short). The model table/view was not found in the Db2® catalog. (long).

This message is issued by the "Create Table" dialog (Db2® Object Functions), when a model table name is entered, but the Db2® object does not exist.

Correct the Db2® object name, retry the operation. You can use the Object List utility (Option 3.4) to show all the Db2® objects (tables/views/aliases ) defined at the local server.

FMNDB958

Too many constraints (short) Too many unique constraints have been found in model tables. Only the first three unique constraints found in the Db2® catalog have been loaded.

This message is issued by the "Create Table" dialog (Db2® Object Functions), when a model table name is entered and a load of the informationm for the model table is requested. The "Create table" dialog supports a maximum of three unique constraints for any table being defined. This message might be issued for the load of a single Db2® object, with 4 or more unique constraints defined, or when multiple loads are requested.

This is an informational message. In the unlikely event that 4 or more unique constraints need to be defined for the table being created, consider defining the table with 3 initial constraints, and using ALTER TABLE to add any additional constraints.

FMNDB959

Invalid option (short). Only column information can be loaded when the add option is selected and columns have already been defined or loaded. (long).

This message is issued by the "Create Table" dialog (Db2® Object Functions), when a model table name is entered. The user loaded information for one model table, then attempted to add load additional information for another. For the second and subsequent loads, only the "Basic table information" and "Column information" options can be selected.

You can only load "Primary key information", "Unique key information", "Referential constraints" and "Check constraint" information for the first model table specified. Deselect the option for all of the above and retry the operation. Alternatively set the Refresh or Add option to Refresh and repeat the operation. This will replace any existing information with that for the current model table.

FMNDB960

Too many constraints (short) Too many table foreign keys have been defined for this table. The number of table foreign keys is limited to the number of ISPF tables named FMN2CTnn that can be created.

This message is issued by the "Create Table" dialog (Db2® Object Functions). An attempt was made to create more than 100 foreign keys for the current table. While there is no Db2® limit on the number of foreign keys, the "Create Table" dialog is limited to a maximum of 100 foreign keys.

Review the number of foreign keys that have been specified, reduce the number to 100 or less.

FMNDB961

Order required (short) A referenced column name has been entered for this column, but no order. An order is required if the column is to be included in the foreign key.

This message is issued on the "Create Table: Table Referential Constraint" panel. When creating a table referential constraint that includes more than one column (the usual usage is for a multiple-column foreign key definition), an order specification is required for every column that is part of the foreign key being defined.

Specify an order for every column that is to be part of the foreign key.

FMNDB962

Ref. column required (short). If any of the foreign key columns reference a specific column in the parent table, then all of the foreign key columns must do so. (long).

This message is issued on the "Create Table: Table Referential Constraint" panel. When creating a table referential constraint that includes more than one column (the usual usage is for a multiple-column foreign key definition), an order specification for a column was entered without a corresponding entry in the Parent Key column field.

Specify a column name in the Parent Key column field, for every column that is to be part of the foreign key.

FMNDB963

No columns selected (short). No columns have been selected to define the foreign key for this constraint. (long).

This message is issued when creating referential constraints for a table (Create Table dialog of Db2® Object functions). The user created a new constraint name and specified the parent table for the relationship. However no foreign key columns have been defined.

Use the 's' command to select the new constraint entry. When the "Create Table: Table Referential Constraint" panel is displayed, select the columns that comprise the foreign key, and enter the names of the corresponding columns in the parent table.

FMNDB964

Some data not loaded (short). The Db2® catalog did not contain any information for the model table or view for at least one of the model load options specified. For example, check constraints were requested but the referenced model table has no check constraints. (long).

This message is issued by the "Create Table" dialog (Db2® Object Functions), when a model table name is entered, and a load of existing Db2® object information is requested.

No action required. Informational message.

FMNDB965

No suitable rows (short) The current table definition does not contain any short string columns specified as not null. Use option 2 to define not null columns before defining Procedure Exits.

This message is issued by the "Create Table" dialog (Db2® Object Functions). The user selected option 7 (Procedure exits). However, there are no suitable columns defined on which a procedure exit can be defined. A procedure exit cannot be defined unless a suitable column is defined.

Option 7 (Procedure exits) allows a FIELDPROC specification for suitable columns of the table. In general, only character (CHARACTER/GRAPHIC) columns of length <=255, defined as NOT NULL, or NOT NULL WITH DEFAULT, are suitable. Define a suitable column using options 1 (Columns) and 2 (Nulls/Default values) and then reselect option 7.

FMNDB966

External name required (short). Specify an external name for the object type using option number before using this option. This is required because the specified name exceeds eight characters. (long).

This message is issued by the "Create Function" and "Create Stored Procedure" dialogs of the Db2® Object Functions. The length of the name for the function, or stored procedure, exceeds 8 characters. In this situation an external name for the function must also be specified. object type is either "function" or "stored procedure", depending on the Object function. number is 4 when creating a function, and 3 when creating a stored procedure.

Select the specified option, and enter an external name for the function or stored procedure. Consult the Db2® for z/OS® SQL Reference for the appropriate version of Db2® for details of acceptable formats for the external name value.

FMNDB967

String too long (short). The string constant specified as a default value is too long for the associated string column. (long).

This message is issued by the "Create Table" dialog (Db2® Object Functions) when specifying a default value for a character data type column. The default value is too long. For example, specifying a default value of 'ABCDE' (length 5) for a CHAR(3) (length 3) column.

Compare the length of the default value string, and the maximum length for the column, as defined in the length field for the data type. Adjust either value as appropriate.

FMNDB968

Invalid data (short). The decimal number specified as a default value is invalid or out of range for the associated decimal number column. (long).

This message is issued by the "Create Table" dialog (Db2® Object Functions) when specifying a default value for a DECIMAL data type column. The specified default value is invalid in the context of the precision and scale specified for the column.

Compare the definition for the DECIMAL column with the implied precision, and scale from the default value. Adjust either the data type (precision and scale) in the column, or the default value.

FMNDB969

Invalid DATE|TIME|TIMESTAMP (short) The format of the DATE|TIME|TIMESTAMP field or the data it contains is invalid.

This message is issued by the "Create Table" dialog (Db2® Object Functions) when specifying a default value for a DATE, TIME, or TIMESTAMP data type column. The specified default value is invalid.

Examine the default value entered and the data type for the column. The two possible causes of this error are:

  1. An invalid format. Example: '12/10/2001' is not a valid format for a TIME column.
  2. An invalid value. Example: '32/11/2001' is an invalid date, since 32 is not a valid day (or month).

Consult the Db2® for z/OS® SQL Reference for the appropriate version of Db2® for a detailed description of valid DATE/TIME and TIMESTAMP constants, including supported formats.

FMNDB970

Date/time not validated (short). The default values for one or more date or time fields were not validated because the Db2® subsystem date/time format is LOCAL or unknown.

This message is issued by the "Create Table" dialog (Db2® Object Functions) when specifying a default value for a DATE or TIME column. The Db2® default for either the DATE or TIME format is either LOCAL, or unknown. In either case, the panel logic cannot validate the specified default value.

No action required. Informational message. If any default value entered is invalid, an SQL error will occur when the attempt is made to create the Db2® object.

FMNDB971

Date/time not validated (short) The specified default date or time value was not validated because the Db2® subsystem date/time format is LOCAL or unknown. (long).

This message is issued by the "Create Table" dialog (Db2® Object Functions) when specifying a default value for a DATE, TIME, or TIMESTAMP column. This message is issued on pop-up panel "Create Table: Default Value". The Db2® default for either the DATE or TIME format is either LOCAL, or unknown. In either case, the panel logic cannot validate the specified default value.

No action required. Informational message. If any default value entered is invalid an SQL error will occur when the attempt is made to create the Db2® object.

FMNDB972

Invalid data (short). The floating point number specified as a default value is invalid or outside the range supported by Db2®. (long).

This message is issued by the "Create Table" dialog (Db2® Object Functions) when specifying a default value for a binary floating point column (REAL, FLOAT, DOUBLE). The specified default value is outside the range supported by Db2®.

The limits for floating point constants are documented in "Limits in Db2® for z/OS®", in the Db2® for z/OS® SQL Reference manual, for the appropriate version of Db2®. Compare the specified default value against the documented values, and adjust as appropriate.

FMNDB973

GENERATED ALWAYS added (short). The GENERATED ALWAYS clause has been added to the definition of the column with a data type of ROWID. To change the GENERATED clause select option 8. (long).

This message is issued by the "Create Table" dialog (Db2® Object Functions), when adding a column definition for a ROWID column.

No action required. Informational message. In most cases it should not be necessary to modify the GENERATED clause for a ROWID column. Option 8 (Generated Values) allows the GENERATED clause to be modified.

FMNDB974

Invalid database name (short). You cannot specify the name of an implicitly created database when creating a table. Implicitly created database names have the form DSNxxxxx, where xxxxx is any 5 numeric digits. (long)

This message is issued by the "Create Table" dialog (Db2® Object Functions) when attempting to create a table. The database name specified is invalid because it has the form 'DSNxxxxx', where xxxxx is 00000-99999 inclusive. Names of this form are reserved for use by Db2®, as implicitly created database names. The table cannot be created.

Specify a different Db2® database name, or remove the database name completely if an implicitly required database is acceptable.

FMNDB980

Invalid value (A/D) (short). The valid values for the A/D field are A, for ascending; D, for descending, or blank. (long).

This message is issued on the "Column Selection/Edit" panel, when a value other than 'A' or 'D' is entered in the "A/D" column.

The "A/D" column in the "Column Selection/Edit" panel is used to specify the sort order for col-umns included in the ORDER BY clause. The valid values are 'A' for ascending (the default) or 'D' for descending. Specify one of these values, or leave the field blank for the default behaviour.

FMNDB981

Enter sort order (short). A sort order is required when a sort column is specified (A or D in the A/D field). Enter a number in the range 1..999. (long).

The 'Order' column in the "Column Selection/Edit" panel is used to specify the sort sequence for columns included in the ORDER BY clause. The user specified either 'A' or 'D' in the "A/D" column, but no value in the 'Order' column.

Enter a number in the 'Order' column for every column that also has a non-blank value in the "A/D" column.

FMNDB990

Mutually exclusive value (short). Specify a JOBNAME value, or an ADDRESS value, but not both. (long).

This message is issued by the "Create Trusted Context" dialog (Db2® Object Functions). A value was entered for both the JOBNAME and ADDRESS fields, however only one value is acceptable.

Specify either a JOBNAME value; or an ADDRESS value, but not both. The syntax for the CREATE TRUSTED CONTEXT SQL statement can be found in the Db2® for z/OS® SQL Reference manual for the appropriate version of Db2®.

FMNDB991

Value required (short). Either a JOBNAME value or an ADDRESS value is required. (long).

This message is issued by the "Create Trusted Context" dialog (Db2® Object Functions). No value was entered in either the JOBNAME or ADDRESS fields; a value is required for one.

Specify either a JOBNAME value; or an ADDRESS value, but not both. The syntax for the CREATE TRUSTED CONTEXT SQL statement can be found in the Db2® for z/OS® SQL Reference manual for the appropriate version of Db2®.

FMNDB992

Value not required (short). Do not specify a "Default Role Name" value when the "No Default Role" option is selected. (long).

This message is issued by the "Create Trusted Context" dialog (Db2® Object Functions). The user selected the "No default role" option, and also entered a value in the "Default role name" field. The two selections are mutually exclusive.

If a default role name is to be specified, deselect the "No default role" option. If there is to be no default role name, remove the "Default role name".

FMNDB993

Value not required (short). Do not specify a "Security Label Name" value when the "No Default Security Label" option" is selected. (long).

This message is issued by the "Create Trusted Context" dialog (Db2® Object Functions). The user selected the "No default security label" option, and also entered a value in the "Security label name" field. The two selections are mutually exclusive.

If a default security label name is to be specified, deselect the "No default security label" option. If there is to be no default security label, remove the "Security label name".

FMNDB994

Value not required (short). Do not select the "Without authentication" option when the "PUBLIC" option" is selected. (long).

This message is issued by the "Create Trusted Context" dialog (Db2® Object Functions). The user did not select the "PUBLIC" use option, and selected the "Without authentication" option. The second selection requires that the first option also be selected.

The valid choices for the two options ("PUBLIC" and "Without authentication") are: 1). Both options not selected. 2) Both options selected. 3) Only the first option selected.

FMNDC014

Rows rows exported (short). Rows row(s) exported from SELECT statement (user-specified) to file data set name. (long).

This is a message insert used by the FM/Db2 Export function. It shows the number of rows rows exported by the export function. The target data set is data set name. This message is specific to the export of data from a user-specified SELECT statement initially entered using FM/Db2 options 4.1-4.4.

No action required. Informational message.

FMNDC015

Rows rows+hdr expd (short). Rows row(s) and column header row exported from SELECT statement (user-specified) to file data set name. (long).

This is a message insert used by the FM/Db2 Export function. It shows the number of rows rows exported by the export function. The target data set is data set name. This message is specific to the export of data in CSV format, with column header data, from a user-specified SELECT statement initially entered using FM/Db2 options 4.1-4.4.

No action required. Informational message.

FMNDC019

Not in large mode (short). The export command with the ALL|X|EX|NX parameter is not available in large editor mode (row count = 0). (long).

The editor EXPORT command with the ALL|X|EX|NX parameter specified was issued from a File Manager/Db2 editor session, in large mode (row count = 0, also ALL, *). This is not supported and the command cannot be processed.

Use normal editor mode and re-try the operation.

FMNDC020

count row(s) exported from Db2® object source Db2 object to file file name. The open returned SQLCODE sqlcode. trunc_count rows had fetch SQLCODE +445 (truncation) warnings. warn_count other rows had fetch warnings (SQLCODE>0, but not +445).

This message is issued at the end of a File Manager/Db2 export function, when at least one positive SQLCODE was received retrieving data from Db2®. The number of rows exported, count; the Db2® object from which the rows were exported, source Db2 object; the output file name that contains the exported data, file name; the SQLCODE for the OPEN cursor, sqlcode; the number of rows fetched that had SQLCODE+445 warnings, trunc_count and the number of rows fetched that gave positive SQLCODEs (but not +445), warn_count are shown. SQLCODE+445 is a warning condition issued when data truncation occurs.

For SQLCODE+445 warnings, examine the exported data to see if the data truncation has resulted in any unexpected consequences. Take action as appropriate. For other warning SQLCODEs: If the export operation was run on-line, repeat the operation using the batch execution option. Run the resulting job and examine the messages produced. Look up the SQLCODEs reported in the Db2® for z/OS® SQL Codes manual, for the appropriate version of Db2®. Take action as appropriate.

FMNDC021

Row count row(s) and column header row exported from Db2® object object name to file data set name. The open returned SQLCODE sqlcode. trunc_count rows had fetch SQLCODE +445 (truncation) warnings. warn_count other rows had fetch warnings (SQLCODE>0, but not +445).

This message is issued by the FM/Db2 export function, when at least one positive SQLCODE was received retrieving data from Db2® and is specific for an export with CSV format and the "Include column headers" option selected. The number of rows exported, count; the Db2® object from which the rows were exported, source Db2 object; the output file name that contains the exported data, file name; the SQLCODE for the OPEN cursor, sqlcode; the number of rows fetched that had SQLCODE+445 warnings, trunc_count and the number of rows fetched that gave positive SQLCODEs (but not +445), warn_count are shown. SQLCODE+445 is a warning condition issued when data truncation occurs.

For SQLCODE+445 warnings, examine the exported data to see if the data truncation has resulted in any unexpected consequences. Take action as appropriate. For other warning SQLCODEs: If the export operation was run on-line, repeat the operation using the batch execution option. Run the resulting job and examine the messages produced. Look up the SQLCODEs reported in the Db2® for z/OS® SQL Codes manual, for the appropriate version of Db2®. Take action as appropriate.

FMNDC022

Rows row(s) exported from SELECT statement (user-specified) to file data set name. The open returned SQLCODE sqlcode. trunc_count rows had fetch SQLCODE +445 (truncation) warnings. warn_count other rows had fetch warnings (SQLCODE>0, but not +445).

This message is issued by the FM/Db2 Export function when at least one positive SQLCODE was received retrieving data from Db2®. It shows the number of rows rows exported by the export function; the target data set is data set name; the SQLCODE for the OPEN cursor is sqlcode; the number of rows fetched that had SQLCODE+445 warnings is trunc_count and the number of rows fetched that gave positive SQLCODEs (but not +445) is warn_count. SQLCODE+445 is a warning condition issued when data truncation occurs.

This message is specific to the export of data from a user-specified SELECT statement initially entered using FM/Db2 options 4.1-4.4.

For SQLCODE+445 warnings, examine the exported data to see if the data truncation has resulted in any unexpected consequences. Take action as appropriate. For other warning SQLCODEs: If the export operation was run on-line, repeat the operation using the batch execution option. Run the resulting job and examine the messages produced. Look up the SQLCODEs reported in the Db2® for z/OS® SQL Codes manual, for the appropriate version of Db2®. Take action as appropriate.

FMNDC023

Rows row(s) and column header row exported from SELECT statement (user-specified) to file data set name. The open returned SQLCODE sqlcode. trunc_count rows had fetch SQLCODE +445 (truncation) warnings. warn_count other rows had fetch warnings (SQLCODE>0, but not +445).

This message is issued by the FM/Db2 Export function when at least one positive SQLCODE was received retrieving data from Db2®. It shows the number of rows rows exported by the export function; the target data set is data set name; the SQLCODE for the OPEN cursor is sqlcode; the number of rows fetched that had SQLCODE+445 warnings is trunc_count and the number of rows fetched that gave positive SQLCODEs (but not +445) is warn_count. SQLCODE+445 is a warning condition issued when data truncation occurs. This message is specific to the export of data in CSV format, with column header data, from a user-specified SELECT statement initially entered using FM/Db2 options 4.1-4.4.

For SQLCODE+445 warnings, examine the exported data to see if the data truncation has resulted in any unexpected consequences. Take action as appropriate. For other warning SQLCODEs: If the export operation was run on-line, repeat the operation using the batch execution option. Run the resulting job and examine the messages produced. Look up the SQLCODEs reported in the Db2® for z/OS® SQL Codes manual, for the appropriate version of Db2®. Take action as appropriate.

FMNDC026

Open cursor SQLCODE=sqlcode.

This message is issued by the FM/Db2 export function, when executed in batch mode, when a positive SQLCODE is received from Db2® when the cursor is opened.

Look up the SQLCODE reported in the Db2® for z/OS® SQL Codes manual, for the appropriate version of Db2®. Take action as appropriate.

FMNDC027

Fetch SQLCODE=sqlcode for row row (data truncation).

This message is issued by the FM/Db2 export function, when executed in batch mode, whenever an SQLCODE+445 is received when fetching a row of data from Db2®. SQLCODE+445 indicates that data truncation occurred.

Examine the exported data to see if the data truncation has resulted in any unexpected consequences. Take action as appropriate.

FMNDC028

Fetch SQLCODE=sqlcode for row row (warning).

This message is issued by the FM/Db2 export function, when executed in batch mode, whenever a positive SQLCODE other than +445 is received when fetching a row of data from Db2®.

Look up the SQLCODE reported in the Db2® for z/OS® SQL Codes manual, for the appropriate version of Db2®. Take action as appropriate.

FMNDC030

Processing Db2® object name for DELETE.

This informational message is issued at the start of a BATSQL function. FM/Db2 is processing object name, for delete processing.

No action is required.

FMNDC031

Inserting rows into Db2® object name.

This informational message is issued at the start of a BATSQL function. FM/Db2 is processing object name, for insert processing.

No action is required.

FMNDC032

Processing Db2® object name for UPDATE.

This informational message is issued at the start of a BATSQL function. FM/Db2 is processing object name, for update processing.

No action is required.

FMNDC033

Row count rows deleted.

This informational message is issued at the end of a BATSQL function. FM/Db2 successfully deleted row count rows from the object.

No action is required.

FMNDC034

Row count rows inserted.

This informational message is issued at the end of a BATSQL function. FM/Db2 successfully inserted row count rows into the target object.

No action is required.

FMNDC035

Row count rows updated.

This informational message is issued at the end of a BATSQL function. FM/Db2 successfully updated row count rows from the object.

No action is required.

FMNDC036

Batch DELETE canceled because of excessive errors (errcnt,maxerr).

This informational message is issued during TYPE=DELETE BATSQL processing. FM/Db2 stopped deleting rows because the user-specified error limit maxerr (MAXERRORS keyword) was reached. The actual number of errors was errcnt. A summary of the errors that are encountered follows (messages FMNDC039 and FMNDC060).

Note that when an error is encountered processing a rowset, the error count is incremented by the number of rows in the rowset. This can result in the actual number of errors reported exceeding the value specified for MAXERRORS.

Examine the error summary and respond.

FMNDC037

Batch INSERT canceled because of excessive errors (errcnt,maxerr).

This informational message is issued during TYPE=INSERT BATSQL processing. FM/Db2 stopped inserting rows because the user-specified error limit maxerr (MAXERRORS keyword) was reached. The actual number of errors was errcnt. A summary of the errors that are encountered follows (messages FMNDC039 and FMNDC060).

Examine the error summary and respond.

FMNDC038

Batch UPDATE canceled because of excessive errors (errcnt,maxerr).

This informational message is issued at the end of a BATSQL function. FM/Db2 stopped updating rows because the user-specified error limit (MAXERRORS keyword) was reached. A summary of the errors that are encountered follows (message FMNDC039).

Note that when an error is encountered processing a rowset, the error count is incremented by the number of rows in the rowset. This can result in the actual number of errors reported exceeding the value specified for MAXERRORS.

Examine the error summary and respond.

FMNDC039

Error count rows gave SQLCODE sqlcode.

This informational message is issued at the end of a BATSQL function. During the function, the delete/insert or update operation resulted in error count SQLCODE sqlcode errors. If there were different SQLCODEs received (for example SQLCODE-803, SQLCODE-545) there is one occurrence of this message for each different SQLCODE.

Examine the error summary and respond.

FMNDC040

Row count pending deletes rolled back.

This informational message is issued at the end of a BATSQL function. FM/Db2 stopped deleting rows because the user-specified error limit (MAXERRORS keyword) was reached. Row count rows were deleted after the last commit point. The changes to these rows were backed out as a result of the Db2® rollback.

No action is required.

FMNDC041

Row count pending inserts rolled back.

This informational message is issued at the end of a BATSQL function. FM/Db2 stopped inserting rows because the user-specified error limit (MAXERRORS keyword) was reached. Row count rows were inserted after the last commit point. The changes to these rows were backed out as a result of the Db2® rollback.

No action is required.

FMNDC042

Row count pending updates rolled back.

This informational message is issued at the end of a BATSQL function. FM/Db2 stopped updating rows because the user-specified error limit (MAXERRORS keyword) was reached. Row count rows were updated after the last commit point. The changes to these rows were backed out as a result of the Db2® rollback.

No action is required.

FMNDC043

Row count commit(s) issued prior to completion.

This informational message is issued at the end of a BATSQL function. The AUTOCOMMIT keyword specified a nonzero value. FM/Db2 issued one or more commits as rows were processed. Row count does not include the final commit or rollback issued when the function ends.

No action is required.

FMNDC044

Required SET clause missing.

This error message is issued during processing of a BATSQL function. An update operation was requested, but no SET clause was found.

Ensure that a SET clause is specified, rerun the function.

FMNDC045

SET clause must begin with 'SET'

This error message is issued during processing of a BATSQL function. An update operation was requested, however the SET clause does not commence with 'SET'.

The SET clause must be a valid SET clause for an update statement, see the Db2® SQL Reference manual for a full description. Ensure that the SET clause begins with 'SET', rerun the function.

FMNDC046

SET clause incomplete, it must contain an assignment for >= 1 column(s).

This error message is issued during processing of a BATSQL function. An update operation was requested, however the SET clause does not include an assignment for at least 1 column.

The SET clause must include an assignment for at lease one column, for example: "SET COL1=value". See the Db2® SQL Reference manual for a full description. Correct the SET clause, rerun the function.

FMNDC047

WHERE clause must begin with 'WHERE'.

This error message is issued during processing of a BATSQL function. An update or delete operation was requested, however the WHERE clause does not commence with 'WHERE'.

The WHERE clause must be a valid WHERE clause for an update or delete statement, see the Db2® SQL Reference manual for a full description. Ensure that the WHERE clause begins with 'WHERE', rerun the function.

FMNDC048

Isolation UR incompatible with delete or update, CS substituted.

This informational message is issued at the start of a BATSQL function. The control statements include ISOLATION=UR for either a delete or update function. Uncommitted read is not supported when a positioned delete or update statement is issued. This method is the method that is used by the BATSQL function for deleting or updating rows. The isolation value was to CS (Cursor stability).

Review the value that is specified for the ISOLATION keyword. Consider changing the value to 'NONE' or 'CS'.

FMNDC049

DELETEALL=YES must be specified for a delete without a WHERE clause.

This error message is issued during processing of a delete BATSQL function. For a delete function, the omission of a where clause results in the attempted deletion of all rows of the table. As a safety feature, DELETEALL=YES must also be included in the control statements.

Review the intended action of the BATSQL function. If the intention is to delete every row in the table, add the DELETEALL=YES statement and rerun the function.

FMNDC050

Insert column list must be enclosed in (). Eg (Col1, Col2).

This error message is issued during processing of an insert BATSQL function. An invalid insert column clause was detected.

The insert column clause must include a list of comma-separated column names. The entire list requires enclosing parentheses. See the Db2® SQL Reference manual for a full description. Correct the insert column clause, rerun the function.

FMNDC051

Insert column list incomplete, it must contain >=1 column(s).

This error message is issued during processing of an insert BATSQL function. An invalid insert column clause was detected.

The insert column clause must contain at least one column name. Further, that column name must be a column of the target table. See the Db2® SQL Reference manual for a full description. Correct the insert column clause, rerun the function.

FMNDC052

Single row processing active.

This informational message is issued at the start of a BATSQL function. Single-row processing is active, that is, FM/Db2 fetches rows one-at-a-time from the source table.

No action is required.

FMNDC053

Rowset processing (nnn rows) active.

This informational message is issued at the start of a BATSQL function. Rowset processing is active, that is, FM/Db2 fetches nnn rows at a time.

No action is required.

FMNDC054

Required SELECT clause is missing or incomplete.

This is an error message issued during processing of the BATSQL function. The specified SELECT clause has either not been specified, or is incomplete.

Correct the coding of the SELECT clause. The SELECT clause should start with 'SELECT' and identify a result table. The shortest valid SELECT clause is 'SELECT * FROM <name>', where <name> is an unqualified Db2® object name. Retry the BATSQL function.

FMNDC055

SELECT clause must begin with 'SELECT'.

This is an error message issued during processing of the BATSQL function. The specified SELECT clause does not start with 'SELECT'.

Correct the coding of the SELECT clause. Retry the BATSQL function.

FMNDC056

SELECT clause is invalid, SQLCODE=SQLCODE.

This is an error message issued during processing of the BATSQL function. The specified SELECT clause is invalid, Db2® returned SQLCODE=SQLCODE in response to an attempt to prepare the statement.

Look up the SQLCODE in the Db2® Codes manual for the appropriate version of Db2® and use the information provided to correct the SELECT statement. Retry the BATSQL function.

FMNDC057

Column COLNAME is not a column of OBJNAME.

This is an error message issued during processing of the BATSQL function. The specified column name COLNAME does not exist in Db2® object OBJNAME.

Determine the reason why the specified column name is not a column of the named Db2® object. A non-exhaustive list of causes is:

  1. Spelling errors
  2. Upper/lower case issues
  3. References to an incorrect Db2® object name
  4. Referring to a Db2® object name on a different Db2® sub-system to the intended system.

Correct the input statements and retry the BATSQL function.

FMNDC058

The requested function is not supported: XML columns.

This is an error message issued during processing of an INSERT BATSQL function. XML columns were detected in either the target Db2® object, or in the source SELECT statement. The BATSQL function with TYPE=INSERT does not support XML columns.

The function cannot be performed.

None, the requested operation cannot be performed.

FMNDC059

Switching to single-row processing because of multi-row errors.

This is an error message issued during processing of a DELETE or UPDATE BATSQL function. Rowset processing is active, however an SQL error was encountered when attempting a delete/update of a rowset. All rows in the current rowset are unchanged, FM/Db2 marks all rows in the rowset as 'in error'. FM/Db2 moves to the next rowset and attempts to process each row in that rowset individually.

Examine the output object to determine why an SQL error occured. Take appropriate action.

FMNDC060

1 rowset gave SQLCODE sqlcode.

This message is issued during processing of a DELETE or UPDATE BATSQL function when rowset processing is active. An SQL error occured when attempting a rowset delete or update, the failing SQLCODE is sqlcode. All rows in the current rowset are unchanged, FM/Db2 marks all rows in the rowset as 'in error'.

Examine the output object to determine why an SQL error occured. Take appropriate action.

FMNDC062

Invalid SET clause.

This message is issued during processing of an UPDATE BATSQL function. The SET clause is invalid. This message is specific to the following form of a SET clause:

SET (Col1 , ...) = (Val1, ...)

See the SQL Reference for the appropriate version of Db2® for a full description of the SET clause syntax.

This error is usually the result of:

  • A missing parenthesis around either the column, or value list.
  • A missing '=' between the column and value lists.
  • The column list has no columns.
  • The value list has no values.

Examine the SET clause, correct the syntax error(s), retry the function.

FMNDC170

Changes discarded (short). The invalid change to the data format option has been discarded. Enter one of the following values: 1, 2, 3, 4. (long).

The user made an invalid change to the "Data format" value on the Import options panel, and then pressed the PFKey assigned to END (or typed END). The invalid value is discarded and the import options panel is redisplayed.

No action required. Informational message. After making changes to the options, press ENTER to validate the changes before attempting to exit the panel.

FMNDC171

Changes discarded (short). The invalid change to the duplicate key processing option has been discarded. Enter one of the following values: 1, 2. (long).

The user made an invalid change to the "Duplicate key processing" value on the Import options panel, and then pressed the PFKey assigned to END (or typed END). The invalid value is discarded and the import options panel is redisplayed.

No action required. Informational message. After making changes to the options, press ENTER to validate the changes before attempting to exit the panel.

FMNDC172

Changes discarded (short). The invalid change to the maximum duplicates option has been discarded. Enter one of the following values: *, ALL, or a number in the range 0-2147483647 inclusive. (long).

The user made an invalid change to the "Max duplicates" value on the Import options panel, and then pressed the PFKey assigned to END (or typed END). The invalid value is discarded and the import options panel is redisplayed.

No action required. Informational message. After making changes to the options, press ENTER to validate the changes before attempting to exit the panel.

FMNDC174

Changes discarded (short). The invalid change to the auto-commit count option has been discarded. Enter a number in the range 0-2147483647 inclusive. (long).

The user made an invalid change to the "Auto commit count" value on the Import options panel, and then pressed the PFKey assigned to END (or typed END). The invalid value is discarded and the import options panel is re-displayed.

No action required. Informational message. After making changes to the options, press ENTER to validate the changes before attempting to exit the panel.

FMNDC180

Enter a value (short). A value is required. Enter a frequency between 0 and 1 exclusive. As an example 0.1 will sample approximately 10% of rows. (long).

The user selected "random sampling" on the FM/Db2 Editor options panel, but did not enter a value for "sampling frequency". A sampling frequency is required when using random sampling.

Enter a decimal value between 0.0 and 1.0. As an example, enter 0.1 will result in approximately 10% of the rows in the object being sampled. These rows will appear in the FM/Db2 editor session. Higher values will result in more rows being sampled; lower values will result in less rows being sampled.

FMNDC181

Invalid value (short). Valid frequencies are 0.000000001 - 0.999999999 inclusive. Enter a value within these limits. (long).

The user selected "random sampling" on the FM/Db2 Editor options panel, but did not enter a valid value for "sampling frequency". A valid sampling frequency is a decimal number between 0.0 and 1.0; with 9 digits of precision after the decimal point.

Enter a decimal value between 0.0 and 1.0. As an example, enter 0.1 will result in approximately 10% of the rows in the object being sampled. These rows will appear in the FM/Db2 editor session. Higher values will result in more rows being sampled; lower values will result in less rows being sampled.

FMNDC182

Enter a number (short). Enter a number (seed) to start the generation of pseudo-random numbers, or 0 to use a seed derived from the system clock. Valid values are 0-2147483647 inclusive. (long).

The user selected "random sampling" on the FM/Db2 Editor options panel, but did not enter a valid value for "sampling seed". The seed value is used to initiate the pseudo-random number generator.

Enter an integer between 0-2147483647 inclusive. A value of 0 sets the seed to a value based on the current value of the system clock on the computer, accurate to the microsecond, and is therefore a random value for most purposes. Any other value will result in repeatable behaviour, in terms of the rows sampled, for a given Db2® object and the same sampling frequency.

FMNDC183

Changes discarded (short). The invalid change to the Initial skip count has been discarded. The Initial skip count value must be in the range 0-999999999. (long).

The user made an invalid change to the "Initial skip count" value on an Editor options panel, and then pressed the PFKey assigned to END (or typed END). The invalid value is discarded and the editor options panel is redisplayed.

No action required. Informational message. After making changes to the options, press ENTER to validate the changes before attempting to exit the panel.

FMNDC184

Changes discarded (short). The invalid change to the Include count has been discarded. The Include count value must be in the range 1-999999999. (long).

The user made an invalid change to the "Include count" value on an Editor options panel, and then pressed the PFKey assigned to END (or typed END). The invalid value is discarded and the editor options panel is redisplayed.

No action required. Informational message. After making changes to the options, press ENTER to validate the changes before attempting to exit the panel.

FMNDC185

Changes discarded (short). The invalid change to the Skip count has been discarded. The Skip count value must be in the range 0-999999999. (long).

The user made an invalid change to the "Skip count" value on an Editor options panel, and then pressed the PFKey assigned to END (or typed END). The invalid value is discarded and the editor options panel is redisplayed.

No action required. Informational message. After making changes to the options, press ENTER to validate the changes before attempting to exit the panel.

FMNDC186

Changes discarded (short). The invalid change to the Sampling limit has been discarded. The Sampling limit value must be in the range 0-999999999. (long).

The user made an invalid change to the "Sampling limit" value on an Editor options panel, and then pressed the PFKey assigned to END (or typed END). The invalid value is discarded and the editor options panel is redisplayed.

No action required. Informational message. After making changes to the options, press ENTER to validate the changes before attempting to exit the panel.

FMNDC187

Changes discarded (short). The invalid change to the Sampling frequency has been discarded. The Sampling frequency value must be in the range 0.000000001 - 0.999999999. (long).

The user made an invalid change to the "Sampling frequency" value on an Editor options panel, and then pressed the PFKey assigned to END (or typed END). The invalid value is discarded and the editor options panel is redisplayed.

No action required. Informational message. After making changes to the options, press ENTER to validate the changes before attempting to exit the panel.

FMNDC188

Changes discarded (short). The invalid change to the Sampling seed has been discarded. The Sampling seed value must be in the range 0-2147483647. (long).

The user made an invalid change to the "Sampling seed" value on an Editor options panel, and then pressed the PFKey assigned to END (or typed END). The invalid value is discarded and the editor options panel is redisplayed.

No action required. Informational message. After making changes to the options, press ENTER to validate the changes before attempting to exit the panel.

FMNDC189

Changes discarded (short). The invalid change to the Change count before auto commit has been discarded. The Change count before auto commit value must be in the range 0-2147483647. (long).

The user made an invalid change to the "Change count before auto commit" value on an Editor options panel, and then pressed the PFKey assigned to END (or typed END). The invalid value is discarded and the editor options panel is redisplayed.

No action required. Informational message. After making changes to the options, press ENTER to validate the changes before attempting to exit the panel.

FMNDC190

Changes discarded (short). The invalid change to the Prefix Length option has been discarded. (long).

The user made an invalid change to the "Prefix length" value on an Editor options panel, and then pressed the PFKey assigned to END (or typed END). The invalid value is discarded and the editor options panel is redisplayed.

No action required. Informational message. After making changes to the options, press ENTER to validate the changes before attempting to exit the panel.

FMNDC191

Changes discarded (short). The invalid change to the input/display characters has been discarded. The input/display delimiter characters must be non-blank and unique. (long).

The user made an invalid change to the String delimiter and/or Null column indicator input/display characters on an Editor options panel, and then pressed the PFKey assigned to END (or typed END). The invalid value is discarded and the editor options panel is redisplayed.

No action required. Informational message. After making changes to the options, press ENTER to validate the changes before attempting to exit the panel.

FMNDC192

Changes discarded (short). The invalid change to the Edit locking option has been discarded. Enter one of the listed values for the Edit locking option. (long).

The user made an invalid change to the "Edit locking" value on an Editor options panel, and then pressed the PFKey assigned to END (or typed END). The invalid value is discarded and the editor options panel is redisplayed.

No action required. Informational message. After making changes to the options, press ENTER to validate the changes before attempting to exit the panel.

FMNDC193

Changes discarded (short). The invalid change to the "Optimization for" value has been discarded. Enter a number in the range 0-999999 inclusive. Use 0 if no optimization clause is required. (long).

The user made an invalid change to the "Optimization for" value on an Editor options panel, and then pressed the PFKey assigned to END (or typed END). The invalid value is discarded and the editor options panel is redisplayed.

No action required. Informational message. After making changes to the options, press ENTER to validate the changes before attempting to exit the panel.

FMNDC194

Changes discarded (short). The invalid change to the Keep locks option has been discarded. Enter one of the listed values for the Keep locks option. (long).

The user made an invalid change to the "Keep locks" value on an Editor options panel, and then pressed the PFKey assigned to END (or typed END). The invalid value is discarded and the editor options panel is redisplayed.

No action required. Informational message. After making changes to the options, press ENTER to validate the changes before attempting to exit the panel.

FMNDC195

Changes discarded (short). The invalid change to the Scrollable cursor type option has been discarded. Enter one of the listed values for the Scrollable cursor type option. (long).

The user made an invalid change to the "Scrollable cursor type" value on an Editor options panel, and then pressed the PFKey assigned to END (or typed END). The invalid value is discarded and the editor option's panel is redisplayed.

No action required. Informational message. After making changes to the options, press ENTER to validate the changes before attempting to exit the panel.

FMNDC196

Changes discarded (short). The invalid change to the Data sampling type option has been discarded. Enter one of the listed values for the Data sampling type option. (long).

The user made an invalid change to the "Data sampling type" value on an Editor options panel, and then pressed the PFKey assigned to END (or typed END). The invalid value is discarded and the editor options panel is redisplayed.

No action required. Informational message. After making changes to the options, press ENTER to validate the changes before attempting to exit the panel.

FMNDC197

Enter a positive number (short). A positive number is required for this option when clustered sampling is selected. Enter a number in the range 1-999999999 inclusive. (long).

The user selected "clustered sampling" on a File Manager/Db2 Editor options panel, but entered an invalid value for one of the "Include count" field. A positive integer value in the indicated range is required.

Enter a positive integer value in the range 1-999999999 inclusive.

FMNDC198

Invalid value or number (short). A number is required for this option. Valid values are range inclusive. (long).

The user selected "cluster sampling", or "random sampling" on a File Manager/Db2 Editor options panel, but entered an invalid value in one of the other sampling fields. Valid values for the indicated field are shown in the message range.

Enter a value in the range shown in the long message. To access the long message, press the PFKey assigned to HELP (typically PF1), or type HELP on the command line, followed by ENTER.

FMNDC199

Enter a number (short). A number is required for the optimization clause. Valid values are 0-999999 inclusive. Use 0 if no optimization clause is required. (long).

The user cleared the "Optimize for" value on a File Manager/Db2 Editor options panel (and pressed ENTER). A value is required for this field.

Enter a value in the range 0-999999 inclusive. Specifying 0 results in no "OPTIMIZE FOR nn ROWS" clause being added to the SELECT statement used to fetch the data for the current editor session. In some situations specifying a small value (eg 1) may change the access path used by Db2® when retrieving the data, thereby improving the response time. See the Db2® SQL Reference manual for a more complete explanation.

FMNDC200

Invalid label range (short). The label range entered is invalid. Press help for more information. (long)

The user entered the EXPORT editor primary command, with labels. The labels specified are invalid. The export command cannot be performed.

Check the labels specified carefully. One common cause of this error is specifying a label that does not exist. You can press the PFKey assigned to HELP (PF1 by default) to display additional help for this error.

FMNDC201

NX|X|EX invalid (short). The NX|X|EX parameters cannot be specified when in SNGL mode. Press help for more information. (long).

The user entered the EXPORT editor primary command, in SNGL mode, with the NX, X or EX option. The excluded or not-excluded row options are not applicable in SNGL mode. The export command cannot be performed.

Change the display mode to TABL and re-issue the command. Alternatively, remove the excluded or not-excluded option and re-issue the command. You can press the PFKey assigned to HELP (PF1 by default) to display additional help for this error.

FMNDC202

Not in zoom mode (short). The export primary command is invalid in Zoom mode. (long).

The user entered the EXPORT editor primary command, in ZOOM mode, which is not supported. The export command cannot be performed.

Return to either TABL or SNGL display modes and re-issue the command. You can press the PFKey assigned to HELP (PF1 by default) to display additional help for this error.

FMNDC203

No labels (short). Labels cannot be specified when in SNGL mode. Press help for more information. (long).

The user entered the EXPORT editor primary command, in SNGL mode, with a label range. Labels may only be specified for the EXPORT command in TABL display mode. The export command cannot be performed.

Return to TABL display mode and re-issue the command. You can press the PFKey assigned to HELP (PF1 by default) to display additional help for this error.

FMNDC204

ALL|NX|X|EX missing (short). Labels cannot be specified unless ALL|NX|X|EX is also specified. Press help for more information. (long).

The user entered the EXPORT editor primary command, with a label range, but without either the ALL or NX|X|EX parameters. When you specify a label range one of the ALL, NX|X|EX options is required. The export command cannot be performed.

Press the PFKey assigned to HELP (PF1 by default) and review the following topics: "Syntax diagram". ALL|NX|X|EX parameter Modify the command to meet the requirements of the syntax diagram, and the intended usage of the EXPORT command, re-issue the command.

FMNDC206

Export failed (short). The export operation failed. (long).

The user issued the EXPORT editor primary command in a File Manager/Db2 editor session. The command failed.

Check the output data set for allocation/space and related errors.

FMNDC207

LRECL mismatch (short). The (RECFM=F) export data set has LRECL=LRECL 1. The required LRECL is LRECL 2. Specify a different export data set. (long).

The user attempted an export operation and specified an LRECL=F data set that is incompatible with the exported data. The export operation cannot be performed.

Use an export data set with LRECL=LRECL 2.

FMNDC208

Inconsistent selection (short). The template usage option should only be set to None when the export data format is set to CSV. Select another template usage option. (long).

This message is issued by the FM/Db2 export function, on the 'To' panel. The user entered '5' (CSV) for the "Template usage" option. However, the export data format option set on the first export options panel is not CSV. The export cannot proceed.

The choice for export data format, on the first export options panel, places restrictions on the template usage option that can be specified on the export 'To' panel. The following list shows which 'template usage' options can be specified for each export data format:

Export data format          Template usage option
FM/Db2 (SQLDA) format   All except 5 (CSV)
Db2 UNLOAD format        All except 5 (CSV)
DSNTIAUL format           All except 5 (CSV)
User defined                All except 5 (CSV)
Delimited variables (CSV)    5 (CSV) only.

FMNDC209

LRECL mismatch (short). The (RECFM=V) export data set has LRECL=LRECL 1. The required LRECL is at least LRECL 2. Specify a different export data set.

The user attempted an export operation and specified an LRECL=F data set that is incompatible with the exported data. The export operation cannot be performed.

Use an export data set with LRECL = LRECL 2.

FMNDC220

NX|X|EX invalid (short). The NX|X|EX parameters cannot be specified when in browse mode. Press help for more information. (long).

The user entered the EXPORT editor primary command in a browse session, the EXPORT command included a reference to excluded, or not-excluded rows. This is not supported in a File Manager/Db2 browse session.

Modify the EXPORT command to remove any reference to excluded, or not-excluded rows, retry the operation. If the intended usage requires the use of excluded or not-excluded rows as part of the EXPORT command, repeat the process using a File Manager/Db2 view session.

FMNDC221

No labels (short). Labels cannot be specified when in browse mode. Press help for more information. (long).

The user entered the EXPORT editor primary command in a browse session, the EXPORT command included label references. There is no prefix area in a File Manager/Db2 browse session, so labels cannot be entered, nor can they be referred to.

Modify the EXPORT command to remove any reference to labels, retry the operation.

FMNDC230

Warning - fixed RECFM (short). The output data set has a fixed record format, which is not recommended when using CSV format. Specify a data set with RECFM=VB or RECFM=V. (long).

This message is issued by the FM/Db2 Export utility, when CSV format is selected. The attributes of the output data set are inconsistent with CSV format, which produces variable length output records.

In general RECFM=F and RECFM=FB should not be used with CSV format. You can specify the name of a new data set on the export 'To' panel and FM/Db2 will calculate the correct LRECL for you.

FMNDC500

Executed OK (short). The ALTER|COMMENT|CREATE|DROP| GRANT|LABEL|REVOKE statement executed successfully. Db2® returned an SQLCODE of SQLCODE. (long).

This message is issued by the FM/Db2 Object List and Object Privileges utilities. An SQL statement was executed successfully.

No action required. Informational message.

FMNDC510

No rows returned (short). No rows were fetched, SQL code = +100. (long).

This message is issued by the FM/Db2 Object List, Object Privileges and Explain utilities functions. A SELECT statement was executed, but returned no rows (SQLCODE+100).

No action required. Informational message.

FMNDC520

No allocation data (short). The PQTY/SQTY values in SYSIBM.SYSTABLEPART indicate that RUNSTATS has not been run. The primary and/or secondary space allocation data for the table space is unavailable. (long).

This message is issued by the Alter table space and Alter index panels, accessed from the FM/Db2 Object list utility. FM/Db2 accessed the Db2® catalog to determine the current space allocation values for the table space or index, however this information is not available because the RUNSTATS utility has not been executed. You can resolve this problem by executing the RUNSTATS utility against the appropriate table space or index, and then repeating the ALTER operation.

No action required. Informational message.

FMNDC521

No allocation data (short). The PQTY/SQTY values in SYSIBM.SYSINDEXPART indicate that RUNSTATS has not been run. The primary and secondary space allocation data for the index space is unavailable. (long).

This message is issued by the Alter index panel, accessed from the FM/Db2 Object list utility. FM/Db2 accessed the Db2® catalog to determine the current space allocation values for the index. However, this information is not available because the RUNSTATS utility has not been executed. You can resolve this problem by executing the RUNSTATS utility against the appropriate index, and then repeating the ALTER operation.

No action required. Informational message.

FMNDC580

Must be blank (short). Specify one value or the other, but not both. (long).

This message is issued by the FM/Db2 Privileges function. The user selected both options when the two options are mutually exclusive.

Select one option, or the other, but not both. Consult the SQL Reference manual for the relevant syntax diagram for the command.

FMNDC581

Cannot drop directly (short). An auxiliary table cannot be dropped directly. To drop an auxiliary table drop the table that uses the auxiliary table. (long).

This message is issued by the FM/Db2 "Db2® Object functions" utility. The user specified the combination of 'D' (Drop) and an object type of 12 (Auxiliary table'. This combination is not supported.

You cannot directly drop an auxiliary table. Auxiliary tables should be dropped by a DROP of the table of which the auxiliary table is a part. See the Db2® SQL Reference for a full explanation of the use of auxiliary tables.

FMNDC583

Reserved (short). Sequence number 1 is reserved for the SEL field. Specify a larger value. (long).

This message is issued by the "Column Selection/Edit"panel, when displayed from the FM/Db2 Object List, Object Privileges and Explain functions (Collectively ISQ functions). The object displays for ISQ functions use a modified version of the FM/Db2 editor to display the data, and allow the same template editor functions as a normal FM/Db2 editor session; with some restrictions. While you can specify a sequence number in the 'Seq' field, a value of 1 is reserved for the 'Sel' field, which appears on most ISQ panels.

Specify the required ordering starting at '2', instead of '1'.

FMNDC584

Must be blank (short). Specify the ALL parameter, or one or more values, but not both. (long).

This message is issued on various Revoke Privilege panels displayed by the FM/Db2 Privileges function. When REVOKING a privilege with SYSADM authority you may REVOKE the privilege from ALL users, or list 1-3 individual Db2® authids. These options are mutually exclusive, you cannot select ALL and also enter an individual Db2® authid.

Select ALL if the privilege is to be REVOKEd from all Db2® authids. Alternatively enter one or more individual Db2® authids.

FMNDC585

Must be selected (short). The PUBLIC selection field must be selected when the AT ALL LOCATIONS selection field is selected. (long).

This message is issued by the Grant table and Grant column privileges' panels. The user selected the 'AT ALL LOCATIONS' field, but not the 'PUBLIC' field. Selecting the former requires that the latter also be selected

Select both the 'PUBLIC' and 'AT ALL LOCATIONS' fields.

FMNDC586

Not with ROLE (short). The ROLE and PUBLIC options cannot both be selected. PUBLIC is a special Db2® authid, not a valid role name. (long).

This message is issued by the Db2® Privileges utility when the user selects both the 'ROLE' and 'PUBLIC' fields. The utility does not support the simultaneous use of both the PUBLIC and ROLE options.

To GRANT/REVOKE the privileges to PUBLIC, clear the ROLE field and process the request. Similarly, to GRANT/REVOKE the privileges to a ROLE, clear the PUBLIC field and process the request.

FMNDC587

Not with ROLE (short). The ROLE and ALL options cannot both be selected. ALL can only be specified with Db2® authids. (long).

This message is issued by the Db2® Privileges utility when the user selects both the 'ROLE' and 'ALL' fields. The utility does not support the simultaneous use of both the PUBLIC and ALL options.

To REVOKE the privileges from ALL Db2® authids that possess the privilege, clear the ROLE field and process the request. Similarly, to REVOKE the privileges from a ROLE, clear the ALL field and process the request.

FMNDC588

Not AT ALL LOCATIONS (short). The Privilege type privilege cannot be granted to PUBLIC AT ALL LOCATIONS. (long).

This message is issued by the Db2® Privileges utility, when granting table or column privileges. The "AT ALL LOCATIONS" may not be used.

Deselect the "AT ALL LOCATIONS" option and process the request.

FMNDC651

Invalid data type (short) ROWID, CLOB, BLOB and DBCLOB columns cannot be specified in a global temporary table definition. (long).

This message is issued by the FM/Db2 Object functions utility, when attempting to create a global temporary table (GTT). One or more of the columns defined for the GTT has a prohibited data type (ROWID, CLOB, BLOB or DBCLOB). The GTT cannot be created.

Correct the definition for any columns defined as ROWID, CLOB, BLOB or DBCLOB, retry the operation.

FMNDD000

Command list error (short). An error was encountered processing the list of valid commands for panel panel_name.

This message is issued by the FM/Db2 Interactive SQL (ISQ) processor (used by the following options: 3.4; 3.5; 4.5). The line commands that may be entered against a list of objects are defined using a customization string. An error occurred during the processing of this string for panel panel_name.

This is an internal error. Contact IBM® Support.

FMNDD001

Customization error (short). An error was encountered processing the template customization string for panel panel_name. (long).

This message is issued by the FM/Db2 Interactive SQL (ISQ) processor (used by the following options: 3.4; 3.5; 4.5). Object lists are displayed using the FM/Db2 editor, the template for the object list is modified prior to display. The template customization is defined using a customization string. An error occurred during the processing of this string for panel panel_name.

This is an internal error. Contact IBM® Support.

FMNDD002

No line commands (short). There are no line commands for this panel. (long).

This message is issued by the FM/Db2 Interactive SQL (ISQ) processor (used by the following options: 3.4; 3.5; 4.5). In most cases you may enter one or more line commands against each row shown in the object list. In some few cases no line commands are available, in which case this message is issued.

No action required. Informational message.

FMNDD003

VDEFINE error, RC=Return code short). A serious ISPF error has been encountered. VDEFINE RC=Return code. (long)

FM/Db2 attempted to use the ISPF VDEFINE service, the call failed with RC = Return code. In most cases the current function will terminate.

The causes of this error are:

  • Problems with the ISPF environment that have caused the ISPF service call to fail. Contact your Systems Programmer for assistance.
  • An internal error. Contact IBM® Support.

Points for the Systems Programmer to consider include:

  • ISPF libraries allocated incorrectly or incompletely.
  • Full ISPF profile data sets.
  • Out of memory, or short on memory, conditions. Are other ISPF applications running? Are multiple ISPF logical sessions active?

FMNDD004

ISPF error, RC=Return code (short). A serious ISPF error has been encountered in FMN2IPSU. ISPF SELECT SERVICE RC=Return code (long).

This message is issued by the FM/Db2 Interactive SQL (ISQ) processor used by the following options: 3.4; 3.5; 4.5). A serious error was encountered in response to an ISPF SELECT service call (return code = Return code) In most cases the function will terminate.

The usual causes of this error are:

  • Problems with the ISPF environment that have caused the ISPF service call to fail. Contact your Systems Programmer for assistance.
  • An internal error. Contact IBM® Support.

Points for the System Programmer to consider include:

  • ISPF libraries allocated incorrectly or incompletely.
  • Full ISPF profile data sets.
  • Out of memory, or short on memory, conditions. Are other ISPF applications running? Are multiple ISPF logical sessions active?

FMNDD005

:ISPF error, RC=Return code short). A serious ISPF error has been encountered in FMN2IPSU. ISPF CONTROL SERVICE RC=Return code long).

This message is issued by the FM/Db2 Interactive SQL (ISQ) processor (used by the following options: 3.4; 3.5; 4.5). A serious error was encountered in response to an ISPF CONTROL service call (return code = Return code). In most cases the function will terminate.

The usual causes of this error are:

  • Problems with the ISPF environment that have caused the ISPF service call to fail. Contact your Systems Programmer for assistance.
  • An internal error. Contact IBM® Support.

Points for the Systems Programmer to consider include:

  • ISPF libraries allocated incorrectly or incompletely.
  • Full ISPF profile data sets.
  • Out of memory, or short on memory, conditions. Are other ISPF applications running? Are multiple ISPF logical sessions active?

FMNDD006

VDELETE error, RC=Return code (short). A serious ISPF error has been encountered. VDELETE RC=Return code(long).

This message is issued by the FM/Db2 Interactive SQL (ISQ) processor (used by the following options: 3.4; 3.5; 4.5). A serious error was encountered in response to an ISPF DELETE service call (return code = Return code). In most cases the function will terminate.

The usual causes of this error are:

  • Problems with the ISPF environment that have caused the ISPF service call to fail. Contact your Systems Programmer for assistance.
  • An internal error. Contact IBM® Support.

Points for the Systems Programmer to consider include:

  • ISPF libraries allocated incorrectly or incompletely.
  • Full ISPF profile data sets.
  • Out of memory, or short on memory, conditions. Are other ISPF applications running? Are multiple ISPF logical sessions active?

FMNDD007

No dynamic area (short). A serious error has been encountered. Panel Panel name oes not contain a dynamic area and therefore cannot be used to display ISQ editor output. (long).

This message is issued by the FM/Db2 Interactive SQL (ISQ) processor (used by the following options: 3.4; 3.5; 4.5). A serious error was encountered attempting to display an ISPF panel.

This is an internal error. Contact IBM® Support.

FMNDD008

Command not available (short). The SQL command is not supported under CICS®. (long).

This message is issued when FM/Db2 is running under CICS®, and the user issues the SQL command. The SQL command is not available when running under CICS®.

No action required. Informational message.

FMNDD009

VREP error, RC=RC (short). A serious ISPF error has been encountered. VREPLACE RC=RC. (long).

This message is issued by the Basic SQL prototyper. In indicates that a serious ISPF error was encountered.

The usual causes of this error are:
  • Problems with the ISPF environment that have caused the ISPF service call to fail. Contact your Systems Programmer for assistance.
  • An internal error. Contact IBM® Support.
Points for the Systems Programmer to consider include:
  • ISPF libraries allocated incorrectly or incompletely.
  • Full ISPF profile data sets.
  • Out of memory, or short on memory, conditions. Are other ISPF applications running? Are multiple ISPF logical sessions active?

FMNDD010

Invalid command Command (short). "Command" is not a valid File Manager Db2® command. List of valid commands. (long).

This message is issued by the FM/Db2 Interactive SQL (ISQ) processor (used by the following options: 3.4; 3.5; 4.5). A command (for example XXXX) was issued on the TSO command line. However, this command is not recognized by the ISQ processor and cannot be run.

No action required. Informational message.

FMNDD011

Too many parms (short). "Command"> is followed by one or more parameters. It is only valid without parameters. PARMS=Parameters. (long).

This message is issued by the FM/Db2 Interactive SQL (ISQ) processor (used by the following options: 3.4; 3.5; 4.5). A command Command, with parameters, was entered on the TSO command line. Command does not require parameters.

Remove the extraneous parameters, re-issue the command.

FMNDD012

No SQL to display (short). There is no SQL statement to display. (long).

The user entered the SQL command; however there is no current SQL statement to display.

No action required. Informational message.

FMNDD018

Object not found (short). No Db2® object at location Location matches the combination of object details entered at Db2® system SSID. Press Help for more information. (long).

The user entered a Db2® object name, including location, owner, and name. This object does not exist. You can press PF1 to see additional help for this error.

Press PF1 to see a more detailed explanation of the error. The usual reasons for this error include:

  • The nominated object does not exist. Is it spelled correctly?
  • When the object name includes lower case letters you must ensure that automatic translation of object names is turned off. See the FM/Db2 systems options.
  • When the automatic translation of object names is turned off, you must ensure that the object name entered matches the case of the actual object name. For example, DSN81010.EMP matches DSN81010.EMP, but dsn81010.EMP does not.

FMNDD020

Invalid selection (short). The value entered is invalid. Type '?' in the field to display a list of valid values. (long).

This message is issued by the FM/Db2 Interactive SQL (ISQ) processor (used by the following options: 3.4; 3.5; 4.5). The user entered a line command against a row. However, the line command is not valid for that type of object.

Check for obvious mistakes such as typos. Type '?' in the field and press Enter to show the list of valid commands for the object.

FMNDD022

No SQL to display (short). There is no SQL statement to display. (long).

The user entered the SQL command; however there is no current SQL statement to display.

No action required. Informational message.

FMNDD028

Requires Db2® V9 (short). This command can only be issued when connected to a Db2® version 9 (or later) system. (long).

This message is issued by the FM/Db2 Interactive SQL (ISQ) processor (used by the following options: 3.4; 3.5; 4.5). When connected to a Db2® version 8 system, the user entered a line command against a row; however the line command is only valid when connected to a Db2® version 9 (or later) system. The command cannot be processed.

No action required. Informational message.

FMNDD029

Must be <= max value (short). The min value entered must be less than or equal to, the max value entered. (long).

The user entered a value in a "minimum" field on the FM/Db2 Object List Options (2 of 2) panel. The value entered is greater than the corresponding maximum value, which is invalid.

Check the minimum and maximum values for the appropriate column type. The minimum value sets the minimum display width for that column type; the maximum value set the maximum display width for that column type. The minimum display width cannot exceed the maximum.

FMNDD501

SQLCOST = Cst>.

This message is issued when a SQL statement is about to be executed, and indicates the comparative cost Cost of executing the current statement. The cost values are those returned by Db2® when the SQL statement to be executed is prepared. See the SQL Reference manual for the appropriate version of Db2® for a more detailed explanation.

No action required. Informational message.

FMNDD502

Invalid at remote server (short). "Line ommand" is only a valid command when entered against an object at the local server. For example, when the location field is blank. (long).

The user entered a line command against an object displayed by the FM/Db2 Interactive SQL (ISQ) Processor (Options 3.4, 3.5 and 4.5 use the ISQ processor). Some line commands are only valid when FM/Db2 is connected to the local Db2® server, an example is privilege related commands such as GRANT and REVOKE. The command cannot be executed.

Connect directly to the remote server and reissue the command.

FMNDD503

Data refreshed

This message is issued by the FM/Db2 Interactive SQL (ISQ) processor (used by the following options: 3.4; 3.5; 4.5). The data for the currently displayed object list has been refreshed. This can occur when, for example, a line command issued against an entry on the current panel was used to change the entry. One example of this is deleting the object.

No action required. Informational message.

FMNDD504

Invalid command (short). "Line command" is not a valid command. Valid commands are D(n), I(n), R(n), and S. (long).

This message is issued by the FM/Db2 Object functions utility. When a list of, for example, columns is displayed, the user can issue various commands to modify the entries in the list. The command line command entered is invalid.

No action required. Informational message.

FMNDD505

Invalid command (short). "Line command" is not a valid command. Valid commands are D(n), I(n, and R(n). (long).

This message is issued by the FM/Db2 Object functions utility. When a list of, for example, columns is displayed, the user can issue various commands to modify the entries in the list. The command line command entered is invalid.

No action required. Informational message.

FMNDD506

Invalid selection (short). Use S to select the column. (long).

This message is issued by the FM/Db2 Object functions utility. An invalid character was entered against an entry in a list of columns.

Use 'S' to select the column.

FMNDD507

Waiting for Db2® prepare …

This message is issued by FM/Db2 functions that use the FM/Db2 editor to display the result table for a SELECT statement. The FM/Db2 editor is operating in "Large" mode, meaning that a Db2® scrollable cursor is in use. The two operating modes for the FM/Db2 editor are described in detail under Specifying the editor session mode: "normal mode" or "large mode". Briefly, when a scrollable cursor is used, there can be a delay while Db2® prepares and opens the SQL statement used to access the data. See also message FMNDD508.

No action required. Informational message.

FMNDD508

Waiting for Db2® open ...

This message is issued by those FM/Db2 functions that use the FM/Db2 editor to display the result table for a SELECT statement. The FM/Db2 editor is operating in "Large" mode, meaning that a Db2® scrollable cursor is in use. The two operating modes for the FM/Db2 editor are described under Specifying the editor session mode: "normal mode" or "large mode". Briefly, when a scrollable cursor is used, there can be a delay while Db2® prepares and opens the SQL statement used to access the data. See also message FMNDD507.

No action required. Informational message.

FMNDD510

Press enter to display the SQL for the view. You can modify/execute the SQL by selecting the "Execute SQL from data set" option.

This message is issued when the user enters the VS (show SQL used to create a view) command against a view in an object list display. The Edit/Execute SQL (Data Set) function is used to display the resulting SQL. When the user presses END or CANCEL from the SQL display, the object list is redisplayed.

Press Enter to see the SQL used to create the view.

FMNDD511

Enter the name of a database and table space defined with at least 8K pages. The Db2® Version 8 DSN_FUNCTION_TABLE requires a larger page size than previous Db2® versions.

This message is issued when the user attempts to create a function table (DSN_FUNCTION_TABLE) on the Explain Utilities panel. This table requires a table space with a page size of 8K or greater, therefore both a database and table space name are required (The default database/table space will have a page size of 4K, which is inadequate).

Enter the name of a database and table space that have a page size of at least 8K. You may need to contact your Db2® Database/System's Administrator for authority/information on how to do this.

FMNDD541

No RI relationships (short). The related edit (REDIT) command was issued. There are no referential integrity relationships defined on the table. (long).

The user entered the REDIT editor primary command. When the object being edited is part of an referential integrity relationship this command displays the other Db2® objects in the relationship. No RI relationships exist that include the object being edited.

No action required. Informational message.

FMNDE495

No Db2® TABLE matches the value entered. It is possible a Db2® object (eg view) that matches the name entered exists - however the selected Db2® utility supports Db2® tables ONLY.

This message is issued when a Db2® object name - other than a table - is entered when preparing a Db2® LOAD or UNLOAD utility job. The Db2® LOAD and UNLOAD utilities support only table objects - not views, aliases, synonyms and so on.

Ensure that the Db2® object name specified is a Db2® table.

FMNDJ999

File Manager Db2 component problem - message Message numbernot found in table.

This message is issued when an attempt is made to issue message Message number, but the message number could not be found. It is a "catch all" message.

If this message occurs during normal processing the likely cause is a logic error. Contact IBM® Support for assistance.