Messages XAM500 through XAM5xx

This group includes messages for the Control-O product.

XAM561E REQUESTED FUNCTION NOT SUPPORTED

Explanation: The requested function is not in the list of supported XAM functions.

The XAM interface 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.

XAM562E INTERNAL RESOURCES EXHAUSTED

Explanation: The space in an internal table is exhausted. The XAM interface keeps an internal table of all XAM activities in the address space. The table can contain a maximum 256 concurrent TCBs requesting XAM services. There is no address space for a new XAM user.

Some TSO, REXX, or CLISTs running in the address space probably did not execute the TERM(inate) function, which releases the acquired XAM resources.

The XAM interface returns a return code of 16 to the calling routine. The final System Action depends on the calling environment.

Corrective Action: Determine why there is insufficient space, and correct the problem accordingly.

XAM563E IOA SUBSYSTEM subsys INACTIVE. INTERFACE CANNOT BE USED

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

The requested activity is aborted.

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

XAM564E CTO ENVIRONMENT NOT PROPERLY INITIALIZED

Explanation: The XAM interface did not find the control blocks belonging to the calling routine. Every requester of XAM services uses a set of control blocks to provide the necessary AutoEdit Environment. The XAM interface did not find the blocks belonging to this requester.

The XAM interface returns a return code of 16 to the calling routine. The final system action depends on the calling environment.

Corrective Action: Execute the INIT function of XAM under the current requester.

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

Explanation: XAM is unable to execute the AutoEdit request. XAM detected an error while trying to resolve or set an AutoEdit expression.

The XAM interface 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.
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.

XAM566E 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 waits up to two minutes for a DORULE request to terminate the rule. If no such request is received within two minutes, this message is displayed.

The XAM interface 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.

XAM567E IOA SUBSYSTEM subsys INACTIVE

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

The XAM interface 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 monitor.

XAM568E IOA SUBSYSTEM subsys DETECTED AN ERROR

Explanation: An internal error was detected by the IOA subsystem subsys during the execution of a XAM DORULE request.

The XAM interface 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 XAM interface.
Determine whether or not the Control-O monitor is properly running for ongoing automation which is not related to XAM.
Contact BMC Customer Support.

XAM569E IOA SUBSYSTEM subsys RETURNED AN INVALID RETURN CODE

Explanation: Due to an internal error, an invalid return code was returned by the subsystem subsys during the execution of a XAM DORULE request.

The XAM interface 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 XAM interface.
Determine whether or not the Control-O monitor is properly running for ongoing automation which is not related to XAM.
Contact BMC Customer Support.

XAM56AW SOME LOCAL VARIABLES NOT COPIED FROM XAM TO RULE, REASON=rsn

Explanation: A request was made to execute a Control-O rule by means of the DORULE function of the XAM interface. However, by the time the request was made, the XAM program that was executing had created an excessive number of local AutoEdit variables. The XAM service cannot share all these local AutoEdit variables with the Control-O rule, so some are discarded before the rule is given control.

In this message, rsn is an internal reason code used by BMC Customer Support.

The DORULE function continues, and control is given to the rule, but some local AutoEdit variables that cannot be copied to the rule environment are discarded. These discarded local AutoEdit variables are not available to the executed rule, nor are they available to the original XAM program once execution of the rule is complete.

Corrective Action: Use less local AutoEdit variables in the XAM program. You may be able to achieve this by using global, rather than local, AutoEdit variables.

If the problem persists, contact BMC Customer Support.

XAM56BW SOME LOCAL VARIABLES NOT COPIED BACK FROM RULE TO XAM, REASON=rsn

Explanation: A request was made to execute a Control-O rule by means of the DORULE function of the XAM interface. However, by the time the rule finished executing, an excessive number of local AutoEdit variables had been created. The XAM service cannot share all these local AutoEdit variables with the original environment (the calling XAM program), so some are discarded before returning from the rule.

In this message, rsn is an internal reason code used by BMC Customer Support.

Execution of the DORULE request is completed, and control returns to the calling XAM program. However, some of the local AutoEdit variables that cannot be copied to the environment of the calling program are discarded. These discarded local AutoEdit variables are then no longer available to the original XAM program.

Corrective Action: Use less local AutoEdit variables in the XAM program and in the Control-O rule that you were executing. You may be able to achieve this by using global, rather than local, AutoEdit variables.

If the problem persists, contact BMC Customer Support.

XAM56EW CONTROL-O MONITOR IS NOT ACTIVE. IOA SUBSYSTEM subsystem_name

Explanation: XAM discovered that Control-O monitor is not active.

The XAM function failed.

Corrective Action: Validate that Control-O monitor is active in the system that the XAM is executing. If Control-O monitor is not active, request the operator to start it and then perform the XAM function again.

XAM56FW CONTROL-O MONITOR INTERFACE ERROR RC=##. IOA subsystem_name

Explanation: This is an internal error that might be created when the XAM interface returns a return code greater than 4. In most cases it occurs when the XAM function is performed when Control-O monitor did not complete its startup or it started its shutdown.

The XAM function failed.

Parent Topic

XAM messages