The IT Information System

1. XINFO The IT Information System XINFO 3.0 HORIZONT Software for Datacenters Garmischer Str. 8 D- 80339 München Tel ++49(0)89 / 540 162 - 0www.horizont-it.com

2. What’s New in XINFO 3.0 Multi Client Support Data Job Flowchart CICS Scanner UC4 Scanner

3. Multi Client Support Development Test Production STEPLIB ENTW.LOAD TEST.LOAD PROD.LOAD STEPLIB TEST.LOAD PROD.LOAD STEPLIB PROD.LOAD SchedulerX PGM1 SUB1 PGM2 SUB1 PGM1 SUB1 SchedulerY PGM1 SUB2 PGM2 SUB2 PGM1 SUB2 PGM1 SUB3 PGM2 SUB3 PGM1 SUB3 JCL PGM2 SUB4 PGM2 SUB1 PGM2 SUB2 JCL PGM2 SUB3 PGM2 SUB4 SYSPLEX DB2A DB2B XINFO-A XINFO-B

4. Multi Client Support • Up to now it was necessary to install one XINFO per company/group/department. XINFO 3.0 will offer an alternative: • All tables have three preceding “Origin” columns to identify the origin of data • Client (=Company, Organisation, Site) • Environment (Test, Production) • Additional free column, e.g. project, application • RACF exit to ensure security

5. One Client SYSPLEXA SchedulerX JCL- JOBA* DB2A XINFO Client “A”, one Sysplex with multiple LPARs “normal” XINFO IT-Personal from “A”

6. Two Separate Clients SYSPLEXA SYSPLEXB SchedulerX SchedulerY JCL- JOBA* JCL- JB* DB2A DB2B XINFO-A XINFO-B Fusion or FM with Client “B”, one more Sysplex 2nd XINFO, as long as systems are separated if authorised

7. Two Clients SchedulerX SchedulerY JCL- JOBA* JCL- JB* DB2A DB2B XINFO-A XINFO-B SYSPLEX The integration of two Clients into one single "IT" world requires the integration of two separate XINFO into one single XINFO

8. Two Clients, one XINFO SchedulerX SchedulerY JCL- JOBA* JCL- JB*, JO* DB2A DB2B XINFO SYSPLEX Scheduler is migrated Job name clashes Überschneidung bei Jobnamen A-User are authorised to see everything B-User should see only B-Jobs

9. Multiple Clients in "old" XINFO • Since the first version it was possible to load multiple schedulers, joblibs etc into one XINFO. • But there where some disadvantages: • No way to see where the data originally came from • No security 

