Messages CTO400 through CTO4xx

This group includes messages for the Control-O product.

CTO403I text

Explanation: This information message is an internal message used by the Control-O or CMEM USS (UNIX Services for OS/390) interface module to trigger a CMEM event using ON DSNEVENT and ON STEP in the USS address space. The message indicates that a forked process started. The text may include unprintable characters.

Corrective Action: No action is required.

CTO410I ALLOCATION OF GLOBAL AUTOEDIT LIBRARY STARTED

Explanation: This information message indicates the normal start of the CTODFG program that allocates the Global library.

Corrective Action: No action is required.

CTO411E INVALID PARAMETERS: parms

Explanation: The CTODFG program detected invalid parameters.

The program terminates with a return code of 08.

Corrective Action: Verify the parameters, correct them, and resubmit the utility.

CTO412E THIS CPU HAS SMFID cpuSmfId AND NOT parmSmfId

Explanation: The SMFID of the CPU on which the CTODFG program is running does not match the SMFID passed as a parameter to the program.

The variables in this message are:

• cpuSmfId - the SMFID of the CPU on which the CTODFG program is running
• parmSmfId - the SMFID passed as a parameter to the program

The program terminates with a condition code of 08.

Corrective Action: Verify the SMFID of the CPU on which Control-O is running, and resubmit the utility with the correct parameter.

CTO416E DYNAMIC ALLOCATION ERROR RC=rc,ERROR=rsn, DSN=dsn

Explanation: The CTODFG program failed while attempting to dynamically allocate the Global library.

The CTODFG program terminates with a condition code of 08.

Corrective Action: For an explanation of the return and reason codes, see the IBM OS/390 Authorized Assembler Services Guide.

CTO417E CTMMEM ERROR, RC= rc

Explanation: The CTODFG program received return code rc from the CTMMEM module while attempting to update the Global library. The error occurred when the CTODFG program attempted to create the $$GLOBAL member in the Global library.

Possible causes indicated by values of rc:

• 08 - The region size is too small.
• 28 - The data set is in use.
• 32 - Internal error.
• 56 - The library is full or an abend occurred.
• 64 - The member already exists.

The CTODFG program terminates with a condition code of 08.

Corrective Action: If possible, correct the problem with the library, and resubmit the utility. If the error persists, contact BMC Customer Support.

CTO418E ALLOCATION OF GLOBAL AUTOEDIT LIBRARY FAILED

Explanation: Allocation of the Global library failed. This error message, which is issued by the CTODFG program, is preceded by another message detailing the reason for the failure.

The CTODFG program terminates with a condition code of 08.

Corrective Action: See the preceding message.

CTO419I ALLOCATION OF GLOBAL AUTOEDIT ENDED

Explanation: This information message indicates that the CTODFG program successfully allocated the Global library.

Corrective Action: No action is required.

CTO421I CTOCPS STARTED

Explanation: This information message indicates that the CTOCPS program, which compresses or verifies the Global AutoEdit library, started.

Corrective Action: No action is required.

CTO422S COMPRESS REQUIRED FOR GLOBAL AUTOEDIT VARIABLES LIBRARY

Explanation: The Global AutoEdit library needs to be compressed but automatic compression was disabled. Control-O does not automatically compress the Global AutoEdit library because N is specified for the GLBCOMP parameter in the CTOPARM member.

The library is not compressed. Command WRITEGLOBAL fails.

Corrective Action: Do one of the following:

• Use site compression procedures to compress the Global AutoEdit library. Ensure that the Global AutoEdit library is large enough to prevent D37 abends between periodic compressions.
• For information on how to set automatic compression, see the Control-O installation chapter in the INCONTROL for z/OS Installation Guide.

CTO423S DYNAMIC ALLOCATION ERROR DURING COMPRESS, ERROR= rc/rsn/dsn

Explanation: Dynamic allocation (SVC 99) failed. The CTOCPS program uses SVC 99 to dynamically allocate and deallocate the Global AutoEdit library and its copy file.

The variables in this message are:

• rc - the return code of the error
• rsn - the reason for the failure
• dsn - the name of the data set that cannot be allocated

