FOR INTERNAL USE ONLY 1 (7)

Bharti FM-BSS 22-Oct-2012

BHARTI FM-BSS
WDU REPLACEMENT PROCEDURE
 FOR INTERNAL USE ONLY 2 (7)

Bharti FM-BSS 22-Oct-2012

REPLACING A HARD DISK UNIT (WDU)

MUST REMEMBER
You should have an initialized WDU at your disposal. Here we assume WDU-1 is faulty and during the activity
please mind the below points.

1) Block Command Calendars

2) Make sure there should be no other activity is in process during the replication process i..e.step-22
3) Stop all activities on the SCSI bus(like FDU) where you are making changes

PROCEDURE
1. Find the states of the WDUs (EG:-WDU-1)

ZISI: :WDU,1:;

2. Dump the data files from OMU and MCMU to disks of OMU

ZDFC:OMU;

ZDFC:MCMU,0; (Working MCMU)

NORMALLY THESE COMMAND END WITH ERROR"

/*** DX ERROR: 11502 ***/
/*** UPDATE FAILED TO I/O UNIT W1 ***/

3. Copy ALL databases from memory to disk

ZDBC:BSDATA,0;
ZDBC:EQUIPM,0;
ZDBC:OEDATA,0;
ZDBC:ILDATA,0:;
ZDBC:PDDATA,0:;

4. See the database file in BSC

ZDBL:;

ZDUR;

"EXP.

BSC3i B012GAY1 2010-10-24 02:46:26

DATABASE OCCURRENCE UNIT DB FAMILY FILES BASE DB IDENTIFIER

BSDATA 0 MCMU 019B 06390000 0009

EQUIPM 0 OMU 01C5 06A50000 0011
OEDATA 0 MCMU 0262 07BD0000 0022
 FOR INTERNAL USE ONLY 3 (7)

Bharti FM-BSS 22-Oct-2012

ILDATA 0 OMU 0679 0B640000 0069

PDDATA 0 MCMU 06AE 0BA60000 006A

5. Prevent file updates and disk updates of databases

ZDUP:;

6. Prevent file updates and disk updates of databases

ZDBP:<database name>,<occurrence>:DISK;

ZDBP:BSDATA,0:DISK;
ZDBP:EQUIPM,0:DISK:;
ZDBP:OEDATA,0:DISK:;
ZDBP:ILDATA,0:DISK:;
ZDBP:PDDATA,0:DISK:;

7. Check for database either they get Prevent or not

ZDBS:BSDATA,0;
ZDBS:EQUIPM,0;
ZDBS:OEDATA,0;
ZDBS:ILDATA,0;
ZDBS:PDDATA,0;

NOTE: O/P should be

MEMORY UPDATES PREVENTED SHOULD BE " YES " STATE

DISK UPDATES PREVENTED SHOULD BE " YES " STATE

8. Check that all databases have been unpacked from the disk log to the disk database (DBX)

The command unpacks the disk logs if they are not empty.

ZDBX:<database name>,<occurrence>;

ZDBX:BSDATA,0:;
ZDBX:PDDATA,0:;
ZDBX:ILDATA,0:;
ZDBX:EQUIPM,0:;
ZDBX:OEDATA,0:;

9. CHECK THE PLUG-IN INFO OR FIND THE TRACK NO OF PLUGIN UNIT ZWTI:P:OMU:;

10. Block the WDU you are changing to BL-US state

ZISC:,<destination unit>,<pair>:<I/O device type>,<I/O device index>:<working state>;

ZISC::WDU,1:BL-US,;
ZISC::WDU,1:MI-US,;

11. Block the other I/O devices (FDU) on the same unit pair's SCSI bus

ZISC::FDU,00:BL-US,;
 FOR INTERNAL USE ONLY 4 (7)

Bharti FM-BSS 22-Oct-2012

12. Check that the state of the hard disk to be replaced is correct (BL-US/MI-US)

ZISI:,<destination unit>,<pair>:<I/O device type>,<I/O device index>;

13. Remove the WDU from the OMU computer cartridge:

1) Switch off power by pressing the 'OFF' button and wait about 7 seconds, until the 'Power Off' led lights.

2) Remove the WDU unit from the cartridge.

14. Check the jumper settings of the new WDU

15. Install the new WDU to the OMU computer cartridge:

Install the WDU to the cartridge and wait about 3 seconds, Until the 'OFF' led is off.

16. After placing new WDU, Change the state of the new WDU to WO-ID (ISC)

ZISC:,<destination unit>,<pair>:<I/O device type>,<I/O device index>:<working state>;

ZISC::WDU,1:WO-ID,;

17. Check that the new disk is the backup disk (WB) (IWQ)

***Note that the command does not end in a semicolon.

ZIWQ:,<destination unit>,<pair>
BY COMPAIRE THIS WITH ZISI::WDU;

IF WDU-0 is Faulty then WS=1, WB=0

IF WDU-1 is Faulty then WS=0, WB=1

18. Format the new hard disk. (This process can take 30 to 60 min.)

Initialize WDU
ZIWI:,OMU:WB,F5,NAME,FFF,02,AG:;

Format WDU

ZIWK:,:WB,,NAME,FF,,AG:;

19. Change the states of other I/O devices on the same SCSI bus (Change the states of FDU to WO-BU)

20. Diagnose the WDU (UDD)