10. Separate Clients • XINFO 3.0 allows to group data. Every table has three preceding columns to identify the source. •  • Client different organisations, sites, departments • EnvironmentDevelopment, test, production • Additional info (Project, zOS/MVS, host/distributed • Additionally some tables have a column for the subsystem, e.g.TWS and DB2

11. Client Keys • First unique keys must be defined that are used by XINFO scanner programs KEY001 CLIENTA PROD KEY002 CLIENTA TEST KEY003 CLIENTB PROD KEY004 CLIENTB TEST PS: Client and Environment are usually sufficient

12. Usage of the Keys • Every instance of a scanner job uses one key and assigns it to the data. As an example the JCL scanner: //JUPIPO EXEC PGM=JUPIPO,... //ADDKEY DD * USEKEY=KEY001 // DD DSN=XINFO.PARM(XXRKKEY) //JUPJI001 DD DSN=CLIENTA.JOBLIB //JUPIPO EXEC PGM=JUPIPO,... //ADDKEY DD * USEKEY=KEY002 // DD DSN=XINFO.PARM(XXRKKEY) //JUPJI001 DD DSN=CLIENTB.JOBLIB ScanA-Jobs Scan B-Jobs

13. Multiple Clients within one Subsys • This is not sufficient, if multiple clients are used within one subsystem, separated by an internal field, e.g. the TWS owner. An example: //XXRILAD EXEC PGM=XXRILAD8,PARM=(‘/SYS=OP8C’) //ADDKEY DD * USEKEY=KEY001 // DD DSN=XINFO.PARM(XXRKKEY) //LADADI DD DSN=SYSH.OP8C.AD A- and B-Jobs together

14. Multiple Clients in one Subsys • In this case XINFO has a utility program that corrects the client columns after having loaded the data into the XINFO database //DBUPDATE EXEC XXRJ2TSO //SYSIN DD * UPDATE XINFO30.XXRTOP SET XXRDATCLIENT = ’CLIENTB’ WHERE ADRID LIKE ’B%’; See XINFO.SAMPLIB(XXRJDBUP)

15. How to activate Client Columns • Right after the installation you must run a XINFO job to activate the client colums //SYSIN DD * ... USECOL XXRTOP Y Y N USECOL XXRTDDF Y Y N ... Client Environment Additional field

16. XINFO with Client Columns

17. XINFO with Client Columns

18. The Security Concept • Single users or groups of users should see only their own data. e.g.: • Some user should see only their own data, but admins should see everything • Within one client some persons should see only selected data (e.g. the SYSIN data of payroll jobs) • Since the first version of XINFO it was possible to protect data by using RDBM grant, now you can use RACF to protect data.

19. XINFO Security Exit • XINFO has an exit to perform RACF checks: • Use Macro XXRSECP to define Which tables and which columns should be checked against which profiles • Right after having assembled it, the exit is active • New RACF profiles can be generated, or you can use existing profiles (e.g. the OPCLASS profiles)

20. Macro XXRSECP • An example: Security by using column "client" with a profile of OPCCLASS 2) Plus contents of column Client ... SECPARM DS 0D XXRSECP TAB=*,PREF=ADG.,COL=XXRDATCLIENT,CLASS=OPCCLASS RACF-Profiles: ADG.CLIENTA ADG.CLIENTB All tables 1) “ADG.” 3) Results in the name used by the RACF check

21. Macro XXRSECP • Example: Protect JCL data by using column JCLLIB with an appropriate DSN profile • SECPARM DS 0D • XXRSECP TAB=XXRTJOB,PREF=,COL=JOBLIB,CLASS=DATASET • RACF-Profiles: • ‘CLIENTA.JOBLIB‘ • ‘CLIENTB.JOBLIB‘ Table JCL Jobstatement 1) Contents of column JOBLIB 2) Contains DSN for RACF check

22. Integration of "Environments" SchedulerX SchedulerX JCL- JOBA* JCL- TJOB* JCL- JB*, JO* DB2T DB2A DB2B XINFO SYSPLEX PROD (production), XINFO is enabled for clients TEST

23. PROD and TEST in one XINFO SchedulerX SchedulerX JCL- JOBA* JCL- TJOB* JCL- JB*, JO* DB2T DB2A DB2B XINFO SYSPLEX A testsystem can be integrated by using column “Environment”. For the scanners appropriate keys must be defined. Client and Environment can be used together.

24. PROD and TEST in one XINFO? SchedulerX SchedulerX JCL- JOBA* JCL- TJOB* JCL- JB*, JO* DB2T DB2A DB2B XINFO TESTPLEX SYSPLEX If the testsystem is separated from production, the scan can be done on the testsystem. After that the data are transferred to the other system and loaded into the centralised XINFO

25. One XINFO per "Environment" SchedulerX SchedulerX JCL- JOBA* JCL- TJOB* JCL- JB*, JO* DB2T DB2A DB2B XINFOT XINFOP TESTPLEX SYSPLEX If the testsystem is totally separated from production, it may be better to use a separate XINFO.

26. Hierarchical "Environments" • The source analysis supports hierarchical development stages PROD is prior to TEST: If a subprogram does not exist in TEST, then the version from PROD is displayed (but not the other way around)

27. Hierarchy of Program Calls Test Production STEPLIB TEST.LOAD PROD.LOAD STEPLIB PROD.LOAD

