Micro Focus Enterprise Developer 4.0 for Eclipse
Welcome
Existing Customers: Updating from an Earlier Release
New Customers: Where do I start?
New to Eclipse
New to COBOL
New to PL/I
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 for Eclipse
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 Net Express, Server Express and Mainframe Express
Upgrading from ACUCOBOL-GT
Upgrading from RM/COBOLĀ®
Procedural COBOL Compared with Managed COBOL
Overview of application development in Eclipse
Overview of Remote Mainframe Development
Enterprise Developer Tutorials Guide
Getting Started
Mainframe Tutorials
Getting started with Enterprise Developer
Using the Rumba Screen Designer
Tutorial: Remote mainframe development
Tutorials: HCO for SQL Server (HCOSS)
Tutorial: Assembler
Tutorials: CICS
Tutorial: CICS
Tutorial: Web-enabled CICS Acting as a Web Server
Tutorial: Web-enabled CICS Acting as a Web Client
Tutorials: CICS Web Services
Tutorials: IMS
Tutorial: JCL
Tutorial: DSNREXX
Tutorials: PL/I
Tutorials: AppMaster Builder
Native COBOL Tutorials
Tutorial: Creating a Native COBOL Application
Tutorial: Running Unit Tests in the IDE
Tutorials: Interface Mapping Toolkit
Tutorials: OpenESQL Assistant
Tutorial: Data File Editor
Tutorial: Classic Data File Tools
Tutorial: Using the Callable File Handler
Managed COBOL Tutorials
Tutorial: Creating a Basic JVM COBOL Application
Tutorial: Deploying JVM COBOL to an Application Server
Tutorial: SQL - Deploying an Enterprise JavaBean Containing JVM COBOL to a JBoss Application Server
Tutorial: Calling JVM COBOL programs as part of an Axis Web service
Tutorial: Creating a JVM COBOL Application Using a JavaFX Interface
Tutorial: Packaging JVM COBOL
Tutorial: Compiling a COBOL Program to JVM Byte Code
Web Services Tutorials
Procedural COBOL Compared with Managed COBOL
Technology Preview Features
Enterprise Developer Editions and Licenses
Product Information
Installation
Before Installing
Basic Installation
Advanced Installation Tasks
On Windows
On UNIX
Installing on Microsoft Terminal Server and Citrix
Mainframe Access Installation Guide
Introduction
Migration information
Installation requirements
Mainframe Access Configuration Utility
Host Installation
Preparing the Installation
Installation procedure
Upload the software
Receive the software
Configuration overview
Quick Configuration
Advanced Configuration Activities
Running Multiple Instances of Mainframe Access Server
Troubleshooting
Customizing Data Connect
Configuring Access to External Library Management Systems
Configuring Access to Enterprise Server Mainframe Subsystem Support
Configuring z/Server feature support
Console Commands
Mainframe Access Messages
Mainframe Access Server Messages
Mainframe Access Operational Messages Format
Mainframe Access Messages
Data Set Services Messages
MFA Direct Messages
Data Connect Messages
Drag and Drop Error Messages
MFDAS01: Mainframe access problem.
MFDAS02: Cannot import multiple files to a single file.
MFDAS03: Cannot export multiple files to a single file.
MFDAS04: Module 'MFLSC' is missing or inaccessible.
MFDAS05: File had no length, or does not exist.
MFDAS06: Call to module 'DFCONV' failed. Unable to convert the VSAM/QSAM file.
MFDAS07: Value is not a valid number.
MFDAS08: For VSAM/QSAM files, extensions of PRO, DAT, or IDX are reserved.
MFDAS09: Rename to file failed.
MFDAS10: The allocation of failed with message number.
MFDAS11: The allocation of differs from the mainframe.
MFDAS12: One or more of the fields have not been properly entered.
MFDAS13: The PC file name cannot have more than 4 subdirectory levels.
MFDAS14: Mismatch between new and repeat passwords.
MFDAS15: Unable to make the directory.
MFDAS16: Unable to remove directory.
MFDAS17: Call to module 'PCIMS' failed. Unable to convert the IMS database.
MFDAS18: A catalog search criteria must be entered.
MFDAS19: A real workstation drive must be used.
MFDAS22: Call to module 'SQL-Wizard' failed. Unable to convert the XDB table.
MFDAS23: Cannot establish connection to the mainframe server.
MFDAS24: Network communication problems with blocks of size.
MFDAS25: CCI module was not found.
MFDAS26: Module is not a CCI module.
MFDAS27: Unable to delete file.
MFDAS28: Either recall this dataset or assign a type.
MFDAS29: Assign a type to this dataset.
MFDAS30: The workstation dataset is connected to the mainframe
MFDAS31: Copy of file failed.
MFDAS32: Paste of file failed.
MFDAS33: PCIMS is not available. Unable to convert the IMS database
Status Codes and Error Messages
Configuration reference
Mainframe Access Server configuration parameters
Mainframe Access Server z/Server feature configuration parameters
After Installing
Installing Enterprise Developer Development Hub
Managing Licenses
Overview
To start Micro Focus License Administration
Installing licenses
Installing licenses silently
Viewing installed licenses
Uninstalling licenses
Installing License Manager
Trial licenses
Commuter licenses
Usage log
Licensing Error Messages
Updates and Product Support
Micro Focus End User License Agreement
Known Issues and Restrictions
Application Server JCA Support
Application Workflow Manager
AppMaster Builder
Calling COBOL Programs from C
COBOL Programming
Compatibility
Installation on Windows
Installing on UNIX and Linux
Data Access
Debugging, Problem Determination and Diagnostic Tools
Docker
Documentation
Eclipse IDE
JVM Code
Mainframe Programming and Management
Remote Mainframe Development
Resource Adapters
Contacting Micro Focus
Sample Programs
Cheat Sheets
The Micro Focus Community
Help on Help
Developing Applications in the IDE
Starting Eclipse
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
To create a project or a file from a custom template
Indicating Whether a File is a Copybook or a COBOL Program
Configuring the Project, Build Configuration and File Properties
Developing applications on remote machines
Building COBOL applications
Compiling COBOL Applications
Linking Native COBOL Code (Windows)
Linking (UNIX)
To clean a project
Tips: Building COBOL projects
How To in the IDE
Code Coverage (Native COBOL)
Code Analysis
Debugging COBOL applications
Overview of the process of debugging
Preparing a Project for Debugging
Debugging Features and Techniques in Eclipse
Debugging Scenarios
Starting the Debugger Automatically
Debugging Windows Services
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 Mainframe Applications and Services on Enterprise Server
Debugging Enterprise Server Services and Applications Using a Live Recording
Debugging with 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
Code Refactoring
Running COBOL Applications
Using Eclipse for PL/I development
Using Enterprise Server from within the IDE
Modern Development Practices
Using Enterprise Developer in Modern Application Development
Using Enterprise Developer with Jenkins
Enterprise Developer Build Tools for Windows
Using Enterprise Developer with Docker
Introduction to Docker
Benefits of Using Docker
Docker Terminology
Getting Ready to Use Enterprise Developer with Docker
Key Concepts When Using Docker with COBOL Applications
Building Images for COBOL Applications
Debugging COBOL Applications Running in Containers
Debugging PL/I Applications Running in Containers
Docker Demonstrations
Programming
COBOL Programming
Getting Started with COBOL
Calling COBOL Programs
Internationalization Support
Preparing Applications for Enterprise Server
Web Services Support for Native COBOL
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 Assembler Subprograms
Interfacing with Windows API Routines
Interfacing with C Programs
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
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 Runtime Functions and Parameters
Compatibility with XML Extensions
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
OpenESQL Preprocessor Options
Setting the OpenESQL Preprocessor and Compiler Directive Options
SQL Code Generation Options
Scope - OpenESQL SQL Compiler Directive Options
OpenESQL DBMAN Use Case Scenarios
OpenESQL Datetime Data Type Handling
OpenESQL Fixed-length Character Strings Handling
SQL Syntax Checking with OpenESQL
OpenESQL Embedded SQL Cursor Behavior and Performance
Database Connections
Managing Transactions
Programming for OpenESQL
ODBC
JDBC
COBOL Program Migration Support
COBSQL
How to
Reference
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
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.
COB ES0121 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
User Interface Reference
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
File Conversion Utilities
Data File Structure Command Line Utility
Classic Data File Tools
Configuring Classic Data File Tools
Data File Converter
Record Layout Editor
Data File Editor
How to
Reference
Rebuild
File Handling
File Handling Examples
Btrieve
Example of Data and Key Compression
External Files
File Handler
File Names
File Status
Indexed Files
MFSORT
Rebuild
Example Relative File Definition
Sequential Files
File Handling Guide
Introduction
File Organizations
Filenames
File Status
Sharing Files
File Handler Configuration
File Handler and Sort APIs
Sort Utilities
Btrieve
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-S to FS252-S
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
Using COBOL and Java Together
Java and COBOL Interoperability Options
Considerations
Deploying a Java Service Interface and Using Resource Adapters
Calling Procedural COBOL from Java
Calling Java from OO COBOL
Calling OO COBOL from Java
Java Data Types
JVM COBOL Interoperating with Java
Mainframe Programming
Mainframe Subsystem Support Developer Introduction
AppMaster Builder
Introducing AppMaster Builder
Developing Applications in the AppMaster Builder Perspective
AppMaster Builder Projects
Workgroups
Screen Painter
Online Express
Program Painter
Customizer/Micro Focus Generator (MFG)
Data View Manager
Data Structure Editor
Report Painter
Application Reports
Analysis Option
Developing Applications in the Team Developer Perspective (Technology Preview)
AMB Endevor Interface (Technology Preview)
Generating Code
Administration
How to
Administration
AMB Endevor Interface (Technology Preview)
Analysis Option
Application Reports
Code Generation
Database Views
Online Express
Preferences and Properties
Program Painter
Projects
Report Painter
Screen Painter
User Areas
Reference
cmdgen command
Configuration XML File
Control (CNTL) Files
Customizer/Micro Focus Generator (MFG)
Customizer Symbols
Customizer Statements
Customizer Rule Examples
MFG command
MFG Structures
Data Communication Calls
Data Structures
Database Access Statements
Database Calls
Date Field Formats
Distributed Generation Server
AppMaster Builder Error Messages
IG- Micro Focus Generator Messages
15 - IG-IGDRVR
16 - IG-PARSE
17 - IG-PARM
19 - IG-INFRA
20 - IG-GLOBAL
21 - IG-STORE
22 - IG-SRVCS
22000 INVALID DLL NAME
22001 ERROR LOADING MODULE
22002 ERROR QUERY PROC ADDR
22003 ERROR QUERY PROC TYPE
22004 ERROR QUERY MOD HANDLE
22005 ERROR QUERY MOD NAME
22006 ERROR FREEING MODULE
22010 ERR FILE NOT FOUND
22011 ERR TOO MANY OPEN FILES
22012 ERR ACCESS DENIED
22013 ERR NOT ENOUGH MEMORY
22014 ERR BAD FORMAT
22015 ERR NOT DOS DISK
22016 ERR INVALID NAME
22017 ERR INVALID MODULETYPE
22020 ERR INVALID EXE SIGNATURE
22021 ERR EXE MARKED INVALID
22022 ERR ITERATED DATA EXCEEDS 64K
22023 ERR INVALID MINALLOCSIZE
22030 ERR INVALID HANDLE
22031 ERR INTERRUPT
22032 ERR PROC NOT FOUND
22033 ERR ENTRY IS CALLGATE
22034 ERR INVALID PROC NAME
22035 ERR INVALID ORDINAL
22036 ERR INVALID ACCESS
22037 ERR BAD NAME LENGTH
22050 ERROR WRITING COMPMAC
22051 ERROR INVALID PROCTYPE
22060 FILE NAME TOO LONG
22061 NULL FILE NAME
22062 ERR OPENING FILE
22063 ERR CLOSING FILE
22080 UNABLE ALLOC MEM
22081 NOT ENOUGH MEMORY
22082 UNABLE FREE MEM
22083 MEM ACCESS DENIED
22084 INVALID FREE ADDRESS
22201 ERR ALLOC MEMPAGE FAILED
22202 ERR ALLOC MEMORY FAILED
22203 ERR UNABLE TO FREE MEMPAGE
22204 ERR MEMPAGE LIMIT REACHED
22205 ERR MEMPAGEINDEX CORRUPTION
22206 ERR MEMINDEX CORRUPTION
22207 ERR MEMCLASS CORRUPTION
22208 ERR MEMCLASS INVALID
22209 ERR MEMPAGE CORRUPTION
22210 ERR MEMPAGE NOT INITIALIZED
22211 ERR MEMPAGE IS ACTIVED
22212 ERR MEMLIST CORRUPTION
22213 ERR FREEING MEM TWICE
22300 ERR UNABLE QUERY DBCS ENV
22301 ERR NLS OPEN FAILED
22302 ERR NLS NO CTRY CODE
22303 ERR NLS TABLE TRUNCATED
22304 ERR NLS TYPE NOT FOUND
22305 ERR CODE PAGE NOT FOUND
23 - IG-VM
24 - IG-BUILTIN
26 - IG-LEX
ADB- database messages
AFE- field edit messages
APX- Online Express messages
BTC- batch call messages
CB2- COBOL messages
CIC- CICS messages
CIC-1010-00-E 1070-00-E Required screen name(s) not supplied
CIC-1020-00-E CIC-1100-00-E CIC-1170-00-E Option Parameter is not allowed
CIC-1030-00-E Option Required parameter was not supplied
CIC-1040-00-E Option Option is unknown by this command
CIC-1050-00-E CIC-1060-00-E Required program name not supplied
CIC-1070-00-E 1010-00-E At least one screen must be specified
CIC-1100-00-E CIC-1020-00-E CIC-1170-00-E Option Parameter is not allowed
CIC-1110-00-E CIC-1120-00-E Required options were not supplied
CIC-1140-00-E CIC-1150-00-E CIC-1180-00-E Option optionname Option is unknown by this command
CIC-1160-00-E Option optionname Invalid parameter for this option
CIC-1170-00-E CIC-1020-00-E CIC-1100-00-E Option Parameter is not allowed
CIC-1180-00-E CIC-1140-00-E CIC-1150-00-E Option optionname Option is unknown by this command
CIC-1200-00-E Screen screenname field fieldname
CIC-1210-00-E Screen field Subscript invalid on non-repeating field
CIC-1220-00-E Screen screenname field fieldname
CIC-1230-00-E Screen combination of attributes Invalid combination of attributes
CIC-1240-00-E Screen Attribute not recognized
CIC-1250-00-E Screen Required field name(s) not supplied
CIC-1260-00-E Screen Required field attribute(s) not supplied
CIC-1270-00-E Required paragraph name not supplied
CIC-1280-00-E Screen Extended attributes are not allowed
CIC-1290-00-E Program Program name must be 8 characters or less
CIC-1300-00-E Data name Data name must be 30 characters or less
CIC-1310-00-E LENGTH option is missing
CIC-1320-00-E Option option LENGTH parameter is missing
CIC-1330-00-E COMMAREA option is missing
CIC-1340-00-E Option option COMMAREA parameter is missing
CIC-1350-00-E Option option COMMAREA option is invalid in call
CIC-1360-00-E Option option LENGTH option is invalid in call
CIC-1370-00-E OPTION option NOCA option is invalid in call
CIC-2010-00-E TP-ADDR-MAX must be increased to accommodate data areas being passed
CIC-2020-00-E CIC-SERVICE-RELOAD may not be used in non-OS-VS COBOL programs
CIC-3010-00-E Record name Record name must be defined to AMB
CIC-4010-00-I TP-USER-LEN TP-USER-LEN set to default value
CIC-4020-00-I Record name copybook was not specified Record assumed coded inline
CIC-4030-00-I CIC-LINKAGE macro no longer supported
CIC-4050-00-I TP-ADDR-MAX &ampTP-ADDR-MAX set to default value
CIC-5010-00-W Option Option is not supported by Micro Focus PC-CICS
CIC-5020-00-E Command Command is not supported by Micro Focus PC-CICS
CIC-5800-00-F AMB module APMFCSTP has been included twice
CIC-8020-00-F AMB module APCICSTP has been included twice
CIC-8020-00-F AMB module APCICSTP has been included twice
DB2- SQL messages
DB2-1001-00-E Not a valid column name
DB2-1002-00-W Cursor not declared
DB2-1003-00-E Not WHERE or NOWHERE or NULL keyword
DB2-1004-00-W This statement will modify an entire table
DB2-1005-00-E No record name defined
DB2-1006-00-E COLUMN not inserted and declared not null
DB2-1007-00-E WHERE not allowed on STORE
DB2-1008-00-W This statement will erase an entire table
DB2-1009-00-W Cursor not declared
DB2-1010-00-E No column names allowed on ERASE
DB2-1011-00-W OBTAIN needs a WHERE clause or it can retrieve multiple rows
DB2-1012-00-E CANNOT OBTAIN WHERE CURRENT NEED CURSOR AND FETCH
DB2-1013-00-E Declare cursor more than once
DB2-1014-00-E Command cannot have WHERE CURRENT OF
DB2-1015-00-E No cursor name defined
DB2-1016-00-E Keyword not allowed as record name
DB2-1017-00-E UPDATE specified but no column name follows keyword
DB2-1018-00-E Parameter not WHERE or NULL or NOWHERE or UPDATE or ORDER
DB2-1019-00-E Invalid column name after UPDATE
DB2-1020-00-F Name not found in DDISYMB
DB2-1021-00-E WHERE search condition not found
DB2-1022-00-E FROM not allowed with
DB2-1023-00-E INTO not allowed with
DB2-1024-00-E DB-PROCESS-ID is valid only with the DB-PROCESS call
DB2-1025-00-E ORDER specified but no column name follows keyword
DB2-1026-00-E Invalid column name after ORDER
DB2-1027-00-E Cannot have UPDATE and ORDER in same cursor declaration
DB2-1028-00-I Column name specified in the UPDATE clause will be updated
DB2-1029-00-E INTO or FROM keyword has no structure name
DB2-1030-00-E DB-PROCESS-ID keyword has no ID name following it
DB2-1031-00-E Found more than once in command
DB2-1032-00-E END or ENDWHERE specified and had no WHERE clause
DB2-1033-00-E Keyword only valid for DB-PROCESS and DB-DECLARE
DB2-1034-00-E WHERE clause found after END or ENDWHERE
DB2-1035-00-E NOWHERE clause specified and there is a WHERE clause
DB2-1036-00-E NOWHERE clause specified and there is an END or ENDWHERE
DB2-1037-00-E When WHERE clause is present UPDATE or ORDER must follow after
DB2-1038-00-E Cannot have CURRENT keyword with a NOWHERE clause
DB2-1039-00-E Found CURRENT keyword before finding WHERE clause
DB2-1040-00-E Invalid use of WHERESQL with CURRENT
DB2-1042-00-E CURSOR longer than 12 characters
DB2-1043-00-E -ID name longer than 10 characters
DB2-1045-00-E Individual cols and builtin functions should not be mixed
DB2-1046-00-E Syntax invalid for SELECT DISTINCT
DB2-1047-00-E Not a valid built-in function
DB2-1048-00-E DISTINCT modifier required for COUNT
DB2-1049-00-E Invalid function argument -
DB2-1050-00-E Cannot return result -
DB2-1051-00-E Cannot create function result -
DB2-1052-00-E Invalid use of DB-LOOP-MAX keyword
DB2-1053-00-E Invalid use of UNION keyword
DB2-1054-00-E UNION select list incompatible
DB2-1055-00-E Data type of column in function cannot be found - regen subschema
DB2-1056-00-E Indicator structure not found for CURSOR
DB2-1057-00-E Indicator structure not found for TABLE
DB2-1058-00-E INSERT table cannot be the same as SUBSELECT table
DB2-1059-00-E Columns in SUBSELECT result table do not match insert column list
DB2-1060-00-E GROUP BY specified but no column name follows keyword
DB2-1061-00-E Invalid column name after GROUP
DB2-1062-00-E Different location names seen in UNION
DB2-1063-00-E Different location names seen in Join
DB2-1064-00-E Cannot INSERT DELETE or UPDATE from remote location if using CICS or IMS
DB2-1065-00-E DISTINCT invalid or used more than once in a statement
DB2-1066-00-E COMMIT-ROLLBACK not supported in non-ISPF environment
DB2-1067-00-E COMMIT with HOLD parameter not supported unless using SQL-400
DB2-1068-00-E Invalid parameter specified for command
DB2-1069-00-E WITH HOLD expected Found An unexpected keyword found following WITH
DB2-1070-00-E Number of row expected
DB2-1071-00-I FETCH ONLY assumed
DB2-1072-00-E In EXPR arithmetic operator applied to CHAR
DB2-1073-00-E Mixed data types - creation of result field not supported
DB2-1074-00-E Command supported for SQLSVR only
DB2-1075-00-E Keyword supported for SQLSVR only
DB2-1076-00-E UPDATE keyword is invalid for SQLSVR
DB2-1077-00-E Cannot have BROWSE and HOLDLOCK in same cursor declaration
DB2-1078-00-E AUTO keyword is only valid for DC targets PM and WIN
DB2-1079-00-E DB2-AUTO-COMMIT disabled for SQLSVR
DB2-1080-00-I DB-COMMIT used without DB-BEGIN-TRAN
DB2-1081-00-E DB-BEGIN-TRAN used without DB-COMMIT
DB2-1082-00-E Keyword supported for ORACLE only
DB2-1083-00-E Command - cannot have AT-DBNAME clause
DB2-1084-00-E Command supported for ORACLE only
DB2-1086-00-E Expression not valid for command
DCL- IMS rule messages
DCL-0900-00-F PSB or subschema invoked more than once
DCL-0910-00-F Regenerate DDI symbols using 17Q or greater
DCL-1010-00-E No parms passed
DCL-1030-00-E REC or REF expected as second parm in
DCL-1040-00-E MODE keyword expected
DCL-1050-00-E NEXT valid only for DB-OBTAIN
DCL-1060-00-E INTO expected as second parm
DCL-1070-00-E Record name expected no more parms
DCL-1080-00-E CKEYED valid only for first record
DCL-1090-00-E CKEYED specified more than once
DCL-1100-00-E Concatenated key value expected no more parms
DCL-1110-00-E Qualification not allowed for
DCL-1120-00-E CURRENT only valid for first record
DCL-1130-00-E CURRENT only valid for referenced record
DCL-1140-00-E CURRENT specified more than once
DCL-1150-00-E FROM or INTO specified more than once in
DCL-1160-00-E Data name expected no more parms
DCL-1170-00-E FROM or INTO expected followed by data area
DCL-1180-00-E WHERE keyword found expected REC or REF or boolean operator
DCL-1190-00-E Field qualification invalid when using keyword IMSREC
DCL-1200-00-E Field qualification invalid with CURRENT
DCL-1210-00-E Field qualification invalid with CKEYED
DCL-1220-00-E Field name expected no more parms
DCL-1230-00-E Relational operator expected no more parms
DCL-1240-00-E Relational operator expected
DCL-1250-00-E Field value expected no more parms
DCL-1260-00-E Subscript expected no more parms
DCL-1270-00-E Right paren expected following key qualification no more parms
DCL-1280-00-E FIRST or LAST invalid with CURRENT
DCL-1290-00-E FIRST or LAST specified more than once for record
DCL-1300-00-E CCODE found more than once for record
DCL-1310-00-E Command code expected no more parms
DCL-1320-00-E FROM or INTO specified more than once for record
DCL-1330-00-E NEXT or IMSREC invalid when specifying more than one record per call
DCL-1340-00-E VIEW specified more than once
DCL-1350-00-E View name expected no more parms
DCL-1360-00-E RESET specified more than once
DCL-1370-00-E HOLD-NOHOLD specified more than once
DCL-1380-00-E PREV specified more than once
DCL-1390-00-E expected no more parms
DCL-1400-00-E Unrecognized or misplaced parm
DCL-1410-00-E VIEW keyword followed by is required for this
DCL-1420-00-E At least one record must be acted upon by specifying keyword REC
DCL-1430-00-E CKEYED invalid for DB-MODIFY
DCL-1440-00-E Added record may not be qualified by concatenated key
DCL-1450-00-E Dependent record under record to be added may not be referenced
DCL-1460-00-E
DCL-1470-00-E Dependent record under record to be deleted may not be referenced
DCL-1480-00-E Lowest level record must be preceded by keyword REC
DCL-1490-00-E Command codes invalid for DB-ERASE
DCL-1500-00-E CKEYED invalid for DB-ERASE
DCL-1510-00-E Expected keyword relational or boolean operator
DCL-1520-00-E FIRST keyword not recognized
DCL-1530-00-E Record name missing
DCL-1540-00-E Record name not defined to subschema record name ()
DCL-2000-00-E DCL-2005-00-E Do not use subscripted fields with EXEC DLI commands
DCL-2007-00-E Do not use multiple field values with EXEC DLI commands
DCL-2010-00-E LOCK keyword invalid for REFERENCED records
DCL-2020-00-E LOCK keyword specified more than once
DCL-2030-00-E Record length expected no more parms
DCL-2040-00-E Offset value expected No more parms
DCL-2050-00-E Keyword RECLENGTH must be specified
DCL-2060-00-E RESET invalid with CURRENT for EXEC DLI
DCL-2070-00-E RESET invalid with FIRST for EXEC DLI
DCL-2080-00-E GN call issued for this command
DDI- database definition messages
DDI-1000-00-F DDI-1007-00-F DDI-1020-00-F UNTIL error PT-PACK too long
DDI-1001-00-F DDI-1008-00-F DDI-1021-00-F UNTIL error PT-TEXT too long
DDI-1002-00-F Error in DELETE
DDI-1003-00-F Empty DDIFILE
DDI-1004-00-F DDI-1022-00-F SAVE-CANCEL file access
DDI-1005-00-F DDI-1023-00-F CREATE-UPDATE file access
DDI-1006-00-F DDI-1024-00-F Record READ access
DDI-1007-00-F DDI-1000-00-F DDI-1020-00-F UNTIL error PT-PACK too long
DDI-1008-00-F DDI-1001-00-F DDI-1021-00-F UNTIL error PT-TEXT too long
DDI-1009-00-F Unclear entity found reload into DDIFILE
DDI-1010-00-F Parameter name too long
DDI-1011-00-F Invalid parameter found
DDI-1012-00-F Too many PSB names
DDI-1013-00-F PSB and subschema not found
DDI-1014-00-F Segment not found
DDI-1015-00-F Segment parent not found
DDI-1016-00-F UNTIL2 program error
DDI-1017-00-F DDG program error
DDI-1018-00-F Record not found
DDI-1019-00-F Record is locked
DDI-1020-00-F DDI-1007-00-F DDI-1000-00-F UNTIL error PT-PACK too long
DDI-1021-00-F DDI-1008-00-F DDI-1001-00-F UNTIL error PT-TEXT too long
DDI-1022-00-F DDI-1004-00-F SAVE-CANCEL file access
DDI-1023-00-F DDI-1005-00-F CREATE-UPDATE file access
DDI-1024-00-F DDI-1006-00-F Record READ access
DDI-1025-00-F CREATE file access
DDI-1026-00-F SAVE-CREATE file access
DDI-1027-00-F DELETE file access
DDI-1028-00-F Illegal version fld
DDI-1029-00-F Version fld too large
DDI-1030-00-F Illegal MOD fld
DDI-1031-00-F MOD fld too large
DDI-1032-00-F Did not find DBDNAME or PSBNAME parameter
DDI-1033-00-F DBDNAME not found
DDI-1034-00-F DBD table limit exceeded max is 10
DDI-1035-00-F PSBNAME not found
DDI-1036-00-F PSB table limit exceeded max is 10
DDI-1037-00-F Unexpected EOF on DBD-PSB file
DDI-1038-00-F DBD name 8 characters
DDI-1039-00-F Parm not DEBUG or IGNORE invalid
DDI-1041-00-F Right paren missing on parm
DDI-1042-00-F No right paren found on parm