PTF SO13945 renames RESTART VMOPER to REBOOT VMOPER

book

Article ID: 195173

calendar_today

Updated On:

Products

CA VM:Operator

Issue/Introduction

PTF SO13945 renames RESTART VMOPER to REBOOT VMOPER

Cause

PTFs RO41324, RO42233, and RO42284 were written to address problems with "RESTART" in VM:Operator.  The underlying issue was that VM:Operator previously provided a RESTART VMOPER macro that had a specific behavior, including a "IPL CMS" that was sometimes desirable. When VM:Operator was converted to the Common Nucleus with version 3.0, the Common Nucleus has an existing RESTART command, so the RESTART command was taking precedence.

Although the previously mentioned PTFs corrected the problems with the RESTART command, customers now were not able to get the behavior that the RESTART VMOPER macro previously provided due to the name conflict.
 
As a workaround, customers were instructed to rename the RESTART VMOPER macro to REBOOT VMOPER, then issue REBOOT instead of RESTART. This worked, however, after running VMDEPLOY to deploy service, VMDEPLOY erases the
REBOOT VMOPER macro because it is not in any VM:Operator build list.

Environment

Release : 3.1

Component : CA VM:Operator

Resolution

Provided an official REBOOT VMOPER that provides the function that the original RESTART VMOPER macro provided.

VM:Operator PTF SO13945 officially renames the RESTART VMOPER macro to REBOOT VMOPER so, REBOOT VMOPER will now always be deployed to the code disk.