|
I found that it is easier to locate your CODE server job by entering the command like this: WRKOBJLCK OBJ(your signon id) OBJTYPE(*USRPRF) You should be able to identify your CODE server job as QZRCSRVS QUSER. In a normal CODE session, there should be only one server job QZRCSRVS associated with one client. I guess the server job could become an orphan when the client detects that a connection has been lost and reconnected with a new session. At this point, the client cannot signal the orphan job to end itself and release the resource. This is a CODE communications issue which has no complete solution yet. Best regards, Hak _______________________ Hak Lui WebSphere Development Studio Client for iSeries, IBM Canada Ltd. e-mail: haklui@xxxxxxxxxx
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.