CA Endevor Software Change Manager

Transcription

1 CA Endevor Software Change Manager Parallel Development WIP Merge Enhancement r12

2 This documentation and any related computer software help programs (hereinafter referred to as the Documentation ) is for the end user s informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and protected by the copyright laws of the United States and international treaties. Notwithstanding the foregoing, licensed users may print a reasonable number of copies of the documentation for their own internal use, and may make one copy of the related software as reasonably required for back-up and disaster recovery purposes, provided that all CA copyright notices and legends are affixed to each reproduced copy. Only authorized employees, consultants, or agents of the user who are bound by the provisions of the license for the product are permitted to have access to such copies. The right to print copies of the documentation and to make a copy of the related software is limited to the period during which the applicable license for the Product remains in full force and effect. Should the license terminate for any reason, it shall be the user s responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed. EXCEPT AS OTHERWISE STATED IN THE APPLICABLE LICENSE AGREEMENT, TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION AS IS WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO THE END USER OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED OF SUCH LOSS OR DAMAGE. The use of any product referenced in the Documentation is governed by the end user s applicable license agreement. The manufacturer of this Documentation is CA. Provided with Restricted Rights. Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections , , and (c)(1) - (2) and DFARS Section (b)(3), as applicable, or their successors. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies. Copyright 2009 CA. All rights reserved.

3 CA Product References This document references the following CA products: CA Endevor Software Change Manager (CA Endevor SCM) Contact CA Contact Technical Support For online technical assistance and a complete list of locations, primary service hours, and telephone numbers, contact Technical Support at Provide Feedback If you have comments or questions about CA product documentation, you can send a message to techpubs@ca.com. If you would like to provide feedback about CA product documentation, please complete our short customer survey, which is also available on the CA Support website.

4

5 Contents Chapter 1: Understanding the PDM WIP Merge Enhancement 7 Direct Merge of WIP Files to CA Endevor SCM Locations... 7 How the Merge Process Works... 8 Merge Process Considerations How to Merge Multiple WIP Files Merge Output SCL Statement New Parameters Updated Merge Output Batch SCL Statements Build WIP Statement Batch SCL Syntax Merge Output WIP Statement Batch SCL Syntax Quick Edit Access to the Parallel Development Option New Messages PDM Messages New Parser Messages CA Endevor SCM Messages Contents 5

6

7 Chapter 1: Understanding the PDM WIP Merge Enhancement This enhancement introduces a new feature to the Parallel Development (PDM) option, which lets users merge output directly into CA Endevor SCM locations. In addition, clients who are licensed for the Quick-Edit option and the Parallel Development option can access PDM from the Quick-Edit Option panel. This section contains the following topics: Direct Merge of WIP Files to CA Endevor SCM Locations (see page 7) How the Merge Process Works (see page 8) How to Merge Multiple WIP Files (see page 14) Merge Output SCL Statement New Parameters (see page 17) Updated Merge Output Batch SCL Statements (see page 17) Quick Edit Access to the Parallel Development Option (see page 31) New Messages (see page 32) Direct Merge of WIP Files to CA Endevor SCM Locations This enhancement lets users of the Parallel Development option merge a Work-In-Progress (WIP) file directly to an output location in CA Endevor SCM, where each derivation is recorded in a separate change level. This option is valid only if the WIP file was built from CA Endevor SCM locations; the file to which programmers are making changes (the Root) and the modified copies of the Root (the derivations) must all be located in CA Endevor SCM. This option is available using either the foreground panels or batch SCL statements. The foreground Merge Output Specification panels let you specify whether you want to merge to a data set or to CA Endevor SCM. If you choose to merge to a CA Endevor SCM location, you must explicitly specify the Environment, System, Subsystem, Type, and Stage ID. If you provide an invalid stage ID, valid stage IDs are displayed after you press Enter and you can then enter a valid number. The batch Merge Output SCL statement now lets you merge derivations directly into a CA Endevor SCM location. You must explicitly specify the Environment, System, Subsystem, Type, and the Stage ID or Stage number. Chapter 1: Understanding the PDM WIP Merge Enhancement 7

8 How the Merge Process Works In foreground or batch, when the merge output location is in CA Endevor SCM, you can specify the following additional options: perform element synchronization at the target CA Endevor SCM location against the Root, before performing actions to create the derivation change levels; delete the derivation elements after a successful merge; bypass the execution of the element's generate processor after a successful merge; and specify a processor group name to override the element's processor group name. How the Merge Process Works The merge process creates CA Endevor SCM change levels from the WIP file. Each derivation is represented in a change level. The element is built at the CA Endevor SCM location you specify. This process can only occur when the root and all derivations are all CA Endevor SCM elements. Before you invoke the merge process, you must edit all conflicts out of the WIP file. The WIP file can contain non-conflicting inserts and deletes. The merge process involves the following steps: 1. The Parallel Development Manager makes the following changes to the merge output file: removes the WIP header information inserts and deletes lines as necessary removes the WIP annotations ignores comment lines 8 Parallel Development WIP Merge Enhancement

