View
90
Download
0
Category
Preview:
Citation preview
Workflow Manager - ENDEVOR Attachment
Page: 2
Micro Focus
The Lawn
22-30 Old Bath Road
Newbury, Berkshire RG14 1QN
UK
http://www.microfocus.com
Copyright © 2013-2014 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.
Workflow Manager - ENDEVOR Attachment
Page: 3
Contents
1 Introduction ...................................................................................................... 5
1.1 Software requirements ........................................................................................................................... 5
2 Installation ..................................................................................................... 7
2.1 General considerations ........................................................................................................................... 7
2.2 Basic Installation Procedure ................................................................................................................... 7
2.2.1 Unzip the Software .............................................................................................................................. 7
2.2.2 Upload the software to the mainframe .......................................................................................... 7
2.2.3 Receive the Software .......................................................................................................................... 9
3 The Endevor Attachment .......................................................................... 12
3.1 Overview of REXX Procedures .......................................................................................................... 12
3.2 Overview of Endevor API COBOL Programs................................................................................. 15
4 Customization ............................................................................................. 17
4.1 Compile and Link the COBOL Sources ........................................................................................... 17
4.2 Add the Endevor Workflow Model to the Master Configuration File ...................................... 19
4.2.1 Master Configuration for Enterprise Developer ............................................................................ 19
4.2.2 Master Configuration for RDz ............................................................................................................ 20
4.2.3 Master Configuration for Eclipse ........................................................................................................ 21
4.3 Allocate additional datasets to the z/Server User Task ................................................................ 22
4.4 Optional: Add the LOAD, EXEC and SKELS datasets to ISPF.conf ........................................... 22
4.5 Customizing REXX procedures .......................................................................................................... 23
4.5.1 General customization ...................................................................................................................... 23
4.5.2 Endevor Allocation Exit TAUENXA1 ........................................................................................... 24
4.5.3 File suffix and dataset format assignment using Exit TAUENXA2 ......................................... 24
4.5.4 Selection of valid CCIDs using Exit TAUENXC1 ...................................................................... 24
4.5.5 Set Property Group and SYSLIB for Background parsing using TAUENXSL ...................... 24
4.5.6 Modify Tree View entries using Exit TAUENXTV .................................................................... 24
Workflow Manager - ENDEVOR Attachment
Page: 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
Workflow Manager - ENDEVOR Attachment
Page: 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
2.2.1 Unzip the Software
You will receive the zipped software by email 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.
2.2.2 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 3120.
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,
Workflow Manager - ENDEVOR Attachment
Page: 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 Description
mvsaddr TCP/IP address or hostname of the z/OS system
tsouid Your TSO user ID
tsopw Your TSO password
hlq 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 2011-08-02.
220 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 ..
250 " " 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
Workflow Manager - ENDEVOR Attachment
Page: 9
250 Transfer completed successfully.
FTP: 2675840 bytes sent in 7,91 seconds 70,59 KB/sec
2.2.3 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.T134430…
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 HAS BEEN SUCCESSFULLY LOADED
IEB154I COBOL HAS BEEN SUCCESSFULLY LOADED
IEB154I LOAD HAS BEEN SUCCESSFULLY LOADED
IEB154I XML 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
Workflow Manager - ENDEVOR Attachment
Page: 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 Description
REXX REXX procedures to execute Endevor functions called from the Client via TCP/IP
CNTL JCL samples
NDVRECE JCL to receive all other members
COBOL COBOL sources which contain the Endevor API calls
LOAD LOAD library which can be used as the target library for the compile/link output
of the COBOL sources
XML The Endevor model file
You must use the TSO RECEIVE command again for the following members to create all necessary
datasets:
Member Receive to PDS
REXX hlq.ENDEVOR.REXX
CNTL hlq.ENDEVOR.CNTL
COBOL hlq.ENDEVOR.COBOL
LOAD hlq.ENDEVOR.LOAD
XML hlq.ENDEVOR.XML
Member NDVRECE (already received) contains a receive sample batch job:
Workflow Manager - ENDEVOR Attachment
Page: 11
//STEP1 EXEC PGM=IKJEFT01
//SYSPRINT DD SYSOUT=*
//SYSTSPRT DD 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'
Workflow Manager - ENDEVOR Attachment
Page: 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 Get Endevor element source for Browse
TAUENBLL Get Endevor element informations (BE, HE, CE, BX, CX, HX, LL)
TAUENBLM List an Endevor member using the Print function
TAUENEAC Create a temporary sequential dataset
TAUENEAD Add an Endevor element
TAUENECR Create a new Endevor element
TAUENEDE Delete an Endevor element
TAUENEED Process functions used during a remote Edit action: retrieve, add,
generate
TAUENEGE Generate an Endevor element in place
TAUENEG1 Generate an Endevor element
TAUENEMO Move an Endevor element
TAUENERE Retrieve an Endevor element
TAUENESI Sign in / sign out
Endevor Package
Actions
TAUENPA1 Process Endevor Packages, Actions Approve, Deny, Backin, Backout, Commit,
Inspect, Execute, Reset
Workflow Manager - ENDEVOR Attachment
Page: 13
REXX Name Description
TAUENPCA Process Endevor Packages, Actions Create, Modify, Cast
TAUENPDE Process Endevor Packages, Actions Delete
Endevor Filter
Actions
For Table Structures
TAUENFEL Create an Endevor element table using search filter
TAUENGPK Create an Endevor package table using search filter
Endevor Table and
Tree Actions
For Table and Tree Structures
TAUENGCI Get list of used CCIDs for tree view
TAUENGEL Get element list for tree and table view
TAUENGEN Get environment list for tree view
TAUENGLC Get component level list for table view
TAUENGLV Get element level list for table view
TAUENGPR Get processor group list for tree view
TAUENGSB Get subsystem list for tree view
TAUENGST Get stage list for tree view
TAUENGSY Get system list for tree view
TAUENGTV Get tree view types for tree view (Environment view / CCID view)
TAUENPST 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
Workflow Manager - ENDEVOR Attachment
Page: 14
REXX Name Description
TAUENGPK Determine the properties of an Endevor package
Endevor Select
Values Actions
TAUENLEN Determine valid Endevor environment
TAUENLPR Determine valid Endevor processor groups
TAUENLSB Determine valid Endevor subsystems
TAUENGPK Create an Endevor package table using search filter
TAUENLSI Determine valid Endevor stage IDs
TAUENLSN Determine valid Endevor stage numbers
TAUENLSY Determine valid Endevor systems
TAUENLTY Determine valid Endevor types
Utilities Used as Subroutines
TAUENS01 Used in an Endevor simulation environment only
TAUENS02 Get Endevor definitions
TAUENS03 Get Endevor element container data
TAUENS04 Get Endevor element level information
TAUENS05 Get Endevor element listings
TAUENS06 Get data for container CMP, CMPOBJ, CMPCOM. Scan the component
list and extract input and output components
TAUENS07 Print Endevor member
TAUENS08 Get Endevor element source
TAUENS09 Check if a ddname is already allocated
Workflow Manager - ENDEVOR Attachment
Page: 15
REXX Name Description
TAUENS10 Call Endevor API SCL processor in foreground mode
TAUENS11 Call Endevor API SCL processor in foreground mode
TAUENS12 Call Endevor API SCL processor batch
TAUENS20 Call Endevor API for package information
TAUENS21 Used in an Endevor simulation environment only
Exits for Endevor
TAUENXA1 Allocation of temporary files for Endevor Attachment
TAUENXA2 Change type properties to be returned to the client (for example file
extension)
TAUENXCI Get a list of valid CCIDs to be used for element action association
TAUENXSL Set property group and SYSLIB for background parsing
TAUENXTV Define entries and labels of the tree view
Initialization / End
Processing
TAUENINI Initialize the Endevor model (must be called in TAUTOXA1)
TAUENEND Close Endevor
3.2 Overview of Endevor API COBOL Programs
The following COBOL Sources are used:
COBOL Name Description
TAUENP01 Get Endevor definitions
TAUENP02 Get Endevor element information
TAUENP03 Shutdown the Endevor API
Workflow Manager - ENDEVOR Attachment
Page: 16
TAUENP04 Put all element change levels in a dataset
TAUENP05 Run Endevor actions
TAUENP06 Get Endevor package information
Workflow Manager - ENDEVOR Attachment
Page: 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=, * MEMBER NAME SRC AND
LOAD
// 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 DD DISP=SHR,DSN=&SRCDSN(&MEMBER)
//SYSLIB DD DISP=SHR,DSN=©LIB
//SYSLIN DD DSN=&&SYSLIN,
// DISP=(NEW,PASS),
// UNIT=&TDISK,
// DSORG=PS,RECFM=FB,LRECL=80,BLKSIZE=3120,
// SPACE=(CYL,(5,5),RLSE)
Workflow Manager - ENDEVOR Attachment
Page: 18
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSUT1 DD SPACE=(3120,(500,100),,,ROUND),UNIT=&TDISK
//SYSUT2 DD SPACE=(3120,(500,100),,,ROUND),UNIT=&TDISK
//SYSUT3 DD SPACE=(3120,(500,100),,,ROUND),UNIT=&TDISK
//SYSUT4 DD SPACE=(3120,(500,100),,,ROUND),UNIT=&TDISK
//SYSUT5 DD SPACE=(3120,(500,100),,,ROUND),UNIT=&TDISK
//SYSUT6 DD SPACE=(3120,(500,100),,,ROUND),UNIT=&TDISK
//SYSUT7 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 DD DISP=SHR,DSN=&LELKED
//SYSUT1 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:
Workflow Manager - ENDEVOR Attachment
Page: 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
4.2.1 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: 2.2.1
* process information
INFO:
* end of application definition. Do not delete this line
EndAppl:
EndUser:
Workflow Manager - ENDEVOR Attachment
Page: 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.
4.2.2 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: 2.2.1
* 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.
Workflow Manager - ENDEVOR Attachment
Page: 21
4.2.3 Master Configuration for Eclipse
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: 2.2.1
* 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.
Workflow Manager - ENDEVOR Attachment
Page: 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.
Workflow Manager - ENDEVOR Attachment
Page: 23
4.5 Customizing REXX procedures
4.5.1 General customization
The following adaptations are of special importance:
REXX Procedure Description
TAUZCAPP 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
TAULAPPL 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
TAUTOXA1
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 */
Workflow Manager - ENDEVOR Attachment
Page: 24
Skeleton Name Description
TAUTOXJC
Skeleton for Batch-Support
Define a default Job Card.
The Endevor Attachment uses this skeleton if the user submits an Endevor
batch job.
4.5.2 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.
4.5.3 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.
4.5.4 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.
4.5.5 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.
4.5.6 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.
Recommended