Conference csc32::consolemanager

902.0. "DIALOG results in %SYSTEM-F-DEVNOTMOUNT" by 54625::WILLEMSG (Geert Willems MCS-Belgium) Wed Aug 02 1995 12:06

	Hi,

	PCM V1.6-100,OpenVMS VAX V6.1.
	Customer upgraded to PCM V1.6 SSB kit(no ECO kit).
	The DIALOG that worked fine under PCM V1.5a for a 
	non privileged user doesn't work anymore.
	He receives :%SYSTEM-F-DEVNOTMOUNT, device is not mounted
	
	If he gives the user SYSPRV it works fine.
	Is this a known problem with PCM V1.6 ? This %X1000007C
	can not be found in the list on page 5-11,5-12 in the PCM
	manual.

	Any help/feedback is welcome.

	Thanks in advance & Rgds,

	Geert




A1> ty vcs01::"0=boot_eln04"
$
$ Eln_system = "ELN04"
$
$ on warning then goto abort
$
$ !
$ !     *** Check time ***
$ !
$ time = f$cvtime("","absolute","hour") + f$cvtime("","absolute","minute")
$
$ if time .GT. "0001"
$    then
$ !     *** Boot ELN with script ***
$
$       Console dialog/file=boot_eln.txt ELN04
POLYCENTER Console Manager
Dialog facility version V1.6-100
Copyright (c) 1995 Digital Equipment Corporation. All Rights Reserved

$Abort:
$ code = $status
$ write sys$output code
%X1000007C
$ write sys$output f$message("%X1000007C")
%SYSTEM-F-DEVNOTMOUNT, device is not mounted
$ write sys$output "BOOT-E-PROBLEM, Problem occured while Booting ELN04"
BOOT-E-PROBLEM, Problem occured while Booting ELN04
$ exit

******************************************************************************

PCM Edit> show user atstest
Full or Brief listing? [f=full, b=brief] (b): f
Output file (SYS$OUTPUT):
User Name       = ATSTEST
    Information = Account used to boot TEST eln systems
    May not startup Console Manager from the C3 interface
    May not reconfigure Console Manager
    May not shutdown Console Manager
    May not edit configuration database
    May unlock consoles
    May transmit break signal
    May not perform archive
    May not exit C3 interface
    May not edit C3 interface
    System Access: (2)
      ELN03         ELN03
      ELN04
    Group Access: (0)

******************************************************************************

$ !
$ !     *** Boot ELN system with script ***
$ set ver
$ if f$getjpi("","mode") .eqs. "NETWORK" then define sys$output sys$net
$
$ Eln_system = "ELN04"
$
$ on warning then goto abort
$
$ !
$ !     *** Check time ***
$ !
$ time = f$cvtime("","absolute","hour") + f$cvtime("","absolute","minute")
$
$ if time .GT. "0001"
$    then
$ !     *** Boot ELN with script ***
$
$       Console dialog/file=boot_eln.txt 'Eln_system'
$       write sys$output "BOOT-S-SCRIPT, ''Eln_system' bootscript done."
$    else
$       write sys$output "BOOT-E-TOOEARLY, Booting ''Eln_system' Only possible a
fter 17:10"
$    endif
$
$ exit
$
$Abort:
$ code = $status
$ write sys$output code
$ write sys$output f$message("''code'")
$ write sys$output "BOOT-E-PROBLEM, Problem occured while Booting ''Eln_system'"
$ exit

    
    
    	HI,
    
    	What are the privileges needed to do a CONSOLE DIALOG ?
    	If a none privileged user (NETMBX,TMPMBX) tries a CONSOLE DIALOG
    	he doesn't receive an error, but the /file=xxx part isn't executed.
    	
    For instance:
    $ console dialog/file=CONSOLE_DIALOG.TEST/noquiet brssws
    POLYCENTER Console Manager
    Dialog facility version V1.6-100
    Copyright (c) 1995 Digital Equipment Corporation. All Rights Reserved
    $
    
    You see, no error and the CONSOLE_DIALOG.TEST is not executed.
    If you test the $status, you will receive DEVNOTMOUNT
    $ sh symb $status
      $STATUS == "%X1000007C"
    $ write sys$output f$message(%X1000007C)
    %SYSTEM-F-DEVNOTMOUNT, device is not mounted
    
    So, if this worked under PCM V1.5 for a non priviliged user, than 
    this means that there is a bug with PCM V1.6 or was there a security
    hole with PCM V1,5 DIALOG ?
    What privileges are needed to do a DIALOG ? Doesn't find it in the
    manual. With SYSPRV it workes fine, but that is no privilege to give
    a non privileged user.
    
    	Any help/feedback is welcome.
    
    	Rgds,
    
    	Geert
     

    
    
    	Do I have to raise an IPMT for this ? Is this a bug ?

    Geert,
      This is not really a bug in the code nor is that message a VMS error 
    code. The value you are getting means:
    
    "Dialog could not check the status of the serviced system."
    
    These return status fields may be seen by doing a
    
    HELP CONS DIAL ERROR
    
    from DCL.
    
    Modify the CONSOLE$STARTUP procedure so that it installs the image
    CONSOLE$DIALOG.EXE with SYSPRV as right now it only has SYSLCK. I will
    have to check the code to see why it needs SYSPRV. I would bet it has
    something to do with the global statistics section. Adding SYSPRV is
    safe to do and it *will not* compromise the security of the customers
    system.
    
    
    Regards,
       Dan