Messages LDT500 through LDT5xx

This group includes messages for the Control-O product.

LDT500I RULE= rule TYPE= rule_typ TABLE= tableName LIB= lib

Explanation: This information message provides information about each rule in the table that was not loaded by ORDER or FORCE requests.

The variables in this message are:

• rule - the name of the rule
• rule_typ - the type of rule
• tableName - the name of the table containing the rule
• lib - the name of the library containing the table

Corrective Action: Examine previously issued messages to ascertain the reason why the rule identified in this message was not loaded, and take appropriate corrective action.

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

LDT502E MEMBER IN USE= memb DSN= dsn

Explanation: The user attempted to load a rule table but the table was currently being used.

This message is issued immediately after message CTM684E to give the name of the member and data set that are in use.

The table is not loaded.

Corrective Action: Try to load the required table manually or by an automated operations product when the table is not in use.

LDT503S RULE ORDER LIST IS EMPTY. DDNAME= {DARULLST | DACTMLST}

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

Possible causes are:

• The DARULLST or DACTMLST DD statement is missing.
• The data set described by the DARULLST or DACTMLST DD statement cannot be opened for sequential read, or the record length is not 80.

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

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

LDT504S INVALID DATA IN RULE ORDER LIST CARDS

Explanation: Invalid data has been found in the rule order list.

For valid format information, see the INCONTROL for z/OS Administrator Guide.

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

LDT505S MEMBER memName NOT FOUND IN LIBRARY lib

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

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.

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

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

LDT508I {ORDER | FORCE} OF RULES’ TABLE(S) ENDED

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

Corrective Action: No action is required.

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

LDT50AI NUMBER OF TABLES numtbl RULES numrul DELETED

Explanation: This information message indicates the number of tables (numtbl) and the number of rules (numrul) deleted as a result of a MODIFY command to the Control-O or CMEM monitor.

Corrective Action: No action is required.

LDT50BE 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 jobId job with the asid ASID on the systemId system.

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.

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

LDT50FI text

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

Corrective Action: No action is required.

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

LDT517S RULE DATA NOT AVAILABLE: MEMBER memName IS EMPTY

Explanation: The memName member that was 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.

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

• ddmmyy - Day, month, and year.
• mmddyy - Month, day, and year.
• * (Asterisk) - Current Control-O or CMEM working date.

The requested table order fails.

Corrective Action: Correct the date, then reorder the rule table.

LDT521S ERROR IN RULE DATA: INVALID 'EXIT' TYPE. VALUES ALLOWED MESSAGE OR WHILE

Explanation: A logical check performed during rule loading detected an invalid DO EXIT statement.

The rule is not loaded.

Corrective Action: Correct the rule definition and reload the table.

LDT522S ERROR IN RULE DATA: EXIT WHILE NOT IN WHILE BLOCK

Explanation: A logical check performed during rule loading detected a DO EXIT WHILE statement that was not in a DO WHILE block. A DO EXIT WHILE statement is only valid if it is located within a DO WHILE block.

The rule is not loaded.

Corrective Action: Correct the rule definition and reload the table.

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

LDT524S func RULE TABLE(S) ENDED WITH ERRORS

Explanation: The indicated function of the CTOLDT program ended with errors. This program loads rule tables when a new Control-O or 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 or CMEM monitor shuts down, or the table is not ordered.

Corrective Action: No action is required.

LDT525I func 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 order/force of rule tables.

Corrective Action: No action is required.

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

LDT527S CARD = stmt

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.

LDT528I 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 or CMEM monitor.

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

Corrective Action: No action is required.

LDT529I TABLE tableName LIBRARY lib DELETED

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

Corrective Action: No action is required.

LDT530E DELETE OF TABLE tableName LIBRARY lib FAILED, TABLE NOT FOUND

Explanation: A request to delete a rule table from the Control-O or CMEM monitor has failed. Table tableName has not been found under Control-O or 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.

LDT531I NO RULE WAS LOADED - TABLE tableName LIBRARY lib

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

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.

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

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

LDT537S 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 or CMEM monitor proceeds without loading the table. If no rules were previously loaded, the Control-O or 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 or CMEM, as necessary.

LDT539W 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 or CMEM monitor.

Corrective Action: Check the IOA Log for further information.

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

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

Explanation: Severe error in the IOA calendar calName, or the year was 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.

LDT549E DO FORCEJOB/RESOURCE NOT SUPPORTED WITHOUT CONTROL-M INSTALLED

Explanation: An attempt was made to order a rule specifying DO FORCEJOB or DO RESOURCE, but Control-M is not installed.

These statements are not supported if Control-M is not installed.

The rule is not ordered.

Corrective Action: Remove these statements from the rule or install Control-M.

LDT54AE INVALID "ON" STATEMENT FOR CMEM RULE

Explanation: An attempt was made to load a CMEM table containing a rule with an invalid “ON” statement.

The table is loaded without the erroneous rule.

Corrective Action: Delete the rule from the table, or load the table as a Control-O table (if Control-O is installed).

LDT54BE INVALID "DO" STATEMENT FOR CMEM RULE

Explanation: An attempt was made to load a CMEM table containing a rule with an invalid “DO” statement.

The table is loaded without the erroneous rule.

Corrective Action: If the rule is required, load the table as a Control-O table. If the rule is not required, delete it from the table.

LDT54CW LOAD REQUEST IGNORED. TABLE tableName LIBRARY lib ALREADY LOADED

Explanation: During monitor startup or REBUILD/NEWCONLIST command, Control-O tried to load a certain table more than once.

This problem can be caused by one of the following:

• Duplicate statements appear in the same list, for example, DACTMLST, DARULLST.
• The same statement appears in different lists, for example, DACTMLST, DARULLST.
• Different generic statements appear in the same or different lists, producing one or more duplicate statements, for example, CTO* and C*.

Only the first appearance of the table is loaded.

Corrective Action: Check the lists for duplicate statements and correct if necessary.

LDT54DE RULE TYPE IS INCORRECT. TABLE tableName LIBRARY lib

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.

LDT54EW RULE WAS NOT LOADED: SCHEDULING DATE WAS NOT SATISFIED

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

When Control-O loads a rule during startup or as a result of an order, it does not load rules whose scheduling date 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 the rule, make the scheduling date match the current date and reload the table containing the rule.

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