TECHNICAL DOCUMENTATION
Written By: Maliha Zaman
Contact Information: Help Desk Ticket
Last Updated: December 17, 2025
Feature Overview
The following steps are needed to run a job in Banner. To extract data based on set parameters.
Prerequisites
Access to Banner INB (Internet Native Banner) or Admin Pages.
Proper security roles to (contact IT help desk):
View system rules in GTVSDAX.
Submit jobs via GJAPCTL.
Review job output in GJIREVO.
Knowledge of the job name and required parameters.
Feature Description
There are three broad forms needed to run a Banner job.
GTVSDAX – System Data Exchange Rules. This Stores configuration values and rules used by Banner jobs. Commonly referenced for:
Parameter defaults.
Integration settings
Custom logic for job execution.
GJAPCTL – Job Submission Control. Used to submit jobs (reports, processes) in Banner. Allows specifying:
Job Name (e.g., GLRSLCT, SHRROLL).
Printer or Database output.
Parameters for the job.
GJIREVO – Job Submission Review. Displays job execution history. Provides access to:
Log files.
Output files.
Status (Completed, Error, etc.).
Step-by-step instruction
Step 1: Verify System Rules in GTVSDAX
Navigate to GTVSDAX.
Set the parameter by calling the correct procedure. Use the FILTER option.
Example: HU_SZRFHCN

Confirm that required values (e.g., term codes, printer settings) are correct.
Save
Step 2: Submit Job via GJAPCTL
Navigate to GJAPCTL.
Enter the Job Name (e.g., GLRSLCT).
Select Printer or choose DATABASE for online output.
Click Go to proceed to the Parameter Values block.
Enter required parameters:
Term Code.
Report Options.
Any values referenced from GTVSDAX.
Save and Submit the job.
Note the Job Number generated for tracking
Step 3: Review Job Output in GJIREVO
Navigate to GJIREVO.
Query using the Job Name or Job Number.
Review:
Status (Completed, Error).
Log File for errors or warnings.
Output File for report results.
Download or print the output as needed.Description
Troubleshooting
If the job fails:
Check GJIREVO log for error messages.
Verify parameter values against GTVSDAX.
Ensure user has correct security roles.
Common issues:
Incorrect term code.
Missing printer setup.
Invalid parameter defaults.Description
Best Practices
Always confirm GTVSDAX values before running jobs.
Use DATABASE output for large reports to avoid printer errors.
Document job parameters for audit and repeatability.
Related Resources
Banner manual
IT helpdesk