Beta 92 Extended Job Manager - betasystems-dci. · PDF fileBenefits and Advantages of an...

Beta 92 Extended Job Manager

Central Job Management for Distributed Systems

Betasystems PowerPoint Template 2

Slide 2

02.07.2014

Challenges Facing a Job Manager ...

Software whose modularity provides specific extensions to meet specific

customer requirements.

Software that supports nearly every platform and nearly every application

used in the enterprise. [Enterprise]

A presentation layer that is accepted by all users. [Web Interface]

A central database that can reliably handle large quantities of data without

much administrative effort, and which can be integrated into existing

operating concepts.

Transparency in the execution of batch processes [Compliance]


02/07/14

Benefits and Advantages of an Extended Job Manager ...

Investment protection thanks to optimization of existing solutions

Cost reduction in terms of time and human resources during the

implementation phase

Production reliability for distributed batch processes on the basis

of proven structures

Little effort and low costs when introducing new platforms / job

networks into batch production



Slide 4

02.07.2014

Components of Beta 92 EJM ...

Beta 48 STC

• Communication task z/OS scheduler distributed platforms

• All target systems are defined centrally

• Status monitor realtime / history

Beta 92 EJM Tracker

• Communication agent for distributed platforms / Beta 48

• Fault-tolerant archtecture (sysmon, recmon, tracker, logadm)

Beta 92 Web Interface

• PHP interface (monitoring of all batch jobs)

02/07/14

Beta 92 EJM

Architecture Every job is planned using the rules of the existing scheduler. Mainframe jobs are passed to JES 2/3, distributed jobs are passed to the target platforms by Beta 48. Communication between the mainframe and the target system is asynchronous!

Cross-platform job networks can efficiently control processes throughout the entire enterprise. Advantages:

easy integration

standardized structures

modular growth

[ Beta 92 Extended Job Manager ]

Beta 92 ESS Beta 92 ETF Beta 92 WLB Beta 92 HFT

Job-Submit Result

TWS z/OS, CA7,

Control/ M, …[ Beta 92 Enterprise ]

Job-Protokoll

Windows, Linux, UNIX, AS/400, zLinux, SAP NetWeaver

[ Beta 92 EJM Agent ]

02/07/14

Beta 92 EJM Function Module ...

Execution and monitoring of Unix / Windows / SAP Netweaver batch jobs

using [Beta 92 EJM Tracker]

Central administration in Beta 92 Extended Job Manager

Communication agent with fault-tolerant architecture available forall the usual platforms

Monitoring of all started batch jobs incl. central access to the job log

Certified RFC connection to SAP Netweaver standard interface BC-XBP

User-friendly installation routine ensures problem-free software distribution

02/07/14

Execution and monitoring of file transfer from Unix / Windows to z/OS using

[Beta 92 File Transfer]

Secure file transfer to all connected platforms (*)

Monitoring / execution by Beta 48 trackers

Supports all the usual data formats and z/OS DCB parameters

File transfer log available with all the relevant information [Compliance]

Integration of Harbor Highspeed File Transfer is possible

(*) except OS/400

The Beta 92 EJM File Transfer is called as a separate step in the JCL and

can therefore replace an existing file transfer solution.



Slide 8

02.07.2014

In this example file “ test1“ is transferred from z/Linux to z/OS in a PDS

member, conversion from ASCII to EBSDIC takes place implicitly in

accordance with country-specific code pages.


[Beta 92 EJM File Transfer]

#############

# THE STEPS #

#############

##FTPSTEP

METHOD=GET

BINARY=NO

DSNAME= DATASET(SEHAM5.HOT2003.DATA)

::MEMBER(ZLINUX)

::DISP(SHR)

FILENAME=/home/rut/test1

##END

02/07/14


Web-based interface for browsing /starting Unix, Windows,

SAP Netweaver batch jobs with [Beta 92 WIF]

Enterprise-wide access protected by existing data security

concepts (e.g. RACF)

Beta 92 WIF base functions: Start, monitor and analyze

heterogeneous batch jobs

Simple integration into existing WEB server structures

Intuitive, user-friendly interface

02/07/14


Web-based Interface for browsing /starting Unix, Windows, SAP Netweaver batch jobs with

[Beta 48 WIF]

02/07/14

Beta 92 ESS (Extended SAP Support)

