What do you think of this post?
  • Awesome 
  • Interesting 
  • Useful 

-- Download al_engine parameters as PDF --



al_engine  Usage:


-A : BW Request ID consisting of RequestID [30 characters], Selection Date [8 characters], Selection Time [6 characters]

-v : Print version number

-D : Print debug messages

-DRowCount=<n>

-DASID=<s>

-DEngineID=<s>

-DGuiID=<s>

-Did<id>        : Specify the Designer session’s unique id

-Dit<it>        : Specify the Designer session’s execution iteration number

-Dt<timestamp>  : Specify the Designer session’s execution timestamp

-Dscan          : Execute in Data Scan mode

-Dclean         : Cleanup any Data Scan temporary files

-DDataScanRows =<n>

-T<TraceNumber> : Trace numbers. The numbers are:

-1           : Trace all

1           : Trace row

2           : Trace plan

4           : Trace session

8           : Trace dataflow

16          : Trace transform

32          : Trace user transform

64          : Trace user function

128         : Trace ABAP Query

256         : Trace SQL For SQL transforms

512         : Trace SQL For SQL functions

1024        : Trace SQL For SQL readers

2048        : Trace SQL For SQL loaders

4096        : Trace Show Optimized DataFlows

8192        : Trace Repository SQL

524288      : Trace Nested View Processing

4194304     : Trace SAP RFC(BAPI) Function Call

33554432    : Trace adapter/client calls

67108864    : Trace broker communication layer

2147483648  : Trace Audit data

-l<FileName> : Name of the trace log file

-z<FileName> : Name of the error log file (only if any error occurs)

-c<FileName> : Name of the config file

-w<FileName> : Name of the monitor file (must be used together with opti

on -r)

-r           : Monitor sample rate (# of rows)

-test        : Execute real-time jobs in batch test mode

-nt          : Execute in single threaded mode

-np          : Execute in single process mode

-no_audit    : Execute with Audit turned off

-no_dq_capture    : Execute with Data quality statistics capture turned off

-Ksp<SystemConfiguration>    : Execute with system configuration

-Ck          : Execute in checkpoint mode

-Cr          : Execute in checkpoint recovery mode

-Cm<MachineName>       : Name of machine that administrates this job

-Ca<AccessServerName>  : Name of access server that administrates this job

-Ct<JobType>           : Type of this job (e.g. -CtBatch or -CtRTDF)

-Cj<JobServerHostName> : Name of job server’s host that executes this job

-Cp<Port>              : Port of job server that executes this job

-U<User>         : Repository login user

-P<Password>     : Repository login password

-S<Server>       : Repository server name

-N<DatabaseType> : Repository database type

-Q<Database>     : Repository database

-g               : Repository using Windows Authentication (Microsoft SQL Server only)

-X               : Export the repository to file “repo_export.atl”

-XX              : Export the repository to file “export.xml”

-XI<Filename.xml>             : Import information into the repository

-Xp<ObjectType>@<FileName>                : Export the specific repository objects to the atl file

-XX<ObjectType>@<FileName>                : Export the specific repository objects to the xml file

-XX<ObjectType>@<FileName>@<ObjectName>   : Export the specific repository object to the xml file

-XX<ObjectType>@<FileName>@<ObjectName>@DE: Export the specific repository object and its dependents with datastore information to the xml file

-XX<ObjectType>@<FileName>@<ObjectName>@D : Export the specific repository object and its dependents without datastore information to the xml file

<ObjectType> can be one of the following

P : Exports all Projects

J : Exports all Jobs

W : Exports all Workflows

D : Exports all Dataflows

T : Exports all Idocs

F : Exports all user defined File formats

X : Exports all XML and DTD Message formats

S : Exports all Datastores

C : Exports all Custom functions

O : Export all COBOL Copybooks

p : Exports all System Profiles

-x              : Export internal built-in function information

-f<Filename.atl>             : Import information into the repository

-F<Datastore.Owner.Function> : Import function(s)

-H<filename>                 : Import a DTD or XML file to Repo

-I<Datastore.Owner.Table>    : Import a single table

-M<Datastore>                : Import tables and functions

-Y<Datastore.Owner.Treename> : Import a tree class

-el<Datastore.Owner.DBLink>  : Import a database link.

-et<Datastore>               : Print all imported database links for the current Datastore.

-G<guid>    : Execute a session specified by a GUID

-s<Session> : Execute a session

-p<Plan>    : Execute a plan

-GV<global var assign list> : A list of global variable assignments, separated by semicolons t   the whole list in double-quotes.

-a<ABAPProgram> : Generate ABAP code

-V<name=value>  : Set the environment variable <name> with <value>

-L<list of value>    : List of Object Labels from UI (separated by , or ; or space) to filter         Use double quotes around list if space used as a separator.

-Jf<XML file>        : Filter the installation scenario defined in XML file

-Je<XML file>        : Execute the installation scenario defined in XML file

-Ja<parameters file> : Filter and execute the installation scenario defined in XML file

-b  : Populate AL_USAGE table

-ep : Populate AL_PARENT_CHILD table

-ec : Populate AL_COLMAP and AL_COLMAP_TEXT tables

Tree following options are for portable database targets (controlled release).

-WE : Delete properties of portable targets for datastore’s database types other than default.

-WP : Populate properties of all portable targets for all datastore’s database types.

-WD<datastore> : Datastore to which -WE and/or -WP is applied. If <datastore> was not specified, the option will apply to all portable targets.

What do you think of this post?
  • Awesome 
  • Interesting 
  • Useful 

5 comments on “al_engine parameters

  1. Hi Sudheer,

    Is there any way to execute the job and Validate all(Icon in the BODI Designer) through command line?
    Could you please explain me in detail..

    Thanks in advance.

    Prasanna

    • Hi Prasanna,

      There is a way to execute a job from command line but not with a validate all functionality.

      Follow the below steps to execute a job from command line

      1. Go to Admin console and login with appropriate credentials
      2. Select the Project under Batch component and select the appropriate job to export.
      3. Now, click on configuration tab and export the selected job thru ‘Export Execution Command’ to a specific location,
      by default it will go to /log directory. This process creates two files one is .txt file another one is .bat file
      4. You can call the batch .bat file from command prompt that in turn it calls the .txt file to kick off the job.

      Let me know if you need more info

      Cheers,
      Sudheer

      • Hi Sudheer,

        I do not have access to admin console. Is it possible to run a job through command line using the al_engine.exe command. What options/switches would be required for it ? How would the syntax for such a command look like ?

Leave a Reply to B Ravi Shankar Cancel reply

Your email address will not be published. Required fields are marked *


*