Errors

Error 114: "%s"(%d): Bad tracesize %s (range %d..%d). (Severity 2)

Explanation

The specified value of TRACESIZE is invalid. The value range of values is 0...16777216 (16M).

Action:

Change to an appropriate value.

Error 115: "%s"(%d): Bad traceopt %s (range %d..%d). (Severity 2)

Explanation

The specified value of TRACEOPT is invalid. The value range of values is 0...FFFFFFFEh (or -2147483648...2147483647, except -1). Note that FFFFFFFFh (or -1) is not allowed.

Action:

Change to an appropriate value.

Error 116: "%s"(%d): traceopt "%s" OR'ed will give 0xFFFFFFFF. (Severity 2)

Explanation

The combined value of all TRACEOPT values hit the special reserved value of 0xFFFFFFFFh (or -1). This value is not allowed.

Action:

Check each TRACEOPT value and make sure the values are correctly specified.

Error 117: "%s"(%d): String data cannot exceed %d characters (Severity 2)

Explanation

The "STRING" data used in "LDATA" statement is too long, and exceeds the size specified in "LOGICAL-SIZE" of "CONFIGURATION" section.

Action:

Reduce the length of the data, or increase the "LOGICAL-SIZE" to fit more data in the Logical Terminal Table extension.

Error 118: "%s"(%d): String data missing (Severity 2)

Explanation

No data specified after the "STRING" keyword (of LDATA statement).

Action:

Insert the missing data or remove the unnecessary "LDATA" line.

Error 119: "%s"(%d): Bad data value "%s" (range %d..%d) (Severity 2)

Explanation

The numeric value specified after the "BYTES" or "INT16" keyword (of LDATA statement) is invalid. Value should be in the specified range.

Action:

Use an appropriate value.

Error 120: "%s"(%d): Unexpected word "%s", line skipped (Severity 2)

Explanation

An specified word is found in the configuration file and is unknown to TTGEN.

Action:

Check for misspelling. Correct spelling or remove the word.

Error 121: "%s"(%d): System name missing (Severity 2)

Explanation

Need to specify System-Name "<name>" in Configuration section. No system name specified after the "SYSTEM-NAME" keyword (of the "CONFIGURATION" section).

Action:

Insert an appropriate system name.

Error 122: "%s"(%d): Bad Terminal-ZLU "%s" (range %d..%d) (Severity 2)

Explanation

Bad Terminal-ZLU specified. The valid range of values is 1...60000 (ZCOM_MAXTZLU in /opt/acc/include/zcom/zcomsys.h). Specified value for TERMINAL-ZLU is out of range.

Action:

Change to an appropriate value.

Error 123: "%s"(%d): Bad Program-ZLU "%s" (range %d..%d) (Severity 2)

Explanation

Bad Program-ZLU specified. The valid range of values is 1...10000 (ZCOM_MAXPZLU in /opt/acc/include/zcom/zcomsys.h). Specified value for PROGRAM-ZLU is out of range.

Action:

Change to an appropriate value.

Error 124: "%s"(%d): Total number of ZLUs > %d (Severity 2)

Explanation

Total number of ZLUs (i.e., TERMINAL-ZLU and PROGRAM-ZLU) exceeded the allowable limit.

Action:

Reduce number of TERMINAL-ZLU or PROGRAM-ZLU to an appropriate value.

Error 125: "%s"(%d): Bad Logical-Term "%s" (range %d..%d) (Severity 2)

Explanation

Bad Logical-Term specified. The valid range of values is 1...65535 (ZCOM_MAXLTERM in /opt/acc/include/zcom/zcomsys.h). Specified value for Logical-Term is out of range.

Action:

Change to an appropriate value.

Error 126: "%s"(%d): Bad Physical-Term "%s" (range %d..%d) (Severity 2)

Explanation

Bad Physical-Term specified. The valid range of values is 1...65535 (ZCOM_MAXPTERM in /opt/acc/include/zcom/zcomsys.h). Specified value for Physical-Term is out of range.

Action:

Change to an appropriate value.

Error 127: "%s"(%d): Bad Port-Limit "%s" (range %d..%d). (Severity 2)

Explanation

Bad Port-Limit specified. The specified value is either invalid or out of range. The valid range of values is 1...25,000.

Action:

Change to an appropriate value.

Error 128: "%s"(%d): Bad Queue-Limit "%s" (range %u..%u) (Severity 2)

Explanation

Specified value for Queue-Limit is out of range.

Action:

Change to an appropriate value.

Error 129: "%s"(%d): Bad Transmit-Limit "%s" (range %u..%u) (Severity 2)

Explanation

Specified value for Transmit-Limit is out of range.

Action:

Change to an appropriate value.

