Introduction › How Type Sequence Processing Works › Process Flow

Process Flow

When you submit your SCL requests, CA Endevor SCM follows a specific processing flow to execute the actions.

Process Flow: Global Type Sequencing Not Enabled

When Global Type Sequencing is not enabled at your site, the process flow is as follows:

1. CA Endevor SCM first parses, or validates, the SCL syntax, assigning a statement number to each SCL statement coded.

   A Syntax Report is produced, echoing the SCL statements entered and flagging any syntax errors.

2. When all requests have been validated, CA Endevor SCM checks for errors. If errors exist within the syntax, processing is terminated.

   If no errors exist, processing continues.

3. CA Endevor SCM checks whether any statements have been entered with an archive file designated as the FROM location. All such actions are performed first, as they are encountered.

   For example, assume you code both an ARCHIVE action and a RESTORE action. If you want CA Endevor SCM to perform the RESTORE action before the ARCHIVE action, designate an archive file as the RESTORE action's FROM location. If you want to perform the ARCHIVE action before the RESTORE action, however, you need to execute SCL twice-first to perform the ARCHIVE action and then to perform the RESTORE action.

   For Elements that are restored, transferred, copied, or listed from an archive file, processing occurs as follows:

   1. The Element(s) is restored (or transferred, copied, or listed), but it is not generated at this time.
   2. CA Endevor SCM continues processing the remaining actions, as described in the following steps (beginning with Step 4).
4. CA Endevor SCM expands any name-mask that may have been entered for system, subsystem, stage, and type.
   • Beginning with the first SCL syntax request, CA Endevor SCM checks for use of the name-mask with the system name.

     If a name-mask has not been used with the system name in the first SCL syntax request, CA Endevor SCM checks for the name-mask in the next syntax request. If no name-mask is found and the system name is the same, CA Endevor SCM checks the system name of the third syntax request. This procedure continues until a system name is found with a name-mask or a new system name is encountered, or until all syntax requests have been searched.

     When one of the three situations mentioned above occurs, CA Endevor SCM returns to the first syntax request and checks for a name-mask with the type name.

     Again, if no name-mask is found, the second syntax request is checked, and so on until a type name is found with a name-mask or a new type name is encountered, or until all syntax requests have been checked. This procedure is repeated for stage and subsystem.

     CA Endevor SCM examines each clause (SYSTEM and STAGE) in the syntax request until a non-match is found. Once a difference is encountered, CA Endevor SCM executes the previous syntax requests-.in type sequence order (see Step 5). Processing then continues accordingly with the next syntax request.

   • If a name-mask has been used with the system name in the first syntax request, CA Endevor SCM expands the entries. Then, within each system of the first syntax request, any remaining name-masks are expanded (in the appropriate order).
5. CA Endevor SCM sorts the types based on type sequence order.

   Processing involves syntax requests for stage within a particular system. Type processing sequence conventions still apply, however. If a name-mask is not used with type, the syntax requests themselves are sorted in type sequence order.

   If a name-mask is used with type, actions across all syntax requests are executed in type sequence order. So, depending on the Elements indicated (see Step 6 below), it is not unusual to see an ADD from syntax #2, followed by a GENERATE from syntax #3, followed by an ADD from syntax #2. When all information has been generated for the first (set of matching) syntax request(s), CA Endevor SCM executes the next (set of) syntax request(s).

6. Once all types have been defined, CA Endevor SCM checks the stage identifier involved within the first type. If a name-mask has been used with the stage identifier, CA Endevor SCM expands the entries.

   Still within the first type, and within the first stage identified, CA Endevor SCM expands any subsystem name-masks that have been coded.

7. CA Endevor SCM expands the Element name-mask if it exists (Element is the Element-name entered in the first [action] clause of the statement) and executes each action within the system, including those actions previously performed but not generated (because they were from an archive file). Remember: all SCL statements are executed in type sequence order.
8. CA Endevor SCM assigns each action an action number. As all actions are processed, an Execution Report is produced. The Execution Report fully expands the action request, providing the complete system name, subsystem name, type, and stage for the Element being processed. In addition, the report lists all options in effect for the action. CA Endevor SCM also produces a Summary Report. This report provides one line of summary information for each action performed.