ADSM V3R1 Messages

Chapter 12. Central Scheduling (2500-2799)



ANR2500I Schedule schedule name defined in policy domain domain name.
Explanation: This message is displayed in response to the DEFINE SCHEDULE command. The schedule named schedule name has been defined in the policy domain named domain name in the server database.
System Action: Server operation continues.
User Response: None.


ANR2501I Schedule schedule name deleted from policy domain domain name.
Explanation: This message is displayed in response to the DELETE SCHEDULE command. The schedule named schedule name has been deleted from the policy domain named domain name in the server database.
System Action: Server operation continues.
User Response: None.


ANR2502I Schedule schedule name updated in policy domain domain name.
Explanation: This message is displayed in response to the UPDATE SCHEDULE command. The schedule named schedule name has been updated in the policy domain named domain name in the server database.
System Action: Server operation continues.
User Response: None.


ANR2503I Schedule schedule name in domain domain name copied to schedule new schedule name in domain new domain name.
Explanation: This message is displayed in response to the COPY SCHEDULE command. The schedule named schedule name in policy domain domain name has been copied to the schedule named new schedule name in the policy domain named new domain name. Node associations have not been copied.
System Action: Server operation continues.
User Response: None.


ANR2504I Schedule schedule name deleted.
Explanation: This message is displayed in response to the DELETE SCHEDULE command. The schedule named schedule name has been deleted from the server database.
System Action: Server operation continues.
User Response: None.


ANR2505I number of schedules schedules were defined for command.
Explanation: number of schedules were generated and nodes successfully associated for the command issued.
System Action: Server operation continues.
User Response: If the number is less than expected, check the nodeList and domainList combination specified to the DEFINE CLIENTACTION command. Schedules are generated when at least one node in the nodeList exists in a domain in the domainList.


ANR2510I Node node name associated with schedule schedule name in policy domain domain name.
Explanation: This message is displayed in response to the DEFINE ASSOCIATION command. Node node name is associated with the schedule named schedule name in policy domain domain name. Schedule schedule name is now applied to node node name.
System Action: Server operation continues.
User Response: None.


ANR2511I Node node name disassociated from schedule schedule name in policy domain domain name.
Explanation: This message is displayed in response to the DELETE ASSOCIATION command. Node node name is no longer associated with the schedule named schedule name in policy domain domain name.
System Action: Server operation continues.
User Response: None.


ANR2512I Event records deleted: record count.
Explanation: This message is displayed in response to the DELETE EVENT command. A total of record count event records have been deleted from the database.
System Action: Server operation continues.
User Response: None.


ANR2513I Schedule schedule name copied to schedule new schedule name.
Explanation: This message is displayed in response to the COPY SCHEDULE command. The schedule named schedule name has been copied to the schedule named new schedule name.
System Action: Server operation continues.
User Response: None.


ANR2520I Scheduled sessions set to percent percent.
Explanation: This message is displayed in response to the SET MAXSCHEDSESSIONS command. It indicates the percentage of total server sessions that can be used for the processing of scheduled work.
System Action: Server operation continues.
User Response: None.


ANR2521I Event record retention period set to days days.
Explanation: This message is displayed in response to the SET EVENTRETENTION command. It indicates the number of days for which event records are retained in the database.
System Action: Server operation continues.
User Response: None.


ANR2522I Randomization set to percent percent.
Explanation: This message is displayed in response to the SET RANDOMIZE command. It indicates the percentage of the startup window over which the start times for individual clients are distributed.
System Action: Server operation continues.
User Response: None.


ANR2523I Schedule query period set to hours hour(s).
Explanation: This message is displayed in response to the SET QUERYSCHEDPERIOD command. It indicates the number of hours between attempts by the client to contact the server for scheduled commands.
System Action: Server operation continues.
User Response: None.


ANR2524I Schedule query period reset to value determined by each client.
Explanation: This message is displayed in response to the SET QUERYSCHEDPERIOD command.
System Action: Server operation continues.
User Response: None.


ANR2525I Maximum number of command retries set to retries.
Explanation: This message is displayed in response to the SET MAXCMDRETRIES command. It indicates the maximum number of times the client scheduler retries a command after a failed attempt to process a scheduled command.
System Action: Server operation continues.
User Response: None.


