How CA Endevor SCM Type Records Affect File Operations

View the online version of this page.

To enable the Eclipse-Based UI to browse, generate, and move elements and components, or exchange files or elements, a CA CA Endevor SCM SCM Type record must be properly defined in CA CA Endevor SCM SCM for each file type you want to work with. The following CA CA Endevor SCM SCM Type definition fields affect Eclipse-Based UI behavior:

• TYPE
  Assigns a user-specified name for a particular file type, for example C, CPY, TXT, COB, SQL, ASM, JCL, JAVA, BMS, DOC.
  The Type value is used as the file extension in the plug-in.
  Each CA CA Endevor SCM SCM element appears in Eclipse-Based UI in the format element.type. This file type format enables the plug-in to recognize files and associate them with a particular editor. For example, the file extension DOC for Microsoft Word files enables the plug-in to recognize the file and open it in Microsoft Word if the file type is associated with the Microsoft Word application in the plug-in preferences.

  • For more information about configuring Eclipse-Based UI to use IBM WebSphere Developer for zSeries file associations to open an alternate editor, see your IBM WebSphere Developer for zSeries documentation.

  • For more information about using Eclipse-Based UI to recognize file associations, see the Eclipse-Based UI documentation.

• DATA FORMAT
  Indicates whether the file type is one of the following:

  • Text (T)
    Prompts Eclipse-Based UI to perform EBCDIC-to-local system character conversion using character sets specified in the web service configuration file or attributes in the wsParameters in the request.

  • Binary (B)
    Specifies that no character conversion should be applied during Add, Update, or Retrieve actions.

    Note: If the DATA FORMAT is not set, no character conversion is applied during Add, Update, or Retrieve actions.

• FILE EXT
  Indicates the 0- to 8-character file extension to be used by Eclipse-Based UI or CA CMEW for elements of this type. The extension can contain mixed case characters of a through z, A through Z, and 0 through 9, or all blanks. Trailing blanks are supported; embedded blanks are not supported.
  If FILE EXT is not defined, then the TYPE value is used as the file extension. However, if FILE EXT is defined, then the TYPE value is not used as the file extension. For example, if TYPE=cobol and FILE EXT=cob, then the file extension cob is used.

• HFS RECFM
  Specifies how text file records are delimited when the text files are transferred to and from Eclipse-Based UI. Valid values are as follows:

  • NL (New Line)
    Specifies the default for CA CA Endevor SCM SCM and UNIX-based file systems. NL causes a single new line character to be inserted at the end of each CA CA Endevor SCM SCM record when opening any element. These characters are stripped off when saving or adding the element to back to CA CA Endevor SCM SCM.

  • CRLF (Carriage Return Linefeed)
    Specifies the default delimiter on PC-based file systems. CRLF causes a pair of characters (a carriage return and a linefeed) to be inserted at the end of each CA CA Endevor SCM SCM record when opening any element. These characters are stripped off when saving or adding the element to back to CA CA Endevor SCM SCM.

  • CR (Carriage Return)
    F (Fixed)
    LF (Linefeed)
    V (Variable)
    Certain file systems or editors may support or require CR and LF characters. However, you may need to specify F or V for binary files.

    Note: For more information on exchanging binary files between CA CA Endevor SCM SCM and Eclipse-Based UI, see the appendix “Working with Binary Files” in CA CA Endevor SCM SCM Administration.

• SOURCE LENGTH
  Specifies the maximum record length that CA CA Endevor SCM SCM will accept.

  Note: For more information about Type definitions, see CA CA Endevor SCM SCM Administration.