Opened 10 days ago
Closed 26 hours ago
#431 closed defect (fixed)
The list_imft_requests command displays garbage if no default destination is known
| Reported by: | Eric Swenson | Owned by: | Eric Swenson |
|---|---|---|---|
| Priority: | minor | Milestone: | MR12.9 |
| Component: | Standard Library | Version: | MR12.5 |
| Keywords: | Cc: |
Description
If you invoke the "lir" command with no parameters, you'll get output like this:
lir list_imft_requests: Unknown destination. "\000\000\000\000\000\000\000\004\000\000\000\000\000\000]\000\000\000\000\000\000\000\00 \c0" GHM-Test 15:05 0.076 0 Swenson
With a valid destination specified output is reasonable:
lir -ds GHM There are no requests in any To_GHM queue. GHM-Test 15:06 0.146 0 Swenson
Both messages (Unknown destination and garbage) come from the same error label in list_imft_requests.pl1. It prints two variables, foreign_system and remote, that are set only when you give -ds or -sc.
Robert Coren's March 1983 change gave lir a default request type, but didn't set them. So with no arguments the message prints uninitialized stack storage. enter_imft_request and the cancel/move commands do set both from the default; lir was the one that missed it.

https://s3.amazonaws.com/eswenson-multics/public/mcrs/MCR10200.pdf