3.3
Table Of Contents
- Avid iNEWS Administration Guide
- Contents
- Using This Guide
- 1 - Introduction
- 2 - Connect Services
- 3 - Database Security
- 4 - Database Management
- 5 - Backing Up the iNEWS System
- 6 - Disconnects
- 7 - Troubleshooting
- A - Command References
- Programs Invoked by iNEWS
- Commands Used by Avid Personnel Only
- Linux Commands Used in iNEWS
- Console Control Commands
- Console Server Commands
- broadcast
- configure
- connect
- ctraits
- dbclean
- dbclose
- dbdev
- dbdump
- dbfree
- dblines
- dboriginal
- dbpurge (Superuser conditional)
- dbrestore
- dbserver
- dbsort
- dbtraits
- dbvisit
- dictionary
- diskclear (Superuser only)
- diskcopy
- doc
- ed
- enter
- force (Superuser only)
- grpcheck
- gtraits (Superuser only)
- help
- hogs
- idiff
- list
- list B
- list C
- list c
- list d
- list g
- list p
- list q
- list s
- list sq
- list u
- logout
- makemontab
- makeshift (Super user only)
- maketab (Superuser only)
- msgclean
- offline
- online
- otod
- reconnect
- remove
- rename (Superuser only)
- reorder
- restart
- searchtape
- send
- shutdown
- sitedump (Superuser only)
- siterestore (Superuser only)
- startup
- status
- stop
- su
- unbusy
- utraits (Super user only)
- version
- wholockedit
- Job List Commands
- Dialog Commands
- B - System Files
- C - Standard Dictionaries
- Using Dictionaries to Define Messages and Commands
- Customizing Dictionaries
- Utility Messages Dictionary (/site/dict/messages)
- DBServer Program Messages
- Disconnect Program Messages
- Category and Keyword Check Program Messages
- Keyboard Check Program Messages
- Keyboard Check Program Messages for Macros
- Grpcheck Messages
- Wire Program Messages
- Mail Server Messages
- Validation (Action) Server
- Seek Server Messages
- Last Login Messages
- Print Server Messages
- dbtraits Messages
- Save Error (Workstation) Messages
- Queues Dictionary (/site/dict/queues)
- Words Dictionary (/site/dict/words)
- Keyboard Macros Dictionary (/site/dict/keymacros)
- Case-shifting Dictionary (/site/dict/shift)
- MCS Dictionary (/site/dict/mcs)
- Job List Command Dictionary (/site/dict/joblist)
- D Messages Dictionary (/site/dict/dmessages)
- S Messages Dictionary (/site/dict/smessages)
- D - Environment Variables
- E - Managing Traits at the Console
- F - The Line Editor, ed
- Index
iNEWS Workstation Problems
99
If a user is editing a story and the system crashes, or the user’s PC locks and needs to be
rebooted, the edit lock placed on the story remains attached to the story. When the system
comes back up or after the user logs back in, he or she might be unable to edit the story. The
edit lock will prevent anyone from making changes to the story and users trying to open the
story will get a story busy message.
The story must be unbusied before any user can get back into it.
This is also true of order lock. If a user’s PC crashes while he or she is in order mode, the
order lock remains behind. Both edit locks and order locks are removed with the unbusy
command. The syntax is:
unbusy <queuename>
You must know the exact queue name to unbusy it, such as SHOW.6PM.RUNDOWN.
When you unbusy a queue and there is an order lock on it, you are first asked whether you
want to remove the order lock. Then you are asked whether you want to unbusy each busy
story in the queue.
You can respond with yes to remove the edit lock or order lock, no to skip that story, or quit
to exit.
c
Care should be taken when removing edit locks. Do not unbusy stories that users are
still working in. If you do, when they try to save the story it will be saved to the Dead
queue.
You might see messages on the console about edit-locked (busy) stories in the Dead queue.
A large number of edit-locked stories at the bottom of the Dead queue can cause problems,
and they should be unbusied.
The Dead queue is usually large and an unbusy on the entire queue could take a long time to
execute.
To unbusy edit-locked stories in the Dead queue:
1. Enter superuser mode on the console.
2. Use the unbusy command to remove the edit locks.
NRCS-A# unbusy -i dead
The -i option allows the unbusy command to ignore the inverted attribute.
3. The system will prompt you for confirmation. After answering “yes” to unbusy the
stories, watch for when the system is no longer finding busy stories. You can then break
out of the unbusy process with Ctrl+\ (Control-backslash) or use the Delete key to
“interrupt” the unbusy process.