home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Network Support Encyclopedia 96-1
/
novell-nsepro-1996-1-cd2.iso
/
download
/
netware
/
ngm175.exe
/
RELNOTE.TXT
< prev
Wrap
Text File
|
1993-10-18
|
19KB
|
481 lines
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* *
* SNADS for NetWare Global MHS v1.0 revC *
* Copyright (C) 1992-1993 by Novell, Inc. *
* *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
The name of this product was changed from NetWare Global
Messaging SNADS Protocol Module to SNADS for NetWare Global
MHS after the product documentation was printed. The product
name has not yet been changed in the documentation.
This version of SNADS for NetWare Global MHS requires NetWare Global
MHS v2.0B.
This release note lists enchanced features and provides
documentation corrections, trouble-shooting hints and other
information of which you need to be aware.
Features
========
The SNADS protocol module provides the following features:
* Transfers messages between NetWare Global MHS and
SNADS endpoints using an existing SNA network.
* Provides support for the SNA communications protocols.
* Supports connections via direct token ring, ethernet, or
SDLC to an SNA wide area network. (Note that the
connection parameters for ethernet are the same as the
connection parameters for token ring.
* Supports one or more LU6.2 sessions and up to two PU2.0 or
2.1 connections.
* Supports automatic directory synchronization between
DISOSS and NetWare Global MHS.
* Supports SMF extended addresses.
* Allows you to choose whether header information (such
as To:, From:, Subject:, cc:, and Date:) will be
included in messages sent to SNADS.
* Allows you to choose whether original messages will be
included in messages replied to by SNADS users.
Extended Address Support
========================
A new feature in SNADS for NetWare Global MHS allows SNADS
users to include SMF extended addresses in messages sent to
NetWare Global MHS. Because SNADS users can now include
address extensions in their messages, the Global MHS server
administrator no longer needs to define users with extended
addresses in the SNADS Auto-Registration Table.
Some environments, such as fax and X.400, require special address
information. To support these environments, the SMF protocol
contains an extended address field. For example, to send a message
to Sharon Carstairs through a fax gateway, a NetWare Global MHS
user would address the message to Sharon Carstairs@FaxGate
{Fax:1-555-1234/Sharon Carstairs}.
However, SNADS does not support extended addresses. To enable
SNADS users to send to these environments, the SNADS protocol
module allows SNADS users to include extended addresses in their
messages.
SNADS users can enter extended addresses in one (and only one) of
the following three locations: at the beginning of the message; in
the subject; or at the beginning of the document. The SNADS
protocol module scans these three locations in the order in which
they are listed. If it finds an extended address in one of these
locations, it will ignore any extended addresses in the others.
An extended address definition begins with two open angle brackets
(<<) and ends with two closed angle brackets (>>). Between the
beginning and ending markers are one or more address extensions,
separated by one or more spaces. Thus, the syntax of the extended
address definition is as follows:
<<extension definition(s)>>
Each extension definition has one of the following formats:
dgn.den={extended address}
dgn.den=(extended address)
dgn.den="extended address"
where dgn.den is a recipient specified in the address (TO and CC)
fields. The extended address can be enclosed in braces, parentheses, or
double quotation marks.
If a message has only one recipient, the dgn.den= can be omitted
from the extended address definition.
For example, Pam Pratt is a SNADS user who wants to send a
message to Sharon Carstairs. Messages for Sharon are routed
through NetWare Global MHS to a fax gateway. Pam creates the following
message:
TO: FAXGATE.SCARSTAI
SUBJECT: <<{Fax:1-555-1234/Sharon Carstairs}>>
Because the message is addressed to only one user, Pam does not
include the dgn.den=.
Consider a second example. Pam Pratt wants to send a message to
Sharon Carstairs, Jack Smith, a Global MHS user, and Donna White, an
X.400 user. Messages for Donna are routed through NetWare Global MHS to
an X.400 Gateway. Pam creates the following message:
TO: FAXGATE.SCARSTAI
NEWYORK.JSMITH
X400GATE.DWHITE
SUBJECT: Monthly Update
<<
FAXGATE.SCARSTAI={Fax:1-555-1234/Sharon Carstairs}
X400GATE.DWHITE={X400:C=US;A=Publicmail;P=ABC;O=ABC;
G=Donna;S=White}
>>
Sharon and Donna: The update will be delayed one
day. We will be sending it tomorrow.
Because the message is addressed to more than one user, Pam must
include the dgn.den=.
SNADS Protocol Module Training
==============================
Self-paced study course #1760, titled Administering SNADS for
NetWare Global MHS, is available. NetWare Global MHS training
course #750 provides comprehensive instruction in installation,
configuration, and administration of the NetWare Global MHS
software.
For more information about either of these training courses, call
(800) 233-3382 or (801) 429-5508, or contact your local Novell
authorized education center.
Contacting Novell Messaging Technical Support
Should you need technical support for NetWare Global MHS,
contact your Novell reseller, or Novell at (800) NETWARE or (801)
429-5588.
Documentation Corrections
=========================
NetWare Global Messaging SNADS Protocol Module Administrator's Guide
--------------------------------------------------------------------
p. 6-2, Step 3b
Enter the NetWare Global MHS address for the user.
If the user is not defined in the local Global MHS database, the
username part of the NGM Name must be the same as the user's DEN. For
example, a SNADS user sends a message to Ron Simpson, an SMTP user.
Ron's Unix ID is RSIMPSON, so the SNADS user addresses the message to
the DEN "RSIMPSON." Therefore, the username part of Ron's NGM Name must
also be "RSIMPSON." Similarly, a SNADS user sends a message to Donna
White, an X.400 user. The SNADS user addresses the message to the DEN
DWHITE. Therefore, the username part of Donna's NGM Name must also be
DWHITE.
If a user's address includes an extended address (for example, if the
user is an X.400 user), you must include the extended address when you
enter the user's NGM Name. For example, Donna White is an X.400 user.
Therefore, her NGM Name must include her X.400 address. It would be in
the format "DWHITE@X400GATE {X400:C=US;A=PUBLICMAIL;P=ABC;O=ABC;G=Donna;
S=White}".
p. 7-8, no. 4
Add the following after no. 4:
4a. Define your server's directory synchronization user (NME-CMP-)
in the SNADS Auto-Registration table. This step is necessary
because, in NetWare Global MHS, the address of an NME-CMP- user
does not contain a workgroup element. (Messages for NME-CMP-
users are addressed to NME-CMP-@server.) However, DISOSS
requires that every user address contain a workgroup element.
p. 7-8, no. 5
After configuring DISOSS and NetWare Global MHS for directory
synchronization, you MUST force a full directory reconciliation to
initiate the directory synchronization feature.
p. 7-12, Step 7
Change the Directory Sync Address for the DISOSS node to
NME-CMP-@<workgroup>, where <workgroup> is the workgroup name for the
DGN to which the DISOSS NME-CMP- user belongs. Ensure that this
workgroup's SNADS alias is its DGN.
p. 7-13
Before forcing a full directory reconciliation, add your server's
NME-CMP- user to the SNADS auto-registration table. Refer to page 5-2
for detailed instructions. The user's NGM name must be
NME-CMP-@<server> (where <server> is the name of your server). The
user's SNADS DUN must be <dgn>.NME-CMP- (where the <dgn> is the same as
the SNADS REN assigned to your server).
p. 7-13
You MUST force a full directory reconciliation to initiate the directory
synchronization feature.
p. 7-29
The DDN for a remote directory synchronization user must be the same as
the user's REN. In the example entry, the DDN and REN should both be
"LA."
p. 7-34
Note: If a new update is generated when the Directory Parcels Status
list contains 40 unsent updates, the oldest update in the list is
deleted.
p. 8-4, Step 1f,
p. 8-9, Step 1f, p. C-4
SNADS.NEW is located in <ngmfiles>/SNADS.
p. 8-5, Step 2d,
p 8-10, Step 2d, p. C-2
The NGMSNADS log is located in <ngmfiles>/LOG.
p. B-4
Add the following to the list of [NGMSNADS] parameters:
Maximum-Recipients=<nnn>
(Optional) If the maximum number of recipients for which your
SNADS node is configured is less than 256 (the default), use
this parameter. The SNADS protocol module will split a message
addressed to more than <nnn> recipients into multiple messages.
add-outgoing-text-headers=TRUE | FALSE
(Optional) Specify whether you want message headers (To:, From:,
Subject:, cc:, and Date:) included on messages sent to SNADS.
The default value is "FALSE."
append-note-to-reply=TRUE | FALSE
(Optional) Specify whether you want the original message appended
to the note when SNADS users reply to Global MHS users.
The default value is "FALSE."
AS/400 Supplement for the NetWare Global Messaging SNADS Protocol Module
Administrator's Guide
------------------------------------------------------------------------
p. 3
Add the following note after the fourth bullet:
Note: If you are using NetWare for SAA PC Support, you must
define an additional Device Description for SNADS for Global
MHS. It cannot use the same Device Description as NetWare for
SAA PC Support, because the Device for SNADS for Global MHS
must be single-session enabled.
p. 10, step 6e
Add the following parameters and values:
Parameter Value
MIN_CONWINNERS_SOURCE 0
MIN_CONWINNERS_TARGET 1
p. 14, step 5
Change the values for the following keywords to:
Keyword Value
LCLCTLSSN 1
PREESTSSN 1
Troubleshooting Hints
=====================
For detailed troubleshooting instructions, refer to Chapter 8 of the
NetWare Global Messaging SNADS Protocol Module Administrator's
Guide. Following are suggestions for troubleshooting common problems.
Problem:
Messages from SNADS are remaining in the NGM queue, with the following
workgroup name:
-unauthorized-.workgroup
Action:
This error occurs if you are using a limited-user version of the SNADS
protocol module. The NetWare Global MHS recipient is not defined as
an authorized user. Add the user to the list of authorized users,
following the instructions in Chapter 6 of the guide.
Problem:
The SNADS node is rejecting messages received from the SNADS protocol module.
Action:
Check the maximum number of recipients for which your SNADS node is
configured. If it is less than 256, add the following parameter to
the [NGMSNADS] section of your server's NGM.CFG file:
Maximum-Recipients=<nnn>
where <nnn> is the maximum number of recipients your SNADS node will
accept. For more information about NGM.CFG, refer to Appendix B of the guide.
Problem:
Global MHS users are receiving non-delivery notifications that contain
no explanation of the reason for non-delivery.
Action:
a. If you are using a limited-user version of SNADS for Global MHS,
make sure the sender has been authorized to send messages to
SNADS. Refer to chapter 6 of the "NetWare Global Messaging
SNADS Protocol Module Administrator's Guide" for detailed
instructions.
b. Check for communication problems. This error occurs if there is
an unrecoverable communication error while SNADS for Global MHS
is transmitting a message to the SNADS node.
Problem:
Messages from SNADS are arriving at their destination in binary format.
The destination server does not connect to SNADS directly, but through
an intermediate server.
Action:
a. (Recommended solution) In the SNADS directory, do not define
servers that connect to SNADS indirectly. Instead, define their
DGNs as belonging to the server that does connect directly. For
example, Server1 connects to SNADS directly; Server2 communicates
with SNADS through Server1. Server2 has two workgroups,
Personnel (SNADS alias=PERSONNE) and Finance (SNADS
alias=FINANCE). In the SNADS directory, PERSONNE and FINANCE are
defined as DGNs at Server1.
b. If you prefer to define indirectly-connected servers in the
SNADS directory, ensure that the SNADS alias for the
directly-connecting server contains the aliases for all servers
to which it routes messages received from SNADS. For example, if
Server2 (RGN=ACME, REN=SERVER2) is defined in the SNADS
directory, you must define the following SNADS alias for Server1
(RGN=ACME, REN=SERVER1):
ACME.SERVER1,ACME.SERVER2
Problem:
Directory information received from DISOSS is not being integrated
into the Global MHS database.
Action:
Ensure that your Global MHS server subscribes to the DISOSS workgroups.
For more information, refer to Chapter 7 of the guide.
General Information
===================
This section provides additional information about the SNADS
protocol module.
* If a session terminates while the SNADS protocol module is
delivering a message to SNADS, the SNADS protocol module
will resend the message during the next session. If the
message was delivered successfully before the termination
occurred, two copies of the message might be delivered to the
SNADS recipient.
* When a DISOSS user sends a message to a NetWare Global
MHS distribution list, DISOSS receives a DIA status (delivery
report) from each of the list members. Since the list member
names do not match the original recipient name (the
distribution list), the message status is not updated.
For example, a DISOSS user sends a message to a NetWare
Global MHS list called "Managers." NetWare Global MHS
distributes the message to John Smith and Mary Adams, the
list members. DISOSS receives DIA statuses from John and
Mary, but it does not receive one from "Managers," the
original recipient. Therefore, it does not update the message
status.
* SMF short names can only include letters, numbers, and the
following special characters: #, $, and -. To ensure
compatibility between SNADS and NetWare Global MHS, do
not use unsupported characters (such as spaces) in SNADS
names.
* If you are using DISOSS Directory Synchronization,
workgroups in your organization must not include both
DISOSS and NetWare Global MHS users.
* SNADS for Global MHS cannot detect the Keyword
document translation program (DOCXLT) when it is
auto-loaded by NGM. If document translations are not
being invoked, unload DOCXLT and reload it manually.
* The Keyword document translation program (DOCXLT) has
an auto-detection feature that allows it to determine
a document type. However, this feature might identify
a binary file as type TEXT, and attempt to convert it.
This results in corruption of the file.
Copyright 1993 Novell, Inc. All rights reserved. No part of this
publication may be reproduced, photocopied, stored on a retrieval system,
or transmitted without the express written consent of the publisher.
Novell, Inc.
2180 Fortune Drive
San Jose, CA 95131
U.S.A.
Disclaimer
==========
Novell, Inc. makes no representations or warranties with respect to the
contents or use of this manual, and specifically disclaims any express or
implied warranties of merchantability or fitness for any particular purpose.
Further, Novell, Inc. reserves the right to revise this publication and to
make changes to its content, at any time, without obligation to notify any
person or entity of such revisions or changes.
Further, Novell, Inc. makes no representations or warranties with respect
to any NetWare software, and specifically disclaims any express or implied
warranties of merchantability or fitness for any particular purpose. Further,
Novell, Inc. reserves the right to make changes to any and all parts of
NetWare software, at any time, without any obligation to notify any
person or entity of such changes.
Trademarks
==========
NetWare and Novell are registered trademarks and NetWare MHS,
NetWare Global MHS, NGM, and SNADS for NetWare Global MHS are
trademarks of Novell, Inc. NetWire is a service mark of Novell, Inc.
UNIX is a registered trademark of UNIX System Laboratories, Inc. (USL). USL is
a wholly owned subsidiary of Novell, Inc.
IBM and AS/400 are registered trademarks of International Business
Machines Corp.
SNADS for NetWare Global MHS v1.0 Release Note
October 1993