Conference specxn::decevent

	Gilles,


   The -l refers to the ext list fmgr$notify_cust0-3. It allows four
actions to be taken after a notification process has been triggered.
Each one if added to the external list can perform a different customer
defined operation via script. 


HTH


Keith

     Hi,
    
    
            I forgot to ask you, if now I want to have an entry in
    /dev/console when the DSE threshold is reached.
    
            I mean, customer wants to know through Polycenter Console
    Manager when a call was logged to DIGITAL, follwing the DSE threshold being
    reached
    
				Gilles.
    

	Hi Keith,


	Thanks for your answer in .1, but

	when does this script is triggered ??


	- I want trigger a script aftafter DSE threshold is reached. See .0 and
.2.

	It would be nice, if you could give me a simple example


	Also, I repeat again this important question.

	Is it possible to increment an error counter to see if the script 
triggers correctly ??


	Thanks for clarification



			Gilles.

	Gilles,


    when the ad ext -l fmgr_notify_cust0 -f it-triggered command is performed.
The script it-triggered will be invoked when the a device crosses the threshold.
What the script does is up to the customer. The customer could also define  

	Gilles,

  To continue, the Customer can define a different operation for one of the
other three notification settings. 


HTH

Keith

    And what about the possibility to increment customer and DSE counters
    virtually to see if it works correctly ?
    
    				Gilles.

	Set the proper setting and run the test auto string.

	dia>test auto -f PADF_OSF_ON.ZPD /var/adm/binery.errorlog
	
	If there is anything worth reporting in the error log you should get
trigger. 


Keith

Hi,

>	dia>test auto -f PADF_OSF_ON.ZPD /var/adm/binery.errorlog
	
Where is PADF_OSF_ON.ZPD?
I couldn't find out such file on UNIX with DECevent V2.4.

Jun

	My apologies, It appears that the PADF_OSF_ON.ZPD file is being deleted
after the installation on Unix. This shortcoming will be rectified. I will put a
copy of the file in the standard ftp public areas for on PINKFT.cxo.dec.com  


Keith

	I put a copy of PADF_OSF_ON.ZPD and PADF_OSF_OFF.ZPD  in
/public/ftp/pub/DECevent on pinkft.cxo.dec.com.

Cheer's


Keith

Thanks Keith,

Dou you have plan to provide these files in future release?
On DECevent for OpenVMS, TEST_AUTO.SYS and VMS_PADF_ON.ZPD are resided in
DIA$MGR directory.

Jun

	Jun-san,


   We had planned to leave the zpd files on the system. I recently found out
the script was changed to delete the files. I will recetify that situation. The
.sys file is the error log used to run the IVP. 

  
HTH