9 How the Merge Process Works 2. The Parallel Development Manager stores the merged output to the CA Endevor SCM location where each derivation is recorded in a separate element change level. Each derivation has a change level created with its associated CCID, Comment, User ID, Date, and Time. How merged elements are stored depends on whether the element exists at the target location or up the map from the target, whether the change level and time stamp of the target element matches the Root of the derivation, and whether the option SYNC NDVR OUTPUT is active. If the element is new to the target location and route, the element is constructed as follows: The Base element contains the Root's statements and has its base attributes set to the Root's CCID, Comment, User ID, Date, and Time. The first derivation's changes are recorded in a change level using the derivation's CCID, Comment, User ID, Date, and Time. If a second derivation was used during the WIP process, another change level is created using this derivation's CCID, Comment, User ID, Date, and Time. If an element with the same name already exists at the merge target location, a synchronization check is performed to insure that the existing element is at the same source level as the Root element used during the WIP process. If the element is in-sync with the Root, change levels are created for each of the derivations found in the WIP file. Each change level inherits the derivation's CCID, Comment, User ID, Date, and Time. If the element is out-of-sync with the Root, the merge output process terminates. After a failure, you should examine the causes to determine the appropriate action. If you still want to perform the merge you can use the Merge Output SYNC option. This creates a sync change level that brings the element back to the Root's state. If an element with the same name exists up the map from the merge target location, a synchronization check is performed between that element and the root. If the element is in-sync with the Root element, then the element is fetched back to the merge target location. Change levels are created for each of the derivations found in the WIP file. Each change level inherits the derivation's CCID, Comment, User ID, Date, and Time. Chapter 1: Understanding the PDM WIP Merge Enhancement 9

10 How the Merge Process Works If the element is out of sync with the Root, then the merge output process terminates. After a failure, you should examine the causes to determine the appropriate action. If you still want to perform the merge you can use the Merge Output SYNC option. This creates a sync change level after the element is fetched back to the target location. This sync level brings the element's source back to the same level as the Root element. Example: The element does not exist at the target, but exist up the map Assume the Root is at PRD S2, DV1 is at DEV S1, DV2 is at QA S1, and you want to merge the two derivations into the target at QA S2. Before the merge process begins, the element change levels are located in the life cycle as shown next: DEV S1 DEV S2 QA S1 QA S2 PRD S2 Elem to Elem to Elem to The result of this merge procedure is as follows: QA S2: Elem , created by fetch Elem contains changes between Root and DV1. Elem contains changes between level and DV2. The merge process occurs in the following sequence: 1. The element Elem is fetched back to QA S2 from PRD S2: DEV S1 DEV S2 QA S1 QA S2 PRD S2 Elem to Elem to Elem to Elem DV1 Elem1 at DEV S1 is added to QA S2 in a separate level as level This Elem contains changes between Root and DV1. DEV S1 DEV S2 QA S1 QA S2 PRD S2 Elem to Elem to Elem to Elem to Parallel Development WIP Merge Enhancement

11 How the Merge Process Works 3. DV2 Elem1 at QA S1 added to QA S2 in separate level as level DEV S1 DEV S2 QA S1 QA S2 PRD S2 Elem to Elem to Elem to Elem , 01.20, Example: Level of target does not match level of Root or DV1 and the SYNC option is on If the element does exist at the target, or up the map, but it is not the same level as the root, the first derivation is not equal to the target's last level and time stamp, and the PDM SYNC option on, storage management ($SMRSYNC) synchronization checks are performed. If the element is not at the target but exists up the map, the element is first fetched back to the target location and a change level is created to bring the element to the Root's state. After this correction, the PDM Merge file containing the Root and DV1 statements are used as input on a pseudo Endevor Add action which creates a change level for DV1. If a DV2 file is involved in a PDM Merge, then another Merge file containing the Root, DV1 and DV2 statements is used as input to perform another pseudo Endevor Add action. The charts below show this process pictorially. Assume the Root is at PRD S2, DV1 is at DEV S1, DV2 is at QA S2, and you want to merge the two derivations into the target at QA S1.And the option SYNC NDVR OUTPUT is active. Before the merge process begins, the element change levels are located in the life cycle as shown next: DEV S1 DEV S2 QA S1 QA S2 PRD S2 Elem to Elem to Elem to The result of this merge procedure is as follows: QA S1: Elem , created by fetch Elem , created by sync Elem contains changes between Root and DV1. Elem contains changes between and DV2. Note: If the SYNC NDVR OUTPUT option was not selected, this process would fail after it determined that the Root and target were out of synchronization. Chapter 1: Understanding the PDM WIP Merge Enhancement 11

