1 01/30/84  bind_fnp
 2 
 3 Syntax:  bind_fnp pathname {-control_args}
 4 
 5 
 6 Function:  produces a core image segment that can be loaded into the
 7 FNP.  It uses two control segments:  a bindfile, which specifies the
 8 configuration that the FNP will support, the names and ordering of the
 9 object segments included in the core image, and the size of certain
10 software tables; and an optional search rules segment, which specifies
11 which directories are searched to find the object segments.
12 
13 
14 Arguments:
15 pathname
16    specifies the pathname of the bindfile.  If pathname does not have a
17    suffix of bind_fnp, one is assumed.
18 
19 
20 Control arguments:
21 -cross_ref, -cref
22    adds a symbol cross reference to the listing segment.  If -cross_ref
23    is specified, the listing is generated regardless of whether -list
24    is also specified.
25 -list, -ls
26    produces a listing segment whose name is derived from the name of
27    the bindfile, with the suffix changed to list.  The listing segment
28    is a record of the binding.  It contains a copy of the bindfile, a
29    load map, and any error messages generated during binding.
30 
31 
32 -search, -se
33    indicates that the user wishes to specify the rules used to search
34    for Multics Communications System object segments being bound into
35    the core image.  If given, there must be a segment in the working
36    directory containing an ASCII list of relative pathnames of
37    directories to be searched in the order in which the search is
38    desired.  By default, the working directory is searched.  This
39    segment must have the same entryname as the bindfile, but with the
40    suffix changed to search.
41 -version STR
42    assigns a version of STR to the core image.  The maximum length of
43    STR is four characters.  If this control argument is given, it
44    overrides the version keyword specified in the bindfile.
45 
46 
47 Notes:  A default bindfile is supplied with the system.  In general,
48 the only fields that a site administrator would change are:  hsla,
49 lsla, version, order, and the size keyword for the trace module.
50 
51 When creating a new FNP core image, object segments that are unchanged
52 must be extracted from the object archive (see the MPM Commands) into a
53 directory in the search list before executing the bind_fnp command.
54 
55 The syntax of the bindfile is described in Section 6 of the MAM --
56 Communications Manual, Order No.  CC75.