{
{   The purpose of this request is to change the logical state of an element.
{ Configuration status and control privilege is required to be able to use this
{ request.
{
{   All element 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 peripheral element 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.  State
{ changes of a central processor made using this request are not preserved
{ across NOS/VE system continuation deadstarts; they merely control the use of
{ a processor until the next NOS/VE deadstart.
{
{   Only system elements which are not critical to system execution may be
{ placed in the OFF or DOWN states.  Examples of requests which would be
{ rejected are:  downing or offing the only CP, the system disk, or the only
{ channel/controller to the system deadstart device.
{
{   A state change is disallowed if the element is currently reserved to a job
{ or it is connected to a channel which is currently reserved to a job.  Refer
{ to the documentation of the CMP$RESERVE_ELEMENT request.  Elements which are
{ reserved by the NOS/VE system itself may or may not be permitted to change
{ state, depending upon the circumstances; refer to the documentation of the
{ CHANGE_ELEMENT_STATE subcommand of the Logical Configuration Utility.
{
{   If a peripheral element is identified in the element descriptor, this
{ request will ensure that the value of the element_type field matches the type
{ of the element identified by the peripheral_descriptor field.  Remember that
{ all reservable elements available to a non-system caller are either
{ classified as a controller or a storage device; refer to the description of
{ the DEFINE_ELEMENT subcommand of the Physical Configuration Utility for more
{ information.
{
{   If a channel has multiple ports, then all ports of the channel are affected
{ by the change of state.  For example, an I4 CIO channel may be referred to by
{ the name CCH1A, CCH1B, or CCH1; with respect to this request all forms of
{ reference have the same result.
{
{   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 one or more of the following:
{
{   .Reloading microcode in a central processor
{
{   .Down-loading of standard microcode into a peripheral
{
{   .Searching for system labels on mass storage volumes
{
{   Placing an element in the DOWN or OFF state has the following impact on the
{ NOS/VE system and its users:
{
{   If the element is a storage device:
{
{        1.  No further access to the media is permitted except for a
{            maintenance job (and then only if the element is in the DOWN
{            state).
{
{        2.  Jobs requiring access to the media are swapped out of memory until
{            the media is re-instated.
{
{        3.  For a mass storage device no further allocation is performed on
{            the media and new files are allocated to the remaining media.
{
{   If the element is a data channel, channel-adapter, or controller, the
{ effect of the state change is configuration-dependent, but the change will
{ prevent access to one or more storage devices in the absence of an alternate
{ access to the storage devices.
{
{   If the element is a central processor, the processor is hardware-idled and
{ isolated from the hardware-error-monitoring part of the system.
{
{       CMP$CHANGE_ELEMENT_STATE (ELEMENT, STATE, STATUS)
{
{ ELEMENT: (input)  This parameter specifies the identity of the system element
{       whose state is to be changed.  The identity may be specified using
{       either the name of the element or its hardware address.
{
{       If a peripheral hardware address is specified you must initialize the
{       physical_address_specifier to indicate how many parts of the address
{       are initialized in the address path.  For example, if you are changing
{       the state of a unit, the physical_address_specifier must include a
{       channel, a channel_address and the unit_address and you must initialize
{       all three fields of the hardware address.
{
{       If use_logical_identification is FALSE in any of the fields of the
{       element descriptor and the mainframe has more than one IOU, the name of
{       the IOU must be initialized because the channel identification is
{       ambiguous in this case.  The IOU component of the peripheral descriptor
{       will be ignored on single IOU mainframes.
{
{
{ STATE: (input)  This parameter specifies the new state of the element.
{
{ STATUS: (output) This parameter specifies the request status.
{
{         CONDITIONS:
{                     cme$element_unavailable_in_170,
{                     cme$lcm_element_not_found,
{                     cme$lcm_empty_pa_set,
{                     cme$lcm_missing_pa_set_member,
{                     cme$lcm_ring_validation_error,
{                     cme$privileged_job_required.
{
{         IDENTIFIER:  'CM'
{
{
