Messages API500 through API5xx

This group includes messages for the Control-O product.

API560I ENVIRONMENT INITIALIZATION COMPLETE

Explanation: This information message is issued when the Control-O API first connects with the Control-O or CMEM monitor and completes the initialization process.

Corrective Action: No user action is required.

API561E REQUESTED FUNCTION NOT SUPPORTED

Explanation: The requested function is not in the list of supported Control-O API functions.

The Control-O API returns a return code of 08 to the calling routine. The final System Action depends on the calling environment.

Corrective Action: Check the syntax and spelling of the requested function. If necessary, contact your INCONTROL administrator.

API563E IOA SUBSYSTEM subsys INACTIVE. INTERFACE CANNOT BE USED

Explanation: A request has been received through the Control-O API that needs the Control-O or CMEM monitor, but Control-O or CMEM is not active.

The requested activity is aborted.

Corrective Action: Check why Control-O or CMEM is not active. Once the Control-O or CMEM monitor is active again, re-issue the request.

API565E SETOLOC/SETOGLB ERROR CODE= rc REASON= rsn, TEXT= text

Explanation: The Control-O API is unable to execute the AutoEdit request. The API detected an error while trying to resolve or set an AutoEdit expression.

The Control-O API returns a return code of 16 to the calling routine. The final System Action depends on the calling environment.

Corrective Action: Ensure that the AutoEdit expression in the SETOLOC, SETOGLB or RESOLVE functions is correctly written.

The following table shows possible values for the error code (rc) and reason code (rsn), with the explanation of each:

Error 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.
	100	ISGENQ returned a non-zero return code.
	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, 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.
	100	Timeout error. %%$DBROW = %%$DBSETVAR was used to set an IOAVAR variable, but the action could not be serialized for 2 minutes.
	107	No global anchor was passed. Program error.
	108	Field not defined in database.
	109	Requested row is out of range. To correct the problem, on the IOA Variables (IV) screen in ADMIN mode, use the U (Update) option to update the NUMBER OF ROWS attribute. Afterwards, issue the CMEM/Control-O LOADGLOBAL operator command to reload the modified database into memory. Control-M must be down when issuing this command to prevent possible loss of updates.
	110	Unable to lock the Global Variables pool.
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.

API566E IOA SUBSYSTEM subsys NOT RESPONDING TO REQUESTS

Explanation: The IOA subsystem subsys did not terminate rule execution within the expected time frame. The XAM requester, or the Control-O API, waits up to two minutes for the termination of the rule through a DORULE request.

The XAM interface, or the Control-O API, returns a return code of 16 to the calling routine. The final system action depends on the calling environment.

Corrective Action: Review the rule execution results for errors and rectify as appropriate.

API567E IOA SUBSYSTEM subsys INACTIVE

Explanation: The requested service cannot be provided because the subsys IOA subsystem is not up.

The Control-O API, returns a return code of 16 to the calling routine. The final system action depends on the calling environment.

Corrective Action: Start the Control-O or CMEM monitor.

API568E IOA SUBSYSTEM subsys DETECTED AN ERROR

Explanation: An internal error was detected by the subsys IOA subsystem during the execution of a Control-O API request.

The Control-O API returns a return code of 16 to the calling routine. The final System Action depends on the calling environment.

Corrective Action: Do the following:

Check the Control-O or CMEM JOBLOG or SYSLOG for error messages.
Collect information about the functions requested by the Control-O API.
Determine whether or not the Control-O monitor is properly running for ongoing automation which is not related to the Control-O API.
Contact BMC Customer Support.

API569E IOA SUBSYSTEM subsys RETURNED AN INVALID RETURN CODE

Explanation: Due to an internal error, an invalid return code was returned by the subsys subsystem during the execution of a request issued through the Control-O API.

The Control-O API returns a return code of 16 to the calling routine. The final System Action depends on the calling environment.

Corrective Action: Do the following:

Collect information about the functions requested by the Control-O API.
Determine whether or not the Control-O or CMEM monitor is properly running for ongoing automation which is not related to the Control-O API.
Contact BMC Customer Support.

API56AE ERROR IN INAREA FIELDS ADDR= add1, add2 LENGTH len DATA= data_val

Explanation: This diagnostic error message appears when an error has occurred while calling an AutoEdit variable service.

The system action is aborted.

Corrective Action: Contact your INCONTROL administrator.

API56BE ERROR IN RESULT FIELDS ADDR= add, LENGTH len DATA= data_val

Explanation: This diagnostic error message appears when an error has occurred while calling an AutoEdit variable service.

The system action is aborted.

Corrective Action: Contact your INCONTROL administrator.

API56CE INAREA LENGTH+RESULT= xxxx+ xxxx= xxxx > 255

Explanation: This diagnostic error message appears when an error has occurred while calling an AutoEdit variable service.

The system action is aborted.

