FUJ00176307
FUJ00176307
Peak Incident Management System
Call Reference PC0194639 Call Logger Deleted User -- Audit-Dev
Release Targeted At -- HNG-X 02.11.00 Top Ref AUDIT _EXTRACT_CLT_0211_V060-V054
Call Type Live Incidents Priority B -- Business restricted
Contact Deleted Contact Call Status Closed -- Build Fix Available to Call Logger
Target Date 26/08/2010 Effort (Man Days) 0
Summary Audit Client does not highlight messages with duplicate message numbers
All References Type Value ;
Product Baseline AUDIT_EXTRACT_CLT_0211_D060-D054
DevintRel-Director ITU SV&I
QFP Review COMPLETE
Release PEAK PC0204191
Product Baseline AUDIT_EXTRACT_CLT_0211_V060
Product Baseline AUDIT EXTRACT _CLT_0211_V060-V054
Imy
cence Vhes eae
Unknown 09-Sep-2010 14:31:17
It is important that any duplicate messages in the retrieved audit data are highlighted to the user.
Duplicates are not being hightlighted when two message sequences have the same start and end message
sequence numbers.
ie. Sequences 2708181 to 2708188 and 2708181 to 2708188 would not be reported as duplicates.
Sequences 2708181 to 2708188 and 2708183 to 2708183 would report a duplicate.
Progress Narrative
oate:16-Feb-2010 14:11:55 User:Andrew Mansfield
cALL. PCO194639 opened
Details entered are:~
summary:Audit Client does not highlight messages with duplicate message numbers
call Type:
call Priority:B
lfarget Release:HNG-X 01.07
Routed to:Audit-Dev - Unassigned_
[Start of Response]
e have been c
age numbers
‘tly of HNG-X messages appearing in the audit files with duplicate JSNs (Journal Sequence Numbers ~
(The JSNs should form a sequence of unique numbers for each counter.)
the fact of duplicate JSNs is an issue with the counter software, but it has shown up that these duplicates are not being
leported clearly to the audit client user.
part of the function of the audit client is to analyze the message sequences and report on any issues. Gaps in the message
sequences are reported clearly to the user but duplicate message numbers are not reported clearly.
[End of Response]
Response code to call Live use error(L) as Incident Under Investigation (40)
jDate:16-Feb-2010 14:14:34 User:Andrew Mansfield
Evidence Added
screen shot showing duplicate JSN in message sequence
lOate:16-Feb-2010 14:31:01 User:Andrew Mansfield
[Start of Response]
Frx IMPACT
IMPACT ON DEVELOPMENT:
3 man days
IMPACT ON TEST:
leed to create an audit file containing a duplicate JSN and show that this
jan audit file without duplicates and check that no duplicates are reported.
reported clearly to the user. Regression test with
IMPACT ON USER:
it is possible to identify duplicates from the current output but in practice it would be very difficult to spot given the
FUJ00176307
FUJ00176307
[Eypical size of output produced:
[fhe purpose of the fix is to highlight any problem with duplicate message numbers and make it obvious to the user.
IRISKS (of releasing and of not releasing proposed fix):
[this is a low risk fix.
LIST OF LIKELY DELIVERABLES:
loueryDLL.dl1 (Audit Server component)
IAEClient.exe (Audit Workstation executable)
Routing to RMF for targeting.
{End of Response]
lkeaponae code to call type L ag Category 40 -- Pending -- Incident Under Investigation
bate:16-Feb-2010 14:32:25 Uscr:Andrew Mansfield
Defect cause updated to 14: Development - Code
jDate:16-Feb-2010 14:32:44 Uscr:Andrew Mansfield
the Call record has been transferred to the team: RelMngmntForum
JDate:17-Feb-2010 08:04:45 User:Lionel Higman
Reference Added: QFP Review COMPLETE
jDate:18-Mar-2010 18:10:49 User:Tyrone Cozens
[fhe call Target Release has been moved to Requested For -~ HNG-X R2
JDate:18-Mar-2010 18:11:09 User:Tyrone Cozens
[the Call record has been transferred to the team: Audit-Dev
Date:18-Mar-2010 18:11:36 User:Tyrone Cozens
[Start of Response]
IMP request for HNGX Release 2 (R2), to be discussed further
[End of Response]
esponse code to call type L as Category 40 -- Pending —- Incident Under Investigation
JDate:01-Apr-2010 16:48:00 User:Christopher Hammond
the call Target Release has been moved to:Requested For -- HNG-X 02.11.00.00
Ik2 RMF: no justification for inclusion in R2; no active requestor. Deferred to 02.11
jate:14-Jun-2010 15:41:16 User:Andrew Mansfield
[fhe call Target Release has been moved to Proposed For ~~ HNG-X 02.11.00,00
Jbate:14-dun-2010 15:42:35 Uscr:Andrew Mansfield
[Start of Response]
Proposed for 02.11
FIX IMPACT
IMPACT ON DEVELOPMENT:
8 man days
HMPACT ON TEST:
leed to create an audit file containing a duplicate JSN and show that this is reported clearly to the user. Regression test with
lan audit file without duplicates and check that no duplicates are reported.
IMPACT. ON USER:
tt is possible to identify duplicates from the current output but in practice it would be very difficult to spot given the
typical size of output produced.
fhe purpose of the fix is to highlight any problem with duplicate message numbers and make it obvious to the user.
RISKS (of releasing and of not releasing proposed fix):
[This is a low risk Fix.
LIST OF LIKELY DELIVERABLES:
eryDLL.dll (Audit Server component)
lARClient .exe (Audit Workstation executable)
[End of Response]
Response code to call type L as Category 40 -- Pending -- Incident Under Investigation
FUJ00176307
FUJ00176307
[ateri4-dun-2010 15:42:44 Uscr:Andrew Mansfield
the Call record has been transferred to the team: RelMngmntForum
IDate:14-ul-2010 16:03:42 User:Andrew Mansfield
Product HNG-X Platforms -- AUW-AUDIT and HSM Workstation (version unspecified) added.
jOate:20-gul-2010 16:00:05 Uscr:Tyrone Cozens
fhe call Target Release has been moved to:Targeted At -- HNG-X 02.11.00.00
flargeted at 02.11.00.00 as agreed within RMF
Jbate:20-Jul-2010 16:18:07 User:Tyrone Cozens
[fhe Call record has been transferred to the team: Audit-Dev
lbate:20-gul-2010 17:17:08 User:Adam Spurgeon
[the Call record has been assigned to the Team Member: Andrew Mansfield
jbate:23-Jul-2010 18:04:50 User:Andrew Mansfield
Evidence Added - Handover note
bate:23-gul-2010 1
[Start of Response]
Delivered in AUDIT EXTRACT CLT_0211_v060-v054
[End of Response]
Response code to call type L as Category 48 -~ Pending -- Fix Released to PIT
5:20 User:Andrew Mansfield
Jbat¢:23-Jul-2010 18:05:52 User:Andrew Mansfield
Reference Added: Product Baseline AUDIT EXTRACT CLT 0211 v060
[Date:23-dul-2010 11
IfOP Reference set to: Product Baseline AUDI'
5:54 Uscr:Andrew Mansfield
RAC’ 0211 _vo6o
jbate:23-ul-2010 18:06:13 User:Andrew Mansfield
[fhe Call record has been transferred to the team: Dev-Int-Rel
Joate:03-Aug-2010 10:20:33 User:PIT Automated User
[Start of Response]
ssigning to Integr
[End of Response]
Inesponse code to call type L as Category 48 (Fix Released to PIT)
fhe incident has been transferred to the Team: Dev-Int-Rel
[the incident has been assigned to the Team Member: Andrew Moor
bate:03-Aug-2010 10:20:34 Uscr:PIT Automated User
lkeference Added: Product Baseline AUDIT EXTRACT CLT 0211 D060-D054 (TOP Reference)
Jbate:03-Aug-2010 10:20:35 User:PIT Automated User
[Start of Response]
peak has been test installed in Integration. Moving to holding stack awaiting release
(End of Response]
Response code to call type L as Category 47 (Fix Processed by PIT)
fhe incident has been transferred to the Team: Int-Rel
Jbate:13-Aug-2010 17:12:32 User:Lionel Higman
fhe call Target Release has been moved to:Released At -- HNG-X 02.11.00
{Start of Response]
Fix applied in 02.11.00
[End of Response]
lkesponse code to call type L as Category 49
lhe Call record has been transferred to the team: Live Support Team
[fhe Call record has been assigned to the Team Member: Unassigned
Date:23-Aug-2010 13:46:49 User:PIT Automated User
[Start of Response]
Iseing processed as part of UNKNOWN
{End of Response]
response code to call type L as Category 48 (Fix Released to PIT)
ffarget Date updated: new value is 25/08/2010 18:30
FUJ00176307
FUJ00176307
Date:24-Aug-2010 0
[Start of Response]
being processed as part of UNKNOWN
[End of Response]
Response code to call type L as Category 48 (Fix Released to PIT)
target Date updated: new value is 26/08/2010 18:30
1:52 User:PIT Automated User
jbate:25-Aug-2010 10:24:52 User:Paul James
[Start of Response]
Tested on SVE rig
railed. Set up a data file with duplicate JSN before filtering a slow ARQ. No Duplicates message was found on the validation and
juery Tab.
Please route back to Development
[End of Response]
Response code to call type L as Category 50 -- Pending -~ Fix Failed
jbate:25-Aug-2010 10:48:49 User:Graham Jennings
the Call record has been transferred to the team: Audit-Dev
jDate:27-Aug-2010 11:09:22 User:Andrew Mansfield
[fhe Call record has been assigned to the Team Member: Andrew Mansfield
[Dat e:08-Sep-2010 17:28:02 User:Tyrone Cozens
Reference Adde P 04143
Date:09-Sep-2010 14:10:33 User:Andrew Mansfield
fhe call Target Release has been moved to Proposed For -- HNG-X R3
JDate:09-Sep-2010 14:11:17 User:Andrew Mansfield
fhe Call record has been assigned to the Team Member: Andrew Mansfield
Date:09-Sep-2010 14:22:52 Uscr:Andrew Mansfield
[DEVELOPMENT IMPACT OF FIX:
SPECIFY THE HNG-X PLATFORMS IMPACTE
es - affects Audit Workstation
[TECHNICAL SUMMARY:
Affects AEClient.exe
IutST OF KNOWN DIMENSIONS DESIGN PARTS AFFEC’
DIT. EXTRACT CLT
BD BY THE CHANGE:
DEPENDENCIES:
DoS THE FIX REQUIRE ANY MANUAL DEPLOYMENT BASELINES:
No
DEV EFFORT IN MANDAYS:
lrix available.
HMPACT ON USER:
Ibuplicates are not reported if two sequences have the same start and end sequence numbers.
ie. two sequences with message numbers:
2708181 to 2708188
2708181 to 2708188
ould not be reported as duplicates.
[the sequences:
2708181 to 2708188
2708183 to 2708185
Would report the duplicates.
HMPACT ON OPERATIONS:
FUJ00176307
FUJ00176307
IMPACT ON TEST:
Need to check that duplicates are reported for two message sequences with the same start and end message sequence numbers.
IRISKS (of releasing and of not releasing proposed fix):
Fix is low risk.
tt is important that duplicates are highlighted to the user.
LIST OF LIKELY DELIVERABLES:
lAUDIT EXTRACT CLT baseline
Jbate:09-Sep-2010 14:31:17 User:Andrew Mansfield
IA new Business Impact has been added:
tt is important that any duplicate messages in the retrieved audit data are highlighted to the user.
buplicates are not being hightlighted when two message sequences have the same start and end message sequence numbers.
i.e. Sequences 2708181 to 2708188 and 2708181 to 2708188 would not be reported as duplicates.
sequences 2708181 to 2708188 and 2708183 to 2708183 would report a duplicate.
lDate:09-Sep-2010 14:35:29 User:Andrew Mansfield
[the Call record has been transferred to the team: RelMngmntForum
Date:09-Sep-2010 17:14:58 User:Tyrone Cozens
Reference Added: PC020.
elease
Date:09-Sep-2010
Itgnore PCO204143
9:33 User: Tyrone Cozens
lbate:22-Sep-2010 11:02:57 User:Tyrone Cozens
[the Call record has been transferred to the team: Live Supp.Test
Date:22-Sep-2010 11:03:06 User: Tyrone Cozens
[fhe call Target Release has been moved to Targeted At -- HNG-X 02.11.00
Jbate:22-Sep-2010 11:03:20 User:Tyrone Cozens
lAlready on release note, so routing to Live Supp Test.
Date:12-Oct-2010 19:31:41 User: Tyrone Cozens
lneference Deleted: Release PEAK PC0204143
[Date:10-Dec-2010 09:09:55 Uscr:Sheila Bamber
the Call record has been assigned to the Team Member: Release to Live
jDate:16-Dec-2010 10:44:34 User:John Rogers
[Start of Response]
lfested in LST as part of Release Note HRU7045 (Various Audit Fixes for Release 02.11)
jfesting completed successfully, on 14.10.2010.
Returning call for closure.
[End of Response]
Response code to call type L as Category 61 -- Final -
outing to Call Logger following Final Progress update.
Build Fix Available to Call Logger
Joate:16-Dec-2010 10:50:52 User:Andrew Mansfield
CALL PC0194639 closed: Category 61 Type L
Root Cause Development - Code
Logger Deleted User -- Audit-Dev
Subject Product Estate Management -- Audit (version unspecified)
Assignee Deleted User -- Audit-Dev
Last Progress 16-Dec-2010 10:50 -- Andrew Mansfield