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



Barbara,

I've been working this issue hard since our last volley of notes on 9/19.
(Much credit to Judy Tenney and Mike Smith in Rochester too, not to mention
a cast of other characters).  It looks like PTFs will be able to fix this
problem later this week to avoid recompilation.  Tentative numbers are
SI06526 and SI06497.   Needless to say, when these PTF's go final, they
will make the next cum, and I assume will go HIPER.

News at 11...

Al - at COMMON in Denver

Al Barsa, Jr.
Barsa Consulting Group, LLC

400>390

914-251-1234
914-251-9406 fax

http://www.barsaconsulting.com
http://www.taatool.com






                      Barbara Morris
                      <bmorris@ca.ibm.co        To:       
midrange-l@midrange.com
                      m>                        cc:
                      Sent by:                  Subject:  Re: V2R1 Bug Bites us 
at V5R2
                      midrange-l-admin@m
                      idrange.com


                      09/19/2002 06:34
                      PM
                      Please respond to
                      midrange-l






Al Barsa wrote:
> ...
> The bad news is that because of a bug in the V2R1 RPG compiler, and
because
> of a change to Level 40 security effective in V5R2, your programs
compiled
> in V5R2 may need to be recompiled.  The bug manifests itself with a
runtime
> MCH6801.  The only circumventions are:
>
>    Go back to level 30 - I don't recommend this
>    Recompile the programs in any release other than V2R1.  They could be
>    recompiled before or after V2R1, even on a System/38 (if you happen to
>    have one hanging around)
>

Al, the programs need to be recompiled on a release AFTER V2R1.  The
problem with the RPG compiler was there from the beginning, and was
fixed in V2R2.  Before V2R2, the RPG compiler generated code that
changed some storage that became write-protected at higher security
levels (40, I thought) in V2R2.  The RPG compiler was fixed to stop
changing that write-protected storage.

Your message should say

  The bad news is that because of a bug in the pre-V2R2 RPG compiler,
and because
  of a change to Level 40 security effective in V5R2, your RPG programs
compiled
  prior to V4R2 may need to be recompiled.  The bug manifests itself
with a runtime
  MCH6801.

Barbara Morris


_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-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.