|
Hi Kari,
I was wondering if I was going to have to move anything from QTEMP, but I
didn't. I really just followed those instructions, and using EDTLIBL added
SMTP to the library list.
I'm still learning myself, but I imagine that you don't necessarily need
QSECOFR authority for the installation.
Once done, running WRKOBJ OBJ(SNDM) I do see both the *PGM and *CMD
objects.
Hopefully that's all you need to do.
Good luck!
Clay
Clay,--
I do not have QSECOFR authority, but I was able to install everything by
using his installation guide. I then did a EDTLIBL and added the library.
I am assuming maybe I should have done ADDLIBLE? Joe mentioned in a
previous email that there is an undocumented step after the STRREXPRC
SRCMBR(MAKE). He said that I should "move" the compiled objects from QTEMP
to the library SMTP. Is that what you also did?
Thanks!
Kari
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Clay B Carley
Sent: Friday, October 25, 2013 8:21 AM
To: Midrange Systems Technical Discussion
Subject: Re: SNDM Command
Hi Kari,
I'm not sure if it matters, but during installation, I was logged in as
QSECOFR; coming from my Linux background it seemed to make sense.
Also, the make process STRREXPRC SRCMBR(MAKE) took some time on my 170; it
did tell me when it was complete though. My system is at V5R2.
Good luck!
Clay
On 10/25/2013 06:49 AM, Kari Zeglin wrote:
Thank you Clay :) I am going to reinstall today and be sure to add SMTP--
to my library list.
Thank you again!
Kari
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Clay B Carley
Sent: Thursday, October 24, 2013 9:00 PM
To: Midrange Systems Technical Discussion
Subject: Re: SNDM Command
I just went through the install according to the directions on the
website.
http://homepage1.nifty.com/uzaemon/sndm_install.html
Everything worked out OK, but I had the same error as you did when I
finished.
I added "SMTP" to the library list as that's where it is installed
according to those instructions, and everything is now working as you
would expect.
Good luck,
Clay Carley
On 10/24/2013 01:45 PM, Kari Zeglin wrote:
I'm very sorry about that. I think I have fried my brain from learning--
so much, including trying this today! Thank you all for your help. I
will start working on getting the program and the command together. I
FTP-ed the SNDM and must have missed something.. Thank you all again.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jeff Crosby
Sent: Thursday, October 24, 2013 2:41 PM
To: Midrange Systems Technical Discussion
Subject: Re: SNDM Command
Your'e not hearing us.
There needs to be 2 objects named SNDM:
1) a command
2) a program
You have the command. What you don't have is the program. A command by
itself is a nothing. A command is simply a way to execute a program.
On Thu, Oct 24, 2013 at 4:35 PM, Kari Zeglin
<Kari.Zeglin@xxxxxxxxxxx>wrote:
When I do the WRKOBJ that you stated I end up with (Cannot find
object to match specified name.) If I just do a WRKOBJ OBJ(SNDM) I
see SNDM in the library SMTP. I tried copying that from the WRKOBJ
menu into my personal library and the same error happens.
The CMD object is NOT your issue. The command is failing toPGM object it calls. WRKOBJ *ALLUSR/SNDM *PGM and see if it's
locate the
really on your >system and if so make sure that the library it's in
is in your LIBL
Thanks,
Tommy Holden
From: Kari Zeglin <Kari.Zeglin@xxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 10/24/2013 03:25 PM
Subject: RE: SNDM Command
Sent by: midrange-l-bounces@xxxxxxxxxxxx
If I copy the command and let's say put it in my library, would
that solve the problem I am having?
It does in fact say *LIBL, but when I do a WRKOBJ it shows theSNDM in library SMTP.
command
crazy thought. Do a DSPCMD SNDM and see if it says *LIBL for theto run or points to a specific library.
program
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept
1600 Mail
to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755 http://www.dekko.com
From: Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 10/24/2013 04:10 PM
Subject: Re: SNDM Command
Sent by: midrange-l-bounces@xxxxxxxxxxxx
Don't forget that the command and the program are 2 different things.
The _command_ might exist, but not the _program_.
On Thu, Oct 24, 2013 at 3:54 PM, Kari Zeglin
<Kari.Zeglin@xxxxxxxxxxx>wrote:
Yes I believe that I do because when I do EDTLIBL I see thatincorrect.
library on the list.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jack Kingsley
Sent: Thursday, October 24, 2013 1:53 PM
To: Midrange Systems Technical Discussion
Subject: Re: SNDM Command
do you have the library in your library list.
On Thu, Oct 24, 2013 at 3:40 PM, Kari Zeglin
<Kari.Zeglin@xxxxxxxxxxx
wrote:
I believe that I have the correct email forum.. Sorry if I am
list--
I just loaded the SNMP command from Uzaemon (
http://homepage1.nifty.com/uzaemon/) and am having trouble with it.
From what I have researched he recently closed down his forums
due to inactivity. Anyway I am trying to email from a CLLE. This is
my code:
SNDM FROM('XXX@xxxxxxx') TO(('YYY@xxxxxxxxx'))
FILE(KZEGLIN/QTSTSRC)
SUBJECT('TESTING!!') SMTPHOST('smtp.host.com')
And receive 'Program SNDM not found in library *LIBL'. Thing is,
I used EDTLIBL and I do have the library that contains the
command in my list (SMTP). I have also tried the same code on a
command line and I also get the same error. I am wondering what
must I be doing wrong to cause this error?
Kari Zeglin
Our virtues and our failings are inseparable, like force and matter.
When they separate, man is no more.<
http://www.brainyquote.com/quotes/quotes/n/nikolatesl127335.html>
Nikola Tesla<
http://www.brainyquote.com/quotes/quotes/n/nikolatesl127335.html>
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx 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@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx 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
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at
http://archive.midrange.com/midrange-l.
--
Jeff Crosby
VP Information Systems
UniPro FoodService/Dilgard
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531
www.dilgardfoods.com
The opinions expressed are my own and not necessarily the opinion
of my company. Unless I say so.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx 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@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx 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@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx 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@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx 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@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx 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@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at
http://archive.midrange.com/midrange-l.
--
Jeff Crosby
VP Information Systems
UniPro FoodService/Dilgard
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531
www.dilgardfoods.com
The opinions expressed are my own and not necessarily the opinion of my
company. Unless I say so.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx 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@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx 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@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.