Error 130:"%s"(%d): Bad Unack-Limit "%s" (range %u..%u) (Severity 2)

Explanation

Specified value for Unack-Limit is out of range.

Action:

Change to an appropriate value.

Error 131: "%s"(%d): Bad Logical-Size "%s" (range %d..%d) (Severity 2)

Explanation

Specified value for Logical-Size is out of range.

Action:

Change to an appropriate value.

Error 132: "%s"(%d): Size must be a multiple of %d (Severity 2)

Explanation

Size must be a multiple of 8 bytes. In the HP-UX 11.0 64-bit environment, data alignment to a 8-byte boundary is necessary for data structures with "long" or "pointer" types. To be consistent in both 32/64-bit environments, TTGEN requires the LOGICAL-SIZE to be a multiple of 8 bytes.

Action:

Increase size to multiple of 8 bytes.

Error 133: "%s"(%d): No Logical-Size defined (Severity 2)

Explanation

Need to specify Logical-Size <size> in the Configuration section. The associated definition requires non-zero Logical Terminal Table extension, but there is no extension defined (i.e., no LOGICAL-SIZE).

Action:

Add a LOGICAL-SIZE definition (in CONFIGURATION section), or remove the definition.

Error 134: "%s"(%d): Bad application number "%s" (range %d..%d) (Severity 2)

Explanation

Bad Logical Data application number. The specified "Application Number" field is out of range.

Action:

Change to an appropriate value.

Error 135: "%s"(%d): Label name missing (Severity 2)

Explanation

Logical-Data label name missing. Each LOGICAL-DATA statement must have a unique label name specified.

Action:

Insert label name.

Error 136: "%s"(%d): Bad data offset "%s" (range %d..%d) (Severity 2)

Explanation

Bad Logical-Data offset specified. The specified byte offset for LOGICAL-DATA statement is out of range.

Action:

Use an appropriate value, or adjust the LOGICAL-SIZE statement to accommodate the required region.

Error 137: "%s"(%d): Offset must be a multiple of %d (Severity 2)

Explanation

Logical-Data offset must be a multiple of 8 bytes. In the HP-UX 11.0 64-bit environment, data alignment to a 8-byte boundary is necessary for data structures with "long" or "pointer" types. To be consistent in both 32/64-bit environments, TTGEN requires LOGICAL-DATA to have an offset of multiple of 8 bytes.

Action:

Align the byte offset to multiple of 8 bytes.

Error 138: "%s"(%d): Bad data size "%s" (range %d..%d) (Severity 2)

Explanation

The specified byte size for the LOGICAL-DATA statement is out of range.

Action:

Use an appropriate value, or adjust the LOGICAL-SIZE statement to accommodate the required region.

Error 139: "%s"(%d): Size must be a multiple of %d (Severity 2)

Explanation

Logical-Data size must be a multiple of 8 bytes. In HP-UX 11.0 64-bit environment, data alignment to a 8-byte boundary is necessary for data structures with "long" or "pointer" types. To be consistent in both 32/64-bit environments, TTGEN requires the LOGICAL-DATA to have a size which is a multiple of 8 bytes.

Action:

Increase the byte size to multiples of 4 bytes.

