[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference csc32::consolemanager

Title:	POLYCENTER Console Manager
Notice:	Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS:
Moderator:	CSC32::BUTTERWORTH

Created:	Thu Aug 06 1992
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	1541
Total number of notes:	6564

445.0. "Automatic Startup" by OHFSS1::COMFORT () Fri Oct 21 1994 16:40

    A customer has asked about a number of features that were in VCS but
    were missing from the earlier versions of PCM.  Using this notes file,
    I have resolved all of them but one.  According to a comparison sheet
    he faxed me, VCS supported "Automatic local and remote C3 startup" but
    PCM 1.0 did not.
    
    Would someone please comment on whether this capability is in 1.5?
    
    Thanks in advance.
    
    Bob C.

T.R Title User Personal
Name Date Lines

445.1 OPG::PHILIP And through the square window... Fri Oct 21 1994 17:26 19

T.R	Title	User	Personal Name	Date	Lines
445.1		OPG::PHILIP	And through the square window...	`Fri Oct 21 1994 17:26`	19
	Bob, This IS NOT in V1.5, PCM's C3 behaves differently than that of VCS, it works on the basis that it only displays those systems the user has access to in the PCM database. Now, after much debate, we decided that to automatically start a C3 would breached our own security measures (we have no way of knowing if the user logged in on a particular workstation is the one who should use that C3 invokation). Now, if the user is REALLY sure they want to do this then they can create themselves a simple batch job which would run under an individuals username and display a C3. This batchj job could be submitted as part of the system startup after PCM has started. Hope this helps. Cheers, Phil

Bob,

  This IS NOT in V1.5, PCM's C3 behaves differently than that
  of VCS, it works on the basis that it only displays those
  systems the user has access to in the PCM database. Now, after
  much debate, we decided that to automatically start a C3 would
  breached our own security measures (we have no way of knowing
  if the user logged in on a particular workstation is the one
  who should use that C3 invokation).

  Now, if the user is REALLY sure they want to do this then they
  can create themselves a simple batch job which would run under
  an individuals username and display a C3. This batchj job could
  be submitted as part of the system startup after PCM has started.

  Hope this helps.

Cheers,
Phil