NCR RSD Atlanta 7710GA2 Electronic Pricing Transmitter User Manual Chapter 12

NCR Corporation, RSD - Atlanta Electronic Pricing Transmitter Chapter 12

Chapter 12

Testing the SystemCBS Diagnostics and TroubleshootingThe information in this chapter will assist trained NCR CustomerService personnel or other trained personnel in analyzing and isolatingproblems with the DecisioNet System. The available tools include theDecisioNet System log, a SmarTalker check called Bedcheck, CBSdiagnostics, and Failure Detection and Analysis (FDA) software.FDA uses the Base Hardware configuration information to detect andlog hardware failures. FDA is included on the optional EPL SystemInformation package that must be installed and running to benefitfrom its diagnostic and logging capability. For error code descriptionsrefer to Chapter 8, “DecisioNet System Messages,” in the NCRDecisioNet System User’s Guide (B005-0000-1087).Site-specific documents created during initial installation as specifiedin the Certification/Re-Certification Site Survey Procedure (497-0410343)and provided to the DecisioNet Technical Support Specialist at yourarea Managed Service Center includes the following information:• Installation Site Survey/Checklist• General site data• EPL requirements• Software types and versions• Price lookup information• Dial-in support data (passwords, etc.)Using the dial-in support data, the Managed Service Center canperform all of the DecisioNet System software testing andtroubleshooting described in this chapter.12
12-2 Testing the SystemTraining for the DecisioNet System includes a 7710 Hardware class,and the DecisioNet Software Support and Programming WBT.Initiating CBS DiagnosticsThe following CBS diagnostics are available:• Self-Diagnostics (Level 0 tests)• DIP Switch Diagnostics (Level 1 factory tests)• EPL Administration Diagnostics (Level 3 tally tests) – requires EPLBase and Application Runtime software• Failure Detection and Analysis (Level 2 tests) – requires EPL Baseand Application Runtime and EPL System Information PackageOpening the CBSThe CBS must be opened to access the switches and Light EmittingDiodes (LEDs) described in the following sections. Refer to theillustrations in the “Installing Primary and Secondary CBSs” section ofChapter 4 for instructions on opening the CBS and mounting the CBS.The safety strap shown around the CBS handle in the CBS MountingSystem illustration must be removed before opening the CBS.Caution:  When opening the CBS with the cables attached, be carefulnot to lift the CBS off the mounting bolts or to disconnect any cables.DIP Switch SettingsWhen running diagnostic tests, set DSW1 as noted in the followingtable.Test Name DSW1–Switch 4 DSW1–Switch 3Self-Diagnostics Off OffDIP Switch Diagnostics Off OnEPL Administration Diagnostics Off OffFailure Detection and Analysis Off Off
Testing the System 12-3The following illustration shows the rotary switch, DIP switch, andLED positions.LED 4LED 3LED 2LED 1LED 6LED 7LED 5Rotary Switch (DSW2)Dip Switch (DSW1)The chassishandle is in this direction.14058Self-DiagnosticsSelf-Diagnostics are ROM-Based (Level 0) diagnostic tests that rununder control of the resident firmware each time the CBS is poweredup with the DSW1 switches set as follows:• DSW1-Switch 4: Off• DSW1-Switch 3: Off
12-4 Testing the SystemWith EPL Software Not RunningWith the EPL Software not running, check the basic functionality of theCBS by turning the power on. Self-Diagnostics performs the followingtests and indicates the test in progress on the LEDs.Test No.Test Name LED 3LED 4LED 5LED 6LED 71 CPU Instruction and RegisterTest On Off On On On2 ROM Test with Sum Check On Off On Off Off3 RAM Test On Off Off On Off4 CPU Timer Test On Off On On On5 CPU ASIC Register Test On Off On On On6 DSP Test Off On Off Off OnAll LEDs are turned off following a successful completion of all thetests. If an error occurs, the LEDs continue to indicate the test inprogress when the error occurred. Replace the CBS for any conditionother than a successful completion.With EPL Software RunningWith EPL Software running, the LEDs in each CBS should be on orblinking, as follows, after a successful CBS power up.LED # - Color Condition/Description1 - Red On/Power On (This LED is not controlled by thefirmware but is directly connected to the power line.)2 - Green On/Primary CBS (This LED identifies CBS connectedto the RS-232/RS-422 Converter)3 - Red Blinking/RS-485 communications active with the EPLController or Primary CBS4 - Yellow Blinking/RF communications active with SmarTalkertags8 - Red Blinking/Master Clock Indicator
Testing the System 12-5Using the CBS LEDs to Diagnose ProblemsThe following sections recommend areas to check when the LEDs donot indicate a successful completion of the Self Diagnostics with EPLSoftware running. Refer to the following sections in this guide fordetails about system components, cable identification, cableinstallation, and cable connector pin out diagrams.• Chapter 4 – Installing the Hardware Infrastructure• Appendix B – DecisioNet System CablesIf LED #1 is NOT OnPerform the following steps:1. Check power supply indicator light to verify that the power supplyis on. If not on, turn on the power switch. Verify that the powercord is plugged in to a proper power source.2. Check power supply connections (C048 cable).3. Check C048 cable connections. Be aware that the C048 cable blocksDC power.4. Check cable connections for all extensions.5. Verify that the RS-495/DC cables (C046 and C048) connector’s pinsmatch the cable diagrams shown in Appendix B.If LED #2 is NOT On for the Primary CBSPerform the following steps:1. Verify that the RS-422 cable (C051) is properly connected to the RS-232/RS-422 Converter and make sure the C051 cable is connectedto CBS CON-3.2. Verify that the RS-485/DC cable (C048) is properly connected tothe power supply and make sure the C048 cable is connected toCBS CON-1 or CBS CON-2.3. Verify that the RS-232/RS-422 Converter power light is on. If not,verify that the power block is plugged in to a proper power source.
12-6 Testing the System4. Verify that the RS-232/RS-422 Converter is connected to the EPLcontroller (RS-232 cable).5. Verify that the Rx/Tx LEDs are blinking on the RS-232/RS-422Converter.6. Make sure that the EPL software is running on the EPL controller.7. If problems persist, call your NCR Representative and review theoriginal site certification documents for support.If LED #3, LED #4 or LED #8 is NOT BlinkingPerform the following steps:1. Make sure the EPL Software is running.2. Verify the C046 and C049 cable connections between CBSs.3. Verify that the Rx/Tx LEDs are blinking on the RS-232/RS-422Converter.DIP Switch DiagnosticsThese Level 1 Diagnostics are typically performed at the factory tovalidate CBS functionality. They are shown here for reference purposesonly. DIP switch diagnostics tests may be run by setting DSW1switches as follows:• DSW1-Switch 4: Off• DSW1-Switch: OnThe DIP switch diagnostics tests and their LED indications are asfollows:Test No. Test Name LED 3 LED 4 LED 5 LED 6 LED 71 ROM Test with CRC On Off On Off Off2 RS-485 Loop Test Off Off Off On On3 Master Clock Test Off Off On Off On
Testing the System 12-7All LEDs are turned off following a successful completion of all thetests. If an error occurs, the LEDs continue to indicate the test inprogress when the error occurred. Replace the CBS for any conditionother than a successful completion.EPL Administration DiagnosticsThe EPL Administration Diagnostics are used to analyze systemperformance and to view the CBS tally for function being tested. TheCBS resets all tallies each time the CBS powers up. Tallies are Level 3diagnostics information.Note:  The installer and/or customer may not need some of thisinformation, but NCR may request it if contacted for remote support.When Diagnostics is selected from the EPL Administration screen, thefollowing functions are available:• CBS Level 1 Diagnostics - Read• CBS Level 1 Diagnostics - Read/Reset• CBS Tally - Read• CBS Tally - Read/Reset• CBS Initial Reset• CBS Address Check• CBS Manager Tally - Read• CBS Manager Tally - Read/Reset• RS-232 Loop Test
12-8 Testing the SystemThe following menu is displayed when Diagnostics is selected fromEPL Administration.Note:  After a function is specified in the diagnostics menu, anyspecific CBS can be targeted for testing.
Testing the System 12-9CBS Level 1 Diagnostics - Read or CBS Level 1 Diagnostics -Read/ResetThis function reads the results of the Level 1 Diagnostics. (CBS Level 1Diagnostics - Read/Resets reads the results and also resets the tallies.)The following is an example CBS Level 1 Diagnostics - Read selectionscreen.Note:  Synth unlocked/TX Low Status: means Synthesizer Unlock/Transmit Power Level.For Antennas A – D, the status indications are:Open: Receive antenna is not connectedNo Error: No error state (receive antenna is connected)Short: Error state (receive antenna is connected)
12-10 Testing the SystemThese are the tallies shown in the Level 1 Read Diagnostics screen.ROM Test: Indicates if the CBS’s ROM is working properly.RAM Test: Indicates if the CBS’s Ram is working properly.DSP Busy: Indicates if a CBS’s Digital Signal Processor (DSP) firmwarequeries are full.DSP echo command test in Level 0 Diag.: Indicates if a CBS’s DSPfirmware is working properly.Master clock test in Level 0 Diag.: Indicates if the Master CBS’s clockis working properly.RS-485 Loop Test in Level 0 Diag.: Indicates if a CBS’s RS-485 Port isworking properly. (This is used at the factory only.)RAM/ROM Test finish or not: Indicates if the RAM/ROM tests havecompleted.RF Unit Power: Indicates if the transmitter is on or off.Synth unlocked/TX Low Status: Indicates if the two parts of the RFboard are operational. Both need to be working for the RF to be on.Antenna A (Open/Short Status): Indicates if Antenna A is connectedto the CBS and is working properly.Antenna B (Open/Short Status): Indicates if Antenna B is connected tothe CBS and is working properly.Antenna C (Open/Short Status): Indicates if Antenna C is connectedto the CBS and is working properly.Antenna D (Open/Short Status): Indicates if Antenna D is connectedto the CBS and is working properly.DSP version number: This is the version number of the CBS’s ROM.
Testing the System 12-11CBS Tally - Read or CBS Tally - Read/ResetThis function retrieves the CBS tallies from each CBS. (CBS Tally -Read/Reset retrieves the tallies and also resets the tallies.)The following shows an example CBS Tally - Read selection screen.These are the tallies shown in the CBS Tally Read screen.No. of received messages from the processor: This is the number ofmessages the Master CBS received from the ISP.No. of send messages to the processor: This is the number of messagesthe Master CBS has sent to the ISP.No. of erroneous msg. from the processor: This is the number ofmessages received from the ISP that have errors.No. of resent messages to the processor: This is the number ofmessages the Master CBS had to resend to the ISP.No. of reception of DC3: This is the number of DC3 messages the CBSreceived telling it to be idle.
12-12 Testing the SystemNo. of framing error in comm. with the proc.: This is the number offraming errors that have occurred in messages sent to the CBS from theISP.No. of overrun error in comm. with the proc.: This is the number oftimes the CBS could not process a message from the ISP because ofmessages being sent too quickly to the CBS from the ISP.No. of received messages from CBSs: This is the number of messagesa CBS has received from other CBSs.No. of sent messages to CBSs: This is the number of messages a CBShas sent to other CBSs.No. of erroneous received messages from CBSs: This is the number ofmessages a CBS has received with errors from other CBSs.No. of resent messages to CBSs: This is the number of messages a CBShas resent to other CBSs because there was an error with the originalmessage sent to the other CBS.No. of framing error in comm. with CBSs: This is the number ofmessages received with framing errors from other CBSs.No. of overrun error in comm. with CBSs: This is the number of timesthe CBS could not process a message from another CBS becausemessages were being sent to quickly from the other CBS.
Testing the System 12-13No. of No responses from slave CBSs: This is the number of times aCBS sent a message to a satellite CBS and did not get a response.No. of sent messages to EPLs: This is the number of messages a CBSsent to a SmarTalker.No. of received data from EPLs: This is the number of times a CBSreceived data from a SmarTalker.No. of lost EPL rcv. data due to no poll from Master CBS: This is thenumber of times EPL data was lost because the Master CBS did notsend a poll for the data.No. of DSP board no acknowledgment: This is the number of timesthe DSP firmware in the CBS did not return an acknowledgment of amessage.No. of DSP board no response of RF/DSP status: This is the numberof times the DSP firmware in the CBS did not return an RF/DSP statuswhen requested.No. of frequency coincidence: This is the number of times the MasterCBS received a message back from multiple satellite CBSs using thesame frequency for the same EPL request.
12-14 Testing the SystemNo. of restart of frequency hopping: This is the number of times theMaster CBS restarted frequency hopping.Using CBS Tally Read Information to Diagnose ProblemsIf No. of erroneous msg. from the processor: exceeds 1 percent of thetotal messages, there is a serious problem with the DecisioNet System.Check the following:• The EPL controller is functioning properly.• The RS-232 and RS-422 cables are properly connected.• There is not a faulty component on the primary CBS.If No. of erroneous received messages from CBSs: exceeds 1 percentof the total messages, there is a CBS problem. Check the following:• The cables between CBSs are not too long. Refer to the section on“Cables Required for Installation” in Chapter 4, “Installing theHardware Infrastructure,” for more information.• There is not a faulty component on the primary CBS.If No. of frequency coincidence: is greater than 100, the limit of 20CBSs installed in the site may have been exceeded or the basesw.cfgfrequency range parameter may be too limited.CBS Initial ResetThis command resets the CBS to its initial power on state. All CBSTallies are set to zero. CBS Manager tallies are not reset.CBS Address CheckThis command is for checking CBS addresses. It causes each CBS toindicate its address on LEDs 3 and 4 when DSW1 Switch 4 is set to“On” and DSW1 Switch 3 is set to “Off” as described in the table at thebeginning of this chapter. LED 3 blinks once to indicate the start of theaddress, then LED 4 blinks the same number of times as the number ofthe address, then LED 3 blinks a final time to indicate the end of theaddress.
Testing the System 12-15CBS Manager Tally - Read or CBS Manager Tally - Read/ResetThis function retrieves the CBS manager tallies from the primary CBS.(The CBS Manager Tally - Read/Reset also resets the tallies.)The following shows a CBS Manager Tally - Read selection screen.These are the tallies shown in the CBS Manager Tally screen.No. of messages sent to CBSs: This is the number of messages the CBSManager sent to the CBSs since the last time tallies were reset.No. of messages resent to CBSs: This is the number of messages theCBS Manager had to resend to the CBSs due to a failure while sendinga request since the last time tallies were reset.No. of messages received from CBSs: This is the number of messagesthe CBS Manager received back from the CBSs.No. of erroneous received messages: This is the number of messagesthe CBS Manager has received with errors from the CBSs.No. of CBS no response time out: This is the number of times the CBStimed out waiting for a response from a CBS or a SmarTalker.
12-16 Testing the SystemNo. of retry over with CBS: This is the number of times the CBSManager reached the retry limit in trying to communicate with a CBS.No. of downlink bursts sent to EPLs: This is the number of downlinkbursts sent to SmarTalkers.No. of no acknowledgments from EPLs: This is the number of timethe CBS Manager did not get an acknowledgment from a message sentto a SmarTalker.No. of requests to send EPL message: This is the number of requestsfrom the DecisioNet Applications to send a message to a SmarTalker.No. of error requests to send EPL message: This is the number oftimes the CBS Manager received a request to send a message to aSmarTalker.No. of arbitrary close of EPL comm. by Master CBS: This is thenumber off times the Master CBS was powered-off, then -on, plus thenumber of times it was reset with the Initial Reset command.No. of replacement of frequency: This is the number of times the CBSManager had to change or replace a frequency in the frequency-hopping screen.RS-232 Loop TestThe RS-232 port on the controller may be tested using this function. Aturnaround plug must be installed before initiating this test.Diagnostic LogsAccess the following logs from the EPL Administration or EPLMaintenance application Log menu:• EPL System Error Log• EPL Data Send Log• EPL Audit Log
Testing the System 12-17EPL System Error LogThe following shows an example EPL System Error Log report. TheEPL System Error Log contains a record of all errors logged by the EPLbase software and applications.Information in the System Error Log includes:Date and Time the error occurredSeverity Code: Information, Warning, ErrorSource module name of the application that logged the errorProcess ID number for the application that logged the errorCategory Code for the application that logged the errorError Code that identifies the errorDescription of the errorFor more information on interpreting errors, refer to Chapter 8 in theNCR DecisioNet System User’s Guide (B005-0000-1087).
12-18 Testing the SystemEPL Data Send LogThe following is an example of the EPL Data Send Log. A Data Sendlog record is recorded when an EPL update is scheduled.Information in the EPL Data Send Log includes:Function: The function that started this operationPLU Number: The item numberPLU Description: A description of the itemLocation: The SmarTalker locationSerial Number: The SmarTalker serial numberBatch Number: The EPL Maintenance Batch Number
Testing the System 12-19Send Status:An EPL’s status is indicated by a number and brief message0:  Successful1:  Waiting2:  CommunicatingAny Negative Number: Resend the data using the instructions in thesection “Resending the EPL Data” in Chapter 9. Refer to Chapter 8,“DecisioNet System Messages,” in the NCR DecisioNet System User’sGuide (B005-0000-1087), for message descriptions.No. of Fail: The number of communication errorsStartTOD: Date and time when communication starts(9708302102 = YYMMDD and 24-hour time)DueTOD: Date and time when communication is due to be completed(9708302112 = YYMMDD and 24-hour time)
12-20 Testing the SystemEPL Audit LogThe following is an example of the EPL Audit Log, which showsinformation relating to the updating of the EPL Table.Information in the EPL Audit Log includes:• Date and Time EPL Table entry occurred• The type of Maintenance Function performed• SmarTalker Serial Number• Price Lookup (PLU) Number• Shelf or Store Location (optional)• PLU Description• Maintenance information including Batch Number and RecordNumber within the Batch
Testing the System 12-21Using Failure and Detection Analysis SoftwareFailure Detection and Analysis (FDA) software can be used as abackground service to report on the condition of DecisioNet Systemhardware. FDA is one of the applications on the optional EPL SystemInformation Package.Power supply, CBS, and antenna failures are reported to the EPLSystem Error Log. Errors related to SmarTalker tags are logged in theBedcheck log and a corresponding entry in the EPL System Error Logindicates the number of tags affected.In a Windows NT system, FDA also logs error conditions to theWindows NT Event Log. These entries include Probable Cause andRecommended Action information.The following types of errors are logged by FDA:Error DescriptionCBS communication closed CBS not communicating withSmarTalkersMaster CBS link down ISP cannot communicate withMaster CBSRS-485 cable failure FDA software identifies faulty cablePower supply failure FDA software identifies faultypower supplyCBS not connected CBS cannot be detectedToo many CBSs connected RS-485 link cannot handle trafficCBS diagnostic errors haveoccurred FDA software identifies faulty CBSUnconfigured CBS detected CBS not configuredCBS connected, but notcommunicating CBS Manager is not using CBSCBS not receiving master RS-485 cable problem
12-22 Testing the SystemError Descriptionclock signalUnconfigured CBS detectedand communicating CBS not configuredCBS RF power is off CBS RF board is not workingproperlyReceive antenna not workingproperly Receive antenna needs to bereplacedUnconfigured receiveantenna is functioning Receive antenna not configuredAmbient noise exceedsthreshold CBSs cannot communicate withSmarTalkers properlySignal level threshold is toohigh CBSs cannot communicate withSmarTalkers properlySmarTalkers not responding Quantity specifiedSmarTalkers have batterylow condition Quantity specifiedSmarTalkers have hardwareerror condition Quantity specifiedFDA also records the CBS tally information in the tally files andforwards tallies to Store Minder. See the “EPL AdministrationDiagnostics” section in this chapter for information about accessingtally information.
Testing the System 12-23Running FDA from a System Prompt When started with other EPL Applications, FDA runs continuouslyand logs errors as they occur. Use the following procedures to runFDA in single-pass mode. The results of the report are sent to theconsole and placed in the EPL System Error Log. Use the -f commandline option to save the report to a file for viewing and printing.1. At a DOS or UNIX prompt, enter esfda to start FDA in single-passmode.2. Review the information output to the console screen, the EPLSystem Error Log and Windows NT Event Log (if testing onWindows NT system).The syntax and options for esfda are as follows:esfda [-r][-x][-y][-f<filename>]-r Report on software and hardware components-x Report only on the hardware components-y Report only on the software components-f<x> Save report in the file specified by <x>. If a path is notspecified, the file is placed in the epl/data/statusdirectory.Example:• Run a hardware and software test and place the report in a filenamed fdatest.esfda -rf fdatestThe following is our report created for the example above.
12-24 Testing the System---------------------------------------------------------------(04/16/99)15:39 System Status Report NCRCorp---------------------------------------------------------------Component : EPLStatus : OkComponent : CBS LinkStatus : OkComponent : Failure Detection and AnalysisStatus : OkComponent : CBS 0Status : NOT OKMeaning : Unconfigured receive antenna A for CBS 0Probable Cause : An unconfigured functional receive antennawas found.Recommended Action : The specified receive antenna isimproperly configured.Component : CBS 0Status : NOT OKMeaning : Receive antenna B failure for CBS 0Probable Cause :Recommended Action : The specified receive antenna isimproperly connected or faulty.Component : BedcheckStatus : OkComponent : EPL BridgeStatus : OkComponent : CBS ManagerStatus : OkComponent : External Data InterfaceStatus : OkComponent : Label Data ManagerStatus : Ok
Testing the System 12-25Component : LoggerStatus : OkComponent : PLU ReaderStatus : OkComponent : Price CheckerStatus : OkComponent : Price VerifierStatus : OkComponent : Promotional Message VerifierStatus : OkComponent : Data SchedulerStatus : OkComponent : Sales Price VerifierStatus : OkComponent : Table ManagerStatus : Ok---------------------------------------------------------------
12-26 Testing the SystemRunning FDA from EPL AdministrationA single–pass Failure Detection and Analysis (FDA) report on thecondition of DecisioNet System hardware and software can be createdby selecting FDA Report from the EPL Administration screen.The following menu is displayed when FDA Report is selected fromEPL Administration.After selecting the Report Type, select View or Save. If View isselected, the report is created and displayed. If Save is selected, you areprompted to enter a path and file name. After entering a path and filename, select Save to create the report and save it in the specifiedlocation.Refer to the FDA error and description table in the previous section“Using Failure and Detection Analysis Software” for an explanation ofany errors.
Testing the System 12-27BedcheckBedcheck verifies if SmarTalkers are working properly. Access theBedcheck functions on the EPL Administration application BedChkmenu.When this function starts, it continues execution as a backgroundprocess until completion or until execution is aborted. The bedcheckerrors are stored in the bedcheck log file for later analysis by the user.The DecisioNet software provides the following functions to controlthe bedcheck process.Function Name FunctionStart Bedcheck This function is used to start the bedcheckprocess to a specified SmarTalker.Stop Bedcheck This function is used to terminate bedcheckexecution.Query Status This function is used to get bedcheck statuswhen running. The DecisioNet softwarereturns the number of passed or failedSmarTalkers that have been processed already.Read BedcheckLog This function is used to read one recordsequentially from the bedcheck log file.Purge BedcheckLog This function is used to delete the log recordsthat have been read by the "Read BedcheckLog" function.For more information on the Bedcheck function, refer to the NCRDecisioNet System User’s Guide (B005-0000-1087).
12-28 Testing the SystemAnalyzing SmarTalker ProblemsThe following table shows some of the errors that may occur withSmarTalkers and the possible remedies. These types of errors arelogged in the EPL System Error Log if the Failure Detection andAnalysis software is installed in your system.Error Causes Possible Remedies No ResponseA black dot (●)displays on the LCDOut of sync. Remove the obstacle between theCBS and the SmarTalker. Contactyour NCR representative andreview the original sitecertification documents to seewhat change may have caused theproblem. Reference theCertification/Re-certification SiteSurvey Procedure (497-0410343) fordetails on the site certificationprocess.EPL No Response Hardware troubleincluding battery loss Replace with new SmarTalker.Refer to Chapter 10 or 11.EPL No Response No existence in the store. Perform a Replace EPL function asdescribed in the “Replace EPL”section of the EPL Maintenancechapter in the NCR DecisioNetSystem User’s Guide(B005-0000-1087).EPL Battery LowThe low batterysymbol ( ) displays.EPL Battery Low Replace with new SmarTalker.Refer to Chapter 10 or 11.
Testing the System 12-29FDA uses the Base Hardware configuration information to detect andlog hardware failures. FDA is included on the optional EPL SystemInformation package that must be installed and running to benefitfrom its diagnostic and logging capability. For error code descriptionsrefer to Chapter 8, “DecisioNet System Messages,” in the NCRDecisioNet System User’s Guide (B005-0000-1087).Site-specific information created during the initial installation asspecified in the Certification/Re-Certification Site Survey Procedure(497-0410343) and provided to the DecisioNet Technical SupportSpecialist at your area Managed Service Center includes the followinginformation:• Installation Site Survey/Checklist• General site data• EPL requirements• Software types and versions• Price lookup information• Dial-in support data (passwords, etc.)Using the dial-in support data, the Managed Service Center canperform all of the DecisioNet System software testing andtroubleshooting described in this chapter.
12-30 Testing the System

Navigation menu