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

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

3. HORIZONT 3 XINFO ® SUB4PGM2 SUB3PGM2 SUB2PGM2 SUB1PGM2 SUB3PGM1 SUB2PGM1 SUB1PGM1SUB1PGM2 SUB2PGM2 SUB3PGM2 SUB4PGM2 Production STEPLIB PROD.LOAD Development STEPLIB ENTW.LOAD TEST.LOAD PROD.LOAD Test STEPLIB TEST.LOAD PROD.LOAD SUB1PGM1 SUB2PGM1 SUB3PGM1 Multi Client Support XINFO-BXINFO-A SYSPLEX DB2A JCL SchedulerX DB2B JCL SchedulerY

4. HORIZONT 4 XINFO ® Multi Client Support 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 Up to now it was necessary to install one XINFO per company/group/department. XINFO 3.0 will offer an alternative:

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

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

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

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

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

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

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

12. HORIZONT 12 XINFO ® //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 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: Scan A-Jobs Scan B-Jobs

13. HORIZONT 13 XINFO ® //XXRILAD EXEC PGM=XXRILAD8,PARM=(‘/SYS=OP8C’) //ADDKEY DD * USEKEY=KEY001 // DD DSN=XINFO.PARM(XXRKKEY) //LADADI DD DSN=SYSH.OP8C.AD 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: A- and B-Jobs together

14. HORIZONT 14 XINFO ® 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 See XINFO.SAMPLIB(XXRJDBUP) //DBUPDATE EXEC XXRJ2TSO //SYSIN DD * UPDATE XINFO30.XXRTOP SET XXRDATCLIENT = ’CLIENTB’ WHERE ADRID LIKE ’B%’;

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

16. HORIZONT 16 XINFO ® XINFO with Client Columns

17. HORIZONT 17 XINFO ® XINFO with Client Columns

18. HORIZONT 18 XINFO ® The Security Concept 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. Single users or groups of users should see only their own data. e.g.:

19. HORIZONT 19 XINFO ® XINFO Security Exit 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) XINFO has an exit to perform RACF checks:

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

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

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

23. HORIZONT 23 XINFO ® PROD and TEST in one XINFO SYSPLEX DB2A JCL- JOBA* SchedulerX XINFO DB2B JCL- JB*, JO* DB2T JCL- TJOB* SchedulerX 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. HORIZONT 24 XINFO ® PROD and TEST in one XINFO? SYSPLEX DB2A JCL- JOBA* SchedulerX XINFO DB2B JCL- JB*, JO* DB2T JCL- TJOB* SchedulerX TESTPLEX 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. HORIZONT 25 XINFO ® One XINFO per "Environment" SYSPLEX DB2A JCL- JOBA* SchedulerX XINFOP DB2B JCL- JB*, JO* DB2T JCL- TJOB* SchedulerX If the testsystem is totally separated from production, it may be better to use a separate XINFO. TESTPLEX XINFOT

26. HORIZONT 26 XINFO ® Hierarchical "Environments" 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) The source analysis supports hierarchical development stages

27. HORIZONT 27 XINFO ® Hierarchy of Program Calls PGM1SUB1 PGM1SUB2 PGM1SUB3 PGM2SUB1 PGM2SUB2 PGM2SUB3 PGM2SUB4 PGM2SUB1 PGM2SUB2 PGM2 Production STEPLIB PROD.LOAD Test STEPLIB TEST.LOAD PROD.LOAD

28. HORIZONT 28 XINFO ® Hierarchy of Program Calls PGM1SUB1 PGM1SUB2 PGM1SUB3 PGM2SUB1 PGM2SUB2 PGM2SUB3 PGM2SUB4 PGM2SUB1 PGM2SUB2 PGM2SUB3 PGM2SUB4 Production STEPLIB PROD.LOAD Development STEPLIB ENTW.LOAD TEST.LOAD PROD.LOAD Test STEPLIB TEST.LOAD PROD.LOAD PGM1SUB1 PGM1

