When data set profile changes take effect

If a user is currently using a data set, changing the data set profile protecting the data set might not affect the user's current access until that user logs on again.

The change affects the user's access immediately in the following cases:

If the user is not logged on. You can check to see if a user is logged on with the TSO STATUS command:
```
STATUS userid
```
If the user is logged on, the system displays a message indicating that a job with the letters TSU in it is executing.
If the user is logged on and has not yet opened the data set or a data set protected by the same generic profile (for example, by browsing or editing).

If the user is logged on and has opened the data set, and you change his access, two situations could occur:

If the profile is a discrete profile, the user's access changes after closing the data set.
If the profile is a generic profile, the user's access changes after one of the following events occurs:
- The user issues the LISTDSD command as follows:
```
LISTDSD DATASET(data-set-protected-by-the-profile) GENERIC
```
  This places a fresh copy of the profile in the user's address space.
- A SETROPTS GENERIC(DATASET) REFRESH is issued on the system the user is logged on to.
  Note: This command cannot be issued by a general user. It can be issued only by someone with the SPECIAL, OPERATIONS, or AUDITOR attribute.
- The user references more than four data sets with different high-level qualifiers, and the data sets are protected by generic profiles.
- The user logs off and then logs back on.