Keith

    	Ansd thanks to comment this functionnality in the next release
    notes for UNIX
    
    
    
    	Gilles.

    	As it is written in .4, I tried to do 
    
    ad ext -l fmgr_notify_cust0 -f /usr/tmp/essai
    
    and the result is:
    
    _DIAGNOSE-FAT: An error occurred while executing a command ruleset
    _DIAGNOSE-FAT: Add external, syntax error - Invalid list '
    fmgr_notify_cust0 '
    
    
    
    So this command doesn't work.
    
    If I do 
    
    dia> ad ext -l customer -f /usr/tmp/essai , it works
    
	So, how to use FMGR$NOTIFY_CUST0-3ist ????????
    
    
    
    Secondly, when I do:
    
    dia> set thr -t UNKN_IOS -s hard -c 1
    dia> set thr -t UNKN_IOS -s soft -c 1
    dia> set thr -t UNKN_CPU -s hard -c 1
    dia> set thr -t UNKN_CPU -s soft -c 1
    
    .....to setup customer threshold,..... and I do
                                                             
    
    dia> test auto -f PADF_OSF_ON.ZPD /var/adm/binary.errlog
    
    I have 
    
    CKNL:
     str1 = <Startup:>
     str2 = <Time=<19970115110733>>
     int1 = 0x<0>
     int2 = 0x<0>
    CKNL:
     str1 = <Calling NOTIFY:>
     str2 = <Type=<UNKN_CPU>>
     int1 = 0x<0>
     int2 = 0x<0>
    CKNL:
     str1 = <Calling NOTIFY:>
     str2 = <Name=<suprix>>
     int1 = 0x<0>
     int2 = 0x<0>
    CKNL:
     str1 = <Calling NOTIFY:>
     str2 = <ID=<suprix>>
     int1 = 0x<0>
     int2 = 0x<0>
    CKNL:
     str1 = <Calling NOTIFY:>
     str2 = <Theory=<Z.2.1>>
     int1 = 0x<0>
     int2 = 0x<0>
    CKNL:
     str1 = <Normal shutdown:>
     str2 = <Time=<19970509102959>>
     int1 = 0x<0>
     int2 = 0x<0>
    ambats... User unknown
    _DIAGNOSE-WAR: Send mail message failed
    _DIAGNOSE-ERR: No such file or directory,
      from not_eng__send_mail_msg in thread 35
    _DIAGNOSE-ERR: Failed to close pipe to mail transport
    _DIAGNOSE-ERR: No such file or directory,
      from svc_mai__send_message in thread 35
    sh: FMGR: not found
    sh: FMGR: not found
    sh: FMGR: not found
    sh: FMGR: not found
    sh: FMGR: not found
    sh: FMGR: not found
    sh: FMGR: not found
    sh: FMGR: not found
    
    
    What are the meaning of those output ??
    
    After when I do 
    
    dia> shw thr
    
    I have
    
    
                        -- Hard ---     -- Soft ---     -- Info ---     --
    Media --
     Device             Cnt DSE Cus     Cnt DSE Cus     Cnt DSE Cus     Cnt
    DSE Cus
    
    ==============================================================================
     suprix             1   1   1       0   0   1       0   0   0       0  
    0   0
     UNKN_UNK           0   5   1       0   0   1       0   0   0       0  
    0   0
     UNKN_IOS           0   1   1       0   0   1       0   0   0       0  
    0   0
     UNKN_CPU           0   1   1       0   0   1       0   0   0       0  
    0   0
     AlphaSrv_1000A_EV450   1   0       0   1   0       0   1   0       0  
    1   0
    
    
    I have a new device name which is suprix and which corerrespond to my
    machine hostname. Effectively, I see the counter to 1, and my script
    /usr/tmp/essai is triggered.
    
    
    So, what conclusion can we have with those results ?? What this device 
    suprix correspond too ???
    
    
    
    	Please, give more clarifications about what is doing 
     PADF_OSF_ON.ZPD file.
    
    	As it is undocumented, we can't guess if triggerinfg function
    correctly
    
    
    
    	Thanks for clarification, please.......
    
    
    
    		Gilles.

	Giles,


 PADF_OSF_ON.ZPD does nothing but change the date of the error log entry in the
error log file you specify on the command line to the current date and time. We
are not going to document it because we do not want customers using it. These
commands are there specifically for the engineers use to test the automatic
process.


  After some review I find I've lead you down a incorrect path. We have two
hidden commands with in DECevent know as sets and seti. These commands will
set string or set integer and are used to manipulate the settings knl.


   To get the external to fire perform the following 

dia-int

dia> sets FMGR_NOTIFY_CUST0 /usr/users/poussard/scriptname
dia> sav sett 

When a trigger occurs the script will run. I would ask that you remove whatever
you added to the ext list and use the sets command to get the external
notification.

	Also after looking at the output of your note I see another problem with
the system. Please remove use ambats from the mail list. rm usr -u ambats

For a reason unknown to us the mail knl is getting loaded with ambats as a user
before we ship the kit. We are resolving the issue. ambats is a user account I
used for testing when building the test scripts for decevent. 


Keith

	Gilles,


  The more tests I run the more we uncover. Disregard the sets and seti
commands I spoke of earlier. The fail on unix because of the $ sign in the 
name fmgr$notify_cust0. Unix expects a environment variable to follow a $ sign. 

  You should be able to do the ad ext -l customer -f scriptname and
get it to trigger. You can test it by performing a tst -e customer
and see if the script run.  a simple echo test script will do for a start.

Cheer's

Keith