{
{   The purpose of this request is to change the logical state of a Central
{ Processor Unit (CPU).  Configuration status and control privilege is required to
{ be able to use this request.
{
{   All CPU state changes are logged in the Engineering Log (statistic CM0200);
{ the specific state change ( e.g.  ON to OFF) and the initiator of the change are
{ recorded.
{
{   The new state of a CPU will be preserved across NOS/VE system continuation
{ deadstarts.
{
{   The state for a central processor is initially determined at each NOS/VE
{ deadstart.  NOS/VE dynamically adapts to the logical presence or absence of
{ central processors dictated by the system operator during deadstart.
{
{   Only CPU elements which are not critical to system execution may be placed in
{ the OFF or DOWN states.  An example of a request which would be rejected is
{ downing or offing the only CPU.
{
{   If the system element is being returned to the ON state from the OFF or DOWN
{ state, it will be subject to automatic, element-dependent re-instatement
{ procedures.  This includes reloading microcode in a central processor, if
{ necessary.
{
{   Placing a CPU in the DOWN or OFF state has the following impact on the NOS/VE
{ system and its users:
{
{   The central processor is hardware idled and isolated from the
{ hardware error monitoring part of the system.
{
{   A few notes on element states:
{   (See ERS A6714: Configuration Management Program Interface, sec. 10.3.2)
{   ON state:
{   The ON state implies that the system element is either fully operational or
{ operating in a degraded mode, i.e.  capable of performing a useful subset of
{ its capabilities.  The ON state further indicated that the element is
{ available for use by the system or by (concurrent) maintenance.  An element
{ whose state is changes to ON will be subjected to NOS/VE-initiated,
{ element-dependent, reinstatement procedures including:
{        - standard microcode loading
{        - confidence testing
{        - label searching
{
{   OFF state:
{   The OFF state indicates that the system element is neither available to the
{ system not to online/concurrent maintenance.  An element may be placed in the
{ OFF state to inhibit its further use.  While in this state the element is
{ logically not present and may be physically isolated from the rest of the
{ system, i.e.  the element may be switched "off-line" or hardware idled so that
{ it cannot affect the rest of the system.  The CE may place an element in the
{ OFF state to prevent other users or OCM (On-line/Concurrent Maintenance) access
{ while an element is being repaired or until replacement parts are available to
{ complete a repair action.
{
{   DOWN state:
{   The DOWN state indicates that the system element may be accessed only by a
{ maintenance job.  This is provided for online, dedicated access to elements
{ which have failed or appear to have failed to operate correctly.  An element
{ in the DOWN state may be undergoing diagnostic or repair acivities.
{
{   A few notes on valid state changes:
{   (See ERS A6714: Configuration Management Program Interface, sec. 10.4.1)
{   The following table shows who may initiate an element state change and under
{ what conditions the state change is allowed.  A 'Y' or 'N' indicates the
{ action is allowed or disallowed under any circumstance.  A numeral refers to
{ one of the rules or comments (which appear in section 10.4.1 of the refered
{ ERS) to which the state change is subject in order to be valid.
{
{    ------------+-------------|----------+----------+------------
{                |             |  SYSTEM  |    CE    |  NOS/VE
{       FROM     |     TO      | OPERATOR |          |  SYSTEM
{    ------------+-------------|----------+----------+------------
{                |             |          |          |
{       ON       |  OFF        |     1,5  |    N     |      N
{       ON       |  DOWN       |     1    |    1     |      Y,2
{       OFF      |  ON         |     3,8  |    N     |      N
{       OFF      |  DOWN       |     4    |    N     |      N
{       DOWN     |  ON         |   3,5,8  |  3,5,6,8 |      N
{       DOWN     |  OFF        |     5    |    5,7   |      N
{
{
{       CMP$CHANGE_ELEMENT_STATE (PROCESSOR_ID, STATE, STATUS)
{
{ PROCESSOR_ID: (input)  This parameter specifies the number of the CPU whose
{       state is to be changed.  The identity specifiea the logical element
{       number of the CPU as it relates to the CPU state table.
{
{ STATE: (input)  This parameter specifies the new state of the element.
{
{ STATUS: (output) This parameter specifies the request status.
{
{         CONDITIONS:
{                     cme$request_state_is_crnt_state,
{                     ose$processor_not_defined,
{                     cme$lcm_ring_validation_error
{
{         IDENTIFIER:  'CM'
{