The CTOCPS program ends with a return code of 08. The WRITEGLOBAL command fails.

Corrective Action: For an explanation of the return code (rc) and the reason code (rsn), see the IBM manual MVS Programming: Authorized Assembler Services Guide. Until this problem is resolved, use site compression procedures to compress the Global AutoEdit library.

CTO424I FIRST COMPRESSION PHASE STARTED - LIBRARY UNLOAD

Explanation: This information message indicates that the backup phase of the CTOCPS program has begun.

Corrective Action: No action is required.

CTO425I SECOND COMPRESSION PHASE STARTED - COMPRESS IN PLACE

Explanation: This information message indicates that the compress in place phase of the CTOCPS program has begun.

Corrective Action: No action is required.

CTO426I CTOCPS ENDED

Explanation: This information message indicates that the CTOCPS program has successfully completed compressing the Global AutoEdit library.

Corrective Action: No action is required.

CTO427S IEBCOPY RETURNED A NON-ZERO COMPLETION CODE

Explanation: IEBCOPY could not complete its task.IEBCOPY is invoked internally by the CTOCPS program to copy or compress a data set.

The CTOCPS program ends with a return code of 08. The WRITEGLOBAL command fails.

Corrective Action: If your system programmer can not resolved the problem, contact your INCONTROL administrator. Until this problem is resolved, use site compression procedures to compress the Global AutoEdit library.

CTO428S CTOCPS RECEIVED AN INVALID PARAMETER LIST

Explanation: The CTOCPS program received a parameter list with an unexpected format. This message indicates an internal error.

The CTOCPS program ends with a return code of 08. The WRITEGLOBAL command fails.

Corrective Action: Contact BMC Customer Support. Until this problem is resolved, use site compression procedures to compress the Global AutoEdit library.

CTO429S PREVIOUS COMPRESS FAILED. GLOBAL LIBRARY CANNOT BE RESTORED FROM BACKUP

Explanation: Compression cannot be performed because the Global AutoEdit library was corrupted during the last compression and no valid backup exists.

During CTOCPS processing, the $$COMPST control member is repeatedly updated to track completed operations. The contents of this control member indicate that the last time CTOCPS ran, Control-O did not successfully compress the Global AutoEdit library. As a result, there is no usable backup. Therefore, the Global AutoEdit library cannot be restored.

Control-O stops loading Global variables.

Corrective Action: If you are unable to restore the Global AutoEdit library, run the NEWGLOB job, which renames the corrupted Global AutoEdit library, and creates a new one with the old name using Global variable information from memory. The NEWGLOB Job is in the INSTWORK library.

For more information, see the section on automatic compression of the global AutoEdit library in the INCONTROL for z/OS Administrator Guide.

CTO430S ERROR READING AUTO-COMPRESS CONTROL-MEMBER $$COMPST

Explanation: The CTOCPS program was unable to read the $$COMPST control member. The $$COMPST member is defined by the NEWGLOB job during installation of Control-O. The CTOCPS program checks the $$COMPST control member to determine if the last automatic compression was successfully completed.

The CTOCPS program ends with a return code of 08. Commands READGLOBAL and WRITEGLOBAL are ignored.

Corrective Action: Ensure that the $$COMPST control member exists in the Global AutoEdit library, and if the NEWGLOB job was not run during installation, submit this job. If the problem is not resolved, contact your INCONTROL administrator.

CTO431S ERROR WRITING AUTO-COMPRESS CONTROL-MEMBER $$COMPST

Explanation: The CTOCPS program was unable to write the $$COMPST control member. The $$COMPST member is defined by the NEWGLOB job during installation of Control-O.

The CTOCPS program ends with a return code of 08.

Corrective Action: Ensure that the $$COMPST control member exists in the Global AutoEdit library, and if the NEWGLOB job was not run during installation, submit this job. If the problem is not resolved, contact your INCONTROL administrator.

CTO432I RESTORE OF GLOBAL VARIABLES LIBRARY STARTED

Explanation: This information messages indicates that the CTOCPS program has begun restoring the Global AutoEdit library. The CTOCPS program was unable to read the Global AutoEdit library, but the backup file is intact.

