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



When I create a new connection, I get the (old) V36 libraries.  I've
rebooted before but Billy needs a new pony and I'll try again.  If that
doesn't work, I'll assume Sammie needs a new pony and re-IMPL tonight
(having a development machine is great).
I've sniffed around for some XML code with the WDSC configuration but
haven't found anything...

-----Original Message-----
From: wdsci-l-admin@midrange.com [mailto:wdsci-l-admin@midrange.com]On
Behalf Of Mark Phippard
Sent: Monday, October 07, 2002 2:08 PM
To: wdsci-l@midrange.com
Subject: Re: [WDSCI-L] Library list problems

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Right-click on the iSeries Commands subsystem and choose Properties.  You
can set the *LIBL using the Communications property.

I had forgot where this was too, but I remembered that the Create New
Connection Wizard talked about where it was, and that was how I found it.

Hope this helps,

Mark






"Reeve Fritchman" <reeve@ltl400.com>
Sent by: wdsci-l-admin@midrange.com
10/07/2002 01:57 PM
Please respond to wdsci-l


        To:     "Wdsci-L@Midrange. Com" <wdsci-l@midrange.com>
        cc:
        Subject:        [WDSCI-L] Library list problems


This is a multi-part message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
VERIFY isn't working; it can't find any files after I juggled my iSeries
library lists (from V36 to V37) over the weekend.  The files are now in
V37
but not in V36; the program(s) compile properly on the green-screen side
in
V37.

I've changed everything application-wise on the iSeries I need to,
including
job descriptions and startup programs (QUSRLIBL isn't used).  I've changed
my CODE autostart server library list, cleared the cache, and deleted the
CODE user spaces in my current library.  The QUSRWRK jobs that appear to
be
handling VERIFY tasks shows the right library list (V37) but the VERIFY
listing shows all V36 files and objects.

Then?*inspiration*: the library list is buried (like everything else)
somewhere in WDSC.  But I don't seem to have a connection defined to my
iSeries.  So I create a connection to my box, go through the steps, and a
connection is created?but the connection has the wrong (old) library list,
meaning there's something hidden somewhere in WDSC.

Now, I'm looking at the Server|iSeries Objects|Default Filter Pool|Library
list and haven't a clue how to change this "filter".  I've double-clicked,
right-clicked, and "Properties"'ed it for the last 30 minutes and remain
baffled.

Can anybody set me straight?

Thanks,
Reeve
--

_______________________________________________
This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
mailing list
To post a message email: WDSCI-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/wdsci-l
or email: WDSCI-L-request@midrange.com
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@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/wdsci-l
or email: WDSCI-L-request@midrange.com
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 ...

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.