CMD-202 CONTROL-M for zOS - Prodcut Roadmap

37
9/2/2006 BMC CONTROL-M for z/OS Product Roadmap

Transcript of CMD-202 CONTROL-M for zOS - Prodcut Roadmap

Page 1: CMD-202 CONTROL-M for zOS - Prodcut Roadmap

9/2/2006

BMC CONTROL-M for z/OS

Product Roadmap

Page 2: CMD-202 CONTROL-M for zOS - Prodcut Roadmap

9/2/2006 ©2006 BMC Software2

Agenda

›6.1 – July 2002

›6.2 – Oct. 2005

›6.2.18 – Aug. 2006 (soon)

›6.3 – Q4 2007

Page 3: CMD-202 CONTROL-M for zOS - Prodcut Roadmap

9/2/2006 ©2006 BMC Software3

CTMPLEX: Exploiting SYSPLEX Capabilities6.1

› What is that?– Single global, several local monitors– Distribute spool access and load among them– Communication, assignment and

Information sharing, through coupling facility

› Why– RAS (Reliability, Availability, Serviceability), recoverability– Performance and capacity – better usage of current HW– Easier upgrade, without need for maintenance window

LocalGlobal

Local

XCFSpool

Page 4: CMD-202 CONTROL-M for zOS - Prodcut Roadmap

9/2/2006 ©2006 BMC Software4

BYPASS

› Bypass command for scheduling waiting jobs– This is an option to allow a job to ignore pre-requisite conditions, missing

resources, etc.– The presentation in the Jobs map should reflect that a job has a bypass on it

6.1

Page 5: CMD-202 CONTROL-M for zOS - Prodcut Roadmap

9/2/2006 ©2006 BMC Software5

Relative ODAT in IN/OUT Conditions6.1

Page 6: CMD-202 CONTROL-M for zOS - Prodcut Roadmap

9/2/2006 ©2006 BMC Software6

Future ODAT in Order

› When ordering a table or a job with a future ODAT, the job or the jobs in the table will run right when all of its pre-requisiteswill be fulfilled

› The new flag tellsBMC CONTROL-M for z/OSto run the job or the jobs inthe table in the ODAT date

› This feature is availablein BMC CONTROL-M for z/OS 6.1

6.1

Page 7: CMD-202 CONTROL-M for zOS - Prodcut Roadmap

9/2/2006 ©2006 BMC Software7

AJF Space Reuse

› AJF Space Reuse– AJF management done as part of New-Day processing – Ad-Hoc jobs can be eliminated from the AJF

› Dynamic reuse of AJF space – Control the behavior of AJF freed space

• May be turned on/off dynamically– Specify the duration of jobs to be kept in AJF

• Applies only to jobs that ENDED-OK and MAXWAIT=0– When new jobs arrive they will be placed in free AJF entries– Controlled by CTMPARM (CKP section)

6.2

› *--------------------------------------------------*› * Data-Base Parameters: *› *--------------------------------------------------*› CKP AJFSIZE=1000, # of records in the AJF (1000-999999). › AJFTHRSH=90, WM2095: AJF-FULL Threshhold› HIST=Y, History Jobs File Enabled (Y/N).› JRNL=Y, Journaling Enabled (Y/N).› REUSTIME=30, AJF Space Reuse Retention Period› REUSAPPL=REUS AJF Space Reuse Application Name Prefix

Page 8: CMD-202 CONTROL-M for zOS - Prodcut Roadmap

9/2/2006 ©2006 BMC Software8

INSTREAM JCL

› Include the JCL control cards as part of scheduling definition› Eliminate the need to access the mainframe JCL library separately› Can also be invoked from eTrigger, EM API and EM Desktop and GUI› The In-Stream JCL will reside in the AJF,

– available for Zoom & Save

6.2

Page 9: CMD-202 CONTROL-M for zOS - Prodcut Roadmap

9/2/2006 ©2006 BMC Software9

INSTREAM JCL (3270)6.2

Page 10: CMD-202 CONTROL-M for zOS - Prodcut Roadmap

9/2/2006 ©2006 BMC Software10

Re-Run Of Job Flow6.2

› Allow rerunning a job flow in a single command:– From AJF (screen 3)– Upstream, downstream or both– Select which jobs in the flow to rerun– The jobs conditions are automatically deleted before rerun – Rerun or restart (steps apply only to the anchor job)

Page 11: CMD-202 CONTROL-M for zOS - Prodcut Roadmap

9/2/2006 ©2006 BMC Software11

Re-Run Of Job Flow: RFLW6.2