28. Hierarchy of Program Calls Development Test Production STEPLIB ENTW.LOAD TEST.LOAD PROD.LOAD STEPLIB TEST.LOAD PROD.LOAD STEPLIB PROD.LOAD

29. Hierarchy of Program Calls Development Test Production STEPLIB ENTW.LOAD TEST.LOAD PROD.LOAD STEPLIB TEST.LOAD PROD.LOAD STEPLIB PROD.LOAD

30. Hierarchy of Program Calls Development Test Production STEPLIB ENTW.LOAD TEST.LOAD PROD.LOAD STEPLIB TEST.LOAD PROD.LOAD STEPLIB PROD.LOAD Every development stage requires a source scan with appropriate keys, e.g. DEV, PROD, and TEST for environment

31. Program XXRIMSP • After having loaded the data, a XINFO program reorganizes all the data to support the hierarchy: //XXRIMSP EXEC PGM=XXRIMSP,... ... //SYSIN DD * ORDER=PROD ORDER=TEST ORDER=ENTW ... Specifies the hierarchy (values must match environment set in scan job)

32. XINFO and "Environments"

33. XINFO and "Environments" Environment Subprogram (Prod/Test/Dev) Client Main program Subprogram Environment main program (Prod/Test/Dev)

34. Clients in XINFO Release • XINFO versions and Multiple client support • Release 2.3 • Client columns • Environments • Release 3.0 • Client columns • Environments • Security • Better support by XINFO utilities

35. Activate clients in XINFO • Following documents are available: • XINFO Manual "Multi Client Support" (xxrdmlte.pdf) • XINFO Manual "Scanner Programs Guide" (xxrdpgme.pdf) • or simply ask HORIZONT's hotline:support@horizont-it.com

36. Data Flowcharts

37. XINFO Data Flowcharts Improved Data Flowchart and New Job/Dataflowchart

38. Data Flowchart - Selection Recommendation: Up to 10 Jobs, (Use generic or "99" selection) Recommendation: Predecessor: 0 Successor: 0

39. Data Flowchart - Overview 1. Job (XXRJDC) 2. Job (XXRJDC) 3. Job (XXRJDBLK) For example: XINFO Space Scanner Jobs

40. Data Flowchart – How to read it Job1 DISP=NEW File Job2 DISP=SHR Input file from “outside” The red line shows a scheduler dependency: From the first step of Job1 to the last step to Job2 SYSIN DD *

41. Data Flowchart - With DB2 DB2 program Load statements SYSIN LOAD / Update DB2 table Here is an input file

42. Data Flowchart - Options DSN can be excluded (local at the PC client and global at the scanner program)

43. Data Flowchart - Options The search function helps to navigate. If you search for all files (*), you'll get a DSN list

44. Data Flowchart - Options Just a simple left mouseclick to move the flowchart directly to the DSN:

45. Job/Data Flowchart XINFO 3.0 introduces a new flowchart, the Job/Data Flowchart: • The Job/Data flowchart shows only jobs and external files (Files that are used by more than one job). Internal file (files that are only used within one job, e.g. temp files) are not displayed • Dependencies that are defined in the scheduler are also displayed • This allows to compare file dependencies to scheduler dependencies

46. Job/Data Flowchart JOB1 JOB2 PGM1 PGM2 PGM2 PGM3 A.B.C D.E.F: TABA JOB4 JOB3 PGM4 PGM5 G.H.I JOB1 JOB2 TABA JOB4 JOB3 K.L.M "Old" data flowchart "New" job/data flowchart

47. Job/Data Flowchart - Selection Recommendation: Up to 20 jobs, Generic or by using "99" Pred/Succ: 0

48. Job/Data Flowchart - Overview 3. Job (XXRJDBLK) 2. Job (XXRJDC) 1. Job (XXRJDC) Output-File Job1 = Input-File Job2 The job dependency that is defined in the scheduler DB2 tables

49. Job/Data Flowchart - Overview Here the file and scheduler dependencies are OK

50. XINFO and CICS