Micro Focus Enterprise Developer 3.0 for Eclipse > Deployment > Configuration and Administration > Enterprise Server Reference > Error Messages > Enterprise Server Error Messages > CASAM error messages

CASAM error messages

0001I Development region region-name created successfully

The %1$s development region has been successfully created.

System action: None
User response: None
Destination: standard error
Module: dfhcrtrg

0002F Region region-name not created

The request to create the region was not successful.

System action: The request is rejected.
User response: Check previous messages for cause of error. Correct the problem and retry the request.
Destination: standard error
Module: dfhcrtrg

0003E Too many arguments, maximum is 2

Too many arguments were specified, the maximum permitted is 2.

System action: The request is rejected
User response: Retry the request with the correct number of arguments
Destination: standard error
Module: dfhcrtrg

0004E Unrecognized option option-value

The specified option is not valid

System action: The request is rejected
User response: Retry the request with a valid option
Destination: standard error
Module: dfhcrtrg

0005E region-name is not a valid region name

region-name cannot be used as a region name. A region name must be alphanumeric, 4-8 characters long, and not a reserved system directory name

System action: The request is rejected
User response: Retry the request with a valid region name
Destination: standard error
Module: dfhcrtrg

0006E Development region region-name already exists

An attempt was made to create a development region that already exists

System action: The request is rejected
User response: Retry the request with a unique region name
Destination: standard error
Module: dfhcrtrg

0007E Development region region-name requires group of same name

When creating a development region the name must match that of an existing user group

System action: The request is rejected
User response: Create a user group of the same name and retry
Destination: standard error
Module: dfhcrtrg

0008S Failed to create directory directory-name, reason return-code

The OS returned a return code of return-code for the request to create the specified directory.

System action: The request is rejected
User response: None
Destination: standard error
Module: dfhcrtrg

0010S Region base path path-name does not exist

A specific path to the region has been specified but does not exist.

System action: The request is rejected
User response: Create the path or correct the configuration file dfhtx.cfg
Destination: standard error
Module: dfhcrtrg

0011S region-name is the default region name and cannot be created

region-name is the default or "global" region. It uses the base directory structure and therefore cannot be created with this utility. It is recommended that the global region (i.e. its directory structure) not be used for normal operations.

System action: The request is rejected
User response: Select another name for the region.
Destination: standard error
Module: dfhcrtrg

0012I Production region region-name created successfully

The production region has been successfully created.

System action: None
User response: None
Destination: standard error
Module: dfhcrtrg

0013I Production region region-name has been changed to development

The production region has been changed to development.

System action: None
User response: None
Destination: standard error
Module: dfhcrtrg

0014I Region base directory for region-name is region-base

The region-name is the region's base directory for region-base.

System action: None
User response: None
Destination: standard error
Module: dfhcrtrg

0015E Production region region-name already exists

An attempt was made to create a production region that already exists

System action: The request is rejected
User response: Retry the request with a unique region name
Destination: standard error
Module: dfhcrtrg

0017I Defaulting to a region-name region for region-type

No command line parameters were specified so the region was created as region-type by default. A production region is created unless the system locates a development configuration file, the default is then a development region.

System action: None
User response: None
Destination: standard error
Module: dfhcrtrg

1001W CFMT file (or dataset) name not supplied

The file name to action was not supplied. Usage is CFMT {fn} {file-name}

System action: None
User response: Correct the input and resubmit the request
Destination: Terminal
Module: dfhzcfmt

1002I CFMT Usage {fn} {file name} where fn={OPen,CLose,ENable,DIsable,INquire,NAme}

No input was supplied with the transaction. This message documents the required parameters. The user should enter the transaction ID, function, and file name. The function may be "open", "close", "enable", "disable", "inquire" or "name". The transaction considers only the first two letters of the function parameter to determine its action.

System action: None
User response: None
Destination: Terminal
Module: dfhzcfmt

1003I Zero length input for CFMT at terminal-id, user user-id

