How to Enable Web Services › How to Configure CA Endevor SCM for Web Services › How to Define an Element Type for Binary Files

How to Define an Element Type for Binary Files

To define an element Type for binary files (for example, WAR, EAR, JAR DOC, PPT, and XLS), use the following steps:

1. Define the Base library—The base library can be PDS, PDSE, ELIB, CA Panvalet, or CA Librarian.
2. Define the Delta library—The delta library can be PDS, PDSE, or ELIB. Define the delta library as follows:
   • The delta PDS, PDSE, or ELIB record format must be variable blocked.
   • The delta library record length and the Type definition source length can be any value (for example, 259, 6024 or 27984). However, define the maximum delta record length about twice the source length. We recommend an LRECL value of 27,984. For example:

     DCB=(DSORG=PO,RECFM=VB,LRECL=27984,BLKSIZE=0)
     

3. Type definition— Set the TYPE DEFINITION to the following values to define the CA Endevor SCM Type record for the binary element data.
   • Set the Fwd/Rev/Img/Log Delta field to one of the following formats:
     • I— Image delta format. The image delta format stores the full image of the file. This format suppresses the comparison logic. Each update causes the entire file to be added as a new level. Using the full image delta can cause the delta file to run out of space if you have very large binary files and set a high consolidation level.
     • L— Log delta format. The log delta format stores only the last level of the element and stores it as a full image of the element. Delta files contain only change activity information by level. Source changes by level are not kept. Consequently, you cannot view prior source levels or display source change or history.

     Important: Before deciding which delta format to use, consider the benefits and limitations of both. The image delta format can use much space, but prior levels are retained. Whereas, the log delta format only keeps the current element, but does not keep prior levels. For more information about delta formats, see Element Storage Formats.

   • Set the COMPARE FROM field to 1. This option specifies the position within each statement at which CA Endevor SCM begins comparing to identify changed statements (5 digits in the range 1-32,000).
   • Set the SOURCE LENGTH field to 13992. This option specifies the logical record length in the source statements. Although the maximum allowable value is 32000, the value must not exceed the maximum physical record length in the delta library definition.
   • Set the COMPARE TO field to 13992. This option specifies the position within each statement at which CA Endevor SCM stops comparing to identify changed statements.
   • Set the HFS RECFM field to F to specify the fixed length. This option specifies the record delimiter used in a HFS file. A record delimiter is necessary due to the nature of HFS files. HFS files contain one large data stream; therefore, a delimiter is used to identify individual records within that data stream. This is also true for elements associated with a Type defined as Data Format=Text when the element is transferred between CA Endevor SCM and Web Services. Web Services recognizes and appends the delimiter for the exchanged records.
   • Set the DATA FORMAT field to B for binary. If left blank, the value defaults to B. This option deactivates compression and prevents text character conversion from being invoked.
   • Set the FILE EXT field to a valid file extension (doc, ppt, xls, jar, ear, and so on) or leave it blank. The file extension identifies the file type when you are adding from or retrieving to a local file directory using CA CMEW, the Eclipse-Based UI, or a Web Services user-written client program.
   • Set the COMPRESS BASE/ENCRYPT NAME field to Y or N. This option specifies whether to encrypt and compress the base form of elements stored in reverse delta format.