|
Violaine, I was able to prevent the pop-up message and found the option to prevent the error window from appearing. I think I found why the *USRSPC object STRCODE was not appearing in my programmer library. On the Library List section, the server of *ALL was set to *USRPRF for the current library. The other servers were set to my user profile name. I assumed it was using the current library set for the server Code was interfacing with. Thank you, Matt Tyler WinCo Foods, LLC mattt@xxxxxxxxxxxxxx -----Original Message----- From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Violaine Batthish Sent: Tuesday, March 29, 2005 2:56 p To: Websphere Development Studio Client for iSeries Subject: RE: [WDSCI-L] Code desginer display create batch job Hi Matt, It sounds like some of your Communication Properties settings may have been inadvertantly changed, or corrupted. To remove this notification: 1) Right click on the Communication Daemon icon in the tooltray 2) Select Properties... 3) Go to the STRCODE Settings node 4) Remove selection of "Announce a connection with a message" The STRCODE *USRSPC object is automatically created in your *CURLIB. If your *CURLIB isn't unique (or something shared like QGPL) then someone else with the same *CURLIB setting may clobber the information within. Once that occurs, compile messages will be sent to the last person to update the STRCODE *USRSPC, if that person is no longer running the Communication Daemon, then the compile job will wait until it times out. If your *CURLIB is QTEMP, then the STRCODE *USRSPC will not be visible in the batch job, and compile acknowledgement messages will not appear, nor will the Error List Window. thanks, Violaine Batthish WebSphere Development Studio Client, IBM Toronto Lab wdsci-l-bounces@xxxxxxxxxxxx wrote on 03/29/2005 03:22:48 PM: > Violaine, > > I was not having issues compiling. All objects compiled right away. Its > just the batch job to compile sat at the TIMW for a minute before ending, > holding up other jobs. > > I did have a STRCODE *USRSPC in my programmer library with different > communication data than one in QGPL. The one in QGPL contained my current > IP address where as the other contained an old one. I deleted both. > > In the communications console stopped all servers and deleted them (with > Code designer and WDSC shut down). > > Now I restarted my system, WDSC and Code designer and it created a new > connection. I was able to supply a user and password to that default > server (R0OPMENT) after shutting down Code designer. > > Now, the compile job sits on the active jobs only for the time frame needed > to compile the object except that now I get a message box with message > EVF40211 "A connection request from 10.21.0.196 has been received" (which I > have never received before). The job sits there until I answer the message. > > > I would like to get rid of this pop-up message since it's the same each > time. Also, the error event display now shows also. This is not as annoying > as the pop-up message, but is redundant with the Error list tab. > > The STRCODE *USRSPC object is now created automatically in QGPL (if I happen > to delete it), instead of my programmer library. So, I have no clue what > setting causes the object to be created or used from my programmer library. > > > > Thank you, > Matt Tyler > WinCo Foods, LLC > mattt@xxxxxxxxxxxxxx > -- This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-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.