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

Re: WDSCI-L Digest, Vol 2, Issue 288

Webfacing project hangs
   IBM iSeries support could assist you with your webfacing questions.
 Other things you can do is check to see if you have any Workstation
Type entries if you do then you need to add one for webfacing.  If
QINTER is all good to go the next step is to do a WRKACTJOB verify
that both QQF server jobs are active with no errors.   Next goto your
PC and hopefully you have WDSC v5.1 or better and you can go to your
RSE connection go down to iSeries Commands, rt click and do a verify
connection.  You will need all the PTFs for webfacing to make this
work.  Also when you goto Help-About Websphere... is your version at
v5.1.0.3?    So if you are all set to go change your JOBD to have max
logging set to 4 00 *SECLVL on the profile you are testing the
webfaced app with.   Finally if this still fails review the QQF server
jobs see if a virtual device is getting created.  If so do a WRKJOB
and see what the errors are within the joblog, this should help you
out.

On Fri, 23 Jul 2004 11:08:27 -0500, wdsci-l-request@xxxxxxxxxxxx
<wdsci-l-request@xxxxxxxxxxxx> wrote:
> Send WDSCI-L mailing list submissions to
>        wdsci-l@xxxxxxxxxxxx
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>        http://lists.midrange.com/mailman/listinfo/wdsci-l
> or, via email, send a message with subject or body 'help' to
>        wdsci-l-request@xxxxxxxxxxxx
> 
> You can reach the person managing the list at
>        wdsci-l-owner@xxxxxxxxxxxx
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of WDSCI-L digest..."
> 
> Today's Topics:
> 
>   1. Re: (re:) webfacing hang (Chip Milosch)
>   2. Exporting Settings (Buzz Fenner)
>   3. Re: Exporting Settings (Vern Hamberg)
>   4. Problem with the verify. (Kelly Cookson)
>   5. RE: Problem with the verify. (Kelly Cookson)
>   6. RE: Problem with the verify. (Bob Anderson)
>   7. RE: Problem with the verify. (Mike Tobey)
>   8. RE: Problem with the verify. (Bob Anderson)
>   9. RE: Problem with the verify. (Mike Tobey)
> 
> ----------------------------------------------------------------------
> 
> message: 1
> date: Thu, 22 Jul 2004 10:14:58 -0700 (PDT)
> from: Chip Milosch <cmilosch@xxxxxxxxxxxxx>
> subject: [WDSCI-L] Re: (re:) webfacing hang
> 
> 1. Webfacing, Do I need to republish? (mikesoucy1262@xxxxxxxx)
> 2. Re: Webfacing, Do I need to republish? (Mark Phippard)
> 3. RE: Webfacing, Do I need to republish? (Vitale, Daniel)
> 4. Re: Webfacing, Do I need to republish?
> (michaelr_41@xxxxxxxxxxxxxx)
> 5. Webfacing project hangs (Chip Milosch)
> 6. Re: Webfacing, Do I need to republish? (mikesoucy1262@xxxxxxxx)
> 7. Re: Webfacing project hangs (michaelr_41@xxxxxxxxxxxxxx)
> 
> ----------------------------------------------------------------------
> 
> message: 5
> date: Thu, 22 Jul 2004 07:54:14 -0700 (PDT)
> from: Chip Milosch
> subject: [WDSCI-L] Webfacing project hangs
> 
> I have an extremely simple webfacing project (one screen) :-)
> 
> When I try to test the project, it hangs after I click the logon button. I 
> think this is some problem with the creation of the QQF* virtual devices, but 
> I don't what to change or fix. Do the QQF* devices always create in QINTER? I 
> did add a WSE into QINTER for QQF*.
> 
> OS/400 V5R2
> WDSC 5.1.0.3
> 
> chip
> 
> ------------------------------
> 
> message: 6
> date: Thu, 22 Jul 2004 15:26:21 GMT
> from: "mikesoucy1262@xxxxxxxx"
> subject: Re: [WDSCI-L] Webfacing, Do I need to republish?
> 
> Thanks all! That's kind of what I thought but, I wanted to make sure.
> 
> ________________________________________________________________
> The best thing to hit the Internet in years - Juno SpeedBand!
> Surf the Web up to FIVE TIMES FASTER!
> Only $14.95/ month - visit www.juno.com to sign up today!
> 
> ------------------------------
> 
> message: 7
> date: Thu, 22 Jul 2004 12:40:14 -0400
> from: michaelr_41@xxxxxxxxxxxxxx
> subject: Re: [WDSCI-L] Webfacing project hangs
> 
> You don't need a WSE. What's the value of QAUTOCFG?
> 
> On Thu, 22 Jul 2004 07:54:14 -0700 (PDT), "Chip Milosch"
> said:
> > I have an extremely simple webfacing project (one screen) :-)
> >
> > When I try to test the project, it hangs after I click the logon button.
> > I think this is some problem with the creation of the QQF* virtual
> > devices, but I don't what to change or fix. Do the QQF* devices always
> > create in QINTER? I did add a WSE into QINTER for QQF*.
> >
> > OS/400 V5R2
> > WDSC 5.1.0.3
> >
> > chip
> > _______________________________________________
> > 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.
> --
> 
> michaelr_41@xxxxxxxxxxxxxx
> 
> ------------------------------
> 
> _______________________________________________
>                              Display System Value
> 
> System value . . . . . :   QAUTOCFG
> Description  . . . . . :   Autoconfigure devices
> 
> Autoconfigure device . :   1          0=Off
>                                       1=On
> 
> cmilosch@xxxxxxxxxxxxx
> 
> ------------------------------
> 
> message: 2
> date: Thu, 22 Jul 2004 15:17:20 -0500
> from: "Buzz Fenner" <bfenner@xxxxxxxxxxxxxxxx>
> subject: [WDSCI-L] Exporting Settings
> 
> I'm moving my user profile from one server to another and would really like
> to take along my RSE settings (member lists, custom commands, etc.).  I
> looked at the export options and I didn't see anything that seemed to apply
> to the situation.  Actually, I though I found a folder/file that had
> everything I needed but, honestly speaking, I think I was just dreaming...
> 
> Buzz
> 
> --
> PRIVACY WARNING: For auditing purposes, a copy of this message has been
> saved in a permanent database by the Net Integrator at jonesborocwl.org.
> 
> ------------------------------
> 
> message: 3
> date: Thu, 22 Jul 2004 16:19:31 -0500
> from: Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>
> subject: Re: [WDSCI-L] Exporting Settings
> 
> Buzz
> 
> Are you talking about server or your PC? When you get on the other server,
> just make a connection to it in RSE. All the other stuff will be there -
> these things are applied across all connections - a little thing some of us
> do not like, as the references may not point to anything on a different
> machine. (I think filter pools can do something about this, but I'm not sure.)
> 
> If it is about moving to a different PC, I have a PMR with IBM right now
> that is related to this - got a new PC and zipped up the workspace folder -
> now I can see the connections in RSE but they contain nothing. Support is
> looking to see how to move all this stuff in order to preserve these
> settings. I'll let the group know what I find out, if it works.
> 
> In my case, I had zipped a workspace from 5.1.0.2 (is that the right
> numbering?). I installed on the machine and updated to 5.1.0.3 before
> bringing the workspace back (unzipping it), so maybe there is something
> wrong in that order.
> 
> I had to zip the workspace. because I was copying to an external drive and
> got messages about the path being too long. I think I was only one level
> deeper than the product uses. Oy!
> 
> Vern
> 
> At 03:17 PM 7/22/2004, you wrote:
> >I'm moving my user profile from one server to another and would really like
> >to take along my RSE settings (member lists, custom commands, etc.).  I
> >looked at the export options and I didn't see anything that seemed to apply
> >to the situation.  Actually, I though I found a folder/file that had
> >everything I needed but, honestly speaking, I think I was just dreaming...
> >
> >Buzz
> >
> >
> >
> >--
> >  PRIVACY WARNING: For auditing purposes, a copy of this message has been
> >  saved in a permanent database by the Net Integrator at jonesborocwl.org.
> >_______________________________________________
> >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.
> 
> ------------------------------
> 
> message: 4
> date: Fri, 23 Jul 2004 08:52:15 -0500
> from: Kelly Cookson <KCookson@xxxxxxxxxxxx>
> subject: [WDSCI-L] Problem with the verify.
> 
> Last week our programmers attended a class where we all verified programs
> using the Verify option in the Source menu. This week, three of us could no
> longer verify programs, but one of us still can. (I've asked all programmers
> to try and let me know who can and who can't.)
> 
> For those of us who can't verify, here's what happens:
> We take the option, and a delay of several seconds occurs where nothing at
> all changes on the screen--no status bar or status message, nothing. If you
> look at the task manager, WDSCi is using about 90-99% of the CPU during this
> delay. Then the status bar finally comes up. The status bar runs endlessly,
> and WDSCi is using significant CPU, but the verify never ends. One
> programmer let the verify run for 20 minutes to see if it would end. Hitting
> the cancel button on the status bar does not end the verify. We have had to
> kill the WDSCi process manually using Task Manager.
> 
> We have not changed anything from last week to this week on our PCs.
> 
> Any ideas?
> Thanks,
> Kelly
> 
> ------------------------------
> 
> message: 5
> date: Fri, 23 Jul 2004 09:52:53 -0500
> from: Kelly Cookson <KCookson@xxxxxxxxxxxx>
> subject: RE: [WDSCI-L] Problem with the verify.
> 
> Update:
> 
> Programmers with new PCs (1G RAM, Windows XP) have no problems verifying
> source.
> 
> Programmers with older PCs (512 RAM, Windows 2000) can verify short ILE
> programs, but cannot verify long ILE programs or any OPM programs.
> 
> Should we even be using verify on OPM? And does verify require more than
> 512RAM for larger (over 150 source lines) programs?
> 
> Thanks,
> Kelly
> 
> -----Original Message-----
> From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
> Sent: Friday, July 23, 2004 8:52 AM
> To: Websphere Development Studio Client for iSeries
> Subject: [WDSCI-L] Problem with the verify.
> 
> Last week our programmers attended a class where we all verified programs
> using the Verify option in the Source menu. This week, three of us could no
> longer verify programs, but one of us still can. (I've asked all programmers
> to try and let me know who can and who can't.)
> 
> For those of us who can't verify, here's what happens:
> We take the option, and a delay of several seconds occurs where nothing at
> all changes on the screen--no status bar or status message, nothing. If you
> look at the task manager, WDSCi is using about 90-99% of the CPU during this
> delay. Then the status bar finally comes up. The status bar runs endlessly,
> and WDSCi is using significant CPU, but the verify never ends. One
> programmer let the verify run for 20 minutes to see if it would end. Hitting
> the cancel button on the status bar does not end the verify. We have had to
> kill the WDSCi process manually using Task Manager.
> 
> We have not changed anything from last week to this week on our PCs.
> 
> Any ideas?
> Thanks,
> Kelly
> _______________________________________________
> 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.
> 
> ------------------------------
> 
> message: 6
> date: Fri, 23 Jul 2004 11:08:47 -0400
> from: "Bob Anderson" <banderson@xxxxxxxxxxxxxxxxxxx>
> subject: RE: [WDSCI-L] Problem with the verify.
> 
> Kelly,
>        I have an old PIII with 512 RAM and Win 2000. I can verify a fairly 
> big ILE
> program but anything else doesn't even have the option to Verify.
> 
> Bob Anderson
> EDI Coordinator
> Kent Watersports
> banderson@xxxxxxxxxxxxxxxxxxx
> 419.929.7021 x315
> Fax 419.929.1380
> 
> -----Original Message-----
> From: wdsci-l-bounces@xxxxxxxxxxxx
> [mailto:wdsci-l-bounces@xxxxxxxxxxxx]On Behalf Of Kelly Cookson
> Sent: Friday, July 23, 2004 10:53 AM
> To: 'Websphere Development Studio Client for iSeries'
> Subject: RE: [WDSCI-L] Problem with the verify.
> 
> Update:
> 
> Programmers with new PCs (1G RAM, Windows XP) have no problems verifying
> source.
> 
> Programmers with older PCs (512 RAM, Windows 2000) can verify short ILE
> programs, but cannot verify long ILE programs or any OPM programs.
> 
> Should we even be using verify on OPM? And does verify require more than
> 512RAM for larger (over 150 source lines) programs?
> 
> Thanks,
> Kelly
> 
> -----Original Message-----
> From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
> Sent: Friday, July 23, 2004 8:52 AM
> To: Websphere Development Studio Client for iSeries
> Subject: [WDSCI-L] Problem with the verify.
> 
> Last week our programmers attended a class where we all verified programs
> using the Verify option in the Source menu. This week, three of us could no
> longer verify programs, but one of us still can. (I've asked all programmers
> to try and let me know who can and who can't.)
> 
> For those of us who can't verify, here's what happens:
> We take the option, and a delay of several seconds occurs where nothing at
> all changes on the screen--no status bar or status message, nothing. If you
> look at the task manager, WDSCi is using about 90-99% of the CPU during this
> delay. Then the status bar finally comes up. The status bar runs endlessly,
> and WDSCi is using significant CPU, but the verify never ends. One
> programmer let the verify run for 20 minutes to see if it would end. Hitting
> the cancel button on the status bar does not end the verify. We have had to
> kill the WDSCi process manually using Task Manager.
> 
> We have not changed anything from last week to this week on our PCs.
> 
> Any ideas?
> Thanks,
> Kelly
> _______________________________________________
> 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.
> 
> ------------------------------
> 
> message: 7
> date: Fri, 23 Jul 2004 10:20:59 -0500
> from: "Mike Tobey" <Mike.Tobey@xxxxxxxxxxxxxxxxx>
> subject: RE: [WDSCI-L] Problem with the verify.
> 
> Kelly,
> 
> I have 512 RAM and occasionally encounter the situation you have described.  
> I have found that this happens when I haven't cleared the cache in awhile.  
> Once I clear the cache the verifies run fine.
> 
> Mike.
> 
> -----Original Message-----
> From: Kelly Cookson [mailto:KCookson@xxxxxxxxxxxx]
> Sent: Friday, July 23, 2004 8:52 AM
> To: Websphere Development Studio Client for iSeries
> Subject: [WDSCI-L] Problem with the verify.
> 
> Last week our programmers attended a class where we all verified programs
> using the Verify option in the Source menu. This week, three of us could no
> longer verify programs, but one of us still can. (I've asked all programmers
> to try and let me know who can and who can't.)
> 
> For those of us who can't verify, here's what happens:
> We take the option, and a delay of several seconds occurs where nothing at
> all changes on the screen--no status bar or status message, nothing. If you
> look at the task manager, WDSCi is using about 90-99% of the CPU during this
> delay. Then the status bar finally comes up. The status bar runs endlessly,
> and WDSCi is using significant CPU, but the verify never ends. One
> programmer let the verify run for 20 minutes to see if it would end. Hitting
> the cancel button on the status bar does not end the verify. We have had to
> kill the WDSCi process manually using Task Manager.
> 
> We have not changed anything from last week to this week on our PCs.
> 
> Any ideas?
> Thanks,
> Kelly
> _______________________________________________
> 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.
> 
> ------------------------------
> 
> message: 8
> date: Fri, 23 Jul 2004 11:32:54 -0400
> from: "Bob Anderson" <banderson@xxxxxxxxxxxxxxxxxxx>
> subject: RE: [WDSCI-L] Problem with the verify.
> 
> Mike,
>        How do you go about clearing the cache. Inquiring minds with 512 RAM 
> would
> love to know.
> 
> Bob
> 
> -----Original Message-----
> From: wdsci-l-bounces@xxxxxxxxxxxx
> [mailto:wdsci-l-bounces@xxxxxxxxxxxx]On Behalf Of Mike Tobey
> Sent: Friday, July 23, 2004 11:21 AM
> To: Websphere Development Studio Client for iSeries
> Subject: RE: [WDSCI-L] Problem with the verify.
> 
> Kelly,
> 
> I have 512 RAM and occasionally encounter the situation you have described.
> I have found that this happens when I haven't cleared the cache in awhile.
> Once I clear the cache the verifies run fine.
> 
> Mike.
> 
> -----Original Message-----
> From: Kelly Cookson [mailto:KCookson@xxxxxxxxxxxx]
> Sent: Friday, July 23, 2004 8:52 AM
> To: Websphere Development Studio Client for iSeries
> Subject: [WDSCI-L] Problem with the verify.
> 
> Last week our programmers attended a class where we all verified programs
> using the Verify option in the Source menu. This week, three of us could no
> longer verify programs, but one of us still can. (I've asked all programmers
> to try and let me know who can and who can't.)
> 
> For those of us who can't verify, here's what happens:
> We take the option, and a delay of several seconds occurs where nothing at
> all changes on the screen--no status bar or status message, nothing. If you
> look at the task manager, WDSCi is using about 90-99% of the CPU during this
> delay. Then the status bar finally comes up. The status bar runs endlessly,
> and WDSCi is using significant CPU, but the verify never ends. One
> programmer let the verify run for 20 minutes to see if it would end. Hitting
> the cancel button on the status bar does not end the verify. We have had to
> kill the WDSCi process manually using Task Manager.
> 
> We have not changed anything from last week to this week on our PCs.
> 
> Any ideas?
> Thanks,
> Kelly
> _______________________________________________
> 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.
> 
> ------------------------------
> 
> message: 9
> date: Fri, 23 Jul 2004 11:08:10 -0500
> from: "Mike Tobey" <Mike.Tobey@xxxxxxxxxxxxxxxxx>
> subject: RE: [WDSCI-L] Problem with the verify.
> 
> Bob,
> 
> >From the menu bar:
> Window, Preferences, Remote Systems, iSeries, Cache.  The last option is to 
> "Clear the current cache".  Press clear and a confirmation window will pop 
> up, press OK and the cache will be cleared.
> 
> Mike
> 
> -----Original Message-----
> From: Bob Anderson [mailto:banderson@xxxxxxxxxxxxxxxxxxx]
> Sent: Friday, July 23, 2004 10:33 AM
> To: Websphere Development Studio Client for iSeries
> Subject: RE: [WDSCI-L] Problem with the verify.
> 
> Mike,
>        How do you go about clearing the cache. Inquiring minds with 512 RAM 
> would
> love to know.
> 
> Bob
> 
> -----Original Message-----
> From: wdsci-l-bounces@xxxxxxxxxxxx
> [mailto:wdsci-l-bounces@xxxxxxxxxxxx]On Behalf Of Mike Tobey
> Sent: Friday, July 23, 2004 11:21 AM
> To: Websphere Development Studio Client for iSeries
> Subject: RE: [WDSCI-L] Problem with the verify.
> 
> Kelly,
> 
> I have 512 RAM and occasionally encounter the situation you have described.
> I have found that this happens when I haven't cleared the cache in awhile.
> Once I clear the cache the verifies run fine.
> 
> Mike.
> 
> -----Original Message-----
> From: Kelly Cookson [mailto:KCookson@xxxxxxxxxxxx]
> Sent: Friday, July 23, 2004 8:52 AM
> To: Websphere Development Studio Client for iSeries
> Subject: [WDSCI-L] Problem with the verify.
> 
> Last week our programmers attended a class where we all verified programs
> using the Verify option in the Source menu. This week, three of us could no
> longer verify programs, but one of us still can. (I've asked all programmers
> to try and let me know who can and who can't.)
> 
> For those of us who can't verify, here's what happens:
> We take the option, and a delay of several seconds occurs where nothing at
> all changes on the screen--no status bar or status message, nothing. If you
> look at the task manager, WDSCi is using about 90-99% of the CPU during this
> delay. Then the status bar finally comes up. The status bar runs endlessly,
> and WDSCi is using significant CPU, but the verify never ends. One
> programmer let the verify run for 20 minutes to see if it would end. Hitting
> the cancel button on the status bar does not end the verify. We have had to
> kill the WDSCi process manually using Task Manager.
> 
> We have not changed anything from last week to this week on our PCs.
> 
> Any ideas?
> Thanks,
> Kelly
> _______________________________________________
> 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) digest 
> 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.
> 
> End of WDSCI-L Digest, Vol 2, Issue 288
> ***************************************
>

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.