1 
  2 09/21/87  io_daemon
  3 Known errors in the current release of io_daemon.
  4 #         Associated TR's
  5 Description
  6 
  7 0074  phx20783
  8 If an error code other than error_table_$noentry is returned from the
  9 dprint_$queue_contents, then the displayed queue contents uses an
 10 uninitialized variable, yielding incorrect queue statistics.
 11 
 12 0073  phx20789
 13 l(a d)r is not listing moved requests when requests are moved with the
 14 -admin or -user options.
 15 
 16 0072  phx20784
 17 If a station tries to login to a line already in use, proper cleanup
 18 is not made so that the line can be reattached.
 19 
 20 0069  phx15162
 21 Moving IMFT requests from one queue to another can sometimes cause the
 22 requests to be transmitted twice.
 23 
 24 0068  phx14542
 25 Under certain circumstances, two I/O Drivers serving the same request
 26 type can each print the same requests, thus double-printing each
 27 segment.  Halting the drivers and giving them a ready seems to clear
 28 up the problem.
 29 
 30 0066  phx09001
 31 When a buffer of data is written by the ibm3780 I/O module in
 32 multi_record mode and the buffer contains 509 or more characters the
 33 block of data gets split arbitrarily by the bisync_ I/O module.
 34 
 35 0064  phx03664
 36 The spooler is supplying a canned no to ALL questions asked by
 37 tape_ansi_ (or tape_ibm_ or whoever).  It should only answer "no" to
 38 those questions it understands and should pass on the rest.
 39 
 40 0063  phx02562
 41 The Card_Input Daemon terminates with message "No unclaimed signal
 42 handler specified for thie process" if it has no access to the user's
 43 card_input.acs and the ++EOF card does not occur within a few hundred
 44 cards.
 45 
 46 0059  phx13732
 47  The dprint and enter_output_request commands attempt to initiate the
 48  file being printed and call object_info_ if successful to check if it
 49  is an object segment.  However, when used in the Initializer's
 50  process, the initiate will succeed for multi-segment files causing
 51  object_info_ to take a fault.  The commands should use the file type
 52  previously determined by a call to hcs_$status_long as the criteria
 53  to control the object segment check.
 54 
 55 0057  phx13435
 56  Due to remote_printer_'s interpretation that "^non_edited" mode is
 57  equivalent to "default", it is not possible to connect a printer to
 58  the I/O daemon using tty_printer_ whose terminal modes specify
 59  "rawo".  As a result, use of the "force_ctl_char" feature of the
 60  I/O daemon will not work without the bypass given in the TR.
 61 
 62 0056  phx13435
 63  The printer modes listed by "req_status -long" do not reflect the
 64  actual modes that will be in effect when the request is printed.
 65 
 66 0053  phx13443
 67  The error message printed by enter_output_request when the default
 68  request type for printing, punching, or plotting is not defined is
 69  confusing in that it never states the the request type is undefined.
 70 
 71 0052  phx13443
 72  The print_request_types command will list the default request types
 73  -- printer, punch, plotter -- even if they are not defined in the
 74  I/O daemon tables.
 75 
 76 0050  phx13354
 77  The enter_output_request command should accept "-forms" for punch
 78  and plotter request types.  Additionally, the dpunch command
 79  should accept "-forms".
 80 
 81 0048  phx12867
 82  Until the standard I/O daemon software supports forms names (see
 83  entry 0049 on this list), the standard I/O daemon drivers should
 84  defer any requests with non-blank forms names as they can not process
 85  these requests properly.  If the drivers could determine that a
 86  non-standard driver will never see the request, they should cancel it
 87  outright; however, that's probably impossible to implement.
 88 
 89 0047  phx06540
 90  Specifying the absout name via ++RJECONTROL expands the pathname given
 91  for the absout file with respect to the I/O daemon's home directory
 92  rather than the user's home directory.  Due to the nature of the
 93  ++RJECONTROL card, the only mechanism which can be used to correct
 94  this problem is to add a new control card called ++ABSOUT with syntax
 95  similar to the ++ABSIN card.
 96 
 97 0044  phx05404
 98  The coordinator should check the DTCM of each component of an MSF to
 99  see if it is greater than the time printed when deciding whether the
100  MSF can be safely deleted.  In order to insure these DTCMs are
101  correct, dprint_ should perform an hcs_$status_ call on each component
102  to fix their DTCMs.
103 
104 0043  phx11647
105  If the copy_cards command can not find the requested deck and a new
106  deck name is supplied, the error message will contain garbage.
107 
108 0040  phx11767
109  If the "-htab" attach argument is used with tty_printer_, the I/O
110  module will force "tabs" mode on the lower-level I/O module.
111  tty_printer_ should not do this and should rely on the lower-level
112  module to properly handle the tabs that tty_printer_ sends it.
113 
114 0027  phx06609
115  validate_card_input_ performs its access checks using the user
116  name and project name supplied on the ++DATA or ++RJE cards which
117  might be aliases; it should first translate these identifiers to
118  avoid using aliases.
119 
120 0021  phx07964
121  On reinitialization, the coordinator will delete all files
122  scheduled for deletion after printing/punching even if the
123  delete-time specified by the site in the iod_tables has not yet
124  passed for the file.  The delete-time should always be honored.
125 
126 0020  phx02646
127  If a "clean_cards" command issued from a card input daemon
128  causes the pool directory to be deleted, subsequent "read_card"
129  commands will fail because the pool is no longer initialized;
130  this situation should be detected and the daemon should
131  reinitialize the card pool.
132 
133 0019  phx09955
134  The dprint command does not print the "N requests queued..."
135  message if an invalid control argument is encountered on the
136  command line after pathnames which are successfully processed.
137 
138 0018  phx09937
139  Non-canonical segments can not be printed using standard I/O
140  daemon software.  When (and if) prt_conv_ is rewritten in PL/I,
141  it should be upgraded at that time to support non-canonical
142  data.
143 
144 0015  phx09556
145  In MCC mode, non-ASCII characters are punched as random garbage
146  rather than as NULs (no punches).
147 
148 0014  phx09556
149  In MCC mode, the DEL (\177) character is not punched on output
150  and the card code defined in the RefGuide to represent DEL is not
151  recognized on input.
152 
153 0008  phx09042
154  When reading cards, the daemon ignores "Dual Read Alert".  It
155  should halt, print a message requesting the bad card be retried,
156  and wait for operator intervention.  (This problem also occurs
157  for other status indicators.)
158 
159 0002  phx06810
160  During coordinator initialization, the error message printed
161  when creating "coord_dir" should indicate that the required
162  quota was 250 records.  Further, this message should appear in
163  the error message documentation.