Error 140: "%s"(%d): Storage overflow (data area = %d bytes (Severity 2)

Explanation

Logical-Data storage overflow. The specified region overflows the defined size in "LOGICAL-SIZE".

Action:

Use an appropriate value, or adjust the LOGICAL-SIZE statement to accommodate the required region.

Error 141: "%s"(%d): Storage label "%s" already defined (Severity 2)

Explanation

The label for the storage region is not unique. Logical-Data storage label already defined.

Action:

Use a different label name.

Error 142: "%s"(%d): Storage allocation conflict (Severity 2)

Explanation

Logical-Data storage allocation conflict. The specified region overlaps with some other previously defined regions.

Action:

Check previously defined regions and avoid using used area.

Error 143: "%s"(%d): Bad Buffer-Pool "%s" (range %u..%u) (Severity 2)

Explanation

Bad Buffer-Pool size specified. The BUFFER-POOL size is out of range.

Action:

Use an appropriate value. The valid range of values is 1024...2147483645 (0x7FFFFFF, ZCOM_MAXBPOOL in /opt/acc/include/zcom/zcomsys.h).

Error 144: "%s"(%d): Size must be a multiple of %d (Severity 2)

Explanation

Buffer-Pool size must be a multiple of 8 bytes. In the HP-UX 11.0 64-bit environment, data alignment to a 8-byte boundary is necessary for data structures with "long" or "pointer" types. To be consistent in both 32/64-bit environments, TTGEN requires BUFFER-POOL to have a size which is a multiple of 8 bytes.

Action:

Increase the byte size to a multiple of 8 bytes.

Error 145: "%s"(%d): Bad Interface-Table "%s" (range %d..%d), ignored (Severity 2)

Explanation

Bad Interface-Table value specified. The specified value is either invalid or out of range. The valid range of values is 1...256 (ZCOM_MAXIFT in /opt/acc/include/zcom/zcomsys.h).

Action:

Change to an appropriate value.

Error 146: "%s"(%d): Same hardware address as interface %d (Severity 2)

Explanation

Duplicate ACC interface hardware address specified. The specified BUS and SLOT numbers have already been assigned to a previously defined ACC card.

Action:

Make sure the correct hardware address is used.

Error 147: "%s"(%d): Bad Mux interface number "%s" (range %d..%d) (Severity 2)

Explanation

The specified ACC card number is out of range.

Action:

Use an appropriate value.

Error 148: "%s"(%d): Bad bus number "%s" (range %d..%d) (Severity 2)

Explanation

Bad ACC interface bus number specified. The specified bus number is out of range.

Action:

Use an appropriate value.

Error 149: "%s"(%d): Bad slot number "%s" (range %d..%d) (Severity 2)

Explanation

Bad ACC interface slot number specified. The specified slot number is out of range.

Action:

Use an appropriate value.

Error 150: "%s"(%d): File name missing (Severity 2)

Explanation

ACC interface protocol file name missing. The Interface-Definition statement must have a firmware download file specified.

Action:

Add appropriate firmware download file name (must use full path name).

Error 151: "%s"(%d): Bad port number "%s" (range %d..%d) (Severity 2)

Explanation

Bad Port number specified. The specified field in PORT statement has an unexpected value. The line is ignored in order to continue compilation.

Action:

Check for misspelling or syntax problem. Use an appropriate values.

Error 152: "%s"(%d): Bad baud rate "%s", line ignored (Severity 2)

Explanation

Bad Port baud rate specified. The specified field in PORT statement has an unexpected value. The line is ignored in order to continue compilation.

Action:

Check for misspelling or syntax problem. Use an appropriate value.

Error 153: "%s"(%d): Bad clock source "%s", line ignored (Severity 2)

Explanation

Bad Port clock source specified. The specified field in PORT statement has an unexpected value. The line is ignored in order to continue compilation.

Action:

Check for misspelling or syntax problem. Use an appropriate value.

Error 154: "%s"(%d): Bad port mode "%s", line ignored (Severity 2)

Explanation

Bad Port mode specified. The specified field in PORT statement has an unexpected value. The line is ignored in order to continue compilation.

Action:

Check for misspelling or syntax problem. Use an appropriate value.

Error 155: "%s"(%d): Bad operating mode "%s", line ignored (Severity 2)

Explanation

Bad Port operating mode specified. The specified field in PORT statement has an unexpected value. The line is ignored in order to continue compilation.

Action:

Check for misspelling or syntax problem. Use an appropriate value.

Error 156: "%s"(%d): Bad clock multiplier "%s", line ignored (Severity 2)

Explanation

Bad Port clock multiplier specified. The specified field in PORT statement has an unexpected value. The line is ignored in order to continue compilation.

Action:

Check for misspelling or syntax problem. Use an appropriate value.

Error 157: "%s"(%d): Bad encoding mode "%s", line ignored (Severity 2)

Explanation

Bad Port encoding mode specified. The specified field in PORT statement has an unexpected value. The line is ignored in order to continue compilation.

Action:

Check for misspelling or syntax problem. Use an appropriate value.

Error 158: "%s"(%d): Bad parity "%s", line ignored (Severity 2)

Explanation

Bad Port parity specified. The specified field in PORT statement has an unexpected value. The line is ignored in order to continue compilation.

Action:

Check for misspelling or syntax problem. Use an appropriate value.

Error 159: "%s"(%d): Bad stop bits "%s", line ignored (Severity 2)

Explanation

Bad Port stop bits specified. The specified field in PORT statement has an unexpected value. The line is ignored in order to continue compilation.

Action:

Check for misspelling or syntax problem. Use an appropriate value.

Error 160: "%s"(%d): ASYNC mode must use internal clock (Severity 2)

Explanation

Port ASYNC mode must use internal clock. The specified port configuration combination is invalid.

Action:

Use an appropriate configuration.

Error 161: "%s"(%d): ASYNC mode must not use x1 clock (Severity 2)

Explanation

Port ASYNC mode must not use x1 clock. The specified port configuration combination is invalid.

Action:

Use an appropriate configuration.

Error 162: "%s"(%d): ASYNC mode must specify parity (Severity 2)

Explanation

Port ASYNC mode must specify parity. The specified port configuration combination is invalid.

Action:

Use an appropriate configuration.

Error 164: "%s"(%d): SYNC/SDLC mode must use x1 clock (Severity 2)

Explanation

Port SYNC/SDLC mode must use x1 clock. The specified port configuration combination is invalid.

Action:

Use an appropriate configuration.

Error 165: "%s"(%d): SDLC mode cannot specify parity (Severity 2)

Explanation

Port SDLC mode cannot specify parity. The specified port configuration combination is invalid.

Action:

Use an appropriate configuration.

Error 166: "%s"(%d): SYNC mode must specify parity (Severity 2)

Explanation

Port SYNC mode must specify parity. The specified port configuration combination is invalid.

Action:

Use an appropriate configuration.

Error 167: "%s"(%d): SYNC/SDLC mode have no stop bits (Severity 2)

Explanation

Port SYNC/SDLC mode must have no stop bits. The specified port configuration combination is invalid.

Action:

Use an appropriate configuration.

Error 168: "%s"(%d): Bad ZLU "%s" (range %d..%d), line ignored (Severity 2)

Explanation

The specified ZLU number is out of range. The line is ignored in order to continue compilation.

Action:

Use an appropriate value or adjust "TERMINAL-ZLU" (of CONFIGURATION section) to accommodate the required terminal ZLU.

Error 169: "%s"(%d): Re-defining ZLU %d, line ignored (Severity 2)

Explanation

The specified ZLU is already defined. The line is ignored in order to continue compilation.

Action:

Check the previously defined ZLU, and use different values.

Error 170: "%s"(%d): Bad interface number "%s" (range %d..%d) (Severity 2)

Explanation

The ACC interface card number specified is out of range.

Action:

Use an appropriate value or define that ACC card number in the Interface-Definition section.

Error 171: "%s"(%d): Bad port "%s" (range %d..%d), line ignored (Severity 2)

Explanation

The specified port number is out of range. The line is ignored in order to continue compilation.

Action:

Use an appropriate value.

Error 172: "%s"(%d): Bad device name "%s", line ignored (Severity 2)

Explanation

The specified device name is defined in the ZCOMDEVICE file used by TTGEN (i.e., /opt/acc/cfg/zcomdevice).

Action:

Check for misspelling or add an appropriate definition into the ZCOMDEVICE file (see ZDGEN program).

Error 173: "%s"(%d): Bad poll code "%s" (range %XH..%XH) (Severity 2)

Explanation

The specified value is out of range.

Action:

Use an appropriate value.

Error 174: "%s"(%d): Bad select code "%s" (range %XH..%XH) (Severity 2)

Explanation

The specified value is out of range.

Action:

Use an appropriate value.

Error 175: "%s"(%d): Bad application number "%s" (range %d..%d) (Severity 2)

Explanation

The specified value is out of range.

Action:

Use an appropriate value.

Error 176: "%s"(%d): Bad institution number "%s" (range %d..%d) (Severity 2)

Explanation

The specified value is out of range.

Action:

Use an appropriate value.

Error 177: "%s"(%d): Bad branch number "%s" (range %d..%d) (Severity 2)

Explanation

The specified value is out of range.

Action:

Use an appropriate value.

Error 178: "%s"(%d): Bad workstation number "%s" (range %d..%d) (Severity 2)

Explanation

The specified value is out of range.

Action:

Use an appropriate value.

Error 179: "%s"(%d): Bad area number "%s" (range %d..%d) (Severity 2)

Explanation

The specified value is out of range.

Action:

Use an appropriate value.

Error 180: "%s"(%d): Bad or missing call number (Severity 2)

Explanation

The optional "CALL" parameter is specified, but no call number follows it.

Action:

Insert appropriate call number, or remove unnecessary keyword "CALL".

Error 181: "%s"(%d): Bad or missing terminal address (Severity 2)

Explanation

Logical terminal address is missing in the LTERM statement.

Action:

Insert an appropriate logical terminal address.

Error 182: "%s"(%d): Terminal name missing (Severity 2)

Explanation

The terminal name field is missing.

Action:

Insert appropriate terminal name.

Error 183: "%s"(%d): Previous PTERM has no following LTERM (Severity 2)

Explanation

A PTERM statement is used but without LTERM following it. This causes the defined physical terminal to become inaccessible.

Action:

Insert missing LTERM statement, or remove this unnecessary PTERM.

Error 184: "%s"(%d): Must have a TERM or PTERM defined before (Severity 2)

Explanation

An LTERM statement is used but without a preceding PTERM or TERM. This results in an unusable LTERM because no physical terminal is linked to it.

Action:

Insert the missing PTERM or TERM statement, or remove the LTERM statement.

Error 185: "%s"(%d): Logical terminals reaches limit (%d) (Severity 2)

Explanation

The defined TERM or LTERM exceeded the allowable number of logical terminal tables.

Action:

Increase the "LOGICAL-TERM" parameter in "CONFIGURATION" section or remove the offending TERM/LTERM line.

Error 186: "%s"(%d): Physical terminals reaches limit (%d) (Severity 2)

Explanation

The defined TERM or PTERM exceeded the allowable number of physical terminal tables.

Action:

Increase the "PHYSICAL-TERM" parameter in "CONFIGURATION" section or remove the offending TERM/PTERM line.

Error 187: "%s"(%d): More than %d terminals on this interface (Severity 2)

Explanation

The number of physical terminals defined on this interface exceeds the absolute limit for this interface.

Action:

Remove the invalid terminal definition(s).

Error 188: "%s"(%d): More than %d terminals on this port (Severity 2)

Explanation

The number of physical terminals defined on this port exceeds the absolute limit for a port on this interface.

Action:

Remove the invalid terminal definition.

Error 189: "%s"(%d): Bad node number "%s" (range %d..%d) (Severity 2)

Explanation

Specified node number is out of range.

Action:

Use an appropriate value.

Error 190: "%s"(%d): Too many nodes defined (max %d) (Severity 2)

Explanation

The node definition exceeds the allowable number of definitions.

Action:

Remove the invalid entry.

Error 191: "%s"(%d): Re-defining node %d (Severity 2)

Explanation

The specified node number is previously defined.

Action:

Use different node number or remove the duplicate entry.

Error 192: "%s"(%d): Host name/IP address missing (Severity 2)

Explanation

The host name or IP address (in dot format) is missing in the Remote-Node definition.

Action:

Correct the Remote-Node entry and supply the appropriate host name or IP address.

Error 193: "%s"(%d): Node ZLU %d not defined (Severity 2)

Explanation

The specified ZLU is not defined in "TERMINAL-DEFINITION" section.

Action:

Use a defined ZLU number or define such ZLU in "TERMINAL-DEFINITION" section.

Error 194: "%s"(%d): Local node not specified (Severity 2)

Explanation

Local node number must be defined in NODE-DEFINITION section.

Action:

Insert "Local-Node" entry in "NODE-DEFINITION" section.

Error 196: "%s"(%d): Missing storage label (Severity 2)

Explanation

A storage label name is missing after the "NAME" keyword in a "LDATA" statement.

Action:

Insert the appropriate label name.

Error 197: "%s"(%d): Bad data offset "%s" (range %d..%d) (Severity 2)

Explanation

The specified byte offset is out of range.

Action:

Use an appropriate value.

Error 198: "%s"(%d): Bad repeat count "%s" (range %d..%d), ignored (Severity 2)

Explanation

Bad repeat value specified. Valid range of values is 1...255 (ZCOM_TPORT_MUX in /opt/acc/include/zcom/zcomsys.h).

Action:

Change to an appropriate value.

Error 199: "%s"(%d): Bad node timeout "%s" (range %d..%d) (Severity 2)

Explanation

The timeout value specified in the node entry is invalid. The valid range of values is 2...65535 (ZCOM_MAXNTOUT in /opt/acc/include/zcom/zcomsys.h).

Action:

Change to an appropriate value.

Error 200: "%s"(%d): Bad low-water mark "%s" (range %d..%d) (Severity 2)

Explanation

The specified flow control low-water mark is invalid. The valid range of values is 1...2147483645 (ZCOM_MAXQLIM in /opt/acc/include/zcom/zcomsys.h).

Action:

Change to an appropriate value.

Error 201: "%s"(%d): Bad high-water mark "%s" (range %d..%d) (Severity 2)

Explanation

The specified flow control high-water mark is invalid. The valid range of values is 1...2147483645 (ZCOM_MAXQLIM in /opt/acc/include/zcom/zcomsys.h).

Action:

Change to an appropriate value.

Error 202: "%s"(%d): Bad Node-Entry "%s" (range %d..%d) (Severity 2)

Explanation

Bad Node-Entry value specified. The specified value is either invalid or out of range. The valid range of values is 1...20 (ZCOM_MAXNODE in /opt/acc/include/zcom/zcomsys.h).

Action:

Change to an appropriate value.

Error 203: "%s"(%d): Bad port Tx limit parameter "%s" (range %d..%d)

Explanation

The port transmit limit is out of range.

Action:

Change to an appropriate value.

Error 204: "%s"(%d): Bad bit offset "%s" (range %d..%d)

Explanation

Action:

Change to an appropriate value.

Error 206: "%s %d": Illegal T2 timer value "%d" in Select Word

Explanation

Action:

Change to an appropriate value.

Error 207: "%s %d": Illegal L2 window size "%d" in Select Word

Explanation

Action:

Change to an appropriate value.

Error 208: "%s %d": Illegal L2 retry counter "%d" in Select Word

Explanation

Action:

Change to an appropriate value.

Error 209: "%s %d": Bad PVC Logical Channel Nbr range (0..255)

Explanation

Action:

Change to an appropriate value.

Error 210: "%s %d": Bad %s SVC Logical Channel Number range

Explanation

Action:

Change to an appropriate value.

Error 211: "%s %d": Logical Channel Numbers out of range (max%d)

Explanation

Action:

Change to an appropriate value.

Error 212: "%s %d": PVC Logical Channel Nbr (%d) too large for subscription. Legal range is (1..%d).

Explanation

Action:

Change to an appropriate value.

Error 213: "%s %d": SVC option word has neither IN nor OUT bit set

Explanation

Action:

Change to an appropriate value.

Error 214: "%s %d": No Link Term defined for this Virtual Circuit Term

Explanation

Action:

Add the link terminal definition.

Error 215: "%s %d": Virtual Circuit trm defined before Link trm %d.

Explanation

Action:

Re-order the terminal definitions.

Error 216: "%s %d": Online_fac_reg facility not supported in the %d ITU-T recommendation X.25

Explanation

Action:

Change to an appropriate value.

Error 217: "%s %d": TOA_NPI_addr facility not supported in the %d ITU-T recommendation X.25

Explanation

Action:

Change to an appropriate value.

Error 218: "%s %d": Ext_thruput_class_neg facility not supported in the %d ITU-T recommendation X.25

Explanation

Action:

Change to an appropriate value.

Error 219: "%s %d": Thruput_class_neg and ext_thruput_class_neg are mutually exclusive, only one may be enabled!

Explanation

Action:

Change to an appropriate value.

Error 220: "%s %d": Number of PVC terms do not match LCN info in Link term.

Explanation

Action:

Change to an appropriate value.

Error 221: "%s %d": Number of incoming SVC's defined is less than the LCN subscription specified in the X.25 link term entry.

Explanation

Action:

Change to an appropriate value.

Error 222: "%s %d": Number of two-way SVC's defined is less than the LCN subscription specified in the X.25 link term entry.

Explanation

Action:

Change to an appropriate value.

Error 223: "%s %d": Number of outgoing SVC's defined is less than the LCN subscription specified in the X.25 link term entry.

Explanation

Action:

Change to an appropriate value.

Error 224: "%s"(%d): X.25 keyword "%s" not allowed in non-X.25 link term entry!

Explanation

Action:

Change to an appropriate value.

Error 225: "%s"(%d): Logical data area too small for X.25 link terminal!

Explanation

Action:

Change to an appropriate value.

Error 226: "%s"(%d): Logical-data statement with label "%s" not defined for X.25 link!

Explanation

Action:

Change to an appropriate value.

Error 227: "%s"(%d): Invalid packet layer role parameter in Network_type statement. Taking default from POLL word.

Explanation

Action:

Change to an appropriate value.

Error 228: "%s"(%d): Invalid X.25 recommendation year in Network_type statement. Taking default from POLL word.

Explanation

Action:

Change to an appropriate value.

Error 229: "%s %d": Calls_in_barred and Calls_out_barred are mutually exclusive, only one may be enabled!

Explanation

Action:

Change to an appropriate value.

Error 230: "%s %d": Timer T1 must be greater than Timer T2!

Explanation

Action:

Change to an appropriate value.

Error 231: "%s %d": Timer T3/T4 must be greater than Timer T1!

Explanation

Action:

Change to an appropriate value.

Error 232: "%s"(%d): Invalid X.25 timer resolution value!

Explanation

Action:

Change to an appropriate value.

Error 233: "%s %d": An X.25 link terminal has already been defined on this Mux and Port.

Explanation

Action:

Change to an appropriate value.

Error 234: "%s %d": LCN %d has already been assigned to another PVC.

Explanation

Action:

Change to an appropriate value.

Error 249: "%s"(%d): Obsolete keyword "mux". Use the specific card product number (e.g. Z7200A)

Explanation

Action:

Change to an appropriate value.

Error 250: "%s"(%d): Illegal keyword %s for interface card %d. (Severity 2)

Explanation

See the section "Optional E1/T1 and Z7340A Tunable Parameters" in chapter 2 of the ACC Utilities Reference Guide for legal keywords.

Action:

Correct to an appropriate keyword.

Error 251: "%s"(%d): Bad zbufsize %d (must be multiple of 16) (Severity 2)

Explanation

Zbufsize value must be a multiple of 16.

Action:

Change to an appropriate value.

Error 252: "%s"(%d): Bad ttablenbr %s (range %d..%d) (Severity 2)

Explanation

Valid ttablenbr range is 1-32k.

Action:

Change to an appropriate value.

Error 253: "%s"(%d): Bad zbufsize %s (range %d..%d) (Severity 2)

Explanation

Valid zbufsize range is 32-8k and should be in multiples of 16.

Action:

Change to an appropriate value.

Error 254: "%s"(%d): Bad zbufnbr %s (range %d..%d) (Severity 2)

Explanation

Valid zbufnbr range is 1-1M.

Action:

Change to an appropriate value.

Error 255: "%s"(%d): Bad mheadnbr %s (range %d..%d) (Severity 2)

Explanation

Valid mheadnbr range is 1-1M.

Action:

Change to an appropriate value.

Error 256: "%s"(%d): Bad mquota %s (range %d..%d) (Severity 2)

Explanation

Valid mquota range is 1-1M.

Action:

Change to an appropriate value.

Error 257: "%s"(%d): Bad bquota %s (range %d..%d) (Severity 2)

Explanation

Valid bquota range is 1-1M.

Action:

Change to an appropriate value.

Error 258: "%s"(%d): Bad tsize %s (range %d..%d) (Severity 2)

Explanation

Valid tsize range is 1-32k.

Action:

Change to an appropriate value.

Error 259: "%s"(%d): Bad frame mode "%s", line ignored (Severity 2)

Explanation

Valid frame modes are F4, F12, D3/4, ESF and F72.

Action:

Change to an appropriate value.

Error 260: "%s"(%d): Bad link code "%s", line ignored) (Severity 2)

