Marc's Place


E$LNGW - Create a Work file

Start Command

e$lngw msgf(<library>/<messagefile>) [F4]

Call Parameters

msgf (a10/a10)
Library name and Message filename of messagefile of which to create a workfile.

Return Parameters


What it does

With this command you can create a work file E$LNGUPD filled with data from the message file. This file can then be transferred to your PC to be worked on in, for example, MS-Excel. Afterwards you can use E$LNGU to update message files with the changed or enhanced data. The work file E$LNGUPD has the following fields:

E$MSGK   Message ID (a7)
E$TEXT Message Text (a132)

A simple way to update existing Language Message Files is the follwoing:

  1. Fill the work file E$LNGUPD from a Language Message file.
  2. Load the file using ODBC into MS-Excel.
  3. Change the texts using find and change.
  4. When you are done, select the columns 1 and 2 and copy them to the clipboard.
  5. Start a plain ASCII editor and paste the TAB-delimited text.
  6. Remove the first line (column titles) and replace all TAB-characters with nothing using 'replace all'.
  7. Copy the textfile, using FTP or so, to the AS/400 into E$LNGUPD.
  8. Start E$LNGU.

Special Options



Here is an example of the steps described above.

First, create the work file:

Import the file using ODBC into MS-Excel, change what you want to change and copy the first two columns:

Start a plain ASCII editor and paste the TAB-delimited text:

Then, with FTP, upload it directly into E$LNGUPD:

Here is the DSPPFM result of E$LNGUPD:

And the last step is to start E$LNGU and choose the language of which the corresponding message file should be updated:

Go to download page
© 1997- Marc Vos (and others)   -   Privacy Statement   -    Contact Me

On this website, Google Analytics is used to track visitor statistics. These are anonymised data about the number of visitors, which pages they visit on this site, from which regions they visit, which web browsers they use, etc.. You will also see non-personalised ads via Google AdSense. Cookies from Paddle or Paypal are placed when you click on a 'Buy now!' or 'Donate!' button, and possible cookies from Disqus when you use that system to comment on one or more blogposts.
Privacy Statement