The schedule prompter skipped the contact attempt with the client scheduler for node node name because the start-up window has passed for that node, or the node was locked.
Server operation continues.
Check the length of the schedule start-up window to see if it needs to be increased. Check the activity log for ANR2716E messages. These messages are associated with failures to contact a client scheduler. If there are an excessive number of these messages the schedule window could have elapsed waiting for TCP/IP timeouts from these failed attempts. Also, check to see if the client node is locked. The contact attempt would be skipped for a locked node.