Opened 13 months ago
Closed 12 months ago
#371 closed enhancement (fixed)
Change verify_info to accept info segments describing an analyze_multics exec_com
| Reported by: | Gary Dixon | Owned by: | Gary Dixon |
|---|---|---|---|
| Priority: | major | Milestone: | MR12.9 |
| Component: | Tools | Version: | MR12.8 |
| Keywords: | Cc: |
Description
verify_info currently permits exec_com segments (ending in .ec) to:
- include use of the .ec suffix in their header line words.
- include use of an exec_com or ec command name in their Syntax line.
For example, in >doc>info>compare_pl1.ec.info, the following header and Syntax lines are accepted as the preferred formatting:
help compare_pl1.ec -bf >doc>info>compare_pl1.ec.info (20 lines in info) 1987-09-10 compare_pl1.ec, cpp.ec Syntax: ec >t>cpp path1 path2 Arguments: path1, path2
As part of new support for analyze_multics exec_com segments (ending in .azmec.info), the same
exceptions in header and Syntax support should be provided.
The installed verify_info (vi) command currently complains about these lines in the proposed event_channel_info.azmec.info segment.
vi event_channel_table.azmec.info
FILE: >udd>m>gd>w>ect>event_channel_table.azmec.info
structure: Info Segment - with History Comment lines: 164
Line Kind Block Names
--- 1 Command
event_channel_table.ec ect.ec
4 Syntax as a command
7 Function
12 Arguments
33 List of modes
72 Access required
--- 79 Subsystem Request
event_channel_table.azmec ect.azmec
header: 2025-06-20 event_channel_table.azmec, ect.azmec
Severity 3. Request/active request header words should each be a reference_name
(begin with a letter, followed by letter/digit/underscore characters) and
appear in a comma-separated list of words ordered by descending lengths.
82 Syntax
syntax items:
| ec ect {MODE_STRING {CHANNEL_IDs}} |
Severity 4. None of the words in the header line appear in syntax.
85 Function
91 Arguments
112 List of modes
153 Access required
--- 160 History Comment
r 04:39 0.166 36
This info segment includes documentation for both the event_channel_table.ec and event_channel_table.azmec segments. verify_info accepts the header and Syntax as a command
contents in the :Info: block describing the .ec segment, but not in the :Info: block describing the .azmec
segment. Both follow the same pattern and should therefore be accepted.
help event_channel_table.ec -bf
>udd>m>gd>w>ect>event_channel_table.ec.info (68 lines in info)
2025-06-20 event_channel_table.ec, ect.ec
Syntax as a command: ec ect {MODE_STRING {CHANNEL_IDs}}
Arguments:
MODE_STRING CHANNEL_ID
List of modes:
default ring=initial lists wait msgs struct
ring=N header call unused itt version
r 04:43 0.139 43
help event_channel_table.azmec -bf
>udd>m>gd>w>ect>event_channel_table.azmec.info (71 lines in info)
2025-06-20 event_channel_table.azmec, ect.azmec
Syntax: ec ect {MODE_STRING {CHANNEL_IDs}}
Arguments:
MODE_STRING CHANNEL_ID
List of modes:
default ring=initial lists wait msgs struct
ring=N header call unused itt version
Change History (2)
comment:1 by , 13 months ago
| Owner: | changed from to |
|---|---|
| Status: | new → accepted |
comment:2 by , 12 months ago
| Milestone: | → MR12.9 |
|---|---|
| Resolution: | → fixed |
| Status: | accepted → closed |

https://s3.amazonaws.com/eswenson-multics/public/mcrs/MCR10154.pdf
Fixed by MR12.9-1021.