Integrating with Endevor
This integration is possible but its implementation is manual. You can import the Rational® Programming Patterns data into Endevor through Rational Team Concert™ if you have previously used the Pacbase - Endevor bridge. Your applications must already contain the $7N User Entities that are required to parameterize the transfer to Endevor.
You must complete the following tasks in the chronological order:
- Generate the source code of the instances to be imported into Endevor:
- Generate the instances in Pacbase.
- Import the design of these instances into Rational Programming Patterns.
- Use the migration help function to migrate the code of the instances into the local workspace.
- Migrate the $7N User Entities that were created for the Pacbase - Endevor bridge to your Rational Team Concert workspace. A $7N User Instance must exist for each instance to be imported.
- Add an RPPinfo micropattern at the beginning of each .cbl
file to be imported. You can add this micropattern manually or include it in a Macro. This
micropattern contains two sets of information:
- General information that can be used in several contexts:
*!RPPinfo *USER=Rational Team Concert connection user *PROJECT=project that contains the design instance *ENTITY=design instance name *TYPE=pacprogram, pacscreen, ... *DATE= *TIME=
- Additional information that is specific to Endevor:
- An Endevor parameter on the micropattern declaration line.
- The Endevor information in the $7N User Entity that corresponds to the generated instance. You must enter this information after the general information.
*!RPPinfo Endevor *ENVIRONMENT= *SYSTEM= *SUBSYSTEM= *TYPEPAC= *TYPEINFOPAC= *COMMENT= *CCID=
Example of an RPPinfo micropattern used for a migration to Endevor:*!RPPinfo Endevor *USER= *PROJECT=BPCEMIBR.FRX *ENTITY=90BE20 *TYPE=pacprogram *DATE=2013/04/16 *TIME=10:36:18 *ENVIRONMENT=HFW *SYSTEM=HUB *SUBSYSTEM=FG *TYPEPAC=COBOLP *COMMENT=Integration V2 V210 *CCID=191018
- General information that can be used in several contexts:
- In Rational Team Concert, deliver the .cbl files that contain the RPPinfo micropattern.
- In the Team artifacts view of the Work items
perspective, create the elements that will update Endevor with the delivered data:
- Create a z/OS dependency build - Rational Build Agent-type build definition.
- Create a translator and associate it with the build generation. This translator must call a REXX script in z/OS® to trigger the update in Endevor.
- Create the REXX script. This script retrieves the source code and the variables of the RPP micropattern to generate a JCL that imports the Pacbase data into Endevor.
- Customize the Endevor environment information as it is indicated in the Pacbase installation guide that is specific to your environment.