The transaction CFMT started on the terminal but there was no input data. The request executed on terminal terminal-id where user user-id was signed on.

System action: None
User response: Correct the input and resubmit the request
Destination: Terminal
Module: dfhzcfmt

1004W Invalid CFMT initiation at terminal-id, user user-id

The transaction CFMT started on the terminal but the start was not a valid start. The request executed on terminal terminal-id where user user-id was signed on.

System action: None
User response: Correct the transaction initiation and resubmit the request
Destination: Terminal
Module: dfhzcfmt

1005I CFMT - File file-id opened successfully; terminal-id, user user-id

The request to open the file was successful.

System action: The file was opened
User response: None
Destination: Terminal, CSMT td queue, and console
Module: dfhzcfmt

1006I CFMT - File file-id closed successfully; terminal-id, user user-id

The request to close the file was successful.

System action: The file was closed
User response: None
Destination: Terminal, CSMT td queue, and console
Module: dfhzcfmt

1007I CFMT - File file-id enabled successfully; terminal-id, user user-id

The request to enable the file was successful.

System action: The file was enabled
User response: None
Destination: Terminal, CSMT td queue, and console
Module: dfhzcfmt

1008I CFMT - File file-id disabled successfully; terminal-id, user user-id

The request to disable the file was successful.

System action: The file was disabled
User response: None
Destination: Terminal, CSMT td queue, and console
Module: dfhzcfmt

1009I CFMT - File file-id is open-status and enable-status; terminal-id, user user-id

The inquire request was successful. The status of file open-status and enable-status. If an unexpected CVDA value is returned for either of these statuses, the actual numeric status will be reported.

System action: None
User response: None
Destination: Terminal
Module: dfhzcfmt

1010W CFMT invalid request (request) for file file-id at terminal-id, user user-id

The request for the file was not recognized. It may be OPen, CLose, ENable, DIsable, INquire or NAme. Only the first two characters of the request are examined by the program. The request is not case sensitive.

System action: The request is ignored
User response: Correct the input and resubmit
Destination: Terminal
Module: dfhzcfmt

1011W CFMT file file-id not found; terminal-id, user user-id

The file was not found. The file name is case sensitive.

System action: The request is ignored
User response: Correct the input and resubmit
Destination: Terminal
Module: dfhzcfmt

1012E CFMT request not authorized for file file-id at terminal-id, user user-id

The request for the file is not authorized.

System action: The request is ignored
User response: Correct the input or consult with the security administrator.
Destination: Terminal, CSMT td queue, and console
Module: dfhzcfmt

1013E CFMT file file-id unexpected response (eibresp); terminal-id, user user-id

The requested action for the file resulted in an unexpected API response.

System action: The request is ignored
User response: Correct the input and resubmit
Destination: Terminal
Module: dfhzcfmt

1014W CFMT illogic response for request to file file-id; terminal-id, user user-id

The requested action for the file resulted in an illogic API response. The requested transition is not logical, for example, an open request for a file that is already open.

System action: The request is ignored
User response: Correct the input and resubmit
Destination: Terminal
Module: dfhzcfmt

1015I CFMT file file-id DSNAME (DSNAME)

The DSNAME associated with the file is displayed.

System action: None.
User response: None.
Destination: Terminal
Module: dfhzcfmt

1016I CFMT function function completed. error-count error(s) encountered. See CEBR.

The requested action has completed. The number of errors is shown.

System action: None.
User response: Use the CEBR transaction to view the log.
Destination: Terminal
Module: dfhzcfmt

1017E CFMT file file-id IOERR (eibresp-1/eibresp-2); terminal-id, user user-id

The requested action for the file resulted in an IOERR.

System action: The request is ignored
User response: Correct the input and resubmit
Destination: Terminal
Module: dfhzcfmt

1020W Error opening file (file-id) group (group-id) - status=(file-status-1, file-status-2)

A file marked as Start Open / Enabled could not be opened in system initialization due to the I/O error specified.