CTOCPS restores the Global AutoEdit library from the backup file.

Corrective Action: No action is required.

CTO433S ABEND abCode INTERCEPTED DURING COMPRESS

Explanation: Recovery routine ESTAE intercepted an abend during execution of a READGLOBAL or WRITEGLOBAL command.

The READGLOBAL or WRITEGLOBAL command is ignored.

Corrective Action: Check and correct the names of the Global AutoEdit library and the backup copy. If these libraries are corrupt (for example, by a disk crash), restore them from a backup.

CTO434I COMPRESS OF GLOBAL VARIABLES LIBRARY STARTED

Explanation: This information message indicates that the CTOCPS program has begun compressing the Global AutoEdit library.

Corrective Action: No action is required.

CTO440I READ/WRITE GLOBAL VARIABLES STARTED

Explanation: This information message indicates that the CTOVPL program, which is responsible for loading and writing global variables, has begun read/write to the Control-O global pools.

Corrective Action: No action is required.

CTO441S INVALID PARAMETERS

Explanation: The CTOVPL program received an incorrect parameter list while executing a LOADGLOBAL or WRITEGLOBAL command.

This message indicates an internal error.

Corrective Action: Contact BMC Customer Support.

CTO442S ERROR OPENING DAGLBLST

Explanation: The CTOVPL program was unable to open the Global Pool List during execution of a LOADGLOBAL or WRITEGLOBAL command.

The Global Pool List is defined by the DAGLBLST DD name in the procedure of the Control-O monitor.

The LOADGLOBAL/WRITEGLOBAL command is ignored.

Corrective Action: Check and correct the DD name and related data set specifications in the Control-O monitor procedure.

CTO443S POOL poolid - GETMAIN ERROR

Explanation: The user issued a LOADGLOBAL command with the specified Variable Global pool. However, the variables in this pool could not be loaded.

There is insufficient storage in ECSA for loading Global variables from the specified Global variable pool.

Command LOADGLOBAL is ignored.

Corrective Action: Increase the size of ECSA storage.

CTO444S POOL poolid - ERROR LOADING GLOBAL VARIABLES

Explanation: Control-O could not load variables from the specified Global variable pool.

This message is preceded by messages describing the cause of the error.

Command LOADGLOBAL is ignored.

Corrective Action: See the accompanying messages for details about the cause of the error and possible solutions.

CTO445S POOL poolid - ERROR WRITING GLOBAL VARIABLES

Explanation: Control-O could not write variables to the specified Global pool.

This message is preceded by messages describing the cause of the error.

Command WRITEGLOBAL is ignored.

Corrective Action: See the accompanying messages for details about the cause of the error and possible solutions.

CTO446S POOL poolid - NOT FOUND IN MEMORY

Explanation: The user specified a LOADGLOBAL/WRITEGLOBAL command, but Control-O could not locate the specified pool.

Control-O could not locate the specified pool while executing a LOADGLOBAL/WRITEGLOBAL command and could not locate the control block for the specified pool name. This usually happens when either the specified pool name is not defined in the Global Pool List member (DAGLBLST) or the specified member was never loaded.

The LOADGLOBAL/ WRITEGLOBAL command is ignored.

Corrective Action:

1. Define the pool in the DAGLBLST member.
2. Use the LOADGLOBAL command to load the pool.

CTO447S FREEMAIN INTERNAL ERROR

Explanation: The CTOVPL program was unable to free internal control blocks while executing a LOADGLOBAL or WRITEGLOBAL command.

This message indicates an internal error.

Corrective Action: Contact BMC Customer Support.

CTO448S ERROR FREEING AUTO-EDIT INTERNAL BLOCKS

Explanation: The CTOVPL program was unable to free internal control blocks while executing a LOADGLOBAL or WRITEGLOBAL command.

This message indicates an internal error.

Corrective Action: Contact BMC Customer Support.

CTO449S ERROR FREEING GLOBAL MEMBER INTERNAL BLOCKS

Explanation: Control-O could not free internal control blocks of a Global variable pool.

Control-O could not free internal control blocks while executing a LOADGLOBAL/WRITEGLOBAL command. This message indicates an internal error.