12 How the Merge Process Works The merge process occurs in the following sequence: 1. The element Elem is fetched back to QA S1 from PRD S2 as shown next: DEV S1 DEV S2 QA S1 QA S2 PRD S2 Elem to Elem to Elem Elem to Elem1 at QA S1 is synchronized with the Root. In this example the SYNC NDVR OUTPUT is active. Sync level is created to bring the element back to changes. DEV S1 DEV S2 QA S1 QA S2 PRD S2 Elem to Elem to Elem to Elem to DV1 Elem1 at DEV S1 is added to QA S1 in a separate level as level DEV S1 DEV S2 QA S1 QA S2 PRD S2 Elem to Elem to Elem , 01.21, Elem to DV2 Elem1 at QA S2 is added to QA S1 in a separate level as level DEV S1 DEV S2 QA S1 QA S2 PRD S2 Elem to Elem to Elem , 01.21, 01.22, Elem to If the DELETE NDVR DV1 DV2 AFTER MERGE option is on during the PDM MERGE, the element at DEV S1 and QA S2 are deleted and the final result would look like this: DEV S1 DEV S2 QA S1 QA S2 PRD S2 Elem , 01.21, 01.22, Elem to Parallel Development WIP Merge Enhancement

13 How the Merge Process Works Note: If the optional SYNC feature is off, the merge process fails after it determines that the element found at the target location, or up the map from it, is out-of-sync with the Root. Merge Process Considerations During the merge process the following considerations apply: The root element location must be the last change level except when the DV1 element specification is equal to the target Endevor location. The sync change level is created with the Root's CCID, Comment, User ID, Time and Date. Each derivation has a change level created with its associated CCID, Comment, User ID, Time and Date. This merge process is in effect two CA Endevor SCM Add actions, where the first Add action contains merged statements between the Root and DV1 and where the second Add action contains merged statements from the Root, DV1, and DV2. Only one security call is performed for this ARQ action. The "before" and "after" exits are executed for each functional Add. The generate processor is done only once just before the last functional add exit 3 call. This PDM Add requires a target stage specification. The target stage is not restricted to the entry stage of an environment. The before exit 2 call honors the following request changes: User data for the target element (REQUSR) Delete Input (DV1 & DV2) source (REQDEL) Bypass Generate (REQBYGEN) Update if present (REQUPDT) Sync (REQSYNC) Processor Group name (REQOPGRP) The before exit 2 call does NOT honor the following request changes: New Element Version (REQELVER) Bypass Element Name Edit (REQBENE) Chapter 1: Understanding the PDM WIP Merge Enhancement 13

14 How to Merge Multiple WIP Files The before exit 2 call passes the following fields to the exit; however, if this information is updated by a user exit 2 program, CA Endevor SCM does not accept these changes. The fields are not modifiable in CA Endevor SCM. CCID (REQCCID) Comment (REQCOMM) Signout override (REQSISOF) The Signin/Signout Option 2 - Validate data set feature is bypassed. This feature verifies that the source of the Add or Update is the same data set and member as specified on the last element retrieval. Override signout is presumed. User authorization for 'override signout' is still done. The Exit 4 invocation is bypassed. This exit is called before exit 2 for the following actions: Add, Update, and Retrieve. Exit 4 is used to change external files using the $FILDS control block. How to Merge Multiple WIP Files You can use the either the foreground panels or the batch SCL statements to merge multiple changes from developer sandboxes to a CA Endevor Location. However, each merge output process is limited to two derivations, so more than one merge process must be used when you want to merge more than two derivations. Example: How to merge changes from three developer sandboxes This example shows how you can use PDM to merge changes from three developer sandboxes into a mapped QA environment. This example assumes the following: The life cycle and map routes are as defined as follows, with three Development sandbox subsystems. DEV Stage1 SYS001 SBS001 mapped to DEV Stage2 SYS001 SBS001 DEV Stage2 SYS001 SBS001 mapped to QA Stage1 SYS001 SBSC1 DEV Stage1 SYS001 SBS002 mapped to DEV Stage2 SYS001 SBS002 DEV Stage2 SYS001 SBS002 mapped to QA Stage1 SYS001 SBSC1 DEV Stage1 SYS001 SBS003 mapped to DEV Stage2 SYS001 SBS003 DEV Stage2 SYS001 SBS003 mapped to QA Stage1 SYS001 SBSC1 QA Stage1 SYS001 SBSC1 mapped to QA Stage2 SYS001 SBSC1 14 Parallel Development WIP Merge Enhancement

