HORIZONT 1 TWS/BatchCP

HORIZONTSoftware for Datacenters

Garmischer Str. 8 D- 80339 MünchenTel ++49(0)89 / 540 162 - 0www.horizont-it.com

TWS/BatchCPAutomation for the Current Plan

Product Presentation

HORIZONT 2 TWS/BatchCP

What is TWS/BatchCP?

• TWS/BatchCP can modify the Current Plan in batch mode

• TWS/BatchCP can do mass updates

TWS/BatchCP is an add on to TWS, it TWS/BatchCP is an add on to TWS, it enables you to:enables you to:

HORIZONT 3 TWS/BatchCP

Who is using TWS/BatchCP?

• Production Planning

• Operations

• ...

TWS/BatchCP is useful to anybody working TWS/BatchCP is useful to anybody working in an TWS environment, especially:in an TWS environment, especially:

HORIZONT 4 TWS/BatchCP

Without TWS/BatchCP

• The TWS mass update is complicated and incomplete

• Your own PIF or OCL program needs

- maintenance for new TWS versions

- manpower to implement requirements

- documentation

TWS’s integrated mass update functions TWS’s integrated mass update functions are no competition for TWS/BatchCP:are no competition for TWS/BatchCP:

HORIZONT 5 TWS/BatchCP

With TWS/BatchCP

• Occurrences

• Operations

• Special Resources

• Dependencies

• JCL from the JS-file

Insert, delete, modify or listInsert, delete, modify or list

execute OPC dialog functions in batch mode! 5.4

5.3

5.2

5.1

5.5

5.6

HORIZONT 6 TWS/BatchCP

How TWS/BatchCP works

• TWS/BatchCP uses PIF (TWS Program Interface) - 100% secure- 100% reliable

• TWS/BatchCP can be used in- Batch programs (JCL)- Dialog programs (Clist, REXX)

TWS/BatchCP is a “normal” program (no STC). TWS/BatchCP is a “normal” program (no STC).

It communicates with the TWS controller.It communicates with the TWS controller.

HORIZONT 7 TWS/BatchCP

Selection

• Generic- Use wildcards * and % to select Occurrences,

Operations, Special Resources...

• All data fields- Even undocumented OPC fields are supported, e.g.

the Extended Status to search for Operations waiting for Special Resources

• Comparison Operators- Use comparison operators to search for Operations

which are now active for more than one hour

TWS/BatchCP offers a wide range of selection TWS/BatchCP offers a wide range of selection

functionality:functionality:

HORIZONT 8 TWS/BatchCP

Control Statements

* SEARCH CRITERIA ADID=A*B*

* ACTION PARAMETER RECORD=CPOC/CPOP/CPDEP/CPSR/JS ACTION=INSERT/DELETE/MODIFY/LIST

* UPDATE PARAMETER STATUS=C

Select Occurrences, Operations, Special Resources...

...select the desired action

..and specify new values for the selected objects

HORIZONT 9 TWS/BatchCP

Some examples

• List all jobs which are now active for more than one hour

• List all jobs which are waiting for Special Resources

• Run cyclic jobs, for example every 15 minutes

• Use TWS/BatchCP and REXX in Operating

The following three examples show you some The following three examples show you some

of the capabilities of TWS/BatchAD:of the capabilities of TWS/BatchAD:

HORIZONT 10 TWS/BatchCP

Example (1)

List all jobs which have been active for more than one hour.

* SEARCH CRITERIA ADID=* STATUS=S OPAS_TO=ACTUAL-0100* ACTION PARAMETER RECORD=CPOP ACTION=LIST

Time variables!

HORIZONT 11 TWS/BatchCP

Example (2)

List all Operations which are waiting for Special List all Operations which are waiting for Special ResourcesResources

* SEARCH CRITERIA ADID=* OPXST=X* ACTION PARAMETER RECORD=CPOP ACTION=LIST

OPC’s Extended Status!

HORIZONT 12 TWS/BatchCP

Example (3)

Possible solution without TWS/BatchCP:

96 Run Cycles with different Input Arrival Timesor

96 time dependent Operations

Disadvantages:

• Do you really want to have to define 96 separate Run Cycles or Operations?

• What happens if you now need to changethe job to run every 10 minutes?

Too complicated!

A job should run every 15 minutes:A job should run every 15 minutes:

HORIZONT 13 TWS/BatchCP

Example (3)

Job with TWS/BatchCP

CPU-Job

Increase the start time of the CPU Operation and reset the Status

A time dependent CPU Operation with the “first” start time

How to run a job every 15 minutes with TWS/BatchCP:How to run a job every 15 minutes with TWS/BatchCP:

HORIZONT 14 TWS/BatchCP

