[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

379.0. "Pseudo connection to PCM system itself" by EEMELI::OJUSSILA (Olli Jussila, OMS Finland) Tue Aug 30 1994 11:19

    
    
    Is it possible to run command procedure/shell scripts as a command
    for pseudo terminal? 
    
    If VMS is used, is the command "@SYS$MANAGER:TEST.COM"
    Do I need to redefine sys$command, sys$input inside command procedure.
    
    I would like to create pseudo terminal connection on same
    system where PCM is running.
    
    PCM/VMS customer is running DECamds which sends events to OPCOM.
    We would like to create system which only needs to receive
    OPCOM messages. Inside command prosedure reply/enable.
    
    
    PCM/ULTRIX customer is planning to monitor AS400. They have TCP/IP
    (FTP) between PCM system and AS400. They don't have
    TWINAX to ASCII converter. Our plan is to use history log of AS400.
    AS400 extracts in every 5 minutes latest events from history
    log and copies this ascii file with ftp to PCM Ultrix system
    On PCM we should have Pseudo connection to script which
    use cat command to type as400 alarms to PCM then
    PCM filters are used to pick up critical AS400 events
    
    
    	Script would be like this?
    
    	While true
    	do
    	
    		cat < /usr/users/as400/alarms/alarm.log
    	        rm /usr/users/as400/alarms/alarm.log
    		sleep 240 
        done
    
    
    what do you thing?  This would increase PCM sell. 
    Or do you have so other ideas to implement this?
    
T.RTitleUserPersonal
Name
DateLines
379.1OPG::PHILIPAnd through the square window...Tue Aug 30 1994 11:3319
>>    Is it possible to run command procedure/shell scripts as a command
>>    for pseudo terminal? 

  Yes
    
>>    If VMS is used, is the command "@SYS$MANAGER:TEST.COM"
>>    Do I need to redefine sys$command, sys$input inside command procedure.

  No

  As for the other stuff, it looks OK to me, you have to support your
  solution, so use whatever mechanism you think best. One problem though
  with your approach is that you could potentially wait 5 minutes to be
  told about a serious problem!

Cheers,
Phil

379.2resultsEEMELI::OJUSSILAOlli Jussila, OMS FinlandTue Aug 30 1994 14:0641
    
>  As for the other stuff, it looks OK to me, you have to support your
>  solution, so use whatever mechanism you think best. One problem though
>  with your approach is that you could potentially wait 5 minutes to be
>  told about a serious problem!
    
    I tested this. It works. 5 minutes is not so long time if you compare
    it to current situation where they will see events after they
    manually check main operators message queue. Critical message could
    wait over a night or even over the weekend.
    
    About VMS.
    
    I found from CONSOLE$TEMP temporary procedure which runs 
    command of Pseudo device. It helps to understand how
    pseudo devices works. If command is a command procedure and
    input is needed then define/user sys$input sys$command is
    needed.

DELPRC-> ty CONSOLE$ROOT:[TEMP]_DELPRC$FTA78.COM;1
$   CMGR_VERIFY = F$VERIFY(0)
$   Set NoOn
$   Set NoControl=(Y,T)
$   LOGOUT :== LOGOUT
$ CM_PseudoStart:
$   DEFINE /USER SYS$INPUT SYS$COMMAND
$   @SYS$SYSTOOLS:PCM.COM
$   If .NOT. ($STATUS .AND. 1) Then Goto CM_PseudoError
$   Goto CM_PseudoStart
$ CM_PseudoError:
$   CMGR_VERIFY = F$VERIFY(CMGR_VERIFY)
$   LOGOUT
----------------------------------------------
    

	If process which is running this process is stopped
	or logout is executes next connect will run loginout
	process.

	-Olli

379.3One way to use PCM to Monitor AS400'sEEMELI::OJUSSILAOlli Jussila, OMS FinlandFri Sep 09 1994 20:2531
	Just for your information. 
	This customer now uses PCM V1.5 on Ultrix to monitor
	2* DEC3000 OSF/1   (DECserver90m)
	1* DECsystem5240   (DECserver90m)
	2* UNISYS6???      (DECserver90m)
	1* SCO/UNIX	   (DECserver90m)
	3* AS400	   (pseudo device)
	1* DECsystem5200   (pseudo device)

	eXcursion for X-display, PSW on ULTRIX and OSF/1

	Only one AS400 has TCP/IP. This AS400 collects system messages
	(history log) from two other systems. It makes EBSDIC to ASCII 		
        conversions
	and sends three node specific files to PCM node.
	If this AS400 hasn't got files from other AS400's (SNA connection)
	it send file with text 
 	AS400DOWN: AS400 node XXX has't send new alarms

	On PCM there is three Pseudo devices with special scripts
	Which in wait loop cats files send by AS400 (TCP/IP) and there has
	been defined AS400 specific events defined. If script dosen't find
	new alarm file after second try it just echos
	AS400DOWN: AS400 node xxxx hasn't send alarms of AS400 yyyy

	Even one AS400 is SF200 and two AS400 are VAX780 icons on Console C3
	screen it looks very nice when AS400 (VAX780) become RED when
	AS400 finds write locked tape.

	-Olli
379.4Create a new AS400 iconZENDIA::DBIGELOWInnovate, Integrate, EvaporateFri Sep 09 1994 22:3128
    Olli,
    
    If you have some scan definitions you'd like to contribute/share, 
    please post them here. You can use the export function in the editor to
    generate an ascii copy of the database.
    
	>Even one AS400 is SF200 and two AS400 are VAX780 icons on Console C3
	>screen it looks very nice when AS400 (VAX780) become RED when
	>AS400 finds write locked tape.

    Why not just create a new icon for the AS400? It is very easy. 
    The following steps should do it.
    
    # cp /usr/var/kits/console/SF_200.xbm /usr/var/kits/console/AS400.xbm
    # dxpaint /usr/var/kits/console/AS400.xbm
    .
    . Make your cahnges using the paint program. Turn 'Zoom on'.
    . You might have to adjust the picture size as well
    
    After you exit, you can use the PCM editor to change the default 
    icon for that system to the one you just created.
    Don't forget to 'reconfigure'
    
    cheers,
    
       dave