Transferring update capability

Given the following initial and target configurations, use this scenario to transfer update capability from one sharing IMS system to another.

  • Initial configuration
    • dbx is authorized for update access to an online IMS system (IMSA).
    • dbx is authorized for read-only access to another online IMS system (IMSB).
  • Target configuration
    • dbx is authorized for read-only access to IMSA.
    • dbx is authorized for update access to IMSB.

Follow these steps to transfer update compatibility:

Procedure

  1. Prevent other IMS systems from obtaining access to dbx with the following command: CHANGE.DB DBD (dbx) NOAUTH
  2. Suspend activity and close dbx in both IMS systems with one of the following commands:
    • /DBRECOVERY DB dbx NOFEOV
    • UPDATE DB STOP(ACCESS)
  3. Allow processing in both IMS systems. Issue one of the following commands on IMSA:
    • /START DB dbx ACCESS=RO
    • UPDATE DB START(ACCESS)
  4. Then issue one of the following commands on IMSB:
    • /START DB dbx ACCESS=UP
    • UPDATE DB START(ACCESS)
  5. Allow access or update in both IMS systems with the following command: CHANGE.DB DBD(dbx) AUTH
    Although IMSA and IMSB now have compatible database authorizations, the database is not protected from other IMS systems until IMSA and IMSB schedule an application program with a PSB that is sensitive to the database. In order to lock out any other updaters, therefore, IMSB must be the first IMS system to obtain the authorization to process the database with update access.