Scribd
Upload
138 views

Usefull IOG Health Checkup Commands

The document provides a series of actions to check the status of various systems and components through a series of print commands. It includes checking alarms, node configurations, link status, fault detection logs, suspect boards, system lists, software characteristics, restart data, event logs, hardware data, I/O unit modes, maintenance files, trace system status, restart logs, transaction logging, DCS components, media attributes, volumes and files, STS database, I/O devices, JTP applications, file attributes, file lists, charging output files, charging data transfers, and load statistics on both nodes. Any issues identified need to be investigated and resolved by following the relevant instructions.

Uploaded by

Rajesh M
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
138 views

Usefull IOG Health Checkup Commands

The document provides a series of actions to check the status of various systems and components through a series of print commands. It includes checking alarms, node configurations, link status, fault detection logs, suspect boards, system lists, software characteristics, restart data, event logs, hardware data, I/O unit modes, maintenance files, trace system status, restart logs, transaction logging, DCS components, media attributes, volumes and files, STS database, I/O devices, JTP applications, file attributes, file lists, charging output files, charging data transfers, and load statistics on both nodes. Any issues identified need to be investigated and resolved by following the relevant instructions.

Uploaded by

Rajesh M
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 7

IOG HEALTH CHECK

Action : Print the Alarm list . ALLIP; Comment : Analyse and clear any IOG related Alarms, following the relevant OPIs .

Action :

Print the SPG node configuration status. IMMCT:SPG=0; IMCSP; NODE CONFIGURATION STATUS SPG 0 NPAIR 1 END; EX NODE CM STATUS STATE A 1 WORKING NORMAL SB NODE CM STATUS STATE B 2 WORKING NORMAL

Comment :

The result printout should be as shown above. If its different then start an Investigation into why .

Action :

Print the SP Link Data to check that the State for both links is WO . EXSLP:SPG=0;

Comment :

Dont continue until both links are in state WO.

Action :

Print the SP Fault Detection Log and the SP Unit Repair List for both Nodes. DISFP:SPG=0; RESUP:SPG=0,NODE=A; RESUP:SPG=0,NODE=B;

Comment :

If there are any boards listed for any of the above print commands , then follow The next action.

Action :

If there are suspect boards detected then perform a repair check. BLSNI:SPG=0,NODE=sb_side; RESUI:SPG=0,NODE=faulty_node; a) If the result is O.K , then deblocked the standby node. BLSNE:SPG=0,NODE=sb_side; b) If the result is Not O.K , then follow the relevant OPI to clear the fault.

Action :

Print the SP system list for both nodes and check that the correct system is Active in both nodes. LASYP:SPG=0,VNODE=A; LASYP:SPG=0,VNODE=B;

Action :

Print the SP Software Characteristics for the active system shown in the previous Printout for Node-A. LASSP:SPG=0,VNODE=A,SYSTEM=active_system,SIZE=ALL;

Action :

Print the Node Restart Data for both nodes. IMMCT:SPG=0; IMRDP:NODE=A; IMRDP:NODE=B; END;

Action :

Print the SPS Event Log for both nodes. IMMCT:SPG=0; IMALP:NODE=A; IMALP:NODE=B; END;

Action :

Print the SP Hardware Data for both nodes. IMLCT:SPG=0; IMHWP:NODE=A; IMHWP:NODE=B; END;

Action :

Print the IO Unit Modes for both nodes. IMMCT:SPG=0; INIOP:NODE=A; INIOP:NODE=B; END;

Action :

Print the Status of Files Subject to Maintenance. IMLCT:SPG=0; INMFP; END;

Comment :

If the printout contains entries, then investigate and clear using the relevant OPIs.

Action :

Print the SP Trace System Status IMLCT:SPG=0; IMTSP;

Comment :

If the STATUS is ACTIVE/S, then print the SP Trace System Log Status for Both Nodes. IMTLP:NODE=ALL; END;

Action :

Print the SP Restart Log Incident List. IMLCT:SPG=0;

IMRLP:PTYPE=INCIDENT; END;

Action:

Print the Transaction Logging conditions and current operating state. IMLCT:SPG=0; MCTLP; END;

Action :

Print the DCS Line Unit Data and status. IMLCT:SPG=0; ILLUP; END;

Action :

Print the DCS Port Data and status. IMLCT:SPG=0; ILNPP; END;

Action :

Print the DCS Route Data and status. IMLCT:SPG=0; ILROP; END;

Action :

Print the Media Attributes for HD-1 in Node A. INMCT:SPG=0; INMEP:NODE=A,IO=HD-1; END;

Action :

Print the SP Volume and File information. INMCT:SPG=0; INVOP; INVOP:VOL=( each volume from the previous printout ) ; INFIP; END;

Action :

Print the STS Data Base configuration data. IMLCT:SPG=0; SDDOP:OBJTYPE=ALL,AREA=OPER; END;

Action :

Print the IO Device Data and status. IOIOP:IO1=ALL;

Action :

Print the JTP Application Data and status. EXJAP:APPL=ALL;

Action :

Print the File attribute Infinite Sequential File. IOIFP;

Action :

Print the File Process Utility file list. INFUP;

Action :

Print the Common Charging Output File Status Data. CHOFP:FN=ALL;

Action :

Print the Common Charging Output Chargeable Duration Data. CHODP:FN=ALL;

Action :

Print the Common Charging Output File Attribute Data. CHOTP:FN=ALL;

Action :

Print the Common Charging Output User Function Data. CHOUP:FN=ALL;

Action :

Check for Charging Output. SAAEP:SAE=500,BLOCK=CHOFTT;

Comment :

Repeat the command a few times to verify that the NIU changes.

Action :

Check which is the Active TT Subfile ( ACTIVESUB ).. IOIFP:FILE=TTFILE00;

Action :

Verify that Charging Data is being transferred to the active subfile. INMCT:SPG=0; INFIP:FILE=TTFILE00- ( ACTIVESUB ); END;

Comment :

Check for NUSER = 1 in the File Attributes printout. Also repeat the above Command over a period of time to verify that the SIZE is increasing.

Action :

Verify that all the TT Subfiles have been transferred to XMATE. INFSP:FILE=TTFILE00,DEST=XMATE;

Comment :

Investigate any file transfer failures.

Action :

Check on XMATE for the Statistics Data Reports on SP LOAD for both nodes.

You might also like