File Typing

For code collection, the AveriSource Platform™ processes application source components and environment or database definition files loaded onto the server in ASCII text format with appropriate file extensions from the table below. Optimally, these are separated into distinct mainframe PDS files or midrange system folders per source type. If this is the case, they should easily be copied via FTP jobs to convert the source from EBCDIC to ASCII, and download the PDS/folder content into a Windows server folder of choice, named by source type, such as COBOL.

Autotyping 

The AveriSource Platform 2.3 and later will now attempt to identify input files with no file extension, or with an unknown extension. The languages recognized in this release are COBOL, JCL, Assembler, and CICS Map. The AveriSource Platform 2.4 and later can also identify RPG, AS400 Objects, CL and Model 204. These abilities are extended to the Preparser as well. Other languages should be given file extensions according to the table below. Should files remain unrecognized, they will appear in the Unknown Files report where they can be multi-selected and given a type manually. 

On the Unknown Files report, select the files for which to change the type. Then, change the type for multiple files at the same time

For any types not listed or in question, contact AveriSource Customer Success at support@averisource.com.