ANR2526I Maximum number of command retries reset to value determined by each client.
Explanation: This message is displayed in response to the SET MAXCMDRETRIES command.
System Action: Server operation continues.
User Response: None.


ANR2527I Retry period set to minutes minutes.
Explanation: This message is displayed in response to the SET RETRYPERIOD command. It indicates the number of minutes between attempts by the client scheduler to retry, after a failed attempt, to contact the server or to process a scheduled command.
System Action: Server operation continues.
User Response: None.


ANR2528I Retry period reset to value determined by each client.
Explanation: This message is displayed in response to the SET RETRYPERIOD command.
System Action: Server operation continues.
User Response: None.


ANR2529I Scheduling mode set to POLLING.
Explanation: This message is displayed in response to the SET SCHEDMODES command. With client-polling scheduling, a client queries the server at prescribed time intervals to obtain scheduled work or to ensure that the schedules the client is waiting to process have not changed.
System Action: Server operation continues.
User Response: None.


ANR2530I Scheduling mode set to PROMPTED.
Explanation: This message is displayed in response to the SET SCHEDMODES command. With server-prompted scheduling, the server contacts the client when scheduled work needs to be performed and a session is available.
System Action: Server operation continues.
User Response: None.


ANR2531I Scheduling mode set to ANY.
Explanation: This message is displayed in response to the SET SCHEDMODES command. The server now allows clients to run in either the client-polling or the server-prompted scheduling mode.
System Action: Server operation continues.
User Response: None.


ANR2532I Schedule schedule name updated.
Explanation: This message is displayed in response to the UPDATE SCHEDULE command. The schedule named schedule name has been updated in the server database.
System Action: Server operation continues.
User Response: None.


ANR2533I Client action schedule duration set to days days.
Explanation: This message is displayed in response to the Set CLIENTACTDuration command. It indicates the number of days for which schedules and associations generated by the DEFine CLIENTAction are retained in the database.
System Action: Server operation continues.
User Response: None.


ANR2534I Client action schedule schedule name was not executed by node name in domain name.
Explanation: Immediate client action schedule name was not executed by node node name, which is in domain domain name. The schedule is being deleted.
System Action: Server operation continues.
User Response: None.


ANR2550W command name: Administrative schedule schedule name does not have valid activation information.
Explanation: This message is displayed during a database audit and indicates that the 'ACTIVE=YES or NO' information is not recorded correctly for an administrative schedule in the server database.
System Action: Server database audit operation continues.
User Response: Execute the AUDITDB operation specifying FIX=YES so that the activation information can be corrected.


ANR2551I command name: Administrative schedule schedule name does not have valid activation information - activation information will be deleted.
Explanation: This message is displayed during a database audit and indicates that the 'ACTIVE=YES or NO' information is not recorded correctly for an administrative schedule in the server database. The audit operation corrects this discrepancy by removing the invalid activation information.
System Action: Server database audit operation continues.
User Response: The named administrative schedule will now appear to be inactive in the server database (as if ACTIVE=NO was specified). If you want this schedule to be active, execute the UPDATE SCHEDULE command with the ACTIVE=YES parameter to activate the schedule when the server is restarted.


ANR2560I Schedule manager started.
Explanation: The schedule manager is started when the server is initialized. The schedule manager maintains entries of scheduled operations.
System Action: Server operation continues.
User Response: None.


ANR2561I Schedule prompter contacting node name (session session number) to start a scheduled operation.
Explanation: The schedule prompter contacts the client scheduler for node node name because a scheduled operation should be started for that node.
System Action: Server operation continues.
User Response: None.


ANR2562I Automatic event record deletion started.
Explanation: A process has been started to delete event records for which the retention period has elapsed.
System Action: Server operation continues.
User Response: None.


ANR2563I Removing event records dated prior to date time.
Explanation: Events that were scheduled to start prior to date time are automatically deleted unless their startup window has not yet elapsed.
System Action: Server operation continues.
User Response: None.


ANR2564I Automatic event record deletion ended - record count records deleted.
Explanation: The event deletion process has ended. A total of record count event records have been deleted from the database.
System Action: Server operation continues.
User Response: None.


