Difference between revisions of "Setting up Job Processing"

From Documentation
Jump to navigation Jump to search
Line 40: Line 40:
 
|}
 
|}
 
|-
 
|-
| '''Prm''' || Example
+
| '''Prm''' || A system generated parameter number
 
|-
 
|-
| '''Recur''' || Example
+
| '''Recur''' || Is this a recurring job, ‘Yes’ or ‘No’. A recurring job runs each time the cycle is scheduled. A non-recurring job runs only once and is then deleted from the job stream
 
|-
 
|-
| '''Descr''' || Example
+
| '''Descr''' || A brief description of the job. When the program identifier is added to the job list, this field is auto-filled with the system description associated with it
 
|}
 
|}
 +
 +
 +
To add a new job to the queue, click the New button on the toolbar. The parameters screen will launch:
 +
 +
 +
[[File:Job Maintenance 3.png]]
 +
 +
 +
  
  
 
[[Category:Periodic Job Processing]]
 
[[Category:Periodic Job Processing]]
 
[[Category:System Administration]]
 
[[Category:System Administration]]

Revision as of 18:29, 29 March 2012

Overview of DDI44SET

Job processing, otherwise known as periodic processing or daily, allows your organization to process reports and system updates such as donations, loan payments and investment deposits. Job processing is usually configured as a part of the DDI implementation process. However, there will be times when a job needs to be maintained or added. The instructions below will walk you through the process of maintaining this screen. You can also contact DDI Client Support for assistance.


  • From the DDI Connect main menu, click Admin and select Job Queue:


Job Maintenance 2.png


You will see a screen similar to this one:


Job Maintenance 1.png


The columns on this screen contain the following information:


Column Description
Date codes The date codes field tells the system when this particular job should be run. A list of date codes can be found here
Seq The sequence field tells the system in what order to run the jobs for a particular date code. Please note that there are some jobs that must process in a certain order so that the system is updated properly
Program The program field indicates what process or report is being run. What the program name is will depend on what you are trying to run. For example:
Trying to run Program Name
Standard system report program name will be REPORTm.r where REPORT is the report identifier. For example, if you are trying to set up the Post Transactions to GL report, you would type fw20m.r. You can determine the report identifier by looking at the report parameter screen - in the upper left and lower left corners, it shows the report identifier
Process Processes that update account or constituent records should be entered as REPORTpro.r. For example, loan payment due processing is configured as il665pro.r
Report Generator or Info Query Report If you utilize either Report Generator or the Information Query to schedule reports, you can configure scheduled reports to run as a part of your periodic processing. They will appear as REPORTrtp.r, where REPORT is the report identifier. In order to schedule these reports, they must have been run at least once. If you would like assistance in configuring one of these report types, please contact DDI Client Support
Prm A system generated parameter number
Recur Is this a recurring job, ‘Yes’ or ‘No’. A recurring job runs each time the cycle is scheduled. A non-recurring job runs only once and is then deleted from the job stream
Descr A brief description of the job. When the program identifier is added to the job list, this field is auto-filled with the system description associated with it


To add a new job to the queue, click the New button on the toolbar. The parameters screen will launch:


Job Maintenance 3.png