Built-in Function Run-Time Error Messages

Execution of a PSL script can cause various run-time error messages from the built-in variables. These messages indicate serious PSL script problems that cannot be suppressed. This section lists the error messages and explains the most likely cause for each error.

The first word in the error message indicates the built-in function that generated the message.

BMCcat: filename -- error_message

Explanation: The cat() function had problems opening the file, for example file not found or permission denied. The system error message is reported using the PSL errno variable.

BMCcat: filename -- read error after number bytes

Explanation: The cat() function read operation failed after number bytes were read.

BMCcreate: unknown application application

Explanation: The create() function could not locate application in the computer symbol table.

BMCcreate: _type_ missing in object object

Explanation: The create() function could not find the special built-in variable _type_ in the symbol table.

BMCcreate: object object is not an application

Explanation: The create() function determined that the object being created is not an application. The create() function cannot create computer instances.

BMCcreate: _self_ missing in object object

Explanation: The create() function could not find the special built-in variable _self_ in the symbol table.

BMCcreate: cannot create instance instance of application application

Explanation: The create() function discovered that either the name application is bad or that too many instances are already registered for application.

BMCcreate: invalid initial state state for instance instance of application application

Explanation: The create() function discovered that the state passed to it is not one of the valid states (ALARM, OK, WARN, or OFFLINE).

BMCcreate: empty symbol table in object object

Explanation: The create() function discovered that the symbol table for object is empty, as would be the case if object were the parent of a computer instance. The create() function cannot create computer instances.

BMCchange_state: unknown object object

Explanation: The change_state() function could not find object where the state was to change.

BMCchange_state: _type_ missing in object object

Explanation: The change_state() function could not find the special built-in variable _type_ in the symbol table.

BMCchange_state: object object is not an application instance

Explanation: The change_state() function attempted to change the state of a computer instance or other non-application instance object.

BMCchange_state: _self_ missing in object object

Explanation: The change_state() function could not find the special built-in variable _self_ in the symbol table.

BMCchange_state: empty symbol table in object object

Explanation: The change_state() function discovered that the symbol table for object is empty, as would be the case if object were the parent of a computer instance.

BMCdestroy: unknown object object

Explanation: The destroy() function could not find object that it was to destroy.

BMCdestroy: _type_ missing in object object

Explanation: The destroy() function could not find the special built-in variable _type_ in the symbol table.

BMCdestroy: object object is not an application instance

Explanation: The destroy() function attempted to destroy a computer instance or other non-instance object. The name object must be an application name.

BMCdestroy: _self_ missing in object object

Explanation: The destroy() function could not find the special built-in variable _self_ in the symbol table.

BMCdestroy: empty symbol table in object object

Explanation: The destroy() function discovered that the symbol table for object is empty, as would be the case if object were the parent of a computer instance.

BMCexecute: cannot find instance instance

Explanation: The execute() command failed to find instance in the symbol table and so could not execute a command against it.

BMCexecute: cannot get type of object object

Explanation: The execute() command could not find the special built-in variable _type_ in the symbol table.

BMCexecute: object object is not an application instance or computer

Explanation: The execute() command discovered that object is neither an application nor a computer instance and could not execute a command against it.

BMCexecute: cannot get instance ptr of object object

Explanation: The execute() command could not find the special built-in variable _self_ in the symbol table.

BMCexecute: couldn't execute command_type command

Explanation: The execute() command was unable to create either the internal run-time cell or the operating system process to execute the command. Possible causes include the following:

• invalid user ID
• bad application instance
• PSL program did not compile
• PSL process creation failed

BMCexecute: couldn't create channel

Explanation: The execute() function encountered an internal PSL problem. Contact your BMC Software Product Support representative for assistance.

BMCgrep: bad regular expression -- regular_expression

Explanation: The grep() function discovered that the regular expression argument passed to it is either not valid or too long.

BMCget_vars: unknown object object

Explanation: The get_vars() function either:

• could not find object ; or
• discovered that object does not have variables (simple variables do not have variables)

BMCin_transition: unknown object object

Explanation: The in_transition() function could not find object on which it was to act.

BMCin_transition: _type_ missing in object object

Explanation: The in_transition() function could not find the special built-in variable _type_ in the symbol table.

BMCin_transition: object object is not an application instance

Explanation: The in_transition() function attempted to apply its timer to a computer instance or other nonapplication instance object.

BMCin_transition: _self_ missing in object object

Explanation: The in_transition() function could not find the special built-in variable _self_ in the symbol table.

BMCin_transition: empty symbol table in object object

Explanation: The in_transition() function discovered that the symbol table for object is empty as would be the case if it were the parent of a computer instance.

BMCread: bad channel# channel_number

Explanation: The read() function has discovered that channel_number is no longer valid for the PSL process. Possible causes include

• a bad channel number (for example, a negative number)
• a channel already closed using the close function

BMCreadln: bad channel# channel_number

Explanation: The readln() function has discovered that channel_number is no longer valid for the PSL process. Possible causes include:

• a bad channel number (for example, a negative number)
• a channel already closed using the close function

BMCwrite: bad channel# channel_number

Explanation: The write() function has discovered that channel_number is no longer valid for the PSL process. Possible causes include:

• bad channel number (for example, a negative number)
• channel already closed using the close function

BMCvariable : non-modifiable data type

Explanation: The set() function attempted to set variable in the PATROL hierarchy that has write permission but is not of a type that the set() function is allowed to modify. For example, this error occurs if variable is another subobject such as an application or instance.

BMCvariable : write permission denied

Explanation: The set() function attempted to set a read-only built-in variable in the PATROL hierarchy.

Where to go from here

Diagnosing PSL Program Errors