Execution and monitoring of batch jobs in SAP Netweaver

Reliable execution of SAP batch jobs as with (SM36)

All available print parameters are passed

Parent/child processing – SAP NetWeaver e-mail support

Dynamic resolution of variables within a variant

Supports various types of SAP background processing

- FS-CD, batch input map, direct input

Supports SAP Netweaver Standard BC-XBP/XMI

Extended SAP functionality (including FS-CD)

Starting BW process chains incl. restart management

Beta 48 for SAP Netweaver is SAP certified and can offer extensive

batch background functions in SAP Netweaver.


Slide 12

02.07.2014

SAP NetWeaver

Beta 92 ESS in a SAP NetWeaver Environment ...

SAP NetWeaver

BC-XMI/XBP BC-XMI/XBPBW-SCH

[ Beta 48 Tracker]

System log

Job logs

Execute process

chains

Execute info package

Return output

Execute different SAP

BBP

Parent/child monitor

Email support

Job log management

[ Beta 92 Extended Job Manager ]

Third Party

Scheduler

TWS z/OS

CA7

Control /M


Slide 13

02.07.2014

Beta 92 ESS in a SAP NetWeaver Environment ...

Example of syntax:

A job with report RSP00041 is is started on system R3N05

under the rights of CPIC User

STW.

In the report, variable MIN_ALT

is given the value “90“. In this

case a copy of the variant is

created and the job is

executed with this copied

variant.

This procedure also supports

the use of scheduler variables

for the execution of dynamic

JCL. No changes need to be

made inSAP NetWeaver.

##HEADER # HEADER STATEMENT

SYSID=R3N05 # SYSID DEFINDIN BETA48 STC

JOBNAME=SAP_PROD4422 # SAP R/3 JOBNAME MAX. 32 CHARACTERS

USER= STW # USER STW

CLIENT= 150 # CLIENT - (999 == UNIX/NT USER)

LANG= EN # LANGUAGE

##END # END OF THE BLOCK

#############

# THE STEPS #

#############

##ABAPSTEP

REPORTID=RSPO0041 # PREDEFINED SAP STANDARD REPORT

VARIANT=TEST # VARIANT PREVIOUSLY DEFINED BY

TRANSACTION

VARIABLE=MIN_ALT,90; # NEW VARIANT FOR VARIABLE TO CHANGE

PRINTRECIP=STW # RECIPIENT

SHOWPASSWD=STW # SHOWPASS

TITLE=HELLO WORLD # PASS TITLE WITH FUNCTION COMPONENT

DESTIN=LJQA # SAP DEFINED PRINTER

PRINTIMM=FALSE # DON'T PRINT IMMEDIATELY

RELEASE=TRUE # DELETE AFTER PRINT

COPIES=001 # NUMBER OF COPIES

PRIARCMODE=1 # PRINT PARAMETER

BANNER=FALSE # PAGE HEADER

BANNERPAGE=TRUE # NO BANNER PAGE

EXPIRATION=3 # DELETE AFTER x DAYS ON SAP SPOOL

NUMLINES=65 # LINES PER PAGE

NUMCOLUMNS=80 # COLUMNS PER PAGE

##END


Slide 14

02.07.2014

The decisive factor for batch

processing in SAP

NetWeaver is the ability to

use different application

servers depending on their

availability. A job should not

be terminated simply

because the status of an

application server is

„unavailable“.

Beta 92 ESS recognizes the

status of every application

server and dynamically

routes the job to a suitable

server.

Beta 92 ESS supports SAP

NetWeaver‘s workload

balancing functionality.

Beta 92 ESS in a SAP Netweaver

Environment

Beta 48 always checks the availability of the system before starting a job in SAP NetWeaver.

Database server

Central entity Application server Application server

BC-XBP

[Beta 48 ESS]


Slide 15

02.07.2014

Beta 92 ESS Solution ...

Beta 92 ESS initiates a “monitor job“

A Beta function module is called to generate the job

Job name & job count as per Beta 92 ESS

“Monitor job“ montors the generated jobs

Job logs with information on the generated jobs

FS-CD Connection to Beta 92 ESS ...

This is a good solution

because the entire process

is monitored, every single

job in Beta 92 ESS is

mapped and can therefore

be selected, performance

is better than when using

FKJO_SCHEDULE, and no

BWPs are needed.

