Workflow Manager - ENDEVOR Attachment

Transcription

1 Workflow Manager - ENDEVOR Attachment

2 Micro Focus The Lawn Old Bath Road Newbury, Berkshire RG14 1QN UK Copyright Micro Focus. All rights reserved. MICRO FOCUS and the Micro Focus logo are trademarks or registered trademarks of Micro Focus or its subsidiaries or affiliated companies in the United States, United Kingdom and other countries. All other marks are the property of their respective owners. Page: 2

3 Contents 1 Introduction Software requirements Installation General considerations Basic Installation Procedure Unzip the Software Upload the software to the mainframe Receive the Software The Endevor Attachment Overview of REXX Procedures Overview of Endevor API COBOL Programs Customization Compile and Link the COBOL Sources Add the Endevor Workflow Model to the Master Configuration File Master Configuration for Enterprise Developer Master Configuration for RDz Master Configuration for Eclipse Allocate additional datasets to the z/server User Task Optional: Add the LOAD, EXEC and SKELS datasets to ISPF.conf Customizing REXX procedures General customization Endevor Allocation Exit TAUENXA File suffix and dataset format assignment using Exit TAUENXA Selection of valid CCIDs using Exit TAUENXC Set Property Group and SYSLIB for Background parsing using TAUENXSL Modify Tree View entries using Exit TAUENXTV Page: 3

4 Page: 4

5 1 Introduction The Workflow Manager Endevor Attachment consists of mainframe components which have to be installed in a z/os environment. CA Endevor Software Change Manager (Endevor) supports the software configuration and change management of mainframe applications. With the Endevor Attachment you can: Provide the Endevor development process in an Eclipse environment. Customize the Endevor development process to suit your needs. Model and customize the Eclipse-based Endevor user interface without any programming effort. Seamlessly integrate existing home-grown and third party tools in Eclipse. This document is intended for system programmers and/or Endevor administrators installing and configuring the Workflow Manager Endevor Attachment on their z/os host system. This document refers to the Workflow Manager Endevor Attachment components as the Endevor Attachment. 1.1 Software requirements To use the Endevor Attachment, you need the following product releases: - Enterprise Developer V2.2 Update 1 or later - CA Endevor Software Change Manager (SCM) Release 14 RAM (Repository Access Manager) or later Page: 5

6 Page: 6

7 2 Installation 2.1 General considerations Determine a dataset prefix that matches the naming convention in your company. This document uses the prefix HLQ.ENDEVOR in its specifications. 2.2 Basic Installation Procedure Unzip the Software You will receive the zipped software by or on CD/DVD. Unzip the file to a temporary folder. A folder named ENDEVOR is created, which contains all mainframe installation components. There are no client components to install Upload the software to the mainframe Upload the endevor\install.xmit in binary format to a sequential dataset with a record length of 80 and a block size of Firstly, on z/os, allocate the datasets to use as the upload target files. To do this, create a dataset with the same characteristics as the sample job below (or by submitting the job below). If you choose to submit the job, note the following: - Before submitting, add a job card and modify the parameters to meet your site's requirements. - hlq is the high level qualifier you choose to use for this dataset. - Optionally, add a valid VOLSER and/or change the UNIT parameter. //ALLOC1 EXEC PGM=IEFBR14 //* //FTPALLOC DD DSN=hlq.INSTALL.XMIT, // DISP=NEW,CATLG,DELETE), // DSORG=PS, // RECFM=FB, // LRECL=80, // BLKSIZE=3120, //* VOL=SER=vvvvvv, Page: 7

8 // UNIT=SYSALLDA, // SPACE=(CYL,(5,5)) To upload the files, you can use FTP from a command prompt. In the sample dialog shown below, commands or other information entered by the user are in bold, and the following values are assumed: User input mvsaddr tsouid tsopw hlq Description TCP/IP address or hostname of the z/os system Your TSO user ID Your TSO password High-level qualifier used for the dataset you allocated in the job above C:\>ftp mvsaddr Connected to mvsaddr. 220-FTPD1 IBM FTP CS V1R10 at custom.com, 12:03:32 on Connection will close if idle for more than 5 minutes. User (mvsaddr:(none)): tsouid 331 Send password please. Password: tsopw 230 tsouid is logged on. Working directory is "tsouid.". ftp> cd " " is the working directory name prefix. ftp> cd hlq 250 "hlq." is the working directory name prefix. ftp> binary 200 Representation type is Image ftp> put d:\endevor\install.xmit 200 Port request OK. 125 Storing dataset hlq.install.xmit Page: 8

