| Reason code 0 | FLG_OK |
Explanation: Completed successfully.
| Reason code 1 | FLG_WRN |
Explanation: Place holder; indicates the beginning of the numeric range for warnings.
| Reason code 201 | FLG_WRN_DISCONNECTED |
Explanation: The database has been disconnected.
| Reason code 202 | FLG_WRN_DBM_ALREADY_ STARTED |
Explanation: The database manager was already started before the information catalog initialization.
| Reason code 203 | FLG_WRN_DB_RESTART |
Explanation: The database manager needed to be restarted before the information catalog initialization.
| Reason code 204 | FLG_WRN_DB_ACTIVE |
Explanation: The specified database manager was already active before the information catalog initialization.
| Reason code 1001 | FLG_WRN_INST_NOTFOUND |
Explanation: Unable to find the object instance (also used by FLGListOrphans, FLGFoundIn, FLGListAssociates, and FLGExport).
| Reason code 1002 | FLG_WRN_CONTAINER_ NOTFOUND |
Explanation: Unable to find a container for the specified object instance.
| Reason code 1003 | FLG_WRN_CONTAINEE_ NOTFOUND |
Explanation: Unable to find any objects contained by the specified object instance.
| Reason code 1004 | FLG_WRN_CONTACT_ NOTFOUND |
Explanation: Unable to find a contact for the specified object instance.
| Reason code 1005 | FLG_WRN_PROGRAM_ NOTFOUND |
Explanation: Unable to find a program associated with this object type.
| Reason code 1006 | FLG_WRN_ANCHOR_ NOTFOUND |
Explanation: Unable to find any anchors (subjects) defined in the information catalog.
| Reason code 1007 | FLG_WRN_PROGRAM_ CHANGED |
Explanation: One or more associated program instances were changed when the object type was deleted.
| Reason code 1008 | FLG_WRN_NO_INPARM_ICON_ FILE |
Explanation: FLGGetReg API call did not specify a pointer to receive the name of the retrieved icon file. The Information Catalog Manager did not return an icon.
| Reason code 1009 | FLG_WRN_NO_ICON |
Explanation: No icon associated with the object type.
| Reason code 1010 | FLG_WRN_ID_LIMIT_REACHED |
Explanation: Reached the maximum number of object types limit.
| Reason code 1011 | FLG_WRN_OBJECT_NOT_ CHANGED |
Explanation: Reserved
| Reason code 1012 | FLG_WRN_EXCEED_MAX_ ANCHORNUM |
Explanation: Unable to return all anchors (subjects) defined in the information catalog.
Possible Extended Codes: Actual number of anchors
| Reason code 1013 | FLG_WRN_ICON_REPLACED |
Explanation: An icon file already existed in the specified ICOPATH. The icon file was replaced.
| Reason code 1014 | FLG_WRN_PROPDUP |
Explanation: The property to be appended already exists.
| Reason code 1015 | FLG_WRN_EXCEED_MAX_ ORPHANNUM |
Explanation: Exceeded the maximum number of orphans.
Possible Extended Codes: Actual number of orphans
| Reason code 1016 | FLG_WRN_DB_ICON_REPLACED |
Explanation: The object type icon has been replaced in the information catalog.
| Reason code 1017 | FLG_WRN_LINKOBJ_ NOTFOUND |
Explanation: Unable to find a linked object for the specified object instance.
| Reason code 1018 | FLG_WRN_ATTACHOBJ_ NOTFOUND |
Explanation: Unable to find attachment objects for the specified object instance.
| Reason code 1019 | FLG_WRN_MISSING_PROPS_ IN_IOSTRUCT |
Explanation: The input structure contains fewer properties than that defined for the object type. All missing properties are optional. Object instance is created or updated.
| Reason code 2002 | FLG_WRN_NO_DISKCNTL_ TAG_PRESENTED |
Explanation: DISKCNTL is not the first tag in the input tag language file on a removable device. Importing continues, but only the tag language file on the current diskette is processed.
| Reason code 2003 | FLG_WRN_NEED_NEW_ TAGFILE_DISKETTE |
Explanation: Insert the next diskette to continue importing the tag language file.
| Reason code 2004 | FLG_WRN_ICONFILE_OPENERR |
Explanation: Reserved
| Reason code 2005 | FLG_WRN_NOTHING_TO_ IMPORT |
Explanation: Unable to find any data to import in the tag language file or in the part of the tag language file after the last checkpoint. The file or part of the file may be empty or contain only COMMENT or DISKCNTL tags.
| Reason code 2006 | FLG_WRN_ICONFILE_ RETRIEVE_ERROR |
Explanation: API FLGCreateReg or FLGUpdateReg encountered an error while retrieving (opening, reading, or closing) the icon file specified in parameter pszIconFileID. The reason code returned in the extended code indicates the error. FLGCreateReg and FLGUpdateReg have completed all other registration processing successfully.
Possible Extended Codes: Reason code
| Reason code 2007 | FLG_WRN_P_HANDLES_ CLEARED |
Explanation: FLGImport cleared the HANDLES property value for a program instance, because this value refers to an object type that does not exist in the target information catalog.
| Reason code 2501 | FLG_WRN_CFLAG_IGNORED |
Explanation: CONTAINEE-IND value for the exported object was ignored because the object does not belong to the Grouping category.
| Reason code 2502 | FLG_WRN_TFLAG_IGNORED |
Explanation: CONTACT-IND value for the exported object was ignored because the object does not belong to the Grouping or Elemental category.
| Reason code 2503 | FLG_WRN_NO_ICOPATH |
Explanation: No icon path was specified; no icons were exported.
| Reason code 2504 | FLG_WRN_GETREG_WARNING |
Explanation: Export encountered a warning from FLGGetReg. The extended code contains the reason code returned by FLGGetReg.
Possible Extended Codes: Reason code
| Reason code 2505 | FLG_WRN_GETINST_WARNING |
Explanation: Export encountered a warning from FLGGetInst. The extended code contains the reason code returned by FLGGetInst.
Possible Extended Codes: Reason code
| Reason code 2506 | FLG_WRN_LISTCONTACTS_ WARNING |
Explanation: Export encountered a warning from FLGListContacts. The extended code contains the reason code returned by FLGListContacts.
Possible Extended Codes: Reason code
| Reason code 2507 | FLG_WRN_NAVIGATE_ WARNING |
Explanation: Export encountered a warning from FLGNavigate. The extended code contains the reason code returned by FLGNavigate.
Possible Extended Codes: Reason code
| Reason code 2508 | FLG_WRN_AFLAG_IGNORED |
Explanation: ATTACHMENT-IND value for the exported object was ignored because the object is in the Attachment category and cannot have associated attachment objects.
| Reason code 2509 | FLG_WRN_LFLAG_IGNORED |
Explanation: LINK-IND value for the exported object was ignored because the object does not belong to the Grouping or Elemental categories.
| Reason code 2601 | FLG_WRN_NO_HISTORY |
Explanation: There is no history entry in the history buffer.
| Reason code 2602 | FLG_WRN_NO_TYPE_RELATE_ TO_PROGRAM |
Explanation: There is no object type related to the program instance.
| Reason code 7500 | FLG_WRN_VIEW_NOT_ SUPPORTED |
Explanation: View "T" is specified in the Tool profile, but this function is not supported by the Information Catalog Manager.
| Reason code 7501 | FLG_WRN_LEVEL_NOT_ SUPPORTED |
Explanation: Level "T" is specified in the Tool profile, but this function is not supported by the Information Catalog Manager.
| Reason code 7505 | FLG_WRN_NO_BEGIN_ DEFINITION_SECTION |
Explanation: The BEGIN DEFINITION section is missing from the tag language file.
| Reason code 7510 | FLG_WRN_VALUE_TRUNCATED |
Explanation: A value is truncated because it exceeded the maximum allowable length.
| Reason code 7515 | FLG_WRN_INV_TIMESTAMP_ FORMAT |
Explanation: A date or time value does not follow the correct format.
Format for date values: YYYY-MM-DD.
Format for time values: HH.MM.SS
Format for refresh date values: YYYY-MM-DD-HH.MM.SS.
| Reason code 30000 | FLG_ERR |
Explanation: Place holder; indicates the beginning of the numeric range for errors.
| Reason code 30001 | FLG_ERR_INVALID_NUM_STR |
Explanation: The numeric string passed to the information catalog as input is invalid.
| Reason code 30002 | FLG_ERR_INVALID_NUMBER |
Explanation: The integer value passed to the information catalog as input is too large.
| Reason code 30003 | FLG_ERR_BUFF_TOO_SMALL |
Explanation: Information Catalog Manager internal error.
| Reason code 30004 | FLG_ERR_MSGFILE_NOTFOUND |
Explanation: Unable to locate the Information Catalog Manager message file (DGxyMSG.MSG or DGxySTR.MSG, where x is the platform identifier and y is the national language version identifier).
This file must be in the Information Catalog Manager working directory.
| Reason code 30005 | FLG_ERR_MSGID_NOTFOUND |
Explanation: The message identifier could not be located in the message file.
| Reason code 30006 | FLG_ERR_CANT_ACCESS_ MSGFILE |
Explanation: Unable to open the Information Catalog Manager message file.
| Reason code 30007 | FLG_ERR_INVALID_MSGFILE_ FORMAT |
Explanation: The message file (DGxyMSG.MSG or DGxySTR.MSG, where x is the platform identifier and y is the national language version identifier) is corrupted or invalid.
Reinstall the affected file.
| Reason code 30008 | FLG_ERR_MSGFILE_ERROR |
Explanation: Information Catalog Manager internal error.
| Reason code 30009 | FLG_ERR_TRACE_FAIL |
Explanation: An error occurred in the Information Catalog Manager trace function. The trace file may be corrupted or incomplete.
| Reason code 30010 | FLG_ERR_INTERNAL_ERROR |
Explanation: Information Catalog Manager encountered an internal error.
Check the reason code returned in the extended code and try to remedy the problem; if this is unsuccessful, call IBM Software Support.
Possible Extended Codes: None; Reason code
| Reason code 30011 | FLG_ERR_RESDLL_NOT_ LOADED |
Explanation: Language DLL file is not found.
| Reason code 30012 | FLG_ERR_DGPATH_NOT_ FOUND |
Explanation: Environment path (DG2PATH) was not set in the CONFIG.SYS file.
Environment path (DGWPATH) was not set in either the system registry or the AUTOEXEC.BAT file.
| Reason code 30013 | FLG_ERR_CP_LOAD_FAILED |
Explanation: The primary and secondary code pages specified in your CONFIG.SYS file are not supported by the Information Catalog Manager.
| Reason code 30014 | FLG_ERR_DBSEM_ERROR |
Explanation: Information Catalog Manager internal error (can't get database semaphore).
| Reason code 30015 | FLG_ERR_STRINGFILE_ERROR |
Explanation: Reserved
| Reason code 30016 | FLG_ERR_MSG_TOO_LONG |
Explanation: Information Catalog Manager internal error.
| Reason code 30017 | FLG_ERR_DG_DB_INUSE |
Explanation: User tried to log on to the same information catalog twice.
| Reason code 30018 | FLG_ERR_DGLANG_PATH_NOT_ FOUND |
Explanation: Information Catalog Manager language-dependent directory path cannot be found.
| Reason code 30019 | FLG_ERR_INV_DG_CP |
Explanation: The code pages specified on the workstation are not supported by the Information Catalog Manager.
| Reason code 30020 | FLG_ERR_INV_DB_CP |
Explanation: The code pages specified on the workstation are not supported by the database.
| Reason code 30021 | FLG_ERR_VWSPATH_NOT_ FOUND |
Explanation: Environment path (VWSPATH) was not set in either the system registry or the AUTOEXEC.BAT file.
| Reason code 31000 | FLG_ERR_DBERROR |
Explanation: An unexpected database error has occurred. See the database documentation for an explanation of the SQLCODE.
Possible Extended Codes: Database SQLCODE
| Reason code 31001 | FLG_ERR_DBDISC_FAIL |
Explanation: Error occurred while disconnecting from the database.
| Reason code 31002 | FLG_ERR_NODBACCESS |
Explanation: You cannot access the specified database.
Ask the administrator or database administrator for the database authorization you need.
| Reason code 31003 | FLG_ERR_ID_LIMIT_EXCEEDED |
Explanation: The system-generated ID (object type ID or instance ID) exceeds the maximum number of IDs allowed in the database.
This limit is 99999999 for object instance IDs, and 999999 for object type IDs.
| Reason code 31004 | FLG_ERR_PROP_LIMIT_ EXCEEDED |
Explanation: Exceeded the maximum number of properties (255) allowed for an object type.
| Reason code 31005 | FLG_ERR_LONG_VARCHAR_ LIMIT_EXCEEDED |
Explanation: Exceeded the maximum number of LONG VARCHAR properties (14) allowed for an object type.
Possible Extended Codes: None; Sequence number of property
| Reason code 31006 | FLG_ERR_PTNAME_EXCEEDS_ ENVSIZE |
Explanation: The physical type name for the object type exceeds the maximum length allowed. This maximum length depends on the underlying database you are using.
| Reason code 31007 | FLG_ERR_DBNAME_NOT_ FOUND |
Explanation: Unable to find the database. If the database is local, the database name was not found. If the database is remote, the database name was not defined in the local database directory.
| Reason code 31008 | FLG_ERR_SRH_CRITERIA_ TOOLONG |
Explanation: The total length of the search criteria is too long. The maximum length for the sum of the lengths for all specified search criteria is about 32 700 bytes, depending on the number of properties in the search criteria.
| Reason code 31009 | FLG_ERR_DB_TRANSLOG_FULL |
Explanation: The database transaction log is full.
Issue FLGCommit or FLGRollback immediately. Increase the database log file size to increase the number of changes possible before you need to commit the changes.
| Reason code 31010 | FLG_ERR_INVALID_ AUTHENTICATION |
Explanation: The database was cataloged with an incorrect authentication option.
| Reason code 31011 | FLG_ERR_CHARCONV_ WINTODBM |
Explanation: An error occurred while converting a character from the Windows code page to the database code page.
| Reason code 31012 | FLG_ERR_DB_TIMEOUT |
Explanation: Database server is busy or locked.
| Reason code 31013 | FLG_ERR_NOT_SUPPORTED_ BY_DB |
Explanation: This function is not supported by the database server.
| Reason code 31014 | FLG_ERR_DB_ICON_EXIST |
Explanation: FLGManageIcons was called with the InOptions parameter set to FLG_ACTION_CREATE, but the icon specified in pszIconFileID already exists in the database.
Specify a different icon file, or use FLG_ACTION_UPDATE.
| Reason code 32000 | FLG_ERR_REG_NOTEXIST |
Explanation: No registration information exists for the specified object type.
| Reason code 32001 | FLG_ERR_TYPEID_NOTEXIST |
Explanation: No registration information exists for the specified object type.
| Reason code 32002 | FLG_ERR_SRCTYPEID_ NOTEXIST |
Explanation: The specified source object type does not exist.
| Reason code 32003 | FLG_ERR_TRGTYPEID_ NOTEXIST |
Explanation: The specified target object type does not exist.
| Reason code 32004 | FLG_ERR_INSTID_NOTEXIST |
Explanation: The specified object ID (FLGID) does not exist.
| Reason code 32005 | FLG_ERR_SRCINSTID_ NOTEXIST |
Explanation: The specified source object ID (FLGID) does not exist.
| Reason code 32006 | FLG_ERR_TRGINSTID_ NOTEXIST |
Explanation: The specified target object ID (FLGID) does not exist.
| Reason code 32007 | FLG_ERR_PROP_NOTEXIST |
Explanation: Unable to start the specified program. The property specified in the program object parameter list is not defined for the object instance.
| Reason code 32008 | FLG_ERR_REL_NOTEXIST |
Explanation: Unable to delete the relationship because it does not exist.
| Reason code 32009 | FLG_ERR_TYPE_NOT_CREATED |
Explanation: The specified object type has been registered but not created.
| Reason code 32010 | FLG_ERR_SRCTYPE_NOT_ CREATED |
Explanation: The object type specified in the FLGID of the source object instance has been registered but not created.
| Reason code 32011 | FLG_ERR_TRGTYPE_NOT_ CREATED |
Explanation: The object type specified in the FLGID of the target object instance has been registered but not created.
| Reason code 32012 | FLG_ERR_INV_P_CATEGORY |
Explanation: P (Program) is an invalid value for the category when creating or deleting object types. You cannot create or delete Program category object types.
| Reason code 32013 | FLG_ERR_INV_P_HANDLE_CAT |
Explanation: The HANDLES property value of the Program object instance is invalid.
The value must be the name of a non-PROGRAM object type.
| Reason code 32014 | FLG_ERR_P_HANDLE_NOTEXIST |
Explanation: The HANDLES property value of the Program object instance is invalid. The specified object type does not exist.
| Reason code 32015 | FLG_ERR_P_HANDLE_NOT_ CREATED |
Explanation: The HANDLES property value of the Program object instance is invalid. The specified object type has been registered, but not created.
| Reason code 32016 | FLG_ERR_INV_A_CATEGORY |
Explanation: A (Attachment) is an invalid value for the category when creating, deleting, or appending to object types. You cannot create, delete, or append to Attachment category object types.
| Reason code 32300 | FLG_ERR_REG_DUP |
Explanation: Unable to register the object type. The specified object type has already been registered.
| Reason code 32301 | FLG_ERR_TYPE_DUP |
Explanation: Unable to create an object type with the specified name. The specified object type name already exists in the database.
| Reason code 32302 | FLG_ERR_INST_DUP |
Explanation: Unable to create the specified object instance. The database already contains an object instance with identical UUI property values.
| Reason code 32303 | FLG_ERR_REL_DUP |
Explanation: Unable to create the specified object relationship. The relationship already exists.
| Reason code 32304 | FLG_ERR_REL_RECURSIVE |
Explanation: Unable to create the specified relationship. The specified relationship would cause a Grouping object to contain itself.
| Reason code 32305 | FLG_ERR_UUI_DUP |
Explanation: The definition of this object type or object contains two or more properties with the same UUI sequence number.
Possible Extended Codes: Sequence number of property that duplicates the UUI sequence number
| Reason code 32306 | FLG_ERR_INVALID_LINK_ RELATION |
Explanation: The specified LINK relationship is invalid, because the linker and linkee are the same.
| Reason code 32307 | FLG_ERR_INVALID_ ATTACHMENT_RELATION |
Explanation: The attachment relationship is rejected because the target object is already related to some non-attachment source object. Attachment category objects can be associated to only one non-attachment category source object.
| Reason code 32308 | FLG_ERR_ICONFILE_RETRIEVE_ ERROR |
Explanation: API FLGManageIcons encountered an error while retrieving (opening, reading, or closing) the icon file specified in parameter pszIconFileID. This applies to input options FLG_ACTION_CREATE or FLG_ACTION_UPDATE only. The reason code returned in the extended code indicates the error. Processing is unsuccessful.
Possible Extended Codes: Reason code
| Reason code 32400 | FLG_ERR_CONTAINEE_EXIST |
Explanation: Unable to delete this object instance because this Grouping object instance contains one or more object instances. You cannot delete this object instance until you delete either the relationships or the contained objects.
| Reason code 32401 | FLG_ERR_INST_EXIST |
Explanation: Unable to delete the specified object type because instances of the object type exist. You cannot delete this object type until you delete all its instances.
| Reason code 32402 | FLG_ERR_TYPE_EXIST |
Explanation: Unable to delete the object type registration because its object type exists. You cannot delete this object type registration until the object type is deleted.
| Reason code 32403 | FLG_ERR_CONTAINEE_ DIFFTYPE |
Explanation: FLGDeleteTypeExt API stopped, because it found a containee belonging to a different object type.
| Reason code 32500 | FLG_ERR_INVALID_SRCCAT |
Explanation: Unable to create the specified relationship. The category for the source object type is invalid.
| Reason code 32501 | FLG_ERR_INVALID_TRGCAT |
Explanation: Unable to create the specified relationship. The category for the target object type is invalid.
| Reason code 32502 | FLG_ERR_INVALID_CAT |
Explanation: The category of the input object type is incorrect.
Refer to the specific documentation for the API you called for the required input object type.
| Reason code 32600 | FLG_ERR_KAEXIST |
Explanation: Unable to log on as an administrator. Another administrator is already logged on. The Information Catalog Manager allows only one administrator to log on at a time.
| Reason code 32601 | FLG_ERR_NOTAUTH |
Explanation: The current user ID is not authorized to use this Information Catalog Manager function.
| Reason code 32602 | FLG_ERR_NOT_INITIALIZED |
Explanation: The information catalog is not initialized.
FLGInit must be issued before the Information Catalog Manager can perform any other functions.
| Reason code 32603 | FLG_ERR_ALREADY_ INITIALIZED |
Explanation: The information catalog has already been initialized. You cannot issue a second FLGInit call before issuing an FLGTerm call.
| Reason code 32604 | FLG_ERR_NOT_CREATOR |
Explanation: You do not have the authority to update Comments objects you did not create.
| Reason code 32700 | FLG_ERR_INVALID_TYPEID |
Explanation: The specified object type ID (OBJTYPID) is invalid.
| Reason code 32701 | FLG_ERR_INVALID_TYPEID_LEN |
Explanation: The specified object type ID (OBJTYPID) is invalid. This value must be 6 bytes long.
| Reason code 32702 | FLG_ERR_INVALID_TYPEID_VAL |
Explanation: The value of the specified object type ID (OBJTYPID) is invalid.
| Reason code 32703 | FLG_ERR_INVALID_FLGID |
Explanation: The specified object ID (FLGID) is invalid.
Possible Extended Codes: Number of exported objects or position of parameter
| Reason code 32704 | FLG_ERR_INVALID_FLGID_LEN |
Explanation: The object ID (FLGID) is invalid. This value must be 16 bytes long.
| Reason code 32705 | FLG_ERR_INVALID_FLGID_VAL |
Explanation: The object ID (FLGID) contains invalid characters.
| Reason code 32706 | FLG_ERR_INVALID_TYPNM |
Explanation: The object type name is invalid.
| Reason code 32707 | FLG_ERR_INVALID_INSTNM |
Explanation: The object instance name is invalid.
| Reason code 32708 | FLG_ERR_INVALID_TIMESTAMP |
Explanation: The input value is invalid. The input value must be a time stamp of the form YYYY-MM-DD-HH.MM.SS.NNNNNN and 26 bytes long.
Possible Extended Codes: Sequence number of property
| Reason code 32709 | FLG_ERR_INVALID_SRCID |
Explanation: The source object ID (FLGID) is invalid.
| Reason code 32710 | FLG_ERR_INVALID_TRGID |
Explanation: The target object ID (FLGID) is invalid.
| Reason code 32711 | FLG_ERR_INVALID_RELTYPE |
Explanation: The specified relation type (RelType) is invalid. Valid values are C, T, A, and L.
| Reason code 32712 | FLG_ERR_INVALID_RELOPT |
Explanation: The specified relation option (RelOpt) is invalid. Valid values are C and D.
| Reason code 32713 | FLG_ERR_INVALID_PGM_FLGID |
Explanation: The specified object ID (FLGID) for the program object is invalid.
| Reason code 32714 | FLG_ERR_INVALID_OBJ_FLGID |
Explanation: The specified object ID (FLGID) for the object providing parameters for the FLGOpen call is invalid.
| Reason code 32718 | FLG_ERR_INVALID_USERID |
Explanation: The user ID value is invalid. The length must be 1-8 characters.
User ID or password is invalid (password is case sensitive on AIX).
User is not logged on to the remote node (DB2 for OS/2 V2.1).
| Reason code 32719 | FLG_ERR_INVALID_PASSWORD |
Explanation: The specified password is invalid. The length must be 1-8 characters.
| Reason code 32720 | FLG_ERR_INVALID_DBNAME |
Explanation: The specified database name is invalid. The length must be 1-8 characters.
| Reason code 32721 | FLG_ERR_INVALID_ADMINOPT |
Explanation: The specified user option (admin) is invalid. Valid values are Y and N.
| Reason code 32722 | FLG_ERR_INVALID_TRACEOPT |
Explanation: The trace option (TraceOpt) is invalid. Valid options are: 0, 1, 2, 3, and 4.
| Reason code 32723 | FLG_ERR_NULL_PARAMETER |
Explanation: A parameter required as input to this API call is missing or null. The extended code indicates the position of the null parameter.
Possible Extended Codes: Position of parameter
| Reason code 32724 | FLG_ERR_NULL_EXTCODE |
Explanation: The extended code pointer parameter (pExtCode) is null.
| Reason code 32725 | FLG_ERR_INVALID_ CONVERTOPT |
Explanation: The specified input option (Options) was invalid. Valid values are D, and F.
| Reason code 32726 | FLG_ERR_INVALID_ICONOPT |
Explanation: The specified input options (Options) are not valid for FLGManageIcons.
| Reason code 32727 | FLG_ERR_INVALID_TAGBUFOPT |
Explanation: The InOptions specified for FLGManageTagBuf API is not valid. Use FLG_TAGBUF_QUERY or FLG_TAGBUF_RESET as defined in the DGxAPI.H file.
| Reason code 32728 | FLG_ERR_INVALID_TAGFILEOPT |
Explanation: The Options parameter specified for FLGXferTagBuf API is not valid. Use FLG_TAGOPT_NEW or FLG_TAGOPT_REPLACE as defined in the DGxAPI.H file.
| Reason code 32729 | FLG_ERR_INV_DGFLAG_ ACTION |
Explanation: The Action parameter specified for FLGManageFlags is not valid. Use FLG_ACTION_GET or FLG_ACTION_UPDATE as defined in DGxAPI.H file.
| Reason code 32730 | FLG_ERR_INV_DGFLAG_ FLAGTYPE |
Explanation: The FlagType parameter specified for the FLGManageFlags API is not valid. Use FLG_HISTORY_TYPE_DELETE as defined in the DGxAPI.H file.
| Reason code 32731 | FLG_ERR_INV_DGFLAG_VALUE |
Explanation: The chValue parameter specified for FLGManageFlags is not valid. Valid values are FLG_YES and FLG_NO.
| Reason code 32732 | FLG_ERR_INV_STATUS_ACTION |
Explanation: The Action parameter specified for the FLGManageCommentStatus API is not valid. Use FLG_ACTION_UPDATE or FLG_ACTION_GET as defined in the DGxAPI.H file.
| Reason code 32733 | FLG_ERR_INV_STATUS_LEN |
Explanation: The input structure object area contains a status field that is longer than 80 characters.
Possible Extended Codes: Sequence number of property
| Reason code 32734 | FLG_ERR_INVALID_TREEOPT |
Explanation: The Options parameter specified for FLGDeleteTree API is not valid. Use FLG_DELTREE_REL or FLG_DELTREE_ALL as defined in the DGxAPI.H file.
| Reason code 32735 | FLG_ERR_INVALID_ASSOCOPT |
Explanation: The Options parameter specified for FLGListAssociates API is not valid. Use FLG_LIST_PROGRAM, FLG_LIST_ATTACHMENT, FLG_LIST_COMMENTS, FLG_LIST_CONTAIN, FLG_LIST_CONTACT, or FLG_LIST_LINK as defined in the DGxAPI.H file.
| Reason code 32736 | FLG_ERR_INVALID_ ORPHANOPT |
Explanation: The Options parameter specified for the FLGListOrphans API is not valid. Use FLG_LIST_PROGRAM, FLG_LIST_CONTACT, FLG_LIST_ATTACHMENT, or FLG_LIST_COMMENTS as defined in the DGxAPI.H file.
| Reason code 32737 | FLG_ERR_INVALID_ FOUNDINOPT |
Explanation: The Options parameter specified in the FLGFoundIn API is not valid. Use FLG_LIST_PROGRAM, FLG_LIST_CONTAIN, FLG_LIST_CONTACT, or FLG_LIST_ATTACHMENT as defined in the DGxAPI.H file.
| Reason code 33000 | FLG_ERR_ICON_NOTEXIST |
Explanation: The specified icon file does not exist.
| Reason code 34000 | FLG_ERR_INVALID_IOSTRUCT |
Explanation: The input structure is invalid. Either the definition area length or object area length does not match the length of the area it describes.
| Reason code 34001 | FLG_ERR_NO_DEFN_AREA |
Explanation: The definition area is missing in the input structure.
| Reason code 34002 | FLG_ERR_NO_OBJ_AREA |
Explanation: The object area is missing in the input structure.
| Reason code 34003 | FLG_ERR_INVALID_POSITION |
Explanation: Information Catalog Manager internal error.
| Reason code 34004 | FLG_ERR_IOSTRUCT_ CONVERSION |
Explanation: An Information Catalog Manager internal error occurred while reading the input structure or writing the output structure.
| Reason code 34005 | FLG_ERR_INVALID_IOSTRUCT_ NULL |
Explanation: The input structure contains a null character.
Possible Extended Codes: Byte offset
| Reason code 34006 | FLG_ERR_OBJLEN_OBJCNT_ MISMATCH |
Explanation: Either the object area entry count or the object area length is zero.
If one of the values is greater than zero, the other value cannot be zero.
| Reason code 34200 | FLG_ERR_INV_HEADER_IDENT |
Explanation: The identifier in the input structure header area is invalid.
The identifier must be FLG-HEAD.
| Reason code 34201 | FLG_ERR_INV_HEADER_ DEFLEN |
Explanation: The definition length in the input structure header area is not valid.
The definition length must be greater than 0 and a multiple of 160. Some API calls require a fixed definition length. See the syntax for the API call for the required definition length.
| Reason code 34202 | FLG_ERR_INV_HEADER_ DEFCNT |
Explanation: The number of definitions expected based on the definition length in the header area is invalid for FLGExport.
The number of definitions must be five for FLGExport; therefore, the definition length must be 800.
| Reason code 34203 | FLG_ERR_INV_HEADER_ OBJLEN |
Explanation: The object length in the input structure header area is not valid.
| Reason code 34204 | FLG_ERR_INV_HEADER_ OBJCNT |
Explanation: The object area entry count in the input structure header area is not valid.
| Reason code 34205 | FLG_ERR_INV_HEADER_ CATEGORY |
Explanation: Invalid category specified in header area.
For FLGCreateReg, the category value must be one of the following: G, E, C, D, or S.
For FLGCreateType, FLGCreateInst, FLGUpdateReg, FLGAppendType, and FLGUpdateInst, the category value must match the value for the related object type registration.
| Reason code 34206 | FLG_ERR_INV_HEADER_ OBJTYPEID |
Explanation: The value of the object type ID in the header area is invalid.
This value must be identical to the object type ID generated for the related object type registration.
| Reason code 34207 | FLG_ERR_CONFLICTING_ HEADER_FIELDS |
Explanation: The number of properties derived from the definition length conflicts with the object area entry count in the header area.
The number of properties equals the definition area length divided by 160, and the object area entry count must be evenly divisible by the number of properties.
| Reason code 34208 | FLG_ERR_CONFLICTING_ OBJTYPID |
Explanation: The value specified for the object type identifier (OBJTYPID) in the object area does not match the object type ID in the header area.
Possible Extended Codes: Sequence number of property
| Reason code 34209 | FLG_ERR_HEADER_DEFLEN_ EXCEEDS_MAX |
Explanation: The definition length in the header area exceeds the maximum number of properties.
| Reason code 34210 | FLG_ERR_NONBLANK_ HEADER_CATEGORY |
Explanation: The category value in the header area is invalid.
| Reason code 34211 | FLG_ERR_NONBLANK_ HEADER_OBJTYPEID |
Explanation: The object type ID value in the header area is invalid.
| Reason code 34222 | FLG_ERR_NONBLANK_ HEADER_RESERVED |
Explanation: The reserved area of the input structure header area must always be blank.
| Reason code 34500 | FLG_ERR_INV_PROPERTY_ NAME |
Explanation: The specified property name is not one of the property names required with this API call.
Possible Extended Codes: None; Sequence number of property
| Reason code 34501 | FLG_ERR_INV_PROPERTY_ PPNAME |
Explanation: The property short name for a property in the definition area is invalid. The value may be missing, using DBCS characters, or not using the value required by the API call.
Possible Extended Codes: None; Sequence number of property
| Reason code 34502 | FLG_ERR_INV_PROPERTY_ DATATYPE |
Explanation: The data type for a property in the definition area is invalid.
Valid values are CHAR, TIMESTAMP, VARCHAR, or LONG VARCHAR, depending on the API call.
Possible Extended Codes: None; Sequence number of property
| Reason code 34503 | FLG_ERR_INV_PROPERTY_V_ FLAG |
Explanation: The value flag for the indicated property in the definition area is invalid.
Valid values are R, O, and S.
Possible Extended Codes: Sequence number of property
| Reason code 34504 | FLG_ERR_INV_PROPERTY_ SVALUE_V_FLAG |
Explanation: The value flag for the indicated property in the definition area is invalid. The specified value flag is S, but the Information Catalog Manager does not generate the property indicated by the property short name.
Possible Extended Codes: Sequence number of property
| Reason code 34505 | FLG_ERR_INV_PROPERTY_CS_ FLAG |
Explanation: The case-sensitivity flag value for the indicated property in the definition area is invalid.
Valid values are Y or N.
Possible Extended Codes: None; Sequence number of property
| Reason code 34506 | FLG_ERR_INV_PROPERTY_FS_ FLAG |
Explanation: The fuzzy search flag value for the indicated property in the definition area is invalid.
Valid values are Y or N.
Possible Extended Codes: Sequence number of property
| Reason code 34507 | FLG_ERR_INV_PROPERTY_ UUISEQ |
Explanation: The UUI sequence for the indicated property in the definition area is invalid.
Valid values are 1, 2, 3, 4, 5, and blank.
Possible Extended Codes: Sequence number of property
| Reason code 34508 | FLG_ERR_INV_PROPERTY_LEN_ FOR_DTYPE |
Explanation: The length value is invalid for the indicated property in the definition area because of the defined data type.
Possible Extended Codes: None; Sequence number of property
| Reason code 34509 | FLG_ERR_INV_PROP_LEN_ FIELD |
Explanation: The length for the indicated property in the definition area is invalid.
Check the API call syntax for the required length.
Possible Extended Codes: Sequence number of property
| Reason code 34510 | FLG_ERR_INV_PROP_VAL_LEN |
Explanation: The length field for a VARCHAR or LONG VARCHAR property value in the object area is invalid; it must contain right-aligned numeric characters.
| Reason code 34511 | FLG_ERR_INV_RQDPROP_SPEC |
Explanation: In a property definition in the definition area, one or more fields required to define a required property are invalid.
For a required property, the following fields must be specified as shown in the input structure diagrams for the API call:
Possible Extended Codes: Sequence number of property
| Reason code 34512 | FLG_ERR_DUP_PROPERTY_ NAME |
Explanation: Another property in the input structure already has this property name. Each property name must be unique in the input structure.
Possible Extended Codes: Sequence number of property
| Reason code 34513 | FLG_ERR_DUP_PROPERTY_ PPNAME |
Explanation: The property short name for the indicated property is identical to the property short name of another property in this input structure. Each property short name must be unique in the input structure.
Possible Extended Codes: Sequence number of property
| Reason code 34514 | FLG_ERR_INV_TOT_UUI_LEN |
Explanation: Reserved
| Reason code 34515 | FLG_ERR_INV_UUI_LENGTH |
Explanation: The indicated UUI property length value in the definition area exceeds the maximum length for a UUI property.
Possible Extended Codes: UUI sequence number
| Reason code 34516 | FLG_ERR_MISSING_PROPERTY |
Explanation: The definition area for the object instance does not contain all the properties defined for the object type.
| Reason code 34517 | FLG_ERR_MISSING_PROPERTY_ NAME |
Explanation: The property name is required but missing for the indicated property in the definition area.
Possible Extended Codes: Sequence number of property
| Reason code 34518 | FLG_ERR_MISSING_PROPERTY_ LENGTH |
Explanation: The length value is required but missing for the indicated property in the definition area.
Possible Extended Codes: Sequence number of property
| Reason code 34519 | FLG_ERR_MISSING_PROPERTY_ PPNAME |
Explanation: The property short name is required but missing for the indicated property in the definition area.
Possible Extended Codes: Sequence number of property
| Reason code 34520 | FLG_ERR_MISSING_REG_ DPNAME |
Explanation: The DP NAME (DPNAME) property is required but missing in the input structure definition area.
| Reason code 34521 | FLG_ERR_MISSING_REG_ PTNAME |
Explanation: The PHYSICAL TYPE NAME (PTNAME) property is required but missing in the input structure definition area.
| Reason code 34522 | FLG_ERR_MISSING_REG_ CREATOR |
Explanation: The CREATOR property is required but missing in the input structure definition area.
| Reason code 34523 | FLG_ERR_MISSING_REG_ UPDATIME |
Explanation: The LAST CHANGED DATE AND TIME (UPDATIME) property is required but missing in the input structure definition area.
| Reason code 34524 | FLG_ERR_MISSING_REG_ UPDATEBY |
Explanation: The LAST CHANGED BY (UPDATEBY) property is required but missing in the input structure definition area.
| Reason code 34525 | FLG_ERR_MISSING_REG_NAME |
Explanation: The EXTERNAL NAME OF OBJ TYPE (NAME) property is required but missing in the input structure definition area.
| Reason code 34526 | FLG_ERR_MISSING_UUI_ SEQUENCE |
Explanation: The indicated UUI sequence number was specified in the definition area, although the preceding number was not.
UUI sequence numbers must not skip numbers in the sequence: 1, 2, and 3 is valid; 1, 3, and 5 is invalid.
| Reason code 34527 | FLG_ERR_MISSING_RQD_ INSTIDNT |
Explanation: The Instance identifier (INSTIDNT) property is required but missing in the input structure definition area.
| Reason code 34528 | FLG_ERR_MISSING_RQD_ NAME |
Explanation: The Name (NAME) property is required but missing in the input structure definition area.
| Reason code 34529 | FLG_ERR_MISSING_RQD_ OBJTYPID |
Explanation: The Object type identifier (OBJTYPID) property is required but missing in the input structure definition area.
| Reason code 34530 | FLG_ERR_MISSING_RQD_ UPDATEBY |
Explanation: The Last Changed By (UPDATEBY) property is required but missing in the input structure definition area.
| Reason code 34531 | FLG_ERR_MISSING_RQD_ UPDATIME |
Explanation: The Last Changed Date and Time (UPDATIME) property is required but missing in the input structure definition area.
| Reason code 34532 | FLG_ERR_NOMATCH_ PROPERTY_NAME |
Explanation: The indicated input property in the definition area matches the property short name for an existing property, but the property names do not match.
Possible Extended Codes: Sequence number of property
| Reason code 34533 | FLG_ERR_NOMATCH_ PROPERTY_SPEC |
Explanation: The indicated property in the definition area matches the property name and property short name for an existing property; however, the data type, length, value flag, or UUI sequence values do not match.
Possible Extended Codes: Sequence number of property
| Reason code 34534 | FLG_ERR_PROPERTY_NOTEXIST |
Explanation: The property specified as part of the selection criteria does not exist.
Possible Extended Codes: Sequence number of property
| Reason code 34536 | FLG_ERR_UNMATCH_ DEFINITION |
Explanation: One of the following occurred:
Possible Extended Codes: None; Sequence number of property
| Reason code 34537 | FLG_ERR_PROPDUP |
Explanation: Duplicate property name or property short name specified in the definition area.
| Reason code 34538 | FLG_ERR_REG_PROPS_OUT_ OF_SEQUENCE |
Explanation: The registration properties are not specified in the correct sequence.
| Reason code 34539 | FLG_ERR_RQD_PROPS_OUT_ OF_SEQUENCE |
Explanation: The required properties are not specified in the correct sequence in the definition area.
| Reason code 34540 | FLG_ERR_INV_V_FLAG_FOR_ APPEND |
Explanation: The indicated appended property has a value flag of S or R.
An appended property must have a value flag of O (optional property).
Possible Extended Codes: Sequence number of property
| Reason code 34541 | FLG_ERR_INV_UUI_FOR_ APPEND |
Explanation: The indicated appended property is specified as a UUI property. Appended properties cannot be UUI properties.
Possible Extended Codes: Sequence number of property
| Reason code 34542 | FLG_ERR_NONBLANK_ PROPERTY_V_FLAG |
Explanation: The value flag for the indicated property is not blank. The value flag is not used by this API call and must be blank.
Possible Extended Codes: Sequence number of property
| Reason code 34543 | FLG_ERR_NONBLANK_ PROPERTY_CS_FLAG |
Explanation: The case-sensitivity flag for the indicated property is not blank. The case-sensitivity flag is not used by this API call and must be blank.
Possible Extended Codes: Sequence number of property
| Reason code 34544 | FLG_ERR_NONBLANK_ PROPERTY_FS_FLAG |
Explanation: The fuzzy search flag for the indicated property is not blank. The fuzzy search flag is not used by this API call and must be blank.
Possible Extended Codes: Sequence number of property
| Reason code 34545 | FLG_ERR_NONBLANK_ PROPERTY_UUISEQ |
Explanation: The UUI sequence position for the indicated property is not blank.
The UUI sequence position is not used by this API and must be blank.
The data type is LONG VARCHAR and the UUI sequence position is not blank. A UUI property can be CHAR, VARCHAR, TIMESTAMP, but not LONG VARCHAR.
Possible Extended Codes: Sequence number of property
| Reason code 34546 | FLG_ERR_NONBLANK_ PROPERTY_RESERVED |
Explanation: The reserved area of the input structure property specifications must always be blank.
Possible Extended Codes: Sequence number of property
| Reason code 34547 | FLG_ERR_UUI_V_FLAG_MUST_ BE_R |
Explanation: The value flag for the indicated property is not valid because all UUI properties must have value flags of R (required).
Possible Extended Codes: Sequence number of property
| Reason code 34548 | FLG_ERR_AT_LEAST_ONE_UUI_ PROP_RQD |
Explanation: None of the properties specified in the definition area is defined as a UUI property.
Every Information Catalog Manager object type must be defined with at least one UUI property.
| Reason code 34550 | FLG_ERR_DUP_REG_DPNAME |
Explanation: The DP NAME (DPNAME) specified in the definition area duplicates the DP NAME value of an existing object type registration.
The DPNAME value must be unique across the database.
| Reason code 34551 | FLG_ERR_DUP_REG_PTNAME |
Explanation: The PHYSICAL TYPE NAME (PTNAME) duplicates the name of an existing table in the database.
The PTNAME value must be unique across the database.
| Reason code 34552 | FLG_ERR_DUP_REG_NAME |
Explanation: The specified EXTERNAL NAME OF OBJ TYPE (NAME) duplicates the NAME value of an existing object type registration.
The NAME must be unique across the database.
| Reason code 34553 | FLG_ERR_INV_DPNAME |
Explanation: The syntax of the specified DPNAME value is invalid.
| Reason code 34554 | FLG_ERR_INV_DB_PTNAME |
Explanation: The specified PTNAME value is not valid according to database syntax rules.
| Reason code 34555 | FLG_ERR_INV_DB_DPNAME |
Explanation: Reserved
| Reason code 34556 | FLG_ERR_INV_DB_PROPERTY_ PPNAME |
Explanation: The property short name is not valid according to database syntax rules.
| Reason code 34557 | FLG_ERR_INV_TOT_PROPERTY_ LEN |
Explanation: The total length of CHAR, VARCHAR, and TIMESTAMP properties, plus overhead, is longer than the maximum allowed by a database for each row in the physical table in the database.
| Reason code 34558 | FLG_ERR_INV_PTNAME |
Explanation: The syntax of the specified PTNAME value is invalid.
| Reason code 34559 | FLG_ERR_INV_PROPERTY_CS_ FLAG_FOR_DB |
Explanation: The value for the case-sensitivity flag is not valid for the database.
Possible Extended Codes: Sequence number of property
| Reason code 34560 | FLG_ERR_SRH_PROP_VAL_ TOOLONG |
Explanation: The search criteria value is too long. The maximum length when using DB2 for MVS/ESA is 254 bytes.
Possible Extended Codes: Sequence number of property
| Reason code 34561 | FLG_ERR_EXTRA_PROPS_IN_ IOSTRUCT |
Explanation: The input structure contains one or more properties that are not in the object type definition.
| Reason code 34562 | FLG_ERR_MISSING_REQ_ PROPERTY |
Explanation: A required property is missing from the input structure of an FLGCreateInst or FLGUpdateInst API. The extended code points to the position of the missing property using the object type's complete definition.
Possible Extended Codes: Sequence number of property
| Reason code 34800 | FLG_ERR_PROP_VALUE_ REQUIRED |
Explanation: No value was specified in the object area for the indicated property. The definition for the property specifies that a value is required.
Possible Extended Codes: Sequence number of property
| Reason code 34801 | FLG_ERR_PROP_VALUE_ EXCEEDED |
Explanation: The length of the value for the indicated property exceeds the maximum length defined in the definition area.
Possible Extended Codes: Sequence number of property
| Reason code 34802 | FLG_ERR_INVALID_PROPERTY_ VALUE |
Explanation: The property value is invalid for one of the following reasons:
Possible Extended Codes: Sequence number of property
| Reason code 34803 | FLG_ERR_INV_SRH_VAL_FOR_ LONGVARCHAR |
Explanation: The search value for the indicated property is longer than the maximum length allowed for search criteria with a LONG VARCHAR data type (3000).
Possible Extended Codes: Sequence number of property
| Reason code 34804 | FLG_ERR_INV_OBJ_LENGTH |
Explanation: The actual length of the object area does not match the object length specified in the header area.
| Reason code 34805 | FLG_ERR_PARMLIST_ REQUIRES_HANDLES |
Explanation: The HANDLES property is not specified in the definition area.
Possible Extended Codes: Sequence number of property
| Reason code 34806 | FLG_ERR_REG_CONFLICT |
Explanation: The DPNAME or the PTNAME values specified in the object area do not match the values for the registration information identified by the object type ID.
| Reason code 34807 | FLG_ERR_ICON_EXCEEDS_ LIMIT |
Explanation: The icon size is greater than the maximum icon size (30000).
| Reason code 34808 | FLG_ERR_INST_VALUE_ EXCEEDED |
Explanation: The total length of the instance value exceeds the database limit.
| Reason code 34809 | FLG_ERR_INVALID_VARCHAR_ LENGTH |
Explanation: Reserved
| Reason code 34810 | FLG_ERR_INVALID_CREATOR |
Explanation: APIs FLGCreateInst and FLGUpdateInst found an error in the input I/O structure. The CREATOR value is not the same as the logged-on user ID. This is a requirement if the calling user is not authorized to perform object management operations.
| Reason code 35000 | FLG_ERR_PRG_NOT_STARTED |
Explanation: The program could not be started due to an unexpected operating system error.
| Reason code 35001 | FLG_ERR_PROG_PARM_ TOOLONG |
Explanation: The parameter specified for the Parameter list (PARMLIST) property of the program object is too long for the platform-specific program invocation.
| Reason code 35002 | FLG_ERR_INV_PROG_PARM |
Explanation: The parameter list in the program object contains an unmatched token specifier (%), or a property delimited by token specifiers is not a property of the object type identified by the HANDLES property.
| Reason code 35003 | FLG_ERR_PROGRAM_NOTEXIST |
Explanation: The program to be started does not exist, or the path specification is incorrect.
| Reason code 35004 | FLG_ERR_INV_SYNTAX_ STARTCMD |
Explanation: The value of the STARTCMD property of the Program object is invalid.
| Reason code 36001 | FLG_ERR_ACCESS_DENIED |
Explanation: Access is denied when opening or reading a file.
| Reason code 36002 | FLG_ERR_BAD_INVOCATION |
Explanation: An error occurred on the Information Catalog Manager command line invocation.
| Reason code 36003 | FLG_ERR_BROKEN_PIPE |
Explanation: Unable to open or read the specified file.
| Reason code 36004 | FLG_ERR_BUFFER_OVERFLOW |
Explanation: Information Catalog Manager internal error.
| Reason code 36005 | FLG_ERR_CANNOT_MAKE |
Explanation: Unable to create the specified file.
| Reason code 36006 | FLG_ERR_CLOSE_ERROR |
Explanation: Unable to close the file.
| Reason code 36007 | FLG_ERR_COPY_ERROR |
Explanation: Unable to copy a file.
| Reason code 36008 | FLG_ERR_DELETE_ERROR |
Explanation: Unable to delete the specified file.
| Reason code 36009 | FLG_ERR_DEVICE_IN_USE |
Explanation: Unable to access a file; the file is currently in use.
| Reason code 36010 | FLG_ERR_DIRECT_ACCESS_ HANDLE |
Explanation: Information Catalog Manager internal error.
| Reason code 36011 | FLG_ERR_DISK_FULL |
Explanation: The disk is full and the file cannot be created.
| Reason code 36012 | FLG_ERR_DRIVE_LOCKED |
Explanation: Unable to access a drive; the drive is currently in use.
| Reason code 36013 | FLG_ERR_DUPHNDL_ERROR |
Explanation: Information Catalog Manager internal error.
| Reason code 36014 | FLG_ERR_EAS_DIDNT_FIT |
Explanation: The icon file has too many extended attributes.
| Reason code 36015 | FLG_ERR_EA_LIST_ INCONSISTENT |
Explanation: Some of the extended attributes of the icon file are invalid.
| Reason code 36016 | FLG_ERR_EAS_NOT_ SUPPORTED |
Explanation: Unable to copy a file with extended attributes to a file system that does not support extended attributes.
| Reason code 36017 | FLG_ERR_FILENAME_EXCED_ RANGE |
Explanation: The file name or path was invalid.
| Reason code 36018 | FLG_ERR_FILE_NOT_FOUND |
Explanation: The specified path and file name was not found.
| Reason code 36019 | FLG_ERR_FINDFILE_ERROR |
Explanation: Unable to find the specified file.
| Reason code 36020 | FLG_ERR_FINDNEXT_ERROR |
Explanation: Unable to find the next file.
| Reason code 36021 | FLG_ERR_INVALID_ACCESS |
Explanation: Unable to write to the file; the file is read-only.
| Reason code 36022 | FLG_ERR_INVALID_DIRECTORY |
Explanation: The specified directory is invalid.
| Reason code 36023 | FLG_ERR_INVALID_DRIVE |
Explanation: Unable to access the specified drive.
| Reason code 36024 | FLG_ERR_INVALID_EA_NAME |
Explanation: Information Catalog Manager internal error.
| Reason code 36025 | FLG_ERR_INVALID_FILE_NAME |
Explanation: The specified file name is invalid.
| Reason code 36026 | FLG_ERR_INVALID_FUNCTION |
Explanation: Information Catalog Manager internal error.
| Reason code 36027 | FLG_ERR_INVALID_HANDLE |
Explanation: Information Catalog Manager internal error.
| Reason code 36028 | FLG_ERR_INVALID_ PARAMETER |
Explanation: Information Catalog Manager internal error.
| Reason code 36029 | FLG_ERR_INVALID_TARGET_ HANDLE |
Explanation: Information Catalog Manager internal error.
| Reason code 36030 | FLG_ERR_LOCK_VIOLATION |
Explanation: Unable to access a file; the file is locked by another application.
| Reason code 36031 | FLG_ERR_META_EXPANSION_ TOO_LONG |
Explanation: Information Catalog Manager internal error.
| Reason code 36032 | FLG_ERR_MORE_DATA |
Explanation: Unable to open a file; the file is too large.
| Reason code 36033 | FLG_ERR_NEED_EAS_FOUND |
Explanation: Unable to move the file to a drive that does not support extended attributes. Extended attributes are required for this file.
| Reason code 36034 | FLG_ERR_NEGATIVE_SEEK |
Explanation: Information Catalog Manager internal error.
| Reason code 36035 | FLG_ERR_NOT_DOS_DISK |
Explanation: The specified disk is not a valid disk or does not exist.
| Reason code 36036 | FLG_ERR_NO_MORE_FILES |
Explanation: Information Catalog Manager internal error.
| Reason code 36037 | FLG_ERR_NO_MORE_SEARCH_ HANDLES |
Explanation: This Information Catalog Manager session reached the maximum number of handles.
In your CONFIG.SYS file, increase the value for the FILES= option.
| Reason code 36038 | FLG_ERR_OPEN_ERROR |
Explanation: Unable to open the icon file, tag language file, echo file, or log file.
| Reason code 36039 | FLG_ERR_OPEN_FAILED |
Explanation: Unable to open the icon file, tag language file, echo file, or log file.
| Reason code 36040 | FLG_ERR_PATH_NOT_FOUND |
Explanation: The specified path was not found.
| Reason code 36041 | FLG_ERR_PIPE_BUSY |
Explanation: Information Catalog Manager internal error.
| Reason code 36042 | FLG_ERR_READ_ERROR |
Explanation: Information Catalog Manager internal error.
| Reason code 36043 | FLG_ERR_SEEK_ON_DEVICE |
Explanation: Information Catalog Manager internal error.
| Reason code 36044 | FLG_ERR_SETFILEPTR_ERROR |
Explanation: Information Catalog Manager internal error.
| Reason code 36045 | FLG_ERR_SHARING_BUFFER_ EXCEEDED |
Explanation: This file cannot be shared, because there is a buffer overflow.
| Reason code 36046 | FLG_ERR_SHARING_ VIOLATION |
Explanation: Unable to access this file. Another process is using this file.
| Reason code 36047 | FLG_ERR_TOO_MANY_OPEN_ FILES |
Explanation: Unable to open any more files.
Under OS/2, increase the value of the FILES= option.
| Reason code 36048 | FLG_ERR_WRITE_ERROR |
Explanation: Information Catalog Manager internal error.
| Reason code 36049 | FLG_ERR_WRITE_FAULT |
Explanation: Unable to write to the disk. The disk might be locked or unreadable.
| Reason code 36050 | FLG_ERR_WRITE_PROTECT |
Explanation: Unable to write to the file. The file is read-only.
| Reason code 36200 | FLG_ERR_NO_MORE_THREADS |
Explanation: No more system threads are available.
Close some existing programs to continue.
| Reason code 36201 | FLG_ERR_QDISK_FAIL |
Explanation: Unable to access information about the disk drive.
| Reason code 37001 | FLG_ERR_INV_RESTART_OPT |
Explanation: The specified restart option (RestartOpt) was invalid.
Valid values are B, C, b, and c.
| Reason code 37002 | FLG_ERR_INV_OBJTYPE_OPT |
Explanation: The option on the ACTION.OBJTYPE tag is invalid.
Valid options are MERGE, ADD, UPDATE, DELETE, DELETE_EXT, and APPEND.
| Reason code 37003 | FLG_ERR_INV_OBJINST_OPT |
Explanation: The option on the ACTION.OBJINST tag is invalid.
Valid options are ADD, UPDATE, DELETE, DELETE_TREE_REL, DELETE_TREE_ALL, and MERGE.
| Reason code 37004 | FLG_ERR_INV_RELATION_OPT |
Explanation: The option on the ACTION.RELATION tag is invalid.
Valid options are ADD and DELETE.
| Reason code 37005 | FLG_ERR_TAG_OUT_OF_ SEQUENCE |
Explanation: A tag is not in the correct sequence following an ACTION tag in the tag language file.
| Reason code 37006 | FLG_ERR_KEYNAME_TOO_ LONG |
Explanation: A UUI property short name on the INSTANCE tag is longer than the maximum length (8).
| Reason code 37007 | FLG_ERR_INV_ACTION_TYPE |
Explanation: The keyword on the ACTION tag is invalid.
Valid keywords are OBJTYPE, OBJINST, and RELATION.
| Reason code 37008 | FLG_ERR_KEYWORD_TOO_ LONG |
Explanation: A keyword on a tag is longer than the maximum allowed for the keyword.
| Reason code 37009 | FLG_ERR_PROPNAME_TOO_ LONG |
Explanation: Property short name on the INSTANCE tag is longer than the maximum length (8).
| Reason code 37010 | FLG_ERR_VALUE_TOO_LONG |
Explanation: Value in the tag language file is longer than the maximum allowed by its keyword, property short name, or UUI property short name.
| Reason code 37011 | FLG_ERR_OBJTAG_DUP_ KEYWORD |
Explanation: A keyword on the OBJECT tag is specified more than once.
| Reason code 37012 | FLG_ERR_PROPTAG_DUP_ KEYWORD |
Explanation: A keyword on the PROPERTY tag is specified more than once.
| Reason code 37013 | FLG_ERR_RELTAG_DUP_ KEYWORD |
Explanation: A keyword is specified more than once on the RELTYPE tag.
| Reason code 37014 | FLG_ERR_INSTTAG_DUP_ KEYNAME |
Explanation: A UUI property short name is specified more than once on the INSTANCE tag.
| Reason code 37015 | FLG_ERR_INSTTAG_DUP_ PROPNAME |
Explanation: A property short name is specified more than once on the INSTANCE tag.
| Reason code 37016 | FLG_ERR_OBJTAG_INV_ KEYWORD |
Explanation: A keyword on the OBJECT tag is invalid.
Valid keywords are TYPE, CATEGORY, EXTNAME, PHYNAME, ICOFILE and ICWFILE.
| Reason code 37017 | FLG_ERR_PROPTAG_INV_ KEYWORD |
Explanation: A keyword on the PROPERTY tag is invalid.
Valid keywords are EXTNAME, DT, DL, SHRTNAME, NULLS, and UUISEQ.
| Reason code 37018 | FLG_ERR_RELTAG_INV_ KEYWORD |
Explanation: A keyword on the RELTYPE tag is invalid.
Valid keywords are TYPE, SOURCETYPE, and TARGETYPE.
| Reason code 37019 | FLG_ERR_CMMTTAG_INV_ KEYWORD |
Explanation: A keyword on the COMMIT tag is invalid.
The valid keyword is CHKPID.
| Reason code 37020 | FLG_ERR_INSTTAG_INV_ KEYNAME |
Explanation: A UUI property short name on the INSTANCE tag is invalid.
| Reason code 37021 | FLG_ERR_INSTTAG_INV_ PROPNAME |
Explanation: A property short name on the INSTANCE tag is invalid.
The property short name must exist in the object type specified on the OBJECT tag.
| Reason code 37022 | FLG_ERR_INSTTAG_MISSING_ SKEY |
Explanation: SOURCEKEY is not the first keyword on the INSTANCE tag.
| Reason code 37023 | FLG_ERR_INSTTAG_MISSING_ TKEY |
Explanation: TARGETKEY is not the second keyword on the INSTANCE tag when creating or deleting a relationship.
| Reason code 37024 | FLG_ERR_TAGFILE_ PREMATURE_EOF |
Explanation: The Information Catalog Manager encountered the end of the tag language file unexpectedly when importing the tag language file.
| Reason code 37025 | FLG_ERR_PROPTAG_INV_DT |
Explanation: The DT value on the PROPERTY tag is invalid.
Valid values are C, V, L, and T.
| Reason code 37026 | FLG_ERR_PROPTAG_ RESERVED_SHRTNAME |
Explanation: The short name of a reserved property was specified as the value for SHRTNAME on the PROPERTY tag.
The following short names are reserved and cannot be specified as the SHRTNAME: OBJTYPID, INSTIDNT, UPDATIME, and UPDATEBY.
| Reason code 37027 | FLG_ERR_PROPTAG_INV_ NULLS |
Explanation: NULLS value on the PROPERTY tag is invalid.
Valid values are Y and N.
| Reason code 37028 | FLG_ERR_PROPTAG_INV_ UUISEQ |
Explanation: UUISEQ value on the PROPERTY tag is invalid.
Valid values are 0, 1, 2, 3, 4, and 5.
| Reason code 37029 | FLG_ERR_INSTTAG_RESERVED_ PROPNAME |
Explanation: The property short name of a reserved property was specified on the INSTANCE tag.
The following property short names are reserved and cannot be assigned values: OBJTYPID, INSTIDNT, UPDATIME, and UPDATEBY.
| Reason code 37030 | FLG_ERR_OBJTAG_MISSING_ REQD_KEYWORD |
Explanation: A required keyword is missing on the OBJECT tag.
| Reason code 37031 | FLG_ERR_OBJTAG_KEYWORD_ NOT_ALLOWED |
Explanation: A keyword specified on the OBJECT tag is not allowed with the current ACTION tag keyword and option.
| Reason code 37032 | FLG_ERR_PROPTAG_MISSING_ REQD_KEYWORD |
Explanation: A required keyword is missing on the PROPERTY tag.
Required keywords are: EXTNAME, DT, DL, SHRTNAME, and NULLS.
When NAME is specified as the value of SHRTNAME, SHRTNAME is the only required keyword.
| Reason code 37033 | FLG_ERR_RELTAG_MISSING_ REQD_KEYWORD |
Explanation: A required keyword is missing on the RELTYPE tag.
Required keywords are TYPE, SOURCETYPE, and TARGETYPE.
| Reason code 37034 | FLG_ERR_INVALID_DISKCNTL_ TAG |
Explanation: The values and keywords on the DISKCNTL tag are invalid.
| Reason code 37035 | FLG_ERR_NO_VALID_INPUT_ TAG |
Explanation: The tag language file contains no valid tags.
| Reason code 37037 | FLG_ERR_OBJTAG_INV_ CATEGORY |
Explanation: The CATEGORY value on the OBJECT tag is invalid.
Valid values are GROUPING, ELEMENTAL, CONTACT, DICTIONARY, and SUPPORT.
| Reason code 37038 | FLG_ERR_RELTAG_INV_TYPE |
Explanation: The TYPE value on the RELTYPE tag is invalid.
Valid values are CONTAIN, CONTACT, LINK, and ATTACHMENT.
| Reason code 37039 | FLG_ERR_MISSING_LPAREN |
Explanation: A left parenthesis is missing following a keyword, UUI property short name, or property short name.
| Reason code 37040 | FLG_ERR_INSTTAG_NO_ PROPNAME |
Explanation: No property short names were specified on the INSTANCE tag.
| Reason code 37041 | FLG_ERR_NO_VALUE |
Explanation: The value for the specified keyword is missing.
| Reason code 37042 | FLG_ERR_NO_KEYWORD |
Explanation: A tag does not include any keywords.
At least one keyword is required for all tags except COMMENT, NL, and TAB.
| Reason code 37043 | FLG_ERR_TAG_FOLLOWED_BY_ GARBAGE |
Explanation: A valid tag is followed by extra characters.
| Reason code 37044 | FLG_ERR_BAD_PAREN_ WITHIN_VALUE |
Explanation: A parenthesis specified within this value is invalid.
A parenthesis within values must be surrounded by single quotation marks.
| Reason code 37046 | FLG_ERR_PROPTAG_ KEYWORD_NOT_ALLOWED |
Explanation: A specified keyword is not allowed on the PROPERTY tag when NAME is specified as the SHRTNAME value.
Valid keywords in this case are SHRTNAME and UUISEQ.
| Reason code 37047 | FLG_ERR_UNEXPECTED_ LPAREN |
Explanation: A left parenthesis is specified before an expected keyword, UUI property short name, or property short name.
| Reason code 37048 | FLG_ERR_UNEXPECTED_ RPAREN |
Explanation: A right parenthesis is specified before an expected left parenthesis, keyword, UUI property short name, or property short name.
| Reason code 37300 | FLG_ERR_CHKPT_DUP |
Explanation: Information Catalog Manager internal error.
| Reason code 37301 | FLG_ERR_CHKPT_NOTEXIST |
Explanation: Information Catalog Manager internal error.
| Reason code 37302 | FLG_ERR_INV_SAVEAREA_LEN |
Explanation: Information Catalog Manager internal error.
| Reason code 37303 | FLG_ERR_INV_CHKPT_TOT_LEN |
Explanation: Information Catalog Manager internal error.
| Reason code 37304 | FLG_ERR_MISSING_CHKPT_ VALUE |
Explanation: Information Catalog Manager internal error.
| Reason code 37305 | FLG_ERR_NO_MATCH_ON_ CHKPTID |
Explanation: Unable to match the system-saved checkpoint ID with any COMMIT tag checkpoint ID in the specified tag language file.
| Reason code 37500 | FLG_ERR_REQUEST_A_NEW_ DISK_FAILED |
Explanation: The user did not insert the next tag language file diskette in the sequence.
| Reason code 37501 | FLG_ERR_VERIFY_DISKETTE_ SEQUENCE_FAILED |
Explanation: The Information Catalog Manager encountered an error while trying to verify the diskette sequence.
| Reason code 37502 | FLG_ERR_UNABLE_TO_FIND_ REQUIRED_PROPERTY |
Explanation: Unable to find a specified property short name in the target database.
This property short name was specified on the INSTANCE tag while updating or merging an object instance using ACTION.OBJINST(UPDATE) or ACTION.OBJINST(MERGE).
| Reason code 37503 | FLG_ERR_UNABLE_TO_FIND_ REQUIRED_OBJTYPE |
Explanation: Unable to find the object type name, specified on the OBJECT tag, in the target database.
| Reason code 37504 | FLG_ERR_NONUNIQUE_UUI_ KEY |
Explanation: The specified UUI values identify more than one instance.
| Reason code 37505 | FLG_ERR_MISMATCH_UUI_IN_ MERGE |
Explanation: In an object type merge, the UUI property short names for the object type in the input tag language file do not match the UUI property short names for the same object type in the database.
| Reason code 37506 | FLG_ERR_DATA_LENGTH_ CONVERSION_FAILED |
Explanation: Information Catalog Manager internal error.
| Reason code 37507 | FLG_ERR_MISMATCH_DATA_ LENGTH_IN_MERGE |
Explanation: The value of DL (data length) on a PROPERTY tag following an ACTION.OBJTYPE(MERGE) tag in the input tag language file does not match the value for the same property in the target database for the same object type.
| Reason code 37508 | FLG_ERR_MISMATCH_DATA_ TYPE_IN_MERGE |
Explanation: The value of DT (data type) on a PROPERTY tag following an ACTION.OBJTYPE(MERGE) tag in the input tag language file does not match the value for the same property in the target database for the same object type.
| Reason code 37509 | FLG_ERR_MISMATCH_ PROPERTY_NAME_IN_MERGE |
Explanation: The value of SHRTNAME (property short name) on a PROPERTY tag that follows an ACTION.OBJTYPE(MERGE) tag in the input tag language file does not match any property in the database for the same object type.
| Reason code 37510 | FLG_ERR_MISMATCH_ CATEGORY_IN_MERGE |
Explanation: The value of CATEGORY on an OBJECT tag following an ACTION.OBJTYPE(MERGE) tag in the input tag language file does not match the value in the database for the same object type.
| Reason code 37511 | FLG_ERR_MISSING_REQUIRED_ OBJTYPE_MERGE_STATEMENT |
Explanation: Unable to merge an object instance using ACTION.OBJINST(MERGE) before its object type is merged using ACTION.OBJTYPE(MERGE).
The ACTION.OBJTYPE(MERGE) tag must be processed before an ACTION.OBJINST(MERGE) for the same object type.
| Reason code 37512 | FLG_ERR_NONUNIQUE_ SOURCE_UUI_KEY |
Explanation: Reserved
| Reason code 37513 | FLG_ERR_NONUNIQUE_ TARGET_UUI_KEY |
Explanation: Reserved
| Reason code 37514 | FLG_ERR_NO_TAGFILE_ON_ DISKETTE |
Explanation: Unable to find the input tag language file on the provided diskette.
| Reason code 37515 | FLG_ERR_WRONG_DISK_ SEQUENCE |
Explanation: The diskettes containing the tag language file were inserted in the wrong order.
| Reason code 37516 | FLG_ERR_REQ_INST_ NOTFOUND |
Explanation: Unable to find the instance to be updated.
| Reason code 37801 | FLG_ERR_NO_UUI |
Explanation: Export encountered an object with no UUI and cannot process.
| Reason code 37802 | FLG_ERR_CREATEREG_FAILED |
Explanation: Reserved
| Reason code 37803 | FLG_ERR_UPDATEREG_FAILED |
Explanation: Reserved
| Reason code 37804 | FLG_ERR_GETREG_FAILED |
Explanation: Export calls FLGGetReg, which returned an error.
See the log file for information about how this error affects the export.
Possible Extended Codes: None; Reason code
| Reason code 37805 | FLG_ERR_DELETEREG_FAILED |
Explanation: Reserved
| Reason code 37806 | FLG_ERR_CREATETYPE_FAILED |
Explanation: Reserved
| Reason code 37807 | FLG_ERR_APPENDTYPE_FAILED |
Explanation: Reserved
| Reason code 37808 | FLG_ERR_GETTYPE_FAILED |
Explanation: Reserved
| Reason code 37809 | FLG_ERR_DELETETYPE_FAILED |
Explanation: Reserved
| Reason code 37820 | FLG_ERR_CREATEINST_FAILED |
Explanation: Reserved
| Reason code 37821 | FLG_ERR_UPDATEINST_FAILED |
Explanation: Reserved
| Reason code 37822 | FLG_ERR_GETINST_FAILED |
Explanation: Export calls FLGGetInst, which returned an error.
See the log file for information about how this error affects the export.
Possible Extended Codes: None; Reason code
| Reason code 37823 | FLG_ERR_DELETEINST_FAILED |
Explanation: Reserved
| Reason code 37824 | FLG_ERR_LISTTYPE_FAILED |
Explanation: Reserved
| Reason code 37825 | FLG_ERR_SEARCH_FAILED |
Explanation: Reserved
| Reason code 37826 | FLG_ERR_RELATE_FAILED |
Explanation: Reserved
| Reason code 37827 | FLG_ERR_LISTCONTACTS_ FAILED |
Explanation: Export calls FLGListContacts, which returned an error.
See the log file for information about how this error affects the export.
Possible Extended Codes: Reason code
| Reason code 37828 | FLG_ERR_NAVIGATE_FAILED |
Explanation: Export calls FLGNavigate, which returned an error.
See the log file for information about how this error affects the export.
Possible Extended Codes: Reason code
| Reason code 37829 | FLG_ERR_FREEMEM_FAILED |
Explanation: Export calls FLGFreeMem, which returned an error.
See the log file for information about how this error affects the export.
Possible Extended Codes: Reason code
| Reason code 37831 | FLG_ERR_LISTASSOC_FAILED |
Explanation: This function calls FLGListAssociates, which returned an error.
Possible Extended Codes: Reason code
| Reason code 37901 | FLG_ERR_NULL_LOGFILE |
Explanation: The log file pointer parameter value is NULL.
A value is required for this parameter.
| Reason code 37902 | FLG_ERR_LOGFILE_OPENERR |
Explanation: Import or export encountered an error while opening the log file.
The extended code contains the reason code for the error.
Possible Extended Codes: Reason code
| Reason code 37904 | FLG_ERR_LOGFILE_WRITEERR |
Explanation: Import or export encountered an error while writing to the log file.
The extended code contains the reason code for the error.
Possible Extended Codes: Reason code
| Reason code 37906 | FLG_ERR_LOGFILE_CLOSEERR |
Explanation: Import or export encountered an error while closing the log file.
The extended code contains the reason code for the error.
Possible Extended Codes: Reason code
| Reason code 37908 | FLG_ERR_INV_TAGFILE_LEN |
Explanation: One of the following has occurred:
| Reason code 37909 | FLG_ERR_INV_LOGFILE_LEN |
Explanation: One of the following has occurred:
| Reason code 37910 | FLG_ERR_INV_TAGFILE |
Explanation: The specified drive for the tag language file is invalid because the Information Catalog Manager encountered an error while trying to access it.
If the tag language file is in MDIS format, then the drive cannot be a removable drive.
| Reason code 37911 | FLG_ERR_INV_LOGFILE |
Explanation: The specified drive for the log file is invalid. The specified drive might be removable, or an error occurred when the Information Catalog Manager tried to access it.
| Reason code 37912 | FLG_ERR_ECHOFILE_OPENERR |
Explanation: Import encountered an error while opening the echo file.
The extended code contains the reason code for the error.
Possible Extended Codes: Reason code
| Reason code 37913 | FLG_ERR_TAGFILE_READERR |
Explanation: Import encountered an error while reading the tag language file.
The extended code contains the reason code for the error.
Possible Extended Codes: Reason code
| Reason code 37914 | FLG_ERR_ECHOFILE_WRITEERR |
Explanation: Import encountered an error while writing to the echo file.
The extended code contains the reason code for the error.
Possible Extended Codes: Reason code
| Reason code 37915 | FLG_ERR_INV_ICOPATH_LEN |
Explanation: The specified icon path is too long.
The maximum length for an icon path, including the drive and directories, is 246.
| Reason code 37919 | FLG_ERR_ICOPATH_ NONBLANK_EXT |
Explanation: The specified icon path (pszIcoPath) includes an extension.
This value should include only the path.
| Reason code 37920 | FLG_ERR_INV_ICOPATH |
Explanation: The drive or extension specified in the icon path is invalid for one of the following reasons:
| Reason code 37921 | FLG_ERR_TAGFILE_OPENERR |
Explanation: Import, export, or FLGXferTagBuf encountered an error while opening the tag language file.
The extended code contains the reason code for the open error.
Possible Extended Codes: Reason code
| Reason code 37922 | FLG_ERR_TAGFILE_CLOSEERR |
Explanation: Import, export, or FLGXferTagBuf encountered an error while closing the tag language file.
The extended code contains the reason code for the error.
Possible Extended Codes: Reason code
| Reason code 37923 | FLG_ERR_ECHOFILE_CLOSEERR |
Explanation: Import encountered an error while closing the echo file.
The extended code contains the reason code for the error.
Possible Extended Codes: Reason code
| Reason code 37924 | FLG_ERR_INV_ECHOFILE_LEN |
Explanation: The length of the log file path with the tag language file name and the ECH extension is longer than the maximum length allowed for the complete echo file path and name.
This maximum is 259 characters.
| Reason code 37925 | FLG_ERR_MAX_OBJTYPE_ EXCEEDED |
Explanation: The tag language file contains more than the maximum number of discrete object types allowed (3500) when importing or exporting.
| Reason code 37926 | FLG_ERR_TAGFILE_WRITEERR |
Explanation: Export or the FLGXferTagBuf API encountered an error while trying to write to the tag language file.
The extended code contains the reason code for the write error.
Possible Extended Codes: Reason code
| Reason code 37928 | FLG_ERR_INV_TAGFILE_EXT |
Explanation: The file name specified for the tag language file has an extension of ECH. This extension is invalid.
| Reason code 37929 | FLG_ERR_INV_LOGFILE_EXT |
Explanation: The file name specified for the log file has an extension of ECH. This extension is invalid.
| Reason code 37930 | FLG_ERR_TAGFILE_LOGFILE_ CONFLICT |
Explanation: The specified log file is the same as the tag language file. The two files must be different.
| Reason code 38000 | FLG_ERR_INVALID_EXPORT_ IOSTRUCT |
Explanation: The input structure for FLGExport is invalid.
Possible Extended Codes: Sequence number of object
| Reason code 38001 | FLG_ERR_INVALID_CFLAG |
Explanation: The containee flag value is invalid in the FLGExport input structure.
Valid values are Y or N.
Possible Extended Codes: Sequence number of object
| Reason code 38002 | FLG_ERR_INVALID_TFLAG |
Explanation: The contact flag value is invalid in the FLGExport input structure.
Valid values are Y or N.
Possible Extended Codes: Sequence number of object
| Reason code 38003 | FLG_ERR_TAGFILE_EXIST |
Explanation: The name specified for the export output tag language file (pszTagFileID) points to a file that already exists.
The name of the output tag language file must not already exist.
| Reason code 38004 | FLG_ERR_GET_ICON_FAILED |
Explanation: Unable to export the icon for the specified object type.
Possible Extended Codes: Reason code
| Reason code 38005 | FLG_ERR_INVALID_AFLAG |
Explanation: The attachment flag on the export input structure is not valid. Valid values are Y and N.
Possible Extended Codes: Sequence number of object
| Reason code 38006 | FLG_ERR_INVALID_LFLAG |
Explanation: The link flag in the export input structure is not valid. Valid values are Y and N.
Possible Extended Codes: Sequence number of object type.
| Reason code 39000 | FLG_ERR_UPM_FAIL |
Explanation: The User Profile Management utility failed (logon failed or logon user ID is different than connected user ID).
| Reason code 39001 | FLG_ERR_INV_INPUT_PARM |
Explanation: The input parameter keywords for the command are invalid or missing.
| Reason code 39002 | FLG_ERR_MISSING_PARM_ VALUE |
Explanation: The input parameter values for the command are invalid or missing.
| Reason code 39003 | FLG_ERR_INIT_BIDI_ERROR |
Explanation: The Information Catalog Manager encountered an error while initializing for the bidirectional environment. This applies only when the Information Catalog Manager is running on an Arabic or Hebrew machine.
| Reason code 39201 | FLG_ERR_INVALID_USERTYPE_ FOR_UPDATE |
Explanation: The user type specified to be updated is invalid. The valid types are either the primary or backup administrator.
| Reason code 39202 | FLG_ERR_INVALID_USERTYPE_ FOR_CRT_OR_DEL |
Explanation: The user type specified to be created or deleted is invalid. Only users authorized to perform object management tasks can be created or deleted.
| Reason code 39203 | FLG_ERR_INVALID_ID_BAD_ CHAR |
Explanation: The specified user ID contains an invalid character. Refer to your database documentation for valid characters.
| Reason code 39204 | FLG_ERR_INVALID_ID_NUM_ START |
Explanation: The specified user ID begins with a numeric character. This is not a valid starting character.
| Reason code 39205 | FLG_ERR_INVALID_ID_IMB_ BLANK |
Explanation: The specified user ID contains an imbedded blank. This is not allowed.
| Reason code 39206 | FLG_ERR_INVALID_MUU_OPT |
Explanation: The option specified for the FLGManageUsers API is invalid. Valid actions are FLG_ACTION_CREATE, FLG_ACTION_UPDATE, FLG_ACTION_DELETE, and FLG_ACTION_LIST.
| Reason code 39209 | FLG_ERR_INVALID_PADMIN_ USERID |
Explanation: The specified user ID for the primary administrator is invalid. Verify the user ID syntax in your database documentation.
| Reason code 39210 | FLG_ERR_INVALID_BADMIN_ USERID |
Explanation: The specified user ID for the backup administrator is invalid. Verify the user ID syntax in your database documentation.
| Reason code 39211 | FLG_ERR_INVALID_ POWERUSER_USERID |
Explanation: The specified user ID is invalid. Verify the user ID syntax in your database documentation.
Possible Extended Codes: Contains the index to the user ID in the input structure that is invalid.
| Reason code 39502 | FLG_ERR_CDF_ERROR |
Explanation: Reserved
| Reason code 39504 | FLG_ERR_INSTPROFILE_ERROR |
Explanation: Reserved
| Reason code 39700 | FLG_ERR_TERM_FAIL_ ROLLBACK_CLOSE |
Explanation: Reserved
| Reason code 39701 | FLG_ERR_TERM_FAIL_ ROLLBACK |
Explanation: Reserved
| Reason code 39702 | FLG_ERR_TERM_FAIL_COMMIT |
Explanation: Reserved
| Reason code 40001 | FLG_ERR_INVALID_CONFIG_ PROFILE |
Explanation: The MDIS configuration profile file does not contain a valid BEGIN CONFIGURATION section.
| Reason code 40002 | FLG_ERR_CONFIGFILE_ READERR |
Explanation: MDIS import encountered an error while reading the configuration profile file.
Possible Extended Codes: reason code
| Reason code 40003 | FLG_ERR_CONFIGFILE_ CLOSEERR |
Explanation: MDIS import encountered an error while closing the configuration profile file.
Possible Extended Codes: reason code
| Reason code 40006 | FLG_ERR_CONFIGFILE_INV_ BEGIN_STMT |
Explanation: The MDIS configuration profile file contains an invalid BEGIN statement. Valid statement is: BEGIN CONFIGURATION.
| Reason code 40007 | FLG_ERR_CONFIGFILE_INV_ END_STMT |
Explanation: The MDIS configuration profile file contains an invalid END statement. Valid statement is: END CONFIGURATION.
| Reason code 40010 | FLG_ERR_CONFIGFILE_INV_ KEYWORD |
Explanation: The MDIS configuration profile file contains an invalid keyword.
| Reason code 40011 | FLG_ERR_CONFIGFILE_INV_ TEXT |
Explanation: The MDIS configuration profile file contains invalid text.
| Reason code 40012 | FLG_ERR_CONFIGFILE_INV_ VALUE |
Explanation: The MDIS configuration profile file contains an invalid keyword value.
| Reason code 40013 | FLG_ERR_CONFIGFILE_VALUE_ TOO_LONG |
Explanation: The MDIS configuration profile file contains a keyword value that exceeds the maximum allowable length for that keyword.
| Reason code 40015 | FLG_ERR_CONFIGFILE_ PREMATURE_EOF |
Explanation: MDIS import unexpectedly encountered the end of the configuration profile file.
| Reason code 40021 | FLG_ERR_INVALID_TOOL_ PROFILE |
Explanation: The MDIS tool profile file does not contain a valid BEGIN TOOL section.
| Reason code 40022 | FLG_ERR_TOOLFILE_READERR |
Explanation: MDIS import encountered an error while reading the tool profile file.
Possible Extended Codes: reason code
| Reason code 40023 | FLG_ERR_TOOLFILE_CLOSEERR |
Explanation: MDIS import encountered an error while closing the tool profile file.
Possible Extended Codes: reason code
| Reason code 40026 | FLG_ERR_TOOLFILE_INV_ BEGIN_STMT |
Explanation: The MDIS tool profile file contains an invalid BEGIN statement. Valid statements are: BEGIN TOOL and BEGIN APPLICATIONDATA.
| Reason code 40027 | FLG_ERR_TOOLFILE_INV_END_ STMT |
Explanation: The MDIS tool profile file contains an invalid END statement. Valid statements are: END TOOL and END APPLICATIONDATA.
| Reason code 40030 | FLG_ERR_TOOLFILE_INV_ KEYWORD |
Explanation: The MDIS tool profile file contains an invalid keyword.
| Reason code 40031 | FLG_ERR_TOOLFILE_INV_TEXT |
Explanation: The MDIS tool profile file contains invalid text.
| Reason code 40032 | FLG_ERR_TOOLFILE_ INV_VALUE |
Explanation: The MDIS tool profile file contains an invalid keyword value.
| Reason code 40033 | FLG_ERR_TOOLFILE_VALUE_ TOO_LONG |
Explanation: The MDIS tool profile file contains a keyword value that exceeds the maximum allowable length for that keyword.
| Reason code 40034 | FLG_ERR_TOOLFILE_ CONFLICTING_VALUES |
Explanation: The MDIS tool profile file contains conflicting RECORD, DIMENSION, or ELEMENT values.
| Reason code 40050 | FLG_ERR_TOOLFILE_ PREMATURE_EOF |
Explanation: MDIS import unexpectedly encountered the end of the tool profile file.
| Reason code 40100 | FLG_ERR_UNSUPPORTED_ MDIS_FUNCTION |
Explanation: The configuration profile file specifies a function that is not supported by the Information Catalog Manager.
| Reason code 40101 | FLG_ERR_MISSING_REQ_ MDIS_KEYWORD |
Explanation: A required MDIS keyword is not present in the tag language file.
| Reason code 40110 | FLG_ERR_TAGFILE_INV_ KEYWORD |
Explanation: The MDIS tag language file contains an invalid keyword.
| Reason code 40111 | FLG_ERR_TAGFILE_INV_TEXT |
Explanation: The MDIS tag language file contains invalid text.
| Reason code 40112 | FLG_ERR_TAGFILE_INV_VALUE |
Explanation: The MDIS tag language file contains an invalid keyword value.
| Reason code 40113 | FLG_ERR_TAGFILE_VALUE_ TOO_LONG |
Explanation: The MIDS tag language file contains a keyword value that exceeds the maximum allowable length for that keyword.
| Reason code 40115 | FLG_ERR_MISSING_DQUOTE |
Explanation: A double quotation mark is missing following a keyword.
| Reason code 40116 | FLG_ERR_UNEXPECTED_ DQUOTE |
Explanation: A double quotation mark was found unexpectedly.
| Reason code 40117 | FLG_ERR_SPECIFIED_ PROPERTY_NOT_FOUND |
Explanation: Unable to find a specified property short name in the target database.
| Reason code 40118 | FLG_ERR_TAGFILE_INV_END_ STMT |
Explanation: The MDIS tag language file contains an invalid END statement.
| Reason code 40119 | FLG_ERR_TAGFILE_INV_ BEGIN_STMT |
Explanation: The MDIS tag language file contains an invalid BEGIN statement.
| Reason code 40130 | FLG_ERR_INV_RECORD_ SECTION |
Explanation: A BEGIN RECORD section is incorrectly nested in the MDIS tag language file.
| Reason code 40131 | FLG_ERR_INV_DIMENSION_ SECTION |
Explanation: A BEGIN DIMENSION section is incorrectly nested in the MDIS tag language file.
| Reason code 40132 | FLG_ERR_INV_SUBSCHEMA_ SECTION |
Explanation: A BEGIN SUBSCHEMA section is incorrectly nested in the MDIS tag language file.
| Reason code 40201 | FLG_ERR_DUPLICATE_ IDENTIFIER |
Explanation: An identifier value is duplicated in the MDIS tag language file.
| Reason code 40202 | FLG_ERR_INV_IDENTIFIER_ REFERENCE |
Explanation: Either a SourceObjectIdentifier or a TargetObjectIdentifier value does not refer to an identifier value previously defined in the tag language file.
| Reason code 40211 | FLG_ERR_INV_PART1_VALUE |
Explanation: The value for the first part of an MDIS object does not match the parent value.
| Reason code 40212 | FLG_ERR_INV_PART2_VALUE |
Explanation: The value for the second part of an MDIS object does not match the parent value.
| Reason code 40213 | FLG_ERR_INV_PART3_VALUE |
Explanation: The value for the third part of an MDIS object does not match the parent value.
| Reason code 40214 | FLG_ERR_INV_PART4_VALUE |
Explanation: The value for the fourth part of an MDIS object does not match the parent value.
| Reason code 40215 | FLG_ERR_MDIS_WORK_ BUFFER_OVERFLOW |
Explanation: An MDIS file (configuration profile file, tool profile file, or tag language file) contains a value that is longer than the maximum allowable size of internal work buffers (32 700 bytes).
| Reason code 40216 | FLG_ERR_MDIS_APPL_DATA_ TOO_LONG |
Explanation: The ApplicationData section of the MDIS tag language file exceeds limits for the Application data object type. The Application data object type is limited to 10 properties of 32 700 bytes each.
| Reason code 80000 | FLG_SEVERR |
Explanation: Place holder; indicates the beginning of the numeric range for severe errors.
| Reason code 80002 | FLG_SEVERR_NO_MEMORY |
Explanation: The Information Catalog Manager is unable to allocate more memory.
| Reason code 80003 | FLG_SEVERR_MEM_ERROR |
Explanation: One of the following occurred:
| Reason code 80004 | FLG_SEVERR_NO_CSA |
Explanation: Information Catalog Manager internal error.
| Reason code 80005 | FLG_SEVERR_APIDLL_FAILURE |
Explanation: The API DLL is missing API calls, or the API DLL could not be loaded.
| Reason code 80006 | FLG_SEVERR_VIOPOPUP_FAIL |
Explanation: The Information Catalog Manager is unable to display OS/2 character-based error messages using video input/output (VIO).
| Reason code 80007 | FLG_SEVERR_BIDIDLL_FAILURE |
Explanation: The Information Catalog Manager encountered an error while loading the PMBIDI.DLL. This DLL is needed when the Information Catalog Manager runs on an Arabic or Hebrew machine.
| Reason code 80008 | FLG_SEVERR_DG2IFORDLL_ FAILURE |
Explanation: A necessary DG2IFOR.DLL file was not found or is invalid. The Information Catalog Manager cannot continue.
| Reason code 81000 | FLG_SEVERR_STARTDBM_FAIL |
Explanation: Unable to start the local database management system. Refer to your database documentation for an explanation of the SQLCODE.
| Reason code 81001 | FLG_SEVERR_STARTDB_FAIL |
Explanation: Reserved
| Reason code 81002 | FLG_SEVERR_DB_ DISCONNECTED |
Explanation: The database disconnected unexpectedly.
| Reason code 81003 | FLG_SEVERR_DB_ INCONSISTENT |
Explanation: The Information Catalog Manager detected an inconsistency in the database.
| Reason code 81004 | FLG_SEVERR_COMMIT_FAIL |
Explanation: The commit call to the database failed.
| Reason code 81005 | FLG_SEVERR_ROLLBACK_FAIL |
Explanation: The rollback call to the database failed.
| Reason code 81006 | FLG_SEVERR_NO_DBSPACE |
Explanation: The database server has run out of space, or the file system is full.
| Reason code 81007 | FLG_SEVERR_DB_AUTO_ ROLLBACK_COMPLETE |
Explanation: The Information Catalog Manager encountered a database error and rolled back any uncommitted changes to the database.
Check the extended code for the database SQLCODE that describes the error condition that caused the Information Catalog Manager to perform the rollback.
Possible Extended Codes: Database SQLCODE
| Reason code 81008 | FLG_SEVERR_DB_AUTO_ ROLLBACK_FAIL |
Explanation: The Information Catalog Manager encountered a database error and attempted to roll back any uncommitted changes to the database, but this rollback failed.
Check the extended code for the database SQLCODE that describes the error condition that caused the Information Catalog Manager to perform the rollback.
The database might be in an inconsistent state and need to be recovered.
Possible Extended Codes: Database SQLCODE
| Reason code 82000 | FLG_SEVERR_INIT_FAIL |
Explanation: The Information Catalog Manager encountered an unexpected condition, probably an OS/2 internal memory error, that prevents the Information Catalog Manager from running normally.
| Reason code 82001 | FLG_SEVERR_TERM_FAIL |
Explanation: The Information Catalog Manager encountered an unexpected condition, probably an OS/2 internal memory error, that prevents the Information Catalog Manager from releasing its allocated resources. The resources will be freed when the calling application session ends.
| Reason code 82002 | FLG_SEVERR_TERM_FAIL_ CLOSE |
Explanation: Reserved
| Reason code 82200 | FLG_SEVERR_GETREG_FAILED |
Explanation: Export calls FLGGetReg, which returned a severe error.
Possible Extended Codes: Reason code
| Reason code 82201 | FLG_SEVERR_GETINST_FAILED |
Explanation: Export calls FLGGetInst, which returned a severe error.
Possible Extended Codes: Reason code
| Reason code 82202 | FLG_SEVERR_LISTCONTACTS_ FAILED |
Explanation: Export calls FLGListContacts, which returned a severe error.
Possible Extended Codes: Reason code
| Reason code 82203 | FLG_SEVERR_NAVIGATE_ FAILED |
Explanation: Export calls FLGNavigate, which returned a severe error.
Possible Extended Codes: Reason code
| Reason code 82204 | FLG_SEVERR_FREEMEM_ FAILED |
Explanation: Export calls FLGFreeMem, which returned a severe error.
Possible Extended Codes: Reason code
| Reason code 82400 | FLG_SEVERR_THREAD_FAILED |
Explanation: A severe error occurred while creating the new thread, and the Information Catalog Manager cannot continue.
| Reason code 82500 | FLG_SEVERR_PARMS_MISSING |
Explanation: The Information Catalog Manager required system table is corrupted or missing.
| Reason code 82501 | FLG_SEVERR_DGEMPTY |
Explanation: The Information Catalog Manager database contains no registrations or object types.The database is corrupted.
Recover the database using your backed-up database files.
| Reason code 82502 | FLG_SEVERR_TYPE_WOUT_ PROPERTY |
Explanation: No properties exist for the specified object type, or the Information Catalog Manager is unable to retrieve any properties.
| Reason code 82503 | FLG_SEVERR_MORE_THAN_ ONE_KA |
Explanation: A security violation occurred; more than one administrator is logged on at the same time.
| Reason code 83000 | FLG_SEVERR_SESSION_ ABENDED |
Explanation: Reserved
| Reason code 83001 | FLG_SEVERR_CDF_ERROR |
Explanation: Reserved
| Reason code 83002 | FLG_SEVERR_INTERNAL_ ERROR |
Explanation: Reserved
| Reason code 84000 | FLG_SEVERR_DEMO_EXPIRED |
Explanation: The evaluation period for IBM Information Catalog Manager Administrator has ended. Please contact the local software reseller or your IBM representative to order the product.
| Reason code 84101 | FLG_SEVERR_DB_CONNECT_ FAILED |
Explanation: Unable to connect to database. Refer to your database documentation for an explanation of the SQLCODE.
| Reason code 84102 | FLG_SEVERR_DB_BIND |
Explanation: Unable to bind the to the information catalog. The Information Catalog Manager has encountered an unexpected database error or cannot find the bind file in the current directory or path.
| Reason code 84103 | FLG_SEVERR_INSAUTH_BIND |
Explanation: You must have SYSADM authority to bind the to the information catalog.
| Reason code 84104 | FLG_SEVERR_CREATETAB |
Explanation: Unable to create the Information Catalog Manager system table.
| Reason code 84105 | FLG_SEVERR_INSAUTH_GRANT |
Explanation: You must have SYSADM authority to grant access to the information catalog.
| Reason code 84106 | FLG_SEVERR_ CREATECOLLECTION |
Explanation: The Information Catalog Manager failed to create a DB2 UDB for AS/400 library collection.
| Reason code 84107 | FLG_SEVERR_ICON_NOT_ GENERATED |
Explanation: The Information Catalog Manager has encountered a system error, or is unable to find the icon files or the executable file.
The Information Catalog Manager icons will not be generated.
| Reason code 84108 | FLG_SEVERR_DGCOL_ NOTEXIST |
Explanation: You must create the DB2 UDB for AS/400 library collection, DATAGUID, before invoking this utility.
| Reason code 84109 | FLG_SEVERR_DB_NOTFOUND |
Explanation: The Information Catalog Manager cannot find the specified database. Create the database if it does not exist. Then, register the remote database on your workstation.
Possible Extended Codes: None