Migrating Assure Security by Live Partition Mobility (LPM) - 7.0

Assure Security Installation (via Wizard) Guide
Product type
Software
Portfolio
Integrate
Product family
Assure
Product
Assure Security > Assure Elevated Authority Manager (EAM)
Assure Security > Assure Encryption
Assure Security > Assure Secure File Transfer
Assure Security > Required for All Modules
Assure Security > Assure Monitoring and Reporting (AMR)
Assure Security > Assure Security Multi-Factor Authentication (MFA)
Assure Security > Assure DB2 Data Monitor (DB2MON)
Assure Security > Assure System Access Manager (SAM)
Assure Security > Assure Secure File Transfer with PGP
Version
7.0
Language
English
Content type
Installation (Wizard) Guide
Product name
Assure Security
Title
Assure Security Installation (via Wizard) Guide
Copyright
2023
First publish date
1999
Last updated
2025-01-05
Published on
2025-01-05T12:58:55.063000
When a system migration is performed by allocating existing disk volumes to a new partition or serial number there are special considerations for Assure Security that must be followed. A system migration of this type could use IBM's Live Partition Mobility (LPM) or perhaps a number of other ways where existing disk volumes are allocated to a new partition or serial number.

Do the following:

Note: The default Assure Security installation library SECOPS is used in the specified commands.
  1. On the original system, end all queries in the correct manner to ensure the appropriate cleanup is done. Run the following command:
    SECOPS/ENDQJF QJ(*ALL)
  2. End the SECOPS subsystem on the original system. Run the following command:
    ENDSBS SBS(SECOPS) OPTION(*IMMED)
  3. Perform the Live Partition Mobility (system migration) procedure. Refer to the IBM documentation for details.
  4. Apply the Assure Security license keys on the new system. For more details, see Obtain license keys after a new install without keys.
  5. On the new system, perform a query coherence check to ensure that the files used within queries are journaled, the fields exist in the repository and the definitions are the same. Run the following command:
    SECOPS/RUNQJCLN
    You can run the command with the default parameters. Alternatively, set Control Queries to NO to make it run faster.
    Note: This command can be run when the SECOPS subsystem is down since it does not submit a job.
  6. Start the SECOPS subsystem on the new system. Run the following command:
    STRSBS SBSD(SECOPS/SECOPS)