[ Pobierz całość w formacie PDF ]
.Pro-gram corrections are used at Ericsson in internal projects during differenttest phases.Program corrections are also used for released products usedin the field (live exchanges).Handling of corrections at Ericsson, and type of corrections used, differsbetween different projects and different Ericsson companies.All faults found during testing must be trouble reported.A trouble report iswritten by the tester and sent to the responsible designer.Normally MHSis used for handling Trouble Reports.The Trouble Report should describethe fault, describe how the fault can be reproduced, and the tester can also,in the Trouble Report, propose a solution to the fault.The proposed solu-tion should contain, if possible, both the HLPLEX/PLEX-solution and thecorresponding ASA-solution.The ASA-solution proposed in the TroubleReport is normally called an Emergency Correction (EC).With this ECloaded in the system, the tester can continue testing his function/testobject.It s called an Emergency Correction since it temporarily seems tosolve the fault found by the tester and he can continue testing, but the solu-tion is not approved by the designer and this means that it might not be acorrect solution to the fault.Testers are not allowed to pass Test Cases withhelp of non-approved ECs.ECs are used both internally at Ericsson, in theprojects and in the field to solve faults temporarily.52 Correction HandlingThe designer receives the Trouble Report and he/she immediately starts toanalyze the fault.If the result of the analysis shows that a correction is tobe written for the fault, the designer indicates this in the Trouble ReportAnswer that s sent back to the issuer of the Trouble Report.The type ofcorrection written by the designer depends on the status of the product/block that is to be corrected.A correction for a non-released block iscalled a Test Correction (TC).This type of correction is usually used dur-ing Function Tests.Corrections written for released blocks are calledApproved Corrections (AC).Approved Corrections are used in late testphases, e.g., Source System Test and AS Verification and for products thatare released and in service.Both Test Corrections and Approved Correc-tions replace Emergency Corrections when they are loaded into the sys-tem.It s extremely important that released Test Corrections (TC) andApproved Corrections (AC) are correct since a faulty correction maydamage the system.The responsible designer must make sure that thewritten correction has the correct syntax (support for this is available inMHC-CH).The correction must also be tested thoroughly.It must be veri-fied that the correction solves the fault it s intended to solve and it mustalso be verified that introduction of the correction doesn t destroy anyother functionality in the block.All written corrections must be test loadedbefore they are released in order to verify that they have correct syntax andthat the corrections are loaded at valid addresses.The Correction AreaCorrections are made in the Program Store (PS) unless they involve themodification of a variable.There is one correction area per function blockin the system.It is located after the program code part in each functionblock.The correction area is used to store the new and the old code when acorrection is inserted.It consists of one or several correction records, eachcontaining information on a correction or indication that the correctionrecord is idle.When applying new corrections to the software unit, the cor-rection information is stored in an idle correction record.The correction area also stores the identity and the state of the correction.When a correction is inserted, a jump is made to the correction area wherethe new code is stored.Figure 3.2 shows an example of a block and itscorrection area.53 Program Corrections and ASAPSSignal Distribution TableCorrection 2Signal Sending TableProgramCorrection 1Data for correction 1Data for correction 2CorrectionAreaFree areaFigure 3.2A block stored in the Program Store with 2 corrections.Note: A correction record is identified by the Correction PoinTeR, CPTR.The value of the correction pointer equals the offset from the CorrectionArea Start Address (CASA) to the first word in the correction record.Theorder in which the correction records appear in the correction area is coin-cidental.The size of the correction area is not fixed.Instead, it adapts dynamicallyto the space required to store the applied corrections.If no correctionsapply to the software unit, no correction area is allocated.Nevertheless,the correction area can also be increased by commandPCCAS.The size ofthe correction area is 1024 words for both APZ 211 and APZ 212.Figure 3.3 shows the command how to check the correction area of blockMMM.Note: This command together with all following commands in this chaptercan be used for both APZ 211 and APZ 212.The structure of the printoutwill differ slightly between the different control systems.All printouts inthis chapter were made on an APZ 212.54 Correction Handling
[ Pobierz całość w formacie PDF ]
