SECTRLOG parameter: Difference between revisions
| Line 36: | Line 36: | ||
<tr><th align="right"><var>X'02' </var></th> | <tr><th align="right"><var>X'02' </var></th> | ||
<td>TSO applications (IODEVs 11, 29) </td></tr> | <td>[[TSO_terminal_interface|TSO applications]] (IODEVs 11, 29) </td></tr> | ||
<tr><th align="right"><var>X'04' </var></th> | <tr><th align="right"><var>X'04' </var></th> | ||
Revision as of 11:23, 25 May 2017
Security trusted login environment
Summary
- Default value
- X'00'
- Parameter type
- User
- Where set
- On user's first parameter line; not resettable
- Related products
- All
- Introduced
- Model 204 V3.2
Description
The CRAM thread applications for which logins are trusted
SECTRLOG defines which CRAM thread applications are allowed to log in with a trusted user ID. The CRAM threads that can have trusted login applications are:
IODEV 11 (CRFSCHNL)
IODEV 29 (CRIOCHNL)
IODEV 23 (IFAMCHNL)
SECTRLOG must be set on the first IODEV line for each trusted CRAM thread so it is picked up during the initialization of each CRAM channel. End users must follow the trusted login procedures described in the Security interfaces pages.
Valid settings of SECTRLOG are (except for X'00', options can be summed):
| Setting | Trusted login allowed for... |
|---|---|
| X'00' | Trusted login not allowed |
| X'01' | CICS applications (IODEVs 11, 23, 29); see the Note below. |
| X'02' | TSO applications (IODEVs 11, 29) |
| X'04' | Batch applications (IODEVs 23, 29) |
Note: TPROCESS applications cannot use the SECTRLOG option. Doing so results in the following message:
M204.1786: PROCESS TO PROCESS NOT SUPPORTED ON THIS THREAD
If your site wants to allow trusted logins from CICS full screen applications (IODEV 11) and BATCH2 jobs (IODEV 29) specify the following settings:
IODEV 11 line:
SECTRLOG=X'01'
IODEV 29 line:
SECTRLOG=X'04'