Not too sure what you are requesting here, can you be more specific?
Do you want to increase job performance via the system or program?
Basicaly i wanted to know…is there any way i can set priorities or i can make my job run faster than the normal completion time.
for example, i know a job runs 3 hrs from Past experience. is there any way i can reduce its time to lesser than 3hrs either before submittng the job or while the job is active?
To reduce the run time, reduce its resource requirements or increase the resources available to it. This requires knowing, or learning, what the job uses or needs. We have no idea what your job might need. It would help if we had an idea what the job does. Otherwise, this is just random thoughts.
If the job becomes I/O bound, then review how I/O is managed. Ensure proper indexing, for example, rather than creating temporary indexes. Try sequential-only processing wherever it fits, and reorg files to the order you’ll be reading them. And maybe reorg simply to compress excessive deleted records out. If conflicts exist with other jobs, eliminate them as far as possible.
If the job is memory constrained, then take control of your memory pools. Review everything you have that runs in *BASE, and reroute it to shared pools instead. (This includes IBM tasks.) Begin organizing work into a set of pools. Once you have a basic organization, start the performance adjuster. (Running it without initial organization might make things actually a little worse.) Provide memory to your job when it runs by reducing use of memory elsewhere.
If the job is CPU constrained, then raise its run priority. Or reduce its competition.
If the job is performing serial operations that can be run in parallel, break the job into parts. Submit parallel sections to run in other jobs along side the main job.
If the job is accessing many objects at different times and uses private authorities, then run the job under an *ALLOBJ profile. Eliminate authority lookups. If the job is making many dynamic calls to programs that open and close files, especially if the files are accessed multiple times, then rework them so that they’re left open. Consider activating the programs into a named activation group or *CALLER and leave the programs active. If there are date “calculations” such as multiplication by (10000.01) that happen a million times, then replace them with decent conversions.
If the job is performing extensive SQL operations, then look closely at how the SQL statements are structured, how they’re executed and what they run over.
There are far too many possibilities to list.
Regardless, make certain that the work being performed happens inside an appropriate system. Do you have enough memory? Is your DASD capacity strained? Are you using the appropriate processor? Are you running programs that actually need to be run and are they performing operations that need to be done?