Replicator I

1. Replicator I Replicator I Replicator I Replicator I Replicator I Replicator I Replicator I Replicator I ReplicatorI page 1

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, jobnamesdataset names and more. This modifications should be done automatically do maybe more ... page 2

3. Unload OPC Identify BatchstreamInterfaces Identify batch objects Copy JCLcomponents Define OPCmodifications Define InterfaceModifications Identify JCLInterfaces Define JCL Changes ModifyOPC data Define InterfaceModifications ModifyJCL components Load batchobjects Load OPC New Entity Replicator I Process Overview page 3

4. Replicator I Process Overview 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. 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. page 4

5. REXXInterfaces UnloadProgram BatchLoader REXXModify Replicator I Technical Overview Dialog input: DatasetnamesBatchEnvironmentNames OPC UnloadInstructionsandParameters IdentificationKeysandModificationRules OPCModificationsBatchEnvironmentModifications New OPCEnvironment OPC Replication Seq. files Identify OPC Interfaces Modify OPC definitions Load OPC Environment Unload OPC AD AD AD AD AD Selected byApplication names orOwner ID‘s MI MI MI MI OPC Databases OPC Databases Change ......... Change WS names Change AD names Modification rules REXX New BatchEnvironment Batch Environment Replication JCL Modifications by REXX programs Identify JCL Interfaces ModificationREXXf. JCL Modify JCL Interface Scan JobInterf. Load BatchEnvironment Jobs Sysin Jobs Jobs Jobs ModificationREXXf. Procs Modify Procs Interface Scan ProcInterf. IEBUPDTE Proc Proc Proc Proc ModificationREXXf. TEC IEBPTPCHUnload Modify TEC Interface Scan TecInterf. Tec Copy statement arebased on OPC selection,i.e. only batch objectswhich are part of theOPC network will necopied. Tec Tec Tec 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. VLK VLK AVK Scanning rules page 5

6. Replicator I Primary Option Menue page 6

7. Replicator I Options page 7

8. Replicator I Unload OPC Definitions 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 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 page 8

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. page 9

10. Replicator I Replication activities (main menu) page 10

11. Replicator I Identify Batchstream Interfaces page 11

12. Replicator I Identify JCL interfaces page 12

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 keywordsOld valuesNew valuesPosition and range inside the old value page 13

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 keywordsOld valuesNew valuesPosition and range inside the old value page 14

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 otherJCL parms during replication.. Previous unloaded JCL library (DS name stored in users profile) JCL objects (maybe extended)Old valuesNew values Position and range inside the old value DSN Qualifier page 15

16. Replicator I Replication logfiles – OPC modifications page 16

17. Replicator I Replication logfiles – JCL modifications page 17

18. Replicator I Future Functions ... may be developed page 18