Batch Scheduling Of Jobs

5 pts.
Tags:
AS/400 batch jobs
Batch jobs
DB2
z/OS configuration
Currently, we are creating 80-100 jobs for a complete batch schedule to execute against individual db2 regions (1 entire batch schedule per region). Is there a way to create one series of batch jobs and use that set against all regions? I apologize if this makes absolutely no sense.

Software/Hardware used:
DB2, CA-7

Answer Wiki

Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Discuss This Question: 5  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • IDean
    Have you considered using Advanced Job Scheduler? There is a GUI plugin for System i Navigator and you can create you own workflow.
    75 pointsBadges:
    report
  • wpoulin
    Smearbrick, It really depends on how your Regions are set up. If it is based on Library Lists, what you are asking to do may be possible, but more information needs to be provided. Hope this helps, Bill Poulin
    2,480 pointsBadges:
    report
  • TomLiotta
    Since this is tagged as { z/OS configuration } and also as { AS/400 batch jobs }, the question is very confusing. Where will the scheduler run? Where will the batch jobs run? Is this about z/OS, or is it about AS/400s? They are very different. Tom
    125,585 pointsBadges:
    report
  • HMSSL2K
    Robot Schedule or the iSeries Advanced Job Schedule does a great job.
    3,175 pointsBadges:
    report
  • Meandyou
    I hope I have addressed your problem with this sort of wordy response. There are so many aspects (and I do not know your knowledge base) that I rambled on in several areas ... We use CA-7 Scheduler on z/OS - And we create different schedules consisting of various numbers of jobs. I'm the DB2 DBA (and the Datacom DBA - we use Datacom DB as well as Datacom AD (AD is just for Scheduler where DB is a full fledged database for application use)). I don't actually set up job streams in Scheduler. Our Production Control people do that. None of my DB2 schedules have over 15 or 20 different jobs. The way we use Scheduler, if one of the jobs in a specific schedule fails, none of the following jobs in that schedule will run. I do not know if that is required by Scheduler or if that is just the way we have it set up. Sometimes that is good, sometimes not so good. So I have to ensure that a schedule contains jobs that are dependent on the preceding jobs. Other restrictions / controls can be specified in Scheduler. As long as a job is set up in Scheduler other jobs (in other schedules) can be triggered by completion of the first job - even down to run it or not based on the return code. Now, as to running one schedule against different DB2 "regions": In z/OS, each DB2 sub-system has a name. (I assume when you use the word 'region' you mean DB2 sub-system). When a job is run in (or against) a specific DB2, the name of that DB2 must be specified. For example, a DB2 utility running against DB2 tablespaces in DB2 sub-system named TEST has an EXEC card that looks like this: //STEP01 EXEC PGM=DSNUTILB,PARM='TEST,DBA020' Where TEST is the name of the DB2 subsystem and DBA020 is the UTIL-ID. To run this same job against a different DB2, maybe named PROD would require that the execute parm be changed. To this: //STEP01 EXEC PGM=DSNUTILB,PARM='PROD,DBA020' You cannot run the exact same job against multiple DB2s. *Unless* those DB2s have the same name - but that is not something I would want to do. Even on different LPARS, I would think you would want different names for your different DB2 subsystems. Could a job (or different jobs in the same schedule) run against different DB2s? If the DB2s were on the same LPAR, then that could be done. But each job step still has to name the DB2 sub-system name. One job in Scheduler can be associated with more than one schedule. Followup with another post if this does not address your question. <end ramble>
    5,220 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following