Re: RE: Changing *module 'LITERAL POOL'

> If you're that hot on internationalizing your programs, why not simply put
> all your literals into a structure that can be overlaid by loading a
> *USRSPC on top of it, then write a simple program for loading translated
> values into that *USRSPC?
>
> That, along with providing DDS source for most of the display files, is
> how QuestView internationalization works.
>

I agree with you, James.
That's what we do for new or rewrotten program (except we store literals
into *usridx instead of *usrspc).
But we have tons of older programs (and our customer too) that wheren't
designed with translation in mind.

I just feel frustrated in that those literals are clearly separated from
code into modules and pgm/srvpgm and I can't reach them !
Most of the work (literals extraction) has already been done during module
creation and we can't reuse that work.

Unfortunately it seems the only solution is to work at the source level :
parsing different HLL langages, analysing /copy, modules, srvpgm used... and
other creation options, and externally files used for creation, etc  . Not
very hard, but very tedious. especially if you have in mind that the job has
already been done.
Too bad
To IBM guys : an API would be welcome and greatly appreciate ;-) !

Since analyzing sources seems the only solution, maybe it's time for us to
really externalize literals instead of only replacing them.

Thanks to all of you for your advices full of wisdom and your patience.

regards

jmp