Re: QWCRSSTS problem

Scott Klement wrote:

Hello Jonathan,



Not I - I didn't write it. I'm just stuck trying to clean up the mess.
This is some kind of shareware/freeware stuff that developers at my
employer obtained long before I arrived there.


Oh, sorry... I got the impression that you (or maybe David Foxwell) were
the developer who was creating a shareware/freeware application for e-mail.

After all, David asked whether it made sense to replace QWCRSSTS with
RTVNETA. That sure sounds like a question that would be asked by the
developer... since the developer is the one writing the code... right?

Anyway... the answer is: NEITHER.

If you are trying to derive the logged in user's e-mail address,
'[1]username@xxxxxxxxxxxxxxxxxxxxxx' then you should probably be retrieving
the SMTP name for your user from the system distribution directory.
there's no reason to assume that a user's e-mail address points to the
current system!

If you want to know your computer's TCP/IP name, then you should be
using the gethostname() API. I'd be happy to give you an RPG or CL
example of this if it's useful to you.

Using RTVNETA or QWCRSSTS to get the 'systemname' portion of
'systemname.company.net' is not a proper way to do it.

For example, I could set up my system's name as follows:

CHGNETA SYSNAME(FOO)

And it could set up it's TCP/IP domain name as follows:

CHGTCPDMN HOSTNAME('bar') DMNNAME('company.net')

If I did that, and someone used either QWCRSSTS or RTVNETA to get the
'systemname', they'd arrive at '[2]scott@xxxxxxxxxxxxxxx' which wouldn't
point to my system, since my system is '[3]scott@xxxxxxxxxxxxxxx'

The existing code makes an assumption that whomever configured the
system always set the CHGNETA SYSNAME(x) to the same value as CHGTCPDMN
HOSTNAME(x). IMHO, that's not a valid assumption. These are two
different settings, and it's perfectly legal to make them different.

I'm just posting this to try to help people understand.

I realize it's not your software and you don't like it. But since David
asked the question about whether to use the API or the command, I
thought it'd be useful to explain it.


The e-mails in question aren't really "from" anyone. That is, it isn't
important to know a real person's e-mail address, and there will never be
a reply sent. They originate in batch jobs on the iSeries that create
spool files that are sent to one or more users, or perhaps send database
files as .xls or .csv attachments. They are only sent to internal users;
never to anyone outside the company.

As far as the application not being mine...I was a midrange developer for
some 23 years, and wish I still were, but circumstances have made me into
an iSeries administrator, and while I'd love to be able to go in and make
this thing right, I just don't have the time. I'm doing my gol-durndest
to make sure I don't end up "owning" this application and having to
enhance or fix it.

References

Visible links
1. mailto:username@xxxxxxxxxxxxxxxxxxxxxx
2. mailto:scott@xxxxxxxxxxxxxxx
3. mailto:scott@xxxxxxxxxxxxxxx