Micro Focus. Enterprise View. MVS Custom Agent Process Guide

Transcription

1 Micro Focus Enterprise View MVS Custom Agent Process Guide

2 Copyright 2008 Micro Focus (IP) Ltd. All rights reserved. Micro Focus (IP) Ltd. has made every effort to ensure that this book is correct and accurate, but reserves the right to make changes without notice at its sole discretion at any time. The software described in this document is supplied under a license and may be used or copied only in accordance with the terms of such license, and in particular any warranty of fitness of Micro Focus software products for any particular purpose is expressly excluded and in no event will Micro Focus be liable for any consequential loss. Animator, COBOL Workbench, EnterpriseLink, Mainframe Express, Micro Focus, Net Express, REQL and Revolve are registered trademarks, and AAI, Analyzer, Application Server, Application to Application Interface, AddPack, AppTrack, AssetMiner, CCI, DataConnect, Dialog System, Enterprise Server, Enterprise Server with MTO, EuroSmart, FixPack, LEVEL II COBOL, License Server, Mainframe Access, Mainframe Manager, Micro Focus COBOL, Micro Focus Studio, Micro Focus Server, Object COBOL, OpenESQL, Personal COBOL, Professional COBOL, Server Express, SmartFind, SmartFind Plus, SmartFix, SourceConnect, SupportLine, Toolbox, VS COBOL, WebSync, and Xilerator are trademarks of Micro Focus (IP) Ltd. IBM and CICS are registered trademarks, and IMS, DB2, DB2/390, DB2 Connect Enterprise Edition, DB2 Connect Personal Edition, COBOL for OS/390, Enterprise Systems Architecture/390, ESA/390, MVS, MVS/ESA, OS/390, S/390, System/390, VSE/ESA and MFS are trademarks, of International Business Machines Corporation. Netscape Enterprise Server is a trademark of Netscape Communications Corporation. Internet Information Server, Windows 95, Windows 98, Windows NT 4.0, Windows ME and Windows 2000 are registered trademarks of Microsoft Corporation. Pentium is a registered trademark of INTEL Corporation. Borland Database Engine and Midas are trademarks of Inprise Corporation. Oracle is a trademark of Oracle Corporation Inc. UNIX is a registered trademark of The Open Group. Solaris, Ultra Sparc and Java are trademarks of Sun Microsystems, Inc. Linux, GCC compiler, GNU CTAGS, GNU DIFF, Samba and KDE/GNOME refer to Open Source tools. This product includes modified versions of software developed by the Apache Software Foundation (as described on the Apache web site). The YGrep Search Engine is Copyright (c) Yves Roumazeilles. All other trademarks are the property of their respective owners. No part of this publication, with the exception of the software product user documentation contained on a CD-ROM, may be copied, photocopied, reproduced, transmitted, transcribed, or reduced to any electronic medium or machine-readable form without prior written consent of Micro Focus (IP) Ltd. Contact your Micro Focus

3 representative if you require access to the modified Apache Software Foundation source files. Licensees may duplicate the software product user documentation contained on a CD- ROM, but only to the extent necessary to support the users authorized access to the software under the license agreement. Any reproduction of the documentation, regardless of whether the documentation is reproduced in whole or in part, must be accompanied by this copyright statement in its entirety, without modification. U.S. GOVERNMENT RESTRICTED RIGHTS. It is acknowledged that the Software and the Documentation were developed at private expense, that no part is in the public domain, and that the Software and Documentation are Commercial Computer Software provided with RESTRICTED RIGHTS under Federal Acquisition Regulations and agency supplements to them. Use, duplication or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of The Rights in Technical Data and Computer Software clause at DFAR et. seq. or subparagraphs (c)(1) and (2) of the Commercial Computer Software Restricted Rights at FAR , as applicable. Contractor is Micro Focus (IP) Ltd, 9420 Key West Avenue, Rockville, Maryland Rights are reserved under copyright laws of the United States with respect to unpublished portions of the Software.

4 4 MVS Custom Agent Process Guide

