Automatic Job Scheduling

Certain maintenance and reporting jobs can be setup to run automatically at specific times from a Linux or Windows network.
The listing of these jobs can be maintained in this schedule, by job name, occurrence, time, and printer. The last date and time that the job was run is also displayed.

Automatic Job Scheduling can be maintained in the window in the "General Settings" on the System tab of the Configure System Settings.
An operator must be assigned a Security Role that allows permission to the System - Automatic Job Scheduling in order to access this table.

Some of these cronjobs, such as those collecting data for the utilization reporting, record a "Snapshot" of the status of each product at a regular pre-determined data capture date and time.
The "Snapshot" job does not require a printer, as a file is created but no output is actually produced at that time. The output can then later be generated as a report or email from Rental Utilization Reports, or Dollar/Time Utilization, or as a report or email from other jobs setup in Background Tasks Processing.

In a Windows environment if the gateways are not proving reliable running the job scheduler, refer to the section for Windows BKTX, Job Scheduling and Emailing which outlines the configuration for using the Windows Scheduler to perform these tasks.

This prompts to setup the schedule are:

FUNCTION NAME

Leave this field blank to view all scheduled jobs, or enter the job or function name, or select a job from the drop-down list.

Programs that can be setup in the Automatic Schedule include:

• AEMP01A (equipment data tracking import)
  - for Import AEMP Telematics as configured on the AEMP Telematics tab of Software Integration and an email alert of the import success or failure is sent to the address defined in AEMP Telematics
  (can be run manually using Import AEMP Telematics)

• ARAR33A (credit capture action)
  - to Capture Credit History that can only run the first day of the month to capture last month history

• ARCF21A (recalculation maintenance job)
  - to recalculate totals as explained in Reset Customer Balances

• CMFE02 (email trigger)
  - to generate Follow-Up emails to Salesman or Division Contacts from Customer Contact Information

• CMSF10 (follow-up update action)
  -to copy Follow Up comments from System Assigned Follow Up to customers matching Profile Class/Code in Customer Contact Information

• CRVU01 (utilization capture action)
  - for Vehicle Utilization snapshot (Car Rental System)

• FCRT02 (create empty temp files)
  - re-create empty temp files as listed in the Re-Create Temporary Files

• GLCN80A (request Playdata update)
  - triggers a request to have the data files from the primary (live) company copied to the playdata (practice) company the next time that the refresh task is executed on the SaaS server, as explained in the Request SaaS Playdata Refresh (but without the interactive prompts)
  This job only applies to companies in the Saas environment and does nothing on other systems

• REM_JUNK (clear bad characters)
  - cleans up Customer names & addresses, Customer notes, Contact names & addresses, Contact notes, and document header & detail notes on Contracts, Quotes, and Reservations, by removing junk characters.

• ROUSE02A (Rouse export & email action)
  - for Rouse Analytics that should be set up to run Daily to the email the address defined on the Rouse Analytics tab of Software Integration
  (can be run manually using Export Rouse Analytics)

• OPNEDG8A (capture OpenEdge transactions)
  - captures Texada Pay transaction data from OpenEdge server to compare with SRM's data in Texada Pay Reconciliation

• RSDC24(cleanup blank contract billing dates)
  - to cleanup blank contract billing dates where there is an accumulated invoice amount but no Bill Thru date, preventing further cycle billing

• RSDU01 (utilization capture action)
  - does the Revenue Accrual capture for Dollar/Time Utilization reporting used in the Dollar Utilization By Group and Dollar Utilization By Tool reports
  - failure can be reported by RSTU04 to addresses defined in Failed Data Capture Email List

• RSFR90A (cleanup action)
  - to delete all Off-Rental Transactions for Contracts in history in Purge Old Off Rental (no cut-off date)

• RSIL57A (RSIL cleanup)
  - to delete all RSIL Transactions with zero quantity for Sales Products and Non-Bulk Rentals in Locations as outlined in the Remove Quantity 0 From Locations utility.
  All locations are considered.

• RSPF113B (price update action)
  - for Update Non-Bulk Rental Selling Price using a percent of revenue as setup in Groups

• RSPF132 (update Status Codes)
  - to refresh Status Code changes for all Non-Bulk Rental Products including changes to the system-assigned-reserved status codes and also to the user-defined product status codes maintained in Product Status Codes

