The Job Catalog
The Job Catalog is a self-service application accessed through the UNF Administrative Applications. Any “jobs” that are produced by ITS are entered here. It is available to the general public in order for them to know what types of jobs are available; as well as, understanding the parameters of the job and whether or not there is any output.
The “Job Name” must follow the naming standards set forth in the Procedures Manual. The first letter is a W; the second letter is the system; and the third letter is a subsystem. Then the last four are digits. This is a required field.
The “Job Title” should be a brief but meaningful description of the job. The “Job Title” should match what is defined in AppWorx as well as in Banner. Keep in mind the various lengths of these fields when naming your jobs. This is a required field.
This will be the ”Analyst” that wrote the job. This is a required field.
This is the analyst who is the backup for the job.
Select the “AppWorx” check box if this job will be used in AppWorx. Either the AppWorx or Banner check box must be checked.
Select the “Banner” check box if this is a Banner job to be run via Banner Job Submission. Either the AppWorx or Banner check box must be checked.
The date the Job Catalog entry was last updated. This is populated automatically.
This is the Banner system for the job. This is populated automatically.
This is the Banner subsystem for the job. This is populated automatically.
Select the “Active” check box when the job has been moved to production and is ready to be used.
Select the “Update Data” check box if the job actually updates any data (Banner or internal).
Add Parameter Button
The “Add Parameter” button is used to add parameters manually. These are the parameters that are defined in Banner (GJAPDEF).
Pull Out Parameters from Banner
The “Pull Out Parameters from Banner” button is used to extract the parameters that have been entered via GJAPDEF into the Job Catalog. Once the parameters have been extracted from Banner, then they can be modified in the Job Catalog. If they are modified in the Job Catalog, the change is NOT reflected in Banner.
The ”Name” field is the name of the parameter.
The “Description” field is the same as the Help field in GJAPDEF. This is the information that displays in the Help line in Banner Job Submission.
The “Format” is the Type and Length of the parameter from GJAPDEF.
The “Required” checkbox is checked if the “Required” radio button is selected on GJAPDEF. In order to delete a parameter, you can just delete the data in each field, then select “Update”.
The “Description” should be a thorough explanation of the job, parameters, and any output. This is the description that the general public sees. This is a required field.
The “Internal Description” is additional technical information. Include the name of the package and procedure that are called to execute this job. You may want to include any tables and descriptions that were created to support this job.
The “Dependency” is to reference another job that may need to run prior to running this job. It may also be instructions about when it is appropriate to run this job. It may be that this job should not be run on a certain day of the month.
The “Schedule” refers to the schedule defined in an AppWorx chain.
Select the check box for the day or days that the job is run.
Select the radio button that describes the frequency with which the job is run. Select “Other” and provide a description if the frequency is not one of the choices listed.
Input the time of day that the job is run.
Add any additional notes that you feel are necessary to fully describe the AppWorx schedule.
Select the “Download” check box if the job delivers a file to the user’s directory.
Select the “Report” check box if the job produces formatted output that is available through Job Submission.
Select the “Email” check box if the job sends an email.
Select the “FTP” check box if the job creates a file and sends it to some other location (i.e. not a user’s directory).
Select the “File” check box if the job creates a file that is not sent to the user’s directory.
The “Source” should be the name of the program that is executed. This will normally be the sql, shl, or other executable file.
Select the “Add Chain” button to input the name of a chain in AppWorx that runs this job. You can add as many chains as necessary.
In order to delete a chain, you can just delete the data in each field, then select “Update”.