× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



System names?

Do you have an entry for the P7 system name in it's local host table?

IIRC SMTP comes up before the DNS does...so the recomendation is to
have a static entry in the local host for the hosts table.

HTH,
CHarles

On Mon, Jul 23, 2012 at 1:15 PM, Cyndi Bradberry <CyndiB@xxxxxxxx> wrote:
Hi everyone. Over the weekend, we swapped to a new P7 box running V7R1 from a P6 box running V6R1. Today, I don't have any email running from our new P7.

I double checked all the SMTP attributes were the same between the two boxes. I found the MailHubRouter parameter and put in the same as in my Mail Router. I changed the attributes of the /tmp folder. I have stopped MSF. And yet each time I attempt to start SMTP I get the following:


Job 011182/QTCP/QTSMTPSRVD started on 07/23/12 at 11:04:49 in subsystem
QSYSWRK in QSYS. Job entered system on 07/23/12 at 11:04:49.
Job 011182/QTCP/QTSMTPSRVD submitted.
SMTP initialization not successful.
SMTP job ended normally.
Parameter SBS required.
Object QTMSSCHD in QTEMP type *USRSPC deleted.
Object QTMSFLRC in QTEMP type *USRSPC deleted.
Job 011182/QTCP/QTSMTPSRVD ended on 07/23/12 at 11:04:49; .029 seconds
used; end code 0 .


And the job is listed as Job Log Pending. If I press F1 on the initialization not successful message:


Message ID . . . . . . : TCP2075 Severity . . . . . . . : 40
Message type . . . . . : Diagnostic
Date sent . . . . . . : 07/23/12 Time sent . . . . . . : 11:04:49

Message . . . . : SMTP initialization not successful.
Cause . . . . . : SMTP initialization did not complete because one of the
SMTP jobs had a problem.
Recovery . . . : Check the job log or the system operator log for messages
from the SMTP jobs.



There are no messages in the system operator queue. What is above is the job log.


For the SBS is required message:

Additional Message Information

Message ID . . . . . . : CPD0071 Severity . . . . . . . : 30
Message type . . . . . : Diagnostic
Date sent . . . . . . : 07/23/12 Time sent . . . . . . : 11:04:49

Message . . . . : Parameter SBS required.
Cause . . . . . : A required parameter was not specified.
Recovery . . . : Enter a value for parameter SBS.


And if I press F9:

Message ID . . . . . . : CPD0071 Severity . . . . . . . : 30
Date sent . . . . . . : 07/23/12 Time sent . . . . . . : 11:04:49
Message type . . . . . : Diagnostic
From . . . . . . . . . : QTCP CCSID . . . . . . . . : 65535

From program . . . . . . . . . : QCAFLD
From library . . . . . . . . : QSYS
Instruction . . . . . . . . : 12F0

To program . . . . . . . . . . : QTMSSRCD
To library . . . . . . . . . : QTCP
To module . . . . . . . . . : QTMSSRCD
To procedure . . . . . . . . : CDoCLCommand__FPc
To statement . . . . . . . . : 25

Time sent . . . . . . . . . . : 11:04:49.814775


I am trying to figure out what IBM needs me to do. The same subsystems, jobq's etc are all duplicated from the old system to the new. We heavily use automated emails so I need to get this running. I get the same errors on our V7 test LPAR, but everything runs perfectly on the V6 system still.

Can anyone point me in the right direction ?

Cyndi B.
Boise, ID

--
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 thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.