Beta Systems has its own

SAP name space and can

therefore be classified as a

competent software

supplier in this application

segment.


Slide 16

02.07.2014

Beta function module FICA is

called on system TESTSYS

under the rights of SAP

NetWeaver user

TESTUSER.

The FICA function module

generates nn jobs,

depending on the contents of

the parameter block in SAP

NetWeaver.

The actual monitoring of the

jobs that are started is made

on the basis of zombie job

„FICA_TEST_JOB“, which

knows the job names and job

count of the generated FICA

jobs.

FS-CD Connection to Beta 92 ESS ...

Example of syntax ##HEADER # JOB DEFINITION

SYSID= TESTSYS # NAME OF SAP SYSTEM

JOBNAME= FICA_TEST_JOB # 32 CHARACTER JOBNAME

USER= TESTUSER # NAME OF USER FOR FICA

CLIENT= 100 # USERS CLIENT

FBID= FICA # START FICA PROCESSING

############################################################

#

# FICAPARM = <JOB TYPE>,<MASS ACTIVITY>,<RUN DATE>,<RUN ID>,

# <XCOPY>,<COPYD>,<COPYI>

# <JOB TYPE>

# <MASS ACTIVITY> SPACE

# <RUN DATE>

# <RUN ID>

# *)<XCOPY> SPACE

# <COPYD> SPACE

# <COPYI> SPACE

#

# *) ARE FLAGS WITH EXTENDED VALUES

# Y - YES

# N - NO

# D - DEFAULT

# X - YES (LIKE SAP)

# ' '- NO (LIKE SAP)

# ''- DEFAULT (LIKE SAP)

#

FICAPARM=A5,,20011218,TESTUSER

##END


Slide 17

02.07.2014

“Monitor job“ 3N05RBI

has started nine

generated jobs. From

the scheduler

viewpoint, this job is

active and monitors the

execution of the actual

jobs.

The „zombie job“ only

finishes and reports the

results to the scheduler

once the started jobs

have “FINISHED“

status.

FS-CD Connection to Beta 92 ESS...

Monitoring


Slide 18

02.07.2014

Job Abend in SAP Netweaver ....

The abend MSG in the SAP NetWeaver job log is not always clear

and unambiguous

Dump & error messages are held in separate locations in

SAP NetWeaver

Beta 48 consolidates all the relevant information in one job log

Job postprocessing in the familiar environment, no SAP skills or

rights are necessary

Output available in JES , z/OS archive [Beta 92], or over WWW

Beta 92 ESS consolidates all the available job information in a

standard job log. If required, it sends the job log per e-mail to the

person responsible

Facts …


Slide 19

02.07.2014

Consolidating SAP NetWeaver Output ...

This example shows that

Beta 92 ESS consoli-

dates all the relevant job

information in a new job

log.

The SAP NetWeaver

system log has read

2777 records, but the

Beta 92 ESS job log has

written only 18 records.

The advantage of this

procedure is that

Production Planning can

see all the important

error messages without

needing recourse to a

SAP NetWeaver GUI or

the relevant SAP trans-

actions (SM21,SM37)


Slide 20

02.07.2014

Dump Logs and Log Excerpt ...

This example shows that job

B48RUTLX abended in SAP

with RC = 8.

The same information is

available to the scheduler.

In order to analyze the

problem, you need to be able

to view the job log.

Option 2 initiates an ISPF link

to Beta 92.


Slide 21

02.07.2014

The ISPF link to

Beta 92 goes directly

to the job log:

SCRIPT:

STARTLOG:

SYSLOG:

JOBLOG:

All the information

needed for error

analysis are available

centrally.

Dump Log and Log Excerpt ...


Slide 22

02.07.2014

The SYSLOG

provides a detailed

description of the

error that caused

RC=8

This enables the

people responsible at

the data center to

restart the job as

required.

Dump Log and Log Excerpt ...


Slide 23

02.07.2014

Starts UNIX / Windows scripts

Starts UNIX / Windows programs

Passes parameters

Returns RCs to z/OS

Enables script management in z/OS or on the target server

Supports script tool kits

Beta 92 EJM on UNIX/Windows Platforms...

Beta 92 EJM enables you to manage the source of Unix/Windows scripts

in the z/OS scheduler, ensuring greater operational reliability


Slide 24

02.07.2014

