Agenda 1. About Colruyt 2. History 3. Tivoli Environment 4. Usage 5. Installation / Configuration 6. Questions?

Transcription

1 Colruyt GSE 11 June 2014 Agenda 1. About Colruyt 2. History 3. Tivoli Environment 4. Usage 5. Installation / Configuration 6. Questions?

2 1 About Colruyt

3 Retail: 76% of group revenue Wholesale and foodservice: 16% of group revenue

4 Other activities: 9% of group revenue 4 locations Halle- Zenneveld Deinze Haasrode India- Hyderabad Colruyt IT

5 Datacenter 1 IBM zec12 (Galilei) 5 CPU 2 ziip 2 ICF Prod IBM zec12 (Newton) 5 CPU 2 ziip 2 ICF Datacenter 2 VSM PC05 PC03 PC06 PC01 PC04 PC02 PC08 VSM Ontw Robot OC03 OC07 OC08 OC02 OC05 OC04 OC06 Robot Acpt AC02 PI09 AC01 DS8870 Primary Mainframe environment DS8870 Secondary Mainframe software Operating system z/os 1.13 JES3 Syncsort (replacement for DFSORT) Security CA-ACF2 CA-LDAP Automation CA-OPS (actions on messages, system restarts, ) Supporting software Abendaid : Dump capture and analysis Fileaid : ISPF application for editing, browsing, defining, VSAM, PDS, PDSE, sequential files, Flasher : SDSF for JES3 CA-CSM (CA-MSM) Syschange (change tracking) Output management VPS & DRS : Printserver CA-View & CA-Deliver : archiving joboutput

6 Job scheduling Control/M Monitoring/Reporting Omegamon CMF CA-Vantage SAS (on Linux) Application server CICS Messaging WebSphere MQ for z/os Databases DB2, CA-IDMS, Objectstar Mainframe software 2 History

7 2007 Introduction of DB2 on Mainframe. First installation of OMEGAMON-product : OMEGAMON for DB OMEGAMON suite replaces ASG-monitors. One product that monitors the complete mainframe environment : z/os MQ CICS TCPIP Storage DB2 First experience with Omegamon 3270 user interfaces were not as userfriendly as the ones we had before Where to find what? CUA or Classic Classic looks like it was build 30 years ago. Numerous problems and PMR s Configuration with ICAT. Pain in the How to get out of this misery? Contact with local IBM people and support team zcac : z/os Customer Advisory Council EAP : Early Access Program Beta-program

8 RTE configuration using PARMGEN Self Describing Agents (SDA). Synchronize product application support. Announcement of Enhanced 3270 User Interface (E3270UI) New green screen user interface View enterprise summary of multiple sysplexes Navigate from one OMEGAMON agent to the other (eg from z/os to CICS) Top consumers view Built-in problem solving senarios Today Less problems with the software itself Colleagues are more and more comfortable with the TEP CUA E3270UI

9 Tomorrow Continuous improvements : PARMGEN FTU Streamline the PARMGEN process for First Time Users E3270UI More products More features Near Term History (NTH) Remark : RMF is prerequisite for z/os-nth Will replace CUA in the future. No plan to stop with the ClassicUI. Documentation OMEGAMON Transparent Development Community

10 3 Tivoli Environment ITM MQ Agent on Linux ITM MQ Agent on Windows ITM MQ Agent on AS/400

11 4 Usage TEP : z/os workspace

12 Situations Situations

13 Situations Situations

14 TEP : CICS workspace TEP : MQ workspace

15 TEP : MQ workspace TEP : MQ workspace

16 E3270UI E3270UI

17 E3270UI Top Consumer for SYSPLEX

18 Top Consumer for SYSPLEX E3270UI

19 E3270UI E3270UI

20 4-Hour rolling average MSU CICS regions

21 CICS Task Summary FIND command

22 FIND command 5 Installation/Configuration

23 Installation and Configuration Tool JOBGEN

24 PARMGEN Ultimate goal of the PARMGEN-application is to have a set of RunTime Environmentlibraries (aka RTE-libraries, <hlq>.rk*-libraries) that are tailored for your environment. An RTE is at LPAR-leveland all subsystems you want to monitor on that LPAR must be configured in that RTE. All LPAR s may have a different set of subsystems to monitor, so configuration is needed. Goal Step 1 : Start PARMGEN-application Make sure all PARMGEN-users see the same PARMGEN-environment and can select an RTE to work with. How Enter values for The global library. Will be shared by all RTE s within the environment HLQ for the PARMGEN-work-libraries RTE-name Result The above values are stored in your ISPPROF-member. Every user must specify these parameters once. From this point on, all parameters and settings are shared by all users.

25 Goal Step 2 : build PARMGEN-work-environment Allocate and tailor a PARMGEN-work-environment for that RTE. How Walk through PARMGEN ISPF-application and fill in the parameters that are valid/needed for your environment. Submit KCIJPCFG-job Result Updated member KCIDJP02 in the global library Allocates PARMGEN-RTE-work-environment-datasets *.WCONFIG : PARMGEN configuration library *.IK* : product runtime member templates *.WK* : interim staging libraries Creates jobs in *.WCONFIG to be able to complete the RTE-configuration Goal Step 3 : Complete the RTE-configuration Have tailored profiles specific for your RTE. How The steps to complete depend on the scenario you choose. The different scenarios are described in SC Create a brand new RTE from scratch (models will be provided) Convert ICAT-rte to PARMGEN-rte Upgrade PARMGEN managed RTE after installing SMP-maintenance Tailor PARMGEN configuration profile *.WCONFIG(<rte-id>). Overview all parameters and check whether you need to change them or not. System variables can be used to be able to change parameters at system startup instead of hard-coding in the RTE-libraries (see SC Appendix C).

26 Step 3 : Complete the RTE-configuration Result Populated IK* libraries Tailored PARMGEN-members in WCONFIG Profile members WCONFIG(<rte-id>) LPAR specific config profile WCONFIG($GLB$USR) Global system libraries. Can be copied to other RTE s to configure <global library>(<rte-id>) System variables config profile IMBED members Used for statements and settings not available in the profiles Goal Ready to use RTE-libraries How Step 4 : complete PARMGEN setup Submit a number of jobs one by one or submit the composite master job. Result <HLQ>.RK* datasets with members specific for your environment and tailored using the profile-members from *.WCONFIG. See also the figure in SC chapter 1

27 6 Questions?

28 Request for enhancement

29 Defined capacity MSU limit nearly reached Soft capped

30 Also interested? Please vote! Vote as User Group?? Private / Public