modify_system

Adds or removes targets from an existing system. An error is not generated when attempting to delete a non-existent target in the system or when attempting to add a target that already exists in the system.

If you specify both the -add_members and -delete_members options in the same command, the members specified by -delete_members are deleted first, then the members specified by -add_members are added.

Format

emcli modify_system 
         -name="name" 
         [-type=<generic_system>]
         [-add_members="name1:type1:key_member|non_key_member;name2:type2;..."]... 
              [-separator=add_members="sep_value"] 
              [-subseparator=add_members="subsep_value"] 
         [-delete_members="name1:type1;name2:type2;..."]... 
              [-separator=delete_members="sep_value"] 
              [-subseparator=delete_members="subsep_value"] 
         [-owner="new_owner"] 
         [-privilege_propagation=true|false] 
         [-drop_existing_grants=yes|no] 
         [-availability_type="ALL/ANY"]

[ ]  indicates that the parameter is optional

Options

• name

  Target name of the system to modify.

• type

  System type: generic_system. Defaults to generic_system.

• add_members

  Targets to add, each specified as target_name:target_type. You can specify this more than once. key_member specifies that this target is a part of the systems availability calculation. non_key_member specifies that this target is not a part of the systems availability calculation.

• delete_members

  Member targets to be removed from the system, each specified as target_name:target_type. You can specify this option more than once.

• owner

  New owner of the system.

• privilege_propagation

  Enables or disables the privilege propagation flag for the group. Converts the normal group to a privilege propagating group and vice versa.

• drop_existing_grants

  Drops existing grants on a group when conversion occurs in privilege propagation nature. This option is only applicable with the privilege_propagation parameter. The default value is yes.

• availability_type

  Availability calculation method of the system. Defining this is required if key_member is defined. ALL denotes that all key members must be up in order to establish the system as UP. ANY denotes that at least one of the key members must be up in order to establish the system as UP.

Examples

Example 1

This example modifies system my_system by adding targets system_a:generic_system and database:oracle_database, and deleting the nonexistent target nosystem:generic_system from the system.

emcli modify_system -name=my_system
      -add_members=system_a:generic_system
      -add_members=database:oracle_database
      -delete_members=nosystem:generic_system

Example 2

This example modifies system db2_system by adding database database1 as a key member, adding databases database2 and database3 as non-key members, and deleting database4 and database5. The availability computation is impacted, since database1 is now part of the availability computation for the db2_system. If database4 and database5 were key members, they are no longer part of the availability computation for the db2_system.

Specifying separator and subseparator is optional. Separator defaults to ; and subseparator defaults to : .

emcli modify_system -name=db2_system -type=generic_system 
  [add_members=database1:oracle_database:key_member,database2:oracle_database] 
     [separator=add_members=","] 
     [subseparator=add_members=":"] 
  [add_members=database3:oracle_database:non_key_member]
  [delete_members=database4:oracle_database,database5:oracle_database]
     [separator=delete_members=","] 
     [subsrparator=delete_members=":]"