If file-status-1 is 3 then the error is a standard file status code. A file-status-2 of 9 indicates a RTS error.

Common values for status:

Status	Reason	Action
3005	file not found	Correct file name in FCT or create file with CFCR if necessary.
9065	file locked	Ensure that another program has not opened the file exclusively.
9124	comms error	Make sure the Fileshare server is running and the correct CCI protocol is defined in the FHREDIR configuration file.

System action: The file will not be opened.
User response: Correct the error and open the file using the CFMT transaction.
Destination: Console
Module: dfhzplt

1030I CNCL Usage: CNCL {program-name}

No input was supplied with the transaction. This message documents the required parameters. The user should enter the transaction ID and program name.

System action: None
User response: None
Destination: Terminal
Module: dfhzcncl

1031I Zero length input for CNCL at terminal-id, user user-id

The transaction CNCL started on the terminal but there was no input data.

System action: None
User response: Correct the input and resubmit the request
Destination: Terminal
Module: dfhzcncl

1032W Invalid CNCL initiation at terminal-id, user user-id

The transaction CNCL started on the terminal but the start was not a valid start.

System action: None
User response: Correct the transaction initiation and resubmit the request
Destination: Terminal
Module: dfhzcncl

1033E Invalid cancel request at terminal-id, PPT entry found for program program-name, user user-id

The program name passed to CNCL was found as a PPT entry. The CPMT transaction should be used to issue NEWCOPY requests for CICS programs.

System action: None
User response: Use the CPMT transaction to release the CICS program.
Destination: Terminal
Module: dfhzcncl

1033E PPT entry found for program program-name not COBOL at terminal-id, user user-id

The program name passed to CNCL was found as a PPT entry which was not marked as a COBOL program. This transaction can only release COBOL programs.

System action: None
User response: Supply a valid program name or change the PPT definition.
Destination: Terminal
Module: dfhzcncl

1034E PPT entry found for program program-name not LOCAL at terminal-id, user user-id

The program name passed to CNCL was found as a PPT entry which was not a local program.

System action: None
User response: Supply a valid program name or change the PPT definition.
Destination: Terminal
Module: dfhzcncl

1035I CNCL request for program program-name issued at terminal-id, user user-id

The program release request was issued successfully.

System action: None
User response: None
Destination: Terminal
Module: dfhzcncl

1036W CNCL request for program program-name failed at terminal-id, user user-id

The program release request failed. This error will occur if the program was not actually in memory when the command was issued or logical cancel support is not enabled in the COBOL RTS.

System action: None
User response: None
Destination: Terminal
Module: dfhzcncl

1101W CKQC can only be run in multi-tasking mode to start an WebSphere MQ CKTI monitor

The region is currently running in single-tasking mode. The WebSphere MQ monitor may only be run in multi-tasking mode.

System action: None
User response: Restart CICS Option in multi-tasking mode, and reinvoke CKQC.
Destination: Terminal
Module: dfhzckqc

1102W Unexpected error (return-code) requesting CKTI

The CICS Option Process Requester returned an unexpected response.

System action: The CKTI monitor is not started.
User response: Retry the CKQC transaction. If the problem persists, contact Support.
Destination: Terminal
Module: dfhzckqc

1103W No initiation queue name given

To start an WebSphere MQ monitor, you need to supply an initiation queue name.

System action: The CKTI monitor is not started.
User response: Resubmit, specifying a queue name.
Destination: Terminal
Module: dfhzckqc

1104I Usage: CKQC STARTCKTI <initiation-queue>

To start an WebSphere MQ monitor via the LINK interface, you need to supply an initiation queue name.

System action: The CKTI monitor is not started.
User response: Resubmit, specifying a queue name.
Destination: Terminal
Module: dfhzckqc

1105W Invalid function key - use ENTER to accept data

The only keys that are recognized are: CLEAR, PF3 & ENTER.

System action: None
User response: Retry using a valid key.
Destination: Terminal
Module: dfhzckqc

