SERVICE_LOAD

 SERVICE

The name of the service to be loaded - in this case AxesTerminalService.

TRACE

To enable tracing from the client program use the TRACE keyword on the SERVICE_LOAD command.

The possible values for the TRACE keyword are:

• *NO
• *YES
• *ERROR

The trace option *ERROR will turn on 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.

The TRACE keyword will override the settings in the manager.properties file.

TRACE_NAME

This optional keyword allows the client to append a user-defined name to the end of the client trace subdirectory.

Special keyword values are also available for the TRACE_NAME keyword.

• *SERVICE
• *PROCESS
• *FUNCTION
• *JOBNAME
• *JOBUSER
• *JOBNUMBER

TRACESCREENS

If tracing is in effect (according to the value specified on the TRACE keyword or in the manager.properties file), this keyword may be used to enable additional tracing of the aXes terminal screen images. Note that enabling the tracing of the screen images may greatly expand the size of the resulting service.txt trace file.

The possible values for the TRACESCREENS keyword are:

• *YES
• *NO

If not specified, a default of *YES is assumed. Note that this is only effective of tracing is enabled.

AXESLOG

If tracing is in effect (according to the value specified on the TRACE keyword or in the manager.properties file), this keyword may be used to enable the creation of an aXes log file. The aXes log file may be useful in diagnosing issues associated with the aXes terminal operations.

The possible values for the AXESLOG keyword are:

• *NO
• *YES

If not specified, a default of *NO is assumed.