Tekelec EAGLE 5 - Table 2: Parse Failure Reasons

It is important to note that the “#” number prefix override is only valid for DNs, DN Blocks, and IMSIs.
The “#” symbol at the beginning of any other parameter value does not parse.
Since the number prefix and the number prefix override apply to all requests and responses that have
DNs, DN Blocks or IMSIs, it is not mentioned on each command separately.
The Number Prefix must conform to syntax rules for DN, NSDN, and DN Block values. Prefix lengths
must not exceed 10 digits.
Common Responses
The response code examples given for each message indicate those codes that are specific for that
message. Other response codes may apply, such as the more general error responses like
PDBI_NOT_CONNECTED, PDBI_NO_ACTIVE_ TXN, PDBI_NOT_FOUND, PDBI_BAD_ARGS.
These are not repeated for each message for simplicity.
No command can be issued until a connection has been established by issuing the connect request to
a PDBA. This restriction includes data provisioning commands such as ent_sub, rtrv_sub, etc., as
well as query commands such as status, dump_conn, etc.
Common Response Messages
Because the PDBI is a string-based API, all requests can return a Parse Failed response message or a
Bad Argument response message.
Parse Failed Response
The Parse Failed response message is identified by return code PARSE_FAILED. This response message
indicates a syntactical problem with the command received and can have a data section present to
provide more information about the parse failure. Table 2: Parse Failure Reasons lists possible reasons
for parse failures.
If the data section exists, two optional parameters are possible. The first parameter is a reason text
string stating explicitly what was wrong with the request. The second parameter is a location string
containing the place where the error occurs and, surrounded by curly braces, the portion of the original
request that contained the error. If no specific information is available, the data section is not present
in the response.
The following example shows the syntax of a Parse Failed response message:
data ([reason “Missing comma”], [location “XXXXXXX{} dn XXXXXXXXX”])
Table 2: Parse Failure Reasons
DescriptionReason
The request verb did not match any of the known commands.Unknown request verb
A white space character was missing after some element of the
request.
Space required
An opening or closing parenthesis was missing.Missing paren
50
910-6022-001 Revision A, March 2011
PDBI Request/Response MessagesProvisioning Database Interface Manual