E. Crane Computing Support Forum

NRothschild

Guest

Re: Migrating to PB10; external function calls

Phil,

I am starting to test a migration of my apps from PB9 to PB10 and I am looking at the unicode issue with external functions.  I initially did what you suggest in your various documentation;  I exported source from my PB9 app and bootstrapped into PB10 with PGen.  I wanted a "fresh start" with new PBLs.  I then started tripping over all the unicode issues since all my external function calls were broken.  I then learned, via the PB10 docs, that the PB10 migration automatically adds the ALIAS clauses that are required to fix the unicode problem.  Apparently PGen 6.0 does not do this.

If I am correct that PB10's migration takes care of this but PGen does not, I think you should update your tips web page and other documentation to suggest that PGen NOT be used to migrate PB9 source to PB10.  I personally don't have a problem with PGen not taking care of this.  I can accomplish the same thing by bootstrapping new PBLs into PB9 and then doing the PB migration, which will give me the best of all worlds.  You should make this clear, though, in your documentation; I'm sure many others will stumble over this issue, which cost me a needless day of time.

Regards,
Neil

NRothschild

Guest

Re: Migrating to PB10; external function calls

I want to add that I believe that PB10 will add the ALIAS FOR clauses by doing a miration from the System Explorer Tree Panel (or elsewhere) after a PGen bootstrap.  I was a bit confused between various iterations of the migration that I performed.  I still think it may be helpful to add some comments to the docs since this is an important issue unique to this new PB release.  It is important to do a migration after a bootstrap from source code generated in a prior release.

Regards,
Neil 

Phil

Guest

Re: Migrating to PB10; external function calls

Hi Niel,

I agree that this is worth a note in the documentation and elsewhere.

As a point of clarification, PowerGen has never attempted to make syntax changes when it imports objects.  The "Alias for" clause is an example in migrating to PB10, but there have been required syntax changes for earlier PB versions that wouldn't have been performed by PowerGen either.

Thanks for pointing this out.

Regards,

Phil

NRothschild

Guest

Re: Migrating to PB10; external function calls

Phil,

I understand and agree that PGen does not change source, nor should it.    The docs are needed for people like me that dive into new releases without reading all the PB release notes :-)  The fact you do NOT modify source and therefore do not "migrate" apps in the context that PB does should also be noted.

Regards,
Neil