Performing User Tasks › How Adding/Updating a Member from Natural or Predict Works

How Adding/Updating a Member from Natural or Predict Works

When you allow CA Endevor SCM to control an object from Natural or Predict using the Add/Update Elements action, CA Endevor SCM performs the following actions and causes these effects:

1. Verifies that the element is signed out to you and does not exist in the entry stage.
2. Searches beyond the entry stage for an element with the same name.

   Note: Every stage in the mapped route is searched for a match. If the element is found in a stage in the map, CA Endevor SCM copies the current version of the element to the target entry stage, along with the last processor group name used for the element.

3. If you code the new version option, the element is not copied back to the entry stage. CA Endevor SCM assigns the version number you enter.

   Important! If CA Endevor SCM finds the element in a stage that is not included in the map, you will see a warning message in the API Message report. The search continues for an element in a stage that is included in the map.

4. Compares the object being added with the entry stage base. If the element is not found along the map, the element is created in the entry stage with a version number of 01 and base level of 00 (zero).
5. If CA Endevor SCM built an entry stage base, the object being added is compared to that base, and builds a new level with any changes. If no changes are detected, you will see a warning message in the API Message report.
6. Updates the Master Control File (MCF).

   Important! The value specified for Signout Upon Fetch (the SOFETCH parameter) in the CA Endevor SCM Defaults Table (C1DEFLTS) effects how the MCF will be updated for the element copied back (fetched). If Signout Upon Fetch is in effect, the element will be signed out to you unless it is already signed out to someone else. If Signout Upon Fetch is not in effect, the element will not be signed out to you.

7. Continues executing the action based on the value in the GENERATE ELEMENT option. If this option is set to N, CA Endevor SCM does not generate the element. If this option is set to Y, CA Endevor SCM performs the following actions:
   • Determines which processor group to use and executes the generate processor in that group (if one has been specified). After the generate processor has been run for the element, CA Endevor SCM updates the processor information in the Master Control File.
   • For Natural or Predict elements, the generate processor loads a Natural or Predict object into the FUSER/Library or FDIC that corresponds to the current CA Endevor SCM stage and subsystem. In the case of Natural programming objects, the generate processor also executes the CATALL utility to generate Natural executables.
   • The CATALL execution output is written to the list library defined for that subsystem.