15 How to Merge Multiple WIP Files QA Stage2 SYS001 SBSC1 mapped to PRD Stage1 SYS001 SBSC1 PRD Stage1 SYS001 SBSC1 mapped to PRD Stage2 SYS001 SBSC1 Element1 is at QA S2 with version level: Element1 is retrieved to the three sandboxes by different developers. All three developers work on changes in their own sandboxes. To merge changes from sandboxes SBS001, SBS002 and SBS003 to QA Stage2, PDM will need to be invoked twice as follows, using either the foreground panels or the batch SCL statements. 1. The first PDM action should be given the following directive: Root = Element1 at QA/2 DV1 = Element1 at DEV Stage1 SYS001 SBS001 DV2 = Element1 at DEV Stage1 SYS001 SBS002 Merge target set to QA Stage2 SYS001 SBSC1 This action will merge the changes at QA Stage2 and will record each change in separate change levels. Change level will represent DV1's modifications (that is, it contains the changes between the Root and DV1) and will be labeled with its CCID, Comment, User ID, Date and Time. Change level will represent DV2's modifications and will be labeled with its CCID, Comment, User id, Date and Time. 2. To merge the third change into Element1 at QA Stage2, PDM should be invoked again. The second PDM action should be given the following directives: Root = Element1 at QA/2 version 01 level 19 DV1 = Element1 at QA/2 version 01 level 21 DV2 = Element1 at DEV Stage1 SYS001 SBS003 Merge target set to QA Stage2 SYS001 SBSC1 This action will merge the changes from DV2 into Element1 at QA Stage2 as change level and will be labeled with DV2's CCID, Comment, User ID, Date and Time. Chapter 1: Understanding the PDM WIP Merge Enhancement 15

16 How to Merge Multiple WIP Files The results from the two sets of PDM commands are shown in the following illustration. The first set of commands merges the changes to element 1 version level made by developers in sandboxes SBS001 and SBS002 to create levels and in QA Stage 2 SBSC1. These merges are represented by the two thick blue arrows. The second set of commands merges the changes to element 1 version level made by a developer in sandbox SBS003 to create levels This merge is represented by the thick red arrow. 16 Parallel Development WIP Merge Enhancement

17 Merge Output SCL Statement New Parameters Merge Output SCL Statement New Parameters The new parameters for the Merge Output SCL statement are as follows: SYNC NDVR OUTPUT Specifies that element synchronization will be performed at the target CA Endevor SCM location against the Root before performing actions to create the DV1 or DV2 change levels. This clause can only be used if the Merge Output location is in CA Endevor SCM. DELETE NDVR DV1 DV2 AFTer MERge Specifies that the DV1 and DV2 elements are deleted after a successful merge. This clause can only be used if the Merge Output location is in CA Endevor SCM. The keywords AFTer MERge are optional. BYPASS GENERATE PROCESSOR AFTer MERge Specifies that the execution of the element's generate processor is bypassed after a successful merge. This clause can only be used if the Merge Output location is in CA Endevor SCM. The keywords AFTer MERge are optional. PROCESSOR GROUP NAME proc-name Specifies a processor group name that will be used to override the element's processor group name. This clause can only be used if the Merge Output location is in CA Endevor SCM. Updated Merge Output Batch SCL Statements You can use the batch SCL Build WIP statement and the Merge Output statement to merge output to a CA Endevor SCM location. The complete syntax for these statements, including the new parameters, is described next. Build WIP Statement Batch SCL Syntax The Build WIP statement compares the root and changes to the root contained in a derivation file. Optionally, you can also compare the changes contained in a second derivation file, compare specific columns, replace data, and merge the WIP data to a merge output library. In addition, you can specify whether to create a WIP file, write statistics gathered during the build process, delete the WIP file after completion of the merge process, and specify the language type for the members when the WIP file is merged and the merge data set is a CA Panvalet or CA Librarian data set. Chapter 1: Understanding the PDM WIP Merge Enhancement 17

18 Updated Merge Output Batch SCL Statements If the merge output option is specified and the merge output location is a CA Endevor SCM location, then the following additional options can be specified: perform element synchronization at the target CA Endevor SCM location against the Root, before performing actions to create the derivation change levels; delete the derivation elements after a successful merge; bypass the execution of the element's generate processor after a successful merge; and specify a processor group name to override the element's processor group name. 18 Parallel Development WIP Merge Enhancement

19 Updated Merge Output Batch SCL Statements The Build WIP statement syntax is shown next. Chapter 1: Understanding the PDM WIP Merge Enhancement 19

20 Updated Merge Output Batch SCL Statements Build WIP Statement SCL Syntax Parameters This statement has the following parameters: BUIld Identifies the action statement. BUIld must be the first word in a Build action statement. WIP DDName ddname DSName dsname Specifies the WIP file as one of the following: DDName ddname Specifies the ddname. This requires the appropriate JCL. DSName dsname Specifies the data set name. ROOt DDName ddname DSName dsname LOCATION1 Specifies the Root location as one of the following: DDName ddname Specifies the ddname. This requires the appropriate JCL. DSName dsname Specifies the data set name. LOCATION1 Specifies the CA Endevor SCM location. This is a syntax fragment composed of the following keywords and variables: ENVironment environment-name SYStem system_name SUBsystem subsystem name TYPE type_name STAge stage_id STAge NUMber stage_number [WHERE CCID ccid [ANY BASE LAST ACTION RETRIEVE GENERATE]] You must specify the environment, system, subsystem, type, and either the stage id or stage number. The optional WHERE CCID clause limits the search to elements that match the ccid you specify. The following keywords and variables are required: ENVironment environment-name Specifies the element's environment location. SYStem system_name Specifies the element's system name association. 20 Parallel Development WIP Merge Enhancement