Explanation

Valid link codes are HDB3, B8ZS and AMI.

Action:

Change to an appropriate value.

Error 261: "%s"(%d): Bad subchannel "%s" (range %d..%d) (Severity 2)

Explanation

Valid subchannel numbers are 0-31.

Action:

Change to an appropriate value.

Error 262: "%s"(%d): Card %d should not have subchannel definition (Severity 2)

Explanation

Subchannel definition is legal for E1/T1 interface card only.

Action:

Delete illegal subchannel definition

Error 263: "%s"(%d): Invalid subchannel transmission mode: %s (Severity 2)

Explanation

Valid subchannel transmission modes are TRANSA, TRANSB, V.110 and HDLC.

Action:

Change to an appropriate value.

Error 264: "%s"(%d): Bad Subchannel ITBS %s (range %d..%d) (Severity 2)

Explanation

Valid subchannel ITBS values are 0-63.

Action:

Change to an appropriate value.

Error 265: "%s"(%d): Bad Subchannel timeslot number %s (range %d..%d) (Severity 2)

Explanation

Valid timeslot numbers are 0-31.

Action:

Change to an appropriate value.

Error 266: "%s"(%d): Bad Subchannel timeslot fill mask %s (range %d..%d) (Severity 2)

Explanation

Valid timeslot fill mask values are (00-FF)hex.

