Changing Primary Langauges

I'm not sure that removing the requirement for a scratch install would
have been considered big enough to justify putting into the announcement
materials.  And I don't believe you'll find it in any of the various
manuals; rather the consideration of doing a scratch was removed from
various manuals.

I should clarify though.  What was removed was the need to scratch the
system, not the need to be aware of application data dependencies.  If
users had DBCS data in their files and then slipped a SBCS primary onto
the system then they are not going to be able to access the DBCS data
in any meaningful fashion (no DBCS displays, no DBCS printers, no DBCS
fonts, no DBCS parameters on various commands, etc.) though the data is
there on the system (though if they need to use the DBCS data I would
really have to wonder about their decision to go SBCS).  Changes to
OS/400 supplied files (such as cross reference fields going from
Open to Char) would take place as part of the install.

Bruce

>
>Hello Bruce,
>
>You wrote:
>>The need for scratch install was removed several releases ago (I think
>>in one of the V3 releases though I cannot find the exact release
>>quickly).
>
>That's interesting.  I missed that in the announcements.  So how does the
>system handle the case of a DBCS system with DB files containing OPEN data
>fields which have DBCS data in them and the user installs an SBCS version?
>What happens to the data?
>
>Just pointing me at the appropriate FM would be good enough but a precis
>would be better.
>
>Regards,
>Simon Coulter.
>


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---