Corrective Action: Contact your INCONTROL administrator.

API56EE CHECKPOINT GLOBAL VARIABLE DATABASE ioavar TIMED OUT AFTER num SECONDS

Explanation: CHECKPOINT was requested in order to save disk changes made in memory to the ioavar variable database. A timeout occurred while the request was being processed.

The CHECKPOINT request is terminated before completion. However, the changes made to the ioavar database are retained in memory, and a subsequent CHECKPOINT request will write them to disk.

Corrective Action: No user action is required.

API56FE CHECKPOINT GLOBAL VARIABLE DATABASE ioavar ENDED WITH ERROR. RC=16

Explanation: CHECKPOINT was requested in order to save disk changes made in memory to the ioavar variable database. An error occurred while the request was being processed.

The CHECKPOINT request is terminated before completion. However, the changes made to the ioavar database are retained in memory, and a subsequent CHECKPOINT request will write them to disk.

Corrective Action: No user action is required.

API570I INITIALIZATION ENVIRONMENT COMPLETED

Explanation: This information message indicates that Control-O API initialization finished.

Corrective Action: No user action is required.

API573E IOA SUBSYSTEM subsys INACTIVE. INTERFACE CANNOT BE USED

Explanation: A request that requires the Control-O or CMEM monitor was issued through Control-O API, but the monitor is not active.

The action is aborted.

Corrective Action: Activate the Control-O or CMEM monitor, and reissue the request.

API575E SETOLOC/SETOGLB ERROR CODE = rc REASON = rsn, TEXT= text

Explanation: A request to set a local or global variable failed.

The action is aborted.

Corrective Action: Check the return code (rc) and reason code (rsn) in the following tables to determine the reason for the failure. Correct the symbol in the rule definition, and reorder the table. If the return code or reason code is not listed, the error is an internal error, and you should notify BMC Customer Support.

Error 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/TIMEOUT - invalid parentheses
	26	%%$RESPMSG/%%TIMEOUT - too ?pmany values
	27	%%$WAITKSL/TSO/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	LRECL 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	LRECL 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, 44		Global Variable Errors. Reason codes are:
	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
	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

API576E IOA SUBSYSTEM subsys NOT RESPONDING TO REQUESTS

Explanation: A request from the Control-O or CMEM monitor using the Control-O API failed due to timeout, but the subsystem is active.

The action is aborted.

Corrective Action: Check the status of the Control-O or CMEM monitor. If the timeout was the result of a termination process, the problem can be ignored. Otherwise, check for other error messages in the monitor JOBLOG, SYSPRINT or IOALOG, and respond accordingly.

API577E IOA SUBSYSTEM subsys INACTIVE

Explanation: A request from the Control-O or CMEM monitor failed, because the Control-O or CMEM monitor is not active.

The action is aborted.

Corrective Action: Start the Control-O or CMEM monitor and reissue the request.

API578E IOA SUBSYSTEM subsys DETECTED AN ERROR

Explanation: A request from the Control-O or CMEM monitor failed, because the CTOWTO Control-O or CMEM executor module detected an error. The request was issued using the Control-O API.

The action is aborted.

Corrective Action: Check the Control-O or CMEM job log or syslog for error messages, and correct accordingly.

API579E IOA SUBSYSTEM subsys RETURNED AN INVALID RETURN CODE

Explanation: A request from the Control-O or CMEM monitor failed, because the CTOWTO Control-O or CMEM executor module returned an invalid return code. The request was issued by means of the Control-O API.

The action is aborted.

Corrective Action: Contact BMC Customer Support.

API57AE ERROR IN INAREA FIELDS ADDR= add1, add2 LENGTH len DATA= value

Explanation: An internal error occurred in the INAREA fields while calling an API service.

The action is aborted.

Corrective Action: Notify BMC Customer Support.

API57BE ERROR IN RESULT FIELDS ADDR= add, LENGTH len DATA= value

Explanation: An internal error occurred in the RESULTS fields while calling an API service.

The action is aborted.

Corrective Action: Notify BMC Customer Support.

API57CE INAREA LENGTH length3 + RESULT LENGTH length2 > 255

Explanation: Due to an internal error, the sum of the INAREA LENGTH and the RESULT LENGTH exceeded the maximum allowable data length of 255 characters when calling the API service.

The action is aborted.

Corrective Action: Notify BMC Customer Support.

API57EE CHECKPOINT GLOBAL VARIABLE DATABASE dbName ENDED DUE TO TIMEOUT AFTER num SECONDS

Explanation: A timeout occurred during checkpoint processing of the Global Variables database. The checkpoint request terminated.

Corrective Action: Check the job log of the Control-O or CMEM monitor for additional messages that explain the cause of the problem. If the request ended OK after the timeout occurred, ignore the problem. Otherwise, respond accordingly.

Parent Topic

API messages