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

[rob@xxxxxxxxx]

Don't mean this to come off flippant, but Do you really need so many 
custom libraries at the 'system' level?  I've seen 1 in some shops to 
override IBM commands with custom commands but that's about it.  Or do you 
do something weird like continue to use the default names for job queues, 
output queues, etc for all your users (like QBATCH, etc) and then override 
the defaults with a string of initial library lists that work if, and only 
if, the user connects via 5250 to a specified subsystem and, heaven forbid 
if they ever connect using a C/S tool?  I'm not trying to sound too 
critical (although I can see how it sounds that way), just trying to 
understand.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Bruce.Vest" <Bruce.Vest@xxxxxxxxxxxxxx> 
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
03/03/2005 08:48 AM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
"Websphere Development Studio Client for iSeries" <wdsci-l@xxxxxxxxxxxx>
cc

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






Hi Joep,
 
But does it manipulate more than CURLIB and USRLIBL?  Here's the
production/normal LIBL I have:
 
Library     Type
YJOBD       SYS 
YSYSTEMS    SYS 
QSYS        SYS 
QSYS2       SYS 
QHLPSYS     SYS 
QUSRSYS     SYS 
EXTERMIN8   SYS 
Y1BAV       CUR 
QTEMP       USR 
DTSSRC      USR 
 
Here's the library list I have when connectioned to the SYSTEST subsystem.
The test subsystem itself forces the YSYSTEMST to the top:
 
Library     Type
YSYSTEMST   SYS 
YJOBD       SYS 
YSYSTEMS    SYS 
QSYS        SYS 
QSYS2       SYS 
QHLPSYS     SYS 
QUSRSYS     SYS 
EXTERMIN8   SYS 
Y1BAV       CUR 
QTEMP       USR 
DTSSRC      USR 
 
-----Original Message----- 
From: wdsci-l-bounces@xxxxxxxxxxxx on behalf of Joep Beckeringh 
Sent: Thu 3/3/2005 1:59 AM 
To: Websphere Development Studio Client for iSeries 
Cc: 
Subject: Re: [WDSCI-L] LPEX Editor for RPG IV



                 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
                 >
 
                 --
                 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.
 

-- 
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.