Avid INEWS Setup And Configuration Guide I News 3.5 V45 SCG EN

iNews - 4.5 - Setup and Configuration Guide iNEWS-v45-SCG_EN User Guide for Avid iNews Software, Free Instruction Manual

User Manual: avid iNews - 3.5 - Setup and Configuration Guide Free User Guide for Avid iNews Software, Manual

Open the PDF directly: View PDF .
Page Count: 704 [warning: Documents this large are best viewed by clicking the View PDF Link!]

Avid® iNEWS®
Setup and Configuration Guide
2
Legal Notices
Product specifications are subject to change without notice and do not represent a commitment on the part of Avid
Technology, Inc.
The software described in this document is furnished under a license agreement. You can obtain a copy of that license by
visiting Avid's Web site at www.avid.com. The terms of that license are also available in the product in the same directory as
the software. The software may not be reverse assembled and may be used or copied only in accordance with the terms of the
license agreement. It is against the law to copy the software on any medium except as specifically allowed in the license
agreement.
Avid products or portions thereof are protected by one or more of the following United States Patents: 4,970,663; 5,267,351;
5,309,528; 5,355,450; 5,396,594; 5,440,348; 5,467,288; 5,513,375; 5,528,310; 5,557,423; 5,577,190; 5,584,006; 5,640,601;
5,644,364; 5,654,737; 5,715,018; 5,719,570; 5,724,605; 5,726,717; 5,729,673; 5,745,637; 5,752,029; 5,754,851; 5,799,150;
5,812,216; 5,828,678; 5,842,014; 5,852,435; 5,999,406; 6,038,573; 6,061,758; 6,141,007; 6,211,869; 6,532,043; 6,546,190;
6,596,031; 6,636,869; 6,747,705; 6,763,523; 6,766,357; 6,813,622; 6,847,373; 7,081,900; RE40,107; 7,403,561; 7,433,519;
D352,278; D372,478; D373,778; D392,267; D392,268; D392,269; D395,291; D396,853; D398,912.
Other patents are pending.
This document is protected under copyright law. An authorized licensee of Avid iNEWS Command may reproduce this
publication for the licensee’s own use in learning how to use the software. This document may not be reproduced or
distributed, in whole or in part, for commercial purposes, such as selling copies of this document or providing support or
educational services to others. This document is supplied as a guide for Avid iNEWS Command. Reasonable care has been
taken in preparing the information it contains. However, this document may contain omissions, technical inaccuracies, or
typographical errors. Avid Technology, Inc. does not accept responsibility of any kind for customers’ losses due to the use of
this document. Product specifications are subject to change without notice.
The following disclaimer is required by Apple Computer, Inc.:
APPLE COMPUTER, INC. MAKES NO WARRANTIES WHATSOEVER, EITHER EXPRESS OR IMPLIED, REGARDING
THIS PRODUCT, INCLUDING WARRANTIES WITH RESPECT TO ITS MERCHANTABILITY OR ITS FITNESS FOR ANY
PARTICULAR PURPOSE. THE EXCLUSION OF IMPLIED WARRANTIES IS NOT PERMITTED BY SOME STATES. THE
ABOVE EXCLUSION MAY NOT APPLY TO YOU. THIS WARRANTY PROVIDES YOU WITH SPECIFIC LEGAL RIGHTS.
THERE MAY BE OTHER RIGHTS THAT YOU MAY HAVE WHICH VARY FROM STATE TO STATE.
The following disclaimer is required by Sam Leffler and Silicon Graphics, Inc. for the use of their TIFF library:
Permission to use, copy, modify, distribute, and sell this software [i.e., the TIFF library] and its documentation for any purpose
is hereby granted without fee, provided that (i) the above copyright notices and this permission notice appear in all copies of
the software and related documentation, and (ii) the names of Sam Leffler and Silicon Graphics may not be used in any
advertising or publicity relating to the software without the specific, prior written permission of Sam Leffler and Silicon
Graphics.
THE SOFTWARE IS PROVIDED “AS-IS” AND WITHOUT WARRANTY OF ANY KIND, EXPRESS, IMPLIED OR
OTHERWISE, INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE.
IN NO EVENT SHALL SAM LEFFLER OR SILICON GRAPHICS BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT
OR CONSEQUENTIAL DAMAGES OF ANY KIND, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE,
DATA OR PROFITS, WHETHER OR NOT ADVISED OF THE POSSIBILITY OF DAMAGE, AND ON ANY THEORY OF
LIABILITY, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
The following disclaimer is required by the Independent JPEG Group:
This software is based in part on the work of the Independent JPEG Group.
This Software may contain components licensed under the following conditions:
3
Redistribution and use in source and binary forms are permitted provided that the above copyright notice and this paragraph
are duplicated in all such forms and that any documentation, advertising materials, and other materials related to such
distribution and use acknowledge that the software was developed by the University of California, Berkeley. The name of the
University may not be used to endorse or promote products derived from this software without specific prior written
permission. THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE.
Copyright (C) 1989, 1991 by Jef Poskanzer.
Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby
granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission
notice appear in supporting documentation. This software is provided "as is" without express or implied warranty.
Copyright 1995, Trinity College Computing Center. Written by David Chappell.
Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby
granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission
notice appear in supporting documentation. This software is provided "as is" without express or implied warranty.
Copyright 1996 Daniel Dardailler.
Permission to use, copy, modify, distribute, and sell this software for any purpose is hereby granted without fee, provided that
the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in
supporting documentation, and that the name of Daniel Dardailler not be used in advertising or publicity pertaining to
distribution of the software without specific, written prior permission. Daniel Dardailler makes no representations about the
suitability of this software for any purpose. It is provided "as is" without express or implied warranty.
Modifications Copyright 1999 Matt Koss, under the same license as above.
Copyright (c) 1991 by AT&T.
Permission to use, copy, modify, and distribute this software for any purpose without fee is hereby granted, provided that this
entire notice is included in all copies of any software which is or includes a copy or modification of this software and in all
copies of the supporting documentation for such software.
THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED WARRANTY. IN PARTICULAR,
NEITHER THE AUTHOR NOR AT&T MAKES ANY REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE
MERCHANTABILITY OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR PURPOSE.
This product includes software developed by the University of California, Berkeley and its contributors.
The following disclaimer is required by Nexidia Inc.:
Manufactured under license from the Georgia Tech Research Corporation, U.S.A. Patent Pending.
The following disclaimer is required by Paradigm Matrix:
Portions of this software licensed from Paradigm Matrix.
The following disclaimer is required by Ray Sauers Associates, Inc.:
“Install-It” is licensed from Ray Sauers Associates, Inc. End-User is prohibited from taking any action to derive a source code
equivalent of “Install-It,” including by reverse assembly or reverse compilation, Ray Sauers Associates, Inc. shall in no event be
liable for any damages resulting from reseller’s failure to perform reseller’s obligation; or any damages arising from use or
operation of reseller’s products or the software; or any other damages, including but not limited to, incidental, direct, indirect,
special or consequential Damages including lost profits, or damages resulting from loss of use or inability to use reseller’s
products or the software for any reason including copyright or patent infringement, or lost data, even if Ray Sauers Associates
has been advised, knew or should have known of the possibility of such damages.
The following disclaimer is required by Videomedia, Inc.:
“Videomedia, Inc. makes no warranties whatsoever, either express or implied, regarding this product, including warranties with
respect to its merchantability or its fitness for any particular purpose.
“This software contains V-LAN ver. 3.0 Command Protocols which communicate with V-LAN ver. 3.0 products developed by
Videomedia, Inc. and V-LAN ver. 3.0 compatible products developed by third parties under license from Videomedia, Inc. Use
of this software will allow “frame accurate” editing control of applicable videotape recorder decks, videodisc recorders/players
and the like.
4
The following disclaimer is required by Altura Software, Inc. for the use of its Mac2Win software and Sample
Source Code:
©1993–1998 Altura Software, Inc.
The following disclaimer is required by Ultimatte Corporation:
Certain real-time compositing capabilities are provided under a license of such technology from Ultimatte Corporation and are
subject to copyright protection.
The following disclaimer is required by 3Prong.com Inc.:
Certain waveform and vector monitoring capabilities are provided under a license from 3Prong.com Inc.
The following disclaimer is required by Interplay Entertainment Corp.:
The “Interplay” name is used with the permission of Interplay Entertainment Corp., which bears no responsibility for Avid
products.
This product includes portions of the Alloy Look & Feel software from Incors GmbH.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/).
This product may include the JCifs library, for which the following notice applies:
Party Software directory on the installation CD.
Avid Interplay contains components licensed from LavanTech. These components may only be used as part of and in
connection with Avid Interplay.
Attn. Government User(s). Restricted Rights Legend
U.S. GOVERNMENT RESTRICTED RIGHTS. This Software and its documentation are “commercial computer software” or
“commercial computer software documentation.” In the event that such Software or documentation is acquired by or on behalf
of a unit or agency of the U.S. Government, all rights with respect to this Software and documentation are subject to the terms
of the License Agreement, pursuant to FAR §12.212(a) and/or DFARS §227.7202-1(a), as applicable.
003, 192 Digital I/O, 192XD I/O, 888 I/O, Adrenaline, AirPlay, AirSPACE, AirSPACE HD, AirSpeed, ALEX, Alienbrain, AniMatte,
AudioMarket, AudioPages, AudioSuite, AudioVision, AutoSync, Avid, Avid Advanced Response, Avid DNA, Avid DNxcel,
Avid DNxHD, AVIDdrive, Avid DS Assist Station, Avid EditStar, Avid Learning Excellerator, Avid Liquid,
Avid Liquid Chrome Xe, Avid MEDIArray, Avid Mojo, AvidNet, AvidNetwork, Avid NewStar, Avid Remote Response,
AVIDstripe, Avid Unity, Avid Unity ISIS, Avid VideoRAID, Avid Xpress, AVoption, AVX, Beauty Without The Bandwidth,
Blacktooth, Boom, C|24, CamCutter, CaptureManager, ChromaCurve, ChromaWheel, Command|24, Conectiv, CountDown,
DAE, Dazzle, Dazzle Digital Video Creator, Deko, DekoCast, D-Fi, D-fx, DigiDelivery, Digidesign, Digidesign Audio Engine,
Digidesign Intelligent Noise Reduction, DigiDrive, DigiLink, DigiMeter, DigiSerial, Digital Nonlinear Accelerator, DigiTranslator,
DINR, DNxchange, do more, DVD Complete, D-Verb, Eleven, Equinox, EveryPhase, ExpertRender, Fastbreak, Fast Track,
FieldPak, Film Composer, FilmScribe, Flexevent, FluidMotion, FXDeko, G7, G-Rack, HD Core, HD Process, HDPack,
Hollywood DV-Bridge, Hybrid, HyperControl, HyperSPACE, HyperSPACE HDCAM, IllusionFX, Image Independence, iNEWS,
iNEWS Assign, iNEWS ControlAir, Instantwrite, Instinct, Intelli-sat Broadcasting Recording Manager, Intelli-Sat, InterFX,
Interplay, inTONE, Intraframe, iS9, iS18, iS23, iS36, ISIS, IsoSync, KeyRig, KeyStudio, LaunchPad, LeaderPlus, Lightning,
ListSync, Lo-Fi, Magic Mask, Make Anything Hollywood, make manage move | media, Marquee, M-Audio, M-Audio Micro,
Maxim, Mbox, MCXpress, Media Browse, Media Composer, MediaDock, MediaDock Shuttle, Media Fusion, Media Illusion,
MediaLog, Media Reader, Media Recorder, MEDIArray, MediaShare, MediaStream, Media Suite, Meridien, MetaFuze,
MetaSync, MicroTrack, Midiman, MissionControl, Mix Rack, MixLab, Moviebox, Moviestar, NaturalMatch, Nearchive,
NetReview, NewsCutter, Nitris, NRV-10 interFX, Octane, OMF, OMF Interchange, OMM, OnDVD, Open Media Framework,
Open Media Management, Palladium, Pinnacle, Pinnacle DistanTV, Pinnacle Geniebox, Pinnacle HomeMusic,
Pinnacle MediaSuite, Pinnacle Mobile Media, Pinnacle PCTV, Pinnacle PCTV HD Ultimate Stick, Pinnacle PCTV Nano Stick,
Pinnacle PCTV To Go, Pinnacle Scorefitter, Pinnacle Studio, Pinnacle Studio MovieBoard, Pinnacle Systems, Pinnacle
VideoSpin, ProEncode, ProServices, ProSessions, Pro Tools, QuietDrive, Recti-Fi, Reel Tape Delay, Reel Tape Flanger,
Reel Tape Saturation, RetroLoop, rS9, rS18, Salesview, Sci-Fi, Scorch, Scorefitter, ScriptSync,
SecureProductionEnvironment, Session, Show Center, Sibelius, SIDON, Soft SampleCell, Soft-Clip Limiter,
Sound Designer II, SPACE, SPACEShift, SpectraGraph, SpectraMatte, Starplay, SteadyGlide, Streamfactory, Streamgenie,
StreamRAID, Strike, Structure, Studiophile, SubCap, Sundance Digital, Sundance, Symphony, SYNC HD, SynchroScience,
5
SynchroScope, Syntax, Targa, TDM FlexCable, Thunder, Titan, Titansync, TL Aggro, TL AutoPan, TL Drum Rehab,
TL Everyphase, TL Fauxlder, TL In Tune, TL MasterMeter, TL Metro, TL Space, TL Utilities, Torq, Torq Xponent, Transfuser,
Trigger Finger, Trillium Lane Labs, TruTouch, UnityRAID, Vari-Fi, Velvet, Venom, VideoRAID, Video Slave Driver, VideoSPACE,
VideoSpin, Vortx, Xdeck, X-Form, Xmon, Xponent, X-Session, and X-Session Pro are either registered trademarks or
trademarks of Avid Technology, Inc. in the United States and/or other countries.
Footage
Arri — Courtesy of Arri/Fauer — John Fauer, Inc.
Bell South “Anticipation” — Courtesy of Two Headed Monster — Tucker/Wayne Atlanta/GMS.
Canyonlands — Courtesy of the National Park Service/Department of the Interior.
Eco Challenge British Columbia — Courtesy of Eco Challenge Lifestyles, Inc., All Rights Reserved.
Eco Challenge Morocco — Courtesy of Discovery Communications, Inc.
It’s Shuttletime — Courtesy of BCP & Canadian Airlines.
Nestlé Coffee Crisp — Courtesy of MacLaren McCann Canada.
Saturn “Calvin Egg” — Courtesy of Cossette Communications.
“Tigers: Tracking a Legend” — Courtesy of www.wildlifeworlds.com, Carol Amore, Executive Producer.
"The Big Swell" — Courtesy of Swell Pictures, Inc.
Windhorse — Courtesy of Paul Wagner Productions.
Arizona Images — KNTV Production — Courtesy of Granite Broadcasting, Inc.,
Editor/Producer Bryan Foote.
Canyonlands — Courtesy of the National Park Service/Department of the Interior.
Ice Island — Courtesy of Kurtis Productions, Ltd.
Tornados + Belle Isle footage — Courtesy of KWTV News 9.
WCAU Fire Story — Courtesy of NBC-10, Philadelphia, PA.
Women in Sports – Paragliding — Courtesy of Legendary Entertainment, Inc.
News material provided by WFTV Television Inc.
GOT FOOTAGE?
Editors — Filmmakers — Special Effects Artists — Game Developers — Animators — Educators — Broadcasters — Content
creators of every genre — Just finished an incredible project and want to share it with the world?
Send us your reels and we may use your footage in our show reel or demo!*
For a copy of our release and Avid’s mailing address, go to www.avid.com/footage.
*Note: Avid cannot guarantee the use of materials submitted.
Avid iNEWS v4.5 Setup and Configuration Guide • 9329-65310-00 Rev A • Created 6/18/13 • This document is
distributed by Avid in online (electronic) form only, and is not available for purchase in printed form.
6
7
Contents
Using This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Symbols and Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
If You Need Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
...With the Syntax of Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Avid Training Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Overview of iNEWS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
System Administrator Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Chapter 2 The iNEWS Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Configuring PuTTY for iNEWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Logging in as a System Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Entering Superuser Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Changing System Administration Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Exiting the Console Session(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Using Server Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Selecting One or More Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Using Command History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Logged Command History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Chapter 3 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Starting the System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Shutting Down the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Starting a System in Single-Server Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Chapter 4 Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Viewing User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Modifying User Traits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
User Traits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Changing a User’s Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Changing User Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
User Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
8
Setting up Simplified Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Simplified User Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Creating New Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Creating a New User Area in News Database . . . . . . . . . . . . . . . . . . . . . . . . . 88
Adding a New User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Enabing a New User to Receive Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Searching for User Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Removing User Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
The User Manager Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
The Database Manager Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Logging Out All Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Importing Users from an LDAP Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Chapter 5 The Database: Directories, Queues, and Stories . . . . . . . . . . . . . . . . . 107
Overview of the iNEWS Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Restrictions to Directory or Queue Creation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Creating a New Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Creating a New Queue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Outgoing Mail Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Dead Letter Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Search Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Viewing Search Queue Information from the Console . . . . . . . . . . . . . . . 119
Creating a New Story . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Using Script Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Renaming a Directory or Queue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Deleting a Directory or Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Recovering a Killed Story. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Viewing Database Traits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Viewing Information about Stories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Viewing Who Moved, Duplicated, or Killed a Story . . . . . . . . . . . . . . . . . 128
Database Traits Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Changing Database Traits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Turning Off the Ordered Trait of a Sorted Queue . . . . . . . . . . . . . . . . . . . . . . 147
Database Purge Intervals and Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
9
Identifying Locked Queues and Stories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Types of Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Removing Locks from a Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Unbusy Stories and Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
MOS Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Chapter 6 Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Overview of Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Viewing Group Information from the Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Viewing Group Information from a Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Creating a New Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Step 1 - Choosing a Group Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Step 2 - Create New Group at Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Step 3 - Creating Group’s Membership Story and Specifying Members . . . . . 165
Group Checker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Group Checker Error Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Renaming a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Step 1 - Change Group Name in Database . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Step 2 - Change Group Name in SYSTEM.GROUPS . . . . . . . . . . . . . . . . . . . 170
Deleting a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Creating or Modifying Multiple Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Adding Users as Members of a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Adding Groups as Members of Other Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Avoiding Recursion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Adding Workstations as Members of a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Combined Permissions and Timeouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Group Access and Usage Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Group Traits for the Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Read Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Write Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Notification Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Editorial Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Restricted Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Restricting Both Reading and Writing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
10
Transferring Group Assignments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Hiding Queues and Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Creating a Mail Alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Mail Aliases for Other Machines or the Internet . . . . . . . . . . . . . . . . . . . . . . . 186
Chapter 7 Keyboards and Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Types of Macros. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Creating a Keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Creating Macros. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Using the State Keys in Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Repeating Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Notes of Caution for Creating Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Keyboard Checker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Testing the Keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Assigning a Default Keyboard to a User Account . . . . . . . . . . . . . . . . . . . . . . . . . 203
Chapter 8 Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Form Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Creating Forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Customizing Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Turning on Label Borders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
SYSTEM.COLORS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
SYSTEM.LISTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Assigning a Form as a Queue or Story Form. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Form Field Types and Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Standard iNEWS Forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Chapter 9 Character Generator Title Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Overview of CG Title Entry. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Title Entry Setup and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
CG Template Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Edit Title Entry Template Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Creating a New Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Using Font PreSets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Title Entry Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Access to CG Template Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
11
Access to CG Title Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Chapter 10 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Making a Backup File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Viewing System Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Licensing iNEWS Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Editing the Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Testing the Site Configuration File After Alteration . . . . . . . . . . . . . . . . . . . . . 265
Incorporating Configuration Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Hosts File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
System Profile Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Changing the System Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Listing Parameter Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
System Profile Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Viewing Information about Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
List C Message Columns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Adding Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Intersystem Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Sending Intersystem Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Receiving Intersystem Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Chapter 11 Printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Local Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
Local Printing Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Creating and Using Print Styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
Local Print Style Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
Banner Format Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Example Style Story . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
Chapter 12 Wires . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Adding a Wire – Avid Data Receiver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
Phase 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
Phase 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
12
Adding a Wire Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
Phase 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Phase 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
Wire Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
Wire Distribution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
The Wire Distribution Story . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Avoiding Hidden Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
Mailboxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Purge Intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Internationalization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Setting Up Wire Keyword Searches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Additional Information about Search Jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
Keyword Search Rule Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
Keyword Checker Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
Chapter 13 Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Adding a Server Program to the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Job Lists: Queues, Stories, and Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Types of Tasks for Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Adding a Scan Line in a Job List Story. . . . . . . . . . . . . . . . . . . . . . . . . . . 333
Defining a Priority Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
Defining an Every Entry Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
A Server’s Command Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
Processing Deleted Stories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
Ordered Queues and the Order Command . . . . . . . . . . . . . . . . . . . . . . . 337
Mailbox Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
Types of Mailboxes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Assigning a Mailbox to a Queue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
Timed-Interval Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Example of Timed Interval Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
Action Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Adding an Action Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Field Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
13
Possible Uses of Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
Using Field Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
Validation Job List Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Rundown Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
Polling Commands for Action Servers or Txnet Servers . . . . . . . . . . . . . . 352
Configuring Rundown Mirroring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Overlapping Job Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
Polling Issues Related to Tx Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
Distribution Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
Distribution Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
Wildcards and the Destination Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
Move and Dup Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
Action Servers or Tx Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
Instructions in the Wire Distribution Story . . . . . . . . . . . . . . . . . . . . . . . . . 359
Matching and Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
Matching and Order. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
Adding a Distribution Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
Parallel Wire Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Adding a Parallel Wire Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Keyword Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Adding a Keyword Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
System Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
Seek Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
Adding a Seek Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
Fast Text Search Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
Installing FTS Components on the Windows-based Server . . . . . . . . . . . 384
Setting up FTS Components on the iNEWS Servers (Linux) . . . . . . . . . . 386
Batch Indexing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
Reindexing (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
Mail Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
Monitor Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
Checklist: Monitor Server Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
Creating a Monitor Server for Each Show . . . . . . . . . . . . . . . . . . . . . . . . . 395
14
Creating Composite and Event List Queues . . . . . . . . . . . . . . . . . . . . . . 398
Set up Queue and Story Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
Assigning Forms to Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
Creating an Entry in the SYSTEM.MAP Story . . . . . . . . . . . . . . . . . . . . . 402
Updating the iNEWS System Dictionaries . . . . . . . . . . . . . . . . . . . . . . . . 409
Creating Styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
Using the Monitor Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
Network iNEWS Systems Using RX/TX Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
Sending Story Forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
Setting Automatic Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
Update Trait - Queue Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
Changing Queue Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
Adding Rxnet/Txnet Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
Chapter 14 iNEWS Community. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
Configuring iNEWS for Community . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
Syntax of the ctraits Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
Viewing Remote Systems or Community Sessions . . . . . . . . . . . . . . . . . . . . . . . . 435
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
Local and Remote SYSTEM.MOS-MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
Removing a System from Community . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
Connection Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
Large vs. Small Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
Guidelines and Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440
Chapter 15 MOS Redirection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
Overview of MOS Redirection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
MOS-MAP Story . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
Configuring iNEWS for MOS Redirection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
Chapter 16 Web Publishing and Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
Web Publishing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
Setting up Txnet to Send HTML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
The HTML Export Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
Sample HTML Export Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
Publishing iNEWS Stories to the Web. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
15
Web Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
The Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
Logging in via Web Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
Web Acess Story Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
Web Access Directory and Queue Templates. . . . . . . . . . . . . . . . . . . . . . 468
Web Access Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
Chapter 17 iNEWS Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
Overview of Projects and Facets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
Setting up the iNEWS Database for Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
Creating Projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
Date Variables for Searching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489
Creating Facets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
Creating a New Story inside a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
Associating Stories with Projects or Facets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
Creating a Shortcut Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
Appendix A Command References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
Programs Invoked by iNEWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
Commands Used by Avid Personnel Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
Linux Commands Used in iNEWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
Console Server Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
configure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
connect. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
ctraits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
dbclean. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502
dbclose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
dbdev and dbsize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
dbdump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
dbfree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
dblines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
dboriginal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
dbpurge (Superuser conditional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
dbrestore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508
16
dbserver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
dbsort . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
dbtraits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
dbvisit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
diskclear (Superuser only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
diskcopy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
doc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
ed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
enter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
force (Superuser only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
grpcheck . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
gtraits (Superuser only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
hogs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
idiff. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
list B. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523
list C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524
list c . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524
list d . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525
list g . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
list p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
list q . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
list s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
list sq . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
list u
. . . . . . . . . . . . . . . . . . . . . . . . . . . 530
logout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
makemontab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
makeshift (Super user only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
maketab (Superuser only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
mapcheck . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
msgclean . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
17
offline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
otod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
reconnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
remove . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
rename (Superuser only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
reorder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
searchtape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542
send . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542
sendlong. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
sitedump (Superuser only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
siterestore (Superuser only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
stop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
su . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
unbusy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
utraits (Super user only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
wholockedit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
Job List Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550
at . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550
blockmode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550
bpoll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550
bscan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
charset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
dup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
every. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
fast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
18
ignore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
ignore-del . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
local . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
mailto. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
move . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
open . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
passive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
poll. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
publish . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
put . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
quiet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
remote . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
remove . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
replace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
scan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
send-del. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
sendform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
sendpassword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
validate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
Dialog Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558
delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558
diag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558
echo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
escape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
expect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
heol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
mapin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
19
mapout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
pass . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
pause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
stop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
wait . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
Appendix B System Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
/etc/hosts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566
/site/config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567
/site/system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579
SYSTEM.CLIENT.WINDOWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580
SYSTEM.COLORS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
SYSTEM.CONFIGURE.301-ACTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
SYSTEM.GROUPS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582
SYSTEM.INTERPLAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582
SYSTEM.LISTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583
SYSTEM.MAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583
SYSTEM.MOS-MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585
SYSTEM.RESOURCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586
SYSTEM.WIRES.DISTRIBUTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589
SYSTEM.WIRES.KEYWORDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590
SYSTEM.WIRES.KEYWORDS-AP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
SYSTEM.WIRES.KEYWORDS-AP2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592
Appendix C Standard Dictionaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
Using Dictionaries to Define Messages and Commands . . . . . . . . . . . . . . . . . . . . 594
Customizing Dictionaries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
Changing Default Dictionary Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
Restoring Dictionary Defaults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598
Utility Messages Dictionary (/site/dict/messages) . . . . . . . . . . . . . . . . . . . . . . . . . . 599
DBServer Program Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600
Disconnect Program Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600
20
Category and Keyword Check Program Messages. . . . . . . . . . . . . . . . . . . . . 600
Keyboard Check Program Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601
Keyboard Check Program Messages for Macros . . . . . . . . . . . . . . . . . . . . . . 602
Grpcheck Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604
Wire Program Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605
Mail Server Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605
Map Check Program Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605
Validation (Action) Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606
Seek Server Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606
Last Login Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607
Print Server Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607
dbtraits Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607
Save Error (Workstation) Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608
Queues Dictionary (/site/dict/queues) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608
Words Dictionary (/site/dict/words). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610
Keyboard Macros Dictionary (/site/dict/keymacros) . . . . . . . . . . . . . . . . . . . . . . . . 613
Case-shifting Dictionary (/site/dict/shift) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615
MCS Dictionary (/site/dict/mcs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617
Device Types Used by Monitor Servers and Drivers. . . . . . . . . . . . . . . . . . . . 618
Special Strings Recognized by the Monitor Server . . . . . . . . . . . . . . . . . . . . . 618
Error Messages for the Monitor Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618
Status Reported in Device Status Field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621
Job List Command Dictionary (/site/dict/joblist) . . . . . . . . . . . . . . . . . . . . . . . . . . . 621
D Messages Dictionary (/site/dict/dmessages) . . . . . . . . . . . . . . . . . . . . . . . . . . . 623
S Messages Dictionary (/site/dict/smessages). . . . . . . . . . . . . . . . . . . . . . . . . . . . 623
Appendix D Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627
Registry Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628
Environment Variables (Registry Values). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629
CCColor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629
DestinationOrder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631
MailLookup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632
MsgMailAlert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633
PIColor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634
21
RGB Hexadecimal Color Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635
ShowTimingBar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636
SyncToServer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640
VT Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641
DisableCommandLine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643
Environmental Variables for Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644
Appendix E Managing Traits at the Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647
Viewing User Traits from the Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648
Modifying User Traits from the Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649
Changing a User’s Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
Listing Users Who Do Not Have Passwords . . . . . . . . . . . . . . . . . . . . . . . 652
User Traits Console Command Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656
Managing Database Traits from the Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659
Getting Basic Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659
Getting Detailed Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
Changing Database Traits from the Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661
Changing a Parent Directory Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661
Database Traits Console Command Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . 661
Sortfield . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669
Changing a Queue’s Sort Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670
Starting the Queue Sort Function from the Console . . . . . . . . . . . . . . . . . 670
Purge Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671
Mailbox Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672
The dis Column . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672
FTSindex Attribute. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674
Interplay Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674
Managing Group Traits at the Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675
Read Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675
Write Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675
Editorial Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676
Notify Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676
Restricting Access Using Read and Write Limitations . . . . . . . . . . . . . . . . . . . 677
Removing Directory or Queue Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . 678
22
Appendix F The Line Editor, ed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679
Starting ed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680
Specifying Lines to Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680
Searching the File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682
Searching Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683
Editing Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683
Saving Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686
Quitting ed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686
Index
3Using This Guide
Congratulations on your purchase of your Avid iNEWS system. It is a vital part of the Avid
news system solution that integrates with other Avid systems and third-party equipment to
provide an ideal nonlinear workflow and optimize the news production process.
This guide is part of a two-book set designed to keep pace with current advances in the Avid
system’s news production capabilities. The set—made up of this book and the Avid iNEWS
Administration Guide—is a comprehensive resource of all administrative information you
will need to take advantage of the many options available to you.
This guide will lead you through even the most complex procedures with task-oriented
instructions. The information provided here builds on basic news production procedures
described in the help system and other user-based guides, while adding a complete
explanation of all of the tools and techniques required to manage the newsroom computer
system, including useful tips, shortcuts, and custom options.
nThe documentation describes the software features and hardware related to the iNEWS
newsroom computer system, which is extremely customizable. Your system might not contain
certain features and/or hardware that are covered in the documentation.
Symbols and Conventions
Avid documentation uses the following symbols and conventions:
Symbol or Convention Meaning or Action
nA note provides important related information, reminders,
recommendations, and strong suggestions.
cA caution means that a specific action you take could cause harm to
your computer or cause you to lose data.
wA warning describes an action that could cause you physical harm.
Follow the guidelines in this document or on the unit itself when
handling electrical equipment.
3 Using This Guide
24
If You Need Help
If you are having trouble using your Avid product:
1. Retry the action, carefully following the instructions given for that task in this guide. It
is especially important to check each step of your workflow.
2. Check the latest information that might have become available after the documentation
was published:
- If the latest information for your Avid product is provided as printed release notes,
they ship with your application and are also available online.
- If the latest information for your Avid product is provided as a ReadMe file, it is
supplied on your Avid installation CD or DVD as a PDF document
(README_product.pdf) and is also available online.
You should always check online for the most up-to-date release notes or ReadMe
because the online version is updated whenever new information becomes
available. To view these online versions, select ReadMe from the Help menu, or visit
the Knowledge Base at www.avid.com/readme.
3. Check the documentation that came with your Avid application or your hardware for
maintenance or hardware-related issues.
> This symbol indicates menu commands (and subcommands) in the
order you select them. For example, File > Import means to open the
File menu and then select the Import command.
This symbol indicates a single-step procedure. Multiple arrows in a list
indicate that you perform one of the actions listed.
(Windows), (Windows
only), (Macintosh), or
(Macintosh only)
This text indicates that the information applies only to the specified
operating system, either Windows or Macintosh OS X.
Bold font Bold font is primarily used in task instructions to identify user interface
items and keyboard sequences.
Italic font Italic font is used to emphasize certain words and to indicate variables.
Courier Bold font
Courier Bold font identifies text that you type.
Ctrl+key or mouse action Press and hold the first key while you press the last key or perform the
mouse action. For example, Command+Option+C or Ctrl+drag.
Symbol or Convention Meaning or Action
If You Need Help
25
4. Visit the online Knowledge Base at www.avid.com/onlinesupport. Online services are
available 24 hours per day, 7 days per week. Search this online Knowledge Base to find
and to read or join online message-board discussions.
...With the Syntax of Commands
If you are at the console and are unsure about the function of a command, use the help
command.
To view instructions about using a command:
tUse the following command:
help
<command name>
For instance, type:
help dbvisit
for an explanation of the dbvisit command.
The following data appears:
dbvisit -<d or v or i> [-r or -c name] [-s] [-l] [block# ...]
‘r’ for read only
‘s’ for “slow” to eliminate cache usage
‘c’ use checkpoint partition (forces “-s”)
‘i’ to just validate isam files
‘l’ to list link count distribution
nLengthy console displays might be edited to emphasize only the most important information
in this guide. An ellipsis (...) represents portions of the console display not shown in the text.
Also, because of the margin limitations of this guide, command lines might appear wrapped
to multiple lines. This does not necessarily indicate the need to press an Enter key. Unless
otherwise indicated, commands should be typed on a single line, allowing the computer to
wrap the text whenever the command line stretches beyond the screen margin.
3 Using This Guide
26
Avid Training Services
Avid makes lifelong learning, career advancement, and personal development easy and
convenient. Avid understands that the knowledge you need to differentiate yourself is always
changing, and Avid continually updates course content and offers new training delivery
methods that accommodate your pressured and competitive work environment.
To learn about Avid's new online learning environment, Avid Learning Excellerator
(ALEX), visit http://learn.avid.com.
For information on courses/schedules, training centers, certifications, courseware, and
books, please visit www.avid.com/training or call Avid Sales at 800-949-AVID
(800-949-2843).
1Introduction
The iNEWS newsroom computer system is an integrated digital news production system,
which provides journalists, producers, directors, writers, and technical personnel with an
array of tools to make their jobs easier.
This chapter contains the following main sections:
Overview of iNEWS
-Customizing the System
-Reviewing Default Settings
-Troubleshooting
Overview of iNEWS
An iNEWS newsroom computer system provides:
News gathering from text sources
News production, including:
- Story creation and script editing
- Association of machine control items to script
- Show planning and creation
- Show archiving
- Contact organization and scheduling
News to air, including:
- On-air playback control
- File exporting
- Internet publishing
Some primary components of iNEWS include:
Linux-based computers running the iNEWS Server software. In this guide, these host
computers are referred to as the iNEWS Servers, or individually as server A, server B,
and so forth.
A Windows-based computer running the PuTTY Command Sender program. This
computer is known as the console.
Windows- or Vista-based computers running the iNEWS client software. These
computers are known as iNEWS Workstations.
Windows-based computers running the iNEWS Data Receiver software, which is used
to ingest wires and other text-based research material
Other peripherals, such as printers and teleprompters.
Additionally, the iNEWS system is capable of interfacing with a wide variety of production
devices. Avid iNEWS Command provides a central point of control for numerous video
servers and graphics devices, or MOS protocol may be used to send playlists to
MOS-compatible playout controllers.
29
The following sections describe common system administrator responsibilities and tasks.
Before you can customize or maintain the iNEWS newsroom computer system, you must
learn several basic tasks, which include:
Start up or shut down iNEWS Server software, which includes logging out users and
taking the system offline.
Back up a site file before making file modifications.
Send system administrator commands from the console to one or more of your system’s
computers.
Become a console superuser, capable of performing actions that are only accessible to
users with superuser permissions.
A user is anyone who can log in to the database and use iNEWS NRCS. Your
responsibilities regarding users are:
Monitor user information, such as users’ access privileges and which users are currently
logged in.
Customize the traits of users’ accounts to enable users to more effectively use the
system.
Provide a new employee access to the information stored in the iNEWS NRCS database
by creating a new user account.
Remove user accounts of former employees to prevent improper access to the iNEWS
NRCS database.
The iNEWS system database contains the information your organization needs to function.
A system administrator’s tasks associated with the database include:
Design forms (that is, story templates) to display important information about stories in
a queue.
Monitor changes to files and queues in the database.
Unlock or delete any item in the database, and recover items that were accidentally
deleted or corrupted.
1 Introduction
30
Create new folders or queues in the iNEWS system database to meet your organization’s
expanding needs—including setting up rundowns.
Remove a directory or queue from the database, if it is no longer used.
Change the name or traits of an existing directory or queue.
Assign the mailbox trait to queues for configuring automatic story distribution into and
out of queues.
There are many ways to ensure the security of your iNEWS system. Your responsibilities
regarding system security include:
Monitor and change passwords or force users to change them by setting up system
checks and modifications.
Monitor user login activity to guard against unauthorized use of the iNEWS system.
Assign security to a directory or queue, limiting access to a specific group of users.
Restrict database access by placing users into security groups based on job roles and
need for information.
Customizing the System
Your responsibilities regarding customization include:
Customize command names, message text, and other items by changing their entries in
your system’s dictionary files.
Create templates for the CG Title Entry tool.
Design and assign custom keyboards for users with a unique set of keyboard macros.
You will want to monitor the database regularly to ensure adequate storage. Storage
Monitor how much free space is available in the database and, if necessary, increase the
amount to prevent the system from running out of space.
Perform preventive database maintenance by periodically running certain utility
programs that can find and fix minor problems before they become serious.
Backup the entire database or portions of it onto tape, so if necessary, the information
can be restored to the database later.
Make a backup copy of files any time you make important changes.
31
A device is any kind of hardware or software that performs a specific function when it is set
up on the iNEWS system. Your responsibilities regarding devices include:
List the parameters of any device running on your system or list all devices of one type.
Add any type of device to your system, if you have the capacity and license permission.
Edit site-specific files, to change the setup information for a device in your system’s
configuration file.
Reconfigure the system so it recognizes any changes you make to your system’s
devices.
Set up printer styles so users can print stories or queues in predetermined formats. For
example, a director rundown only showing specific rundown fields.
Set up servers, which are utility programs automatically performing various actions on
the database.
Change wire distribution and sorting of data coming into your database from a wire
service to queues based on their category codes or content.
(Optional) Write dialogs—lists of instructions—for each connect service to automate
the connection process. A connect service is a device that connects a user to a remote
computer system.
Reviewing Default Settings
Your responsibilities regarding system profiles, default settings, and command syntax
include:
Changing a system profile setting to change your system’s operation.
Reviewing default settings of all system profile parameters.
Reviewing command syntax for edit, console, and job list commands.
Troubleshooting
Your troubleshooting responsibilities include:
Transfer system activities from a halted computer to other system computers. If a
computer connected to the system has been halted, bring the system back to operation
using the remaining computers
Reconnect a computer that has been halted. Following routine maintenance, reintegrate
a computer into your system’s operation.
1 Introduction
32
2The iNEWS Console
The iNEWS console is a Windows-based computer that serves as a “command center”
enabling system administrators to monitor and maintain the iNEWS newsroom computer
system. The console uses PuTTY software to send commands to one or more iNEWS
servers.
This chapter contains the following main sections:
Configuring PuTTY for iNEWS
Logging in as a System Operator
Entering Superuser Mode
Exiting the Console Session(s)
Using Server Commands
Selecting One or More Servers
Using Command History
Configuring PuTTY for iNEWS
PuTTY is a free (MIT-licensed) Win32 Telnet and SSH terminal emulation program that can
be installed and used by an iNEWS system administrator to access the Red Hat Linux
command line interface. Every command line command entered at the console can be
entered through a PuTTY connection.
nAvid software distribution of iNEWS only includes PuTTYtel (the Telnet only version of
PuTTY) for countries where encryption is outlawed.
A full PuTTY installer may be freely downloaded from online sources, such as:
http://the.earth.li/~sgtatham/putty/latest/x86/putty-0.62-installer.exe. User guides with
instructions for installing, configuring, and using the third-party program are also available
online, such as: http://the.earth.li/~sgtatham/putty/0.62/htmldoc/index.html.
nAvid recommends installing the PuTTY executables in C:\Console and creating a sub-folder
called Logs at C:\Console\Logs to hold the console log files. Also, make sure the COM1 and
COM2 is connected to all iNEWS servers if there is enough on-board Serial COM port, a
USB to serial adaptor can be used instead.
For the purposes of this guide, this section provides configuration information as it relates
specifically to using PuTTY with an iNEWS newsroom computer system.
The following procedure must be repeated for each server. Examples are provided showing
settings for a dual-server configuration with servers A and B.
To configure PuTTY:
1. Click Start > Programs > PuTTY > PuTTY.
The PuTTY Configuration dialog box appears.
2. Expand Session and select the Logging category.
Configuring PuTTY for iNEWS
35
a. Set Session logging to All session output.
b. Select the Always append to the end of it radio button.
c. Set each server’s log file name.
tWhen doing this procedure for server A, set the Log file name to
C:\Console\logs\iNEWS-A-&Y&M&D.log
tWhen doing this procedure for server B, set the Log file name to
C:\Console\logs\iNEWS-B-&Y&M&D.log
nThe examples shown here are for the more common 2-server system configuration, but an
iNEWS system can have up to four servers (A, B, C, and D). For 3-server and 4-server
systems, use log file names that correspond to each server’s letter assignment.
2 The iNEWS Console
36
This creates a log file for each server with the year, month, and day appended to the
name.
nThere is no auto-delete or auto-purge of log files.
Configuring PuTTY for iNEWS
37
3. Expand Window and select Behavior category.
a. Set Window title for each server’s console session.
tWhen doing this procedure for server A, type Console for iNEWS-A.
tWhen doing this procedure for server B, type Console for iNEWS-B.
2 The iNEWS Console
38
b. Select the Translation category and set Remote character set to UTF-8.
Configuring PuTTY for iNEWS
39
4. Expand Connection and select the Serial category.
tFor server A, set Serial line to connect to COM1.
2 The iNEWS Console
40
tFor server B, set Serial line to connect to COM 2.
5. Select Session.
a. For server A, do the following:
- Set Serial line to COM1.
- Set Connection type to Serial.
- Set Saved Sessions to iNEWS-A com.
Configuring PuTTY for iNEWS
41
b. For server B, do the following:
- Set Serial line to COM2.
- Set Connection type to Serial.
- Set Saved Sessions to iNEWS-B com.
2 The iNEWS Console
42
Configuring PuTTY for iNEWS
43
6. Ensure the console connections start at startup.
a. Create shortcuts for each PuTTY console connection in the Startup folder.
b. Add the Startup command option into each shortcut, as shown in the following
images—one for each server.
2 The iNEWS Console
44
Configuring PuTTY for iNEWS
45
7. Start the PuTTY Command Sender program by clicking the PuTTYCS icon installed on
the desktop.
The following dialog box opens.
2 The iNEWS Console
46
8. Click Preferences.
9. Configure the preference start-up settings.
Section/Setting Description
Window > Tool window Display PuTTYCS as a tool window with the thin title bar.
Window > Always on top Display PuTTYCS on top of all other windows.
Configuring PuTTY for iNEWS
47
Window > Minimize a system
tray
Minimizes PuTTYCS to the system tray. If enabled, PuTTYCS can only be
exited through the system tray popup menu.
Window > Opacity Use the slider to set the opacity for the PuTTYCS window. This may be
useful if PuTTYCS sometimes blocks your existing PuTTY windows.
Auto arrange > Off, Cascade, Tile Use to turn auto arrange off or on and set to cascade or tile PuTTY windows.
Auto arrange > Minimize other
PuTTYs
When auto-arranging filtered PuTTY windows, minimize all other PuTTY
sessions.
Auto arrange > Arrange on
startup
When starting PuTTYCS, auto arrange filtered PuTTY windows.
Auto arrange > Unhide PuTTYs
on exit
Unhides any PuTTY sessions previously hidden using the Hide button.
Tile method > Vertical,
Horizontal, Classic
When tiling PuTTY windows, use selected method. The Classic style tiles
windows like version 1.7 of PuTTYCS or earlier.
Cascade dimensions Sets dimensions of filtered PuTTY windows when the Cascade setting is
enabled. PuTTYCS only supports cascading dimensions between 98x18
(12x1) and 1042x802 (130x50). Default dimensions are 642x386 (80x24).
These dimensions are hardcoded and will not change with system settings.
nYou can press the Find button to determine the dimensions of the largest visible PuTTY window.
Keyboard/Mouse > Enable Tab
completion
If enabled, pressing Tab in the command field, sends the command including
the Tab key. Useful for file completion in shells like tcsh.
Keyboard/Mouse > Scroll
command history with up/down
arrows keys
If enabled, you can use the Up and Down Arrow keys to scroll through the
command history.
Keyboard/Mouse > Selection
copies, right button pastes
Enable this to emulate PuTTY’s selection to clipboard and right mouse
button paste features.
Transition delays: (Advanced) >
Window
Sets the amount of time (in milliseconds) to pause after focusing a PuTTY
window and before sending the command.
The slower the machine or remote connection, the higher this value should
be.
Transition delays: (Advanced) >
Post send
Sets the amount of time (in milliseconds) to pause after sending a command
to a PuTTY window.
The slower the machine or remote connection, the higher this value should
be.
Section/Setting Description
2 The iNEWS Console
48
10. Click OK to save changes.
11. Select the Filters button.
The PuTTY Filters dialog box appears.
By default, AllPuTTYs filter is set. This means PuttyCS sends commands to all open
sessions; however, you can create filters to send commands to only specific sessions. For
instance, when you log in via serial ports, the sessions have a title of COM3, COM4, etc.
If you log in via SSH, the sessions have titles of so@WAVD-A, so@WAVD-B, etc.
12. Click Add to add new filters.
Miscellaneous > Save password Saves the password used in the SEnd Password dialog.
nPasswords are encoded in Base64 and stored in the PuTTYCS.ini file. This might present a potential
security risk.
Miscellaneous > Run on system
startup
If enabled, adds a registry entry that automatically executes PuTTYCS when
the system is started.
nThe registry entry is:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run\PuTTYCS
Miscellaneous > Check for
If enabled, PuTTYCS will check for software updates when started.
Section/Setting Description
Configuring PuTTY for iNEWS
49
Enter a name for the filter, and then create the filter list, using the following format:
+inclusion; +inclusion;... -exclusion;-exclusion;.... You can use asterisks (*) and
question marks (?) for wildcards.
13. Click OK to save changes.
2 The iNEWS Console
50
Logging in as a System Operator
System administrators must log in to iNEWS at the console differently than other users who
log in at an iNEWS Workstation. For security reasons, system administrators should log out
of the system when not using it.
To log in as the system operator:
1. Select the server(s) displaying the login prompt.
2. Type:
so
.
3. Press Enter.
4. If your system has a password for this account—and most do—then type in the
password when prompted. To keep the password confidential, the console does not
display what you type.
nThe system operator password is set during installation of the iNEWS Server software on the
iNEWS servers. For information about changing the system operator password, see
“Changing System Administration Passwords” on page 51.
5. Press Enter.
The console’s server prompt will look similar to this:
NRCS-A\$
nEach server’s name is based on the system ID (typically a station’s call letters) and the
server’s name (usually a single letter, such as A, B, or C). Examples in this guide use NRCS
as the fictional station and system ID.
Entering Superuser Mode
An administrator can take special system privileges as a console superuser when he or she
needs to use more powerful—and therefore potentially more dangerous—commands. Once
the administrator is done with these more powerful commands, he or she can give up the
privileges without logging out. Giving up the privileges (by exiting superuser mode) helps
prevent mistakes and provides better security.
The console’s server prompt is the visual indicator for whether you are logged in as a system
operator or have enter superuser mode. The server prompt for a system operator login ends
with a dollar sign (\$). The server prompt while in superuser mode ends in a pound sign (#).
The system operator prompt looks like this:
NRCS-A\$
51
The superuser prompt looks like this:
NRCS-A#
nIf a command example in this guide shows the superuser prompt—ending in a pound sign
(#)—you must be in superuser mode to use the command.
A password is required for taking superuser privileges. This password is the same as the root
user password, which is set during installation of the Linux operating system on the iNEWS
servers. See “Changing System Administration Passwords” on page 51 for more
information.
To take superuser privileges:
1. If you are not already logged in, then log in as a system operator, by typing:
so
.
2. Enter superuser mode by typing:
su
.
3. Press Enter.
4. Type the superuser password at the password prompt. To keep the password
confidential, the console does not display what you type.
5. Press Enter.
After you entered the password correctly, the console shows that you have superuser
privileges by changing the dollar sign (\$) at the end of the server prompt to a pound sign
(#). If you enter an incorrect password, the console displays an error message and
returns you to a system operator prompt.
cTo prevent users from typing unauthorized commands, never leave the console
unattended when logged in with superuser privileges. You should enter superuser
mode only when you need to type a superuser command, and give up the privileges
immediately after typing the command.
To give up superuser privileges and return to the system operator prompt:
tPress Ctrl+D.
The console shows that you are a system operator by changing the pound sign (#) at the
end of the console’s server prompt to a dollar sign (\$).
When logging in to the console as either a system operator or superuser, a password is
needed. These system administration passwords are typically set by Avid Customer Support
technicians during the installation of either the iNEWS Server software or the Linux
operating system (OS). However, they can be changed later by system administrators at the
console.
2 The iNEWS Console
52
nChanging the superuser password also changes the Linux root user password, which is set
during the Linux OS installation, must be more than six characters, initially.
Keep a confidential record of password changes. Knowing the passwords is critical. If you
forget your passwords, the operating system might need to be reinstalled from scratch by
Avid Customer Support technicians.
To change the system operator password:
1. Log in as a system operator, using the current password.
2. At the server prompt, type the password command, as shown:
NRCS-A\$
passwd
3. Press Enter.
4. Type the current password, and press Enter.
5. When prompted, type a new password, and press Enter.
nIf the system operator password is fewer than six characters or is based on a word in the
dictionary, the system will issue a “BAD PASSWORD...” message, but it will accept such
passwords. The system will not accept a blank password.
6. When prompted to confirm, retype the new password, and press Enter.
To change the console superuser password:
1. Enter superuser mode, using the current password.
2. At the superuser prompt, type the password command, as shown:
NRCS-A#
passwd
3. Press Enter.
4. Type the current password, and press Enter.
5. When prompted, type a new password, and press Enter.
6. When prompted to confirm, retype the new password, and press Enter.
nIf the password does not match, the system displays an error message. Start over by retyping
the new password. Also, if the superuser password is fewer than six characters or is based
on a word in the dictionary, the system will issue a “BAD PASSWORD...” message, but it
will accept such passwords. The system will not accept a blank password.
7. Press Ctrl+D to leave superuser mode.
The pound sign (#) at the end of the console’s server prompt will change to a dollar sign
(\$).
Exiting the Console Session(s)
53
Exiting the Console Session(s)
You should leave the console sessions on at all times while the iNEWS system is running.
However, some regular maintenance situations might require you to exit the console.
nAvid recommends system administrators close and restart PuTTY console programs
regularly—such as once a month. By doing so, this helps keep log files at manageable file
sizes.
To exit the console:
1. Close the windows for each server’s console session.
2. Exit the PuTTYCS applications.
Using Server Commands
The iNEWS system will not recognize server commands entered in upper case. Type server
commands at the console in lower case after the prompt for the server to which you want the
command sent. For instance, if you want to send a command to server A, type the command
after the server prompt associated with server A.
nThe console displays each server’s prompt based on the system ID and the server’s name,
separated by a hyphen. Some examples in this guide use NRCS as the system ID and single
letters—such as A, B, or C—as the server name. For instance, the server prompt might
appear like this:
NRCS-A\$
. Other examples show WAVD as the system ID, such as WAVD-A
or WAVD-B.
The appearance of the server prompt varies, depending on how the system administrator is
logged in to the console session. See “Logging in as a System Operator” on page 50 and
“Entering Superuser Mode” on page 50 for more information.
An example of a server command is the
list sessions
command—or
list s
command—which when sent to an iNEWS server will return information about who is
logged in to that session.
A detailed list of commands is provided as an appendix to this guide. See “Console Server
Commands” on page 500 for more information.
To simultaneously send a server command to multiple servers:
tFrom the PuTTYCS application, select the PuTTY Filter created for sending server
commands to which servers you want to send the command.
2 The iNEWS Console
54
For instance, if you want to send a command to servers A and B only, select the filter
that sends commands to only those two servers, or to send a command to all servers,
select the filter for all servers.
tType the command.
tClick Send.
To stop a server command:
tPress Ctrl+C—the stty interrupt character. Doing so will interrupt the command’s
execution.
nAs a last resort, pressing the Control and Backslash keys (Ctrl+\—the stty quit character)
will stop the command’s execution. Avid recommends you should attempt to “interrupt”
before trying to “quit” the execution.
If the server sends a message while you are typing a command, the console stops displaying
your keystrokes to display the message. However, it continues to record what you type. After
it has displayed the message, then the console will display the data you typed in its entirety.
If you are interrupted by a console display or have mistyped a command, you can cancel the
entire command line and start over by pressing Ctrl+U.
Selecting One or More Servers
55
nThe character used to issue the command that cancels an entire command line—known as
the “kill” character—may be customized, using the stty command. For instance, to set it to
the “at” character, you would type:
stty kill @
.
To reset it to the default Ctrl+U, type:
stty kill ^U
.
The same customization capability applies to the “intr” or “interrupt” character, which is
used to interrupt a running program. For instance, type:
stty intr ^?
to set it to the
Delete key, To reset it to the default Ctrl+C, type:
stty intr ^C
.
To clarify, the
^U
and
^C
—shown above— mean to hold the Shift key down and press the 6
key, to get the ^ character, and then the U or C letter key respectively. The same applies to
the
^?
. You can view these settings by entering the server command:
stty -a
.
Selecting One or More Servers
You can select to send a command to one server or multiple servers at the same time. For
instance, some commands must be executed on all servers simultaneously, so on a
two-server system, you must select to send the command to both server A and B via the
PuTTY Command Sender application (PuTTYCS).
The following image shows a computer screen with two individual console windows
open—one console session per iNEWS server, which are named iNEWS-A and
iNEWS-B—and the PuTTY Command Sender application.
2 The iNEWS Console
56
To send a command to only server A:
1. Select the console window for server A.
2. Type your command.
3. Press Enter.
To simultaneously send a command to both the A and B servers:
1. From the PuTTYCS application, select the PuTTY Filter created for sending server
commands to servers A and B.
2. Type the command.
3. Click Send.
To simultaneously send a command to all servers:
1. From the PuTTYCS application, select the PuTTY Filter created for sending server
commands to all servers, such as iNEWS Consoles.
2. Type the command.
3. Click Send.
Using Command History
57
Using Command History
When output from a server command consists of more lines than can fit in the window, lines
will be scrolled off the screen. However, the PuTTY application does keep a buffer of recent
history that you can view by scrolling through the data in each corresponding PuTTY
window. The top of the buffer contains the oldest information; the bottom of the buffer
contains the most current.
By default the PuTTY application maintains 200 lines of data in the buffer. This setting can
be modified.
nThe PuTTY application can also be configured to log console history for viewing at a later
time. See “Configuring PuTTY for iNEWS” on page 34 for more on configuring PuTTY to
store log files.
To change the number of lines kept in the buffer:
1. Expand the Window category in the PuTTY Configuration dialog box.
2. Enter in the Lines of scrollback field the number of lines you want stored in the
command history buffer.
2 The iNEWS Console
58
To view recent history on a particular server:
1. Maximize the server’s window whose history you want to review.
2. Scroll through the most recent console history. By default the buffer contains 200 lines
of data.
If enabled in Keyboard/Mouse section of the Preferences dialog box for the PuTTYCS
application, you can use the Up or Down Arrow keys on the keyboard to scroll.
Logged Command History
You can configure PuTTY to log command history to disk for later review. The logs are
written to the hard drive on your console PC, traditionally in the
C:\Console\logs
directory. The name of the log files for each iNEWS server are set up when PuTTY is first
installed and configured. See “Configuring PuTTY for iNEWS” on page 34 for more
information.
The log files are ASCII text files that can be read with any word processing program.
3Getting Started
System Administrators are responsible for knowing how to start up and shut down the
iNEWS system. This requires logging in at the console, which is done differently than other
iNEWS users and provides access to features that other logins do not. Information on using
the console, including logging in, is covered in Chapter 2. This chapter provides specifics on
starting up and shutting down the newsroom computer system.
This chapter contains the following main sections:
Starting the System
Shutting Down the System
Starting a System in Single-Server Mode
Starting the System
The following procedure shows you how to reboot your servers and synchronize them. This
is primarily for dual- or triple-server systems. For steps on starting a system in single-server
mode, see “Starting a System in Single-Server Mode” on page 65.
nBecause the following procedure applies to an entire system that has been shut down, you
must perform all the steps on all servers, except where otherwise indicated.
To start your iNEWS system:
1. Power up or reboot servers to the login prompt.
The servers will display the following line ten times—one per second:
Press any key to continue.
If no key is pressed, the bootup will continue normally after ten seconds. If a key is
pressed, the system displays a message similar to the following:
The default is the SERIAL CONSOLE option, for booting to the iNEWS console. Use
the up or down arrow keys to select another option; however, the other options should
not be used for any reason, unless instructed to do so by Avid Customer Support
personnel. Press Enter to continue.
Starting the System
61
cIf the system was not shut down as described in “Shutting Down the System” on page
63, check the iNEWS system log files for messages indicating that all servers shut down
at the same time. Do not connect servers unless you are sure their databases are
mirrored. If you cannot find messages indicating simultaneous shutdown, or are
otherwise unsure whether the disks are mirrored, call Avid Customer Support for
assistance before proceeding. If the servers are not mirrored, it will be necessary to
bring the system up as a single-server system and go through the re-mirroring process.
See “Starting a System in Single-Server Mode” on page 65 for more information.
cIf the system was taken through a normal shut down according to instructions, the
databases would still be mirrored and you can continue the normal startup procedure.
2. From the PuTTYCS application, select the PuTTY Filter created for sending server
commands to all servers, such as iNEWS Consoles.
3. Log in as a system operator by typing:
so
4. When prompted, type the password.
5. Type:
connect #
The # character acts as a place holder for each server name, allowing you to send a
single command to multiple servers simultaneously. So, typing
connect #
will send
connect a
to server A,
connect b
to server B, and so forth.
When connected, each server displays status messages and the system prompt returns.
Messages similar to the following appears:
connect successful for NRCS-A, starting servers...
A is OFFLINE. ID is NRCS.
System is A. Master is A.
Disk status is OK. The database is OPEN.
Connecting servers provides each server with a unique name and causes each one to
read and interpret the system profile. The servers can work together as a system after
reading the system profile information.
6. (Optional) Check for edit and order locks if you are restarting the system after a power
failure. During a power failure, the system might not have had time to remove edit and
order locks from the database before shutting down.
When you restart the system, remove these locks.
3 Getting Started
62
nChecking for edit and order locks might take time depending on the size of the database. In
an emergency, bypass this step to get the system running. Go back later and remove locks to
provide system access. The system can detect invalid locks and will ignore them.
a. Select the console window for one server, such as server A.
b. Type:
dbclean -x .
The
-x
option tells dbclean to skip queues or directories marked with a skip flag,
reducing the time it takes to run.
The period (
.
) after the
-x
causes dbclean to start at the root directory of the
database, so that it does not miss any part of the database not marked with a skip
flag.
7. From the PuTTYCS application, select the PuTTY Filter created for sending server
commands to all servers, such as iNEWS Consoles.
8. Type:
startup
Information similar to the following appears:
Checking free space...
Sep 10 15:42:51 NRCS msg: System is being configured
database size 10002352,free 9955000=100%,freelist 1991
Starting NRCS programs...
booting device 100
booting server 130
The startup command does the following:
- Causes the master computer (usually server A) to read the configuration file
- Brings each server online so users can log in
- Checks database free space (dbfree)
Shutting Down the System
63
- Starts all devices and utility programs
The console displays device-ready messages (Hot-to-go as each device starts up,
indicating that the device is online and available.
nResources used for iNEWS Workstation, Data Receiver, and rxnet sessions do not print any
messages until a workstation establishes a connection.
Shutting Down the System
If you need to turn off your servers or reboot the system, first shut down the system. Shutting
down the system:
Saves any open stories
Removes any remaining edit and order locks
Ensures that each server’s copy of the database is the same
nBecause the system requires that you shut down all servers at the same time, most steps in
this procedure are performed on all servers simultaneously. Except where instructed to do
otherwise, ensure that you have selected the filter for sending commands to all servers
before performing each step. See “Selecting One or More Servers” on page 55 for more
information.
To shut down your iNEWS system:
1. Broadcast a message to notify users that the system is being shut down. For instance,
type:
broadcast -dl Please log out, system being shut down.
2. From the PuTTYCS application, select the PuTTY Filter created for sending server
commands to all servers, such as iNEWS Consoles.
3. Log out all users.
4. Type:
status
This will display the systems current configuration status; verify that the servers are still
connected to each other and running in the normal AB configuration for dual-server
systems or ABC configuration for triple-server systems. If they are, you may continue
with normal shutdown procedures.
nIf the servers do not all display the same configuration settings—such as “System is
AB”—then the databases on the servers are most likely not mirrored and must not be
brought back up using normal startup procedures. Contact Avid Customer Support before
proceeding.
5. Type:
shutdown
3 Getting Started
64
A message similar to the following appears:
WARNING! This will stop all devices on this computer, and close the
database.
To prevent loss of work in progress, 'logout all' first.
Do you really want to do this (y/n)?
6. To continue, type:
y
and press Enter.
The screen appears similar to the following:
Do you really want to do this (y/n)? y
/exc/shutdown: Stopping all devices
/exc/shutdown: Closing database
The shutdown process stops all workstations, wires, and other devices, and no further
changes can be made to the database.
7. Log in as a superuser, by typing:
su
8. When prompted, enter the password.
NRCS-A\$ su
NRCS-A#
9. When the superuser prompt appears, shut down the system by using a form of the init
command, as shown:
NRCS-A# halt
Broadcast message from root (ttySO) (Fri ...)
The system is going down for system halt NOW!
INIT: Stopping atd: [ OK ]
Stopping keytable: [ OK ]
...
Turning off swap:
Turning off quotas:
Unmounting file systems:
Halting system...
flushing ide devices: hda
System halted.
10. Turn off each server.
To start up the system again, follow the procedure in “Starting the System” on page 60.
Starting a System in Single-Server Mode
65
cIf the system was no shut down as described in this section—such as, as a result of
power failure, operator error, or hardware failure—do not connect the servers because
the database may no longer be mirrored. In such cases, bring up one single server and
go through the re-mirroring process.
Starting a System in Single-Server Mode
If the servers were not operating in their normal system configuration, such as AB in
dual-server systems, or if they were not shutdown using normal procedures according to
instructions in this manual, the databases on the servers may not be mirrored.
cIf the databases are not mirrored, you must not bring the system up using normal start
up procedures as instructed in Starting the System” on page 60 or you will risk
database corruption.
If non-mirrored servers, the system administrator must bring the system up in single-server
mode and then go through the database re-mirroring process. This section provides the steps
for starting a system in single-server mode.
nContact Avid Customer Support for assistance with triple-server systems. It might be
possible to start these systems in a dual-server mode, depending on the circumstances of the
shutdown.
To start the iNEWS system in single-server mode:
1. Power up or reboot the server on which you want the system to run.
2. Select that server.
3. Log in as a system operator by typing:
so
4. When prompted, type the password.
5. Do one of the following:
tTo connect server A as a single system, enter the following command:
connect a single=a
tTo connect server B as a single system, enter the following command:
connect b single=b
nThe syntax
net=a
or
net= b
is also acceptable. If you have a third server, such as server C,
use C in place of A or B. Also, notice in the following sample message that the “System is A”
not AB or ABC.
3 Getting Started
66
Messages similar to the following appear:
Sep 10 16:25:52 inews-a last message repeated 15 times
...
Sep 10 16:26:44 inews-a work:[2034]workserver Hot-to-go
connect successful for NRCS-A, starting servers...
A is OFFLINE. ID is NRCS
System is A. Master is A.
Disk status is OK. The database is OPEN.
NRCS-A\$
6. (Optional) Check for edit and order locks if you are restarting the system after a power
failure. During a power failure, the system might not have had time to remove edit and
order locks from the database before shutting down.
When you restart the system, remove these locks.
nChecking for edit and order locks might take time depending on the size of the database. In
an emergency, bypass this step to get the system running. Go back later and remove locks to
provide system access. The system can detect invalid locks and will ignore them.
tType:
dbclean -x .
The
-x
option tells dbclean to skip queues or directories marked with a skip flag,
reducing the time it takes to run.
The period (
.
) after the
-x
causes dbclean to start at the root directory of the database,
so that it does not miss any part of the database not marked with a skip flag.
7. Type:
startup
Checking free space...
Sep 10 15:42:51 NRCS msg: System is being configured
database size 10002352,free 9955000=100%,freelist 1991
Starting NRCS programs...
booting device 100
booting server 130
The entire newsroom computer system will now be run off the single server. The
commands entered on a single-server system for shutting down are the same as those
used to shut down a dual-server or triple-server system.
To return to a dual or triple-server system, it will be necessary to complete the database
re-mirroring process.
4Users
People in your newsroom must have user accounts to use the iNEWS newsroom computer
system. Each user account has various user traits associated with it that capture information
about the user’s interaction with the system—information such as passwords, keyboard
preferences, and permissions for story editing.
This chapter explains how the system administrator can access and change user account
information from any iNEWS Workstation. However, user traits can also be viewed and
modified at the console. The procedures for using the console are covered in “Managing
Traits at the Console” on page 647.
This chapter contains the following main sections:
Viewing User Accounts
Modifying User Traits
-Changing a User’s Password
-Changing User Preferences
-Setting up Simplified Users
Creating New Users
-Creating a New User Area in News Database
-Adding a New User Account
-Enabing a New User to Receive Mail
Searching for User Information
Removing User Accounts
The User Manager Account
The Database Manager Account
Logging Out All Users
Importing Users from an LDAP Server
Viewing User Accounts
You must be logged on as a superuser or user manager (umanager) to change user traits. For
an explanation of the umanager account and privileges, see “The User Manager Account” on
page 98.
To view traits associated with a particular user account:
1. Select Tools > Options > Users.
The Manage User Accounts dialog box appears.
2. Enter the user name in the User ID field.
nAn asterisk (*) in the User ID field will result in all user accounts listed when you click
Search or press Enter. To search for all users with names that start with a certain letter, type
that letter followed by an asterisk.
3. Do one of the following:
tClick Search.
tPress Enter.
Viewing User Accounts
69
The results of the search appear in the User List field located in the center of the dialog
box. The data provided in the field includes: User ID and Name, last time the user
logged in, whether the user account has superuser privileges, and so forth. The scroll bar
at the bottom of the field may be used to view the rest of the User Account data.
nThe Print User List button will send the User Account data for the results appearing in
the User List field to the printer. There is no option to selectively limit what data is
printed.
4. Do one of the following:
tDouble-click the user name in the User List field.
tClick the name once to select it, and then click the Modify/Display button.
nThe Modify button will appear with the word Display on it if you do not have authority to
modify user accounts. This applies to user managers (umanager) who cannot alter
superuser accounts. Also, the traits shown in the dialog box will appear gray to indicate that
the information is for viewing only.
The Modify User Account dialog box appears.
The dialog box shows user traits associated with the account you chose, such as the
user’s name, read rate, and mail queue name. All user traits shown in the various
sections of the Modify User Account dialog box are explained in detail in “User Traits”
on page 71.
4 Users
70
Modifying User Traits
You must be logged on as a superuser or user manager (umanager) to change user traits. The
superuser account is an iNEWS user account with superuser type access privileges. It is not
the same as the superuser mode used at the console. See “User Traits” on page 71 for more
information. For an explanation of the umanager account and privileges, see “The User
Manager Account” on page 98.
To modify a user’s traits from an iNEWS Workstation:
1. Access the Modify User Account dialog box as explained in “Viewing User Accounts
on page 68.
The Modify User Account dialog box appears.
2. Select or deselect check boxes and fill in the fields in the Queues section of the dialog
box as needed. See “User Traits” on page 71 for more information.
nYou can click the Get from Template button to copy traits from another pre-defined user
account. The template must be selected prior to the start of account modification or the
button will be inaccessible (grayed out). See “Adding a New User Account” on page 90 for
3. Create or change the password, as explained in “Changing a User’s Password” on page
77.
Modifying User Traits
71
4. Click User Preferences and modify settings, as explained in “Changing User
Preferences” on page 77.
5. Click OK to save modifications. The Cancel button closes the dialog box without saving
changes.
User Traits
The Modify User Account dialog box divides each user’s traits into sections, such as Type,
Edit Mode, Queues, and so forth.
These sections are explained in the following summary of all user traits.
User ID and User Name
The User Name field contains the user’s real name. It should not be confused with the User
ID, which the system uses to identify account activity. For instance, a user might have an
account with a User ID
dmitchell
; his real User Name is Dan Mitchell, but he will type
dmitchell
, his User ID, to log on to iNEWS.
4 Users
72
Type
The Type section contains the check boxes that determine what type of user account is
assigned to the user, and consequently, what privileges.
If the check box is selected, the type is applied to that user account.
Edit Mode
The Edit Mode section’s radio buttons set up the condition of the PC keyboard’s Insert
key at log in. The users can still toggle between Insert and Overwrite mode as they work.
Type Description
Superuser A superuser account allows the user complete access to administration
features, such as user accounts, the database, the System directory, and
connect sessions to the console that controls the servers.
Blacklisted A blacklisted account cannot be used to log in to an iNEWS Workstation.
This type is used for special accounts, such as umanager and dbmanager. It is
not intended for standard user accounts. Another practical use for this trait is
to quickly disable an account of someone leaving or someone who works
intermittently.
Simplified A simplified account sets certain access limits, such as the maximum number
of iNEWS Workspaces allowed. See “Setting up Simplified Users” on page
Local Only User accounts flagged as local only cannot be used for session identification
by incoming Community sessions. The generic username is used instead.
Condition Description
Insert The Insert editing mode, when selected, means if a user types text between
two characters, the text is inserted at the cursor position without overwriting
the character to the right of the cursor. This is the more typical selection.
Modifying User Traits
73
Queues
The iNEWS system provides a People directory in the database file structure that lets system
administrators to set up a personal directory and two queues for each user as data storage.
The Queues fields in the Modify User Account dialog box indicate the navigation paths (or
locations) of the user’s personal directory and queues.
nThe actual directory and queues are not created here. The People directory, which can be
customized for your environment through a system dictionary, is provided as part of the
default database. See “Creating a New User Area in News Database” on page 88 for more
information.
Overwrite The Overwrite editing mode, when selected, means each character a user
types replaces the next character to the right of the cursor as the cursor moves
through the text.
Condition Description
Queue Fields Description
Home The Home field contains the path to the directory (folder) where the
Destination and Mail queues are stored in the database file structure.
Destination The Destination field contains the path to the queue provided for the user as a
storage location, such as Notes.
Mail The Mail field contains the path to the user’s Mail queue, which is where all
internal iNEWS mail to that user is kept in the database.
For sites that do not use iNEWS mail, set this field to
SYSTEM.SHREDDER. Also, even if your site uses iNEWS mail, all
template or special accounts (umanager and dbmanager for example) should
be set to SYSTEM.SHREDDER. This does not prevent users from sending
mail, but it does prevent user accounts from receiving mail.
4 Users
74
The Read Rate is the users spoken reading rate in words per minute. The average English
reading rate is 180 words per minute. The iNEWS system takes the read rate from the user
ID named in the story’s presenter field to determine the audio (air) time of a story. This also
applies to the text timing clocks.
Session Features
There are three sections of the Modify User Account dialog box pertaining to features. The
Session Features section defines access to other parts of the system.
If the check box is selected, the feature is applied to that user account.
Configuration Features
The Configuration Features section pertains to the look of the iNEWS Workspace.
If the check box is selected, the feature is applied to that user account.
Feature Description
Media Browse The Media Browse check box determines access to the Media Browse
plug-ins within iNEWS.
Connect Services The Connect Services check box determines access to the Connect to Service
dialog box.
Manage Projects The Manage Projects check box determine whether a user can manage
projects and facets in the system.
Modifying User Traits
75
Queue Features
The Queue Features section pertains to access privileges in the Queue panel of the iNEWS
Workspace.
If the check box is selected, the feature is applied to that user account.
Feature Description
Toolbars The Toolbars check box determines whether the user can create custom
toolbars.
Color Highlights The Color Highlights check box determines whether the user can customize
the highlighting status colors in the queue.
Highlight Read The Highlight Read Stories check box specifies that unread stories in the
queue are highlighted on the user’s screen. The highlight is removed when
the cursor is positioned on the story. This feature only applies to stories in a
queue with the Watch Appends database trait.
Feature Description
Reorder Stories The Reorder Stories check box determines authority to alter the order of the
stories in any queue to which the user has write access.
Create/Kill... The Create/Kill Folders/Queues check box determines authority to create or
delete queues and folders (directories) in the database file structure, as seen
in the Directory panel of the iNEWS Workspace.
Kill All Stories The Kill All Stories check box determines authority to delete all stories in a
single action from any queue to which the user has write access. The data is
actually moved from the selected queue to the DEAD queue where it remains
(and can be accessed) until purged.
4 Users
76
The Password section has two options with which you can set up or force a user to change an
External User
An iNEWS user account can be set as an External User when added to the database via a
setting in the Add New User dialog box. The purpose of the External User account is for the
User ID credentials to be validated on an LDAP server instead of the iNEWS Server.
For this external validation to work, customer domain information must be entered in the
/etc/krb5.conf file during the iNEWS Server installation. For instance, the following excerpt
is an example from the updated iNEWS server installation procedure:
Initializing Kervberos configuration...
The default realm is ‘EXAMPLE.COM’. Do you wish to change it? [y/n] y
Enter the default realm: global.wavd.com
Do you wish to set the default realm to “<domain o LDAP server>”? [y/n] y
Creating certificate...
User Preferences...
The User Preferences button is used to view and/or modify a user’s preferences, such as
keyboard, printer, and confirmation settings. See “Changing User Preferences” on page 77
Option Description
Password The Password button opens a dialog box that you can use to set up or change
Force Change The Force Change check box determines whether the user is forced to change
the assigned password at the next login.
Modifying User Traits
77
Get from Template...
The Get from Template button is only used when copying the traits of one user’s account to
another. See Adding a New User Account” on page 90 for more information.
Changing a User’s Password
The password must be a minimum of five alphanumeric characters (and a maximum of 12
characters) with no spaces. Use the system profile to set or change a required length for all
nSystem administrators cannot retrieve a user’s password, only change it.
To change a user’s password:
1. Click the Password button in the Modify User Account dialog box.
The Change User’s Password dialog box appears.
2. Type the password in the New password field.
3. Confirm the new password by retyping it in the Confirm new password field.
4. Do one of the following:
tClick OK to store the password for saving after all modifications to the user’s
account are done. This will close the dialog box. The process of saving the
password is only completed after the OK button on the Modify User Account dialog
box is also clicked.
tClick Cancel to close the dialog box without saving changes.
Changing User Preferences
System administrators can use the Preferences dialog box to set up default preferences for
users. However, the Preferences dialog box is—by default—accessible to users, so they can
alter these settings at any time. Users, unless their access is limited by the system
administrator, can access the Preferences dialog box to modify their preferences by selecting
4 Users
78
Tools > Options > Preferences at any iNEWS Workstation. To learn how the system
administrator can limit access to this dialog box and its features, see “Setting up Simplified
Users” on page 85.
To change user preferences:
1. Click the User Preferences button in the Modify User Account dialog box.
The Preferences dialog box will appear, containing several tabs.
2. Modify the preference settings on each tab as needed. The settings are described in
detail in “User Preferences” on page 78.
3. Do one of the following:
tClick OK to store the preferences for saving after all modifications to the user’s
account are done. This will close the dialog box.
cThe process of saving the preferences is only completed after the OK button on the
Modify User Account dialog box is also clicked.
tClick Cancel to close the dialog box without saving preference changes.
User Preferences
The Preferences dialog box contains several tabs. These various tabs are explained in the
following summary of all user preferences.
Modifying User Traits
79
Session Tab
The Session tab has two sections, which system administrators can use to set up default user
preferences.
User Preference Description
Keyboard The keyboard drop-down list contains a list of keyboards (or sets of macros)
that can be assigned to the user account as a default for when the user logs in.
The Reload button lets the keyboard assignment take effect without having
the user log off and back on.
Printing The Printing drop-down list contains pre-defined Styles that can be assigned
to the user account as defaults for when the user prints data from an iNEWS
Workstation.
4 Users
80
Confirmations Tab
The Confirmations tab is divided into sections and contains check boxes that determine
whether iNEWS prompts the user to confirm a request before completing the command.
User Preference Description
Saving Story When Saving Story is checked, iNEWS Workstation will display a
confirmation message to save changes before closing an edited story. If you
do not select the Saving Story check box, the system automatically saves
changes before closing stories.
Exit When Exit is checked, iNEWS Workstation will display a confirmation
message when the user attempts to close the iNEWS NRCS program at the
workstation.
Story Operations When Story Operations is checked, iNEWS Workstation will display a
confirmation message before moving a story when you use the mouse to drag
it to its new position.
Queue Operations When Queue Operations is checked, iNEWS Workstation will display a
confirmation message before moving all stories in a queue when you use the
mouse to drag them to their new position.
Queue Reorder When Queue Reorder is checked, iNEWS Workstation will display a
confirmation message before moving a story to a new location in the same
queue.
Story When Story is checked, iNEWS Workstation will display a confirmation
message before deleting a story or stories.
Modifying User Traits
81
Backup Tab
The Backup tab defines the settings for the iNEWS Workstation to automatically back up
work in a current session to a specified location at specific time intervals.
Mail or Message When Mail or Message is checked, iNEWS Workstation will display a
confirmation message before deleting e-mail or instant messages.
Production Cue When Production Cue is checked, iNEWS Workstation will display a
confirmation message before deleting a production cue and its marker from a
story.
nA production cue marker (shown at left) appears in the Story Text
panel.
User Preference Description
User Preference Description
Interval Interval specifies the number of minutes between story backups. The default
is 10 minutes. Set the interval to 0 (zero) minutes to turn off the automatic
backup feature.
Directory Directory specifies the path name—the location in which iNEWS
Workstation should store backup copies of stories. The location should be a
directory (folder) on the harddrive of the local PC/workstation. By default,
the location is the iNEWS program directory, which is only accessible to
computer administrators or power users. Regular Windows users should set
this to My Documents. You can type the path in manually, or click the
Browse button to select the directory from the Browse dialog box.
4 Users
82
Refresh Tab
The Refresh tab sets the seconds for refreshing the screen at the workstation.
nThis preference is unique because it only affects the workstation on which it is set.
Set the number to zero (0) for instant updating—that is, if you do not want to delay
refreshes. A zero delay does require more system and network resources.
Layout Tab
The Layout tab is divided into sections and contains buttons and check boxes that determine
the layout of panels and workspaces in the iNEWS Workstation main window.
Modifying User Traits
83
nUsers can manually override the Preview Lines setting by selecting the Story Preview option
in the View drop-down menu. In the Story Preview dialog box, the user can override the
default setting by typing in a number in the Lines to preview field. This overrides the setting
for the queue while displayed. Once the user exits the queue, the queue’s default setting is
reinstated. If the user wants to return to the default setting manually (as defined in the
queue’s properties), the user can click the Default button in the Story Preview dialog box.
The following figures show the difference between Queue panel displays with and without
Preview lines. The first figure shows the display using the default of seven preview lines, as
defined in the queue’s properties.
User Preference Description
Start in Session The Start in Session field specifies the default session that will appear on
screen when the user logs in to iNEWS Workstation.
Get Current The Get Current button will reset the preferences on the Layout tab to what
was set when the dialog box opened.
Depending on which Arrangement button is selected, the iNEWS
Workstation will display the panels of the iNEWS Workspace accordingly.
Zoom In the Arrangement section, when Zoom is checked, iNEWS Workstation
will display the iNEWS Workspace in zoom mode—that is, zoomed into one
of the three panels: Directory, Queue or Story.
Hide Form In the Arrangement section, when Hide Form is checked, iNEWS
Workstation will display the Story panel with its Story Form panel hidden.
The user can choose to show the Story Form panel by selecting the option to
show the form from the Story drop-down menu.
Horizontal In the Gridlines section, when Horizontal is checked, iNEWS Workstation
will display horizontal gridlines between rows in the Queue panel.
Vertical In the Gridlines section, when Vertical is checked, iNEWS Workstation will
display vertical gridlines between columns in the Queue panel.
Use Default In the Preview Lines section, when Use Default is checked, iNEWS
Workstation will display the default number of preview lines for each story in
the Queue panel as defined by the queue’s properties. When Use Default is
not checked, every queue will display only one line of information per story
in the Queue panel.
4 Users
84
The second figure shows the Queue panel display without preview lines. This is the view
when Use Default is unchecked, unless otherwise specified.
Modifying User Traits
85
Search ResultsTab
The Search Results tab allows you to set the default form used in the Queue panel of the
Search Results workspace.
The iNEWS Workstation will use the form selected from the Use form drop-down list when
displaying the results from searches in iNEWS. The forms you can choose from are those
created and stored in SYSTEM.FORMS. See “Creating Forms” on page 208 for more
information.
Setting up Simplified Users
A simplified user is one that has certain limitations pertaining to the iNEWS Workstation.
As the system administrator, you can define the limitations and then assign them to users.
Only one set of limitations can be defined, which is then applied to all user accounts with the
simplified user trait. In other words, either a user account has the simplifed user trait, with its
designated limitation settings, or it does not.
Some of the Simplified User Settings lock the user’s preferences to those defined by the
system administrator using the Preferences dialog box. See “User Preferences” on page 78
To set up or modify the simplified user limitations:
1. Access the Modify User Account dialog box as explained in “Viewing User Accounts”
on page 68.
2. Click the Simplified UI button.
4 Users
86
The Simplified User Settings dialog box appears.
The dialog box divides the settings into two sections, which are explained in the next
sections of this chapter.
3. Select or deselect check boxes, as required.
4. Click the OK button to save the settings and close the Simplified User Settings dialog
box.
nUse the Reset button to discard changes and reset the check box settings to what they were
when the dialog box opened.
Simplified User Settings
The Simplified User Settings dialog box splits the settings into two sections. These sections
are explained in the following summary of all simplified user settings.
Workspaces Section
The Workspaces section of the dialog box provides settings that pertain to the arrangement
and quantity of workspaces within the iNEWS Workstation’s main window.
Modifying User Traits
87
Application Section
The Application section of the dialog box provides settings that pertain to accessing certain
iNEWS features at any workstation.
Setting Description
Limit Number to When Limit Number to is checked, iNEWS Workstation will prevent the user
from opening more workspaces than the number specified. This limit does
not apply to the workspaces opened using the Urgent Wire and Mail buttons.
However, this does lock the Urgent Wire workspace so the user is unable to
navigate to other queues or directories in that workspace.
Lock Arrange When Lock Arrange is checked, iNEWS Workstation will prevent the user
from altering the arrangement of panels in the Workspace. This disables the
Arrangement buttons on the standard Layout toolbar. The setting is locked
into the default arrangement as defined in the user’s User Account
Preferences.
Lock Layout When Lock Layout is checked, iNEWS Workstation will prevent the user
from altering the layout of workspaces in the iNEWS Workstation main
window. This disables the Layout buttons on the standard Layout toolbar.
The setting is locked into the default layout as defined in the user’s User
Account Preferences.
Lock Zoom When Lock Zoom is checked, iNEWS Workstation will prevent the user from
altering the zoom of panels in the iNEWS Workspace. The setting is locked
into the default as defined in the user’s User Account Preferences.
Setting Description
Lock Toolbars When Lock Toolbars is checked, iNEWS Workstation will prevent the user
from altering the display of toolbars.
Lock Sessions When Lock Sessions is checked, iNEWS Workstation will prevent the user
from creating or altering sessions. The user will be locked to sessions created
prior to the Lock Sessions being applied to the user account.
4 Users
88
Creating New Users
To set up new users in iNEWS, you must complete three separate procedures:
Create areas in the iNEWS database file structure where the user can store notes and
receive mail. See “Creating a New User Area in News Database” on page 88 for more
information.
Add a new user account so that your system recognizes the user. This includes setting up
the user traits associated with the account. See Adding a New User Account” on page
Enable the new user to receive mail by adding him or her to the appropriate group. See
“Enabing a New User to Receive Mail” on page 93 for more information.
nTo ensure a user has appropriate database privileges, the user should also be assigned to the
correct group or groups. For more information, see “Adding Users as Members of a Group”
on page 172.
Creating a New User Area in News Database
While a user account will work without this area, it is traditional for each user to have his or
her own area in the database to keep notes and to receive e-mail. Usually, these areas are
separate queues called Notes and Mail. These queues are kept in a sub-folder—with the
user’s account name—in the People directory.
The common practice is to separate the first level of People sub-folders by using the first
initial of the user’s last name—otherwise, since the system is limited to 250 folders in the
People directory, your site might eventually reach the limit.
Disable Title Entry When Disable Title Entry is checked, iNEWS Workstation will prevent user
access to the Title Entry dialog box, used to enter production cues in stories,
and the Edit Title Entry Template dialog box, used to create CG templates for
the Title Entry feature.
Disable User Prefs... When Disable User Prefs Dlg is checked, iNEWS Workstation will prevent
user access to the Preferences dialog box. The user will be unable to alter
user preferences, such as default printer settings. The user will be locked to
settings already in place at the time Disable User Prefs Dlg is applied to the
user account. See “Changing User Preferences” on page 77 and “User
Preferences” on page 78 for more information.
Setting Description
Creating New Users
89
For instance, the following procedures, the Home directory for our sample user,
DANIELMI, would be: PEOPLE.D.DANIELMI. The Notes and Mail queues would be:
PEOPLE.D.DANIELMI.NOTES and PEOPLE.D.DANIELMI.MAIL, respectively.
nYou must be logged on to iNEWS NRCS with a user account that has authority to create new
directories and/or queues to complete these procedures.
To create a new directory:
1. Using the database file structure in the Directory panel of the iNEWS Workspace, select
the directory under which you want the new folder to be created, as shown in the
following example.
For instance, for user DANIELMI, you would select PEOPLE, then the folder with the
alphabetic name corresponding to the first letter of the user’s name, such as D. This
ensures the new folder will be created in the D directory (folder).
2. Do one of the following:
tSelect Tools > New Folder.
tRight-click on the folder in the Directory panel, and select New Folder from the
A new folder is created under the selected folder. The New-Folder appears at the end of
the list of existing folders.The title, New-Folder, is highlighted, so you can rename it.
3. Type the name of the new folder.
4. Press Enter to save the new folder name. You can now open the new folder (directory)
by double-clicking on it.
You can now create new queues for the user, such as Notes and Mail queues.
4 Users
90
To create a new queue:
1. Navigate to and select the folder created to hold the queue you want to create, such as
PEOPLE.D.DANIELMI.
2. Do one of the following:
tSelect Tools > New Queue.
tRight-click on the folder in the Directory panel and select New Queue from the
A new queue appears under the folder you selected. The New-Queue appears at the end
of the list of existing queues. The title, New-Queue, is highlighted, so you can rename it.
3. Type the name of the new queue, such as MAIL or NOTES.
4. Press Enter to save the new queue name. You can now open the new queue by
double-clicking on it.
Adding a New User Account
When adding a new user account, you have the option of creating the account from scratch
or copying the traits of another user account already in the system. This section covers both
options.
Before you can copy user traits from one user account to another, you must first select the
account you want to copy—that is, select an account to use as a template.
Creating New Users
91
To define an account as a template for copying to other accounts:
1. Select Tools > Options > Users.
The Manage User Accounts dialog box appears.
nIf you do not have superuser privileges, which permits access to the Manage User Accounts
dialog box, the system will prompt you for the umanager password. If the umanager account
does not exist in the system, then access is only allowed to system administrators—that is,
those with superuser privileges. See “The User Manager Account” on page 98 for more
information. Also, see “User Traits” on page 71 for more information on the superuser trait
and its privileges.
2. Search for the user account you want to use as a template for copying user traits. See
“Searching for User Information” on page 93 for more information.
3. Select the User ID when it appears in the search results list.
4. Click Copy. The User ID should appear to the right of the button. When no template is
selected for copying, the words, “No template set,” appears to the right of the Copy
button.
Once a Template User is established, selecting the New User... button will start with the
same configuration as the template user, and selecting Get from Template when
modifying an existing user will set the configuration to that of the template user.
4 Users
92
To add a new user account (either from scratch or by copying the user traits):
1. Select Tools > Options > Users.
The Manage User Accounts dialog box appears.
2. Click New User.
The Add New User dialog box appears.
3. In the User ID field, enter the login name of the user account.
4. (Optional) In the User Name field, enter the user’s real name.
5. (Optional) Modify the various traits you want to apply to the new user account.
nA user’s traits can be modified at the time of creation or afterwards from the iNEWS
Workstation or from the console. For more details about the various user traits, see “User
Traits” on page 71 or “User Traits Console Command Summary” on page 656.
6. Click Add to add the new user account.
Searching for User Information
93
Enabing a New User to Receive Mail
This section gives you the basic steps you need to follow to enable a new user to receive
mail. If you need more information, refer to the information on groups in Adding Users as
Members of a Group” on page 172.
To enable a new user to receive mail:
tAdd the user to a group in SYSTEM.GROUPS. When the group story is saved, the mail
delivery files are updated automatically.
A group story is one that you created in the system for groups in your organization such
as newscasters, staff, or reporters. By adding the user to a group, the user inherits the
group’s security traits.
Searching for User Information
A search capability in iNEWS lets you search for information about a particular user by
specifying a user name and including certain criteria to refine the search. You can specify
any alphanumeric characters in the search. You can use the asterisk (*), which acts as a
wildcard, only as a suffix—not as a prefix or in the middle of a word. Used alone, the
wildcard is equivalent to “all.” Used with additional information, the wildcard serves as a
parameter to the search.
For instance, if you are searching for all user accounts beginning with Dave, type Dave* (no
space).
4 Users
94
To search for information about users:
1. Select Tools > Options > Users.
The Manage User Accounts dialog box appears.
2. Enter the name of the user in the User ID field.
3. Click Search or press Enter.
If you search with a wildcard character and the system finds multiple matches, a results
box appears listing all “hits”. You can specify one by double-clicking on it; this opens
the specified user’s information in another dialog box.
The results of the search appear in the User List field in the center of the dialog box.
To quickly locate a name in the User List, type the name you want; the list will be
positioned to a point matching what you type. User names are not case-sensitive, so you
can use lowercase. To prevent you from having to type the whole name, the system
automatically tries to match the letters you supply with a name in the list. Continue
typing until the system locates the name you want.
4. Click Advanced to refine your search for a user.
The Advanced Search Settings dialog box appears with the All Users setting selected by
default.
Searching for User Information
95
5. Select from the settings to specify additional search criteria. The criteria options are
explained in detail below.
Settings Description
All Users Search through all user accounts on the server.
Superusers Confine the search to user accounts with the superuser attribute.
Non-Superusers Confine the search to user accounts without the superuser attribute.
Blacklisted Users Confine the search to user accounts with the blacklisted attribute.
Non-Blacklisted
Users
Confine the search to user accounts without the blacklisted attribute.
Members of Group Confine the search to user accounts belonging to the security group you
select from the drop-down list.
Users Without
Confine the search to user accounts that do not have passwords.
Simplified Users Confine the search to user accounts that have the simplified user trait.
Non-Simplified Users Confine the search to user accounts that do not have the simplified user
trait.
Local Only Users Confine the search to local system user accounts only.
4 Users
96
6. Click OK to confirm your advanced search setting or click Cancel to cancel it.
7. Click Search to initiate the search.
A progress bar appears if a lengthy search is underway. The results of the search appear
in the User List field in the center of the Manage User Accounts dialog box.
Above the field, iNEWS NRCS will display a brief statement indicating what matched
the search criteria, such as:
All users matching ‘*‘:
Use the horizontal scroll bar at the bottom of the User List field to view the information
headings, such as User Name, Last Login, Read Rate, and so forth.
Non-Local Only
Users
Confine the search to non-local system user accounts only.
Date Range Confine the search to dates you specify in the From and To fields and the
kind of date range:
When the user last logged in
When the user account was created
When the password changed
Specify the date by either clicking the arrow buttons or typing the dates
in ddmmmyyyy format. Indicate the day with two digits, the month with
three letters, and the year with four digits.
Settings Description
Removing User Accounts
97
Removing User Accounts
You must have access to the Manage User Accounts dialog box to remove user accounts. In
other words, you must be logged on as a system administrator—that is, with an account that
has superuser privileges—or successfully enter the user manager (umanager) password to
remove user accounts.
nBefore removing user accounts from the system, remove the users’ names from the
stories in
SYSTEM.GROUPS
. This reduces the potential for mail bounce back errors.
To remove user accounts:
1. Select Tools > Options > Users.
The Manage User Accounts dialog box appears.
nIf you are logged on as a system administrator, the Manage User Accounts dialog box will
appear automatically, following step 1. Otherwise, iNEWS will prompt you for the umanager
password (if that account exists in the system) before allowing access to the dialog box.
2. Enter the name of the user in the User ID field.
3. Click Search or press Enter.
The results of the search appear in the User List field in the center of the Manage User
Accounts dialog box.
4. Select the name of the user you want to remove by clicking the name in the User List
field.
4 Users
98
5. Click Remove.
6. Click OK to remove the user or Cancel to stop the removal.
nAfter removing the user, you will also need to remove the user’s Home directory and the
Notes and Mail queues by deleting them from the system’s database file structure. You can
also use the msgclean command at the console to remove any of the user’s unread messages.
The User Manager Account
A user manager has some special system privileges, but not as many as a system
administrator/superuser. For instance, user managers can add, remove, or change any user
account, except those with the superuser attribute.
There can be only one user manager account in iNEWS; however, several users may acquire
user manager privileges by successfully entering the user manager password when
prompted. Unlike a superuser account, the user manager account is not used to log in to the
system. Users with user manager privileges log in to their own accounts, as usual. When
they need to do user manager tasks, they must access the Manage User Accounts dialog box,
by typing in the user manager password.
To create a user manager account:
1. Create a user account as explained in Adding a New User Account” on page 90.
2. Give the account a User ID:
umanager
.
3. Assign a password to the account.
4. Make the user manager account blacklisted so that no one can use it to log in to the
system.
5. Assign the account superuser status to prevent a user manager (or anyone who does not
have superuser status) from changing the account’s password.
6. Tell the user manager(s) the ID and password for the user manager account.
cFor further security, a write-access group should be assigned to SYSTEM.GROUPS
and only those with user manager privileges should be included in the group. If no
write-access group is assigned to SYSTEM.GROUPS, then all users who know the
umanager password can access the Manage User Accounts dialog box by selecting
Tools > Options > Users. After a write-access group is set up, any user managers with
nonsuperuser accounts must be included in the write-access group for
SYSTEM.GROUPS or they will not be allowed access to the Manage User Accounts
dialog box. See “Groups Tab” on page 137, “Adding Users as Members of a Group” on
page 172, and “Group Access and Usage Restrictions” on page 179 for more
information.
The Database Manager Account
99
The Database Manager Account
A database manager has some special system privileges, but not as many as a system
administrator/superuser. For instance, database managers can add, remove, or change any
database trait on a directory or queue in the iNEWS database from a workstation. Database
managers also have access to the CG Template Editor, used to create and modify template
for the Title Entry feature.
There can be only one database manager account in iNEWS; however, several users may
acquire database manager privileges by successfully entering the database manager
password when prompted. Unlike a superuser account, the database manager account is not
used to log in to the system. Users with database manager privileges log in to their own
accounts, as usual. When they need to do database manager tasks, they must access the
Directory/Queue Properties dialog box. To modify anything in the dialog box, they must
provide the database manager password.
To create a database manager account:
1. Create a user account as explained in Adding a New User Account” on page 90.
2. Give the account a User ID:
dbmanager
.
3. Assign a password to the account.
4. Make the database manager account blacklisted so that no one can use it to log in to the
system.
5. Assign the account superuser status to prevent a user manager (or anyone who does not
have superuser status) from changing the account’s password.
6. Tell the database manager(s) the ID and password for the database manager account.
Logging Out All Users
Sometimes maintenance of the iNEWS system requires you to first log out all users before
completing a certain task, such as shutting down the system. This section explains the best
way to log out all users from the console.
To log out all users:
1. From the PuTTYCS application, select the PuTTY Filter created for sending server
commands to all servers, such as iNEWS Consoles.
2. To prevent users from logging in, take the system offline by typing:
offline
Use
offline silent
if you want to suppress output of messages from new user login
attempts.
4 Users
100
3. Use the broadcast command to send a message warning all users that are logged in that
they must log out and why. If the system will be shut down, include the time it will be
shut down. Here are a few examples:
NRCS-A\$ broadcast -l WARNING\! System shut down at 12PM
NRCS-A\$ broadcast -l LOG OUT\! System shut down at 5 minutes.
NRCS-A\$ broadcast -dl LOG OUT\! System shut down in 10 seconds.
nThe backslash (\) before the exclamation point (!) is required because the exclamation point
is a reserved character in Linux.
The -l (the letter L, not the number 1) after broadcast is to limit the message to local
workstations only and not to users connected through Community. You may also add -d after
broadcast and before the message if you want your message to appear at the workstation as
a popup message. The two can be combined as shown (-dl) to broadcast local popup
messages.
4. At the specified shutdown time, check the system for any users still logged in by
selecting one server and typing:
list s
A message similar to the following appears:
G505 miller A
G500 allen B
G507 stevens A
R801 stevens A
A connect session will show up as an ‘R’ device. The system administrator must notify
them of the shutdown by some other means, such as by telephone.
cYou must ensure that all users are logged out if shutting down the system. If a user is in
a connect session when the system is shut down, the user’s workstation stops, the
session is disconnected, and any unsaved work is lost. Ensure any connect session users
have logged out before you continue the shutdown procedure.
5. To stop a connect session, select the appropriate server and then use the following
format of the stop command:
stop <device number>
.
For instance, to stop the connect session (
R801 stevens A
) that was shown in the
previous example, type:
stop 801
6. From the PuTTYCS application, select the PuTTY Filter created for sending server
commands to all servers, such as iNEWS Consoles.
7. Log out all users by typing:
logout all
Importing Users from an LDAP Server
101
nIf a user is editing a story, the system saves the file and then logs out the user. The logout
command will not log out users who are in connect sessions.
Importing Users from an LDAP Server
With iNEWS, you can import users from LDAP servers. For sites using LDAP servers, there
are many ways of acquiring a list of LDAP users, various applications that can export LDAP
information in LDIF and/or CSV formats. The procedure in this section is one option.
To import users from an LDAP server:
1. Find domain and currently logged in LDAP server.
a. In a Windows MSDOS prompt from local computer, run the command:
echo %UserDnsDomain%
Example output:
GLOBAL.WAVD.COM
b. Run the command:
echo %LogonServer%
Example output:
\\MSN-DC01
c. From the output given, combine the results to make up the name of the logged in
LDAP server on the domain. For example, using the previous sample output:
msn-dc01.global.wavd.com
2. Find LDAP server on the domain to get the port number.
In a console session on the iNEWS Server, run the command in the following format:
dig +short-t srv_ldap._tcp.<User DNS Domain>
The User DNS Domain is the output obtain in the previous step of this procedure. For
instance, type:
dig +short-t srv_ldap._tcp.global.wavd.com
Example output:
0 100 389 kai-dc01.global.wavd.com
0 100 389 ldn-dc01.global.wavd.com
0 100 389 msn-dc01.global.wavd.com
These sample results show all LDAP servers on the domain. The third set of numbers in
the results is the port number; in this case, it is 389.
3. Search LDAP server from the iNEWS Server and create output file of users.
a. Obtain Kerberos ticket-granting ticket by running the command:
kinit <windows user account name>
4 Users
102
b. When prompted, provide the Windows domain password. This will result with the
account being cached on the iNEWS Server so the credentials can be used by the
ldapsearch function.
c. Create a script file to search an LDAP server by starting a document on the local
For example:
ldapsearch\
-H ldap://msn-dc01.global.wavd.com:389 \
-b DC=global,DC=wavd,Dc=com \
“(&(objectClass=person)(sAMAccountName=bri*)(sAMAccountType
=80 5306368))” sAMAccountName cn sn mail objectclass \
kdestroy
In the example, ldapsearch\ is the ldap command. The -H line is a URL for the AD
server. The port number (389) shown in the example is the same sample port used in
previous steps of this procedure. The -b line is the searchbase. It is possible that
DC=global is not needed.
The last line of the search is the query followed by the attributes that you want to
see. You only need samaccountname and cn. The example is a set of three matching
criteria that are joined together via the Boolean ampersand (&). The syntax is to
enclose each term in parentheses and to prefix a set with the Boolean operator. So
you see the ampersand (&) before the 3 criteria and the set is enclosed in
parentheses.
This example search limits the user account names, “sAMAccountName”, to those
starting with “bri”. The “sAMAccountType” value is a Windows defined value for a
user account. It might not be needed in the script you create, but note that the last
term appears as if it has a carriage return. It does not have a carriage return before
=80—it only appears that way because of margin settings for this document. Make
sure the script that you create does not have carriage returns either.
d. Name the .txt file what you want, minus the tag (.txt). Copy script file from
Windows workstation to /tmp/ directory on the iNEWS Server, using the WinSCP
ftp utility.
e. Convert the script file to linux via a PUTTY session to the iNEWS Server. Go to the
/tmp/ directory by typing
cd /tmp/
, and then run Dos2Unix by typing:
dos2unix <name of script file>
f. Run the script file to see it return results by typing:
sh-x /tmp/<name of script file>
Importing Users from an LDAP Server
103
Example results:
+ ldapsearch ldap://msn-dc01.global.wavd.com:389 -b
DC=global,DC=wavd,DC=com
'(&(objectClass=person)(sAMAccountName=bri*)(sAMAccountType=8053
06368
))' sAMAccountName cn sn mail objectclass
ldap_initialize( ldap://msn-dc01.global.wavd.com:389/??base )
nThe utraits user input will only import the cn and sAMAccountName attributes, shown as
bold italics below.
# extended LDIF
#
# LDAPv3
# base <DC=global,DC=avidww,DC=com> with scope subtree
# filter:
(&(objectClass=person)(sAMAccountName=bri*)(sAMAccountType=80530
6368))
# requesting: sAMAccountName cn sn mail objectclass
#
# John Doe, Users, Engineering, AVID Technology Inc,
global.wavd.com
dn: CN=John Doe,OU=Users,OU=Engineering,OU=AVID Technology
Inc,DC=global,DC=wavd,DC=com
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: user
cn: John Doe
sn: Doe
sAMAccountName: jdoe
mail: john.doe@wavd.com
# Jane Smith, Users, North America, AVID Technology Inc,
global.wavd.com
dn: CN=Jane Smith,OU=Users,OU=North America,OU=
AVID Technology Inc,DC=global,DC=wavd,DC=com
4 Users
104
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: user
cn: Jane Smith
sn: Smith
sAMAccountName: jsmith
mail: jane.smith@wavd.com
# search reference
ref:
ldap://DomainDnsZones.global.avidww.com/DC=DomainDnsZones,DC=glo
bal,DC=wavd,DC=com
# search result
search: 2
result: 0 Success
# numResponses: 4
# numEntries: 2
# numReferences: 1
4. After the output is verified as good, dump exported users to file by typing:
sh -x /tmp/<script file> > /tmp/<output file>
nIt will appear as if the command is halted. Technically, it is halted. What you don’t see is the
“Enter LDAP Password:” prompt for the password used in the -D parameter of the script
file. So after you enter the command, when it halts, enter the password. In a few moments,
the linux prompt will be back, and the file will be placed in /tmp/directory.
This file is then used to import new users into iNEWS.
5. Import.
a. Users from output file.
Users in output file are imported into iNEWS using the utraits command.There are
two file types that can be imported, csv and ldif. Common output of active
directory query will be ldif. Sometimes customers might export their users to csv
file eliminating the work above. You can also use the ‘list’ option in utraits to create
a comma separated output from ldif output, or just use ‘list’ to verify the data to be
imported into iNEWS. In each scenario a template user that already exists in the
Importing Users from an LDAP Server
105
iNEWS system is used as the clone user. Every user in the output file will be
imported using the template user’s settings and password. If you choose to give
these imported users a different startup password than what is used by the template
user, you will need to include the ‘password’ option of utraits as well. Otherwise
imported users will first login using the password of the template user, then be
forced to create their own unique password.
tImport users into iNEWS from output file, using the standard ldif format.
Type:
utraits ldif:<output file> clone <template user> password
extern-user +eu
tImport users into iNEWS from .csv file.
Type:
utraits csv:<output file> clone <template user>password
extern-user +eu
Example output for either import method:
2 user records added
Running a
list u j*
command or logging in as the users will verify that the users
are now imported into the system.
nTo create a .csv file from an ldif output file, run the utraits command in the following format:
utraits ldif:<ldif output file> list > <new csv file>
.
b. Group names from output file.
- Run the query script without the OU values.
- Note the OU values from the query results as these will tell you the group
names.
- Modify -b value to include OU group data.
- Save script and rerun.
You now have a query that will segregate based on groups.
6. Use the kdestroy command to delete the Kerberos ticket-granting ticket.
4 Users
106
5The Database: Directories, Queues,
and Stories
All relevant iNEWS information—except the system software and the Linux files—is stored
in the iNEWS database. This database contains stories, queues, and directories or more
specifically: scripts, rundowns, e-mail, messages, users, groups and their memberships, and
any other kind of information entered into the system. Some database maintenance, such as
altering the database file structure and traits, can be done from the console or from any
iNEWS Workstation. This chapter focuses on maintenance tasks at the workstation when
possible. However, when a task can be done at both the workstation and console, the console
information is provided as an appendix in this guide. See procedures for using the console in
“Managing Traits at the Console” on page 647.
This chapter contains the following main sections:
Overview of the iNEWS Database
Restrictions to Directory or Queue Creation
Creating a New Directory
Creating a New Queue
Creating a New Story
Renaming a Directory or Queue
Deleting a Directory or Queue
Recovering a Killed Story
Viewing Database Traits
Changing Database Traits
Database Purge Intervals and Limits
Identifying Locked Queues and Stories
Removing Locks from a Workstation
Unbusy Stories and Queues
Overview of the iNEWS Database
The iNEWS database is where all the data, such as scripts, rundowns, user accounts, and so
forth, are stored. The database is structured in a way to promote ease of maintenance. For
instance, it contains a file structure made up of directories, that contain other folders or
queues, which in turn contain stories. It is similarly to a filing cabinet.
In iNEWS, the database file structure—directories and queues—can be seen (depending on
your access privileges) in the Directory panel of the iNEWS Workspace. Directories, also
known as folders, are indicated by manila folders, such as the People directory in the
previous graphic. Queues are indicated by three overlapping pieces of paper, such as the
nIf your site uses the Projects feature of iNEWS, tabs will appear in the Directory panel
letting you select whether you want to view the iNEWS database file structure via the
Directory tab or a list of defined projects via the Project tab. For more information on the
Projects feature, see “iNEWS Projects” on page 483.
The scripts, notes, e-mail, news stories, and other kinds of information are all called stories;
each story is contained in a particular queue, and each queue in a single directory. A
directory can also be contained within another directory in which case it would be called a
subdirectory or sub-folder of that directory.
Directories and queues have database traits that determine how the system manages the
stories they contain, and also what actions users can perform with those stories.
Restrictions to Directory or Queue Creation
109
For instance, by modifying the database traits of a particular queue, you can:
Set its stories to read-only
Restrict who can read them
Enable the system to routinely purge stories in the queue older than a certain number of
days
Database traits are used in conjunction with the user traits discussed in “Users” on page 67.
For instance, stories in a queue that has a read group specified can be read only by users who
are members of that user group.
Restrictions to Directory or Queue Creation
Before you can modify the database traits of queues or directories, the queues and
directories must exist in the database. If they do not, you can create them from the iNEWS
Workstation. However, there are certain restrictions you should be aware of when creating
new directories and queues.
The total path name of a directory, including the separator characters (.), cannot exceed
60 characters.
The total path name of a queue, including the separator characters (.), cannot exceed 62
characters.
Each branch of a path name—that is the name between periods—cannot exceed 20
characters.
The number of directory levels available is limited to 31.
You cannot use a space or period in directory or queue names.
The system has a limit of 250 queues per directory.
nThe 250 limit also applies to first-level sub-folders in a directory. If you need more than 250
in a directory, such as employee folders, create alphabetic sub-folders on the first level, then
place the personal folders in the matching sub-folder. For instance, in a given directory, you
could have 26 sub-folders, each with one of the 26 letters of the English alphabet as a name.
This enables you to have 250 personal folders in each of the 26 alphabetic sub-folders;
that’s enough personal folders for up to 6,500 employees. See “Creating a New User Area in
News Database” on page 88 for more information.
cWhile punctuation marks can be used in path names, Avid strongly recommends their
use be limited to dashes and underscores only to avoid confusion for FTP clients, like
teleprompters, accessing the database. It’s best to limit path names to 0-9, A-Z, hyphen
(-), and underscore (_) characters only because using anything else will have
consequences for console commands and could affect system functioning.
5 The Database: Directories, Queues, and Stories
110
Ordinarily, directories and queues are listed in alphabetical order within their parent
directory. However, you can add items to a directory in a different order. For instance, if you
had directories for each month in the Futures directory, you would want them to appear in
order by month (January, February, and so on). To do this, turn on the sequential database
trait for the parent directory before you create the new items. See “Database Traits
Summary” on page 130 for more information.
Creating a New Directory
If you are creating a new first-level directory, be sure to select the server rather than a
directory or folder as explained in this procedure.
To create a new directory (folder):
directory. This ensures that you have full access to the database.
2. Using the database file structure in the Directory panel of the iNEWS Workspace, select
the directory under which you want the new folder to be created, as shown in the
following example.
For instance, you could select the Shows folder if you want to add a new directory for a
10 PM show. After the new sub-folder (10P) is created, you can create queues or
additional sub-folders in it.
3. Do one of the following:
tSelect Tools > New Folder.
tRight-click on the directory—or server, if you are creating a new first-level
folder—in the Directory panel, and choose New Folder from the context menu.
A new folder is created under the selected folder. The New-Folder appears at the end of
the list of existing folders.The title, New-Folder, is highlighted, so you can rename it.
Creating a New Directory
111
4. Type the name of the new folder, such as
10P
.
5. Press Enter to save the new folder name. The newly created folder will inherit the
database traits of its parent directory initially. You can open the new folder by
double-clicking on it.
nOnce created, directories cannot be renamed from the iNEWS Workstation. If you incorrectly
name a newly created directory, delete it and recreate it with the appropriate name. See
“Renaming a Directory or Queue” on page 121 or “Deleting a Directory or Queue” on
After you create a directory, you can configure its properties by right-clicking on the queue
and selecting Properties. A quick way to apply properties is to use a template. For more
information on copying properties from templates, see “Directory/Queue Properties Dialog
Box” on page 130.
5 The Database: Directories, Queues, and Stories
112
Creating a New Queue
Similar to creating a new directory, you can create a new queue from an iNEWS
Workstation.
To create a new queue:
1. Navigate to and select the directory (folder) created to hold the queue you want to
create.
For instance, select the Shows folder, then the 10P folder, if you want to create new
queues, such as the Rundown and Master queues for the 10PM show.
The new queue will be created in the folder you select.
2. Do one of the following:
tSelect Tools > New Queue.
tRight-click on the folder in the Directory panel and choose New Queue from the
A new queue appears under the folder you selected. The New-Queue appears at the end
of the list of existing queues.The title, New-Queue, is highlighted, so you can rename it.
Creating a New Queue
113
3. Type the name of the new queue, such as
RUNDOWN
or
MASTER
.
4. Press Enter to save the new queue name. The newly created queue will inherit the
database traits of its parent directory initially. You can open the new queue by
double-clicking on it.
nOnce created, queues cannot be renamed from the iNEWS Workstation. If you incorrectly
name a newly created queue, delete it and recreate it with the appropriate name. See
“Renaming a Directory or Queue” on page 121 or “Deleting a Directory or Queue” on
After you create a queue, you can configure its properties by right-clicking on the queue and
selecting Properties. A quick way to apply properties is to use a template. For more
information on copying properties from templates, see “Directory/Queue Properties Dialog
Box” on page 130.
Outgoing Mail Queue
When someone sends e-mail, the first thing your system does is move the mail to the
outgoing mail queue, usually called SYSTEM.MAIL.OUT.
nThe outgoing mail queue’s name is defined in
/site/dict/queues
. When your system was
installed, the outgoing mail queue was defined in this dictionary as SYSTEM.MAIL.OUT. To
change this name, modify the dictionary entry in
/site/dict/queues
. The token used to
define the outgoing mail queue is Q_MAILOUT. See “System Configuration” on page 255
for more information on editing system files.
Mail always uses the form that is assigned to the outgoing mail queue. See “Mail Form” on
After mail arrives in that queue, a utility program known as the mail server processes and
sends it to its intended destination. If the outgoing mail queue, SYSTEM.MAIL.OUT, does
not exist in the System directory, the mail server cannot distribute e-mail. To create this
queue, follow the instructions provided in “Creating a New Queue” on page 112, making
The queue’s name should be “Out.
The queue should be located in the Mail folder, which is in the System directory. If the
Mail folder (directory) does not exist, create it. See “Creating a New Directory” on page
Moreover, the Out queue’s read group must be set properly for the mail server to process
mail correctly. See “Read Group” on page 181 for more information. Although not required,
you can restrict read permission for the queue SYSTEM.MAIL.OUT to a group that has no
5 The Database: Directories, Queues, and Stories
114
users. Doing so does not interfere with anyone’s ability to send e-mail, but it prevents
anyone (except superusers) from reading mail in SYSTEM.MAIL.OUT waiting to be
processed. See “Restricting Both Reading and Writing” on page 184 for more information.
Also, for your system to notify the mail server when new mail arrives in
SYSTEM.MAIL.OUT, that queue must have the same mailbox number assigned to it as the
mail server. If the queue does not have a mailbox or has an incorrect one, your system has no
way to notify the mail server when there is mail to process. See “Maintain Tab” on page 139
nThe mailbox number is not solely related to e-mail. This database trait lets you link a queue
to a server (utility program) so that the system notifies the server program when stories are
added to or edited in the queue. See “Maintain Tab” on page 139 and “Servers” on page
Your system must also have a dead letter queue, usually called SYSTEM.MAIL.ERROR.
This queue is a final destination for any e-mail that your system is unable to deliver to the
nThe dead letter queue’s name is defined in
/site/dict/queues
as SYSTEM.MAIL.ERROR.
To change the name of the queue, modify its dictionary entry in
/site/dict/queues
.
If SYSTEM.MAIL.ERROR does not exist, any mail that the mail server cannot deliver or
return to the sender is put in the Dead queue. To create SYSTEM.MAIL.ERROR, follow the
instructions provided in “Creating a New Queue” on page 112, making these adjustments:
The queue’s name should be “Error.
The queue should be in the Mail folder, located in the System directory. If the Mail
folder (directory) does not exist, create it. See “Creating a New Directory” on page 110
Returned mail may contain sensitive information. Therefore, restrict read permission for
SYSTEM.MAIL.ERROR to a group that has no members. Then, only superusers can read
mail in the queue. See “Read Group” on page 181 for more information. Examine the queue
occasionally to see whether any mail exists.
Creating a New Queue
115
Search Queues
A search queue is a special queue that stores a pre-defined query of indexed queues, along
with its own queue form and read group. When users with proper read access open a search
queue, a fast text search (FTS) is activated, and the results are delivered to the workspace in
the Queue panel instead of the Search Results pane. The results can then be copied, moved,
deleted, and edited from the workspace. How fast the results are returned depends on the
speed of your FTS system, the size of your index, and the number of areas that is being
searched, but the usual timeframe is between one and 15 seconds.
To create a search queue:
1. At an iNEWS Workstation, in the Directory panel, right-click on a folder in which you
want the search queue created.
2. Select New Search Queue.
The New Search Queue dialog box appears.
3. Type the name of the new search queue and click OK. The naming restrictions for
search queues are the same for those of directories and other queues.
The Search Queue Setup dialog box opens with the name of the search queue appearing
in square brackets in the title bar. For instance, CRIME is the search queue name in the
following sample image.
5 The Database: Directories, Queues, and Stories
116
4. Select the indexed queue or queues you want to search from your site or a Community
site, if available. To choose multiple queues, press and hold the Control key while
clicking on your selections.
5. Use the Search For area of the Search Criteria tab to set the filters for your search.
Otherwise, you can type in your query using the Raw Query Editor.
If using the Raw Query Editor, you should be familiar with syntax and operators used in
Find All searches, since they are the same for defining raw queries. For instance, the
following characters are used for the operators: And, Or, And Not, and Has Not.
Operator Character
And Ampersand (&)
Or Pipe symbol ( | )
AndNot Caret symbol ( ^ )
Has Not Exclamation mark (!)
Creating a New Queue
117
Parentheses are used to specify evaluation order. For instance, you want to search for
stories that mention either Hillary or Bill Clinton, but you only want stories that do not
also mention their daughter, Chelsea.
You could enter:
(Hillary & Clinton) | (Bill & Clinton) &!(Chelsea)
The combination &! accomplishes the same thing as the caret symbol (^) would in a
query. Another example is a query that searches for stories about domestic policies or
domestic agenda, but not domestic abuse. In this example the query might be written
this way:
(domestic & agenda) | (domestic & policy) ^ (domestic & abuse)
An asterisk (*) may be used as a wildcard for partial spellings, such as
airp*
to find
stories with words such as airport, airplane, and airplay.
6. Use the Date Search area to define a time frame for the query; you can search by the
date a story aired or was created, or by last date a story was modified.
7. (Optional) Maximum hits can also be altered in the Search Queue Setup dialog box. The
default is 10. When a user opens a search queue, the search’s result count is displayed in
the status bar.
8. Click Save to save your new search queue. It will appear in the Directory panel.
Search queues are distinguished from other types of queues by the icon. For search
queues, a magnifying glass icon appears, as shown at left.
9. After the search queue is created, by default it will use the queue form and read group
already associated with the parent directory in which the search queue was created. You
can view these properties or modify them by doing the following:
a. Right-click on the new search queue in the Directory panel.
b. Select Properties.
An abbreviated version of the Queue Properties dialog box opens, showing only the
Forms and Groups tabs.
5 The Database: Directories, Queues, and Stories
118
Only the queue form property on the Forms tab may be altered for a search queue.
Though the other properties are displayed, they are read-only and not used by the
system.
On the Groups tab, only the read group property may be altered. A setting of
!<none>
means no read group is defined; therefore, there is no restriction, and
every user can see the search queue.
Creating a New Story
119
c. Click OK. If any settings were modified, they will be saved. To close without
saving, click Cancel.
nFor more information about groups or forms, see “Groups” on page 161 or “Forms” on
page 207. See also “Database Traits Summary” on page 130.
Viewing Search Queue Information from the Console
A system administrator can view some information about search queues from the console,
by using variations of the list command.
To view information about a search queue:
tUse the following format:
list sq -v <search queue name>
For instance:
NRCS-A\$ list sq-v news.football
NEWS.FOOTBALL query id:10522758
{MaxFound=100[SPIDEY]WIRES.ALL}((football))
For more information, see “list sq” on page 530.
Creating a New Story
In addition to opening existing stories, you can create new stories in a queue.
To create a story:
1. Open the queue in which you want to create a story.
2. Position your cursor in the queue below where you want the new story created.
3. Do one of the following:
tSelect File > New Story.
tPress Ctrl+N.
tPress the Insert key.
A new queue entry appears in the Queue panel as a blank row, and a blank story appears
in the Story panel.
4. In the Slug column of the Queue panel, enter the new story’s title.
5. Enter any other important information in the remaining columns for the new story.
6. In the Story panel, enter the story’s text.
5 The Database: Directories, Queues, and Stories
120
nAvid iNEWS supports creating story links. When focus is on a story, the context menu and
the story menu have available the Copy story link to clipboard option. When this option is
selected, it creates a story link on the user’s clipboard. This link can be pasted into another
story and will appear as:
inews://<server>/<path>/<story>
. Clicking the link will
create a new workspace displaying the linked story.
Using Script Templates
Script templates are templates created by an administrator for users to quickly insert
predefined text into stories. The database structure for script templates is the same as the
structure used for forms and lists:
SYSTEM.SCRIPT-TEMPLATES.<first letter>.<name>
For example, if a standard weather story has a set of production cues and presenter text that
are always the same, you can create a story that will be a script template in
SYSTEM.SCRIPT-TEMPLATES.W.WEATHER. In this story, place the standard text,
presenter text, and production cues found in standard weather stories. After the template
story is saved, the template is available to users via the Story menu or through an option in
the Story Text sub-panel’s context menu.
To use a script template:
1. Right-click in the Story Text sub-panel.
2. Select Insert Script Template. The Template dialog box appears with a list of all
available templates.
3. Enter the name or select the template from the list.
4. Click OK.
After the template is chosen, the template is inserted in the story’s body at the cursor
position.
Renaming a Directory or Queue
121
nScript templates can be used to replace the use of complex macros to insert reusable
material in stories.
Renaming a Directory or Queue
You cannot change the name of a directory or queue from an iNEWS Workstation. However,
you can rename one from the console. All traits are preserved when a folder or queue is
renamed.
cDo not rename queues on an active database. Do not run directory or queue
modification console commands (such as dbvisit or dbtraits) at the same time as the
rename command.
To rename a directory or queue in the database:
1. At the console, enter superuser mode.
2. Select all computers.
3. Take the system offline by typing the command:
offline
.
4. Broadcast a message instructing users to log out.
5. Log out all users on the system before renaming a queue or directory. This ensures that
no stories are open for editing.
cIf users are not logged out, changes to stories may not be saved after the queue or
directory is renamed. It is often most efficient to make several name changes at once.
See “Logging Out All Users” on page 99 for more information.
6. Type:
stop all
. This command stops running all utility programs—known as
servers—wire programs, and devices.
7. Select one computer.
8. Type the rename command to rename the folder or queue. Use the following format:
rename [-v|-r] <from> <to>
For instance, to rename your People folder to STAFF, select one computer and type:
NRCS-B# rename people staff
A message similar to the following appears:
Do you really want to rename PEOPLE
and all its sub-directories to STAFF ?
56 records will be modified [y/n]:
5 The Database: Directories, Queues, and Stories
122
To display a console message for each renamed folder and queue, include the -v (for
verbose) option with the rename command, such as:
NRCS-B# rename -v people staff
cIf an attempt to rename a folder or queue was interrupted by a system crash, complete
it by re-entering the same command with the -r option. Use this option only to resume
an interrupted renaming—at any other time, its use will corrupt the database.
9. To continue with the renaming, type:
y
. A message similar to the following appears:
56 records will be modified [y/n]: y
Updating directory names...
56 directories renamed
The system verifies that the queue or folder you specified exists, and it creates new
folders necessary to complete your command (such as STAFF in this example). If you
choose a pathname over 63 characters, the following appears:
TO: name too long
nBefore modifying files, the system checks for name length overflow. If any of the
directory/queue names exceed their maximum length, no changes are made.
10. A verification request appears:
Do you want to update the user file (MAIL, HOME, DEST)? [y/n]:
The user file is where the names of users’ mail queues, home folders, and automatic
destinations are stored. If you answer y, any item affected by renaming is changed
automatically. If you answer no, you must change them yourself. Typically, answer yes.
Do you want to update the user file (MAIL, HOME, DEST)? [y/n]: y
23 user records modified
11. Manually update any other references on the iNEWS system to the renamed folders.
nUpdate the references while the system is unavailable to users. Failure to update any
references affected by renaming a folder or queue can cause problems with system
operation.
These references can include:
- Command bar icons set up by users
- Your system’s service table
-Dialogs
Deleting a Directory or Queue
123
- Keyboard description stories
- Server or Rx/Tx link job lists
- Wire distribution or keyword stories
- Your system’s queue dictionary (/site/dict/queues)
12. Select all servers.
13. Restart all devices by typing:
restart all
. You will see Hot-to-go messages as each
device starts.
14. Bring the system back online by typing:
online
. This allows users to log in.
15. Press Ctrl+D to leave superuser mode.
Deleting a Directory or Queue
If a queue or story is locked, unlock it first before deleting it from the database.
Ideally, each directory or queue should be empty of other directories, queues, and stories,
before it is deleted, but it is not required.
cIf a directory contains sub-folders or queues when you attempt to delete it, iNEWS will
prompt you for confirmation. If you affirm the deletion, the directory and all its
contents will be deleted from the system. Caution should be taken so that sub-folders
and sub-queues are not inadvertently deleted.
To delete a directory or queue from the database:
1. Log in as a system administrator unless you have write access to the queue or directory.
2. Select the directory or queue you want to delete.
3. Do one of the following:
tSelect Tools > Delete Folder (or Delete Queue).
tRight-click on the directory or queue, then select Delete Folder (or Delete Queue)
from the context menu.
Recovering a Killed Story
You can recover a story that has been killed—moved to and currently resiing in the Dead
queue—from any iNEWS Workstation.
5 The Database: Directories, Queues, and Stories
124
To retrieve a story from the Dead queue:
1. Log in as a system administrator—that is, with a superuser account. This ensures you
stories within it are set to retain their original read and write permissions.
2. Navigate to the Dead queue in the Directory panel and open it by double-clicking on it.
3. Locate the story you want to recover in the Dead queue by scanning the list of stories
displayed in the Queue panel for the story title (slug) or using the Find or Find All
command. The Dead queue cannot be indexed, so you cannot use the Fast Text Search
feature.
4. Select the story or stories you want to retrieve by doing one of the following:
tClick on the selector button located to the left of the story’s row in the Queue panel.
The entire row is highlighted when selected.
tMove the cursor to the row and press Shift-Spacebar.
tClick on each row’s selector button while holding down the Control (Ctrl) key to
select multiple stories. The Shift key can be held down if you want to select all story
rows between two mouse clicks.
5. Copy the selected story (or stories) to the new location by doing one of the following:
tClick on and drag the highlighted selection to another queue in the Directory panel
and release. The selected stories will be copied to the new queue location.
tUse the Copy and Paste buttons or the Edit menu options to copy and paste the
highlighted selection into a new queue location.
tUse the Duplicate command to copy the highlighted selection to another
location—particularly if the Dead queue is read-only.
tDrag the story or stories from the Dead queue into another queue in another
workspace. This lets you position the story or stories where you want them.
Viewing Database Traits
You can get information about your iNEWS database from both the iNEWS Workstation and
the console. Which one you use depends on what information you want to view.
Information Wanted Source to Use
Information about a directory or queue iNEWS Workstation
Information about several directories or queues
simultaneously
iNEWS Console
Viewing Database Traits
125
This section provides procedures for viewing database traits for directories or queues from
either the workstation or the console. For more information about getting information on
stories, see “Viewing Information about Stories” on page 126.
To view database information about directories or queues from the console:
tUse the following format of the list command:
list d <folder/queue name>
nThis command has a verbose option,
list d-v
, which gives you more detailed information.
To view database information on a specific directory or queue from an iNEWS
Workstation:
1. Log in to iNEWS at a workstation.
2. Open an iNEWS Workspace.
3. Navigate to the directory or queue you want in the Directory panel.
4. Right-click on the name of the directory or queue.
5. Select Properties in the context menu.
The Directory/Queue Properties dialog box shows you the properties (traits) for the
directory or queue you selected; however, its look can vary. For instance, the Locks tab
does not appear when viewing properties of directories. If you are not logged in as a
system administrator, and no database manager account was created in iNEWS, the
dialog will appear like this:
Information about stories in the database iNEWS Console
Information Wanted Source to Use
5 The Database: Directories, Queues, and Stories
126
The options in the dialog box appear gray, indicating they are for viewing only and
cannot be altered. Any user can view the traits of directories and queues in the iNEWS
database from a workstation.
If a database manager account exists, then a Database manager login button will appear
in the bottom left corner of the dialog box. See “Changing Database Traits” on page 145
nFor more information about the various database traits available from the iNEWS
Workstation, see “Database Traits Summary” on page 130.
Viewing Information about Stories
The list q command lists story information at at the console for any of your system’s queues.
The basic format of the command is as follows:
list q <queue name> [<record limit>]
nThe list q command has a verbose option that gives you more detailed information. For
instance, a verbose list, such as
list q-v
, includes read and write group information for
each story in the queue. Read and write groups are explained in “Groups” on page 161.
Also, see “Managing Traits at the Console” on page 647.
The <record limit> specifies the number of stories from the queue you want to list. Queues
might contain thousands of stories so a command without a specified <record limit> might
scroll large amounts of output. For instance, to limit the list to the first three stories in
PEOPLE.CAROLYN.NOTES, type:
list q people.carolyn.notes 2
Viewing Database Traits
127
A message similar to the following appears:
PEOPLE.CAROLYN.NOTES.SEARCH id=449889
rec quick index LHDM-WObfpRmF f.id time modified-time
2 pm-chronology --DM-W------- 457243 165 Jul 10 16:16:39 2010
3 pm-thumbnails --DM-W------- 487595 163 Jul 10 16:21:17 2010
By default, the stories are listed in chronological order with the oldest story first.
The one-letter flags (
LHDM-WObfpRmF
) after the quick indexes provide current status
information. The flags are:
You cannot change any of these flags from the console, except the edit-locked status, which
you can remove from a story with the unbusy console command. For instructions, see
“Unbusy Stories and Queues” on page 156.
To list information for a particular story:
tUse the following format of the list command:
list qindex=<index value> q <queue name>
The index value is the value of the selected sort field of the story you want to list. This
value is typically the text found in the title field, but you can set different fields as the
index field.
For instance, to get story information for a story called Nomad in the queue
PEOPLE.SMITH.NOTES, type:
list qindex=nomad q people.smith.notes
Flag Status Information Flag Status Information
L Locked b Story’s body (text) is edit locked.
H Held f Story’s fields are edit locked.
D Duplicated p Story’s production cues are edit locked
M Modified R Read only
- ----------- m Mail
W Wire F Floating
O Ordered
5 The Database: Directories, Queues, and Stories
128
A screen similar to the following appears:
PEOPLE.SMITH.NOTES id=449889
rec quick index LHDM-WObfpRmF f.id time modified-time
3901 bc-exp--nomad --DM--------- 420690 165 Jul 6 20:23:11 2010
In this example of the story in PEOPLE.SMITH.NOTES, the D and M flags appear,
indicating the story is duplicated and has the modified flag set.
The quick index value can be uppercase or lowercase and must be a single word with no
spaces unless you precede the space with a backslash (\) or put the index value inside
quotation marks (“ ”), such as either of these examples:
list qindex=terror\ suspect q show.10pm.rundown
list qindex=“terror suspect” q show.10pm.rundown
Viewing Who Moved, Duplicated, or Killed a Story
Additional options for the list command can also tell you the last person to move, duplicate,
or kill a story (sending it to the Dead queue).
To list the last person to move, duplicate, or kill a particular story:
tUse the following format of the list command:
list qindex=<search word> q-mb <queue name> [<record limit>]
Since the Index field is typically the field containing the story’s title (slug), it can be
used as the search word.
The search word is a word from the Index (sort) field of the story. It is not case-sensitive.
It must be a single word with no spaces unless you precede the space with a backslash
(\) or put the search words inside quotation marks (“ ”). The record limit is the numerical
limit of stories provided in response to your list command—for instance, the most
recent stories killed in the Dead queue.
To list information for each story in a queue without using a word in the Index field:
tUse the following format of the list command:
list q-mb <queue name> [<record limit>]
The b in the command is optional and stands for backwards.
- list q-m — lists stories beginning with the oldest story in the queue
- list q-mb — reverses the order and lists stories from the most recent material in the
queue, such as the most recently killed stories in Dead.
You can also run the command without the m to see the date and time stories were
moved, duplicated or killed.
For instance, type:
list q-b dead 5
Viewing Database Traits
129
A screen similar to the following appears:
rec quick index LHDM-WObfpRmF f.id time modified-time
0 ---M--O----- 314490 0 Sep 6 09:51:58 2010
-1 kyw-directors --DM--O----- 313587 15 Sep 5 11:47:33 2010
-2 a ---M-------- 161746 11 Sep 6 09:15:06 2010
-3 sep 2010 ---M-------- 314093 0 Sep 5 17:34:19 2010
-4 008 --DM--O----- 313555 600 Sep 5 16:49:24 2010
Here is an example of how to obtain the five most recently killed stories in dead:
list q-mb dead 5
A screen similar to the following appears:
rec quick index LHDM-WObfpRmF f.id time user name
0 ---M--O----- 314490 0 palmer
-1 kyw-directors --DM--O----- 313587 15 williams
-2 a ---M-------- 161746 11 adbpurge
-3 sep 2000 ---M-------- 314093 0
-4 008 --DM--O----- 313555 600 ragusa
As shown in the example, some stories might be sent to the Dead queue by system
processes, such as the automatic dbpurge (adbpurge). Lines without names are old
versions of stories that were not written in the database by a user; for instance, they
might have been put in the database through txnet.
Here is an example of how to get information for a story called “Camera” in the
ASSIGNMENTS.MONDAY queue:
list qindex=camera q-m assignments.monday
A screen similar to the following appears:
ASSIGNMENTS.MONDAY id=14569
rec quick index LHDM-WObfpRmF f.id time user name
0 camera --DM-------- 16217 274 williams
Williams was the last person to move, duplicate, or kill this story; list q-m does not
make any distinction between these actions. Killed stories can reside only in the Dead
queue, while duplicated stories will have the D flag on their listing, as shown in the
previous example.
5 The Database: Directories, Queues, and Stories
130
nIf a utility program, such as a server or link, moves, duplicates, or kills a story, its device
number is listed in the list q-m or list q-mb display.
When using the list command, long list results will scroll out of sight on the console
screen. Since you might need to search through a long list of stories, such as 5000 in the
Dead queue, you can redirect the output of the list command to a file in the database. For
instance, the following example redirects output to a users Notes queue.
NRCS-A# list q-mb dead 5000 | doc -ptu people.p.palmer.notes
Database Traits Summary
Assigning traits can be done from the iNEWS Workstation as well as the console. For
information on viewing and altering database traits from the console, see Appendix G.
On the iNEWS Workstation, the database traits are grouped together on various tabs in the
Directory/Queue Properties dialog box. This section provides a detailed description of the
dialog box, tabs, and database traits. In some cases, traits offer a selection of options, such as
what read group is assigned to a queue. These traits are usually shown as drop-down lists in
the dialog box. In other cases, traits are either assigned to a queue or not—that is, the trait is
“turned on” or “turned off.” These traits are usually shown as check boxes in the dialog box.
Directory/Queue Properties Dialog Box
The appearance of the Directory/Queue Properties dialog box changes slightly, depending
on whether you choose to view properties for a queue or a directory. First, the dialog box’s
title bar will appear different, indicating that choice—either Directory Properties or Queue
Properties.
Viewing Database Traits
131
Other differences include check boxes and tabs. For instance, the Apply changes... check
box—shown in graphic on the left—only appears in the bottom left corner of the Directory
Properties dialog box. Also, the Ordered check box—shown in graphic on the right—only
appears in the right column of the Forms tab in the Queue Properties dialog box.
Both, however, have a Copy From Template button, which can be used to apply directory or
queue property settings from a template to the chosen folder or queue, respectively. This can
be very helpful when adding a new newscast to the database file structure.
nAvid recommends the use of templates to help speed up the process of future configuration
modifications as well as to help avoid the potential for user error.
When you click the Copy From Template button, the following dialog box opens with a
drop-down list of available templates from which to choose.
The templates in the list are created as queues in SYSTEM.PROPERTIES.
The number of tabs in the Directory/Queue Properties dialog box varies, depending on
whether you choose to view properties for a queue or a directory. The tabs are:
•Forms
•Groups
•Maintain
User Interface
Interplay Server
Locks (This tab only appears in the Queue Properties dialog box.)
Each tab is explained in the following sections.
5 The Database: Directories, Queues, and Stories
132
Forms Tab
The Forms tab is unique because it is the only tab that allows access to certain items even
when a user is connected to a local database, as opposed to the online database on the
system’s servers.
nIf you are connected to a local database on your workstation, you can still change the queue
and story form selection using the drop-down lists. However, all other traits in the
Directory/Queue Properties dialog box will appear gray, indicating access to them is
Trait Options Description
Queue The Queue drop-down list lets you select a form to display information in the
Queue panel. The form defines what fields appear, which should be a sub-set
of the fields used in the story form. A field included in the queue form that
does not actually exist in the story form cannot be written to in the Queue
panel. When !<none> is selected, no form is applied. This drop-down list is
the equivalent of the qform database trait (dbtrait) at the console.
Story The Story drop-down list lets you select a form to display information in the
Story Form panel. When !<none> is selected, no form is applied. This
drop-down list is the equivalent of the sform dbtrait at the console.
Index Field The Index Field drop-down list lets you select a form field that will be used to
sort the queue alphabetically. The cursor is placed on this form field by
default when a user displays stories in a queue. This drop-down list is the
equivalent of the sortfield dbtrait at the console. For more information, see
“Index Field/Story Form Compatibility Error Messages” on page 134.
nThe optional fields in the Index Field drop-down list depend on the form selected in the Story
drop-down list on the Forms tab. For instance, if you select a story form that only contains two
fields, such as Title and Writer, then those two fields will be the only options listed in the Index
Field drop-down list.
Update existing... The Update existing stories to use story form check box, when selected,
changes the story form assignment for previously existing stories within a
queue. This check box is the equivalent of the cform dbtrait at the console.
Viewing Database Traits
133
Strip embedded... The Strip embedded form info for existing stories check box, when selected,
removes embedded form traits from stories. For instance, queues with the
Forms Allowed trait stamp the look of the story form into the story.
Assigning a different story form to one of these queues and selecting Update
existing... check box will not affect the look of stories with the embedded
forms. You would need to strip the embedded “look” from the story so it
would then use the form assigned to the queue it is in. This check box is the
equivalent of the stripform dbtrait at the console.
nThe Update existing... and Strip embedded... check boxes are not database traits, but rather,
they are used to apply current settings and/or changes in the dialog box at present. This means
they will always appear unchecked when the dialog box opens, and they will not appear at all
if the Directory/Queue Properties dialog box is opened in read-only mode.
Forms Allowed The Forms Allowed check box must be assigned to all queues in the Forms
directory. The forms will not work without this database trait applied.
Additionally, this trait can be assigned to any queue in the database, but is
usually only assigned to other queues that receive stories from other systems
via rxnet/txnet and then build forms for those stories, as needed. This check
box is the equivalent of the dbtrait +f|-f at the console.
Indexed The Indexed check box, when selected, applies the Index trait. This trait is
assigned to queues and directories you want to be indexed by the Fast Text
Search (FTS) server. This allows for quicker searching of the queue or
directory.
This check box is the equivalent of the dbtrait +index|-index at the console.
See “Batch Indexing” on page 389 for more information.
Sorted The Sorted check box, when selected, applies the sort trait, which determines
whether or not the stories in a queue will be sorted. Queues with the sort trait
are sorted by the form field you choose in the Index Field drop-down list. For
instance, you may want to sort a rundown queue by the Page Number field,
so when a user changes the numbering in the fields of that column, the rows
automatically adjust to the numerical order. See “Turning Off the Ordered
Trait of a Sorted Queue” on page 147 for more information. This check box
is the equivalent of the dbtrait +so|-so at the console.
Trait Options Description
5 The Database: Directories, Queues, and Stories
134
Index Field/Story Form Compatibility Error Messages
A story form is a form that defines the fields displayed in the Story Form panel of the
iNEWS Workspace. The fields typically consist of important information about the stories
kept in the queue, such as the title, writer’s name, and the dates the story was created or
modified. The field chosen as the Index Field in the Queue Properties dialog box serves two
purposes:
It is the field used to sort stories in sorted queues.
When the Index Field is selected during a Find or Find All search of a non-indexed
queue, the system is able to return search results faster.
The Index Field is not associated with Fast Text Searches (FTS).
Therefore, it is crucial that the field selected as the Index Field actually exists as part of the
story form. For this reason, the system will check for compatibility between the settings of
the Story drop-down list and the Index Field drop-down list. Depending on the list
selections, various messages may appear.
When the index field is already defined based on the current story form setting, and a user
selects a different form from the Story drop-down list, the system will check to see if the
field chosen as the index field exists in the new story form. If it does not, a warning is issued.
For instance, the Index Field drop-down list is set to a field, such as Audio-Time, and the
Story drop-down list is set to the Rundown story form. At the current settings, there is no
warning because the Audio-Time field exists in the Rundown story form.
Ordered The Ordered check box only appears on the Queue Properties dialog box, not
the Directory Properties dialog box. The Ordered check box is a unique
check box, because it might appear as read-only, depending on the
circumstance. It is provided to show you whether a queue is currently
ordered. This is particularly helpful in identifying queues that have the sort
trait, but are no longer being sorted because a user manually adjusted the
order of stories in the queue. If a sorted queue was manually ordered, the
check box appears white and contains a checkmark, which you can remove if
you want to reinstate the sorting feature. Unchecking the check box is the
equivalent of the dbtrait, -o, at the console. See “Turning Off the Ordered
Trait of a Sorted Queue” on page 147 for more information. However, if a
queue is not ordered at present, then the box will appear gray and empty. You
cannot select this box to order a queue.
Trait Options Description
Viewing Database Traits
135
However, if the user changes the story form from Rundown to another form that does not
have the Audio-Time field, the following message appears.
The Audio-Time field is no longer in the Index Field drop-down list. The user must select
another field from the list as the warning message instructed. When the user clicks on the
Index Field drop-down list, the system refreshes the list of options to display only those
fields that exist in the currently selected story form.
nNormally, pressing the Escape (Esc) key after the Index Field drop-down list is open (and
therefore, refreshed), will close the list, retaining the original field selection. However, if the
original field choice does not exist in the newly chosen story form—such as the Audio-Time
field in the previously mentioned example—the list closes without any selection made, in
which case, the setting appears blank.
If you select no story form—or set it to !<none>— then the system is forced to blank out the
index field and issue the following warning message.
This means the Index Field drop-down list will be inaccessible and appear grayed out. When
the index field setting is blank, the system will use the default field, which is the Title field
(also called the Slug field).
5 The Database: Directories, Queues, and Stories
136
When an index field is blank—or in other words, no field is selected—the following
message appears.
If the index field drop-down list was already set to the Title field when the Directory/Queue
Properties dialog box opened, and the user manually blanks out the setting, the following
message appears.
The above message indicates that by blanking out the index field setting, the default field,
which is Title, is automatically applied. Since the default is the same field as the original
field setting, no change occurs.
Viewing Database Traits
137
Groups Tab
This section provides information about database traits available as options on the Groups
tab of the Queue Properties dialog box.
See “Groups” on page 161 for more information about groups.
Trait Options Description
General The General check box, when selected, specifies that stories moved to the
queue will retain their original security restrictions, namely, their read and
write groups. For instance, in some cases, sites restrict access to the Dead
queue, but to further guarantee security of stories, the General trait is applied
to the Dead queue. This prevents users who do have access to the Dead queue
from opening stories they could not have opened in their original queues.
This check box is the equivalent of the dbtrait +g|-g at the console.
directory to a group of users. Users who are not in the read group cannot see
the directory or queue. When !<none> is selected, no group is applied;
therefore, all users will have read access to the queue or directory. The groups
are not created here.
This drop-down list is the equivalent of the dbtrait readgroup or rg at the
console.
5 The Database: Directories, Queues, and Stories
138
Write Group The Write Group drop-down list lets you restrict write access to a queue or
directory. Users who are not in the write group cannot add or modify data in
the directory or queue. When !<none> is selected, no group is applied;
therefore, all users will have write access to the queue or directory. The
groups are not created here.
This drop-down list is the equivalent of the dbtrait writegroup or wg at the
console.
Notify Group The Notify Group drop-down list lets you specify what group of users is
notified whenever stories are added to or modified in a queue. When !<none>
is selected, no group is applied; therefore, no users will be notified of
additions or modifications to the queue or directory. The groups are not
created here.
This drop-down list is the equivalent of the dbtrait notify or ng at the console.
Editorial Group The Editorial Group drop-down list lets you restrict editorial access to a
queue or directory. Users who are not in the editorial group cannot add
breaks, float stories, or reorder queues, nor can they delete, remove or move
data from a queue or directory. When !<none> is selected, no group is
applied; therefore, only a user who has Write privileges to the queue can add
breaks or float, reorder, delete, or move stories from the queue.
This drop-down list is the equivalent of the dbtrait editorialgroup or eg at the
console.
Trait Options Description
Viewing Database Traits
139
Maintain Tab
This section provides information about database traits available as options on the Maintain
tab of the Queue Properties dialog box.
Trait Options Description
Save Old Versions The Save Old Versions drop-down list determines how many old story
versions are retained in each queue. The Save Old Versions drop-down list is
the equivalent of the dbtrait save-|n|o|a at the console. Options include:
Save None – Retains no old versions of a story when a new version is
saved in the queue.
Save Previous – Retains the previous version of a story when a new
version is saved in the queue.
Save Original – Retains the original version of a story when a new
version is saved in the queue.
Save All – Retains all versions of a story when a new version is saved in
the queue.
nThe Save Old Versions trait is queue-specific. For instance, a story is moved from a queue that
saves all versions to a queue saving none. In this case, all versions are moved to that queue,
but the next time the story is edited and saved, the old versions are sent to the Dead queue. The
command dbdump honors the Save Old Versions when set to Save None and will only dump the
latest version of a story in the queue with that trait.
5 The Database: Directories, Queues, and Stories
140
Skip Backup The Skip Backup check box determines whether or not a directory or queue
is left out of database backups. This check box is the equivalent of the dbtrait
+x|-x at the console, and is also known as a skip flag.
Update The Update check box indicates whether or not the stories in a queue will be
replaced as new versions are moved or copied to it. This check box is the
equivalent of the dbtrait +u|-u at the console.
nThe Update trait does not affect stories restored from tape backups. If you restore a story to a
queue that already contains a version of that story, you will have two versions of the same
story, even if the queue is assigned the update trait.
Mailbox section The Mailbox section does not apply to the e-mail feature of iNEWS. These
mailboxes are “signal carriers” by which utility programs, called servers, are
notified to perform a pre-defined task. See “Mailbox Tasks” on page 337 for
This section’s trait is the equivalent of the mail dbtrait at the console.
There are two types of mailboxes:
System – The System radio button and drop-down list are used to assign
mailboxes reserved for system functions, such as the keyboard and form
checkers. Each queue or directory that needs a reserved system mailbox
is assigned the correct one when the system is installed by Avid Customer
Support personnel. Options include: All, Keyboard, Keyword,
Distribution, Group, and Map. See “Reserved Mailboxes” on page 339
Standard – The Standard radio button and spin box are used to assign
mailboxes to queues. These are mailboxes used by utility programs you
can configure, such as action servers. The mailbox number assigned to
the queue must match the mailbox number of the server monitoring it, as
defined in the
/site/config
file. Valid mailbox numbers are one
through 5000.
Purge The Purge section allows you to set the reoccurrence schedule for purging a
queue. The purge interval determines how old stories in a queue can get
before they are purged. Every hour, your system removes any stories that are
older than their queue’s purge interval and places the stories in the Dead
queue. For more information, see “Database Purge Intervals and Limits” on
page 148.
The Purge section’s Days and Hours spin boxes are the equivalent of the
purgeinterval dbtrait at the console.
Trait Options Description
Viewing Database Traits
141
User Interface Tab
This section provides information about database traits available as options on the User
Interface tab of the Queue Properties dialog box.
Trait Options Description
Preview Lines The Preview Lines spin box allows you to set a number of lines per story that
will appear as a preview in the Queue panel. Usually, a queue will only show
one line of information per story, similar to what appears in the fields of the
Story Form panel. By applying the preview trait, users can also see a preview
of each story’s text in the Queue panel, without having to open the entire
story. A setting of zero will show the one line of information that is the
standard; A setting of one will show that line plus one line of text, and so
forth. This trait can be overridden by a user’s preferences. See “Layout Tab”
The maximum number of preview lines allowed is 22. This spin box is the
equivalent of the dbtrait, dis, at the console.
Inverted The Inverted check box, when selected, will force the most recent stories in a
queue to be displayed at the top. Otherwise, the most recent stories will
appear at the bottom.
This check box is the equivalent of the dbtrait +i|-i at the console.
5 The Database: Directories, Queues, and Stories
142
Sequential The Sequential check box, when selected, will force a directory to list its
contents—of sub-directories and queues—in the order in which they were
created. Otherwise, the contents are listed in alphabetical order.
This check box is the equivalent of the dbtrait +s|-s at the console.
Refresh The Refresh check box, when selected, assigns the Refresh trait to a queue,
so the system will begin automatically refreshing your screen when changes
are made in the queue. This means when you are looking at a queue in the
Queue panel, you will immediately see changes made to that queue by other
users.
This check box is the equivalent of the dbtrait +refresh|-refresh at the
console.
nUse the Refresh trait only on important queues, like rundown queues that are often modified by
multiple users simultaneously. To automatically refresh a queue, your system must spend a lot
of time monitoring workstations where users are viewing that queue. Assigning the refresh
trait to too many queues that are often accessed at the same time greatly increases the amount
of work your system has to do and may severely degrade its overall performance.
Watch Appends The Watch Appends check box, when selected, lets a queue monitor
incoming data for new stories sent by the wire service, appends them to the
wire queue, and immediately displays them to users who have that wire
queue open. While this trait can be applied to any queue, it is crucial that it be
assigned to queues that receive wire service data, such as the WIRES.ALL
queue.
This check box is the equivalent of the dbtrait +w|-w at the console.
Batch Allowed The Batch Allowed check box, when selected, indicates whether or not the
kill, move, or duplicate operations can be performed against an entire queue.