Background Tasks Processing

This processing is used by Contracts, Invoices, Rental Return, Worksheet, Quotes, Inventory Adjustments.
It delays updating certain files, such as product, product location, and customer file, when the files are in use.
It completes the information in the background when the file becomes available.

The primary advantage of background processing is the prevention of record locking at the counter.
If the updating program gets a lock on a record, it will skip that product, location, or customer record, and will process it later in background processing.
The disadvantage is that customer information, product quantity information, and product location changes, are often not reflected in the product file for several seconds.

When Daily Close 2 is initiated, the program checks to ensure that background processing has been run within the last 5 minutes. To allow for locations in other time zones, this processing always uses the fileserver's clock.
If it has not been run within the last 5 minutes, the window opens to warn the operator that the process has not run, and requires that it be run before continuing.
Click the RUN TASKS button to initiate the Background Tasks, and contact Texada Support to ensure the complete process has been re-activated.

Note: For the SCS operator if the Background Task processing is not running a warning message is generated on the screen every 15 minutes when the operator changes menu options, as outlined in Background Tasks are Inactive.

Background Tasks can be tested by Texada Services staff using Create Test BKTX Transaction.

Background processing writes a report log when it is active, and when it encounters any errors.
The file is: /tmp/btxlog.mmdd (where mmdd is month and day run)

The background processing is handled differently for Windows and Linux or HP servers.

Linux or HP environments:
If your firm is having problems with the bus and task failing, BKTX and SCSCRON can be run from a session on the server using Scheduling and Process Console.

Windows environments:
In Windows the background tasks, scheduled tasks and background emailing use gateways, but if this is not running reliably the gateway services can be stopped and your system can be configured to use a .piv called by the Windows Task Scheduler to run the processes.
For details on configuring this alternate method refer to Windows BKTX, Job Scheduling and Emailing.