Action:

Change to an appropriate value.

Error 267: "%s"(%d): Port %d: duplicate instance %d of timeslots assignment (Severity 2)

Explanation

Multiple timeslot assignments have been defined for a given instance within a port.

Action:

Delete duplicate timeslot assignment.

Error 268: "%s"(%d): Unexpected subchannel number %s for ZLU %d (Severity 2)

Explanation

Action:

Delete subchannel number for non-E1/T1 interface.

Error 269: "%s"(%d): Bad ttablesize %s (range %d..%d) (Severity 2)

Explanation

Valid ttablesize range is 160-1k, and should be in multiples of 16.

Action:

Change to an appropriate value.

Error 270: "%s"(%d): Invalid subchannel specification INV: %s

Explanation

Only "INV=ON" or "INV=OFF" is permitted.

Action:

Change to an appropriate value.

Error 271: "%s"(%d): Bad E1/T1 Port-Limit "%s" (range %u..%u)

Explanation

The E1T1-Port-Limit parameter is out of range.

Action:

Change to an appropriate value.

Error 272: "%s"(%d): No E1/T1 cards defined, so Port-Limit (%u) must remain within the range %u..%u

Explanation

The Port-Limit parameter may exceed it's normal limit only if E1/T1 cards are defined.

Action:

Change to an appropriate value.

