3.4.4 Service Load Tracing
To enable tracing from the client program, use the TRACE keyword on the SERVICE_LOAD command.
|
Command |
Keyword |
Value |
Developer notes for Command/Keyword/Value |
|
SERVICE_LOAD |
SERVICE |
servicename |
Name of the service to be loaded. |
|
|
TRACE |
*NO |
Optional. Disable tracing. |
|
*YES |
Enable tracing. |
||
|
*ERROR |
Enable tracing and if the service does not return an ERROR, FATAL or SOAPFAULT status to the client, the trace files are deleted on the JSM CLOSE call. |
||
|
TRACE_NAME |
value |
Optional. Append a user-defined name to the end of the client trace subdirectory. |
|
|
*SERVICE |
Use service name as name. |
||
|
*PROCESS |
Use process name as name. |
||
|
*FUNCTION |
Use function name as name. |
||
|
*JOBNAME |
Use job name as name. |
||
|
*JOBUSER |
Use job user as name. |
||
|
*JOBNUMBER |
Use job number as name. |
||
|
*REQUESTID |
Use request Id as name |
||
|
TRACE_GROUP |
value |
Optional. Allows the trace files to be grouped under a specified subfolder. |
During the service loading, tracing can be enabled using this command:
SERVICE_LOAD SERVICE(servicename) TRACE(option) TRACE_NAME(name)TRACE_GROUP(name)