Corrective Action: Contact BMC Customer Support.

CTO44AS ERROR RELEASING COUPLING FACILITY RESOURCES

Explanation: Old data was not successfully deleted from the Coupling facility.

When newly loaded variables became effective after a LOAGLOBAL operation for an XAE (SYSPLEX-wide AutoEdit) database, Control-O or CMEM failed to delete the old copy of the AutoEdit databases from the Coupling facility.

Old data from the Coupling facility structure is not deleted.

As a result, unnecessary data may accumulate in the space allocated for the Coupling facility structure until the space is exhausted.

Corrective Action: Shut down all Control-O or CMEM monitors as soon as possible and restart them, one at a time.

In addition, send the sysout files for your monitor to BMC Customer Support for analysis.

CTO44BE ERROR SWITCHING COUPLING FACILITY INFORMATION

Explanation: During an attempt to switch to the new version of XAE database variables that were being loaded, an error occurred.

XAE variables are loaded in three steps. They are loaded to ECSA, copied to the Coupling facility and then marked effective in the Coupling facility. This message indicates a failure during the third step.

During the implicit LOADGLOBAL operation at startup, Control-O initialization fails. During ongoing operations, only the LOADGLOBAL operation fails.

Corrective Action: Send all the Control-O sysout files and the contents of the DAGLBLST library member to BMC Customer Support for analysis.

CTO44CE request (X’ code’) FOR STRUCTURE structureName FAILED. REASON: rsn

Explanation: A request to the XAE structure failed. The message details the request name and code, and the reason for the failure.

Additional information is written to DATRACE.

Corrective Action: Check that all XAE structures are allocated and that Control-O or CMEM did not lose a connection to them. If a connection was lost, restart Control-O or CMEM. Otherwise, contact BMC Customer Support for assistance.

CTO450S POOL poolid IS NOT SPECIFIED IN DAGLBLST

Explanation: Control-O could not locate the poolid pool in the DAGLBLST Global Variable Pool List member.

This message is normally issued in response to a failure of a LOADGLOBAL/ WRITEGLOBAL command in the DAGLBLST Global Pool List member.

The LOADGLOBAL/WRITEGLOBAL command is ignored.

Corrective Action: Do the following:

1. Define the pool in the DAGLBLST Global Pool List member.
2. Use the LOADGLOBAL command to load the pool.

CTO451S INVALID CARD IN DAGLBLST

Explanation: The CTOVPL program detected an invalid statement in the Global Pool List.

The Global Pool List is defined in the DAGLBLST DD statement in the Control-O monitor procedure.

The LOADGLOBAL/ WRITEGLOBAL command is ignored.

Corrective Action: Check and correct the Global Pool List member.

CTO452S POOL poolid IS PROTECTED. IT CANNOT BE UPDATED

Explanation: Control-O cannot execute a WRITEGLOBAL command for the poolid Global Variable pool.

The poolid pool name is defined in the DAGLBLST Global Variable Pool List member as protected or temporary.

The WRITEGLOBAL command is ignored.

Corrective Action: Check the definition of the pool in the DAGLBLST member and correct the definition if necessary.

CTO453S pooling ERROR HANDLING PNX BLOCKS

Explanation: This message indicates an internal error.

Corrective Action: Contact BMC Customer Support.

CTO454S POOL poolid - AUTOEDIT ERROR, RC= rc, REASON= rsn

Explanation: Control-O detected an invalid AutoEdit expression in the poolid Global Variable pool at startup or while executing the LOADGLOBAL command.

The poolid Global variable specified in the AutoEdit expression was not loaded. The error was caused for one of the following reasons:

• A mistake was made when the POOL member was manually edited.
• There was an internal error.

Depending on poolid type, the pool is stored in one of two locations: the Global Variables Library or a Control-O AutoEdit Variable database.

The AutoEdit statement is ignored. The LOADGLOBAL command continues with the next line in the DAGLBLST member.

Corrective Action:

