AionDS Messages and Codes Guide
AionDS Messages and Codes Guide AionDS Messages and Codes Guide
Examining the system log SQL Messages .........................................................................................................................................................................................................˝.......................................... Overview 8-12 AionDS Messages and Codes After each SQL call, AionDS writes information to the system log. The log entry consists of the statement that AionDS passed to the SQL database and an optional error code if an error occurred. The format of the log entry is as follows: where ADS##### sev [(sql_code)] SQL: sql_stmt ##### unique number that identifies the AionDS subsystem from which the message was issued sev message severity sql_code value of SQLCODE in SQLCA sql_stmt SQL statement .........................................................................................................................................................................................................˝.......................................... Examples Here is an example of an SQL error message: ADS37303 I SQL: select * from c3871dp.cars ADS37303 E SQL: (-128) update flight set cost = 100000 where ADS37303 E cost = 0 In the second example, the actual SQL statement could be the following: sql ('update flight set cost = :n_cost where cost = :unk_cost') The values of N_COST and UNK_COST are substituted for the parameters when AionDS executes the statement.
DL/I Messages Examining the system log After each DL/I call, AionDS writes information to the system log. The format of the log entry is as follows: where ADS##### sev call_type,segment,dbname,dli_request,rc='pcb_status' ##### unique number that identifies the AionDS subsystem from which the message was issued sev message severity call_type AionDS-defined call type segment segment name dbname database name dli_request DL/I function code pcb_status PCB status code returned by the call .........................................................................................................................................................................................................˝.......................................... Example The following line shows a sample entry in the log: ADS35000 I DL/I: Get,SKILLS,EMPDB,GN,rc=' ' The request is a GET that operates on the SKILLS segment of the EMPDB database. AionDS executed a GN function. The return code of two blanks indicates that the call completed successfully. AionDS System Log 8-13
- Page 307 and 308: MAESLOG messages ..................
- Page 309 and 310: MAESLOG messages ..................
- Page 311 and 312: MAESLOG messages ..................
- Page 313 and 314: MAESLOG messages ..................
- Page 315 and 316: MAESLOG messages ..................
- Page 317 and 318: MAESLOG messages ..................
- Page 319 and 320: MAESLOG messages ..................
- Page 321 and 322: MAESLOG messages ■ The node is ac
- Page 323 and 324: MAESLOG messages ..................
- Page 325 and 326: MAESLOG messages ..................
- Page 327 and 328: MAESLOG messages ..................
- Page 329 and 330: MAESLOG messages ..................
- Page 331 and 332: MAESLOG messages ..................
- Page 333 and 334: MAESLOG messages ..................
- Page 335 and 336: MAESLOG messages ..................
- Page 337 and 338: Chapter 7 AionDS Fatal System Error
- Page 339 and 340: Overview Only at edit time can the
- Page 341 and 342: Fatal system errors ...............
- Page 343 and 344: Fatal system errors ...............
- Page 345 and 346: Fatal system errors ...............
- Page 347 and 348: Chapter 8 AionDS System Log .......
- Page 349 and 350: Examining the system log database T
- Page 351 and 352: Execution messages Examining the sy
- Page 353 and 354: Consultation messages Examining the
- Page 355 and 356: Examining the system log ..........
- Page 357: Examining the system log ..........
- Page 361: AionDS Messages and Codes DC0431
Examining the system log<br />
SQL <strong>Messages</strong><br />
.........................................................................................................................................................................................................˝..........................................<br />
Overview<br />
8-12 <strong>AionDS</strong> <strong>Messages</strong> <strong>and</strong> <strong>Codes</strong><br />
After each SQL call, <strong>AionDS</strong> writes information to the system log. The log<br />
entry consists of the statement that <strong>AionDS</strong> passed to the SQL database <strong>and</strong><br />
an optional error code if an error occurred. The format of the log entry is as<br />
follows:<br />
where<br />
ADS##### sev [(sql_code)] SQL: sql_stmt<br />
##### unique number that identifies the <strong>AionDS</strong> subsystem from<br />
which the message was issued<br />
sev message severity<br />
sql_code value of SQLCODE in SQLCA<br />
sql_stmt SQL statement<br />
.........................................................................................................................................................................................................˝..........................................<br />
Examples<br />
Here is an example of an SQL error message:<br />
ADS37303 I SQL: select * from c3871dp.cars<br />
ADS37303 E SQL: (-128) update flight set cost = 100000<br />
where<br />
ADS37303 E cost = 0<br />
In the second example, the actual SQL statement could be the following:<br />
sql ('update flight set cost = :n_cost where cost =<br />
:unk_cost')<br />
The values of N_COST <strong>and</strong> UNK_COST are substituted for the parameters<br />
when <strong>AionDS</strong> executes the statement.