ANR2565I schedules schedules for immediate client actions have been deleted.
Explanation: A total of schedules that were generated by the DEFine CLIENTAction command have expired and been deleted from the database.
System Action: Server operation continues.
User Response: None.


ANR2566E An error occurred while deleting immediate client action schedules.
Explanation: Processing did not complete for deleting schedules that were generated by the DEFine CLIENTAction command.
System Action: Server operation continues.
User Response: Check the activity log for other messages that might relate to this failure. Correct any memory or space problems.


ANR2570W A scheduled session has been denied. The schedule manager is not active.
Explanation: The client scheduler attempts to connect with the server, but it is denied a session because the schedule manager is not active.
System Action: Server operation continues, but central scheduling is not operational.
User Response: Issue the QUERY OPTION command to determine if the option DISABLESCHEDS YES has been specified in the server options file. If so, scheduling can be enabled by updating the server options file with DISABLESCHEDS NO and restarting the server.

If DISABLESCHEDS YES was not specified in the server options file, determine the source of the error by examining the QUERY ACTLOG command to view the activity log and search for messages. After the error has been resolved, restart the server to restore central scheduler operations. If the error cannot be isolated and resolved, contact your service representative.


ANR2571W Scheduled session from node node name (platform name) has been denied, scheduled sessions are not currently available.
Explanation: The client scheduler for node node name attempts to connect with the server, but is denied a session. All sessions that have been allocated for scheduled operations are already in use.
System Action: Server operation continues.
User Response: Issue the QUERY OPTION command to determine if the option DISABLESCHEDS YES has been specified in the server options file. If so, scheduling can be enabled by updating the server options file with DISABLESCHEDS NO and restarting the ADSM server.

If DISABLESCHEDS YES was not specified in the server options file, change the total number of sessions by altering the MAXSESSIONS parameter in the server options file and then restarting the server. The percentage of sessions that are available for scheduled operations can be increased by using the SET MAXSCHEDSESSIONS command.


ANR2572W Schedule prompter session to node node name has been denied, scheduled sessions are not currently available.
Explanation: The server attempts to prompt the client scheduler for node node name, but all sessions that have been allocated for scheduled operations are already in use.
System Action: The server continues to attempt contact with the client scheduler until the startup window for the scheduled event has elapsed.
User Response: To change the total number of sessions, alter the MAXSESSIONS parameter in the server options file and then restart the server. The percentage of sessions that are available for scheduled operations can be increased by using the SET MAXSCHEDSESSIONS command.


ANR2573W Sufficient memory is not available for the central scheduler - will retry in number of seconds seconds.
Explanation: The server suspends central scheduler processing because sufficient server memory is not available.
System Action: Server operation continues; the scheduler operation will be retried after the specified delay.
User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".


ANR2574W Insufficient recovery log space available for the central scheduler - will retry in number of seconds seconds.
Explanation: The server suspends central scheduler processing because sufficient recovery log space is not available.
System Action: Server operation continues; the scheduler operation will be retried after the specified delay.
User Response: To increase the amount of log space available to the server, an authorized administrator can add log volumes by using the DEFINE LOGVOLUME command, and can extend the size of the log by using the EXTEND LOG command.


ANR2575W Insufficient database space available for the central scheduler - will retry in number of seconds seconds.
Explanation: The server suspends central scheduler processing because sufficient database space is not available.
System Action: Server operation continues; the scheduler operation will be retried after the specified delay.
User Response: To increase the amount of database space available to the server, an authorized administrator can add database volumes by using the DEFINE DBVOLUME command, and can extend the size of the log by using the EXTEND DB command.


ANR2576W An attempt was made to update an event record for a scheduled operation which has already been executed - multiple client schedulers may be active for node node name.
Explanation: The server has attempted to update an event record for a scheduled operation for the specified client node. However, the existing event record shows that this scheduled operation has already been executed, either successfully or unsuccessfully. Two or more client schedulers may be running for this node.
System Action: Server operation continues. The existing event record is not modified. No further processing is performed for this scheduled operation.
User Response: Contact the user for this client node, and make sure that only one client scheduler is running.


