Anything interesting in the QSYSOPR message queue, the history log, or PRTERRLOG? Is there a different job log for the DDM server instance, maybe in QEZDEBUG or QEZJOBLOG? > -------- Original Message -------- > Subject: DDM Server Error > From: Guy Terry <guy.terry@xxxxxxxxxxxxxxxxxxx> > Date: Thu, September 22, 2005 7:10 am > To: midrange-l@xxxxxxxxxxxx > > Hi all, > > In iSeries Navigator, if I do Network -> Servers -> TCP/IP and do > 'Properties' on SMTP server I get: > > > There was an error when trying to retrieve data from the server. > > Try the following possible solutions then contact you next level of > > support. > > - Verify the DDM server is started. > > - Verify the connection name and server name are identical. > > The iSeries Navigator tells me that the DDM server is actually started, > but if I look at the joblog for it (well, for QRWTLSTN in QSYSWRK) I see > that an entry appears each time the error above is produced: > > > CPD3E33 - DDM TCP/IP server error occurred with reason code 5. > > 5 -- Starting of the server job failed. > > Whilst I can a little reference to CPD3E33 via Google, there's nothing > about reason code 5 - Starting of the server job failed. > > This is causing problems, as the CPD3E33 message is also produced when > asking the WebSphere Development Studio for iSeries Client package to do > anything useful. > > Were on v5r3m0, and having spent a fair amount of time over the last > couple of weeks sorting the PTF's, we're patched up-to-date. > > Any ideas why DDM server is barfing? > > Guy > > > > > > -- > 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.