Previous Topic

Next Topic

Book Contents

Book Index
Messages CTO500 through CTO5xx

This group includes messages for the Control-O product.

CTO500I INPUT LEN= inplen REC= inputRecordMsg

Explanation: This information message is generated when the CTOTEST Control-O utility is invoked.

Corrective Action: This message is sent to CTOTEST. It echoes the input record.

CTO501I func OF RULE TABLE(S) STARTED

Explanation: This information message indicates that the function func started on the rule tables.

Corrective Action: No action is required.

CTO501S OPEN FAILED FOR DDNAME CMDMSGFL

Explanation: The attempt to open input file CMDMSGFL failed.

Possible causes are:

CTOTEST execution terminates.

Corrective Action: Check if the CMDMSGFL DD statement is present in the JCL.

CTO502S INPUT PARAMETER ERROR

Explanation: The subsystem name input parameter is invalid or missing.

CTOTEST execution terminates.

Corrective Action: Check if PARM= subsystemName is present in the parameter string.

CTO503I RC rc LEN= len REC= msgText

Explanation: This information message is generated when the CTOTEST Control-O utility is invoked.

The variables in this message are:

Corrective Action: No action is required.

CTO503S RULE ORDER LIST IS EMPTY. DDNAME="DARULLST"

Explanation: Open of rule list data set failed (the DARULLST/DACTMLST DD statement).

The message may be due to one of the following reasons:

The Control-O/CMEM monitor shuts down or continues processing according to the status of the monitor.

Corrective Action: Correct the JCL and restart the Control-O/CMEM monitor.

CTO504S INVALID DATA IN RULE ORDER LIST CARDS

Explanation: Invalid data has been found in the rule order list. See INCONTROL for z/OS Administrator Guide for valid format information.

Corrective Action: Check the format of the rule list in the PARM library; correct and restart the Control-O/CMEM monitor.

CTO505S MEMBER memName NOT FOUND IN LIBRARY lib

Explanation: The memName member in the rule order was not found in library lib.

The member (rule table) may be specified incorrectly or may be missing from the library.

The rule table is not ordered.

Corrective Action: Check and correct the member specification; reorder the rule table.

CTO506S ORDER OF TABLE tableName RULE ruleName FAILED

Explanation: The order of rule ruleName from table tableName failed. Prior messages usually explain why the rule table could not be ordered.

The rule is not be ordered.

Corrective Action: Check earlier messages for reasons the rule order failed. Correct as necessary, and reorder the rule table.

CTO507I LOAD ENDED FOR TABLE table LIBRARY lib

Explanation: This information message indicates that after ordering or forcing a Control-O rule table, loading of rules from the table ended.

Corrective Action: No action is required.

CTO508I {ORDER | FORCE} OF RULE TABLE(S) ENDED

Explanation: This information message indicates that Order or Force of the Control-O rule table ended.

Corrective Action: No action is required.

CTO509I NUMBER OF TABLES numtbl PROCESSED. numrul1 RULES LOADED AND numrul2 RULES REJECTED

Explanation: This information message indicates the number of tables processed, and the number of rules that were loaded or deleted (not loaded) as a result of an ORDER or FORCE request. This information can be used for manual verification purposes.

Corrective Action: Check the results to ensure that the rule loading was performed correctly.

CTO50BE HOLD BY jobId ASID asid ON SYSTEM systemId

Explanation: An ORDER or FORCE command to the Control-O or CMEM monitor to load a table or tables of rules failed, because the library is held by the job jobId with the ASID asid on system systemId.

The command fails.

Corrective Action: Try to determine why the library is held. If possible, release it, and try again to ORDER or FORCE the table or tables.

CTO50CE LIBRARY WAS MIGRATED BY HSM DSNAME=

Explanation: An ORDER or FORCE command to the Control-O or CMEM monitor to load a table or tables of rules failed, because the library had been migrated by HSM.

The command fails.

Corrective Action: If possible, restore or recall the library, then try again to ORDER or FORCE the table or tables.

CTO50FI text

Explanation: This information message displays the control record from the DARULLST or DACTMLST DD statement.

Corrective Action: No action is required.

CTO516S ERROR IN RULE DATA - MANDATORY stmt_type CARD IS EITHER MISSING OR IN AN INCORRECT ORDER

Explanation: A stmt_type statement is either missing or in the wrong order in a rule definition member.

Someone may have tampered with the rule definition data; the data do not conform to a valid Control-O or CMEM format.

The rule is not ordered.

Corrective Action: Restore the table to its original state from a backup copy, and reorder the rule table.

CTO517S RULE DATA NOT AVAILABLE: MEMBER memName IS EMPTY

