# Migrating user DASD group definitions

After upgrading to Interim Feature 2, you can make your user DASD groups dynamic. Instead of using the Configuration Tool to define a group, you can specify dynamic user DASD groups within the Tivoli Enterprise Portal.

Groups defined prior to Interim Feature 2 using the Configuration Tool are stored in RKANPARU member KDFDUDGI. A migration function in Interim Feature 2 allows you to create new dynamic user DASD groups from the definitions in KDFDUDGI. After migrating the KDFDUDGI, you can manage those groups dynamically using the Tivoli Enterprise Portal.

To navigate to the migration function, select the User DASD Groups Space workspace from the navigation tree, right-click a row on the table view, and select the Migrate Groups menu item. Confirm the migration in the Confirm User DASD Group Migration dialog box.

The migration process:

1. Locates and reads the KDFDUDGI member of the RKANPAR dataset of the z/OS based Tivoli Enterprise Monitoring Server (monitoring server).
2. Parses each individual group definition defined in the KDFDUDGI member.
3. Re-creates each individually read and parsed group definition as a persisted dynamic user DASD group definition.

Note:

- Previously migrated or identically named user DASD groups are not updated or affected by the migration function.
- Group definitions from KDFDUDGI are always created with the persist flag enabled.
- KDFDUDGI group definitions with invalid syntax are not migrated.
- KDFDUDGI member is not altered in any way by the migration function.
- User DASD group descriptions from Configuration Tool are not included in KDFDUDGI member and therefore are not migrated.
- Migration error messages are logged to the RKLVLOG of the z/OS-based monitoring server.