Conference share::zap

71.0. "Customizations - clear screen, file logical" by POLAR::HUTCH () Sat Mar 10 1990 10:24

I have just completed a preliminary review of ZAP 4.1. For several releases now
I have been customizing ZAP to solve two problems for me. I mention them here
for consideration of inclusion in a future version.


Customization #1	Disable clear screen in line mode

I run ZAP in line mode. The reason I like line mode is that it makes the reason
for disconnect very obvious to the user. When the user returns to their terminal
after a disconnect, what remains on the screen are the idle process warnings.
The problem I have with the standard ZAP is that even in line mode, a clear
screen is sent to the terminal just before stopping the idle process. This final
clear screen basically defeats the reason why I prefer line mode.

This is the section of ZAP.PAS code I modify to get the functionality I want

               send_message then
               status := $brkthru ( msgbuf := message,
                                    sendto := pid_ptr^.terminal,
                                    sndtyp := brk$c_device,
                                    iosb := status_block,
                                    flags := 24,
                                    timout := 15 );

In the distributed source, the flags are 280. When flags are set to 24 then
the $brkthru system service does not perform the clear screen function.

I have found that this modification has also proved helpful for those lat users
that switch back to an old disconnected session because the 'logged out' message
will still get displayed.


Customization #2	Logical for exception filename

I have need for 2 different ZAP.DAT files. I use one for the CI members of
a cluster and the other for all the satellites. I should mention that I have
installed ZAP on my cluster such that all the files resides in a common
directory. Each node writes to a zap_'nodename'.log. I configure the satellites
exception file mostly for DECwindows usage and have set a very generous 'Global
for all other users' exception period. The 'Global for all other users'
exception period for the CI cluster members is closer to the default of 20
minutes.

My modification involves changing the 3 references to ZAP$DIR:ZAP.DAT in
ZAP.PAS to use a filename logical. I name my logical ZAP$EXCEPTION_FILE. By
using this logical I can simply reassign it to the a different exception file
for satellites (which I name zap_satellite.dat)

I include the following commands in my zap$startup.com

$ NODE = F$GETSYI("NODENAME")
$ SATELLITE := FALSE
$ ROOT = F$TRNLNM("SYS$TOPSYS") - "SYS"
$ IF ROOT .GE. 10 THEN SATELLITE := TRUE
$ IF SATELLITE
$  THEN ASSIGN/SYSTEM/NOLOG ZAP$DIR:ZAP_SATELLITE.DAT	ZAP$EXCEPTION_FILE
$  ELSE ASSIGN/SYSTEM/NOLOG ZAP$DIR:ZAP.DAT		ZAP$EXCEPTION_FILE
$ ENDIF


Mike

    Mike,
    
    	could you please tell me how to obtain  the sources for ZAP.
    Greg

    Sources are not available for ZAP.