Previous Topic

Next Topic

Book Contents

Book Index

Messages SLO100 through SLO1xx

This group includes messages for the Control-O product.

SLO160I {CONTROL-O | CTMCMEM} SELECTOR STARTED

Explanation: This information message indicates the start of the Control-O Selector task, which controls the runtime selection criteria for rules.

Corrective Action: No action is required.

SLO161I {CONTROL-O | CTMCMEM} SELECTOR ENDED

Explanation: This information message indicates normal termination of the Control-O Selector task that controls the runtime selection criteria for rules.

Corrective Action: No action is required.

SLO163S OPEN FAILED FOR DDNAME "DARESF" OR "DASINC"

Explanation: Open of IOA Conditions or Resources file failed (the DARESF or the DASINC DD statement).

Possible causes are:

Control-O monitor shuts down with error message.

Corrective Action: Correct the JCL for the Control-O procedure, and restart the monitor.

SLO164S INTERNAL ERROR PROCESSING RESOURCE FILE FOR CONDITION cond

Explanation: An internal error occurred while the cond condition was being processed.

The Control-O monitor is terminated.

Corrective Action: Contact BMC Customer Support.

SLO165E COND name date NOT action BY CONTROL-O - SECURITY VIOLATION

Explanation: Control-O issued a DO COND request, but the user is not authorized by the security exit to add or delete this condition in the IOA Conditions file.

The prerequisite condition is not added or deleted.

Corrective Action: Contact your INCONTROL administrator.

SLO166W COND name date NOT UPDATED BY CONTROL-O - NO MORE SPACE. NOTIFY THE IOA ADMINISTRATOR

Explanation: Highlighted, unrollable message.

There is no more space for adding output conditions to the IOA Conditions file.

The record for the specified day of the month is full. For example, if a condition with date reference of January 3rd cannot be added, an entry in the conditions file which contains conditions for January 3rd, February 3rd, March 3rd, and so on, is full.

The format for the date specified in this message is mmdd.

The condition is not added. A highlighted message is displayed on the operator console. Control-O or CMEM continues to function, but the rules that depend on the condition may not be triggered.

Corrective Action: Perform the following immediate actions and then perform the long term actions described below.

Immediate actions:

  1. Enter the IOA Conditions list (Screen 4).
  2. Look for conditions with the same day (but with a different month) as the condition that could not be added. Delete them manually if they are not needed.
  3. Add the failing condition manually in order to maintain production flow.
  4. Report the event to your System Programmer.

Long term actions:

SLO167I COND name date WAS action BY {CONTROL-O | CTMCMEM}

Explanation: This information message displays the results of a Control-O or CMEM DO COND request.

The Control-O or CMEM monitor adds/deletes the prerequisite condition.

Corrective Action: No action is required.

SLO168I COND name date ALREADY action

Explanation: This information message indicates that the user requested an action that has already been performed.

The user either tried to add a condition that already exists or tried to delete a condition that had already been deleted.

Corrective Action: No action is required.

SLO169W COND name date NOT ADDED BY {CONTROL-O | CTMCMEM} GLOBAL DATE ADDITION IS NOT SUPPORTED

Explanation: A DO COND statement in a rule requested the addition of the specified condition with date **** or $$$$. This date specification is valid only when conditions are being deleted.

The DO COND request is not performed.

Corrective Action: Correct the DO COND statement.

Parent Topic

SLO messages