Limited support BMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see ALTER and BMC AMI Change Manager for Db2 13.1.

Creating a receive-type work ID

When you migrate data only or data structures and data to a different subsystem, you must use a receive-type work ID on the receiving subsystem to execute phase 2 of the worklist.

Phase 2 of the worklist creates the data structures and loads any migrated data. You can create a receive-type work ID by using any of the following methods:

  • Creating the work ID in the Front End before executing the worklist.
  • Building the JCL manually in batch mode by using the NEWWORKID or REPLACEWORKID keyword in the AEXIN input stream.

Note

The receive-type work ID must have the same name as the migrate-type work ID that you used to generate the migrate-type worklist on the sending subsystem.

This task requires an existing migrate-type worklist.

To create a receive-type work ID in the Front End

  1. On the BMC AMI Change Manager for Db2 Main Menu, select WORKID, and press Enter.
  2. On the WORKID Action Menu, type the name of the migrate-type work ID that you used to generate the migrate-type worklist and select Create a new WORKID. Then, press Enter.

  3. On the Create WORKID pane, specify the information for the work ID.

    1. Select Receive for the Type.
    2. (Optional) Specify a Comment to describe the work ID.
    3. Press Enter.

    The WORKID Action Menu is displayed.

To create a receive-type work ID in batch

You can create a receive-type work ID in batch by editing the JCL outside of ALTER or BMC AMI Change Manager for Db2.

  1. In ISPF, edit the Execution JCL.

  2. Insert the NEWWORKID a.b ( a.b is the new work ID that you want to create) keyword into the AEXIN data input stream, as shown below The work ID must not currently exist.

    //AEXIN    DD *
     ACM
     SSID DEBA NEWWORKID RDAMAF.REC

    Note

    In the CM/PILOT component of Change Manager, you can use a template to specify the Change Manager keyword. The #### characters are resolved by an ascending sequence of numbers and the @@@@@@@@ characters are resolved by using the current date. For more information, see Creating-a-task-ID.

To re-create an existing receive-type work ID in batch

You can receive a migrate-type worklist from a remote location to re-create the existing receive-type work ID by editing the JCL outside of ALTER or Change Manager.

  1. In ISPF, edit the Execution JCL.

  2. Insert the REPLACEWORKID a.b (where a.b is the name of the existing work ID that you want to replace) keyword into the AEXIN data input stream, as shown below.

    //AEXIN    DD *
     ACM
     SSID DEBA REPLACEWORKID RDAMAF.REC

    Note

    If the specified work ID does not exist, Execution creates it.

    When the job is run, the receive-type work ID is replaced.

    Note

    In the CM/PILOT component of Change Manager, you can use a template to specify the REPLACEWORKID keyword. The #### characters are resolved by an ascending sequence of numbers and the @@@@@@@@ characters are resolved by using the current date. For more information, see Creating-a-task-ID.

    REPLACEWORKID is not allowed if the existing work ID status indicates that execution was started but not successfully completed.

Where to go from here

After you create the receive-type work ID, select Execute WORKID worklist created by Analysis to execute the worklist.



 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*