Re: Code/400 STRCODE question....

Why does IBM do this.  Why has IBM tied a client development tool to the server
OS version?  Do you have any idea how long it takes to upgrade 50, 100, 200+
developer PC's?  Do you think it would happen the same day OS400 is upgraded?
WDSc isn't an upgrade - it's a new product!  That means training!  That means PC
upgrades!  Not only does it take a long time to do but it adds little value
compared to the great expense involved with upgrading PC's, training people, and
lost productivity in the meantime.

Where I work we're in the middle of rolling out WDTS 5.1. Because it was the
released version when we started.  The group responsible for the servers are
planning to upgrade the servers to V5R2 in the spring.  Oops!  Do think
management will say "Oh.  Bummer.  Don't worry about it."  No, they'll say "Why
didn't you know this? You're fired."

Jon Paris says SEU and PDM is dead.  Not when this happens!  SEU will have to be
used for such a long time after upgrading to V5R2 that we may never be allowed
to go back to an IBM gui editor.

This is unacceptable.  WDTS 5.1 should run at least on all V5 releases.

What is the recommended solution if you have both V5R2 and V5R1 and V4 servers
that you support?!  Buy a second PC?  Dual boot?

Toronto.  Americans are known to be lousy with geography.  I guess it's true
because I always thought Toronto was in Canada but apparently Toronto is on the
Moon.

Phil Groschwitz
> Hi Steve,
>
> The V5R1M0 version of WDT (and CODE) does not support the V5R2M0 version of
> OS/400.
> For V5R2M0 support, you must install WDSC 4.0 and SP2, which coincided with
> the GA of V5R2M0 OS/400.
> You should have received CDs of WDSC 4.0 with your host CDs.
>
> thanks,
>
> Violaine Batthish
> CODE Project Lead
> batthish@ca.ibm.com          IBMCA(BATTHISH)
>
>
> WDT/400 page:  http://www.ibm.com/software/ad/wdt400
> WDT/400 Support : http://www.ibm.com/software/ad/wdt400/support
>
>
>
>
>                       Steve Cross
>                       <SCross@clippergr        To:
> "'code400-l@midrange.com'" <code400-l@midrange.com>
>                       oup.com>                 cc:
>                       Sent by:                 Subject:  Code/400 STRCODE
> question....
>                       code400-l-admin@m
>                       idrange.com
>
>
>                       12/20/2002 03:04
>                       PM
>                       Please respond to
>                       code400-l
>
>
>
>
>
> This message is in MIME format. Since your mail reader does not understand
> this format, some or all of this message may not be legible.
> --
> [ Picked text/plain from multipart/alternative ]
> Hello,
>
> My company upgraded to OS/400 V5R2, so I upgraded CODE/400 to V5R1.  Now
> when I issue the debug command through CODE/400, the message box says that
> no interactive STRCODE sessions are available for debug.  So I go to the
> AS/400 screen and issue the STRCODE command with these parameters. STRCODE
> RMTLOCNAME('192.168.1.247') CMNTYPE(*TCPIP) PORT(*DFT).  It starts to
> process, but I get another message box on my PC stating: EVF4025E -
> Communication Daemon  Handshake information from the host server contains
> errors.  Connection request from 'the AS400 IP' had been ended by the
> daemon.
>
> Any ideas what I am doing wrong?  At first when I installed CODE/400 that
> shipped with V5R2, I couldn't communicate with the AS/400.  Dr. Watson (Win
> 2K) kept dumping my programs.  So I installed CODE/400 SP5 and now I can
> use
> CODE/400 to program, compile, verify, etc.  I can also use Code Designer on
> DDS without any problems.  I just can't debug anything, and until I get the
> STRCODE command to work, I can't use STRCODECMD to initiate CODE/400 from
> the AS/400 side.
>
> Thanks in Advance,
>
> Steve Cross
> Sr. Programmer Analyst
> Clipper Group
> (630) 739-0700 Ext 102
>
> _______________________________________________
> 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.
>
> NOTE: WDSc for iSeries disucssion has it's own mailing list.
> Information can be found at
> http://lists.midrange.com/cgi-bin/listinfo/wdsc-l
>
>
>
>
> _______________________________________________
> 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.
>
> NOTE: WDSc for iSeries disucssion has it's own mailing list.
> Information can be found at http://lists.midrange.com/cgi-bin/listinfo/wdsc-l
>