Tachyon Linkage Editor - Input and Output Files

The input and output files read and written by the Tachyon Linkage Editor are similar in concept, use and format with those read and written by IBM’s z/OS Binder. The primary input (SYSIN) is from one or more files containing control statements and/or object records. The primary input can cause files to be read from secondary sources (SYSLIB and SYSLMOD). The output files include the load modules (SYSLMOD), the listing (SYSPRINT) and the messages (SYSTERM).

The z/OS Binder defines SYSLIB and SYSLMOD as partitioned data sets. The Tachyon Linkage Editor simulates partitioned data sets as groups of workstation files in a directory. The names of files accessed like partitioned data set (PDS) members must follow the rules for PDS member names and have a common file name extention. The Tachyon Linkage Editor requires that a path pattern be provided to define the group of files to be treated as a simulated partitioned data set. The path pattern starts with the directory name followed by either &M or &m which is then followed by the file name extension. e.g. C:\MACLIB\&M.MAC If the directory name is omitted, the current working directory is used. The file name extension is also optional. The actual file name is generated by the Tachyon Linkage Editor by replacing the &M or &m with the member name whenever a PDS member is to be accessed. &M is replaced by the member name in upper case. &m is replaced by the member name in lower case.

The files accessed by the Tachyon Update Utility are:

SYSIN - Primary Input File

At least one primary input file is required by the Tachyon Linkage Editor. Each input file contains control statements or object records or both. Each input file can contain either ASCII text or EBCDIC data. If a file contains only control statements, it can be either ASCII or EBCDIC, however if the file contains object records it must be EBCDIC. Object files can contain Object Module Format (OMF) records, Extended OMF (XOBJ) records or Generalized Object File Format (GOFF) records.

The Tachon Linkage Editor detects if a file contains ASCII by checking the first character of the file. If the first character is an ASCII blank, an ASCII asterisk, an ASCII line feed or ASCII carriage return character, the entire file is processed as an ASCII text file. If the first character is an EBCDIC blank, an EBCDIC asterisk or an EBCDIC new line character and an EBCDIC new line character appears in the first 81 bytes, the entire file is processed as an EBCDIC text file. If none of these are true, the file is processed as fixed-length 80-byte EBCDIC records. If a text line is shorter than 80 characters, it is padded with blanks. If a text line is longer than 80 characters, the extra characters are ignored.

The primary input files must be specified on the command line or via the SYSIN DD JCL statement.

SYSLIB - Secondary Input Files

SYSLIB is a list of path patterns that define a simulated partitioned data set. The Tachyon Linkage Editor reads members from the simulated SYSLIB partitioned data set when requested by a control statement such as INCLUDE and during autocall processing. Depending on the input, SYSLIB may not be required. The SYSLIB path patterns are specified via the -S command line parameter or via the SYSLIB DD JCL statement.

When a member is to be read from SYSLIB, the &m or &M in each path pattern is in turn replaced by the requested member name and the Tachyon Linkage Editor checks if the resulting file name exists. The first valid file name stops the search. Like the primary input files, the secondary input files may also contain EBCDIC object records and ASCII or EBCDIC control statements.

SYSLMOD - Load Module Output

SYSLMOD is a single path pattern defining a simulated partitioned data set to which load modules will be written. Certain control statements can also refer to SYSLMOD instead of SYSLIB, causing SYSLMOD members to be read. The SYSLMOD path pattern definition is required.

When the Tachyon Linkage Editor is invoked via JCL, the SYSLMOD DD statement is required to define the output simulated partitioned data set. A member name may be specified with the SYSLMOD data set name to set the default load module name. When the Tachyon Linkage Editor is invoked via the command line, the path pattern and default member name are specified via the -syslmod and -o parameters.

SYSPRINT - Listing

The Tachyon Linkage Editor will normally create a listing file into which a report of the actions performed will be written. The listing file can also contain module maps and cross references. The listing file will contain ASCII text records, each with a leading ASA control character and normal line termination characters.

When the Tachyon Linkage Editor is invoked via JCL, the SYSPRINT DD statement is required to define the listing file. When the Tachyon Linkage Editor is invoked via the command line, the listing file is optional and is specified via the -sysprint command line parameter.

SYSTERM - Messages

When the Tachyon Linkage Editor is invoked via the command line, it can write informational, warning and error messages to the listing file as well as a separate messages file. If not specified via the -systerm command line parameter, messages are written to stdout.