1106E WebSphere MQ queue manager name not found. RC=return-code

The WebSphere MQ queue manager name cannot be found.

System action: None
User response: Check that WebSphere MQ has been configured correctly in the system initialization table.
Destination: Terminal
Module: dfhzckqc

1107I CKTI requested for initiation-queue

A request to start a CKTI has been initiated.

System action: CICS Option attempts to initialize an WebSphere MQ trigger monitor.
User response: Check console
Destination: Terminal
Module: dfhzckqc

2001W CPMT program or table name not supplied

The program name to action was not supplied. Usage is CPMT {fn} {program-name}.

System action: None
User response: Correct the input and resubmit the request
Destination: Terminal
Module: dfhzcpmt

2003I Zero length input for CPMT at terminal-id, user user-id

The transaction CPMT started on the terminal but there was no input data.

System action: None
User response: Correct the input and resubmit the request
Destination: Terminal
Module: dfhzcpmt

2004W Invalid CPMT initiation at terminal-id, user user-id

The transaction CPMT started on the terminal but the start was not a valid start.

System action: None
User response: Correct the transaction initiation and resubmit the request
Destination: Terminal
Module: dfhzcpmt

2005I CPMT - Program program-id newcopy; terminal-id, user user-id

The request to load a new copy of the program was successful.

System action: A new copy of the program is loaded.
User response: None
Destination: Terminal, CSMT td queue, and console
Module: dfhzcpmt

2006I CPMT - Program program-name phasein; terminal-id, user user-id

The request to load a new copy of %3$s by user %2$s at terminal %1$s was successful. The new copy will be used for all new requests.

System action: A new copy of the program is being phased in.
User response: None
Destination: Terminal, CSMT td queue, and console
Module: dfhzcpmt

2007I CPMT - Program program-name private; terminal-id, user user-id

The request to mark the program as private was successful.

System action:
User response: None
Destination: Terminal, CSMT td queue, and console
Module: dfhzcpmt

2008I CPMT - Program program-name shared; terminal-id, user user-id

The request to mark the program as shared was successful.

System action:
User response: None
Destination: Terminal, CSMT td queue, and console
Module: dfhzcpmt

2009I CPMT - Program program-name dplsubset; terminal-id, user user-id

The request to mark the program as dplsubset was successful.

System action:
User response: None
Destination: Terminal, CSMT td queue, and console
Module: dfhzcpmt

2010I CPMT - Program program-name fullapi; terminal-id, user user-id

The request to mark the program as fullapi successful.

System action:
User response: None
Destination: Terminal, CSMT td queue, and console
Module: dfhzcpmt

2011I CPMT - Program program-name cedf; terminal-id, user user-id

The request to mark the program as cedf was successful.

System action:
User response: None
Destination: Terminal, CSMT td queue, and console
Module: dfhzcpmt

2012I CPMT - Program program-name nocedf; terminal-id, user user-id

The request to mark the program as nocedf was successful.

System action:
User response: None
Destination: Terminal, CSMT td queue, and console
Module: dfhzcpmt

2013I CPMT - Program program-name is disabled; terminal-id, user user-id

The request to mark the program as disabled was successful.

System action:
User response: None
Destination: Terminal, CSMT td queue, and console
Module: dfhzcpmt

2014I CPMT - Program program-name is enabled; terminal-id, user user-id

The request to mark the program %3$s as enabled was successful.

System action:
User response: None
Destination: Terminal, CSMT td queue, and console
Module: dfhzcpmt

2016I Program program-name is not currently loaded

Program has not been loaded. The full name cannot be displayed until it has been accessed.

System action:
User response: Do a NEWCOPY or PHASEIN command and repeat this inquiry.
Destination: Terminal, CSMT td queue, and console
Module: dfhzcpmt

2018W CPMT invalid request (request) for program program-name at terminal-id, user user-id

The request for the program was not recognized. It may be OPen, CLose, ENable, DIsable, or INquire. Only the first two characters of the request are examined by the program. The request is not case sensitive.

