Using Set, Clear and EOF Statements › Set Statements › Set Statement Conventions › The Set To Statement › Set To Syntax

Set To Syntax

The following is the syntax for set to action:

►►─ SET TO ─┬─ SYSOut ───────────────────────────────────────────┬─ . ────────►◄
            ├─ C1PRINT ──────────────────────────────────────────┤
            ├─ C1PRTVB ──────────────────────────────────────────┤
            ├─┬─ FILe ───┬─ dd-name ─────────────────────────────┤
            │ └─ DDName ─┘                                       │
            ├─ DSName ─ dataset-name ─┬────────────────────────┬─┤
            │                         └─ MEMber ─ member-name ─┘ │
            └─┤ LOCATION ├───────────────────────────────────────┘

Expansion of LOCATION

├── ENVironment ─ env-name ─ SYStem ─ sys-name ─ SUBsystem ─ subsys-name ─────►

 ►─ TYPe ─ type-name ─┬───────────────────────────┬────────────────────────────┤
                      ├─ STAge ─ stage-id ────────┤
                      └─ STAge NUMber ─ stage-no ─┘

SET TO SYSOUT

SYSOUT applies to the LIST action only. Normally when you execute the LIST action, CA Endevor SCM lists the action cards in both the listing (Execution Report) and the location you have indicated in the TO clause. If you do not enter any information in the TO clause for the LIST action, CA Endevor SCM checks the SET TO statement for information. If the appropriate information has not been entered in the SET TO statement or the SET TO statement indicates only SYSOUT, CA Endevor SCM defaults to SYSOUT alone.

When SYSOUT alone is selected, the action cards requested in the LIST action are printed immediately after the LIST request, as part of the listing. You cannot perform any editing on these action cards because they are available only in the printout. If you have indicated another location (such as a library) in the TO clause, however, you can access, and therefore edit, the action cards generated.

SET TO C1PRINT

C1PRINT applies to the PRINT action only. If you do not enter any information in the TO clause for the PRINT action, CA Endevor SCM checks the SET TO statement for information. If the appropriate information has not been entered in the SET TO statement or the SET TO statement indicates C1PRINT, CA Endevor SCM defaults to C1PRINT and prints the specified element or member in a listing. When using C1PRINT, be sure you have included the appropriate JCL. See the following examples:

• To send your output to the queue, code the following:

  //C1PRINT DD SYSOUT=*
  

• To send your output to an existing file, code the following:

  //C1PRINT DD DISP=SHR,DSN=filename
  

SET TO C1PRTVB

Prints elements that have records that are longer than 121 characters to a location external to CA Endevor SCM (for example, a library, sequential file, or PDS). You must have previously allocated the C1PRTVB data set appropriately. The recommended DCB for C1PRTVB is LRECL=27994,BLKSIZE=0,RECFM=VB. However, if the record size of any record is longer than 27978, code a larger record length. You must code a sufficiently long LRECL for the output file. The LRECL size should be at least 16 bytes longer than the longest record of the element. For example, allocate the data set as follows:

//C1PRTVB  DD DISP=(,CATLG),DSN=my.C1PRTVB,
//         SPACE=TRK,(5,5),UNIT=SYSDA, 
//         DCB=(RECFM=VB,LRECL=27994,BLKSIZE=0)

SET TO FILE (DDNAME) dd-name

DSNAME dataset-name

When the TO location for the element is external to CA Endevor SCM (for example, a library, sequential file, or PDS), you can enter either a file name (or DDname) or a data set name in the TO clause.

• When you enter a file name (DDname), be sure that the appropriate JCL is coded for the entry.
• When you enter a data set name, be sure to enclose the name in quotes (single or double) if there is a period in the name; for example, the data set TEST.LIB must be coded as 'TEST.LIB'.

Note: You cannot code both a file name (or DDname) and a data set name.If you do, you receive an error message. You also receive an error message if you enter CA Endevor SCM location information along with a data set name.

SET TO ENVIRONMENT env-name

SYSTEM sys-name

SUBSYSTEM subsys-name

TYPE type-name

STAGE stage-id

STAGE NUMBER stage-no

Elements in CA Endevor SCM are identified by environment, system, subsystem, type, and stage (ID or number). Several actions require all or part of this information in the TO clause. Whatever data you do not code in the syntax of the specific action must be entered in the SET TO statement.

A brief definition of each identifier follows.

• ENVIRONMENT-The functional areas within an organization. Environment names can be up to 8 characters in length.
• SYSTEM-The applications at a site. System names can be up to 8 characters in length.
• SUBSYSTEM-Specific applications within a system. Subsystem name can be up to 8 characters in length.
• TYPE-Categories of source code. Type names can be up to 8 characters in length.
• STAGE-A stage in a software life cycle. You refer to stages i n SCL statements by one of the following:
  • STAGE ID-A 1-character, alphanumeric stage identifier.
  • STAGE NUMBER-Either 1 or 2. Indicates the position of a stage within the current environment.

Note: For more information about each term, see the User Guide.

SET TO MEMBER NAME

SET TO MEMBER applies only to the LIST action. If you do not enter a member name in the LIST action, CA Endevor SCM checks the related SET TO statement for a member name. If a member name has not been coded, the system defaults to SYSOUT and the list is produced in the listing immediately following the request.

Note: If this statement is used for any other action other than LIST it will be ignored.