1. For an explanation of the return code and reason code included in this message, see the following table.
2. Check the source of the AutoEdit expression.
3. Correct the error and reissue command LOADGLOBAL.
4. If the problem is due to an internal error, contact BMC Customer Support.

   Return Code ( rc )	Reason Code ( rsn )	Explanation
   04	GETMAIN or FREEMAIN error
   	1 through 6	GETMAIN failure
   	7 through 10	FREEMAIN failure
   08	Variable not found
   	13	Variable not found and RESOLVE flag is on.
   	36	%%$COMMSYS value length error.
   	68	%%$TIMEINT first argument is not a valid date.
   	69	%%$TIMEINT second argument is not a valid date.
   	74	%%$X2C argument length is greater than 4.
   	88	%%$DOLIMIT first argument is not numeric.
   	89	%%$RULE functions argument is out of rule stack.
   	90	%%$RULE functions argument is not numeric.
   	98	Global variable pool not found.
   	980	Internal error - global pool or database not found
   	982	Internal error - global pool or database not found
   12	Syntax error or general error
   	11	Empty SET command.
   	15	Empty IF command.
   	21	%% not found in SET command.
   	22	Separator not found after %%.
   	23	‘=’ not found in SET command.
   	24	%%$TIMEOUT value not numeric.
   	25	%%$RESPMSG or %%$TIMEOUT - invalid parentheses.
   	26	%%$RESPMSG or %%$TIMEOUT - too many values.
   	27	%%$WAITKSL or %%$TSO or %%$CMD - invalid value (not YES/NO).
   	28	%%$TIMEOUT - value too large.
   	29	%%$‘STATID value length error.
   	30	%%$AUTOLOG value length error.
   	37	%%$AUTOSYS value length error.
   	41	Function arguments not separated.
   	42	Too few function arguments.
   	45	CTMLINE# PARAMETER NOT NUMERIC when trying to set %%$CTMLINE# to a non-numeric value.
   	46	CTMLINE# > CTMLINES when trying to set %%$CTMLINE# to a value greater than %%$CTMLINES.
   	47	CTMLINE# < 0 when trying to set %%$CTMLINE# to a value less than 0.
   	52	%%$SUBSTR 2nd argument not numeric.
   	53	%%$SUBSTR 3rd argument not numeric.
   	54	%%$SUBSTR 2nd argument out of range.
   	55	%%$SUBSTR 3rd argument out of range.
   	56	%%$RESOLVE argument not recognized.
   	57	%%$RANGE 1st argument not numeric.
   	58	%%$RANGE 2nd argument not numeric.
   	59	%%$RANGE 1st argument out of range.
   	60	%%$RANGE 2nd argument out of range.
   	61	%%$RANGE is too narrow.
   	62	%%$CALCDATE 1st argument not in valid format.
   	63	%%$CALCDATE 2nd argument not in valid format.
   	64	%%$TIMEINT 1st argument is not 11 digits in length.
   	65	%%$TIMEINT 1st argument is not numeric.
   	66	%%$TIMEINT 2nd argument is not 11 digits.
   	67	%%$TIMEINT 2nd argument is not numeric.
   	71	More than one operator in one line.
   	72	Less than two operands for an operator.
   	73	More than two operands for an operator.
   	75	%%$D2X argument length is greater than 10.
   	76	%%$D2X argument is not numeric.
   	77	%%$D2X argument number is greater than 2147483647 (2G).
   	78	%%$X2D argument length is greater than 8.
   	79	%%$X2D argument has an invalid character.
   	81	First operand in arithmetic operation is not numeric.
   	82	Second operand in arithmetic operation is not numeric.
   	83	%%$DIV 2nd operand is 0.
   	84	First operand is greater than 2G.
   	85	Second operand is greater than 2G.
   	86	Result of %%$PLUS case overflow.
   	87	Result of %%$MINUS case overflow.
   	91	Logical operand not numeric.
   	92	Numeric logical operand out of range.
   	93	Invalid logical operator.
   	94	Logical atomic expression expected but not found.
   	95	Unbalanced parentheses in logical expression.
   	96	Too many nested parentheses in logical expression.
   	97	Unbalanced quotes.
   	99	%%$GLOBAL value length error.
   16	Errors reading the global member
   	08	Insufficient memory.
   	12	Member not found.
   	16	DSN is not a library.
   	20	DSN is not fixed.
   	24	Logical record length is not 80.
   	28	Data set in use.
   	36	Data set not in catalog.
   	40	Dynamic allocation failed.
   	52	Error when opening/processing a directory
   	56	An abend was intercepted.
   20	Errors writing the global member
   	08	Insufficient memory.
   	12	Member not found.
   	16	DSN is not a library.
   	20	DSN is not fixed.
   	24	Logical record length is not 80.
   	28	Data set in use.
   	36	Data set not in catalog.
   	40	Dynamic allocation failed.
   	52	Error when opening/processing a directory
   	56	An abend was intercepted.
   24	Program buffers shortage
   	12	Not enough space in RSL buffer.
   	32	Not enough space in VCB for name and value. Variable name and data are too long.
   	43	Arguments too long (ARG buffer overflow).
   32	Program errors
   	100	No last non-blank for non-blank value in SET command.
   	101	No succeeding RSL for adjoining variables.
   	102	Problems in PUTVAR while initiating.
   	103	Too many arguments requested from PARSARGS.
   	104	Problems calculating weekday.
   	105	Invalid SET system variable.
   	106	No local anchor was passed.
   	107	No global anchor was passed.
   	109	No MCT or SWT present in %%$IPLDATE for date formatting WO0816*.
   36, 40, and 44	Global variables errors
   	04	Empty chain.
   	08	End of chain.
   	12	PNXH header error.
   	16	PLBH header error.
   	20	CTMMSK mash error, RC from IS is > 4.
   	24	Pool is protected.
   	32	Unable to get XAE information.
   	33	Machine is not participating on XAE.
   	34	Attempt made to set an XAE type 1 database variable in another system image.
   	98	Pool not found.
   	107	No global anchor was passed. Program error.
   	108	Field not defined in database.
   	109	Requested row is out of range.
   48	Parse errors
   	08	Invalid type.
   	12	Place holder error.
   	16	Position specification too long.
   	20	Non numeric.
   	24	Position null.
   	28	Invalid variable. Specified variable is greater than 256, or the variable name is too long.
   	32	String error.
   	36	Invalid TPE type.
   	40	Section vector overflow.
   	44	Variable buffer overflow.
   	107	No global anchor was passed.

