Skip to Content
Information
Limited support BMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Storage Allocation 8.1.

Stopping SVOS

Use the following procedures to stop SVOS.

To stop SVOS and all active components

On the COMMAND line, enter //SHUTDOWNIn this command, / is the SVOS command character that is specified in the SUBCHAR parameter in SVOS JCL.

The SHUTDOWN command stops SVOS and any BMC products that are running under SVOS. No SVOS messages are written to the console on a successful shutdown.

To stop SVOS and all active components except SVALLOC or X37II

On the COMMAND line, enter one of the following commands:

  • /HONLY
  • /HOOKONLY

In this command, / is the SVOS command character that is specified in the SUBCHAR parameter in SVOS JCL.

The HOOKONLY command stops SVOS and all BMC products that are running under SVOS except MainView SRM Allocation (SVALLOC) or MainView SRM StopX37/II (X37II stand-alone product). This command allows you to make JCL changes to the MainView SRM Started Task (SVOS) without removing recovery hooks for Allocation or StopX37/II.

Warning

Note

Subsequently restarting the MainView SRM started task automatically reinstalls the recovery hooks for Allocation or StopX37/II, with any updated maintenance applied.

Error
Warning

The risk to leaving the Allocation or StopX37/II hooks in place and shutting down the SVOS address space is that no active loader will be available to accept the commands to shut down SVALLOC or X37II. The only way to remove the hooks is to start SVOS again. If you want to remove the Allocation or StopX37/II hooks and system problems prevent SVOS from being started, an IPL will be required.

Restarting the MainView SRM address space stops and restarts the existing SVALLOC or X37II product. The following examples show the messages you will see when MainView SRM is restarted prior to reinitializing the product components:

SVO0106I RELEASE v.r.m OF MainView SRM OPERATOR SERVICES HAS BEEN STARTED

SVO0627I MainView SRM/ALLOC v.r.m STOPPING ON ETIS

SVO0620I MainView SRM/ALLOC v.r.m HAS BEEN STOPPED ON ETIS

SVO0620I MainView SRM SVOS v.r.m HAS BEEN STOPPED ON ETIS

For the Allocation component or the StopX37/II product, the following loss of functionality will occur when the SVOS address space is not active:

  • No MainView SRM commands can be processed, including the REFRESH command that is used to modify existing rules for MainView SRM components.
  • You cannot access MainView SRM views.
  • SVALLOC or X37II functions are bypassed as follows:
    • NOCATLG2 function for all SMS-managed data sets
    • DASDPOOL function using DPO* parameters in FLST/RLST rules
    • DASDPOOL function using HDPO* parameters in FLST/RLST rules
    • DASDPOOL function using VOLSEL=CRITDSN/DPO/HISTDPO parameter in FLST/RLST rules
    • SMSSELCT function using DPO* parameters in FLST/RLST rules
    • SMSSELCT function using HDPO* parameters in FLST/RLST rules
    • SMSSELCT function using VOLSEL=CRITDSN/DPO/HISTDPO parameter in FLST/RLST rules

When the SVOS address space is not active, the Automation and Reporting components will not function except for the following batch report (SGBRPORT) verbs:

  • BCDS_DATASET
  • BCDS_VERSION
  • HLQ
  • MCDS
  • OCDS_DATASET
  • OCDS_VOLUME
  • SLOC_ATTRIB
  • SLOC_DSN
  • SLOC_SPACE
  • SLOC_TOTAL
  • SLOC_VOLUME

The VTOC_DSN and VTOC_VOL report verbs will work when COSSR400 creates and passes the extract file to the batch report; however, they will not work when the batch report invokes a VTOC SCAN to generate an extract file.

 

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

MainView SRM Allocation 8.0