1 
 2 09/21/87  search_paths
 3 Known errors in the current release of search_paths.
 4 #         Associated TR's
 5 Description
 6 
 7 22  phx14598
 8 The search_paths_$get entrypoint returns the sl_info structure.  The
 9 list_header.update_count field is not incremented if the entire search
10 list is deleted.  Therefore, an obsolete version of some search_list is
11 used because it does not know that the list is absolete.
12 
13 
14 21  phx15867
15 Assume you have a link named forum.search that points to an object
16 segment that does not contain the forum_search_ cds component; but it
17 contains another component with an entrypoint called "forum", then the
18 print_search_paths command displays a totally useless error message.
19 For example:
20 
21   ! cwd [pd]
22   ! ac x >ldd>unb>o>bound_forum_ forum
23   ! in forum forum.search -fc
24   ! dsp forum -a
25   ! psp forum
26     Error:  area condition by search_paths_$set|3513
27     (>sss>bound_search_facility_)
28     Either a variable could not be allocated in an area
29     or an area could not be assigned to an existing area.
30     system handler for error returns to command level
31 
32 
33 The search_paths_ could do a much better job of validating that
34 forum.search$forum is a search list default segment before it goes off
35 and tries it.  It should print the following message:
36 
37 "search_list_pathname is not a search list default segment"
38 
39 rather than taking a fault.
40 
41 
42 19  phx14548
43 The EXL add_search_paths commands gets error when it adds a specified
44 search path name which has an hyphen appeared anywhere in that name to
45 a specified search list.  For example:
46 
47   ! in >exl>sfd>execution>add_search_paths
48   ! add_search_paths compose >udd>m>TLNguyen>compose-links
49     add_search_paths: Specified control argument is not accepted.
50                       >udd>m>TLNguyen>compose-links
51 
52 Note that the add_search_paths in the >sss library does not get this
53 error.  So Barry Margolin guesses that the hyphen appeared anywhere in
54 the search path has caused this error.
55 
56 
57 14  phx12901
58 The -no_force control arg for add_search_rules is not implemented.
59 
60 12  phx12051
61 add_search_paths allows a path to be entered into a list more than one,
62 differing only by add names.
63 
64 11  phx11940
65 For certain errors, delete_search_rules identifies itself as
66 'add_search_rules'.
67 
68 
69 9  phx09886
70 The search facility doesnt handle explicitly null paths (ie, those
71 given as "") correctly.
72 
73 6  phx11766
74 delete_search_paths does not honor the short keywords -hd, -pd, -rd,
75 and -wd.
76 
77 
78 4  phx03790 phx09883 phx12818 phx13325 phx14166
79 The add_search_paths command displays wrong input argument in the error
80 message after it found that that input argument is invalid.  For
81 example:
82 
83    ! asp trans -before -working_dir foo
84      add_search_paths:  Specified control argument is not accepted. -before
85 
86 It must report the invalid argument that it just found such as
87 -working_dir in this example.
88 
89 3  phx03555 phx05116 phx07934 phx13432
90 add_search_paths has no feature that allows moving a search path in a
91 search list, ie., there is no -force control arg.