CTO455I POOL poolid HAS BEEN LOADED TYPE= pool_type ROWS= loaded_variables / max_variables_allowed

Explanation: This information message indicates that the Global Variable pool poolid was successfully loaded. If pool_type starts with DB, S1 or S2 the numbers in ROWS= are the loaded value and the maximum variables allowed. In other cases the values will be 0.

Corrective Action: No action is required.

CTO457W DATABASE database NOT FOUND IN DATABASES FILE

Explanation: During Control-O or CMEM initialization, Control-O or CMEM failed to load the Global AutoEdit Variable database because the database does not exist in the Global AutoEdit Variable Database file. The member pointed to by the DAGLBLST DD statement contains a list that specifies the Control-O Load Global AutoEdit Variable databases and the IOA Load Global AutoEdit Variable database. The required database that appears in the list does not exist in the Global AutoEdit Variable Database file.

Control-O or CMEM initialization continues.

Corrective Action: Notify the INCONTROL administrator

CTO458S POOL poolid - ERRORS WHILE READING POOL

Explanation: Control-O could not read the poolid Global variable pool during execution of command LOADGLOBAL.

The poolid pool is not loaded.

Corrective Action: Verify that the Global pool is in the Global AutoEdit library and that the library is not corrupted.

CTO459I READ/WRITE GLOBAL VARIABLES ENDED

Explanation: This information message indicates that the CTOVPL program successfully completed execution of command LOADGLOBAL/WRITEGLOBAL.

Corrective Action: No action is required.

CTO45AW WARNING! poolName CONVERTED FROM Stype TO DBtype

Explanation: There is a conflict between inconsistent IOAPLEX and DAGLBLST settings, as follows:

• In IOAPLEX, the ENABXES parameter or ENABXAE parameter is set to N.
• In DAGLBLST, the XAE database is specified as S1 type and S2 type, where type is the one of the following database types:
  • TEMP
  • PROT
  • INPUT
  • INOUT

