Laserfiche WebLink
<br />'. <br /> <br />00llBS <br /> <br />. The original program was renamed and saved as TAPEDIT,BUR. The ported <br />program was broken into 54 separate subroutines (Attachment 1) using the <br />FORTRAN utility CUTSUB,FOR. Note functions were also broken out as <br />separate subroutines to assist in implementing a revision control procedure on a <br />work station version of TAP EDIT, <br /> <br />. Input and output file names were revised, Attachment 2 presents the data file <br />and naming convention adopted for this application, Attachment 3 presents the <br />flow of input and output files, Note the original files 5 and 6 were replaced with <br />files 55 and 66, respectively for convince to assist in porting to a workstation, <br />Also the path designation (CRSS/DA T/*, *) is used for some input files, <br /> <br />. A m:w subroutine OPENTA.FOR was developed to simplifY the editing and <br />renaming of input files and their storage properties, This subroutine is called by <br />the main program, T APEDIT ,FOR, and reads Attachment 2 as input. <br /> <br />. Compiling and Linking batch files were developed to assist in the porting <br />process, Note, the ported model is stored in directory CRSS/LR/TAPEDIT while <br />the objective files are stored in directory CRSS/LR/OBJT, <br /> <br />. Common blocks were removed from each subroutine to simplifY the designation <br />of character types, They are reinserted into each subroutine during the compiling <br />process by using the INCLUDE command, <br /> <br />. Data statements were revised and included in a Blockdata subroutine, <br /> <br />. End of file designations were revised, <br /> <br />. Hollirith constants within executable statements were revised to include a quote, <br /> <br />. Character types were identified by reviewing I/O formats, if comparisons, etc. <br />To simplifY these edits and insure common blocks and data types were consistent <br />from one subroutine to the next, all common blocks were removed from the <br />individual subroutines and stored as individual files named * ,com, Common <br />blocks are inserted into a subroutine during the compilation step using the <br />INCLUDE command, <br /> <br />. The subroutine which reads CRSM output was revised to coincide with the <br />revisions to that program which allow a direct access read. This allows Single <br />and Multi-Trace input to be located and processed from one file, <br /> <br />2 <br />