Standard Procedures

1
S1 Welcome and Introduction S2 Introduction to
Safety Information Exchange S3 Operational
Concepts S4 System Overview S5 CVIEW
Networking S6 Microsoft Windows NT S7 Standard
Procedures S8 System Configuration S9 Change and
Problem Tracking S10 CVIEW Versions S11 Using
OpCon S12 Laboratory Exercises S13 Wrap-up
Session 7 Standard Procedures
2
Session Plan

• CVIEW Service Startup
• Carrier Update Verifications
• Vehicle Update Verifications
• IRP Update Verification
• Monitor Database Size
• Monitor Temp Files

3
Session Objectives

• Understand CVIEW Operating Procedures
• Prepare for Hands-On Operations Training
• Hands-On Training to be Scheduled

4
Startup of CVIEW Service (1 of 2)

• Description The CVIEW services are not started
  automatically when the server it is on is
  started. They must be started manually. This
  procedure starts up the CVIEW services.
• Frequency Whenever VADMCVIEW1 (the computer
  running the CVIEW service) is started or rebooted.

5
Startup of CVIEW Service (2 of 2)

• Description The CVIEW services are not started
  automatically when the server it is on is
  started. They must be started manually. This
  procedure starts up the CVIEW services.
• Frequency Whenever VADMCVIEW1 (the computer
  running the CVIEW service) is started or
  rebooted.
• Use the START button on VADMCVIEW1 to open
  Administrative Tools -gt Server Manager.
• Select VADMCVIEW1 from the list of computers.
• Select Services under the Computer menu.
• Verify that the POP Service and the SMTP Service
  are started.
• Verify that the OracleServiceORCL, the
  OracleStartORCL and the OracleTNSListener
  services are started.
• Select CVIEW from the list of services.
• In the Startup Parameter field enter CVIEW
• Select Start and wait for the services state
  to change to started.
• Select CVIEW22 from the list of services.
• In the Startup Parameter field enter CVIEW22
• Select Start and wait for the services state
  to change to started.
• Select Close.

6
Carrier Update Verifications (1 of 2)

• MCMIS sends SAFER Carrier Updates Weekly
• SAFER sends subset to VADMCVIEW1
• SAFER generally sends Updates on Monday
• Run Verification on Tuesday
• Open MS DOS Command Window on VADMCVIEW1
• Issue command carrier_counts ltYYYY-MM-DDgt where
  ltYYYY-MM-DDgt is the current date.
• The file Carrier_Counts22.log is created in the
  directory C\CVIEW\LOAD\ltYYYY-MM-DDgt.

7
Carrier Update Verifications (2 of 2)

• Examine counts for each CVIEW version. There
  should be a count for the most recent Sunday. If
  there is no count, contact the Volpe law
  enforcement help desk to initiate
  troubleshooting.
• The most recent count should be roughly
  consistent with the previous history of counts.

8
ROC Carrier Subscription Processing (1 of 2)

• CVIEW sends ROC the carrier updates sent from
  SAFER.
• The individual database records are combined
  together into one file before being sent.
• The Sendlist2000 utility performs this function
• This procedure should be performed once a week
  after verifying the carrier update from SAFER.

9
ROC Carrier Subscription Processing (2 of 2)

• Open a MS DOS command window on VADMCVIEW1.
• Enter the command SENDLIST2000.
• In the sendlist2000 GUI window
• Change WIN.INI SECTION to SENDLIST_V22.
• Change THREADS to 10.
• Change LOG TO FILE to C\CVIEW\LOAD\ltYYYY-MM-DD
  gt\SENDLIST.LOG where ltYYYY-MM-DDgt is the
  directory used for checking the carrier counts.
• Click the LOGIN button. This connects to the
  database.
• Click the START button. This starts the
  subscription processing.
• Wait for the sendlist2000 logo to stop spinning
  and the status line to read done. This may
  take several hours.
• Open the SENDLIST.LOG file and verify that the
  ROC subscriptions were sent without error.

