CASSI9001 - CASSI9025

CASSI9001E Command parameter error: parameter
parameter is invalid for this command line.
CASSI9002E Command conflict error: cmd-parm
cmd-parm conflicts with or duplicates preceding parameters on the command line.
CASSI9003E Command parameter error: parameter
parameter is invalid for this command line.
CASSI9004S Failed to 'exec' debug server, rc = return-code
The attempt to start a CICS API server under debugger control failed due to an error in DosExecPgm.
CASSI9005E Error, could not inform REM of debug server termination, rc = return-code
The attempt to inform the region manager of the debug server's termination failed due to an error in DosExecPgm.
CASSI9006S Failed to 'exec' debug server, rc = return-code
The attempt to start a CICS API server under debugger control failed due to an error in execlp.
CASSI9007S Debug option animate-option for resource resource-name invalid
The attempt to start a CICS API server under debugger control in the single process region failed due to an illegal command line. The single process region will debug all tasks being run if '/a' is specified on the command line.
CASSI9008I Debug initialization for terminal transaction successful
The server is registered as a debug server for terminal transaction.
CASSI9009I Debug initialization for ALL transaction successful
The server is registered as a debug server for transaction.
CASSI9010S Debug initialization unsuccessful, reason = RC
The debug initialization was unsuccessful.
CASSI9011S Active and server configured working modes do not match
The server working mode does not match the current environment. Either you are starting a 64bit server from a 32bit environment or a 32bit server from a 64bit environment.
CASSI9012E JCL support failed to start. Error returned from casspool, RC=Return code from call to casspool
JCL support is not enabled because call to casspool failed with the inserted return code.
CASSI9013S GLM lock file exists and in use by Applid of the region that has the lock on casglm.lck, ES Cluster Manager cannot start.
The lock file is in use. ES Cluster member started before manager. Or shared resource used by a region not part of the ES Cluster.
CASSI9014S JCL support disabled. GLM lock file creation failed RC = return-code
The lock file could not be created.
CASSI9015S JCL support disabled: RC return-code creating catalog folder path
The Default Allocated Dataset folder could not be created.
CASSI9016S CASGLM.LCK Dataset in use by region Region name using the allocation area. JCL support disabled
The lock file CASGLM.LCK is in use.
CASSI9017S Connection to ES Cluster manager remote-region (sysid sys-id) is disabled, verify and release global locks on ES cluster manager
The CAS gateway connection to remote-region is lost after GLM timeout exceeded.
CASSI9018S Attempt to connect to a disabled ES Cluster manager remote-region (sysid sys-id)
The CAS gateway connection to remote-region has been disabled.
CASSI9019S no connection available to the ES Cluster manager (sysid sys-id)
The CAS gateway connection to sys-id cannot be found.
CASSI9020I Default RNLDEF created in Name of the file containing the RNL definitions (All SYSDSNs are Global resources).
The file ESCLRNLs.cfg does not exits.
CASSI9021S RC Name of the file containing the RNL definitions attempting to create default RNLs file
The default file ESCLRNLs.cfg could not be created.
CASSI9022E RC Name of the file containing the RNL definitions accessing RNLs file .
The default file ESCLRNLs.cfg could not be written to.
CASSI9023E missing or invalid parameter parameter name in RNL record number record number.
Invalid or missing parameter found in an RNLDEF.
CASSI9024I Number of records loaded RNLDEF loaded from ESCLRNLs.cfgNumber of records in error
The ESCLRNLs.cfg file has been loaded.
CASSI9025I RNLDEFs received and installed from ES Cluster Manager Number of records loaded.
All RNLs have been received and loaded from the GLM.

Parent topic: CASSI Error Messages