1 / 27

Beta92 V4R3 New Functions

Beta92 V4R3 New Functions. 14./15. April 2008 Working Commitee Beta92 in Munich at BMW Christian Bressler. Agenda. Who is Beta Systems? Berlin „z/OS lab“ History „Joblog Archiving“ Beta92 V4.3 new functions Reader (Jes SAPI, Open Systems) Enterprise Syslog Management

moriah
Télécharger la présentation

Beta92 V4R3 New Functions

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. Beta92 V4R3 New Functions 14./15. April 2008 Working Commitee Beta92 in Munich at BMW Christian Bressler

  2. Agenda • Who is Beta Systems? • Berlin „z/OS lab“ • History „Joblog Archiving“ • Beta92 V4.3 new functions • Reader (Jes SAPI, Open Systems) • Enterprise Syslog Management • Event processing • Requirements

  3. Who is Beta Systems? • Established 1983 „25 years Beta Systems“ • Headquarter in Berlin • Laboritories in Berlin, Calgary, Köln, Augsburg • > 1300 customers • > 600 employees

  4. Berlin Lab • z9 IBM 2094 - mod. S08 • 2 CPs, 1 IFL, 1 zAAP, 1 zIIP • „a total of“ 2900 Mips ~ 400 MSU • Dasd Storage DS8000 (2107-921) 9,6 TB Brutto • VTS with IBM3494

  5. History „Joblog Archiving“ • 80s 30.000 jobs daily • 90s 100.000 jobs daily • Today 200.000 jobs daily • Tomorrow 500.000 jobs daily

  6. Situation today The average will be over 100.000 jobs per year in 2008 === Objectives Version 4: • 500.000 jobs per day • 4 millions of lists per day • 1 milliard lines per day values achieved in the laboratory

  7. Enhanced Jes-SAPI Reader What did we aim for? More ... • Flexibility • Performance • Information

  8. Enhanced Jes-SAPI Reader More selection parameters • all queues • Types: JOB, STC, TSU, APPC • Jobname, Forms, Destination, Owner, Writer • Number of Lines (min/max) Definition / Control • Up to 64 local readers • Any number of remote readers • Online status display (incl. stop/start/restart)

  9. Enhanced Jes-SAPI Reader Beta 92 Enterprise - Process History Manager - V4R3 ------- Row 1 of 6 Command ===> Scroll ===> CSR Reader Definition Table S - Select Reader Definition D - Delete Reader Definition I - Insert Reader Definition C - Copy Reader Definition Only for Reader Name 92T4 : R - Restart Reader F - Freeze Reader Sel Name ID A Startup Classes Jobname Owner Destin Min Lines Max Lines RFF1 00 Y DORMANT Y 0 0 RFF1 66 Y DORMANT Y 0 0 RFF1 88 Y ACTIVE Y 0 0 RFF1 99 Y DORMANT Y 0 0 92T4 00 Y ACTIVE X 0 0 92T4 01 N DORMANT Y 0 0 ******************************* BOTTOM OF DATA ********************************

  10. Enhanced Jes-SAPI Reader Beta 92 Enterprise - Process History Manager - V4R3 --------------------------- Command ===> Update Reader DefinitionLast update: ROMYD2 10.02.2008 09:31:16 Reader Name :92T4 Reader ID : 00 Startup ===>ACTIVE (A)ctive or (D)ormant Sysout Classes ===>X A-Z, 0-9 Additional Selection Criteria Jobname ===> Owner ===> Destination ===> Writer ===> Node Name ===>DEBETAJ2 Minimum Lines ===>0 Maximum Lines ===>0 Forms ===> ===> ===> ===> ===> ===> ===> ===> Queue Selection: HLD ===> NO XWH ===> NO WTR ===> YES Type Selection: JOB ===> YES STC ===> YES TSU ===> YES APPC ===> YES Press ENTER key to update this entry and continue. Press END key to cancel changes or HELP key for help information.

  11. Open Systems Reader „OSY Agents“ What is new ... • SSL • Performance + less z-Mips • Syslog plugin “

  12. Enterprise Syslog Management The idea ... How can we help the „z/OS fraction“ to establish a central log-management? • usecase, examples • plug & play The doorway from MVS-syslog archiving to Enterprise syslog archiving „made easy“

  13. Enterprise Syslog Management Requirements: • „this is not a job“ • Web interface • Selection criteria: System, date, time, search items • Shorttime access (e.g.30 days) immediately • Longtime archiving for several years • Easy implementation on all platforms

  14. Enterprise Syslog Management Beta 92 Enterprise - Process History Manager - V4R3 -------------------------- Option ===> Primary Selection Menu System - B92V43M Location - BERLIN Subsys-ID - 92T4 User ID - CHRIS 1JOB - Display or Print Online Jobs 2RELOAD - Display and Reload Archived Jobs 3UTILITIES - Display Utilities Selection Menu OOPEN SYSTEMS - Unix, Windows, SAP Output Selection Menu LSYSLOG - Display or Print Syslogs EEVENTS - Event Selection Menu PPROFILENNEWSAADMINMMORE Select one of the above options, or pressENDkey to exit. Press theHELPkey from any panel for help information.

  15. Enterprise Syslog Management Beta 92 Enterprise - Process History Manager - V4R3 --------------------------- Command ===> Scroll ===> CSR Display Syslogs Layout: BETA_SYSL_SEARCH Select from last ===>99 days 1-99, (m)inutes, (h)ours, or (d)ays Select from Date ===>HEUTE Time ===>00:00:00 Select to Date ===>HEUTE Time ===>23:59:59 Jobname : SYSL* z/OS System ID ===>* or Agent Name ===> Press ENTER key to display syslogs. Press END key to return to the previous menu.

  16. Enterprise Syslog Management Beta 92 Enterprise - Process History Manager - V4R3 ----- Row 1 of 4 Command ===> Scroll ===> CSR Syslog Select TableSorted by Submit Date and Time D Displayed Submit date and time S,? - Select a syslog W - Toggle work queue K - Toggle keep status P,M - Print/Mail a syslog T - Toggle non-retain X - Toggle nokeep status I - Reset input queue B - Browse a syslog E - Toggle error queue N - Change user notes R - Reload offline syslog Sel Jobname System Date Time Type SYSL1X BETA 28.02.2008 00:00:00 MAINFRAME SYSLBETA BETA 28.02.2008 00:00:00 MAINFRAME SYSLOG JEK43AGE 13.02.2008 00:00:00 OPEN SYSTEMS SYSLOG JEK43AGE 06.02.2008 00:00:00 OPEN SYSTEMS ******************************* BOTTOM OF DATA *******************************

  17. Event Processing (in 3 steps)) Step 1 ... Identification of ... • News, information • Errors • Values

  18. Event Processing (in 3 steps) Step 2 ... Logging of recognized „Events“ Advantages: • Dialog query of the „event database“ • Alternate access to jobs and logs • Batch reporting

  19. Event Processing (in 3 steps) Step 3 ... Execution of certain tasks • eMail transmission • incl. weblink to job/log • Job submission • incl. all available information (variable substitution)

  20. Event Processing (in 3 steps) Yet another step ... Use of „customer specific“ event tables • Arbitrary fields • Example: „Filetransfer analysis • Which FTP program is used where? • Which file is being transfered at what time and from where to where?

  21. Event Processing Beta 92 Enterprise - Process History Manager - V4R3 --------------------------- Command ===> Scroll ===> CSR Display Events by Input Date Layout: BETA_EVNT_SEARCH Select from last ===>99 days 1-99, (m)inutes, (h)ours, or (d)ays Select from Date ===> Time ===> 00:00:00 Select to Date ===> Time ===> 23:59:59 Event Text ===>* Severity ===> (I/W/E) Event ID ===> Category ===> (B)eta,(U)ser Source ===> (H)ostJob,(F)ileRule,(S)APRule Status ===> (I/P/E) Event Jobname ===> System ID ===> Press ENTER key to display events. Press END key to return to the previous menu.

  22. Event Processing Beta 92 Enterprise - Process History Manager - V4R3 ----- Row 1 of 8 Command ===> Scroll ===> CSR Event Select TableSorted by Submit Date and Time D Layout: BETA_EVNT_RESULT S - Select event job I - Display event information Sel Input Date Time Jobname Sev S Event Text 01.04.2008 16:09 B92AGIN2 I P JOB ON ERROR QUEUE: JCLFAIL 01.04.2008 16:07 B92AGIN6 I P HWM REACHED: 81% 01.04.2008 13:57 B92AGINF I P FEHLER -017 01.04.2008 13:47 B92AGINT I P STEP: INFOSTP1.QUEUE ERROR CODE: 0008 01.04.2008 13:47 B92AGINT I P JOB ON ERROR QUEUE: CC 0008 01.04.2008 13:37 B92AGIN3 I P -002 ******************************* BOTTOM OF DATA *******************************

  23. Requirements 2006 / 2007 „paused“ Reason: Readjustment of BSA Version 4 • 64 bit (e.g. for „caching“ of huge amounts of data) • Extended-VSAM (so far only 4GB „linking“) • Standardization of interfaces (necessary after 8 years of V3) • XCF (Sysplex) optimizing (already in V3 available) • Dynamic database enlargement (without downtime)

  24. Requirements Short overview: • TWS E2E, UC4 Joblog archiving (enhanced, standardized) • NOERROR table (also for TWS) • JESJCLIN „what has been submitted“ • „VIEW“ JCL & Logs (temp. Edit) • NEWS „Info-Panel“ • JESSPOOL Security • Print2Mail (Online & Batch) • With attachment or as WebLink

  25. RACF on Joblevel and Listlevel B92.ssid.BRS.jobname.ddname  4. & 5. Qualifier New SAMPLE B92UXSE4 (old: B92UXSEC) ICH408I USER(CHRIS2 ) GROUP(STAFF ) NAME(CHRISTIAN BRESSLER ) 548 B92.B92W.BRS.PRRZ1897.JESJCLIN CL($BETA ) INSUFFICIENT ACCESS AUTHORITY FROM B92.B92W.BRS.*.JESJCLIN (G) ACCESS INTENT(READ ) ACCESS ALLOWED(NONE )

  26. Available end of June 2008 • Tests so far have shown: V4.3 is comparable with V4.1 + V4.2 • In stability • And quality • Are you going to install V4.3 this year ? !!!

  27. “Jeden Tag ein bisschen besser” Thank you for your attention !

More Related