Control-O loads the database as a standard, or non-XAE, database. Database loading continues.

Corrective Action: Check whether, and how, the reduced capability affects any applications that use the downgraded XAE pool.

CTO45BE -- MEMBER TYPE ERROR ---

Explanation: Control-O or CMEM monitor encounter an invalid POOL TYPE in control record in the DAGLOBAL list file.

Corrective Action: No action is required.

CTO45CE --- KEYWORD NOT RECOGNIZED ---

Explanation: Control-O or CMEM monitor encounter an invalid keyword in a record in the DAGLOBAL list file.

Corrective Action: No action is required.

CTO45DE --- ALL BLANKS - ERROR ---

Explanation: Control-O or CMEM monitor the control record in the DAGLOBAL list file is all blank.

Corrective Action: No action is required.

CTO45EE --- NO BLANKS - ERROR ---

Explanation: Control-O or CMEM monitor encounter an empty control record format in the DAGLOBAL list file.

Corrective Action: No action is required.

CTO45FE --- LESS THAN ZERO ---

Explanation: Control-O or CMEM monitor encounter an invalid control record value in the DAGLOBAL list file.

Corrective Action: No action is required.

CTO45GE --- INVALID CARD FORMAT ---

Explanation: Control-O or CMEM monitor encounter an invalid control record format in the DAGLOBAL list file.

Corrective Action: No action is required.

CTO45HE RECORD= record

Explanation: Control-O or CMEM monitor encounter an error in the DAGLOBAL list file the previous error messages.

The record has been rejected.

Corrective Action: Correct the record and LOADGLOBAL or WRITEGLOBAL as necessary.

CTO45IE MAXIMUM NUMBER OF ROWS max-num-rows EXCEEDED WHILE LOADING POOL pool-name. LOAD STOPPED.

Explanation: During LOADGLOBAL of AutoEdit POOL pool-name, excessive rows were encountered beyond the maximum number of defined rows max-num-rows in screen IV.

The loading stops.

Corrective Action: If the unloaded AutoEdit variable is required, increase the maximum number of rows for the pool using the screen IV and re-issue the LOADGLOBAL command.

CTO45JI XAE TYPE 2 POOL pool-name HAS NOT BEEN LOADED BECAUSE ANOTHER LPAR HAS ALREADY LOADED IT.

Explanation: During initial loading of AutoEdit POOLs, loading of the POOL pool-name, has been skipped because the POOL has already been loaded by Control-O/CMEM on another LPAR.

Corrective Action: No action is required.

CTO45KE DATABASE IOAVAR IS ALREADY LOADED AS DBINOUT ON ANOTHER LPAR

Explanation: IOAVAR is the database that Control-M uses to store pool AutoEdit variables (%%\M\..). It can be defined (in IOAGLBVL) as either DBINOUT or S2INOUT. DBINOUT should be used only when IOAVAR is loaded by CMEM or Control-O in a single LPAR. Defining the same IOAVAR as DBINOUT in multiple LPARs creates a serious integrity exposure.

This message indicates that IOAVAR has already been loaded on another LPAR as DBINOUT and loading it again in this LPAR is unsafe. It may result in each LPAR having a different image of the database (different variable names, different variable values) and in one LPAR overwriting the other LPAR’s database when issuing WRITEGLOBAL (automatically or manually).

Corrective Action: If IOAVAR (AutoEdit variables) is not in use, this message can be ignored and no action is necessary.

If IOAVAR is in use, enable IOAPLEX and define IOAVAR as XES AutoEdit facility (XAE) Type 2 (S2INOUT). Defining IOAVAR as S2INOUT uses the XES AutoEdit facility (XAE), which allows for resolution of variables on a Sysplex-wide level by utilizing Coupling Facility structures. For more information, see "Step 7.6 – IOAPLEX considerations (optional)" in the INCONTROL for z/OS Installation Guide: Installing, and "IOAVAR Database" and "using XAE Type Databases Instead of Standard Type Databases" in the INCONTROL for z/OS Administrator Guide.