5 5 Table of Contents 1. INTRODUCTION DISCLAIMER ABOUT THIS DOCUMENT WHO SHOULD USE THIS DOCUMENT WHAT IS THE MVS CUSTOM AGENT BEFORE YOU START SOFTWARE ARTIFACTS FOLDER STRUCTURE ON LINUX/UNIX BOX APPLICATION AGENT COMPONENTS STANDARD INTERFACE FILE FOR CCM API FOR CCM INTERFACE TRANSMISSION FUNCTIONALITIES SETTINGS Work with system settings Work with agent settings Work with Enterprise View settings Work with Source Management settings Clear environment INVENTORY Add or update library to catalogue Add or update library to catalogue Add members from PDS ADDITIONAL INFORMATION Unload System Catalogue Extract information from DB2 Catalogue Generate DDL SERVER UPDATING Create scripts for server structure and changed components updating Update information for Enterprise View Builder PROCESS OVERVIEW INITIAL LOAD PROCESS LIFECYCLE PROCESS SYNCHRONIZATION PROCESS EXAMPLE OF INITIAL LOAD PROCESS SOURCES MANAGED BY CA-ENDEVOR...23 MVS Custom Agent Process Guide

6 Generate the elements list managed by CA-ENDEVOR Sample of output report (CONRPT03) Load interface file Command string format SOURCE NOT MANAGED BY ANY CCM Load IMPSRC for sources not managed by CCM Command string format TRANSMISSION Generate files and scripts to update Unix/Linux box Update Unix/Linux box EXAMPLE OF LIFECYCLE PROCESS SOURCES MANAGED BY CA-ENDEVOR CA-ENDEVOR promotion procedures Command string format SOURCE NOT MANAGED BY ANY CCM Load IMPSRC for sources not managed by CCM Command string format MVS CUSTOM AGENT FILES GLOSSARY MVS Custom Agent 5.6 Process Guide

7 7 1. Introduction Above, there are basic information about the book, its content and the toolkit Disclaimer At the time of writing Micro Focus would like to point out that product naming and terminology is subject to change in the near future. All information provided is considered Micro Focus Proprietary and Confidential and should not be disclosed without permission About this document This document provides detailed information about the processes of MVS Custom Agents. It provides only a reference material and assumes you are experienced in the use of MVS environment and Enterprise view Who should use this document Anyone who has to create interfaces or needs documentation about MVS Custom Agents What is the MVS Custom Agent The MVS Custom Agent is an application running on the zos Systems and is the main actor interfacing the Change & Configuration Management tools in order to: Get the software artifacts and their basic information (system, application, last promoting date, etc.) and environment configuration files (for CICS and/or IMS) for the initial loading; Get the software artifacts and business information (from CCM or other tools) about changes; Execute a parallel process to check the main one and automatically undertake the suitable actions to fix the issues; Prepare and update the Enterprise View Engine UNIX Machine. MVS Custom Agent Process Guide

8 8 In addition, it collects software artifacts and data about: Software artifacts not managed by CCM tools; Environment configuration files (for CICS and/or IMS); Customer files to integrate external data. An additional component, installed on the Enterprise View Engine UNIX Machine, should be used to increase the performance of the transmission or to integrate data with additional information provided by applications running on distributed systems. Enterprise View now provides NLS (National Language Support). This lets you specify an EBCDIC file system code page name (CCSID Coded Character Set Identifier), for the operating system where the product is installed. The specified EBCDIC file system code page name is converted to an ASCII network transfer code page name according to ICONV supported code pages. ASCII ISO standard is used as internal encoding. It covers the coded character set based on the Latin-1 alphabet which includes Western European languages. Note: Before you start using the NLS options, make sure that FTP ISO standards are supported in your system. MVS Custom Agent 5.6 Process Guide

