Option 81 INI after midnight routine. 1

[pjazz]

This is a

VERSION 3311
RELEASE 25
ISSUE 40 B + DepList x112540b_cpp

This is the first time this has happened that I know off. I was trying to analyze the INI messages but having a hard time decoding them through the NTP.
Could anyone chime in if this is a real problem with the system or is this a one time occurance where the system figured it needed an ini to clear a problem.





DROL001 DAILY ROUTINE END
% DTIM LD60 END 02:07 2/8/2012
%
% INI000 00000024 02 08 39 00000000 00000000 00000000 00000000 0 1 00000000
% DSET000 DOWN LOAD 0 0 0 0 0 0 0 134085
%
% INI014 000000EF
%
% INI002 0000008A 0000008B 0000008C 0000008D
%
% INI007 00000078 00000079 0000007E 0000007F
% ACDR ACTIVATED
%

 

[bhassell2000]

I dont have anytihng for an INI 024

INI014 is Firmware Fault. nCPU clock unmasked

INI002 is a manual INI

INI007 is an overload from a persig pack



Thanks,

Buddy

Linked in Profile

http://www.linkedin.com/in/buddyhassell

 

[telebub]

My book shows:

INI 000 Fault Code 24 - not listed
INI014 - Not listed
INI002 - I/O Device Fault
INI007 - IGS Card Fault

Typically the bottom INI code is the culprit and the other INI codes above it are a result of the actual cause. I haven't broken down the hex of 78, 79, 7E, 7F but looks like an IGS issue to me.

 

[pjazz]

Thanks for the responses. I choose to ignore the first INI. 4 months later the system INI again after the midnight routine with the same codes. I was trying to decode the hex 78 79 7E 7F but I can't figure out on how to break it down. Could some one help me out.

 

[GHTROUT]

Let's see what occurs after LD60 runs

LD 22
REQ PRT
TYPE OVLY

