Task Rejection Messages Under certain conditions TaskMan can avoid trapping obvious errors by checking the tasks themselves for internal consistency. Whenever it finds tasks with bad data, it rejects them. This involves unscheduling them, setting their status codes to B, and adding a brief explanatory message. These messages can help identify bugs in application queuing software, in the local system configuration, or in TaskMan itself. Table : TaskMan Rejection Messages TaskMan Rejection Message Description BAD DESTINATION UCI The Manager rejects a task for this reason under three different conditions: If the task is bound for the own Volume Manager’s Set, whatever value has been passed for the destination UCI must be a valid UCI on the current Volume Set. If rejects the ^%ZOSF(“UCICHECK”) UCI, TaskMan rejects the task. If the task is bound for a different Volume Set and the destination UCI is not listed in the UCI ASSOCIATION (#14.6) file under that Volume Set, the UCI must be accepted as a valid UCI on the current Volume Set so TaskMan can use File #14.6 to determine where the task should run. If rejects the UCI, TaskMan ^%ZOSF(“UCICHECK”) rejects the task. If the task is bound for a different Volume Set and that Volume link is down and its Set’s REPLACEMENT VOLUME SET is the current Volume Set, TaskMan rejects the task. BAD DESTINATION VOLUME Every destination Volume Set must be listed in the task’s SET VOLUME SET (#14.5) file. BAD IO DEVICE <$I> If a port goes bad while many tasks wait for it in the Busy Device Waiting list, TaskMan traps an error whenever the port is tested for availability. When the submanager traps such an error, it rejects every task waiting for that device. INVALID OUTPUT DEVICE The Manager performs a lookup on the devices that tasks request. If the ^%ZIS call indicates that the device does not exist, TaskMan rejects the task. INVALID ROUTINE NAME If a entry point is in a %-routine, the Manager tests task’s for that existence in the library UCI. If the routine’s routine does exist there, TaskMan rejects the task. not NO DESTINATION UCI When older applications bypassed the Program Interface, they sometimes scheduled tasks without specifying the destination UCI. The Manager rejects all such tasks.
Task Rejection Messages Under certain conditions TaskMan can avoid trapping obvious errors by checking the tasks themselves for internal consistency. Whenever it finds tasks with bad data, it rejects them. This involves unscheduling them, setting their status codes to B, and adding a brief explanatory message. These messages can help identify bugs in application queuing software, in the local system configuration, or in TaskMan itself. Table : TaskMan Rejection Messages TaskMan Rejection Message Description BAD DESTINATION UCI The Manager rejects a task for this reason under three different conditions: If the task is bound for the Manager’s own Volume Set, whatever value has been passed for the destination UCI must be a valid UCI on the current Volume Set. If ^%ZOSF(“UCICHECK”) rejects the UCI, TaskMan rejects the task. If the task is bound for a different Volume Set and the destination UCI is not listed in the UCI ASSOCIATION (#14.6) file under that Volume Set, the UCI must be accepted as a valid UCI on the current Volume Set so TaskMan can use File #14.6 to determine where the task should run. If ^%ZOSF(“UCICHECK”) rejects the UCI, TaskMan rejects the task. If the task is bound for a different Volume Set and that Volume Set’s link is down and its REPLACEMENT VOLUME SET is the current Volume Set, TaskMan rejects the task. BAD DESTINATION VOLUME SET Every task’s destination Volume Set must be listed in the VOLUME SET (#14.5) file. BAD IO DEVICE <$I> If a port goes bad while many tasks wait for it in the Busy Device Waiting list, TaskMan traps an error whenever the port is tested for availability. When the submanager traps such an error, it rejects every task waiting for that device. INVALID OUTPUT DEVICE The Manager performs a lookup on the devices that tasks request. If the ^%ZIS call indicates that the device does not exist, TaskMan rejects the task. INVALID ROUTINE NAME If a task’s entry point is in a %-routine, the Manager tests for that routine’s existence in the library UCI. If the routine does not exist there, TaskMan rejects the task. NO DESTINATION UCI When older applications bypassed the Program Interface, they sometimes scheduled tasks without specifying the destination UCI. The Manager rejects all such tasks.