Error 273: "%s"(%d): Port-Limit (%u) must remain within %u..%u if E1T1-Port-Limit is used in this file

Explanation

The Port-Limit parameter must remain within normal limits if the E1T1-Port-Limit parameter is specified.

Action:

Change to an appropriate value.

Error 274: "%s"(%d): Port %d is not well-defined

Explanation

Cannot proceed with subchannel definition if port definition has errors.

Action:

Correct the port definition.

Error 275: "%s"(%d): Undefined or not well-defined subchannel %d

Explanation

The subchannel specified for the terminal, was not properly defined.

Action:

Correct the subchannel definition.

Error 276: "%s"(%d): '%s' Logical-data definition required

Explanation

The "X25UDT" area must be defined before the UDATA keyword can be used.

Action:

Add the "X25UDT" Logical-Data definition to the Configuration section.

Error 277: "%s"(%d): Minimum '%s' Logical-data size required: %d.

Explanation

The "X25UDT" area has been defined too small.

Action:

Increase the size of the "X25UDT" area in the Configuration section.

Error 278: "%s"(%d): Too many digits, %d, in non-ASCII octal value in Udata string: %s. Only %d max allowed. Last digit at char position %d in string (starting from 0)

Explanation

Action:

Correct the Udata parameter.

Error 279: "%s"(%d): Non-ASCII octal digits were expected at char position %d (starting from 0) in Udata string: %s