9 9 2. Before You Start A solid implementation must start from a deep knowledge of the customer environment, a good definition of the goals to achieve and a detailed study of the integration processes Software artifacts First of all you have to understand type and processes of the software artifacts you have to process (to achieve the goals): Which is the development process to maintain them? Are they managed by a CCM or not? Are the sources available or not? 2.2. Folder structure on Linux/Unix box One of the main decisions regards the folder structure on Enterprise view Engine machine. It is important because: Enterprise view builds the technical view inherited the structure from the folder; Enterprise view analyses the relationship between objects basing on hierarchical structure of the technical view Application It is the main aggregation of the data. Generally, all software artifacts managed by CCM have a code (System or Sub-System) that identifies it. For all software artifacts not managed by the CCM, you can: Put them into a common application; Define rules based on naming convention (software artifacts or PDS); Get the information from an external file containing the relationships. MVS Custom Agent Process Guide

10 10 MVS Custom Agent 5.6 Process Guide

11 11 3. Agent components This chapter provides a description of main Agent components in order to understand the processes (described into the following chapters) Standard Interface file for CCM Agent provides a standard interface file to store information about software artifacts should be processed, internally named IMPSRC. This file is a sequential multi-format file containing: Basic information about software artifacts normally provided by the CCM tools: name, library, type, creation date, last promoting date, last generation date, etc. Basic information about software artifacts not managed by the CCM tools: name, library, etc. Additional information about software artifacts: source description; Information about the destination path on the Enterprise View Engine UNIX Machine normally derived by the CCM logical structure (system, environment, application and type) or by the PDS name; Information about ownership: application, outsourcer having in charge, etc.; Information about changes: reason code, project codes, business codes, outsourcing performs the changes, etc. It is useful to provide information both for initial load and lifecycle processes API for CCM interface A set of standard APIs or ones designed for a specific CCM tool, like CA- ENDEVOR or SERENA CHANGEMAN, provides a simple layer to storing the information listed above. The main peculiarity, distinguishing the CA-ENDEVOR or SERENA CHANGEMAN interfaces from standard one, is the capability to assign an extension to the software artifacts basing on CCM type. This is done reading a specific configuration file <Environment>.KTQCM where the relationships are stored. MVS Custom Agent Process Guide

12 Transmission The Transmission is a set of files necessary to process the environment in the best way. A transmission could be composed by: Sources (with the suitable extension) of software artifacts (mandatory); List of software artifacts into a dedicated XML file (REPXML.XML) driving the updating process (mandatory); CICS System Definition (CSD); List of software artifacts properties into a dedicated XML file (KBPROPERTY.XML); List of external relationships (not derived by the source analysis) of software artifacts into a dedicated XML file (KBREFERENCE.XML); List of software artifacts into a dedicated XML file driving the synchronization process (KBSYNCHRO.XML); Other additional files; An empty file, named EOT.KB. Agent will send this file at the end of the transmission to activate the receiving process. MVS Custom Agent 5.6 Process Guide

13 13 4. Functionalities This chapter describes in details the functionalities provided by the MVS Custom Agents to support the implementation project Settings There are a set of functions that allows the toolkit customization Work with system settings This function allows the collecting all of the parameters regarding the customer environment: language environment, DB2 and CICS. This is useful to actualize the skeletons before the job submission. About Language Environment Load Library : CEE.SCEERUN Link-edit Library : CEE.SCEELKED About DB2 Environment Run-time (RUNLIB) : DSKB.RUNLIB.LOAD DB2 Load Library (SDSNLOAD). : DSN710.SDSNLOAD About DB2 Database Sub-system (DSN) : DSKB Database : KBT53ADB Storage group : KBT53ASG Creator (Owner) : KBT53A Sql Id : Bufferpool for Data.... : BP2 Bufferpool for Index.... : BP3 About DB2 Utility DSNTIAD Program and Plan.. : DSNTIAD DSNTIA71 DSNTIAUL Program and Plan. : DSNTIAUL DSNTIB71 About DB2 Bind Bind Plan : KBT53APL Package Collection..... : KBT53A Explain in Plan Table... : NO NO, YES About CICS Environment CSD File Name : CICS.DFHCSD CICS Load Libraries.... : CICS.SDFHLOAD MVS Custom Agent Process Guide

