Tape alert codes
I'm having troble trying to convert tape alert codes as explained below. Can any explain how the 1 came to be under the 22 when the tape alter number was 0x00000400 0x00000000?
This information is also recorded in the /usr/openv/netbackup/bin/bptm/log.<date> file. The bptm log may also list the meaning of the TapeAlert flag. This second example is from a different system where a TapeAlert flag was generated due to having expired cleaning media.
03:50:22.688 [3288.3396] <2> log_media_error: successfully wrote to error file - 03/31/07 03:50:22 19 TAPE_ALERT BS09_Drv3 0x00000400 0x00000000
03:50:23.594 [3288.3396] <16> process_tapealert: TapeAlert Code: 0x16, Type: Critical, Flag: EXPIRED CLEANING MEDIA, from drive BS09_Drv3 (index 19), Media Id
If the meaning of the TapeAlert number is not listed in the log then it can be converted.
The values 0x00000400 0x00000000 in the bptm log convert to:
0x00000400
(top down: one, two,.. eleven, twelve,.. ending in thirty two)
111 1111 1112 2222 2222 2333
1234 5678 9012 3456 7890 1234 5678 9012
----------------------------------------
0000 0000 0000 0000 0000 0100 0000 0000
0 0 0 0 0 4 0 0 (0x00000400)
0x00000000
(top down: thirty three, ending in sixty four)
3333 3334 4444 4444 4555 5555 5556 6666
3456 7890 1234 5678 9012 3456 7890 1234
----------------------------------------
0000 0000 0000 0000 0000 0000 0000 0000
0 0 0 0 0 0 0 0 (0x00000000)
as the format's not quite there!!
Going from the T/N that your post is taken ( http://www.symantec.com/business/support/index?page=content&id=TECH48603 ) & just cuttin out the "relevant" bit, there's a 1 under the 22 as 4 converts to 0100 in binary - at least that's how I explain it!
i.e. (once I managed to format correctly!!)
111 1111 1112 2222 2222 2333
1234 5678 9012 3456 7890 1234 5678 9012
----------------------------------------------------------------
0000 0000 0000 0000 0000 0100 0000 0000
0 0 0 0 0 4 0 0 (0x00000400)
