AUTOADDV console command

This topic describes the AUTOADDV console command.

Related topic

Component-specific-SVOS-console-commands

The AUTOADDV command causes the Automation component to add a volume to a storage group.

This command can be scheduled:

  • With the Scheduled Service facility
  • In response to any message or situation that indicates that a storage group has reached a utilization threshold
  • From an automated operations package in response to an event or message, such as in response to a message indicating a failure due to available space in a storage group
  • In response to an AUTO function solution or SET statement

For example, an AUTOPOOL function solution could detect a storage group over 95 percent full and issue an AUTOADDV command to add a volume to the group. The AUTOPOOL statement might look like this example:

SET SOLUTION=ADDGT95 SVOSCMD='AUTOADDV GROUP=&GROUP'
INC AP_PERFL > 95

The &GROUP variable in the SVOSCMD command text would be resolved with the storage group matching the SET statement.

Any new volume added to a storage group will be unknown to BMC AMI Storage until the next configuration refresh completes when a volume is varied online and the SVM2046I CONFIGURATION COLLECTION/REFRESH SUCCESSFULLY COMPLETED message appears in the BMC AMI Storage joblog. For more information about new volumes varied online, see ENFTIME global parameter in Reference for BMC AMI Storage products.

Syntax

AUTOADDV GROUP=<storageGroup>

Variable

The storageGroup variable specifies the name of the storage group to which the volume will be added. The SMS storage group definition must contain definitions for volumes that do not exist, known as empty slots, which are used by this facility without having to change the storage group definition.

An alphanumeric value (up to 30 characters), as determined by the storage group definition

The variable is required. If it is not specified, the command is rejected.

Example:

This example causes a volume from the candidate pool to be added to the GROUPABC storage group.

SVOS AUTOADDV,GROUP=GROUPABC

Restrictions

The following restrictions apply to AUTOADDV command usage:

  • Only one AUTOADDV command can be processed at a time.

    After an AUTOADDV command is in process, subsequent requests for the same storage group are rejected and a message is issued, indicating that the request is considered a duplicate request. Subsequent requests for different storage groups are accepted and are queued for execution. Each request will be processed in the reverse order in which it was received, however, there may only be one request for any single storage group at a time. No other limits apply to the number of volumes that can be added to a storage group.

  • MCS consoles must be supported.

    This facility makes use of an extended MCS console from within the SVOS address space. MCS console support can be removed by using the IEARELEC sample program that is shipped with MVS. For more information, see the IBM document, z/OS MVS PLANNING: OPERATIONS.

    If the MVS.MCSOPER.** RACF facility is active, the USERID associated with the SVOS address space must be given READ access, which enables SVOS to activate an MCS console. For more information, see Customizing-after-installation.

    Note: If the MVS.MCSOPER.** RACF facility is active, the USERID associated with the SVOS address space must be given READ access, which enables SVOS to activate an MCS console. For more information, see Customizing-after-installation.

  • All volumes in the target storage group must be online to the local system.

    If the system is a member of a sysplex, all volumes in the group should be online to all systems in the sysplex. The device number of the volume should be the same across all systems in a sysplex. If volumes in the target storage group are not online, BMC AMI Storage could consider the volser values as available slots in the storage group definition and could then initialize another device with the same volser.

  • The local system cannot be a VM system.

    If the system is a member of a sysplex, no member of the sysplex can be a VM system.

  • In a JES3 environment, volumes in the candidate pool must be devices that are managed by MVS.

    JES3 devices, devices managed by JES3, and jointly-managed devices cannot be used.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*