ANR2577I Schedule schedule name defined.
Explanation: This message is displayed in response to the DEFINE SCHEDULE command. The schedule named schedule name in the server database.
System Action: Server operation continues.
User Response: None.


ANR2578I Schedule schedule name in domain domain name for node node name has missed its scheduled start up window.
Explanation: This message is displayed when the scheduled startup window for this schedule has passed and the schedule has not begun.
System Action: Server operation continues. The scheduled operation is not processed by the server.
User Response: Ensure that a scheduled session for node node name has been initiated from the client to the server. Refer to ADSM Administrator's Guide and ADSM Administrator's Reference for more information on setting up scheduling operations.


ANR2600E command: Invalid schedule name - schedule name.
Explanation: The specified command has been issued with an invalid schedule name.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command with a valid schedule name.


ANR2601E command: Schedule description exceeds maximum length characters.
Explanation: The specified command has been issued with a description that exceeds the maximum length.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command and specify a valid description.


ANR2602E command: Invalid action - action.
Explanation: The specified command has been issued with an invalid action.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command and specify a valid action.


ANR2603E command: Options string exceeds maximum length characters.
Explanation: The specified command has been issued with an options string that exceeds the maximum length.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command with a valid options string.


ANR2604E command: Objects string exceeds maximum length characters.
Explanation: The specified command has been issued with an objects string that exceeds the maximum length.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command with a valid objects string.


ANR2605E command: Invalid priority - priority.
Explanation: The specified command has been issued with an invalid priority.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command and specify a valid priority.


ANR2606E command: Invalid start date - date.
Explanation: The specified command has been issued with an invalid start date.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command and specify a valid start date.


ANR2607E command: Invalid start time - time.
Explanation: The specified command has been issued with an invalid start time.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command and specify a valid start time.


ANR2608E command: Invalid duration - duration.
Explanation: The specified command has been issued with an invalid duration.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command and specify a valid duration.


ANR2609E command: Invalid duration units - duration units.
Explanation: The specified command has been issued with an invalid value for duration units.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command and specify a valid value for duration units.


ANR2610E command: Invalid period - period.
Explanation: The specified command has been issued with an invalid period.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command and specify a valid period.


ANR2611E command: Invalid period units - period units.
Explanation: The specified command has been issued with an invalid value for period units.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command and specify a valid value for period units.


ANR2612E command: Invalid day of week - day of week.
Explanation: The specified command has been issued with an invalid value for day of the week.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command and specify a valid value for day of the week.


ANR2613E command: Invalid expiration - date.
Explanation: The specified command has been issued with an invalid expiration date.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command and specify a valid expiration date.


ANR2614E command: Invalid combination of the following parameters: duration, duration units, period, period units.
Explanation: The specified command has been issued with an invalid combination of the DURATION, DURUNITS, PERIOD, and PERUNITS parameters. This message may be displayed if the duration of the startup window for the schedule is not shorter than the period between windows. This message may also be displayed if DURUNITS=INDefinite is specified, but PERUNITS=Onetime is not specified.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command and specify a valid combination of parameters.


ANR2615E command: Expiration date date has elapsed.
Explanation: The specified command has been issued with an elapsed expiration date date.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command and specify an expiration date that has not already elapsed.


ANR2616E command: Start date start date must be earlier than expiration date expiration.
Explanation: The specified command has been issued with a start date that is not earlier than the expiration date.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command using a schedule start date that is earlier than the expiration date.


ANR2617E command: Schedule schedule name is not defined in policy domain domain name.
Explanation: The specified command has been issued with a schedule name that has not been defined in the indicated policy domain.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command using a schedule that has already been defined for this domain.


ANR2618E command: Schedule schedule name is already defined in policy domain domain name.
Explanation: The specified command has been issued with a schedule name that has already been defined for the indicated policy domain.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command using a schedule that has not already been defined for this domain.


ANR2619E command: Currently defined period period is invalid with updated period units.
Explanation: The specified command has been issued with a value for period units that is not allowed with the existing period.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command and specify a new period.


