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



http://www-912.ibm.com/n_dir/nas4apar.NSF/$$v5r1?OpenView&Start=1&Count=30&E
xpand=20#20

-----Original Message-----
From: Dave Boettcher [mailto:DBoettch@xxxxxxxxxxxxxxxx]
Sent: Thursday, March 20, 2003 10:27 AM
To: 'CODE/400 Discussion & Support'
Subject: RE: Top Ten reasons to upgrade to V5R2 Code400


Violaine, 

I tried the link and access was denied.  ?? Is it just me??

Dave Boettcher

-----Original Message-----
From: Violaine Batthish [mailto:batthish@xxxxxxxxxx]
Sent: Thursday, March 20, 2003 12:13 PM
To: CODE/400 Discussion & Support
Subject: RE: Top Ten reasons to upgrade to V5R2 Code400


Hi Mark,

If you go to:
http://www-912.ibm.com/n_dir/nas4apar.NSF/
$$v5r1?OpenView&Start=1&Count=30&Expand=20#20
You will see the list of APARs opened against the V5R1 version of CODE.
I found 33 APARs marked as UR1, which means that the problem reported is
fixed in a future release.  For CODE, most of these are fixed in V4, unless
otherwise noted.

I also checked V4 APARs and I found that there were 8 fixes reported in V4
(but would also have applied to V5R1) which shipped in various service
packs of V4 and the fix patch that can be downloaded from the support web
page (link below)

It is also important to note that V4 Sp2 co-incides with the GA of V5R2M0
OS/400, and contains the V5R2M0 version of the verifier for ILE RPG and all
the V5R2M0 documentation for the ILE RPG language.

thanks,

Violaine Batthish
CODE Project Lead
batthish@xxxxxxxxxx          IBMCA(BATTHISH)


WDT/400 page:  http://www.ibm.com/software/ad/wdt400
WDT/400 Support : http://www.ibm.com/software/ad/wdt400/support



|---------+-------------------------------------------------->
|         |           Buck Calabro                           |
|         |           <Buck.Calabro@xxxxxxxxxxxx>            |
|         |           Sent by:                               |
|         |           code400-l-bounces+batthish=ca.ibm.com@x|
|         |           idrange.com                            |
|         |                                                  |
|         |                                                  |
|         |           03/20/2003 12:44 PM                    |
|         |           Please respond to CODE/400 Discussion &|
|         |           Support                                |
|         |                                                  |
|---------+-------------------------------------------------->
 
>---------------------------------------------------------------------------
--------------------|
  |
|
  |       To:       CODE/400 Discussion & Support <code400-l@xxxxxxxxxxxx>
|
  |       cc:
|
  |       Subject:  RE: Top Ten reasons to upgrade to V5R2 Code400
|
  |
|
  |
|
 
>---------------------------------------------------------------------------
--------------------|



Mark wrote:
>Hello.  We are on WDT V5R1.  So, Wdsc 4.0 is what
>I want to upgrade to.  I was hoping to get a list
>of some of the biggest bug fixes within the Code400
>part of the software.

I don't think such a list is available.  Be sure you are on the latest
service pack for V5R1 and you'll be in good shape.

>Since that is the only part I currently use, I need
>to justify the addition of memory to my machine.

As Edmund said, WDSC 4.0 is basically the "web" release.  The native
editor,
LPEX has very little support for RPG, etc.  So the lab includes Code in
with
WDSC 4.0.  There have been some Code fixes in 4.0, but I don't think there
are that many.  There are more Code fixes due in V5.0.  I wonder how long
IBM will continue to update and support the classic tools, as LPEX and RSE
become more mature?

The bottom line is that if you are a Code-only user, V4.0 has little to
offer, but V5.0 might!
  --buck
_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/code400-l
or email: CODE400-L-request@xxxxxxxxxxxx
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@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/code400-l
or email: CODE400-L-request@xxxxxxxxxxxx
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@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/code400-l
or email: CODE400-L-request@xxxxxxxxxxxx
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

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.