KSDNC

[DevPlan]

I have BC10 and according to Dynatext for BC10 the command KSDNC should work but is not known by my BC10. The EXDNC (for analogue extention) works fine. Is KSDNC not available in BC10?

 

[rrmagno]

These commands are for BC10
1 KSANC Key system additional number change
2 KSANE Key system additional number end
3 KSANI Key system additional number initiate
4 KSCAC Key system category change
5 KSCAP Key system category print
6 KSCHC Key system character data change
7 KSCHP Key system character data print
8 KSCUC Key system extension customer number change
9 KSDDP Key system directory data print
10 KSDNC Key system directory number change
11 KSEXC Key system extension equipment change
12 KSEXE Key system extension end
13 KSEXI Key system extension initiate
14 KSFKC Key system function key change
15 KSFKP Key system function key print
16 KSMDE Key system multiple directory number end
17 KSMDI Key system multiple directory number initiate
18 KSMDP Key system multiple directory number print
19 KSTSC Key system text string change
20 KSTSP Key system text string print

 

[whosrdaddy]

Devplan :
reply with the printout from this command:
CNPIP:UNIT=KHH;

http://www.damovo.com

 

[rorni]

Hello,

In some releases, some commands may have been removed by local distributors because they are known to give a lot of troubles. This is the case for command KSDNC and KSEXC which may cause data corruptions.

I strongly advise You to change equ or number of a dts using command KSEXE and µKSEXI (despite the fact it give you extra work with MNS and keys)

Regards
rorni

 

[spamfree]

KSDNC can be very troublesome in multi-LIM systems, causing corruption. Command uses pointers to change extensions. Better to end both extensions and then swap them. Sometimes when a LIM is being removed the system still thinks certain extensions still reside in the LIM eventhough it's been removed.

 

[mdfan]

These runs fine in BC11 ...

 

[safron]

KSEXC...IS A NO NO!! , BUT KSDNC SHOULD BE NO PROBS.

 

[mdfan]

The most elegant way to perform a KSEXC is to use the 'exchange' feature of Extension Manager of DNA.
Otherwise one has to undefine everything manually and redefine it . Basically this is what EMG does so nicely for us.

 

[FICRI]

If you have access to the PC-Regen program you can use that program to retreive exchange data and regenerate it to the same BC release (source and target system will be the same).

This way you will get an exchange data backup in the form of command files in your PC. There will be files for KS which can be used to reinitiate a DTS to a different EQU if needed.
Not so elegant as in EMG but usable.

//FICRI

 

[Kronehead]

I have DNA & the exchange command is fine for analogue but if you are doing a few digi swaps with MNS keys, ADINI etc then you'd better have a nice snooze while you wait for the changes to execute, oh yes & hope that the MDN isn't on the phone or you'll be rolling back and waiting even longer! I have always done my digi swaps with KSEXC then synchronised the DNA & never had any problems. Then again maybe my service provider will tell you different when I log a call for corrupted hunt groups etc. Always wondered why that happened ;-))