Explanation

Octal data was expected.

Action:

Correct the Udata parameter.

Error 280: "%s"(%d): sscanf() failed to convert octal digits, %s, in Udata into a byte value. Errno: %d. Resulting byte value (in octal) so far: %o.

Explanation

Octal data was expected.

Action:

Correct the Udata parameter.

Error 281: "%s"(%d): Octal value in Udata, %o, exceeds the max octal value allowed for a byte, %o. Udata string: %s. Last digit character position %d (starting from 0)

Explanation

Action:

Correct the Udata parameter.

Error 282: "%s"(%d): Too many ASCII characters and/or octal bytes specified in the Udata string for the Udata buffer to hold. Only a max of %d bytes allowed. Last character from Udata string successfully processed: %c

Explanation

Action:

Correct the Udata parameters.

Error 283: "%s"(%d): Two Udata statements were detected for Term entry %d. Only one Udata is allowed per Term entry

Explanation

Action:

Remove one of the Udata statements.

Error 284: "%s"(%d): An Ldata statement can only be used after a Term or Lterm entry, or after an Ldata statement following a Term or Lterm entry.

Explanation

Action:

Move the Ldata statement to the correct place in the configuration file.

Error 285: "%s"(%d): A Udata statement can only be used after a Term or Lterm entry

