Pinnacle Systems iNews - 3.3 User Manual

Avid® iNEWS

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

The following disclaimer is required by Apple Computer, Inc.:

APPLE COMPUTER, INC. MAKES NO WARRANTIES WHATSOEVER, EITHER EXPRESS OR IMPLIED, REGARDING THIS PRODUCT, INCLUDING WARRANTIES WITH RESPECT TO ITS MERCHANTABILITY OR ITS FITNESS FOR ANY PARTICULAR PURPOSE. THE EXCLUSION OF IMPLIED WARRANTIES IS NOT PERMITTED BY SOME STATES. THE ABOVE EXCLUSION MAY NOT APPLY TO YOU. THIS WARRANTY PROVIDES YOU WITH SPECIFIC LEGAL RIGHTS. THERE MAY BE OTHER RIGHTS THAT YOU MAY HAVE WHICH VARY FROM STATE TO STATE.

The following disclaimer is required by Sam Leffler and Silicon Graphics, Inc. for the use of their TIFF library:

Permission to use, copy, modify, distribute, and sell this software [i.e., the TIFF library] and its documentation for any purpose is hereby granted without fee, provided that (i) the above copyright notices and this permission notice appear in all copies of the software and related documentation, and (ii) the names of Sam Leffler and Silicon Graphics may not be used in any advertising or publicity relating to the software without the specific, prior written permission of Sam Leffler and Silicon Graphics.

THE SOFTWARE IS PROVIDED “AS-IS” AND WITHOUT WARRANTY OF ANY KIND, EXPRESS, IMPLIED OR OTHERWISE, INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

IN NO EVENT SHALL SAM LEFFLER OR SILICON GRAPHICS BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES OF ANY KIND, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER OR NOT ADVISED OF THE POSSIBILITY OF DAMAGE, AND ON ANY THEORY OF LIABILITY, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

The following disclaimer is required by the Independent JPEG Group:

This software is based in part on the work of the Independent JPEG Group.

This Software may contain components licensed under the following conditions:

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.

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.

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.

Permission to use, copy, modify, and distribute this software for any purpose without fee is hereby granted, provided that this entire notice is included in all copies of any software which is or includes a copy or modification of this software and in all copies of the supporting documentation for such software.

THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED WARRANTY. IN PARTICULAR, NEITHER THE AUTHOR NOR AT&T MAKES ANY REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE MERCHANTABILITY OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR PURPOSE.

This product includes software developed by the University of California, Berkeley and its contributors.

The following disclaimer is required by Nexidia Inc.:

Manufactured under license from the Georgia Tech Research Corporation, U.S.A. Patent Pending.

The following disclaimer is required by Paradigm Matrix:

Portions of this software licensed from Paradigm Matrix.

The following disclaimer is required by Ray Sauers Associates, Inc.:

“Install-It” is licensed from Ray Sauers Associates, Inc. End-User is prohibited from taking any action to derive a source code equivalent of “Install-It,” including by reverse assembly or reverse compilation, Ray Sauers Associates, Inc. shall in no event be liable for any damages resulting from reseller’s failure to perform reseller’s obligation; or any damages arising from use or operation of reseller’s products or the software; or any other damages, including but not limited to, incidental, direct, indirect, special or consequential Damages including lost profits, or damages resulting from loss of use or inability to use reseller’s products or the software for any reason including copyright or patent infringement, or lost data, even if Ray Sauers Associates has been advised, knew or should have known of the possibility of such damages.

The following disclaimer is required by Videomedia, Inc.:

“Videomedia, Inc. makes no warranties whatsoever, either express or implied, regarding this product, including warranties with respect to its merchantability or its fitness for any particular purpose.”

“This software contains V-LAN ver. 3.0 Command Protocols which communicate with V-LAN ver. 3.0 products developed by Videomedia, Inc. and V-LAN ver. 3.0 compatible products developed by third parties under license from Videomedia, Inc. Use of this software will allow “frame accurate” editing control of applicable videotape recorder decks, videodisc recorders/players and the like.”

The following disclaimer is required by Altura Software, Inc. for the use of its Mac2Win software and Sample Source Code:

The following disclaimer is required by Ultimatte Corporation:

Certain real-time compositing capabilities are provided under a license of such technology from Ultimatte Corporation and are subject to copyright protection.

The following disclaimer is required by 3Prong.com Inc.:

Certain waveform and vector monitoring capabilities are provided under a license from 3Prong.com Inc.

The following disclaimer is required by Interplay Entertainment Corp.:

The “Interplay” name is used with the permission of Interplay Entertainment Corp., which bears no responsibility for Avid products.

This product includes portions of the Alloy Look & Feel software from Incors GmbH.

