All parameters are optional, but at least one parameter must be specified for this tag to be useful.
A change to the timeout takes effect as soon as either timeout parameter is parsed and the timer is restarted at that point.
It is strongly recommended that the inactivity and service timeout intervals are kept as short as possible. Setting the session
inactivity limit to the maximum will keep sessions from automatically terminating when browser sessions are abandoned; this
can result in a large number of orphaned BIS sessions that will not be cleaned up for over a week. It is better to set the
minutes to keep the session active only while the browser window remains open.
Setting the service timeout interval too high can also have detrimental effects if a service programs unexpectedly runs away.
Such a program can use 100% of the available CPU, preventing any other programs from starting or running effectively. The
default setting of 30 seconds will terminate any run-away program within this reasonable amount of time.
The session scope determines if pages served from subdirectories of the session base directory are executed in new sessions.
For example, if this page created the initial session:
SessionParms(Scope=All) is in effect, the subordinate page will be served from the same session as the initial page. However, if
SessionParms(Scope=Isolate) is in effect, a new session will be created for the subordinate page.