System action: The request is ignored
User response: Correct the input and resubmit
Destination: Terminal
Module: dfhzcpmt

2019W CPMT program program-name not found; terminal-id, user user-id

The program was not found. The program name is case sensitive on some platforms.

System action: The request is ignored
User response: Correct the input and resubmit
Destination: Terminal
Module: dfhzcpmt

2020E CPMT request not authorized for program program-name at terminal-id, user user-id

The request for the program is not authorized.

System action: The request is ignored
User response: Correct the input or consult with the security administrator.
Destination: Terminal, CSMT td queue, and console
Module: dfhzcpmt

2021E CPMT program program-name unexpected response (eibresp); terminal-id, user user-id

The requested action for the program resulted in an unexpected API response.

System action: The request is ignored
User response: Correct the input and resubmit
Destination: Terminal
Module: dfhzcpmt

2023I CPMT - PPT for Program program-name was discarded; terminal-id, user user-id

The request to discard the PPT for program %3$s by user %2$s at terminal %1$s was successful.

System action:
User response: None
Destination: Terminal, CSMT td queue, and console
Module: dfhzcpmt

3000S Critical Event Manager storage error

The Event Manager Process encountered a local storage failure that was not recoverable.

System action: The Event Manager will be terminated.
User response: The event manager could not allocate local storage, free some memory.
Destination: Console and standard error.
Module: casevmgr

3001I Event Manager exit enabled (exit-program-name)

The Event Manager Process loaded the user-defined exit.

System action: The Event Manager call the exit at appropriate points.
User response: None
Destination: Console and standard error.
Module: casevmgr

3002W Event Manager unable to load exit (exit-program-name)

The Event Manager Process was unable to load the user-defined exit.

System action: The Event Manager will ignore the exit.
User response: Check the exit specification and ensure it is on the search path.
Destination: Console and standard error.
Module: casevmgr

3005E Unable to parse filter string. expected "expected-value"; found "actual-value-found" - at end of "filter-string"

The event manager was unable to process the event filter string because it was badly constructed.

System action: Event manager will switch off event filtering for this exit and send all events without being filtered
User response: Check the filter string, and restart the server
Destination: Console and standard error.
Module: casevmgr

3006I Event Filter for (exit-name) has been enabled/disabled. Filter string: "filter-string"

Event manager has enabled/disabled the event filter for this exit.

System action: none
User response: none
Destination: Console and standard error.
Module: casevmgr

3007E Unexpected logic error in program when parsing the event filter string. Exit: "exit-name" / Filter string: "filter-string"

Event manager encountered a logic error when parsing the filter string for the specified exit.

System action: none
User response: contact Micro Focus Team
Destination: Console and standard error.
Module: casevmgr

3008E Illegal Type-id: "type-id-found". Max type-id: "max-type-id"

The type ID specified exceeds the maximum type ID.

System action: none
User response: check and correct the filter string
Destination: Console and standard error.
Module: casevmgr

3009E Illegal sub-type-id: "sub-type-id-found". Max sub-type-id: "max-sub-type-id"

The subtype ID specified exceeds the maximum subtype ID.

System action: none
User response: check and correct the filter string
Destination: Console and standard error.
Module: casevmgr

3010E Illegal id range: "id-lo" - "id-hi"

The ID range specified is invalid.

System action: none
User response: check and correct the filter string
Destination: Console and standard error.
Module: casevmgr

3011W Exit initialisation failed. Exit name: "exit-name"

The exit returned a return code specifying its initialisation failed.

System action: none
User response: check the exit to find out why initialisation of the exit failed
Destination: Console and standard error.
Module: casevmgr

3012E Initialisation to generate Windows Events from EMP failed.

EMP is unable to generate Windows events based on the events reported to EMP.

System action: none
User response: contact Micro Focus
Destination: Console and standard error.
Module: casevmgr

3013E Unable to register server as active server for Monitoring and Management. Monitoring and Management support disabled.

