× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Bruce,

Because I regularly need to switch environments, I have a small library list setting program for every environment I use. I make entries for 'CALL MYLIB/environment_program' in the 'iSeries Commands' subtree. First thing to do when I start using WDSC is setting the right environment. (At one point I even succeeded in having the 'iSeries Commands' branch appear before the 'iSeries Objects' branch by messing with the XML, but that was reset after an update.)

Joep Beckeringh



Bruce.Vest wrote:
Is there a way to get LPEX editor to connect to a specific subsystem on the
iSeries?  We use TELNET exits to force 5250 sessions to have specific device
names based on the server IP address the person is connecting to.  Specific
device names connect to specific subsystems.

The test/development subsystem uses the "System library list entry"
parameter to force the development library above all others in the library
list (this includes the SYSTEM portion of the library list).

The problem I have is, when I run open WDSC 5.1.2, load a source member and
then need to verify the changes, it uses a job name of QZRCSRVS and user ID
QUSER.  I need the verify to work with the test/development subsystem not
QUSRWRK.  As it is, the verify feature is only going to work if I remove
stuff from production (which is in the system portion of the library list)
or rename everything anytime I had to make a change.

Any help would be GREATLY appreciated!!

Bruce Vest



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.