• RSPFS01 (suspension update action)
  - to Take Products Off Suspension in the Product Suspension Information according to days set in Company Inventory Parameters

• RSPO91A (recalculation maintenance job)
  - to recount Quantity on Purchase Order per Recalculate Quantity on P.O.

• RSRF16A (new rate update action)
  - to Update Rates to New Rates in the Rate Structure according to the "New Rate As Of" date in the expanded rate details for the product or group, or as setup by the Rate Increase/Decrease Utility utility, and to clear the previously "pending" rate change fields

• RSRH98A (reservation purge)
  - to delete old reservations that have no deposits, according to the value defined in the Auto Purge Days field in the Company Reservation Parameters, and write an audit record to the Delete Log for RSRH98A

• RSRQ91B (recalculates product quantity maintenance job)
  - to recount Quantity on Contract/Reservation/Order per Recalculate Inventory Availability

• RSRQ93 (recalculation maintenance job)
  - to reconstruct the product bookings table using Rebuild Requirements
  - when the program is initiated generally all current users are "killed" to avoid record locking
  - an environment variable can be set so that it will not disable all sessions (export RSRQ93_KILLALL=N)

• RSTU01 (utilization capture action)
  - does the On Hand count capture for Dollar/Time Utilization reporting and optionally used in the Rental Age Report
  - failure can be reported by RSTU04 to addresses defined in Failed Data Capture Email List

• RSTU02 (utilization capture action)
  - does the On Rent count capture from contracts and invoices for Dollar/Time Utilization reporting and optionally used in the Rental Age Report
  - failure can be reported by RSTU04 to addresses defined in Failed Data Capture Email List

• RSTU04 (email trigger)
  - to generate email validation for Dollar/Time Utilization reporting to addresses defined in Failed Data Capture Email List for Dollar/Time utilization cronjob "snapshots" RSDU01, RSTU01 & RSTU02.

• RSUS01 (utilization capture action)
  - captures the Utilization by Status code snapshot for Rental Utilization by Status Code

• RSUS02D (email trigger)
  - to generate emails for the Rental Utilization by Status Code (RSUS01) snapshot to the addresses defined in Utilization Report Email Addresses

• RSUS02E (print trigger)
  - to generate printed output from the Rental Utilization by Status Code (RSUS01) snapshot:

  • For Linux: to the divisional printers defined in Rental Utilization Report Setup or if no divisional printers defined, to the printer defined on the second detail line of the CRONJOB record
  • For Windows: to the single printer defined on the second detail line of the CRONJOB record (no Divisional Printing respected)

  Note: In Windows environments the Alternate Printers table in Rental Utilization Report Setup must be empty so as not to cause print failures that could halt the CRONJOB.

• SCS96E (email trigger)
  - to generate an email report on the previous month's peak user license count as reported in Peak License Usage Details to the email address defined in the Windows directory for the appropriate .ini file

• SCS96F (email trigger)
  - to generate an email report on the previous week's peak user license count as reported in Peak License Usage Details to the email address defined in the Windows directory for the appropriate .ini file

• SCSCRON3 (maintenance test job)
  - to initiate SCSCRON status check

• SFEX01(export action)
  - for Web Services to export all records not yet marked as processed as outlined in Web Services Overview

• SMCR99 (auto-reporting service)
  - that generates and emails various reports configured in Automatic Reporting to the email addresses defined for each report

• SMRTE01A (SmartEquip export & email action)
  - can be set up to export and ftp inventory information to SmartEquip and to email success/failure to the address defined on the SmartEquip tab of Software Integration
  (can be run manually using Export Inventory to SmartEquip)

• TXER01 (Portal reporting service)
  - that generates and emails various Subscribed Reports for Portal Customers to the email addresses setup in the Customer Internet Information

• WSQUEUE1 (Web Services cleanup)
  - can be used to clean up any temporary working files that are more than 2 hours old, that are used by web services such as SmartEquip and Texada Web when activated from Software Integration.
  Some of these files include: WSQUEUE, WS016, WS017, WS017, WS019H, WS019D

