Processing Element Actions › The Update Statement › Update Statement Syntax

Update Statement Syntax

├── UPDate ELEment ─ element-name ─┬──────────────────────────────┬─────────►
                                   └─┬─ THRough ─┬─ element-name ─┘
                                     └─ THRu  ───┘
 ►─ FROm ─┬─┬─ FILe ───┬─ dd-name ──────────────────────────────┬───────────►
         │ └─ DDName ─┘                                        │
         ├─ DSName ─ dataset-name ─┬─────────────────────────┬─┤
         │                         └─ MEMber ─ member-name ──┘ │
         └─ PATH ─ usspath ─ HFSFILE ─ filename ───────────────┘
 ►──TO ─ ENVironment ─ env-name ─ SYStem ─ sys-name ────────────────────────►
 ►─ SUBsystem ─ subsys-name ─ TYPe ─ type-name ─────────────────────────────►
 ►─┬──────────────────────────────────────────────────────────────────────┬─►
   └─ OPTion ─ ¤ ─┬────────────────────────────────────────────────┬─ ¤ ──┘
                  ├─ CCId ─ ccid ──────────────────────────────────┤
                  ├─ COMment ─ comment ────────────────────────────┤
                  ├─ DELete input source ──────────────────────────┤
                  ├─ OVErride SIGNOut ─────────────────────────────┤
                  ├─┬─ BYPass GENerate PROcessor ────────────────┬─┤
                  │ └─ PROcessor GROup ─┬─ EQual ─┬─ group name ─┘ │
                  │                     └─ = ─────┘                │
                  └─ AUTogen ─┬───────────────────┬────────────────┘
                              ├─ SPAN NONe ───────┤
                              ├─ SPAN ALL ────────┤
                              ├─ SPAN SYStems ────┤
                              └─ SPAN SUBsystems ─┘
 ►─ .──────────────────────────────────────────────────────────────────────►◄

UPDATE ELEMENT element-name

Indicates the element(s) to be updated. Code the required syntax and enter the appropriate element name; up to 255 characters are allowed. In addition, you can use a name mask with the element name.

THROUGH (THRU) element-name

Indicates that a range of elements should be updated, beginning with the element coded in the UPDATE ELEMENT statement, up to and including the element specified in this statement. You can use a name mask with the element name. If you use the THROUGH clause, however, you cannot enter a member name (in the FROM clause).

Note: If you are working with a sequential file, the THROUGH clause is ignored.

FROM FILE (DDNAME) dd-name

DSNAME dataset-name

MEMBER member-name

PATH usspath

HFSFILE filename

The FROM clause indicates the location of the element being updated. Endevor uses both the FROM clause in an action and any preceding SET FROM clause to determine the "from" criteria for that action.

• A FROM clause in an action overrides values in a SET FROM clause that precedes the action.
• If the SET FROM clause contains values that are not included in the FROM clause, Endevor uses these values.

For more information, see the description of the SET FROM statement, in Chapter 3, "Set Clear, and EOF Statements."

You must enter a FILE, DDNAME, DSNAME, or PATH in conjunction with the HFSFILE (enter one and only one). If you enter a FILE or DDNAME, be sure the appropriate JCL is coded. Enter a member name (up to 255 characters) if it differs from the element name specified in the UPDATE ELEMENT clause; you can use a name mask with this entry. If you do not enter a member name, Endevor assumes that the element name and member name are the same.

• You can enter a member name only if a full element name has been coded in the UPDATE ELEMENT clause; that is, if you have not used a name mask.
• If you want to code a member name, you must do so in the UPDATE statement; the SET FROM clause does not contain a member name entry. If you do enter a member name, you cannot enter a THROUGH clause.
• If you are working with a sequential file, the MEMBER clause is ignored

PATH

The USS directory where the element source file resides.

HFSFILE

The file in the USS directory that you want to put under the control of CA Endevor SCM.

TO ENVIRONMENT env-name

SYSTEM sys-name

SUBSYSTEM subsys-name

TYPE type-name

The TO clause indicates where the element is being updated. CA Endevor SCM uses both the TO clause in an action and any preceding SET TO clause to determine the "to" criteria for that action.

• A TO clause in an action overrides values in a SET TO clause that precedes the action.
• If the SET TO clause contains values that are not included in the TO clause, CA Endevor SCM uses these values.

You must specify an environment, system, subsystem, and type. Remember that you cannot use a name mask with a TO field location.

OPTIONS

OPTIONS clauses allow you to further specify action requests.

CCID ccid COMMENT comment

You can enter a one- to twelve-character CCID, a one- to forty-character comment. CCIDs, or both. CCIDs and comments may be required. If you do not provide a required CCID or comment, the UPDATE action fails. When you specify a CCID or comment in an UPDATE action for an existing element, CA Endevor SCM uses this CCID or comment to:

• Set the source and source delta CCID or COMMENT fields, if the CCID or comment has changed.
• Set the generate CCID or COMMENT fields, if the generate processor is run.
• Set the component list delta CCID or COMMENT fields, if running the generate processor creates a change.
• Set the last action CCID or COMMENT fields.

CA Endevor SCM also clears the entry stage retrieve CCID or COMMENT fields when you update an element. If you use the BYPASS GENERATE PROCESSOR, the UPDATE action will not set the generate or component delta CCID or COMMENT fields.

DELETE INPUT SOURCE

After an element has been successfully updated in CA Endevor SCM, you can use this option to remove the member from the library in which it originated. If you input a sequential file, this option deletes that file.

OVERRIDE SIGNOUT

If the element has been signed out to a person other than yourself, you must code this option in order to perform this action. Use OVERRIDE SIGNOUT with caution to avoid regressing changes made by another user.

BYPASS GENERATE PROCESSOR

Use this option if you do not want the generate processor executed for the element. Otherwise, CA Endevor SCM looks for and executes the generate processor for the element when it is updated.

PROCESSOR GROUP group name

Use this option to specify a predefined named group of processors. If you do not specify a processor group, CA Endevor SCM defaults to the processor group last used for this element.

AUTOGEN | SPAN NONE| SPAN ALL | SPAN SYSTEMS | SPAN SUBSYSTEMS

Applicable for Add, Update, and Generate actions in batch requests. This option cannot be used in packages and the option does not work if Bypass Generate Processor is set. The Global Type Sequencing batch processing method must be enabled. Autogen only acts on components whose Types are listed in the Global Type Sequencing table. If the component's Type is not listed in the Global Type Sequencing table, the Autogen request is ignored. In addition, your site must have purchased and activated the CA Endevor Automated Configuration. Autogen can be specified alone or with various Span keyword options. "Autogen Span" is not a valid option. Valid options follow:

AUTOGEN

Generates all elements that use the component that is the target of the action. These using elements are generated at the target location that is specified in the SCL statement. If they do not exist at the target location, they are brought back to the target location as sourceless elements. An administrator can change the behavior of the Autogen feature, by activating AUTOGEN_SOURCE in the Optional Features Table (ENCOPTBL). When this option is activated, the Generate actions for the using elements are built with the Copyback, instead of the NoSource, option. For more information about sourceless elements, see the NoSource option description in Generate Syntax.

Note: Using elements are elements that use the element that is the target of an Add , Update, or Generate action. For example, if Autogen is specified for copybook, COPYA, then the programs that use that copybook are known as using elements.

AUTOGEN SPAN NONE

Generates all elements that use the component being acted upon. This option has the exact same effect as the option "AUTOGEN."

AUTOGEN SPAN ALL

Generates using elements that are found in any System and Subsystem combinations within the Environment and Stage of the component's logical map.

AUTOGEN SPAN SYSTEMS

Generates using elements found in any System, provided the element's Subsystem name matches the name of the Subsystem of the target component. Only Systems found within the Environment and Stage of the component's logical map or higher up the map are searched. This option is different from the Autogen option in that it includes additional Systems with the same Subsystem name in the search.

AUTOGEN SPAN SUBSYSTEMS

Generates using elements from all Subsystems with the same-named System of the component specified. Only Subsystem found in the System of the target component within the Environment and Stage of the component's logical map or higher up the map are searched. This option is different from the Autogen option in that it includes additional Subsystems with the same System in the search.

The following restrictions apply to the SPAN options:

• Common libraries must be included in the generate processor concatenations of the Systems and Subsystems of the using elements. If the libraries are not included, then the Generate action does include the changes made to the component element when searching across Systems or Subsystems.
• The same Systems and Subsystems must exist in each Environment and Stage location. For example, if ELEMENTA is a using element in the PROD Environment, system A, then system A must exist in the DEV Environment also.
• SPAN only includes using elements from Systems or Subsystems located in the target Environment and higher up the map.
• SPAN does not include using elements from outside the Environment map.

Example: Update SCL

The following is an example of UPDATE SCL. This SCL modifies the Payroll Reporting program "PAYRPT23." After the update is complete, the source member will be deleted.

UPDATE     ELEMENT 'PAYRPT23'
   TO      ENVIRONMENT 'PROD'
	    SYSTEM 'PAYROLL'
	    SUBSYSTEM 'REPORTS'
	    TYPE 'COBOL'
   FROM    DSNAME 'PAYROLL.SRCLIB'
   OPTIONS DELETE INPUT SOURCE
	    CCID REQ#42976
	    COMMENT 'CHANGES FOR NEW REPORTING REQUIREMENTS' .