|
midrange.com
Hi Rick,
I've done the library list manipulation before and it works great here so
long as I'm not trying to modify a part of a production process. Where it
gets tedious for us is if we need to change one piece of 20 piece process.
The ADDLIBLE approach means I have to copy and rename various stuff in order
to test a change to the middle of the string of objects.
Unfortunately our system-wide customized stuff is in a library in the
SYSLIBL which is always above stuff that gets added with ADDLIBLE. I'll try
to explain our setup below as simply as possible (no offense to anyone!). I
think this will help to explain why the ADDLIBLE command, doesn't work for
our situation.
Bruce
The way the setup works now from a green screen is:
1) Multiple IP addresses are active on a single server
2) TELNET exit program intercepts all TELNET connections
3) if a connection is coming in to IP address 89, a device name prefix of
SYST is forced
4) if a connection is coming in to any other IP address it defaults to
device name prefix QPADEV***
5) Subsystem QINTER will not accept devices starting with SYST but does
accept QPADEV***
6) subsystem SYSTEST only accepts devices starting with SYST
7) subsystem SYSTEST has SYSTEST in the systel library list parameter
This forces devices (or jobs) starting with SYST*** to have the SYSTEST
library as the very first library in the library list - up above the
SYSLIBL, CURLIB, and USRLIBL portions.
By doing it this way, I can work on enhancing our system processes (in a
SYSPROD library in the SYSLIBL portion of the library list) without having
to hard code any library names. I let it default to a library list search
and if I'm testing/developing something it finds it in SYSTEST other wise it
picks up the file/program/etc. from SYSPROD. Once I have something working
the way I want, I can just copy the source to SYSPROD and recompile - no
changes needed.
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx on behalf of
Rick.Chevalier@xxxxxxxxxxxxxxx
Sent: Wed 3/2/2005 3:56 PM
To: wdsci-l@xxxxxxxxxxxx
Cc:
Subject: RE: [WDSCI-L] LPEX Editor for RPG IV
I do have to manipulate the WDSc library list from time to time.
There is a library list item in RSE under the connection, iSeries objects,
your filter pool. You can add and remove entries from there. You can also
move libraries up and down in the list.
Is the test library added at sign-on now? I'm probably
oversimplifying but why not just use ADDLIBLE in the signon CL to put the
test library at the top of the library list?
Rick
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx]On Behalf Of Bruce.Vest
Sent: Wednesday, March 02, 2005 3:41 PM
To: Websphere Development Studio Client for iSeries
Subject: RE: [WDSCI-L] LPEX Editor for RPG IV
It's close. I can use something like this to get compiles to hit
the
correct job queue (one attached to our test SBS) but it doesn't get
the test
library above everything the way I can get an IP connected 5250 to
do.
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of Rick.Chevalier@xxxxxxxxxxxxxxx
Sent: Wednesday, March 02, 2005 2:48 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: RE: [WDSCI-L] LPEX Editor for RPG IV
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.
--
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.
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.
--
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 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.
