There is no way to 'localize' XEQ parameters however for your example I have a couple of suggestions, either of which should yield what your want:

• Make your function into a multi-line function and use LOCAL there to localize the variables.
• Replace your whole function with def fnget_extension$(local filename$)=arg(sub(filename$,".",sep,-1),2)
  Basically the above replaces the last "." with a field separator then asks for the second argument.  If no dot was present there will be no second arg thus the logic will return "".
  

You must be running PxPus 2016 or earlier as this was addressed a few years ago.
Please update your system and try again.

If all you want to do is match the IOLISTs and file key definitions the easiest solution is to create a new temporary file from the Nomads Data Dictionary definition then compare:

• FIN(nn,"KEY_DEFINITION")
• IOL(nn:*)
• IOL(nn:^) If present
• IOL(nn:key) If present

To create a temporary file from the dictionary definition use:

CALL "*dict/dd_updt;Update_Physical", table_name$, temporary_file_path$,"",errmsg$

Just an update on this issue.  We got access to the panel James was having trouble with and noticed that a non-primary radio button (a button with an index other than one) had different On Focus logic associated with it.  This logic overrode the logic associated with the primary button (index 1) of the radio button group.

This type of situation can happen by creating a radio button, assigning logic to it, then using CTRL-D (or copy/paste) to duplicate it.  If you then rename this duplicate button back to the original group and set its index to some other value the system leaves the original logic on the duplicate button and it ends up overriding the primary buttons logic.  As this duplicate button is not index 1 you cannot edit/view the logic assignments in the Nomads designer.

We have added logic for PxPlus 2019 to avoid this from happening in the future.

If I understand your question the problem is that when running the application you want to receive some form of signal from the user to stop.   The challenge is doing this without having to "poll" the workstation looking for input.

One thing you could try would be to create a button whose CTL event is -1001 as this emulate a ESCAPE/BREAK being pressed.  You can thus simply create a small window in the center of the screen with this button then have a SETESC in your code trap the event to allow for an orderly exit.  If desired you could also include an animated GIF on the window to show progress to your user.

Personally though I would use the PxPlus progress bar utility and issue a call to it on a regular basis in your logic.  This provides not only a means to do an orderly shutdown but also a visual indication that work is being done.  There are two (2) options with PxPlus progress bars, one that allows you to display the percentage complete and one that just provides a ongoing progress display.  If you know how much of the work has been done I recommend the former option (the percentage complete bar).

BTW: It should be noted that the PxPlus progress bar has built-in logic to only update the screen every few seconds instead of every time it is called.  This helps overall performance which can be impacted by repeatedly screen updates.

I just ran these lines of code on our SUSE Linux server here and did not encounter any problem
(Windows 10, WindX PxPlus 2018 build 0002, SUSE 64 bit PxPlus 2017 build 2)

Problems like this should be reported to either our support desk if you purchased from us, or to your reseller so they can assist you and work with us on a resolution.
Once the nature of the issue has been determined we can provide an update here on the forum as appropriate.

Regarding your questions:

• The easiest way to disable/enable all radio buttons in a group is issue a DISABLE CONTROL nnn (or ENABLE CONTROL nnn) where nnn is the radio button CTL value. 
• To uncheck try setting the 'Value$ property to ""