9 250 Transfer completed successfully. FTP: bytes sent in 7,91 seconds 70,59 KB/sec Receive the Software Using the TSO RECEIVE command creates the partitioned dataset from the compressed XMIT file. This document takes hlq.endevor to be the installation prefix. Enter TSO or Workstation commands below: ===> receive in dataset('hlq.install.xmit') When prompted, enter: INMR906A Enter restore parameters or 'DELETE' or 'END' + restore dataset('hlq.endevor.install.xmit ) You should receive the following messages: COPY INDD=((SYS00031,R)),OUTDD=SYS00030 IEB1013I COPYING FROM PDSU INDD=SYS00031 VOL=USR001 DSN= SYS11214.T IEB1014I TO PDS OUTDD=SYS00030 VOL=USR002 DSN=hlq.ENDEVOR.XMIT IEB167I FOLLOWING MEMBER(S) LOADED FROM INPUT DATA SET REFERENCED BY SYS00031 IEB154I REXX HAS BEEN SUCCESSFULLY LOADED IEB154I NDVRECE HAS BEEN SUCCESSFULLY LOADED IEB154I CNTL IEB154I COBOL IEB154I LOAD IEB154I XML HAS BEEN SUCCESSFULLY LOADED HAS BEEN SUCCESSFULLY LOADED HAS BEEN SUCCESSFULLY LOADED HAS BEEN SUCCESSFULLY LOADED IEB1098I 6 OF 6 MEMBERS LOADED FROM INPUT DATA SET REFERENCED BY SYS00031 IEB147I END OF JOB - 0 WAS HIGHEST SEVERITY CODE INMR001I Restore successful to dataset 'hlq.endevor.install.xmit' The result is a partitioned dataset with the following members: BROWSE hlq.endevor.install.xmit Volume: PROJ00 Page: 9

10 Command ===> Scroll: CSR Name Prompt Size Created Changed ID REXX CNTL NDVRECE COBOL LOAD XML **End** Each member except NDVRECE is a compressed dataset: Member REXX CNTL NDVRECE COBOL LOAD XML Description REXX procedures to execute Endevor functions called from the Client via TCP/IP JCL samples JCL to receive all other members COBOL sources which contain the Endevor API calls LOAD library which can be used as the target library for the compile/link output of the COBOL sources The Endevor model file You must use the TSO RECEIVE command again for the following members to create all necessary datasets: Member REXX CNTL COBOL LOAD XML Receive to PDS hlq.endevor.rexx hlq.endevor.cntl hlq.endevor.cobol hlq.endevor.load hlq.endevor.xml Member NDVRECE (already received) contains a receive sample batch job: Page: 10

11 //STEP1 EXEC PGM=IKJEFT01 //SYSPRINT DD //SYSTSPRT DD SYSOUT=* SYSOUT=* //SYSTSIN DD * RECEIVE INDSNAME('hlq.ENDEVOR.XMIT(REXX)') NONAMES DATASET('hlq.ENDEVOR.REXX') RECEIVE INDSNAME('hlq.ENDEVOR.XMIT(CNTL)') NONAMES DATASET('hlq.ENDEVOR.CNTL') RECEIVE INDSNAME('hlq.ENDEVOR.XMIT(COBOL)') NONAMES DATASET('hlq.ENDEVOR.COBOL') RECEIVE INDSNAME('hlq.ENDEVOR.XMIT(LOAD)') NONAMES DATASET('hlq.ENDEVOR.LOAD') RECEIVE INDSNAME('hlq.ENDEVOR.XMIT(XML)') NONAMES DATASET('hlq.ENDEVOR.XML') /* Verify that each RECEIVE has been successfully processed, e.g. the SYSTSPRT output from the batch job should end with Restore successful for each type received: Restore successful to dataset 'hlq.endevor.type' Page: 11

12 3 The Endevor Attachment 3.1 Overview of REXX Procedures The following REXX procedures are part of the Endevor Attachment: REXX Name Description Endevor Element Actions TAUENBEL TAUENBLL TAUENBLM TAUENEAC TAUENEAD TAUENECR TAUENEDE TAUENEED TAUENEGE TAUENEG1 TAUENEMO TAUENERE TAUENESI Get Endevor element source for Browse Get Endevor element informations (BE, HE, CE, BX, CX, HX, LL) List an Endevor member using the Print function Create a temporary sequential dataset Add an Endevor element Create a new Endevor element Delete an Endevor element Process functions used during a remote Edit action: retrieve, add, generate Generate an Endevor element in place Generate an Endevor element Move an Endevor element Retrieve an Endevor element Sign in / sign out Endevor Package Actions TAUENPA1 Process Endevor Packages, Actions Approve, Deny, Backin, Backout, Commit, Inspect, Execute, Reset Page: 12

13 REXX Name TAUENPCA TAUENPDE Description Process Endevor Packages, Actions Create, Modify, Cast Process Endevor Packages, Actions Delete Endevor Filter Actions For Table Structures TAUENFEL TAUENGPK Endevor Table and Tree Actions Create an Endevor element table using search filter Create an Endevor package table using search filter For Table and Tree Structures TAUENGCI TAUENGEL TAUENGEN TAUENGLC TAUENGLV TAUENGPR TAUENGSB TAUENGST TAUENGSY TAUENGTV TAUENPST Get list of used CCIDs for tree view Get element list for tree and table view Get environment list for tree view Get component level list for table view Get element level list for table view Get processor group list for tree view Get subsystem list for tree view Get stage list for tree view Get system list for tree view Get tree view types for tree view (Environment view / CCID view) Get package status for tree view Determination of Endevor Properties To Complete the Properties View TAUENEPR Determine the properties of an Endevor element or element level Page: 13

14 REXX Name TAUENGPK Description Determine the properties of an Endevor package Endevor Select Values Actions TAUENLEN TAUENLPR TAUENLSB TAUENGPK TAUENLSI TAUENLSN TAUENLSY TAUENLTY Utilities TAUENS01 TAUENS02 TAUENS03 TAUENS04 TAUENS05 TAUENS06 TAUENS07 TAUENS08 TAUENS09 Determine valid Endevor environment Determine valid Endevor processor groups Determine valid Endevor subsystems Create an Endevor package table using search filter Determine valid Endevor stage IDs Determine valid Endevor stage numbers Determine valid Endevor systems Determine valid Endevor types Used as Subroutines Used in an Endevor simulation environment only Get Endevor definitions Get Endevor element container data Get Endevor element level information Get Endevor element listings Get data for container CMP, CMPOBJ, CMPCOM. Scan the component list and extract input and output components Print Endevor member Get Endevor element source Check if a ddname is already allocated Page: 14

15 REXX Name TAUENS10 TAUENS11 TAUENS12 TAUENS20 TAUENS21 Description Call Endevor API SCL processor in foreground mode Call Endevor API SCL processor in foreground mode Call Endevor API SCL processor batch Call Endevor API for package information Used in an Endevor simulation environment only Exits for Endevor TAUENXA1 TAUENXA2 TAUENXCI TAUENXSL TAUENXTV Allocation of temporary files for Endevor Attachment Change type properties to be returned to the client (for example file extension) Get a list of valid CCIDs to be used for element action association Set property group and SYSLIB for background parsing Define entries and labels of the tree view Initialization / End Processing TAUENINI TAUENEND Initialize the Endevor model (must be called in TAUTOXA1) Close Endevor 3.2 Overview of Endevor API COBOL Programs The following COBOL Sources are used: COBOL Name TAUENP01 TAUENP02 TAUENP03 Description Get Endevor definitions Get Endevor element information Shutdown the Endevor API Page: 15

16 TAUENP04 TAUENP05 TAUENP06 Put all element change levels in a dataset Run Endevor actions Get Endevor package information Page: 16

17 4 Customization Before using the Endevor Attachment for the first time, you must perform some modifications. 4.1 Compile and Link the COBOL Sources You need to compile and link all the COBOL sources in hlq.endevor.cobol. The following sample compile and link job COBLNK is delivered in hlq.endevor.cntl: //JOBCARD //* //PCOBLNK PROC MEMBER=, LOAD * MEMBER NAME SRC AND // LOADLIB=HLQ.ENDEVOR.LOAD, * TARGET LOAD LIBRARY // SRCDSN=HLQ.ENDEVOR.COBOL, * SOURCE DATASET // TDISK=SYSDA, * UNIT // LELKED=CEE.SCEELKED, * LE SCEELKED // STEPCOB=IGY420.SIGYCOMP, * LE COBOL COMPILER // COPYLIB=ENDEVOR.CSIQOPTN * ENDEVOR CSIQOPTN //********************************************************************** //* COMPILE THE PROGRAM //********************************************************************** //COB EXEC PGM=IGYCRCTL, // COND=(4,LT), // PARM='LIST,MAP,LIB,RENT,SOURCE,DYN' //STEPLIB DD DISP=SHR,DSN=&STEPCOB //SYSIN //SYSLIB //SYSLIN DD DISP=SHR,DSN=&SRCDSN(&MEMBER) DD DISP=SHR,DSN=&COPYLIB DD DSN=&&SYSLIN, // DISP=(NEW,PASS), // UNIT=&TDISK, // DSORG=PS,RECFM=FB,LRECL=80,BLKSIZE=3120, // SPACE=(CYL,(5,5),RLSE) Page: 17

18 //SYSPRINT DD SYSOUT=* //SYSUDUMP DD SYSOUT=* //SYSUT1 //SYSUT2 //SYSUT3 //SYSUT4 //SYSUT5 //SYSUT6 //SYSUT7 DD SPACE=(3120,(500,100),,,ROUND),UNIT=&TDISK DD SPACE=(3120,(500,100),,,ROUND),UNIT=&TDISK DD SPACE=(3120,(500,100),,,ROUND),UNIT=&TDISK DD SPACE=(3120,(500,100),,,ROUND),UNIT=&TDISK DD SPACE=(3120,(500,100),,,ROUND),UNIT=&TDISK DD SPACE=(3120,(500,100),,,ROUND),UNIT=&TDISK DD SPACE=(3120,(500,100),,,ROUND),UNIT=&TDISK //********************************************************************** //* LINK EDIT THE COBOL PROGRAM //********************************************************************** //LNK EXEC PGM=IEWL, // COND=(4,LT), // PARM='AMODE=31,RMODE=ANY,LIST,XREF,RENT,REUS' //SYSLIN DD DSN=&&SYSLIN,DISP=(OLD,DELETE) //SYSLMOD DD DISP=SHR,DSN=&LOADLIB(&MEMBER) //SYSLIB //SYSUT1 DD DISP=SHR,DSN=&LELKED DD DSN=&&SYSUT1,UNIT=&TDISK,SPACE=(1024,(50,20)) //SYSPRINT DD SYSOUT=* // PEND //* // EXEC PCOBLNK,MEMBER=TAUENP01 // EXEC PCOBLNK,MEMBER=TAUENP02 // EXEC PCOBLNK,MEMBER=TAUENP03 // EXEC PCOBLNK,MEMBER=TAUENP04 // EXEC PCOBLNK,MEMBER=TAUENP05 // EXEC PCOBLNK,MEMBER=TAUENP06 Before you submit this job you must perform some customizations: Page: 18

19 - Enter a valid jobcard - Change the HLQ to your installation s first qualifier - Verify the dataset name of the link library and change the name if necessary - Verify the dataset name where the COBOL compiler is installed and change the name if necessary - Enter a valid unit parameter or delete this parameter if it is not necessary in your system environment - Change the first qualifiers of the CSIQOPTN dataset to the ENDEVOR installation prefix Submit the job and verify that all compile and link steps were successfully executed. If the job runs successfully, the load library HLQ.ENDEVOR.LOAD should contain seven members; the member DUMMY and six members TAUENPnn (nn=01 to 06). 4.2 Add the Endevor Workflow Model to the Master Configuration File Master Configuration for Enterprise Developer Edit the master configuration file and insert the following reference to the Endevor workflow model: * * Endevor Workflow Model for Enterprise Developer * * application name User: Appl: Endevor Application * location of the application configuration file Conf: MVS:HLQ.ENDEVOR.XML(NDV221) Property: PROP_Client_env =ED * application version number Version: * process information INFO: * end of application definition. Do not delete this line EndAppl: EndUser: Page: 19

20 You must customize the Conf: entry to reference the installed XML dataset. Save the member NDV221 before you start to customize the Endevor model Master Configuration for RDz Edit the Master Configuration file and insert the following reference to the Endevor workflow model: * * Endevor Workflow Model for RDz * * application name User: Appl: Endevor Application * location of the application configuration file Conf: MVS:HLQ.ENDEVOR.XML(NDV221) Property: PROP_Client_env =RDZ * application version number Version: * process information INFO: * end of application definition. Do not delete this line EndAppl: EndUser: You must customize the Conf: entry to reference the installed XML dataset. Save the member NDV221 before you start to customize the Endevor model. Page: 20

21 4.2.3 Master Configuration for Eclipse Workflow Manager - ENDEVOR Attachment Edit the master configuration file and insert the following reference to the Endevor workflow model: * * Endevor Workflow Model for Eclipse * * application name User: Appl: Endevor Application * location of the application configuration file Conf: MVS:HLQ.ENDEVOR.XML(NDV221) Property: PROP_Client_env = * application version number Version: * process information INFO: * end of application definition. Do not delete this line EndAppl: EndUser: You must customize the Conf: entry to reference the installed XML dataset. Save the member NDV221 before you start to customize the Endevor model. Page: 21

22 4.3 Allocate additional datasets to the z/server User Task Within the z/server User Task, you must allocate all datasets necessary to run Endevor functions and the Endevor Attachment in ISPF batch. To be able to access the Endevor Attachment, you must allocate the received REXX library to SYSEXEC, and the LOAD library to the STEPLIB. Customize the JCL of the z/server User Task to perform this allocation (see the z/server Installation Guide for details on how to set up a user server): //IVPISPF EXEC PGM=IKJEFT1B,PARM='%IVPINIT1 &PORT ', // DYNAMNBR=200,REGION=0M,TIME=NOLIMIT //STEPLIB DD DSN=&TAURHLQ..LOADLIB,DISP=SHR // DD DSN=HLQ.ENDEVOR.LOADLIB,DISP=SHR //SYSEXEC DD DSN=&TAURHLQ..REXX,DISP=SHR // DD DSN=HLQ.ENDEVOR.REXX,DISP=SHR // DD DSN=&TAURHLQ..REXX,DISP=SHR //ISPPLIB DD DSN=&ISPFHLQ..SISPPENU,DISP=SHR // DD DSN=ISF.SISFPLIB,DISP=SHR //ISPSLIB DD DSN=&ISPFHLQ..SISPSENU,DISP=SHR // DD DSN=&TAURUHLQ..SKELS,DISP=SHR // DD DSN=ISF.SISFSLIB,DISP=SHR //ISPMLIB DD DSN=&ISPFHLQ..SISPMENU,DISP=SHR // DD DSN=ISF.SISFMLIB,DISP=SHR 4.4 Optional: Add the LOAD, EXEC and SKELS datasets to ISPF.conf If the Endevor attachment is used within Rational Developer for System z with the IBM RSE daemon as server, you need to add the installation EXEC and SKELS datasets to the configuration file ISPF.conf in the USS configuration path of the RSE daemon. Page: 22

23 4.5 Customizing REXX procedures General customization The following adaptations are of special importance: Workflow Manager - ENDEVOR Attachment REXX Procedure TAUZCAPP TAULAPPL TAUTOXA1 Description If the Endevor attachment is used within Enterprise Developer with z/server as server, adjust the reference to the location of the master configuration file, as required. Default: HLQ.ZSERVER.MASTER If the Endevor attachment is used within Rational Developer for System z with the IBM RSE daemon as server, adjust the reference to the location of the master configuration file, as required. Default: HLQ.ZSERVER.MASTER Tool interface exit: you may use this exit for dynamic allocations or to set the ISPF environment variables necessary to run your specific Endevor application. You must call the procedure TAUENINI shipped with the Endevor Attachment in TAUTOXA1. To minimize the number of calls during a user task session, add the following statements somewhere after the variable TAUTOALC has been retrieved from the ISPF shared pool: Call ISPF '8 VGET (TAUTOALC) SHARED'. /* Endevor Init */ Call ISPF '8 VGET (#ALLVAR) SHARED' If Result = 0 Then Do If tautoalc /= p_parm Then Call REXX '0 TAUENINI' p_parm End Else Call REXX '0 TAUENINI' p_parm /* End of Endevor Init */ Page: 23

24 Skeleton Name TAUTOXJC Description Skeleton for Batch-Support Define a default Job Card. The Endevor Attachment uses this skeleton if the user submits an Endevor batch job Endevor Allocation Exit TAUENXA1 Data is partially interchanged using files for the communication between the client and the Endevor Attachment. The creation of the temporary files is done as part of the procedure TAUENXA1. TAUENXA1 should be adjusted to the available environment as needed. Files which begin with userid.tauentmp are created by default. These files are temporary but are not deleted automatically within the tool attachment. Instead, once created, they can be reused. We advise that you place these files on a work unit and allow them to be deleted after being inactive for a long period of time File suffix and dataset format assignment using Exit TAUENXA2 A file must contain the correct suffix (for example CBL, JCL) in order for it to be opened with the required editor. By default, the Endevor Attachment gets the dataset format information from Endevor. The information is passed to the Exit TAUTOXA2 where you can replace specific values if necessary. If, for example, the file extension is not maintained in Endevor, you should use this Exit procedure to associate the correct file suffix depending on the Type or Processor Group passed Selection of valid CCIDs using Exit TAUENXC1 If you allow your Endevor user to associate only valid CCIDs that are maintained outside of Endevor, you can customize this Exit procedure to create a valid selection list Set Property Group and SYSLIB for Background parsing using TAUENXSL Set the values Property Group, Category and SYSLIB if you want to use Background parsing. The values allow the parser to resolve copy books Modify Tree View entries using Exit TAUENXTV In this rexx, the tree view entries and their labels are defined. You can change the labels or remove entries from tree view. Page: 24