The APPX 4.2.1 Patch Release addresses the following items:
- Bug 754: Design Transfer hangs on third Transfer
- Bug 803: APPX_PRINT on Unix doesn't spool to Unique properly
- Bug 807: Background Processing Fails
- Bug 808: PRINT FILE PATHNAME corrupted
- Bug 815: No "Acknowledge Delete" button for work fields
- Task 17: APPX_USAGE_BITS needs another one just for Session End
Bug 754: Design Transfer hangs on third Transfer
- Running Design Transfer several times in a row and scanning for the "From" process name each time caused a lockup on the third Scan operation. This has been fixed.
Bug 803: APPX_PRINT on Unix doesn't spool to Unique properly
- When spooling to Unique via appx_print, nothing gets into the Unique print queue. This is because the print file is deleted by appx_print before Unique can print it. We now don't delete the print file, we leave it there for unique to delete.
Bug 807: Background Processing Fails
- Background processing fails 100% of the time. Usage log shows 'Appx System Error (BI.C:1714) - An unrecoverable error has occurred (signal), exiting'. Background processing works again.
Bug 808: PRINT FILE PATHNAME corrupted
- The value of --- PRINT FILE PATHNAME has changed with 4.2 so that it now has a null 0x00 appended immediately after the pathname. All code that uses PRINT FILE PATHNAME as part of a RUN string now fails since the RUN string is truncated on execution at the 0x00. This has been fixed so that PRINT FILE PATHNAME works as it always has in the past.
Bug 815: No "Acknowledge Delete" button for work fields
- In Work Fields maintenance, in delete mode, there is no Ack Delete button on the screen. This has been fixed.
Task 17: APPX_USAGE_BITS needs another one just for Session End
- Under a minimal surveilance scheme I'd like to simply log the session start and end. Currently you can get the session start by itself by simply setting APPX_USAGE_BITS to 0x80000000. You won't get any end info unless you also set the lowest bit. Then you get every process that you ever run in addtion to the END of the first process that you executed when you started you APPX session. Should be fixed in 4.2.1 - use bit 0x200 to see session start and session end log entries
Refer to the APPX 4.2.0 Release Notes for all enhancements and corrections built into this major release.