At 09:22 PM 5/19/98 -0700, Darlene Brengle wrote:
>The info I received from all the gracious folks on the list regarding 
>logical files was the perfect solution until today when I found out that not 
>all the 
>sites are moving from a System 36 to an AS/400 at the same time. Some will 
>stay on the 
>36 for awhile. The very sticky problem is that some files are shared by sites. 
>sites that are not upgrading now need the multiple record type files and the 
>sites that 
>are upgrading need the multiformat logicals with separate physical files. They 
>do not 
>want to run in the 36 environment on the AS/400. Are there any other options?


If what you are saying is that the S/36 sites need to access the AS/400 data, 
this should not be a problem if you use DDM. The AS/400 FMTSLR program should 
take care of record adds and automagically put the data in the correct physical 
file. Some minor program tweaks may be necessary to prevent data decimal 

If you are saying that you need to run the same code on S/36 and AS/400, you 
are probably limited to the S36EE until all sites are ready to move to AS/400, 
as there are a fair number of differences between RPG3 and RPG2, as you have 
already observed. In this situation, it may be worth investigating what it 
would take to run SSP on the AS/400 as a "personality". I have not done this, 
so I can't shed much light on it, other than that it effectively gives you a 
partition on the AS/400 that is a real System/36, complete with WSU capability, 
assembler, VASP and all that other 36ish stuff.


Pete Hall

| This is the Midrange System Mailing List!
| To submit a new message, send your mail to
| To unsubscribe from this list send email to
| Questions should be directed to the list owner/operator:

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by 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].