14 Work with agent settings This function allows the collecting all of the parameters regarding the agent environment: installation libraries, environment, and processes. This is useful to actualize the skeletons before the job submission and to process sources not managed by the CCM during the software lifecycle. Library prefixes for product run-time Customization library... : KBB.R53WRK Latest fixes library... : KBB.R53FIX PTF library : KBB.R53PTF Release library : KBB.R53 Library prefixes for environment Environment : KBB.KBT53A Actualizing job (FTOUTPUT). : Handle original source library Add new library by SLC... : YES Destination Path Rule... : LIBRARY Destination path separators : / NO, YES LIBRARY, OBJECT Character Work with Enterprise View settings This function allows the collecting all of the parameters regarding the Engine machine environment: connection and updating parameters. This is useful to actualize the skeletons before the job submission and to define how the transmission should be created. Enterprise View box IP Address : User :evuser Password : Prefix for destination path:awdpre/ Updating method Update directly......:yes Method for updating scripts:ftp Compress options Compress before sending..:no Compress utility.....: NLS options NLS support : YES MVS codepage :IBM-1047 NO, YES FTP, ASI, CD NO, YES GZIP NO, YES NONE, Value Description of the NLS options: MVS Custom Agent 5.6 Process Guide

15 15 NLS options are displayed in the System z EV Agent Work with Enterprise View settings window. There are two new fields. The NLS support field lets you include and exclude NLS. YES includes NLS. When you enter YES, CCSID value must be specified in the MVS codepage field. NO excludes NLS. In this case the product works as in the previous versions. The sources are converted according to the default FTP translation of the system where the product is installed. When NLS support is set to NO the MVS codepage field must have the value NONE. MVS codepage indicates file system code page name (CCSID). The possible file system code page names that can be entered when the NLS is included are: IBM-037 EBCDIC USA, Canada, Australia, New Zealand, Netherlands, Brazil, Portugal IBM-273 EBCDIC Austria, Germany IBM-274 EBCDIC Belgium IBM-275 EBCDIC Brazil IBM-277 EBCDIC Denmark, Norway IBM-278 EBCDIC Finland, Sweden IBM-280 EBCDIC Italy IBM-281 EBCDIC Japanese English IBM-284 EBCDIC Spanish IBM-285 EBCDIC United Kingdom IBM-297 EBCDIC France IBM-500 EBCDIC Latin - 1 IBM-871 EBCDIC Iceland IBM-1047 EBCDIC Latin Work with Source Management settings This function allows the additional parameter defining to understand how the transmission has to manage the software artifacts. This is useful to actualize the skeletons before the job submission and to define how the transmission should be created. MVS Custom Agent Process Guide

16 16 Source Management File Name : KBS Extended File Name....: KBB.KBT53A.SRC Number of files......: 30 Number of Record for file : Allocation Unit......: C CYL, TRK Primary Qty : 250 Secondary Qty : 25 Record Format : F FB, VB,... Record Lenght : 80 Block Size : Kind of Transfer.....: SEQ SRC, SEQ Clear environment This function allows the environment data cleaning. Use the function when you have to run the process again from the beginning. Attention all data will be lost Inventory These functionalities allow the libraries cataloguing (and the software artifacts stored in). They should be used only for the libraries and software artifacts not managed by any CCM tools. To catalogue libraries and software artifacts managed by the CCM tool a specific interface and the initial load process must be done (See 5.1 Initial load process at page 21 for further information). For the libraries and software artifacts not managed by any CCM tools, there are some attention points to analyze: Must the library be scanned during the software lifecycle and which is the frequency? How should the destination path (on Engine machine) be identified? Does the library contain one or more different type of sources? The implementer/customer must take much care to provide the answers, especially for the third one Add or update library to catalogue The function allows the cataloguing of the libraries not managed by the CCM. MVS Custom Agent 5.6 Process Guide

