AJ

Explanation

For call-level programs: For calls that provide parameters in the I/O area, such as SETS, ROLS,, and INIT, the format of the parameters in the I/O area is invalid.

For INIT VERSION (dbname=number), the syntax of the parameters in the I/O area is invalid. For example, a required value might be missing.

For database calls that include SSAs, such as the get-type calls, DLET, REPL, and ISRT, the format of one of the SSAs is invalid. The number in the segment level number field of the DB PCB is the level number of the SSA that is invalid. Some possible reasons for the invalid SSA format are:

• The SSA contains a command code that is invalid for that call.
• The relational operator in the qualification statement is invalid.
• A qualification statement is missing a right parenthesis or a Boolean connector.
• A comparative value contains one or more parentheses.
• A DLET call has multiple or qualified SSAs.
• A REPL call has qualified SSAs.
• The last SSA on an ISRT call is a qualified SSA.
• An ISRT call that inserts a logical child segment into an existing database includes the D command code. ISRT calls for logical child segments cannot be path calls.
• The RSA parameter on a GSAM call is invalid.
• The SSA used an R, S, Z, W, or M command code for a segment for which no subset pointers are defined in the DBD.
• The subset command codes included in the SSA are in conflict; for example, if one SSA contained an S status code and a Z status code, Fast Path would return an AJ status code. S means to set the pointer to current position; Z means to set the pointer to 0. You cannot use these status codes in one SSA.
• The pointer number that follows a subset pointer command code is invalid. Either you did not include a number, or you included an invalid character. The number that follows the command code must be between 1 and 8, inclusive.
• The SSA included more than one R command code. An SSA can include only one R command code.
• The specified size for the SSA is too small. After this status code is returned, your position in the database is unchanged.
• In response to a SETS or ROLS call, the length of the I/O area is 0, the LL field is less than 4, or the ZZ field is not 0.
• In response to an INIT call, the format of the I/O area is incorrect.
• For calls that provide the length of the I/O area in the AIB, such as INQY, the I/O area length is invalid.
• For SETO, I/O area length is less than 4096 or less than the minimum.
• For the Q command code, the specified lock class is not a letter (A-J).
• A DL/I call with multiple SSAs was constructed in such a manner that the SSAs were conflicting and resulted in an impossible retrieval.

For command-level programs: An ISRT command attempted to insert a logical child segment by using a path command. ISRT commands for logical child segments cannot be path commands.