NetMaster SSIDB Vsam record corrupted, how to remove corrupted Vsam Key from SSIDB Vsam Dataset
Article ID: 236683
Updated On:
Products
Issue/Introduction
Starting NetMaster Network Mangement for TCP/IP SSI region and receive KEY error:
Start NMTCPSSI, the following errors are received and NMTCPSSI does not start
NF1101 STACK MONITOR ENUMERATION COMPLETE
NSN501 CONNECTED TO VTAM SNAMGMT SERVER, LEVEL: VE624 FLAGS: E0
NF5302 REFORMAT ERROR: FDBK (X/D)=84/132 ERRID (X/D)=0730/1840 KEY=060101010301C8E2D4C9D740404040404
040404040404040404040404040404040400000
NF5302 REFORMAT ERROR: FDBK (X/D)=84/132 ERRID (X/D)=0730/1840 KEY=060101010301E9C3E7404040404040404
040404040404040404040404040404040400000
NF5311 PACKET ANALYZER STATIC DATABASE PROCESSING COMPLETE
NS1092 PASS 2 CALL TO NM000F50 RETURNED R15=00000004.
NS8999 NMSSI TERMINATED 2022/02/23
IEF285I NMTCPSSI.NMTCPSSI.JOB03100.D0000009.? SYSOUT
BPXP018I THREAD 1DF5100000000000, IN PROCESS 67109297, ENDED
WITHOUT BEING UNDUBBED WITH COMPLETION CODE 0033E000
, AND REASON CODE 00000000.
IEF142I NMTCPSSI NMTCPSSI - STEP WAS EXECUTED - COND CODE 0040
Running a job to show the contents of the key shows the following:
PRINT INFILE(SSIDB) -
FROMKEY(X'060101010301C8E2D4C9D740404040404-
040404040404040404040404040404040400000') -
COUNT(1) -
DUMP
IDCAMS SYSTEM SERVICES TIME: 10:20:45 02/23/22 PAGE 2
LISTING OF DATA SET -SYS3.NETMSTR.NMTCPL.SSIDB
KEY OF RECORD - 060101010301C8E2D4C9D740404040404040404040404040404040404040404040400000
000000 06010101 0301C8E2 D4C9D740 40404040 40404040 40404040 40404040 40404040 *......HSMIP *
000020 40400000 01D80055 00240064 0020000A C8E2D4C9 D7404040 40404040 40404040 * ...Q..........HSMIP *
000040 40404040 40404040 40404040 000603E8 00D30005 03F20000 0504B000 0015044C * ...Y.L...2.........<*
000060 C8E2D440 C9D740C3 96959585 83A38996 95000404 56000404 60000804 7EE4E2C5 *HSM IP C................-...=USE*
000080 D9000404 88000C04 92E57ED5 D5E8D5E8 E8003400 78000C71 48C1F0F8 E3C3D7C9 *R........V=NNYNYY........A08TCPI*
0000A0 D7000C71 52D5C5E3 F6F14040 40000C71 5CF2F0F2 F2F0F2F1 F6000C71 66F1F0F4 *P....NET61 ...*20220216....104*
0000C0 F8F5F1F4 F4000405 14003805 1ED7D2E3 4BD7D9D6 E3D67EF6 50D7D2E3 4BD7D9D6 *85144........PKT.PROTO=6&PKT.PRO*
0000E0 E3D64BE5 C1D3C9C4 7EE8C5E2 50D7D2E3 4BD9C17E F1F04BF1 F5F64BF2 F4F94BF6 *TO.VALID=YES&PKT.RA=10.156.249.6*
000100 F6000405 28000405 78003505 82E3F1FF FFFFF1F0 4BF1F5F6 4BF2F4F9 4BF6F6FF *6............T1...10.156.249.66.*
000120 FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFF0004 *................................*
000140 058C000C 05DCE3C3 D7C9D740 4040000C 05E64040 40404040 4040000C 05F04040 *......TCPIP ...W ...0 *
000160 40404040 40400005 06400100 05064A00 00050654 01000506 5E000005 06680100 * ... ....¢.........;.......*
000180 05067200 0005067C 00000506 86000005 06900000 05069A00 000506A4 00000506 *.......@........................*
0001A0 AE140006 06B84E20 000606C2 4E200006 06CC05A0 000606D6 05A00006 06E005A0 *......+....B+..........O.....\..*
0001C0 000606EA 05A00005 06F40000 0506FE64 00050708 00000507 12000005 071C0000 *.........4......................*
0001E0 05072600 000C060E 40404040 40404040 00060730 07800006 073A0780 *........ ............ *
IDC0005I NUMBER OF RECORDS PROCESSED WAS 1
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0
How to fix KEY error instead of creating a new SSIDB Vsam dataset.
Environment
Release : 12.2
Component : NetMaster Network Management for TCP/IP
Resolution
If you have a Backup (Dasd or Dataset), you can restore that SSIDB, this is the best way to recover from this.
You could try and use a combination of a couple of IDCAMS Repro's to copy fromkey from the beginning of the file to the key before the corrupt key, then another IDCAMS Repro fromkey the key after the corrupt key to the end.
That way you will end up having everything except the corrupted KEY/record
FROMKEY(X'060101010301C8E2D4C9D740404040404-
040404040404040404040404040404040400000') -
Feedback
