Guide January 2000 Version 2.3 CMSS System Management Guide, version 2.3 Date of Issue: January 2000 Copyright: 2002 by Commonwealth Bureau of Meteorology All rights reserved. No part of this doument may be reprodued by any means or in any form without the e!press permission of the Commonwealth Bureau of Meteorology. "his doumentation was prepared for Commonwealth Bureau of Meteorology by# $ordware %ty &td '()2' $hitehorse *oad Nunawading +,C )')' /var/www/apps/conversion/tmp/scratch_1/228579685.doc Introduction Table of Contents Introduction...........................................................12 asic Concepts.......................................................13 Message -withing.................................................................................................................. ') Addressing -heme................................................................................................................. ') Messages or .iles.................................................................................................................... '/ 0upliate Message 1limination...............................................................................................'/ 0upliate *eport 1limination..................................................................................................'/ Data !"o#...............................................................1$ %rocess Contro"......................................................1& -tarting CM--........................................................................................................................ '2 Starting CMSS from GUI:..............................................................................................18 Starting CMSS from command line:...............................................................................18 -topping CM--...................................................................................................................... '2 Stopping CMSS from GUI:.............................................................................................18 Stopping CMSS from the command line: .......................................................................18 Monitoring(*estarting %roesses.............................................................................................'3 Restarting processes.......................................................................................................19 Stopping an individual process.......................................................................................19 e! processes.................................................................................................................. 19 -tarting the .a! -ystem..........................................................................................................20 -topping the .a! -ystem.........................................................................................................20 System Structure...................................................21 0iretory -truture................................................................................................................. 2' e! files.......................................................................................................................... "1 Creating files.................................................................................................................. "" 4n5line file e!pansion..............................................................................................................22 System Configuration...........................................2' -ystem %arameters.................................................................................................................. 2/ 67, Configuration.................................................................................................................. 28 CMSS Sstem Mana!ement "uide# version 2.$ Page 3 %a&'e o( Contents Circuit Contro"......................................................2( Adding a New Ciruit..............................................................................................................29 Adding an ,nput Ciruit...........................................................................................................22 #$ample 1: %dding an input &M' (C)*I) soc+et connection.......................................,- #$ample ": %dding an input .() circuit........................................................................,1 #$ample ,: %dding a &M' /atched .() messages input circuit..................................," #$ample 0: %dding an 1."2 )3C input line....................................................................,, Adding an 4utput Ciruit........................................................................................................)8 #$ample 1: %dding an output &M' (C)*I) soc+et connection.....................................,4 #$ample ": %dding an output &M'5standard .() circuit ...........................................,8 #$ample ,: %dding a non5&M' output .() circuit .....................................................,9 #$ample 0: %dding an output 1."2 )3C.........................................................................,9 Changing an 1!isting Ciruit................................................................................................../' '. update the re:uired database table by using the 67,#.........................................................../' a. -elet C,*C7," C4N"*4& from the CM-- 67, ............................................................/' b. 7se the left mouse button to selet the re:uired iruit........................................................./' . -elet C&4-1...................................................................................................................... /' d. -elet 4%1N........................................................................................................................ /' *emoving an 1!isting Ciruit................................................................................................../' 15mail iruits......................................................................................................................... /2 )roposed &M' e5mail standard....................................................................................0" 6on5&M' format e5mail ...............................................................................................0" #5mail securit! considerations:......................................................................................0, CMSS #5mail input circuit..............................................................................................0, CMSS #5mail output circuit............................................................................................00 &ines;out "able...................................................................................................................... /< &ines;in table 67,.................................................................................................................. /2 S#itching )a*"es...................................................$1 6"- Bulletin -withing "able =buldesr>..................................................................................8' .ile -withing =stndesrf and filedes>......................................................................................8) 6roup Address "able =grpaddrs(grpdes>................................................................................8/ Client Address "able...............................................................................................................8/ System !unctions..................................................$+ Automati Job 1!eution =?C"N&,-">..................................................................................8< 1C(66#1( ta/le fields..................................................................................................27 u""etin %reparation ............................................$& Page 4 CMSS Sstem Mana!ement "uide# version 1.) Introduction ,ntrodution to the Automati Bulletin %reparation -ystem.....................................................82 (erminolog!.................................................................................................................... 28 Categories of /ulletins....................................................................................................28 Message recognition and /ulletin preparation...............................................................29 "he 4rale .orms 67,............................................................................................................83 .unctions of the 'racle forms GUI................................................................................7- 'perating modes.............................................................................................................7- 8utton palette.................................................................................................................. 71 8loc+s............................................................................................................................. 7, Bulletin .untions................................................................................................................... </ .unction 1 9 #nter search data.....................................................................................70 .unction " 9 %dd a ne: /ulletin....................................................................................72 .unction , 9 Modif! and e$isting /ulletin.....................................................................72 $M4 Catalogue..................................................................................................................... <8 4rale 0atabase "ables..........................................................................................................<< stndsr"............................................................................................................................ 74 /ulnd$"........................................................................................................................... 74 /ulnd$,........................................................................................................................... 74 /ulnd$2........................................................................................................................... 74 tafstns.............................................................................................................................. 78 e! .ields in the ta/les...................................................................................................78 System Monitoring !unctions..............................+, $athdog %roess................................................................................................................... <3 -ystem -tatus.......................................................................................................................... 90 &ine monitor............................................................................................................................ 9' Data*ase )a*"es.....................................................(2 Management !aci"ities..........................................(' &ine5loading and delay -tatistis.............................................................................................9/ *eal5"ime Monitoring of 4bservations...................................................................................98 -urvey %rograms =$M4 -urvey>...........................................................................................99 )rocedure to produce &M' Surve!:..............................................................................44 )rocedure to o/tain R8S6 files......................................................................................44 )rocedure to send results to &M'.................................................................................48 -e.uest/-epeat !aci"ity........................................&0 -ending *e:uests for missing data..........................................................................................20 *esponding to *e:uests for missing data................................................................................20 CMSS Sstem Mana!ement "uide# version 2.$ Page 5 %a&'e o( Contents Misce""aneous.........................................................&1 %riority -heme....................................................................................................................... 2' @andling $M4 "/ Charts......................................................................................................2' ,gnoring -eleted Messages.....................................................................................................22 -ervie Messages.................................................................................................................... 22 %rinting .ailities.................................................................................................................... 22 Using the CMSS GUI to print.........................................................................................8, Setting up a destination circuit*address for a printer.....................................................8, 7se of shared memory.............................................................................................................2/ 1ey %rocesses and !i"es........................................&$ CM-- %roesses..................................................................................................................... 28 CM-- %roess 4ptions...........................................................................................................2< Message related files............................................................................................................... 29 Circular files................................................................................................................... 84 Data*ase Interface................................................&, 0eoder %roesses................................................................................................................... 23 2anguage Support.................................................,0 "ranslation Method................................................................................................................. 30 "ranslation .ile 0iretories.....................................................................................................3' Changing a language translation..............................................................................................3' &anguage translation restritions.............................................................................................3' Message 3rchive....................................................,2 Insta""ation %rocedure...........................................,3 !a4 De"ivery...........................................................,( ,ntrodution............................................................................................................................. 39 .a$ data flo:.................................................................................................................. 98 ,nstalling @ylafa!.................................................................................................................... 32 e. Add the entry manually.........................................................................................................33 f. 1nsure the syslog file e!ists and is readable =touh as root and maAe world readable>..........33 g. 6et the syslog daemon =syslogd> to re5read the (et(syslog.onf file =Aill 5@7% BsyslogC>.....33 Page 6 CMSS Sstem Mana!ement "uide# version 1.) Introduction Customising @ylafa!.............................................................................................................'00 Managing the @ylafa! -ystem...............................................................................................'00 ;!lafa$ daemons*processes..........................................................................................1-- Monitoring ;!lafa$......................................................................................................1-1 ;!lafa$ client processes...............................................................................................1-" @ylafa! -tartup -ript..........................................................................................................'02 Configuration .iles................................................................................................................'0) &ogs(0iagnostis................................................................................................................... '0/ -tatistis =Aounting>..........................................................................................................'08 7se of &AN "erminal -ervers...............................................................................................'08 Adding and 0eleting .a! Modems........................................................................................'0< %dding a modem...........................................................................................................1-7 h. &ogin as root...................................................................................................................... '0< i. mAfifo .,.4.fa!nn..............................................................................................................'0< D. hown fa!#fa! .,.4.fa!nn..................................................................................................'0< A. hmod uogErw .,.4.fa!nn................................................................................................'0< l. &og in as root...................................................................................................................... '0< m. fa!ptydr FCM-- fa!nn terminal5server port 5 G.............................................................'0< n. H fa!ptydr FCM-- fa!nn terminal5server port 5 G...........................................................'09 o. H nohup fa!getty fa!nn I (dev(null G.................................................................................'09 <eleting a fa$ modem...................................................................................................1-4 p. ,ssues a @ylafa! ommand fa!:uit fa!nn to stop the fa!getty...........................................'09 :. "erminates the fa!ptydr......................................................................................................'09 @ylafa! Cleanup -ripts =C*4N>.........................................................................................'09 IM 5.2$ Support..............................................10, Monitoring ?.28.................................................................................................................... '03 BaAing 7p and *estoring the ?.28 Configuration................................................................'03 Restarting the I8M 1."2 ..............................................................................................11- 1."2 and failover =;%CM)>.........................................................................................11- %roblem5solving.................................................................................................................... ''0 6% 5.2$ Support.................................................112 Monitoring ?.28.................................................................................................................... ''2 -topping ?.28....................................................................................................................... ''2 85port %CC Card .........................................................................................................11" "5port 1."2 Card..........................................................................................................11" CMSS Sstem Mana!ement "uide# version 2.$ Page 7 %a&'e o( Contents -tarting ?.28......................................................................................................................... ''2 85port %CC Card .........................................................................................................11" "5port 1."2 Card..........................................................................................................11" ACC Card Configuration......................................................................................................'') 25port Card Configuration.....................................................................................................'') G"ossary................................................................11' $M4 aronyms.................................................................................................................... ''/ 4ther aronyms..................................................................................................................... ''/ 6"- "erms........................................................................................................................... ''/ Computing "erms.................................................................................................................. ''8 CM-- "erms........................................................................................................................ ''8 CM-- 0iretories(.iles.........................................................................................................''< CM-- %roesses................................................................................................................... ''9 4rale "ables........................................................................................................................ ''2 2ist of !igures and )a*"es !igure 1: CMSS....................................................12 !igure 2: CMSS Data !"o#.................................1+ !igure 3: CMSS Data !"o# 7detai"8....................1( !igure ': on9"ine fi"e e4pansion G:I...................23 !igure $: System %arameters G:I......................2$ !igure +: G:I configuration...............................2$ !igure (: ;rac"e Input 2ines G:I......................2, !igure &: ;rac"e ;utput 2ines G:I....................3+ !igure ,: ;rac"e forms G:I................................$, Page 8 CMSS Sstem Mana!ement "uide# version 1.) Introduction !igure 10: ;rac"e *utton pa"ette........................+1 !igure 11: <M; Cata"ogue.................................++ !igure 12: CMSS status G:I...............................(0 !igure 13: CMSS "ine9"oading statistics..............($ !igure 1': -ea"9)ime o*servation monitoring G:I.........................................................................(+ !igure 1$: CMSS fa4 system...............................,( )a*"e 1: Main continuous"y running non "ine drivers processes....................................................1, )a*"e 2: =CMSS directory > ?ey fi"es................21 )a*"e 3: "ines@out ta*"e.........................................'+ )a*"e ': "ines@in ta*"e:..........................................'& )a*"e $: "ines@in ta*"e 7-e.uest/-epeat fie"ds8. ', )a*"e +: *u"desr fie"ds 7co"umns8.........................$1 )a*"e (: *u"desr fie"d definitions.........................$1 )a*"e &: A4amp"e SB2 resu"ts............................$2 )a*"e ,: !i"e S#itching 7stndesrf8........................$3 )a*"e 10: !i"e S#itching 7fi"edesc8.......................$3 )a*"e 11: grpaddrs fie"ds 7co"umns8....................$' CMSS Sstem Mana!ement "uide# version 2.$ Page 9 %a&'e o( Contents )a*"e 12: Group Description ta*"e......................$' )a*"e 13: 5C)CCA5) ta*"e fie"ds......................$+ )a*"e 1': ;rac"e *utton functions......................+2 )a*"e 1$: "oc? 1 fie"ds........................................+3 )a*"e 1+: "oc? 2 fie"ds........................................+3 )a*"e 1(: "oc? 3 fie"ds........................................+' )a*"e 1&: u""etin ta*"e ?ey fie"ds......................+& )a*"e 1,: time@out structure................................(1 )a*"e 20: cmop ;rac"e ta*"es..............................(2 )a*"e 21: ;ther important ta*"es used *y CMSS .................................................................................(3 )a*"e 22: %rinter definition ta*"e.......................&3 )a*"e 23: 1ey CMSS processes..........................&$ )a*"e 2': Message re"ated fi"es...........................&( )a*"e 2$: Circu"ar fi"es........................................&( )a*"e 2+: !i"e re9creation commands.................&& )a*"e 2(: Standard decoder processes...............&, )a*"e 2&: 6y"afa4 insta""ation directories...........,, )a*"e 2,: config fi"es main options....................103 Page 10 CMSS Sstem Mana!ement "uide# version 1.) Introduction )a*"e 30: Config fi"e avai"a*"e options.............10' CMSS Sstem Mana!ement "uide# version 2.$ Page 11 Circuit Contro' Introduction !igure 1: CMSS CM-- stands for Computer Message Swithing System. ,ts primary funtions are# -end and reeive meteorologial messages and files =for e!ampleJ harts>. %rodue bulletins =or olletives> of meteorologial reports in aordane with $M4(6"- rules. ,nterfae to message 0eoders to allow data to be deodedJ plottedJ fed into numerial models et Allow loal messages to be manually entered %rovide a omprehensive 6raphial 7ser ,nterfae =67,> to allow the operators to be alerted about signifiant events =for e!ampleJ oding errors in msgs>J ontrol the ommuniations lines et Page 12 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' Basic Concepts Message Switching 1ah inoming message is heAed to determine where it is to be sent. "ypially messages are swithed based on# ,nternational @eader# ""AA,, and CCCC .ile Name -tation Number 0estination addresses defined in the inoming message =eg A."N addresses> "he following Aey database tables ontrol the swithing of messages and determine where an inoming message is to be sent# 6"- Bulletin -withing =*u"desr8 .ile -withing =stndesrf and fi"edesc8 -tation swithing 7stndesr8 6roup Address 7grpaddrs8 ,nput Conversion "able =cmssin> Client Address "able =c"ient@addr@t*"> !!ressing Sche"e CM-- uses a nine5harater addressing sheme to determine where to send inoming messages. "hat isJ assoiated with every outgoing onnetion are one or more addresses that must be ) to 3 haraters in length. "here are some restritions and onventions with the first harater of the address. "hese are# A K A."N address. ,f an address is nine haraters long and starts with an LAM then it is assumed to be an A."N address and is sent down the default A."N output line =with the leading LAM removed> 6 K 6roup address. ? K By onvention =but not mandatory> fa! addresses start with L?M. ,f an address starts with an L?M and is followed by / or more digits then the digits are assumed to be the atual fa! number. CMSS Sstem Mana!ement "uide# version 2.$ Page 13 Circuit Contro' N K dummy address Cote: -ome addressesJ liAe e5mail addressesJ do not fit into 3 haraters. .or these addresses the input conversion ta*"e and the output C"ient 3ddress ta*"e are used to onvert between 3 haraters CM-- addresses and foreign addresses. Cote: .rom the CM-- 67, it is possible to send to e5mail addresses by using the atual e5mail address rather than using a 3 harater address Messages or #i$es "wo forms of data are proessed in CM--# MessagesJ whih are up to '8J000 haraters long and typially in A-C,, !i"esJ whih are normally large graphi images O for e!ampleJ %ostsriptJ 6ifJ "/ hartsJ however they an inlude A-C,, te!t files. "he differenes between how CM-- handles these data types are# Most messages an be edited in the CM-- 67,J but files annot be edited Messages are stored in large irular files and old messages are overwritten over time =typially 2/ to 92 hours>. .iles are stored individually in a produts diretory. 4ld files are removed by a proess referred to as cmfi"ec"ean. "he time before old files are deleted may be individually set =good for huge files> or a default time used =normally 2/ hours>. %u&$icate Message '$i"ination 0upliate inoming messages are deteted and not sent to ustomers or to the reognition and deoding proesses. A dupliate message an be identified in the CM-- 67, when the DD D:%2IC3)A IGC;-AD DD label is displayed. %u&$icate (e&ort '$i"ination 0upliate reports are also deteted and not plaed in $M4(6"- bulletins or sent to the 0eoder. A dupliate report an be identified in the CM-- 67, when the DD D:%2IC3)A IGC;-AD DD label is displayed Page 14 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' Data Flow ,n CM-- messages and details about messages are stored in large circu"ar files. "hese irular files are of a fi!ed siPe so the storage apaity in CM-- is based on the number of messages and not on time =for e!ample CM-- ould be onfigured to hold '00J000 inoming messages but not to hold 2/ hours of data>. "he reason for this is beause we do not want to fill the omputer disA=s> if there is a sudden inrease in the number of messages reeived. Messages are passed between various CM-- proesses via these irular files whih an be written to by multiple proesses but typially read by only one proess. "he basi CM-- data flow is as follows# '. ,noming messages are writtenJ by the &ine 0riversJ to a large irular file alled msgint4t. 2. "he msgana" proess reads the new messages from msgint!t and does the following# +alidate the message header and trailer. -ends re:uests for missing messages based on breaAs in se:uene numbers CheAs for dupliate messages Construts a EdirectoryF reord =or summary reord> about the message ontaining information suh as time of reeiptJ ""AA,,J CCCC et. ). .inally msgana" writes the diretory reord to a irular file alled MSGIC =short for Message ,n> /. "he message reognition proess recogn reads new messages from M-6,N and does the following# .inds eah report within a message CheAs if the report is syntatially orret and if not then produes an alarm message. .inds the station number and identifies the report type CheAs if the report is re:uired for international bulletin prodution. .or eah report it finds recogn writes a diretory reord to the *1%4*"- file that inludes details suh as the station number and report type. 8. After reognitionJ reognJ writes diretory reords for eah reportJ and for the original messageJ to another irular file alled s#itchdir <. Another proessJ msgs#tchJ read the swithdir file and determines where eah report or message is to be swithed. Msgswth :ueues messages to the re:uired output iruits by adding them to the ;:)B 7output .ueue8 file. CMSS Sstem Mana!ement "uide# version 2.$ Page 15 Circuit Contro' "he swithing re:uirements are determined from a series of Data*ase S#itching )a*"es. "here is one table for swithing on $M4 ""AA,,J CCCC and another for swithing on station number et. Normally all reports are automatially :ueued to the harater deoder. 9. Assoiated with every output :ueue are two proesses Q a message preparation proess =msgprep8 and a &ine 0river. 2. $hen a new message is plaed on an output :ueue =47"R file> it is immediately read by the msgprep for that output line. Msgprep adds the re:uired output header and trailer to the message and passes it to the output 2ine Driver. 3. 2ine Drivers send messages to the various destinations. "here are different line driver proesses for eah different protool eg ?.28J "C%(,% soAetsJ ."% !igure 2: CMSS Data !"o# Page 16 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' !igure 3: CMSS Data !"o# 7detai"8 CMSS Sstem Mana!ement "uide# version 2.$ Page 17 Circuit Contro' Process Control Starting )MSS "he Computer Message -withing -ystem =CM--> is started from the sript rc.cmop in the $CMSS diretory from the owner aount =cmop>. FCM-- is an important environment variable that defines the CM-- home diretory. CM-- is started automatially and there should be no need to stop or start it manually. "here are however ommand line and 67, proedures to do this in an emergeny. Starting CMSS from GUI "he CM-- owner aount =mop> has aess to a speial 3dmin pulldown menu on the CM-- 67,. ,n this 3dmin pulldown there is an option to -AS)3-) CMSS. $hen pressed it stops CM-- if it is running and then restarts it. Starting CMSS from command line '. &og in as cmop 2. 1nter cd =CMSS ). 1nter ./rc.cmop CMSS must be started from the cmop aount. No other user an start CM--. Cote: 1 CM-- will not start orretly unless the 4rale *0BM- is running =refer to the S!stem Management .unctions Guide>. Cote: 2 4nly one opy of CM-- should be run at any time. Be areful to ensure that no CM-- proess is running when you e!eute rc.cmop. Sto&&ing )MSS Stopping CMSS from GUI Sou may stop CM-- via the S);% CMSS option in the 3dmin pulldown. Stopping CMSS from t!e command line '. &og in as cmop 2. 1nter ommand G stopcmss Cote: "he CM-- 67, is not terminated by the stopcmss ommand. Page 18 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' Monitoring*(estarting Processes CM-- inludes monitoring proesses that periodially heA that all proesses are running and that Aey files are being updated. "hese proesses are# #atchdogJ whih monitors proesses and Aey files cm"nmon =&ine Monitor>J whih monitors inoming and outgoing lines. "estarting processes "he $athdog automatially restarts failed proesses. By default it restarts a failed proess up to five =8> times an hour at two =2> minute intervals. ,f a proess fails on the same message repeatedly then the wathdog is often able to fore the failed proess to sAip that message before resuming. ,f you want to manually restart a proess then do it as follows# '. &ogin as cmop 2. 1nter ommand info 444444 =where !!!!! is the proess name>. 4r 1nter ommand info rrrcc =where rrr is the line name>. Cote: "he info display ontains the startup ommand for the re:uired proess. "his ommand is issued from the ommand line. Stopping an indi#idual process "o stop an individual non line5driver proess O for e!ampleJ when a new version of a proess is made availableJ issue the following ommand# c"osedo#n 444444 =where !!!!!! is the proess name> Cote: "he losedown ommand tells the wathdog to delay '8 minutes before automatially restarting the stopped proess $ey processes "he main non line5driver proesses that run ontinuously are# )a*"e 1: Main continuous"y running non "ine drivers processes Process Description Decoder Decodes standard World Meteorological Organisation (WMO) reports Msganal Checks incoming messages for header/trailer errors CMSS Sstem Mana!ement "uide# version 2.$ Page 19 Circuit Contro' Process Description Recogn Performs message recognition msgswtch Message switching process xctnmain Controls execution list (starts processes at predefined times) !ur"e# !a"es raw information for WMO sur"e#s cmre$uest %andles re$uests for missing data cmfileclean Deletes old files DataRe$uest Re$uests missing o&ser"ations and messages' DataMon Performs realtime monitoring of o&ser"ations and messages Cm"iew Creates "iewa&le %bm file copies for specified incoming files ( for example) postscript files watchdog Monitors all other processes Starting the #a+ Syste" "he .a! system =@ylafa!> is started and stopped independently of CM-- for the following reasons# ,t must be started as root and not cmop ,t is a separate =) rd party> produt. Carry out the following proedure to start the .a! system# '. &ogin as root 2. 1nter cd Hcmop/fa4 ). 1nter ./rc.fa4 Sto&&ing the #a+ Syste" Carry out the following proedure to stop the .a! system# '. &ogin as root. 2. 1nter cd Hcmop/fa4 ). 1nter ./stop.fa4 Page 20 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' System Structure %irectory Structure Tey files are loated in the $CMSS diretory and the following sub5diretories# )a*"e 2: =CMSS directory > ?ey fi"es Directory Description *CM!!/restart !#stem details for restart purposes *CM!!/pids +ist of processes and their Process ,Ds (P,Ds) *CM!!/faxout Details of messages/files passed to the -ax s#stem (%#lafax) *CM!!/screen$ -iles that need to &e made "iewa&le for the CM!! ./, *CM!!/"iews 0iewa&le files for the CM!! ./, *CM!!/products Master cop# of incoming data files $ey files "he Aey data files in the FCM-- diretory are# Message Directory Files "hese files are all fi!ed siPe and ontain a ertain number of messages. msgindir (dat/ptr) msgotdir (dat/ptr) recogdir (dat/ptr) switchdir (dat/ptr) service (dat/ptr) request (dat/ptr) Log Files "hese files are all fi!ed siPe and ontain a ertain number of reords. log (dat/ptr) logd (dat/ptr) journal (dat/ptr) journald (dat/ptr) alarm (dat/ptr) alarmd (dat/ptr) Miscellaneous Files msgintxt (dat/ptr) CMSS Sstem Mana!ement "uide# version 2.$ Page 21 Circuit Contro' addrdir (dat/ptr) cmss.params cmssfile.shm Creating files '. 1nter the ommand createdir to reate Message 0iretory files. 2. 1nter the ommand cre&"ogc to reate &og files. ). 1nter the ommand ne#te4t to reate msgint!t files. Note# Sou should never need to use these ommands after initial installation. CM-- ontains a 67, based tool to allow all the siPe of Aey files to be inreased online. ,n-$ine .i$e e+&ansion All the Aey CM-- files may be e!panded without shutting down CM--. As for other administration funtions this is done via the 3dmin pulldown menu on the CM-- 67,. '. AdDust the siPes of the files as re:uired. 0o this by using the arrows or by entering new values in the te!t fields. 2. %ress U:%D3)AG ). @aving done this a window will be displayed showing you the names of the files whose siPes you have hanged and the additional disA spae re:uired. /. "his faility only allows you to use up to 20V of the disA apaity. ,f you try to e!eed this limit then an error message will be displayed. 8. ,f you wish to proeed then press U;1G. 4therwise press UC3CCA2G. <. $hen you press U4TI the system will start e!panding the files. "his proess ould taAe up to 8 minutes. Note# ,t is important that the )e4t !i"e ontains more hours of data than M-6,NJ M-647"J *1%4*"- et. "his is beause these file point to the raw messages stored in the "e!t .ile Page 22 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' Note# "his faility only allows you to inrease the siPe of files. Sou may N4" use this faility to redue the siPe of files. !igure ': on9"ine fi"e e4pansion G:I CMSS Sstem Mana!ement "uide# version 2.$ Page 23 Circuit Contro' System Configuration Syste" Para"eters "he CM-- system5wide onfiguration parameters are held in the file cmss.params, whih is loated in the $CMSS diretory. All these system wide parameters may be viewed and hanged from the CM-- 67,. As user BmopC use the System %arameters menu in the CM-- 67, 3dmin pulldown menu to view or hange these parameters. Note '# .or most CM-- system parameters it is neessary to restart CM-- for the hange to taAe effet. Note 2# Always hange these parameters via the 67,. 0o C;) modify the raw file. "he most ommonly hanged parameters are# 6"- CCCC =ie the 6"- loation indiator for this entre> A."N address =A."N address of this entre> 6"- Bulletin %rodution =this defines whih international format messages and whih report types are heAed for bulletin prodution. 7sed by entres that use the $M4 format nationally> 15mail onfiguration Page 24 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' !igure $: System %arameters G:I /01 )on.iguration "he systems administrator an maAe some hanges to the CM-- 6raphial 7ser ,nterfae =67,> by hoosing the G:I %arameters menu in the 3dmin pulldown menu. ,ndividual users may also hange the CM-- 67, for their individual aount by hoosing the G:I %arameters 7user8 menu in the Misc pulldown menu. %erhaps the most useful parameter that an be hanged is the 2anguage. 1ah user may hoose their preferred language for the 67,. !igure +: G:I configuration CMSS Sstem Mana!ement "uide# version 2.$ Page 25 Circuit Contro'
Page 26 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' Circuit Control !!ing a 2ew )ircuit Adding a new line to CM-- is simply a matter of inserting the re:uired information into the database. "here are separate database tables =lines;in and lines;out> for input and output iruits. ,f a iruit is both input and output =send and reeive> then information must be entered into both tables. Cote: As for all administration funtionsJ iruits may only be addedJ deleted or hanged from the master mop aount. CMSS Sstem Mana!ement "uide# version 2.$ Page 27 Circuit Contro' !!ing an 1n&ut )ircuit '. .rom the CM-- 67, run the 4rale B,nput &inesC interfae# )a*"es II Input 2ines 2. ,n the 4rale 67, press IInsertG ). 1nter the re:uired fields into the 4rale 67,. /. %ress ISaveG. CM-- will then automatially onfigure the iruitJ start the re:uired proesses et. ,n the 4rale ,nput &ines 67, there are typially 85'0 fields that you must enter# '. Circuit name# A 8 harater name 2. 2ine )ype: "here is a list of line types available and you need to selet one. "he most ommon line types are# "C%(,% $M4 listen soAet Q leave all up "C%(,% soAet# $M4 "/ harts "C%(,% listen soAet Q e!trat on NCNC(NNNN ?.28 -end(*eeive %+C ,nput M1--A61- from a given diretory ). &ine .ormat. "here is a list of line(message formats available for a hosen B&ine "ypeC. "he most ommon line formats are# $M48 Q $M4 ,"A8 U-4@I .. U1"?I format $M4 Q $M4 NCNC(NNNN format A."N Q A."N NCNC(NNNN format A."N2 Q A."N U-4@I .. U1"?I format /. Description# a omment line 8. ;utput circuit# optional <. )C%/I% 9G Service/%ortJ: =optional> .or soAet onnetions it is neessary to define whih servie(port the iruit is to reeive data on =normally '028 .. <8800>. Page 28 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' !igure (: ;rac"e Input 2ines G:I CMSS Sstem Mana!ement "uide# version 2.$ Page 29 Circuit Contro' &%ample ' (dding an input )M* TCP+IP soc,et connection '. 0etermine the soAet(port that you will listen on. ,t is reommended that these ports be in the range )0000 to <0000 to avoid lashes with other appliations =eg httpJ ftp>. 2. Add this port number to the /etc/services file =as root>. .or e!ample# mop;usa0' )008<(tp W $ashington te!t input ). 1nter the iruit details into the ,nput &ines 67, and press U-A+1I. ,n the ,nput &ines 67, enter the following# '. %ress IInsertG 2. 1nter Circuit Came ). 2ine )ype# hoose B)C%/I% <M; "isten soc?etC =from list>. "he B&ine .ormatC will automatially be set to B$M48C. /. 1nter a iruit description 8. -et the output circuit if you will send and reeive on this onnetion. <. %ress the Se.uence button to hange se:uene number related fields Change se:uene number range if re:uired -et the *e:uest .or *epetition fields# i. -et auto re.uest K to S1- ii. address K CM-- address of related output iruit =an be left blanA if have set output iruit> iii. ma4imumJ K ma!imum number of messages to be re:uested in one message iv. originator K / harater CCCC of destination 9. %ress the )C%/I% button and set the Service/%ortJ field to the servie name =or number> on whih you want to listen for alls 2. %ress ISaveG. CM-- will then onfigure the iruit and start listening for alls. Page 30 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' &%ample - (dding an input FTP circuit Create a directory into #hich the sender can put fi"es using !)%. .iles in this diretory need to be read and deleted by CM-- =user K mop> and so it is reommended that the diretory by owned by mop. 6enerally it is also reommended that you use anonymous !)% and that the directory name *e the same as the circuit name. m?dir Hftp/pu*/55501 cho#n cmop:cmss Hftp/pu*/55501 chmod uogLr#4 Hftp/pu*/55501 ,n the ,nput &ines 67, enter the following# '. %ress IInsertG 2. 1nter Circuit Came ). 2ine )ype# hoose BInput MASS3GAS from a given directoryC =from list>. /. A list of B2ine !ormatsC will appear. Choose the re:uired entry depending on the header(trailer format to be used. %robably the most ommon is BGACA-32 M !-AA !;-M3)F 8. 1nter a iruit description <. %ress the Se.uence button and hange chec? se.Js to C; 9. %ress the Drivers button and set the parameters field to ontain the name of the diretory where CM-- will read the messages from =as defined above>. .or e!ample# (home(ftp(pub(.",0' 2. By default CM-- only reads BH.msgC files from the given diretory. ,f you want to read files with a different suffi! then you will need to add more information to the parameters field. .or e!ample to read only H.t!t files from diretory (home(ftp(pub(.",0' put the following in the parameters field# (home(ftp(pub(.",0' Q1 t!t 3. %ress ISaveG. CM-- will then onfigure the iruit and start reading messages from the diretory. CMSS Sstem Mana!ement "uide# version 2.$ Page 31 Circuit Contro' &%ample . (dding a )M* batc!ed FTP messages input circuit "here is a $M4 standard that allows 6"- messages to be reeived via ."%. !irst create a directory into #hich the sender can put fi"es using !)%. .iles in this diretory need to be read and deleted by CM-- =user K mop> and so it is reommended that the diretory by owned by mop. 6enerally it is also reommended that you use anonymous !)% and that the directory name *e the same as the circuit name. m?dir Hftp/pu*/55501 cho#n cmop:cmss Hftp/pu*/55501 chmod uogLr#4 Hftp/pu*/55501 ,n the ,nput &ines 67, enter the following# '. %ress IInsertG 2. 1nter Circuit Came ). 2ine )ype# hoose B<M; MASS3GAS !)% standardC =from list>. /. 1nter a iruit description 8. 1nter an output circuit if re:uired. <. %ress the Se.uence button Change se:uene number range if re:uired -et the *e:uest .or *epetition fields# i. -et auto re.uest K to S1- ii. address K CM-- address of related output iruit =an be left blanA if have set output iruit> iii. ma4imumJ K ma!imum number of messages to be re:uested in one message iv. originator K / harater CCCC of destination 9. %ress the Drivers button and set the parameters field to ontain the name of the diretory where CM-- will read the messages from =as defined above>. .or e!ample# (home(ftp(pub(???0' Note# By default the 0river looAs for $M4 BH.bC files whih is the standard most ommonly used for the e!hange of messages. ,f you wish to looA Page 32 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' for another of the $M4 defined formats then use MA option in the parameters fie"d. 9A a alphanumeri messages 9A f fa! harts 2. %ress ISaveG. CM-- will then onfigure the iruit and start reading messages from the diretory &%ample / (dding an 01-2 P3C input line .irst onfigure the ?.28 line on the -erver =see later setion for details>. ,n the ,nput &ines 67, enter the following# '. %ress IInsertG 2. 1nter Circuit Came ). 2ine )ype# hoose B5.2$ -eceive on"y %NCC or B5.2$ Send/-eceive %NCF =from list>. Note# ,f you are defining a -end(*eeive %+C then always define the *eeive =input> line first /. Choose the B2ine !ormatC from the list displayed. Normally you would use B$M48C. 8. 1nter a iruit description <. -et the output circuit if you will send and reeive on this onnetion. 9. %ress the Se.uence button to hange se:uene number related fields Change se:uene number range if re:uired -et the *e:uest .or *epetition fields# i. -et auto re.uest K to S1- ii. address K CM-- address of related output iruit =an be left blanA if have set output iruit> CMSS Sstem Mana!ement "uide# version 2.$ Page 33 Circuit Contro' iii. ma4imumJ K ma!imum number of messages to be re:uested in one message iv. originator K / harater CCCC of destination 2. %ress the 5.2$ button and set the fields# 5.2$ card K line on whih will onnet =eg !28pa0> M *it K typially set to S1- ca""ed/ca""ing addresses K %+C number =eg '..> pac?et "ength Q typially is '22 or 28< 3. %ress ISaveG. CM-- will then onfigure the iruit and start listening for alls. Page 34 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' !!ing an ,ut&ut )ircuit '. .rom the CM-- 67, run the 4rale B4utput &inesC interfae# )a*"es II ;utput 2ines 2. ,n the 4rale 67, press IInsertG ). 1nter the re:uired fields into the 4rale 67,. /. %ress ISaveG. CM-- will then automatially start the re:uired proesses et. ,n the 4rale 4utput &ines 67, there are several fields that you must enter# '. Circuit name# A 8 harater name 2. 2ine )ype: "here is a list of line types available and you need to selet one. "he most ommon line types are# "C%(,% $M4 soAet Q leave all up "C%(,% $M4 "/ hart ?.28 %+C ."% delivery of .,&1- ). &ine .ormat. "here is a list of line(message formats available for a hosen B&ine "ypeC. "he most ommon line formats are# $M48 Q $M4 ,"A8 U-4@I .. U1"?I format $M485"C% Q $M4 "C%(,% soAet standard $M4 Q $M4 NCNC(NNNN format A."N Q A."N NCNC(NNNN format =send heA msgs> A."N' Q A."N NCNC(NNNN format =N4 heA msgs> A."N2 Q A."N U-4@I .. U1"?I format /. Description# a omment line 8. 3ddress# Mandatory destination address =)53 haraters long> <. Input circuit# optional 9. )C%/I% 9G host# .or soAet onnetions define the ,% address or hostname of the mahine that you wish to send to. 2. )C%/I% 9G %ort: .or soAet onnetions define whih servie(port the iruit is to send data to =normally '028 .. <8800>. CMSS Sstem Mana!ement "uide# version 2.$ Page 35 Circuit Contro' !igure &: ;rac"e ;utput 2ines G:I Page 36 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' &%ample ' (dding an output )M* TCP+IP soc,et connection '. .irst obtain the destination ,% address and the destination port number. 2. 1nter the iruit details into the 4utput &ines 67, and press U-A+1I. ,n the 4utput &ines 67, enter the following# '. %ress IInsertG 2. 1nter Circuit Came ). 2ine )ype# hoose B)C%/I% <M; soc?et standardC =from list>. "he B&ine .ormatC will automatially be set to B$M485"C%C. /. 1nter a iruit description 8. 1nter the destination address <. -et the input circuit if there will be a related reeive onnetion. 9. %ress the )C%/I% button to store the host ,% address and the port number. Note# -ome M-- re:uire that you onnet to an alternative host if the primary fails. ,f there is an alternative host then store this ,% address in the *ac?up host field 2. %ress the 3dvanced button if you want to hange some other default iruit parameters# msg siOe Q normally leave at default ='8J000> but will need to hange ma!imum message length for A."N iruits =normally '200> Pourna" msg K Q on some iruits you may not want to Dournal the transmission of eah message cance" B after nn hours Q partiularly on unreliable or busy linAs it is sometimes desirable to automatially anel old messages :ueued for transmission after a ertain number of hours. Se.uence Cum*ers min/ma4 3. %ress ISaveG. CM-- will then onfigure the iruit. CMSS Sstem Mana!ement "uide# version 2.$ Page 37 Circuit Contro' &%ample - (dding an output )M*4standard FTP circuit .irst obtain the following information from the destination# '. ,% address 2. user name and password ). destination diretory /. use se:uene numbers or not X =strongly suggest S1-> 8. $hether to send alphanumeri files using the .a suffi! and binary files using the .* suffi! or send both types of files with .* suffi! ,n the 4utput &ines 67, enter the following# '. %ress IInsertG 2. 1nter Circuit Came ). 2ine )ype# hoose B!)% de"ivery M <M; standardC =from list>. "he B&ine .ormatC will automatially be set to B$M4;."%;-1RC. /. 1nter a iruit description 8. 1nter the destination address <. -et the input circuit if there will be a related reeive onnetion. 9. %ress the !)% button. "his will ause a separate display to appear into whih you need to plae the ."% information# Destination 6ost: 5 ,% address :ser9ID: G %ass#ord Defau"t directory Cote: "here are many other optional ."% fields in this display that are overed by the online @1&% notes. 2. %ress the 3dvanced button if you want to hange some other default iruit parameters# msg siOe Q normally leave at default ='8J000> but will need to hange ma!imum message length for A."N iruits =normally '200> Pourna" msg K Q on some iruits you may not want to Dournal the transmission of eah message Page 38 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' cance" B after nn hours Q partiularly on unreliable or busy linAs it is sometimes desirable to automatially anel old messages :ueued for transmission after a ertain number of hours. Se.uence Cum*ers min/ma4 3. %ress ISaveG. CM-- will then onfigure the iruit. &%ample . (dding a non4)M* output FTP circuit ,t is sometimes useful to ."% messages and files and use a filenaming onvention that is different from the $M4 one. ,n partiular this would our when you are not sending to another M-- and when the filenames need to be meaningful. "o do this follow e!ample 2 but for the 2ine )ype hoose B!)% de"ivery of !I2ASC. 7sing this option the !I2AS are sent with a destination filename that is the same as their origina" fi"enames or with a filename that you supply via the !i"e S#itching ta*"e. ,f you send a MASS3GA then the destination filename is ))33IICCCC for $M4 format messages. .or non5$M4 messages the filename is simply Snnn.t4t where nnn K 000..333 Cote# 4ther filenaming options are available Cote: ,f you wish to send a file to a non5default diretory then this an be done via the !i"e S#itching ta*"e. &%ample / (dding an output 01-2 P3C .irst onfigure the ?.28 line on the -erver =see later setion for details>. ,n the 4utput &ines 67, enter the following# '. %ress IInsertG 2. 1nter Circuit Came ). 2ine )ype# hoose B5.2$ %NCC =from list>. /. -elet the appropriate B2ine !ormatC Q typially $M48 or A."N. 8. 1nter a iruit description <. 1nter the destination address 9. -et the input circuit if there is a related reeive onnetion. CMSS Sstem Mana!ement "uide# version 2.$ Page 39 Circuit Contro' Note# ,f you are defining a -end(*eeive ?.28 %+C then always define the *eeive =input> line first 2. %ress the 5.2$ button to store the ?.28 interface name and the %NC num*er 7address8 and pac?et "ength. interface K line on whih will onnet =eg !28pa0> address Q %+C number *ac?up address K not used here pac?et "ength Q typially is '22 or 28< =bytes> 3. %ress the 3dvanced button if you want to hange some other default iruit parameters# msg siOe Q normally leave at default ='8J000> but will need to hange ma!imum message length for A."N iruits =normally '200> Pourna" msg K Q on some iruits you may not want to Dournal the transmission of eah message cance" B after nn hours Q partiularly on unreliable or busy linAs it is sometimes desirable to automatially anel old messages :ueued for transmission after a ertain number of hours. Se.uence Cum*ers min/ma4 '0. %ress ISaveG. CM-- will then onfigure the iruit. Page 40 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' )hanging an '+isting )ircuit ,t may be neessary to hange the onfiguration of an e!isting iruit O for e!ampleJ to hange the destination mahine address. Most hanges are done by# '. update the re:uired database table by using the 67,# )a*"es GG Input 2ines 4r )a*"es GG ;utput 2ines. 2. ,f the hange relates to the ?.28("C%5,% address that the system uses to ommuniate then you may need to lose the e!isting onnetion and establish a new one# a. -elet CI-C:I) C;C)-;2 from the CM-- 67, . b. 7se the left mouse button to selet the re:uired iruit. . -elet C2;SA. d. -elet ;%AC. Note# if the hange is to the E2ine )ypeF then it is neessary to stop any e!isting line driver proess assoiated with this line and then start the new proess. *ather than do this it is muh easier to reate a new iruit and then delete the old iruit after you have suessfully tested then new iruit. (e"o3ing an '+isting )ircuit "o remove =or delete> an e!isting iruit =or onnetion> simply selet the De"ete 2ine in the CM-- 67, 3dmin pulldown menu. "his auses any related proesses to be stopped and related files and database reords to be deleted. 4ptionally all related swithing table entries are also deleted. CMSS Sstem Mana!ement "uide# version 2.$ Page 41 Circuit Contro' '-"ai$ circuits e5mail input and output iruits an be onfigured in the same manner as other iruits. 1letroni mail =15mail> an be a very simple and ost effetive way to e!hange 6"- messages. -ome entres may even find it a useful tool in a baAup situation when a 6"- linA is unavailable. ,t should be noted however that e5mail is not an end5to5end servie and there is no guarantee of the timely delivery of messages. Proposed )M* e4mail standard "he following rules desribe a proposed $M4 standard for sending both 0ata Colletion Bulletins and Binary 6"- Messages via 15mail. -u"es for sending G)S messages via e"ectronic mai" on the Internet: '. 6"- Messages must be sent in A-C,, =plain te!t>J and not in @"M&. 2. "he 6"- message must be sent in the body of the te!t. ). 1ah e5mail may ontain only one 6"- messageJ starting with the abbreviated header line. ))33ii CCCC RRGGgg ST message te4t /. 1ah line of the 6"- message should not e!eed <3 haraters. 8. Binary data may be transferred in e5mail attahments. "he struture of an attahment shall be idential to that of a file transferred by ftp. "he length of an attahment shall not e!eed 2 MBytes or as speified in a bilateral agreement. "he body of the e5mail shall remain empty if attahments are used. 4nly one attahment per e5mail is permitted. Attahments shall be oded in Base</ =M,M1 standard>. <. "he BsubDet lineC depends on the ontent of the e5mail. .or e5mails that ontain a 6"- message in their bodyJ the BsubDet lineC shall ontain the abbreviated header line of the message. .or e5mails that ontain a binary data attahmentJ the BsubDet lineC shall follow the $M4 file naming onventions. 5on4)M* format e4mail Besides the $M4 standardJ CM-- also supports other e5mail message formats for domesti use. "hese inlude# '. freeMformat. 15mails an be reeived ontaining Dust the report. .or e!ample# AA?? 222)) 3/82) ''(90 <)/08 '0'3' 20'9< <332/ 90//2 888 20((( /9332 82/'/ 9''(( 999// 2. UCUC heading. "he e5mail may start with a NCNC and optionally some CM-- destination addresses. .or e!ample# Page 42 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' NCNC 6A+N 6A0* 6".- N*.C 6A.N "A. AM0 S-N$ 222'28N 2202 22009T" 3333 BTN0'8 -C"'20 .M00 '2002T" 3333 -C"020 -C"'20 .M0) 0<0'2T" CA+4T %*4B/0 ,N"1* 0)02 )000 "-*A -C"0'8 -C"080CB " '< 22 2) 22 R '0'8 '0') '0'' '0'0 NNNN &4mail security considerations '. 15mail is inherently inseure. "o minimise seurity issues the reeiving entre should only proess 6"- related e5mails from a pre5defined list of e5mail addresses. "hat isJ the reeiving entre should validate the e5mail header B.rom#C field. "o do this in CM--# '. -et the BNa"idate source emai" address KC option on the CMSS G:I, 3dmin M System %arameters disp"ay. 2. -et the e5mail addresses that you want to aept messages from via the CMSS G:I, )a*"es 9G Misce""aneous )a*"es 9G Na"id emai" 3ddress )a*"e. ,n this table put individual email addresses or the base address for an organiPation =eg bom.gov.au> ). $hen an e5mail is then reeived that is not from an authoriPed addressJ CM-- raises an alarm of the following form and does not proess the message# 3C2022I M3I01 MSG nnn -APAC)AD: 6A3DA- 9 IVG C;) 3CCA%)AD 2. ,t is reommended to use speifi mail aounts for 6"- data transfer with bilaterally agreed names and not to reeive 6"- data in personal mailbo!es. ). A problem with some Mail 1!hangers is that by default they operate as an Bopen5 relayC. An open5relay oursJ for e!ampleJ if you are on site 1'COMJ and you aept mail from 2'345 destined for C'OR.' "his means that spammers an use your mail system to distribute their e5mails. Centres should ensure that they do not operate as an open5relay. .or entres using BsendmailC as the Mail 1!hanger it is reommended that they use version 2.3 or later whih by default denies unauthorised relaying. CMSS &4mail input circuit "o add a CM-- e5mail input iruit do the following# '. Agree on an e5mail address to reeive messages on. eg mssYbom.gov.au 2. Add an entry for this address to the (et(mail(aliases file on the CM-- mahine=s>. .or e!ample# cmss : WX/usr/"oca"/*in/cmmai"in /home/cmop/cmss M3I01F CMSS Sstem Mana!ement "uide# version 2.$ Page 43 Circuit Contro' $hat this entry says is that when an e5mail is reeived that is addressed to BmssC then pass it to the program alled Bcmmai"inF whih will pass it to CM-- via the input iruit alled BM3I01F. /home/cmop/cmss is the CM-- home diretory and may be different on some mahines. ). *un the ne#a"iases ommand to rebuild the mail aliases database from (et(mail(aliases /. Change the /etc/mai"/aliases file on the primary mail e!hange server to pass messages for this address to the CM-- -erver =and run newaliases>. .or e!ample# mss# mssYomms.ho.bom.gov.au 8. Create a CM-- input iruit =normally MA,0'> to reeive the inoming e5mail messages. 0o this in the normal manner via the )a*"es 9G Input 2ines onfiguration menu. <. Set the ENa"idate source emai" address KF option on the CMSS G:I, 3dmin M System %arameters disp"ay. 9. -et the e5mail addresses that you want to aept messages from via the CMSS G:I, )a*"es 9G Misce""aneous )a*"es 9G Na"id emai" 3ddress )a*"e. ,n this table put individual email addresses or the base address for an organiPation =eg bom.gov.au> CMSS &4mail output circuit "o add a CM-- e5mail output iruit do the following# '. +ia the CM-- 67,J 3dmin 9G System %arameters menu define the following# '. Came of te4t message mai"er to be used. Normally /usr/"i*/sendmai" 2. Came of !i"e mai"er. "his allows CM-- to send files =eg gifs> as attahments =optional>. ). -ep"y 3ddress# e5mail address to whih reipients an reply. /. )he Defau"t Su*Yect line. CM-- always sends e5mails using this default subDet unless it is sending messages from the 3I!S %roduct %reparation System. ,n this ase CM-- adds the A,.- produt name to the subDet line. 2. Add the output iruit in the normal manner via the )a*"es 9G ;utput 2ines menu. ,t is reommended that the iruit name be BAM3I2F. ). -etup CM-- addresses to point to e5mail addresses via the cmssout ta*"e 7output conversion ta*"e8 or via the 3I!S Despatch system. )a*"es 9G Misce""aneous )a*"es 9G cmssout Page 44 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' Cote# ,f you are using the CM-- 3 harater addressing sheme then via the 67, SACD field you may speify atual e5mail addresses rather than the CM-- 3 harater e:uivalent. CMSS Sstem Mana!ement "uide# version 2.$ Page 45 Circuit Contro' 4ines5out 6a7$e "he "ines@out table 67, updates information in the database table. Sou should never need to hange the table diretly. Sou an see the format of the lines;out table by issuing the following 4rale ommands at the ommand line# s."p"us / desc "ines@out "he struture of the database "ines@out table is as follows# )a*"e 3: "ines@out ta*"e Field Description RRRCC Mandator# field' ,dentifies the circuit/connection' ,t must &e fi"e characters in length' 5#picall# it is three characters followed &# two digits ( for example) 5!567 would &e connection num&er one (7) to TST' O5%4R8CC5 Optional field' Defines the related input circuit when a single connection is used to &oth send and recei"e data' 95#picall# used for :';< Permanent 0irtual Circuits (P0Cs)'= D4!CR,P5,O3 Optional comment field' 5his information is displa#ed in the C,RC/,5 CO35RO+ ./,' 1DDR4!! 5his is the address that is used to send messages to this circuit' 5he address ma# &e up to > characters in length' -M5 5his field defines the header and trailer that is sent surrounding each message' ,t is stored as a num&er' 5he standard 1-53 and .5! formats are? 6' @ WMO AsohB '' AetxB format' 6- @ WMO ACCCCB '' A3333B format 67 @ WMO AsohB '' AetxB format for 5CP !ocket connections 2/ @ 1-53 ACCCCB '' A3333B format with Check Messages' M!.!,C4 !ets the maximum message length for the circuit' 5his should not exceed 7<)666 characters' ,t is used for some old destination computers that cannot handle (crash) when long messages are sent' On non1-53 circuits if the message length limit is exceeded then an alarm is raised and the message is not sent ( for example) PRP6<71 M!. nnnnnn 5OO +O3. -OR RRRCC M1:+43 ,! nnnn) M!.+43 ,! xxxx' -or 1-53 circuits t#picall# the maximum siDe is 7E66 characters' ,f a message exceeds this length on 1-53 connections) CM!! automaticall# di"ides the message into smaller messages' Page 46 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' Field Description M,38!4F Minimum se$uence num&er' 3ormall# 6 or 7' M1:8!4F Maximum se$uence num&er' 3ormall# >>> or >>>>> O/5F 1lwa#s set to ' (5rue)' ,P831M4 -or 5CP/,P connections this is the name of the destination computer or its ,P address' -or :';< connections this is the local machine :';< port num&er that is to &e used for the connection' On ,2M !er"ers the :';< interfaces are num&ered 6 '' n ' D5481DDR4!! 5his complements the G,P831M4H field gi"en a&o"e' -or 5CP/,P connections it defines the GportH (or ser"ice num&er) to connect to on the remote computer' -or :';< Permanent 0irtual Circuit (P0C) connections it defines the P0C to &e used ? 7 '' n' -or :';< !witched 0irtual Circuit (!0C) connections) it defines the :'7;7 address of the destination machine' P1CI458+43 Defines the length of :';< data packets to &e used (%P onl#)' 21CI/P8%O!5 3ot normall# used and not supported on most links' Defines an alternati"e host to &e used if the primar# host is una"aila&le' DR,04R Defines the process to &e run to communicate on this line/circuit' 5here is a multitude of dri"ers' 5he standard ones are? Tcpsend used to send data using 5CP/,P sockets Ibm%-2p#c ,2Mspecific dri"er for use with :';< P0Cs Ibm%-2s#cout ,2M dri"er for sending using :';< !0Cs Ibm%-2s#c ,2M dri"er for sending and recei"ing using :';< !0Cs mailout email deli"er# cfa%out -ax deli"er# lppsout +13 Printer deli"er# %-2p#c %P e$ui"alent of i&mx;<p"c %-2s#cout %P e$ui"alent of i&mx;<s"cout %-2s#c %P e$ui"alent of i&mx;<s"c' P1R1M454R! Most of the a&o"e dri"ers ha"e optional parameters) which can &e determined (as for an# other CM!! process) &# starting the process with no options set' -or all dri"er processes) the first two parameters are the home director# (*CM!!) for CM!! and the circuit (RRRCC) that the process is to dri"e' T!ese two fields CMSS Sstem Mana!ement "uide# version 2.$ Page 47 Circuit Contro' Field Description are added automatically by t!e system and s!ould 5*T be included in t!e Dri#er parameters field' 4ines5in ta7$e /01 "he "ines@in table 67, updates information in the database table. Sou should never need to hange the table diretly. "he struture of the database "ines@in table is as follows# )a*"e ': "ines@in ta*"e: Field Description RRRCC ,dentifies the circuit/connection' ,t is a mandatory field and must &e fi"e characters in length' 5#picall# it is three characters followed &# two digits ( for example) 5!567 would &e connection num&er one (7) to 5!5' O5%4R8CC5 Defines the related output circuit) if an#' !et for :;< P0Cs where the same connection (P0C) is used to send and recei"e data' 1lso set to help the automatic re$uest/repeat ser"ice' ,f a re$uest for missing data is recei"ed then the *T8&"9CCT field is checked to determine where to send the response' +,3485JP4 5his field defines the header and trailer that is recei"ed surrounding each message' ,t is stored as a num&er' 5he standard 1-53 and .5! formats are? 6- allow a multitude of different headers/trailers 6. WMO A!O%B '' A45:B format 6/ WMO ACCCCB '' A3333B format 62 1-53 ACCCCB '' A3333B format '6 1-53 A!O%B '' A45:B format' !4F8C%4CI !et to ' (5rue) if message se$uence num&ers are to &e checked and 6 (-alse) if not' !e$uence num&ers are used on 1-53 and WMO/.5! connections and should &e checked' ,f the# are checked then the s#stem will re$uest missing messages &ased on gaps in se$uence num&ers or raise an Operator alarm so that the operator can take action' D4!CR,P5,O3 Optional comment field' 5his information is displa#ed in the C,RC/,5 CO35RO+ ./,' DR,04R 5his defines the process to &e run to communicate on this line/circuit' 5here is a multitude of dri"ers' 5he standard ones are? ibms#cin ,2M onl#' +istens for :';< calls and recei"es messages ibm%-2p#c ( ,2M onl#) recei"es messages on an :';< P0C Page 48 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' Field Description tcpin ( listens for 5CP/,P connections and recei"es messages tcpincall ( connects to a gi"en 5CP/,P address and recei"es messages s#cin ( %P e$ui"alent of i&ms"cin %-2p#c ( %P e$ui"alent of i&mx;<p"c P1R1M454R! Most of the a&o"e dri"ers ha"e some optional parameters' Jou can determine what these parameters are for an# dri"er (or an# other CM!! process) &# starting the process with no options' -or all Gdri"erH processes) the first two parameters are the CM!! home director# (*CM!!) and the circuit (RRRCC) that the process is to dri"e' T!ese two fields are added automatically by t!e system and s!ould 5*T be included in t!e :Dri#er parameters; field' !4R0,C4 -or incoming 5CP/,P connections (dri"er @ tcpin) this field contains the local port/ser"ice num&er that this process listens on) and to which the otherend connects' -or outgoing 5CP/,P connections (tcpincall) it contains the host name of the de"ice to &e connected to' -or :;< P0Cs (i&mx;<p"c) this is the local machine :';< port num&er that is to &e used for the connection' On ,2M !er"ers the :';< interfaces are num&ered 6 '' n' 5his field is not used for :';< !0Cs' D5481DDR4!!7 -or :';< P0Cs this contains the P0C num&er to &e used (7'')' -or :';< !0Cs this contains the :'7;7 num&er to &e listened on for calls' -or tcpincall) it contains the 5CP/,P port/ser"ice to &e connected to' M82,5 :';< onl#' !et to < (Jes) if the sending site uses the M&it to define the end of each message' ,f this is not set for :';< connections then CM!! looks for CCCC/3333 or A!O%B/A45:B to determine start and end of messages P1CI458+43 -or :';< connections this defines the packet length expected )a*"e $: "ines@in ta*"e 7-e.uest/-epeat fie"ds8 Field Description R4FR4P-M5 Defines the format of the Re$uest message to &e sent' ,f this field is left &lank or set to =) no re$uest message is CMSS Sstem Mana!ement "uide# version 2.$ Page 49 Circuit Contro' Field Description sent and instead an alarm is sent to the Operator' 5wo of the formats are? B WMO format re$uest C 1-53 format re$uest' 1DDR4!! 1ddress to which the re$uest or response is sent' M1:8R4FR4P !ome centres put a limit on the num&er of messages that can &e re$uested &# one messages' ,f the num&er of missing messages exceeds this limit then CM!! sends multiple re$uests' R4F8OR,. WMO countr# code (CCCC) of destination for re$uest messages' Page 50 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' Switc!ing Tables All swithing funtions are ontrolled by a series of 0atabase tables. /6S 8u$$etin Switching 6a7$e 97u$!esr: *u"desr stands for Bulletin 0esription. ,t defines where inoming 6"- formatted messages are sent. "he ))33II/CCCC of the inoming message is heAed in *u"desr to determine the message destination=s>. ,t is normally updated by user interation through the CM-- 67, )a*"es pulldown menu. )a*"e +: *u"desr fie"ds 7co"umns8 5ame 5ull> Type 5511,, 3ot null Char(K) CCCC 3ot null Char(L) !O/RC4 Char(<) O2!85,M4 3ot null Char(;) D4!581DDR 3ot null Char(>) )a*"e (: *u"desr fie"d definitions Field Description 5511,, WMO defined Kcharacter field that defines the message contents' CCCC WMO defined countr# code of message' 5he 5511,, and CCCC uni$uel# identif# the message' !O/RC4 Optional field' ,f set) it defines that onl# messages from the gi"en source (RRRCC) are to &e switched to the destination address' O2!85,M4 5he o&ser"ation hour of the message' ,f set this means that the destination onl# wishes to recei"e this message (5511,,/CCCC) for the gi"en o&ser"ation hour ( for example) onl# recei"e 66M/5C messages' 3ormall# this field is empt# (3/++) which means switch all hours' D4!581DDR Destination address where message is to &e sent' Cote: CM-- allows A."N messages with embedded $M4 headers to be swithed through *u"desr. @oweverJ for this to be used at the moment CMSS Sstem Mana!ement "uide# version 2.$ Page 51 Circuit Contro' the -47*C1 field must be set with the A."N iruit name. "his is to stop a message from being swithed twie when it is reeived on both the 6"- and the A."N. "his restrition is under review. "he following -R& e!ample e!trats si! rows indiating Australian =AMMC> bulletin -MA70' is sent to si! destination addresses. SB2G se"ect D from *u"desr #here ttaaii Q ZSM3:01Z *eturns the result# )a*"e &: A4amp"e SB2 resu"ts TT((II CCCC S*U"C TIM& D&ST !M1/67 1MMC 13O/ !M1/67 1MMC 13C+ !M1/67 1MMC -1C0 !M1/67 1MMC .5IJ !M1/67 1MMC ,3WD !M1/67 1MMC MP3. "he wildard harater J is used to redue the number of entries re:uired in *u"desr. A wildard is typially used to swith groups of Model 0ata messages =that have a similar ""AA,,> with a minimum of *u"desr entries. "he system searhes *u"desr entries for a speified ""AA,,(CCCC. ,f an e!at math is not foundJ it attempts a series of partial mathes. "he searh stops when a partial math is found. "he wildard searh hierarhy is as follows# Search for exact TTAAII/CCCC match Search for TTAA##/CCCC Search for TTA###/CCCC Search for TT####/CCCC Search for TTAAII/#### Search for TTAA##/#### Search for TTA###/#### Search for TT####/#### Cote: "aAe are when using wildards. A new entry that defines a omplete math will taAe preedene over entries that define a partial math. Page 52 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' #i$e Switching 9stn!esr. an! .i$e!esc: .iles are swithed via their name. &iAe the other swithing tablesJ .ile -withing is defined via a 67, aessed through the CM-- 67, )a*"es pulldown menu. )a*"es GG S#itching )a*"es GG !i"e S#itching )a*"e '. "he file names normally is up to )0 haraters in length =but this an be inreased> 2. A simple wildard sheme is deployed. Basially a string to digits an be replaed by an asterisA =H> in the tables. %rimarily this is used to allow for files that ontain date(time information in their name. 1g A filename of .,&1?;H.gif in the .ile -withing table will math files liAe .,&1?;200'08)0.gif ). Also in the .ile -withing table you an define how long eah file is stored for. %rimarily this is designed to stop vast amounts of disA spae being used to save old opies of large files that are fre:uently reeived. /. -ometimes it is neessary to send a file with a different name than normal. 0o this by plaing the destination fi"ename in the EinformationF fie"d. 8. -ometimes it is also neessary to send a file to a non5default diretory on the destination mahine. ,n this ase store the directory name in the EinformationF fie"d #ithin ang"e *rac?ets. .or e!ample# I/#e*/htdocs/radar/regG )a*"e ,: !i"e S#itching 7stndesrf8 Field Description -,+431M4 !/--,: 1DDR4!! Destination address ,3-O /sed to specif# a destination director# and/or a destination file name' PR,OR,5J CM!! priorit# G1H '' GDH )a*"e 10: !i"e S#itching 7fi"edesc8 Field Description -,+431M4 !/--,: +,-45,M4 5ime in hours that the file is kept' CMSS Sstem Mana!ement "uide# version 2.$ Page 53 Circuit Contro' /rou& !!ress 6a7$e 9gr&a!!rs*gr&!esc: 6roup Addressing defines a group address that points to a series of single addresses O for e!ampleJ if a series of messages are to be sent to multiple destinationsJ it is simpler to assign them by group address rather than address eah message individually to eah destination. 6roup Addresses always start with G and the 6roup Addresses table name is grpaddrs. "he fields =olumns> in grpaddrs are as follows# SB2G desc grpaddrs# )a*"e 11: grpaddrs fie"ds 7co"umns8 5ame 5ull> Type .RO/P! 3ot null 0archar;(>) 1DDR! 3ot null 0archar;(>) "here is a related 6roup 0esription table that desribes why the 6roup Address is being used# grpdesc SB2G desc grpdesc# )a*"e 12: Group Description ta*"e 5ame 5ull> Type .RO/P! 3ot null 0archar;(>) D4!CR 0archar;(766) "here are two 67, table displays for 6roup Addressing# "ables II 6roup Addresses E 0esription "ables II 6roup Addresses ,t is preferable to always use 6roup Addresses E 0esription beause this fores eah new 6roup Address to be doumented )$ient !!ress 6a7$e Normally there is one CM-- nine =3> harater address assoiated with an output iruit. @owever there are irumstanes where multiple addresses need to be assoiated with one output iruit or when the destination address does not fit into our nine harater format. 1!amples are# '. .A?# .a! numbers may e!eed nine haraters in length and one message may be sent to any number of fa! addresses =ie need to assoiate multiple addresses with a iruit>. Page 54 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' 2. 15MA,&# e5mail addresses do not fit within nine haraters and one message may be sent to multiple e5mail addresses ). A."N# A."N addresses are 25haraters long and so fit within our addressing sheme however many A."N addresses need to be assoiated with an A."N line. "o handle these situations the c"ient@addr@t*" is used. Basially it maps a CM-- address into an output iruit and optionally maps the CM-- into an e!ternal address =eg a .A? number or an e5mail address> ,f CM-- is installed with A,.- then this information is entered via the Despatch G:I that an be started from the U"ablesI pulldown on the CM-- 67,# )a*"es GG %roduct Despatch ,f A,.- is not installed then this information is entered via the C"ient 3ddress G:I that an be started from the U"ablesI pulldown. )a*"es GG C"ient 3ddress )a*"e CMSS Sstem Mana!ement "uide# version 2.$ Page 55 Circuit Contro' System Functions uto"atic Jo7 '+ecution 9;)6241S6: CM-- allows proesses to be started at a set time of dayJ in the same way that 7ni! ron operates. "he differene between CM-- and ron is that if CM-- is down(stopped when a proess is due to be startedJ it will be started as soon as CM-- is restarted. @oweverJ if the system is down at the due timeJ ron will not run the proess. "he ?C"N&,-" =referred to as L1!eution &istM> onsists of two database tables# 4ctn"ist ontains a list of all proesses to be started and their start times 4ctnne4t details the ne!t proess to be started. All tables in CM-- an be displayed and modified from the CM-- 67, as follows# 5a&les BB 2ulletin 5a&les BB 4xecution +istBB 4xecution +ist 3ext "he 1!eution &ist is normally used to produe the first edition and first retard of $M4 bulletinsJ but it an also be used to start any other proess. Cote: Currently only one proess an be run by the 1!eution &ist at a time. No two proesses should have the same start time. Normally CM-- operates in 7"C(6M" time and not loal time. 0CT55&0T table fields 5ctnne4t ontains a single reord that defines the ne!t proess to be started. )a*"e 13: 5C)CCA5) ta*"e fie"ds 5ame 5ull> Type !515/! 3ot null Char(L) 5,M4 3ot null Char(L) NO231M4 3ot null Char(76) 5,M4+,M,5 3ot null 3um&er(OE) P1R1M454R! Char(E6) Page 56 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' Status "he proess has four status parametersJ as follows# #ait O waiting for the proess start time e4ec O proess is e!euting now 4no# O proess is to be e!euted immediately =set by user> ha"t O set by user. No further proesses will be started until this status is hanged to #ait or 4no#. Time @our and Minute =@@MM> that the proess is to be started =in 7"C(6M">. Timelimit "he ma!imum time that this proess is e!peted to run for =in minutes>. $hen this time has e!pired the system raises a warning alarm and moves to the ne!t proess in the table. Parameters "he startup parameters for the proess. "he CM-- home diretory =$CMSS> is automatially added as the first parameter. CMSS Sstem Mana!ement "uide# version 2.$ Page 57 Circuit Contro' Bulletin Preparation 1ntro!uction to the uto"atic 8u$$etin Pre&aration Syste" Terminology A bulletin is a olletive of meteorologial reports. A report is either an observation =obs> or a foreast made at a partiular loation at a partiular time. "he report type is identified by a $M4 Aeyword O for e!ampleJ AA?? for -SN4% reports. ,n the Automati Bulletin %rodution -ystem =AB%->J a report is identified by a two5digit ode referred to as msgtype. A report may be made at a fi!ed land station or by a mobile station =that isJ a shipJ airraftJ drifting buoy or satellite>. "he loation of a fi!ed land station is given by either a $M4 station number or an ,CA4 identifier. ,n the AB%-J it is referred to as stn@num. "he loation of a mobile station is given by latitude and longitude. "he shipJ airraft or buoy is identified by a all sign or buoy ,0. ,n the AB%- a dummy stn;num of 33333 is used for mobile stations. "he time of an observation is referred to as o*s@hour. "wo times are defined for foreasts# the start time referred to as va"id@start and the end time or va"id@end. Categories of bulletins "he two types of bulletins are. "he fi!ed format bulletinJ with a fi!ed list of reporting stations that are ompiled into it. 1!amples of fi!ed format bulletins are -SN4% and M1"A*. "he normal format bulletinJ whih inludes any with the re:uired type and observation time. 1!amples of normal format bulletins are -@,% and A,*1%. "he format of bulletins is desribed in the Manual 'n the G(S? 3olume 1? )art II? Section ". A bulletin is identifiedJ for swithing purposes by its abbreviated header. "he data designators for the ""AAii are given in %ttachment II52 of the manual. Cote: By default CM-- does not inlude observations from international format messages in loal bulletins. ,f you want to do this for fi!ed stations then you must hange the BG)S u""etin %roductionF options in the BSystem %arametersF 67,. Page 58 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' Cote: -imilarly by default CM-- does not inlude Bmo*i"eF observations from international format messages in loal bulletins. ,f you want to do this then you must define the BCCCCFs of the messages that you want to inlude. Again this is done via the BG)S u""etin %roductionF options in the BSystem %arametersF 67,. Message recognition and bulletin preparation "he AB%s has three main omponents# An 4rale .4*M- 67, 5 to onstrut and modify bulletins =desribed below> A sub5system of the CMSS Message Recognizer stores reports for inlusion in bulletins =desribed in the Communications User Guide> "he bulljob program is run every '8 minutes to ompile bulletins =desribed in the Communications User Guide> 6he ,rac$e #or"s /01 "he 4rale .orms 67, is an interfae to the underlying 4rale 0atabase tables whih ontrol the Bulletin %reparation -ystem. !igure ,: ;rac"e forms G:I CMSS Sstem Mana!ement "uide# version 2.$ Page 59 Circuit Contro' Functions of t!e *racle forms GUI "he funtions of the 4rale .orms 67, are to '. .ind information about an e!isting bulletin 2. Add a new bulletin ). Modify an e!isting bulletin Add(delete bulletins Add(delete obs times Add(delete station numbers. *perating modes "he 67, has two operating modes# Normal 1nter Ruery. ,t is important to understand how they differ and to Anow whih mode you are in at any point sine this affets the way the 67, behaves and what ation the buttons perform. Normal mode $hen the 4rale .orms 67, is first startedJ it is in Normal Mode and all bulletins are seleted. "he first bulletinJ usually W 000'J is displayed. "he following buttons are enabled# Anter a Buery button CopyJ InsertJ De"ete and Save buttons. "he IIJ IJ G and GG arrow buttonsJ whih are used to navigate between the seleted bulletins. .untions 2 and ) an be performed in Normal Mode. Enter Query mode "o perform .untion ' O that isJ find e!isting bulletins O the 67, must be put into 1nter Ruery Mode. "o do thisJ press the Anter a Buery button. Page 60 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' "he following hanges our to the 67,# "he Anter a Buery button label hanges to -un the Buery button label "he CopyJ InsertJ De"ete and Save buttons are disabled "he IIJ IJ G and GG arrow buttons are disabled "he message Enter Query appears on the onsole display at the bottom of the 67, All fields on the 67, are leared and hange to light blue Cote: As with other buttons if the fous is in "oc? 2 or "oc? 3J then the ation affets only that bloA. Button palette !igure 10: ;rac"e *utton pa"ette Varying functions of some buttons -ome of the buttons have different funtions depending on whih BloA of the form urrently has the fous O that isJ where the ursor is loated. "he Anter a Buery button has two separate funtions and two different names depending on whih mode the form is in $hen the form is in Normal ModeJ it is the Anter a Buery button $hen the form is in 1nter Ruery Mode it hanges to the -un the Buery button. Availability "he C"earJ -estore and A4it buttons are always ative. -ome buttons are not ative at all times. "he 2ist of Na"ues button is only ative if a list of values popup window is available for that field O for e!ampleJ Msgtype has a list of values assoiated with it. ,n 1nter Ruery ModeJ only the -estoreJ C"ear and A4it buttons are ative. CMSS Sstem Mana!ement "uide# version 2.$ Page 61 Circuit Contro' utton functions )a*"e 1': ;rac"e *utton functions Button Function (dditional Information Cop# 2lock 7 Duplicates the currentl# displa#ed &ulletin 1 new window pops up for entr# of the new &ulletin num&er 5511ii and CCCC1ll information in 2locks ; and O is copied to the new &ulletin 2lock ; Duplicates the current first edition and retard times 1 new o&s hour must &e entered 5he station num&er must &e changed &efore sa"ing the &ulletin 2lock O Duplicates the current station num&er information ,nsert Clears the current displa# and inserts a new &lank record 1dds a new &ulletin in Bloc, ' 1dds a new record for the &lock in Bloc,s - and . Delete Remo"es the currentl# displa#ed record ,n 2lock 7) the whole &ulletin) including o&s times and station num&ers) is remo"ed ,n 2lock ; and O) onl# the currentl# selected record in the &lock is remo"ed 5o complete the function) press the Sa#e &utton 5o re"erse the delete action) press the "estore or Clear &utton' !a"e Commits all changes to the data&ase ta&les Jou cannot complete an# other action until #ou either press either Sa#e) Clear or "estore &uttons Clear /ndoes all pending changes and lea"es the form &lank Restore /ndoes all pending changes and re"ert to the last $uer# 4xit Closes down the ./, ,f there are changes pending) the s#stem issues an alert is issued to sa"e or clear Page 62 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' Bloc,s loc! " "his BloA ontains the $M4 Bulletin @eader information and bulletin format information. )a*"e 1$: "oc? 1 fie"ds Field Description Format 1DP 3o /ni$ue &ulletin identifier 3umeric ( 6666 >>>> 5511ii WMO identifier Refer to 1ttachment ,,< of the Manua' on the "%S# WMO 3o OEK CCCC Originator ,C1O identifier ( for example) 1MMC and 3--3 msgt#pe ,nternal message t#pe identifier Press the ?ist 3alues &utton to pop up a ta&le of msgt#pes and ke#words nil -lag to determine if 3,+ &ulletins are to &e prepared < or 5 fmt 5#pe of &ulletin F @ fixed format a specific list of stations is compiled 5 @ normal format all reports of the re$uired t#pe are compiled wind -or -M7;) 7O) 7L defines the "alue of iw in JJ..iw Refer to Code 5a&le 7E<< of Manua' *n Codes# +o'ume 1.1# WMO 3o' O6K loc! # )a*"e 1+: "oc? 2 fie"ds Field Description Format o&s hour 7' 5he nominal o&ser"ation time 7' numeric) 66;O ;' 5he nominal forecast time ;' numeric) 66;O O' 1 coded "alue indicating the num&er of &ulletins to prepare per da# O' the +ist 2ox attached to this field gi"es the other options including P hourl# M451R and ad hoc !P4C, indicators rtd ind 5he next letter to use as the 222 indicator for R451RD &ulletins 7 @ next &ulletin is the first edition 1 Q : CMSS Sstem Mana!ement "uide# version 2.$ Page 63 Circuit Contro' Field Description Format cor ind 222 letter for CORR4C54D &ulletins 1 : first edn hour) min 7' the time after the nominal o&s time when the first edition is prepared ;' 5he time &efore the nominal forecast time when the first edition is prepared numeric 66;O hours) multiples of 7< minutes first rtd hour) min 5he time of the first R451RD &ulletin) relati"e to the nominal o&s or forecast time 1s for first edn (see a&o"e) 5ote -or o&s time) rtd must &e greater than edn -or forecast time) rtd must &e less than edn prep hour) min) da#) month) #ear 5he time of the last &ulletin prepared Default for a new &ulletin is 66?66 67/67/>< loc! $ )a*"e 1(: "oc? 3 fie"ds Field Description Format ,rr ind -lag to specif# if this station reports regularl# or not " @ regular I @ irregular station num&er 7' WMO station identifier ,iiii 7' II @ 2lock 3um&er (refer to 0olume 1 of WMO 3o >) iii @ !tation ,ndex refer to !ection D of WMO 3o O6K ;' ,C1O location indicator for -M7<) 7K and <7 ;' CCCC "alid time -or -M<7 onl#) defines the "alidit# time for routine 51-s 3umeric 66 ;L hours 8u$$etin #unctions Function ' @ &nter searc! data $ith the 67, in 1nter Ruery ModeJ you may enter searh data into "oc? 1. '. %ress the -un the Buery button to interrogate the database tables to find reords whih math the searh data. Page 64 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' ,f one or more reords are foundJ the first one is displayed and the 67, returns to Normal Mode. ,f no math is foundJ the 67, stays in 1nter Ruery Mode. Sou may try hanging the data entered or press the C"ear or -estore buttons to return to Normal Mode. Function - @ (dd a new bulletin Sou an add a new bulletin by using either of two methods. Method 1 > Create a comp"ete"y ne# *u""etin '. MaAe sure the fous is in "oc? 1 O that isJ the ursor is in one the of the fields in "oc? 1. ,f the fous is in "oc? 2 or "oc? 3 then only that bloA will be affeted by the ompletion of step 2. 2. %ress the Insert or C"ear button to lear the urrent bulletin. All the fields on the form will be leared and the fields in BloA ' will hange to white to indiate they are ready to be filled with new data. Method 2 > Copy an e4isting *u""etin of the same message type '. MaAe sure the fous in is "oc? 1. 2. %ress the Copy button to bring a new window. "he system displays a new window with the ""AAiiJ CCCC and bulletin number of the original bulletin and all the other information from "oc?s 1J 2 and 3. ). Change the bulletin number to an unused number. Modify the ""AAii and CCCC if neessary. %ress ;1. Function . @ Modify and e%isting bulletin .untion ) allows you to# 0elete the urrently displayed bulletin from "oc? 1 0elete obs times from "oc? 2 Add new obs times to "oc? 2 0elete station numbers from "oc? 3 Add new station numbers to "oc? 3. Cote: Any hanges made to bulletins must be saved or leared before any other ations an be performed <M, )ata$ogue "he $M4 Catalogue is a list of all bulletins prepared by member ountries for distribution on the 6"-. CMSS Sstem Mana!ement "uide# version 2.$ Page 65 Circuit Contro' Most of the information re:uired for the Catalogue is already part of the Bulletin system Q the e!tra information is entered via the $M4 +ol C panel on the Bulletin 67,. .or bulletins that are generated by the Bulletin systemJ eg -SN4%J the "imegroup and Content fields are automatially alulated from the 4bs "imes(-tations panel and so are not modifiable. .or other types of bulletinsJ eg .4*1CA-"- and $A*N,N6-J these fields must be entered manually. "he information on the Compiling Centre may also be updated by using the 1dit Centre option. .or more information on the $M4 Catalogue refer to the appropriate $M4 0ouments. !igure 11: <M; Cata"ogue ,rac$e %ata7ase 6a7$es "he information needed to ompile and onstrut $M4 bulletins is stored in a series of 4rale 0atabase tables. 0uring Message *eognition ertain fields are e!trated from the report whih are used as Aeys into the database tables. "hese fields are the station number or identifier stn@numJ the report type msgtypeJ the observation time o*s@hour. Page 66 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' stndsr- "his table ontains the list of stations for eah fi!ed bulletin. 1ah bulletin has a uni:ue identifying number or *u"@num. "here is a many to many relationship between stn@num and *u"@num. Cote: .or normal format bulletins a dummy stn;num of 33333 is used. bulnd%- "his table ontains the list the observation times for eah bulletin. "he standard obs hours are 00 to 2). "he o*s@hour an also be oded as a two5digit number between 30 and 33. 0 K no bulletins "his is used speifially for -%1C, bulletins whih have no fi!ed ompile timeJ but are issued immediately a report is reeived. 1 Q one bulletin at 00N 2 K two bulletins at 00N and '2N 3J 'J +J & similarly at e:ually spaed intervals.Z ,$ Q half hourly M1"A* bulletins ,, Q hourly bulletins Q used for AM0A*J M1"A* et "his field is used differently for C&,MA" bulletins Q here the seond digit represents the day of the month to issue the first edition. bulnd%. .or eah stn;numJ msgtypeJ bul;num in stndsr2J and obs;hour and bul;num in *u"nd42J there is an stn;numJ msgtype and obs;hour reord in *u"nd43. "he te!t of a report from a fi!ed station at a partiular observation time is stored in this table. bulnd%2 "his is a dynami table whih ontains the te!t of reports to go into normal format bulletins. "he reports are stored using *u"@num and o*s@hour as a Aey. "here an be any number of reports for a bulletin. $hen the reports have been ompiled into a bulletinJ the reords are deleted. CMSS Sstem Mana!ement "uide# version 2.$ Page 67 Circuit Contro' tafstns "his is the e:uivalent of *u"nd43 for "A. reports. "A. reports are more ompliated than other observation type reports sine they are foreasts for a period of time in the future. 1ah station has a set of e!peted reporting times and a routine valid time period alled stn_valid_time. .or eah stn;num and bul;num in stndsr2 and obs;hour and bul;num in *u"nd42J there is an stn;numJ valid;start and valid;end reord in tafstns. "he valid_start is the obs;hour from *u"nd42. "he valid;end is valid;start E stn;valid;time. $ey Fields in t!e tables "he following table desribes the Aey fields in the bulletin tables# )a*"e 1&: u""etin ta*"e ?ey fie"ds Table name $ey fields Content &ulndx7 &ul8num Char(L) Msgt#pe Char(;) &ulndx; &ul8num Char(L) o&s8hour Char(;) &ulndxO Msgt#pe Char(;) o&s8hour Char(;) &ul8num Char(L) stndsr; stn8num Char(<) Msgt#pe Char(;) &ul8num Char(L) &ulndx< &ul8num Char(L) O&s8hour Char(;) tafstns stn8num Char(<) "alid8start Char(;) "alid8end Char(;) Page 68 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' System Monitoring Functions <atch!og Process CM-- inludes a $athdog proess. ,ts funtion it is to heA the health of the system as follows# ,t heAs that all other proesses are running ,t heAs that Aey files are being updated. ,f a proess fails then the $athdog restarts it and raises the following alarm# WAT900I ERROR - PROCESS xxxx NOT RUNNING - RESTARTING IT ,f the same proess fails repeatedly then the $athdog stops trying to restart it and instead raises the following alarm every two minutes. "he number of times the $athdog restarts a proess is onfigurable. WAT008A SERIOUS ERROR - PROCESS xxxx NOT RUNNING ,f a line driver proess is not running the alarm ontains the iruit =***CC> for whih the driver has failedJ whereas for non5driver proesses the alarm ontains the atual proess name . "he differene is beause multiple line driver proesses with the same name an be running at any one time =one for eah iruit>. "he files that are monitored are# MSGICJ input messages file MSG;:)J output messages file -A%;-)SJ reports file =onstruted from M-6,N messages>. ,f one of these files is not updated for a speifi time periodJ an alarm is raised as follows# WAT026A WARNING: xxxx FILE HAS NOT BEEN WRITTEN TO RECENTLY WAT027A WARNING: xxxx FILE HAS NOT BEEN READ RECENTLY $here !!!! K M-6,NJ M-647" or *1%4*"- "he time periods used to heA these files vary from entre to entre. "hey are passed as ommand line parameters to the $athdog. 4ne reason for periodially heAing these files is to detet if a proess is still running but has gone into an infinite loop. "here will be times when it is not desirable for the $athdog to raise alarmsJ partiularly when installing a new version of a proess. ,n this situation use the CM-- 67, option to instrut the $athdog to stop monitoring the system for '8 minutes as follows. 3dmin II Buiet the <atchdog CMSS Sstem Mana!ement "uide# version 2.$ Page 69 Circuit Contro' Syste" Status "here is a display that allows you to :uiAly heA CM--Ms health. ,t is started by hoosing the ISystem StatusG option on the Misellaneous =UMisI> pulldown on the CM-- 67,. Amongst other thingsJ this display shows the number of messages proessed and the health of Aey proesses. "hese Aey proesses are displayed in greenJ amber or red depending on how :uiAly messages are being proessed. .or LMessage AnalysisM =msganal> the display is red if data is waiting but nothing has been proessed for 2 seonds. .or the L*eogniPerM =reogn> the display is amber =aution> if data is being delayed for more than 8 seonds or if the number of messages waiting e!eeds '00. "he display is red if messages are delayed for more than )0 seonds. .or LMessage -withingM =msgswth> the display is also amber if the delay e!eeds 8 seonds or '00 messages and the display is red if the delay e!eeds )0 seonds. !igure 12: CMSS status G:I Page 70 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' 4ine "onitor A &ine Monitor proess =cm"nmon> is used to warn if messages are not being reeived or sent on Aey iruits. An 4rale table is used to define when data is e!peted for eah iruit. ,f data is not sent or reeived during this period then an alarm is raised# .or e!ampleJ LMN007A NO TRAFFIC DETECTED ON RRRCC FOR 60 MINUTES where ***CC is the name of the onnetion. "he table an be aessed from the CM-- 67, as follows# )a*"es II System@Config@)a*"es II 2ine Monitor. "he underlying table is alled time@outJ and is strutured as follows# )a*"e 1,: time@out structure 5ame 5ull> Type C,RC/,5 3ot null Char(<) !51R585,M4 3ot 3ull Char(L) D/R15,O3 3ot 3ull Char(L) -"A*";",M1 K "he time hour(minute =hhmm> at whih monitoring for this iruit is to begin. 07*A",4N K "ime =in minutes> that is the ma!imum time e!peted between messages before an alarm is raised. A duration of 0000 means do not raise an alarm for this iruit. An e!ample of the entries for a onnetion is# CIRCUIT = XXX01 START_TIME = 0000 DURATION = 0060 CIRCUIT = XXX01 START_TIME = 0600 DURATION = 0120 "his means for iruit ???0' from 000050<007"C at least one message is e!peted every <0 minutes. .rom 0<00500007"CJ one message is e!peted every '20 minutes. .or any onnetion =iruit>J multiple entries an be inluded to allow for variations in the antiipated data flows during the day. CMSS Sstem Mana!ement "uide# version 2.$ Page 71 Circuit Contro' Database Tables CM-- database tables are owned by the database user cmop. "he table names are heAed as follows# sqlplus cmop select * from tab;. "his should give a list similar to the following# )a*"e 20: cmop ;rac"e ta*"es T5(M& T(BT<P& C?UST&"ID 1,R+OC 5a&le 1+1RM8512 5a&le CM!!,3 5a&le -,+4D4!C 5a&le .RP1DDR! 5a&le .RPD4!C 5a&le +,34-M5 5a&le +,34!8,3 5a&le +,34!8O/5 5a&le M451R 5a&le M!.85127 5a&le P+134,D 5a&le !4CO3D1RJ8O/5 5a&le !53D4!R7 5a&le !53D4!R- 5a&le 5,M4O/5 5a&le "he Aey tables =lines;inJ lines;outJ buldesr et> are desribed earlier in this setion. 4ther important tables used by CM-- are# Page 72 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' )a*"e 21: ;ther important ta*"es used *y CMSS Table Content Description airloc 1,R4P (aircraft reports) locations 5his ta&le details the lat/long of e"er# significant point used in 1,R4P messages %owe"er) man# 1,R4P reports contain a location indicator (sig point) rather than a lat/long' 5his ta&le determines the lat/long to generate reports for displa# and/or plotting ,f a message is recei"ed with a sig point that is not in this ta&le) an operator alarm is raised alarm8ta& 1larm Documentation 5his ta&le contains an explanation of the alarms generated &# CM!! All tables are aessible from the CM-- 67,. CMSS Sstem Mana!ement "uide# version 2.$ Page 73 Circuit Contro' Management Facilities Management failities that have little system overhead and are re:uired by a range of people are $eb based. ,f however something involves signifiant proessing then it must be run from the 3dmin pulldown on the CM-- 67,. 4ine-$oa!ing an! !e$ay Statistics CM-- an optionally save statistis about the number of bytes of dataJ and the number of messagesJ sent and reeived on eah iruit at ten5minute intervals. "hese statistis an then be displayed via a simple $eb based interfae. "his option may be useful in determining trends in data volumes and determining when a line upgrade is re:uired. "his system also reords and displays pea? and average swithing delays in CM--. "hat isJ it reords the delay from the time CM-- reeived a message to the time it started sending it. "he swithing delay graph an displays either the peaA or average delay at '0 minute intervals. Note# "he swithing delays are reorded in seonds but most delays are less than one seond. "his means that the average delay figure is not e!at "he proess that produes the raw statistis is "inestats. ,t stores the raw statistis in a ompressed form in the diretory $CMSS/linestats. Although the old statistis files do not taAe up a lot of disA spaeJ it may be advisable to periodially remove them using ron. Page 74 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' !igure 13: CMSS "ine9"oading statistics (ea$-6i"e Monitoring o. ,7ser3ations "here is a omprehensive $eb based 67, to monitor the observing networA. "he 67, displays inlude# '. -ummary of observations reeived and missing 2. "ime of reeipt of eah observation with earlyJ late and missing observations highlighted. ). 0etails of missing observations "o operateJ this system must Anow the reporting program of eah station to be monitored. "here are two options for defining the reporting program# CMSS Sstem Mana!ement "uide# version 2.$ Page 75 Circuit Contro' '. Many entres maintain a database ontaining the reporting program. ,n this ase a CM-- utility is used to read the database and store this information for the monitoring program. "ypially this utility is run one per day. 2. "here is a simple CM-- database table that an be used to define the reporting program. ,t is aessible via the CM-- 67,# )a*"es 9G System Config )a*"es 9G ;*servation %rogram "he raw statistis are produed for the $eb by a CM-- proess alled DataMon whih updates the statistis files every minute. "here is another proess alled Data-e.uest whih send re:uests for missing observations to the sender. "ypially this proess needs to be ustomiPed for eah installation beause the proedures for obtaining missing data will vary aording to the sending devie used. !igure 1': -ea"9)ime o*servation monitoring G:I Page 76 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' Sur3ey Progra"s 9<M, Sur3ey: .or international entres there is a $M4 re:uirement to provide data on the reports sent and reeived by the entre over a given period =typially '5'8 4tober>. A CM-- proess alled survey produes the raw statistis for the $M4 survey. "he statistis produed by survey are typially stored in the =CMSS/survey diretory. "he reports re:uired by $M4 an be reated from the <M; Survey menu in the CM-- 67, 3dmin pulldown. Procedure to produce )M* Sur#ey '. Normally you will first need to obtain the A-C,, versions of the $M4 *B-N files and store them in the appropriate CM-- diretory. Normally the CM-- diretory is# FCM--(survey(yyyy(*B-N yyyy K year =eg 200'> *B-N stands for *egional Basi -ynopti NetworA. 2. ,n the CM-- 67, set the field BDirectory containing -SC fi"es#C ). -et the date(time period for whih the survey is to be run. /. %ress the U-un SurveyI button. "he survey reports ould taAe up to '8 minutes to produe. $hen they are ompleted a CM-- alarm is raised of the form# ELLL <M; S:-NAR %-;G-3M C;M%2A)AD LLLF 8. Sou may then use the INie# ;utputG button to looA at the results in the diretory# =CMSS/survey/yyyy <. Normally you will then need to send the files to $M4. "he easiest method is to ."% them to ###.#mo.ch Procedure to obtain "BS5 files 1very year before the annual survey you will need to obtain the latest *B-N files from $M4. "he proedure to obtain these files is# '. d FCM--(survey(yyyy(*B-N 2. ftp www.wmo.h ). =user5id K anonymous> /. d 6"-;monitoring(A6M(.rom;$M4 8. d SS =year in digits> CMSS Sstem Mana!ement "uide# version 2.$ Page 77 Circuit Contro' <. d *B-NSSm =SSK year in digits. M K '..C =month>> 9. mget H.A-C Procedure to send results to )M* 4ne method for sending the results to $M4 is via ."% as follows# '. Change into the diretory where the results files are stored# 1g cd =CMSS/survey/yyyy 2. ftp www.wmo.h ). =user5id K anonymous> /. d 6"-;monitoring(A6M("o;$M4 8. d SS =year in digits> <. Create diretory to store your results in# m?dir CCCC.RRm =CCCC K your entre. SSK year in digits. M K '..C =month>> cd CCCC.RRm 9. Create sub5diretory for the survey period Q normally 4tober =LAM> 0'5'8. m?dir G30131$.3SC cd G30131$.3SC 2. -tore all the results files in this diretory# mput D.asc Cote: By defaultJ old statistis are not removed from the $CMSS/survey diretory. ,t is advisable to set up a ron Dob to remove old statistis files. Page 78 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' CMSS Sstem Mana!ement "uide# version 2.$ Page 79 Circuit Contro' "eAuest+"epeat Facility CM-- an automatially issue re:uests for missing messages based on breaAs in se:uene numbers. -imilarly CM-- an respond to orretly formatted re:uests for missing messages based on the $M4 and A."N standards. Sen!ing (e=uests .or "issing !ata .or those inoming iruits that use se:uene numbersJ this number is immediately heAed when eah new message is reeived =by proess# msgana"8. ,f there is a breaA in se:uene number then the line onfiguration is heAed =lines;in table> to see if this iruit supports $M4(A."N re:uests for missing data. A re:uest for repetition is only issued if the breaA in se:uene number is less than 100. A ma!imum of five 7$8 re:uests for repetition are sent on a iruit per hour. "his is to try to limit re:uests when a iruit is faulty. ,f a re:uest for missing data is N4" sent automatially then a CM-- alarm is generated so that an operator an taAe manual ation if re:uired. (es&on!ing to (e=uests .or "issing !ata $M4 re:uests for repetition messages use a speial heading Q ""AA,, K LBMM or LB,MJ and the message te!t is a set format. ,noming *e:uest messages are swithed to the CM-- Service !i"e via the normal 6"- Bulletin -withing "able =buldesr>. A."N re:uests for missing data are normally sent to a speial A."N address or start with ESNCF. Again these messages are automatially swithed to the Service !i"e. "here is a CM-- proess alled cmre.uest that heAs eah message that is added to the -ervie .ile. ,f the message is a standard $M4(A."N re:uest for missing data then this proess finds the re:uired messages and sends them baA to the originator. ,f Bmre:uestC annot find the re:uired data or annot interpret the message then it raises a speial 4perator alarm Q A -ervie Message Alarm. Note# mre:uest uses fields defined in the lines;in table to determine where to send the found messages. ,f these fields are not set then mre:uest simply issues a -ervie Message Alarm Page 80 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' Miscellaneous Priority Sche"e CM-- uses a four level priority sheme Q LAMJ LBMJ LCM and L0M. LAM is the highest priority and L0M is the lowest. L0M is also the default. $hen sending messages to the A."NJ CM-- onverts its priorities to A."N priorities as follows# A 00 B .. C 66 0 66 >an!$ing <M, 64 )harts $M4 "/ harts are stored as fi"es. "hey are however swithed on $M4 header =""AA,, and CCCC> liAe all other 6"- produts. A ommon re:uirement is for "/ harts to be onverted into an image format =eg gif> suitable for viewing via $eb pages. "his is ahieved in CM-- by swithing these files to a speial output iruit that an be onfigured to onvert the harts to gif and store them in a designated diretory. 4ne problem with "/ harts is their orientation. "hese harts an be reeived upside down or at some other orientation and there is no way for CM-- to determine this. "o overome this problem there is an 4rale "able that allows you to define for eah hart =""AA,, and CCCC> how it is to be rotated when it is onverted for the $eb. )a*"es GG Misce""aneous )a*"es GG C63-) -;)3)I;C )a*"e "his table ontains three fields# ""AA,,J CCCC and rotation. "he rotation field an have four values# 0 K no rotation ' K 30 rotation 2 K '20 rotation ) K 290 rotation Cote: "/ harts are always displayed un5rotated in CM--. "he rotation only ours when the hart is onverted to gif. CMSS Sstem Mana!ement "uide# version 2.$ Page 81 Circuit Contro' 1gnoring Se$ecte! Messages ,t may be neessary to ignore seleted messages based on ""AA,, and CCCC. "ypially this is used to filter inorret observations and messages reeived from broadast systems. 7se this as follows# '. -et the BIgnore se"ected <M; messagesF option in the System %arameters display in the CM-- 67,. 3dmin GG System %arameters 2. Add the ""AA,,(CCCC of the messages to be ignored in the appropriate database table# )a*"es GG Misce""aneous )a*"es GG IGC;-A <M; MASS3GAS Cote: By default this faility is disabled =in -ystem %arameters> as it an plae a signifiant overhead on the system as every reeived message is heAed to see if it should be ignored. %robably this faility will be e!tended so that only seleted iruits are heAed =eg the satellite broadasts> to redue the system overheads. Ser3ice Messages "here is a speial address BMCSCF that is used to swith messages to the -ervie .ile and to ause an 4perator alarm to be generated of the form# SNC002I SA-NICA MASS3GA 3) nnnnn "ypially you use the 6"- -withing "able to swith all $M4 administrative and re:uest messages to BMC-CC. Printing #aci$ities "here are two methods for printing to a &AN printer from CM--# '. 7sing the CM-- 67,. 2. -etting up a destination iruit(address for a printer. Page 82 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' Using t!e CMSS GUI to print '. -elet the %rint button from the !i"e pulldown menu on the CM-- 67,# !i"e II %rint. Cote: "his %rint option allows you to print the &ogJ JournalJ or Alarm page being displayed or to print the urrently displayed message. -ome displays O for e!ampleJ Circuit Contro"J annot be printed. By defaultJ the %rint option prints to the default printer as defined by the server. Change the default printer by setting the 7ni! environment variable =CMSS@%-IC)A-. AlternativelyJ to hange the printer in the urrent 67, sessionJ set the %rinter Came te!t field in the print menu displayed when seleting the %rint button. Cote: "he printer name that is to be seleted must be defined in the 7ni! -erver. Setting up a destination circuit+address for a printer Nine5harater CM-- addresses an be linAed to real printers to allow messages to be routinely sent to these printers or to be oasionally resent to them. Normally this is setup from the CM-- 67,# )a*"es II %rinter Definition "he B%rinter 0efinition#C table ontains three fields as follows# )a*"e 22: %rinter definition ta*"e 5ame Type 1ddress char > CM!! address Printer Definition Char 1ctual /nix printer name Paper !iDe 1L/1O Defaults to 1L ,n CM-- the printer addresses are linAed to a speial outgoing onnetion referred to as %-IC). "he assoiated driver proess issues a 7ni! "p ommand to the speifi printer address. Cote: All the printers defined are assumed to be &AN onneted printers apable of handling both %ostsript and A-C,, te!t. .or some other CMSS Sstem Mana!ement "uide# version 2.$ Page 83 Circuit Contro' data types =for e!ampleJ $M4 "/ fa!> CM-- automatially onverts the data into %ostsript for printing. 0se o. share! "e"ory CM-- maAes e!tensive use of shared memoryJ whih it alloates as re:uired when the system is started. "he program that alloates -hared Memory is alled cmssmem. ,t is run from the startup sript rc.cmop. $hen cmssmem is e!euted by rc.cmopJ it is told the ma!imum number of input and output lines that may be onfigured O for e!ampleJ cmssmem =CMSS 9create '0 $0. "his reates enough shared memory to support /0 inoming lines and 80 outgoing lines. "o inrease the number of input or output lineJ do the following# 2. Change the cmssmem parameters in rc.cmop to the appropriate values. -hut down CM-- =stopcmss ommand>. ,ssue the following ommand to delete the urrent shared memory bloA# cmssmem =CMSS 9de"ete *e5start CM-- 7rc.cmop>. Cote: 4ther cmssmem parameters allow the urrent bloA of shared memory to be displayed. Page 84 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' $ey Processes and Files )MSS Processes "he main CM-- proesses are# )a*"e 23: 1ey CMSS processes Process Description Msganal Checks all incoming messages? 0alidates headers and trailers Checks se$uence num&ers and sends re$uests for missing messages (se$uence num&er errors) 4liminates duplicate messages Creates director# information' Recogn Recognition process? ,solates all reports within each message and writes reports to "&P*"TS file !a"es station num&er and report t#pe of each report 4liminates duplicate reports from decoding and &ulletin production !a"es information for 2ulletin Production !ends immediate retard and correction &ulletins for the .5!' Msgswtch Message !witching process? Determines destination addresses/connections for outgoing messages Fueues messages for transmission according to relati"e priorities' Msgprep Message Preparation (for outgoing messages)? One msgprep is run per output connection Reads next message from output $ueue and adds appropriate %eader and 5railer Passes next message to the Dri"er %andles !tart and !top commands' Rdri"ersS 0arious names ( for example) tcpsend) tcpin /sed to send or recei"e messages %andles Close and Open commands Watchdog Monitors the other processes Cmlnmon Monitors data transmission on the connections' CMSS Sstem Mana!ement "uide# version 2.$ Page 85 Circuit Contro' Process Description :ctnmain Controls the 4xecution +ist (xctnlist) cmre$uest ,ntercepts !er"ice Re$uests from other centres (incoming connections) and tries to respond to them automaticall#' ,n particular it handles 1-53/.5! re$uests for repetition of messages &ased on se$uence num&er or 5511,,/CCCC' Cm"iew 1utomaticall# con"erts selected files ( for example) Postscript files) into images that are "iewa&le (%bm)' /sed to make displa#ing selected files in the ./, $uicker' cmfileclean Remo"es old files ( for example) Postscript files) from the s#stem after an agreed time' 2ullTo& !tarted periodicall# from the 4xecution +ist' Produces first editions and first retards of WMO/.5! &ulletins' !ur"e# !a"es information on incoming messages for use in WMO sur"e#s DataMon /ses the o&ser"ation program pro"ided to sa"e information a&out what o&ser"ations are recei"ed and when DataRe$uest /ses the information sa"ed &# DataMon to re$uest missing data from the source or to notif# the Operators or other users' +inestats !a"es information a&out the num&er of &#tes of data sent and recei"ed per connection' )MSS Process ,&tions "o determine all the ommand line startup options for a proess then run the proess with no options at all. "his auses the proess to list its options and then terminate. "his an be very useful for many proessesJ inluding the &ine 0rivers. .or e!ample# G tcpsend tpsend 0ir rrr [5d\ [5\ [50\ [5, nnn\ [5b nnn\ [5t nnn\ [5a nnn\ [5w nnn\ 0ir K worAing diretory of program rrr K C4MM- iruit 5, nnn K inative time before all is dropped =in seonds> =default <0 ses> =0 K never drop all> 5t nnn K time between alarms =in minutes> =default '0 minutes>=0 K no alarms> 5a nnn K "ime that that new alls fail before raising alarm =in minutes> 4nly used on slow linAs. 0efault is to alarm aording to ]5t] Page 86 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' 5bnnn K set buffer siPe at this value =default /03<> 5d K dummy modeJ simulate transmission 5 K lose soAet after eah message 50 K put diagnosti messages to stdout 5w K wait in seonds after onnetion before sending Message re$ate! .i$es "he names of message related files are# )a*"e 2': Message re"ated fi"es 5ame Description Msgintxt !tore text of all messages Msgindir M!.,3 director# file Msgotdir M!.O/5 director# file Recogdir R4POR5 director# file !er"ice !4R0,C4 director# file Re$uest Related to !4R0,C4 file ReTect R4N4C5 file 1ddrdir 1ddress extension director# Out$ Output $ueue file (out$) Cote: "he Address e!tension diretory =addrdir> is used to save addressing information for iruits where there an be many addresses Q eg .A?J e5mail and A."N. Circular files 4ther irular files are# )a*"e 2$: Circu"ar fi"es 5ame Description 1larm Communications alarm file 1larmd Message Decoding alarm file CMSS Sstem Mana!ement "uide# version 2.$ Page 87 Circuit Contro' 5ame Description +og Communications log file +ogd Message Decoding log file Nournal Raw Tournal file Nournald -ormatted Tournal file "o re5reate filesJ use the following ommands# )a*"e 2+: !i"e re9creation commands Command Description 3ewtext Create the message text file Createdir Creates a message Director# file CreElogc Creates a log file (or Tournal) alarm) Out$init Creates the Output Fueue file "he 4utput Rueue file =out.> is the most internally ompliated file. Page 88 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' Database Interface 4ne of the Aey funtions of CM-- is to store deoded reports in the 0atabase through the use of deoder proesses. %eco!er Processes "he standard deoder proesses are# )a*"e 2(: Standard decoder processes Process Description Decoder (DCD67) Decodes most WMO character &ased codes' .ri&ingest (.R267) Decodes WMO .R,2 messages 2ufringest (2-R67) Decodes WMO 2/-R messages CM-- passes harater5oded reports to a deoder proess through the onnetion 0C00'. CM-- an be onfigured to pass all reports to the deoder =e!luding dupliates and others marAed LignoreM> or it an be onfigured to pass only seleted reports. ,f only seleted reports are to be deoded then CM-- heAs eah report(station against a table alled the Station Dictionary. 4nly if the Store flag is set for the station is the report deoded. "he -tation 0itionary ontains a list of all Anown stations and their details O for e!ampleJ latitude(longitude. G-I and :!- message are only sent to their respetive deoders if they are e!pliitly addressed to them in the -withing "ables 7*u"desr8. Cote: ,f reports from a partiular station are not being deodedJ heA that the station is in the -tation 0itionary and that it indiates this stationMs data is to be stored. *efer to the Station<ictionar! S!stem Management Guide. CMSS Sstem Mana!ement "uide# version 2.$ Page 89 Circuit Contro' ?anguage Support By default the CM-- 67, displays information in 1nglish. "here is however a proDet under way ='3(3(02> to allow this information to be displayed in other languages. "his will eventually inlude the 3"arm and 2og messages and the ;rac"e G:I. "here are three options for hanging the language displayed on the CM-- 67,# '. "he -ystems Administrator an set the default language for all users via the G:I %arameters menu on the 3dmin pulldown. 2. 1ah user an set the language for their 7N,? aount via the G:I %arameters menu on the Misc pulldown. ). 1ah user may toggle between different languages dynamially via the 2anguages menu on the the Misc pulldown 6rans$ation Metho! "he language translations are performed using the 6N7 gette!t toolAit. "his re:uires a file to be setup that ontains the 1nglish language strings used by CM-- and the e:uivalent foreign language strings. 1ah 1nglish string in the file is preeded by the word msgid and the string is enlosed in :uotes. "he foreign strings are preeded by msgstr and enlosed in :uotes. .or e!ample# msgid ^1!it^ msgstr ^-alida^ msgid ^C&1A*^ msgstr ^C&A*4^ ,f a string ontains multiple lines then plae a E[nF at the end of eah line. msgid ^%ressing the print button auses the information to be printedZn^ ^immediately =to a &AN %rinter>.ZnZn^ msgstr ^MeneAan tombol C1"AT menyebabAan informasi dietaA segeraZn^ ^=Ae printer(penetaA di &AN>ZnZn^ ,f the non51nglish string ontains speial haraters then these need to be defined in he!adeimal 7[4nn8. msgid ^More ..^ msgstr ^MZ!e's ..^ Page 90 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' 6rans$ation #i$e %irectories "he translation files are ontained under the =CMSS/"oca"e diretory. ,n the loale diretory there is a sub5diretory for eah foreign language defined. .or e!ample# =CMSS/"oca"e/es/2C@MASS3GAS =-panish> =CMSS/"oca"e/id/2C@MASS3GAS =,ndonesian> $ithin eah of these diretories should be two files# '. cmssgui.po 5 1ditable file ontaining the msgid(msgstr strings e!plained above. 2. cmssgui.mo Q Mahine readable file used by CM-- to perform the translations )hanging a $anguage trans$ation "o hange a translation simple edit the appropriate cmssgui.po file and then run the following ommand# msgfmt Mo cmssgui.mo cmssgui.po "his ommand reates the mssgui.mo file that CM-- uses from the mssgui..po Cote: Always taAe a baAup opy of the mssgui.po file before you edit it. eg cp cmssgui.po cmssgui.po.1,0,2002 Cote# @aving reated the mssgui.mo file you must then restart the CM-- 67, to see the hanges. "hat isJ the CM-- 67, only reads the mssgui.mo file when it starts. 4anguage trans$ation restrictions $herever possible the CM-- 67, tries to hange the siPe of labels and buttons to handle the hange in the siPe of words or sentenes when the language is hanged. @owever sometimes this is not possible. .or e!ample the large buttons are limited to '' haraters in length so sometimes some e!perimentation or abbreviation is re:uired when replaing an 1nglish word with the foreign e:uivalent. CMSS Sstem Mana!ement "uide# version 2.$ Page 91 Circuit Contro' Message (rc!i#e 0etails of the CM-- Message Arhive system are ontained in a separate doument. "he Aey points are# '. "he -ystems Administrator hooses the data to be arhived from the 3rchive ;ptions menu in the 3dmin pulldown on the CM-- 67,. 2. "he seleted data is arhived every minute. ). )he archive shou"d *e on a separate fi"esystem. "his is to avoid problems if the arhive fills the filesystem /. -ome proedure =automati or manual> is re:uired to move old data from the arhive filesystem to an e!ternal storage devie =eg C0 or tape> before the filesystem fills. 8. 1ah monthMs data is stored in a separate diretory. 1ah days data is stored in a separate file <. Normally the arhive data is made viewable via a $eb page interfae. Page 92 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' Installation Procedure A standard CM-- installation is very easy to perform. @owever if a high data volume and high performane system is re:uired then are needs to be taAen partiularly with the setup of disAs. CM-- should always be installed on one or more separate disA partitions. Sou should not install non5CM-- systems on the same disA as CM-- as they may fill the disA and prevent CM-- from running. 0epending on data volumes and the number of days data that you re:uire online then CM-- re:uires at least 'G* An 4rale database should be installed before CM--. '. ,nstall 4rale on a separate disA. "ypially 4rale re:uires 29'G* 2. -etup the standard CM-- 4rale tables. ). ,nstall the following standard tools for CM-- and add them to the default path ,mageMagiA# '. gette!t 2. gs =ghostsript> ). onvert =,mageMagiA> /. gnuplot /. Create the master CM-- 7N,? aount 5 EcmopF. %ut BmopC in a group alled BcmssF. 8. "he home diretory for the BmopC aount should be the base of the separate CM-- disA partition. <. Create the home CM-- diretory. "ypially this is# Hcmop/cmss 9. ,n the BmopC aount define an environment variable =CMSS that points to the home CM-- diretory. 1g e4port CMSSQHcmop/cmss 2. ,nstall the CM-- e!eutables and installation sripts in the FCM-- diretory from the supplied tape or C0. cd =CMSS tar 4v .. 3. "he tar ommand will install files in several diretories under FCM--. bin CMSS Sstem Mana!ement "uide# version 2.$ Page 93 Circuit Contro' tools install loale '0. Add the BbinC and BtoolsC diretories to the %A"@ for mop. e4port %3)6Q=%3)6:=CMSS/*in:=CMSS/too"s ''. Create the CM-- data files et by running the onfiguration sript. "his sript will prompt for various information. cd =CMSS/insta"" ./configure Cote: ,t is reommended that initially you alloate '0V of the CM-- spae to the M-6,N te!t file and 2V of the spae to eah of the M-6,NJ *1%4*"- and M-647" files. "he M-6,NJ *1%4*"- and M-647" files are speified in terms of number of messages to be stored with eah message re:uiring about 220 bytes so the number of messages is spae(220. Cote# ,t is better to maAe the files small initially and to grow them via the 67, interfae. ,t is muh more diffiult to redue the siPe of files. Page 94 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' Note# '2. ,f the onfiguration fails beause of insuffiient disA spae then delete all the files from the FCM-- diretory and re5run the onfigure sript. '). As root symbolially linA the CM-- 67, defau"ts fi"e into the (usr(lib(?''(app5 defaults diretory "n Ms =CMSS/5Mcmss@sma"" 5Mcmss@sma"" '/. CustomiPe the two files that define the onfiguration of two of the CM-- 67,Ms pu""do#n menus '. 5%:22D;<C@Misc =Mis pulldown> 2. 5%:22D;<C@)a*"es ="ables pulldown> '8. "he installation proedure will have plaed a default CM-- startup file =r.mop> in the FCM-- diretory. 1dit this file as re:uired. vi =CMSS/rc.cmop '<. Customise the CM-- onfiguration file cmss.params as re:uired. 0o this by either editing the file diretly or by running the 67, 4cmssparams vi =CMSS/cmss.params 4ne#*in cmssparams =CMSS \ '9. Sou should now be able to start a basi CM-- system cd =CMSS ./rc.cmop '2. *un a CM-- 67, on a sreen to looA at CM--. cmss9#in I%@address '3. .rom the CM-- 67, you may now add the re:uired iruitsJ inrease the siPe of Aey files and hange other information =via the B-ystem %arametersC 67,>. 20. .or systems with multiple disAs and with high performane re:uirements it is very desirable to share the ,(4 aross multiple disAs. 0o this as follows# '. shutdown CM-- =stopmss ommand> 2. Move seleted files and diretories to the other disAs and symbolially linA them baA to FCM-- mv =CMSS/fi"ename /ne#dis?/fi"ename "n Ms /ne#dis?/fi"ename =CMSS/fi"ename ). "he most heavily used files and diretories are the ones that you should onsider moving. "hese inlude CMSS Sstem Mana!ement "uide# version 2.$ Page 95 Circuit Contro' BproductsF diretory =used to store all files and depending on the system may be very large> out. Q output :ueuing file msgin4t Q raw message te!t msgindir Q diretory of information about inoming messages msgotdir 5 diretory of information about outgoing messages Yourna" Q summary of messages sent and reeived Page 96 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' Fa% Deli#ery !igure 1$: CMSS fa4 system 1ntro!uction A separate fa! software produt alled @ylafa! is used to send fa!es to ustomers. @ylafa! is a freeware produt. ,t is supplied with e!tensive @"M& doumentationJ whih is stored in the htdocs sub5 diretory under the main @ylafa! diretory. "he @"M& doumentation an also be viewed at# http#((www.vi!.om(hylafa! @ylafa! is also supplied with man pages stored in the @ylafa! man sub5diretory. "he following @ylafa! users e5mail list enables subsribers to ommuniate and disuss @ylafa!5related problems# fle!fa!Ysgi.om CMSS Sstem Mana!ement "uide# version 2.$ Page 97 Circuit Contro' Fa% data flow CM-- passes messages to @ylafa! through the .A?0' iruit. ,t provides @ylafa! with the message to be sent and the destination telephone numbers by issuing a @ylafa! sendfa4 ommand. By defaultJ @ylafa! will fa! messages in the following formats# A-C,, =te!t> %ostsript .a! format Cote: @ylafa! may be ustomised to aept other formats. A @ylafa! proess alled hfa4d listens for user ommands suh as sendfa4. $hen hfa4d reeives a message(file from sendfa4 it is stored in a diretory in the form ~cmop/fax/spool/docq. ,t then notifies a seond @ylafa! proess alled fa4.. "he @ylafa! fa4. proess ontrols fa! transmission based on available modems and priorities. "he fa! lines =and fa! modems> are onneted to the &AN by a &AN "erminal -erver. fa4. is notified of the e!istene of a fa! line by a separate proess alled fa4getty. Cote: 4ne fa4getty is run per fa! modem. 1nsta$$ing >y$a.a+ *efer to ;!lafa$ ;(M@ documentation for further details about the @ylafa! installation proedureJ available on the ,nternet at# http#((www.vi!.om(hylafa! . "he basi installation proedure is as follows# '. 4btain the @ylafa! software from the following site# ftp.sgi.com 71,2.'&.1$3.18 directory sgi/fa4. 2. 6o to the @ylafa! soure diretory and issue the following ommands# ./configure ma?e insta"" =must be run as rosot>. Page 98 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' Cote: configure heAs the type of mahine and ompiler. ,t also asAs :uestions about where the system should be set up. ma?e insta"" ompiles @ylafa! and puts e!eutables(files in agreed diretories. ). 1nsure that sys"og will log all @ylafa! messages as this maAes debugging possible. CheA for entry of the following form in /etc/syslog.conf# D.de*ug,mai".none,"oca"0.none /usr/adm/sys"og. ,f this entry is not presentJ do the following# e. Add the entry manually. f. 1nsure the sys"og file e!ists and is readable =touh as root and maAe world readable>. g. 6et the syslog daemon 7sys"ogd> to re5read the /etc/sys"og.conf file 7?i"" 96:% Esys"ogF>. /. Add a fa! user to the systemJ either by hanging /etc/pass#d or using CIS. Cote: "his fa! user must have the same user ,0 =7,0> as uucp and must be after the uucp entry. 8. Add an entry =for the port that hfa4d listens on> to the /etc/services file =or N,-> that @ylafa! will use to reeive user ommandsJ as follows# hy"afa4 '$$,/tcp J 6y"a!35 c"ient9server protoco" At this stage a basi version of @ylafa! may be startedJ however some ustomisation will be re:uired prior to operation. Cote: Most installation problems enountered relate to permission problems on diretories(files. Always heA sys"og if a problem of this nature ours. "he normal @ylafa! installation diretories for are# )a*"e 2&: 6y"afa4 insta""ation directories Files Directory 4xecuta&les Ucmop/fax data files Ucmop/fax/spool CMSS Sstem Mana!ement "uide# version 2.$ Page 99 Circuit Contro' )usto"ising >y$a.a+ "he following onfiguration hanges may be re:uired to @ylafa! after installation. '. *eplae standard @ylafa! te4tfmt e!eutable with the version supplied by BoM =for A-C,, to %- onversion> O textfmt.c++ & bomlogo.h. @ylafa! invoAes te4tfmt by looAing up the typeru"es table in @ylafa! sub5diretory .../lib/fax/typerules. typeru"es inludes the start5up parameters for te4tfmtJ whih inlude the heading te!t and font to be used. "his should be hanged as appropriate. 2. By defaultJ if a fa! transmission fails a set number of timesJ the user O for e!ampleJ cmop is notified by e5mail. ,n CM--J a @ylafa! notify proess raises a CM-- Alarm. Modify the notify command parameter in the @ylafa! onfig file =typially .../etc/config> to all the cnotify proessJ as follows# CotifyCmd: *in/cnotify. ). Copy the cnotify sript and the cfa4notify e!eutable into the @ylafa! bin diretory# (.../bin). /. 1nsure the owner of the e!eutables is the same as that used to run CM--# (chown cmop ..). 8. -et the stic?y *it on the two e!eutables to run under the 7ser ,0 =7,0> cmop and to have aess to the CM-- &og and Alarm files =when @ylafa! invoAes them>J as follows# chmod uog+s cfaxnotify chmod uog+s cnotify Managing the >y$a.a+ Syste" 8ylafa% daemons+processes "he following daemons must be running =as root> for the @ylafa! system to operate# hfa4d handles lient ommands O for e!ampleJ it aepts files to be sent and the destination telephone numbers fa4. is the entral :ueuing agent. ,t is notified by hfa4d of the arrival of a new message(file to be fa!ed. ,t alloates messages to modems and handles retries fa4getty initialiPes a fa! modem and then informs fa4. that a modem is available for use. 4ne opy of fa4getty must be run for every modem to be used. Cote: @ylafa! e!pets the modems to be diretly onneted to the server and to ommuniate with them through ""Ss =/dev/tty..>. @owever in the modems are onneted through a 23C )ermina" Server. "his re:uires a separate daemon 7fa4ptydr> to interfae eah fa4getty to the "erminal -erver port. "his means that if there are '0 modems there must be '0 fa4getty proesses running and ten fa4ptydr proesses. "he fa4ptydr Page 100 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' proess was written by BoM and is not stritly part of the @ylafa! system. ,f a fa! modem or a fa! telephone line beomes faultyJ @ylafa! marAs the modem as LwedgedM and terminates the assoiated fa4getty. "he fa4getty must be restarted when the problem is retified. "his is done to prevent @ylafa! from wasting time repeatedly trying to send fa!es on a faulty modem(line. Monitoring 8ylafa% "he CM-- #atchdog monitors the @ylafa! proesses =hfa4d, fa4., fa4getty> and automatially restarts failed proesses. "he CM-- 67, I!35 C;C)-;2I option also shows the status of @ylafa!. "he @ylafa! fa4stat lient ommand an also be used to heA if the @ylafa! server proesses =fa4., hfa4d, fa4getty> are running. fa4stat displays the status of @ylafa!J in partiular whih messages are :ueued and whih modems are available. fa4stat does this by sending a re:uest to hfa4d. ,f hfa4d is not runningJ the fa4stat display will appear as follows# Can not reach server at host "xxxx", port nnnn. $here# !!!! K hostname =normally loalhost> nnnn K @ylafa! port number O for e!ampleJ /883. ,f fa4. is not runningJ the fa4stat display will appear as follows# HylaFAX scheduler on hostname: Not running. ,f a fa! modem =fa4getty> is not running =although the fa! line will be displayed>J no asterisA =H> will be displayed ne!t to its name O for e!ampleJ the following display indiates that fa! line fa!02 is not worAing 5 no fa!getty. HylaFAX scheduler on hostname: Running Modem fax01 * (+61.3.96694805): Running and idle Modem fax02 (+61.3.96694805): Waiting for modem to come ready CMSS Sstem Mana!ement "uide# version 2.$ Page 101 Circuit Contro' 8ylafa% client processes @ylafa! is a lient(server system where users an send and monitor fa!es from any lient mahine that has the @ylafa! lient proesses installed. "he server proesses are fa4., hfa4d and fa4getty. "he lient proesses are# fa4statJ displays status of fa! modems and :ueued fa!es on the server sendfa4, sends a message(file to the -erver =hfa4d> for fa! transmission to the given telephone numbers. >y$a.a+ Startu& Scri&t As for all proesses the startup sript should be in Hcmop/fa4. ,t should be alled rc.fax and it must be started as root. A typial rc.fax file should onsist of the following te!t# PATH=$PATH:~cmop/fax/bin:~cmop/fax/sbin:~cmop/cmss/bin export PATH CMSS=~cmop/cmss export CMSS # # Start PTY/LAN interface processes # faxptydr $CMSS fax01 melbourne-ts-a 4007 -c > /dev/null & faxptydr $CMSS fax02 melbourne-ts-b 4006 -c > /dev/null & faxptydr $CMSS fax03 melbourne-ts-a 4008 -c > /dev/null & faxptydr $CMSS fax04 melbourne-ts-b 4007 -c > /dev/null & # # Start process that handles user commands # hfaxd -i hylafax # # Start Hylafax central queuing agent # faxq # # Sleep a while to ensure faxptydr have started # sleep 5 # # Start Hylafax modem control processes # nohup faxgetty fax01 > /dev/null & sleep 1 nohup faxgetty fax02 > /dev/null & sleep 1 nohup faxgetty fax03 > /dev/null & sleep 1 nohup faxgetty fax04 > /dev/null & Page 102 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' Cote: "he fa4ptydr proesses must be started before the fa4getty proesses beause they provide the ommuniations paths between fa4getty and the modems =through ptys>. A one5seond delay is used between starting eah fa4getty beause originally there was a bug in fa4. whereJ if it reeived multiple messages that modems were available in very :uiA suessionJ it would ignore some of them. 4r in other wordsJ some modems would not be used beause fa4. did not Anow about them. )on.iguration #i$es @ylafa! uses a onfiguration file for the entral :ueuing agent =fa4.> and one for eah fa! modem attahed. "he onfiguration files are stored in the etc sub5diretory. "he fa4. onfiguration file is referred to as config. "he fa! modem onfiguration files are referred to as config.faxnnJ where nn is the modem number. "he main options in the onfig files are# config 7for fa4.8. )a*"e 2,: config fi"es main options Configuration *ption Description MaxDials Maximum attempts where cannot connect ( for example) &us# signal Max5ries Maximum num&er of attempts that connect &ut still fail No&Re$2us# 5ime &etween retries (sec) when recei"e a &us# signal No&Re$DataConn No&Re$3o1nswer Retr# time when no answer No&Re$3oCarrier No&Re$3o-Con No&Re$Other No&Re$Proto !er"er5racing CMSS Sstem Mana!ement "uide# version 2.$ Page 103 Circuit Contro' Cote: ,n CM-- these values are normally set as follows# Ma!0ials# 8 Ma!"ries# ) Job!!!# '20 "his means that if a all does not onnet O for e!ampleJ busy or no answerJ @ylafa! will retry up to five times at two5minute intervals before giving up and raising a CM-- operator alarm. Ma!"ries of ) means that if we onnet but have a fa! onversation error then @ylafa! attempts a ma!imum of three times at two5minute intervals. config.faxnn =for a modem># "he config.faxnn ontains modem speifi items. ,n partiularJ modem ommands that need to be issuedJ whih differ between brands of modems. $hen adding a new modem =new onfig file> of an e!isting type it is reommended that a opy be used from an e!isting onfig file. Available options inlude# )a*"e 30: Config fi"e avai"a*"e options *ption Description -1:3um&er 5elephone num&er of fax modem +ocal,dentifier -ax identification string Dial!tringRules 1llows s#stem to prefix telephone num&er with G6V or G>V for P12: lines' Max!etup1ttempts Maximum num&er of attempts to initialiDe the modem &efore %#lafax discards the modem (marks it as wedged) A omplete list of the onfig options an be seen by issuing the man ommandJ as follows# man config. 4ogs*%iagnostics @ylafa! writes operating information to &og filesJ whih are useful for fault diagnosis. fa4. normally logs this information to sys"og. "he amount of information that is written an be modified by hanging the following parameter in the @ylafa! -erver config file =normally loated in .../etc/config>. Server)racing: n where n K amount of information. Page 104 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' "he modem onversations an also be logged =fa4getty/fa4send> by setting parameters in the config.faxnn file for an individual modem =normally loated in ../etc>. "he parameters are# Server)racing: n Session)racing: n Modem session information is logged to the "og sub5diretory. Statistics 9ccounting: @ylafa! stores information about every fa! send in a file named 4fer"og in the etc sub5 diretory. "his information an be formatted by using the 4ferstats utility. *efer to the Man pages for additional information about !ferstats 7man 4ferstats8. @ylafa! also stores information about the apabilities of every fa! mahine it alls and the all failure rates in the info sub5diretory. 0se o. 42 6er"ina$ Ser3ers @ylafa! e!pets modems to be diretly onneted to the server and ommuniates with them through serial ""S ports O for e!ampleJ /dev/ttynn. ,n CM--J @ylafa! is onneted to the modems on the &AN through "erminal -ervers for the following reasons# ,t worAs with 7ni! -ervers automati failover software whereas diret lines will not ,t saves valuable -erver slots ,t is easier to add "erminal -ervers to a &AN than add serial ports to a -erver. .or the "erminal -erver to operate orretlyJ the following items M7-" be onfigured. '. "he "erminal -erver must drop 0"* to the modem when it loses the "C%(,% onnetion to the -erver. "his ensures that if @ylafa! =or the -erver> dies then 0"* will be dropped to the Modem whih will drop any telephone all it may have. 2. "he "erminal -erver must be onfigured to use 1eepa"ive so that if the "C%(,% onnetion disappears O for e!ampleJ the -erver diesJ the "erminal -erver will notie this and drop 0"*. "o allow @ylafa! to ommuniate with a "erminal -erver portJ an additional BoM proess fa4ptydr is used to ommuniate with @ylafa! through a %"S onnetion =%seudo5""S>. Cote: A %"S looAs liAe a ""S to @ylafa!. @oweverJ instead of passing the data to a -erial %ort it passes it to another proess =fa4ptydr>. CMSS Sstem Mana!ement "uide# version 2.$ Page 105 Circuit Contro' !!ing an! %e$eting #a+ Mo!e"s "he onvention for naming fa! modems is to refer to them as fa4nnJ =where nn K 0'..33> and the fa! modems to be onseutively numbered O for e!ampleJ fa!0'J fa!02 ... (dding a modem "he following proedure adds a new fa! modem to @ylafa!. Cote: "his proedure assumes that the modem is the same type as e!isting modems =Multiteh>. '. Connet a new fa! modem to a telephone onnetion and to a &AN "erminal -erver port. 2. Configure the &AN "erminal -erver port. ). "est the modem and "erminal -erver port by using )A2CA) to onnet to the port and then issue modem 3) ommands. /. Copy an e!isting modem onfiguration file for the new modemJ as follows# cp -p config.fax01 config.faxnn =where nn K new fa! number>. Cote: 1nsure the file permissions are the same as for the original file. 8. ,f re:uiredJ hange the following items in the new modem onfig file# H !35Cum*er H 2oca"Identifier. <. Create a new @ylafa! .,.4 pipe for the new modem as followsJ to allow ommuniation between fa4getty and fa4.. "he .,.4s are in the @ylafa! home data diretory =typially Hcmop/fa4/spoo"/..> h. &ogin as root i. m?fifo !I!;.fa4nn Y. cho#n fa4:fa4 !I!;.fa4nn ?. chmod uogLr# !I!;.fa4nn 9. -tart a fa4ptydr for this modemJ as follows# l. &og in as root m. fa4ptydr =CMSS fa4nn termina"9server port 9c \ Page 106 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' Cote: ,nitially fa4ptydr may be run in debug mode =9D>J where it produes stdout output on onnetion suesses. 2. -tart a fa4getty for this modemJ as follows nohup fa4getty fa4nn G /dev/nu"" \ Cote: "he fa4getty re:uires the ommand nohup or it will terminate on e!iting the window. 3. 4n suessful ompletion and the modem is funtioning suessfullyJ add the startup ommands to Hcmop/cmss/rc.fa4J as follows# n. H fa4ptydr =CMSS fa4nn termina"9server port 9c \ o. H nohup fa4getty fa4nn G /dev/nu"" \ Deleting a fa% modem "o permanently remove a fa! modem from the systemJ arry out the following proedure# '. -ilene the CM-- wathdogJ as follows# 3dmin II Buiet the <atchdog. 2. &og in as rootJ then enter the ommandI c"osedo#nfa4 fa4nn "he c"osedo#nfa4 fa4nn sript then arries out the following steps# p. ,ssues a @ylafa! ommand fa4.uit fa4nn to stop the fa4getty :. "erminates the fa4ptydr. ). ,nstrut CM-- to no longer monitor this modem by removing the fa4ptydr .,.4J as follows# rm =CMSS/fa4dir/!I!;.fa4nn. >y$a.a+ )$eanu& Scri&ts 9)(,2: "he following @ylafa! related ronDobs should be run as detailed# "he root rontab should inlude an entry of the form# 10 10 D D D Hcmop/fa4/s*in/fa4.c"ean fa4.c"ean removes old data files. ,f it is not runJ the @ylafa! file system :uiAly fills up. "he fa4 rontab produes transmission statistisJ tidies up old files and should inlude# $$ 23 D D D Hcmop/fa4/s*in/fa4cron 9"og 1 W mai" ... "he fa4 rontab should also inlude# CMSS Sstem Mana!ement "uide# version 2.$ Page 107 Circuit Contro' 0 0 1 D D =CMSS/too"s/fa4"ogc"ean G /dev/nu"" Cote: "his proess is a BoM tool that ompresses one monthMs @ylafa! 4fer"og. Page 108 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' IBM 01-2 Support CM-- supports onnetivity based on ?.28. ?.28 is a CC,"" standard used e!tensively on 6"- and A."N linAs. "he ,BM -ervers have been onfigured with the following ?.28 apabilities# "here are eight ?.28 *-2)2 lines 1ah line is apable of speeds up to </ Tbps "he urrent ,BM ?.28 liene for 1M- limits the number of onnetions =virtual iruits> that an be onfigured to only '< =referred to as a Basi &iene> Beause of the liene restritions only two of the eight lines have been onfigured Both the two lines have been onfigured with two %+Cs =%ermanent +irtual Ciruits> and si! -+Cs =-with +irtual Ciruits>. "he ?.28 onfiguration an be observed using the -ystem Management ,nterfae "ool =-M,"> or by viewing the latest baAup file /usr/s*in/c"uster/"oca"/42$. "he ?.28 lines are onneted to an ?.28 paAet swith that onnets to the destination lines. "his feature allows the ?.28 lines to easily failover to a seond ,BM -erver as part of the normal failover proedures =@ACM%>. Monitoring ;.25 1nter the following ,BM ommand =as root> to heA the status of the ?.28# 42$status 1nter the following ,BM ommand =as root> to monitor the ?.28# 42$mon 8ac?ing 0& an! (estoring the ;.25 )on.iguration Create a baAup of the ?.28 onfiguration in the /usr/s*in/c"uster/"oca"/42$ diretory by entering the following ommands# cd /usr/s*in/c"uster/"oca"/42$ *ac?up42$ 9f "o reload(restore the baAup onfiguration to the worAing diretoryJ enter the following ommands# cd /usr/s*in/c"uster/"oca"/42$ restore42$ CMSS Sstem Mana!ement "uide# version 2.$ Page 109 Circuit Contro' "estarting t!e IBM 01-2 "o restart an ?.28 lineJ enter the following ommands# rmdev 9" 4444 7#here 4444 Q the "ine7for e4amp"e, s42$a8 m?dev 9" 4444. Cote: "he rmdev ommand deativates. "he m?dev ommand restores the line. "o restart the ?.28 interfaeJ enter the following ommands# removes42$ 9f 9. J removes 5.2$ cd /usr/s*in/c"uster/"oca"/42$ restore42$ Cote: ' 7nder some onditionsJ the rmdev and removes42$ ommands may not worA. "his problem relates to ommuniations being onneted on one or more of the ?.28 ports when these ommands are issued. ,f these ommands failJ lose the ?.28 lines in CM-- through the CM-- 67, =refer to the Comms GUI User Guide> before re5issuing the rmdev or removes42$ ommand. Cote: 2 A problem is Anown to our when attempting to run the ,BM ?.28 interfae at high speed O for e!ampleJ </TbpsJ using the *-2)2 interfae. "his problem ours oasionally when the ?.28 linA is restarted. "he Comms server does not resume sending ?.28 paAetsJ but its internal trae 42$mon may indiate that it is. "he paAets do not arrive at the physial line. .or this reasonJ run CM-- lines at a lower speed whenever possible. 01-2 and failo#er B8(CMPC "he ?.28 lines are onneted to the Comms server through an ?.28 %aAet -with. ,t is N4" neessary to physially move ?.28 ables when CM-- is e!hanged between the mahines. ,n a failover situationJ the new Comms server will issue the following ommands =the latest operational ?.28 onfiguration> when the luster node starts up# cd /usr/s*in/c"uster/"oca"/42$ restore42$. "he ?.28 %aAet -withes are onfigured to attempt rediretion of the traffi to the alternate Comms -erver if the primary Comms -erver is unavailable. Pro7$e"-so$3ing Symptom Page 110 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' .ollowing a restart of the ?.28 NodeJ to whih the Comms server is onnetedJ 42$mon indiates that -ABMs are being sent but no responses are being reeived. "his appears to be a bug in the Comms serverJ beause line traes have shown frames being sent to the ,BM. Suggested remedy '. *estart the ?.28 line affeted on the Comms server. 2. ,f -tep ' is not suessfulJ restart the entire ,BM ?.28 interfae. CMSS Sstem Mana!ement "uide# version 2.$ Page 111 Circuit Contro' 8P 01-2 Support "here are at least two different @% ?.28 ards whih are managed differently# '. 25port ?.28 ACC ard 2. 25port ?.28 ard Both these ards are apable of speeds up to </T bps. "he ACC ard has the advantage of allowing automati failover of the ?.28 lines if the operational mahine fails =in a @% -ervie6uard environment>. Monitoring ;.25 1nter the following ommand =as root> to heA the status of an ?.28 line =/dev/xxxx># 42$stat 9d /dev/4444 .or the 25port ard some useful information is also available via the ommand# /etc/netfmt 9f /usr/adm/nett".2;G00 9t$0 Sto&&ing ;.25 D4port (CC Card A daemon alled Omasterd ontrols the ACC ard. -top the ACC ard =and all the ?.28 lines> by entering the following ommand# /etc/Omasterd stop -4port 01-2 Card .or the 25port ardJ unliAe the ACC ardJ eah ?.28 line must be stopped separately as follows# 42$stop 9d /dev/4444 Starting ;.25 D4port (CC Card '. "o start the ACC ard and all the ?.28 lines issue the following two ommands# /etc/Omasterd /etc/42$/start@42$ -4port 01-2 Card '. "o start one ?.28 line issue the following ommand# 42$init 9c /etc/42$/42$config@444 where !28onfig;!!! is the onfiguration file for the given line Page 112 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' )) )ar! )on.iguration '. "he ACC Card has a separate onfiguration fileJ typially in# /opt/acc/cfg/42$.ans# 2. "he LanswM file must be ompiled into a file =!28.tmem> for downloading into the ?.28 ard. ttgen 9o 9v 42$.ans# 42$.tmem "he !28.tmem file is downloaded to the ?.28 ard by the Omasterd ommand. ). "here is also a separate onfiguration file for eah line in the Card. "hese onfiguration files are stored in diretory /etc/x25 under names of the form 42$config@n. "he onfiguration of a single line an be modified by hanging the appropriate /etc/x25 file and then downloading it to the ard as follows# /etc/x25init -c /etc/x25/x25config_n "here is a sript /etc/42$/start@42$ to download all the line onfigs. /. 4ne of the daemons started by Omasterd is #atch. "his daemon monitors the Card and restarts it if it fails. -imilarly the Card shuts down if it does not reeive periodi messages from $ath. 2-&ort )ar! )on.iguration '. ,ndividual ?.28 line onfigurations are stored in diretory /etc/x25. 2. "o hange a line onfiguration simply modify the appropriate file and then download the new onfiguration# /etc/x25init -c /etc/x25/x25config_n CMSS Sstem Mana!ement "uide# version 2.$ Page 113 Circuit Contro' Glossary <M, acrony"s $M4 Q $orld Meteorologial 4rganiPation 6"- Q Global )eleommuniation System NMC Q National Meteorologial Centre M"N Q Main "eleommuniation NetworA. "his omprises the Aey entres and linAs on the 6"- *B-N 5 *egional Basi -ynopti NetworA. *"@ Q *egional "eleommuniation @ub. "hese are entres with responsibility for olleting and disseminating data within their region. ,ther acrony"s A."N 5 Aeronautial .i!ed "eleommuniations NetworA. /6S 6er"s Message Q some information surrounded by a start line and an end of message indiator. -tart line Q "ypially this is BNCNC nnnC for Baudot messages and U-4@IUC*IUC*IU&.Innn for A-C,, messages 1nd of message indiator Q BNNNNC for Baudot messages. U1"?I for A-C,, messages "railer K end of message indiator A-C,, Q ommon 25bit harater set Baudot Q old 85bit harater set ,"A2 Q same as Baudot ,"A8 Q same as A-C,, ""AAii Q si! harater message identifier CCCC Q four harater originating entre abbreviated header Q line ontaining the ""AA,, CCCC header Q *efers to the message up to the data. "hat isJ the start line and the abbreviated header. Bulletin Q one of more observations oded aording to 6"- rules Page 114 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' originator 5 a field used in message headers =eg CCCC> that desribes where a message is from. report Q an observation. se:uene number =nnn> Q a rotating number. 7sed to deteting missing inoming messages )o"&uting 6er"s 67, 5 6raphial 7ser ,nterfae. 7sed to refer to CM-- user interfae *0BM- 5 *elational 0ataBase Management -ystem. 4rale Q A ommerial *0BM- .orms 5 4rale database produtJ used to provide a 67, interfae into 4rale tables. )MSS 6er"s CM-- 5 Computer Message -withing -ystem. C4MM- 5 alternate name for CM--. AB%- 5 Automated Bulletin %rodution -ystem. A,.- 5 Australian ,ntegrated .oreast -ystem. Journal 5 .ile ontaining a summary of every message sent or reeived. M-6,N 5 a large irular file that stores message diretories for reeived messages. M-647" 5 a large irular file that stores message diretories for sent messages. 47"R Q -hort for 4utput Rueues. "his is a file that ontains the :ueues of messages waiting to be sent to eah destination. *1J1C" 5 messages that have failed validation in some way. *1%4*"- 5 a large irular file that stores message diretories for reports(observations that have been reeived. -1*+,C1 Q a irular file ontaining messages that are flagged for operator attention. -$,"C@0,* 5 a small irular file used to pass messages between the message reognition proess =reogn> and the message swithing proess =msgswth> address Q 253 harater identifier used to send messages to output iruits. aifsop Q 7ni! user identifier =uid>. Normally the owner aount for A,.- and sometimes the owner aount for CM-- alarm Q 1rror alert that re:uires operator attention CMSS Sstem Mana!ement "uide# version 2.$ Page 115 Circuit Contro' iruit 5 CM-- term referring to an input or output data soure(destination. mop 5 7ni! user identifier =uid>. Normally the owner aount of CM--. @ylafa! 5 third party produt used for .a! delivery from CM--. message diretory Q A reord ontaining information about a message or observation. 1g the time it was reeived. msgdir 5 CM-- abbreviation for ^message diretory^. priority Q A four level =AJBJCJ0> sheme is used to allow important messages to be sent first. ***CC Q -ame as iruit. "hat isJ a soure of data or a destination. )MSS %irectories*#i$es FCM-- Q 7N,? environment variable. %oints to CM-- home diretory FCM--(pids 5 0iretory where CM-- proess identifier numbers =pids> are stored. FCM--(produts 5 0iretory where inoming files =eg harts> are stored. FCM--(restart 5 0iretory where restart information is stored. FCM--(sreen: 5 0iretory where files are :ueued to be onverted to a form that an be viewed on the CM-- 67,. FCM--(views 5 0iretory where viewable files are stored. alarmd 5 CM-- irular file that reords important deoder alert information for operator attention. mss.params 5 CM-- system parameter file ontaining loal onfiguration options. mssfile.shm 5 system file used as a Aey to reate CM-- shared memory bloA. Dournal 5 CM-- irular file that reords reeption(transmission summary reords for 67, perusal. Dournald 5 CM-- irular file that reords summary reords for outgoing messages only. 4ften used when also using A,.-. ,s more readable than the raw BDournalC log 5 CM-- irular file that reords error and information messages for perusal. logd 5 CM-- irular file that reords deoder error and information messages for perusal. msgindir Q %art of M-6,N. &arge irular file that stores message diretories validated by msganal. msgint!t Q +ery large flat file that stores the physial message te!t reeived(sent by CM--. %ointed to by all the various message diretory files. Page 116 CMSS Sstem Mana!ement "uide# version 1.) Circuit Contro' msgotdir 5 CM-- irular file that stores message diretories sent by output line drivers. r.mop 5 CM-- startup sript. -tarts all CM-- proesses and line drivers. r.fa! 5 CM-- startup sript. -tarts the fa! system. reogdir 5 CM-- irular file that stores message diretories for reogniPed messages =ie. reports>. stop.fa! 5 CM-- tool used to stop the fa! sub5system. stopmss 5 CM-- tool used to stop the CM-- system. swithdir Q -mall irular file used to pass messages and reports from the reogniPer to the message swithing =msgswth> proess. )MSS Processes 0ataMon 5 baAground proess that reords raw statistis on reports reeived by CM--. 0ata*e:uest 5 baAground proess that heAs for missing observations and re:uests resends. bufringest 5 baAground proess that deodes reeived B7.* format messages. bullDob 5 sheduled tasA that produes bulletins and sends them into CM-- for swithing =run from the !tnlist table>. losedown 5 ommand to terminate a proess or line driver. mfilelean 5 baAground proess used to remove old file messages from the FCM--(produts diretory. mlnmon 5 baAground proess used to monitor input and output lines and alert unusual inativity. mmailin 5 proess that is run from the mail aliases file to ingest email messages into CM--. mss!2 Q CM-- graphial user interfae =67,> mre:uest 5 baAground proess that analyses and proesses inoming re:uest for repetitions. mssmem 5 program used to reate and update shared memory bloA. mview 5 baAground proess that onverts image produts into pbmraw images for CM-- 67, display. re2log 5 program to reate a CM-- log type irular file. reatedir 5 program to reate a CM-- message diretory type irular file. deoder 5 baAground proess that deodes reeiver harater format messages. CMSS Sstem Mana!ement "uide# version 2.$ Page 117 Circuit Contro' gribingest 5 baAground proess that deodes reeived 6*,B format messages. info 5 tool used to return information about a iruit or proess. linestats Q baAground proess that reords line loading statistis. msganal 5 baAground proess used to validate reeived message header(trailer. msgprep 5 baAground proess that prepares messages for transmission in a format aeptable to the destination. msgswth 5 baAground proess that determines swithing destinations for messages. newte!t 5 tool that reates(e!pands the msgint!t.dat te!t file. reogn 5 baAground proess that reogniPes meteorologial reports in the message te!t. survey 5 baAground proess that reords raw information used for $M4 surveys. wathdog 5 baAground proess used to ensure all CM-- proesses are running. ,rac$e 6a7$es alarm;tab 5 table that lists CM-- alarms and desriptions. buldesr 5 table that lists swithing information for $M4 format messages =""AAii(CCCC>. lient;addr;tbl 5 table ontaining CM-- e!ternal lient information. mssin 5 table that onverts a foreign swith address to a CM-- swith address. filedes 5 table that lists inoming CM-- data filesJ along with desriptionJ et. grpaddrs 5 table ontaining CM-- ^one to many^ swith addresses. grpdes 5 table ontaining desription of CM-- group addresses. line format 5 a field used to desribe the harateristis of input(output CM-- iruits. line type 5 a field used to desribe the harateristis of input(output CM-- iruits. lines;in 5 table defining the CM-- input iruits. lines;out 5 table defining the CM-- output iruits. stndesr 5 table that stores swithing information based on station number and report type. stndesrf 5 table that stores swithing information based on file name and file e!tension. !tnmain 5 table listing CM-- sheduled Dobs(tasAs along with their start times. !tnne!t 5 table listing the ne!t !tnmain Dob to be run. Page 118 CMSS Sstem Mana!ement "uide# version 1.)