Before diagnostic, change the state of WDU to TE-ID using command ZISC::WDU,1:TE-ID;

ZUDD: <main unit type>, <pair>, <main unit index>: <device type>, <device index>;

ZUDD:OMU,0:WDU,1;
If the diagnosis is successful, you will see diagnostic report 3999 DIAGNOSIS EXECUTED - UNIT OK
 FOR INTERNAL USE ONLY 5 (7)

Bharti FM-BSS 22-Oct-2012

21. Change the working state of the new WDU to WO-BU (ISC)

ZISC:,<destination unit>,<pair>:<I/O device type>,<I/O device index>:<working state>;

ZISC:,OMU:WDU,1:WO-BU;

22. Copy the system WDU to the new WDU (IPS) including subdirectories, using the default and active build
directory name 'ASE_1_28_0'. Use ZWQO:CR; to verify build directory name.

ZIWY:S:SYSTEM=,UNIT=OMU,PATH=/,DRIVE=WDU-S,; (Create Source)

ZIWY:D:SYSTEM=,UNIT=OMU,PATH=/,DRIVE=WDU-B,; (Create Destination)

ZIBC:,,,,,,,,,DIR:; (Copy Source to Destination)

***IF Files are not getting transfer to new disk using above commands, then need to create source and
destination using below commands

ZIPS:<source unit>,<source I/O device>,<source path>,,:,<destination I/O device>,<destination

path>,,:<directory mode>,<copy task name>;

ZIPS:"OMU",WDU-S,/ASB_1_34_0,:,WDU-B,/,:DIR=INC,NAME=COPY,;
ZIPS:OMU,WDU-S,/ASC_1_40_0,:,WDU-B,/,:DIR=INC,NAME=COPY; OR

ZIPS:,WDU-S,/,,:,WDU-B,/,:NAME=COPY,DIR=INC,::;

Now, Check the progress of the copy task to see when it is ready.

ZIPI: NAME=<copy task name>;

23. Kill GEORGE Use service terminal command to prevent the log files of Q3 Disseminator getting corrupted.

ZDDS:;

00-MAN>OD: 2B1

24. Remove LOGRECS* files from the disks LFILES on both OMU disks

Use service terminal command MD in order to maintain the required syncronisation status between
DEEGUT and GEORGE during the hard disk change. Use ZWQO:CR; to verify build directory name. Here
build directory name is ASE_1_28_0.

ZMD: W0-/<Build directory name>/LFILES/LOGR*.*

ZMD: W1-/<Build directory name>/LFILES/LOGR*.*

ZDDS:;

WELCOME TO SERVICE TERMINAL DIALOGUE

 FOR INTERNAL USE ONLY 6 (7)

Bharti FM-BSS 22-Oct-2012

0- MAN>ZMD:W1-/ASE_1_28_0/LFILES/LOGR*.* (Also use the same command for W0)

Sample Output:

DELETING FILE: W1-/ASE_1_28_0/LFILES/LOGRECSD01.DAT:00

EXECUTED
DELETING FILE: W1-/ASE_1_28_0/LFILES/LOGRECSD03.DAT:00
EXECUTED
DELETING FILE: W1-/ASE_1_28_0/LFILES/LOGRECSD02.DAT:00
EXECUTED
DELETING FILE: W1-/ASE_1_28_0/LFILES/LOGRECSD04.DAT:00
EXECUTED
00000004 FILES DELETED

25. Resume updates of disks and memory file disk copies of the databases which you prevented before
changing the WDU

ZDUR;

ZDBR:BSDATA,0:DISK;
ZDBR:EQUIPM,0:DISK:;
ZDBR:OEDATA,0:DISK:;
ZDBR:ILDATA,0:DISK:;
ZDBR:PDDATA,0:DISK:;

26. Check that the database states are restored to 'normal' or 'dumping' (DBS)

ZDBS:<database name>,<occurrence>; //The command displays the states of the databases.

ZDBS:BSDATA,0;
ZDBS:EQUIPM,0;
ZDBS:OEDATA,0;
ZDBS:ILDATA,0;
ZDBS:PDDATA,0;

NOTE: O/P should be

MEMORY UPDATES PREVENTED SHOULD BE " NO " STATE

DISK UPDATES PREVENTED SHOULD BE " NO" STATE

27. Copy the data from database to disk

ZDBC:<database name>,<occurrence>;

ZDBC:BSDATA,0:;
ZDBC:EQUIPM,0:;
ZDBC:OEDATA,0:;
ZDBC:ILDATA,0:;
ZDBC:PDDATA,0:;

28. Check that the states of the units are correct (WO-EX, SP-EX) (USI)

ZUSI:<unit type>,<unit index>;

 FOR INTERNAL USE ONLY 7 (7)

Bharti FM-BSS 22-Oct-2012

29. Restart OMU (USU) ZUSU:OMU:C=DSK;

30. Take Fall Back

ZWKS:MODE=FULL,NAME=FB011211,DIRE-FB011211:;

31. Check for consistency of both BU & FB packages

ZWQB:NAME=directory_name:FORM=FAILED:;

SOME POINTS NEED TO BE CHECKED AFTER THE ACTIVITY

1) Check state of both WDU

2) Check Measurements are getting transfer or not atleast for next two hours. If found any issue escalate the
same to your SPOC and perform necessary action.

3) Check for critical alarms at BSC.