Previous Topic: How CA Endevor SCM Type Records Affect File OperationsNext Topic: Getting Started


Preserve File Format and Structure

When a file has been retrieved to the local file system, any application you use to edit the file must preserve the format of the file. For binary files (DATA FORMAT=B), the editor is typically associated with the application.

For text files (DATA FORMAT=T), the editor must maintain the format associated with the CA Endevor SCM Type field definition, including the linefeed setting (HFS RECFM). Text files are also likely to be associated with an application that handles mainframe-based work. For example, a COBOL file is stored in CA Endevor SCM as fixed-length, 80-byte records, and defined with a Type record DATA FORMAT=T. If you open this element in Eclipse-Based UI to work on it, the editor must maintain the fixed length. If a record is too long, CA Endevor SCM generates an error when you transfer the file back to the mainframe.

More information:

Mainframe Considerations

How CA Endevor SCM Type Records Affect File Operations

Site Batch ID

Site Batch ID

We recommend using BatchID > 0 in the configuration of the Endevor site when using the Eclipse-Based UI. The Eclipse-Based UI uses batch processing and BatchID=0 will cause a mismatch between the logged user and the user of executed jobs.