› 1+----------+ +----------+ +----------+ +----------+› | JOBA |--->| OPHIR7 |--->| JOBD |--->--->--->--->--->| OPHIR7 |› +----------+ | | | | | |› | | | | | |› | | | | +----+ | › | | | |--->-->| 1 | | |› | | +----------+ +----+ | |› | | | |› | | +----------+ | |› | |--->| JOBE |--->--->--->--->--->| |› | | | | | |› | | | | | |› | | | | +----+ | |› | | | |--->-->| 2 | | |› | | +----------+ +----+ | |› | | | |› | | +----------+ | | +----------+ +----------+› | |--->--->--->--->--->| JOBF |--->| |--->| JOBH |--->| JOBJ |› | | | | | | +----------+ | |› | | | | | | | |› | | | | | | +----------+ | |› | | | | | |--->| JOBI |--->| |› | | | | +----------+ +----------+ +----------+› | | | |› | | +----+ | |› | | | 2 |-->--->| |› | | +----+ | |› | | | |› | | +----+ | |› | | | 1 |-->--->| |› | | +----+ +----------+› | |› +----------+ | |› | JOBC |--->| |› +----------+ +----------+

Page 12: CMD-202 CONTROL-M for zOS - Prodcut Roadmap

9/2/2006 ©2006 BMC Software12

Re-Run Of Job Flow: Job List6.2

Page 13: CMD-202 CONTROL-M for zOS - Prodcut Roadmap

9/2/2006 ©2006 BMC Software13

Re-Run Of Job Flow: R Command6.2

Page 14: CMD-202 CONTROL-M for zOS - Prodcut Roadmap

9/2/2006 ©2006 BMC Software14

Re-Run Of Job Flow: Parms To Fill6.2

Page 15: CMD-202 CONTROL-M for zOS - Prodcut Roadmap

9/2/2006 ©2006 BMC Software15

Re-Run Of Job Flow: With Parms6.2

Page 16: CMD-202 CONTROL-M for zOS - Prodcut Roadmap

9/2/2006 ©2006 BMC Software16

Re-Run Of Job Flow – Job Selection6.2

Page 17: CMD-202 CONTROL-M for zOS - Prodcut Roadmap

9/2/2006 ©2006 BMC Software17

Re-Run Of Job Flow: Ready To Run6.2

Page 18: CMD-202 CONTROL-M for zOS - Prodcut Roadmap

9/2/2006 ©2006 BMC Software18

Re-Run Of Job Flow: Done6.2

Page 19: CMD-202 CONTROL-M for zOS - Prodcut Roadmap

9/2/2006 ©2006 BMC Software19

Re-Run Of Job Flow: Running Again6.2

Page 20: CMD-202 CONTROL-M for zOS - Prodcut Roadmap

9/2/2006 ©2006 BMC Software20

Re-Run Of Job Flow: JOBJ Excluded6.2

Page 21: CMD-202 CONTROL-M for zOS - Prodcut Roadmap

9/2/2006 ©2006 BMC Software21

Keep / Discard Resources

› Keep resources when JOB ended NOTOK / Discard when OK– When job ends NOTOK resources are automatically released– In 6.2 BMC CONTROL-M will keep resources (control and quantitative)

allocated• Release only when: re-run and ended OK, Forced OK, Deleted

– Determined throughan attribute of aresource in a specificJOB (a field in the jobdefinition per resource)

– Option to discardresources after usage

6.2

Page 22: CMD-202 CONTROL-M for zOS - Prodcut Roadmap

9/2/2006 ©2006 BMC Software22

Keep / Discard Resources6.2

Page 23: CMD-202 CONTROL-M for zOS - Prodcut Roadmap

9/2/2006 ©2006 BMC Software23

SHOW FILTER Enhancements6.2

› Following fields were added to filter:– Wait quant, Wait cond, Wait time, Wait control– Grp Active, Late– Forced OK, Grp Hold, Restarted, CM Forced, Note attached – Schedule library, CPU ID, LPAR ID

› Text field values – 2 options controlled by profile– Any string is prefix, default– Use regular expression,

• Any string used as is• For prefix use ABC*• For suffix use *XYZ

Page 24: CMD-202 CONTROL-M for zOS - Prodcut Roadmap

9/2/2006 ©2006 BMC Software24

SHOW FILTER enhancements6.2

Page 25: CMD-202 CONTROL-M for zOS - Prodcut Roadmap

9/2/2006 ©2006 BMC Software25

Statistics Calendar for Better Prediction6.2

› Deadline scheduling calculations are based on job statistics› Jobs’ statistics based on average elapsed time calculation› How to handle variance in elapsed time?

– Job’s elapsed time is exceptional during weekend– Job’s elapsed time

is exceptional duringend of quarter

› Jobs’ statistics areperiodically based

– Implemented throughcalendars

– 20 entries per period

Page 26: CMD-202 CONTROL-M for zOS - Prodcut Roadmap

9/2/2006 ©2006 BMC Software26

Statistics Calendar for Better Prediction6.2

Page 27: CMD-202 CONTROL-M for zOS - Prodcut Roadmap

