1:

PBX NUMBER DATA
SNB                PXR     DETY     PXRD    R1    SI
178551244          B-0     LI3      ST-0

DEV                HNB     SNB1                   SFX
LI3-14197          1       178551054
LI3-11224          0   

SNB                PXR     DETY     PXRD    R1    SI
178536576          B-1     LIMA     ST-0

DEV                HNB     SNB1                   SFX
LIMA-1234          1       17857795
LIMA-1245          0   
END

Note! The above PBX will have the DETY for PXR B-1 defined as LI3

2:

SNB's ported to another AXE is normally provided a ICS class, but remain unconnected and invisible for MaxSus in the old AXE. In special cases, diversion classes (CFUF etc.) are connected to SNB's without a device connection. Use Figaro Conversion Manager to read, log and generate DT's for SCL provision. 

3:

Test numbers (TE) have their connected device hidden, until an EXNRE command is given. MaxSus does not support EXNRE, but commands without device number is always placed in the output editor for manual intervention, even if you are migrating directly to the Terminal B. If MaxSus is attended, you can check the TE Notification, to Alert you and pause migration when a Test Number is found.

4:

PBX NUMBER DATA
SNB                PXR     DETY     PXRD    R1    SI
178551244          B-0     LI3      ST-0

DDEV               HNB     SNB1                   SFX
LI3-11197          1       178551054
LI3-11224          0       178551570

END

Most PBX's have their head number connected to the device with HNB=0, where no SNB1 is present. In this case the head number 178551244 is not connected to any device, so the PBX will not be part of the migration, if the option Migrate PBX when head number is found is selected. If the option Migrate PNB when read is selected, MuxSus will try with a SUPLI command, but it's rejected, because no PXR is defined.    
When migration is finished use SUSPP:SUT=PB; to check if all PBX's are defined. Figaro Conversion Manager can handle the SUSPP log file and generate commands for definition of PBX, SCL and SUS on basis of the SNB's found in a SUSPP log file.
For ISDN-E subscribers use the corresponding command IUSPP:SNBTY=3; to read, check and generate DT's in Figaro.

Duplicates

The same SNB number can occur multiple times in a DEVICE STATE DETAILS (STDEP) printout:

DEVICE STATE DETAILS

DEV           STATE   BLS   FTYPE   ADM     ABS    SNB       SNBST      LIST

LIBAE-29      IDLE                          H'0    23665510  IDLE       YES
                                                   32665513  IDLE
LIBAE-30      BLOC    MBL           NC      H'0
LIBAE-31      IDLE                          H'0    23665998  IDLE       YES
                                                   24665988  IDLE
LIBAE-32      IDLE                          H'0    23661655  IDLE       YES
LIBAE-33      IDLE                          H'0    23661655  IDLE       YES
LIBAE-34      IDLE                          H'0    23695215  IDLE       YES
LIBAE-35      IDLE                          H'0    24695000  IDLE       YES

END

Every time a new PBX is defined with command SUPBI or IUPBI, MaxSus updates a list of already handled PBX's to avoid generation of duplicated commands. If you migrate all devices within the same DETY in one step, you will meet no duplicates. Since the Duplicates List is cleared every time you press the Migrate button, you can meet duplicates, if you migrate small groups of LI-devices. Duplicates are a little confusing, but completely harmless. The PBX definition commands are rejected with a fault code telling, that the PBX is already defined. Ignore the fault codes, but when migration is finished use SUSPP:SUT=PB; and IUSPP:SNBTY=3; to check, if all PBX's are defined.