Explanation: A member designated in the rule list is empty. This error message is issued by the CTOLDT program, which loads tables when a new Control-O or CMEM monitor is activated.

The table is not ordered.

Corrective Action: Check that the specification of the member in the rule list is correct. If so, check why the member is empty. Correct, and reorder the rule table.

CTO518S INVALID SCHEDULING DATE - date

Explanation: An invalid scheduling date format was used in the rule list or in a order/force request.

Valid date formats are:

The requested table order fails.

Corrective Action: Correct the date. Reorder the rule table.

CTO523S ERROR IN RULE DATA: INVALID IF-THEN-ELSE NESTING

Explanation: This message is issued during the ordering of the rule. The rule definition contains an invalid IF-ELSE-ENDIF nesting.

The rule is not ordered.

Corrective Action: Correct the rule definition and order it again.

CTO524S RULE TABLE(S) ENDED WITH ERROR

Explanation: The indicated function of the CTOLDT program ended with errors. This program loads rule tables when a new Control-O/CMEM monitor is activated, and performs order/force of rule tables.

The IOA Log should contain prior messages concerning the errors.

Depending on when it fails, either the Control-O/CMEM monitor shuts down, or the table is not ordered.

Corrective Action: No action is required.

CTO525I RULE TABLE(S) ENDED

Explanation: This information message is a normal message issued when the indicated function of the CTOLDT program has terminated successfully. This program loads rule tables when a new Control-O or CMEM monitor is activated, or performs an ORDER or FORCE of rule tables.

Corrective Action: No action is required.

CTO526S **** ERROR IN RULE CARDS. CHECK THE FOLLOWING CARDS ***

Explanation: The rule definition has been corrupted and the data do not conform to a valid Control-O/CMEM format.

This message is followed by one or more LDT527S messages describing all statements belonging to the damaged rule order. An asterisk (*) appears in the line under the erroneous data.

The rule is not ordered.

Corrective Action: Using the Online Viewing Facility, or by editing the member, restore the table to its original state, and reorder the rule table.

CTO527S CARD = card

Explanation: The rule definition has been corrupted.

This message follows message LDT526, and displays each statement in the damaged rule in the scheduling table. An asterisk * appears in the line under a damaged statement.

Corrective Action: Restore the table to its original state.

CTO528I RULE ruleName rule_type TABLE tableName LIBRARY lib ODATE odate LOADED

Explanation: This information message is a normal message when a rule order is successfully loaded by the Control-O/CMEM monitor.

The rule is now in Control-O/CMEM memory.

Corrective Action: No action is required.

CTO529I TABLE tableName LIBRARY lib DELETED

Explanation: This information message indicates that rule table tableName has been deleted from the Control-O/CMEM monitor as a result of an F CONTROLO,D=... operator command.

Corrective Action: No action is required.

CTO530E TABLE tableName LIBRARY lib REQUESTED DELETED NOT FOUND

Explanation: A request to delete a rule table from the Control-O/CMEM monitor has failed. Table tableName has not been found under Control-O/CMEM.

The table may be specified incorrectly or it may never have been ordered.

The table is not deleted.

Corrective Action: If the table specification incorrect, check and correct the table specification and issue the delete request again. If the table was never ordered, there is no reason to attempt to delete it.

CTO531I NO RULE WAS LOADED - TABLE tableName LIBRARY lib

Explanation: This information message indicates that the Control-O monitor did not load new rules from the tableName table in the lib library.

While ordering or forcing a rule library, Control-O found no rules that matched the Basic Scheduling parameters.

No rule is loaded.

Corrective Action: No action is required.

CTO532E MASK mask DOES NOT MATCH IN DSN=dsn

Explanation: The specified mask does not match any members in the rule library.

During rule ordering, the Control-O monitor found no members matching the specified mask.

No rule is loaded.

Corrective Action: Check and correct the parameters specified in the ORDER/FORCE command or in the rule list.

CTO536S SEVERE ERROR IN RULE DATA CARDS

Explanation: Severe error was found in the rule definition data statements. It is followed with additional messages regarding the error.

The rule table is not ordered.

Corrective Action: Check for additional messages concerning the errors in the systems and IOA Log and Control-O or CTMCMEM sysprint; correct the error and reorder the table.

CTO537S INSUFFICIENT STORAGE IN (EXTENDED) CSA. CANNOT LOAD TABLE

Explanation: Insufficient storage in the Extended Common Service Area (CSA) to load the rule table.

If any rules have been previously loaded, the Control-O/CMEM monitor proceeds without loading the table. If no rules were previously loaded, the Control-O/CMEM monitor shuts down.

