Presentation is loading. Please wait.

Presentation is loading. Please wait.

Egon Dümig Information Technology Consulting page 1 Replicator I ReplicatorI Replicator I Replicator I.

Similar presentations


Presentation on theme: "Egon Dümig Information Technology Consulting page 1 Replicator I ReplicatorI Replicator I Replicator I."— Presentation transcript:

1 Egon Dümig Information Technology Consulting page 1 Replicator I ReplicatorI Replicator I Replicator I

2 Egon Dümig Information Technology Consulting page 2 Replicator I Functional Objectives A first version of REPLICATOR should be able to... replicate all OPC objects into the same or another OPC for a new client or customer replicate all batch objects like JCL, procedures, technical members etc. identify and change special interfaces, which are different or no longer available in the new production environment modify OPC and jobcontrol definitions, like application names, jobnames dataset names and more. This modifications should be done automatically do maybe more...

3 Egon Dümig Information Technology Consulting page 3 Replicator I Process Overview Unload OPC Identify Batchstream Interfaces Modify OPC data Define Interface Modifications Define OPC modifications Load OPC New Entity Identify batch objects Copy JCL components Identify JCL Interfaces Define JCL Changes Define Interface Modifications Modify JCL components Load batch objects

4 Egon Dümig Information Technology Consulting page 4 Replicator I Process Overview Unload OPC Unload of all OPC objects related to a selected client using a program or tool. This replication process must contain OPC application definitions and their internal relationships, OPC basic definitions like calendars, workstations, periods and all other objetcs like special ressources, ETT criteria und more. Identify Batchstream Interfaces Batchstream interfaces are inter-application dependencies, which are not longer available after the replication process. Define interface modifications These previous identified interfaces must be changed into dummy functions which must be identifiable automatically for further modifications. The original interface should be documented automatically. Define OPC modifications Some of the replicated OPC objects can only exist as a unique object within one production environment. Therefore it is necessary to change some object fields like application names, jobnames, owners and the relationships to other applications. Modify OPC data We will use self-developed programs (REXX) to modify OPC objetcs based on the predefined modification lists in a single run.. Load OPC Load all OPC objects for a new entity into the same or another production environment using an existing OPC program interface. Identify Batch Objects Scanning unloaded OPC objects will identify all needed batch objects, like jobcontrol, jobcontrol procedures and control data for a new entity Copy JCL Components Based on previous identification all JCL components must be copied from the production environment. All objects will be stored into sequential files for further processing, modifications, transfer and so on. Identify JCL Interfaces Scanning all batch objects for technical interfaces. This is one of the most important issues related to a batch environment. Any program interface to OPC, calls to trigger AOC actions, interfaces to the Tivoli Business System Manager (TBSM), Message Queue Manager calls and data receives from other entities or non-DBT applications must be identified and documented. Define interface modifications Maybe some of these interfaces must be eliminated or changed to dummy or other technical functions, because the called function is not avaiabke inside the new environment or using another technical standard. The rest must be changed maybe to other names, adresses and technical environments. Define JCL Changes New entities (clients) will need their own production environments in form of separate jobs and job libraries (lawful client capabilitiy), application datasets and more. Therefore it is useful to change the names of all related objects. Naming standards must be stated before, together with responsable production groups. Load Batch Objects Load all batch objects for a new entity into the same or another production environment.

5 Egon Dümig Information Technology Consulting page 5 REXX Interfaces Jobs Proc VLK Tec Jobs Proc Tec VLK Replicator I Technical Overview Unload Program OPC Replication OPC Databases Seq. files Batch Environment Replication REXX IEBPTPCH Unload Sysi n AD MI AD Identify OPC Interfaces MI AD Job Inter f. Interface Scan Modification rules REXX Modify Modify OPC definitions Batch Loader Load OPC Environment MI AD Unload OPC Change AD names Change WS names Change Proc Inter f. Tec Inter f. Identify JCL Interfaces OPC Databases New OPC Environment Modification REXX f. JCL Modify JCL Jobs Proc AVK Tec Jobs Proc Tec IEBUPDTE Scanning rules JCL Modifications by REXX programs Modify Procs Modify TEC Modification REXX f. Procs Modification REXX f. TEC New Batch Environment Datasetnames Batch Environment Names Identification Keys and Modification Rules Dialog input: Load Batch Environment OPC Modifications Batch Environment Modifications OPC Unload Instructions and Parameters Selected by Application names or Owner ID‘s Copy statement are based on OPC selection, i.e. only batch objects which are part of the OPC network will ne copied. Interface modifications are based on fixed and predefined rules. All JCL and other modifications are variable and modular, the user is able to change any modífications at any times save and syntax checked. AD

6 Egon Dümig Information Technology Consulting page 6 Replicator I Primary Option Menue

7 Egon Dümig Information Technology Consulting page 7 Replicator I Options

8 Egon Dümig Information Technology Consulting page 8 Data selection by application names or owner ID‘s Eligible unload file names will be stored in user‘s profile for further use Edit JCL before submission User‘s jobcard Unload OPC data using delivered programs or tools. All application related objects will be copied from OPC database into a sequential dataset. Some system and tool related informations like image name, date and time last unload date and time Replicator I Unload OPC Definitions

9 Egon Dümig Information Technology Consulting page 9 Replicator I Unload OPC Definitions At each step of the replication it is possible to edit the unloaded files for control or manual modifications.

10 Egon Dümig Information Technology Consulting page 10 Replicator I Replication activities (main menu)

11 Egon Dümig Information Technology Consulting page 11 Replicator I Identify Batchstream Interfaces

12 Egon Dümig Information Technology Consulting page 12 Replicator I Identify JCL interfaces

13 Egon Dümig Information Technology Consulting page 13 Replicator I OPC Modifications General OPC Modifications to implement a new client can be done in this function. The OPC keywords to modify are unlimited, careless usage may change network dependencies or planning logic. Previous unloaded OPC data (DS name stored in users profile) OPC keywords Old values New values Position and range inside the old value

14 Egon Dümig Information Technology Consulting page 14 Replicator I OPC Modifications General OPC Modifications to implement a new client can be done in this function. The OPC keywords to modify are unlimited, careless usage may change network dependencies or planning logic. Previous unloaded OPC data (DS name stored in users profile) OPC keywords Old values New values Position and range inside the old value

15 Egon Dümig Information Technology Consulting page 15 Replicator I JCL Modifications General JCL Modifications to implement a new client can be done in this function. The JCL keywords to modify are limited, because it is not wanted to change any other JCL parms during replication.. Previous unloaded JCL library (DS name stored in users profile) JCL objects (maybe extended) Old values New values Position and range inside the old value DSN Qualifier

16 Egon Dümig Information Technology Consulting page 16 Replicator I Replication logfiles – OPC modifications

17 Egon Dümig Information Technology Consulting page 17 Replicator I Replication logfiles – JCL modifications

18 Egon Dümig Information Technology Consulting page 18 Replicator I Future Functions... may be developed


Download ppt "Egon Dümig Information Technology Consulting page 1 Replicator I ReplicatorI Replicator I Replicator I."

Similar presentations


Ads by Google