Avid INEWS V5.2 Administration Guide I News 5.2 NEWSv52 AG EN

User Manual: avid iNews - 5.2 - Administration Guide Free User Guide for Avid iNews Software, Manual

Open the PDF directly: View PDF PDF.
Page Count: 308

DownloadAvid INEWS V5.2 Administration Guide I News - 5.2 NEWSv52-AG-EN
Open PDF In BrowserView PDF
®

®

Avid iNEWS

Administration Guide

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.

Copyright © 2014 Avid Technology, Inc. and its licensors. All rights reserved.

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:
Copyright © 1988–1997 Sam Leffler
Copyright © 1991–1997 Silicon Graphics, Inc.
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:
Copyright (c) 1989 The Regents of the University of California. All rights reserved.

2

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.:
© 2006 Nexidia. All rights reserved.
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.”

3

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/).
© DevelopMentor

This product may include the JCifs library, for which the following notice applies:
JCifs © Copyright 2004, The JCIFS Project, is licensed under LGPL (http://jcifs.samba.org/). See the LGPL.txt file in the Third
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.

Trademarks
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,

4

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 v5.2 Administration Guide • 9329-65311-00 Rev C • Created 12/10/14 • This document is
distributed by Avid in online (electronic) form only, and is not available for purchase in printed form.

5

6

Contents
Using This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Symbols and Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
If You Need Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
...With the Syntax of Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Avid Training Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Chapter 1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Overview of iNEWS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
System Administrator Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Chapter 2

Connect Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Network Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Dialogs for Connect Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Building a Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Dialog Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Dialog Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Adding System Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Setting up the Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Console Connect Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Chapter 3

Database Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Establishing Security Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
User Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Checking Password Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Forcing Individual Users to Change Their Passwords . . . . . . . . . . . . . . . . . . . . 42
. . . At an iNEWS Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Tracking User Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Tracking User Login Activity and Date Created . . . . . . . . . . . . . . . . . . . . . . . . . 44
. . . At an iNEWS Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
. . . At the Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Listing Users Currently Logged in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Recording Logins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
7

Using Group Security to Control System Access . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Chapter 4

Database Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Monitoring Free Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Understanding Database Storage Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Monitoring the Free List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Understanding How the System Copies Stories . . . . . . . . . . . . . . . . . . . . . . . . 50
Tracking Database Space over Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Using the hogs Command to Obtain Information . . . . . . . . . . . . . . . . . . . . . . . 51
Using dbserver and dbfree to Obtain Information . . . . . . . . . . . . . . . . . . . . . . . 52
Increasing Database Space for Immediate Use. . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Maintaining the Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Checking the Database for Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Cleaning the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Cleaning Your Database Offline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Cleaning Your Database with Online Dbvisit . . . . . . . . . . . . . . . . . . . . . . . 58

Chapter 5

Avid System Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Using SNMP Monitoring on the iNEWS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Installing and Enabling the SNMP Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Chapter 6

Backing Up the iNEWS System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Tape Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Establishing Policies for Backup Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Backing up the iNEWS Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
The dbdump Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Backing up the Entire Database to Tape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Tapeless Database Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Backing up Individual Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Notes on Backing up the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Restoring Data to the iNEWS Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
The dbrestore Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Restoring a First-Level Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Listing Tape Contents and Backup Dates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Listing Contents of a Tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Listing Items Dumped on a Particular Date . . . . . . . . . . . . . . . . . . . . . . . . 80

8

Listing the Date of Each Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Searching a Tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
The searchtape Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Searching a Tape for Stories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Searching a Tape by Word(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Searching a Tape by Word and Date Range. . . . . . . . . . . . . . . . . . . . . . . . 83
Searching a Tape by Word and Day . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Searching a Tape by Word and Month . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Specifying a Maximum Number of Stories to Search . . . . . . . . . . . . . . . . . 84
Checking for Free Space on a Database . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Adding Blocks to the Free List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Restoring the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Disaster Recovery Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Disaster Recovery Dbdump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Create Minimal dbdump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Backing up Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Backing up System Site Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
The sitedump Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Chapter 7

Disconnects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Normal System Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Disconnects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Detecting a Disconnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Types of Disconnect. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Causes of Disconnects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Disconnect Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Recovery Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Chapter 8

Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
iNEWS Workstation Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
A User Cannot Log in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
A User Cannot Establish a Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
A User Cannot Access an Item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
9

Group Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Busy Stories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Wire Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Data Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Locked Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
How to Check Process Status (ps Command) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Power Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Network Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
netstat -i Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Output Errors (TX-ERRs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Input Errors (RX-ERRs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
iNEWS and FTS Connectivity (ftsdebug Command) . . . . . . . . . . . . . . . . . . . . . . . 110
Checking Communication between iNEWS and FTS Servers . . . . . . . . . . . . 111
Community . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Appendix A

Command References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Programs Invoked by iNEWS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Commands Used by Avid Personnel Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Linux Commands Used in iNEWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Console Server Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
broadcast. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
ctraits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
dbclean . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
dbclose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
dbdev and dbsize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
dbdump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
dbfree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
dblines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
dboriginal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
dbpurge
(Superuser conditional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
dbrestore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

10

dbserver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
dbsort . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
dbtraits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
dbvisit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
diskclear
(Superuser only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
diskcopy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
doc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
ed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
enter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
force
(Superuser only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
grpcheck. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
gtraits
(Superuser only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
hogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
idiff . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
list B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
list C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
list c . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
list d . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
list g . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
list p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
list q . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
list s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
list sq . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
list u . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
logout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
makemontab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
makeshift (Super user only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
maketab
11

(Superuser only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
mapcheck . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
msgclean . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
offline. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
online. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
otod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
reconnect. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
remove . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
rename
(Superuser only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
reorder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
searchtape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
send. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
sendlong . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
sitedump
(Superuser only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
siterestore
(Superuser only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
su. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
unbusy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
utraits
(Super user only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
wholockedit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Job List Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
at . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
blockmode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
bpoll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
bscan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
12

charset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
dup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
every. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
fast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
ignore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
ignore-del . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
local . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
mailto . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
move. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
open . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
passive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
poll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
publish . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
put . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
quiet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
remote . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
remove . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
replace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
send-del . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
sendform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
sendpassword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
validate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Dialog Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
delay. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
diag. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
13

echo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
escape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
expect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
heol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
mapin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
mapout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
pass . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
pause. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
wait . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Appendix B

System Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
/etc/hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
/site/config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
/site/system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
SYSTEM.CLIENT.WINDOWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
SYSTEM.COLORS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
SYSTEM.CONFIGURE.301-ACTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
SYSTEM.GROUPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
SYSTEM.LISTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
SYSTEM.MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
SYSTEM.MOS-MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
SYSTEM.RESOURCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
SYSTEM.WIRES.DISTRIBUTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
SYSTEM.WIRES.KEYWORDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
SYSTEM.WIRES.KEYWORDS-AP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
SYSTEM.WIRES.KEYWORDS-AP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

Appendix C

Standard Dictionaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Using Dictionaries to Define Messages and Commands . . . . . . . . . . . . . . . . . . . . 208
Customizing Dictionaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

14

Changing Default Dictionary Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Restoring Dictionary Defaults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Utility Messages Dictionary (/site/dict/messages) . . . . . . . . . . . . . . . . . . . . . . . . . . 212
DBServer Program Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Disconnect Program Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Category and Keyword Check Program Messages . . . . . . . . . . . . . . . . . . . . . 214
Keyboard Check Program Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Keyboard Check Program Messages for Macros. . . . . . . . . . . . . . . . . . . . . . . 216
Grpcheck Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Wire Program Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Mail Server Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Map Check Program Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Validation (Action) Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Seek Server Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Last Login Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Print Server Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
dbtraits Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Save Error (Workstation) Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Queues Dictionary (/site/dict/queues) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Words Dictionary (/site/dict/words) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Keyboard Macros Dictionary (/site/dict/keymacros) . . . . . . . . . . . . . . . . . . . . . . . . 227
Case-shifting Dictionary (/site/dict/shift) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
MCS Dictionary (/site/dict/mcs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Device Types Used by Monitor Servers and Drivers . . . . . . . . . . . . . . . . . . . . 231
Special Strings Recognized by the Monitor Server . . . . . . . . . . . . . . . . . . . . . 232
Error Messages for the Monitor Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Status Reported in Device Status Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Job List Command Dictionary (/site/dict/joblist) . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
D Messages Dictionary (/site/dict/dmessages) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
S Messages Dictionary (/site/dict/smessages) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

Appendix D

Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Registry Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Environment Variables (Registry Values) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
15

CCColor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
DestinationOrder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
MailLookup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
MsgMailAlert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
PIColor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
RGB Hexadecimal Color Chart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
ShowTimingBar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
SyncToServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
VT Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
DisableCommandLine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Environmental Variables for Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
GBUFFERLIMIT Environment Variable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

Appendix E

Managing Traits at the Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Viewing User Traits from the Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Modifying User Traits from the Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Changing a User’s Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Listing Users Who Do Not Have Passwords . . . . . . . . . . . . . . . . . . . . . . 265
User Traits Console Command Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Managing Database Traits from the Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Getting Basic Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Getting Detailed Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Changing Database Traits from the Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Changing a Parent Directory Only. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Database Traits Console Command Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Sortfield . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Changing a Queue’s Sort Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
Starting the Queue Sort Function from the Console. . . . . . . . . . . . . . . . . 283
Purge Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
Mailbox Attribute. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
The dis Column . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
FTSindex Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Managing Group Traits at the Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Read Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288

16

Write Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
Editorial Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
Notify Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Restricting Access Using Read and Write Limitations . . . . . . . . . . . . . . . . . . . 289
Removing Directory or Queue Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

Appendix F

The Line Editor, ed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Starting ed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Specifying Lines to Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
Searching the File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
Searching Tips. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
Editing Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
Saving Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Quitting ed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297

17

18

Using 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
Setup and Configuration 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.

n

The 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

n

A note provides important related information, reminders,
recommendations, and strong suggestions.

c

A caution means that a specific action you take could cause harm to
your computer or cause you to lose data.

w
>

A 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.
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.

| (pipe character)

The pipe character is used in some Avid product names, such as
Interplay | Production. In this document, the pipe is used in product
names when they are in headings or at their first use in text.

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.
20

If You Need Help

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.
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
answers, to view error messages, to access troubleshooting tips, to download updates,
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:

t

Use the following command: help 
For instance, type: help dbvisit for an explanation of the dbvisit command.
The following data appears:
dbvisit - [-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

n

Lengthy 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

21

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.

22

Avid Training Services

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).

23

24

1 Introduction
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

•

System Administrator Tasks
-

Basic Tasks

-

User Tasks

-

Database Tasks

-

Security Tasks

-

Customizing the System

-

Storage Maintenance Tasks

-

Device Tasks

-

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.

System Administrator Tasks

System Administrator Tasks
The following sections describe common system administrator responsibilities and tasks.
Basic 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.

User Tasks

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.

Database Tasks

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.

•

Create new folders or queues in the iNEWS system database to meet your organization’s
expanding needs—including setting up rundowns.
27

System Administrator Tasks

•

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.

Security Tasks

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.

Storage Maintenance Tasks

You will want to monitor the database regularly to ensure adequate storage. Storage maintenance
tasks include:
•

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.

28

System Administrator Tasks

Device Tasks

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.

29

2 Connect Services
Connect services are utilities you can set up to enable iNEWS users to connect to other
computers or information services over the network, such as a remote console for your iNEWS
newsroom computer system.
This chapter contains the following main sections:
•

Network Services

•

Adding System Services

•

Console Connect Sessions

Network Services

Network Services
It is useful to set up a service to let you connect to your iNEWS Servers. For instance, setting up
network remote connect services lets you perform many administrative tasks from your iNEWS
Workstation rather than from the console.

Dialogs for Connect Services
A dialog is a script that tells the service what prompts to expect from the device it connects to,
and provides the service with appropriate responses for each prompt. Using any service involves
some routine activities, such as logging in, that you do each time you use that service. You can
create a dialog for any service to handle these routine activities.

Building a Dialog
This section explains how to design and create a simple dialog that logs a user in to an
information service. Once logged in, the dialog yields control to the user until he/she is ready to
close the connection. Then the dialog logs the user out of the service and closes the connection.
When you design a dialog, it is helpful to turn on the capture connect command and perform
the procedure you want to incorporate into the dialog. This way, steps in that procedure are
captured to a story that you can refer to while designing the dialog; each line in the dialog is built
as a line of the story.
This process includes the most commonly used dialog commands.
To build a dialog:

1. Create a dialog queue.
Each dialog must be in a separate queue in the SYSTEM.DIALOGS directory. The first step
in creating a new dialog is to go to SYSTEM.DIALOGS and create a queue to hold it. The
name you give this queue is also the name of the dialog, so choose a queue name that
describes what the dialog does, such as Console, for a dialog used during connect sessions to
the console. See the iNEWS Setup and Configuration Guide for more information about
adding new directories, queues or stories.
2. Open a new story in the queue and build the dialog.
3. Type a message that will be displayed on the user’s workstation, indicating the connection is
being established, using the following format:
message text

The message dialog command displays on the user’s screen whatever text you enter in place
of the text parameter.
4. Type: wait CONNECT
31

Network Services

When you use a modem to make the connection, you want the dialog to wait until the
modem sends the word CONNECT to the workstation, signaling it has made the connection.
If necessary, use these additional commands to accommodate the login procedure:
Command

Description

delay nn

Use this command to pause the dialog while the service continues connect
and login processes.
(nn is the number of seconds you want the dialog to pause before continuing
to the next command)

type text

Use the type command to send a text message to the device to which the
workstation is being connected.

5. To send your login data, such as an account number, type type text with text being the
account number.
6. Type pass to yield control to the user after login is complete.
This command instructs the dialog to pass whatever the user enters to the device to which the
service has connected.
Use pass x to include a character the user can enter to cue the dialog to resume. The x
should be a character or symbol, such as the at symbol (@), he or she will not normally use.
Use pass alone to instruct the system to accept what the user enters until he/she closes the
connection.
7. Type commands to log out of the service.
When the user exits a connection using the quit connect command, the dialog resumes and
performs the logout process and closes the connection.
8. Attach the dialog to the service by placing the dialog’s name in the service’s dialog
parameter in the service table, located in the SYSTEM.SERVICE queue.
9. Type the configure -s command to incorporate this change into the service.
Dialog Commands
Available dialog commands are flexible enough to script entire connect sessions. For instance, a
dialog could be constructed to automatically log in to the remote console and “unbusy” a
rundown if desired.
The available dialog commands are reviewed in “Command References” on page 497.

32

Adding System Services

Dialog Examples
Here are a few examples of dialogs for remote console connect services:

In the example,  and  are used to indicate a “carriage return” and “line feed.”

Adding System Services
A service consists of two parts:
•

A network resource, set up as a device in the configuration file (/site/config).

•

The service, set up in the service table in the database file (SYSTEM.SERVICE); it uses the
resource to make a connection.
To add a new service to your system, you must design and build the service and select a
network resource for the service to use. If an appropriate resource does not exist, create one.

Setting up the Service
To set up the service and its resource:

1. Determine whether the service and its resource exists.
Try connecting to a service you want. If it works, then the necessary programs are installed.
If you cannot find the service, or one does not work, call Avid for help.

33

Adding System Services

2. Choose a device number for the resource and a name for the service. In the following
examples, the service name is console.
Check your configuration file (/site/config) to determine the appropriate device number for
your new resource. For a network resource, choose a number in the range you have reserved
for services, servers, and similar devices. Ensure the number you choose is out of the range
used for normal devices.

n

See the iNEWS Setup and Configuration Guide for more information on the Site Configuration
file and selecting servers via the PuTTYCS application.
3. Add the resource to the configuration file on each server in your system.

n

a.

Add the device number of the network resource to the reslist line in the server’s host
definition.

b.

To keep the network resource available if you bring down one of the system servers, add
this line to any appropriate alternate host definitions.

The following steps use ed to modify system files. If you are unfamiliar with this line editor, see
“The Line Editor, ed” on page 679.
c.

Use ed (line editor) to open the configuration file. The display will look similar to:
NRCS-A$ ed /site/config
1356

The general format for a network resource configuration line is:
resource   
Parameter

Description

device #

Identifies resource’s device number.

resource name

Name you want to give to the resource. Network resources can share the
same name; services choose the first available resource of the correct kind.
In the following example, we call the resource net.

device name

Resource’s device name. If you do not want to give it a name, put a hyphen
in this position.

For instance, our new network resource configuration line would look like this:
resource

220

net - ; net connect

4. Add the service to the service table in the database.

34

Adding System Services

Each service installed in your system is defined on a separate line in your system’s service
table, which is the first story in SYSTEM.SERVICE. Each service defined in the service
table consists of a few parameters that determine how the service behaves. It does not matter
where in the service table you add the new line.
A service line has six parameters in this general format:
     

The following table contains information on service line formats:
Parameter

Definition

service

Name you want the service to have.

host

Name of the server where you want the service to look for its resource. List
the target server’s name in your system’s /etc/hosts file.
A hyphen in this position will force the service to search each server until it
finds one that has a resource it can use.

dialog

If you want the service to use a dialog, put the dialog name in this position of
the service line. Otherwise, fill this position with a hyphen.

resource

Name of the resource you want the service to use.

group

You can restrict who can use the service by specifying a user group. If you do
not want to restrict access, place a hyphen in this position.

command

Specifies the command you want the service to use to handle communication.
To create a service using telnet, type the telnet command here. Ensure you
specify the program’s full pathname and include the system name to which
you are connecting.

You will need one such service line for each server on your system. Use the ssh command in
the following way:
/usr/bin/ssh  -1 

The following sample entries in SYSTEM.SERVICE let you establish a network connection
to your console from an iNEWS Workstation session.
a - console console sysops /usr/bin/ssh NRCS-A -l so
b - console console sysops /usr/bin/ssh NRCS-B -l so

The resource assigned to the service must be configured on the computer you want to log in
to.
5. (Optional) Create a dialog for the service.

35

Adding System Services

If you want your service to follow certain instructions every time it is invoked, create a
dialog for the service containing those instructions. See “Building a Dialog” on page 31 for
more information.
6. (Optional) Test your configuration changes on iNEWS. See the iNEWS Setup and
Configuration Guide for more information on testing the site configuration file.
7. Reconfigure the system.
This causes your system to note changes and incorporate them into appropriate programs.
Do the following:

n

See the iNEWS Setup and Configuration Guide for more information on selecting servers and the
superuser mode.
a.

Select the console window for the master computer (typically server A).

b.

Enter superuser mode.

c.

Type what appears in bold text:
NRCS-A# offline

d. If you added a new resource or modified an existing one in the process of creating a new
service, reconfigure your system by typing the following:
NRCS-A# configure

If you modified an existing service or added a service that uses an existing network
resource, you did not make any changes to your system’s configuration file. So, you
need to have the system note only changes made to the service table by typing the
following:
NRCS-A# configure -s

8. When the prompt returns, type what appears in bold text:
NRCS-A# online

9. Exit superuser mode by holding the Control key (Ctrl) down and typing the letter D. A
message similar to the following will appear:
A Tue Oct 5 00:18:58 2000 msg System being configured

When you see the system prompt, the network service you created and its resource you
added (if any) is ready for use.
10. (Optional) Back up site files.
If you have made significant changes, back up your site files with the sitedump console
command.

36

Console Connect Sessions

Console Connect Sessions
To connect to the console from an iNEWS Workstation—that is, after the network remote
connect service and its resources are set up—do the following:

1. Log in to any iNEWS Workstation, with a user account allowed to use the Connect to
Service feature.
2. Select Communicate > Connect to Service. The Connect to Service dialog box will appear,
offering you a list of services.
As shown in this example, two options are provided to connect to the console—each option
corresponding to a different iNEWS Server.

3. Double-click on the service you want.
A dialog box will appear with a dialog (as defined in the SYSTEM.DIALOGS) that requests
a password.
4. Type in the password and press Enter.
5. Once connected, the dialog box will display the console prompt, similar to what appears on
the console when you are logged in as a system operator.
Here is an example of a remote console connection:

37

Console Connect Sessions

6. You can now perform various administrative tasks through the console connect session, as
opposed to doing them while physically located at the console.

c

To stop a console connect session, press Ctrl+D. Do not close the dialog box by selecting File
> Close or by clicking on the X button in the upper-right corner.

38

3 Database Security
This chapter describes how to use various features in the iNEWS newsroom computer system to
establish and maintain database security.
This chapter contains the following main sections:
•

Establishing Security Procedures

•

User Passwords

•

Checking Password Status

•

Tracking User Activity

•

Using Group Security to Control System Access

Establishing Security Procedures

Establishing Security Procedures
Use the following guidelines to improve the security of your system:
•

Set up official security procedures and have everyone follow them.

•

Keep track of your backup tapes. You can get user passwords from a backup tape.

•

Assign users superuser status only when they need it.

•

If any user does not need superuser status, remove it. Create two user accounts for staff
members who need superuser privileges—one to be a superuser and another to be a regular
user. That way, you can track activity of superuser accounts.

•

Change the superuser password regularly.

•

Ensure that users do not use their names, station call letters, or other easily guessed words as
passwords. Require everyone to include at least one non-alphabetic character such as a
punctuation mark or a number.

•

Use the system profile to set a required minimum length for all passwords so no one uses a
short password.

•

For devices for which you have dedicated resources—that is, devices that have a one-to-one
correspondence between the physical device and device number used to identify it—use
device name security on workstations in specific locations and put the device ID in a group.

•

If you have dedicated resources, you can put a MODIFY-DEV field in the queue’s story
form if you suspect that someone has broken into a user’s account. When changes are made
to stories created after the MODIFY-DEV field has been added, the system puts the device
name of the workstation where changes were made in that field. This information is kept
internally, but having the MODIFY-DEV field makes it visible to users.

•

Be familiar with valid user accounts on your system. Restrict access to these account names
to protect against unauthorized outside access.

User Passwords
Your iNEWS newsroom computer system protects against unauthorized access by giving each
authorized user a password to log into the system. Group security, described under “Using Group
Security to Control System Access” on page 47, lets you control specific areas of your database
that each user can access.
For added security, iNEWS uses encryption to pass user credentials to the server.

40

Checking Password Status

Checking Password Status
A user account without a password is an open door to your system. You should always give a
user a password when you add the user to your system. See the iNEWS Setup and Configuration
Manual for more information on setting up new user accounts.
However, if you suspect that a user does not have a password or has not changed it in awhile, you
can find out for certain from any iNEWS Workstation.

n

For information on how to check password status from the console, see “Listing Users Who Do
Not Have Passwords” on page 652.
To check user password status from an iNEWS Workstation:

1. Log in as a system administrator—that is, use a superuser account.
2. Select Tools > Options > Users.
The Manage User Accounts dialog box appears.

3. Type an asterisk (*) in the User ID field if it does not already appear.
The iNEWS system recognizes this as a wildcard and therefore will search the entire
database of users.

n

The other criteria options available in this dialog box are explained in the iNEWS Setup and
Configuration Manual.
4. Click the Advanced button.
41

Checking Password Status

The Advanced Search Settings dialog box appears with All Users selected by default.

5. Do one of the following:
t

To search for all users without passwords, select Users Without Passwords.

t

To search for all users who have not changed their password within a specific time,
select Date Range. Then click Password Changed, and specify the time frame to search.

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. Results of the search appear in the
User List field in the center of the Manage User Accounts dialog box.
As a system administrator, you can change a user’s password. Change a user’s password to
provide a new user with a temporary password or to supply an established user with a new
password if the user forgets it and cannot log in. See the iNEWS Setup and Configuration
Manual for more information on how to do this from any iNEWS Workstation. For steps on
how to change a user’s password from the console using the utraits console command, see
“Changing a User’s Password” on page 650.

Forcing Individual Users to Change Their Passwords
Occasionally, you might have individual users who do not change their passwords as required.
When that happens, you can force them to change their password at their next login. You can do
this for a single user at an iNEWS Workstation.
42

Checking Password Status

To force multiple users to change their passwords—such as all users who haven’t changed their
passwords in the past six months—you must go to the console. For steps on how to force
password changes from the console, see “Changing a User’s Password” on page 650.
. . . At an iNEWS Workstation
To force an individual user to change his or her password:

1. Select Tools > Options > Users.
The Manage User Accounts dialog box appears.
2. Type the user name in the User ID field.
3. Click Search.
4. Select the user name when it appears in the dialog box.
5. Click Modify.
The Modify User Account dialog box appears.

6. Check the Force Change box.
7. Click OK.
The next time the user logs in, he or she will be required to choose a new password.

43

Tracking User Activity

Tracking User Activity
Keep a record of who uses iNEWS and when they use it by following the procedures described
in this section. These security measures can ensure there is no unauthorized use of your system.
At an iNEWS Workstation, you can determine:
•

Last login date of one or more user accounts

•

Date user accounts were created

•

Users currently logged in

At the console, you can determine attempted and successful logins.

Tracking User Login Activity and Date Created
You can search for a user account’s last login and the date the user account was created from an
iNEWS Workstation.
. . . At an iNEWS Workstation
To search for a user’s last login:

1. Select Tools > Options > Users.
The Manage User Accounts dialog box appears.
2. Click Advanced. The Advanced Search Settings dialog box appears.
3. Click Date Range.
4. Do one of the following:
t

To search for user accounts with a last login date that matches a specified date range,
click Last Login.

t

To search for user accounts created within a specified date range, click Account Created.

5. Specify a date range in the From and To fields.
6. Click OK.
7. Click Search.
The requested user name information appears.
. . . At the Console
Another command you can type at the console will give you valuable information about users:
list u-t []
44

Tracking User Activity

This command shows the date and time a user account was created, date and time of last login,
and date and time of last password change.
If you do not specify a particular user name to check, you will get a listing for all users.

Listing Users Currently Logged in
From the iNEWS Workstation, you can see a list of all users logged in, and you can find out
whether a specific user is currently logged in.
To see a list of all logged-in users:

1. Press Ctrl+L or select Communicate > Messages > Logged In Users.
A dialog box appears with a list of users currently logged in.
2. Click OK when you are done looking at the list.
To determine whether a specific user is logged in:

1. Select the Message bar.

2. Type the user name in the To field.
3. Move cursor to the message field, using the mouse or Tab key.
4. One of three symbols appears to the left of the To field, depending on what you type in the
To text box:
Icon

Description

If the user is currently logged in, an icon of connected cables appears to the left of the
user name.
If the user is not currently logged in, an icon of disconnected cables appears to the left of
the user name.
If there is no such user name in the system, a question mark appears to the left of the user
name.

Recording Logins
Keep track of successful and attempted logins to preserve system security. You can spot
unauthorized users, people logging in at odd hours, or repeated attempts to guess passwords.

45

Tracking User Activity

To monitor logins from different types of devices:

1. Change the value for the W_LOGTYPES token in the dictionary /site/dict/words. A typical
definition for this token might look like this:
W_LOGTYPES/G

Each letter in the W_LOGTYPES value represents a different type of device that can log in
on an iNEWS newsroom computer system.
The letters are the same ones that appear in the first column of a list s or list c display for
these device types.
2. To track logins by device type, add the appropriate letter to the W_LOGTYPES value.
Use the following letters:
Letter

Description

G

iNEWS Workstation

g

Web Client

B

Web sessions

C

Community sessions

c

COM

A

Interplay (Instinct or NewsCutter)

a

Web Services API

I

Instinct

For instance, to track logins from all devices on your system, change the W_LOGTYPES
line to look like this:
W_LOGTYPES/GBc

The letters can appear in any order.

n

On a busy system, this can create a large amount of console activity.
3. When a user logs in at a device of a type listed in W_LOGTYPES, a message similar to the
following is sent to the console:
Apr 5 16:25:47 NRCS-A G3494: Attempted login bloyd 172.24.96.247
3.1.1.2/3.1.1.3 RH5

This message includes the device type and number, time of login, user name, IP address of
PC used, and client version number.
46

Using Group Security to Control System Access

4. A logout message similar to the following is sent to the console when the user logs out:
Apr 5 16:23:55 NRCS-A G3495: Logout fiatala 172.24.96.247 {9}
3.1.1.2/3.1.1.3 RH5

A failed login—that is, an invalid user name or password—produces a message similar to
this:
Apr 5 16:25:47 NRCS-A G3494: Attempted login bogus 172.24.96.247
3.1.1.2/3.1.1.3 RH5

Regardless of the W_LOGTYPES value, a message is always sent to the console when a
superuser logs in or out. This message includes (n) if the user is a superuser. An
unsuccessful login by a superuser generates a message only if the device type used is
included in W_LOGTYPES.
Using login tracking in conjunction with console history and disk logging, you can keep
accurate records of who is using your system and when and where they are connecting to it.
A listing of currently logged in users may be obtained from the console using the list s
command. See “list s” on page 529 for more information.

Using Group Security to Control System Access
Your system is designed to be used by a wide range of people. For the system to accommodate so
many diverse job roles, restrict sensitive areas of your database to authorized users. The system’s
powerful security features let you restrict access to important directories and queues.

c

Security ensures that only authorized people can view or make changes to important
queues. It does not provide absolute privacy, because superusers can open any story while
performing normal system maintenance. Warn your staff not to store personal or
confidential material in the database.
Many security features in iNEWS involve establishing groups and assigning privileges and
restrictions to them. The iNEWS Setup and Configuration Manual gives you complete
information about using the group features in iNEWS to help you maintain system security.

47

4 Database Management
This chapter provides you with information required to manage the iNEWS database, where all
business data, such as stories, is stored. Much of the iNEWS system data is stored in
configuration files, which is covered in the Avid iNEWS Setup and Configuration Guide.
This chapter contains the following main sections:
•

Monitoring Free Space

•

Tracking Database Space over Time

•

Increasing Database Space for Immediate Use

•

Maintaining the Database

Monitoring Free Space

Monitoring Free Space
The iNEWS newsroom computer system is constantly collecting wire stories and adding them to
the database while the news staff adds scripts, rundowns, memos, assignment sheets, and other
stories. To avoid running out of disk space, iNEWS tracks old stories. As stories get old, the
system purges them.
Distribution and purging of disk space is called the database cycle. In this cycle, wire stories are
collected and stored in the database for a specific interval of time. Other news items, such as
scripts and assignment sheets, are created by the news staff and also kept for a preset period of
time, called the purge interval, which is set individually for each queue. Any story older than its
queue’s purge interval is purged, and its space is reclaimed for new stories.
The purge interval is a database trait, so you can set different purge intervals for queues and
directories, depending on the information they hold. Setting purge intervals appropriate for
stories in various queues helps keep the database from growing too large.
Once an hour, at 15 minutes after the hour, an automatic dbpurge program scans each queue for
stories older than the queue’s purge interval and moves these stories into the Dead queue.
Stories sent to the Dead queue are not erased until the system needs the space. Until the system
reclaims this space, stories in the Dead queue can be read, searched, edited, copied, or printed.
To retrieve a story from the Dead queue, select the story and copy it to a different queue in the
database, where you have write permission.
Although you can open stories in the Dead queue, they are marked for removal and will be
permanently removed when the system detects the computer is running out of storage space.
Your system keeps track of the space available by examining and maintaining a list of free space
on the disk. The free list is explained in “Monitoring the Free List” on page 50.

Understanding Database Storage Units
Your computer’s disk is divided into blocks. The database portion of the disk is divided into
1024-byte blocks. When a story is saved, the system allocates as many blocks as necessary to
hold the story and then divides the story among those blocks.
Blocks used to hold a story need not be sequential; a story can be saved in blocks that are apart.
To tie together all blocks, each block contains a reference to the block containing the next part of
the story.
A block is either “in use” or “free”.

49

Monitoring Free Space

n

iNEWS versions 3.x and earlier supported a maximum database size of 16GB. Beginning with
iNEWS versions 4.x and later, the maximum database size increased to 128GB. When the
database size was expanded the storage block size also increased from 1k blocks to 4k blocks.

Monitoring the Free List
The free list is the list of free space on the disk. By keeping track of space in the free list, the
system can detect when it is running low on space. It runs an automatic dbserver program,
which removes the oldest stories from the Dead queue and adds the space to the free list, where it
is made available to the system. This way, dbserver maintains the volume of free space available
in the database.
The free list measures space in blocks (a block=1024 bytes), and has a lower limit called the
lowwater mark, which represents the least amount of free space available. When the space
available drops below the lowwater mark, the system runs dbserver to reclaim enough space
from the Dead queue to rebuild the free list to the highwater mark.
Together, the highwater and lowwater marks determine the free list’s normal operational range.
If the system cannot get back up to the highwater mark after reclaiming free space, the user will
get a low on space message. Create free space immediately, as explained in the following
section.

Understanding How the System Copies Stories
You can configure iNEWS to distribute a wire story to several queues when it is received.
Likewise, two or more users can put copies of the same story into their personal queues. If you
copy and distribute enough stories, a large portion of the database can become cluttered with the
copies.
To avoid filling up the disk with copies of stories, your system keeps only the original story on
the disk. When a story is copied to another queue, your system puts a reference to the original
story in the queue that will hold the copy.
When someone opens a copy of a story, the system uses the reference to find the original story. It
makes a working copy of that story, which it sends to the user. If the user examines the working
copy and makes no changes, the working copy is deleted when the user closes the story.
However, if the user makes changes to the working copy and saves it, the system saves that copy
as a story, replacing the reference.

50

Tracking Database Space over Time

In most cases, you can treat a reference to an actual story as if it were the story. The only time
you need to take references into consideration is when setting purge intervals. When the system
references a story to several different queues, each reference takes on the purge interval of the
queue. When a reference becomes older than its queue’s purge interval, the computer puts the
reference, not the actual story, in the Dead queue.
The space used for a story becomes free only when the last reference to the story has been
removed from the system.

Tracking Database Space over Time
Do not wait until you encounter an “out-of-space” condition before you start to think about
database storage. There are two ways you can get a good picture of space usage over time:
•

The “hogs” report

•

The information generated by the dbfree command

Using the hogs Command to Obtain Information
The hogs command displays how much space particular queues are using in the database. It uses
this format:
hogs

[]

To get a hogs report on the People directory, type:
hogs people

A screen similar to the following appears:
%

USED

SHARED

HELD

LOCKED

PURGE

QUEUE NAME

0

36

20

0

0

0

PEOPLE.LEVY.BYLINE

0

128

20

0

0

0

PEOPLE.LEVY.FINAL

0

32

40

0

0

0

PEOPLE.LEVY.FORM

40

0

0

0

PEOPLE.WALTERS.NOVEL

...
0

425

51

Increasing Database Space for Immediate Use

The USED column contains the number of blocks used in that queue. The SHARED column
indicates the number of blocks used in that queue that are also used in other queues. To get the
number of blocks used only by that queue, subtract the SHARED count from the USED count. If
any queue has a substantially greater number of used blocks than the others, examine that queue
more closely.
To obtain a hogs report on the entire database, type:
hogs .

To send a hogs report to yourself, type:
NRCS-A# sh
# hogs . | mail  &

n

For more examples on how to use the hogs command, see “hogs” on page 518.

Using dbserver and dbfree to Obtain Information
To obtain an accurate idea of how much space is being used by stories in the system:

1. Empty out the Dead queue and reclaim all space used in it. Type:
dbserver 34000000

n

You must run dbserver when other programs like dbpurge are not running.The number 34000000
reflects the maximum database size in blocks and ensures the DEAD queue is emptied.
2. The next day, or after completion, run the dbfree program to see how much space is being
devoted to functions in your newsroom you consider critical.
3. Repeat this process from time to time, so you are aware of trends in space usage.
Use the information to make decisions on projected storage needs, and how space is used.

Increasing Database Space for Immediate Use
If your database has not reached the “Low on Space” point, but you want to increase free space
for immediate use, do the following:
To increase free space for immediate use:

1. Type the command that appears on bold:
NRCS-A$ dbfree
database size 16,386,300 free 1,746,564 = 11%, freelist 1,493
52

Maintaining the Database

The dbfree command—used by a system operator or a superuser—displays database size,
free list size, and percentage of remaining database available. The freelist number indicates
how many database blocks are used to hold the free list. The free list is compressed. This
results in anywhere from 250 to 5,000 free-block numbers contained in each free list block.
In this example, 1,493 blocks are used to hold the 1,746,564 free block numbers. That is an
average of 1,169 free block numbers per free list block.
2. Back up old material to tape and remove it from the database.
3. Check and reset purge intervals of Wires directories and queues.
To view purge intervals at the console, type:
list d wires

Information similar to the following appears:
SRPlo-LIsUG-QSXWFiTm sortfield

purge dis mbox directory

D-R-----I----Q-XW---- TITLE

P4.0

D1

-

WIRES

D-R-----I----Q-XW---- TITLE

P4.0

D1

-

WIRES.ALL

D-R-----I----Q-XW---- TITLE

P4.0

D1

-

WIRES.AP

...

One of the biggest consumers of database space in a newsroom is the Wires directory.
Because wire stories lose much of their value after a few days, most newsrooms set a purge
interval of 2 or 3 days. In this example, all Wires directories and queues have a purge
interval of four days. The purge interval is a database trait you can customize for each
database directory or queue. For more information on modifying database traits, including
purge intervals, see the Avid iNEWS Setup and Configuration Guide.

Maintaining the Database
The following sections describe the two most important maintenance procedures you should
perform regularly on your database:
•

Check the database for errors

•

Clean up the database on a monthly basis

Checking the Database for Errors
In the large databases typically maintained by newsrooms, minor errors can develop in some
stories as a result of vast amounts of information the system processes every day. These errors
can grow and eventually begin to damage the database if they are not removed.

53

Maintaining the Database

To check stories in your database for errors, use the dblines console command, which examines
every story in the database. You can run dblines on any server while the system is online. It can
point out problems or errors in the structure of the database, find queue corruption that must be
fixed before a dbvisit is run, and make some repairs. It cannot reclaim unreferenced blocks,
adjust link counts, or rebuild the free list; dbvisit is required for that.
Since dblines examines every story in your database, it requires several hours to complete its
task, so run dblines before you go home at night. By the time you return in the morning, it should
be done.
When dblines discovers an error, it ordinarily sends an error message to the console. However, if
you run it at night, you can have the system send its messages to a log file for you to review the
next day.

n

For more information on the various commands used in this section, see “Command References”
on page 497.
To execute the command and have it send output to a log file:

1. Enter superuser mode on the master computer.
2. Type: dblines . > /tmp/dblines.log
You can also use the at command to schedule the dblines command to run at a specified
time. For instance:
To execute the dblines command so it logs at a specified time:

1. Enter superuser mode on the master computer
2. Get the current time, using the date command:
NRCS-A# date
Sat Jul 10 11:05:07 EDT 2010

n

You must use 24-hour military time.
3. Set the schedule, such as 5 minutes later, using the at command:
NRCS-A# at 11:10

4. Type the dblines command line:
/exc/dblines . > /tmp/dblines.log


Pressing Ctrl+D after entering the command line marks the end of commands to be executed
according to the at schedule. Afterwards, the server prompt returns to the original prompt,
showing the server name, such as NRCS-A#.

54

Maintaining the Database

After the dblines is complete, you can check the log file for error messages, by using the
grep command:
NRCS-A# grep failed /tmp/dblines.log

This searches the log file for the word failed. If there are no errors involving queue
corruption, such as  scan failed ,  read error, or unable to open ,
the prompt will simply be returned. If there are any error messages related to queue
corruption, call Avid for assistance.
If you want to review the entire log, you can use the doc command to place a copy in a queue
you specify. For instance, replacing the previous example, the sequence of commands
(shown in bold) may appear similar to the following:

n

You must use 24-hour military time.
NRCS-A# at 11:10
/exc/dblines . |/exc/doc-ptu people.sysadmin.notes

job 1001340600.a at Sat Jul 10 11:10:00 2010
NRCS-A#

In the example, the system would execute the dblines command at 11:10, and then place the
output in PEOPLE.SYSADMIN.NOTES. As indicated by the pound sign (#) in the prompt,
you must be in superuser mode to execute the commands.

Cleaning the Database
Over the course of a month, the iNEWS database may develop minor errors in its structure—the
overall organization in which individual stories are arranged. These errors are the result of
normal database cycles in which old material is removed and new information is added.
These errors grow and begin to damage the database if you do not remove them. The database
cleanup procedure identifies errors so you can repair them before they become harmful.

n

Unless you are instructed to perform this procedure more often, do a database cleanup once a
month.
You can conduct database cleanup, using the dbvisit command, while your system offline or
online. The procedures for each are provided in the following sections:
•

Cleaning Your Database Offline

•

Cleaning Your Database with Online Dbvisit

55

Maintaining the Database

Cleaning Your Database Offline
The database cleanup procedure using the dbvisit command requires you to briefly take your
system offline, preventing users from logging in.
The day before performing the monthly database cleanup offline, do the following:

1. Select the console window for the master computer (typically server A).
2. Type dbserver 34000000 to empty the Dead queue.
Starting the day before, allows time for the system to complete this process, which may take
several hours, before you run dbvisit.

n

To check the database structure for errors, dbvisit must perform a cursory check of stories in the
database, including those in the Dead queue. You can shorten the time it takes dbvisit to examine
the database by using dbserver to empty the Dead queue first.
The dbserver command initiates a day-long operation and should be done one day ahead of the
next steps in this procedure. Your system remains online during the operation.
After the dbserver operation is completed, you are ready to clean up the database offline,
by doing the following:

1. Shutdown the system, by completing the following steps:

n

For more details on the procedure for shutting down the system, see the Avid iNEWS Setup and
Configuration Guide.
a.

From the PuTTYCS application, select the PuTTY Filter created for sending server
commands to all servers, such as iNEWS Consoles.

b.

Take the system offline.

c.

Log out all users.
The dbvisit command cannot examine stories being edited. You must log out everyone
on the system and stop all news programs on the servers before running dbvisit.

d. Run the stop all console command on all servers to stop all workstations, wires, and
other devices from making further changes to the database.
After using the stop all command, wait a few seconds for the prompt to reappear. When it
does, proceed to the next step.

c

If conducting a dbvisit offline, ensure system is offline and that you have stopped all
network devices. If you do not do this before cleaning your database, you may corrupt the
data when you perform the cleanup. For procedures to conduct an online dbvisit, see
“Cleaning Your Database with Online Dbvisit” on page 58.

56

Maintaining the Database

2. Start the database cleanup by doing the following:
a.

Select the console window for the master computer (typically server A).

b.

Enter superuser mode.

c.

Type: dbvisit -d
A message similar to the following appears:
09:31:45 opening database
09:31:45 traversing roots

The -d instructs dbvisit to print a period each time it visits a new queue and a colon for
every 1,000 stories in a queue. After you have done a few cleanups, you can judge how
far dbvisit has progressed by the number of periods it has printed. When you run dbvisit,
it begins with the root file structure and then examines the entire directory. As it inspects
the root files and then the directory, dbvisit prints messages indicating its progress.
Add the -l flag (the letter L) to include the link count distribution information in the
output. If there are link count discrepancies, the system will list them. Such advisory
messages about high and low link counts are not errors, however, you will be prompted
to correct them.

n

Running dbvisit on all servers instead of just the master computer is an option, performed by
typing dbvisit -dr. The 'r' indicates read-only mode, and it can run while the read-write
dbvisit is running on the master server. The read-only dbvisit cannot be started until the
read-write dbvisit reaches the 'traversing directory' phase. After dbvisit runs on all computers,
the output can be compared to verify the integrity of the mirror.
The dbvisit process has four main phases:
-

Visiting the “root” blocks

-

Traversing the project, directory and queue structures

-

Visiting the stories

-

Updating the free list and fixing link counts

3. Beginning with iNEWS version 4.x, dbvisit was modified so that it would no longer allow
you to update the free list if critical errors are found in the database. Instead, if critical errors
are found, dbvisit will attempt to traverse the directories, reporting all errors it finds, and
then completes without offering an opportunity to update the free list. Errors reported during
the traversal of stories are not considered critical. Therefore, if the system presents you with
the question: Update the free list (y/n)?, do one of the following:
t

Type y to update the free list.

t

Type n to skip the update.

57

Maintaining the Database

n

If there are many story errors, you may want to skip the update and contact Avid to assess the
problems.
In addition to spotting errors in the database structure, dbvisit collects any unreferenced
blocks and puts them on the free list. Unreferenced blocks are not used by any story and
are not a part of the free list. They are stray blocks that cannot be used until they are put
on the free list. Skipping this update of the free list retains the old free list. While this
means that unreferenced blocks are not collected back to the free list, you can add them
to the free list later by performing another dbvisit.
4. Restart your system, by doing the following:
a.

From the PuTTYCS application, select the PuTTY Filter created for sending server
commands to all servers, such as iNEWS Consoles.

b.

Exit superuser mode by pressing Ctrl+D.

c.

Type online to bring the system back online.

d. Type restart all to restart all devices.
The system displays Hot-to-go messages as the devices start. If a device cannot be started, a
failed message is displayed for that device. Wait for the other devices to start, then use
standard procedures to restart failed devices, as covered in the Avid iNEWS Setup and
Configuration Guide.
Cleaning Your Database with Online Dbvisit
If performing a dbvisit offline prevents usage of your system for too long a period of time, there
is a way to run dbvisit while your system is online, letting system administrators do crucial
database maintenance without stopping iNEWS users from doing their work.
The strategy used to allow an online dbvisit is to checkpoint the system in a quiet/inactive state,
and to maintain the checkpoint state by copying any block that is to be change in the database
onto the checkpoint partition, namely /dev/rp5backup prior to writing the block onto the
database partition - /dev/rp5.
Your system must be shutdown briefly before initiating checkpoint mode. But after checkpoint is
turned on, you can bring your system online for iNEWS users while performing database
cleanup with the dbvisit command.

n

Do not conduct an online dbvisit without checkpoint mode initiated.If you do, not do this before
cleaning your database, you may corrupt the data when you perform the cleanup.

58

Maintaining the Database

To perform an online dbvisit:

1. Bring the iNEWS system down and close the database on all servers. This is only for the
very brief period of time it takes to ensure checkpoint mode is active.
a.

From the PuTTYCS application, select the PuTTY Filter created for sending server
commands to all servers, such as iNEWS Consoles.

b.

Type offline to take the system offline.

c.

Type logout all to logout all users. You might want to broadcast a message to users
prior to this so they can save their work and prepare for the brief downtime.

d. Type shutdown to stop all devices and close the database.
e.

The system will present a warning and question: Do you really want to do this? (y/n)?
Type y to shut down the system.

2. Initiate checkpoint mode.
a.

(Optional) Type the status command to determine which server is the master computer
and view the current status of the database.
For instance:
WAVD-A# status
A is OFFLINE and has been CONFIGURED. ID is WAVD.
System is AB. Master is A.
Disk status is OK. The database is CLOSED.

n

b.

Select the console window for the master computer (typically server A).

c.

Type checkpoint on to reopen the database in checkpoint mode.

Attempting to turn checkpoint on while the database is open will result in the following warning:
Database must be CLOSED when activating checkpoint -3. Bring the iNEWS system online.
a.

From the PuTTYCS application, select the PuTTY Filter created for sending server
commands to all servers, such as iNEWS Consoles.

b.

Type startup to start the system. This will put the system online as well as start up all
iNEWS devices.

c.

(Optional) Type the status command to view the current status of the database.

59

Maintaining the Database

For instance:
WAVD-A# status
A is ONLINE and has been CONFIGURED. ID is WAVD.
System is AB. Master is A.
Disk status is OK. The database is OPEN with checkpoint.

Users can now log in to iNEWS.
4. Start the database cleanup by doing the following:
a.

Select the console window for the master computer (typically server A).

b.

Enter superuser mode.

c.

Type: dbvisit -cd
A message similar to the following appears:
09:31:45 2013-06-30 Using checkpoint partition
09:31:45 traversing roots
-----message truncated for documentation brevity-----

The dbvisit process has four main phases:

n

-

Visiting the “root” blocks

-

Traversing the directory, queue, and project structures

-

Visiting the stories

-

Updating the free list and fixing link counts

More details on the dbvisit command syntax and all of its flags are provided in Command
References appendix of this guide. See“dbvisit” on page 512 for more information.
5. Beginning with iNEWS version 4.x, dbvisit was modified so that it would no longer allow
you to update the free list if critical errors are found in the database. Instead, if critical errors
are found, dbvisit will attempt to traverse the directories, reporting all errors it finds, and
then completes without offering an opportunity to update the free list. Errors reported during
the traversal of stories are not considered critical. Therefore, if the system presents you with
the question: Update the free list (y/n)?, do one of the following:

n

t

Type y to update the free list.

t

Type n to skip the update.

If there are many story errors, you may want to skip the update and contact Avid to assess the
problems.
6. At the end of the dbvisit process, you might be presented with the question: Do you want to
turn off the checkpoint (y/n)?
60

Maintaining the Database

t

Type y to turn checkpoint mode off.
A message similar to the following appears:
09:51:17 Checkpoint partition closed
09:51:17 complete - Elapsed time: 20:32

7. (Optional) Type the status command to view the current status of the database.
For instance:
WAVD-A# status
A is ONLINE and has been CONFIGURED. ID is WAVD.
System is AB. Master is A.
Disk status is OK. The database is OPEN.

61

5 Avid System Monitoring
This chapter provides you with information about monitoring iNEWS Server statistics via an
SNMP monitoring application such as Avid System Monitor (ASM).
This chapter contains the following main sections:
•

Using SNMP Monitoring on the iNEWS Server

•

Installing and Enabling the SNMP Agent

Using SNMP Monitoring on the iNEWS Server

Using SNMP Monitoring on the iNEWS Server
Avid iNEWS version 4.5 supports SNMP monitoring. SNMP monitoring applications, such as
Avid System Monitor, lets you monitor system level environmental information dynamically
through an SNMP agent. Avid System Monitor also lets you graph this information over time.
For example, the following data can be graphed over time in the Avid System Monitor web page
interface:
•

Average CPU load

•

Number of CPU interrupts per second

•

System uptime

•

Swap space (disk space reserved for memory when RAM is fully loaded)

•

System memory usage

•

CPU usage

By default, the SNMP Agent is not enabled.

Installing and Enabling the SNMP Agent
This section describes how to install and enable the SNMP agent on the iNEWS Server. See your
Avid representative for information about setting up an Avid System Monitor server and
configuring it to monitor the iNEWS Server.

n

These steps should be performed only by qualified Avid personnel.
To install the SNMP agent on the iNEWS server:

1. Install the net-snmp Red Hat 6 packages. This will create a /etc/snmp directory.
2. Set up the snmpd.conf configuration file. In the /etc/snmp directory, locate the snmpd.conf
file. Using a Linux editor, open the configuration file and add the following information near
the top of the file.
a.

Replace the public value in rocommunity public with your community name.

b.

Locate the line with syslocation and add your location, such as the name of your city.

c.

Locate the line with syscontact and add your iNEWS administrator email.

3. Save the changes and exit.
To enable the SNMP agent process:

t

In a console to the server, type:
# service snmpd start
63

Installing and Enabling the SNMP Agent

t

(Optional) Set snmpd to automatically start at boot by typing:
# chkconfigsnmpd on

To disable the SNMP agent process:

t

In a console to the server, type:
# service snmpd stop

64

6 Backing Up the iNEWS System
Proper maintenance of the iNEWS system requires three kinds of backups:
•

Database backups—of the iNEWS database

•

Software backups—of iNEWS software and the operating system

•

System file backups—of files like /site/config and /etc/hosts

This chapter explains the procedures for the various types of backups necessary to maintain the
iNEWS system. It also provides general information about using tapes and tape drives or
conducting a tapeless backup for iNEWS on RedHat Enterprise Linux (RHEL).

n

Previous versions of iNEWS worked on 32-bit or 64-bit RHEL; iNEWS v4.0 and later are only
qualified on 64-bit RHEL.
This chapter contains the following main sections:
•

Tape Operations

•

Backing up the iNEWS Database
-

Backing up the Entire Database to Tape

-

Tapeless Database Backup

-

Backing up Individual Queues

•

Restoring Data to the iNEWS Database

•

Disaster Recovery Planning

•

Backing up Software

•

Backing up System Site Files

Tape Operations

Tape Operations
When making backup tapes, pay particular attention to the write-protect tab on the tape. If you
have trouble writing to the tape, check the tab and try moving it in the opposite direction.
When loading a tape, ensure the tape has finished loading before issuing tape commands. Trying
to access the tape before it is ready may result in a “hung” process that waits forever for the tape
to be ready. The only solution is a reboot. For DAT tapes, wait at least a minute after all tape
activity lights cease blinking to be sure the tape is properly loaded.

n

Always clearly label tapes with the type of backup tape it is, date it was produced, and command
used to produce it. Ensure that your tapes can be found quickly, in case of emergency.
Since the database is mirrored on all servers in your system, it does not matter on which server
you produce the database backup tape. You might want to rotate which server does the database
tape dump so the tape drives wear evenly and you extend the life of the drives. Alternatively, you
might want to always run the backup on one server’s drive so you have another, relatively unused
drive standing by in case the heavily-used drive develops problems. However, for software and
site file backups, Avid recommends separate backups be made on each iNEWS Server.
Later in this chapter, various procedures are provided for checking data on tapes, searching for
specific data on tapes, and restoring data from tapes. For more information, see “Listing Tape
Contents and Backup Dates” on page 79 and “Searching a Tape” on page 82.

Establishing Policies for Backup Procedures
Since your software and system files change infrequently, you do not need to back them up very
often. Your database, however, changes hundreds or even thousands of times every day, so they
need more frequent backups
Avid recommends your station establish and follow a local backup policy for each type of data in
your iNEWS system.
The following list has some general backup guidelines:
•

Since the database is mirrored across multiple servers you have built-in hardware
redundancy. Backups also provide some protection against the rare cases of database
corruption.

•

One approach is weekly backups rotating through 5 tapes, one for each week of the month.
If you need to keep old data for a period of time you may supplement the five tape rotation
with 12 more tapes labeled with the months in the year.

•

Do not store archived material beneath daily show production queues. Segregate archive
material under it’s own directory.
66

Backing up the iNEWS Database

•

If you archive old shows on your system, you might want to produce dbdump tapes that
cover old years For instance, ARCHIVE.2008 through ARCHIVE.2009, and store them
separately.

•

It is a good idea to make extra copies of the tapes and store them off site. If your computer
room is destroyed, you can buy new servers. But if the computer room is destroyed with all
backup tapes stored in the room, your data is lost. Many corporations use off-site storage
services for backup tapes.

Backing up the iNEWS Database
Database backups provide insurance against system calamities. Also, to free up space in the
database, you can back up stories to a tape—or to a file, which can be transferred to another
computer for storage—and then remove those stories from the database.
Avid recommends making frequent backups of important material and the entire database. To
back up database items, you will need to use the dbdump console command.

The dbdump Command
The dbdump command backs up the news database, including the People files, show rundowns,
wire stories, and root database information such as user accounts, passwords, and directory traits.
All user, database, and group traits are stored within the database.
The simplest form of the dbdump command is:
NRCS-A# dbdump c

The c stands for create. When you use this command, it overwrites any information currently on
the tape and does a full database backup of everything—except the contents of any queue or
directory with its skip flag enabled.

n

The skip flag is a database trait that prevents the dbdump c command from backing up contents
of queues and directories. Generally, Wires queues and the Dead queue are usually skip-flagged
so they are not backed up. This results in less time for the backup and less tape used. If a dbdump
reaches the end of the tape and still has more data to back up, you will be prompted for another
tape. For more information on skip flags—also known as the Skip Backup database trait—see the
iNEWS Newsroom Computer System Setup and Configuration Manual.
For instance, to dump all database items contained in the SCRIPTS.2010 directory to tape, you
could type:
dbdump c -n script.2010

67

Backing up the iNEWS Database

If you already have dbdump material on tape and you want to append another dbdump to the end
of it, use the following command:
NRCS-A# dbdump ad

An append does not overwrite dbdump information currently on the tape. See “Backing up
Individual Queues” on page 75 for more information.

n

To minimize the impact of any potential problems, perform dbdump at less critical usage periods.

Backing up the Entire Database to Tape
This section provides the procedure for backing up the iNEWS database to a tape. For
information on tapeless database backups, see “Tapeless Database Backup” on page 69.
To back up the entire database to tape:

1. Insert a tape into a server’s tape drive.
2. Select the server that has the backup tape. For information on selecting a server, see the
iNEWS Newsroom Computer System Setup and Configuration Manual.
3. Type dbdump c.
A verification request similar to the following appears:
Do you really want to create a new archive? (n/y)

c

When backing up the database onto a tape, anything on that tape is overwritten by the new
copy of the database.
4. Type y to begin copying the database to tape.
Information similar to the following appears:
Starting Dump(1), block(0)
dumping isam user
...
3121 stories dumped
Ending Dump(1), block(223)

As dbdump copies, the console displays messages like those above. The number of stories
dumped and the ending block mentioned in these messages depends on your system.
When the console prompt returns, the backup is done. You can then verify the backup.
Otherwise, remove the tape from the drive. Set the tape’s write protect switch to the on
position, return it to its case, and write the date on the case label.

68

Backing up the iNEWS Database

5. (Optional) Type dbrestore tdv at the console to verify the backup was complete—that
everything you wanted backed up was copied to tape.
The dbrestore tdv console command lists every directory and queue on the tape. Since the
tape contains most of the database, this list is very long.

n

To list contents of a tape, the server must read the entire tape; therefore, listing contents takes
approximately as long as it does to back up the database to tape.
A truncated example of the output of the dbrestore tdv command looks like this:
Listing tape contents only!
Type

Stories

Name

Dir
Que

DEAD

Dir

SYSTEM

Dir

SYSTEM.KEYBOARDS

Que

1

SYSTEM.KEYBOARDS.000-INSTALLATION

3

TEST.SMITH

...
Que

3630 stories listed

The first column of the listing identifies whether the item is a queue or a directory. If it is a
queue, the second column indicates how many stories are in that queue. The third column
displays the name of the directory or queue.
If any queues in the list do not have stories listed, then either the queue has no stories, or the
queue has its skip flag enabled. If the skip flag is enabled, the queue name is copied to tape,
but none of its stories are copied. In the previous example, the Dead queue does not have any
stories on the tape.
6. When the list is complete, remove the tape.
7. Set the tape’s write protect switch to the on position, and write the date on the case label.

Tapeless Database Backup
Instead of backing up the iNEWS database to tapes for potential restoration, you can dump the
information to a file and then transfer (FTP) the backed up data to another computer for storage.
The more compact way to do this is to use the dbdump C command piped through gzip and
directed to create a file in the /tmp/directory. For instance, type:
NRCS-A$: dbdump C -f+ |gzip > /tmp/061709.gz

69

Backing up the iNEWS Database

To dump information to a file without the gzip option:

1. On an iNEWS Server, use the dbdump command in the following format:
dbdump Cv -f 

For instance, type: NRCS-A$ dbdump Cv -f /tmp/dbdump.061709
The C option creates a new dump file, and the v option switches on the verbose mode, which
gives you an idea of progress. After you enter the command, a message similar to the
following is displayed:
Starting

Dump(1)

Block(0), dumped on 2009-06-17 16:33:37

Dumping ISAM files
Dumping user
Dumping message
Dumping group
Dumping system-blobs
Dumping community
Type

Stories

Name

Dir
Dir

SHOW

Dir

SHOW.TRAINING

Que

SHOW.TRAINING.RUNDOWN

Que

SHOW.TRAINING.CG

Que

SHOW.TRAINING.VIDEO

Que

44

SHOW.TRAINING.MASTER

70

Backing up the iNEWS Database

…
Que

1

SHOW.MOSGWE

Que

31840

SHOW.VID-ID

Dir

SHOW.SCRIPTWRITING

Que

SHOW.SCRIPTWRITING.ONE

Que

SHOW.SCRIPTWRITING.TWO

Que

SHOW.SCRIPTWRITING.THREE

Que

5

Que

SHOW.NEWSTARTEST
ARCHIVE.SCRIPTS.2009

310 directories scanned
1684 queues dumped
3109046 stories dumped
Ending

Dump(1)

Block(136), dumped on 2009-06-17 16:33:37

2. On a Windows-based PC with at least 16 GB free for storage, start a command prompt
session, by selecting Start > Run and then entering CMD.
3. Navigate to the directory on the PC where you want to store the backup file by typing cd and
the directory path. In this example, the directory is C:\dbdumps.

4. At the cmd prompt, type ftp -i and press Enter to start the FTP session.

71

Backing up the iNEWS Database

5. Then type the open command using the following format:
open  49152

The numerical value at the end of the command line is the number for the port, which should
be 49152.

6. Type so and press Enter. Then enter the system operator password when prompted. A
message will appear to indicate whether the login was successful.

72

Backing up the iNEWS Database

7. Type cd /tmp to change to the /tmp directory.
8. Type binary to change to binary mode.

9. (Optional) You can list the directory contents to get the name of the file you want to transfer,
by entering the command: ls -l
10. To transfer the dump file, enter the get command using the following format:
get /tmp/

73

Backing up the iNEWS Database

The FTP command prompt will reappear in the window as a definitive indication that the
transfer has finished. However, you can check the directory on the Windows PC for the
presence of the file; it is created as soon as the transfer begins, and the size will continue to
grow during the transfer process.

n

The file will be much larger than the one shown in the example here, so the transfer can take a
while to complete. Avid suggests conducting file transfers (FTP) from computers that do not have
aggressive power saving settings in place.

74

Backing up the iNEWS Database

11. Type bye to end the FTP session.
12. Type exit to exit the command prompt window.
You are now ready to remove the temporary dump file.

n

While you can leave one or two in the /tmp folder temporarily, Avid recommends that no more
than a couple of database dump files be kept at any given time. Removal of older dump files will
help avoid running out of hard drive space on the server.
13. Use the rm command at the console to remove old database dump files from the /tmp folder
on iNEWS.
a.

Enter superuser mode, first.
NRCS-A$ su
Password:

b.

Type the rm command, using the following format: rm /tmp/
NRCS-A# rm /tmp/dbdump061709-div
rm: remove regular file ‘/tmp/dbdump061709-div’?

c.

Type y to answer verification question.
rm: remove regular file ‘/tmp/dbdump061709-div’? y

d. (Optional) When the prompt reappears, such as NRCS-A#, you can verify the file’s
removal by viewing the contents of the /tmp folder again.
NRCS-A$ cd /tmp
NRCS-A$ ls -l

Backing up Individual Queues
Individual queues can be backed up by specifying the -n flag and listing up to 10 queue or
directory names:
NRCS-A# dbdump c –n 
To back up individual queues or directories to tape:

1. Insert tape into a server’s drive and select that server.
2. Use the dbdump command in one of the following formats:
t

If you do not have a tape that already contains a backup, insert a new tape and back up
the queue. For instance, to back up SCRIPTS.2010.FEB on a new tape, type:
dbdump c -n scripts.2010.feb

75

Backing up the iNEWS Database

A verification request appears:
Do you really want to create a new archive? (n/y)

If there is nothing on the tape that you want to save, type y to continue. A message
similar to the following will appear:
Starting track(1), block(0)
47 stories dumped
Ending track(1), block(34)

n

When you back up a queue, dbdump ignores the queue’s skip flag, so you can use it to back up a
queue or directory that has its skip flag enabled. You can also use this process to save a queue or
directory to tape before removing it from the database. For instance, if you want to restore
database space by removing a queue with material no longer used, use dbdump to backup the
queue first. Then, if you need it later, you can retrieve it from the tape.
t

If you have previous backups on the tape, append the next backup to the tape with:
dbdump

a

-n



You can append additional backups to that tape until you use up all space on the tape.
Continuing with the previous example, the next day you would insert the same tape,
make sure its write protect is off, and then type dbdump a to append that day’s scripts to
the tape:
For instance, after making the first backup of SCRIPTS.2010.FEB shown in the
previous example, back up SCRIPTS.2010.MAR the following month by inserting the
same tape and entering the following:
dbdump a -n scripts.2010.mar

n

If you try to use dbdump a with a tape that does not already contain at least one backup, you get
an Empty tape message. If this happens, use dbdump c instead.
3. When the console prompt returns, the backup is done. Remove the tape and set the
write-protect switch on. Date the tape case label.
4. To verify the backup, type:
dbrestore tdv

This list should be short, but it could take time to complete if the tape contains several
weeks’ worth of backups.

76

Restoring Data to the iNEWS Database

Notes on Backing up the Database
If you try to back up data to a write-protected tape on the Linux platform, you get a message
similar to the following:
NRCS-A# dbdump c
Do you really want to create a new archive? (y/n) y
Starting Dump(1) Block (0), dumped on Thur Jul15 ‘0:36:14: 2010

dumping isam user
Please remove tape.
Insert continuation tape (make sure safety is off)
When continuation tape is ready type: y (RETURN)

If the tape is write-protected, remove it from the drive. On some tape drives you can change the
write-protect without removing the tape. Set the write protect switch to off, insert the tape, and
repeat dbdump.
Daily backups usually take very little time and generally do not affect system performance.
However, backing up a large amount of material to tape may hinder system performance, so you
should only do it during times of lighter system use.
If you have a very large database, the full database backup may require two or more tapes. The
system prompts you to insert the next tape. Remove the current tape, number it as tape number
one, and insert another tape. The server automatically continues copying the database when you
insert the second tape.

Restoring Data to the iNEWS Database
The following sections describe how to restore data from tape.

The dbrestore Command
Tapes produced with the dbdump command can be read back in and restored using the dbrestore
command. The most common use of the dbrestore command is to restore a specific queue or
directory. This is done by specifying the name on the command line:
NRCS-A# dbrestore d –n   ...

77

Restoring Data to the iNEWS Database

n

You can use the dbrestore tdv command to verify that you can properly read a dbdump tape.
Check free space before you restore large amounts of data to the database. Before you dbrestore
stories or queues to your database from tape, ensure you have enough free space available to hold
the restored stories. You can create free space using the dbserver command to empty out some of
the Dead queue and add that space to the free list. A conservative estimate would be to have 10
free blocks for every story you plan to restore.

n

When the -i option is used with the dbrestore command, dbrestore does not create any index
requests in SYSTEM.INDEX when stories are restored to indexed queues.The dbrestore process
is slowed when attempting to create index requests. Avid recommends the database be restored
using the -i option and the stories be re-indexed at a later time.

Restoring a First-Level Directory
Restoring a first-level directory, such as Scripts, as opposed to SCRIPTS.FEB, is the same as
restoring queues and other directories. However, when restoring such a directory, you also have
the option of restoring it under a new name. Use:
dbrestore

d

-n

[=]

If the new directory does not already exist, dbrestore creates it.
For instance, suppose you have a directory called Scripts and you want to restore a previous
backup of this directory to another directory called Scripts-temp, which does not exist. Type:
dbrestore d -n scripts=scripts-temp

A message similar to the following appears:
744 stories restored

Since Scripts-temp does not exist, dbrestore creates it before restoring Scripts-temp. When
dbrestore has restored all stories in Scripts-temp, it displays a message indicating how many
stories were restored.

n

If you want to restore a specific directory, be sure to always include the -n and the directory
name. If you do not, dbrestore tries to restore everything on the tape to your database, which
could cause your system to run out of space.
You may not restore a first-level directory to a lower level. In the example above, for instance, we
could not have restored the Scripts directory to SCRIPTS.MAY.

78

Restoring Data to the iNEWS Database

When you restore a first-level directory to an existing directory, it acquires the traits of that
directory. If dbrestore must create the directory, it uses database traits of the directory it is
restoring.

c

If the new directory name is longer than the old one, there is a possibility that sub-directory
names may become too long and cannot be restored. When the new name is longer than the
old name, the dbrestore program will prompt with the following warning message:
WARNING: Alias too long! It should be shorter or the same length as current directory
name to avoid exceeding directory name length restrictions.
Do you really want to continue? (n/y)

Listing Tape Contents and Backup Dates
When restoring a directory, you might need to examine the tape’s contents to ensure the directory
you want to restore is actually on that tape. Otherwise, if you attempt to restore a directory or
queue that is not on the tape, the system may take several minutes to search the entire tape before
reporting no stories restored.
The pages that follow show you how to use the dbrestore command to list the directories and
queues that have been backed up on a tape, to find out if the tape contains any stories saved after
a certain date, and to find out the date of each backup on the tape.
Listing Contents of a Tape
If you want to list every directory and queue on the tape, as well as the number of stories in each
queue, to the server with the tape drive, type:
dbrestore tdv

79

Restoring Data to the iNEWS Database

Information similar to the following appears:
Listing tape contents only!
Type

Stories

Name

Dir
Que

DEAD

Dir

SYSTEM

Dir

SYSTEM.KEYBOARDS

...
Que

3

TEST.SMITH

3630 stories listed

Each line in the list consists of three columns and identifies a directory or a queue that has been
saved to the tape:
•

The Type column indicates whether the line lists information about a directory or a queue.
Directories are identified by Dir and queues by Que.

•

The Stories column is used only in lines beginning with Que and identifies how many stories
are in that queue. Use this number as a guide to how much space you need to restore the
queue. If there is no number, the queue is empty. (The queue is empty because either no
stories existed in the queue or the queue’s skip flag was enabled.)

The Name column identifies the directory or queue by name.
If you attempt to restore a queue with no stories, you see the following message:
no stories restored

Listing Items Dumped on a Particular Date
To list items dumped on a particular date:

1. Use the following format of dbrestore:
dbrestore

td

-d



2. Enter the date in YYMMDD (year, month, day) or YYYYMMDD format.
Begin single-digit months and days with a zero, such as 04 for April. Also check for items
dumped to tape during a month by using the year and the month (YYMM).
80

Restoring Data to the iNEWS Database

You can check to see what was dumped to a tape during a year by specifying just the year
(YY).
For instance, to list everything dumped in October 2009, type:
dbrestore td -d 0910

A message similar to the following appears:
Listing tape contents only!
Type

Stories

Name

Dir
Dir

SHOW.TODAY

Que

34

SHOW.TODAY.SCRIPTS

Que

3

SHOW.TODAY.RUNDOWNS

Continuing with

Dump(2)

Block(0)

Dumped Thu Jul15 10:30:19 2009
Dir

SHOW.TODAY

Que

27

SHOW.TODAY.SCRIPTS

Que

3

SHOW.TODAY.RUNDOWNS

67 stories listed

In the previous example, the tape contains only backups from two dates: the first backup and
one made on July 15, 2009. Notice the date of the first backup is not included in the listing.
To find the date of the first backup, type the dbrestore tf command described below.
The dbrestore displays a Continuing with Dump message just before processing the second
dump.
Listing the Date of Each Backup
To list the dates of each backup on a tape:

t

Type: dbrestore tf
A message similar to the following appears:
Listing tape contents only!
Starting:

Dump(1)

Block(0)

Dumped Tue Jul10 15:33:01 2009
Continuing with Dump(2)

Block(0)

Dumped Thu Jul15 10:30:19 2009
Elapsed time: 00:13

81

Restoring Data to the iNEWS Database

In the example, the tape contains two backups, one done on July 10, 2009, and another done
on July 15, 2009.

Searching a Tape
You can retrieve individual stories from a tape by searching for a word contained in the story.
The searchtape Command
The searchtape command allows you to search through a tape looking for a specific word. Stories
that contain that word are restored to the SYSTEM.SEARCHTAPE queue. There is a maximum
number of stories or hits that will be restored with the searchtape command. This default is
specified in the /site/system file. See “Searching a Tape by Word(s)” on page 82 for more
information.

n

When you list a tape’s contents, your system must read all information on the tape to generate a
list of the contents. If the tape contains much information, listing the tape’s contents takes a
significant amount of time.
Because searching tapes for stories takes a long time and can reduce system performance,
restrict tape searches to periods of lighter system use. Avid recommends running all tape
operations during non-critical periods, not during shows.

Searching a Tape for Stories
To search a tape for stories:

1. Combine one or more keywords with a date or range of dates, as described in the following
sections.
2. When the system finds a story matching the search criteria, it restores the story to the
database. Because stories on tape may be old versions of stories still in the database, the
system restores them to the SYSTEM.SEARCHTAPE queue. This prevents the system from
putting an old version of a story in a queue that contains the current version of the same
story.
After restoring a story to SYSTEM.SEARCHTAPE, you can move it to any queue.

n

Before restoring stories from tape, check how much free space remains in your database at the
console. See “Checking for Free Space on a Database” on page 85 for more information.

Searching a Tape by Word(s)
To search a tape by word(s), follow the searchtape command with the word for and the word(s)
for which you want to search.

82

Restoring Data to the iNEWS Database

Use this form of the command:
searchtape

for



If you include more than one search word, the system searches for stories that contain any words
for which you are searching. You can search for up to 20 words at a time with this command.
For instance, to search for stories that contain either helicopter or president, type:
searchtape for helicopter president

A message similar to the following appears:
8 stories restored to SYSTEM.SEARCHTAPE

This command finds stories with the word president and it also finds stories with the word
helicopter. It would not limit the results to stories that contained both president and helicopter.

n

It is not possible to construct Boolean (and) searches using the searchtape command.
Always include the word “for” and one or more words for which you want to search when you
use the searchtape command. Even if you use a date or a date range as part of the search criteria,
as explained in the next section, you must include a word or words for which you want the
system to search.
Use search criteria that is as specific as possible:
•

Always use a narrow range of dates

•

Use a small number of search words

•

Use words likely to appear only in stories for which you are searching

Searching a Tape by Word and Date Range
To restrict a search to stories backed up between certain dates:

1. Include the range of dates to which you want to restrict the search in the searchtape
command.
The command format for this kind of search is:
searchtape from  to  for 

Dates must be in YYMMDD (year, month, day) or YYYYMMDD format, and single digit
months and days must begin with a zero (for instance, April is 04). If you want to specify
only a month or year, shorten the date format to YYMM or just YY.
2. Follow the second date with the word for and the word(s) for which you want to search.

83

Restoring Data to the iNEWS Database

To restore stories archived between May 1, 2000, and May 21, 2000, that contain the word
helicopter, type:
searchtape from 000501 to 000521 for helicopter

A message similar to the following appears:
6 stories restored to SYSTEM.SEARCHTAPE

n

The searchtape command looks for stories saved to tape within the dates you specify. It does not
look for stories created within those dates.

Searching a Tape by Word and Day
To search for stories saved to tape on a particular day, use the search format:
searchtape

just



for



To search for stories backed up on May 15, 2010 that contains the words helicopter or president,
type:
searchtape just 100515 for helicopter president

Searching a Tape by Word and Month
To search for stories saved to tape during a particular month, follow searchtape with just and
shorten the date to the year and month (YYMM).
For instance, to search a tape for any story saved to tape in February, 2009 that contains the word
helicopter, type:
searchtape just 0902 for helicopter

Specifying a Maximum Number of Stories to Search
To specify a maximum number of stories for searchtape to restore, include the word max and the
number of stories you want to restore.
To search a tape for all stories that contain the word president, type:
searchtape for president

If you do not specify a maximum, the system restores up to 50 stories.
If you specify a maximum number, searchtape stops when that number of stories has been
restored, or when all stories containing the text have been found—whichever comes first.

84

Restoring Data to the iNEWS Database

To search a tape for the first 10 stories containing president, type:
searchtape max 10 for president

Anytime you specify more than 50 stories to restore, you are reminded that this could cause the
system to run out of disk space.
When the search is complete, searchtape stops and displays a message indicating the number of
stories it has restored.
To cancel the restore operation at any time while in progress, press Delete.
Checking for Free Space on a Database
To check free space on a database:

1. Select a server.

n

For information on selecting a server, see the iNEWS Newsroom Computer System Setup and
Configuration Manual.
2. Type: dbfree.
A message similar to the following appears:
database size 16,386,300 free 3,288,408 = 20%, freelist 3,730

In the previous message example the freelist item indicates how many database blocks are
used to hold the free list. The freelist is compressed. You should have 10 free blocks for each
story you want to restore. For instance, if you expect to find 10 stories to restore, you should
have 100 free blocks. Add extra space to the free list before conducting a search because the
search may find and restore more stories than you expect.
Adding Blocks to the Free List
To add 100 blocks to the free list:

1. Select the master computer (typically server A).
2. Type: dbserver 3288508
The number after dbserver must be the sum of the additional blocks and the free blocks from
dbfree.
A message similar to the following appears:
NRCS-A Sat Jul24 10:29:26 2010 dbserver complete-exiting

At this message, dbserver is finished and you may proceed. You can run dbfree again to
verify that you have enough space.

85

Disaster Recovery Planning

Restoring the Database
When a story being restored has more than 1,000 lines, the following message is displayed:
Warning: Large story being restored.
Queue: FUTURES.FEBRUARY
Title:
Size:

"Senate Hearing"
1004 lines (approximate)

Press  to skip this story.

If the story size continues to grow, the following message prints every 1500 lines:
Large story continuing: 1500 lines
Press  to skip this story.

To skip the large story, press Delete while it is being restored.

Disaster Recovery Planning
Having a complete dbdump of the database ensures that you can restore your data in case of
calamity; however, restoring a complete dbdump to a freshly initialized database can be very
time-consuming and leave the newsroom without access to the system until the full database
dbrestore finishes. On very large databases, the full database dbrestore can take from 12 to 36
hours.
Planning a separate, efficient disaster recovery dbdump/dbrestore procedure can significantly
speed up the time before the system becomes functional to users.

Disaster Recovery Dbdump
The first step is to create a stripped down dbdump that contains the directory structure and
minimal amount of queues and directories needed to bring the system online. After the minimal
dbdump was restored, users can start working while the remainder of the database is restored
from the last full database dbdump tape.

86

Backing up Software

Create Minimal dbdump
The entire structure of the database, along with your designated minimal set of queues, can be
backed up, specifying the list of essential queues (or directories) to be backed up:
NRCS-A# dbdump ci -d -n  ...”

n

The -d option dumps the news directory skeleton but will not dump any stories. The -n option will
dump the stories in any directories and/or queues specified. The i option will dump the isam files.
The essential directories would be System and possibly Show and a few daily Assignments
queues. The System directory must be part of the minimal dbdump.
If master rundown skeletons are stored elsewhere, add them to your list of essential queues. This
may be the bare minimum of directories needed to get a show on the air.

n

Do not store archives of shows beneath the Shows directory. Having years of archive material
mixed in along with your rundowns and master rundowns will slow the dbrestore significantly. If
restoring Assignments queues, ensure you restore only daily queues needed to operate; do not
include all future files in the minimal dbdump.
You may list up to 10 directories and queues with the -n option of the dbdump program.
NRCS-A# dbdump ci -d -n system shows assignments

In case of disaster, this minimal dbdump would be the first tape restored to the system. Since it
will not contain many stories, to dbdump to or dbrestore from this tape is relatively quick and
users can resume work while the remainder of the material trickles in from the full dbdump tape.
This minimal dbdump tape should be updated periodically.

Backing up Software
Your system uses programs and site-dependent configuration files, called site files, to adapt it to
your newsroom operations and run the workstations, printers, wires, and other devices. These
programs and site files make your system software unique from that found in any other
newsroom.
It is important you keep a current copy of your software on tape in case you need to restore the
software area of the disk. Anytime you make major changes to the system software—such as
extracting new programs from an update tape—make a new software backup.

87

Backing up System Site Files

Likewise, when you make major changes to a site file, update the software backup to include
these changes. For instance, if you add a new wireserver to your system, you define that
workstation in the configuration file. This represents an important change to this site file so, after
modifying this file, update your software backup tape.

Backing up System Site Files
Your system uses site files in combination with software taken from your release CD and update
tapes. Back up your site files on a separate tape. If anything happens to your system, you can use
your release CD and site file backup to rebuild your system software.
Make a new site file backup after making significant changes to any site file. For instance,
adding a wireserver to your system requires that you modify your configuration file
(/site/config). After making this change, make a new site file backup.
To make a separate sitedump tape for each server, repeat this procedure on each server. After
backing up a server’s site files, ensure you label the tape to clearly indicate which server’s site
files are on it.

The sitedump Command
The sitedump command backs up files in the /site directory and certain key files in the /etc
directory. This is where all of your site-specific configuration files are kept. The tape should be
updated whenever you make changes to your configuration.
To back up your system’s site files to tape:

1. Insert the tape into the master computer (typically server A).
2. Select the master computer.
3. Enter superuser mode.
4. Type: sitedump
Linux systems can make sitedumps to their hard drives.
sitedump -f /backups/.sitedump

5. When the sitedump is done and the prompt returns, exit from superuser mode by pressing
Ctrl+D.
6. Remove the tape and label it. Include the date and type of backup.

88

7 Disconnects
This chapter provides vital information to help you recover from a system disconnect.
This chapter contains the following main sections:
•

Normal System Status

•

Disconnects

•

Disconnect Recovery

Normal System Status

Normal System Status
The displays will vary when the system is a triple system configuration.
On a dual server system, the status command will show the system is AB, with both servers
connected to each other. A display similar to the following will appear on server A:
NRCS-A#

status

A is ONLINE and has been CONFIGURED.
System is AB.

ID is NRCS.

Master is A.

Disk status is OK. The database is OPEN.

The system status is reported identically on both servers in the system. For instance, a display
similar to the following will appear on server B:
NRCS-B#

status

B is ONLINE and has been CONFIGURED.
System is AB.

ID is NRCS.

Master is A.

Disk status is OK. The database is OPEN.

When the system is dual and databases are mirroring between the two servers, a story written on
one server is automatically mirrored to the database of the other server. When the system is
connected and has the normal prompt, the servers are in communication with each other and the
disk mirroring process is active.

Disconnects
If the servers disconnect from each other, the databases are no longer mirrored between the two
servers and immediate attention is required. Since mirroring has stopped, stories written by users
on server A will not be seen by users logged in to server B. There will be two entirely separate
databases.
There is no way to reintegrate two disparate databases. You must decide which database will be
retained as the master database, and the other database must be erased. The steps for recovering
from a disconnect are outlined later in “Procedures” on page 95.

90

Disconnects

If a disconnect occurs, users may want to export the stories they are working on to local hard
drives, in addition to normally saving them to the server. They can export stories by selecting
File > Export Story. This will make a backup copy of the story on the local hard drive of their
PC. Since they may be logged in to the server containing the non-master database that will be
erased, this will give them a backup copy, which could be re-imported if necessary.

c

When the servers disconnect, stories written on server A are not mirrored to server B and
stories saved on B are not mirrored to A. The system issues a popup to alert users who must
contact their system administrator immediately.

Detecting a Disconnect
You can check to see if the servers are connected to each other and mirroring at any time using
the status command at the console. If they are connected and properly mirroring, they will both
agree on the system status and it will report that the system is dual (AB):
System is AB.

See “Types of Disconnect” on page 93 for more information.
If the servers disconnect, a disconnect warning message appears on the console.

91

Disconnects

On the Linux platform, the messages include detailed information from the driver (mp) that
controls the mirroring:
Jul 13 07:45:44 nrcs-a IO handler: B silent for 30 seconds
Jul 13 07:45:44 nrcs-a IO handler: LINK TO B FAILED, DISCONNECTING B
Jul 13 07:46:05 nrcs-a msg:

66 to server on computer A

Jul 13 07:46:25 nrcs-a S508: [15028] monitor 508

508 Server - Hot-to-go

Jul 13 07:46:25 nrcs-a S510: [15029] monitor 510

510 Server - Hot-to-go

Jul 13 07:46:25 nrcs-a S238: [14998] seek 238

238 Server -

Hot-to-go

Jul 13 07:46:25 nrcs-a S240: [14999] seek 240

240 Server -

Hot-to-go

Jul 13 07:46:25 nrcs-a S236: [14997] seek 236

236 Server -

Hot-to-go

Jul 13 07:46:25 nrcs-a S232: [14995] seek 232

232 Server -

Hot-to-go

Jul 13 07:46:25 nrcs-a S234: [14996] seek 234

234 Server -

Hot-to-go

Jul 13 07:46:25 nrcs-a S254: [15001] action 254

254 Server -

Hot-to-go

Jul 13 07:46:25 nrcs-a S504: [15026] monitor 504

504 Server - Hot-to-go

Jul 13 07:46:25 nrcs-a S506: [15027] monitor 506

506 Server - Hot-to-go

Jul 13 07:46:25 nrcs-a S508: [15028] monitor 508

508 Server - Hot-to-go

Jul 13 07:46:25 nrcs-a S510: [15029] monitor 510

510 Server - Hot-to-go

Jul 13 07:46:25 nrcs-a S238: [14998] seek 238

238 Server -

Hot-to-go

Jul 13 07:46:25 nrcs-a S240: [14999] seek 240

240 Server -

Hot-to-go

Jul 13 07:46:25 nrcs-a S236: [14997] seek 236

236 Server -

Hot-to-go

Jul 13 07:46:25 nrcs-a S232: [14995] seek 232

232 Server -

Hot-to-go

Jul 13 07:46:25 nrcs-a S234: [14996] seek 234

234 Server -

Hot-to-go

Jul 13 07:46:25 nrcs-a S254: [15001] action 254

254 Server -

Hot-to-go

Jul 13 07:46:25 nrcs-a S258: [15003] action 258

258 Server -

Hot-to-go

Jul 13 07:46:25 nrcs-a S252: [15000] action 252

252 Server -

Hot-to-go

Jul 13 07:46:25 nrcs-a S256: [15002] action 256

256 Server -

Hot-to-go

92

Disconnects

Jul 13 07:46:25 nrcs-a disconnect: B COMPUTER DISCONNECTED

In addition to console warning messages, a warning message is broadcast to all users currently
logged in to the system via a popup window at the workstations.

Types of Disconnect
When the servers disconnect, one may disconnect from the other, or they may both disconnect
from each other.
If they have disconnected from each other, each will report that it is a single system, with itself as
the master:
NRCS-A#

status

A is ONLINE and has been CONFIGURED.
System is A.

ID is NRCS.

Master is A.

Disk status is OK. The database is OPEN.

The single system status is reported identically on both servers:
NRCS-B#

status

B is ONLINE and has been CONFIGURED.
System is B.

ID is NRCS.

Master is B.

Disk status is OK. The database is OPEN.

The other possibility is that servers will disconnect, but one of the servers will not note the
disconnect. In this case, one will report that the system is single while the other states the system
is still AB.
Regardless of the report, once one of the servers has disconnected, the system must be recovered
following the procedures in this chapter. The steps outlined are the only way to recover and get
the servers back in mirror.

c

If the system has disconnected, you cannot simply reboot the servers and bring it back up
normally. Rebooting and connecting two servers together after a disconnect can lead to
database corruption!

93

Disconnect Recovery

Causes of Disconnects
Servers are normally in constant communication with each other. When a story is saved, the
server tries to mirror that change across to the other server’s database. If the server cannot
contact the other server for a period of 30 seconds, it assumes the worst—that the other server
has died and is not available and that as the surviving server it must be responsible for the entire
system.
Knowing this design, it is obvious that network outages will cause a disconnect, as will the loss
of power by one server.
A “dirty” network leading to numerous network output errors (called RX-ERRs, as revealed by
the netstat -i command) can cause a disconnect, particularly if the output errors are rapidly
climbing.
A software error that leads to a looping condition that causes a server to become so busy it
cannot respond to a mirroring request could also theoretically lead to a disconnect.
Hardware failures such as the failure of a network card or hard drive may also lead to
disconnects.

Disconnect Recovery
This section provides an overview of recovering your system from a disconnect, recovery
procedures, and a quick reference worksheet you can use should a disconnect occur.

Overview
After a system has disconnected, one server must be selected to continue on as the master
computer. This server will be referred to as the survivor. The other server will be referred to as
the failed server.
Before the failed server can be reconnected to the survivor, it must be rebooted and its database
wiped clean. After the database on the failed server has been cleared, the server can be
reconnected to the survivor and the master database copied back across from the survivor.
Because one server’s database will be selected as the master database and the other’s database
erased, discovering a disconnect as soon as possible minimizes the possibility of data loss.
In normal dual-server operation, half the devices and sessions are configured on one server and
the other half are configured on the other server. The most important thing to do after a
disconnect is to reconfigure the survivor so that it knows it must be responsible for all devices
and sessions. You can then restart any network devices that were running on the failed server.
94

Disconnect Recovery

n

The steps are covered in more detail in the next section, “Procedures” on page 95.
The disconnect recovery steps are as follows:
1. Reboot the failed server.
2. Clear the database on the failed server.
3. Reconnect the failed server.
4. Copy the database to the failed server.
5. Log out and stop all servers and resources.
6. Reconfigure the system.
7. Start up all servers and resources.

Procedures
This section contains an example of recovery from a disconnect of a dual AB system. The steps
might vary when the system is a triple system configuration. Triple system configuration
customers might need to contact Avid for more specific instructions.
In the example, it is assumed that server A was chosen as the survivor and server B was
designated the failed server:
•

NRCS-A–survivor

•

NRCS-B–failed server

The failed server is also referred to as the revived server after it is reconnected to the system.

n

If you reverse the roles of the servers during your disconnect and make B the survivor and server
A the failed server, remember to adjust which server you issue the commands on appropriately.
The steps shown in the following example assume server A is the survivor; reverse A and B
throughout the process if server B is chosen as your survivor.
It is assumed (for this example) that when the servers disconnected, server A became a single
system (system is A, master is A) and server B also became a single system (system is B, master
is B). In this situation, users logged in on A can continue working and saving stories. Users
logged in on B can also continue working and saving stories, but since the servers are not
mirroring, anything saved to server A’s database is not copied over to server B’s database, and
vice versa.
The databases on the machines are no longer mirrored. The only recourse is to choose one of the
servers’ databases to become the master database. The database on the other server is wiped
clean and then recopied from the master server.

95

Disconnect Recovery

To export a story to a local hard drive:

t

Select File > Export Story.
Users logged on to the failed server (B) are creating stories on a database that is going to be
wiped clean. That information will be lost unless stories created after the disconnect are first
exported to the local hard drive so they can be imported to the survivor once the user logs in
to the other server.

To recover the system:

1. Choose one master machine to continue working with (survivor)
It does not matter whether you choose server A or B as your master computer. What is
important is to choose one quickly. You may choose one server over the other if it has more
users logged in on it. Or you may choose the server that has the show producer logged in on
it. If you are about to enter a show, you may pick the one that runs the teleprompter. Or you
may choose A as the survivor so the steps exactly shadow instructions in this section.
2. Halt and reboot the disconnected (failed) server using the following command:
NRCS-B# shutdown
NRCS-B# reboot

3. Log in to the rebooted failed server as system operator, then become superuser.
a.

At the login prompt, log in as the system operator user (so):
iNEWS Newsroom Computer System
login: so
Password:
Last login: Mon Jul 19 07:17:23 on ttyS0
?:

b.

When you log back in you will be at the question mark prompt because the server is not
yet named (connected). You must be in superuser mode for the next step:
?:su
Password:
?#

n

For more information on superuser mode, selecting servers, and configuring the system, see the
iNEWS Newsroom Computer System Setup and Configuration Manual.
4. Select the failed (disconnected) server on the console and use the diskclear command to
wipe the database off the failed server.

96

Disconnect Recovery

The display will look similar to the following (with what you type appearing in bold):
?# diskclear DANGER -- This program DESTROYS all information on this computer's data
base.
Do you wish to save the current data base? (y/n): n
Are you sure you wish to CLEAR the disk? (n/y): y
?

Mon Jan

3 16:18:23 2000 diskclear CLEARING DATA BASE

? Mon Jan 3 16:18:23 2000 Each dot represents 10,000 blocks. The entire
database = 1677 dots.
........10.........20.........30.........40.........50
.........60.........70.........80.........90.........100
.........110......

The diskclear will print a sequence of dots and numbers as it clears the disk. For instance, on
a full 16 gigabyte database, the dots and numbers count to 16,000. The diskclear may take
some time to complete.
5. Reconnect the failed server to the survivor.
a.

After the diskclear has completed you can reconnect the servers. Select both (all) servers
on the console and type:
reconnect  master= net=ab

b.

Depending on which one failed and which one is master, you would enter one of the
following commands:
reconnect a master=b net=ab
reconnect b master=a net=ab

A few moments after entering the command, the failed server will regain its normal,
named prompt. Communication and mirroring between the servers is reestablished.
6. Begin copying the database back over to the failed server.
a.

Select the revived (failed) server only on the console and begin a diskcopy:
NRCS-B#

diskcopy -9

Users can continue working while the diskcopy continues in the background.
7. When the diskcopy has completed, stop all servers and devices.
At this point, all devices and sessions are running on the survivor—that is, master
computer—even the ones that normally run on the other, revived server. These devices,
utility programs, and sessions eventually need to run in their normal place on the revived
server.
97

Disconnect Recovery

Schedule a time to log the users off and stop the servers and devices. At that time, run the
following commands on the survivor:
NRCS-A#

offline

NRCS-A#

logout all

NRCS-A#

stop all

8. Reconfigure the system (survivor).
The system is now running in a dual AB configuration. When you run the configure
command, the system will reconsult the /site/config file and divide responsibility for which
server will run the devices, half for server A and half for B:
NRCS-A#

offline

NRCS-A#

configure

NRCS-A#

online

Wait for the system being configured messages to appear on both servers before moving on
to the next step.
9. Start up the revived server.
When you run startup on the revived server, the devices and utility programs (such as action
servers or txnet links) on that server are started and it is placed online:
NRCS-B#

startup

10. Restart all of the survivor’s devices by typing restart all on the master computer. The
system is now running normally (dual) with all sessions and devices in their normal places.
If server B was selected as the master database, it is now the master computer. Since either
server can run as master, nothing further needs to be done. If you want to make server A the
master computer again, perform a normal system shutdown, reboot and startup, as described
in iNEWS Newsroom Computer System Setup and Configuration Manual.

c

Wait for the diskcopy to complete before rebooting the system to make server A the master
computer again. Database corruption may result if the system is taken down before the
diskcopy completes. If the system loses power or must be rebooted; the master computer
that contains the full database must be brought up in a single server configuration, and the
disconnect recovery procedure restarted again.

98

Disconnect Recovery

Recovery Worksheet
The following Disconnect Recovery table lists:
•

Commands involved with recovering from a disconnect

•

Whether the command is run on the failed server, survivor, or both servers

•

Offers a column where you can fill in the name (either A or B) of the server that fits that role
(either survivor or failed)

You may want to photocopy this table and write in names (letters) of your survivor and failed
servers in the boxes for each step.

n

Before proceeding, review and understand the narrative steps in the previous section
“Procedures” on page 95.
The table’s procedure shows Method 2 (logout all, stop all) of splitting the workload to get the
devices, utility programs, and sessions back to their regular positions.
Computer

A/B

Commands to Run:

survivor

Enter superuser mode.

failed

shutdown
reboot

Login as system operator.
Enter superuser mode.
diskclear -

both

AB

reconnect  master= net=ab

Type either of the following:
reconnect a master=b net=ab
reconnect b master=a net=ab

failed

diskcopy -9

99

Disconnect Recovery

Computer

A/B

Commands to Run:
offline

survivor

logout all
stop all
configure

both
survivor

AB

Wait for the “system being configured” messages on both
restart all
online

failed

startup

Be patient for the server to come up.

100

8 Troubleshooting
This chapter provides information to help you recover from various kinds of system failures.
This chapter contains the following main sections:
•

iNEWS Workstation Problems

•

Wire Problems

•

Locked Blocks

•

How to Check Process Status (ps Command)

•

Power Failure

•

Network Failure

•

iNEWS and FTS Connectivity (ftsdebug Command)

iNEWS Workstation Problems

iNEWS Workstation Problems
This section explains common problems users might have during daily operations. Possible
solutions appear after each problem.

n

A user who installs the client software, iNEWS Workstation, must have Administrator or Power
User permission.

A User Cannot Log in
If a user is unable to log in to the iNEWS Workstation and gets the Invalid User Name/Password
error message, ensure the user:
•

Entered correct user name and password, spelled correctly

•

Specified proper server name

Use the list u console command to verify a user with that name exists on the system.
If the password is a problem, assign the user a new password. Then, force a password change to
maintain security. See “Database Security” on page 39 for more information.

A User Cannot Establish a Session
If the user is properly entering user name, password and server name, but the login attempt
“hangs” and then begins to cycle through alternate server names, wait until the login attempt
times out and follow these steps:
To check server network connections:

1. Try to ping the server to check network connection to the server, by doing the following.
a.

Click Start.

b.

Select Programs > Accessories > Command Prompt to open a DOS window.
The name and location of this submenu option might vary depending on the
Windows-based operating system.

c.

Enter the following command, substituting the name of your server:
C:\>ping nrcs-a

102

iNEWS Workstation Problems

A message similar to the following should appear:
Pinging nrcs-a [10.1.38.30] with 32 bytes of data:
Reply from 10.1.38.30: bytes=32 time<10ms TTL=255
Reply from 10.1.38.30: bytes=32 time<10ms TTL=255
Reply from 10.1.38.30: bytes=32 time<10ms TTL=255
C:\>;

If you do not get replies, then the server is either down or a networking problem exists.
A brief message, similar to one of the following lines, might appear:
Bad IP address nrcs-a
Bad host nrcs-a

The iNEWS Workstation is unable to look up the name to obtain the IP address of the
server. It is unable to resolve the host name. This indicates the name entered in the login
dialog box does not exist in the local hosts file on the PC or on the Domain Name Server
(DNS) if your network is configured to use a DNS.

n

The workdebug command may be used in system operator or superuser mode.
2. If the workstation can successfully ping the server, the next step is to run the workdebug stat
command on each server at the console.
The workserver process runs on iNEWS Servers that manage the connection between PCs
and servers. The workdebug stat command queries the workserver to obtain a list of how
many sessions are configured and how many are currently logged in:
NRCS-A# workdebug stat
workserver: configured GUI general count: A 19 B 0 C 0 D 0
workserver: running GUI general count: A 0 B 0 C 0 D 0
(etc)

If workdebug stat does not return a response at the console, this may indicate the workserver
process has either died or entered a non-responsive state. The workserver process may need
to be killed and restarted. Contact Avid for further instructions.
3. If you get a response from workdebug stat, you can put workserver into a diagnostic mode
where it will display messages on the screen when PC clients attempt to establish a
connection. To do this, select the filter to send commands to all servers via the PuTTYCS
application and type:
NRCS-A$ workdebug debug

103

iNEWS Workstation Problems

The message returned when the workstation attempts to log in may give you a clue as to the
problem. If no messages appear when the workstation tries to log in, then the workstation is
not reaching the server. Use the workdebug command again to turn off debugging mode and
stop the diagnostic messaging, by typing:
NRCS-A$ workdebug silent

A User Cannot Access an Item
If a user cannot read or write stories in part of the database, he or she may not have permission to
do so. Check the user’s group permissions.
Group Permissions
To assign permission to a user:

1. Use the list g  command to determine which groups the user belongs to.
2. Compare assigned user groups to groups assigned to the directory or queue. To do this, use
the list d-g  command.
3. If necessary, add the user to the appropriate group story or stories in SYSTEM.GROUPS.
See the iNEWS Newsroom Computer System Setup and Configuration Manual for more
information.
If a user can create new stories in a queue, but not edit existing stories, it may be because existing
stories were created when the queue had another write group assigned to it. Previous stories
would have been created with previous security restrictions. To change the group permissions on
existing stories, use the gtraits command in the following format:
gtraits c 

A user may also be unable to access a queue or story in the database if another user is ordering
that queue or editing the story. The queue or story becomes “free” when the other user finishes
the operation, but until then, it is considered to be “busy.”

Busy Stories
Only one user can edit a story at a time. No one else can edit that story until the first user is done
with it. If a second user tries to edit a story that another user is working on, the second user will
get a message that the story is busy. When a user opens a story for editing, the system puts an edit
lock on the story and removes it when the user saves the story and gets out of it. Edit locks
prevent multiple users from making changes to stories.
Similarly, when a user goes into order mode, the system puts an order lock on the queue. No
other user can change the order of stories in the queue until the first user exits order mode.

104

iNEWS Workstation Problems

If a user is editing a story and the system crashes, or the user’s PC locks and needs to be
rebooted, the edit lock placed on the story remains attached to the story. When the system comes
back up or after the user logs back in, he or she might be unable to edit the story. The edit lock
will prevent anyone from making changes to the story and users trying to open the story will get
a story busy message.
The story must be unbusied before any user can get back into it.
This is also true of order lock. If a user’s PC crashes while he or she is in order mode, the order
lock remains behind. Both edit locks and order locks are removed with the unbusy command.
The syntax is:
unbusy 

You must know the exact queue name to unbusy it, such as SHOW.6PM.RUNDOWN.
When you unbusy a queue and there is an order lock on it, you are first asked whether you want
to remove the order lock. Then you are asked whether you want to unbusy each busy story in the
queue.
You can respond with yes to remove the edit lock or order lock, no to skip that story, or quit to
exit.

c

Care should be taken when removing edit locks. Do not unbusy stories that users are still
working in. If you do, when they try to save the story it will be saved to the Dead queue.
You might see messages on the console about edit-locked (busy) stories in the Dead queue. A
large number of edit-locked stories at the bottom of the Dead queue can cause problems, and
they should be unbusied.
The Dead queue is usually large and an unbusy on the entire queue could take a long time to
execute.
To unbusy edit-locked stories in the Dead queue:

1. Enter superuser mode on the console.
2. Use the unbusy command to remove the edit locks.
NRCS-A# unbusy -i dead

The -i option allows the unbusy command to ignore the inverted attribute.
3. The system will prompt you for confirmation. After answering “yes” to unbusy the stories,
watch for when the system is no longer finding busy stories. You can then break out of the
unbusy process with Ctrl+\ (Control-backslash) or use the Delete key to “interrupt” the
unbusy process.

105

Wire Problems

Wire Problems
This section explains common problems users might encounter with their wire ingests during
daily operation.

Data Receiver
The Avid Data Receiver provides an Administration application that may be used to troubleshoot
most issues related to ingesting wires to iNEWS using a Data Receiver instance. For more
information, see the Avid Data Receiver Installation and Operations Manual.
If stories are not being sent to iNEWS—that is, the number of stories processed never increments
in the Administration application—ensure raw data logging is enabled and functioning. If it’s
not, check your hardware connection and the Data Receiver configuration. If some raw data is
being logged, but stories are still not being sent to iNEWS, then check the start/stop sequence
configuration for Serial and Telnet input types. Also ensure file logging is set to ALL and check
the log file for parsing errors. This would indicate a possible problem with parsing NSML, which
could make iNEWS reject stories when Data Receiver attempts to send them.

Locked Blocks
During normal operations the system constantly locks and unlocks blocks on the servers’ hard
drive as data is accessed. Occasionally, something may go wrong and a locked block is left
behind.
If you have a persistently locked block, any other process that tries to access the locked block
will wait for the block to become available. The usual scenario for this problem is that PCs start
hanging in the newsroom when users get to a story in a rundown that is in a locked block. Users
then move to another PC, and hang that one too when they access the locked block story.
If the original locked block is unlocked, then all frozen PCs “unhang.”
To check for a locked block, type the dblock command on all servers. Type dblock several times
in succession and note the block numbers reported. If block numbers are changing, then the
process is not hung up on a locked block. If the block number and process ID number remain the
same through successive dblock commands, then it might be a locked block situation. If a block
remains locked for more than one minute, the system will print a diagnostic on the console and
will repeat the message every minute the block remains locked. The system will remove block
locks owned by processes that have exited.
If you have a persistently locked block, contact Avid.

106

How to Check Process Status (ps Command)

How to Check Process Status (ps Command)
Occasionally, the support staff might ask you to run a few Linux commands to troubleshoot
problems. One of the most common would be a request to check on the status of a process using
the ps command.
NRCS-A$ ps -ef

The ps -ef command returns a list of all the processes currently running on the server. On large
systems there can be hundreds or even thousands of processes.
The process list gives useful information about each process including the process owner, when
it was started, on which terminal port it started, how much processor time has been expended on
the process, and so forth.
You can also use piping with the fgrep command to search the process list for a particular
process and check whether it is running. This example produces a full process list and then filters
it for the lines that contain the word, workserver:
NRCS-A$ ps -ef | fgrep workserver

When you use fgrep on the process list for a specific word, two processes are usually returned in
the display. One line is the process you are looking for, and one line is the fgrep process that
looked for that word.
If you know a particular process ID number, you can check to see if that process is running or has
completed:
ps -p 

If the process is still running, you will get a one-line process list for that number:
PID TTY

TIME CMD

516 tablet

0:01 workserver

If it is not running, the command will simply return a header line like this:
PID TTY

TIME CMD

You might also use ps -fp for a fuller listing.

107

Power Failure

Power Failure
If you experience a power failure, the servers will reboot. After they work their way back to the
login prompt and you have logged in, the servers will not be named, they will be at the question
mark-colon prompt.
?:

If both servers went down at the same time, the databases will still be in mirror and they can be
connected normally and started up:
To connect and start up servers after a simultaneous power failure:

1. On all servers simultaneously, type: connect 
2. To remove edit locks, on the master computer only, type: dbclean -x .

n

This command is not strictly necessary. “Stale” edit locks are detected and ignored. An edit lock
is considered to be “stale” if the session that owns the lock no longer exists or if the session was
started—logged in—after the edit lock was acquired.
3. On all servers simultaneously, type: startup
If they are plugged into different UPSs and they ran through the UPS battery and then lost
power and rebooted, you will not know if they went down concurrently. One UPS might
have run longer than another. If so, more stories may have flowed in on a wire or been saved
by a user while the one server was still up and the other was down. The database will not be
in mirror and you will need to go through the recovery process.

Network Failure
The iNEWS newsroom computer system is a networked client-server application. A
well-running Ethernet network is essential for proper communication between the devices. A
network failure can disable the entire system.
The simplest way to test network connectivity is to try to ping other computers on the network.
When you ping a server, your computer sends a “pulse” across the network. The pulse then is
echoed back from the target server and returns to the sending computer in the form of ICMP
replies. If the network or server is down, you will not get replies from the server (or computer)
you are trying to ping. You can ping a computer using its IP address or name, as shown in the
following examples:
NRCS-A$ ping -c 5 152.165.17.110
NRCS-A$ ping -c 5 nrcs-a

108

Network Failure

In the previous ping command examples, the number of ping requests sent would continue
endlessly. To control the number of ping requests use a specific number to limit the number of
requests. For instance, in the following examples, five ping requests will be attempted as noted
by including the number 5 in the ping command.
NRCS-A$ ping 5 152.165.17.110
NRCS-A$ ping 5 nrcs-a

In the case of an iNEWS Workstation that is having problems connecting, the first step is to try
pinging the server from the workstation to make sure they can see each other on the network.
(The syntax for ping on Windows is different than the Linux ping command.)
If computers are unable to ping each other, check for a loose or disconnected network cable or a
hub that might have lost power.

netstat -i Command
One diagnostic command you can run on the server to quantify network errors is the netstat -i
command. The netstat -i will show:
•

How many packets have been transmitted

•

How many input errors (RX-ERRs) have been detected

•

How many output errors (TX-ERRs) have occurred

Output Errors (TX-ERRs)
The primary barometer of network health is the output errors (TX-ERRs) column. The computer
will try to transmit a packet 15 times before chalking the attempt up as an TX-ERR. It will then
try to transmit again 15 times and may wind up incrementing the TX-ERR count. Clean
networks will show zero TX-ERRs, or no more than a few.
Of more concern than the raw number of TX-ERRs is how quickly they are increasing. If you are
picking up an TX-ERR every minute, this would be indicative of network problems and a
disconnect may be imminent.
Periodically run a netstat -i so you can get a baseline feel for how many TX-ERRs your system
produces each week or month.

Input Errors (RX-ERRs)
Input errors (RX-ERRs) are fragments of packets or unrecognizable packets. Systems
co-existing on a Novell Local Area Network (LAN) generally show many RX-ERRs, although
they do not seem to cause problems.
109

iNEWS and FTS Connectivity (ftsdebug Command)

iNEWS and FTS Connectivity (ftsdebug Command)
For more information about Fast Text Search and its utility programs, see the iNEWS Newsroom
Computer System Setup and Configuration Manual.
The ftsdebug command can be used to verify communication between the iNEWS Servers and
the two server (utility) programs related to Fast Text Search (FTS). It can also be used to
compare the contents of indexes and indexed queues, adjust the indexes, and is a vital tool for
FTS troubleshooting and operation. The format for the command is:
ftsdebug [index | search] 

The index option will apply the ftsdebug command to the utility program used by FTS, known as
the ftsindex server or ftsidx.exe. The search option will apply the ftsdebug command to the
utility program known as the ftsseek server or ftssch.exe.
Parameter

Description

closelog

Close the log file (leaves log intact).

debug

Set debug log level for the program to:
Level 0 - no logging done
Level 1 - each action logged
Level 2 - request parameters logged
Level 3 - request parameters and log each action

openlog

Open/reopen the log (truncates existing log).

shutdown

Shutdown the program on the FTS server.

n

There is no start parameter because the FTS
programs must be started from the FTS server.

statistics

Show program version, start time, and statistics.

viewlog

Print the contents of the log file

Limited to index only:
showrequests

List pending index requests (SYSTEM.INDEX)

tune on | off

Turn tuning on or off or force a major tune.

tune 

Types of tunes are: minor, major, and absolute (which
tunes immediately)

110

iNEWS and FTS Connectivity (ftsdebug Command)

Parameter

Description

Limited to search only:
adjust [-v] 

Compare FTS index for  against database content
and fix discrepancies. Used to bring indexing
up-to-date. For instance, type:
ftsdebug index adjust archives.2002

compare [-v] 

Compare FTS index for  against database
content.

list [-n] 

List FTS index entries for 

search [-v] 

Search FTS index for  terms

Checking Communication between iNEWS and FTS Servers
Verify communication from the iNEWS Servers to the FTS utility programs running on the
Windows-based FTS server by using the following forms of the ftsdebug command:
ftsdebug index stat
ftsdebug search stat

These commands may also be used to monitor the indexing process.
After each command is entered at the console, a display of statistics about the utility program,
either the ftsindex server (ftsidx.exe) or the ftsseek server (ftssch.exe), appears. The display will
vary depending on which form of the command you used. Samples of each are shown in the
following two columns:

111

iNEWS and FTS Connectivity (ftsdebug Command)

NRCS-A$ ftsdebug index stat

NRCS-A$ ftsdebug s stat

Program name: ftsidx.exe

Program name: ftssch.exe

Version: 3.1.0.2 FTS

Version: 3.1.0.2 FTS

Process id: 1172

Process id: 2024

Started: 06/17/10 09:00:52

Started: 06/17/10 09:00:52

Debug value: 0

Debug value: 0

Tuning: on

Current Role: 1

Index Base: C:\FTS

Index Base: C:\FTS

Current Index: 029
Requests Serviced: 57

Indexed Documents: 1386610
Requests Serviced: 1669414
000 File sizes (KB): 499/440 508/1 713 1
Documents: 1346 Added: 2759 Removed: 1393 Replaced: 15
Purged: 35
002 File sizes (KB): 1/0 1/0 2 1
Documents: 2 Added: 2 Removed: 0 Replaced: 0 Purged: 0
005 File sizes (KB): 223941/223921 45479/1 402846 1
Documents: 962661 Added: 962661 Removed: 0 Replaced: 0
Purged: 0
029 File sizes (KB): 310330/302993 79098/1 156588 1
Documents: 356213 Added: 459650 Removed: 61 Replaced: 0
Purged: 103376
040 File sizes (KB): 53628/0 147319/0 28849 1
Documents: 66388 Added: 131984 Removed: 48163 Replaced: 7
Purged: 17440

The number of requests serviced includes index requests, purge requests, and ftsdebug status
requests, so it is unlikely to match the number of indexed documents.
If communication with the FTS utility programs on the FTS server is unavailable, the ftsdebug
command will hang, and then eventually time out and respond with a message that it couldn’t
connect. If this happens, check the Windows-based FTS server to see whether it rebooted. Also,
confirm whether the utility programs (ftsidx.exe and ftssch.exe) are running. Stop and restart
them, then check for communication again.

112

iNEWS and FTS Connectivity (ftsdebug Command)

n

If the ftsdebug command hangs, you can break out of it by pressing the Control and C keys
(Ctrl+C).

Community
The iNEWS Community communication protocol requires compatibility between server
versions and database sizes, as explained in the Avid iNEWS Setup and Configuration Guide.
When incompatibility occurs between systems in an iNEWS Community, error messages are
provided.
The following table shows error messages and the cases in which they appear.
Case

Error Message

iNEWS version 3.4.5 with large database
connecting to version 3.4.3 or earlier

local: G###: Error (1) during SETCOMMUNITY
to 
remote: C###: Cannot service request: eB

iNEWS version 3.4.3 or earlier connecting to
version 3.4.5 with large database

local: G###: Unable to set community server
number with  (9)
remote: C###: Cannot participate in small
database community

iNEWS version 3.4.5 with large database
connecting to version 3.4.5 with small database

local: G###: Unable to set community server
number with  (9)
remote: C###: Cannot participate in large
database community

iNEWS version 3.4.5 with small database
connecting to version 3.4.5 with large database

local: G###: Unable to set community server
number with  (9)
remote: C###: Cannot participate in small
database community

iNEWS version 3.7.0, configured for large
database, connecting to version 3.5.2 with small
database.

local: G####: Community system  does
not support a large community
remote: C###: Exit: Error communicating with
Client (16:Recv)  RH5

iNEWS version 3.7.0 connecting to version 3.5.2. local: G###: Community server 
The client is using communication protocal (from communication error (16)
newer version) that the remote system does not
remote: C###: Exit: Error communicating with
understand.
Client (24:Protocol level)  RH5

113

iNEWS and FTS Connectivity (ftsdebug Command)

n

There was no version 3.4.4 of iNEWS released.

114

A Command References
Most of your system’s commands are special commands provided by Avid. The commands you
are most likely to need are listed and explained in this appendix, along with examples.

c

Some available commands are meant to be used only by Avid technicians or under the
supervision of Avid personnel. These commands may cause damage if used improperly.
They are listed in this appendix on “Commands Used by Avid Personnel Only” on
page 116.
This appendix contains the following main sections:
•

Programs Invoked by iNEWS

•

Commands Used by Avid Personnel Only

•

Linux Commands Used in iNEWS

•

Console Server Commands

•

Job List Commands

•

Dialog Commands

Programs Invoked by iNEWS
The following programs are invoked and used by your iNEWS system. Do not use them as
commands.
action

ftsseek

nxserver

bio.conf

gnews

parallel

bioserver

ismessage

rxnet

boot

keyword

seek

brand

license

server

cgi-fcgi

mailserver

snews

connect.sh

monitor

start

Commands Used by Avid Personnel Only

copyright

monserver

txnet

disconnect

news

webaccserver

distribution

newsmail

workserver

ftsindex

NewsWeb.fcgi

Commands Used by Avid Personnel Only
The following commands are used by Avid personnel only.
attach

dbsize

netterm

bdump

detach

nsupgrade

binhex

diddle

qcheck

biodebug

edit

qstampcheck

biolatency

finit

qxcheck

biosleep

ftsdebug

rcat

biostat

gnewslog

strerror

catcheck

ifis

sysname

ccuputkey

ifmaster

traverse

clearflagbyte

ifsu

userclean

cmrdebug

keycheck

wordbreaks

dbcopy

kwdcheck

workdebug

dbgen

link

wxlate

dblinks

msgdebug

xi

dblock

Linux Commands Used in iNEWS
The following Linux commands are available in iNEWS. For more information, see the
reference material that came with your Linux system. To obtain command syntax and other
usage information, type the man command along with the command name.

116

Console Server Commands

For instance, to get information about the grep command, type: man grep
cat

kill

pwd

cp

more

rm

date

mv

sync

df

passwd

telnet

grep

ps

Console Server Commands
You must enter commands in lowercase. Your system does not recognize commands entered in
uppercase.

broadcast
broadcast [-dl | --] 

Sends a message to everyone logged in. The -d option will issue the broadcast in a popup
window. The -l option will issue the broadcast only to those directly logged in to the local
system, not through Community. For instance, to send a message, select one server and type:
NRCS-A$ broadcast -d System going down at 12:00

n

Certain characters are interpreted by the bash shell program, so when including characters,
such as angled brackets, exclamation points, asterisks, or pound signs (<,>,!,*,#) in the
, the entire message should be placed within quotation marks to prevent the program
from interpretting them.
Use the double-hyphen (--) option when message begins with a hyphen (-).

configure
configure [-ns] [ [ ]]

Incorporates changes to your configuration file into your system’s operation, and checks the
configuration file for any errors.
For instance, suppose you made changes to rxnet 310 and 311, which are connected to server A
in an AB system. To test these changes, become a superuser and type:
NRCS-A# configure /site/config ab a
117

Console Server Commands

If no  is specified, /site/config is used.
If a service has been added to a database story in SYSTEM.SERVICE, use configure -s so the
service can be recognized.
If an Ethernet or Internet address has been added to a database story in the
SYSTEM.CLIENT.WINDOWS directory, use configure -n to validate the address and allow it to
be recognized by the system.
In both cases, you must first take the system offline, enter the configure command, then put the
system back online.

connect
connect



[

Source Exif Data:
File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.6
Linearized                      : Yes
Encryption                      : Standard V4.4 (128-bit)
User Access                     : Print, Copy, Extract, Print high-res
Author                          : Avid
Create Date                     : 2014:12:10 14:35:58Z
Modify Date                     : 2014:12:10 22:29:01-06:00
Part Number                     : 9329-65311-00 Rev C
Writer Editor                   : BBL
Has XFA                         : No
Language                        : en
XMP Toolkit                     : Adobe XMP Core 5.2-c001 63.139439, 2010/09/27-13:37:26
Format                          : application/pdf
Title                           : Avid iNEWS v5.2 Administration Guide
Creator                         : Avid
Creator Tool                    : FrameMaker 11.0
Metadata Date                   : 2014:12:10 22:29:01-06:00
Producer                        : Acrobat Distiller 10.0.0 (Windows)
Document ID                     : uuid:3f72300c-3d3c-446b-b9e5-4beb9cb48168
Instance ID                     : uuid:9d4766f6-d4f8-40d9-bf45-242b99f527de
Writer 002F Editor              : BBL
Part 0020number                 : 9329-65311-00 Rev C
Page Mode                       : UseOutlines
Page Count                      : 308
EXIF Metadata provided by
EXIF.tools

Navigation menu