egon dümig information technology consulting page 1 replicator i replicatori replicator i...
TRANSCRIPT
page 1
Egon Dümig Information Technology Consulting
Replicator IReplicator IReplicator IReplicator I
Replicator IReplicator I
Replicator IReplicator I
Replicator IReplicator IReplicator Replicator II
Replicator IReplicator I
ReplicatoReplicatorr II
Replicator IReplicator I
page 2
Egon Dümig Information Technology Consulting
Replicator IFunctional 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, jobnamesdataset names and more. This modifications should be done automatically
do maybe more ...
page 3
Egon Dümig Information Technology Consulting
Replicator IProcess Overview
Unload OPCIdentify Batchstream
Interfaces
ModifyOPC data
Define InterfaceModifications
Define OPCmodifications
Load OPC
New Entity
Identify batch objects
Copy JCLcomponents
Identify JCLInterfacesDefine JCL Changes
Define InterfaceModifications
ModifyJCL components
Load batchobjects
page 4
Egon Dümig Information Technology Consulting
Replicator IProcess Overview
Unload OPCUnload 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 InterfacesBatchstream interfaces are inter-application dependencies, which are not longer available after the replication process.
Define interface modificationsThese 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 modificationsSome 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 dataWe will use self-developed programs (REXX) to modify OPC objetcs based on the predefined modification lists in a single run..
Load OPCLoad 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.
page 5
Egon Dümig Information Technology Consulting
REXXInterfaces
Jobs
Proc
VLK
Tec
Jobs
Proc
Tec
VLK
Replicator ITechnical Overview
UnloadProgram
OPC Replication
OPC Databases
Seq. files
Batch Environment Replication
REXX
IEBPTPCHUnload
Sysin
AD
MI MI
AD
Identify OPC Interfaces
MI
AD
JobInter
f.
Interface Scan
Interface Scan
Interface Scan
Modification rules
REXXModify
Modify OPC definitions
BatchLoader
Load OPC Environment
MI
AD
Unload OPC
Change AD names
Change WS names
Change .........
ProcInter
f.
TecInter
f.
Identify JCL Interfaces
OPC Databases
New OPCEnvironment
ModificationREXXf. JCL
Modify JCL Jobs
Proc
AVK
Tec
Jobs
Proc
Tec
IEBUPDTE
Scanning rules
JCL Modifications by REXX programs
Modify Procs
Modify TEC
ModificationREXX
f. Procs
ModificationREXXf. TEC
New BatchEnvironment
Datasetnames
BatchEnvironmentNames
IdentificationKeysandModificationRules
Dialog input:
Load BatchEnvironment
OPCModificationsBatchEnvironmentModifications
OPC UnloadInstructionsandParameters
Selected byApplication names orOwner ID‘s
Copy statement arebased on OPC selection,i.e. only batch objectswhich are part of theOPC network will necopied.
Interface modifications are based on fixed and predefined rules.All JCL and other modifications are variable and modular, theuser is able to change any modífications at any times save and syntax checked.
AD
page 8
Egon Dümig Information Technology Consulting
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 timelast unload date and time
Replicator IUnload OPC Definitions
page 9
Egon Dümig Information Technology Consulting
Replicator IUnload OPC Definitions
At each step of the replication it is possible to edit the unloaded files for control or manual modifications.
page 13
Egon Dümig Information Technology Consulting
Replicator IOPC 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
page 14
Egon Dümig Information Technology Consulting
Replicator IOPC 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
page 15
Egon Dümig Information Technology Consulting
Replicator IJCL 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 otherJCL 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
page 16
Egon Dümig Information Technology Consulting
Replicator IReplication logfiles – OPC modifications
page 17
Egon Dümig Information Technology Consulting
Replicator IReplication logfiles – JCL modifications