56
Version 3.5.2 ReadMe 1 iNEWS ® Newsroom Computer System Version 3.5.2 ReadMe Date Revised Changes Made 25 May 2012 Added information related to v3.5.2 release 29 February 2012 Added information related to v3.5.1 release 15 February 2012 Added information related to v3.5 release including FTS v4.0 (There was no v3.4.6 release.) 19 October 2011 Added information related to v3.4.5 release (There was no v3.4.4 release.) 11 August 2011 Added information related to v3.4.3 release 28 July 2011 Added information related to v3.4.2 release 5 July 2011 Added information related to v3.4.1 release 12 May 2011 Added information related to v3.4.0 release 7 March 2011 Added information related to v3.3.1 release 30 November 2010 Added information related to v3.3.0 release 23 November 2010 Added information related to v3.2.2 release 14 October 2010 Added information related to v3.2.1 release 24 May 2010 Initial version (based off of v3.1.1 doc.) Important Information Avid recommends that you thoroughly read all of the information in this ReadMe file before installing or using any new software release. Note: Search the Avid Knowledge Base (http://www.avid.com/onlinesupport ) for the most up-to-date ReadMe file, which contains the latest information that might have become available after the documentation was published. This document describes compatibility issues with previous releases, hardware and software requirements, software installation instructions, and summary information on system and memory requirements, when applicable. This document also lists any hardware and/or software limitations. Note: Since this release of iNEWS will be more widely distributed than previous versions, some notes on important features and changes have been brought forward from previous ReadMe documents. Notes that are less important were not brought forward, and users should reference older iNEWS ReadMe files for additional change information not contained in this ReadMe.

Version 3.5.2 ReadMe - Avid Technologyresources.avid.com/SupportFiles/attach/Broadcast/ReadMe...Version 3.5.2 ReadMe 1 ˜˜ iNEWS® Newsroom Computer System Version 3.5.2 ReadMe Date

  • Upload
    others

  • View
    30

  • Download
    0

Embed Size (px)

Citation preview

  • Version 3.5.2 ReadMe

    1

    ��iNEWS® Newsroom Computer System Version 3.5.2 ReadMe

    Date Revised Changes Made

    25 May 2012 Added information related to v3.5.2 release

    29 February 2012 Added information related to v3.5.1 release

    15 February 2012 Added information related to v3.5 release including FTS v4.0 (There was no v3.4.6 release.)

    19 October 2011 Added information related to v3.4.5 release (There was no v3.4.4 release.)

    11 August 2011 Added information related to v3.4.3 release

    28 July 2011 Added information related to v3.4.2 release

    5 July 2011 Added information related to v3.4.1 release

    12 May 2011 Added information related to v3.4.0 release

    7 March 2011 Added information related to v3.3.1 release

    30 November 2010 Added information related to v3.3.0 release

    23 November 2010 Added information related to v3.2.2 release

    14 October 2010 Added information related to v3.2.1 release

    24 May 2010 Initial version (based off of v3.1.1 doc.)

    Important Information Avid recommends that you thoroughly read all of the information in this ReadMe file before installing or using any new software release.

    Note: Search the Avid Knowledge Base (http://www.avid.com/onlinesupport) for the most up-to-date ReadMe file, which contains the latest information that might have become available after the documentation was published.

    This document describes compatibility issues with previous releases, hardware and software requirements, software installation instructions, and summary information on system and memory requirements, when applicable. This document also lists any hardware and/or software limitations.

    Note: Since this release of iNEWS will be more widely distributed than previous versions, some notes on important features and changes have been brought forward from previous ReadMe documents. Notes that are less important were not brought forward, and users should reference older iNEWS ReadMe files for additional change information not contained in this ReadMe.

    http://www.avid.com/onlinesupport

  • Version 3.5.2 ReadMe

    2

    Contents

    Compatibility Notes and Issues ................................................................................................................................. 7

    Fast Text Search .................................................................................................................................................... 7

    Workstation/Server Compatibility Chart ............................................................................................................... 7

    Community Feature ............................................................................................................................................... 7

    iNEWS Client ........................................................................................................................................................ 7 iNEWS Server ....................................................................................................................................................... 8

    Command .............................................................................................................................................................. 8

    ControlAir .............................................................................................................................................................. 8

    MOS Gateway ....................................................................................................................................................... 8

    Console Multiplexer .............................................................................................................................................. 8

    Data Receiver ........................................................................................................................................................ 8 Instinct ................................................................................................................................................................... 8

    NewsCutter ............................................................................................................................................................ 8

    Teleprompter ......................................................................................................................................................... 8

    Installation Notes and Issues ..................................................................................................................................... 8

    FTS v4.0 ................................................................................................................................................................ 8

    FTS Installation and Configuration Procedure .................................................................................................. 9 iNEWS Installer ................................................................................................................................................... 15

    FTS v3.1.x ........................................................................................................................................................... 15

    New End User License Agreement ...................................................................................................................... 15

    Upgrade Notes and Issues ........................................................................................................................................ 15

    iNEWS v3.5.0 and FTS v4.0 ............................................................................................................................... 15

    iNEWS v3.4.1 ...................................................................................................................................................... 15 iNEWS v3.4.0 ...................................................................................................................................................... 15

    Upgrading iNEWS Server Software from Previous Versions ............................................................................. 16

    Upgrading iNEWS Client Software from Previous Versions .............................................................................. 16

    Upgrading iNEWS v2.8 Client Software to Future Versions .............................................................................. 16

    Upgrading iNEWS Server from Previous Versions ............................................................................................. 16 Changes between 3.5.1 and 3.5.2 ............................................................................................................................ 17

    Workstation ......................................................................................................................................................... 17

    Server ................................................................................................................................................................... 17

    Changes between 3.5 and 3.5.1 ............................................................................................................................... 17

    Monitor Server ..................................................................................................................................................... 17

    Changes between 3.4.5 and 3.5 ............................................................................................................................... 18

  • Version 3.5.2 ReadMe

    3

    FTS ...................................................................................................................................................................... 18

    Server ................................................................................................................................................................... 18

    Workstation ......................................................................................................................................................... 18 NSML .................................................................................................................................................................. 19

    Mapcheck ............................................................................................................................................................ 19

    Miscellaneous ...................................................................................................................................................... 19

    Changes between 3.4.3 and 3.4.5 ............................................................................................................................ 19

    Indexing ............................................................................................................................................................... 19

    Monitor Server ..................................................................................................................................................... 20 Messaging ............................................................................................................................................................ 20

    MOS .................................................................................................................................................................... 20

    Miscellaneous ...................................................................................................................................................... 20

    Changes between 3.4.2 and 3.4.3 ............................................................................................................................ 21

    Monitor ................................................................................................................................................................ 21

    Server ................................................................................................................................................................... 21 Workstation ......................................................................................................................................................... 21

    Changes between 3.4.1 and 3.4.2 ............................................................................................................................ 22

    Server ................................................................................................................................................................... 22

    User Interface ...................................................................................................................................................... 22

    Projects ................................................................................................................................................................ 23

    Production Cues ................................................................................................................................................... 23 Macros ................................................................................................................................................................. 23

    Changes between 3.4.0 and 3.4.1 ............................................................................................................................ 23

    Server ................................................................................................................................................................... 23

    Monitor Server ..................................................................................................................................................... 24

    Changes between 3.3.1 and 3.4.0 ............................................................................................................................ 24 Installation ........................................................................................................................................................... 24

    User Interface ...................................................................................................................................................... 24

    Server ................................................................................................................................................................... 25

    MCS Dictionary ................................................................................................................................................... 31

    Txnet .................................................................................................................................................................... 31

    Changes between 3.3.0 and 3.3.1 ............................................................................................................................ 31 Projects ................................................................................................................................................................ 31

    Community .......................................................................................................................................................... 32

    Messaging ............................................................................................................................................................ 32

    FTS ...................................................................................................................................................................... 32

    Seek ..................................................................................................................................................................... 32

  • Version 3.5.2 ReadMe

    4

    User Interface ...................................................................................................................................................... 32

    Macros ................................................................................................................................................................. 33

    MOS Integration .................................................................................................................................................. 33 Monitor Server ..................................................................................................................................................... 33

    Txnet .................................................................................................................................................................... 33

    Web Access ......................................................................................................................................................... 33

    Tokens ................................................................................................................................................................. 33

    Changes between 3.2.x and 3.3.0 ............................................................................................................................ 34

    Installation ........................................................................................................................................................... 34 User Interface ...................................................................................................................................................... 34

    Monitor Server ..................................................................................................................................................... 34

    Server ................................................................................................................................................................... 34

    NSML .................................................................................................................................................................. 35

    URLs and Web Services API .............................................................................................................................. 35

    Changes between 3.2.4 and 3.2.5 ............................................................................................................................ 35 Txnet .................................................................................................................................................................... 35

    User Interface ...................................................................................................................................................... 35

    Macros ................................................................................................................................................................. 36

    Server ................................................................................................................................................................... 36

    Changes between 3.2.3 and 3.2.4 ............................................................................................................................ 36

    User Interface ...................................................................................................................................................... 36 TXNET Server ..................................................................................................................................................... 36

    Changes between 3.2.2 and 3.2.3 ............................................................................................................................ 36

    Plug-ins ................................................................................................................................................................ 36

    User Interface ...................................................................................................................................................... 36

    Community .......................................................................................................................................................... 36 Interplay Integration ............................................................................................................................................ 36

    Changes between 3.2.1 and 3.2.2 ............................................................................................................................ 37

    Active X ............................................................................................................................................................... 37

    SYSTEM.MAP .................................................................................................................................................... 37

    User Interface ...................................................................................................................................................... 37

    Changes between 3.2.0 and 3.2.1 ............................................................................................................................ 37 Searching ............................................................................................................................................................. 37

    User Interface ...................................................................................................................................................... 37

    Calendar Issues .................................................................................................................................................... 38

    Miscellaneous ...................................................................................................................................................... 38

    Changes between 3.1.1 and 3.2.0 ............................................................................................................................ 38

  • Version 3.5.2 ReadMe

    5

    Hyperlinks ........................................................................................................................................................... 38

    Macros ................................................................................................................................................................. 38

    User Interface ...................................................................................................................................................... 38 Changes between 3.1.0 and 3.1.1 ............................................................................................................................ 38

    ActiveX Plugins ................................................................................................................................................... 38

    dbrestore and Restoring Stories ........................................................................................................................... 39

    Message Server .................................................................................................................................................... 39

    Changes between 3.0.x and 3.1.0 ............................................................................................................................ 39

    User Interface ...................................................................................................................................................... 39 Playout ................................................................................................................................................................. 39

    Searching and FTS ............................................................................................................................................... 40

    Stories .................................................................................................................................................................. 41

    NewsCutter Integration ........................................................................................................................................ 41

    Unicode ................................................................................................................................................................ 41

    Changes between 3.0.0 and 3.0.1 ............................................................................................................................ 41 Client ................................................................................................................................................................... 41

    Server ................................................................................................................................................................... 41

    Monitor Server ..................................................................................................................................................... 41

    User Interface ...................................................................................................................................................... 42

    Indexing & Searching .......................................................................................................................................... 42

    Macros ................................................................................................................................................................. 42 Changes between 2.x and 3.0.0 ............................................................................................................................... 42

    Messaging ............................................................................................................................................................ 42

    Monitor Server ..................................................................................................................................................... 42

    User Interface ...................................................................................................................................................... 42

    iNEWS Server ..................................................................................................................................................... 43 FTS Multiple Indexes .......................................................................................................................................... 43

    Site files ............................................................................................................................................................... 44

    New Features ........................................................................................................................................................... 44

    For iNEWS v3.5 .................................................................................................................................................. 44

    FTS .................................................................................................................................................................. 44

    Blockmode Command ..................................................................................................................................... 45 For iNEWS v3.4.5 ............................................................................................................................................... 45

    Community ...................................................................................................................................................... 45

    SYSTEM.MAP Syntax .................................................................................................................................... 46

    For iNEWS v3.4.0 ............................................................................................................................................... 46

    Mapcheck Utility ............................................................................................................................................. 46

  • Version 3.5.2 ReadMe

    6

    SYSTEM.MAP Queue .................................................................................................................................... 46

    For iNEWS v3.3.0 ............................................................................................................................................... 47

    Desktop Icon .................................................................................................................................................... 47 Projects and Facets .......................................................................................................................................... 47

    Search Queues ................................................................................................................................................. 47

    Queue Templates ............................................................................................................................................. 47

    For iNEWS v3.1.0 ............................................................................................................................................... 47

    Script Templates .............................................................................................................................................. 47

    NewsCutter media ............................................................................................................................................... 48 For iNEWS v3.0.0 ............................................................................................................................................... 48

    Hyperlinks ....................................................................................................................................................... 48

    Story links ........................................................................................................................................................ 48

    Comboboxes .................................................................................................................................................... 49

    Check boxes ..................................................................................................................................................... 49

    Duration ........................................................................................................................................................... 49 Calendar ........................................................................................................................................................... 49

    Field write groups ............................................................................................................................................ 50

    Editorial groups ............................................................................................................................................... 50

    Colors .............................................................................................................................................................. 50

    Lists ................................................................................................................................................................. 50

    Play Interplay Low-res Streams ....................................................................................................................... 51 Qualified Asian Languages and IMEs ..................................................................................................................... 51

    Korean ................................................................................................................................................................. 51

    Chinese Simplified .............................................................................................................................................. 51

    Chinese Traditional .............................................................................................................................................. 52

    Japanese ............................................................................................................................................................... 52 Vietnamese .......................................................................................................................................................... 52

    Microsoft Windows Critical Updates ...................................................................................................................... 52

    Known Issues and Limitations ................................................................................................................................. 53

    UNC Paths ........................................................................................................................................................... 53

    Keyboards ............................................................................................................................................................ 53

    iNEWS Web Services API .................................................................................................................................. 53 Multiple Monitors ................................................................................................................................................ 53

    Macros and Keystrokes........................................................................................................................................ 54

    Technical Support Information ................................................................................................................................ 55

    Accessing Online Support ................................................................................................................................... 55

  • Version 3.5.2 ReadMe

    7

    Compatibility Notes and Issues This section contains compatibility information related to the iNEWS 3.5 release or earlier.

    Fast Text Search Fast Text Search (FTS) version 4 is required for iNEWS Server version 3.5 and higher. FTS 4 is not supported on any iNEWS Server versions lower than 3.5. FTS 4 is supported on Windows Server 2008 R2, Windows XP SP3 (32-bit), and Windows Server 2003 SP2 (32-bit). The recommended operating system is Windows Server 2008 R2. A full re-index is required with an upgrade to FTS 4.

    Workstation/Server Compatibility Chart

    2.8 Server 3.0/1/2 Server 3.3. Server 3.4/5 Server

    2.8 Client Allowed Allowed Allowed Allowed

    3.0/1/2 Client Not allowed Allowed Allowed Allowed

    3.3 Client Not allowed Not allowed Allowed Allowed

    3.4/5 Client Not allowed Not allowed Not allowed Allowed

    Community Feature

    For iNEWS 3.4.5 to connect via community to iNEWS 3.4.5 or earlier servers, the 3.4.5 servers need to have a file named /site/env/gnews. The following string must be placed in that file: GCOMMUNITYSMALLDATABASE=1. See the New Features section of this document for additional information.

    iNEWS Clients cannot be used in a community where any server in their path is of a lower version than the client.

    • 3.4 clients can connect to 3.4 servers, which can connect through community to 3.4 servers.

    • 3.4 clients cannot connect to pre-3.4 servers directly or through community.

    • 3.3 clients can connect to 3.3 and higher servers, which can then connect through community to 3.3 and higher servers.

    • Clients prior to iNEWS 3.3 do not support the new features in iNEWS 3.3: projects, facets, search queues, and queue templates.

    • 2.8 clients can connect to 2.8 and higher servers, which can then connect through community to 2.8 and higher server.

    • The iNEWS 2.8 client software does not support the new features in iNEWS 3.x: combo boxes, check boxes, story links, URL links, calendar fields, duration fields.

    iNEWS Client The iNEWS client software is qualified and supported for use on Windows 7 (32-bit), Windows 7 64-bit Service Pack 1, Windows Vista (32-bit), Windows 2000 Professional (SP4), Windows 2000 Server (SP4), Windows XP Professional (SP2 or SP3) and Windows Server 2003 (SP1). This version of iNEWS is not officially supported for use on any other Windows operating system, including the pre-SP1 release of Windows 7 64-bit

  • Version 3.5.2 ReadMe

    8

    • The iNEWS 3.5.0 client software cannot connect to servers earlier than iNEWS 3.5.0.

    iNEWS Server The iNEWS Server is qualified and supported for use on 32-bit Red Hat Enterprise Linux 5.x.

    The iNEWS Server is qualified with VMWare Server v2.0 and later for Windows operating systems and is supported to run in a VMWare image. It must have networking set to BRIDGED to allow a unique IP address.

    Command The iNEWS Server is qualified and supported for use with Command 1.0.1 or later.

    ControlAir The iNEWS system is qualified and supported for use with ControlAir 1.6 or later. However, for the loading of single playlists with between 500 to 1000 stories, ControlAir v1.7.4.4 or later is required.

    MOS Gateway The iNEWS system is qualified and supported for use with MOS Gateway 3.0.2 or later.

    Console Multiplexer The iNEWS Server requires version 2.0 of the console multiplexer (MUX) software, which is on the iNEWS installation CD. The console multiplexer cannot currently display Unicode characters. A terminal emulator that supports Unicode characters can be used if Unicode support is required.

    Data Receiver The iNEWS system is qualified and supported for use with Data Receiver 1.8 or later. iNEWS 3.0 Server saves data as well-formed XML. Data Receiver SFCs must be updated to deliver well-formed XML. Also, field tags have changed from to .

    Instinct The iNEWS system is qualified and supported for use with Avid Instinct 1.1 and 1.6 or later. After the iNEWS client software is installed on an Instinct computer, manual registration of the Instinct installation’s COM control should be performed: Start > Run > regsvr32 “C:\Program Files\Avid\Avid iNEWS Instinct\iNewsCOMU.dll”.

    NewsCutter The iNEWS system is qualified and supported for use with NewsCutter NRCS Tool 6.1.5 or later. After the iNEWS client software is installed on a NewsCutter, manual registration of the NewsCutter installation’s COM control should be performed: Start > Run > regsvr32 “C:\Program Files\Avid\Avid NewsCutter\iNewsCOMU.dll”. If both NewsCutter and Instinct are on the machine, the Instinct COM control should be the one you register.

    Teleprompter The iNEWS system supports the following teleprompter software: WinPlus BDL Unicode version 6.8.7.3 and WinCue version 1.30 (build 674 or higher).

    Installation Notes and Issues

    FTS v4.0 • An FTS server installation supports up to 50 iNEWS systems.

  • Version 3.5.2 ReadMe

    9

    FTS Installation and Configuration Procedure The new installation and configuration procedure for FTS server version 4 is provided here. To install and configure FTS:

    1. Navigate to the FTS folder on the iNEWS installation DVD and click Setup.exe. The InstallShield Wizard starts and displays a Welcome dialog box.

    2. Click Next.

  • Version 3.5.2 ReadMe

    10

    The License Agreement dialog box appears.

    3. Read the Avid Software License Agreement, accept the terms, and click Next.

    The Destination Folder dialog box appears.

    4. (Optional) Click Change if you want to alter the default installation location. Otherwise, you can

    accept the default and click Next.

  • Version 3.5.2 ReadMe

    11

    5. Click Install when you are ready to begin the installation.

    When the InstallShield Wizard completes the installation successfully, the following dialog box appears.

    6. Select the Launch Avid FTS Configuration check box and click Finish.

  • Version 3.5.2 ReadMe

    12

    You are now ready to configure the system. The Fast Text Search configuration window appears. By default, no services are active.

    7. Click Configure to configure the FTS_1 services.

    The default configuration values will appear, as shown in the following illustration.

    8. Set the Active field to ACTIVE. 9. Set the System Name to the name of the iNEWS system to be associated with this service. 10. (Optional) Modify the ports and index path. 11. Click Save.

    A warning might appear to indicate if the Index Path Folder, indicated in the Index Path field, does not exist.

    12. Click Yes to create the folder at the configured path.

  • Version 3.5.2 ReadMe

    13

    The firewall exceptions, service configurations, and index path are created at this time.

    13. Click Back to return to the main configuration window and start the services. The configuration

    window will now display the active services with the configured system name. 14. Configure additional systems by selecting unused FTS_# entries from the list.

    Stopping and starting services should be performed from the Fast Text Search configuration window, using the Pause and Play buttons next to the relevant system name. Even though the services will appear in the Windows Services list, all stopping and starting should be performed from the FTS management UI.

    15. By default, logs and index bases are stored in C:\ProgramData\Avid\FTS in Windows Server 2008 R2 and in C:\Documents and Settings\All Users\Avid\FTS in Windows XP and 2003.

  • Version 3.5.2 ReadMe

    14

    If FTS needs to be uninstalled, all FTS entries should be set to “DISABLED” prior to the uninstall. Below is sample output from ftsdebug…

    NRCS-A$ ftsdebug index statistics Service name: ftsindex1

    Version: 4.0.0.33

    Process id: 2364

    Started: 12/20/11 07:30:47

    Debug value: 0

    Tuning: on

    Index Base: C:\ProgramData\Avid\FTS\NRCS

    iNEWS System: nrcs

    Port: 6100

    Current Index: 000

    Total Documents: 39736

    Requests Serviced: 95081

    000 File sizes (KB): 25702/25660 16376/1 15823 1

    Documents: 34076 Added: 39724 Removed: 5651 Replaced: 3 Purged: 0

    001 File sizes (KB): 592/543 572/1 1215 1

    Documents: 3174 Added: 3174 Removed: 11 Replaced: 11 Purged: 0

    003 File sizes (KB): 2540/2528 2547/1 1086 1

    Documents: 2486 Added: 2486 Removed: 2 Replaced: 2 Purged: 0

    010 File sizes (KB): 4/0 4/1 3 1

    Documents: 0 Added: 7 Removed: 7 Replaced: 0 Purged: 0

    An index rebuild is required when upgrading to FTS 4.

    To build the iNEWS index:

    Perform the following commands: ftsdebug index statistics — This confirms communication with the FTS Index

    service. ftsdebug search statistics — This confirms communication with the FTS Search

    service. list c fts — This displays the ftsseek and ftsindex device numbers (ftsseek# and

    ftsindex#). stop — This stops the FTS devices. dbpurge system.index 0 — This clears any unhandled index requests. dbpurge system.fts 0 — This clears any unhandled search requests. dbtraits . reindex > /dev/null & — This creates an index request for each

    indexed queue. The output is sent to /dev/null because of output volume.

    Note: Alternatively, more important wires and recent archives can be added to the index before adding the full database during the reindexing.

  • Version 3.5.2 ReadMe

    15

    start — This restarts the FTS devices.

    iNEWS Installer • The iNEWS Server installer no longer allows installation on 64-bit operating systems.

    FTS v3.1.x • Beginning in FTS 3.1, "ftsdebug index statistics" reports index base file size as well as truncated file size.

    The truncated size is a measurement of the "in use" size of the files. When stories or queues are removed from an index base, the file size does not decrease, but the truncated size does decrease. The truncated size can be used to more accurately determine the free space in the index base. A truncated size of 0 (zero) indicates that the file cannot be truncated. Queues should be moved to different index bases if the truncated size of any file in the index base approaches two gigabytes

    New End User License Agreement • Beginning with version 3.0, the iNEWS Server now displays an End User License Agreement (EULA) on

    the master at the first configure/startup after an installation or upgrade. The EULA is in English and formatted at 80 columns for the iNEWS Console Multiplexor. Non-English EULAs are available on the release DVD.

    • Beginning with version 2.8, an End User License Agreement is part of the iNEWS client software installation. This EULA must be accepted for installation to proceed. Administrators should generate a new silent install script before rolling out the client.

    Upgrade Notes and Issues This section contains information related to upgrading from previous versions of iNEWS.

    iNEWS v3.5.0 and FTS v4.0 • An upgrade to iNEWS 3.5 and FTS 4 requires a full rebuild of each index.

    iNEWS v3.4.1 • If upgrading from previous 3.x versions of iNEWS, there are likely invalid URLs stored in the database.

    Repair these URLs by running the command: dblines c .

    Note: The period (.) in the dblines c. command indicates the entire database.

    Some early versions of iNEWS 3 created NSML links in SYSTEM.KEYBOARDS. When the dblines command fixes those links, they become invalid keyboards. To repair the keyboards, remove the excess whitespace at the beginning and the middle of the keystroke line.

    iNEWS v3.4.0 • If a full dbrestore is not performed as part of the upgrade to iNEWS 3.4.0, the clearflagbyte utility

    should be run on the database. Usage is simply “clearflagbyte.” This utility touches all database nodes and initializes the new byte that holds the monitored attribute. This should be performed before running mapcheck.

    • iNEWS 3.4 and higher references all stories in SYSTEM.MAP when determining functionality. Excess stories should be moved to other queues or deleted. After removing excess stories from SYSTEM.MAP, the Mapcheck utility (mapcheck -f system.map) should be run to validate SYSTEM.MAP and set the monitored trait on all rundowns. For more information on the Mapcheck utility, see the “New Features” section of this ReadMe file.

  • Version 3.5.2 ReadMe

    16

    Upgrading iNEWS Server Software from Previous Versions • When upgrading iNEWS to 3.3.0 from any version, both dbgen p and dbgen m are required.

    The dbgen p command initializes projects, and the dbgen m command initializes mailboxes for project-related notifications.

    • When upgrading iNEWS from a version prior to 3.0, a dbrestore is required.

    The dbrestore command converts the database to the NSML 3.0 specification. This conversion formats existing stories into well-formed XML documents. Stories containing invalid data will not be restored, and will display StoryCreate errors during the dbrestore process. Errors include 'Anchor missing element,' 'AE missing attachment,' and 'Finish aelist bad M.' These errors should be rare, and the NSML2 version of the story are accessible by the 'remnant ID' reported to the console.

    Upgrading iNEWS Client Software from Previous Versions • Client upgrades have changed in version 3.0 to allow smoother minor and major upgrades in future. All

    iNEWS 2.6+ language installations are seen as the same product, so a major upgrade from 2.6+ to 3.0 will uninstall all 2.6+ languages that are installed. Beginning in version 3.0, different language installations will be considered different products of the same family, allowing upgrades to version 3.x of specific languages without uninstalling all other 3.0 languages.

    During transition periods, both 2.6+ and 3.0 clients may need to be on the same machine. The 3.0 installation uninstalls 2.6+, so if both are needed, simply re-install 2.x into a different directory after 3.0 has been installed.

    • When installing or upgrading iNEWS, you must have adequate user rights to install the client software.

    Note: During the install procedure, iNEWS client software version 3.0 will not provide an option to upgrade from any previous iNEWS version. iNEWS 2.6 and higher will automatically be uninstalled by the iNEWS 3.0 installation. iNEWS 2.1 and lower should be uninstalled manually before the iNEWS 3.0 installation.

    Upgrading iNEWS v2.8 Client Software to Future Versions Due to changes made for Windows Vista, upgrades on Windows XP, Windows Server 2003, and Windows Vista require escalation to administrator privileges. When iNEWS administrators have set their system to roll out upgrades, Windows Limited and Power users will receive the iNEWS auto-upgrade dialog when logging in to a server. Once the user accepts the option to download the new installer they will receive a Run As dialog box in which an administrator's name and password must be entered to complete download and installation. If the Current user in the Run As dialog box is an administrator, it is necessary to deselect the check box called: Protect my computer and data from unauthorized program activity for the upgrade to succeed. This is a Windows security restriction outside of iNEWS client control.

    Using the v2.8 download.exe program to download and upgrade to a new client version still requires a manual Run As… administrator. Limited users running download.exe without running the program as an administrator will not be able to complete installation.

    Upgrading iNEWS Server from Previous Versions • When moving to the Red Hat Enterprise Linux 5.0 version from Red Hat 3.0, a full OS and iNEWS install

    must be completed. There is no upgrade path from Red Hat 3.0 to Red Hat 5.0.

  • Version 3.5.2 ReadMe

    17

    Changes between 3.5.1 and 3.5.2

    Workstation • In previous versions of iNEWS 3, custom form fields in SYSTEM.FORMS had their data type changed to

    Editbox after user logged out then back in. This is fixed. • In previous versions of iNEWS 3, only editbox form fields would paste into new story form. This is fixed. • In previous versions of iNEWS 3, Cut Production Cue context menu option in production cue, and

    CTRL+ALT+SHIFT+X, were not working correctly, leaving production cue contents in place. This is fixed.

    • In previous versions of iNEWS 3, some updates within the same second were not shown as updated in observing sessions in refresh queues. This is now fixed.

    • In previous versions of iNEWS 3, duplicate field types could be found in field properties droplist when that field type was used for two different data types in two different stories. This now fixed.

    • In previous versions of iNEWS 3, legacy forms with zero length edit boxes placed underneath the field label would incorrectly show the editbox. Doing this corrupted the form view and covered up the label of the field below it. This is fixed.

    • In previous versions of iNEWS 3, new workspaces would open with all tree nodes collapsed. This is fixed. New workspace now opens with the root node of local server expanded.

    • In previous versions of iNEWS 3, the scroll bar within the VizRT plugin was not functioning. This is fixed.

    • In previous versions of iNEWS 3, script templates which included bold formatted text would be imported into story missing the bold formatting. This is fixed.

    • In previous versions of iNEWS 3, line breaks could be removed when copying and pasting inside the production cue panel. This is fixed.

    • In prior versions of iNEWS 3, web pages with script errors would pop up a script error to the iNEWS user because the web interface in iNEWS had script debugging enabled. This is fixed.

    • In previous versions of iNEWS 3, the user session was terminated when a user logged in directly to a form that contained a duration cell. This is fixed.

    • In previous versions of iNEWS 3, localized versions of iNEWS had issues loading exisiting search criteria for search queues. This is fixed.

    Server • In previous versions of iNEWS 3, stories that were txnetted to an email address using the mailto function

    would not show the proper Backtime or Cume-time. This is fixed.

    Changes between 3.5 and 3.5.1 • User InterfaceIn previous versions of iNEWS 3, iNEWS formatted text would lose its formatting when it

    was copied and pasted in to a new story, and sometimes within the same story, when Windows clipboard was used. This is fixed.

    Monitor Server • In previous versions of iNEWS 3, the monitor server would exit when it encountered a MOS item

    exceeding 32,667 Unicode characters (65,334 bytes). The behavior has been changed so that the utility program will no longer exit. Instead, the monitor server will return an error message for that production cue that is A_BADMOSSIZE, “MOS item too large”.

  • Version 3.5.2 ReadMe

    18

    Changes between 3.4.5 and 3.5

    FTS • The W_INDEXBASE token is removed from /site/dict/words; the location of the index base is now

    configured at the FTS server.

    • iNEWS Server to FTS Index service communication now reuses the active network socket instead of opening a new socket for each story. This change improves indexing speed by 10-to-15% and eliminates the “Add failed (25,99)” errors that appeared during large index rebuilds. Because of this change, the ftsdebug commands could take up to 10 seconds to respond when the FTS Index service is actively re-indexing a large queue.

    • Individual index bases are still limited to 2GB per file. Continue using the ftsindex dbtraits setting in iNEWS to define which index base each queue uses.

    • The ftsindex program now prints a diagnostic to the iNEWS log when the size of any index base file reaches the 2GB limit.

    • The shutdown command has been removed from both ftsdebug search and ftsdebug index. Stopping services is now handled on the FTS server.

    • The rotatelog command has been added to both ftsdebug search and ftsdebug index. This command is used to save the current log and start a new log when it is necessary to read the logs on the FTS server. Active logs are locked by the relevant service. The rotated log file name has a number (1, 2, 3, etc.) added between the service name and the process ID.

    • The limitlog command has been added to both ftsdebug search and ftsdebug index. This command changes the size at which the log file will rotate to a new file. The default size is 10MB. The command is provided a log size in megabytes: ftsdebug index limitlog 50.

    Server • In this version of iNEWS, dbvisit terminates at the end of the traversals if any critical errors were found.

    This termination prevents administrators from rebuilding the freelist when it would not be advisable.

    • In previous versions of iNEWS server, the monitor server (utility program) could report network communication failures during story reorders with multiple Command servers loaded in the same rundown. This is fixed.

    • In previous versions of iNEWS server, the rename utility could not be used to rename a path of the maximum length: 63 characters. This is fixed.

    • In prior versions of iNEWS unsafe characters in hyperlinks were not encoded correctly to the server. This is now fixed.

    • Current iNEWS servers and workstations use only a TCP socket for communication. Legacy workstations communicating with the current server continue to use TCP and UDP communication. This change was made in the iNEWS 3.3.0 release of server and client software.

    Workstation • In previous versions of iNEWS 3, at times iNEWS had troubles with the painting of some toolbars after

    user logged in. This is fixed.

    • In previous versions of iNEWS3, copy and pastes from Internet Explorer to iNEWS story would include extra characters for iNEWS installs onto Czech operating systems. This is fixed.

    • In previous versions of iNEWS 3, sometimes HTML text that was copied from a Web page and then pasted into an iNEWS story would have its CC formatted text change when the user left the story and went back to it. This is now fixed.

  • Version 3.5.2 ReadMe

    19

    • In previous versions of iNEWS 3, multiple cell copy and pastes from the queue view to Excel for combo boxes would paste the wrong value. This has been fixed.

    • In previous versions of the iNEWS client, links could be submitted to the server with formatting (bold, italic, underline) intact. This is fixed. Formatting is now removed from links before submission for saving.

    • In previous versions of iNEWS, the iNEWS client software could crash when receiving data from the Harris server after the NXMB Control plug-in had been closed. This is fixed.

    • In previous versions of iNEWS 3, mail queues which contained accented characters in the mail messages in an iNEWS 2.0 database would cause the client software to hang when mail was accessed after an upgrade to 3.x. This is fixed.

    • In previous versions of iNEWS3, if enough notifications were being processed and sent it would clog network activity and would terminate the client software. This is fixed.

    • In previous versions of iNEWS 3, Project pull down menu would terminate iNEWS when previous focus was on an opened plug-in. This is fixed.

    NSML • In previous versions of iNEWS 3, iNEWS would allow the paste of complex links which would break the

    NSML parser. Complex links are now pasted as plain text. This is fixed.

    • In previous versions of iNEWS 3, UNC paths were encoded as NSML links which was incorrect because UNC paths are not valid links. This is fixed.

    Mapcheck • Running the mapcheck utility on a system that has not been configured is no longer allowed. The user is

    informed that the system has not been configured.

    • In previous versions of iNEWS 3, mapcheck would give an Invalid CG Address Block error when there was a dash in the delta / buffer of SYSTEM.MAP. This is fixed.

    Miscellaneous

    • In previous versions of iNEWS 3, local database stories were timed using a wordlength of 1. This is fixed. Local stories are now timed using the wordlength and readrate configured on the server to which the client PC most recently connected. If no server connection has been made from the PC, the local stories are timed with a wordlength of 6 and a readrate of 180.

    • In previous versions of 3.4, standard users logging into and out of NewsWeb would occasionally terminate the NewsWeb application. This is fixed.

    Changes between 3.4.3 and 3.4.5

    Indexing • In previous versions of iNEWS server, ftsindex could stop scanning SYSTEM.INDEX during long squeeze

    operations triggered by adbserver. This is fixed.

  • Version 3.5.2 ReadMe

    20

    • FTS Indexbase can now be assigned from an iNEWS Workstation, using the Directory/Queue Properties dialog box. A drop-down option allowing integer selection from zero through 49 has been added to the Forms tab, adjacent to the Indexed check box. Prior to iNEWS 3.4.5, this value could only be assigned from the console via the dbtraits ftsindex command.

    Monitor Server • In previous versions of iNEWS server, the monitor server could assign duplicate CG addresses when

    addressing CGs that were added to stories already containing CGs. This is fixed.

    • In previous versions of iNEWS, the monitor server could corrupt production cues when writing changes triggered by mosItemReplace. This is fixed.

    Messaging • In iNEWS 2.6 and later, the top-line messaging Check Name (CTRL+W) function did not list partial

    matches when an exact match was found. This has been changed. Check Name now displays both exact matches and partial matches for the supplied user name.

    • In previous versions of iNEWS 3, the Up and Down Arrow buttons in the message bar did not disable when the user reached the top or bottom of the message list. This is fixed.

    MOS • In iNEWS 2.6 and later, the ReplaceTime MOS-MAP variable did not work correctly. This is fixed.

    If ReplaceTime=No, then MOS items dropped into the story form do not populate the mos-duration field. MOS items dropped into the story body do not include a RUNS time. If ReplaceTime=Yes, then MOS items dropped into the story form populate the mos-duration field. MOS items dropped into the story body include a RUNS time. Yes is the default value for ReplaceTime.

    Miscellaneous • In previous versions of iNEWS 3, pressing Escape while text was highlighted could result in the

    highlighted text being deleted. This is fixed.

    • In iNEWS 2.1, the Format toolbar was localized for non-English install sets. These localized toolbars were not used in iNEWS 2.6 and later. This is fixed. The Format toolbars that were localized in iNEWS 2.1 are now localized in the current iNEWS client software.

  • Version 3.5.2 ReadMe

    21

    • In previous versions of iNEWS 3, story save failures could occur if fields from different forms shared a Current Field Type but had different Data Types. For example, a "var-1" field that is an editbox in one form and a checkbox in another form could result in errors. This is fixed.

    • In previous versions of iNEWS server, serial device licenses could be incorrectly identified as mobile device licenses. This is fixed.

    • In previous versions of iNEWS 3.4, groups added to combobox definitions were not saved correctly. This is fixed.

    • In iNEWS 3.3 and later, navigating among queues when the story form was hidden could result in the client software terminating. This is fixed.

    • In some previous versions of iNEWS server, txnet would attempt to reuse a data port for a transfer after the prior transfer completed. This resulted in port reuse errors when transferring to Windows FTP servers. This is fixed. Now, txnet uses ports supplied by the host operating system when transferring data, as it did in iNEWS 2.8 and earlier.

    Changes between 3.4.2 and 3.4.3

    Monitor • In iNEWS 3.4.0 and higher, users not in the read group of SYSTEM.MAP could not load monitor for

    rundowns that were defined after the first story in SYSTEM.MAP. This is fixed. Users in the rundown's monitor group can now load monitor regardless of the definition location in SYSTEM.MAP.

    Server • In previous versions of iNEWS, the server would not tolerate links saved with formatting (bold, italic,

    underline) within the link. This is fixed. The formatting is now removed from the link when the server saves a story to the database.

    When the server repairs these links, the following informational diagnostics are printed in the iNEWS log:

    G2998: Removing from content

    G2998: Nested error, removing

    Workstation • In previous versions of iNEWS, a user could not re-submit a story from the workstation to the server after a

    story save failure. The body of the story would not be sent after the user repaired invalid elements. This is fixed. The story is resubmitted to the server if a user attempts to save after a story save failure.

    • In previous versions of iNEWS, presenter instructions or closed captioning combined with two or more formatting elements (bold, italic, underline) would send invalid NSML to the server, resulting in a story save failure. This is fixed. The client no longer submits invalid NSML, and the server will repair invalid NSML received from legacy clients.

    When the server repairs these errors, the following informational diagnostics are printed in the iNEWS log:

    G2996: Nested error, removing

    G2996: discarding nested

    G2996: discarding orphan

  • Version 3.5.2 ReadMe

    22

    Changes between 3.4.1 and 3.4.2

    Server • In previous versions of iNEWS, monitor could abort during periods of high message volume with verbose

    logging active. This is fixed.

    • In previous versions of iNEWS, the monitor program could corrupt production cues for invalid items when stories containing those items were edited. This corruption caused monitor to abort when the stories were next scanned. This is fixed. Monitor no longer corrupts items, and if it encounters corrupt items from previous versions a 'parse error' diagnostic will be printed to the console. The corrupt stories should be deleted when encountered. These stories will appear in 'dblines c' output with a message stating, "Invalid Nsml in AEset section."

    • In previous versions of iNEWS 3, cume-time and back-time were not exported as formatted time values through txnet or web forms. This is fixed.

    • Any unsupported or incorrect server strings listed in /site/config will generate "failed to invoke " diagnostics at startup. These lines should be removed from /site/config. Example: Print servers are no longer supported. If a server is upgraded and a printserver line is not removed from /site/config, startup will print a "failed to invoke 'printserver'" diagnostic. Remove the printserver reference.

    • In previous versions of iNEWS, top-line messages retrieved from remote servers could display an incorrect second character. This is fixed.

    User Interface • To select a server in the monitor dialog, users must click the selector button to the left of the row. Clicking

    in a Device or Status cell will not select the row.

    • In iNEWS 3.3 and later, searching for multiple words using the Find toolbar did not work correctly. The incorrect search criteria were submitted to the server. This is fixed.

    • In previous versions of iNEWS 3, the timing bar could show incorrect values or asterisks if the show crossed midnight during timing. This is fixed.

    • In previous versions of iNEWS 3, the workstation would not display search results if the M_BGSDONE token was set to multiple words in /site/dict/messages. This is fixed.

    • In previous versions of iNEWS 3, pressing the Escape key while text was highlighted deleted the highlighted text. This is fixed.

    • The Launch Link to Machine Control context option is now available for MOS items attached to the story form.

    • In iNEWS 3.3 and later, a user could not scroll to the bottom of the Directory panel when their workspace was set to the two-panel horizontal layout. This is fixed.

    • Values saved in calendar and duration fields are now converted to readable format when printing.

    • In previous versions of iNEWS 3, defining multiple CGs for a Command server could result in the first CG using an incorrect style string. This is fixed.

    • In previous versions of iNEWS, the client could save the incorrect group in Field Properties. This is fixed.

    • In iNEWS 3.3 and later, the Copy To and Move To options in the Edit menu did not work when focus was in the Directory panel. This is fixed.

    • In previous versions of iNEWS 3, typing Ctrl+End in a large non-refresh queue could crash the client. This is fixed.

  • Version 3.5.2 ReadMe

    23

    • In iNEWS 3.4.0, some users would crash while logging in if a prior 3.x client had not logged in with that username. This is fixed.

    • Floating toolbars are no longer remembered on successive launches. This 3.3.1 fix was removed.

    • In iNEWS 3.3 and later, Alt+keypad keystrokes could not be used to insert Unicode characters into the story body. This is fixed.

    • In previous versions of iNEWS, the client could terminate when receiving a 'logout' command from a remote server to which that client was connected. This is fixed.

    Projects • In previous versions of iNEWS, all project and facet nodes displayed the same queue form after the first

    node was accessed. This is fixed. The nodes now display the configured form.

    • In previous versions of iNEWS, clicking directly from the Project menu into an ActiveX plug-in could cause the iNEWS client to crash. This is fixed.

    • In iNEWS 3.3 and later, the Project tab in the story body was not visible in some zoomed layouts. This is fixed.

    Production Cues •

    • In previous versions of iNEWS 3, editing a story with an error-state production cue could cause the cue to save as normal text instead of machine instructions. This is fixed.

    • In previous versions of iNEWS, script template insertion could leave keyboard focus in the Instruction panel, even though visual focus was in the Story Text panel. This is fixed. Keyboard focus is now always in the Story Text panel after a script template is inserted into a story.

    Macros • In previous versions of iNEWS, changes to the item-channel field could cause the workstation application

    to freeze. This is fixed

    • In previous versions of iNEWS 3, keyboard and button macros executed while focus was in the message bar would fail to activate menu items. This is fixed.

    Changes between 3.4.0 and 3.4.1

    Server • In previous versions of iNEWS 3, the server allowed the iNEWS client to store invalid URLs. Stories with

    invalid URLs are problematic when accessed with the iNEWS Web Services API. Therefore, beginning with version 3.4.1, the iNEWS Server no longer allows storage of invalid URLs. When any client submits an invalid URL to the server, a server diagnostic is produced, and the server changes the link, show, and url NSML tags to spaces.

    The dblines command has also been enhanced to discover and clean invalid URLs. Customers upgrading from 3.x to 3.4.1 or greater should run dblines c . to repair any invalid URLs currently stored in the database.

    • In previous versions of iNEWS Server, rxnet would disconnect a client when receiving a UTF-8 upload that included a byte order mark. This is fixed.

    • In previous versions of iNEWS 3, any invalid date or duration fields caused a story to be rejected during dbrestore. This is changed. Invalid duration fields are now reformatted if the contents are MM:SS or MMM:SS. Any other invalid duration entries are simply discarded, and the story is restored with a blank

  • Version 3.5.2 ReadMe

    24

    duration value. If the create-date field is invalid, the internal story create date replaces the invalid field content. If the modify-date field is invalid, the internal story modify date replaces the invalid field content. Any other invalid date values are discarded.

    All instances of values being replaced or discarded include a dbrestore diagnostic similar to the following: "ARCHIVE.1998.TRAINING.RUNDOWN "cold open" stamp:804148398 storyid:1138877 field audio-time invalid[1:23] converting to [83]".

    • In iNEWS Server version 3.3, the dbdump utility could become stuck in a loop when encountering a corrupt story. This is fixed.

    • The dbrestore utility now renumbers mismatched anchored elements, allowing restoration of some stories that would have failed with “Anchor missing element” errors in previous versions of dbrestore. A diagnostic similar to the following appears in this situation: "SHOW.TRAINING.RUNDOWN "t: celts reax" stamp:1072494491 storyid:238123 changed to match ."

    • The –S option is removed from dblines in iNEWS server 3.3.0 and later.

    • The number of allowed concurrent locked blocks in a system is increased from 30 to 100.

    Monitor Server • In iNEWS 3.3.0 and 3.4.0, floating or deleting a story immediately after it was added to a monitor loaded

    rundown could cause the monitor server to hang. This is fixed.

    • In previous versions of iNEWS 3, floated, deleted, or moved BREAK lines in event list queues were only removed from a server's final device's event list. The server's final device is the last device listed in its SYSTEM.MAP entry. Non-final event lists were not updated properly. This is fixed. The monitor server (utility program) now handles break events properly in all event list queues.

    • In previous versions of iNEWS, placing more than 32766 characters in a story field would cause the monitor server to crash when the story was sent to playout. This is fixed. The monitor server now truncates fields to 255 characters. If more characters are needed, the FIELD_TEXT_LIMIT variable can be set in the monitor file: /site/env/monitor.. A value of 0 (zero) indicates no truncation, and monitor will once again abort if a field crosses the upper bound of 32766 Unicode characters.

    Note: The truncation only affects the message being sent. The field stored in the database is not truncated. Also, this limit only impacts story fields: title, page-number, etc. Story attachments are not affected.

    • In previous versions of iNEWS, monitor would abort if verbose logging was set and the monitor log reached two gigabytes. This is fixed. The monitor log now rolls over to a new file when the current file reaches one gigabyte.

    Changes between 3.3.1 and 3.4.0

    Installation • Previous versions of the iNEWS client installer would display an Internet Explorer 4 error if the computer

    had been upgraded to Internet Explorer 9. This is fixed.

    User Interface • In previous versions of iNEWS 3, decimal entry was not allowed in the Local Printing Line Spacing field.

    This is fixed.

    • In previous versions of iNEWS, the Story > Approve menu item worked to approve a story when the user was not in the write group of the endorse-by field. This is fixed.

  • Version 3.5.2 ReadMe

    25

    Server • In previous versions of iNEWS 3, some special characters in paths were not escaped properly when

    submitting Indexed searches. This is fixed.

    • In previous versions of iNEWS, diskcopy did not detect mirror failure during the copy. This is fixed; diskcopy will now terminate if the mirror fails.

    • In previous versions of iNEWS 3, NSML links were downgraded to NSML 2 for legacy compatibility. This downgrade consisted of removing show and link tags while keeping the url tags. This is changed. The downgrade for legacy clients now strips all tags from links so that the NSML2 client will only receive the address portion of the URL. For example, "http://www.avid.com" will become simply “http://www.avid.com.”

    • The optional 'choice' parameter is added to the SYSTEM.MAP syntax. Choice is the fifth column of the server line in SYSTEM.MAP...

    Choice can be any string. Lines with matching choice strings are mutually exclusive to monitor, allowing the user who turns monitor on to select the device control systems that will receive stories and events. When monitor is turned on, the user must select one server from each choice. After monitor is on, all stories relevant to that choice will be sent only to the selected server. To change the selection, the user must turn monitor off and back on.

    The following example has two Command server choices (cmdchoice), two no-choice MOS servers, three ControlAir CG choices (CG), and two ControlAir SS choices (SS).

    SHOW.10PM.RUNDOWN SHOW.10PM SHOW.10PM.COMPOSITE MONITOR D4

    wnasvr cmda1 cmda2 - cmdchoice

    video vid - A

    wnasvr cmdb1 cmdb2 - cmdchoice

    video vid - A

    mossvr xmos - event-mos

    mos xmos - storytext

    mossvr zmos - event-mos

    mos zmos -

    casvr cg-room3 - ctrlair CG

    cg cg - D:\CDI_2007/Templates - 100 199

    casvr cg-room1 - ctrlair CG

    cg cg - D:\CDI_2007/Templates - 100 699

    casvr cg-room2 - ctrlair CG

    cg cg - D:\CDI_2007/Templates - 100 199

    casvr ss-r1 - mcs-pb SS

    ss ss - D:\CDI_PB - 1 999

    casvr ss-r2 - mcs-pb SS

    ss ss - D:\CDI_PB - 1 999

    The following illustration shows the appearance of the Monitor dialog box when monitor server is off.

    http://www.avid.com./

  • Version 3.5.2 ReadMe

    26

    Selections are made by selecting the radio button next to the desired server. The user may only select one server from each choice grouping. The default selection is the first server of that choice in SYSTEM.MAP. (Notice that cg-room3 is the default CG choice selection.)

    The user can select one server from each choice, and then turn monitor on. If the user selects the b1 Command system, the room2 CG system, and the r1 SS system, this is how the monitor dialog will display before and after monitor is turned on.

  • Version 3.5.2 ReadMe

    27

    Before:

  • Version 3.5.2 ReadMe

    28

    After:

  • Version 3.5.2 ReadMe

    29

    To load individual devices:

    1. Click the selector button to the left of the device(s) you want to load.

  • Version 3.5.2 ReadMe

    30

    2. Click Load.

    • The 'monitored' trait is added to queue attributes and the Queue Properties dialog. Monitored indicates a rundown. A queue without the monitored attribute cannot be monitored. The -f flag of mapcheck sets the monitored attribute for all rundowns in the SYSTEM.MAP queue.

    The monitored attribute is displayed as a capital M in the twentieth column of the 'list d' output.

    NRCS-A$ list d show.training

    SRPlo-LIsUGQSXWFiTM sortfield purge dis mbox directory

    DS-P----I---QA------ TITLE P0 R1 - SHOW.10PM

    Q--P---------NX----- TITLE P18 R1 - SHOW.10PM.CG

    Q-RP----I---QA----T- TITLE P0 R1 - SHOW.10PM.MASTER

    Q--P----I---QA----TM TITLE P0 R1 503 SHOW.10PM.RUNDOWN

    Q--P---------NX----- TITLE P18 R1 - SHOW.10PM.VIDEO

    • The biolatency command is added. This utility can be used by iNEWS support and engineering to evaluate the status of the system's bioservers and mirror network.

    NRCS-A# help biolatency

  • Version 3.5.2 ReadMe

    31

    usage: biolatency [ []]

    Example:

    NRCS-A$ biolatency 5 5

    Block # allocate lock write all write one unlock free

    11679162 0.000057 0.000077 0.008994 0.000161 0.000040 0.000037

    11679176 0.000086 0.000049 0.000980 0.000152 0.000040 0.000037

    11679175 0.000079 0.000053 0.000945 0.000154 0.000040 0.005246

    11475447 0.000084 0.000053 0.000988 0.000151 0.000041 0.000036

    11503284 0.000068 0.000048 0.001018 0.000151 0.000040 0.000037

    average 0.000074 0.000056 0.002585 0.000153 0.000040 0.001078

    high 0.000086 0.000077 0.008994 0.000161 0.000041 0.005246

    low 0.000057 0.000048 0.000945 0.000151 0.000040 0.000036

    • The output of the unbusy command is changed. In previous versions, empty fields were displayed showing no data. This output was generally ignored and could cause relevant data to be missed. Empty fields are now suppressed from output. They can be shown using the -e option.

    NRCS-A# unbusy

    usage: unbusy [-i] [-v] [-e] |

    use "-i" to ignore the inverted attribute.

    use "-v" to show the entire story (implies -e.)

    use "-e" to show empty fields.

    MCS Dictionary • A_BADMAPCHOICE is added to /site/dict/mcs. The default value is "Bad Map line: choice server-

    type mismatch." This error message is received by the user who turns on the monitor server if a single 'choice' has multiple server types, such as mossvr, casvr, wnasvr.

    • A_ENDSVRS is added to /site/dict/mcs. The default value is "ENDSVRS." This string can be entered in SYSTEM.MAP to indicate the end of a rundown's entry. The string is not required, but it can improve readability when using the new 'choices' format.

    Txnet • In previous versions of iNEWS 3, txnet open responses that spanned multiple TCP packets would result in

    the connection failing. This is fixed.

    Changes between 3.3.0 and 3.3.1

    Projects • In iNEWS 3.3.0, non-English installations had two Help menu labels instead of a Project label and a Help

    label. This is fixed.

    • In iNEWS 3.3.0, Project and Facet Properties used the form list from a local database if one was present. This is fixed. The Properties dialogs now use the form list provided by the server to which the user is connected.

  • Version 3.5.2 ReadMe

    32

    • In iNEWS 3.3.0, dragging a story from an indexed queue to a project or facet would not cause the story's project tab to appear. This is fixed.

    • Shortcut keystrokes have been added for all project functions.

    Function Keystroke Combination

    New Project Ctrl+Alt+J

    New Facet Ctrl+Alt+F

    Properties Alt+Enter

    Delete Project Ctrl+Alt+D

    Subscribe to Project Ctrl+Alt+S

    Unsubscribe to Project Ctrl+Alt+U

    Show Expired Project Ctrl+Alt+E

    Community • In previous versions of iNEWS, community story moves or copies were rejected if the story contained a

    CART item. This is fixed.

    • iNEWS 3.3.0 could not accept stories copied via community from iNEWS versions 3.0 through 3.2.2. This is fixed.

    Messaging • The 'sendlong' utility is added. The sendlong utility is used to send messages greater than 71 characters in

    length. Clients that cannot accept messages over 71 characters will receive multiple messages. usage: sendlong The long message to be sent is read from standard input - CR LF stripped.

    FTS • In previous versions of iNEWS server, FTS searches would fail if the system name contained a hyphen:

    NRCS-SYS-A, for example. This is fixed.

    Seek • In iNEWS 3.3.0, form-level seek searches searched the story and the form. This is fixed. Selecting ‘Form’

    in Find All only searches the form.

    User Interface • Shortcut keystrokes are added for the following basic user functions:

    Function Keystroke Combination

    Play Low-Res Video Shift+Ctrl+D

    Insert Script Template Shift+Ctrl+I

    Copy Story Link to Clipboard Shift+Ctrl+K

    • In previous versions of iNEWS, toolbars that were floated at application close were docked at the next launch of the application. This is fixed. Floating toolbar placement is recalled.

  • Version 3.5.2 ReadMe

    33

    • In previous versions of iNEWS, the storyform area could display without accounting for the height of the horizontal scrollbar, resulting in the scrollbar covering fields. This is fixed.

    • In iNEWS 3.3.0, navigating to the Maintain tab of the Queue Properties dialog when a system mailbox was set would result in an error. This is fixed.

    • In previous versions of iNEWS, queue panel edits could be lost if not saved before a refresh notification was received. This is fixed. Active edits now recall both cursor position and edit status when other stories are updated in the queue.

    • The amount of directory view refreshing (flashing) has been reduced when double-clicking a queue or expanding a folder.

    • In this version of iNEWS, dbmanager support was added to the Copy From Template folder and Queue Properties feature.

    • In previous versions of iNEWS 3, some advanced user search options could cause the client to terminate. This is fixed.

    Macros • In previous versions of iNEWS, a macro that types text immediately after a {window }

    command could insert an unwanted underscore before the typed text. This is fixed.

    MOS Integration • In iNEWS 3.3.0, mos-title was not taken from objSlug if itemSlug was empty or not present. This behavior

    resulted in a blank mos-title field when MOS items were dragged to the story form and blank production cue descriptions when MOS items were placed in the story body. This is fixed.

    • In previous versions of iNEWS, a mosItemReplace that changed the mosSchema resulted in a monitor hang. This is fixed.

    Monitor Server • In iNEWS 3.3.0, the monitor server could become unresponsive if deletions or edits were made in

    composite lists. This is fixed. When the monitor server is unable to find an expected entry in a composite list an error will be posted to the iNEWS server log and the monitor server will continue to behave normally.

    • In previous versions of iNEWS 3, the monitor server could corrupt a story if the story contained fields that were split across database records. This is fixed.

    • Unread message sent from monitor to MON ON and MON LOAD users are now cleared at MON OFF. Some device-specific messages will still be present.

    • In previous versions of iNEWS, BREAK items in event lists and composite queues had a queue stamp of zero, making them irretrievable by FTP connections. This is fixed.

    Txnet • In previous versions of iNEWS, txnet could terminate when sending edit-locked stories. This is fixed.

    Web Access • In previous versions of Web Access, 12-character passwords were not considered valid. This is fixed.

    Tokens • Two /site/dict/queues tokens are added:

  • Version 3.5.2 ReadMe

    34

    • Q_CLIENT_MOBILE_IDS has a default of system.client.mobile-ids. This queue is reserved for integration with upcoming products.

    • Q_CLIENT_MOBILE_VERSIONS has a default of system.client.mobile-versions. This queue is reserved for integration with upcoming products.

    Changes between 3.2.x and 3.3.0

    Installation • In previous versions of iNEWS, the server installer allowed installation on 64-bit operating systems. This is

    fixed. The iNEWS Server installer no longer allows installation on 64-bit operating systems.

    • When installing iNEWS 3.3.0 Server, installers must run dbgen p to initialize projects

    • When installing iNEWS 3.3.0 Server, installers must run dbgen m to initialize the mailbox, which allows project-related notifications.

    User Interface • In previous versions of iNEWS 3, production cue text would not be displayed if cursor focus moved from

    the production cue directly to a non-iNEWS application. This is fixed. Production cue text continues to display regardless of cursor focus.

    • In previous versions of iNEWS, button and keyboard macros that move from the Queue panel to the story body and up to the story form could insert unwanted characters into the first field in the form. This is fixed.

    • In previous versions of iNEWS, editing of text pasted into the Queue panel was not allowed if the user had double-clicked or used F2 to enter input mode before pasting. This is fixed. Double-clicking followed by pasting will allow further editing of the pasted text.

    • In previous versions of iNEWS 3, the Directory panel flickered or flashed as focus moved. The issue existed in all operating systems, but was most apparent in Windows 7. This is fixed.

    • In previous versions of iNEWS, moving focus among search results, a mail workspace, and a directory workspace could result in an 'object not managed' error. This is fixed.

    Monitor Server • In previous versions of iNEWS, monitor could exit if Command disconnected immediately after initial

    connection. This is fixed. monitor now recognizes that Command is unavailable, and will go to error.

    • In previous versions of iNEWS, monitor could exit with some item-channel changes in MOS-enabled rundowns. This is fixed.

    Server • In previous versions of iNEWS 3, dblines reported script and margin errors every time it was run. This

    resulted in large diagnostic output that was difficult to parse. These messages have been removed.

    • In previous versions of iNEWS, running the remove console command against a non-empty queue would result in that queue being purge locked. This is fixed.

    • Beginning with this version of iNEWS, dbvisit and dblines now display a diagnostic for every REFRESH, UPDATE, or SORTED queue that contains more than 1000 stories.

    • In previous versions of iNEWS, 'finit -' would fail if the database partition was larger than 17GB. This is fixed. 'finit -' now initializes the database to the maximum size allowed by the server or the partition. If the partition is larger than the the maximum database size, finit will initialize up to the maximum allowed size. Space remaining on the partition will not be used.

  • Version 3.5.2 ReadMe

    35

    NSML • iNEWS now uses NSML 3.1. This version of NSML adds the projects section and the body-level tag

    that will be used by future journalist editor applications. , when encountered by the iNEWS client, will display a "Segment B