.-LIMRES--=--NO------. >>-+-+--------------------+-+---------------------------------->< | | .-NO--. | | | '-LIMRES--=--+-----+-' | | '-YES-' | | .-LIMRES--=--NO-. (1) | '-+---------------+------' '-LIMRES--=--NO-'
Notes:
- LIMRES=NO is the only valid value if the TRLE operand is coded.
| statements: | PU |
| dependencies: | LIMQSINT; LU 6.2 only; PUTYPE=1 or 2 |
Specifies whether this physical unit is to be treated as a limited resource. A limited resource allows you to limit the use of some network connections. It also causes any sessions that traverse the resource to be deactivated if no conversation is active. A session can also be deactivated if the time limit you specify for the LIMQSINT operand on the APPL definition statement expires.
This operand applies only to LU 6.2 conversations and PU types 1 and 2.
Note: If the TRLE operand is coded, LIMRES must be specified
as NO or allowed to default. See TRLE for more information.
If you do not code a value for LIMRES, resources are not considered to be limited resources. Furthermore, sessions will remain active even after all conversations have ended.
You can also use LIMRES in conjunction with the LIMINTCP start
option to specify the interval to retain a free session using a limited
resource for some network management flows (excluding flows using
the APPN control point sessions or dependent LU server sessions).
If you do not code a value for the LIMINTCP start option, resources
are not considered to be limited resources, and the sessions will
remain active even after all conversations have ended.
- LIMRES=NO
- Specifies that this physical unit is not to be treated as a limited resource.
- LIMRES=YES
- Specifies that this physical unit is to be treated as a limited resource.