WEBOPT parameter: Difference between revisions
No edit summary |
|||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 3: | Line 3: | ||
<dl> | <dl> | ||
<dt>Default value | <dt>Default value | ||
<dd>0 | <dd>3, as of Model 204 V7.5 (formerly 0), if a security interface is active, otherwise it remains at 0. | ||
<dt>Parameter type | <dt>Parameter type | ||
<dd>System | <dd>System | ||
| Line 13: | Line 13: | ||
<dd>Before <var class="product">Sirius Mods</var> 6.5 | <dd>Before <var class="product">Sirius Mods</var> 6.5 | ||
</dl> | </dl> | ||
==Description== | ==Description== | ||
The WEBOPT parameter is a standard Model 204 bitmask-type parameter introduced in | The <var>WEBOPT</var> parameter is a standard Model 204 bitmask-type parameter introduced in | ||
Sirius Mods version 6.5. The X'01' setting causes RACF calls to be performed in a | Sirius Mods version 6.5. The X'01' setting causes RACF calls to be performed in a | ||
special RACF subtask. | special RACF subtask. | ||
| Line 20: | Line 21: | ||
In cases where Janus Web Server is deployed and RACF handles login validation, the | In cases where Janus Web Server is deployed and RACF handles login validation, the | ||
RACF call load for login-protected web pages can get very high. Since these calls often | RACF call load for login-protected web pages can get very high. Since these calls often | ||
involve synchronous I/Os that stop the Model 204 | involve synchronous I/Os that stop the Model 204 maintask, they are generally not very | ||
good for Model 204 performance. However, if you set the WEBOPT system parameter | good for Model 204 performance. However, if you set the <var>WEBOPT</var> system parameter | ||
to X'01', these calls are done in a subtask, reducing their impact on Online performance | to X'01', these calls are done in a subtask, reducing their impact on Online performance | ||
dramatically. | dramatically. | ||
| Line 28: | Line 29: | ||
<dd>RACF Calls are performed in a special RACF subtask. | <dd>RACF Calls are performed in a special RACF subtask. | ||
<dt>X'02' | <dt>X'02' | ||
<dd>Introduced with Sirius Mods 7.9, this bit directs that Model 204 set the RACF Control Group Name as the APPL parameter for RACF verify calls. Note: | <dd>Introduced with Sirius Mods 7.9, this bit directs that Model 204 set the RACF Control Group Name as the APPL parameter for RACF verify calls. | ||
<p class="note"><b>Note:</b> This setting only takes effect if the X'01' bit is also set.</p> | |||
<dt>X'10' | |||
<dd>[[Daemon class#Janus_Web_API_methods|Transactional daemon threads]] can access web data owned by their ancestor (usually parent) threads. | |||
</dl> | </dl> | ||
When WEBOPT includes the X'03' bits, the RACF Control Group name | When <var>WEBOPT</var> includes the X'03' bits (the default as of Model 204 V7.5), the RACF Control Group name is set as the SNA APPL parameter. | ||
This enables both the generation of RACF Pass Tickets and the use of extended APPLDATA('RACF-INITSTATS(DAILY)') to limit history updates for RACF logins. | This enables both the generation of RACF Pass Tickets and the use of extended APPLDATA('RACF-INITSTATS(DAILY)') to limit history updates for RACF logins. | ||
The APPL name is set to the value of the Model 204 RACF Control Group name, which can be found by issuing the following command: | The APPL name is set to the value of the Model 204 RACF Control Group name, which can be found by issuing the following command: | ||
Latest revision as of 14:20, 9 July 2020
Miscellaneous Janus Web options
Summary
- Default value
- 3, as of Model 204 V7.5 (formerly 0), if a security interface is active, otherwise it remains at 0.
- Parameter type
- System
- Where set
- User 0 resettable
- Related products
- Janus Web Server
- Introduced
- Before Sirius Mods 6.5
Description
The WEBOPT parameter is a standard Model 204 bitmask-type parameter introduced in Sirius Mods version 6.5. The X'01' setting causes RACF calls to be performed in a special RACF subtask.
In cases where Janus Web Server is deployed and RACF handles login validation, the RACF call load for login-protected web pages can get very high. Since these calls often involve synchronous I/Os that stop the Model 204 maintask, they are generally not very good for Model 204 performance. However, if you set the WEBOPT system parameter to X'01', these calls are done in a subtask, reducing their impact on Online performance dramatically.
- X'01'
- RACF Calls are performed in a special RACF subtask.
- X'02'
- Introduced with Sirius Mods 7.9, this bit directs that Model 204 set the RACF Control Group Name as the APPL parameter for RACF verify calls.
Note: This setting only takes effect if the X'01' bit is also set.
- X'10'
- Transactional daemon threads can access web data owned by their ancestor (usually parent) threads.
When WEBOPT includes the X'03' bits (the default as of Model 204 V7.5), the RACF Control Group name is set as the SNA APPL parameter. This enables both the generation of RACF Pass Tickets and the use of extended APPLDATA('RACF-INITSTATS(DAILY)') to limit history updates for RACF logins. The APPL name is set to the value of the Model 204 RACF Control Group name, which can be found by issuing the following command:
AUTHCTL VIEW