R3_ACTIVATE_SESSIONS
Processes batch input sessions.
Transaction: SM35
Interface: AE
Syntax
R3_ACTIVATE_SESSION[S]
NAME=...
[,STATUS=...]
[,NOFOUND=...]
[,ERROR=...]
[,ERRORLEVEL=...]
[,SELECT=...]
[,JOBNAME=...]
[,ORDER_BY=...]
Syntax |
Description/Format |
---|---|
NAME= |
Selection of sessions by name (such as 'xxx*'). |
STATUS= |
Selection of sessions by status. Allowed Values: "" (default value) and "E" "" - Session that should be processed. |
NOFOUND= |
Action if no sessions have been selected. Allowed values: "NORMAL" (default value) and "ABEND" "NORMAL" - Script execution continues, the AE job ends normally. |
ERROR= |
Action if one of the selected sessions terminates abnormally. Allowed values: "ABEND" (default value) and "IGNORE" ABEND - Script execution stops, the AE job ends abnormally. For more information, see ERROR/ERRORLEVEL with R3_ACTIVATE_SESSIONS. |
ERRORLEVEL= |
Defines the number of erroneous transactions in percent (%). Default value: "101" The job ends abnormally if this number has been exceeded. |
SELECT= |
Single or permanent selection. Allowed values: "ONCE" (default value) and "EVERY" ONCE - The number of selected session is retrieved once. |
JOBN[AME]= |
Each session is processed with an SAP job. Allowed values: "ATTRIBUTE" (default value) and "SESSION" "ATTRIBUTE" - Contents of the "Job Name" text field
in the host attributes. A standard AE job name is created if there is no text. For more information, see SAP ABAP, Java and PI. |
ORDER[_BY]= |
Criteria that can be used to sorting the selection of session. All field names of the SAP table APQI can be used. Example: ORDER_BY=GROUPID This parameter is supported for SAP version 4.6 and later ones. |
R3_ACTIVATE_SESSION[S]
[QID=...]
[,NOFOUND=...]
[,ERROR=...]
[,ERRORLEVEL=...]
[,JOBNAME=...]
Syntax |
Description/Format |
---|---|
QID= |
Queue ID that clearly identifies a batch input session. This parameter can be used to start a single batch input session. |
NOFOUND= |
Action if no sessions have been selected. Allowed values: "NORMAL" (default value) and "ABEND" "NORMAL" - Script execution continues, the AE job ends normally. |
ERROR= |
Action if one of the selected sessions terminates abnormally. Allowed values: "ABEND" (default value) and "IGNORE" ABEND - Script execution stops, the AE job ends abnormally. For more information, see ERROR/ERRORLEVEL with R3_ACTIVATE_SESSIONS. |
ERRORLEVEL= |
Defines the number of erroneous transactions in percent (%). Default value: "101" The job ends abnormally if this limit has been exceeded. |
JOBN[AME]= |
Each session is processed with an SAP job. Allowed values: "ATTRIBUTE" (default value) and "SESSION" "ATTRIBUTE" - Contents of the "Job Name" text field
in the host attributes. A standard AE job name is created if there is no text. For more information, see SAP ABAP, Java and PI. |
The batch input sessions that should be started can be retrieved using a selection. Use the parameter QID= to start a single batch input session. The selection results of R3_GET_SESSIONS that are stored in the activation report or in a file serve to locate the individual session by queue ID.
The parameter ORDER_BY can be used to define the order in which the batch input sessions should be processed. The selection is sorted according to the criteria that have specified in this parameter.
Examples
Processing all sessions called 'FI*'. The job will end abnormally if it contains invalid transactions.
R3_ACTIVATE_SESSIONS NAME='FI*',STATUS=,NOFOUND=NORMAL,ERROR=ABEND,ERRORLEVEL=0
In the second example, a single batch input session starts whose queue ID has been specified as a parameter.
R3_ACTIVATE_SESSION QID='20020318171302022315'
See also:
seealso