ANR2620E command: Currently defined duration duration is invalid with updated duration units.
Explanation: The specified command has been issued with a value for duration units that is not allowed with the existing duration.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command and specify a new duration.


ANR2621E command: No matching schedules.
Explanation: The specified command has been issued but no matching schedules have been found.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command and specify different schedules.


ANR2622E command: No new node associations added.
Explanation: The specified command has been issued but no new node associations are defined.
System Action: Server operation continues, but the command has no effect.
User Response: Issue the command and specify different nodes.


ANR2623E command: No node associations deleted.
Explanation: The specified command has been issued but no node associations are deleted.
System Action: Server operation continues, but the command has no effect.
User Response: Issue the command and specify different nodes.


ANR2624E command: No matching nodes registered.
Explanation: No matching nodes are found for the specified command.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command and specify different nodes.


ANR2625E command: No matching nodes registered in policy domain domain name.
Explanation: The specified command has been issued, but no matching nodes are registered in the indicated policy domain.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command and specify different nodes.


ANR2626E command: Invalid value for replace - replace.
Explanation: The specified command has been issued with an invalid value for replace.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command using a valid value for replace.


ANR2627E command: Invalid value for format - format.
Explanation: The specified command has been issued with an invalid value for format.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command using a valid value for format.


ANR2628E command: Invalid date - date.
Explanation: The specified command has been issued with an invalid date.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command with a valid date.


ANR2629E command: Invalid time - time.
Explanation: The specified command has been issued with an invalid time.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command with a valid time.


ANR2630E command: Event deletion is already in process.
Explanation: The specified command has been issued while event deletion is already in progress.
System Action: Server operation continues, but the command is not processed.
User Response: Wait for event deletion to complete before issuing the command.


ANR2631E command: Invalid begin date - date.
Explanation: The specified command has been issued with an invalid begin date.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command with a valid begin date.


ANR2632E command: Invalid begin time - date.
Explanation: The specified command has been issued with an invalid begin time.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command with a valid begin time.


ANR2633E command: Invalid end date - date.
Explanation: The specified command has been issued with an invalid end date.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command with a valid end date.


ANR2634E command: Invalid end time - time.
Explanation: The specified command has been issued with an invalid end time.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command with a valid end time.


ANR2635E command: Invalid time range - Begin: begin End: end.
Explanation: The specified command has been issued with an invalid time range. This occurs if the date and time for the beginning of the time range (begin) do not precede the date and time for the end of the time range (end).
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command with a valid time range.


ANR2636E command: Invalid value for exceptions only - exceptions only.
Explanation: The specified command has been issued with an invalid value for exceptions only.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command with a valid value for exceptions only.


ANR2640E command: Invalid percentage of sessions for scheduled processing - value.
Explanation: The specified command has been issued with an invalid value.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command with a valid value.


ANR2641E command: Invalid event record retention period - value.
Explanation: The specified command has been issued with an invalid value.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command with a valid value.


ANR2642E command: Invalid percentage for randomization - value.
Explanation: The specified command has been issued with an invalid value.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command with a valid value.


ANR2643E command: Invalid schedule query period - value.
Explanation: The specified command has been issued with an invalid value.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command with a valid value.


ANR2644E command: Invalid maximum number of command retries - value.
Explanation: The specified command has been issued with an invalid value.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command with a valid value.


ANR2645E command: Invalid retry period - value.
Explanation: The specified command has been issued with an invalid value.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command with a valid value.


ANR2646E command: Invalid scheduling mode - value.
Explanation: The specified command has been issued with an invalid value.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command with a valid value.


ANR2647E command: Invalid type - type.
Explanation: The specified command has been issued with an invalid type.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command with a valid type.


ANR2648E command: Type string exceeds maximum length characters.
Explanation: The specified command has been issued with a type string that exceeds the maximum length.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command with a valid type string.


ANR2649E command: Schedule schedule name is not defined.
Explanation: The specified command has been issued with a schedule name that has not been defined.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command with a schedule that has already been defined.


ANR2650E command: Schedule schedule name is already defined.
Explanation: The specified command has been issued with a schedule name that has already been defined.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command with a schedule name that has not already been defined.


