Re: S/36 to AS/400 conversion tools and Y2K tools

Hey Guys !
Thanks
I am fine for  what I need right now  -just int he process of replying  and
the note got away  with  just one word  (then the infamous Oops send key).

 I Tend to agree with  both your conclusions

At 04:38 PM 10/1/97 +0000, you wrote:
>Carl H. Gerlach wrote:
>> 
>> Glenn:
>> 
>> I can't make a recommendation on converting S36 code to native 400,
however I would like to inquire if you were able to consider leaving your
S36 code as-is and run it on an Advanced 36 or a AS400 with OS400 v3r7 or
better with SSP. The speed is incredible. You also can share the data with
OS400 rather nicely.
>----------------------<snip>-------------------
>I'll second that.  Unless the S/36 code was designed with the AS/400 in
>mind, converting code to native would give you little, if any, benefit
>over running a S/36 environment.
>
>If you have very clean source members for let's say the input specs of a
>file, you could write a program in an afternoon which would create a
>bare bones file DDS, but sooner or later you would want to make
>reference to a data dictionary, add edit codes, validity checks, etc.
>and I don't know of any conversion tool which does that.  The S/D screen
>specs automatically create display file DDS, again without dictionary
>references.
>
>See if you can get a copy of RedBook GG24-3250-x "System/36 to AS/400
>Application Migration" and GG24-3304 "Converting System/36 Environment
>Applications to Native AS/400".
>
>The migration aid is a S/36 software product which would create a list
>of programs to compile and produce an audit report of the progress.
>
>James W. Kilgore
>QAPPDSN@ibm.net
>+---

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---