9/2/2006 ©2006 BMC Software27

WLM Support: SCHEDENV6.2

› SCHEDENV– Introduced in version 6.1– Specify scheduling environment within job definition– Will submit only when SCHEDENV available

Page 28: CMD-202 CONTROL-M for zOS - Prodcut Roadmap

9/2/2006 ©2006 BMC Software28

WLM Support: SRVCLASS6.2

› SRVCLASS– Service class: set of parameters to determine required resources for job (CPU, I/O)– Adjust job’s service class based on

• Specific time frames (time-from, time-to)• Jobs that are late submission (late-sub-SRVCLASS)• Jobs that are late execution (late-exec-SRVCLASS)

– Will be specified globally using job prefix

*---+----1----+----2----+----3----+----4----+----5----+----6----+----7* **JOB_NAME APPLICATION_NAME____ FROM TO__ JOB_INIT LATE_SUB LATEEXEC **__MASK__ ________MASK________ TIME TIME SRVCLASS SRVCLASS SRVCLASS ** **********************************************************************K15JOBA TESTAPPLICATION 2200 0200 STANDARD QUICK QUICKERN50* 0000 2359 QUICK QUICKER QUICKEST

EMERGENCYAPPL 0000 2359 QUICKEST QUICKEST QUICKESTSTAMJOB 1700 2000 STANDARDSTAMJOB 2200 0200 QUICK* PROD* 0000 2359 STANDARD QUICKER QUICKER

Page 29: CMD-202 CONTROL-M for zOS - Prodcut Roadmap

9/2/2006 ©2006 BMC Software29

Job Flow Across NewDay

› Current situationScenario 1 Scenario 2– New day at midnight (1/1/05) - Flow of jobs to run through all weekend– Job A is ordered to run at 23:00 - 2 hours Backup window is needed at – Late sub warning is required 2 hours Saturday noon

later at 01:00 the following day (1/2/05) - FROM specific time (late Saturday) – Late Sub Shout is coded to 01:00 - Late Sub warning is required for a job– At 23:00 (1/1/05) a late sub shout is that should run on Saturday evening

issued for Job A – 2 hours ahead of time› The solution

– Provide ODATE relative value • from-time, to-time• shout• due out

6.2

Page 30: CMD-202 CONTROL-M for zOS - Prodcut Roadmap

9/2/2006 ©2006 BMC Software30

Job Flow Across NewDay6.2

Page 31: CMD-202 CONTROL-M for zOS - Prodcut Roadmap

9/2/2006 ©2006 BMC Software31

Job Flow Across NewDay: Multi-Day6.2

Page 32: CMD-202 CONTROL-M for zOS - Prodcut Roadmap

9/2/2006 ©2006 BMC Software32

Job Flow Across NewDay: Multi-Day6.2

Page 33: CMD-202 CONTROL-M for zOS - Prodcut Roadmap

9/2/2006 ©2006 BMC Software33

6.2.18: Support for EM 6.3 enhancements6.2.18

› Configure BMC CONTROL-M for z/OS to support EM 6.3 protocol› Configuration Manager Support› DO BMC REMEDY

Page 34: CMD-202 CONTROL-M for zOS - Prodcut Roadmap

9/2/2006 ©2006 BMC Software34

6.2.18: Additional Enhancements6.2.18

› Records order time for jobs› Submit with In-Memory buffer› Export schedule definition to XML – CTMTLB› Built-in support for BMC Batch Impact Manager

Page 35: CMD-202 CONTROL-M for zOS - Prodcut Roadmap

9/2/2006 ©2006 BMC Software35

6.3 Planned Items

› Jobs that cause problems will not be download to EM › Dynamic refresh of user exits› New-Day in memory – no read from AJF on DASD› STAT file enhancements› Condition bridge when deleting job definition› Limit number of CTM submitted jobs › Dynamically move re-used AJF entries to history› Enhanced IOAVERFY - for every field› IOALOG - improve performance by having indexes

6.3

Page 36: CMD-202 CONTROL-M for zOS - Prodcut Roadmap

9/2/2006 ©2006 BMC Software36

IOA and Install plans6.3

› Installation audit – Log update sections done through ICE

› Separate installation from customization– Separation SysProg tasks from BMC CONTROL-M Admin tasks

› Installation parameters in default - Express Install – Allow Install with very few questions if All Defaults are used– Single job for all actions, for all products

› IOA Cloning – Easy replication for every LPAR– Mechanism for distribution of updates– Reports to assist in synchronizing between IOA environments

› Support sharing SMP/E Global files between multiple IOA env. – Simplify maintaining multiple IOA SMP/E environments

Page 37: CMD-202 CONTROL-M for zOS - Prodcut Roadmap

9/2/2006 ©2006 BMC Software37

Questions?

Thank you