Need DN -> TN behaviour explained

[swoofter]

Hi,

I have a DN 1766 which for some reason is redirecting to a specific TN (4 12). TN 4 12 has a 3902 DN 1767 setup on it. A DNB dump of 1767 gives:

DN 1767
TYPE SL1
TN 004 0 00 12 KEY 00 MARP DES 3902 12 AUG 2003
(3902)

DNB of 1766 gives:

DN 1766
TYPE SL1
TN 004 0 00 12 KEY 00 MARP DES 3902 12 AUG 2003
(3902)

TNB of 4 12 gives:
DES 3902
TN 004 0 00 12
TYPE 3902
CDEN 8D
CUST 0
FDN
TGAR 0
LDN NO
NCOS 6
SGRP 0
RNPG 1
SCI 0
SSU 0010
LNRS 20
XLST
SCPW
SFLT NO
CAC_MFC 0
CLS TLD FBD WTA LPR PUA MTD FNA HTD ADD HFA GRLD
MWD RMMD SMWD AAD IMD XHD IRD NID OLD VCE DRG1
POD DSX VMD CMSD SLKD CCSD SWD LNA CNDA
CFTA SFD MRD DDV CNID CDCA MSID DAPA BFED RCBD
ICDD CDMD LLCN MCTD CLBD AUTU
GPUA DPUA DNDA CFXD ARHA CLTD ASCD
CPFA CPTA ABDD CFHD FICD NAID BUZZ AGRD MOAD
UDI RCC HBTA AHD DDGA NAMA MIND PRSD NRWD NRCD NROD
DRDD EXR0
USRD ULAD RTDD RBDD RBHD PGND OCBD FLXD FTTC MCBN
CPND_LANG ENG
RCO 2
EFD 1701
HUNT
EHT 1701
LHK 0
PLEV 02
AST
IAPG 0
AACS NO
ITNA NO
DGRP
MLWU_LANG 0
DNDR 0
KEY 00 SCR 1767 0 MARP
01 RNP
02 CFW 4
03 SSU 0010
04 TRN
05
DATE 12 AUG 2003

If i OUT the relevant TN and recreate it the problem still exists and i can't OUT the TN and reuse DN 1766 elsewhere (i get SCH5525 - New TN(s) copied from a TN template with new DNs for the prime DN appearances. The new TNs are MARPs for the new prime DNs. Secondary DNs are copied without retaining MARP designations.) I can reuse 1767 elsewhere but 1766 only ever wants to redirect to whatever is setup on TN 4 12.

Can someone point me in the right direction so i can utilise DN 1766 by removing whatever is diverting it to TN 4 12?

Thanks.

 

[joelunchpail]

if you out tn 4 12 and then do a prt dnb of 1766 what do you get?
its possible the data is corrupt,
I had two tns with one dn when i removed one tn i got all kinds of errors, when i tried to remove the other it said it didnt exist, it was like both tn's were sharing the same dn info, it didnt matter which tn i removed it screwed up the other one.
if it is a similar problem try this.
Out 4 12 , do an edd ,then do a sys load,if the data is corrupt loading that dn and tn will fail and that tn will be left unused. then do an edd.(it fixed my problem)

 

[swoofter]

After i out 4 12 i get prt dnb of 1766 as below:

DN 1766
TYPE SL1
TN 004 0 00 12 KEY 00 DES NO DES NO DATE
(3902)
SCH5526

SCH5526 Warning: In printing the DN block for a DN, no MARP or more than one MARP TN was found in the database. Only one MARP should be defined for a DN. Action: Changing the database is recommended.

Does this point towards what you suggest?

If so, can you explain the process to perform an edd and a sys load and what implications there may be in performing these actions.

Thanks for your help.

 

[joelunchpail]

it isnt the same problem, but it seems to be corrupted data just the same. it is marped to a tn that is not in service somehow. seems pretty weird!!.
im assuming this is an option 11
.
Load 43 , edd writes to your floppy disk.
Then if you do a sys load by pressing the sys load button on the front of the cpu card , all call processing is stopped and all calls are dropped.while it reloads from the floppy and ram.( SO CHOOSE A TIME WHEN THE BUSINES IS CLOSED OR OUT TO LUNCH). It takes 3 or 4 minutes ( seems like twenty when you are waiting for it to come back up) .
When it does this if the data isn't correct for that tn, or dn . it won't load it , leaving that tn un used. Have a look at your dnb of that 1766, and a tnb of 4 12. they should both be unused . Then go to load 43 and do another edd , updating your floppy again.

good luck

 

[joelunchpail]

you might want to back up a second floppy the way it is now, before you start just for safety sake. it always makes the waiting during the sys load less stressful.

 

[mehnter]

swoofter,
Do you have voice mail?
Check the NIT1 setting in ld 15
OR,

From you phone near the terminal go to ld 80
trace your number calling 1766 e.g phone # 7979 customer 0
trac 0 7979 dev
dial 1766 from your phone
hit return.
This should show you where the call is routed

 

[joelunchpail]

sorry ,mental laps . dont know what i was thinking about .
no floppy on opt 11,
edd .just backs up to memory
you might want to back up to pcmcia card or laptop first but the pricess is the same
out tn. edd, sys load.1766 shouldnt marp to nonexistant tn.

 

[swoofter]

Thanks for the replies. I will do an edd, sys load etc. after W/H today. However, in reply to Mehnter the NIT1 setting is 1899 which is the meridian mail extn. and a trace of 1728 -> 1766 gives the output below:

.trac 0 1728

ACTIVE TN 006 0 00 07
ORIG 006 0 00 07 0 SCR MARP 0 1728 3904
TERM 004 0 00 12 0 SCR MARP 0 1767 3902
DIAL DN 1766
MAIN_PM ESTD
TALKSLOT ORIG 8 TERM 10
EES_DATA:
NONE
QUEU NONE
CALL ID 0 209

I am presuming it must be some form of corruption and hoping the sys load will fix it. I will let you know how I get on. Thanks again.

 

[swoofter]

All fixed now.

Followed the process as above:
Backed up to PCMCIA
OUT'ed relevant TN
edd then a sys load.

DN 1766 was then listed as unused. Must have been some form of corruption.

Thanks for all your help.

 

[joelunchpail]

thanks for the update