ANR2651E command: Invalid combination of one or more of the following parameters: cmd, type, action, objects, options.
Explanation: The specified command has been issued with an invalid combination of the CMD, ACTION, OBJECTS, and OPTIONS parameters. This message is displayed when the CMD parameter is specified and TYPE=CLIENT is not specified, or when TYPE=ADMIN is specified, and one or more of the following is specified: ACTION, OBJECTS, or OPTIONS.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command with a valid combination of parameters.


ANR2652E command: Invalid combination of one or more of the following parameters: active, cmd, type.
Explanation: The specified command has been issued with an invalid combination of the TYPE, CMD, or ACTIVE parameters. This message is displayed when TYPE=CLIENT is specified and one or more of the following is specified: ACTIVE, CMD.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command with a valid combination of parameters.


ANR2653W command: Node node name cannot be processed because it is not registered or does not belong to the specified domain.
Explanation: This command cannot be processed for the indicated node. Either the node is not registered or it is not assigned to the required domain.
System Action: The indicated node is not processed, but other nodes may be processed if specified by this command.
User Response: If the node name was entered incorrectly, reissue the command with the correct node name.


ANR2654E command: The NODES parameter cannot be used when querying administrative schedules.
Explanation: A QUERY SCHEDULE command has been issued with TYPE=ADMINISTRATIVE and the NODES parameter both specified. The NODES parameter cannot be specified when querying administrative schedules.
System Action: Server operation continues, but the command is not processed.
User Response: Issue the command without the NODES parameter.


ANR2655E command: Invalid client action schedule duration - days.
Explanation: The specified command has been issued with an invalid number of days. Valid values are 1 to 9999 inclusive. days specifies the length of time during which a schedule defined by the DEFine CLIENTAction command must be executed by an associated node. After that, the schedule will be deleted from the database.
System Action: Server operation continues, but the command is not processed.
User Response: Reissue the command with a valid number of days.


ANR2700E Schedule manager aborted.
Explanation: The schedule manager has ended because of an error condition and is not able to maintain entries for scheduled operations.
System Action: Server operation continues, but the central scheduler is not operational.
User Response: To determine the source of the error, examine server messages issued prior to this message. Issue the QUERY ACTLOG command to view the activity log and search for messages. After the error has been resolved, restart the server to restore central scheduler operations. If the error cannot be isolated and resolved, contact your service representative.


ANR2707E Out of server log space in central scheduler.
Explanation: The server ends a database update transaction for the central scheduler because sufficient log space is not available on the server.
System Action: Server operation continues, but the database update fails.
User Response: An authorized administrator can use the DEFINE LOGVOLUME command to add volumes for use by the log and can issue the EXTEND LOG command to extend the size of the log so that the new volumes are used.


ANR2708E Out of server database space in central scheduler.
Explanation: The server ends a database update transaction for the central scheduler because sufficient database space is not available on the server.
System Action: Server operation continues, but the database update fails.
User Response: An authorized administrator can use the DEFINE DBVOLUME command to add volumes for use by the database and can use the EXTEND DB command to extend the size of the database so that the new volumes are used.


ANR2712E Node node1 requested scheduling information for node node2 - session rejected.
Explanation: A request for pending scheduled operations has been sent from the client scheduler for node node1. However, the request is for scheduling information concerning another node node2.
System Action: Server operation continues, but the client scheduler for node node1 will not be able to process pending operations.
User Response: Try restarting the client scheduler for node node1. If the problem persists, contact your service representative to resolve the client program error.


ANR2713E Node node1 trying to start scheduled operation for node node2 - session rejected.
Explanation: The client scheduler for node node1 has attempted to execute a scheduled operation for another node, node2.
System Action: Server operation continues, but the scheduled operation is not processed.
User Response: Try restarting the client scheduler for node node1. If the problem persists, contact your service representative to resolve client program error.


ANR2714E Node node1 trying to report scheduled operation results for node node2 - session rejected.
Explanation: The client scheduler for node node1 has attempted to report the results of a scheduled operation using another node name, node2.
System Action: Server operation continues, but the results that were sent from node node1 are not be stored in the server's database.
User Response: Try restarting the client scheduler for node node1. If the problem persists, contact your service representative to resolve the client program error.


