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
7 Troubleshooting
98
The message returned when the workstation attempts to log in may give you a clue as to
the problem. If no messages appear when the workstation tries to log in, then the
workstation is not reaching the server. Use the workdebug command again to turn off
debugging mode and stop the diagnostic messaging, by typing:
NRCS-A$ workdebug silent
A User Cannot Access an Item
If a user cannot read or write stories in part of the database, he or she may not have
permission to do so. Check the user’s group permissions.
Group Permissions
To assign permission to a user:
1. Use the list g <username> command to determine which groups the user belongs to.
2. Compare assigned user groups to groups assigned to the directory or queue. To do this,
use the list d-g <name of queue> command.
3. If necessary, add the user to the appropriate group story or stories in
SYSTEM.GROUPS. See the iNEWS Newsroom Computer System Setup and
Configuration Manual for more information.
If a user can create new stories in a queue, but not edit existing stories, it may be because
existing stories were created when the queue had another write group assigned to it. Previous
stories would have been created with previous security restrictions. To change the group
permissions on existing stories, use the gtraits command in the following format:
gtraits c <name of queue>
A user may also be unable to access a queue or story in the database if another user is
ordering that queue or editing the story. The queue or story becomes “free” when the other
user finishes the operation, but until then, it is considered to be “busy.”
Busy Stories
Only one user can edit a story at a time. No one else can edit that story until the first user is
done with it. If a second user tries to edit a story that another user is working on, the second
user will get a message that the story is busy. When a user opens a story for editing, the
system puts an edit lock on the story and removes it when the user saves the story and gets
out of it. Edit locks prevent multiple users from making changes to stories.
Similarly, when a user goes into order mode, the system puts an order lock on the queue. No
other user can change the order of stories in the queue until the first user exits order mode.