|
Hi; I am having problems with the code400 library list. I have changed the server library list to what I want it to be using the communications properties. I originally had the list set for all servers, but read the note in help so added the library list to the specific server (there is still a library list associated with the all servers version). When I submit a compile, the library list is not what I requested. I have checked the archives and did not find anything that solved the problem. When I use F9 and print the library list, it is the incorrect library list that is used with the compiles. I can not figure out where it is getting this library list - it is not my current library list or the library list in my jobd. The library list used to be okay and has changed somehow. At this location we are on V5R1 and Development Studio Client for iSeries version 4.0. There are two developers and we have had problems with not having our own STRCODE userspace. During one session, I started code400 through SEU without my library as the current library and the code session opened in the other developers workstation. I then reset the current library to my library. Could this have messed up the library list? I deleted the user space in QGPL and have my own STRCODE user space in my current library. I tried ending all servers (right click on the icon) and tried a reboot. I read the post about using F9 and manually changing the library list with the rmvlible and addlible commands, but this seems like a real pain, especially since I have never had to do this before. What sets the library list for compiles in code400? I am not impressed with the process so far. Thanks in advance for any help. Dave Murvin DRM Enterprises, Inc. davem@drme.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.