Important Notes

• APPX 4.0.2 is shipped with default language translation files. If you have modified these files, you will need to back them up before installing this release and restore them when the install is done. These files are in the $APPXPATH/0SA/Data/ directory and are DICTNARY.* LANGUAGE.* and XLAT.*.
• APPX 4.0.2 has a new file that must be created for the SCAN option to work right. If you are doing a fresh install, then this file is created automatically. Otherwise, you will need to Create System Administration files to get the new file created.
• Under APPX for Windows®, a RUN statement would spawn a Windows task that would run in parallel with the main APPX runtime thread. (APPX for Unix waits for the RUN to complete, before resuming execution.) RUN (under APPX for Windows) now uses the same syntax as the DOS "start" command. RUN now honors a "/w" switch, which waits for completion of the RUN object, before resuming mainline execution.

  Also, if /w is set, --- RETURN CODE will be set to the exit status of the program executed. (#3220)

Run-time

• Release numbers (stored in the application's PARAM file) are now visible from the popup detail window in the System Administration, Applications file. This allows the release number to be viewed for applications where the site does not have Application Design rights (such as the APPX 0app applications). (#4709)
• When there are multiple files to Scan from, the logic to select one has been improved over that which was in 4.0.
• User selection of file to scan and access path to use are now remembered in a permanent scan preferences file. These selections will be recalled and used as appropriate when the user scans on the same item in subsequent sessions. Note that changes to the process will cause these preferences to become obsolete and default selections will then be made.
• If 4.0.2 is installed as a new installation, the System Administration file, SCANPRF, will be created automatically. If 4.0.2 is installed over an existing APPX installation, you will have to manually create this file. (#4710)

• There is now an option in "Database Management" so that the following screen reporting data file errors can be remedied more conveniently.

• • "System Directory Record is Missing"
  • "File Does Not Exist"
  • "Restructure Required"

There remains a bug which will sometimes prevent the "Database Management" feature from running properly. If this occurs, running "Database Management" in the regular manner and selecting the file, should permit the necessary operation to run. (#4743)

• When SCANning on an Alternate Index, one could generate an: "Internal error has been detected, proceed with caution!" message. This was fixed in the 4.0 SCAN rewrite. (#4747)
• You could not scan from Query Setup, Record Selection if your query process is defined in an application with a version other than '00'. This has been corrected. (#4758)
• A drop down token scan box in the Java client now has a "--Select Path--" item included to provide for changing access paths. (#4763)
• When scanning from query select records and then using option-2, "Select Path", selecting an access path often resulted in the wrong one being selected. This has been corrected. (#4764)
• As an aid in tracking down USAGE file locking problems, for release 4.0.2, you can set APPX LS LOG=filename and APPX LS DBG=0x10 to cause Appx to log client-side locking operations to the given log file. (#4770)

Designer

• After completion of various database management functions (create files, verify integrity, verify files, etc.), a log can be produced with option-1. This log would sometimes incorrectly display the Application ID. It also did not include the Database ID. (#4700)
• If you create design files for an application and then immediately attempt to import the design files, you would not be able to import the PROCESS file. You would receive the error "File is Not Closed". This has been corrected. (#4701)
• In Database Management | File Specifications, "FMS Controls" and "Optional Path" could be improperly modified when executing the option "Restructure Files". This has been corrected. (#4741)

Enhancement

• The unix command, "kill -USR2 (pid)" can now be used to interrupt an APPX session. The APPX session will receive it as a "Direct Process 1" signal. This can be trapped for in Option Intercept and acted on accordingly. Previously, this technique worked only on BSD-based systems (such as HP-UX). It should now work on all Unix Systems.

  Previously the receiving process would act on the Direct Process 1 signal only after the user would next hit a key. This has been changed. It will now act on the signal whenever APPX is awaiting keyboard input without requiring the user to hit a key. (#4017)

External

• As of release 4.0.2, it is no longer necessary to double-up backslashes in a RUN statement. A backslash now only has special meaning if it immediately precedes a dollar sign, "$". Without a preceeding backslash a "$" is an indicator of a substitution in the RUN command string based on a PASS statement. A backslash preceeding a "$" tells APPX not to do a substitution but to allow the "$" to remain in the RUN command string. (#3315)
• When installing 3.5.2 for Linux, you would get upon startup:

  Error Opening Terminal: vt220

  Fixed in 4.0. Under 3.5, you can set up a symbolic link from /usr/lib/terminfo -> /usr/share/terminfo by performing the following as root:

  cd /usr/lib; ln -s /usr/share/terminfo terminfo (#4585)