#UniData#Windows#PrintingFor 32-Bit versions of UniData running on a 64-Bit version of Windows (i.e., prior to UniData 8) UDT.OPTIONS 116 was added to overcome a delay of around 60 seconds when executing the SETPTR with the DEST or AT options. The effect of turning UDT.OPTIONS 116 ON changes the user ID running the command to SYSTEM, as Spooler functions run faster as a SYSTEM user. After the spooler function completes, UniData switches back to the original user ID.
UDT.OPTIONS 116 should not be needed for 64-Bit versions of UniData. If you were previously running 7.2 or 7.3 versions of UniData and have upgraded to 8.2 you may have UDT.OPTIONS 116 ON to avoid the problem. Until a recent round of Windows updates leaving UDT.OPTIONS 116 ON was not problematic on a 64-Bit version of UniData other than all the print jobs that were created would be owned by SYSTEM not by the user that created them.
The following two articles discuss the change that Microsoft has made in the latest security patches.
https://answers.microsoft.com/en-us/windows/forum/windows_10-other_settings/cant-print-to-a-local-port-since-kb4586768-if-i/1738c856-73ff-4a79-835d-57957fa995f9https://support.microsoft.com/en-us/topic/november-10-2020-kb4586830-os-build-14393-4046-cc8a2d8c-4af6-576d-4f32-a3315bdb396eSo, what does this mean for UniData I hear you asking. If you have a printer assigned to a local port within windows (such as using a port to print directly to a file) with UDT.OPTIONS 116 ON and the latest Microsoft patches installed, you will no longer be able to print to that port. Setting UDT.OPTIONS 116 to OFF should correct the problem.
------------------------------
Jonathan Smith
UniData ATS and Principal Engineer
Rocket Software
------------------------------