Cisco DNCS System Release 2.7 3.7 4.2 Design Guide
Chapter 3 M-Card-Related Diagnostic Screens
152
78-4001708-01 Rev B
Screen Fields and Values
This section describes the fields and possible values that can appear in this
diagnostic screen.
Field Names
Description
Possible Values
Loaded
The location of the
podchan.tblo file that is loaded
for the channel map
podchan.tblo file that is loaded
for the channel map
[Directory-dependent]
Example:
POD-Data/2/podchan.tblo
GDF rule action Displays the action that was
taken in reference to the
matching rule in the group
definition file
matching rule in the group
definition file
Read
Not Read
Unassigned
NA
GDF LastLoad
Time
Time
Displays the time at which the
GDF file was last read
GDF file was last read
[Date, Time]
GDF LoadErr
Indicates if any errors occurred
when the GDF was loading
when the GDF was loading
NoErr
Path Not Found
Out of Memory
ReadErr
Exceeded Max Length
File Changed
UnknownErr
SyntaxErr
Displays the number of syntax
errors present in the group
definition file
errors present in the group
definition file
[Integer > 0]
N/A
Phy. HubID
Defines the ID for the physical
hub associated with the M-
Card module
hub associated with the M-
Card module
[Hub-dependent]
N/A
Lug ID
Defines the lineup group
identifier (LUG ID) associated
with the channel map for this
M-Card module
identifier (LUG ID) associated
with the channel map for this
M-Card module
[Integer > 0]—dependent upon
group number assigned to LUG by
the system
group number assigned to LUG by
the system
N/A
Vir. HubID
Defines the ID for the virtual
hub associated with the M-
Card module
hub associated with the M-
Card module
[Integer > 0]
N/A
Bouquet ID
Defines the ID for the bouquet
associated with the LUG for
this M-Card module
associated with the LUG for
this M-Card module
[Integer > 0]
N/A
active GDF
statement
lineNum
statement
lineNum
Indicates the line number
within the GDF file at which the
GDF rule is located
within the GDF file at which the
GDF rule is located
[Integer > 0]
N/A