HJOBNUM threshold

[Dick Winston]

My HJOBNUM is set at 2000 which is plenty for my installation.  But once a job enters the system and is given a number, that job holds that number until it's purged from CA7.  So I periodically run out of job numbers and have to manually purge each job to free them up.  Is there a way to have jobs age out and purge after some threshold (days, # of runs, ???)?   Or is there a batch job I can run to purge them?​

[Roderick Woods]

Hello,

To start, I recommend you increase your HIJBNUM to 9999. If you are running r12.1,  there are 2 values for HIJBNUM (9999 and MAX). If you have HIJBNUM=2000 specified on the SCHEDULE statement in the init deck, CA 7 will automatically change it to HIJBNUM=9999 at startup.

When a job goes through completion processing or is canceled from the static queues (request, ready or active), the job number is freed and available for use. 
I am not sure what you mean by you have to purge jobs periodically to free job numbers. Can you please explain, what exactly you are doing.

[Dick Winston]

"When a job goes through completion processing or is canceled from the static queues (request, ready or active), the job number is freed and available for use. "

I think that's the crux of my problem.  The jobs never go away so their numbers aren't freed.  There must be a setting I have wrong that keeps the jobs from purging.

[RenateLynn Edwards]

Are all your jobs running?  If they don't run they aren't going to release a number and go away.   I'm trying to understand WHY you have to purge.  We very RAIRLY ever have to cancel a job.  The job runs and leaves the queue.

[Dick Winston]

Thanks.  The schedulers are checking to see if these are all jobs that weren't run.