17 17 Library information Path name : KBB.R53.SKEL Scan during SLC : N N, Y, 1, 2, 3, 4, 5, 6, 7 Extension Default SKEL Optional Destination path KBB/R53/SKEL Path name. It is the name of the library must be catalogued. Scan during SLC. The indicator defines when the library must be scanned to identify the changes to the software artifacts. Allowed values are: N. Library is ignored by the scanning process; Y. Every lifecycle execution, the library will be scanned to identify the changes; 1 7. The library will be scanned to identify the changes every day of week (1 - Monday, 2 Thursday, 3 Wednesday and so on). This option is very useful when there are many libraries to scan every day. Considering that the scanning takes a lot of system resources, the user is able to manage every library in different way basing on the updating frequency. Extension. It is the default extension assigned to the software artifacts. When the user provides the default extension only, the tool assigns it to all of the software artifacts. When the user provides more than one values, the tool assigns the default extension only when one of the other values (optional) are not compatible with the content of the software artifact. Destination path. For each type of software artifacts is possible to specify a different destination path on Engine machine (it must be provided in *nix format) Add or update library to catalogue The function allows the cataloguing of the software artifacts for the libraries not managed by the CCM. Library information Path name :,KBB.R53.SKEL Name, *ALL, *Generic* Source name :,*ALL, Name, *ALL, *Generic* Path name. It is the name of the library containing the software artifacts should be catalogued. Source name. It provides the filtering for the software artifacts should be catalogued. MVS Custom Agent Process Guide

18 Add members from PDS The function is in alternative to the previous ones. It allows the cataloguing of the software artifacts by a customized interface. The first step (standard) generates a list of the software artifacts and stores it into a sequential file. The second step (customized routine) reads the sequential file and invoking the standard API for the initial load stores the information for the processing into IMPSRC. This functionality is very useful when there are custom rules to assign the application name, to provide the destination path or something like that. Library information Path name :,KBB.R53.SKEL, Option Program to invoke.... :,, Path name. It is the name of the library containing the software artifacts should be catalogued. Program to invoke. It is the custom program for cataloguing the software artifacts Additional information Unload System Catalogue No options are available. The process runs the following steps: Generate a LIST CAT. User can customized the extraction copying the original SYSIN from <product libraries>.sysin to <environment library>.sysin and changing the parameters in KYSYSCAT member Generate an XML file containing information about VSAM and NON-VSAM files for the engine Extract information from DB2 Catalogue No options are available. The process generates sequential files extracting information from DB2 catalogue tables. User can customized the extraction copying the original SYSIN from <product libraries>.sysin to <environment library>.sysin and changing the parameters in KYDB2CAT member MVS Custom Agent 5.6 Process Guide

19 19 This process is separated from the next one (Generate DDL). That s why it could be run on different platforms (live environment) where the toolkit is installed. After the extraction a user process moves the sequential files to the machine where the toolkit is installed to generate the DDL. This strategy allows for avoiding a multiple installations of Agent Generate DDL Staring from the sequential files, it re-generates the DDLs. The content of the re-generated software artifacts is partial because is useful only for the engine analysis Server updating Create scripts for server structure and changed components updating It generates all the needed files for the transmission. In particular, if you want to transfer the CSD you need to customize the TRANSFER file, containing the list of additional files sent by the transmission. About the format, it should be specified as follow: o o source (like it ll be a sequential) target: file name and folder; folder must be specified as <IP Address>/<TimeStamp>/Config (<IP Address> and <TimeStamp> can be specified as keywords) One entry must be specified for each different CICS (the different CSD are not queued, but sent separately in different.csd files on the engine machine) A sample TRANSFER file is included in the installation procedure Update information for Enterprise View Builder It updates the engine on Linux machine sending all the information about changes (or, during the initial phase, for inventorying of the software artifacts). MVS Custom Agent Process Guide

20 20 MVS Custom Agent 5.6 Process Guide

21 21 5. Process overview This chapter provides an overview of the main processes implemented at customer site in order to provide a solid installation Initial load process Starting from the software artifacts list, Agent collects and stores information about the element in list into the Agents Knowledge Base. After that, it is able to generate the transmission to update the Enterprise View Engine UNIX Machine Lifecycle process Starting from the list of changes to software artifacts, Agent collects and stores information into the Agents Knowledge Base. After that, it is able to generate the transmission to update the Enterprise View Engine UNIX Machine Synchronization process Starting from the software artifacts list, Agent builds an XML file to drive the synchronization process on the Enterprise View Engine UNIX Machine. Enterprise view generates a XML list of the unmatched software artifacts comparing the XML file and the AKP content. Normally the list should be empty. If not, an action is required. MVS Custom Agent Process Guide

