1 08/02/84  gcos_build_library, gcbl
 2 
 3 Syntax as a command:  gcbl input_path output_path {-control_args}
 4 
 5 
 6 Function:
 7      This command builds a GCOS simulator software library from a
 8 native GCOS system-loadable file and optionally appends a second
 9 software file.  A catalog (or load table) is built from information on
10 the input file and the optional append file, and occupies the first
11 1000 words of the output file.  This process is analogous to building
12 the "GECALL TABLE" by GCOS, at startup, and exists for the same reason
13 (i.e., to facilitate loading of the individual modules).
14 
15 
16 Arguments:
17 input_path
18    is the pathname of the input file.  This file may or may not already
19    have a catalog.  This file may have been created by this procedure,
20    in which case it has a catalog, or by the gcos_extract_module or
21    gcos_pull_tape, in which case it would not have a catalog.
22 output_path
23    is the pathname of the file into which the modules in the input file
24    (plus those in the optional append file) are to be copied, preceded
25    by a catalog.  If this file already exists, it is overwritten, with
26    no warning.
27 
28 
29 Control arguments:
30 -append append_path
31    -append append_path append_path is the pathname of a file whose
32    contents are to be appended to those of the input file (i.e., copied
33    to the end of the output file) before the new catalog is built.
34 -brief, bf
35    suppresses printing of the catalog (load name and offset) of
36    output_path.
37 
38 
39 Notes:  The catalog occupies the first 1000 words of the output file,
40 and has space for 499 entries.
41 
42 Existing modules are not replaced by the appending function.  The only
43 way to replace an existing module with a different version of itself is
44 to extract from the existing library, into a new file, all the modules
45 except the one(s) to be replaced, extract the new versions of those
46 modules into the new file (they are appended to those previously
47 extracted into the file), and then build a catalog for the new file.
48 
49 This command cannot be used to manipulate a random system-loadable file
50 since the catalog created differs from the format of the catalog
51 produced by SYSEDIT (commonly used for ** files).
52 
53 
54 This command is not used to convert the GCOS subroutine libraries (the
55 SOFTW-SYSLIB files) to a form usable by the GCOS simulator.  To do
56 this, the gcos_reformat_syslib command is used.