FUJ00176332
FUJ00176332
Peak Incident Management System
Call Reference PC0230183 Call Logger Deleted User -- Security Ops
Release Reported In -- HNG-X Rel. Ind. Top Ref W12214R
Call Type Live Incidents Priority B -- Business restricted
Contact Deleted Contact Call Status Closed -- Administrative Response
Target Date 23/12/2013 Effort (Man Days) 0
Summary ARQ 221 POI3529B
All References Type Value
Call reference PC0162602
Work Instruction W12214R
DevIntRel-Director Live Supp.Test
Progress Narrative
bate:20-Dec-2013 13:41:56 User:Christine Phillips
CALL PC0230183 opened
betails entered are:~
summary :ARQ 221 POT3529B
call Type:L
call Priority:B
Target Release: HNG-X Rel. Ind.
Routed to:Audit-Dev - _Unassigned_
Date: 20-Dec-2013 13:41:56 User:Christine Phillips
[Start of Response]
[there appears to be ‘gaps' in this report once run.
t've run it twice on Bootle and Wigan but still getting the same error.
lcerald Barnes I beleive was going to pursue this.
thank you
[End of Response]
Response code to call Live Incidents/Defects(L) as Incident Under Investigation (40)
jate:20-Dec-2013 14:38:51 Uscr:Gerald Barnes
[fhe Call record has been assigned to the Team Member: Gerald Rarnes
bate:20-Dec-2013 14:43:37 User:Gerald Barnes
[Start of Response]
It ain robocopying the whole ARQ to a workstation at the moment for a detailed analysis.
[End of Respons
lkesponse code to call type L as Category 40
Pending -- Incident Under Investigation
bate: 23-Dec-2013 12:12:01 User:Gerald Barnes
{Start of Response]
I have now copies of the ARQ and I am about to copy them to my PC for analysis.
[End of Response]
Response code to call type L as Category 40 -- Pending -- Incident Under Investigation
[Date:24-Dec-2013 15:28:20 Uscr:Gerald Barnes
Reference Added: 1 er
Date:24-Dec-2013 15:38:40 User:Gerald Barnes
[Start of Response]
[the GAPS only occur on the correspondence server nodes. The reason for these GAPS is covered in PC0162602. If you wish to get
spreadsheets using Bootle you must use the slow ARQ approach. Each spreadsheet will then list the GAPs but since they only occur
cor the correspondence server they do not matter too much. However there is a better approach which follows.
in the secure terminal room is a notice board (on the right wall as you enter the door). On it is a section which says "Possible
caps" and lists "2008 14 Jun to 6 Jul Cluster 3 use Wigan".
I reran a FAST ARQ on Wigan. It was OTH3127W. It ran fine. I asked for all spreadsheets. I notice that Christine said she had
ried a run on Wigan too and it had failed. Whatever reason it had failed there for must have been an intermittent problem rather
than a hard problem. I attach the output from this FAST ARQ.
[End of Response]
Response code to call type L as Category 40
Pending -- Incident Under Investigation
jbate:24-Dec-2013 15:40:20 User:Gerald Barnes
Evidence Added - Successful FAST ARQ ra
on Wigan for the period in question
FUJ00176332
FUJ00176332
flate:24-Dec-2015 15:45:16 User:Gerald Barnes
[Start of Response]
fhe reason for the failure is a known problem documented in PCO162602.
It have done this and attach the output.
[End of Response]
Response code to call type L as Category 95 -- Final -- Advice after Investigation
routing to Call Logger following Final Progress update.
spent since call received: 15 hours
cause updated to 14 -- Development - Code
[there is an notice about this problem in the secure terminal room and it states there that the FAST ARQ can be run OK on Wigan.
Date:20-dan-2014 15:26:12 User:Christine Phillips
{Start of Response]
[thank you. Disc sent to POL. Clsoing call.
[End of Response]
Response code to call type L as Category 68 -~ Final -- Administrative Response
Routing to Call Logger following Final Progress update.
jate:20-Jan-2014 15:26:16 User:Christine Phillips
CALL PCO230183 closed: Category 68 Type L
Root Cause Development - Code
Logger Deleted User -- Security Ops
Subject Product _ General/Other/Misc -- ACE (version unspecified)
Assignee Deleted User -- Security Ops
Last Progress 20-Jan-2014 15:26 -- Christine Phillips