Command lines using ADELJOB must have the following syntax:
ADELJOB EnvironmentName JobType JobParam OptionList
where OptionList => (nothing) | Option OptionParam OptionList
The table below shows the various possible combinations of ADELJOB command parameters, including the possible values of the OptionList parameter:
We recommend viewing it in full screen mode.
JobType |
JobParam |
OptionList |
||
Option |
OptionParam |
Notes on Option |
||
PDMGEN (Generates the PDM) |
|
|||
LogicalEntityName |
/AS400 or /AS400SQL or /DB2 or /BTRIEVE or /ORACLE or /SQLSERVER or /MYSQL or /POSTGRESQL or /ACCESS |
Database type used to generate the PDM. |
||
/KEY (*) |
Generates the physical file with a key. If /KEY is not used, the physical file and the associated logical file are generated. |
|||
/CLEAR (*) |
Clears the data before generating. |
|||
/DEL_REF_CNT (*) |
Destroys all constraints referencing the entity. |
|||
/DEL_CNT (*) |
Destroys the entity's constraints. |
|||
/CRT_TBL (*) |
Creates the table. If no constraint management option is specified, this is the default value. |
|||
/CRT_CNT (*) |
Creates the entity's constraints. |
|||
/CRT_REF_CNT (*) |
Creates the constraints referencing the entity. |
|||
| /GEN_SCRIPT (*) | FileName | Generates a generic entity description file. | ||
| /SQL_SCRIPT (*) | FileName | Generates a SQL script. | ||
| /NEW_FILE (*) | Creates a new file. If this option is omitted, the generated queries will be added to the existing file. | |||
| /FORMAT_FILE (*) | Formats the generated SQL script. | |||
| /OMIT_LIBRARY (*) | Omits the name of the AS400 library in the generated script. | |||
ERRMSGFILE (Generates the error message file) |
AppAreaName or *REPOSITORY |
/ADELIA400 or /ADELIA_WINDOWS or /VADELIA_WINDOWS or /VADELIA_JAVA or /VADELIA_CLOUD or /EVENT_ADELIA or /ADELIA_WEB or /WINDOWS_SERVER or /JAVA_SERVER or /AS400_SERVER |
Error message file generation type. As from version Adelia Studio, /VADELIA_WINDOWS replaces /VISUAL_ADELIA. |
|
/ADD (*) |
Generates in Add/Modify mode (only with /ADELIA400 and /ADELIA_WINDOWS). If /ADD is not used, the job is generated in Replace mode. |
|||
PGMGEN (Generates programs) |
ProgramName |
With SADELIA, VADELIA or WADELIA programs. |
||
/C or /RPG |
With ADELIA programs. |
|||
CLAGEN (Generates classes) |
ClassName |
|||
EXECUTE (Executes a command line) |
CommandLine |
/JOBNAME (*) |
JobName |
Name of the job used in the job manager. |
For all |
/LOG (*) |
FileName |
Logs the job creation in the log file. |
|
/BATCH (*) |
Executes ADELJOB in batch mode (no interactive message display). |
|||
/SYNC (*) (1) |
Execution of ADELJOB in totally synchronous mode. The job is no longer submitted in the job manager, but executed in synchronous mode. The job is visible in the job manager, but runs even if the job manager is not opened. |
|||
(*) These options are not mandatory.
(1) Caution: if your test programs have AS/400 server parts, you must be, on your AS/400, at least at the level of PTF 003 of the AS/400 part of Adelia Studio 13.
Rules and restrictions
JoinEntityName, AppAreaName, ProgramName and JobName must not exceed 15 characters in length.
CommandLine, JobName and FileName must be placed between quotes if they contain spaces.
If CommandLine contains the " character (quote), it must be preceded by a \ (backslash). This applies if the executable file in the command line includes parameters and/or if its path name contains spaces.
Example: AdelJob KBADEL Execute "\"C:\Path with spaces\Executable.exe\" \"parameter with spaces\""
CommandLine must not be longer than 1,000 characters.
All parameters can be entered in upper or lower case, with the exception of CommandLine, JobName and FileName which are case sensitive.
You can use the /BATCH option so that no interactive messages (such as error messages and job creation success or fail messages) are displayed while the job is being created, apart from any messages concerning errors that occur while connecting to the environment.
Click below for further information about: