1 / 25

H O RIZONT Software for Datacenters

TWS/BatchCP. Automation for the Current Plan. Product Presentation. H O RIZONT Software for Datacenters. Garmischer Str. 8 D- 80339 München Tel ++49(0)89 / 540 162 - 0 www.horizont-it.com. What is TWS/BatchCP?. TWS/BatchCP is an add on to TWS, it enables you to:.

bill
Download Presentation

H O RIZONT Software for Datacenters

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TWS/BatchCP Automation for the Current Plan Product Presentation HORIZONT Software for Datacenters Garmischer Str. 8 D- 80339 München Tel ++49(0)89 / 540 162 - 0www.horizont-it.com

  2. What is TWS/BatchCP? TWS/BatchCP is an add on to TWS, it enables you to: • TWS/BatchCP can modify the Current Plan in batch mode • TWS/BatchCP can do mass updates

  3. Who is using TWS/BatchCP? TWS/BatchCP is useful to anybody working in an TWS environment, especially: • Production Planning • Operations • ...

  4. Without TWS/BatchCP TWS’s integrated mass update functions are no competition for 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

  5. With TWS/BatchCP 5.1 5.2 5.3 5.4 5.5 5.6 Insert, delete, modify or list • Occurrences • Operations • Special Resources • Dependencies • JCL from the JS-file execute OPC dialog functions in batch mode!

  6. How TWS/BatchCP works TWS/BatchCP is a “normal” program (no STC). It communicates with the TWS controller. • TWS/BatchCP uses PIF (TWS Program Interface) - 100% secure- 100% reliable • TWS/BatchCP can be used in- Batch programs (JCL)- Dialog programs (Clist, REXX)

  7. Selection TWS/BatchCP offers a wide range of selection functionality: • 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

  8. 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

  9. Some examples The following three examples show you some of the capabilities of TWS/BatchAD: • 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

  10. Example (1) List all jobs which have been active for more than one hour. Time variables! * SEARCH CRITERIA ADID=* STATUS=S OPAS_TO=ACTUAL-0100 * ACTION PARAMETER RECORD=CPOP ACTION=LIST

  11. Example (2) List all Operations which are waiting for Special Resources * SEARCH CRITERIA ADID=* OPXST=X* ACTION PARAMETER RECORD=CPOP ACTION=LIST OPC’s Extended Status!

  12. Example (3) A job should run every 15 minutes: Possible solution without TWS/BatchCP: Too complicated! 96 Run Cycles with different Input Arrival Times or 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?

  13. Example (3) How to run a job every 15 minutes with TWS/BatchCP: A time dependent CPU Operation with the “first” start time CPU-Job Job with TWS/BatchCP Increase the start time of the CPU Operation and reset the Status

  14. Example (4) TWS/BatchCP and REXX: File with TWS/BatchCP control cards /* 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 ... Contents of the file

  15. Example (4) TWS/BatchCP and REXX: Set Operations to MH (Manual Hold) Instead of hundred line commands... ...simply one primary command!

  16. TWS/BatchCP vs. BCI Basic Functions TWS/BatchCP BCI Modify • Application • Operation • Predecessor • Special Resource Yes Yes Delete Application Yes Yes Copy Application Yes Yes Insert Application Yes Yes

  17. TWS/BatchCP vs. BCI Basic Functions TWS/BatchCP BCI Insert and Delete • Operation • Predecessor • Special Resource Yes Yes Delete JS-JCL Yes No Insert JS-JCL Yes No List JS-JCL Yes Yes List CP-WS No Yes

  18. TWS/BatchCP vs. BCI Basic Functions TWS/BatchCP BCI List CP-WS (5.5.) Yes Yes Modify CP-WS (5.5.) Yes No Modify CP-WS-Interval (5.5.) Yes No List CP Special Res. Yes No Modify CP Special Resource (5.7.) Yes No

  19. TWS/BatchCP vs. BCI Special Functions TWS/BatchCP BCI Variable simulation Yes Yes List JCL only Yes No List JCL sorted by planned start time Yes No LIST Status with RC No Yes “move” IA from CPto LTP, if IA > CP end No Yes

  20. TWS/BatchCP vs. BCI Basic functionality TWS/BatchCP BCI Operators Yes No Generic Selection Yes, always Not all Number of selectionparms > 50 < 20 Integrated date andtime functions Yes No

  21. TWS/BatchCP vs. BCI Selection Criteria TWS/BatchCP BCI Predecessor Yes No Successor Yes No Special Resources Yes No

  22. TWS/BatchCP vs. BCI Selection Criteria TWS/BatchCP BCI Extended status Yes No Time depend Y/N Yes No Operation MH, NOP Yes No No on critical path Yes No Operation is urgent Yes No Op. latest out passed Yes No Op. cancel if late Yes No

  23. TWS/BatchCP vs. BCI New Values TWS/BatchCP BCI Old start time+HHMM Yes No Commands MH etc. Yes No

  24. 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. OCL The OCL (OPC Command Language) is a powerful tool, but:

  25. TWS/BatchCP Automation for the Current Plan Thank you very much for your attention! HORIZONT Software for Datacenters Garmischer Str. 8 D- 80339 München Tel ++49(0)89 / 540 162 - 0www.horizont-it.com

More Related