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


  1.  Home
  2. WDSCI-L
  3. March 2005

RE: LPEX Editor for RPG IV

Thanks - hope your consolidation was smooth.  Ours has mostly been smooth.

-----Original Message-----
From: wdsci-l-bounces+bruce.vest=yellowcorp.com@xxxxxxxxxxxx
[mailto:wdsci-l-bounces+bruce.vest=yellowcorp.com@xxxxxxxxxxxx] On Behalf Of
rob@xxxxxxxxx
Sent: Thursday, March 03, 2005 12:21 PM
To: Websphere Development Studio Client for iSeries
Subject: RE: [WDSCI-L] LPEX Editor for RPG IV

I guess that "Seven Habits" course taught me something with the habit 
"Seek first to Understand".  Not that understanding means you have to 
agree.  :-)
Good luck there.
Glad that you found a workaround with the CHGSYSLIBL.
ps:  We combined 14 separate AS/400's for each manufacturing division on 
to 1 iSeries.

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 11:17 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






We've got a number of different environments today.  The bulk of our 
AS400's
are all setup the same.  One user environment per location, each location
having 1 (or 2) AS400's.  (Lucky ones having 2 with the second being a hot
failover.)

We've got a few systems now that have multiple user environments on them.
This is almost new concept here.  When management decided to put multiple
environments on a system with each area having it's own library lists
(another new concept), the only way I could get it to fit with their
approval was use the TELNET exit programs.  All 5250 connectivity is 
Client
Access TCP/IP based.  This let me use the telnet exits to force a specific
device name which in turn forces the specific subsystem, job description,
etc. allowing me to kill connectivity to an application by killing that
application's version of QINTER.  Also helps with performance monitoring,
etc.

I'd like to push them along at a faster rate but management can only 
handle
so many new concepts at a time.  ;)

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] 
On
Behalf Of rob@xxxxxxxxx
Sent: Thursday, March 03, 2005 10:08 AM
To: Websphere Development Studio Client for iSeries
Subject: RE: [WDSCI-L] LPEX Editor for RPG IV

I guess your argument could be to support an opening into the C/S, and 
web, world of programming.

There's probably a PHB somewhere that loves this system library list 
method because it forces all the teams to
- make sure they follow a strict naming convention on new workstation 
sessions
- so that they get into the right subsystem, thus breaking down divisions 
by subsystem
- so not only does the library list then work, but they can do stuff like 
kill a subsystem to lock out a division for backups, period end, etc.

Good luck.

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 10:27 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 Rob,

I'm actually in full agreement with you.  Personally, I don't see any 
reason
for more than a SINGLE custom library in the SYSLIBL - as you said, for
customizations of IBM commands typically found in QSYS.

This is an inherited setup.  This company has been using 400's since the
days of the S36 I think.  There have been a number of people come and go 
in
the systems team.  We've got 50+ systems scattered all over the 
continental
US.

I would like nothing better than to clean up a large part of this
environment (starting with LIBL issues)..  The hard part is convincing
management that the overall environmental setup on the AS400's needs
revamped because what worked great for a lot of years is not always a 
viable
approach to things anymore.  It took me a couple years before I could even
get an RPG IV syntax program into production because everything was in RPG
III and it worked.  This was about three years ago believe it or not.

The application guys still aren't allowed to use COBOL/ILE - they are 
stuck
with COBOL/400 limitations which means no true timestamp data type, etc.
They have to patch it together.  I'm S L O W L Y getting things changed 
but
its usually a fight until I can PROVE that I'm not breaking anything by
doing things "different".

Bruce

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] 
On
Behalf Of rob@xxxxxxxxx
Sent: Thursday, March 03, 2005 8:12 AM
To: Websphere Development Studio Client for iSeries
Subject: RE: [WDSCI-L] LPEX Editor for RPG IV

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.

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

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

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

As an Amazon Associate we earn from qualifying purchases.

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