Look for DROL. See what follows 60. That overlay number (and it's actions) is what is causing the INI.


Find more at GHTROUT.com

 

[pjazz]

Thanks this is the previous day before the recent INI.

NPR000
% DROL000 DAILY ROUTINE BEGIN
% NPR LD32 BEGIN 02:00 21/11/2012
%
% NPR029 52 0 12 10
%
% NPR029 52 0 12 8
%
% NPR029 24 0 9 11
%
% NPR029 12 0 13 10
% PBXT DONE
%
% DROL001 DAILY ROUTINE END
% NPR LD32 END 02:00 21/11/2012
%
% DROL000 DAILY ROUTINE BEGIN
% TDS LD34 BEGIN 02:00 21/11/2012
%
% DROL001 DAILY ROUTINE END
% TDS LD34 END 02:04 21/11/2012
% ST
% DROL000 DAILY ROUTINE BEGIN
% MTRK LD36 BEGIN 02:04 21/11/2012
%
% DROL001 DAILY ROUTINE END
% MTRK LD36 END 02:04 21/11/2012
%
% DROL000 DAILY ROUTINE BEGIN
% IOD LD37 BEGIN 02:04 21/11/2012
%
% PWR000 XSMC 00 0 0
%
% DROL001 DAILY ROUTINE END
% IOD LD37 END 02:04 21/11/2012
%
% DROL000 DAILY ROUTINE BEGIN
% CNF LD38 BEGIN 02:04 21/11/2012
%
% PWR000 XSMC 01 0 0
%
% PWR000 XSMC 02 0 0
%
% PWR000 XSMC 03 0 0
%
% DROL001 DAILY ROUTINE END
% CNF LD38 END 02:05 21/11/2012
%
% EDD000
% DROL000 DAILY ROUTINE BEGIN
% DUMP LD43 BEGIN 02:05 21/11/2012
%
% DB SEQ NUM = 3592
% CONFIG
% CIOD157 INFO: CMDU 0 is ACTIVE, RDUN is ENABLED
%
% PHYSICAL MAP
% BCS TEMPLATE
% PBX TEMPLATE
% CUST
% CLID
% ROUTE
% DAPC
% LTN TN
% LTN LNK
% TN
% SCL
% ESN 00
% NCTL
% ACD
% ACD SCH
% ACD IO
% AUTH 00
% CPK
% IDC TREES
% DIGITAL
% DTI
% ASNCH
% AML / ELAN
% VAS
% TRSH
% DCH
% PRI
% ARIES
% FDL
% SYSP
% XPEC
% XTDT
% FTC
% MCAD
% FCAD
% FDCT
% FFC
% LAPW
% MSDL/MISP BLK
% SOCKET ID BLK
% TIME
% DTI PDCA
% STS BLK
% CPND
% CPND NM
% SPECIFIC DATA
% HI
% ALARM_MGT
% ZONE_MGT
% CHECKING
%
% RECORD COUNT = 0303
% DATADUMP COMPLETE
% Backing up reten.bkp
%
% Starting database backup
% to floppy diskette on CMDU 0
% KEYCODE
% DIRECTORY
% CONFIG
% DATA
% HI
% ZONE
% ESET1
% ESET2
% Backing up reten.bkp to floppy
%
% Database backup Complete!
%
% DROL001 DAILY ROUTINE END
% DUMP LD43 END 02:06 21/11/2012
%
% PRI TRK LOOP 2 ATLP 0
% DROL000 DAILY ROUTINE BEGIN
% DTIM LD60 BEGIN 02:06 21/11/2012
%
% TEMU129 BackUP process ended successfully.
% Number of floppy diskette(s) used: 1
% Amount of space remaining on the last floppy: 1089
%
% SLFT OK
% TRSH CNT:
% BPV -000
% SLIPD -000
% SLIPR -000
% CRC -000
% LOSFA -000
% OS_BPV -000
% OS_LOSFA-000
% OS_YEL -000
%
% PRI TRK LOOP 18 ATLP 0
% SLFT OK
% TRSH CNT:
% BPV -000
% SLIPD -000
% SLIPR -000
% CRC -000
% LOSFA -000
% OS_BPV -000
% OS_LOSFA-000
% OS_YEL -000
%
% PRI TRK LOOP 50 ATLP 0
% SLFT OK
% TRSH CNT:
% BPV -000
% SLIPD -000
% SLIPR -000
% CRC -000
% LOSFA -000
% OS_BPV -000
% OS_LOSFA-000
% OS_YEL -000
%
% PRI TRK LOOP 51 ATLP 0
% SLFT OK
% TRSH CNT:
% BPV -000
% SLIPD -000
% SLIPR -000
% CRC -000
% LOSFA -000
% OS_BPV -000
% OS_LOSFA-000
% OS_YEL -000
%
% PRI TRK LOOP 60 ATLP 0
% SLFT OK
% TRSH CNT:
% BPV -000
% SLIPD -000
% SLIPR -000
% CRC -000
% LOSFA -000
% OS_BPV -000
% OS_LOSFA-000
% OS_YEL -000
%
% PRI TRK LOOP 61 ATLP 0
% SLFT OK
% TRSH CNT:
% BPV -000
% SLIPD -000
% SLIPR -000
% CRC -000
% LOSFA -000
% OS_BPV -000
% OS_LOSFA-000
% OS_YEL -000
%
% DROL001 DAILY ROUTINE END
% DTIM LD60 END 02:06 21/11/2012
%
% AUD000
%
% DTC001
%
% DTC001
%
% AUD000
%
% DTC001
%
% TIM422 03:00 21/11/2012 CPU 0
I don't have access to the system this evening but you can see the successful DROL ends at ld 60.

 

[StanleySteamer]

An INI after the midnight routine could be a "deferred" INI for a problem that the system was able to recover from during the day. You may see RCV messages during the day before the INI.

 

[pjazz]

You nailed it.
TIM422 13:34 21/11/2012 CPU 0
%
% DTC001
% RCV001 0061A9BC 006197F6 08FFA19F 08FC6BA9 012560F9 012533F8
% RCV001 + 01253241 0124F0D2 017B55FB 017A3D20 017A3731 017A355D
% RCV001 : 00001002 0375FEB9 00000000 00000000
%
% TIM422 13:54 21/11/2012 CPU 0
%
% AUD065 0375FEB9 00001002 00000003 00003204 00000000 00000000 00000013 0143
%
% AUD005 0375FEB9 00000000 00000000 00000000 00000000 00000000 0000000C 00003204

%
% AUD393 00003204 0362DC49 0362DC49 00000000 0362DC49
%
% AUD017 00000020 0000EFFA 0000FFFA
%
% AUD017 00000032 0000FEFE 0000FFFE
%
% AUD516 00000010 1
%
% TFS501 32 1 0
%
% TFS501 50 1 0
%
% AUD399 00000003 00000001 0000871E 0362DC49 0362DC49
%
% AUD000
%
% TIM422 14:00 21/11/2012 CPU 0
%
% DTC001
%
% ERR183 3100 61 1
%
% TIM422 14:15 21/11/2012 CPU 0
%
% DTC001
%
% ERR183 5868 51 1
%
% AUD000
%
% TIM422 14:30 21/11/2012 CPU 0
%
% DTC001
%
% DTC001
%
% AUD000
%
% TIM422 15:00 21/11/2012 CPU 0
%
% DTC001
% RCV001 0061A9BC 006197F6 00986903 00970014 08FF1ADA 00D11FE7
% RCV001 + 00D11853 0129A21F 08F84969 0128EB7D 01261FD0 01261D2D
% RCV001 : 00000900 0371D5F5 00000000 00000000
%
% ERR183 8635 51 1
%
% ERR183 2091 2 2
%
% TIM422 15:15 21/11/2012 CPU 0
%
% DTC001


RCV0001 Invalid queue information was found. The auto-recovery mechanism has
taken care of the problem

I'm not going to persue this any longer unless it happens more often.
Many thanks.