z/os Guide Share Europe z/os, ziip and DataWareHouse with DB2 in Toyota Motor Europe

Transcription

1 z/os Guide Share Europe z/os, ziip and DataWareHouse with DB2 in Toyota Motor Europe Hein Vandenabeele z/os Team Leader 17Mar2010

2 Agenda Toyota In Europe z/os in TME ziip in TME DataWareHouse in TME Questions?

3 Toyota In Europe

4 Toyota In Europe First vehicle imported in 1963 HO in Brussels / Evere NMSCs (TBEL, TDE, TGB, ) EMCs (Plants - TMUK, TMMF, TMMT, TMMP, ) HUBs (Ports - Zeebrugge, Malmo, Hanko, ) TPC (Parts Center Diest, Le Pouzin, ) R2D2 (Nice) Dealers (x1000) Belgium is VERY important to TME Strong link with TMC (Toyota Motor Corporation)

5 Toyota In Europe

6 Toyota In Europe

7 IT Infrastructure in TME z Series 2 z9 AIX / Sun Solaris: 150 virtual on 60 physical machines Power5, Power6 AS/400: 18 lpars on 3 physical machines Windows 23 VM Ware Physical ESX Servers 340 Virtual Machines (Lotus Notes, FileSharing, Print Servers, Web, ) Linux

8 zos in TME

9 Computer Rooms in TME HO4N CR TASC CR

10 MainFrame HeadCount Infrastructure Teams: zos Team: 3 ppl (incl storage mgmt) DBA Team: 7 ppl (incl CICS, MQS, Version Mgmt) Development: Sales (Brussels) RDMC (Derby UK)

11 z Series in TME - I 2 x z9 EC S MIPS in two locations 200m apart (HO4N TASC buildings) 4 GP each 1 ICF 1 ziip each Dasd: 2 Sun/STK V2Xf PPRC Migration to IBM DS8300 ongoing Implementation of HyperSwap Tape: 2 IBM ATL 3494, H1A tape units, 3000 tapes Media3 (Blue) / Media 4 (Green)

12 z Series in TME - II zos V1R10 since Feb2010 DB2 V8 CICS TS V2R3 (EOS - $$$ ) MQS V5R3M1 (EOS - $$$ ) IMS V8 (EOS - $$$ ) Programming Languages Cobol PLI C (NatStar) Java Some ASM

13 z Series in TME - III System Automation + NetView (Autom. Operat.) TWS (Scheduling) BMC MainView DB2, CICS, MQS, zos (System Monitoring) IBM DB2 Tools Coming from BMC DB2 Tools ConnectDirect (Data Transfer) XFB (Data Transfer) Beta 92, 93 (Output Management) MXG, SAS (Reporting, Capacity Planning) ISPW (Version Management)

14 z Series in TME - IV 5 Production Lpars (PRD0, PRD1, PRD2 = Sales PROD, TEST = RDMC) 2 ICF Parallel Sysplex DB2 DataSharing NO MQ Sharing (yet) Balancing batch workload amongst lpars using WLM Resources (Sales - PRD0/PRD1) Communication Server SysPlex Distributor (DDF, FTP, Telnet, CICS Listener) Lots of CF Structures (RACF, VTAM, JES2, IMS, GRS, MQS, OperLog, HSM, DB2, )

15 z Series in TME - V

16 z Series in TME - VI

17

18 z Series in TME - VII

19 z Series in TME CP - I WLM Report Class per Application Workload Type (Batch, Online, DDF, TSO, ) Environment Use of Business Drivers for the BIG applications Collaboration With Business Application of growth factor per application / type Input for xls that provides forecast

20 z Series in TME CP - II

21 zos in TME Costing Model We use PSLC. According to IBM we are (almost) The Last Of The Mohicans Study for VWLC has been done more than once. Conclusion: it is 20% more expensive. Reasons: ULC for MQS and IMS High average usage (> 90%)

22 zos in TME Future Plans - I We migrated to zos V1R6, V1R8 and now V1R10. No migration to zos V1R11 foreseen. Check zos guides for new features, we haven t done that for a long time. It might be useful. RoadMap: create a detailed plan for 0 yr < 1 yr 1 yr < 2 yr 2 yr <

23

24 zos in TME Future Plans - II Some Highlights: MQ Queue Sharing Study z10 Create (almost) Perfect (Sales) Plex DataSharing for RDMC (now only Sales DB2P) Study zlinux (To IBM: It says Study ) Study WebSphere on zos (idem) PPP (Possible Political Problems )

25 ziip in TME

26 ziip What is the 50%?

27 ziip Usage in TME DB2: DDF All day long Rebuild Indexes Out of peak hours All lpars Query //: experimented but no big success DFSORT (with some apars) Out of peak hours Since zaapziip (zos V1R10 Mid Feb2010): Java Batch Jobs All day long Online Jetty Java Application Server All All lpars

28 ziip DW2P Results

29 ziip Overall DB2 Results

30 ziip - Later

31 ziip in TME - Latest

32 ziip in TME $$$ Justification zos V1R8, no zaapziip

33 ziip in TME Future Plans Create Capacity Plan for ziip. Not really needed as not fully used. However at some moments they are used up to 80%-90%. Use of XRMFINT table in SAS which contains a WEALTH of information.. z9? More powerful ziips (985 MIPS z10 EC). Target = 2 per CEC. IBM: better start thinking. Other ISV? Now only BMC MainView zos, DB2 Tools DB2 V8+: Native Stored Procs

34 DWH on z Series in TME

35 DataWareHouse in TME - I What is it? Purpose? Infrastructure? Users? Development?

36 DataWareHouse in TME - I Purpose: Create Operational Reporting Create Cubes Multidimensional structure to analyse data Like an xls but with more axes

37 Cube - I

38 Cube - II

39 Cube - III

40 DataWareHouse in TME - I HardWare InfraStructure: z9 Cognos on Windows NT / 2000 SoftWare InfraStructure: PowerPlay Being replaced by IBM Cognos ReportNet (Cognos8 Web Based) Cubes Cognos 7 / Impromptu Being phased out Reporting

41 DataWareHouse in TME - II Users: 14 NMSC TME Users (Central Warranty, New Parts, Vehicle): x100 Development 1 IT Admin + Reporting 2 Key Users Reporting

42 DataWareHouse in TME - ziip

43 DataWareHouse in TME - III

44 DataWareHouse in TME - ziip

45 DataWareHouse in TME - SDR

46 DataWareHouse in TME - SDR Different Data Sources from which to distill reports

47 DataWareHouse in TME - SDR PowerDesigner used as modeling tool Different Data Models for different Data Sources

48 DataWareHouse in TME - SDR Most Data comes from z DB2: - Source - Target IBM InfoSphere DataStage

49 DataWareHouse in TME - SDR

50 DataWareHouse in TME - QREP BMC LogManager: Now used to scan logs and apply changes to DWH tables Several drawbacks: Logs are scanned more than once (once per application) Leadtime for application Not real time Queue Replication (QREP): IBM solution to use MQS to get the same result but better Several advantages: Real time replication Single scan of logs Easier management

51 DataWareHouse in TME - QREP

52 DataWareHouse in TME - QREP The IBM $$$ Problem: QREP comes with MQS (now V6) under the covers for which we do NOT have to pay. We have an ULC licence for the normal MQS usage which uses the SMF89 for billing (now V5R3) The MULC report distinguishes between MQ Versions so today no problem If we ever run the same version of MQ for these two functionalities than we will not see the difference in the SMF records. Only base for differentiating is the MQ SubSystem! But how will we sort SMF89?

53 Questions

54 Thank you