| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 61.1 | MR-Memo - in what language has it been written?
| VNASWS::HELENE | Berlin Marathon was the first .. | Mon Dec 10 1990 21:38 | 10 |
| The system where our gateway is running is poor on diskspace, so during
installation of SNAAPI you can choose which languages you need.
I left out ADA, because it took 3000 blocks, and now I found a String in
a Stack dump ADA$ELAB_DDS: does it mean you used ADA,i.e do I need the SNA-
Symbolfiles for ADA?
regards
Helene
|
| 61.2 | MRMEMO is multilingual | STKOFF::SPERSSON | Pas de Probleme | Tue Dec 11 1990 10:24 | 82 |
|
Hi Helene,
> Question 1:
>
> Memo does not accept e.g. .. (dot dot) in the address string. How do I(the
> customer) have to set up the Memo validation, that it works this way?
I assume you mean that MEMO users cannot specify ".." in their address
strings. MEMO must be set up so that it accepts what they call "Complex
addressing", otherwise it will only accept the usual 8+8 character
MEMO address. Is this the problem? If so, the MEMO system manager
should be able to fix this rather easily.
> Question 2:
>
> When I started the first server, I had the following error due to a missing
> task object (the customer's system manager usually deletes it due to
> security reasons)
>
> MRMEMO-W-NOSERVER, the target server is not accessible
> -SYSTEM-F-NOSUCHOBJ, network object is unknown at remote node
>
> Perhaps you would think of taking it into the documentation?
Point taken. I'll check the documentation and see what we can do to
clarify.
> Is the task object needed during startup of the server only, i.e. can I remove
> it afterwards?
Yes, this should work, although you'd have to test it. If your customer
feels safer ho could define an object named MRMEMO with number 0 and
use the MRMEMO account name and passwords. The MRMEMO account is set
up to reject all break-ins.
> I had a situation today, where the server was in LEF state and did not react
> on shut commands or on mail inbound from Memo.
> In the MRMEMO1.LOG I found two SYSTEM-F-PAGRDERR (page read errors),
> followed by
> SNA-F-INTERR, internal error in Gateway Access Routines
> SNA-F-CTXBLKINU, no active ports, but context blocks still in use
> ---end of exception message
>
> followed by
>
> %SNALU0-E-XMTFAIL, call to SNALU0$TRANSMIT[_W] failed
> -SNALU0-E-TOPOSRSP failed to change RU to positive response
> -SNA-E-FUNNOTVAL, function not valid with port in current state
>
> followed by
>
> %SNA-F-PROBINREVT, problem with internal sna$readevent call
> -SNA-E-FUNNOTVAL, function not valid with port in current state
>
>
> Is it reasonable to assume, that all the SNA-errors were a consequence of
> the pagereaderrors?
Yes, I hope so! I have never seen these error messages on any other
site. If you have fixed the page read errors and the SNA errors don't
occur again I daresay you should be OK.
> The system where our gateway is running is poor on diskspace, so during
> installation of SNAAPI you can choose which languages you need.
>
> I left out ADA, because it took 3000 blocks, and now I found a String in
> a Stack dump ADA$ELAB_DDS: does it mean you used ADA,i.e do I need the SNA-
> Symbolfiles for ADA?
No. We use ADA for other purposes, and even if we did use it for SNA
communication I would have thought the symbolfiles only applied if you
were actually doing development on the system.
cheers,
Stefan
|
| 61.3 | Recipient validation for certain DGN's, Header | VNASWS::HELENE | Berlin Marathon was the first .. | Fri Dec 14 1990 11:24 | 37 |
| Hi Stefan,
thank you very much for your fast answers!
I have been at Philips yesterday.
Definition of an object MRMEMO does not work, TASK Object has to be
there for starting and shutting the server. We protected the
Task Object with the Account MRMEMO + Password - it works and
the customer feels safe.
The SNA-errors did not appear again up to now.
I brought some new questions:
* When a MEMO user gets a mail from a Vaxmail user, the Originator
information on the mail is approx. 15 lines, which is rather confusing.
Is there a way to reduce the output of all the addressing information?
* Is there a way to restrict senders from the VAX-world to certain
groups of recipients, e.g. VAXUSER1 may send to DGN A, but not to
DGN B?
* The User Agent is VAXmail in this implementation. How can I implement
some help for addressing?
One idea is, to use a logical for NODEA::MRGATE::"MEMOMBX:: and have
the user type the logical + DGN.DEN. What would the exact syntax of
the Logical Name definition be (with quotes etc.?)?
One distribution list per user is not really feasible, because there
are 3000 Memo Users.
I recommended ALL-IN-1 Mail as a user agent because of its
DDS-Interface, has someone of you found a solution for VMSmail?
Kind regards
Helene
|
| 61.4 | | PEARS::SONNTAG | Michael Sonntag, TSSC-OIS, @MUH | Fri Dec 14 1990 14:18 | 9 |
| Hi Helene,
>> I recommended ALL-IN-1 Mail as a user agent because of its
>> DDS-Interface, has someone of you found a solution for VMSmail?
see FORTY2::MAILBUS Note 1798.*
regards
Michael
|
| 61.5 | try this | STKOFF::SPERSSON | Pas de Probleme | Sat Dec 15 1990 00:04 | 66 |
|
> Definition of an object MRMEMO does not work, TASK Object has to be
> there for starting and shutting the server. We protected the
> Task Object with the Account MRMEMO + Password - it works and
> the customer feels safe.
Sorry, I thought it was possible to do as I lined out. Anyway if the
customer is happy with your solution then you should be OK.
> * When a MEMO user gets a mail from a Vaxmail user, the Originator
> information on the mail is approx. 15 lines, which is rather confusing.
> Is there a way to reduce the output of all the addressing information?
I think you have the server option /HEADER_IN_TEXT enabled (it is by
default). This option means that you will get the full Sender
information plus a number of other attributes as part of the message.
If you wish to disable this option, do:
$ MC MRMMAN
MRMMAN> DEFINE /NOHEADER_IN_TEXT
...and restart the server.
There is also a timestamp that you can disable with:
$ MC MRMMAN
MRMMAN> DEFINE /NOTIMESTAMP
> * Is there a way to restrict senders from the VAX-world to certain
> groups of recipients, e.g. VAXUSER1 may send to DGN A, but not to
> DGN B?
No.
> * The User Agent is VAXmail in this implementation. How can I implement
> some help for addressing?
> One idea is, to use a logical for NODEA::MRGATE::"MEMOMBX:: and have
> the user type the logical + DGN.DEN. What would the exact syntax of
> the Logical Name definition be (with quotes etc.?)?
> One distribution list per user is not really feasible, because there
> are 3000 Memo Users.
try:
$ define memo "vaxbox::mrgate::memo5::"
...and then:
$ MAIL
MAIL> send
To: MEMO::abc.def
SUBJ: hi hi
.
.
,
|
| 61.6 | making things complicated... | VNASWS::HELENE | Berlin Marathon was the first .. | Mon Dec 17 1990 08:25 | 8 |
| Hi,
$set mode/embarrassed
thanks for the logical for Memo-Mailbox ..
trying the easy way is a good idea sometimes -
perhaps my brain was spoiled by the space in the ALL-IN-1 username
|