Explanation

Action:

Move the Udata statement to the correct place in the configuration file.

Error 286: "%s"(%d): The application number, %d, for the Logical-Data area, %s, for an Ldata/Udata entry does not match the application number, %d, for the Term/Lterm entry associated with the Ldata/Udata entry

Explanation

Action:

Correct the application number in the Term/Lterm definition or in the Logical-Data definition.

Error 288: "%s"(%d): Bad datadelay %s (range %d . .%d)

Explanation

Action:

Choose a valid value for datadelay in the range 0 to 100. The default value of 5 milliseconds has been chosen after careful performance measurements by Hewlett-Packard. The default value is strongly recommended.

Error 289: "%s"(%d): Unrecognized subchannel keyword id: %d (Severity 2)

Explanation

The Subchannel definition has an unrecognized keyword. The keyword id number displayed is an internally used value.

Action:

Check for misspelling. Correct the spelling or remove the unsupported word. If the problem persists, this may indicate an internal software problem, please inform HP support center.

Error 290: "%s"(%d): F4/SF/ESF/F72 frame modes for T1 only (Severity 2)

Explanation

The Frame Mode specified is only allowed for a T1 link.

Action:

Either change to use compatible frame modes (e.g., for E1 link, use DF, CRCMF, etc), or change the port mode to be a T1 link (e.g., T1RJ45, T1DB9, etc).

Error 291: "%s"(%d): DF/CRCMF frame modes for E1 only (Severity 2)

Explanation

The Frame Mode specified is only allowed for E1 link.

Action:

Either change to use compatible frame modes (e.g., for T1 link, use F4, SF, ESF, F72, etc), or change the port mode to be a E1 link (e.g., E1RJ45, E1DB9, etc).

Error 292: "%s"(%d): HDB3 encoding can only be used in E1 mode (Severity 2)

Explanation

The Frame Mode specified is only allowed for E1 link.

Action:

Use B8ZS for non-E1 link.

Error 293: "%s"(%d): B8ZS encoding can only be used in T1 mode (Severity 2)

Explanation

This encoding mode is only allowed for T1 link.

Action:

Use HDB3 for non-T1 link.

Error 294: "%s"(%d): Port clock-source must be another port (Severity 2)

Explanation

The clock source CLKPTx specified must be of a port other than the port currently being defined in this definition. (e.g., Port 0 cannot be specified to use CLKPT0).

Action:

Change the clock source CLKPTx to a port other than the current port being defined.

Error 295: "%s"(%d): Port mode "%s" invalid for this card type (Severity 2)

Explanation

The port of this type of ACC card does not support the port mode specified.

Action:

Check for consistence of Interface/Port definition. Use a correct port mode, or make sure the port being defined is referring to the desired interface card.