The following messages are information level 2 messages. These messages appear only when the information display level is 2 (option -i).

I2001: Input file(s):input-file ...	

The list of input files containing BADB commands, as specified on the BADB call line.

I2002: Create case sensitive database (-s option).

Confirmation message indicating that the option to create a case sensitive database was specified. BADB does not automatically make delimiters and token text uppercase when the option -s is specified as part of the creation option (-c).

I2003: Create case insensitive database (-i option).

Confirmation message indicating that the option to create a case insensitive database was specified. BADB automatically makes delimiters and token text uppercase when the option -i is specified as part of the creation option (-c). Case insensitivity is assumed if neither the -i nor the -s option is specified as part of the file creation option.

I2004: Maximum memory size set to xxxK bytes (m option).

Confirmation message indicating the maximum memory size was set by the -m option. xxx indicates maximum in thousands (1024) of bytes (10 ≤ xxx ≤ 512).

I2006: Warning level set to x (w option).

Confirmation message indicating that the warning level was set by the option -w. x is the warning level setting (0 ≤ x ≤ 2).

I2007: Information level set to x (i option).

Confirmation indicating that the information level was set by the option -i. x is the information level setting (0 ≤ x ≤ 2).

I2008: Leading and/or trailing spaces removed 
around string "string".

A string (either text, group name, or token text in a standard pattern definition) contained leading spaces, trailing spaces or both. BADB considers these spaces to be insignificant and automatically removes them.

I2009: Default message type 'OTHER' assumed.

A message type was not specified for the defined message. The default message type OTHER was assumed.

I2010: Default sender type 'type' assumed.

A sender type was not specified for the defined message. For an SP-AMS database, the default ANY-SENDER was assumed. For a SMART AMS database, the default ANY-SENDER was assumed for an SCF message type; PRIVILEGED-EXEC was assumed for all other message types. For a CP-AMS database, PRIVILEGED-EXEC was assumed.

I2011: Default priority '128' assumed.

No priority specified for the defined message. The default priority 128 was assumed.

I2012: Token type 'type' assumed.

A token type was not specified in a TOKEN command. The token type type (either FIXED or MASKED) was determined by examining the token text.

I2013: Message token text "text" assumed.

Token text was not specified in a TOKEN command. The token text was determined by examining the token at the corresponding position in the pattern's MESSAGE command.

I2014: Estimated number of patterns set to n (s option).

Confirmation message indicating that the estimated number of standard patterns was set by the option -s. n is the estimated number of patterns (0 ≤ n). Note that n can be less than the actual -s option specification if the estimated number of patterns is greater than the maximum allowable number of patterns.

I2015: Default instance type 'PRIMARY' assumed.

An instance type was not specified for the pattern. The default instance type PRIMARY was assumed.

I2016: Create type database (option option).

Confirmation message indicating the type of database that BADB is creating, where type is either SMART AMS or CP-AMS. There are two types of OS 2200 databases: SMART AMS used with the no longer supported Unisys SMART product (.ams extension) and CP-AMS used by ClearPath Enterprise Systems OS 2200 consoles (.acp extension). SMART AMS databases can also be used by ClearPath Enterprise Systems OS 2200 consoles. BADB creates a SMART AMS database when the u option or c option is not specified as part of the creation option (-c).

I2017: Create Single Point AMS database (option option).

Confirmation message indicating that BADB is creating an SP-AMS database, with extension .asp.

BADB creates an SP-AMS database when the option u is specified as part of the creation option (-cu).

I2018: Default definition type 'PATTERN' assumed.

A definition type was not specified for a DEFINE command. The default definition type PATTERN was assumed.

I2019: Default variable type 'STRING' assumed.

A variable type was not specified for a variable definition. The default variable type STRING was assumed.

I2020: Default value default-value assumed.

A default value was not specified for a variable definition. The default value of the null string (“”) was assumed for a STRING variable and zero (0) was assumed for an INTEGER variable.

I2021: Default time type 'SECONDS' assumed.

A time unit was not specified for a variable TIMEOUT or action WAIT clause definition. The default time unit of SECONDS was assumed.

I2022: Variable "variable-name" created.

A new variable identified by variable-name was successfully added to the database.

I2023: No 'KEYWORD' token specified for standard pattern.

Although not required, using a keyword token makes a standard pattern more efficient at run time.

I2025: locale ’locale’ (LANG=locale)
in use - maximum character byte length x.
				

BADB is using locale locale, where x is the maximum number of bytes that can make up a character.

I2101: This pattern match does not have any actions.

In VADB, the input message matched a pattern in the specified database, but that pattern does not have any actions associated with it for the operating mode you requested.