22 22 MVS Custom Agent 5.6 Process Guide

23 23 6. Example of initial load process Starting from the software artifacts list, Agent collects and stores information into the Agents Knowledge Base to generate the transmission Sources managed by CA-ENDEVOR Generate the elements list managed by CA-ENDEVOR CONRPT03 is a standard CA-ENDEVOR report provides information about the catalogued elements into the CCM. The list must include all the elements belonging to the environments and systems must be managed in Enterprise view. Elements of other environments or systems must be excluded from the list. No actions are required to filter information based on object type. This action will be performed by the next step basing on information stored into <Environment>.KTQCM file Sample of output report (CONRPT03) 1 (C) 2002 Computer Associates International, Inc Endevor 09/22/05 10:20:49 PAGE 3 RELEASE 4.0 SERIAL B4002C CONRPT03: ELEMENT CATALOG ELEMENT ENVIRON SYSTEM SUBSYS TYPE STAGE VV.LL PROCESSOR BASE BASE CURRENT CURRENT LAST GEN LAST GEN DELTA ID SEQ GROUP DATE USER ID DATE USER ID DATE USER ID LIVE WBY BCHACC MACRO *NOPROC* 05APR01 WBOJT40P 05APR01 WBOJT40P 05APR01 WBOJT40P LIVE WBY BCHACC MACRO *NOPROC* 05APR01 WBOJT40P 05APR01 WBOJT40P 05APR01 WBOJT40P R ABTSECT LIVE WBY BCHACC MACRO *NOPROC* 07JAN94 WBYASFU 07JAN94 WBYASFU 23JUN98 UCYDJRM R ACCDCB LIVE WBY BCHACC MACRO *NOPROC* 14APR90 NDYDCG 21OCT98 WBODC400 12OCT99 WBOSB300 R ACCPDR LIVE WBY BCHACC MACRO *NOPROC* 14APR90 NDYDCG 30SEP99 WBOSB300 12OCT99 WBOSB300 R MVS Custom Agent Process Guide

24 Load interface file A custom interface reads the elements list provided by CCM, composes the command string for the API (KPEDVRI) and invokes it to store information about the software artifacts into IMPSRC. The API interprets CA-ENDEVOR object type (EDVRTYPE) in order to understand which extension must be used for each element. The element will be skipped when the CA-ENDEVOR type is not present into <Environment>.KTQCM file. This allows a dynamic managing of the types to include or exclude. At the end, the output will be stored in a sequential file (IMPSRC) Command string format Information included into the standard report will be used to generate the command string for the API: NAME(<Element>); LIBRARY(<Prefix>.<Environment>.<System>.<Type>); EDVRTYPE(<Type>); DESTINATIONPATH(<Application code>, <Application code>, <ObjectType>,); OBJECTCODES(<Environment>, <System>, <Sub-System>, <Type>, <Stage>, <VV.LL>, <Application code>,);\ Values put in highlights (italic and underline) will be calculated in the following way (it is only an example): Application code. It is calculated on the first 2 characters of CA-ENDEVOR system; ObjectType. It is composed by application code and CA-ENDEVOR object type (<Application code> + <Type>) Source not managed by any CCM Load IMPSRC for sources not managed by CCM Each library not managed by the CCM must be catalogued manually into the Agent. After that, a scan process could be run to: For each library, the process generates a member list (into a temporary file); For each member, the process generates a standard command string to catalogue sources; Invoke the standard API passing the command string (KPCCMI) to store information into IMPSRC. MVS Custom Agent 5.6 Process Guide