This product includes software developed by the Apache Software Foundation (http://www.apache.org/).

This product may include the JCifs library, for which the following notice applies:

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,

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 v3.3 Setup and Configuration Guide • 0130-30597-01 • Created 11/23/10 • This document is distributed by Avid in online (electronic) form only, and is not available for purchase in printed form.

Using This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Symbols and Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

If You Need Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

...With the Syntax of Console Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Avid Training Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Overview of iNEWS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

System Administrator Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Chapter 2 The iNEWS Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Overview of Hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Starting the Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Console Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Logging in as a System Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Entering Superuser Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Changing System Administration Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Exiting the Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Troubleshooting a Frozen Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Types of Console Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Using Server Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Using Console Control Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Assigning Commands to Function Keys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Displaying Function Key Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Selecting One or More Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Zooming in on One Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Using Console History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Logged Console History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Using the Remote Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Executing Remote Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Logging out a Remote Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

The Console Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Viewing the Console Configuration File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Editing the Console Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Chapter 3 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Starting the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Shutting Down the System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Starting a System in Single-Server Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Chapter 4 Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Viewing User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Modifying User Traits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

User Traits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Changing a User’s Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Changing User Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

User Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Setting up Simplified Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Simplified User Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Creating New Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Creating a New User Area in News Database . . . . . . . . . . . . . . . . . . . . . . . . . 86

Adding a New User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Enabing a New User to Receive Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Searching for User Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Removing User Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

The User Manager Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

The Database Manager Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Logging Out All Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Chapter 5 The Database: Directories, Queues, and Stories . . . . . . . . . . . . . . . . . . 99

Overview of the iNEWS Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Restrictions to Directory or Queue Creation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Creating a New Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Creating a New Queue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Outgoing Mail Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Dead Letter Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Search Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Viewing Search Queue Information from the Console . . . . . . . . . . . . . . . 111

Creating a New Story . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Using Script Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Renaming a Directory or Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Deleting a Directory or Queue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Recovering a Killed Story . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Viewing Database Traits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Viewing Information about Stories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Viewing Who Moved, Duplicated, or Killed a Story . . . . . . . . . . . . . . . . . . 119

Database Traits Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Changing Database Traits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Turning Off the Ordered Trait of a Sorted Queue. . . . . . . . . . . . . . . . . . . . . . . 138

Database Purge Intervals and Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Identifying Locked Queues and Stories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Types of Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Removing Locks from a Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Unbusy Stories and Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Chapter 6 Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Overview of Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Viewing Group Information from the Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Viewing Group Information from a Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Creating a New Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Step 1 - Choosing a Group Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Step 2 - Create New Group at Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Step 3 - Creating Group’s Membership Story and Specifying Members . . . . . 155

Group Checker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Group Checker Error Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Renaming a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Step 1 - Change Group Name in Database . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Step 2 - Change Group Name in SYSTEM.GROUPS . . . . . . . . . . . . . . . . . . . 160

Deleting a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Creating or Modifying Multiple Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Adding Users as Members of a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Adding Groups as Members of Other Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Avoiding Recursion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Adding Workstations as Members of a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Combined Permissions and Timeouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Group Access and Usage Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Group Traits for the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Read Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Write Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Notification Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Editorial Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Restricted Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Restricting Both Reading and Writing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Transferring Group Assignments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Hiding Queues and Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Creating a Mail Alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Mail Aliases for Other Machines or the Internet . . . . . . . . . . . . . . . . . . . . . . . 176

Chapter 7 Keyboards and Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Types of Macros. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Creating a Keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Creating Macros. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Using the State Keys in Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Repeating Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

Notes of Caution for Creating Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Keyboard Checker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Testing the Keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

Assigning a Default Keyboard to a User Account . . . . . . . . . . . . . . . . . . . . . . . . . 193

Chapter 8 Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Form Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

Creating Forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

Customizing Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

Turning on Label Borders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

SYSTEM.COLORS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

SYSTEM.LISTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

Assigning a Form as a Queue or Story Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

Form Field Types and Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

Standard iNEWS Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

Chapter 9 Character Generator Title Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

Overview of CG Title Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

Title Entry Setup and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

CG Template Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Edit Title Entry Template Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

Creating a New Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

Using Font PreSets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

Title Entry Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

Access to CG Template Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

Access to CG Title Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

Chapter 10 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

Making a Backup File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

Viewing System Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

Licensing iNEWS Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Editing the Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

Testing the Site Configuration File After Alteration . . . . . . . . . . . . . . . . . . . . . 253

Incorporating Configuration Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

Hosts File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254

System Profile Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254

Changing the System Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

Listing Parameter Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

System Profile Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

Viewing Information about Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

List C Message Columns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

Adding Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

Intersystem Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

Sending Intersystem Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

Receiving Intersystem Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

Chapter 11 Printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

Local Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

Local Printing Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

Creating and Using Print Styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

Local Print Style Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

Banner Format Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

Example Style Story . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288

Chapter 12 Wires . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

Adding a Wire – Avid Data Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292

Phase 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292

Phase 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

Adding a Wire Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

Phase 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295

Phase 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296

Wire Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296

Wire Distribution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297

The Wire Distribution Story . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297

Avoiding Hidden Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302

Mailboxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303

Purge Intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303

Internationalization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303

Setting Up Wire Keyword Searches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303

Additional Information about Search Jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . 306

Keyword Search Rule Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307

Keyword Checker Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311

Chapter 13 Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316

Adding a Server Program to the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316

Job Lists: Queues, Stories, and Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320

Types of Tasks for Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320

Adding a Scan Line in a Job List Story. . . . . . . . . . . . . . . . . . . . . . . . . . . 321

Defining a Priority Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322

Defining an Every Entry Queue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322

A Server’s Command Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323

Processing Deleted Stories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324

Ordered Queues and the Order Command . . . . . . . . . . . . . . . . . . . . . . . . 325

Mailbox Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325

Types of Mailboxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326

Assigning a Mailbox to a Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328

Timed-Interval Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

Example of Timed Interval Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330

Action Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332

Adding an Action Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333

Field Validation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335

Possible Uses of Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335

Using Field Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336

Validation Job List Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338

Rundown Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339

Polling Commands for Action Servers/Tx Links . . . . . . . . . . . . . . . . . . . . 340

Configuring Rundown Mirroring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340

Overlapping Job Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342

Polling Issues Related to Tx Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343

Distribution Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344

Distribution Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345

Wildcards and the Destination Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345

Move and Dup Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346

Action Servers or Tx Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346

Instructions in the Wire Distribution Story . . . . . . . . . . . . . . . . . . . . . . . . . 347

Matching and Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348

Matching and Order. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348

Adding a Distribution Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350

Parallel Wire Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353

Adding a Parallel Wire Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354

Keyword Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360

Adding a Keyword Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361

System Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

Seek Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

Adding a Seek Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

Fast Text Search Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369

Installing FTS Components on the Windows-based Server . . . . . . . . . . . 372

Setting up FTS Components on the iNEWS Servers (Linux) . . . . . . . . . . 374

Batch Indexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377

Reindexing (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379

Mail Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380

Monitor Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381

Checklist: Monitor Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383

Creating a Monitor Server for Each Show . . . . . . . . . . . . . . . . . . . . . . . . 384

Creating Composite and Event List Queues . . . . . . . . . . . . . . . . . . . . . . 387

Set up Queue and Story Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390

Assigning Forms to Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390

Creating an Entry in the SYSTEM.MAP Story . . . . . . . . . . . . . . . . . . . . . 391

Updating the iNEWS System Dictionaries . . . . . . . . . . . . . . . . . . . . . . . . 397

Creating Styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400

Using the Monitor Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405

Network iNEWS Systems Using RX/TX Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407

Sending Story Forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407

Setting Automatic Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407

Update Trait - Queue Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409

Changing Queue Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410

Adding Rx/Tx Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410

Chapter 14 iNEWS Community . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419

Configuring iNEWS for Community . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420

Syntax of the ctraits Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422

Viewing Remote Systems or Community Sessions . . . . . . . . . . . . . . . . . . . . . . . . 423

Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423

Local and Remote SYSTEM.MOS-MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424

Removing a System from Community . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424

Connection Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425

Chapter 15 Web Publishing and Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429

Web Publishing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430

Setting up Txnet to Send HTML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430

The HTML Export Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432

Sample HTML Export Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441

Publishing iNEWS Stories to the Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446

Web Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446

The Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446

Logging in via Web Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447

Web Acess Story Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447

Web Access Directory and Queue Templates. . . . . . . . . . . . . . . . . . . . . . 450

Web Access Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461

Chapter 16 iNEWS Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465

Overview of Projects and Facets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466

Setting up the iNEWS Database for Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467

Creating Projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468

Creating Facets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471

Associating Stories with Projects or Facets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473

Appendix A Command References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475

Programs Invoked by iNEWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476

Commands Used by Avid Personnel Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476

Linux Commands Used in iNEWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477

Console Control Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478

Console Server Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482

broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482

configure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482

connect. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483

ctraits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483

dbclean. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484

dbclose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484

dbdev . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485

dbdump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485

dbfree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486

dblines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487

dboriginal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488

dbpurge

(Superuser conditional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488

dbrestore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489

dbserver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491

dbsort . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491

dbtraits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492

dbvisit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493

dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495

diskclear

(Superuser only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495

diskcopy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496

doc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496

ed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496

enter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497

force

(Superuser only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497

grpcheck . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497

gtraits

(Superuser only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498

help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498

hogs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499

idiff. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499

list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500

list B. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502

list C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503

list c . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504

list d . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504

list g . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505

list p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506

list q . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508

list s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508

list sq . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509

list u

. . . . . . . . . . . . . . . . . . . . . . . . . . . 509

logout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511

makemontab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511

makeshift (Super user only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511

maketab

(Superuser only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512

msgclean . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513

offline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517

online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517

otod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517

reconnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518

remove . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519

rename

(Superuser only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519

reorder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520

restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520

searchtape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520

send . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521

shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521

sitedump

(Superuser only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521

siterestore

(Superuser only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522

startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523

status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523

stop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523

su . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524

unbusy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524

utraits

(Super user only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524

version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525

wholockedit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526

Job List Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527

at . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527

bpoll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527

bscan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527

distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527

dup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528

every . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528

extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528

fast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528

ignore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528

ignore-del . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529

local . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529

mailto. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529

move . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529

number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529

on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530

open . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530

order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530

poll. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531

publish . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531

put . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531

quiet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531

remote . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531

remove . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532

replace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532

scan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532

send-del. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532

sendform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533

source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533

validate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533

Dialog Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533

capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534

delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534

diag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534

echo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535

escape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535

expect. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535

heol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536

map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536

mapin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537

mapout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537

message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537

pass . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537

pause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538

stop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538

timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538

type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539

wait . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539

Appendix B System Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541

/etc/hosts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542

/site/config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543

/site/system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555

console.cfg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556

SYSTEM.CLIENT.WINDOWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558

SYSTEM.CONFIGURE.301-ACTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559

SYSTEM.MAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560

SYSTEM.RESOURCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562

SYSTEM.WIRES.DISTRIBUTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565

SYSTEM.WIRES.KEYWORDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566

SYSTEM.WIRES.KEYWORDS-AP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567

SYSTEM.WIRES.KEYWORDS-AP2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568

Appendix C Standard Dictionaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569

Using Dictionaries to Define Messages and Commands . . . . . . . . . . . . . . . . . . . . 570

Customizing Dictionaries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572

Changing Default Dictionary Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572

Restoring Dictionary Defaults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574

Utility Messages Dictionary (/site/dict/messages) . . . . . . . . . . . . . . . . . . . . . . . . . . 575

DBServer Program Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576

Disconnect Program Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576

Category and Keyword Check Program Messages. . . . . . . . . . . . . . . . . . . . . 576

Keyboard Check Program Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577

Keyboard Check Program Messages for Macros . . . . . . . . . . . . . . . . . . . . . . 578

Grpcheck Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579

Wire Program Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581

Mail Server Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581

Validation (Action) Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581

Seek Server Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582

Last Login Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583

Print Server Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583

dbtraits Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583

Save Error (Workstation) Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583

Queues Dictionary (/site/dict/queues) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583

Words Dictionary (/site/dict/words). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586

Keyboard Macros Dictionary (/site/dict/keymacros) . . . . . . . . . . . . . . . . . . . . . . . . 589

Case-shifting Dictionary (/site/dict/shift) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591

MCS Dictionary (/site/dict/mcs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593

Device Types Used by Monitor Servers and Drivers. . . . . . . . . . . . . . . . . . . . 593

Special Strings Recognized by the Monitor Server . . . . . . . . . . . . . . . . . . . . . 594

Error Messages for the Monitor Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594

Status Reported in Device Status Field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596

Job List Command Dictionary (/site/dict/joblist) . . . . . . . . . . . . . . . . . . . . . . . . . . . 597

D Messages Dictionary (/site/dict/dmessages) . . . . . . . . . . . . . . . . . . . . . . . . . . . 598

S Messages Dictionary (/site/dict/smessages). . . . . . . . . . . . . . . . . . . . . . . . . . . . 599

Appendix D Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603

Registry Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604

Environment Variables (Registry Values). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605

CCColor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605

DestinationOrder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607

MailLookup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608

MsgMailAlert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609

PIColor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610

RGB Hexadecimal Color Chart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611

ShowTimingBar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612

SyncToServer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616

VT Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617

DisableCommandLine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619

Environmental Variables for Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620

Appendix E Managing Traits at the Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623

Viewing User Traits from the Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624

Modifying User Traits from the Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625

Changing a User’s Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626

Listing Users Who Do Not Have Passwords . . . . . . . . . . . . . . . . . . . . . . . 628

User Traits Console Command Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632

Managing Database Traits from the Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635

Getting Basic Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635

Getting Detailed Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636

Changing Database Traits from the Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637

Changing a Parent Directory Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637

Database Traits Console Command Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . 637

Sortfield . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645

Changing a Queue’s Sort Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645

Starting the Queue Sort Function from the Console . . . . . . . . . . . . . . . . . 646

Purge Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646

Mailbox Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647

The dis Column . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648

FTSindex Attribute. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649

Interplay Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650

Managing Group Traits at the Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650

Read Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651

Write Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651

Editorial Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651

Notify Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652

Restricting Access Using Read and Write Limitations . . . . . . . . . . . . . . . . . . . 652

Removing Directory or Queue Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . 653

Appendix F The Line Editor, ed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655

Starting ed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656

Specifying Lines to Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656

Searching the File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658

Searching Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659

Editing Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659

Saving Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662

Quitting ed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665

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 Administration Guide—is a comprehensive resource of all administrative information you will need to take advantage of the many options available to you.

This guide will lead you through even the most complex procedures with task-oriented instructions. The information provided here builds on basic news production procedures described in the help system and other user-based guides, while adding a complete explanation of all of the tools and techniques required to manage the newsroom computer system, including useful tips, shortcuts, and custom options.

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

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

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

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.

Symbol or Convention Meaning or Action

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

Bold font Bold font is primarily used in task instructions to identify user interface

Italic font Italic font is used to emphasize certain words and to indicate variables.

Courier Bold font

Ctrl+key or mouse action Press and hold the first key while you press the last key or perform the

If You Need Help

If you are having trouble using your Avid product:

1. Retry the action, carefully following the instructions given for that task in this guide. It is especially important to check each step of your workflow.

2. Check the latest information that might have become available after the documentation was published:

- If the latest information for your Avid product is provided as printed release notes,

they ship with your application and are also available online.

This text indicates that the information applies only to the specified operating system, either Windows or Macintosh OS X.

items and keyboard sequences.

Courier Bold font identifies text that you type.

mouse action. For example, Command+Option+C or Ctrl+drag.

- 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 Console Commands

If you are at the console and are unsure about the function of a console command, use the help command.

To view instructions about using a command:

If You Need Help

t Use the following command:

For instance, type:

The following data appears:

dbvisit -<d or v or i> -[r or m name] -[s] [block# ...]

‘r’ for read only

‘s’ for “slow” to eliminate cache usage

‘m’ for machine name to disconnect

‘i’ to just validate isam files

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, console command lines might appear wrapped to multiple lines. This does not necessarily indicate the need to press an Enter key. Unless otherwise indicated, console commands should be typed on a single line, allowing the computer to wrap the text whenever the command line stretches beyond the screen margin.

help dbvisit

help

for an explanation of the dbvisit command.

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

™

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 iNEWS console multiplexor 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

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:

System Administrator Tasks

• 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 oganization needs to function. A system administrator’s tasks associated with the database include:

• Design forms (that is, story templates) to display important information about stories in a queue.

• Monitor changes to files and queues in the database.

• Unlock or delete any item in the database, and recover items that were accidentally deleted or corrupted.

1 Introduction

• Create new folders or queues in the iNEWS system database to meet your organization’s

• 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

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

• 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

Customizing the System

expanding needs—including setting up rundowns.

out of queues.

checks and modifications.

need for information.

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.

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.

1 Introduction

2 The iNEWS Console

The iNEWS console multiplexor serves as a “command center” that enables system administrators to monitor and maintain the iNEWS newsroom computer system.

This chapter contains the following main sections:

• Overview of Hardware

• Starting the Console

• Logging in as a System Operator

• Entering Superuser Mode

• Changing System Administration Passwords

• Exiting the Console

• Troubleshooting a Frozen Console

• Types of Console Commands

• Selecting One or More Servers

• Zooming in on One Server

• Using Console History

• Using the Remote Console

• The Console Configuration File

Overview of Hardware

The iNEWS console multiplexor serves as a “command center” that enables system administrators to monitor and maintain the iNEWS newsroom computer system. The iNEWS console multiplexor—commonly known as the console—is a DOS- or Windows-based computer running custom-created Avid software. The console PC connects—via a serial link—to two or more iNEWS Servers and communicates with each server simultaneously.

The following diagram shows a sample layout for a dual-server newsroom computer system.

With an external analog modem line, the console also provides a secure remote console feature, which enables a system administrator or Avid Customer Support personnel, if necessary, to do routine maintenance and diagnostic work while away from the computer

Starting the Console

room. On newer Windows-based consoles, other remote access software can let administrators access the console securely from inside the network without needing to be at the console. However, Avid Customer Support requires a modem for remote access.

Console Keyboard

While the console multiplexor uses a standard computer keyboard, the Enter key on the numeric keypad is the console’s Command key, the Escape key is—by default—used as the Escape character for remote command execution, and the system administrator can preprogram the keyboard’s function keys to execute console commands. The following diagram identifies the locations of important keys on the typical console keyboard.

The Enter key on the numeric keypad will be called the Command key throughout this guide

to prevent confusion with the Enter key on the keyboard.

Starting the Console

If your console has been turned completely off, it should start the console program automatically when it boots up. If not, it can be started manually.

To start the console program:

1. Do one of the following:

t From the operating system prompt, type:

t Double-click

2. Press Enter.

The console display will appear with multiple regions, each region associated with a server and showing the following prompt:

console.exe

console

2 The iNEWS Console

Console Display

Although the console can control multiple servers, your console has one screen, which is often divided into regions to separate the output from each server. The user can alter the display to show multiple regions or a single region.

The following graphic shows a console display for a dual-server system; the console screen is divided into two regions.

Your console screen has as many regions as there are host servers in your system.In the example, the top region displays the output from server A, and the bottom region displays the output from server B. The wavy lines (^^^) to the left of the identifier for server B indicate that it is currently selected or active. Each region will have its own server and command prompts, after which you can enter various commands. See “Types of Console

Commands” on page 41 for more information.

To identify which region belongs to which server, the console displays the name of the server that a region represents in that region’s lower right corner.

Each server’s name is based on the system ID (typically a station’s call letters) and the

server’s name (usually a single letter, such as A, B, or C). Examples in this guide use NRCS as the fictional station and system ID.

Should data shown in a region extend beyond the size of the screen, the user can temporarily pause the display output. See “Using Console History” on page 46 for more information.

Logging in as a System Operator

System administrators must log in to iNEWS at the console differently than other users who log in at an iNEWS Workstation. For security reasons, system administrators should log out of the system when not using it.

To log in as the system operator:

1. Select the server(s) displaying the login prompt. See “Selecting One or More Servers”

on page 45 for more information.

2. Type:

3. Press Enter.

4. If your system has a password for this account—and most do—then type in the password when prompted. To keep the password confidential, the console does not display what you type.

The system operator password is set during installation of the iNEWS Server software on the

iNEWS Servers. For information about changing the system operator password, see

“Changing System Administration Passwords” on page 38.

5. Press Enter.

Logging in as a System Operator

The console’s server prompt will look similar to this:

NRCS-A$

Entering Superuser Mode

An administrator can take special system privileges as a console superuser when he or she needs to use more powerful—and therefore potentially more dangerous—commands. Once the administrator is done with these more powerful commands, he or she can give up the privileges without logging out. Giving up the privileges (by exiting superuser mode) helps prevent mistakes and provides better security.

The console’s server prompt is the visual indicator for whether you are logged in as a system operator or have enter superuser mode. The server prompt for a system operator login ends with a dollar sign ($). The server prompt while in superuser mode ends in a pound sign (#).

The system operator prompt looks like this:

NRCS-A$

2 The iNEWS Console

The superuser prompt looks like this:

NRCS-A#

If a command example in this guide shows the superuser prompt—ending in a pound sign

(#)—you must be in superuser mode to use the command.

A password is required for taking superuser privileges. This password is the same as the root user password, which is set during installation of the Linux operating system on the iNEWS Servers. See “Changing System Administration Passwords” on page 38 for more information.

To take superuser privileges:

1. If you are not already logged in, then log in as a system operator, by typing: so.

2. Enter superuser mode by typing:

3. Press Enter.

4. Type the superuser password at the password prompt. To keep the password confidential, the console does not display what you type.

5. Press Enter.

After you entered the password correctly, the console shows that you have superuser privileges by changing the dollar sign ($) at the end of the server prompt to a pound sign (#). If you enter an incorrect password, the console displays an error message and returns you to a system operator prompt.

To prevent users from typing unauthorized commands, never leave the console unattended when logged in with superuser privileges. You should enter superuser mode only when you need to type a superuser command, and give up the privileges immediately after typing the command.

To give up superuser privileges and return to the system operator prompt:

t Press Ctrl+D.

The console shows that you are a system operator by changing the pound sign (#) at the end of the console’s server prompt to a dollar sign ($).

Changing System Administration Passwords

When logging in to the console as either a system operator or superuser, a password is needed. These system administration passwords are typically set by Avid Customer Support technicians during the installation of either the iNEWS Server software or the Linux operating system (OS). However, they can be changed later by system administrators at the console.

Changing System Administration Passwords

Changing the superuser password also changes the Linux root user password, which is set

during the Linux OS installation, must be more than six characters, initially.

Keep a confidential record of password changes. Knowing the passwords is critical. If you forget your passwords, the operating system might need to be reinstalled from scratch by Avid Customer Support technicians.

For more information on changing the password for the remote console, see “Editing the

Console Configuration File” on page 55.

To change the system operator password:

1. Log in as a system operator, using the current password.

2. At the server prompt, type the password command, as shown:

3. Press Enter.

4. Type the current password, and press Enter.

5. When prompted, type a new password, and press Enter.

If the system operator password is fewer than six characters or is based on a word in the

dictionary, the system will issue a “BAD PASSWORD...” message, but it will accept such passwords. The system will not accept a blank password.

6. When prompted to confirm, retype the new password, and press Enter.

To change the console superuser password:

1. Enter superuser mode, using the current password.

2. At the superuser prompt, type the password command, as shown:

3. Press Enter.

4. Type the current password, and press Enter.

5. When prompted, type a new password, and press Enter.

6. When prompted to confirm, retype the new password, and press Enter.

If the password does not match, the system displays an error message. Start over by retyping

the new password. Also, if the superuser password is fewer than six characters or is based on a word in the dictionary, the system will issue a “BAD PASSWORD...” message, but it will accept such passwords. The system will not accept a blank password.

NRCS-A$ passwd

NRCS-A# passwd

7. Press Ctrl+D to leave superuser mode.

The pound sign (#) at the end of the console’s server prompt will change to a dollar sign ($).

2 The iNEWS Console

Exiting the Console

You should leave the console on at all times while the iNEWS system is running. However, the following situations might require you to exit the console:

• You need to edit the console’s configuration file. See “The Console Configuration File”

on page 52 for more information.

• The console is frozen, and you are unable to unfreeze it using the methods described in

“Troubleshooting a Frozen Console” on page 40.

To exit the console:

1. Press the Command key.

2. Press Ctrl+E.

3. When

If running on a DOS system, after the console application closes, the prompt for your

operating system will appear.

COMMAND^EXIT

The console application closes.

appears, press Enter.

Troubleshooting a Frozen Console

If the servers on your system are not responding to commands and are not displaying messages, potential causes to look for include:

• Ensure that you or someone else has not stopped scrolling. If you suspect this problem, restart scrolling.

• Ensure that the server ports have not stopped sending and receiving. If you suspect this problem, restart the sending and receiving from server ports.

• Verify whether static electricity froze one or more of the servers’ I/O ports. If you suspect this problem, reset the servers’ I/O ports.

• Check for an application program that will not stop running. If you suspect this problem, stop the program and log in again to the console.

Here are several possible procedures you can do to identify and resolve the problem.

To check and restart scrolling:

1. If that is the case, XOFF is displayed under the region where scrolling has stopped.

2. Press Ctrl+Q to start scrolling.

Types of Console Commands

To restart sending and receiving from server ports:

1. Press the Command key.

2. Type:

3. Press Enter.

In the previous two procedures, the XON command is shown being issued in two ways: first,

by pressing Ctrl+Q and second, by pressing the Command key and typing accomplish the exact same thing.

To reset the servers’ I/O ports:

1. Select the affected server(s).

2. Press the Command key.

3. Type:

4. Press Enter.

To stop a runaway program:

1. Select the affected server(s).

2. Hold down the Control key and press the backslash key (Ctrl+\).

(for reset).

. Either way will

This stops the program on the selected server(s).

If this does not stop the program so that the console displays a system prompt, suspend the program by pressing Ctrl+Z—or whatever the suspend (susp) character is. The default is Ctrl+Z.

You can use the jobs command to list suspended programs and kill suspended programs by using the kill command along with a percent sign (%) and the job number, such as:

If the console still does not respond, exit the console program and restart it as described in

“Exiting the Console” on page 40 and “Starting the Console” on page 35.

Types of Console Commands

You can type two kinds of commands at the console:

• Server commands are sent to the iNEWS Servers.

• Console control commands are sent to the iNEWS console software that communicates with the servers.

kill %1

2 The iNEWS Console

A detailed list of commands is provided as an appendix to this guide. See “Console Control

Commands” on page 478 and “Console Server Commands” on page 482 for more

information. Also, see “If You Need Help” on page 24 for more information on syntax of console commands.

System administrators can preprogram the function keys on the keyboard to execute commands, too. For more information about assigning commands to function keys, see

“Assigning Commands to Function Keys” on page 44.

Using Server Commands

The iNEWS system will not recognize server commands entered in upper case. Type server commands at the console in lower case after the prompt for the server to which you want the command sent. For instance, if you want to send a command to server A, type the command after the server prompt associated with server A.

The console displays each server’s prompt based on the system ID and the server’s name,

separated by a hyphen. Examples in this guide use NRCS as the system ID and single letters—such as A, B, or C—as the server name.

For instance, the server prompt might appear like this:

The appearance of the server prompt varies, depending on how the system administrator is logged in to the console. See “Logging in as a System Operator” on page 37 and “Entering

Superuser Mode” on page 37 for more information.

An example of a server command is the command—which when sent to an iNEWS Server will return information about who is logged in.

To simultaneously send a server command to multiple servers:

t Type the server command followed by a pound sign (#).

The # character acts as a place holder for each server name. It is replaced with each server’s computer name, such as A or B, before the console sends the server command to all servers in the system. This allows system administrators to send commands to multiple servers without having to select each server and send commands individually.

For instance, when you type

connect b

To stop a server command:

t Press Delete.

to server B, and so forth.

connect #

list sessions

the command

NRCS-A$

command—or

connect a

list s

is sent to server A,

Types of Console Commands

If that does not work, press Ctrl+C—the stty interrupt character. Doing so will interrupt the command’s execution. As a last resort, pressing the Control and Backslash keys (Ctrl+\—the stty quit character) will stop the command’s execution. Avid recommends you should attempt to “interrupt” before trying to “quit” the execution.

If the server sends a message while you are typing a command, the console stops displaying your keystrokes to display the message. However, it continues to record what you type. After it has displayed the message, then the console will display the data you typed in its entirety.

If you are interrupted by a console display or have mistyped a command, you can cancel the entire command line and start over by pressing Ctrl+U.

The character used to issue the command that cancels an entire command line—known as

the “kill” character—may be customized, using the stty command. For instance, to set it to the “at” character, you would type:

stty kill @

To reset it to the default Ctrl+U, type:

The same customization capability applies to the “intr” or “interrupt” character, which is used to interrupt a running program. For instance, type: Delete key, To reset it to the default Ctrl+C, type:

To cl ari fy, the key, to get the ^ character, and then the U or C letter key respectively. The same applies to

. You can view these settings by entering the server command:

the

and ^C —shown above— mean to hold the Shift key down and press the 6

Using Console Control Commands

The Enter key on the numeric keypad is the console’s Command key. When you press it, the console displays the command prompt—also called the command line—from which you can type in commands.

The command prompt appears as shown:

COMMAND^

To enter console control commands:

1. Press the Command key.

2. Type the console control command.

Some of the most common console control commands are those used to activate a region of the console display—by selecting an iNEWS Server(s)—and those commands used to view a record of messages displayed on the console, known as the console history.

stty kill ^U

stty intr ^C

stty intr ^?

to set it to the

stty -a

2 The iNEWS Console

These commands are explained in “Selecting One or More Servers” on page 45 and

“Using Console History” on page 46. For a complete list of console control commands,

see “Console Control Commands” on page 478.

3. Press Enter.

If you make a mistake when typing a command, use the Backspace key to move the cursor

back and then type over the error.

Assigning Commands to Function Keys

The system administrator can preprogram the keyboard function keys to execute commands. For instance, you can program F1 to select server A, F2 to select server B, and F7 to move up 200 lines in the console history buffer.

To assign a command to a function key:

1. Press the Command key.

2. Type the name of the function key you want to use, followed by the equal sign (=) and the command the key is supposed to execute.

The following example assigns the command of choosing server A to the F1 key:

f1=c a

3. Press Enter.

To assign a command sequence to a function key—that is, include the Command and Enter keys in the definition—use the open brace ({) to represent Command, and the close brace (}) to represent Enter.

For example, to program the complete command sequence (press Command key, type computer command to select all servers, and press Enter) to function key F10, you would type:

To change a command assigned to a function key:

t Assign a new command to the key.

To delete a function key’s command assignment:

t Assign a null value to the key.

Displaying Function Key Assignments

To avoid inadvertently overwriting a function key’s command assignment, you can check whether a command has been assigned to a specific function key.

f10={c *}

To find out the command (if any) assigned to a key:

1. Press the Command key.

2. Type the name of the key, such as F9.

3. Press Enter.

Press Command again to clear the command assignment from the console screen.

Selecting One or More Servers

On the console, you can select one server or multiple servers at the same time. For instance, some commands must be executed on all servers simultaneously, so on a two-server system, you must select both server A and B before typing in the command.

To select only server A:

1. Press the Command key.

2. Do one of the following:

Selecting One or More Servers

t Type:

computer a

c a

3. Press Enter.

To select both the A and B servers:

1. Press the Command key.

2. Do one of the following:

t Type:

computer ab

c ab

3. Press Enter.

To select all servers:

1. Press the Command key.

2. Type:

c *

3. Press Enter.

Selecting all servers enables you to send a command to all of them simultaneously. When you select all servers, each server region’s bottom line changes to a wavy line of caret symbols (^^^). Only one cursor appears, usually in the top region; however, the console commands you type appear simultaneously in each region of the console screen.

2 The iNEWS Console

Zooming in on One Server

In addition to the computer command, you can also use the zoom command to select a server. Unlike the computer command, which operates in multiple region mode, zoom selects one server at a time and devotes the entire console screen to that server (or region).

To zoom in on one server, such as server B:

1. Press the Command key.

2. Do one of the following:

t Type :

3. Press Enter.

The following graphic shows the console screen after “zooming in” on server B’s region.

To restore the screen to its former multiple region state, use the select any server. It does not matter which one you select; the console screen will revert to a multiple region display, and the region for the selected server will have the cursor.

zoom b

z b

computer

command to

Using Console History

When output from a server command consists of more lines than can fit in a region, lines will be scrolled off the screen. The console maintains a history buffer containing data—known as console history—that has appeared on the screen.

The system can also be configured to log console history for viewing at a later time.

Using Console History

You can go scroll through the console history to review prior activity on any of the iNEWS Servers.

The top of the buffer contains the oldest information; the bottom of the buffer contains the most current. To view this data in screen-sized chunks, you must pause the screen display.

To pause the screen display:

t Press Ctrl+S. The console screen temporarily stops scrolling.

Pressing Ctrl+S does not have any effect if you are using a remote console. A remote console

is connected by a modem dial-in from an external location. See “Using the Remote

Console” on page 50 for more information.

When the screen is full of text, XOFF appears at the bottom of the selected region, as shown:

To manually resume scrolling:

t Press Ctrl+Q.

2 The iNEWS Console

Even if you do not press Ctrl+Q, the console automatically resumes scrolling after a pause of 60 seconds.

To view recent history on a particular server:

1. Zoom in to the server whose history you want to review.

2. Press the Command key.

3. Do one of the following:

t Type th e

history.

t Type th e

command, which moves the console screen up one line in the history.

down

command, which moves the console screen down one line in the

top

command, which moves the console screen to the top of the history.

t Type th e

history.

If you follow the up or down commands with a number, the console screen will move up or down that number of lines in the history. For instance, the console history—10 lines. If you follow the up or down commands with a word, the console screen will search from the current position backward or forward for that word, and if found, moves to the line containing that word. The commands are not case sensitive.

The pound character (#) is a wild card that can be included in the word to be searched for

with the up and down commands. It is also used to search for numbers. For instance, is a numerical search, and is not the same as console history.

4. Press Enter.

The command is followed by a number, the screen will display that number of lines of history, starting from the current position. When the word, bottom of the history, or newest line of information.

The

printing lines of history to a printer is See “Console Control Commands” on page 478 for more information.

bottom

command may also be used to view lines of console history. When the

all

, the screen will display all lines from the current position scrolling to the

command does not send console history text to a printer. The command for

command, which moves the console screen to the bottom of the

up 10

, moves up—or back in

up 10

, which will move up 10 lines in the

command is followed by the

list

, followed by either a number or the word, all.

up 10#

Logged Console History

You can configure iNEWS to log console history to disk for later review. The logs are written to the hard drive on your console PC, traditionally in the a Windows-based computer at:

The logs are named as shown in the following table:

File for server A File for server B Contains the following information

log.a1 log.b1 Most recent console history

log.a2 log.b2 Old console history

log.a3 log.b3 Older console history

log.a4 log.b4 Oldest console history

The log.a1 file is the most recent console history; you can also view it as shown in prior examples using the up command.

As the log.a1 file fills up, old files are renamed and a new log.a1 file is created as follows:

C:\Console

C:\Program Files\Avid\Console

Using Console History

directory or on

• log.a1 is renamed log.a2

• log.a2 is renamed log.a3

• log.a3 is renamed log.a4

• A new log.a1 is created

The log files are ASCII text files that can be read with any word processing program. You must exit the console program if you want to edit the logs in any way.

You can use the view console control command to view the log files without editing or exiting

to DOS, but view only lets you start at the top of the file and scroll down. You cannot move back or search for words. See “Console Control Commands” on page 478 for more information.

Both the presence or absence of disk logging and the size of the log files can be configured

console.cfg

in the information.

file. See “The Console Configuration File” on page 52 for more

2 The iNEWS Console

Using the Remote Console

The console should have a modem attached to it. This enables someone in another location to call up the console and log in, thereby turning the remote computer into a remote console. The primary use for a remote console is to enable Avid Customer Support technicians or system administrators to perform diagnostics and maintenance work on the iNEWS system from a remote location.

This section explains the requirements for dialing in over a modem line, what you can expect to see on the remote screen, and how to execute commands remotely. It also provides procedures for logging out from a remote console and logging out a remote user from the main console.

To dial in to the console, you must have a computer that transmits and receives ASCII characters. You must also have set the following modem options:

• Eight data bits

•No Parity

• One stop bit

• 9600 baud rate

To connect as a remote console:

1. Dial in to the console.

To prevent unauthorized people from dialing in to the console, remote access is protected with a password. When you dial in, you see a If you do not see the prompt immediately, pressing Enter should display it.

2. Enter the password when prompted.

After you type the correct modem password, the console connects you to the first server listed in the console configuration file, usually server A.

The modem password is set in the console’s configuration file. See “Editing the Console

Configuration File” on page 55 for more information.

MDM

At the console, was selected from the remote console. Commands typed at the remote console are sent to that server and displayed on its console region. Likewise, output from that server are displayed both on the console and the remote console.

is displayed at the bottom of the region representing the server that

PASSWORD

prompt on the screen.

Executing Remote Commands

After logging in, you can type commands and review history almost as if you were seated at the console itself. All commands except zoom are available from the remote console. Just as at the console, these commands can be abbreviated using the first letter in each command.

There are also some differences when using a remote console:

• The remote console displays screen input and output for only one server at a time, even if you have more than one selected.

When you select two or more servers, the order in which you list the servers in the computer command determines which server’s display you see. For instance, if you type c ab to select servers A and B, you see output only from server A on the remote console, even though what you type is sent to both A and B.

• Use the Escape character instead of the Command key to display the console command prompt.

The Escape character, by default, is set to the Escape (Esc) key; however, the character may

be customized, using the

For instance, to set the Escape character to the keystroke combination of the Control and Y keys (Ctrl+Y), type:

escape

escape Ctrl+Y

command in the following format:

Using the Remote Console

escape <char>

The Ctrl in the above command means to hold down the Control key while pressing the Y letter key. It is important to remember that the remote console and there must be a space after the command.

To reset the Escape character to its default, type the Escape key. For instance, type:

escape Esc

Logging out a Remote Console

After connecting to the console from a remote location, you should remember to log out.

If you are at the main console and discover that you or someone else has been using the remote console but did not log out when done, you can log out the remote user from the main console.

To log out after you finish using the remote console:

1. Press the Escape character.

2. Type:

3. Press Enter.

4. When the remote console redisplays the

. The lowercased L in this step stands for logout.

escape

PASSWORD

command can only be used from a

command, space, then press the

prompt, hang up your modem.

2 The iNEWS Console

To log out a remote console user from the main console:

1. Press the Command key.

2. Type:

. The lowercased M in this step stands for modem.

3. Press Enter.

Always follow this procedure before disconnecting the modem on the main console.

The Console Configuration File

The console uses information from its own configuration file—a text file called console.cfg—to set a number of parameters, such as:

• Whether or not disk logging is enabled

• Information about each of the servers connected to the console

• Information about the remote console

This section contains a sample configuration file, defines the console configuration keywords and their parameters, and provides procedures for viewing and editing the file.

Sample Console Configuration File

Here is a sample console configuration file:

computer hostess 3f8 irq 4 label NRCS-A name A speed 9600 ; computer hostess 2f8 irq 3 label NRCS-B name B speed 9600 ; computer hostess 3e8 irq 4 label NRCS-C name C speed 9600 ;

The Console Configuration File

modem hostess 2e8 irq 3 password mux speed 9600 timeout 0:05

The configuration file consists of a list of keywords, such as name and label. Most keywords are followed by parameters, such as a and NEWS. The keyword modem identifies the start of the modem (remote console) section. The keyword computer identifies a server section. Each server and the modem must have its own section in the console configuration file.

Console Configuration Keywords

Here are the configuration keywords and their parameters if they have any.

Keyword & Parameters Description

computer Indicates the beginning of a server section. Must appear at the top

of each server section on the configuration file.

hostess <port-address> Indicates which port address (in hex) the console uses to

communicate with a particular device (that is, a server or the modem). This information, which is dictated by the hardware, was placed in the configuration file when your system was installed and should not be changed.

irq <interrupt-request-number> To get the attention of the console, each device (that is, the servers

and the modem) connected to the console must have an interrupt request number defined. Typically, these are shared: COM 1 and 3 use the same number, and COM 2 and 4 use the same number. The irq keyword tells the console which interrupt request to expect from each device.

This information, which is dictated by the hardware, was placed in the configuration file when your system was installed and should not be changed.

label <region-name> Defines a label that the console uses to identify each server’s

region of the console screen. The label can be up to 15 alphanumeric characters long, and is typically the system ID.

2 The iNEWS Console

Keyword & Parameters Description

log <drive:filename> [server(s)] [max size]

Enables disk logging. No matter what filename (for example, log) you designate here, the system always uses extensions like A1, A2, and B1, as indicated in “Logged Console History” on page

49. If you do not follow the filename with a list of the servers for

which you want history to be recorded, the console records history for all servers. If you omit a log size it defaults to 16,384 bytes.

This example creates a log file on the C drive in the same location as the console application (console.exe) for all servers, and its maximum size is 40,000 bytes:

log c:log * 40000

modem Indicates the beginning of a modem section of the configuration

file.

name <computer-name> Names the server described in that section of the configuration

file. Each server must have A, B, C, or D as its name.

password <password> The modem password that must be typed when someone logs in at

a remote console. The password can have up to eight alphanumeric characters and is case sensitive.

portaddress <port> Selects the DOS address (in hex) the console should use to

communicate with a particular device, such as a modem. This information which is dictated by the hardware, is placed in the configuration file during installation and should not be changed. Each device must have a port address defined in its section. The portaddress keyword is used instead of hostess when your system has four servers and a modem. In that case, the modem must use com1 as its port. The port parameter should always be defined as 3f8.

speed <baud-rate> Sets the baud rate for communication between the console and the

server. The console ports always communicate at 9600 baud, eight data bits, no parity, and one stop bit.

timeout <minutes:seconds> Allows you to set a time-out value for any modem connection.

The system automatically logs out a modem connection if there is no activity for a specified amount of time. For instance, a value of 6:00 would automatically log out a modem connection after six minutes of inactivity. This keyword, which should only be used in the modem section, provides added protection should a user forget to logout from a modem connection to the console.

With a value of 0:00—the default value—the feature is disabled, which means the system will not log out a modem connection regardless of inactivity length. The maximum value is 546 minutes and 7 seconds (546:07).

Viewing the Console Configuration File

You can view the console’s configuration file from the console itself or, on a Windows-based PC, open it in a text editing program, such as Wordpad, to view it.

To view the console.cfg at the console:

1. Zoom in on one server, such as server A.

2. Press the Command key.

3. Do one of the following:

The Console Configuration File

t Type:

4. Press Enter to display the first line in the console configuration file.

5. Continue to press Enter to scroll through the file.

view console.cfg

v console.cfg

Editing the Console Configuration File

Probably the only modification you will ever need to make to the console’s configuration file is to change the modem password, used when logging in from a remote console.

To edit the console.cfg file:

1. Open the file using Microsoft’s program, Wordpad.

2. Save the file after you complete your modifications.

If the console configuration file is stored on a DOS PC, you need to use a DOS editing tool,

such as

edit

to change it, or copy the file to a Windows-based PC to edit it.

2 The iNEWS Console

3 Getting Started

System Administrators are responsible for knowing how to start up and shut down the iNEWS system. This requires logging in at the console multiplexor, which is done differently than other iNEWS users and provides access to features that other logins do not. Information on using the console, including logging in, is covered in Chapter 2. This chapter provides specifics on starting up and shutting down the newsroom computer system.

This chapter contains the following main sections:

• Starting the System

• Shutting Down the System

• Starting a System in Single-Server Mode

Starting the System

The following procedure shows you how to reboot your servers and synchronize them. This is primarily for dual- or triple-server systems. For steps on starting a system in single-server mode, see “Starting a System in Single-Server Mode” on page 62.

Because the following procedure applies to an entire system that has been shut down, you

must perform all the steps on all servers, except where otherwise indicated.

To start your iNEWS system:

1. Power up or reboot servers to the login prompt.

The servers will display the following line ten times—one per second:

Press any key to continue.

If no key is pressed, the bootup will continue normally after ten seconds. If a key is pressed, the system displays a message similar to the following:

The default is the SERIAL CONSOLE option, for booting to the iNEWS console. Use the up or down arrow keys to select another option; however, the other options should not be used for any reason, unless instructed to do so by Avid Customer Support personnel. Press Enter to continue.

Starting the System

If the system was not shut down as described in “Shutting Down the System” on page

60, check the console history for messages indicating that all servers shut down at the

same time. Do not connect servers unless you are sure their databases are mirrored. If you cannot find messages indicating simultaneous shutdown, or are otherwise unsure whether the disks are mirrored, call Avid Customer Support for assistance before proceeding. If the servers are not mirrored, it will be necessary to bring the system up as a single-server system and go through the re-mirroring process. See “Starting a

System in Single-Server Mode” on page 62 for more information.

If the system was taken through a normal shut down according to instructions, the databases would still be mirrored and you can continue the normal startup procedure.

2. Select all servers.

3. Log in as a system operator by typing:

4. When prompted, type the password.

5. Type:

connect #

The # character acts as a place holder for each server name, allowing you to send a single command to multiple servers simultaneously. So, typing

connect a

When connected, each server displays status messages and the system prompt returns.

Messages similar to the following appears:

connect successful for NRCS-A, starting servers...

A is OFFLINE. ID is NRCS.

System is A. Master is A.

Disk status is OK. The database is OPEN.

to server A,

connect b

to server B, and so forth.

connect #

will send

Connecting servers provides each server with a unique name and causes each one to read and interpret the system profile. The servers can work together as a system after reading the system profile information.

6. (Optional) Check for edit and order locks if you are restarting the system after a power failure. During a power failure, the system might not have had time to remove edit and order locks from the database before shutting down.

When you restart the system, remove these locks.

Checking for edit and order locks might take time depending on the size of the database. In

an emergency, bypass this step to get the system running. Go back later and remove locks to provide system access. The system can detect invalid locks and will ignore them.

a. Select one server.

b. Type:

dbclean -x .

3 Getting Started

7. Select all servers.

The -x option tells dbclean to skip queues or directories marked with a skip flag, reducing the time it takes to run.

The period ( database, so that it does not miss any part of the database not marked with a skip flag.

) after the -x causes dbclean to start at the root directory of the

8. Type:

Resources used for iNEWS Workstation, Data Receiver, and rxnet sessions do not print any

messages until a workstation establishes a connection.

startup

Information similar to the following appears:

Checking free space...

Sep 10 15:42:51 NRCS msg: System is being configured

database size 10002352,free 9955000=100%,freelist 1991

Starting NRCS programs...

booting device 100

booting server 130

The startup command does the following:

- Causes the master computer (usually server A) to read the configuration file

- Brings each server online so users can log in

- Checks database free space (dbfree)

- Starts all devices and utility programs

The console displays device-ready messages (Hot-to-go as each device starts up, indicating that the device is online and available.

Shutting Down the System

If you need to turn off your servers or reboot the system, first shut down the system. Shutting down the system:

• Saves any open stories

• Removes any remaining edit and order locks

• Ensures that each server’s copy of the database is the same

Shutting Down the System

Because the system requires that you shut down all servers at the same time, most steps in

this procedure are performed on all servers simultaneously. Except where instructed to do otherwise, ensure that you have selected all servers before performing each step. See

“Selecting One or More Servers” on page 45 for more information.

To shut down your iNEWS system:

1. Broadcast a message to notify users that the system is being shut down. For instance,

broadcast -dl Please log out, system being shut down.

type:

2. Select all servers.

3. Log out all users.

4. Type:

If the servers do not all display the same configuration settings—such as “System is

AB”—then the databases on the servers are most likely not mirrored and must not be brought back up using normal startup procedures. Contact Avid before proceeding.

5. Type:

6. To continue, type: y and press Enter.

status

This will display the systems current configuration status; verify that the servers are still connected to each other and running in the normal AB configuration for dual-server systems or ABC configuration for triple-server systems. If they are, you may continue with normal shutdown procedures.

shutdown

A message similar to the following appears:

WARNING! This will stop all devices on this computer, and close the database.

To prevent loss of work in progress, 'logout all' first.

Do you really want to do this (y/n)?

The screen appears similar to the following:

Do you really want to do this (y/n)? y

/exc/shutdown: Stopping all devices

/exc/shutdown: Closing database

The shutdown process stops all workstations, wires, and other devices, and no further changes can be made to the database.

7. Log in as a superuser, by typing:

3 Getting Started

8. When prompted, enter the password.

NRCS-A$ su

password:

NRCS-A#

9. When the superuser prompt appears, shut down the system by using a form of the init command, as shown:

NRCS-A# halt

Broadcast message from root (ttySO) (Fri ...)

The system is going down for system halt NOW!

INIT: Stopping atd: [ OK ]

Stopping keytable: [ OK ]

...

Turning off swap:

Turning off quotas:

Unmounting file systems:

Halting system...

flushing ide devices: hda

System halted.

10. Turn off each server.

To start up the system again, follow the procedure in “Starting the System” on page 58.

Starting a System in Single-Server Mode

If the servers were not operating in their normal system configuration, such as AB in dual-server systems, or if they were not shutdown using normal procedures according to instructions in this manual, the databases on the servers may not be mirrored.

If the databases are not mirrored, you must not bring the system up using normal start up procedures as instructed in “Starting the System” on page 58 or you will risk database corruption.

If non-mirrored servers, the system administrator must bring the system up in single-server mode and then go through the database re-mirroring process. This section provides the steps for starting a system in single-server mode.

Starting a System in Single-Server Mode

Contact Avid Customer Support for assistance with triple-server systems. It might be

possible to start these systems in a dual-server mode, depending on the circumstances of the shutdown.

To start the iNEWS system in single-server mode:

1. Power up or reboot the server on which you want the system to run.

2. Select that server.

3. Log in as a system operator by typing:

4. When prompted, type the password.

5. Do one of the following:

t To connect server A as a single system, enter the following command:

connect a single=a

t To connect server B as a single system, enter the following command:

connect b single=b

The syntax

use C in place of A or B. Also, notice in the following sample message that the “System is A” not AB or ABC.

net=a

net= b

Messages similar to the following appear:

Sep 10 16:25:52 inews-a last message repeated 15 times ...

Sep 10 16:26:44 inews-a work:[2034]workserver Hot-to-go

connect successful for NRCS-A, starting servers...

A is OFFLINE. ID is NRCS

System is A. Master is A.

Disk status is OK. The database is OPEN.

NRCS-A$

is also acceptable. If you have a third server, such as server C,

When you restart the system, remove these locks.

Checking for edit and order locks might take time depending on the size of the database. In

an emergency, bypass this step to get the system running. Go back later and remove locks to provide system access. The system can detect invalid locks and will ignore them.

t Type:

dbclean -x .

3 Getting Started

The -x option tells dbclean to skip queues or directories marked with a skip flag, reducing the time it takes to run.

The period ( so that it does not miss any part of the database not marked with a skip flag.

) after the -x causes dbclean to start at the root directory of the database,

7. Type:

startup

Checking free space...

Sep 10 15:42:51 NRCS msg: System is being configured

database size 10002352,free 9955000=100%,freelist 1991

Starting NRCS programs...

booting device 100

booting server 130

The entire newsroom computer system will now be run off the single server. The commands entered on a single-server system for shutting down are the same as those used to shut down a dual-server or triple-server system. To return to a dual or triple-server system, it will be necessary to complete the database re-mirroring process.

4 Users

People in your newsroom must have user accounts to use the iNEWS newsroom computer system. Each user account has various user traits associated with it that capture information about the user’s interaction with the system—information such as passwords, keyboard preferences, and permissions for story editing.

This chapter explains how the system administrator can access and change user account information from any iNEWS Workstation. However, user traits can also be viewed and modified at the console. The procedures for using the console are covered in “Managing

Traits at the Console” on page 623.

This chapter contains the following main sections:

• Viewing User Accounts

• Modifying User Traits

- Changing a User’s Password

- Changing User Preferences

- Setting up Simplified Users

• Creating New Users

- Creating a New User Area in News Database

- Adding a New User Account

- Enabing a New User to Receive Mail

• Searching for User Information

• Removing User Accounts

• The User Manager Account

• The Database Manager Account

• Logging Out All Users

Viewing User Accounts

You must be logged on as a superuser or user manager (umanager) to change user traits. For an explanation of the umanager account and privileges, see “The User Manager Account” on

page 96.

To view traits associated with a particular user account:

1. Select Tools > Options > Users.

The Manage User Accounts dialog box appears.

2. Enter the user name in the User ID field.

An asterisk (*) in the User ID field will result in all user accounts listed when you click

Search or press Enter. To search for all users with names that start with a certain letter, type that letter followed by an asterisk.

3. Do one of the following:

t Click Search.

t Press Enter.

Viewing User Accounts

The results of the search appear in the User List field located in the center of the dialog box. The data provided in the field includes: User ID and Name, last time the user logged in, whether the user account has superuser privileges, and so forth. The scroll bar at the bottom of the field may be used to view the rest of the User Account data.

The Print User List button will send the User Account data for the results appearing in

the User List field to the printer. There is no option to selectively limit what data is printed.

4. Do one of the following:

t Double-click the user name in the User List field.

t Click the name once to select it, and then click the Modify/Display button.

The Modify button will appear with the word Display on it if you do not have authority to

modify user accounts. This applies to user managers (umanager) who cannot alter superuser accounts. Also, the traits shown in the dialog box will appear gray to indicate that the information is for viewing only.

The Modify User Account dialog box appears.

The dialog box shows user traits associated with the account you chose, such as the user’s name, read rate, and mail queue name. All user traits shown in the various sections of the Modify User Account dialog box are explained in detail in “User Traits”

on page 69.

4 Users

Modifying User Traits

You must be logged on as a superuser or user manager (umanager) to change user traits. The superuser account is an iNEWS user account with superuser type access privileges. It is not the same as the superuser mode used at the console. See “User Traits” on page 69 for more information. For an explanation of the umanager account and privileges, see “The User

Manager Account” on page 96.

To modify a user’s traits from an iNEWS Workstation:

1. Access the Modify User Account dialog box as explained in “Viewing User Accounts”

on page 66.

The Modify User Account dialog box appears.

2. Select or deselect check boxes and fill in the fields in the Queues section of the dialog box as needed. See “User Traits” on page 69 for more information.

You can click the Get from Template button to copy traits from another pre-defined user

account. The template must be selected prior to the start of account modification or the button will be inaccessible (grayed out). See “Adding a New User Account” on page 88 for more information.

3. Create or change the password, as explained in “Changing a User’s Password” on page

74.

4. Click User Preferences and modify settings, as explained in “Changing User

5. Click OK to save modifications. The Cancel button closes the dialog box without saving

User Traits

The Modify User Account dialog box divides each user’s traits into sections, such as Type, Edit Mode, Queues, and so forth.

Modifying User Traits

Preferences” on page 75.

changes.

These sections are explained in the following summary of all user traits.

User ID and User Name

The User Name field contains the user’s real name. It should not be confused with the User ID, which the system uses to identify account activity. For instance, a user might have an account with a User ID

dmitchell

, his User ID, to log on to iNEWS.

dmitchell

; his real User Name is Dan Mitchell, but he will type

4 Users

Typ e

The Type section contains the check boxes that determine what type of user account is assigned to the user, and consequently, what privileges.

If the check box is selected, the type is applied to that user account.

Type Description

Superuser A superuser account allows the user complete access to administration

features, such as user accounts, the database, the System directory, and connect sessions to the console that controls the servers.

Blacklisted A blacklisted account cannot be used to log in to an iNEWS Workstation.

This type is used for special accounts, such as umanager and dbmanager. It is not intended for standard user accounts. Another practical use for this trait is to quickly disable an account of someone leaving or someone who works intermittently.

Simplified A simplified account sets certain access limits, such as the maximum number

of iNEWS Workspaces allowed. See “Setting up Simplified Users” on page

83 for more information.

Local Only User accounts flagged as local only cannot be used for session identification

by incoming Community sessions. The generic username is used instead.

Edit Mode

The Edit Mode section’s radio buttons set up the condition of the PC keyboard’s Insert key at log in. The users can still toggle between Insert and Overwrite mode as they work.

Condition Description

Insert The Insert editing mode, when selected, means if a user types text between

two characters, the text is inserted at the cursor position without overwriting the character to the right of the cursor. This is the more typical selection.

Modifying User Traits

Condition Description

Overwrite The Overwrite editing mode, when selected, means each character a user

types replaces the next character to the right of the cursor as the cursor moves through the text.

Queues

The iNEWS system provides a People directory in the database file structure that lets system administrators to set up a personal directory and two queues for each user as data storage. The Queues fields in the Modify User Account dialog box indicate the navigation paths (or locations) of the user’s personal directory and queues.

The actual directory and queues are not created here. The People directory, which can be

customized for your environment through a system dictionary, is provided as part of the default database. See “Creating a New User Area in News Database” on page 86 for more information.

Queue Fields Description

Home The Home field contains the path to the directory (folder) where the

Destination and Mail queues are stored in the database file structure.

Destination The Destination field contains the path to the queue provided for the user as a

storage location, such as Notes.

Mail The Mail field contains the path to the user’s Mail queue, which is where all

internal iNEWS mail to that user is kept in the database.

For sites that do not use iNEWS mail, set this field to SYSTEM.SHREDDER. Also, even if your site uses iNEWS mail, all template or special accounts (umanager and dbmanager for example) should be set to SYSTEM.SHREDDER. This does not prevent users from sending mail, but it does prevent user accounts from receiving mail.

4 Users

Read Rate

The Read Rate is the user’s spoken reading rate in words per minute. The average English reading rate is 180 words per minute. The iNEWS system takes the read rate from the user ID named in the story’s presenter field to determine the audio (air) time of a story. This also applies to the text timing clocks.

Session Features

There are three sections of the Modify User Account dialog box pertaining to features. The Session Features section defines access to other parts of the system.

If the check box is selected, the feature is applied to that user account.

Feature Description

Media Browse The Media Browse check box determines access to the Media Browse

plug-ins within iNEWS.

Connect Services The Connect Services check box determines access to the Connect to Service

dialog box.

Manage Projects The Manage Projects check box determine whether a user can manage

projects and facets in the system.

Configuration Features

The Configuration Features section pertains to the look of the iNEWS Workspace.

If the check box is selected, the feature is applied to that user account.

Modifying User Traits

Feature Description

Toolbars The Toolbars check box determines whether the user can create custom

toolbars.

Color Highlights The Color Highlights check box determines whether the user can customize

the highlighting status colors in the queue.

Highlight Read The Highlight Read Stories check box specifies that unread stories in the

queue are highlighted on the user’s screen. The highlight is removed when the cursor is positioned on the story. This feature only applies to stories in a queue with the Watch Appends database trait.

Queue Features

The Queue Features section pertains to access privileges in the Queue panel of the iNEWS Workspace.

If the check box is selected, the feature is applied to that user account.

Feature Description

Reorder Stories The Reorder Stories check box determines authority to alter the order of the

stories in any queue to which the user has write access.

Create/Kill... The Create/Kill Folders/Queues check box determines authority to create or

delete queues and folders (directories) in the database file structure, as seen in the Directory panel of the iNEWS Workspace.

Kill All Stories The Kill All Stories check box determines authority to delete all stories in a

single action from any queue to which the user has write access. The data is actually moved from the selected queue to the DEAD queue where it remains (and can be accessed) until purged.

4 Users

Password

The Password section has two options with which you can set up or force a user to change an assigned password. See “Changing a User’s Password” on page 74 for more information.

Option Description

Password The Password button opens a dialog box that you can use to set up or change

the password protecting access to the user account.

Force Change The Force Change check box determines whether the user is forced to change

the assigned password at the next login.

User Preferences...

The User Preferences button is used to view and/or modify a user’s preferences, such as keyboard, printer, and confirmation settings. See “Changing User Preferences” on page 75 for more information.

Get from Template...

The Get from Template button is only used when copying the traits of one user’s account to another. See “Adding a New User Account” on page 88 for more information.

Changing a User’s Password

The password must be a minimum of five alphanumeric characters (and a maximum of 12 characters) with no spaces. Use the system profile to set or change a required length for all passwords for your site.

System administrators cannot retrieve a user’s password, only change it.

Modifying User Traits

To change a user’s password:

1. Click the Password button in the Modify User Account dialog box.

The Change User’s Password dialog box appears.

2. Type the password in the New password field.

3. Confirm the new password by retyping it in the Confirm new password field.

4. Do one of the following:

t Click OK to store the password for saving after all modifications to the user’s

account are done. This will close the dialog box. The process of saving the password is only completed after the OK button on the Modify User Account dialog box is also clicked.

t Click Cancel to close the dialog box without saving changes.

Changing User Preferences

System administrators can use the Preferences dialog box to set up default preferences for users. However, the Preferences dialog box is—by default—accessible to users, so they can alter these settings at any time. Users, unless their access is limited by the system administrator, can access the Preferences dialog box to modify their preferences by selecting Tools > Options > Preferences at any iNEWS Workstation. To learn how the system administrator can limit access to this dialog box and its features, see “Setting up Simplified

Users” on page 83.

4 Users

To change user preferences:

1. Click the User Preferences button in the Modify User Account dialog box.

The Preferences dialog box will appear, containing several tabs.

2. Modify the preference settings on each tab as needed. The settings are described in detail in “User Preferences” on page 76.

3. Do one of the following:

t Click OK to store the preferences for saving after all modifications to the user’s

account are done. This will close the dialog box.

The process of saving the preferences is only completed after the OK button on the Modify User Account dialog box is also clicked.

t Click Cancel to close the dialog box without saving preference changes.

User Preferences

The Preferences dialog box contains several tabs. These various tabs are explained in the following summary of all user preferences.

Modifying User Traits

Session Tab

The Session tab has two sections, which system administrators can use to set up default user preferences.

User Preference Description

Keyboard The keyboard drop-down list contains a list of keyboards (or sets of macros)

that can be assigned to the user account as a default for when the user logs in. The Reload button lets the keyboard assignment take effect without having the user log off and back on.

Printing The Printing drop-down list contains pre-defined Styles that can be assigned

to the user account as defaults for when the user prints data from an iNEWS Workstation.

4 Users

Confirmations Tab

The Confirmations tab is divided into sections and contains check boxes that determine whether iNEWS prompts the user to confirm a request before completing the command.

User Preference Description

Saving Story When Saving Story is checked, iNEWS Workstation will display a

confirmation message to save changes before closing an edited story. If you do not select the Saving Story check box, the system automatically saves changes before closing stories.

Exit When Exit is checked, iNEWS Workstation will display a confirmation

message when the user attempts to close the iNEWS NRCS program at the workstation.

Story Operations When Story Operations is checked, iNEWS Workstation will display a

confirmation message before moving a story when you use the mouse to drag it to its new position.

Queue Operations When Queue Operations is checked, iNEWS Workstation will display a

confirmation message before moving all stories in a queue when you use the mouse to drag them to their new position.

Queue Reorder When Queue Reorder is checked, iNEWS Workstation will display a

confirmation message before moving a story to a new location in the same queue.

Story When Story is checked, iNEWS Workstation will display a confirmation

message before deleting a story or stories.

Modifying User Traits

User Preference Description

Mail or Message When Mail or Message is checked, iNEWS Workstation will display a

confirmation message before deleting e-mail or instant messages.

Production Cue When Production Cue is checked, iNEWS Workstation will display a

confirmation message before deleting a production cue and its marker from a story.

A production cue marker (shown at left) appears in the Story Text

panel.

Backup Tab

The Backup tab defines the settings for the iNEWS Workstation to automatically back up work in a current session to a specified location at specific time intervals.

User Preference Description

Interval Interval specifies the number of minutes between story backups. The default

is 10 minutes. Set the interval to 0 (zero) minutes to turn off the automatic backup feature.

Directory Directory specifies the path name—the location in which iNEWS

Workstation should store backup copies of stories. The location should be a directory (folder) on the harddrive of the local PC/workstation. By default, the location is the iNEWS program directory, which is only accessible to computer administrators or power users. Regular Windows users should set this to My Documents. You can type the path in manually, or click the Browse button to select the directory from the Browse dialog box.

4 Users

Refresh Tab

The Refresh tab sets the seconds for refreshing the screen at the workstation.

This preference is unique because it only affects the workstation on which it is set.

Set the number to zero (0) for instant updating—that is, if you do not want to delay refreshes. A zero delay does require more system and network resources.

Layout Tab

The Layout tab is divided into sections and contains buttons and check boxes that determine the layout of panels and workspaces in the iNEWS Workstation main window.

Modifying User Traits

User Preference Description

Start in Session The Start in Session field specifies the default session that will appear on

screen when the user logs in to iNEWS Workstation.

Get Current The Get Current button will reset the preferences on the Layout tab to what

was set when the dialog box opened.

Depending on which Arrangement button is selected, the iNEWS Workstation will display the panels of the iNEWS Workspace accordingly.

Zoom In the Arrangement section, when Zoom is checked, iNEWS Workstation

will display the iNEWS Workspace in zoom mode—that is, zoomed into one of the three panels: Directory, Queue or Story.

Hide Form In the Arrangement section, when Hide Form is checked, iNEWS

Workstation will display the Story panel with its Story Form panel hidden. The user can choose to show the Story Form panel by selecting the option to show the form from the Story drop-down menu.

Horizontal In the Gridlines section, when Horizontal is checked, iNEWS Workstation

will display horizontal gridlines between rows in the Queue panel.

Vertical In the Gridlines section, when Vertical is checked, iNEWS Workstation will

display vertical gridlines between columns in the Queue panel.

Use Default In the Preview Lines section, when Use Default is checked, iNEWS

Workstation will display the default number of preview lines for each story in the Queue panel as defined by the queue’s properties. When Use Default is not checked, every queue will display only one line of information per story in the Queue panel.

Users can manually override the Preview Lines setting by selecting the Story Preview option

in the View drop-down menu. In the Story Preview dialog box, the user can override the default setting by typing in a number in the Lines to preview field. This overrides the setting for the queue while displayed. Once the user exits the queue, the queue’s default setting is reinstated. If the user wants to return to the default setting manually (as defined in the queue’s properties), the user can click the Default button in the Story Preview dialog box.

The following figures show the difference between Queue panel displays with and without Preview lines. The first figure shows the display using the default of seven preview lines, as defined in the queue’s properties.

4 Users

The second figure shows the Queue panel display without preview lines. This is the view when Use Default is unchecked, unless otherwise specified.

Modifying User Traits

Search ResultsTab

The Search Results tab allows you to set the default form used in the Queue panel of the Search Results workspace.

The iNEWS Workstation will use the form selected from the Use form drop-down list when displaying the results from searches in iNEWS. The forms you can choose from are those created and stored in SYSTEM.FORMS. See “Creating Forms” on page 198 for more information.

Setting up Simplified Users

A simplified user is one that has certain limitations pertaining to the iNEWS Workstation. As the system administrator, you can define the limitations and then assign them to users. Only one set of limitations can be defined, which is then applied to all user accounts with the simplified user trait. In other words, either a user account has the simplifed user trait, with its designated limitation settings, or it does not.

Some of the Simplified User Settings lock the user’s preferences to those defined by the system administrator using the Preferences dialog box. See “User Preferences” on page 76 for more information.

To set up or modify the simplified user limitations:

1. Access the Modify User Account dialog box as explained in “Viewing User Accounts”

on page 66.

2. Click the Simplified UI button.

4 Users

The Simplified User Settings dialog box appears.

The dialog box divides the settings into two sections, which are explained in the next sections of this chapter.

3. Select or deselect check boxes, as required.

4. Click the OK button to save the settings and close the Simplified User Settings dialog box.

Use the Reset button to discard changes and reset the check box settings to what they were when the dialog box opened.

Simplified User Settings

The Simplified User Settings dialog box splits the settings into two sections. These sections are explained in the following summary of all simplified user settings.

Workspaces Section

The Workspaces section of the dialog box provides settings that pertain to the arrangement and quantity of workspaces within the iNEWS Workstation’s main window.

Modifying User Traits

Setting Description

Limit Number to When Limit Number to is checked, iNEWS Workstation will prevent the user

from opening more workspaces than the number specified. This limit does not apply to the workspaces opened using the Urgent Wire and Mail buttons. However, this does lock the Urgent Wire workspace so the user is unable to navigate to other queues or directories in that workspace.

Lock Arrange When Lock Arrange is checked, iNEWS Workstation will prevent the user

from altering the arrangement of panels in the Workspace. This disables the Arrangement buttons on the standard Layout toolbar. The setting is locked into the default arrangement as defined in the user’s User Account Preferences.

Lock Layout When Lock Layout is checked, iNEWS Workstation will prevent the user

from altering the layout of workspaces in the iNEWS Workstation main window. This disables the Layout buttons on the standard Layout toolbar. The setting is locked into the default layout as defined in the user’s User Account Preferences.

Lock Zoom When Lock Zoom is checked, iNEWS Workstation will prevent the user from

altering the zoom of panels in the iNEWS Workspace. The setting is locked into the default as defined in the user’s User Account Preferences.

Application Section

The Application section of the dialog box provides settings that pertain to accessing certain iNEWS features at any workstation.

Setting Description

Lock Toolbars When Lock Toolbars is checked, iNEWS Workstation will prevent the user

from altering the display of toolbars.

Lock Sessions When Lock Sessions is checked, iNEWS Workstation will prevent the user

from creating or altering sessions. The user will be locked to sessions created prior to the Lock Sessions being applied to the user account.

4 Users

Setting Description

Disable Title Entry When Disable Title Entry is checked, iNEWS Workstation will prevent user

access to the Title Entry dialog box, used to enter production cues in stories, and the Edit Title Entry Template dialog box, used to create CG templates for the Title Entry feature.

Disable User Prefs... When Disable User Prefs Dlg is checked, iNEWS Workstation will prevent

user access to the Preferences dialog box. The user will be unable to alter user preferences, such as default printer settings. The user will be locked to settings already in place at the time Disable User Prefs Dlg is applied to the user account. See “Changing User Preferences” on page 75 and “User

Preferences” on page 76 for more information.

Creating New Users

To set up new users in iNEWS, you must complete three separate procedures:

• Create areas in the iNEWS database file structure where the user can store notes and receive mail. See “Creating a New User Area in News Database” on page 86 for more information.

• Add a new user account so that your system recognizes the user. This includes setting up the user traits associated with the account. See “Adding a New User Account” on page

88 for more information.

• Enable the new user to receive mail by adding him or her to the appropriate group. See

“Enabing a New User to Receive Mail” on page 91 for more information.

To ensure a user has appropriate database privileges, the user should also be assigned to the

correct group or groups. For more information, see “Adding Users as Members of a Group”

on page 162.

Creating a New User Area in News Database

While a user account will work without this area, it is traditional for each user to have his or her own area in the database to keep notes and to receive e-mail. Usually, these areas are separate queues called Notes and Mail. These queues are kept in a sub-folder—with the user’s account name—in the People directory.

The common practice is to separate the first level of People sub-folders by using the first initial of the user’s last name—otherwise, since the system is limited to 250 folders in the People directory, your site might eventually reach the limit.

Creating New Users

For instance, the following procedures, the Home directory for our sample user, DANIELMI, would be: PEOPLE.D.DANIELMI. The Notes and Mail queues would be: PEOPLE.D.DANIELMI.NOTES and PEOPLE.D.DANIELMI.MAIL, respectively.

You must be logged on to iNEWS NRCS with a user account that has authority to create new

directories and/or queues to complete these procedures.

To create a new directory:

1. Using the database file structure in the Directory panel of the iNEWS Workspace, select the directory under which you want the new folder to be created, as shown in the following example.

For instance, for user DANIELMI, you would select PEOPLE, then the folder with the alphabetic name corresponding to the first letter of the user’s name, such as D. This ensures the new folder will be created in the D directory (folder).

2. Do one of the following:

t Select Tools > New Folder.

t Right-click on the folder in the Directory panel, and select New Folder from the

context menu.

A new folder is created under the selected folder. The New-Folder appears at the end of the list of existing folders.The title, New-Folder, is highlighted, so you can rename it.

3. Type the name of the new folder.

4. Press Enter to save the new folder name. You can now open the new folder (directory) by double-clicking on it.

You can now create new queues for the user, such as Notes and Mail queues.

4 Users

To create a new queue:

1. Navigate to and select the folder created to hold the queue you want to create, such as PEOPLE.D.DANIELMI.

2. Do one of the following:

t Select Tools > New Queue.

t Right-click on the folder in the Directory panel and select New Queue from the

context menu.

A new queue appears under the folder you selected. The New-Queue appears at the end of the list of existing queues. The title, New-Queue, is highlighted, so you can rename it.

3. Type the name of the new queue, such as MAIL or NOTES.

4. Press Enter to save the new queue name. You can now open the new queue by double-clicking on it.

Adding a New User Account

When adding a new user account, you have the option of creating the account from scratch or copying the traits of another user account already in the system. This section covers both options.

Before you can copy user traits from one user account to another, you must first select the account you want to copy—that is, select an account to use as a template.

To define an account as a template for copying to other accounts:

1. Select Tools > Options > Users.

The Manage User Accounts dialog box appears.

Creating New Users

If you do not have superuser privileges, which permits access to the Manage User Accounts

dialog box, the system will prompt you for the umanager password. If the umanager account does not exist in the system, then access is only allowed to system administrators—that is, those with superuser privileges. See “The User Manager Account” on page 96 for more information. Also, see “User Traits” on page 69 for more information on the superuser trait and its privileges.

2. Search for the user account you want to use as a template for copying user traits. See

“Searching for User Information” on page 91 for more information.

3. Select the User ID when it appears in the search results list.

4. Click Copy. The User ID should appear to the right of the button. When no template is selected for copying, the words, “No template set,” appears to the right of the Copy button.

Once a Template User is established, selecting the New User... button will start with the same configuration as the template user, and selecting Get from Template when modifying an existing user will set the configuration to that of the template user.

4 Users

To add a new user account (either from scratch or by copying the user traits):

1. Select Tools > Options > Users.

The Manage User Accounts dialog box appears.

2. Click New User.

The Add New User dialog box appears.

3. In the User ID field, enter the login name of the user account.

4. (Optional) In the User Name field, enter the user’s real name.

5. (Optional) Modify the various traits you want to apply to the new user account.

A user’s traits can be modified at the time of creation or afterwards from the iNEWS

Workstation or from the console. For more details about the various user traits, see “User

Traits” on page 69 or “User Traits Console Command Summary” on page 632.

6. Click Add to add the new user account.

Enabing a New User to Receive Mail

This section gives you the basic steps you need to follow to enable a new user to receive mail. If you need more information, refer to the information on groups in “Adding Users as

Members of a Group” on page 162.

To enable a new user to receive mail:

t Add the user to a group in SYSTEM.GROUPS. When the group story is saved, the mail

delivery files are updated automatically.

A group story is one that you created in the system for groups in your organization such as newscasters, staff, or reporters. By adding the user to a group, the user inherits the group’s security traits.

Searching for User Information

A search capability in iNEWS lets you search for information about a particular user by specifying a user name and including certain criteria to refine the search. You can specify any alphanumeric characters in the search. You can use the asterisk (*), which acts as a wildcard, only as a suffix—not as a prefix or in the middle of a word. Used alone, the wildcard is equivalent to “all.” Used with additional information, the wildcard serves as a parameter to the search.

Searching for User Information

For instance, if you are searching for all user accounts beginning with Dave, type Dave* (no space).

4 Users

To search for information about users:

1. Select Tools > Options > Users.

The Manage User Accounts dialog box appears.

2. Enter the name of the user in the User ID field.

3. Click Search or press Enter.

If you search with a wildcard character and the system finds multiple matches, a results box appears listing all “hits”. You can specify one by double-clicking on it; this opens the specified user’s information in another dialog box.

The results of the search appear in the User List field in the center of the dialog box.

To quickly locate a name in the User List, type the name you want; the list will be positioned to a point matching what you type. User names are not case-sensitive, so you can use lowercase. To prevent you from having to type the whole name, the system automatically tries to match the letters you supply with a name in the list. Continue typing until the system locates the name you want.

4. Click Advanced to refine your search for a user.

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

Searching for User Information

5. Select from the settings to specify additional search criteria. The criteria options are explained in detail below.

Settings Description

All Users Search through all user accounts on the server.

Superusers Confine the search to user accounts with the superuser attribute.

Non-Superusers Confine the search to user accounts without the superuser attribute.

Blacklisted Users Confine the search to user accounts with the blacklisted attribute.

Non-Blacklisted Users

Members of Group Confine the search to user accounts belonging to the security group you

Users Without Passwords

Simplified Users Confine the search to user accounts that have the simplified user trait.

Non-Simplified Users Confine the search to user accounts that do not have the simplified user

Local Only Users Confine the search to local system user accounts only.

Confine the search to user accounts without the blacklisted attribute.

select from the drop-down list.

Confine the search to user accounts that do not have passwords.

trait.

4 Users

Settings Description

Non-Local Only Users

Date Range Confine the search to dates you specify in the From and To fields and the

Confine the search to non-local system user accounts only.

kind of date range:

When the user last logged in

When the user account was created

When the password changed

Specify the date by either clicking the arrow buttons or typing the dates in ddmmmyyyy format. Indicate the day with two digits, the month with three letters, and the year with four digits.

6. Click OK to confirm your advanced search setting or click Cancel to cancel it.

7. Click Search to initiate the search.

A progress bar appears if a lengthy search is underway. The results of the search appear in the User List field in the center of the Manage User Accounts dialog box.

Above the field, iNEWS NRCS will display a brief statement indicating what matched the search criteria, such as:

All users matching ‘*‘:

Use the horizontal scroll bar at the bottom of the User List field to view the information headings, such as User Name, Last Login, Read Rate, and so forth.

Removing User Accounts

You must have access to the Manage User Accounts dialog box to remove user accounts. In other words, you must be logged on as a system administrator—that is, with an account that has superuser privileges—or successfully enter the user manager (umanager) password to remove user accounts.

Before removing user accounts from the system, remove the users’ names from the

stories in

To remove user accounts:

1. Select Tools > Options > Users.

SYSTEM.GROUPS

The Manage User Accounts dialog box appears.

. This reduces the potential for mail bounce back errors.

Removing User Accounts

If you are logged on as a system administrator, the Manage User Accounts dialog box will

appear automatically, following step 1. Otherwise, iNEWS will prompt you for the umanager password (if that account exists in the system) before allowing access to the dialog box.

2. Enter the name of the user in the User ID field.

3. Click Search or press Enter.

The results of the search appear in the User List field in the center of the Manage User Accounts dialog box.

4. Select the name of the user you want to remove by clicking the name in the User List field.

4 Users

5. Click Remove.

6. Click OK to remove the user or Cancel to stop the removal.

After removing the user, you will also need to remove the user’s Home directory and the

Notes and Mail queues by deleting them from the system’s database file structure. You can also use the msgclean command at the console to remove any of the user’s unread messages.

The User Manager Account

A user manager has some special system privileges, but not as many as a system administrator/superuser. For instance, user managers can add, remove, or change any user account, except those with the superuser attribute.

There can be only one user manager account in iNEWS; however, several users may acquire user manager privileges by successfully entering the user manager password when prompted. Unlike a superuser account, the user manager account is not used to log in to the system. Users with user manager privileges log in to their own accounts, as usual. When they need to do user manager tasks, they must access the Manage User Accounts dialog box, by typing in the user manager password.

To create a user manager account:

1. Create a user account as explained in “Adding a New User Account” on page 88.

2. Give the account a User ID:

3. Assign a password to the account.

4. Make the user manager account blacklisted so that no one can use it to log in to the system.

5. Assign the account superuser status to prevent a user manager (or anyone who does not have superuser status) from changing the account’s password.

6. Tell the user manager(s) the ID and password for the user manager account.

For further security, a write-access group should be assigned to SYSTEM.GROUPS and only those with user manager privileges should be included in the group. If no write-access group is assigned to SYSTEM.GROUPS, then all users who know the umanager password can access the Manage User Accounts dialog box by selecting Tools > Options > Users. After a write-access group is set up, any user managers with nonsuperuser accounts must be included in the write-access group for SYSTEM.GROUPS or they will not be allowed access to the Manage User Accounts dialog box. See “Groups Tab” on page 128, “Adding Users as Members of a Group” on

page 162, and “Group Access and Usage Restrictions” on page 169 for more

information.

umanager

The Database Manager Account

A database manager has some special system privileges, but not as many as a system administrator/superuser. For instance, database managers can add, remove, or change any database trait on a directory or queue in the iNEWS database from a workstation. Database managers also have access to the CG Template Editor, used to create and modify template for the Title Entry feature.

There can be only one database manager account in iNEWS; however, several users may acquire database manager privileges by successfully entering the database manager password when prompted. Unlike a superuser account, the database manager account is not used to log in to the system. Users with database manager privileges log in to their own accounts, as usual. When they need to do database manager tasks, they must access the Directory/Queue Properties dialog box. To modify anything in the dialog box, they must provide the database manager password.

To create a database manager account:

1. Create a user account as explained in “Adding a New User Account” on page 88.

The Database Manager Account

2. Give the account a User ID:

3. Assign a password to the account.

4. Make the database manager account blacklisted so that no one can use it to log in to the system.

5. Assign the account superuser status to prevent a user manager (or anyone who does not have superuser status) from changing the account’s password.

6. Tell the database manager(s) the ID and password for the database manager account.

Logging Out All Users

Sometimes maintenance of the iNEWS system requires you to first log out all users before completing a certain task, such as shutting down the system. This section explains the best way to log out all users from the console.

To log out all users:

1. Select all servers.

2. To prevent users from logging in, take the system offline by typing:

Use

offline silent

attempts.

if you want to suppress output of messages from new user login

dbmanager

offline

4 Users

3. Use the broadcast command to send a message warning all users that are logged in that they must log out and why. If the system will be shut down, include the time it will be shut down. Here are a few examples:

NRCS-A$ broadcast -l WARNING\! System shut down at 12PM

NRCS-A$ broadcast -l LOG OUT\! System shut down at 5 minutes.

NRCS-A$ broadcast -dl LOG OUT\! System shut down in 10 seconds.

The backslash (\) before the exclamation point (!) is required because the exclamation point is a reserved character in Linux.

The -l (the letter L, not the number 1) after broadcast is to limit the message to local workstations only and not to users connected through Community. You may also add -d after broadcast and before the message if you want your message to appear at the workstation as a popup message. The two can be combined as shown (-dl) to broadcast local popup messages.

4. At the specified shutdown time, check the system for any users still logged in by selecting one server and typing:

A message similar to the following appears:

G505 miller A

G500 allen B

G507 stevens A

R801 stevens A

list s

A connect session will show up as an ‘R’ device. The system administrator must notify them of the shutdown by some other means, such as by telephone.

You must ensure that all users are logged out if shutting down the system. If a user is in a connect session when the system is shut down, the user’s workstation stops, the session is disconnected, and any unsaved work is lost. Ensure any connect session users have logged out before you continue the shutdown procedure.

5. To stop a connect session, select the appropriate server and then use the following format of the stop command:

For instance, to stop the connect session ( previous example, type:

6. Select all servers.

7. Log out all users by typing:

stop <device number>

stop 801

logout all

R801 stevens A

) that was shown in the

If a user is editing a story, the system saves the file and then logs out the user. The logout command will not log out users who are in connect sessions.

5 The Database: Directories, Queues,

and Stories

All relevant iNEWS information—except the system software and the Linux files—is stored in the iNEWS database. This database contains stories, queues, and directories or more specifically: scripts, rundowns, e-mail, messages, users, groups and their memberships, and any other kind of information entered into the system. Some database maintenance, such as altering the database file structure and traits, can be done from the console or from any iNEWS Workstation. This chapter focuses on maintenance tasks at the workstation when possible. However, when a task can be done at both the workstation and console, the console information is provided as an appendix in this guide. See procedures for using the console in

“Managing Traits at the Console” on page 623.

This chapter contains the following main sections:

• Overview of the iNEWS Database

• Restrictions to Directory or Queue Creation

• Creating a New Directory

• Creating a New Queue

• Creating a New Story

• Renaming a Directory or Queue

• Deleting a Directory or Queue

• Recovering a Killed Story

• Viewing Database Traits

• Changing Database Traits

• Database Purge Intervals and Limits

• Identifying Locked Queues and Stories

• Removing Locks from a Workstation

• Unbusy Stories and Queues

Overview of the iNEWS Database

The iNEWS database is where all the data, such as scripts, rundowns, user accounts, and so forth, are stored. The database is structured in a way to promote ease of maintenance. For instance, it contains a file structure made up of directories, that contain other folders or queues, which in turn contain stories. It is similarly to a filing cabinet.

In iNEWS, the database file structure—directories and queues—can be seen (depending on your access privileges) in the Directory panel of the iNEWS Workspace. Directories, also known as folders, are indicated by manila folders, such as the People directory in the previous graphic. Queues are indicated by three overlapping pieces of paper, such as the Dead queue.

If your site uses the Projects feature of iNEWS, tabs will appear in the Directory panel

letting you select whether you want to view the iNEWS database file structure via the Directory tab or a list of defined projects via the Project tab. For more information on the Projects feature, see “iNEWS Projects” on page 465.

The scripts, notes, e-mail, news stories, and other kinds of information are all called stories; each story is contained in a particular queue, and each queue in a single directory. A directory can also be contained within another directory in which case it would be called a subdirectory or sub-folder of that directory.

Directories and queues have database traits that determine how the system manages the stories they contain, and also what actions users can perform with those stories.

Pinnacle Systems iNews - 3.3 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Contents

Using This Guide

Symbols and Conventions

If You Need Help

...With the Syntax of Console Commands

Avid Training Services

Overview of iNEWS

System Administrator Tasks

Overview of Hardware

Starting the Console

Console Display

Logging in as a System Operator

Entering Superuser Mode

Changing System Administration Passwords

Exiting the Console

Troubleshooting a Frozen Console

Types of Console Commands

Using Server Commands

Using Console Control Commands

Assigning Commands to Function Keys

Displaying Function Key Assignments

Selecting One or More Servers

Zooming in on One Server

Using Console History

Logged Console History

Using the Remote Console

Executing Remote Commands

Logging out a Remote Console

The Console Configuration File

Viewing the Console Configuration File

Editing the Console Configuration File

Starting the System

Shutting Down the System

Starting a System in Single-Server Mode

Viewing User Accounts

Modifying User Traits

User Traits

Changing a User’s Password

Changing User Preferences

User Preferences

Setting up Simplified Users

Simplified User Settings

Creating New Users

Creating a New User Area in News Database

Adding a New User Account

Enabing a New User to Receive Mail

Searching for User Information

Removing User Accounts

The User Manager Account

The Database Manager Account

Logging Out All Users

Overview of the iNEWS Database