Corrective Action: Check why there is insufficient CSA. You may need to contact your systems programmer. After correcting the problem, reload the table, or restart Control-O/CMEM, as necessary.

CTO539W ORDER CANCELLED BY USER EXIT: RULE ruleName TABLE tableName LIBRARY lib

Explanation: The specified rule order failed as a result of a user exit check.

The IOA Log should contain prior messages concerning the reason for failure.

The rule order is not ordered/loaded by the Control-O/CMEM monitor.

Corrective Action: Check the IOA Log for further information.

CTO545E DO-MISSION NOT SUPPORTED WITHOUT CONTROL-D INSTALLED

Explanation: An attempt was made to order a rule specifying DO MISSION, but Control-D is not installed. DO MISSION is supported only if Control-D is installed.

The rule is not ordered.

Corrective Action: Either remove this statement from the rule or install Control-D.

CTO548E SEVERE ERROR IN CALENDAR calName OR YEAR NOT FOUND IN CALENDAR

Explanation: Severe error in the IOA calendar calName, or the year not found in the calendar.

Either the year is not defined in the calendar or the calendar has been incorrectly modified.

The rule is not ordered.

Corrective Action: Check the contents of the rule order and the calendar. Correct and reorder the rule.

CTO54DE RULE TYPE IS INCORRECT. TABLE tableName LIBRARY dsn

Explanation: The user attempted to order or force a CMEM rule table from Control-O screen OR, or a Control-O rule table from CMEM screen C.

Control-O rules can only be ordered or forced from Control-O screen OR. CMEM rules can only be ordered or forced from CMEM screen C.

The table specified in the message is not loaded.

Corrective Action: If you issued the command from screen OR, issue it from screen C, or vice versa.

CTO54FW RULE WAS NOT LOADED: {SYSTEM | SMF ID} {rul_sysname|rul_smfid} DOES NOT MATCH {cur_sysname|cur_smfid}

Explanation: Control-O did not load a rule because the environment specified for that rule does not match the current environment.

When Control-O loads a table of rules during startup or as a result of an order, it does not load rules whose specified environment does not match the current one.

The Control-O monitor sends this message to SYSPRINT and to the IOALOG, and does not load the rule.

Corrective Action: To load a rule, make the environment specified for it match the current one and reload the table containing the rule.

CTO555S INSUFFICIENT STORAGE. INCREASE THE REGION SIZE

Explanation: There was insufficient memory to perform a task.

The action that could not be performed accompanies this message. It may vary depending on the environment in which the message was issued.

Corrective Action: For jobs, increase the REGION size. For TSO, log on again using a larger SIZE parameter or exit one of the screens.

CTO560I 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 action is required.

CTO561E REQUESTED FUNCTION NOT SUPPORTED

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

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

CTO562E 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.

CTO563E IOA SUBSYSTEM subsys INACTIVE. INTERFACE CANNOT BE USED

Explanation: A request has been received through the XAM interface, or 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.

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

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

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: 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.

 

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.

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

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.

CTO567E IOA SUBSYSTEM subsys INACTIVE

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

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: Start the Control-O monitor.

CTO568E IOA SUBSYSTEM subsys DETECTED AN ERROR

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

The XAM interface, or 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:

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

CTO569E 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 or a Control-O or CMEM 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: Do the following:

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

CTO56AE 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.

CTO56AW 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.

CTO56BE 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.

Contact your INCONTROL administrator.

Corrective Action: No action is required.

CTO56BW 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.

CTO56CE 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.

CTO56EE 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 time-out 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 action is required.

CTO56FE 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 action is required.

CTO570I INITIALIZATION ENVIRONMENT COMPLETED.

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

Corrective Action: No action is required.

CTO573E IOA SUBSYSTEM subsys INACTIVE. INTERFACE CANNOT BE USED

Explanation: A request that requires the Control-O or CMEM monitor was issued by means of 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.

CTO575E 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 table 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.

Code

Description

Return Code 04

GETMAIN or FREEMAIN error. Reason codes are:

1 through 6

GETMAIN failure

7 through 10

FREEMAIN failure

Return Code 08

Variable not found. Reason codes are:

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

Return Code 12

Syntax error or General error. Reason codes are:

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 ?πmany 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

980

Internal error - global pool or database not found

982

Internal error - global pool or database not found

Return Code 16

Errors reading the global member. Reason codes are:

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

Return Code 20

Errors writing the global member. Reason codes are:

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

Return Code 24

Program Buffers Shortage. Reason codes are:

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)

Return Code 32

Program Errors. Reason codes are:

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*.