21 Updated Merge Output Batch SCL Statements SUBsystem subsystem name Specifies the element's subsystem association. TYPE type_name Specifies the element's type. Also, you must specify one of the following: STAge stage_id Specifies the element's stage ID location. STAge NUMber stage_number Specifies the element's stage number location. The following clause is optional: WHERE CCID ccid [ANY BASE LAST ACTION RETRIEVE GENERATE] (Optional) Specifies the element's CCID. The following keywords are optional and let you limit the match to the element whose base, last action, retrieve, or generate CCID matches the CCID you specify. ANY is the default. ANY - Indicates any element, with the specified CCID, at the specified location. The default. BASE - Indicates the base level element, with the specified CCID, at the specified location. LASt ACTion - Indicates the version of the element, with the specified CCID, upon which the last action was performed at the specified location. RETrieve - Indicates the version of the element, with the specified CCID, that was retrieved to the specified location. GENerate - Indicates the version of the element, with the specified CCID, that was generated at the specified location. DV1 DDName ddname DSName dsname LOCATION1 Specifies Derivation 1 location as one of the following: Note: The maximum LRECL allowed for a Derivation 1 member is DDName ddname Specifies the ddname. This requires the appropriate JCL. DSName dsname Specifies the data set name. Chapter 1: Understanding the PDM WIP Merge Enhancement 21

22 Updated Merge Output Batch SCL Statements LOCATION1 Specifies the CA Endevor SCM location. This is a syntax fragment. Note: For more information, see the parameter ROOt DDName ddname DSName dsname LOCATION1. DV2 DDName ddname DSName dsname LOCATION1 (Optional) Specifies Derivation 2 location as one of the following: DDName ddname Specifies the ddname. This requires the appropriate JCL. DSName dsname Specifies the data set name. LOCATION1 Specifies the CA Endevor SCM location. This is a syntax fragment. For more information, see the parameter ROOt DDName ddname DSName dsname LOCATION1. Note: The maximum LRECL allowed for a Derivation 2 member is COMpare nn THRu nn (Optional) Specifies the columns for comparison during the Build WIP process, to establish changes. If specified, you must provide a beginning column and an ending column with the keyword THRu or THRough. If only one column value is entered, you will receive an error message. The beginning column default is 7. The end column default is 72. Note: Use caution when specifying a compare range for variable length records. If record lengths are different, PDM may annotate a record (line) as changed, even if record data is identical. For example, trailing blanks may be truncated in a variable length record. REPlace NO REPlace (Optional) Indicates on a global level, whether you want to replace likenamed WIP members in the WIP data set. Specify one of the following. REPlace Replaces existing members with like-named new members. NO REPlace Specifies that PDM will not replace like-named WIP members in the WIP data set and PDM will not write a new member to the WIP data set. The default. 22 Parallel Development WIP Merge Enhancement

23 Updated Merge Output Batch SCL Statements MERge OUTput DDName ddname DSName dsname LOCATION2 [NO REPLACE REPLACE] (Optional) Specifies the location for the merge output library associated with this WIP data set. You have the option to replace existing members with like-named new members. If you code this clause, you must provide one of the following: DDName ddname Specifies the ddname. This requires the appropriate JCL. DSName dsname Specifies the data set name. LOCATION2 Specifies the CA Endevor SCM location. This is a syntax fragment composed of the following keywords and variables: ENVironment environment-name SYStem system_name SUBsystem subsystem name TYPE type_name STAge stage_id STAge NUMber stage_number You must specify the environment, system, subsystem, type, and either the stage id or stage number. The following keywords and variables are required: ENVironment environment-name Specifies the element's environment location. SYStem system_name Specifies the element's system name association. SUBsystem subsystem name Specifies the element's subsystem association. TYPE type_name Specifies the element's type. Also, you must specify one of the following: STAge stage_id Specifies the element's stage ID location. STAge NUMber stage_number Specifies the element's stage number location. Chapter 1: Understanding the PDM WIP Merge Enhancement 23

24 Updated Merge Output Batch SCL Statements REPlace NO REPlace OPTions (Optional) Indicates on a global level, whether you want to replace like-named elements at the Merge CA Endevor SCM location or like named members on a merge to a PDS file. REPlace Replaces existing members with like-named new members. NO REPlace Does not replace existing members with like-named new members. The default. Specifies optional parameters. You can specify any of the following parameters: CREate WIP ALWAYS NEVER (Optional) Specifies whether PDM is to create a WIP file during the Build process. Specify one of the following. ALWAYS Specifies that PDM is to create a WIP file during the Build process. The default. NEVER Indicates that PDM is not to create a WIP file. WRIte STATIstics TO DDName ddname DSName dsname Specifies the location of the statistics file gathered during the Build process. specify one of the following. DDName ddname Specifies the ddname. This requires the appropriate JCL. DSName dsname Specifies the data set name. Note: See Statistical Data Control Blocks for information on statistics data set characteristics. SYNC NDVR OUTPUT Specifies that element synchronization will be performed at the target CA Endevor SCM location against the Root before performing actions to create the DV1 or DV2 change levels. This clause can only be used if the Merge Output location is in CA Endevor SCM. DELete WIP AFTer MERge Specifies that the WIP file is deleted after successful completion of the Merge process. The keywords AFTer MERge are optional. 24 Parallel Development WIP Merge Enhancement

25 Updated Merge Output Batch SCL Statements DELETE NDVR DV1 DV2 AFTer MERge Specifies that the DV1 and DV2 elements are deleted after a successful merge. This clause can only be used if the Merge Output location is in CA Endevor SCM. The keywords AFTer MERge are optional. BYPASS GENERATE PROCESSOR AFTER MERGE Specifies that the execution of the element's generate processor is bypassed after a successful merge. This clause can only be used if the Merge Output location is in CA Endevor SCM. The keywords AFTer MERge are optional. PROCESSOR GROUP NAME proc-name Specifies a processor group name that will be used to override the element's processor group name, This clause can only be used if the Merge Output location is in CA Endevor SCM. LANguage Specifies the associated language type for the members when PDM automatically merges the WIP file and the merge data set is a CA Panvalet or CA Librarian data set. For CA Panvalet valid values are: ALC ANSCOBOL AUTOCODE BAL COBOL COBOL-72 DATA FORTRAN JCL OBJECT PL/1 RPG USER180 USER780 OTHER Chapter 1: Understanding the PDM WIP Merge Enhancement 25

26 Updated Merge Output Batch SCL Statements For CA Librarian, valid values are: ASM COB DAT FOR FRG FRS GIF GOF JCL PLF PLI RPG TXT VSB DISable PERformance ENHancement Directs PDM to use external (disk) storage instead of virtual storage for Build WIP processing. Generally, this option is not specified unless necessitated by message PDM2001E. Specifying this option degrades Build WIP processing performance. Note: For a sequential file, no additional information is required for the BUILD statement, unless you want to use the STATS OFF statement. For partitioned data sets, CA Panvalet, CA Librarian files, or CA Endevor SCM locations, you must enter the appropriate MASK statements. 26 Parallel Development WIP Merge Enhancement

27 Updated Merge Output Batch SCL Statements Merge Output WIP Statement Batch SCL Syntax The Merge Output WIP statement merges the WIP data to a merge output library. You can specify whether to write statistics gathered during the merge process, delete the WIP file after completion of the merge process, and specify the language type for the members when the WIP file is merged and the merge data set is a CA Panvalet or CA Librarian data set. If the merge output option is specified and the merge output location is a CA Endevor SCM location, then the following additional options can be specified: perform element synchronization at the target CA Endevor SCM location against the Root, before performing actions to create the derivation change levels; delete the derivation elements after a successful merge; bypass the execution of the element's generate processor after a successful merge; and specify a processor group name to override the element's processor group name. The Merge Output WIP statement syntax is shown next. Chapter 1: Understanding the PDM WIP Merge Enhancement 27

28 Updated Merge Output Batch SCL Statements Merge Output Statement SCL Syntax Parameters This statement has the following parameters: MERge OUTput DDName ddname DSName dsname LOCATION2 WIP DDName ddname DSName dsname [NO REPLACE REPLACE] Specifies the the merge output file as either a ddname, dsname, or a CA Endevor SCM location. One of the following is required: DDName ddname Species a defined data set name. This requires the appropriate JCL. DSName dsname Specifies a data set name. LOCATION2 Specifies the CA Endevor SCM location. This is a syntax fragment composed of the following keywords and variables: ENVironment environment-name SYStem system_name SUBsystem subsystem name TYPE type_name STAge stage_id STAge NUMber stage_number You must specify the environment, system, subsystem, type, and either the stage id or stage number. The following keywords and variables are required: ENVironment environment-name Specifies the element's environment location. SYStem system_name Specifies the element's system name association. SUBsystem subsystem name Specifies the element's subsystem association. TYPE type_name Specifies the element's type. Also, you must specify one of the following: STAge stage_id Specifies the element's stage ID location. STAge NUMber stage_number Specifies the element's stage number location. 28 Parallel Development WIP Merge Enhancement

29 Updated Merge Output Batch SCL Statements WIP Specifies the WIP data set as one of the following: DDName ddname Species a defined data set name. This requires the appropriate JCL. DSName dsname Specifies a data set name REPlace NO REPlace OPTions (Optional) Indicates on a global level, whether you want to replace like-named elements at the Merge CA Endevor SCM location or like named members on a merge to a PDS file. REPlace Replaces existing members with like-named new members. NO REPlace Does not replace existing members with like-named new members. The default. Specifies optional parameters. You can specify any of the following parameters: SYNC NDVR OUTPUT Specifies that element synchronization will be performed at the target CA Endevor SCM location against the Root before performing actions to create the DV1 or DV2 change levels. This clause can only be used if the Merge Output location is in CA Endevor SCM. DELete WIP AFTer MERge Specifies that the WIP file is deleted after successful completion of the Merge process. The keywords AFTer MERge are optional. DELETE NDVR DV1 DV2 AFTer MERge Specifies that the DV1 and DV2 elements are deleted after a successful merge. This clause can only be used if the Merge Output location is in CA Endevor SCM. The keywords AFTer MERge are optional. BYPASS GENERATE PROCESSOR AFTer MERge Specifies that the execution of the element's generate processor is bypassed after a successful merge. This clause can only be used if the Merge Output location is in CA Endevor SCM. The keywords AFTer MERge are optional. PROCESSOR GROUP NAME proc-name Chapter 1: Understanding the PDM WIP Merge Enhancement 29

30 Updated Merge Output Batch SCL Statements Specifies a processor group name that will be used to override the element's processor group name, This clause can only be used if the Merge Output location is in CA Endevor SCM. LANguage Specifies the associated language type for the members when PDM automatically merges the WIP file and the merge data set is a CA Panvalet or CA Librarian data set. For CA Panvalet valid values are: ALC ANSCOBOL AUTOCODE BAL COBOL COBOL-72 DATA FORTRAN JCL OBJECT PL/1 RPG USER180 USER780 OTHER For CA Librarian, valid values are: ASM COB DAT FOR FRG FRS GIF GOF JCL PLF 30 Parallel Development WIP Merge Enhancement

31 Quick Edit Access to the Parallel Development Option PLI RPG TXT VSB WRIte STATIstics TO This parameter denotes the location of the statistics file gathered during the Build process. Valid values are: DDName - requires the appropriate JCL DSName (data set name) Note: See Statistical Data Control Blocks for information on statistics data set characteristics. DISable PERformance ENHancement Directs PDM to use external (disk) storage instead of virtual storage for Build WIP processing. Generally, this option is not specified unless necessitated by message PDM2001E. Specifying this option degrades Build WIP processing performance. Note: For sequential file, no additional information is required for the BUILD statement, unless you want to use the STATS OFF statement. For partitioned data sets, CA Panvalet, CA Librarian files, or CA Endevor SCM locations, you must enter the appropriate MASK statements. Quick Edit Access to the Parallel Development Option Clients who are licensed for the Quick-Edit option and the Parallel Development option can access PDM from the Quick-Edit Option panel. Provided PDM is enabled in the C1DEFLTS table, users can access PDM by selecting the PD Parallel Dev option, which now appears in the Dialog Commands section of the Quick-Edit panel. If PDM is not enabled, then the option is displayed on the panel in lower intensity than the rest of the panel and if you select this option a message is displayed indicating that the option is not available. If PDM is enabled, but you are not licensed for PDM, when you select the PD Parallel Dev option from the Quick-Edit panel, the LMP licensing rules are invoked. Chapter 1: Understanding the PDM WIP Merge Enhancement 31

32 New Messages New Messages This section details messages generated in the course of WIP merge processing, along with possible causes and corrective actions to take in error situations. PDM Messages PDM0027E PDM0028E PDM0029E reason-code ERROR ACQUIRING INITIAL STORAGE An out-of-storage condition or an internal error has occurred. If the reason code is NOSTG, increase the amount of storage available to the region. For other reason codes, contact CA Technical Support. $IMR REQUEST FAILED. $IMR ERROR MESSAGE FOLLOWS Informational message. Contact CA Technical Support if you cannot resolve the problem. DV1 and ROOT MUST BE INVENTORY LOCATIONS SINCE THE MERGE IS TO AN INVENTORY LOCATION All merging items must be CA Endevor SCM elements, if the target of the merge is an CA Endevor SCM inventory location. Merge to an output file, and then add the member into CA Endevor SCM. 32 Parallel Development WIP Merge Enhancement

33 New Messages PDM0030E DV1, DV2 AND ROOT MUST BE INVENTORY LOCATIONS SINCE THE MERGE IS TO AN INVENTORY LOCATION. All merging items must be CA Endevor SCM elements, if the target of the merge is an CA Endevor SCM Inventory location. Merge to an output file then add the member into CA Endevor SCM. PDM0031E TARGET INVENTORY TYPE DEFINITION NOT DEFINED An incorrect type name was specified on the target CA Endevor SCM location. Re-do the merge using the correct type name. PDM0166I THE WIP FILE WAS MERGED INTO DATASET dataset-name Informational message. None. PDM0166I THE WIP FILE WAS MERGED INTO INVENTORY env/stgid/sys/sbs/type Informational message. None. Chapter 1: Understanding the PDM WIP Merge Enhancement 33