• XML Exports:
  If the Directory defined in the XML Data Exports in the Company Daily Close Parameters is not valid, the XML Export jobs will fail.

  • XMLEX13A
    - to generate an XML file for a range of vendor records for XML Data Exports as outlined in Export Vendor Information

  • XMLEX14A
    - to generate an XML file for a range of open warehouse receiving transactions for XML Data Exports as outlined in Export Warehouse Receipts

  • XMLEXP4A
    - to re-generate an XML file for the A/P invoice file for XML Data Exports as outlined in Export A/P Invoices

    * Note: If XMLEXP4A is included to be run automatically in the Automatic Job Scheduling then the corresponding export will NOT be triggered by the Daily Close posting process as well.

  • XMLEXP5A
    - to re-generate an XML file for the A/R invoice file for XML Data Exports as outlined in Export A/R Invoices

    * Note: If XMLEXP5A is included to be run automatically in the Automatic Job Scheduling then the corresponding export will NOT be triggered by the Daily Close posting process as well.

  • XMLEXPAA
    - to generate an XML file of customer balances for a range of customers for XML Data Exports as outlined in Export Customer Balances

This list of functions is maintained by Texada Software.
If your firm would like additional reports to be available, please contact Texada Support to discuss programming options.

Diagnostics:
The SCS operator can click on the icon to view the log as outlined in SCSCRON Log

SCHEDULED JOB LIST:

SEQ#

Sequence numbers are automatically assigned to track and organize the records in the file.
Multiple records can be entered.

JOB NAME

The program or function name displays.
To add a new job, enter the function name or select it from the drop-down list.

DESCRIPTION

The program, report, or job description displays.

DAY

Window to view the scheduling options:

• Enter 01 to 31, to execute the job on a specific date each month.
• Enter the first 3 letters of the day of the week, to execute the job on a specific day of every week.
• Enter DAY to execute the job once a day.
• Enter ONE to execute the job one time only.

TIME

Regardless of the location time zone, all jobs run as of the files server's clock.
Enter the server time, using a 24 hour clock, that the job should be initiated.

Window to access the Time Conversion window to view the current server date and time.
Enter the local time for the job to be run and the screen will also display the converted server time at which the job will be run.

NEXT RUN

The date that the program will next be run is displayed.
This is calculated according to the Day information.

LAST DATE

This field displays the date that the job was last run.

LAST TIME

This field displays the time that the job was last run.

PRINTER

Enter the printer code or select a system printer from the window.
This prompt does not appear for System Call Commands.

COMMAND

This prompt only appears for System Call Commands.
Enter the system command to be run at the scheduled date and time.

Expanded Record

Click EXP/CON button to view the additional information including:

DISABLE IN PLAY

Automatic Job scheduling is usually not configured for Playdata, and to prevent confusion in reporting only three functions can be run from Play data including REM_JUNK, SCSCRON3, and WSQUEUE1.
All other functions are disabled in Play.

Check this box if this report should NOT be generated in the Playdata or Pre-production companies.

• A PlayData company is identified when the data directory name contains the word "play".
  
• A Pre-Production company is identified when the data directory name contains the word "pre".

Uncheck this box to cause the report to be generated in both the actual and the test/play company.

LAST RUN FINISHED

Displays the completion date and time for the last time that the job was run.

Finished ?

Click ACCEPT to accept the records and again to close the screen.

When the accepted list is re-accessed, it is re-sorted alphabetically by function or job name.

Email Output:
The email address used to post the results of some of the automated jobs, can be setup in the window on the Email field in Automatic Reporting, or as defined for each job above, or the default can be setup in Company Miscellaneous Parameters.

Note: Some reports are emailed in spreadsheet format, and if the resulting file is not recognizing the file association and is opening in a browser instead of Excel, open the file in Windows Explorer, or save the file to disk before opening in Excel.

ACTIONS:
Additional actions provided by buttons on the Automatic Job Scheduling screen include:

• Manually run the Reporting Jobs on a Linux network:
  To force the scheduler to run the automated jobs that are due, click the RESET/INITIATE button to access Reset or Initiate Confirmation and then click INITIATE as outlined in Initiate Automatic Job Scheduling.

  Note: This manual action is not required for Windows networks as Windows initiates each job according to the frequency, date, and time in the Automatic Job Scheduling table.

• Restart the Scheduler:
  If the cronjob that controls and runs the Automatic Job Scheduling programs crashes or does not finish properly, the scheduler can be restarted as follows:

  • On a Linux network click the RESET/INITIATE button to access Reset or Initiate Confirmation, and then click RESET as outlined in Reset Automatic Job Scheduling utility.
  • In Windows networks, just click the RESET button to access the Reset Automatic Job Scheduling utility.
    Confirmation is required.