Beta 92 EJM on UNIX / Windows Platforms ...

Example syntax

The job starts a

script on a UNIX

system under the

rights of user rut.

The resulting

output is saved

under LONG job

name

ZLIUNUX_HOT200

3_.

#################

# THE JOB INFOS #

#################

##HEADER #HEADER STATEMENT

JOBNAME= ZLINUX_HOT2003 # 32 Charakter

SYSID= RUTEJF #SYSID DEFINED WITHIN BETA48 STC

USER= rut #USER DEFINED WITHIN BETA48 STC

##END #END OF THE BLOCK

#############

# THE STEPS #

#############

##EXTSTEP

SCRIPT=my-testscript

##END


Slide 25

02.07.2014

Merger of all logs from SAP

Transfer of STDout & STDerr to Beta 92 EJM

Re-routing of files to a special DD-OUT

Central job management with Beta 92 Enterprise

Direct link Beta 92 EJM Beta 92 Beta 92 EJM

Direct link TWS Beta 92 EJM Beta92

Special layout structure for TWSE2E users

Beta 92 EJM Job Log Management provides the user with all the information

that‘s needed at a central location in [Beta 92 Enterprise]

Beta 92 EJM Job Log Management ...


Slide 26

02.07.2014

The Beta 92 EJM Activity

Monitor provides the user

with details of all active and

completed SAP, UNIX &

Windows processes at a

glance.

A variety of options supply

the status of all jobs with

e.g. run time, return code,

short abend text.

Beta 92 EJM Central Monitoring ...


Slide 27

02.07.2014

Beta 92 WLB (Workload Balancer)

Fail-Over ManagementRecognizes the condition of the target server within a

virtual domain

Dynamic Workload BalancingExecution of batch jobs on the most suitable

server

Overdrive ExecutionForces job execution without queueing

Beta 92 WLB with its “dynamic workload domains” guarantees

load balancing on all the connected servers


Slide 28

02.07.2014

Beta 92 Workload Balancer ..Basics

Beta 92 WLB Dynamic

Workload Balancing

Definition of individual threshold

values for performance #

Monitoring of server workloads in

terms of CPU, memory, max. no.

of jobs running in parallel

Storage of the returned data in

the Beta 48 Performance DB

Starting / Monitoring of batch jobs,

taking performance measurements

into account

Logging of all performance

data incl. job information


Slide 29

02.07.2014

Beta 92 Workload Balancer

Beta 92 WLB Fail-Over

Definition of “nn” alternative

paths

Monitoring of availability of target

systems

Re-routing of batch jobs to an

active system

Setting “TWS z/OS workstation“

to OFFLINE if target server

“unavailable“

Logging of all activities

Result:

No job cancellations due to an

unavailable server


Slide 30

02.07.2014

Beta 92 Workload Balancer

Beta 92 WLB Overdrive

Beta 48 JCL statement for

defining jobs that are to be

excluded from queueing

Adhoc bypass for high priority

jobs with the Beta 48 “enforce“

command from ISPF

Logging of all jobs executed

with the enforce command

Result

Jobs are not delayed although

max. performance values are

reached on all servers within a

Beta 48 domain


Slide 31

02.07.2014

Beta 92 EJM – Customer References

Project

Facts

Benefits

“Enterprise-wide job control” within the framework of central production control

TWS for z/OS processes 130,000 batch jobs daily, 40,000 of them with Beta 48 EJM

400 connected servers are controlled by Beta 92 EJM

Batch processes are executed under the control of Beta 92 ESS on 70 SAP systems

High level of batch processing through Beta 92 EJM

Beta 92 EJM as component process in VW production (warehouse management, …)

Event-controlled batch processes (Beta 92 ETF) increase efficiency

biggest European car manufacturer ...

02/07/14

Beta 92 Extended Job Manager ...Summary

Enterprise-wide reliability for all batch-based processes

Execution of cross platform job networks using any z/OS scheduler

Certified for SAP Netweaver & SAP Business Warehouse

Secure, cross-platform highspeed file transfer

Single point of control for the entire batch production

Integrated output management

Thank youfor your attention!

Beta 92 Extended Job Manager - betasystems-dci. · PDF fileBenefits and Advantages of an...

Documents

Transcript of Beta 92 Extended Job Manager - betasystems-dci. · PDF fileBenefits and Advantages of an...