CA Mainframe VM Product Manager - 1.2 : Starting a CA VM Product

Contents

The CA Mainframe VM Product Manager manages server products using an interface which connects the server to the product manager when the server starts. Server configuration information you define in the VMSERVER NAMES file tells the server how to operate under your control. This connection is established when the server PROFILE EXEC calls the PROFRUN EXEC.

PROFRUN EXEC Processing

When you log on to a CA VM product user ID, the PROFILE EXEC invokes the PROFRUN EXEC. The first time you access a product after installing or upgrading it, log on to the product instead of using an AUTOLOG process, so that you can learn of any errors that PROFRUN EXEC encounters.

Because PROFRUN EXEC is run each time you log on to a product server, the product is kept properly positioned for upgrading to new release levels and for day-to-day product administration.

The PROFRUN EXEC performs the following functions:

  • Links and accesses CA Mainframe Product Manager product configuration definitions in the VMSERVER NAMES files.
  • Links and accesses CA Mainframe Product Manager utility programs and startup service routines.
  • Links and accesses CA Product License Key certificates for verification.
  • Accesses any additional minidisks needed to start the product.
  • Starts the product
  • Initiates the Do you wish to start product? prompt and additional options as defined by the product
  • Logs off the product if it is running disconnected when the END command is issued
  • Manages the product re-initialization process. If you are logged on to the VMANAGER user ID, you can reinitialize products from the VMADMIN Administration Menu instead of logging on to the product.

The PROFRUN EXEC supports keyword parameters, which tailor the following function.

  • NOPROMPT suppresses the prompt which asks whether to start operations and proceeds directly to start the product execution.
  • NOSTART links and accesses the configuration disk and service routines disk, but returns to CMS command mode without starting the product execution.
  • NOLOG suppresses the LOGOFF command usually issued when the product is stopped by a product END command.

Starting a Product Server

When PROFRUN EXEC runs, it prompts you to enter yes or no to indicate whether you want to start the product. Some product servers prompt for and accept additional responses.

Starting CA VM Director or CA VM Secure

If you are starting CA VM:Director or CA VM:Secure, PROFRUN EXEC gives you an additional option at the prompt:

  • SOURCE
    Forces CA VM:Director or CA VM:Secure to rewrite the online directory from the source files on the DRCT minidisk. The SOURCE option takes precedence over any other startup command coded in the VMSERVER NAMES file.

Starting CA VM Backup

If you are starting CA VM:Backup, PROFRUN EXEC gives you additional options at the prompt:

  • COLD
    Suppresses restart recovery when CA VM:Backup is restarted after an abnormal system termination. This option erases the COMPJOB files for existing jobs, and removes all jobs waiting in the job queue and their associated checkpoint data.
  • SUSPEND
    Starts CA VM:Backup without permitting new jobs to start. Interrupted backup and restore jobs are not restarted. CA VM:Backup comes up in a suspended state, exactly as if you issued the SUSPEND command after initialization.
  • NOCHECK
    Initializes CA VM:Backup without performing catalog verification. This option expedites processing during initialization, but can cost you additional time later if the CA VM:Backup catalog files are not structured properly.

Server Startup Command

The PROFRUN EXEC retrieves the product specific server startup command line from the STARTCMD tag in the VMSERVER NAMES file entry for the server. The tag value is displayed on the NAMEs file panel displayed by the VMSERVER command and is prefixed by the label Server Startup Command.

If you have a site-specific startup command or option, you may manually insert an alternate command string, including any desired options, in the VMSERVER NAMES file.

For example, if you want server VMBACK33 to execute with the NOCHECK option, replace the value of the STARTCMD tag in the VMSERVER NAMES file entry for VMBACK33 with the string:

VMBSYS ( NOCHECK