25 Command string format The command string for the API (KPCCMI) will be: NAME(<Source name>); LIBRARY(<Library name>); EXTENSION(<EV Extension>); DESTINATIONPATH( *SCAN,); OBJECTCODES(<VV.MM>, <Changed DateTime>, <User Id>,);\ Values put in highlights (italic and underline) will be calculated in the following way: Changed date. Latest changed date as showed into ISPF panel. If not available, you should indicate a dummy date (format ); User id. User who performs the latest changes Transmission Generate files and scripts to update Unix/Linux box The product generates a set of files containing the sources to process and a set of scripts to manage the transmission (stored in specific sequential files) from MVS to Linux/Unix Box. The driver is the KTOBJ (DB2 table). It contains information about the sources to process. In output, the step generates a set of sequential files containing: Information for the connections (as user, IP address, etc.) (FTPHDR); Information about the folders structure on Linux/Unix Box (STRUCTUR); Information about the source list to transfer (SOURCELS); Information about the sequential files where sources are stored (SOURCEFL); An XML file containing all information about the source to process (REPXML); Additional information about DB2 or system catalogue (ADDINFO, SYSCAT, DB2CAT); Additional customized information (TRANSFER) Update Unix/Linux box The step runs the scripts previously created to update the Linux/Unix box. At the end, the job deletes all the file and PDS created by the process. MVS Custom Agent Process Guide

26 26 MVS Custom Agent 5.6 Process Guide

27 27 7. Example of lifecycle process One of the main features, that the product provides, is the technical documentation up to date. A process, named Lifecycle, performs the updating. The product provides a synchronous process, invoked during the promoting phase, and an asynchronous process, should be daily scheduled. This allows to minimize the impact on customer procedures, and to optimize resource usage Sources managed by CA-ENDEVOR CA-ENDEVOR promotion procedures For each promotion event, a card should be built with information about the object. After that, the promotion procedure should have a JCL step, call the API (KPEDVRU) referencing this card, in order to store information about the changed software components into IMPSRC. The API interprets CA-ENDEVOR object type (EDVRTYPE) in order to understand which Enterprise view object extension must be used for each element. The element will be skipped when the CA-ENDEVOR object type is not present into <Environment>.KTQCM file. This allows a dynamic managing of the types to include or exclude. At the end, the output will be stored in a sequential file (IMPSRC) Command string format Information, provided to the API from the code promotion action, will be used to generate the command string for the API: NAME(<Element>); LIBRARY(<Prefix>.<Environment>.<System>.<Type>); EDVRTYPE(<Type>); DESTINATIONPATH(<Application code>, <Application code>, <ObjectType>,); OBJECTCODES(<Environment>, <System>, <Sub-System>, <Type>, <Stage>, <VV.LL>, <Application code>,);\ MVS Custom Agent Process Guide

28 28 Values put in highlights (italic and underline) will be calculated in the following way (it is only an example): Application code. It is calculated on the first 2 characters of CA-ENDEVOR system; ObjectType. It is composed by application code and CA-ENDEVOR object type (<Application code> + <Type>) Source not managed by any CCM Load IMPSRC for sources not managed by CCM Each library not managed by the CCM must be catalogued manually into Enterprise view. After that, a scan process could be run to: For each library, the process generates a member list (into a temporary file); For each member, the process generates a standard command string to catalogue sources; Invoke the standard API passing the command string (KPCCMU) to store information into IMPSRC Command string format The command string for the API (KPCCMU) will be: NAME(<Source name>); LIBRARY(<Library name>); EXTENSION( *SCAN ); DESTINATIONPATH( *SCAN,); OBJECTCODES(<VV.MM>, <Changed DateTime>, <User Id>,);\ Values put in highlights (italic and underline) will be calculated in the following way: Changed date. Latest changed date as showed into ISPF panel. If not available, you should indicate a dummy date (format ); User id. User who performs the latest changes. MVS Custom Agent 5.6 Process Guide

