Micro Focus Enterprise Developer 9.0 for Eclipse (UNIX)
Welcome
Product Overview
Existing Customers: Updating from an Earlier Release
New Features
New Features in Enterprise Developer 9.0
Features Added in Enterprise Developer 8.0
Features Added in Enterprise Developer 2.3 Update 2
Features Added in Enterprise Developer 2.3 Update 1
Features Added in Enterprise Developer 2.3
Features Added in Enterprise Developer 2.2 Update 2
Features Added in Enterprise Developer 2.2 Update 1
Features Added in Enterprise Developer 2.2
Features Added in Enterprise Developer 2.1 Update 1
Features Added in Enterprise Developer 2.1
Features Added in Enterprise Developer 2.0
Significant Changes in Behavior or Usage
New Customers: Where do I start?
New to Eclipse
Where do I start: Developer Tasks
Where do I start: Developing Mainframe Applications in Enterprise Developer
Where do I start: Deploying Mainframe Applications to Enterprise Server
New to COBOL
New to PL/I
New to Micro Focus Enterprise Developer UNIX Components
Upgrading from Mainframe Express
Upgrading from Net Express
Upgrading from Server Express
Upgrading from Studio Enterprise Edition
Want to deploy an application
Upgrading to Enterprise Developer
Licensing Changes
Resolving conflicts between reserved keywords and data item names
Importing Existing COBOL Code into Enterprise Developer
Recompile all source code
Upgrading from Mainframe Express to Enterprise Developer
Upgrading from Studio Enterprise Edition (Windows)
Upgrading from Server Express and Studio Enterprise Edition (UNIX)
Differences between Enterprise Developer and Server Express and Mainframe Express
Upgrading from ACUCOBOL-GT
Upgrading from RM/COBOL®
Overview of application development in Eclipse
Overview of Remote Mainframe Development
Enterprise Developer Tutorials Guide
Mainframe Tutorials
Tutorials: CICS
Tutorial: CICS Support
Tutorial: Web-enabled CICS Acting as a Web Server
Tutorial: Web-enabled CICS Acting as a Web Client
Tutorials: CICS Web Services
Tutorial: CICS Web Service Provider from WSDL, Top-down Method
Tutorial: CICS Web Service Requester from WSDL, Top-down Method
Tutorial: CICS Web Service Provider from WSDL, Bottom-up Method
Tutorial: CICS Web Service Provider from JSON, Request-Response Top-down Method
Tutorial: CICS Web Service Requester from JSON, Linkable Interface Top-down Method
Tutorial: CICS Web Service Provider from JSON, Request-Response Bottom-up Method
Tutorial: CICS Web Service Provider from JSON, RESTful
Tutorials: Application Migration using HCO for PostgreSQL
Tutorials: HCO for SQL Server (HCOSS)
Tutorials: IMS
Tutorial: JCL
Tutorials: Open PL/I
Native COBOL Tutorials
Tutorial: Creating a Native COBOL Application
Tutorial: Running Unit Tests in the IDE
Tutorials: Interface Mapping Toolkit
Tutorial: Using the Callable File Handler
Tutorials: JSON Processing
JVM COBOL Tutorials
Technology Preview Features
EAP Features
Enterprise Developer Editions and Activating Licenses
Product Information
Supported Operating Systems and Third-party Software
Additional Software Requirements
Installation
Installing Enterprise Developer for Eclipse (UNIX)
Installing Enterprise Developer Development Hub
Managing Licenses
Overview
To start Micro Focus License Administration
Configuring Micro Focus License Administration
Installing licenses
Installing licenses silently
Viewing installed licenses
Uninstalling licenses
Installing License Manager
Trial licenses
Subscription licenses
Usage Logging
Licensing Error Messages
Updates and Product Support
Micro Focus End User License Agreement
Known Issues and Restrictions
.NET
Application Server JCA Support
Application Workflow Manager
Audit Manager
Calling COBOL Programs from C
COBOL Programming
Compatibility
Containers
Installing on UNIX and Linux
Data Access
Debugging, Problem Determination and Diagnostic Tools
Documentation
Enterprise Server
Eclipse IDE
JVM COBOL Applications
Licensing
Mainframe Programming and Management
SSL and TLS
Remote Mainframe Development
Contacting Micro Focus
Sample Programs
Cheat Sheets
The Micro Focus Community
Help on Help
Developing Applications in the IDE
Starting Enterprise Developer
Introduction to Eclipse
Configuring Eclipse
Using Eclipse for COBOL Development
Creating COBOL projects
Creating and importing COBOL projects
Creating and importing resources
Using source files from outside your project
Using custom project and file templates
Identifying COBOL copybooks and programs
Configuring the project, build configuration, folder and file properties
Building COBOL applications
Developing applications on remote machines
Java Interoperability within the IDE
Preparing files for deployment
Code coverage (native COBOL)
Code Analysis
Debugging COBOL Applications
Debugging Scenarios
Starting the debugger automatically
Debugging using a core dump
Debugging using a live recording
Debugging using a remote machine
Debugging CICS channels and containers
Debugging mixed language applications
Debugging on Enterprise Server Scenarios
Debugging Enterprise Server services and applications using a live recording
Debugging outside of Eclipse
The Character Animator
Overview of Character Animator Functions
Working With Character Animator
Directives for Character Animator
Cross-session Debugging
Using cobesdebug to Debug Services and Applications on Enterprise Server
Overview of the debugging process
Preparing projects for debugging
Debugging features and techniques in Eclipse
Code Refactoring
Running COBOL applications
Working with Apache Maven
COBOL Applications for .NET
Using Eclipse for PL/I development
PL/I Perspective and Projects
The PL/I Editor
Configuring the PL/I Editor
Creating a PL/I project
Creating Remote PL/I Projects
Setting PL/I Project, File and Build Configuration Settings
Indicating That a .pli File is a Source File
Extracting PL/I code to an include file
Compiling and building a PL/I project
Linking PL/I programs
Code Coverage (PL/I)
Debugging PL/I projects
Running a PL/I application
Using Enterprise Server from within the IDE
Modern Development Practices
Using Enterprise Developer in Modern Application Development
Using Enterprise Developer with Jenkins
Using Enterprise Developer with Containers
Introduction to Containers
Benefits of Using Containers
Container Terminology
Getting Ready to Use Enterprise Developer with Containers
Key Concepts When Using Containers for COBOL Application Development
Building Images for COBOL Applications
Debugging and Running COBOL Applications in Containers
Debugging and Running PL/I Applications in Containers
Container Demonstrations
Programming
COBOL Programming
What is COBOL?
History of COBOL
Learn COBOL
Glossary
Calling COBOL Programs
JVM COBOL Programming
Native COBOL Compared to JVM COBOL
Introduction to Object-Oriented Programming for COBOL Developers
Moving Native COBOL Applications to JVM COBOL
Compiling and Calling JVM COBOL Applications as Part of a Package
64-bit applications in the Java environment
Using a File Handler in JVM COBOL
Multiple user COBOL applications in Java
Interoperability
Exposing COBOL as Web Services
Java and COBOL Interoperability
Java and OO COBOL Interoperability
Java and OO COBOL Interoperability Options
Considerations
Deploying a Java Service Interface and Using Resource Adapters
Calling Procedural COBOL from Java
Calling Java from Native OO COBOL
Calling Native OO COBOL from Java
Java Data Types
Micro Focus COBOL Java Class Library
JVM COBOL Interoperating with Java
Java and non-OO COBOL Interoperability
Internationalization Support
Preparing Applications for Enterprise Server
Interface Mapping Toolkit (IMTK)
Managing IMTK Projects
Defining Service Interfaces
Deploying Service Interfaces
Clients
How to
Reference
Mixed Language Programming
Ordering Parameters to Pass to Non-COBOL Programs
Removing Parameters from the Stack
Storage Representation of Parameters
Aligning Parameters on Word and Double Word Boundaries
Handling Return Codes in Mixed Language Applications
Call Conventions for Interfacing with Mixed Languages
Building a Mixed Language Application
Interfacing with C Programs
Avoiding data name conflicts
Calling a COBOL Entry Point Directly
Passing Data between C and COBOL
Header-to-COPY Utility
Overview
Converting Header Files Using the H2cpy Utility
Overview - H2cpy Messages
Warning Messages
Error Messages - Command Line Errors
Error Messages - Invalid C Source
Calling COBOL Programs from C
Error Messages when Calling Non-COBOL Programs
Signal Handling
Examples of Mixed Language Programming
Using COBOL and XML together
XML Extensions
Installation and introduction
Getting started with XML Extensions
XML Extensions statements reference
COBOL considerations
XML considerations
Appendix A XML Extensions examples
Example 1 Import file and export file
Example 2 Export file and import file with XSLT stylesheets
Example 3 Export file and import file with OCCURS DEPENDING
Example 4 Export file and import file with sparse arrays
Example 5 Export and import text
Example 6 Export file and import file with directory polling
Example 7 Export file, test well-formed file, and validate file
Example 8 Export text, test well-formed text, and validate text
Example 9 Export file, transform file, and import file
Example 10 Diagnostic messages
Example 11 Import file with missing intermediate parent names
Example batch files
Appendix B: XML Extensions sample application programs
Appendix C: XML Extensions error messages
XML Syntax Extensions
Generating COBOL Structures with XML Syntax from the Command Line
XML PARSE
Glossary of terms
64-bit Native COBOL Programming
Embedded HTML
Compatibility
Compatibility with ACUCOBOL-GT
Converting ACUCOBOL-GT Applications
ACUCOBOL-GT File Handling
ACUCOBOL-GT Library Routines
ACUCOBOL-GT Windowing Syntax
Compatibility with DG Interactive COBOL
Compatibility with RM/COBOL
Converting RM/COBOL Applications
Configuring Your Application for Eclipse
Compiler Directives for RM/COBOL Compatibility
Compiling RM/COBOL Programs Without DIALECT"RM"
RM/COBOL Data Types
RM/COBOL Conversion Issues
RM/COBOL Library Routines
RM/COBOL File Handling
RM/Panels
Restrictions and Limitations
Converting RM/Panels Applications
Conversion Example: Using Eclipse
Writing Programs
Appendix A: Master Copy File RMPANELS.WS
Appendix B Standard Utility, and Extended Run-time Functions and Parameters
Compatibility with XML Extensions
Native OO COBOL Class Library Reference
Data Access
Database Access
Accessing Databases from COBOL
Database Access Features
Database Access Preprocessors
Developing SQL Applications
Compiling SQL Applications
OpenESQL
COBSQL
How to
Reference
EXEC SQL Statement
OpenESQL
Embedded SQL Statements
SQL Compiler Directive Options
DBMAN Directive Settings
JDBC Driver Classes
JDBC URLs
Sample DataSource Object Files
SQL/COBOL Data Type Mappings
MF_ERRORMAP_PATH
OpenESQL Messages
SQLSTATE Values
SQLCODE Values
OpenESQL Preprocessor Error Messages
COBES0002 token is badly defined.
COBES0003 Program contains more than one definition of token
COBES0004 Nested or multi-source programs not allowed.
COBES0005 An error occurred when processing the internal dictionary.
COBES0006 No DB engine could be found.
COBES0007 Source file name is invalid.
COBES0010 OESQL rejected an unspecified option.
COBES0022 The directive SQL(DBMAN=ODBC) is not supported under Personal Edition.
COBES0023 The SQL(DBMAN) directive option is not supported with native applications.
COBES0024 The SQL(DBMAN) directive option is not supported with JDBC applications.
COBES0100 SQL incompatible with MAINFRAME
COBES0101 Statement is too long.
COBES0102 Statement contains too many host variables.
COBES0103 token does not have a suitable definition to be used as a host variable.
COBES0104 Bad SQL data declaration.
COBES0105 Syntax error.
COBES0106 Filename too long.
COBES0107 File token not found.
COBES0108 token is not unique and should be qualified.
COBES0109 token is not a data item.
COBES0110 Statement contains more than one SQLDA.
COBES0111 token is not a table of null indicator variables.
COBES0112 variable should not be defined with an OCCURS clause.
COBES0113 token should not be a subordinate to an item defined with an OCCURS clause.
COBES0114 Statement only allowed in the Procedure Division.
COBES0115 Statement not allowed in the Procedure Division.
COBES0116 An error occurred when processing the trace file.
COBES0118 Mismatched DECLARE.
COBES0119 Host variable name is too long.
COBES0120 Internal error - dictionary handle is too big.
COBES0121 Compiler directive SQL (token1=token2) is invalid or badly sequenced - all SQL statements ignored.
COBES0123 Invalid ILTARGET - cannot use ILTARGET(ANYCPU) - must specify ILTARGET(X86) or ILTARGET(X64).
COBES0124 Host or Indicator Variable varname should not be defined in EXEC SQL statement using a subscript.
COBES0125 variable should be defined with an OCCURS clause.
COBES0130 Host variable host-var.group-var is part of a group variable expansion that is not supported in this type of SQL statement.
COBES0201 BEHAVIOR directive not valid unless TARGETDB directive of DB2, ORACLE, or MSSQLSERVER set first.
COBES0202 BEHAVIOR directive not set.
COBES0203 PREFETCH and BEHAVIOR directives are mutually exclusive - cannot set both.
COBES0205 Cannot set directive PF_RO_CURSOR > 1 if RO_CURSOR directive is set to IC_FH.
COBES0206 Cannot set directive PF_RO_CURSOR > 1 if RO_CURSOR directive is set to FORWARD and TARGETDB is MSSQLSERVER.
COBES0207 Cannot set directive PF_UPD_CURSOR > 1 if UPD_CURSOR directive is set to FORWARD.
COBES0208 Cannot set UPD_CURSOR directive to DYNAMIC if TARGETDB directive is set to ORACLE.
COBES0209 Cannot set UPD_CURSOR directive to STATIC if TARGETDB directive is set to MSSQLSERVER.
COBES0211 DBRMLIB name is too long, max 44 characters.
COBES0212 Simple name in DBRMLIB name is too long, max 8 characters.
COBES0213 Simple name in DBRMLIB name starts with invalid character.
COBES0214 Invalid character in DBRMLIB name.
COBES0215 MEMBER name is too long, max 8 characters.
COBES0216 MEMBER name cannot begin with a numeric digit.
COBES0217 Invalid character in MEMBER name.
COBES0218 MEMBER directive not valid unless DBRMLIB directive set.
COBES0219 VERSION directive not valid unless DBRMLIB directive set.
COBES0220 VERSION is too long, max 64 characters.
COBES0221 Invalid character in VERSION.
COBES0222 Invalid Framework target - SQL applications must be built to target the 4.0 .NET Framework.
COBES0223 TARGETDB directive not set.
COBES0900 An internal error occurred.
COBES0901 This error prevents SQL processing from continuing - further EXEC SQL statements will be ignored.
COBES1000W Use of EXEC SQL INCLUDE SQLCA END-EXEC
COBES1002 Statement is not in area B.
COBES1004 token directive is not supported and has been ignored.
DSNTIAR and DSNTIAC
esqlconfig command
COBSQL
PREPROCESS(cobsql)
COBOL Directives
COBSQL Compiler Directive Options
COBSQL Messages
CSQL-I-001 to CSQL-E-023
CSQL-E-024 to CSQL-F-050
SQL Data Types
SQL TYPEs
Data Structures
Keywords
Data Files
Data File Tools
Data File Editor
Data File Structure Command Line Utility
Rebuild
Data Modernization
Database Connectors for Enterprise Developer
Database Connectors User's Guide
Database Connectors Overview
Getting Started
XFDs
Using XFD Directives
Invalid Data
Working with COBOL
New and Existing Databases
File Handling Configuration
Run Time System Configuration
Database Connectors for DB2
Database Connectors for Microsoft SQL Server
Database Connectors for ODBC
Database Connectors for Oracle
Performance and Troubleshooting
Questions and Answers
Database Connectors Tasks
Database Connectors Reference
Configuration Variables
4GL_2000_CUTOFF
4GL_8_DIGIT_CUTOFF
4GL_COLUMN_CASE
4GL_COMMIT_COUNT
4GL_CONVERT_DATE_ZERO
4GL_DB_MAP
4GL_FULL_DATA_TEST
4GL_IGNORED_SUFFIX_LIST
4GL_ILLEGAL_DATA
4GL_JULIAN_BASE_DATE
4GL_WHERE_CONSTRAINT
A_DB2_ALTERNATE_COMMIT_LOGIC
A_DB2_CATALOG
A_DB2_COMMIT_ON_BEGIN
A_DB2_DATASOURCE
A_DB2_ERROR_MAP_FILE
A_DB2_ISOLATION_LEVEL
A_DB2_LOCK_METHOD
A_DB2_LOGIN
A_DB2_PASSWD
A_DB2_STRICT_EQUAL
A_DB2_TABLE_TYPES
A_DB2_USE_CATALOG
A_DB2_USE_CHAR_FOR_BINARY
A_MSSQL_ADD_IDENTITY
A_MSSQL_ADD_TIMESTAMP
A_MSSQL_APPROLE_NAME
A_MSSQL_APPROLE_PASSWD
A_MSSQL_CREATE_UNICODE_COLUMNS
A_MSSQL_CURSOR_OPTION_1,2,3
A_MSSQL_DATABASE
A_MSSQL_DEADLOCK_LOOPS
A_MSSQL_DEFAULT_CONNECTION
A_MSSQL_DEFAULT_OWNER
A_MSSQL_DO_NOT_TRANSLATE_CHAR
A_MSSQL_ENCRYPT_CONNECTION
A_MSSQL_EXTRA_CONNECTION_INFO
A_MSSQL_FAILOVER_PARTNER
A_MSSQL_FAILOVER_PARTNER_SPN
A_MSSQL_FAST_ACCESS
A_MSSQL_GRANT_PERMISSIONS
A_MSSQL_GRANT_USERNAME
A_MSSQL_IDENTITY_TYPE
A_MSSQL_IGNORE_GUID_COLUMNS
A_MSSQL_LIMIT_DROPDOWN
A_MSSQL_LOCK_DB
A_MSSQL_LOGIN
A_MSSQL_MAX_BINARY_LENGTH
A_MSSQL_MAX_CHAR_LENGTH
A_MSSQL_MAX_CHARACTERS
A_MSSQL_MAX_COLUMNS
A_MSSQL_MULTI_SUBNET_FAILOVER
A_MSSQL_NATIVE_LOCK_TIMEOUT
A_MSSQL_NO_23_ON_START
A_MSSQL_NO_CACHED_READ
A_MSSQL_NO_COUNT_CHECK
A_MSSQL_NO_DBID
A_MSSQL_NO_RECORD_LOCKS
A_MSSQL_NO_TABLE_LOCKS
A_MSSQL_ODBC_DRIVER_NAME
A_MSSQL_PACKETSIZE
A_MSSQL_PASSWD
A_MSSQL_ROWCOUNT
A_MSSQL_SELECT_KEY_ONLY
A_MSSQL_SEPARATE_LOCK_CONN
A_MSSQL_SERVER_SPN
A_MSSQL_SKIP_ALTERNATE_KEYS
A_MSSQL_STRIP_PATH_INFO
A_MSSQL_TRANSACTION_LEVEL
A_MSSQL_TRANSLATE_TO_ANSI
A_MSSQL_TRUST_SERVER_CERTIFICATE
A_MSSQL_UNLOCK_ON_EXECUTE
A_MSSQL_UPDATE_PRIMARY_COLS
A_MSSQL_USE_DROPDOWN_QUERIES
A_ODBC_ALTERNATE_COMMIT_LOGIC
A_ODBC_CATALOG
A_ODBC_COMMIT_ON_BEGIN
A_ODBC_DATASOURCE
A_ODBC_ERROR_MAP_FILE
A_ODBC_ISOLATION_LEVEL
A_ODBC_LOCK_METHOD
A_ODBC_LOGIN
A_ODBC_MAX_COLUMNNAME_LEN
A_ODBC_MAX_TABLENAME_LEN
A_ODBC_NO_NULL_COLUMNS
A_ODBC_PASSWD
A_ODBC_PRINT_LOG
A_ODBC_QUOTE_IDENTIFIERS
A_ODBC_STRICT_EQUAL
A_ODBC_TABLE_TYPES
A_ODBC_UNSIGNED_TINYINT
A_ODBC_USE_CATALOG
A_ODBC_USE_CHAR_FOR_BINARY
A_ODBC_USE_SPACE_IN_DATES
A_ODBC_USE_SQLCOLUMNS
A_ODBC_USE_SQLTABLES
A_ORA_DATABASE
A_ORA_HINTS
A_ORA_KEEP_START_CURSOR
A_ORA_LIMIT_DROPDOWN
A_ORA_MAX_FILE_CURSORS
A_ORA_NLS_SORT
A_ORA_WAIT_LOCK
A_ORACLE_ERROR_FILE
COMMIT_COUNT
FILE_TRACE
FILE TRACE FLUSH
LOCKS_PER_FILE
ORA_LOGIN
ORA_PASSWD
MAX_FILES
MAX_LOCKS
USER_PATH (for Oracle)
USER_PATH (for DB2)
XFD_DIRECTORY
XFD_MAP
XFD_MAP_RESETS
XFD_PREFIX
Database Connectors Error Messages
XFD Directives
Compiler Directives Affecting XFD Creation
File Handling
File Handling Examples
Data and Key Compression Example
External Files Example
File Handler Examples
File Names Examples
File Status Examples
Indexed File Examples
MFSORT Examples
Rebuild Examples
Relative File Definition Example
Sequential File Examples
File Handling Guide
Introduction
File Organizations
File names
File Status
Sharing Files
File Handler Configuration
File Handler and Sort APIs
Sort Utilities
Data and Key Compression
Tracing File Operations
File Systems
Fileshare Guide
Introduction
Standard Operation
Configuring CCI Communications for Fileshare
Database Integrity
Security
Advanced Operation
Error Handling
Fileshare Server Messages
Messages from FS001-S to FS050-W
FS001-S The parameter "text " is not recognized as a valid parameter.
FS004-S The parameter "text " specifies a time-out value that is invalid.
FS005-S The parameter "text " is too long or invalid.
FS006-S The parameter "text " has already been specified.
FS007-S Invalid parameter combination.
FS008-S Communications Initialization Failure.
FS009-S The required communications module cannot be found.
FS011-W Communications send failure.
FS012-W Communications disconnect failure.
FS013-W Communications receive error.
FS014-W Communications data length not as expected.
FS015-W Request from unknown user - request rejected.
FS016-S The parameter "text " is invalid.
FS017-S Unable to open the file : filename.
FS018-S Log file corrupt - unrecognizable record in file.
FS019-S Log file corrupt - can't read header.
FS020-S The log file does not match the database sequence numbers - recovery aborted.
FS021-S There is no log filename specified in the database reference file.
FS022-S The log filename given cannot be found in the database reference file.
FS024-S Failed to open log file : filename.
FS025-S Write failure to the log file, Fileshare Server is closing down.
FS026-W Failed to close the log file.
FS027-S A second log file parameter has been found.
FS028-W The log file shows the last session was not shut down successfully.
FS029-S The log filename is already specified in the database reference file.
FS030-S Insufficient disk space to continue logging to log file.
FS031-I Record lock time-out failure on user : user.
FS034-S A filename or log file parameter must be specified.
FS035-S A database reference file must be specified.
FS037-I The file filename does not have a file header record. Sequence checking is switched off for this file.
FS038-S A matching sequence number not found in filename.
FS039-S Improperly closed file - filename.
FS040-S Unable to read the file header record in the file filename.
FS041-S Unable to update the sequence number in the file filename.
FS042-S Unable to open the database reference file: filename.
FS043-S The database reference file contains an invalid entry.
FS044-S Error reading the database reference file.
FS045-W Duplicate filename specified in the database reference file.
FS050-W A log file is not specified in the database reference file.
Messages from FS051-W to FS099-W
FS051-W Failure to allocate a larger buffer, the I-O request failed.
FS052-S Failure to allocate required memory. The Fileshare Server is closing down.
FS055-S The parameter "text " specifies a configuration file that does not exist.
FS056-S The parameter "text " specifies a data compression value that is not within the range 0-255.
FS057-S The parameter "text " specifies a key compression value that is not within the range 0-7.
FS058-S Failure to allocate memory for the decompression of the log file.
FS059-S Failure to allocate the memory required for processing the database reference file.
FS062-S Failure creating the password file filename.
FS063-S Failure opening the password file filename.
FS064-S Failure reading the password file filename.
FS065-S The password file is not of a recognized format.
FS066-S The specified user name already exists in the password file.
FS068-I The password file is now empty and has been deleted.
FS069-S The specified entry could not be found in the password file.
FS070-S Failure writing to the password file.
FS071-W Unable to load the module FHXSCOMP to decompress the data area.
FS072-S The parameter "text " contains a wild card which is not allowed with this parameter.
FS073-S Failure to allocate memory to process the password file.
FS074-S The Fileshare Server (NLM) failed to log on to NetWare with the login id specified.
FS075-W Unable to load the module FSSECLOG - LOGON has been denied.
FS076-W Unable to load the module FSSECOPN - OPEN has been denied.
FS077-S A Fileshare Server of the same name has already been defined - the Fileshare Server is closing down.
FS078-S No password file has been specified for the use of background mode.
FS079-S A supervisor password entry must exist for the use of background mode.
FS080-S No password file has been specified for the use of the synchronous communications mode.
FS081-S A supervisor password must be specified in the password file for the synchronous communications mode.
FS082-S The Netbios communications protocol is not responding. Ensure the requester software is loaded and functional.
FS083-S Incompatible CCIIPX.NLM version.
FS084-I Fileshare Server is starting.
FS085-I Fileshare Server is active.
FS086-I Fileshare Server is closing down.
FS087-I Fileshare Server has closed down.
FS089-I Database Reference File Maintenance Utility.
FS090-I Database Reference File installation completed successfully.
FS091-I Rollforward Recovery Utility
FS092-I Rollforward Recovery has completed.
FS094-I Password File Maintenance Utility.
FS096-I Password File installation has completed.
FS097-I Are you sure that you wish to close down the Fileshare Server ? (Y/N)
FS099-W File I/O status was not as expected. Returned status: status Expected status: status Action code: text File: filename.
Messages from FS101-I to FS149-I
FS101-I text -- parameter has been accepted.
FS103-I The log filename has been added to the database reference file.
FS104-I The log file cannot be found, creating a new recovery log file.
FS105-W The disk free space for the log file is below acceptable limits.
FS106-I filename - added to database reference file.
FS107-I filename - removed from the database reference file.
FS108-I Processing the files specified in the database reference file.
FS109-W The file filename does not exist.
FS110-I filename - OK.
FS111-W Files are still open. Continue to close down the Fileshare Server (Y/N) ?
FS114-W Waiting for the old log file to be removed.
FS118-I The database sequence number matches the sequence number in the log file, no recovery is needed.
FS122-I Communications too busy on CCI SEND - retrying.
FS123-I Communications too busy on CCI RECEIVE - retrying.
FS124-I Checking the validity of the log file, please wait.
FS125-I Recovery possible to last valid recovery log file record.
FS126-I Performing recovery, please wait.
FS127-S Invalid name mapping command.
FS128-W Fileshare Server closedown invoked by Stop Run processing.
FS129-I The Fileshare Server is still active.
FS130-I Reading database reference file, please wait.
FS131-W Invalid communications mode - parameter ignored.
FS132-I The Fileshare Server is running with the following communication protocol(s):
FS133-I Processing the password file, please wait.
FS134-I The password file cannot be found - creating a new password file.
FS135-I Fileshare Server security is active.
FS136-I Fileshare Server security is not active.
FS138-W The log file has been backed up and a new one has been created.
FS139-I A matching date and time entry has been found in the log file.
FS140-I No matching date and time entry has been found in the log file.
FS142-W The Operating System does not permit the log file to be flushed to disk.
FS143-W The Operating System does not allow free disk space information to be obtained.
FS144-W More than one communications protocol has been specified - synchronous communications mode not active.
FS145-W Fileshare Client disconnected, cannot contact user: text.
FS146-W Unexpected action code, action-code - discarded.
FS147-I A duplicate network message was received and discarded.
FS148-I CCI return-code (function func) = code.
FS149-I CCI SEND not complete, status will be checked later.
Messages from FS151-I to FS200-W
FS151-I CCI message size received = text. Indicated send message size = text
FS153-I The Fileshare Server name has been reregistered on the network.
FS154-I Please enter the FSVIEW supervisor password to enable the use of CCI Trace.
FS155-I Password accepted - CCI Trace is enabled. Do you want CCI Trace active immediately? (Y/N)
FS156-W Incorrect password - CCI Trace is disabled.
FS158-I CCI Trace activated.
FS159-I CCI Trace switched off.
FS160-I Fileshare trace activated.
FS161-I Fileshare trace switched off.
FS163-I Input useropcode [filename-1] [ filename-2].
FS170-I Input- Logon.
FS171-I Input- Logoff user.
FS172-I Input- Find File userfilename.
FS173-I Output- userstatus.
FS176-W There is no backup directory specified in the database reference file.
FS177-S The backup directory specified cannot be found in the database reference file.
FS178-I The backup directory has been added to the database reference file.
FS179-S A backup directory is already specified in the database reference file.
FS180-W The log filename specified has an extension. The name of the log file has been changed to "filename".
FS182-W Output- Access Denied
FS188-W Fileshare Server database reference file installation completed with errors.
FS189-W The backup directory does not exist.
FS190-W The backup directory specifies the name of an existing file.
FS191-W An error occurred accessing the backup directory.
FS192-S More than one log file exists in the log file directory.
FS193-S Unable to open the log file.
FS194-I The log file "filename-1" has been backed up successfully to "filename-2".
FS195-I The Fileshare Server is using the log file "filename".
FS196-W Unable to create the log file "filename".
FS197-S Unable to create the log file "filename".
FS198-W The attempt to backup the log file failed because the backup file "filename" already exists.
FS199-S The attempt to backup the log file failed because the backup file "filename" already exists.
FS200-W The attempt to backup the log file to "filename" failed.
Messages from FS201 to FS300
FS201-S The attempt to backup the log file to "filename" failed.
FS202-I The Fileshare Server will continue logging to the log file "filename".
FS203-I The Fileshare Server is appending to the log file "filename".
FS204-W The Fileshare Server is unable to log to the log file "filename". Rollforward recovery logging is disabled.
FS205-W Unable to remove the old recovery log file "filename".
FS206-S There is more than one starter log file. The Recovery Utility is unable to determine which one to use.
FS207-I There is no starter log file in the log file directory.
FS208-S There is no starter log file in the backup directory.
FS209-I A starter log file has been located in the backup directory.
FS210-S There is more than one starter log file in the backup directory.
FS211-S An error occurred checking the header on the log file "filename".
FS212-I The Rollforward Recovery Utility is processing the log file "filename".
FS213-W Unable to locate the continuation log file "filename" in the log file directory.
FS214-I Searching for a backed up log file in the log file directory.
FS215-I Searching for a backed up log file in the backup directory.
FS216-I No backed up starter log file can be found in the log file directory.
FS217-I No backed up starter log file can be found in the backup directory.
FS218-I No backed up continuation log file can be found in the log file directory.
FS219-I No backed up continuation log file can be found in the backup directory.
FS220-I A backed up starter log file has been found in the log file directory.
FS221-I A backed up starter log file has been found in the backup directory.
FS222-I A backed up continuation log file has been found in the log file directory.
FS223-I A backed up continuation log file has been found in the backup directory.
FS224-S The log file directory contains more than one backed up starter log file.
FS225-S The backup directory contains more than one backed up starter log file.
FS227-W Failure to set Fileshare Server's access rights.
FS228-I CCI SEND status checked.
FS229-I Unrecognized CCI session ID - could not disconnect user.
FS230-I User : user-IDuser-name
FS231-S The parameter "nnn" is not numeric.
FS232-I Date : date.
FS233-W Unable to set the maximum amount of dynamic memory to the limit specified
FS234-W The parameter "text " specifies a memory limit below the minimum of 6 Mbytes allowed.
FS235-W Failure to allocate memory for incomplete CCI SEND processing.
FS236-I The log file name has been removed from the database reference file.
FS237-S The next log file to use filename already exists, unable to back up current log file.
FS237-W The next log file to use filename already exists, unable to back up current log file.
FS238-I Terminating communications with this user.
FS239-I Output - user Record locked. Retry operation.
FS240-I Output - user File locked. Retry operation.
FS241-I Output - user Insufficient log file disk space. Retry operation.
FS243-S Failure backing up the file filename1 to filename2.
FS244-S Failure restoring the backed up file filename1 to filename2.
FS245-S Failure deleting the log file filename.
FS246-I Backing up database files to directory backup directory. Please wait.
FS247-I Restoring database files from directory backup directory. Please wait.
FS248-I Commencing automatic Fileshare Recovery.
FS249-I Restarting Fileshare Server.
FS250-I Deleting all unwanted log files.
FS251-S Logging must be activated for all files when specifying a backup directory.
FS252-S Failure deleting the file filename.
Messages from FS301 - FS400
Micro Focus Native Database File Handling and Enterprise Server Region Database Management
System Requirements
Types of Database
Database Permissions
Configuration Requirements
Using Microsoft SQL Server
Using Microsoft Azure
Using PostgreSQL
Using Db2
Using Oracle
Configuring CICS Applications for Native Database File Handling
Configuring the JCL Environment for Native Database File Handling
The Database Configuration File
Database Connections
Datastore Management
Database Management and Recovery
File View Generation
Resource Locking
Record Locking Strategies
MFDBFH Error Messages
ADM - DBFHADMIN Messages
ADM0000 - ADM0019
ADM0020 - ADM0039
ADM0040 - ADM0059
ADM0060 - ADM0079
ADM0080 - ADM0099
ADM0100 - ADM0119
CFG - MFDBFH Configuration Messages
CFG0000 - CFG0019
CFG00040 - CFG00059
CFG0000 - CFG0019
CFG0020 - CFG0039
CFG0040 - CFG0059
DBFH - MFDBFH General Messages
DBFH00000 - DBFH00019
DBFH00020 - DBFH00039
DBFH00020S Failed to load 'odbc-oci-db2-api-load-library'
DBFH00021I Successfully registered XA connection 'xa-connection-name' for datastore 'datastore-url'
DBFH00022I Successfully de-registered XA connection 'xa-connection-name' for datastore 'datastore-url'
DBFH00023I Build svn-tag, svn-revision
DBFH00024S Failed to load Secrets/Vault API
DBFH00025W Failed to read secret from the vault for attribute 'attr-name' (RC=return-code): Server=server-name; Dsn=dsn-name
DBFH00026E db-api-type error: 'odbc-oci-error-message'
DBFH00027E I/O error: io-error-message
DBFH00028W Configuration file 'configuration-file-name' does not exist
DBFH00029W SQL script file folder 'script-file-folder-name' does not exist
DBFH00030E Required stored procedure 'stored-procedure-name' does not exist
DBFH00031W The region must be cold started
DBFH00032S MFDBFH requires the multi-threaded COBOL run-time system
DBFH00033S SQL script file 'sql-script-file-name' does not exist
DBFH00034S MFDBFH failed to upgrade the datastore. Manual upgrade required. Use 'dbfhadmin -upgrade -datastore datastore-url' to generate an upgrade script and run the script as a user with sysadmin privileges
DBFH00035W Record lock strategy changed for file 'sql-url' Already opened by PID process-id on host 'host-name' with 'existing-record-lock-strategy'. Requested 'requested-record-lock-strategy'
DBFH00036E Cannot cold start region database 'region-database-name' Already started by 'program-name (PID process-id)' on host 'host-name'
DBFH00037E Cannot warm start region database 'region-database-name' Already started by 'program-name (PID process-id)' on host 'host-name'
DBFH00038E Cannot stop region database 'region-database-name'. Not started
DBFH00039W Force cold start of region database 'region-database-name' Already started by 'program-name (PID process-id)' on host 'host-name'
DBFH00040 - DBFH00059
DBFH0080 - DBFH0099
DEP - DBFHDEPLOY Messages
DEP0000 - DEP0019
DEP0020 - DEP0039
DEP0040 - DEP0059
DEP0100 - DEP0119
VGN - DBFHVIEW Messages
VGN0000 - VGN0019
VGN0020 - VGN0039
MFDBFH
MQSeries
Mainframe Programming
Mainframe Subsystem Support Developer Introduction
CICS Support
Mainframe-style Pointers
Forcing a Program to be Reloaded
Accessing Large VSAM Files
Abend Codes in CICS Transactions
Using the SET Option of the BMS-related SEND Functions
Developing Exit Programs
CICS Web Services
Demonstration Applications
Configuration Requirements for CICS Web Services
CCSID Conversion Tables
CICS Web Service Types and Methods
CWS Security
New CICS Web Service Wizard
Validating Your Enterprise Server Instance Configuration
Troubleshooting
How to
Reference
HCO for DB2 LUW
Demonstration Applications
DB2 External Compiler Module
COBOL DB2 Stored Procedures
Host Compatibility Option (HCO)
How to
Reference
DB2 Compiler Directive Options
DB2 Environment Variables
DB2 ECM Error Messages
COBDB0002 - COBDB0013
COBDB0100 - COBDB0115
COBDB0116 - COBDB0137
COBDB0501 - COBDB0503
COBDB0900 - COBDB1004
HCO Tools
HCO for PostgreSQL (HCOPG)
HCO for SQL Server (HCOSS)
IMS Support
IMS DB Compatible Production DBMS
IMS TM Compatible Transaction Manager
IMS Installation Verification Procedure (IVP)
Developing IMS Applications
Deploying IMS Applications
Creating and Configuring an Enterprise Server Region for IMS
IMS Database Administration
WebSphere MQ Support
Advanced Database Administration
How to
IMS Projects
IMS Segment Layout Editor
IMS Database Editor
IMS Enterprise Server Configuration
To create an IMS-enabled enterprise server from the IDE
To create an MSS-enabled enterprise server for IMS applications from Enterprise Server
To enable MSS for an existing enterprise server
To enable IMS for an MSS-enabled enterprise server
To specify the location of generated files
To specify the location of application files
To define a message processing region
To enable IMS Connect
To define how MFS attributes are coded
To define the MFS null character
To run an IMS transaction from a 3270 session
To start a temporary MPR
To perform a cold start
Message Queue
Printers
Resources
Transactions
WebSphere MQ
Reference
DBD, PSB, and MFS Statements
DBUTIL
EXEC DLI Statements
IMS DB system commands
IMS DB system command interfaces
IMS Database Control (DBC) Commands
MFDBUJCL Utility
IMS Error Messages
DBD Error Messages
Messages DBDUT0401 to DBDUT0417
Messages DBDUT04A1 to DBDUT04A7
Messages DBDUT04E1 to DBDUT04E2
Messages DBDUT0801 to DBDUT0882
DBDUT0801E SEGM macro not preceded by DBD macro. DBD macro must be first statement in DBD source
DBDUT0802E DBD macro missing required NAME operand
DBDUT0803E HDAM or DEDB database missing required RMNAME operand
DBDUT0804E PARENT segment parentsegname for segment segname not previously defined in this database
DBDUT0805E Source segment segname for XDFLD fldname not defined
DBDUT0806E SEGM macro missing required NAME operand
DBDUT0807E Missing required DBDGEN statement
DBDUT0808E SEGM segname has missing or invalid BYTES operand
DBDUT0809E SEGM segname, minimum bytes (nnnn) exceeds maximum bytes (nnnn)
DBDUT0810E DEDB root segment segname, field fldname not unique
DBDUT0811E Non-related MSDB segment segname, field fldname not unique
DBDUT0812E INDEX DBD segment segname must contain a sequence field. Field fldname not a sequence field
DBDUT0813E FIELD macro not preceded by SEGM macro
DBDUT0814E Segment segname, FIELD macro missing required NAME operand
DBDUT0815E SEGM segname, FIELD fldname, contains invalid data in name parameter, 3rd operand xxxxxxxx
DBDUT0816E DEDB sequential dependent segment segname contains invalid sequence field fldname
DBDUT0817E SEGM segname, FIELD fldname contains invalid data in name parameter, 2nd operand xxxx not SEQ
DBDUT0818E Segment segname, sequence field fldname must be first field after SEGM for IMS/ESA compatibility. Use system config, IBM DLI PLATFORM setting for DOS/VS syntax
DBDUT0819E COPY statement missing required name parameter
DBDUT0820E COPY member copymember not found
DBDUT0821E Segment segname, field fldname not unique
DBDUT0822E Segment segname, field fldname packed length cannot exceed 16 bytes
DBDUT0823E Segment segname, field fldname, BYTES operand missing or invalid
DBDUT0824E Segment segname, field fldname missing required START operand
DBDUT0825E Field fldname extends beyond segment maximum size of nnnnn, field start nnnnn, length nnnnn
DBDUT0826E Segment name segname not unique within this DBD
DBDUT0827E accesstype ACCESS type requires DATASET DD1 operand when DATASET does not have a label
DBDUT0828E DATASET SCAN value of nnnnn, exceeds maximum of 255
DBDUT0829E DATASET FRSPC (free block frequency) of nnnnn must be in range of zero to 100, but not 1
DBDUT0830E DATASET FRSPC percentage of nnn must be in range of 0 to 99
DBDUT0831E LOGICAL DATASET not valid with ACCESS accesstype
DBDUT0832E MSDB missing required DATASET REL operand
DBDUT0833E Only 1 SEGM statement allowed in MSDB database
DBDUT0834E SEGM segname missing required PARENT operand
DBDUT0835E Segment segname, length nnnnnn exceeds maximum segment length of 32760
DBDUT0836E Segment segname level is deeper than 15, parent segment parentsegment
DBDUT0837E DBD ACCESS accesstype does not support Virtual segments
DBDUT0838E LCHILD missing required segment NAME operand
DBDUT0839E LCHILD segment operand dbdname missing required DBD NAME operand in index DBD
DBDUT0840E LCHILD PAIR operand not supported with ACCESS accesstype
DBDUT0841E XDFLD statement not supported with ACCESS accesstype
DBDUT0842E GSAM DATASET macro missing required RECFM operand
DBDUT0843E Missing required DBD macro statement
DBDUT0844E SEGM statement not found, DBD requires at least one
DBDUT0845E Paired segment segname not found in DBD or occurred more than once
DBDUT0846E Index DBD can contain only one LCHILD statement
DBDUT0847E Index DBD missing required LCHILD statement
DBDUT0848E XDFLD missing required NAME operand
DBDUT0849E XDFLD fldname missing required SRCH operand
DBDUT0850E XDFLD fldname precedes SEGM statement and is missing SEGMENT operand
DBDUT0851E XDFLD fldname has more than 5 SUBSEQ fields
DBDUT0852E XDFLD fldname has more than 5 DDATA fields
DBDUT0853E XDFLD fldname has more than 5 SRCH fields
DBDUT0854E LCHILD lchildname, XDFLD fldname, key length nnnn exceeds maximum CONST,SRCH,SUBSEQ length of 240
DBDUT0855E XDFLD fldname, SEGMENT sgmname not defined in database
DBDUT0856E XDFLD fldname, SRCH field srchfld not in source segment sgmname
DBDUT0857E XDFLD fldname, DDATA field ddatafld not in source segment sgmname
DBDUT0858E XDFLD fldname, source segment sgmname, DDATA field ddatafld cannot be a /SX field
DBDUT0859E XDFLD fldname, SUBSEQ field fldname not in source segment sgmname
DBDUT0860E XDFLD fldname, target segment sgmname not parent of source segment sourcesgmname
DBDUT0862E Sequence field fldname in root segment sgmname must be unique for database type accesstype
DBDUT0863E GSAM minimum record length exceeds maximum for RECFM=V
DBDUT0865E SEGM statement limit of 255 exceeded
DBDUT0866E FIELD statement limit of 1000 exceeded
DBDUT0867E Segment sgmname, key sequence field fldname, length nnnn exceeds maximum
DBDUT0868E Virtual logical child segment sgmname not referenced by an LCHILD PAIR statement
DBDUT0869E Paired (real) logical child segment sgmname missing logical PARENT specification
DBDUT0870E DBD statement missing required ACCESS operand
DBDUT0871E MSDB missing required DATASET REL operand
DBDUT0872E XDFLD has no preceding LCHILD statement
DBDUT0873E Sequence field fldname, start nnnnn, length nnnnn extends beyond SEGM minimum size of nnnnnbytes
DBDUT0874E Segment sgmname, sequence field fldname invalid, only 1 sequence field allowed for this segment type
DBDUT0875E Segment sgmname, field fldname, START value parmvalue not numeric or names a field which is not defined for this SEGM
DBDUT0876E EXIT parameter is not allowed with ACCESS of accesstype
DBDUT0877E Logical SEGM sgmname missing required SOURCE operand
DBDUT0878E Segment sgmname, hierarchy sequence error
DBDUT0879E First ACCESS statement must precede first SEGM
DBDUT0880E ACCESS statement contains mutually exclusive keywords RMRTN and REF
DBDUT0881E ACCESS statement only valid with DBD ACCESS=HD
DBDUT0882 Segment FIELD statement limit of 255 exceeded
Messages DBDUT08A1 to DBDUT08A3
Messages DBDUT08P1 to DBDUT08P2
Messages DBDUT0L02 to DBDUT0L99
Messages DBDUT0LA1 to DBDUT0LA2
Messages DBDUT0LP1 to DBDUT0LP3
Messages DBDUT0U01 to DBDUT0U35
Messages DBDUT0W01 to DBDUT0W36
Messages DBDUT0WA1 to DBDUT0WA9
Messages DBDUT0WE1 to DBDUT0WE2
Messages DBDUT0WF1 to DBDUT0WF2
Message DBDUT0WP2
DBUTIL Error Messages
IMSUT0115I DBUTIL: Processing complete - %6 calls were issued
IMSUT0532E DD statement missing for %8
IMSUT0533E SYSIN LRECL exceeds DBUTIL maximum of %5%
IMSUT0534E Dynamic memory allocation failure. RC=%8% Size=%5%
IMSUT0535E Function is required for interactive calls
IMSUT0536E PCB Number is required for interactive calls
IMSUT0537E Cannot mix control cards with interactive call
IMSUT0538E SYSIN dataset not found. DSN=%60
IMSUT0539E SYSIN dataset open failure status=%5% DSN=%60
IMSUT0540E terminated "LDIX" due to status code of %2%
IMSUT0541E SEGM %8 is not in PCB for: %8
IMSUT0542E Dataset not found: %60
IMSUT0543E DBUTIL terminated %4 due to status code of %2%
IMSUT0544E Error status= %5% reading input dataset DSN=%60
IMSUT0545E Invalid length in record. Length=%8
IMSUT0546E Error opening input dataset. Status code: %5% DSN=%60
IMSUT0547E Input file not found. DSN=%60
IMSUT0548E "MLOD" can only be issued for MSDBs
IMSUT0549E Invalid command syntax. DSN required
IMSUT0550E Cannnot load remote database %8
IMSUT0551E Cannot "LOAD" "INDEX" database %8
IMSUT0552E Cannot "LOAD" database %8 USING "PROCSEQ" PCB
IMSUT0553E "USEQ" does not support "REMOTE" database
IMSUT0554E "USEQ" does not support "USER CAT" database
IMSUT0555E Error status %5% opening output dataset DSN=%60
IMSUT0556E LRECL for unload not given and default not available
IMSUT0557E "UNLO" of logical DBD requires a non-zero LRECL specification, or variable length RECFM
IMSUT0558E "USEQ" does not support variable length
IMSUT0559E Invalid command syntax. RC=%4
IMSUT0560E Invalid command syntax. DSN required
IMSUT0561E Database selected is not a DEDB
IMSUT0562E GSAM PCB missing required "RECLEN" parameter
IMSUT0563E PCB number %3 not defined in PSB
IMSUT0564E GSAM PCB missing required RECLEN parameter
IMSUT0565E Cannot issue calls against IO or ALT TP PCBs
IMSUT0566E DBD referenced by PCB number not defined
IMSUT0567E PCB number not numeric
IMSUT0568E PCB number cannot be zero
IMSUT0569E DBD name not found in PCB list
IMSUT0570E No PCB ID provided
IMSUT0571E Continuation error card number %6. Card=%65
IMSUT0572E "LOAD" of logical DBD requires a non-zero LRECL specification, or variable length RECFM
IMSUT0573E LRECL for load not given and default not available
IMSUT0574E This version of DBUTIL does not support %4
IMSUT0575E %4 function only available when run as DBB or DLI
IMSUT0576E This version of IMSDBU only supports the batch interface
IMSUT0577E SYSOUT dataset open failure status=%5% DSN=%60
IMSUT0578E Write to SYSOUT dataset failure status=%5%
IMSUT0580E Information for PSB %8 not found in configuration file
IMSUT0602E Input card dataset is busy. Try later. DSN=%60
IMS Database Editor Error Messages
IMS Run-time System Error Messages
IMSRT0000I <message text>
IMSRT0039E ACB failure for %8. %60%
IMSRT0040E PSB Authorization failure for %8.
IMSRT0041E No ACEE available. Function %4 can't test authorization of %8
IMSRT0042E Error initializing MFIMS - IMS terminating. %12% not found or incorrect version
IMSRT0043E Error initializing MFIMS - IMS terminating. Error opening/reading IMSCONFG file. File Status: %6 Description: %40%
IMSRT0044E Error initializing MFIMS - IMS terminating. Error opening %6 files. File Status: %6 Description: %40%
IMSRT0045E Error initializing MFIMS - IMS terminating. Failure reason code: %4
IMSRT0048E External XA subsystem %8 failure RC=%5
IMSRT0052I The following POP-UP was suppressed during shutdown
IMSRT0053I The following POP-UP was suppressed by system request
IMSRT0054I Suppression resulted in automatic termination
IMSRT0055I End of message
IMSRT0056I OPTION VALUE MUST BE "C" OR "T"
IMSRT0057I OPTION VALUE MUST BE "Y" OR "N"
IMSRT0058I OPTION VALUE MUST BE "R" OR "T"
IMSRT0059I INVALID KEY PRESSED
IMSRT0060I ONLY 4 DIGITS ARE ALLOWED
IMSRT0061I LIMIT VALUE NOT NUMERIC
IMSRT0062I STATUS CODE MUST BE TWO BYTE VALUE OR BLANK
IMSRT0063I OPTION MUST BE "C", "T", OR "S"
IMSRT0064I SAVE OPTION ONLY AVAILABLE ON WINDOWS NT
IMSRT0065I USERID IS A REQUIRED FIELD
IMSRT0066I PASSWORD IS A REQUIRED FIELD
IMSRT0068I MFIMS SYSTEM WINDOW ERROR
IMSRT0069I CONTACT TECHNICAL SUPPORT
IMSRT0070I PRESS ENTER TO TERMINATE
IMSRT0080E Error allocating memory for ACB DBD field blocks REF1: %4 REF2: %5
IMSRT0081E ACB create/modify failure: Too many DBD fields Total DBD fields required for this PSB exceeds: %6
IMSRT0082E ACB create/modify failure: Caching SENSEG/SENFLD SENSEG/SENFLD cache exceeded reserved memory
IMSRT0083E Error allocating memory for ACB PCB SENFLD blocks REF1: %4 REF2: %5
IMSRT0084E ACB create/modify failure: Too many SENFLD statements More than 10,000 SENFLDs in this PSB
IMSRT0087E Unrecoverable System Software Abend <abend-number>
IMSRT0105E Database ACCESS error for DB:
IMSRT0121E DLI call failure - <return/reason code> JCLXM0000I * DATABASE ERROR AO *
IMSRT1003W CHKP ID=id duplicates an existing ID. Pausing 1 second.
IMSRT1012E MFIMS DATABASE SHARING MANAGER A database record is in use by %12%. Database: %8 Root Key: %50%
MFS Error Messages
Messages MFSUT0401 to MFSUT0435
MFSUT0401W MSG %8 has invalid OPT=%1, defaulting to OPT=1
MFSUT0402W Cannot specify FILL on input MSG, FILL ignored
MFSUT0403W Cannot specify PAGE on input MSG, PAGE ignored
MFSUT0405W MFLD LTH operand missing, defaulting to LTH=0001. MFLD: %50%
MFSUT0406W EXIT ignored, only input MFLDs can use field exits. MFLD: %50%
MFSUT0407W MFLD literals cannot specify ATTR=YES, ATTR=NO assumed. MFLD literal: %45%
MFSUT0408W EXIT ignored, MFLD literals cannot use field exits. MFLD literal: %45%
MFSUT0409W ATTR=YES only valid when MFLD names DFLD, ATTR=NO assumed
MFSUT0410W MSG(%8), SEG GRAPHIC not YES or NO, assumed YES
MFSUT0411W MSG(%8), EXIT ignored, only input messages can use segment exits
MFSUT0412W MOD LPAGE's COND operand missing, assuming last LPAGE of set
MFSUT0413W MSG(%8), MSGEND statement missing, assumed present
MFSUT0414W No STACK is on to issue STACK OFF
MFSUT0415W MFLD's DFLD name in DO truncated to 6 characters
MFSUT0416W Initial cursor position defaulting to row 1, column 2
MFSUT0417W LABEL ignored, labeled DFLDs should not have PASSWORD
MFSUT0418W DFLD label in DO truncated to 6 characters
MFSUT0419W Recommended END statement missing, assumed present
MFSUT0420W ENDDO statement missing, assumed present
MFSUT0421W FMTEND statement missing, assumed present
MFSUT0422W MFLD JUST operand invalid with system literal %8. JUST operand ignored for MFLD %19
MFSUT0423W MFLD ATTR operand invalid with system literal %8. ATTR operand ignored for MFLD %19
MFSUT0424W MFLD LTH operand invalid with system literal %8. LTH operand ignored for MFLD %19
MFSUT0425W OPCTL operand ignored, not valid with literal DFLDs
MFSUT0426W MOD(%8), LPAGE(%3%) contains no MFLDs, this MOD/LPAGE bypassed
MFSUT0427W MOD(%8), MID(%8), DPAGE(%8), could not find MID for MOD/LPAGE selected or MID contains no MFLDs or all MIDs specified LPAGE and no SOR stated this DPAGE
MFSUT0428W FMT name %8 greater than 6 characters, truncated to 6 possibly causing duplicates
MFSUT0429W EGCS "G" literal missing an SO or SI character. Literal assumed to contain valid SO/SI pair. Card: %50%
MFSUT0430W EGCS "G" literal contains odd number of bytes, literal accepted as specified. Card: %50%
MFSUT0431W Invalid DFLD ATTR value "%8" ignored
MFSUT0432W SYSMSG parameter not valid
MFSUT0433W Message %8 has no format or is assigned to another format outside this MFS source
MFSUT0434W Format %6 has no messages
MFSUT0435W Device type of DPM not supported. Device ignored.
Messages MFSUT04A1 to MFSUT04A7