Using the command language variable

You can begin using English commands in an NLF session when you have the objects you need for your application. To do this, set the presiding language variable, DSQEC_NLFCMD_LANG, to English. This variable lets you switch between English and the presiding language of the NLF session.

Assuming your application is a procedure named WEEKLY_P, you would use the following commands:

"GET GLOBAL (CURR_LANG=DSQEC_NLFCMD_LANG"
"SET GLOBAL (DSQEC_NLFCMD_LANG='1'"
"RUN PROC WEEKLY_P"
"SET GLOBAL (DSQEC_NLFCMD_LANG=CURR_LANG"

These commands can be part of any valid QMF application, from an initial procedure to a high-level language program, but they must be in this order. The commands work in the following way:

Saving the presiding language value

The GET GLOBAL command saves the value for the presiding language in a variable called CURR_LANG. When that value is saved, you can reset DSQEC_NLFCMD_LANG to the value for English, 1.

Running your application

When your QMF session is set to English, you can run your English application. Any commands the user enters must be in English. However, if a user presses a function key, the underlying command is assumed to be in the presiding language.

QMF assumes that prompt panels are in the user's presiding language. For the EXPORT and IMPORT command prompt panels, the default file type is in the presiding language, too.

If the NLF provides uppercasing options in the profile, QMF adheres to the user's presiding language option, even when the user runs English commands.

Returning to the presiding language

After your application ends, you should reset the command language variable to the original value.

[ Previous Page | Next Page | Contents | Index ]