FUJ00171892
FUJ00171892
Peak Incident Management System
Call Reference PC0205353 Call Logger Deleted User -- QC Interface
Release Targeted At -- HNG-X 03.13 Top Ref PC0206076
Call Type Quality Centre Raised Incidents/Defects Priority A -- High Impact - Priority 4
Contact Deleted Contact Call Status Closed -- S/W Fix Available to Call Logger
Target Date 31/10/2010 Effort (Man Days) 0
Summary LST - Audit - Duplicate message sequences are not reported if they are identical
All References Type Value
DevintRel-Director QC Interface
Product Baseline AUDIT EXTRACT CLT 0313 V063-V062
QC_DEFECTID 14356-hng_x_hng x _release_1_db.
QC Severity 3 - High
Product Baseline AUDIT_EXTRACT_CLT_0313_V063
Release PEAK PC0206076
Product Baseline AUDIT_EXTRACT_CLT_0313 D063-D062
QC Defect No 14356
Impact
Si ee : User Date
Unknown 25-Oct-2010 15:32:36
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.
This is a very serious issue. We experienced the presence of duplicate Horizon transactions which were not
removed when the HNG-X application was introduced. POL did not accept a manual workaround and the
ARQ service basically stopped for almost 2 months.
The issue contained in this PEAK came to light on 21 October and I have instigated the creation of a macro
which will identify if duplicated transactions are contained within a spreadsheet. We will need to generate
an additional spreadsheet containing the JVN and check for duplicates by using the macro. This will
increase our work load by 15-20 minutes for each ARQ containing HNG-X transaction records.
The real problem will arise if we do identify duplicate transactions because POL is not likely to accept a
workaround for transaction records used for litigation support.
Penny Thomas
Progress Narrative
bate:i4-Oct-2010 15:15:10 User:dohn Rogers
CALI PCO205353 opened
petails e: ed are:
summary = Audit - Duplicate message sequences are not reported if they are identical
call Type
call Priority:B
lfarget Re ING-X 01.07
Routed to:QFF - Unassigned_
Jbate:14-Oct-2010 15:15:10 User:John Rogers
Jteieeetsteeiesiteieée Quality Centre Bug Report +##++tttitereireries
FUJ00171892
FUJ00171892
Bug Reference: 14356-hng_x_hng_x_release_1 db.
fest Date: Oct 14 2010 12:00AM
t User: rogers}
> Impact: 3 = High
Patheode: Path201
loTr Team: None
product: Infrastructure
Product Version: N/A
summary: LST - Audit ~ Duplicate message sequences are not reported if they are identical
incident Description:
this defect follows on from PCO194639.
tf two Audit Tracks contain exactly the same message sequence then these are not reported as duplicate messages.
li-e.
wdit Track A contains the message sequences 2708181 to 2708188 and
wdit Track B also contains the message sequences 2708181 to 2708188 then these messages are not reported as duplicates.
comment:s:
ohn Rogers <rogersj>, 14/10/2010 1.
Htmpact
[fhe use of Audit Tracks in legal actions may be invalidated if duplicate messages are not identified.
0r35:
jDate:414-Oct-2010 15:34:20 Uscr:Lionel Higman
[the Call record has been transferred to the team: Audit-Dev
Jbate:15-Oct-2010 14:36:56 User:Andrew Mansfield
Ithe Call record has been assigned to the Team Member: Andrew Mansfield
Jbate:18-Oct-2010 17:27:27 User:Andrew Mansfield
Product HNG-X Platforms -~ Audit Workstation (AUW) (vers
ion unspecified) added.
Jbate:18-Oct-2010 17:29:25 User
[Start of Response]
[DEVELOPMENT IMPACT OF FIX:
‘Andrew Mansfield
SPECIFY THE HNG-X PLATFORMS IMPAC
les - affects Audit Workstation
[TECHNICAL SUMMARY:
ffects AEClient.exe
tS? OF KNOWN DIMENSIONS DESIGN PARTS AFFECTED BY THE CHANG!
\UDIT_EXTRACT_CLT
DEPENDENCIES:
jone.
DOES THE FIX REQUIRE ANY MANUAL DEPLOYMENT BASELINES:
DEV EFFORT IN MANDAYS
fix available.
HMPACT ON USER:
jbuplicates are not reported if two sequences have the same start and end sequence numbers.
lie. 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
jwould report the duplicates.
IMPACT ON OPERATIONS:
No
IMPACT ON TEST:
leed to check that dup]
tes are reported for two message sequences with the same start and end message sequence numbers.
RISKS (of releasing and of not releasing proposed fix):
Fix is low risk.
Itt is important that duplicates are highlighted to the user.
I.Ist OF LIKELY DELIVERABLES:
FUJ00171892
FUJ00171892
DIT EXTRACT CLT baseline
[End of Response]
Response code to call type Q as Category 41 -- Pending -- Product Error Diagnosed
Date:18-Oct-2010 17:30:15 User:Andrew Mansfield
lA new Business Impact has been added:
tt is important that any duplicate messages in the retrieved audit data are highlighted to the user.
uplicates 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.
jbate:18-Oct-2010 17:33:06 Uscr:Andrew Mansfield
the Call record has been transferred to the team: QFP
jbate:19-Oct-2010 08:30:07 User:Lionel Higman
the Call record has been transferred to the team: RelMngmntForum
Jbate:20-Oct=2010 13:56:54 User:Tyrone Cozens
[Start of Response]
Proposed for 04.00, Tom Northcott to confirm if acceptable
[End of Response]
lkesponse code to call type Q as Category 41 -- Pending -- Product Error Diagnosed
bate: 22-Oct-2010 18:08:16 User:Tyrone Cozens
fhe call Target Release has been moved to:Targeted At -- HNG-X 04.00
largeted at release 04.00 as agreed with Tom Northcott and RMF
Jbate:22-Oct-2010 18:10:36 User: Tyrone Cozens
[the Call record has been transferred to the team: Audit-Dev
Date:25-Oct-2010 09:46:45 User:Andrew Mansfield
[the Call record has been assigned to the Team Member: Andrew Mansfield
Date: 25-Oct-2010 15:32:36 User:Penny Thomas
[fhe Business Impact has been updated:
It is important that any duplicate messages in the retrieved audit data are highlighted to the user.
Jbuplicates 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.
\This is a very serious issue. We experienced the presence of duplicate Horizon transactions which were not removed when the HNG-X
lapplication was introduced. POL did not accept a manual workaround and the ARQ service basically stopped for almost 2 months.
[the issue contained in this PEAK came to light on 21 October and I have instigated the creation of a macro which will identify if
Jduplicated transactions are contained within a spreadsheet. We will need to generate an additional spreadsheet containing the JVN
land check for duplicates by using the macro. this will increase our work load by 15-20 minutes for each ARQ containing HNG-X
transaction records.
the real problem will arise if we do identify duplicate transactions because POL is not likely to accept a workaround for
transaction records used for litigation support.
Penny Thomas
Date: 25-Oct-2010 15:42:32 Usor:Penny Thomas
[Start of Response]
\dditionally, this is service impacting for the Prosecution & Litigation Service; POL will not accept a workaround relating to
litigation support so this fix needs to be tested and applied as a matter of urgency.
Penny Thomas
[End of Response]
lkesponse code to call type Q as Category 41 -- Pending -- Product Error Diagnosed
lbate:27-Oct-2010 07:27:18 User:John Boston
{the call Priority has been changed from B
fhe call Priority is now A
FUJ00171892
FUJ00171892
[bate:27-Oct=2010 07:27:52 User:dohn Boston
the call Target Release has been moved to Targeted At -- HNG-X 03.13
Jbate:27-Oct-2010 0
IMF 26/10/10 Agreed -
for this.
9:44 User:dohn Boston
0 retarget for HINGX 03.13 to enable urgent fix to be released. Steve Goddard to liaise with Andrew Aylward
lOate:27-Oct-2010 09:05:33 User:Steve Goddard
{Start of Response]
it will be Andrew Mansfield (not Aylward).
[End of Response]
response code to call type Q as Category 41 -- Pending -- Product Error Diagnosed
Jat o:27-Oct-2010
:vidence Added ~
2:39 Uscr:Andrew Mansfield
ndover note
ldate:28-Oct-2010 15:02:08 User:Andrew Mansfield
Reference Added: Product Baseline AUDIT EXTRACT CLT_0313_v063
[Date:28-Oct-2010 1:
tor Reference set t
2:09 Uscr:Andrew Mansfield
Product Baseline AUDIT EXTRACT CLT_0313_v063
[Date:28-Oct-2010 15:09:46 Uscr:Andrew Mansfield
[Start of Response]
tested by opening a new slow ARQ, retrieving BRDB data and proceeding to the filtering stage. Then edit one of the retrieved
files in the EXTRACTED AT folder for this ARQ on the audit server so that there are two identical sequences of JSNs in the file.
then perform a filtering operation and view the message sequences on the ‘Validation and Query’ tab. The duplicate sequences
should be highlighted in blue.
Fixed in incremental baseline AUDIT EXTRACT CLT_0313_vo63-vo62.
{End of Response]
kesponse code to call type Q as Category 48 -- Pending -- Fix Released to PIT
jDate:28-Oct-2010 15:09:57 User:Andrew Mansfield
[fhe Call record has been transferred to the team: Dev-Int-Rel
bate: 28-Oct-2010 1
[Start of Response]
ssigning to Integrator
[End of Response]
Response code to call type Q as Category 48 (Fix Released to PIT)
the incident has been transferred to the Team: Dev-Int-Rel
[fhe incident has been assigned to the Team Member: Geoff Inglis
2:26 Usor:PIT Automated User
bate: 28-Oct-2010 16:32:26 User:PIT Automated User
lkeference Added: Product Baseline AUDIT EXTRACT C!
" 0313_D063-D062
pats:29-Oct-2010 0:
[Start of Response]
Peak has been test installed in Integration. Moving to holding stack awaiting release
[End of Response]
lkesponse code to call type Q as Category 47 (Fix Processed by PIT)
[the incident has been transferred to the Team: Int-Rel
7:26 User:PIT Automated User
bate:29-Oct-2010 08:32:21 User:PIT Automated User
[Start of Response]
Peak has been test installed in integration, routing back to source.
[End of Response]
Response code to call type Q as Category 60 (S/W Fix Available to Call Logger)
target Date updated: new value is 31/10/2010 18:30
Routing to Call Logger following Final Progress update.
[Date:04-Nov-2010 11:03:09 User:Tyrone Cozens
Reference Added: Release PEAK PC
[Date:25-Nov-2010
tneident closure
comments Update:
5:12 User:John Rogers
ived from Quality Centre
FUJ00171892
FUJ00171892
flohn Rogers <rogersj>, 25/11/2010 14:01:28:
closing call
cleared in Release 3.13 (Audit System) and tested in LST under Release Notes HRU?7206 and HRU7239.
JDate:25-Nov-2010 18:15:12 User:John Rogers
CALL PC0205353 closed: Category 60 Type 0
Root Cause General - Unknown
Logger Deleted User -- QC Interface
Subject Product QC Defects -- Infrastructure (version: 1)
Assignee Deleted User -- QC Interface
Last Progress 25-Nov-2010 15:15 -- John Rogers