Managing Sessions
The WebDocs security model you set up works statically, not dynamically. The first time a user logs in, WebDocs looks at the user's profile and groups to find all that user's permissions and creates a static session file for that user. The next time the user logs in, WebDocs looks for an existing static session file first and, if one exists, uses the information in that file. This technique enhances WebDocs' performance and speeds up the website.
However, if a user's permissions change, you need a way to delete the existing session so that the new permissions take effect. There are three options for managing this periodic purging:
Option | Pros | Cons | How to do it |
Each time you change a user or group's permissions, delete that user or group's session manually. |
|
|
After you change a user or group's permissions:
|
Use a job to regularly delete all sessions. |
|
|
|
Run a monitor that regularly deletes all inactive sessions. |
|
|
Use the DOCSESPRG command to set the timing for the monitor. Note: This monitor calls the DOCPRGSES command. |
Automatically delete a user's session every time they log out. |
|
|
Set the DOCENDSESB data area to *YES. |
See also:
- Appendix A: Reference of Relevant Data Areas for a reference of session data areas.
- Appendix C: Reference of Relevant Commandsfor a reference of session commands.