The MAES Log shows client communication messages from OAES. Since these messages do not have message codes assigned to them, they are written to the MAES Log if the MAES Log is activated (MAESLOG=YES or MAESLOG=msg codes).
To specify that the MAES Log display only client messages, including Execution Trace, use the following command:
MAESLOG=(2-3)
The following is an example of filtered MAES Log output, showing only client messages (including application trace statements):
Parm # 8 is DATE: 2039/12/31 at B36C2
Parm # 9 is INT: 12B31EA8 Parm # 10 is REAL: 0.000000 Parm # 11 is LPSTR, Length(1024) Parm # 12 is BOOL: 12B31ED8 Parm # 13 is INT: 12B31EE8 Parm # 14 is REAL: 0.000000 Parm # 15 is LPSTR, Length(1024) Parm # 16 is BOOL: 12B31F18 Parm # 17 is INT: 12B31F28 Parm # 18 is REAL: 0.000000 Parm # 19 is LPSTR, Length(1024) Parm # 20 is BOOL: 12B31F58 Parm # 21 is INT: 12B31F68 Parm # 22 is REAL: 0.000000 Parm # 23 is LPSTR, Length(1024) Built parameter list: Calling otype_mall_many 0.08 --executing mall_many (otype_00001) 0.08 --completed mall_many otype_mall_many returned: 11C708 Sending response for otype_mall_many Function request: otype_Delete Function pointer: 12A97FF8 Returntype is INT otype_Delete has 1 parms: Parm # 1 is INT: 12B31668 Built parameter list: Calling otype_Delete 0.10 --application terminated 0.10 Aion execution completed:: 2001/02/12 10:11:14 otype_Delete returned: 0 Sending response for otype_Delete Cleanup received,shutting down. Freeing 3072 bytes of memory at: 12A83028 Terminating subtask A001 VLOG: Cleanup received, shutting down
| Copyright © 2009 CA. All rights reserved. | Email CA about this topic |