|
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] I tried what you suggested by first ensuring that the STRCODE command was entered using the user ID and password as coded in STRCODE Communications Console settings... Ended up with the same two error messages. I then removed the ID and password in the Console settings and I got the 1st message: "EVC4021I - Communication Daemon - A connection request from system '*NONAME' has been received." After which it appeared to connect... I have not yet tried debug for this, but I will soon. Thanks for the help. Ric -- Original message -- Subject: Re: [WDSCI-L] *NONAME server when trying to start debug from Code/400 To: wdsci-l@midrange.com From: yantzi@ca.ibm.com Date: Wed, 27 Nov 2002 21:10:05 -0500 Reply-To: wdsci-l@midrange.com Ric, Check that you don't have a userid / password specified in the CODE communications properties settings. To do this go to Start -> Programs -> WebSphere Development Studio Client for iSeries -> Communications -> Communications Console. Select STRCODE settings and check under Advanced Settings if there is a STRCODE userid ID / password specified. If so then you either need to specify this user id / password on the STRCODE command or delete them from the communications console. Hope this helps. Don Yantzi WebSphere Development Studio Client for iSeries IBM Toronto Lab Phone: (905) 413-4476 IBM internal: IBMCA(yantzi) - Internet: yantzi@ca.ibm.com Ric Richard A. LuBell Director of Professional Services I/O International, Inc. Phone: 914-232-2233 Fax : 914-232-2566 eMail : rlubell@iointernational.com <mailto:rlubell@iointernational.com>
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.