10
Vehicle Update Verifications (1 of 2)

• SAFER Sends VADMCVIEW1 vehicle updates based on
  recent inspection reports.
• MD IRP Workstation sends vehicle updates (via
  SAFER) based on MDs Lockheed Vista IRP file.
• VA E-Screening enrollment LSI (future) will send
  vehicle updates based on carriers requests. Both
  IRP and enrollment information will be updated.
• Updates from SAFER occur daily, from other
  sources as often as daily during peak processing
  times.

11
Vehicle Update Verifications (2 of 2)

• Vehicle verifications should be performed each
  week day.
• Open MS DOS Command Window on VADMCVIEW1
• Issue command vehicle_counts ltYYYY-MM-DDgt where
  ltYYYY-MM-DDgt is the current date.
• The file Vehicle _Counts22.log is created in the
  directory C\CVIEW\LOAD\ltYYYY-MM-DDgt.
• Each file contains counts for three kinds of
  updates SAFER IR, IRP and VA E-Screening
  Enrollment.

12
IR Vehicle Verification

• The total and by date counts are recorded in
  each file.
• The total should generally increase each day.
• The count for the current date should be between
  500 and 1000, weekends excepted.
• If a count for the current date does not exist,
  contact the Volpe law enforcement help desk to
  initiate trouble shooting.

13
IRP/E-screening Update Verification

• The IRP/E-Screening total and by date counts
  are recorded in each file.
• The IRP total should generally increase each day
  that MD IRP or VA E-screening processing occurs.
• The E-Screening total should generally increase
  each day that VA E-screening processing occurs.

14
Monitor ROC Subscription Downloads (1 of 2)

• VADMCVIEW1 sends VA ROC carrier and vehicle
  updates.
• Carrier updates sent weekly.
• Vehicle updates typically sent daily.
• Check that ROC is downloading its updates
• Check size of file C\NtMail\In\roadssc1sub.mbx

15
Monitor ROC Subscription Downloads (2 of 2)

• Early in day, file size should be close to zero.
  Late in day it should be larger. Next morning it
  should again be close to zero.
• If file size grows large without getting smaller,
  call ROC operator to initiate trouble shooting.
• If file size stays at zero throughout the day,
  VADMCVIEW1 subscription processing may or may not
  be active. Call APL development team to initiate
  trouble shooting.

16
Monitor Database Size

• Description This procedure determines whether
  the CVIEW database is getting full.
• Frequency This procedure should be run once a
  week.
• Open an MS DOS command window on VADMCVIEW1.
• Enter the command db_check.
• If the names of any database tables are
  displayed, they are starting to fill up and need
  to be fixed. Contact the CVIEW database
  administrator.
• If no information is displayed, the database is
  all right.
• The screen output is saved in a file called
  db_check.log in the default directory for the
  MS DOS command window. Delete it or save it for
  use by the CVIEW database administrator.

17
Monitor and Clean Up Temp Files and Logs (1 of 2)

• Description This procedure detects infrequent or
  intermittent problems with queries and
  subscription processing.
• Frequency Daily
• Look in the system temporary folder for files
  such as MBX, IOX, IIX, IOE, IOG, IOS, and ZIP
  files.
• There should be none, or few, and any that appear
  should be transient and go away again quickly.

18
Monitor and Clean Up Temp Files and Logs (2 of 2)

• Description This procedure detects infrequent or
  intermittent problems with queries and inspection
  report updates.
• Frequency Daily
• Open the C\Temp folder on VADMCVIEW1.
• Examine the folder for any files named
  mbxltNNNgt where ltNNNgt is a unique serial
  number.
• Examine the folder for any files named
• ioxltNNNNgt.tmp
• iixltNNNNgt.tmp
• ioeltNNNNgt.tmp
• iogltNNNNgt.tmp
• If a large number of any of these files exist, or
  if those few that do remain for several minutes,
  contact the APL development team to initiate
  trouble shooting.