mountain!!

There is no specific tool which you input an NCOS and is just prints out a nice list. However, you can get the information using one of the two methods.

The first method requires you capture the scrolling data into an ASCII file (You can use PROCOMM to capture the data), then import that data in Excel to sort it by the NCOS column to give you a list. Be warned, this method lists every possible DN (even DNs which point to a trunk group). The command syntax is:

QNCOS ALL D


Output looks like this with the last column being the NCOS

9513753464 PP01 00 0 03 86 448
9513753465 PP01 00 0 03 87 448
9513753466 PP01 00 0 03 88 448
9513753467 PP01 00 0 03 89 448
9513753468 PP01 00 0 03 90 448
9513753469 PP01 00 0 03 91 448
9513753470 PP01 00 0 03 92 448
9513753471 PP01 00 0 03 93 448
9513753472 PP01 00 0 03 94 448
9513753473 PP01 00 0 03 95 448
9513753474 PP01 00 0 03 96 448
9513753475 PP01 00 0 03 97 448
9513753494 PP01 00 0 03 24 13
9513753495 PP01 00 0 03 25 13
9513753496 PP01 00 0 03 26 13

The second method is to list table IBNLINES (using the FORMAT PACK) to get and capture the data to an ASCII file, then using EXCEL to sort the data by NCOS.

rhack

Heres a simple way. Go into the tables and do wildcard searches.

FOR ANALOG LINES
This example searches for sets in NCOS 89
>table ibnlines
TABLE: IBNLINES
>format pack
<line length>: 76 columns can be output per line.
<pack mode>: Pack mode is ON.
<indent column>: Indented lines will begin in column 1.
<first column>: The first column of output is column 1.
>lis all(3 eq '* * * * * * 89 * *')
TOP
LEN DNNO RESULT
---------------
HOST 14 0 15 08 0 DT STN IBN 4275775 FUNB 0 89 704 (LNR) $
HOST 00 0 00 16 0 DT STN IBN 4271693 FUNB 0 89 704 (COD) $
BOTTOM
>

FOR DIGITAL SETS
This example searches for sets in NCOS 8
>table ksetline
TABLE: KSETLINE
>format pack
<line length>: 76 columns can be output per line.
<pack mode>: Pack mode is ON.
<indent column>: Indented lines will begin in column 1.
<first column>: The first column of output is column 1.
>lis all(3 eq '* * * * * 8 * * *')
TOP
KSETKEY FORMAT DNRESULT KSFMTID KSFMTARE
----------------------------------------
HOST 10 2 14 08 7 DN Y 4275629 FUNB 0 8 704 (3WC) (AUTODISP) $ IVD
HOST 14 2 12 12 1 DN Y 4278813 FUNB 0 8 704 (3WC) (CFX) $ IVD
BOTTOM
>

mountain!!

The problem with wild card searches is the wild cards must match the number of options assigned to the line. In your example above, all lines with two options assigned to the line will be displayed. However, lines with only one option or three options will not display. You can adjust the wild card searches for one option (using one less star) or three options (adding another star), but you never know if you are getting all the lines with the search because the number of fields in range 3 is variable based on the number of options assigned to the line. Wild card searches work well for ranges which have a fixed number of fields, but not ranges which have a variable number of fields.

rhack

Yep, you are absolutely right mountain. I'm surprised that got by me, I should have known better. I tested on NCOS's that I knew did not have alot of phones so it did not look unusual to me. I should have tested against the main NCOS's we use. Anyway, I usually dump the tables and do as you suggested with Excel or Access.

hgperez

You can also dump the tables to a SLM volume and run the sort command to build you a flat file that has the ncos's neatly arrange by numeric value.