ANR2715E Client node node name unable to register valid address for server prompting: type address type (high address low address).
Explanation: The client scheduler for node node name has attempted to register an invalid address for server-prompted central scheduling. The address was type address type with high-level field high address and low-level field low address. The only valid address type is 1.
System Action: Server operation continues, but the node node name will not be prompted to perform scheduled operations.
User Response: Verify that the address type and address are correct for this client. The only valid address type is 1 (for TCP/IP). Make sure the client scheduler is not using an invalid address obtained from the client's options file or from the command line when the client scheduler was started.


ANR2716E Schedule prompter was not able to contact client node name using type address type (high address low address).
Explanation: The server has attempted to prompt the client scheduler for node node name because a scheduled operation should be started. The server is unable to contact the client by using address type address type, with high-level field high address and low-level field low address.
System Action: Server operation continues, but node node name is not prompted to start the scheduled operation. If operations should be started for other nodes, the server will attempt to prompt the client schedulers for these nodes. This error is usually caused by network outages or the client scheduler program not being run on the client node.
User Response: Verify that the address type and address are correct for this client. The only valid address type is 1 (for TCP/IP). Make sure the client scheduler is not using an invalid address, obtained at the time the client scheduler was started, from either the client's options file or from the command line. Verify that the client scheduler for node node name is running and that the necessary communication links to that scheduler are operational.


ANR2717E Schedule prompter cannot contact client node name using address type (address type).
Explanation: The server attempts to prompt the client scheduler for node node name because scheduled work should be started. However, either the server does not support address type address type needed for server-prompted scheduling, or the communication method is not currently available. The only valid address type is 1 (for TCP/IP).
System Action: Server operation continues, but the server does not prompt node node name.
User Response: If the server does not support the address type specified, clients may only use the polling mode of scheduling.

If the communication method is temporarily not available, prompted mode scheduling will resume after the communication problem is fixed and service restored.

If the problem persists, contact your service representative.


ANR2718W Schedule manager disabled.
Explanation: The schedule manager has been disabled because the DISABLESCHEDS YES option was specified in the server options file.
System Action: Server operation continues, but the central scheduler is not operational.
User Response: To enable the schedule manager, specify DISABLESCHEDS NO in the server options file and restart the server.


ANR2750I Starting scheduled command schedule name ( scheduled command ).
Explanation: This message is displayed when the server starts the execution of a scheduled command. The name of the schedule and the actual command scheduled is displayed.
System Action: Server operation continues, the scheduled command is processed.
User Response: None.


ANR2751I Scheduled command schedule name completed successfully.
Explanation: This message is displayed when the server successfully completes processing of a scheduled command.
System Action: Server operation continues.
User Response: None.


ANR2752E Scheduled command schedule name failed.
Explanation: This message is displayed when the server encounters a failure in processing a scheduled command.
System Action: Server operation continues. The scheduled command is ended.
User Response: Examine messages issued prior to this message and use the UPDATE SCHEDULE command to correct the scheduled command. The QUERY EVENT command may also be used to determine the cause of the failure for this scheduled command.


ANR2753I (schedule name):command response
Explanation: This message is used to display the server response to a scheduled command. The name of the command schedule is included at the beginning of the message in parentheses.
System Action: Server operation continues. The scheduled command is ended.
User Response: None.


ANR2754E DEFINE SCHEDULE or UPDATE SCHEDULE parameter CMD='command' - Unknown command.
Explanation: The specified command is not a valid server command.
System Action: The DEFINE SCHEDULE or UPDATE SCHEDULE command is not processed.
User Response: Reissue the correct command.


ANR2755E DEFINE SCHEDULE or UPDATE SCHEDULE parameter CMD='command' - not eligible for scheduling.
Explanation: The specified command is not eligible for scheduling.
System Action: The DEFINE SCHEDULE or UPDATE SCHEDULE command is not processed.
User Response: None.


ANR2756I Scheduled command schedule name started successfully.
Explanation: This message is displayed when the server successfully starts processing of a background process for a scheduled command.
System Action: Server operation continues.
User Response: None.

[ Top of Page | Previous Page | Next Page | Table of Contents ]