29 29 8. MVS Custom Agent files Type DSN/Table name DESCRIPTION Rcd length Space required (Depend on the ) DB2 <Owner>. KTCCON CICS Connections 132 Connections defined into the CSD DB2 <Owner>. KTCDCT CICS Data control table Size Stable after the initial load 79 DCTs defined into the CICS Stable after the initial load DB2 <Owner>. KTCFIL CICS Files 238 Files defined into the CSD Stable after the initial load DB2 <Owner>. KTCLST CICS Lists 139 Lists defined into the CSD Stable after the initial load DB2 <Owner>. KTCMAP CICS Mapsets 108 Mapsets defined into the CSD DB2 <Owner>. KTCPGM CICS Programs 132 Programs defined into the CSD DB2 <Owner>. KTCTRN CICS Transactions 403 Transactions defined into the CSD DB2 <Owner>. KTDDN DB2 DDL members from DB2 catalogue 51 DB2 object (tables and views) defined into the DB2 catalogues DB2 <Owner>. KTMSG Error log 1415 Error messages generated by the product Stable after the initial load Stable after the initial load Stable after the initial load Stable after the initial load Could increase DB2 <Owner>. KTOBJ Objects 426 Element to process. Stable after the initial load DB2 <Owner>. KTOBJC Object codes 309 Element to process (from 0 to 20 record for each element) DB2 <Owner>. KTOBJP Object properties 302 Element to process (from 0 to 20 record for each element) DB2 <Owner>. KTOBJR Object relationships 48 Element to process (from 0 to n record for each element) Stable after the initial load Stable after the initial load Stable after the initial load DB2 <Owner>. KTPTH Paths 94 Catalogued libraries Stable after the initial load DB2 <Owner>. KTPTHD Details of path 1081 Catalogued libraries (from 0 to 5 record for each element) Stable after the initial load DB2 <Owner>. KTPTY Properties 99 User defined properties Fixed after installation DB2 <Owner>. KTQCM CCM interface 143 Relationship between CCM and Enterprise view object extension Fixed after installation DB2 <Owner>. KTQOB Object extension 130 Object extensions Fixed after installation SEQ <MF EV>. IMPSRC Information about members to process 500 Sources to process Quite stable SEQ SEQ <MF EV>. MBRLSTEN <MF EV>. RTVMBREN List of members into a library List of command for source extraction 354 Sources stored into the library 80 Sources to extract from CCM SEQ <MF EV>. KTQCM CCM interface 80 Relationship between CCM and Enterprise view object extension Quite stable Quite stable after the initial load Fixed after installation MVS Custom Agent Process Guide

30 30 SEQ <MF EV>. ADDINFO Additional Information records Fixed after installation SEQ <MF EV>. CMDLIST List of commands 4096 Number of sources Could increase SEQ <MF EV>. DB2CAT XML version of DB Number of DB2 objects Quite stable catalogue SEQ <MF EV>. SYSCAT XML version of Vsam catalogue 4096 Number of Vsam objects Quite stable SEQ <MF EV>. FTPHDR Header of Script Records Fixed after installation SEQ <MF EV>. REPXML XML version of transmission s Report SEQ SEQ SEQ <MF EV>. SOURCEFL <MF EV>. SOURCEFL.FTP <MF EV>. SOURCELS.FTP List of Sequential files to send FTP format for send SOURCEFL FTP format for send SOURCELS 4096 Number of objects transferred 4100 Number of objects transferred Could increase Could increase 80 0 records Fixed after installation 80 0 records Fixed after installation SEQ <MF EV>. EOT End of transmission 5 0 records Fixed after installation SEQ SEQ SEQ SEQ <MF EV>. TRANSFER.FTP <MF EV>. TRANSFER <MF EV>. SOURCELS <MF EV>. STRUCTUR FTP format for send TRANSFER List of Source to send List of directory to be create on Linux machine records Fixed after installation records Fixed after installation 4100 Number of objects transferred 4096 Number of complexity of architecture Could increase Could increase Some information could be change installing an updated version. MVS Custom Agent 5.6 Process Guide

31 31 9. Glossary Change codes are a set of customer codes link to the changes performed to the sources. For example the enhancement projects, the ticket, the outsourcer and so on. These codes could be use to arrange for specific analysis. Destination path MVS Custom Agents transfers all information about customer software to *inux box where the engine, that will perform the analysis, is installed. Environment name is the name indicated during the creation environment and it is also the same you indicate to connect to the environment. Normally, it corresponds to library prefix of the environment. Extension Each source is recognized based on its class, type and language provided by the change management tool. During the transfer, the product renames the source adding an extension identifying its classification. Object codes are a set of customer codes link to the sources. For example the application, sub-application, development team and so on. These codes could be use to maintain specific views named organization views. MVS Custom Agent Process Guide

32 32