RE: CPO work properly on Win2K?

Chris, you have one of your key terms wrong: it's "dain bramage".  Me?
CODE/400 triggers manic-depressive episodes.  Warning: opinions follow.

1. CODE/400 offers a great increase in programmer productivity, and I bitch
because I have to go back to SEU too often.
2. CODE/400 is a complex product supported by both Rochester and Toronto.
Do you think we have a problem here?
3. CPO: you may have to uncheck "Cache" to get things working the first time
after you set up a project.  Once you have a list built, you can cache it
and refresh from the cache'd list.  But if there's nothing in the list, you
can't refresh.  I think this is not working right.
4. 2.5 SP's for CODE/400 V5R1.  SP3 was released but is defective, so use
SP2 and don't complain.  We're all waiting for a corrected SP3, due any day
now.
5. Make sure your bad-end, oops (Freudian or not?), back-end PTF's are on
your iBox.
6. "OS400A" is some kind of funky internal default host server name; some
internal table must get corrupted and this is what shows up.  When it pops
up in the application, I go into the Comm console and click on the real
server.  That refreshes something somewhere and things work.
7. I've used CODE/400 on a LAN, on a WAN, and on a dial-up.  LAN generally
works very well (as in "nearly flawless").  WAN (cable modem) and dial-up
suck: unstable, frequent lockups, frequent lost connections, constant
aggravation; there is a fix in SP3.
8. When all else fails: (1) go to your tasks window and kill all the EVF
jobs.  (2) C:\WDT400\CODEEDIT /CM EXIT (parms must be upper-case).  (3) Go
back into your communications console and click on the server, then OK.  (4)
WRKOBJLCK {file} *FILE {member_name} to release any object locks.  (5) In
CODE/400, go to Options|Autosave, set to 1 minute/5 changes, check "Accept
settings".  (7) Save you work frequently to the iBox.
9. I believe the Toronto software labs (these folks aren't a direct part of
the iSeries team) are committed to the product and do the best they can with
the resources they're allocated; I believe the rest of the Midrange Server
Group could shive a git about this product and what is means to application
developers (the people who put the System/38 and AS/400 on the map).  As
long as LPAR and Linux are making waves, the iSeries marketing team has done
its job.

HTH,
RF

-----Original Message-----
From: code400-l-admin@midrange.com [mailto:code400-l-admin@midrange.com]On
Behalf Of Chris Proctor
Sent: Friday, October 05, 2001 11:39 AM
To: Code/400 Listserv
Subject: CPO work properly on Win2K?

Hi all!

I am really starting to experience some really wierd things with
WebSphere Dev Tools V5R1. Here's a couple of problems:

1. I add a server via the comm console called DEV. Then I add a CPO,
using that server and it doesn't find any objects in that AS/400
library. So, I thought, "Ok, maybe I have to end the daemon and restart
the communications. I EVEN went so far as to reboot my machine.  When I
went back into that CPO, and tried to add a member filter the DEV server
was not an option, it was changed (in the comm console to
OS400A!!!!!!!!Auuuuggggghhhhhh!!!!). So, I tried adding the filter
anyway and NO members were found!!
2. So, I went into an existing CPO and pulled it up. I clicked on a
member filter that already exists and it displayed the members from
another source file in the same library. NOT the ones associated with
the filter!!!

Has anyone else experienced this kind of brain damage? I'm just about
ready to delete the whole #@$%$ thing from my system! It's very
frustrating when I can't get any work done using these "helpful" tools!
It works great (most of the time) on my NT PC at work, just not here at
home. I just loaded it off the CDs that were sent to me. Are there any
SPs for V5R1? BTW, the AS/400s are V4R5.

Thanks for ANY assistance!

Chris Proctor
Gart Sports
Denver

_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l
or email: CODE400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.