skip book previous and next navigation links
go up to top of book: HP OpenVMS Alpha Partitioning and Galaxy Guide HP OpenVMS Alpha Partitioning and Galaxy Guide
go to beginning of chapter: CPU Reassignment at the DCL CLI CPU Reassignment at the DCL CLI
 
go to next page: GCU Drag-and-Drop ReassignmentGCU Drag-and-Drop Reassignment
end of book navigation links

DCL Reassignment  



You can perform CPU reassignment operations if you have CMKRNL privilege using the following DCL command:
$ STOP/CPU/MIGRATE=instance-or-id   cpu-id
You must provide the target instance name (SCSNAME) or numeric ID (0, 1, and so on), and the numeric ID of the CPU being reassigned. The following examples show a few forms of this command:
$ STOP/CPU/MIGRATE=0  4      !Reassign CPU 4 to instance 0
$ STOP/CPU/MIGRATE=1  3,4,5  !Reassign CPUs 3,4,5 to instance 1
$ STOP/CPU 7/MIGRATE=BIGBNG  !ReassignCPU 7 to instance BIGBNG
$ STOP/CPU/ALL/MIGRATE=0     !Reassign all secondary CPUs to instance 0
You can insert these commands into command procedures. For example, you might want to move extra CPU resources to an instance in a startup procedure of an application with known processing requirements. Similarly, you may want to reassign CPUs away from an instance that is about to perform lengthy, I/O-intensive operations (such as backups) so that the CPUs are available to other instances. When the job completes, you may reassign them back or you may reassign CPUs away from an instance that is shutting down.

You can only reassign resources away from an instance. This is the push model defined by the Galaxy Software Architecture. This model prevents resources from being stolen by other instances that may not be aware of their current usage. To effectively manage the entire Galaxy system using DCL, you must either log in to each of the involved instances or use the SYSMAN utility to execute the commands on the owner instance.


 
go to next page: GCU Drag-and-Drop ReassignmentGCU Drag-and-Drop Reassignment