Re: SPL2Email tool

Oh,
If SMTP is not active, you can start it there from Op's Nav using Right
Click.  You can also Right Click to change the Properties and turn on the
'Start when TCP/IP is started' checkbox.


Rob Berendt

==================
A smart person learns from their mistakes,
but a wise person learns from OTHER peoples mistakes.



                    rob@dekko.com
                    Sent by:                  To:     midrange-l@midrange.com
                    midrange-l-admin@mi       cc:
                    drange.com                Fax to:
                                              Subject:     Re: SPL2Email tool

                    09/17/2001 12:45 PM
                    Please respond to
                    midrange-l







WRKJOB QMSF
If none active
STRMSF
Then add it to your startup routines.

WRKCFGSTS *LIN yourlinename
Long shot, but this should be active.

Use Op's Nav to check and see if SMTP is running:
  Open up your computer
  Network, Servers, TCP/IP
  Look for SMTP


Rob Berendt

==================
A smart person learns from their mistakes,
but a wise person learns from OTHER peoples mistakes.



                    Basit Khan
                    <Bkhan@medexassist.       To:
"'midrange-l@midrange.com'" <midrange-l@midrange.com>
                    com>                      cc:
                    Sent by:                  Fax to:
                    midrange-l-admin@mi       Subject:     SPL2Email tool
                    drange.com


                    09/17/2001 12:18 PM
                    Please respond to
                    midrange-l






I am using SPL2Email to send email from AS/400 it was working fine until I
IPLed my system last night ( and of course installed the latest CUM).
It processes the command and tells me the email has been sent, creates a
STMF in SPLtool directory but never sends the email .

Any ideas?


B Khan



-----Original Message-----
From: John Earl [mailto:johnearl@powertechgroup.com]
Sent: Monday, September 17, 2001 1:08 PM
To: midrange-l@midrange.com
Subject: Re: Monitoring messaging


For the SNDMSG you could use the (V4R5 and later) command exits.  They
work on any command.   For QEZSNDMG... much tougher,  I think.  You
can audit object use, but that won't give you the text of the message.
You could write a command exit for the "CALL" command and filter only
the program QEZSNDMG, but I would be concerned about wider system
impacts.

Another thought - The receiving part will give you the sending part.
Part of each message is who sent it.  Is that enough?

jte


--
John Earl                              johnearl@powertechgroup.com
The Powertech Group          www.powertechgroup.com
Kent, Washington, USA       +1 253-872-7788


----- Original Message -----
From: Chris Bipes <chris.bipes@cross-check.com>
To: Midrange Mailing List (E-mail) <midrange-L@midrange.com>
Sent: Monday, September 17, 2001 9:54 AM
Subject: Monitoring messaging


> Has any one figured out how to monitor all messages some one sends?
I have
> the need to document what some employees are sending to and
receiving from
> others.  The receiving part is easy but I have been unable to do the
sending
> part.  Is there an exit point on the send message command or APIs?
We use
> both SNDMSG and call to QEZSNDMG.  The users also use the system
request
> function to send messages.
>
> TIA,
>
> Christopher K. Bipes mailto:ChrisB@Cross-Check.com
> Operations & Network Mgr mailto:Chris_Bipes@Yahoo.com
> CrossCheck, Inc. http://www.cross-check.com
> 6119 State Farm Drive Phone: 707 586-0551 x 1102
> Rohnert Park CA  94928 Fax: 707 586-1884
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.





_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.