Obtain Downgraded Objects at Requested Protection

Checking a Subset In or Out of the Encyclopedia › Recover from Scoping Errors › Obtain Downgraded Objects at Requested Protection

Obtain Downgraded Objects at Requested Protection

After identifying protection downgrades, you want to:

Wait for the conflicting subsets to be checked in. Meanwhile, if you have checked out your subset:
- Check it in so that you can try again.
- Override the subset checkout status of your subset (if you checked it out). If you are a member of a group user ID and the group is the model administrator, you can also override the checkout or can ask the model administrator to override the checkout.
Ask the user of a conflicting subset to make the downgraded objects available to you. To make the objects available, the user must check in the subset and:
- Wait for you to finish working with the objects.
- Change the conflicting subset's definition to lower the protection that is requested on the downgraded objects so that the new protection requests are not in conflict with your requests.
- Asking the current user to check in or change a subset definition is justified if the person has requested Delete protection on an object when Modify or Access would serve too.
If the current user is unavailable, consult the model administrator about changing the checkout user ID for that person's subset.
After the change of checkout user ID, the person whose TSO ID is substituted can check the subset in, thus making the subset's objects available for other users. For more information, see the Change Checkout User ID for Subset section.

The following table shows an example about the subset's objects have insufficient protection:

Task	To delete the Import View from Procedure Step C
What was scoped	Procedure Step C, default expansion and Delete protection.
Resulting subset	The resulting subset contains Procedure Step C but without Delete protection. The import view of Procedure Step C cannot be deleted.
What to do next	Check in subset or override checkout status. Determine why scoping for view deletion is incorrect. To delete an import view (entity view), you must scope the process or procedure step with full expansion and Delete protection and every process or procedure step that calls it, with expansion A and Modify protection. Run the Delete report to identify every process and procedure step that calls the view. To delete a view, your subset must contain all references to the view. The Objects Preventing Deletion report helps you define a subset that contains all references to the object. Use the Subset Definition Summary function to: Change the expansion of Procedure Step C to Full. Scope every process and procedure step that references the import view, with expansion A. Modify protection. Check out the subset again.

Task

To delete the Import View from Procedure
Step C

What was scoped

Procedure Step C, default expansion and Delete protection.

Resulting subset

The resulting subset contains Procedure Step C but without Delete protection.

The import view of Procedure Step C cannot be deleted.

What to do next

Check in subset or override checkout status.

Determine why scoping for view deletion is incorrect. To delete an import view (entity view), you must scope the process or procedure step with full expansion and Delete protection and every process or procedure step that calls it, with expansion A and Modify protection.

Run the Delete report to identify every process and procedure step that calls the view. To delete a view, your subset must contain all references to the view. The Objects Preventing Deletion report helps you define a subset that contains all references to the object.

Use the Subset Definition Summary function to:

Change the expansion of Procedure Step C to Full.

Scope every process and procedure step that references the import view, with expansion A.

Modify protection.

Check out the subset again.