SERVICE_LOAD

LANSA Integrator

SERVICE_LOAD

Loads and initializes the service.

 

                                                          Required

 

 SERVICE_LOAD ---- SERVICE --------- service name --------------->

 

 

                                                          Optional

 

               >-- TRACE ----------- *NO ------------------------>

                                     *YES

                                     *ERROR

 

               >-- TRACE_NAME ------ name -----------------------|

                                     *SERVICE

                                     *PROCESS

                                     *FUNCTION

                                     *JOBNAME

                                     *JOBUSER

                                     *JOBNUMBER

 

For more information refer to:

Service Program Tracing from the Client

Keywords

SERVICE

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

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.

TRACE_NAME

The optional TRACE_NAME 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

Examples

RDML

 

CHANGE FIELD(#JSMCMD) TO('SERVICE_LOAD SERVICE(ZIPSERVICE)'

USE BUILTIN(JSM_COMMAND) WITH_ARGS(#JSMCMD) TO_GET(#JSMSTS #JSMMSG)

 

RDMLX

 

#jsmcommand := 'service_load service(zipservice)'

use builtin(jsmx_command) with_args(#jsmxhdle1 #jsmcommand) to_get(#jsmxsts #jsmxmsg)