×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')
Installation System ... Maintaining Maintaining the Installation System

Managing the bootstrap RTCS

The bootstrap Runtime Component System  ( RTCS ) creates the RTCS  address space, which is used to store data and anchor resources. All processing occurs in the TSO session or batch jobs. Use the following procedures to manage the bootstrap RTCS :

To stop the bootstrap  RTCS

When you are not using the Installation System, you should stop the bootstrap RTCS  address space.

  1. Have all users exit the Installation System.
  2. Have all users of the Installation System log off their TSO sessions.
  3. Issue the following command:

    P STCProcName

    STCProcName is the name of the bootstrap RTCS  address space you assigned when creating the bootstrap RTCS .

To start the bootstrap  RTCS

When you want to use the Installation System again, you need to start the bootstrap RTCS  address space.

Issue the following command:

S STCProcName

STCProcName is the name of the bootstrap RTCS  address space you assigned when creating the bootstrap RTCS .

To switch to a permanent  RTCS

If you have been using the bootstrap RTCS , and you have now installed a permanent RTCS , you can copy the Installation System repository from the bootstrap RTCS  to the permanent RTCS .

Perform this procedure before starting the Installation System.

  1. Perform a backup of the bootstrap RTCS .

    Use the BACKUP control statement of the RTCS  Registry Maintenance Utility (RMU).

    For more information about RMU, see Administering Runtime Component System (RTCS) Open link .

  2. Perform an import of the bootstrap RTCS  to your permanent RTCS .

    Use the RESTORE control statement of the RMU.

Related topic

Maintaining the Installation System

Was this page helpful? Yes No Submitting... Thank you
Last modified by Jyoti Birajdar on Sep 06, 2022
maintenance task

Comments

  1. Horst Gfrerer

    Some cmds are incorrect according to OSZBOOT Docs

    CONTENTS: RTCS BOOTSTRAP SUBSYSTEM ADDRESS SPACE STARTED
    TASK (STC) PROCEDURE. THIS PROC IS INTENDED TO BE
    PLACED INTO ANY JES-MANAGED STARTED TASK PROCEDURE
    LIBRARY. 

          OSZBOOT (WHATEVER ITS ACTUAL NAME IN AN STC PROCLIB) 
      WILL USUALLY BE STARTED UNDER THE PRIMARY JOB ENTRY  
      SUBSYSTEM (JES) USING THE FOLLOWING MVS COMMAND:     

         START OSZBOOT.RTCS                                

      THE OPERATOR MODIFY COMMAND ENTRY "CSCB NAME"        
      QUALIFIER '.RTCS' IS _REQUIRED_ AND MAY NOT BE       
      OMITTED. THIS REQUIREMENT IS INTENDED TO PREVENT     
      AN ACCIDENTAL, UNWANTED, AND UNINTENDED START OF     
      THE RTCS BOOTSTRAP SUBSYSTEM ADDRESS SPACE.

    Stop is always /P RTCS ?

    Jun 06, 2023 06:37
    1. Dov Kaiser

      Hi, Horst. Thank you for your question. I have forwarded to the writer who is responsible for this content.

      Jun 06, 2023 07:20
  2. Jyoti Birajdar

    Hi, Horst.

    The command to stop RTCS depends on what command was used to start the RTCS Bootstrap Subsystem. In the normal production case, you start the bootstrap with the following command:

    S OSZRTCS.RTCS

    To stop RTCS, use the following command:

    P RTCS

    For more information about how to stop RTCS, see https://docs.bmc.com/docs/display/cmi22/Stopping+RTCS.

    Regards,

    Jyoti

    Jul 19, 2023 09:07

Log in or register to comment.

Managing projects
Authorizing
© Copyright 2014–2023 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.