Return Codes 36, 40, 44

Global Variables 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

Return Code 48

Parse Errors. Reason codes are:

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

CTO576E IOA SUBSYSTEM subsys NOT RESPONDING TO REQUESTS

Explanation: A request from the Control-O or CMEM monitor by means of the Control-O API failed due to time-out, 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.

CTO577E 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.

CTO578E 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.

CTO579E 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: Notify BMC Customer Support.

CTO57AE 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.

CTO57BE 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.

CTO57CE INAREA LENGTH length1 + RESULT LENGTH length4 > 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.

CTO57EE 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 Control-O or CMEM monitor job log 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.

CTO5A0E SERVER serverId, SECURITY ENVIRONMENT CREATION FAILED RC=rc REASON=rsn

Explanation: The IOASECUR security handling module failed to establish the security environment.

In rules in which value OWNER or TRIGGER has been specified for the RUNTSEC parameter, the IOASECUR module runs a security check on every DO KSL/TSO/SHELL request included in the rule.

This message is often accompanied by the SRV5A1I or CTO281I message, which contains the error message returned by the locally active security product.

The KSL/TSO/SHELL request is not performed.

Corrective Action: See the DOCSECUR member in the IOA DOC library for a description of rc and reason.

Correct the security definitions, and/or verify changes made to the IOASECUR security module. Additional information is provided in the CTO5A1I or CTO281I message (if issued).

CTO5A1I ERROR MESSAGE = text

Explanation: This information message indicates that the IOASECUR security module failed to establish the security environment.

In rules in which the value OWNER or TRIGGER has been specified for the RUNTSEC parameter, the IOASECUR module runs a security check on every DO KSL/TSO/SHELL request included in the rule.

In this message, text is the error message returned by the security product active at the site.

The KSL/TSO/SHELL request is not performed.

Corrective Action: Depending on the message text, correct the security definitions and verify changes made to the IOASECUR security module.

CTO5A2W SERVER serverId, SECURITY ENVIRONMENT CLEANUP FAILED RC=rc REASON=rsn

Explanation: The IOASECUR security handling module failed to reset the security environment.

In rules in which value OWNER or TRIGGER has been specified for the RUNTSEC parameter, the IOASECUR module runs a security check on every DO KSL/TSO/SHELL request included in the rule.

This message is often accompanied by message SRV5A1I which contains the error message text returned by the locally active security product.

Depending on the rc and reason, the DO KSL/TSO/SHELL request may or may not be performed.

Corrective Action: See the DOCSECUR member in the IOA DOC library for a description of rc and rsn.

Correct the security definitions, and/or verify changes made to the IOASECUR security module. More information is provided in the CTO5A1I or CTO281I message (if issued).

CTO5A3I CONTROL-O SERVER serverId STARTED

Explanation: This information message indicates that the specified Control-O server has been successfully started.

Corrective Action: No action is required.

CTO5A4I CONTROL-O SERVER serverId ENDED

Explanation: This information message indicates that the specified Control-O server has been successfully terminated.

Corrective Action: No action is required.

CTO5A5E SERVER serverId SEVERE ERROR - details

Explanation: The specified server detected an internal error.

The server is terminated.

Corrective Action: Contact BMC Customer Support.

CTO5A9S CONTROL-O SERVER serverId HAS ABENDED. ABEND CODE = abCode

Explanation: The server detected an internal abend.

This message indicates an internal error.

Server serverId is terminated.

Corrective Action: Contact BMC Customer Support for assistance.

CTO5AFE SERVER serverName, TIMEOUT OCCURRED. REQUEST WILL BE CANCELED

Explanation: The server is executing a DO KSL, DO TSO, or DO SHELL with TIMEOUT and STOP=Y defined. This DO KSL or DO TSO command, z/OS SHELL script, REXX, or CLIST has reached its timeout limit and the sub-task running it will be canceled.

After this message is issued, the server will usually terminate. In the case of a General or Dedicated server with SRVTERM set to N, the server will continue to accept other requests.

Corrective Action: Either enlarge the TIMEOUT amount defined for the execution or correct the TSO Command, z/OS SHELL script, REXX, or CLIST whose time limit was reached.

CTO5AGE DYNAMIC ALLOCATION OF SYSTSIN FAILED. R15=rc REASON=rsn

Explanation: Control-O was unable to dynamically allocate SYSTSIN DD.

Control-O uses the SYSTSIN DD used to pass the TSO command to the Control-O server address space.

Corrective Action: Refer to the IBM MVS Programming: Authorized Assembler Services Guide for the Dynamic Allocation return code and reason code explanation.

Parent Topic

CTO messages