Example (4)

/* REXX SETOPCMH */ARG JOBNAME "ALLOC DD(PARMIN) DSN('HLQ.OCBBSP1') SHR REUSE""ALLOC DD(EQQMLIB) DSN('SYS1.OPCESA.V2R1M0.SEQQMSG0') SHR REUSE""ALLOC DD(EQQYPARM) DSN('HLQ.OPCESA.V2R1M0.EQQYPARM') SHR""ALLOC DD(EQQMLOG) DSN(*) SHR REUSE""ALLOC DD(SYSPRINT) DSN(*) REUSE""CALL 'OPCBATCP.V1R9M1.LOAD(OCBICOM5)' '/"JOBNAME"'""FREE DD(PARMIN EQQMLOG EQQMLIB EQQYPARM PRGRCF OCBOUT)"EXIT

CUSTOMER=PARMJOBN SECURITY_FLAG=N CONTINUE_ON_PIFERROR=Y * SEARCH CRITERIA ...

* ACTION PARAMETER RECORD=CPOC/CPOP/CPDEP/CPSR/JS ACTION=INSERT/DELETE/MODIFY/LIST

* UPDATE PARAMETER ...

File with TWS/BatchCP control cards

Contents of the file

TWS/BatchCP and REXX:TWS/BatchCP and REXX:

HORIZONT 15 TWS/BatchCP

Example (4)

Instead of hundred line commands... ...simply one

primary command!

TWS/BatchCP and REXX: TWS/BatchCP and REXX: Set Operations to MH (Manual Hold)Set Operations to MH (Manual Hold)

HORIZONT 17 TWS/BatchCP

TWS/BatchCP vs. BCITWS/BatchCP BCI

Yes Yes

Yes Yes

Modify• Application• Operation• Predecessor• Special Resource

Delete Application

Yes YesCopy Application

Yes YesInsert Application

Basic Functions

HORIZONT 18 TWS/BatchCP

TWS/BatchCP vs. BCITWS/BatchCP BCI

Yes Yes

Insert and Delete• Operation• Predecessor• Special Resource

Yes NoDelete JS-JCL

Yes NoInsert JS-JCL

No YesList CP-WS

Yes YesList JS-JCL

Basic Functions

HORIZONT 19 TWS/BatchCP

TWS/BatchCP vs. BCITWS/BatchCP BCI

Yes YesList CP-WS (5.5.)

Yes NoModify CP-WS (5.5.)

Yes NoList CP Special Res.

Yes NoModify CP-WS-Interval (5.5.)

Basic Functions

Yes NoModify CP Special Resource (5.7.)

HORIZONT 20 TWS/BatchCP

TWS/BatchCP vs. BCITWS/BatchCP

Variable simulation

BCI

Yes Yes

No Yes

Special Functions

LIST Status with RC

Yes NoList JCL sorted by planned start time

List JCL only Yes No

No Yes“move” IA from CPto LTP, if IA > CP end

HORIZONT 21 TWS/BatchCP

TWS/BatchCP vs. BCITWS/BatchCP

Operators

BCI

Yes No

Basic functionality

> 50 < 20

NoYes

Number of selectionparms

Integrated date andtime functions

Yes, always Not allGeneric Selection

HORIZONT 22 TWS/BatchCP

TWS/BatchCP vs. BCITWS/BatchCP BCISelection Criteria

Predecessor Yes No

Successor Yes No

Special Resources Yes No

HORIZONT 23 TWS/BatchCP

TWS/BatchCP vs. BCITWS/BatchCP BCISelection Criteria

Yes No

Yes NoExtended status

Time depend Y/N

Yes No

Yes No

Yes No

NoOperation MH, NOP

on critical path

Operation is urgent

Yes NoOp. latest out passed

Yes NoOp. cancel if late

HORIZONT 24 TWS/BatchCP

TWS/BatchCP vs. BCITWS/BatchCP BCI

Old start time+HHMM Yes No

New Values

Commands MH etc. Yes No

HORIZONT 25 TWS/BatchCP

• REXX Runtime Library or IBM Compiler Libraries for REXX are required

• REXX experience is required

• Would you like to write your own code?

• Would you maintain your program (from OPC/A to TWS 8.2?)

TWS/BatchCP vs. OCLThe OCL (OPC Command Language) is a powerful The OCL (OPC Command Language) is a powerful tool, but:tool, but:

HORIZONT 26 TWS/BatchCP

HORIZONTSoftware for Datacenters

Garmischer Str. 8 D- 80339 MünchenTel ++49(0)89 / 540 162 - 0www.horizont-it.com

TWS/BatchCPAutomation for the Current Plan

Thank you very much for your attention!