29. HORIZONT 29 XINFO ® Hierarchy of Program Calls PGM1SUB1 PGM1SUB2 PGM1SUB3 PGM2SUB1 PGM2SUB2 PGM2SUB3 PGM2SUB4 PGM2SUB1 PGM2SUB2 PGM2SUB3 PGM2SUB4 Production STEPLIB PROD.LOAD Development STEPLIB ENTW.LOAD TEST.LOAD PROD.LOAD Test STEPLIB TEST.LOAD PROD.LOAD PGM1SUB1 PGM1SUB2 PGM1SUB3

30. HORIZONT 30 XINFO ® Hierarchy of Program Calls DevelopmentTestProduction PGM1SUB1 PGM1SUB2 PGM1SUB3 PGM2SUB1 PGM2SUB2 PGM2SUB3 PGM2SUB4 PGM2SUB1 PGM2SUB2 PGM2SUB3 PGM2SUB4 STEPLIB PROD.LOADSTEPLIB ENTW.LOAD TEST.LOAD PROD.LOAD STEPLIB TEST.LOAD PROD.LOAD PGM1SUB1 PGM1SUB2 PGM1SUB3 Every development stage requires a source scan with appropriate keys, e.g. DEV, PROD, and TEST for environment

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

32. HORIZONT 32 XINFO ® XINFO and "Environments"

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

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

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

36. HORIZONT 36 XINFO ® Data Flowcharts

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

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

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

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

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

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

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

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

45. HORIZONT 45 XINFO ® 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 XINFO 3.0 introduces a new flowchart, the Job/Data Flowchart:

46. HORIZONT 46 XINFO ® Job/Data Flowchart JOB4 JOB1 JOB3 PGM1PGM2 A.B.C TABA JOB2 PGM2PGM3 D.E.F: PGM4PGM5 G.H.I JOB1JOB2 JOB3 JOB4 K.L.M TABA "Old" data flowchart "New" job/data flowchart

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

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

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

50. HORIZONT 50 XINFO ® XINFO and CICS

51. HORIZONT 51 XINFO ® XINFO and CICS Complete overview about all CSD data Complete Cross Reference, e.g. - Batch and CICS - COBOL and CICS - PL/1 and CICS XINFO‘s CICS scanner analyzes the CSD file:

52. HORIZONT 52 XINFO ® Why analyzing the CSD file? "Normal" IT personal like production planners have no detailed knowledge about internal structures of CICS. "Normal" IT personal like operators have no access to CICS data A standard "Cross Reference" for CICS does not exist Typical questions like "which CICS programs are currently using file A.B.C" cannot be answered easily

53. HORIZONT 53 XINFO ® XINFO and CICS ListGroup 1 Group nTransaction 1 Transaction nProgram 1 Program n MAPSE T FILE (DD and DSN) Transient data Queue The Structure of XINFO's CICS Implementation:

54. HORIZONT 54 XINFO ® XINFO and CICS Which programs belong to which transactions? Which programs are running below the 16M line? Which programs are running in a remote CICS? Which files are password protected? Which files are still BDAM? Which programs use key=CICS? Which "TDQUEUE" is used in a remote CICS? Which DB2 subsystems are used? Which DB2 plans are used? Which TCP/IP services are using which ports?... Some examples:

55. HORIZONT 55 XINFO ® CICS - Displays The displays for CICS… (28 predefined queries!)

56. HORIZONT 56 XINFO ® CICS - transactions 1. Select "Transaction Info" Which programs belong to a transaction? 2. Specify transaction

57. HORIZONT 57 XINFO ® CICS - transactions These programs belong to transaction AC03 Details

58. HORIZONT 58 XINFO ® CICS – transactions and programs Use the right mouse to op up the CICS menu, then select "Program Information"

59. HORIZONT 59 XINFO ® CICS – transactions and programs Detailed lnfo

60. HORIZONT 60 XINFO ® CICS – programs Which PL1 or COBOL programs are running below the 16M line? 1. Select "Program Info" 2. Scroll down

61. HORIZONT 61 XINFO ® CICS – programs 3. Specify 99 at "Language" to get more selection fields 4. Specify languages

62. HORIZONT 62 XINFO ® CICS – programs These programs are running below the line

63. HORIZONT 63 XINFO ® CICS – files Which files are defined in a remote CICS? 1. Select "Dataset Info" 2. Scroll down

