COBOL - Endevor - Update Element - www.cadcobol.com.br



Desenvolvido por DORNELLES Carlos Alberto - Analista de Sistemas - Brasília DF. - cad_cobol@hotmail.com

Endevor - Update Element

Updating a Member Using the Update Elements Action

To control and manage a member when an element with the same name already exists in the target entry stage, you use the Update Elements action (available in foreground, batch, and in packages).

This section contains information for performing this development task in the foreground only.

Note: For more information about how to perform this element action in batch, see the SCL Reference Guide.
For more information about how to perform this element action using packages, see the Packages Guide.
The Add, Move, Generate, and Signin actions can be performed from the Quick-Edit Option panel, if the CA Endevor SCM Quick Edit option is enabled at your site.
For more information about Quick-Edit, see the Quick Edit Option User Guide.

How Updating a Member Works

When you allow the product to control a member when an element with the same name already exists in the target entry stage using the Update Elements action, the product performs the following actions and causes these effects:

  • Verifies that the element currently exists in the entry stage. If the element does not exist in the entry stage, the update fails.

  • Determines whether the element is signed out to you.
    If the element is signed out to someone else, you must set the OVERRIDE SIGNOUT option to Y to update the element.

    Note: If the element is in the entry stage, but it is identical to the update source element, you get a warning message saying "NO CHANGES," and no level is created.


  • Stores update changes in the delta library as a new level.

  • Continues based on the value in the GENERATE ELEMENT option.
    If this option is set to N, the product does not generate the element.
    If this option is set to Y, the product performs the following actions:

    • Reads the type definition for a Source Output Library specification, and then writes a copy of the current level of the element to that library.
      If the EXPAND INCLUDES option is set to Y, the product expands INCLUDE statements in the source.

    • Determines which processor group to use, and then executes the generate processor in that group (if one has been specified).

    • After the generate processor has been run for the element, updates the information in the Master Control File (MCF).

  • Updates the Master Control File after the element is successfully updated.
    If the DELETE INPUT SOURCE option is set to Y, the product deletes the member indicated in the FROM library.

Updating a Member and Trailing Blanks in Input Files

When the product compares an input file against the source for an existing element that will be updated, trailing blanks (that is, blanks that occur in a data record after the last non-blank character) are ignored.
This happens for comparison reasons when the base file is a fixed format, but the input file is variable.
Variable includes not only MVS RECFM=V or VB files, but also HFS files and files sent from CA CM Enterprise Workbench.

Example: Use Trailing Blanks in Each Record

In this example, there is a small file that has trailing blanks in each record.
In general, you will see trailing blanks in text records when the record size is fixed.
Trailing blanks affect the compare logic performed by UPDATE ELEMENT logic in the product when it compares an input file to the existing element source.

'123 '
'456 '
'X '

Example: Use One-record Element, Base File is Fixed

In this example, you have a one-record element in which the base file is a fixed record format with a record length of 80.
The element data is a single record that contains "ABC" followed by 77 trailing blanks.
You try to update this element with an input file with a record length of three with the content of "ABC."
In this example, the product does not consider that the file has changed and does not create a new delta level.

Example: Use an Element on a Base File, Record Format is Variable

In this example, you have an element on a base file with the record format of variable.
The element record is "ABC " and has one trailing blank.
You try to update this element with an input file whose record is "ABC " (contains two trailing blanks).
In this example, the product considers that the element has changed and creates a new delta level.

How Updating a Member Affects the Signout Status

Your site administrator can enable a signout capability on a system-by-system basis.
When you allow the product to control a member when an element with the same name already exists in the target entry stage using the Update Elements action, the product performs the following actions and causes these effects:

  • If the element exists up the map, a fetch is performed.
    • If your site administrator has enabled Signout Upon Fetch, there is no change to the signout status for the target element.
    • If your site administrator has not enabled Signout Upon Fetch, there is no change in the signout status for the target element.

      Note: For more information about Signout Upon Fetch, see the Administration Guide.

How Updating a Member Affects CCIDs and Comments

When you allow the product to control a member when an element with the same name already exists in the target entry stage using the Update Elements action, you can enter a CCID and comment.
When you enter a CCID and comment, the product sets the following options:

  • Current Source CCID/Comment (if changed)
  • Generate CCID/Comment (if generated)
  • Last Action CCID/Comment
  • Source Delta CCID/Comment (if changed)
  • Component Delta CCID/Comment (if generate creates a delta)

Note: If you set the GENERATE ELEMENT option to N, the Update Elements action does not set the generate or component delta CCIDs and

Update a Member

To control and manage a member when an element with the same name already exists in the target entry stage, you use the Update Elements action.

Follow the below steps to update an element into endevor entry stage.

  1. Start the product using the instructions provided by your site administrator.

    The Primary Options panel appears.

  2. Enter 2 (Foreground) and press Enter.

    The Foreground Options menu appears.

  3. Enter 2 (Add/Update) and press Enter.

    The Add/Update Elements panel appears.

    Note: For more information about a field or option on the panel, press PF1.

    Note: For more information about adding or updating an element with the Autogen option, see How Generating Elements with Autogen Works.

  4. Choose one of the following steps.

    1. To update a member, enter the information for the action, enter U in the Option field, and press Enter.

    2. To update a member from the source library, enter the information for the action, leave the Option field blank and press Enter.

    The Member Selection List appears. This list appears when the source data set is a library, you leave the Option field blank, the DISPLAY LIST option is set to Y, and when both the ELEMENT and MEMBER options are blank or have a name mask.
    The ISPF Locate command is supported on Member Selection lists.

  5. (Optional) If the Member Selection List appears, enter U to the left of each member you want to update and press Enter.

    The members are updated and you return to the Add/Update Elements panel.
    You can browse the listing data set for more information about each selected member.


© Copyright CA Technologies.