RE: [WDSCI-L] LPEX Editor for RPG IV

[<Rick.Chevalier@xxxxxxxxxxxxxxx>]

Bruce,

This may not be exactly what you wanted but it might help.

You can create a signon job that sets your library list when WDSc starts.  I 
have one specifically for WDSc signon.  Right click your connection name -> 
properties -> susbystems -> iSeries Commands.  At the bottom of the panel is 
the entry for initial command.  Enter a call command to the startup job.

HTH,

Rick

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx]On Behalf Of Bruce.Vest
Sent: Wednesday, March 02, 2005 1:47 PM
To: Websphere Development Studio Client for iSeries
Subject: [WDSCI-L] LPEX Editor for RPG IV


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


Privileged and Confidential.  This e-mail, and any attachments there to, is 
intended only for use by the addressee(s) named herein and may contain legally 
privileged or confidential information.  If you have received this e-mail in 
error, please notify me immediately by a return e-mail and delete this e-mail.  
You are hereby notified that any dissemination, distribution or copying of this 
e-mail and/or any attachments thereto, is strictly prohibited.