64. HORIZONT 64 XINFO ® CICS – files 3. Specify NB at "Remote System Name" (not blank)

65. HORIZONT 65 XINFO ® CICS – files Filenames

66. HORIZONT 66 XINFO ® The difference Without XINFO With XINFO Following example illustrates the difference....

67. HORIZONT 67 XINFO ® CICS information without XINFO 1) Type Command CEDA An Example: Which CICS files have fixed LRECL ?

68. HORIZONT 68 XINFO ® CICS information without XINFO 2) Specify selection criteria Do you really know that command?

69. HORIZONT 69 XINFO ® CICS information without XINFO 3) The results are the files in several groups for one CICS. 4) Type View in front the group …..

70. HORIZONT 70 XINFO ® CICS information without XINFO 5) Here is the first file Description, Now HIT PF11 to got next page…… 6) Now PF11 to see the next page……

71. HORIZONT 71 XINFO ® CICS information without XINFO 7) Here is the result for one file, But: For the Next file, hit PF11, and so on………… Searching for information without XINFO is difficult and costs time!

72. HORIZONT 72 XINFO ® CICS information with XINFO 1) Select Dataset Info And now the same work with XINFO:

73. HORIZONT 73 XINFO ® CICS information with XINFO 2) Type Record Format F

74. HORIZONT 74 XINFO ® CICS information with XINFO 3) Here are the files with RECFM = F

75. HORIZONT 75 XINFO ® XINFO and UC4

76. HORIZONT 76 XINFO ® UC4 Scanner The database of UC4 and its objects - JOBS - JOBP (Jobplan) - SYNC - SCHD (Schedule) Statistic (Job runtimes) SAP Variants UC4 is one of the leading schedulers for Open Systems. The XINFO scanner analyses:

77. HORIZONT 77 XINFO ® UC4 Scanner “Built-in” jobnetplans are not clear (see following examples) The UC4 dialog has no built-in “Cross-Reference” that allows you to search for all values by using comparison operators, AND-OR logic, from-to ranges etc. The UC4 dialog has no export functions for various standard formats like Excel, HTML, VISIO, JPEG The UC4 dialog requires special user privileges The UC4 dialog requires special knowledge UC4 offers everything a scheduler needs, but:

78. HORIZONT 78 XINFO ® UC4 Dialog - Graphics Does that job really have 5 predecessors? 1 2 3 4 5

79. HORIZONT 79 XINFO ® UC4 Dialog - Graphics No, this job has only four predecessors. The problem is caused by that link! 1 2 3 4

80. HORIZONT 80 XINFO ® XINFO Dialog - Graphics XINFO displays that correctly

81. HORIZONT 81 XINFO ® UC4 Dialog - Printing Printing netplans?

82. HORIZONT 82 XINFO ® UC4 Dialog - Printing Printing yes, but netplans, sorry, No.

83. HORIZONT 83 XINFO ® XINFO Dialog - Printing XINFO prints netplans on all devices (printers, plotters etc.)

84. HORIZONT 84 XINFO ® XINFO – UC4 Netplans XINFO groups jobs graphically by Job plan (or any other field)

85. HORIZONT 85 XINFO ® XINFO – UC4 Netplans Go directly to related data, e.g. the Job plan definition

86. HORIZONT 86 XINFO ® XINFO – UC4 Netplans …the Job plan definition…

87. HORIZONT 87 XINFO ® XINFO – UC4 Job Runtime Total number of jobs Time axis Jobnames Error job

88. HORIZONT 88 XINFO ® XINFO – UC4 Cross Reference UC4 Cross Reference in XINFO An example: You need an overview about all jobs that did run at 30.9.2003

89. HORIZONT 89 XINFO ® XINFO – UC4 Cross Reference The resulting jobs (taken from UC4 statistics)

90. HORIZONT 90 XINFO ® XINFO – UC4 Data Export You need to export that data, e.g. to HTML?

91. HORIZONT 91 XINFO ® XINFO – UC4 Data Export Your UC4 data as an HTML file…

92. HORIZONT 92 XINFO ® XINFO – UC4 Data Export …or as an EXCEL spreadsheet XINFO supports TXT, HTML, EXCEL, VISIO, JPEG, BMP, GIF etc.

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