Reach TaskMan’s The key issue that defines is its those places where TaskMan TaskMan’s configuration “reach,” can start background jobs. reach extends to: TaskMan’s All UCIs a submanager can access directly after using UCI switching facilities. Kernel’s All other managers TASKS (#14.4) and SCHEDULE files to which a given manager can WRITE using extended global reference. All UCIs on Print Servers with link access to the current Volume Set. reach does include other sites on a wide area network, because they be not cannot TaskMan’s accessed through either UCI switching or through extended global reference. There are ways to simulate such a reach through the use of server options, however. For purposes of TaskMan configuration, we generally think in terms of the reach of a single manager, which can only run tasks in the UCIs it can reach. TASKMAN SITE PARAMETERS (#14.7) File Figure : Site Parameters Edit Option SYSTEMS MANAGER MENU ... [EVE] Task Manager ... [XUTM MGR] Taskman Management Utilities ... [XUTM UTIL] Edit Taskman Parameters ... [XUTM PARAMETER EDIT] Site Parameters Edit [XUTM BVPAIR] System managers enter one set of site parameters into the TASKMAN SITE must PARAMETERS (#14.7) file for each manager that runs in a different Volume Set/CPU. This set of parameters tells each manager how it should process tasks. The parameters are organized both by Volume Set and by CPU. This allows two CPUs that share a Volume Set to be treated differently if one is more powerful than the other.
TaskMan’s Reach The key issue that defines TaskMan’s configuration is its “reach,” those places where TaskMan can start background jobs. TaskMan’s reach extends to: All UCIs a submanager can access directly after using Kernel’s UCI switching facilities. All other managers TASKS (#14.4) and SCHEDULE files to which a given manager can WRITE using extended global reference. All UCIs on Print Servers with link access to the current Volume Set. TaskMan’s reach does not include other sites on a wide area network, because they cannot be accessed through either UCI switching or through extended global reference. There are ways to simulate such a reach through the use of server options, however. For purposes of TaskMan configuration, we generally think in terms of the reach of a single manager, which can only run tasks in the UCIs it can reach. TASKMAN SITE PARAMETERS (#14.7) File Figure : Site Parameters Edit Option SYSTEMS MANAGER MENU ... [EVE] Task Manager ... [XUTM MGR] Taskman Management Utilities ... [XUTM UTIL] Edit Taskman Parameters ... [XUTM PARAMETER EDIT] Site Parameters Edit [XUTM BVPAIR] System managers must enter one set of site parameters into the TASKMAN SITE PARAMETERS (#14.7) file for each manager that runs in a different Volume Set/CPU. This set of parameters tells each manager how it should process tasks. The parameters are organized both by Volume Set and by CPU. This allows two CPUs that share a Volume Set to be treated differently if one is more powerful than the other.