R3_ACTIVATE_SESSIONS
Use the R3_ACTIVATE_SESSIONS script element to process batch input sessions. You can retrieve the batch input sessions that should start through various selections, or use the QID= parameter to start a particular single batch input session. You can retrieve the queue ID of individual sessions from the selection results of R3_GET_SESSIONS that are stored in the activation report or in a file.
Transaction: SM35
Interface: AE
This page includes the following:
Syntax Option 1
R3_ACTIVATE_SESSION[S]
NAME=...
[,STATUS=...]
[,NOFOUND=...]
[,ERROR=...]
[,ERRORLEVEL=...]
[,SELECT=...]
[,JOBNAME=...]
[,ORDER_BY=...]
Parameters
-
R3_ACTIVATE_SESSION[S]
Processes batch input sessions -
NAME=
Selects sessions according by names (such as 'xxx*')
Format: script literal -
STATUS=
(Optional) Selects sessions by status
Format: script literal
Allowed values:-
"" (default)
Session that should be processed -
E
Erroneous session
-
-
NOFOUND=
(Optional) Action to be taken if no sessions have been selected
Format: script literal
Allowed values:-
NORMAL (default)
Script execution continues, the AE job ends normally -
ABEND
Script execution stops, the AE job ends abnormally
-
-
ERROR=
(Optional) Action to be taken if one of the selected sessions terminates abnormally
Format: script literal
Allowed values:-
ABEND (default)
Script execution stops, the AE job ends abnormally -
IGNORE
Script execution continues, the AE job ends normally
For details, see
-
-
ERRORLEVEL=
(Optional) Defines the number of erroneous transactions in percent (%)
Format: script literal
Default value: 101, the job ends abnormally if this number is exceeded -
SELECT=
(Optional) Selects once or permanently
Format: script literal
Allowed values:-
ONCE (default)
The number of selected session is retrieved once -
EVERY
The number of selected sessions is retrieved after each session release. In doing so, you can parallelize released sessions.
-
-
JOBN[AME]=
(Optional) Each session is processed with an SAP job
Format: script literal
Allowed values:-
ATTRIBUTE (default)
Contents of the Job Name text field in the host attributes. A standard AE job name is created if there is no text. For details, see SAP ABAP, Java and PI. -
SESSION
Name of the session that should be processed
-
-
ORDER[_BY]=
(Optional) This parameter is supported as of SAP version 4.6. Use it to define the order in which the batch input sessions should be processed. The selection is sorted according to the criteria that you specify in this parameter. All field names of the APQI SAP table can be used.
Example: ORDER_BY=GROUPID
Example
The following example processes 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
SYNTAX Option 2
R3_ACTIVATE_SESSION[S]
[QID=...]
[,NOFOUND=...]
[,ERROR=...]
[,ERRORLEVEL=...]
[,JOBNAME=...]
Parameters
-
R3_ACTIVATE_SESSION[S]
Processes batch input sessions -
QID=
Queue ID that clearly identifies a batch input session. Use this parameter to start a single batch input session.
Format: script literal -
NOFOUND=
(Optional) Action to be taken if no sessions have been selected
Format: script literal
Allowed values:-
NORMAL (default)
Script execution continues, the AE job ends normally -
ABEND
Script execution stops, the AE job ends abnormally
-
-
ERROR=
(Optional) Action to be taken if one of the selected sessions terminates abnormally
Format: script literal
Allowed values:-
ABEND (default)
Script execution stops, the AE job ends abnormally -
IGNORE
Script execution continues, the AE job ends normally
For details, see
-
-
ERRORLEVEL=
(Optional) Defines the number of erroneous transactions in percent (%)
Format: script literal
Default value: 101, the job ends abnormally if this number is exceeded -
JOBN[AME]=
(Optional) Each session is processed with an SAP job
Format: script literal
Allowed values:-
ATTRIBUTE (default)
Contents of the Job Name text field in the host attributes. A standard AE job name is created if there is no text. For details, see SAP ABAP, Java and PI. -
SESSION
Name of the session that should be processed
-
Example
The following example starts a single batch input session where the queue ID is specified as a parameter:
R3_ACTIVATE_SESSION QID='20020318171302022315'
ERROR/ERRORLEVEL Parameters
When processing R3_ACTIVATE_SESSIONS, the AE first retrieves a list of sessions that should be processed from the SAP system. Each of these sessions is processed with an individual SAP job that is referred to as a replayer. A replayer uses the RSBDCBTC ABAP program to process sessions.
-
ERROR
Refers to the result (status) of the replayer. The status can be "A" for abend or "F" for finished successfully.
-
ERROR=IGNORE
The session that is next on the list is processed in any case. The result of the previous replayer is ignored.
-
ERROR=ABEND
Processing of sessions stops immediately if a replayer ends with the status "A". The AE job abends.
-
ERRORLEVEL
Always refers to the session itself and is checked when the replayer ends. ERRORLEVEL defines the number of incorrectly processed transactions within a session in %. When the session value is exceeded, the processing of the AE job is canceled. No further sessions of the session list are processed. Successfully processed transactions are only checked if an ERRORLEVEL is specified.
See also: