AllFusion Endevor Change Manager

Release Summary r7 SP2

F00160-3E

This documentation and related computer software program (hereinafter referred to as the “Documentation”) is for the end user’s informational purposes only and is subject to change or withdrawal by Computer Associates International, Inc. (“CA”) at any time.

This documentation may not be copied, transferred, reproduced, disclosed or duplicated, in whole or in part, without the prior written consent of CA. This documentation is 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 this documentation for their own internal use, 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 confidentiality provisions of the license for the software are permitted to have access to such copies.

This right to print copies is limited to the period during which the 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 return to CA the reproduced copies or to certify to CA that same have been destroyed.

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 this documentation and this documentation is governed by the end user’s applicable license agreement.

The manufacturer of this documentation is Computer Associates International, Inc.

Provided with “Restricted Rights” as set forth in 48 C.F.R. Section 12.212, 48 C.F.R. Sections 52.227-19(c)(1) and (2) or DFARS Section 252.227-7013(c)(1)(ii) or applicable successor provisions.

2006 Computer Associates International, Inc.

All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

Contents iii

Contents

Chapter 1: New Features What’s New? ................................................................................. 1-1

Global Type Sequencing ................................................................... 1-2 Dynamic Approvers....................................................................... 1-3 Multiple Entry-Stage Environments......................................................... 1-4 API SCL Format Action.................................................................... 1-5 API/CSV List Destination ................................................................. 1-5 API and CSV Utility Inventory Wildcarding ................................................. 1-6 Type Definition Function .................................................................. 1-6 Package Display Panel Shows Package Shipment Information ................................. 1-7 User Data in Element Record............................................................... 1-8 Move Component List Enhancement........................................................ 1-8 Catalog Synchronization Utility ............................................................ 1-9

Chapter 2: New Features for SP1 What’s New for Release r7 SP1? ................................................................ 2-1

Simplified Email Table Maintenance ........................................................ 2-2 Certain Functions Called by Unauthorized Programs......................................... 2-4 Sync Option on Move or Transfer Actions If Target Element Nonexistent....................... 2-5 Element Registration Processor Output Type Check Option ................................... 2-6 CCID and Comments Saved Across Sessions ................................................ 2-6 ISPF View Mode Option ................................................................... 2-6 ISPF Element Master File Display........................................................... 2-6 Quick Edit................................................................................ 2-7 Processor Step Option to Override Alternate ID .............................................. 2-7 Processor Symbolic Resolution ............................................................. 2-7

iv Release Summary

Chapter 3: New Features for SP2 What’s New for Release r7 SP2? ................................................................ 3-1

Move/Generate Symbolics ................................................................. 3-1

Chapter

1 New Features

The new features and enhancements added to AllFusion® Endevor® Change Manager r7 (referred to as Endevor) are summarized in this chapter. Further details are provided in the individual guides that make up the documentation set.

What’s New? A brief description of each new feature and enhancement appears next. More detailed descriptions follow.

Global Type Sequencing–When this optional feature is enabled, API element actions (if wildcarded) and SCL element actions are executed in type sequence order defined in a sequence at the site level by the Endevor administrator.

Multiple Entry-Stage Environments–The administrator now has the option of defining an environment’s entry stage. Previously, the entry stage was always stage 1.

Dynamic Approvers- If the Dynamic Approvers option is enabled in the Endevor Options Table, then package approvers can add additional users as one–time approvers for a particular package while it is in the in-approval state.

API SCL Format Action-This new method of building requests allows your user-written program to build and pass free-form SCL statements in a new SCL style request structure. The SCL is passed to and processed by existing Endevor batch utility programs.

API/CSV List Destination-A new list package action, List Destination for API and CSV, allows you to produce a list of destinations that packages can be shipped to.

API and CSV Utility Inventory Wildcarding-You can use wildcard and placeholder characters with the Comma Separated Value (CSV) utility to extract data across inventory locations.

New Features 1–1

What’s New?

Type Definition Function-The Type Definition function is enhanced for use with the companion product AllFusion® Change Manager Enterprise Workbench, which provides a web interface to Endevor.

Package Display Panel Package Shipment Information-The Package Display panel now displays the date and destination ID of the most recent shipment record, and allows direct access to the Package Shipment Status panel for the displayed package.

User Data in Element Record-Users can read and update a new user data field in the element records of the Master Control File (MCF).

Move Component List Enhancement-This enhancement provides the ability to update the component list to reflect the new location of the output components as the result of the execution of the move processor. An additional consequence of this is that the Quick Edit commands LL and LO will now function properly after a move.

Catalog Synchronization Utility-An administrator can use this utility to update the element catalog to recover differences between the element catalog and its related MCF files.

Global Type Sequencing

A type processing sequence is used when multiple element types are processed within a single batch request. When Global Type Sequencing is enabled, element actions are processed by type sequence regardless of the inventory location of each action. API element actions (if wildcarded) and SCL element actions are executed in type sequence order defined at the site level in the Type Sequence member created by the administrator.

By default, Endevor allows you to define the relative sequence of processing for the various element types defined within a system. If your site does not choose the Global Type Sequencing option, element actions execute within your system in the same order as the types were defined to the system and stage by the administrator or as reordered by the administrator using the Type Sequence panel.

Implementing Global Type Sequencing

To implement Global Type Sequencing, the Endevor administrator creates a Type Sequence member. The order of the type records in the Type Sequence member represents the processing sequence.

1–2 Release Summary

What’s New?

The administrator can use the standard ISFP editor to create the type sequencing file. A new utility is provided to assist in building the type sequence file. The build utility is JCL member BC1JBTSE available in the site’s Endevor JCLLIB data set. This utility will build type sequence records for all types defined to a site. The administrator then edits the member, by re-ordering types and deleting types that do not require any particular processing order. After the file is in the desired order, the administrator copies the file to the site’s Type Sequence member file within the Endevor Parmlib data set. Any types not defined in the member are processed after all the defined types are processed.

A new Parmlib data set is used to contain the Type Sequence member. The administrator must allocate the data set by editing the BC1JEPRM member in the site’s Endevor JCLLIB data set, and then executing the batch job.

To define the Parmlib data set and the Type Sequence file to Endevor, the administrator adds two new parameters, PARMLIB= and TYPESEQMBR=, to the C1DEFLTS table.

Viewing the Defined Global Type Processing Sequence

You can view the contents of the site Type Sequence member on the Type Processing Sequence panel, which you can access through the Environment Options Menu or the Display Options Menu. However, the processing sequence can be changed only if the administrator edits the Type Sequence member. You can also view the contents of the Type Sequence Member, along with Parmlib information, in the Site Options report.

Dynamic Approvers

This option provides Endevor package approvers with the ability to add additional approvers to a package while it is in the in-approval state. This enhances the approval process by allowing one or more individuals to be dynamically defined as one-time approvers for a particular package. When an approver is added to a dynamic approver group, Endevor can automatically send email notification to that approver.

This feature is supported in Endevor ISPF Foreground Package processing and can be allowed or disallowed through the Endevor options table (ENCOPTBL). By default, it is disallowed. You can activate the Dynamic Approvers feature by setting DYNAMIC_APPROVERS=ON in ENCOPTBL.

New Features 1–3

What’s New?

Dynamic Approver Group

If the Dynamic Approvers option is activated in the Endevor options table, the DA-Dynamic Approvers option will appear on the foreground package ISPF panel, Review Package. When you choose the DA option, the Dynamic Approver Group panel appears. Here authorized users can specify the following for the Dynamic Approver Group:

Quorum size

This is the number of approvers from a group that must approve a package before it can be executed.

Approvers

These are the TSO user IDs of approvers who can approve or deny the package. Required approvers must approve a package before it can be executed.

Even if quorum requirements are met, a package cannot be executed until all required approvers have approved it. The Dynamic Approver group is removed from the package once it is reset.

Multiple Entry-Stage Environments

The administrator now has the option of defining an environment’s entry stage. Previously, the entry stage was always stage 1. If an entry stage is not defined, the entry stage defaults to stage 1. If you want all of the stage entry points to remain with the first stage of each environment, you do not have to make any changes.

The administrator defines the entry stage in the C1DEFLTS table using the ENTRYSTG# parameter. The ENTRYSTG# parameter can be defined as 1 or 2.

This feature allows you to add or update at the defined entry stage, either 1 or 2, but not both. This change does not affect SCL or API syntax. When Endevor processes an add or update, in foreground, batch, or through the API, the environment’s defined stage entry is used.

In releases prior to r7, the Search and Replace utility always assumed stage 1 as the entry stage to an environment. Beginning with r7, the actual environment’s entry stage is used to begin the search and, if necessary, target the entry stage for the appropriate action.

Note: Endevor never checks the existence of an element down the map. When an element is added to a stage 2-entry stage location, Endevor will not check that environment’s stage 1 non-entry stage location for an occurrence of that element.

1–4 Release Summary

What’s New?

Under Native and ESI security, an entry stage has the same access level as stage 1 actions on generate, delete, restore, move and transfer. Therefore the administrator must change security permissions as appropriate, if the entry level is defined as stage 2.

The foreground ISPF panel and the Roscoe Add/Update Elements panel no longer display the stage ID value. As with Quick Edit, the entry stage is taken from the environment’s C1DEFLTS entry stage definition.

The Member Selection List panel generated from an Add/Update (under ISPF and Roscoe) now show the entry stage ID value. The Display Stage panel also indicates which stage is the entry stage. The Stage Information panel now shows which stage is defined as the entry stage. The System Definition report includes the environment entry stage identification. The API list stage function returns the entry stage attribute field associated with the stage. The CSV utility includes the entry stage attribute field in its output.

API SCL Format Action

For this new method of building requests, instead of populating fields in unique fixed request structures, the user-written program builds and passes free-form SCL statements in a new SCL style request structure. The SCL is passed to and processed by existing Endevor batch utility programs.

This enhancement supports the SCL for all actions supported by the batch environment administration facility, the CSV utility, the batch element action facility, and the batch package facility.

One style of request structure is used to support all actions. The request structure consists of the standard 12-character header, followed by an SCL type code field and the SCL statements. One or more actions can be coded on a request; however, all the actions must all be for the same SCL type.

To execute the API SCL action, use the same JCL that you would use to execute any other API request. Special considerations apply to the API control structure.

API/CSV List Destination

A new list package action, List Destination for API and CSV, allows you to produce a list of destinations that packages can be shipped to. You can request package shipment destination information using a user-written API program or by executing the CSV utility.

New Features 1–5

What’s New?

API and CSV Utility Inventory Wildcarding

You can use wildcard and placeholder characters with the CSV utility to extract data across inventory locations.

The Endevor API and CSV utility now allow name-masking support on inventory locations. List requests are enhanced to allow wildcard with mask placeholder support on the environment, system, subsystem, type name and stage ID inventory locations. These list requests are: List Stage, List System, List Subsystem, List Type, List Data Set, List Processor Group, List Approver Group, and List Approver Group Junctions. In addition, the List Processor Group is enhanced to support mapped data extractions.

On non-explicit environment requests for these list requests, data is extracted by location order (environment/stage). On explicit environment requests, data is returned by mapped order.

Type Definition Function

The Type Definition function is enhanced for use with the companion product AllFusion Change Manager Enterprise Workbench (AllFusion CM Enterprise Workbench), which provides a web interface to Endevor.

The Endevor create and update Type Definition panels and the display Type Definition panel now include the fields DATA FORMAT and FILE EXT. These replace the fields WS HOME OPSYS and WS EXT FILE, which previously were visible only if AllFusion CM Enterprise Workbench was installed. Descriptions of the new fields follow:

DATA FORMAT

Indicates the element classification type and is used for file conversion when transferring files between Endevor and AllFusion CM Enterprise Workbench. Acceptable values are:

B

Binary. Element exchanged between Endevor and AllFusion CM Enterprise Workbench is not modified. This applies to both directions.

T

Text. Character set conversion is applied to element.

blank

AllFusion CM Enterprise Workbench is not installed or feature does not apply to this type. If blank, the AllFusion CM Enterprise Workbench assumes a value of B.

1–6 Release Summary

What’s New?

FILE EXT

Indicates the 0- to 8-character file extension to be used by the AllFusion CM Enterprise Workbench for elements of this type. Valid characters supported in this field are: 0-9, a-z, A-Z and all blanks. Trailing blanks are supported; embedded blanks are not supported.

The batch Define Type SCL syntax is similarly changed to include the following two clauses:

DATA FORMAT IS BINary/TEXt

This replaces the previous clause HOMe OPErating System IS WORkstation/MVS.

FILe EXTension IS file-extention

This replaces the previous clause WORKstation FILe EXTension IS file-extention.

The API List Type function is similarly changed as follows:

ALTYP_RS_DATAFMT

Format of this type of data with the following valid 1-character values: B, for Binary; T, for text; or blank, for not specified. This replaces the previous field ALTYP_RS_HOOP, which defined the home operating system as either M, for z/OS or OS/390, or W, for Workstation.

ALTYP_RS_FILEEXT

The name of this field is not changed. The value of this field is a 0- to 8-character file extension associated with this type of data. Type value can consist of the characters: a-z, A-Z, 0-9 or blanks. Trailing blanks are supported; embedded blanks are not supported.

Package Display Panel Shows Package Shipment Information

The Package Display panel now displays the date and destination ID of the most recent shipment record, and allows direct access to the Package Shipment Status panel for the displayed package.

This enhancement adds two new display only fields to the Package Display panel, LAST SHIPPED and DEST-ID. If applicable, these fields will contain the date, time and destination ID of the most current shipment record for the displayed package. This enhancement also adds a new option to the Package Display panel, SH - Display Ship Status Information. This option will only be available if ship records exist for the displayed package. Selecting this option will bring the user to the Package Shipment Status panel for the selected package.

New Features 1–7

What’s New?

User Data in Element Record

This change allows users to read and update a user data field in the element records of the MCF. In addition, a symbolic has been created that enables users to reference the field in processors and use sub-stringing.

Users can store up to 80 bytes of user data with the element records, by means of an exit 2. This data can be used in processors with the new symbolic &C1EUDATA.

Move Component List Enhancement

This enhancement provides the ability to update the component list to reflect the location of the output components as the result of the move processor. The move processor utility BC1PMVCL now can dynamically replace old Endevor output components with the new output components at the end of the move processor execution. An additional consequence is that the Quick Edit commands LL and LO will now function properly after a move.

A move processor typically copies the outputs of the generate processor from their libraries to the next stage’s output libraries. Once the outputs have been copied, the move processor typically also copies the existing component list to the new inventory area. The utility to move component lists is a pseudo processor program called BC1PMVCL.

When using BC1PMVCL, the existing component data does not get updated so all the input and output components in the component list reflect the data sets used at generate time.

If, in a move processor, MONITOR=COMPONENTS is coded on the output files, and BC1PMVCL is part of the processor (as the last step), Endevor will now:

Remove existing output components from component list

Add new output components to component list

Will not change input components

Technically, the BC1PMVCL does not have to be the last step; however, it must execute after all monitored components.

If components have been monitored in a move processor (prior to the execution of BC1PMVCL), then all of the gathered output components will be used to replace all of the existing output components in the existing component list. These gathered output components are subsequently removed from the storage lists in which they were collected in order to avoid subsequent update at the end of the processor execution.

1–8 Release Summary

What’s New?

New Features 1–9

The feature will cause output component lists to be generated by a move if a move processor has collected new output components prior to the execution of BC1PMVCL. The output components will replace all of the output in the existing components list.

Also, Quick-Edit uses the output components of the component lists for the commands LL and LO. Previously when the outputs had been moved, LL and LO were no longer usable. This enhancement makes the LL and LO usable.

Catalog Synchronization Utility

The Catalog Synchronization Utility updates the element catalog to recover differences between the element catalog and its related MCF files. In addition to the update mode, you can use the validate mode to simply report the differences without changing the catalog.

The utility synchronizes the element catalog with the MCF element records in two phases.

The first phase validates MCF records against the catalog. In update mode, a catalog segment is created for any MCF record found missing from the catalog. A catalog segment is updated with MCF element data when the associated catalog data is found to be different.

The second phase validates the catalog to the MCF. In update mode, all segments which do not have a MCF element record are removed from the catalog.

In both phases, processing is done by environment. You can specify which environments the utility will process, or allow the environment selection to default to all environments defined in the C1DEFLTS table.

To execute the utility, use the JCL member BC1JCSYN which is provided in the Endevor JCLLIB data set. The utility generates the Endevor MCF Catalog Synchronization Utility Log.

Chapter

2 New Features for SP1

The new features and enhancements added to AllFusion® Endevor® Change Manager r7 SP1 (referred to as Endevor) are summarized in this chapter. Further details are provided in the individual guides that make up the documentation set.

What’s New for Release r7 SP1? A brief description of each new feature and enhancement appears next. More detailed descriptions follow.

Simplified Email Notification–A new optional parameter in the ESMTPTBL table (which defines email addresses for user IDs) constructs default email addresses for user IDs that are not explicitly listed in ESMTPTBL. Additional enhancements include the ability to query the ESMTPTBL, an easy-to-use interface utility that allows you to write simple email programs, improved readability of override signout emails, the suppression of override signout emails, and the ability to modify email FROM data.

Unauthorized Calling Programs–This change allows certain Endevor functions to be executed when these functions are called from a non-APF-authorized program.

Move or Transfer Action Sync Level–The SYNC=Y option on a move or transfer action can now create a sync level at the target when the following conditions exist: 1) the element does not exist at the target and 2) the source element is out of sync with the element found up the map. You can turn off this default behavior by activating the optional feature DO_NOT_SYNC_AT_TARGET=ON in ENCOPTBL.

Element Registration Processor Output Type Check–Endevor can check across systems for the existence of an element that has the same name and processor output type, but a different element type. To turn on this behavior, you must activate ELM_REG_CHK_OUTPTYPE_ACROSS_SYSTEMS=ON in the optional features table (ENCOPTBL).

New Features for SP1 2–1

What’s New for Release r7 SP1?

CCIDs and Comments Across Sessions–You can activate an optional feature in ENCOPTBL to turn off the default behavior that remembers CCIDs and comments across sessions.

ISPF View Mode Option–The new ISPF view mode option is available on the user defaults panel.

ISPF Element Master File Display–The master file information for a selected element can be displayed from the element summary selection list panels.

Quick Edit–The CCID/COMMAND prompt panel now displays the element name.

Override Alternate ID in Processor Step- A new processor step parameter, ALTID=N, enables you to disable the Endevor alternate user ID during execution of a processor step.

Long Name Processor Symbolics- The resolution of processor symbolics is changed, so that when a processor defines a symbolic name, long symbolic names are accurately resolved.

Simplified Email Table Maintenance

This enhancement changes how Endevor treats user IDs that are not explicitly listed in the mainframe ID and email ID table ESMTPTBL. Instead of bypassing unlisted IDs, Endevor now tries to send an email to them using an address constructed with the Endevor user ID suffixed with the default domain.

Previously, the administrator had to maintain ESMTPBL to insert or remove the $ESMTP macro defining each individual user's MFID and EMAILID. To avoid this, a new default $ESMTP parameter, DFTID, is added to ESMTPTBL.

To enable this feature, only one value is permitted (DFTID=USERID). If the value is omitted, or coded as null (DFTID=), then Endevor continues to work as before.

Upward Compatibility

Your existing exit 7 email programs (XIT7MAIL) and signout override emails will continue to work without modification. However, to utilize this enhancement, you must reassemble your existing programs. The sample XIT7MAIL program provided with this service pack includes the new DFTID optional parameter for the ESMTPTBL.

2–2 Release Summary

What’s New for Release r7 SP1?

Valid Email Address or Alias

Of course, any email address identified by the new DFTID parameter still needs to be a valid SMTP address. That is, your Endevor user IDs must have corresponding email addresses or aliases.

For many organizations this is already the case; their mainframe user IDs, network and email IDs are all synchronized. Even if this is not already true, it is simple to set up an email alias on your email server, where all the information relating to a user's alternate email addresses is already defined (for example, SMTP, X500, alternate spellings, and so on).

For example, Peter Smith might have PETER01 as his TSO Userid and an alias Peter01@yourco.com, which points to his default email address Peter.Smith@yourco.com.

Additional Enhancements to Email Notification

To improve performance, whether you are using the old exit or the new exit, ESMTPTBL is loaded only once (at Endevor session start-up) and deleted at Endevor session shutdown.

There are two new SMTP-specific parameters, which your email exit program passes to the control block. The NOTMSGLP parameter improves the readability of override signout emails by allowing multiline variable records in emails. The NOTFROM parameter allows you to override the default FROM USER to specify a FROM USER for emails that are sent.

You can use SCANRUTN to query the contents of the mainframe ID and user ID table ESMTPTBL to determine if it defines an email address for a specific user ID. The SCANRUTN source code can be found in member XIT7MAIL of the iprfx.iqual.SOURCE library. The SCANRUTN return code tells you if it found the user ID. If the user ID was not found, the return indicates if the table includes the DFTID=USERID parameter, which sends emails to undefined user IDs.

It is now possible to suppress email notification for some or all cases when override signout is used. You can suppress the sending of override signout emails by activating SUPPRESS_OVERRIDE_SIGNOUT EMAILS in the optional features table ENCOPTBL. You can suppress all override signout emails for all actions or for the following types of actions: ADD, ARCHIVE, DELETE, GENERATE, SIGNIN, TRANSFER, RETRIEVE, or UPDATE.

New Features for SP1 2–3

What’s New for Release r7 SP1?

A new interface program, BC1MLIF, allows you to write simple email programs to be called at exit points or in processors. Your email program can call BC1MLIF with an easy to use parameter list. BC1PMLIF formats the required internal control blocks and calls the existing Endevor email interface modules. BC1PMLIF gets the email address from ESMTPTBL, formats the message, and sends it to the email server. To use this utility, you do not need an in-depth knowledge of the $NOTIFY block or the ESMTP table lookup. A sample COBOL email program, CALLMLIF, is provided in the installation SOURCE library.

Certain Functions Called by Unauthorized Programs

This change allows certain Endevor functions to be executed when these functions are called from a non-APF-authorized program. Users executing the non-authorized program must have the requisite security access to the Endevor data sets for the function requested. The caller’s security profile must have sufficient eTrust™ Top Secret Security, eTrust™ ACF2 Security, or RACF, access to the Endevor control files (catalog, master, package, base, delta), because the Endevor alternate ID facility is not available when running in an unauthorized mode.

Programs that call the following Endevor functions are not required to reside in an authorized library: Comma Separated Value (CSV) utility, BC1PCSVO; Parallel Development Manager (PDM), BC1G1000; the Report utility, C1BR1000; and the Footprint Extract utility, BC1PFOOT. Your program that invokes the API is not required to reside in an authorized library in order to execute the following API functions:

■ All the LIST inventory functions:

- List Element

- List Environment

- List Site

- List Stage

- List Subsystem

- List System

- List Type

■ All the LIST package functions:

- List Package Action Summary

- List Destination API

- List Package Approvers

- List Package Backout Information

- List Package Cast Report

2–4 Release Summary

What’s New for Release r7 SP1?

- List Package Correlation

- List Package Header

- List Package SCL

■ Extract Element and Component Request

■ List Directory

■ Print Element

■ Print Member

The ability to execute read-only actions such as PRINT, LIST, and so on has not been made available, because that capability is provided already through the API interface and partially through the CSV utility. Endevor actions may require APF authorization to create SMF records, authorize functions related to processor execution, etc.

Sync Option on Move or Transfer Actions If Target Element Nonexistent

This enhancement affects the behavior of the SYNC option on a move or transfer action, when the element is not present at the target location and is out of sync with the element located up the map.

In cases where there is no element at the target, Endevor now searches up the map for the element. If the element found up the map is not in sync with the base level at the source location, Endevor copies the current level of the element back to the target and creates a sync level at the target. The sync level reflects the differences between the base level at the source location and the current level of the element copied from up the map. Then the move or transfer proceeds and appends the source element delta levels to the target sync level.

If the element found up the map is in sync with the base level at the source location, Endevor copies the element from the source location and does not create a sync level.

Previously, when the SYNC=Y option was specified and the element did not exist at the target of the move, Endevor searched up the map to identify a sync condition, but did not create a sync level, instead it simply promoted the element to the target and issued an appropriate sync warning message.

To disable the new functionality for SYNC=Y and cause Endevor to behave as before, you can activate the option DO_NOT_SYNC_AT_TARGET=ON in the optional features table ENCOPTBL.

New Features for SP1 2–5

What’s New for Release r7 SP1?

Element Registration Processor Output Type Check Option

A new option allows processor output type checking across systems. When you define a system, you can select the element registration option duplicate processor output type checking. Using the System Definition panel, if you specified Y in the Duplicate Proc O/P Type Check field, then Endevor checks within the same system for elements that have the same name and processor output type, but are different element types. Now the check will also be performed across different (non-mapped) systems if the optional feature ELM_REG_CHK_OUTPTYPE_ACROSS_SYSTEMS=ON is activated in the optional features table (ENCOPTBL).

CCID and Comments Saved Across Sessions

As delivered, the CCID and COMMENT field values are remembered across sessions. If your site decides to turn this option off, edit the Optional Features Table source, ENCOPTBL, and activate the DO_NOT_SAVE_CCIDCOMM=ON option. This will cause Endevor to not remember CCID and COMMENT fields across sessions. However, the CCID and COMMENT values will still be carried from panel to panel within a session. (This option applies to Quick Edit, Endevor foreground, batch action, and package processing.)

This new option DO_NOT_SAVE_CCIDCOMM, replaces the SAVE_CCIDCOMM option. Previously, if you activated the SAVE-CCIDCOMM option in ENCOPTBL, the CCID and COMMENT values used during the previous session of Quick Edit were saved for the next user session.

ISPF View Mode Option

The User Defaults panel and the Quick Edit Dialog Defaults panel now include a field that allows you to specify whether you want to use view mode or browse mode. The sample Default Configuration Table ENDICNFG, provided with Endevor, sets the default to browse (BROWSE_VIEW_MODE=B,). Previously, there was no option to choose view mode.

ISPF Element Master File Display

The master file information for a selected element can be displayed from the summary of levels selection list panels. To display the master file information, enter the new option M next to the change level line in any summary of levels selection list panel.

2–6 Release Summary

What’s New for Release r7 SP1?

Quick Edit

The CCID/COMMAND prompt panel now displays the element name.

Processor Step Option to Override Alternate ID

If an Endevor alternate ID is defined in the C1DEFLTS table, then a processor step executes under the security context of the Endevor alternate ID. However, you can override this behavior by specifying ALTID=N on the EXEC statement of the processor. If ALTID=N is specified, then the processor step runs under the security context of the user ID associated with the job.

If ALTID=N is specified, then Endevor does not use the alternate user ID during execution of that processor step, the value of the INTRDR_ALTID option in the Endevor Options Table is ignored, and any jobs submitted to the internal reader run under the security context of the user ID.

Note: If you are using eTrust Top Secret Security and you want Endevor to submit JOBs to the INTRDR using the credentials of the Endevor user ID, you must set the eTrust Top Secret global option JES(VERIFY). If the JES(VERIFY) option is not set, eTrust Top Secret attempts to build the USER= JOBCARD parameter with the Endevor Alternate ID as the USER parameter value. This causes the submitted JOB to fail, because users typically do not have the authority to specify the Endevor Alternate ID on their JOBCARD.

Processor Symbolic Resolution

The logic used to resolve processor symbolic variables has been improved so that two symbolic variables that have different lengths and begin with the same character text are resolved correctly.

Prior to the correction, the first symbolic variable found that matched the processor override was substituted with the overridden value. The name-match logic incorrectly used the length of the overridden symbolic value rather than the length of the processor symbolic variable. Because of this, a processor symbolic variable named “&PROCSYMBOLIC1” would be resolved with the value associated with the shorter symbolic variable name of “PROCSYM.”

This correction could affect the way symbolic variables are resolved in your processors. To determine if you will be affected by this change:

1. Execute the CSV utility program to extract your processor symbolic variable overrides (wildcarding environment, stage, system and type names), with “OPTION NOCSV SEARCH” specified.

2. Use ISPF EDIT (or VIEW) to see the data.

New Features for SP1 2–7

What’s New for Release r7 SP1?

2–8 Release Summary

3. Issue the ISPF SORT 175 182 command to organize the data in symbolic variable name sequence.

4. Issue the ISPF FIND P’^’ 175 command to find the first symbolic variable.

5. View and scroll down the list of symbolic variable names, looking for variable names of different lengths that begin with the same character strings.

New Features for SP2 3–1

Chapter

3 New Features for SP2

The feature enhancements added to AllFusion® Endevor® Change Manager r7 SP2 are summarized in this chapter.

What’s New for Release r7 SP2? A brief description of the new feature enhancements appears next.

Move/Generate Symbolics– This feature enables generate processors to utilize the source symbolics.

Additional Feature Enhancements– For details regarding additional feature enhancements, defined as modifications to product functionality or behavior, introduced in AllFusion Endevor r7 SP2, see the informational APAR reserved in STAR (QI76384) and attached to the problem record 4742 and solution record 377.

Move/Generate Symbolics

Many times it is necessary to use a generate processor for a move action. This enhancement makes the same C1 source symbolics available to the generate processor as are available to the move processor when the generate action is the result of a move or transfer. Previously, C1 source symbolics were only available to move processors, which meant that a generate processor used for a move could not reference the source stage name, environment, and so on, of the move. This change does not affect the way any other generate actions work. For example, neither a generate in place nor a generate with copyback are affected by this change.

For details, see Extended Processors in the chapter “Writing Processors” in the AllFusion Endevor Change Manager r7 SP2 Extended Processors Guide.