Event Manager is unable to register the server as an active server for Monitoring and Management.

System action: none
User response: contact Micro Focus
Destination: Console and standard error.
Module: casevmgr

3014E Unable to create Server Monitoring and Management shared memory. Monitoring and Management support disabled.

Event Manager is unable to create the shared memory region for Monitoring and Management

System action: none
User response: contact Micro Focus
Destination: Console and standard error.
Module: casevmgr

3015W Unable to unregister the server from active servers list for Monitoring and Management. Error Accessing registry

Event Manager is unable to unregister the server from the active servers for Monitoring and Management list.

System action: none
User response: contact Micro Focus
Destination: Console and standard error.
Module: casevmgr

3016I ES Monitoring and Management support enabled

The Monitoring and management support for this server has been enabled

System action: none
User response: none
Destination: Console and standard error.
Module: casevmgr

3017E ES Monitoring and Management unable to open performance registry key: "Registry key", RC=Return code for WIN API call "RegOpenKeyExA". M & M disabled.

Event manager encountered an error opening the performance registry key

System action: none
User response: none
Destination: Console and standard error.
Module: casevmgr

3018E ES Monitoring and Management unable to get performance registry key: "Registry key\Registry value name", RC=Return code for WIN API call "RegQueryValueExA".

Event manager encountered an error retrieving the performance registry key value

System action: M & M is disabled.
User response: Perform an install repair on your system.
Destination: Console and standard error.
Module: casevmgr

3019W ES Monitoring and Management retrieved unexpected value for "Registry key\Registry value name": actual=Actual value of registry key, expected Expected value of registry key.

Event manager retrieved an unexpected value for the performance registry key value. You may have performed a Windows install repair, which has reinstated a back-level registry entry.

System action: M & M may have been disabled.
User response: Perform an install repair on your system. You may also need to run a script file to effect additional repairs on the registry settings. This is called perfreg.cmd and is provided in NX\Base\SOURCE\ENTERPRISESERVER\Monitoring.
Destination: Console and standard error.
Module: casevmgr

3020E ES Monitoring and Management detected non-zero value for "Registry key\Registry value name". M & M disabled.

Event manager has detected that performance monitoring has been disabled.

System action: M&M is disabled.
User response: Use the registry editor program, regedit, to delete the key value or set it to 0. Check the "library" entry is pointing to the correct version of cas0perf.dll. Check the server's console.log file for monitoring and management messages. Shut down and restart your server.
Destination: Console and standard error.
Module: casevmgr

3021W ES Monitoring and Management unable to get value for "Registry key\Registry value name": Return code for WIN API call "RegQueryValueExA"

Event manager retrieved an unexpected return code when querying the performance registry key value. The performance counters may not have been loaded correctly.

System action: none
User response: Perform an install repair on your system. If this fails to restore performance monitoring, you will need to run the load counter utility, LODCTR. First, locate the file cas0psys.ini, which is in NX\Base\Bin. Then run this command: lodctr cas0psys.ini
Destination: Console and standard error.
Module: casevmgr

3022W ES Monitoring and Management detected incorrect value for "Registry key\Registry value name": Performance monitoring load module name

Event manager retrieved an unexpected value when querying the performance registry key value. Performance monitoring may not have been behave correctly.

System action: none
User response: Perform an install repair on your system. If this fails to restore performance monitoring, you will need update the registry key. This should have a value of NX\Base\Bin\cas0perf.dll, where NX" is the folder where you installed the product.
Destination: Console and standard error.
Module: casevmgr

3023E Error accessing file casglm.lck "return-code".

While trying to access the file casglm.lck an error occurred.

System action: none
User response: Check the return code, and contact your technical support.
Destination: Console and standard error.
Module: casmgr

3024E Unable to map shared memory for performance monitoring. Monitoring and Management support disabled. Error: ""

Event Manager is unable to map shared memory for performance monitoring.

Resolution: Contact Micro Focus.
Module: casevmgr
Destination: Console and standard error.