[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | FOCUS, from INFORMATION BUILDERS |
|
| Moderator: | ZAYIUS::BROUILLETTE |
|
| Created: | Thu Feb 19 1987 |
| Last Modified: | Mon May 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 615 |
| Total number of notes: | 1779 |
611.0. "FOCUS and captive account" by BIS1::DURY (Alain Dury _ Brussels) Tue Aug 01 1995 04:29
We have some applications using FOCUS procedure in CAPTIVE mode.
In VMS 5.5-2 no problem, but in VMS 6.1 we get:
FOCUS 6.5.3 (C)Copyright 1993 Information Builders Inc.
Licensed for Digital Internal Administrative Use (A87110072)
>>>>>>>>>>>>>>>>>>%CLI-E-CAPTSPAWN, captive account - SPAWN command not allowed
Description: The VMS (under FOCUS) command is not anymore allowed.
This requires the use of LIB$SPAWN which is not permitted for
CAPTIVE accounts under OpenVMS 6.1, unless special flags are
set by the calling program.
This is more or less to be expected from pg 45 ch 2.5.2.22.6, that
warns that starting V6 in captive accounts no lib$spawn is allowed.
From lib$spawn doc:
6 TRUSTED If this bit is set, it indicates a SPAWN command
on behalf of the application. If this bit is
not set, it indicates that the SPAWN command
originates from user. SPAWN commands
originating
from users are disallowed in captive accounts
(DCL).
A workaround is removing the captive flag from the accounts but is not the
best solution. For security reason we wil keep the captive account mode.
Do you have a solution?
Alain.
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 611.1 | you may not have a choice | SHIPS::CARSE_D | | Tue Aug 01 1995 13:37 | 13 |
|
1. Patch FOCUS.EXE to set the relevant bit (don't as me how!)
2. Contact IBI and request a change in their code (this will takes
ages to ripple through)
3. Write a jacket login command procedure for the users and set their
accounts to RESTRICTED rather than CAPTIVE.
I know which I'd rather do.
Cheers,
David
|