34 New Messages PDM0180I THE MERGE OPERATION COMPLETED WITH A RETURN CODE OF rc Informational message. None. New Parser Messages PDM1004E PDM1047E OUTPUT DDNAME, DSNAME or Endevor location must be specified for the Merge operation. You must specify an output location on the PDM Merge statement. Specify a Merge output location and resubmit the job. Invalid Syntax. The BUILD WIP MERGE OUTPUT statement must specify DDNAME, DSNAME or Endevor location. You must specify an output location on the BUILD WIP MERGE OUTPUT statement. Specify a Merge output location and resubmit the job. 34 Parallel Development WIP Merge Enhancement

35 New Messages PDM1051E Invalid Endevor environment name on MERGE OUTPUT statement. An output CA Endevor SCM location was specified for the merge. The environment name used is invalid. Specify a correct environment name and resubmit the job. PDM1052E Invalid Endevor system name on MERGE OUTPUT statement. An output CA Endevor SCM location was specified for the merge. The system name used is invalid. Specify a correct system name and resubmit the job. PDM1053E Invalid Endevor subsystem name on MERGE OUTPUT statement. An output CA Endevor SCM location was specified for the merge. The subsystem name is invalid. Specify a correct subsystem name and resubmit the job. PDM1054E Invalid Endevor type name on MERGE OUTPUT statement. An output CA Endevor SCM location was specified for the merge. The type name is invalid. Specify a correct type name and resubmit the job. Chapter 1: Understanding the PDM WIP Merge Enhancement 35

36 New Messages PDM1055E Invalid Endevor stage on MERGE OUTPUT statement. An output CA Endevor SCM location was specified for the merge. The stage is invalid. Specify a correct stage name and resubmit the job. PDM1056E Invalid Processor Group Name. The processor group name is not defined for the type specified on the merge output CA Endevor SCM location. Specify a correct processor group name and resubmit the job. PDM1057W DELETE NDVR DV1 DV2 is ignored without the MERGE OUTPUT Endevor location statement. The DELETE NDVR DV1 DV2 clause is only applicable when the merge is to an CA Endevor SCM location. Nothing. PDM1058W SYNC NDVR OUTPUT is ignored without the MERGE OUTPUT Endevor location statement. The SYNC NDVR OUTPUT clause is only applicable when the merge is to an CA Endevor SCM location. Nothing. 36 Parallel Development WIP Merge Enhancement

37 New Messages PDM1059W BYPASS GENERATE PROCESSOR is ignored without the MERGE OUTPUT Endevor location statement. The BYPASS GENERATE PROCESSOR clause is only applicable when the merge is to an CA Endevor SCM location. Nothing. PDM1060W PROCESSOR GROUP NAME is ignored without the MERGE OUTPUT Endevor location statement. The PROCESSOR GROUP NAME clause is only applicable when the merge is to an CA Endevor SCM location. Nothing. CA Endevor SCM Messages C1G0046E THE ROOT ELEMENT IS NO LONGER VALID. ELEMENT NOT AT THE LOCATION SPECIFIED IN THE WIP FILE. After the WIP file was built, the ROOT element is no longer at the location when the WIP file was built. The PDM merge action terminates. Rebuild the WIP file then perform the PDM merge again. Chapter 1: Understanding the PDM WIP Merge Enhancement 37

38 New Messages C1G0047E ELEMENT AT TARGET. AN OUT-OF-SYNC CONDITION EXISTS BETWEEN THE ROOT ELEMENT AND THE TARGET. The element was found at the merge target and is not the same as the Root Element. Examine all locations along the map for this element. Then determine corrective action. To override the out-of-sync condition, specify the SYNC NDVR OUTPUT option. Note, this option will create a change level to bring the element back to the Root level before creating the merge change levels. C1G0048E AN OUT-OF-SYNC CONDITION EXISTS BETWEEN THE ROOT AND THE ELEMENT UP THE MAP. The element found up the map from the merge target location is not the same as the Root element. Examine all locations along the map for this element. Then determine corrective action. To override the out-of-sync condition, specify the SYNC NDVR OUTPUT option. Note, this option will first fetch the element from up the map back to the target location then it will create a change level to bring the element back to the Root level before creating the merge change levels. 38 Parallel Development WIP Merge Enhancement

39 New Messages C1G0049E ELEMENT UPDATED BEFORE THE FETCH BACK TO TARGET LOCATION COMPLETED. During the PDM merge process, an element was found up the map and it was in sync with the Root element. Before the fetch process, that element was updated. The merge process stopped, because this would have created an outof-sync condition. Examine all locations along the map for this element, and then determine the corrective action. C1G0065E THE ROOT ELEMENT IS NO LONGER VALID. IT HAS BEEN UPDATED AFTER THE WIP FILE WAS BUILT The Root element was updated after the WIP file was built. Examine all locations along the map for this element. Then determine corrective action. Chapter 1: Understanding the PDM WIP Merge Enhancement 39

40