1. jumpmanager_2.1.25.4.zip Driver
2. popup.txt File Contents

popup.txt Driver File Contents (jumpmanager_2.1.25.4.zip)

                Network (popup) messages in JUMP Manager

  JUMP Manager is equiped with various alarm handling facilities. One of them
is the possibility to send network (popup) messages initiated by alarm 
condition.

  Network messages are commonly used in Windows environment, but they are found
also on other platforms like Unix, Linux or OpenVMS. Actual sending of network
message is of course platform dependent, but the principle is always the same:
JUMP manager starts for that script called message, which can be found in the
platform dependent directory - for Win95/98 in directory 
[JM_istalled\scripts\win], for WinNT in [JM_istalled\scripts\nt], for Win 2000
in [JM_istalled\scripts\win2000]. In Windows environment it always has extension
.bat.
 Let us look at say Win2000 message.bat and it's structure:

@echo off
REM 2 parameters are sent from the JUMP Manager Server program
REM 1. param - message
REM 2. param - user
net send %2 %1

The structure is actualy very simple, using two parameters passed from JUMP
Manager - user ('target') of the message and message itself. The problem is,
that Microsoft's "net send" command is very flexible and behaves differently
in different environments. Problem is, that Windows networking ranges from
essentialy peer to peer networking to users beeing validated by domain controler
(server). In these different networking situations also "net send" behaves
differently. That is why we cannot deliver righ solution for every networking
situation. Therefore WE EXPECT THE USER TO MODIFY our generic batch file to
suit his networking situation. What we mean by this is two steps:
 
 1. User finds out on the command line what type of 'net send' command
    best suits his actual needs (sending message to all user's, workgroup
    etc).
 2. User then modifies message.bat to reflect his previous findings so that
    messages are sent to users/groups that he wants.

Please have a look at the help for 'net send' command. You will understand, 
that it has fair amount of switches and experimentaly you can find that it
behaves quite differently in different networking scenarios. That is why we
cannot provide universal solution for every situation but we have to rely
on user's intervention to adjust 'message.bat' to his needs.

 Please note, that for Win95/98 environment 'net send' command is not even
present in the basic networking software of Microsoft. That is why we provide
utility sendpop.exe that has similar function at the 'net send' command on NT
or Win 2000. 

  Please refer also to 'Messaging Manual' that is part of JUMP Manager 
distribution.