| Hi Sunil!
Yes, that is all just fine.
> The customer will not go to TeamLinks right away don't ask me why, they
> just won't.
>
You're right, this sounds odd. Need to retrain twice. I suppose it
is two small bites to swallow instead of one large...
> My thoughts are:
>
> 1. Startup PATHWORKS before ALL-IN-1 IOS so that the NETBIOS process
> is running.
Yes, you need to do this in case mail comes in during startup.
If you start them the other way round, you might loose some
broadcasts. The actual A1V30START doesn't care about NETBIOS.
Assuming you are running under Windows you need step 4:
4. Run WINRCV to get broadcasts under Windows (maybe put it in
your startup group).
Make sure you run the c:\teamlink versions of RCV and WINRCV and
not the ones that come with PATHWORKS. Also note that
c:\decnet\startnet.bat loads the PATHWORKS RCV; loading the
TeamLinks one afterwards has no effect.
I think we decided not to document OA$PC_NOTIFY.DAT this time as
it is not accessible from any menu option, but I'll attach a chunk
of an ICO which describes it.
> I know that MUPA provides the facility to
> enable broadcast messages to TeamLinks clients.
Actually I've just realised this isn't correct. The MUP only
contains HOOKS for the broadcast stuff. The actual broadcast
code is in the TLC, so you need to install that as well (same
tape, free, real quick to install). This was done to minimise
risk to non-TeamLinks ALL-IN-1 customers installing the MUP.
Regards,
Paul
In the TeamLinks Connection Package, we introduced a new
file, OA$PC_NOTIFY.DAT, called the PC notification database.
There is also a flag in the ALL-IN-1 PROFILE which must be
set to enable PC broadcasting. If this flag is not set in
the PROFILE, ALL-IN-1 will not look at OA$PC_NOTIFY.DAT for
this user (performance enhancement). The field is RSVD_FOR_TCS
which must be 1 to enable broadcasting and should be 0 to disable.
PC Notification Database
ALL-IN-1 user: <----- Your A1 username
Node: <----- Your PC nodename in uppercase (6 chars max)
Used for NETBIOS DECnet notification.
Path: <----- More specific path information to reach
the node. For UDP notification, the NODE
field is not used, only the PATH which
should be the nodename of the PC.
Transport: <----- N for NETBIOS and U for UDP
Subject: <----- 0 = subject DISABLED
1 = subject ENABLED
If the subject is enabled, then the subject line from
the mail message is also broadcast.
For MAC notification it is proposed to extend the above scheme
as follows:
DECnet
Transport = "D", Node = <nodename>, the Path is not looked
at, although it may be needed for future extensions to Phase V.
The server connects to the Mac using object 202 and sends the
notification packet and disconnects.
TCP/IP
Transport = "T", Node = not used, Path = client address (eg
mynode.iosg.reo)
The server connects to the Mac using port 2020 and sends the
notification packet and disconnects.
AppleTalk
Transport = "T", Node = not used, Path = ADSP address, type and
name (need to agree the exact format).
The server connects to the Mac using ADSP type
"ALL-IN-1 MAIL Notification" and sends the
notification packet and disconnects.
Where the node field is not used, it should be filled in with
something useful if possible.
|
| Hi Paul,
Just to sum up what you have said and to give all concerned a "simple"
procedure to follow I am enclosing a check list below.
Any corrections would be welcomed,
Sunil
Mail Notification for ALL-IN-1 IOS
1. You need to install MUPA (ALL-IN-1 IOS 3.0A) and the TLC (TeamLinks
Connection package), the TLC is on the same tape as the MUPA.
2. Startup PATHWORKS before ALL-IN-1 IOS so that the NETBIOS process
is running.
3. Use the form OA$PC_NOTIFY to enable mail notification for the user. You
will have to enable the RSVD_FOR_TCS field in your ALL-IN-1 IOS profile.
1 will enable mail notification and 0 will disable it.
4. To update your PC Notification Database enter:
<form OA$PC_NOTIFY/mode=update
Where:
ALL-IN-1 user: <----- Your A1 username
Node: <----- Your PC nodename in uppercase
(6 chars max) Used for NETBIOS DECnet
notification.
Path: <----- More specific path information to reach
the node. For UCX notification, the NODE
field is not used, only the PATH which
should be the nodename of the PC.
(TCP/IP only)
Transport: <----- N for NETBIOS and U for UCX
Subject: <----- 0 = subject DISABLED
1 = subject ENABLED
If the subject is enabled, then the subject line from
the mail message is also broadcast.
On your PC you will require the following:
TeamLinks version of RCV and WINRCV, the standard PATHWORKS versions are
different from the TeamLinks version. Make sure the TeamLinks versions are
installed.
|