2 Command Line Options
The following parameters can be specified in the command line that starts the ISA Dialog Manager:
When this binary option is set to false (-IDMbinerror=false), error messages are suppressed in the binary reading process.
This option prevents the IDM from administering a callstack that stores the call list of rules, methods, built-in, application, and interface functions, which is output with the dumpstate.
Default Setting
true
Availability
IDM versions A.05.01.g3, A.05.01.h, since A.05.02.e
This option prevents the installation of an exception catcher.
Default Setting
true
Availability
IDM versions A.05.01.g3, A.05.01.h, since A.05.02.e
This option sets the color variant to be used.
When this option is specified, the indicated file is used as configuration file, and the option is removed from the argv parameter. When the option is not given, the IDM looks for the environment variable IDM_CONFIGFILE. The file specified in this variable is then used as configuration file.
If a configuration file has been specified and the file can be opened, the options given in the file are processed before the remaining options of the command line.
The configuration file contains a list of command line options. The characters BLANK (
), TAB (\t
) and RETURN (\n
) can be used as delimiters between options and their parameters.
All options are treated as if they had been input on the command line, which means that they are also used by the application.
-IDMerrfile cannot be used in the same command line.
This option causes log file and error messages to be written to the standard output channels (STDOUT) on Microsoft Windows – analog to Unix. If the process does not run within the console, a new console is opened for potential outputs. In the predecessor versions of Windows XP, a new console is always opened.
Availability
Versions since A.05.02.f; platform Microsoft Windows
-IDMcp_appl <code page>
-IDMcp_format <code page>
-IDMcp_input <code page>
-IDMcp_io <code page>
-IDMcp_output <code page>
These are options to set the code page for various operations. See chapter “Command Line Options for Setting Code Pages”.
This option sets the cursor variant to be used.
This option influences the output of IDM status information (dumpstate). Via the <enum> parameter the output of certain information is enforced.
Parameters
|
Value (enum) |
Meaning |
|---|---|
|
dump_all |
All sections are written out in an abbreviated form. |
|
dump_error |
The sections ERRORS, CALLSTACK and EVENTS are written out in an abbreviated form. |
|
dump_events |
The section THISEVENT/EVENT QUEUE is written out in full. |
|
dump_full |
All sections are written out in full. |
|
dump_locked |
The section SLOTS is written out in full. In addition, for locked objects their attribute values are written out. |
|
dump_memory |
The section MEMORY is written out in full. |
|
dump_none |
No action (nothing is written out). |
|
dump_process |
The section PROCESS is written out in full. |
|
dump_short |
All sections (excluding SLOTS) are written out in an abbreviated form. |
|
dump_slots |
The section SLOTS is written out in full. |
|
dump_stack |
The section CALLSTACK is written out in full. |
|
dump_usage |
The section USAGE is written out in full. |
|
dump_uservisible |
The section VISIBLE OBJECTS is written out in full for all visible top-level objects including their children, the pre-defined and user-defined attributes. |
|
dump_visible |
The section VISIBLE OBJECTS is completely written out. |
Availability
IDM versions A.05.01.g3, A.05.01.h, since A.05.02.e
-IDMdumpstateseverity <string>
The output of a dumpstate normally occurs when an EVAL ERROR or a FATAL ERROR arises. With this option, a dumpstate output can be enforced for other types of errors and messages.
Parameters
|
First Character |
Dumpstate Output… |
|---|---|
|
E |
in case of normal error messages [E: …] |
|
F |
in case of fatal error messages [F: …] |
|
I |
in case of informative messages [I: …], warnings and error messages |
|
O |
only in case of EVAL ERROR |
|
W |
for warnings [W: …] and error messages |
Default Setting
F
Availability
IDM versions A.05.01.g3, A.05.01.h, since A.05.02.e
The ISA Dialog Manager allows setting environment variables from the command line. This is especially useful with the IDM on Microsoft Windows. Microsoft Windows generally provides no means to set environment variables for all applications.
With the command line option ‑IDMenv <variable>=<value> those variables can be set for an IDM application. In doing so, the environment variables of Microsoft Windows are overwritten for the IDM application. The environment variables are set only temporarily and only for the IDM application.
Note
No blanks are allowed between the variable name, the equals sign and the variable value.
This option can be indicated several times in order to set different variables.
Example
Windows
idm -IDMenv BINARY=c:\idm\bin -IDMenv IF=c:\idm\if dialog.dlg
Unix
idm -IDMenv binary=/home/user1/bin -IDMenv IF=/usr/idm/interface dialog.dlg
This option specifies an error file. The file traces all errors that occur while the application runs.
The same can be achieved by setting the environment variable IDM_LOGFILE to a file path.
The command line option overwrites the environment variable when both are set.
With the command line option and the environment variable, none can be specified instead of a file path to prevent the creation of an error file.
In the file name, place holders can be used (see chapter “Place Holders in File Names”).
Note
When the option ‑IDMtracefile (or the respective environment variable) is used in coincidence with this option, the error file specified with this option may not be created or may be left empty. Possible error messages then have been written to the trace file.
-IDMerrwinfile <filepath>|none
This options redirects error messages, which are displayed as messageboxes or output to the console, to the specified file. This enables for example server processes (especially on Microsoft Windows) to run without any user interaction (like the confirmation of error dialogs).
The same can be achieved by setting the environment variable IDM_ERRWIN to a file path.
The command line option overwrites the environment variable when both are set.
With the command line option and the environment variable, none can be specified instead of a file path. This prevents the display of error dialogs and the output of error messages to the console, as well as the creation of a file to trace the errors.
In the file name, place holders can be used (see chapter “Place Holders in File Names”).
Note
When the options ‑IDMerrfile or ‑IDMtracefile (or the respective environment variables) are used in coincidence with this option, the file specified with this option may not be created or may be left empty. Possible error messages then have been written to file specified with the other option.
With -IDMfatalneterrors true a compatible behavior to the IDM versions before A.05.01.d is set for the Distributed Dialog Managers (DDM), enforcing an immediate termination on client and server side when a network, protocol or version error occurs. This means that except for local applications no more start and finish events will be triggered and AppFinish will not be called.
When using a command line option is impossible, the option DMF_FatalNetErrors of the function DM_Initialize can be utilized instead of -IDMfatalneterros. DMF_FatalNetErrors takes precedence over -IDMfatalneterrors.
See Also
C function DM_Initialize
This option sets the font variant to be used.
This option defines, which variant of the format resources is used.
-IDMindent <indent>[:<tabsize>[:<traceindent>]]
This option controls the indenting in source code and optionally for tracing. Moreover, the replacement of spaces through tabs can be configured.
For <indent>, which defines the indenting of source code, and for the optional <traceindent>, which sets up the indenting within the trace file, integral numbers >=0 are allowed. For the optional <tabsize> that controls the replacement of spaces through tabs, only the values 0 and 8 are allowed.
For instance, to get an indenting of three characters for each level without tab replacement, you specify 3:0; an indenting of one tab for each level is achieved with 8:8.
Note
For the trace file, the indenting can also be set up on the setup object.
This option sets the accelerator variant to be used.
This option defines, which variant of the text resources is used.
With this option, the calling of monitoring functions, which have been registered with YiRegisterUserEventMonitor, can be disabled. This option supports error analysis in the case where a monitoring function is supect to cause the error.
The environment variable IDM_NO_YI_MONITORING can be used instead of this command line option.
The command line option overwrites the environment variable when both are set.
Alternatively, the option .options[opt_yi_monitoring] of the setup object can be set to false. If monitoring functions have been disabled through the command line option or the environment variable, they cannot be enabled by setting .options[opt_yi_monitoring] = true on the setup object.
-IDMobjdump_fkey <func_key_no>
This command line option effects that the source code of the active window is written to the trace file when the function key with the number <func_key_no> is pressed. In the trace file, the output source code is marked with the trace codes DC and DR.
The -IDMscale option determines the scaling with which the application is to be displayed. A value of 0 switches off the scaling. The value is given in %.
Default setting:
The current scaling used by the system.
Attention
It is not recommended to use a scaling > 0 and < 100%, as this may impact the display and operation of objects.
Limitations Windows:
This startup option can only be used to turn DPI awareness on or off. However, this option should not be used under Microsoft Windows. Since DPI awareness is a property of the application, it should only be specified via a manifest file. Using the startup option under Windows results in a warning in the trace or log file.
For test purposes, DPI awareness can be switched on (value: 1) or off (value: 0), but should never be changed while the application is running.
Limitations Qt:
Whether a scaling factor set here is actually applied depends strongly on the desktop environment and its support for HighDPI.
Availability
See also
This option sets the search path in which dialog, module, interface and binary files
The search path is a semicolon-separated list of paths (absolute or relative) with the following special features:
|
~ or ~: |
Search beneath the directory in which the application is located. |
|
"" ( |
Search in the current working directory (same behavior as in previous versions). |
|
<ENVNAME>: |
Search in the paths that are defined in the environment variable <ENVNAME>. |
Note
The search path can also be set with DM_ControlEx() and the setup object.
Availability
See also
Chapter “Search Path for Interface, Module, Dialog, and Binary Files” in manual “Programming Techniques”
This option queries the version of the window system interface.
This option only works with the Motif version of the ISA Dialog Manager. With the Windows version it produces an error.
Outputs internal errors, which are handled by IDM, into the trace file too. Normally these errors can be ignored. However, they may provide hints for the cause of other errors in some situations.
This option defines, which variant of the source resources is used for drag&drop actions.
The trace file is used in safety mode. For this option to work, the tracing must be activated via the ‑IDMtracefile <filepath> option.
In order to keep the trace file running during long application sessions without experiencing a slower running system and the use of too many resources, safety tracing uses a limited ring buffer that is held in the memory. The content of the ring buffer is saved to the file on termination of the application.
Availability
IDM versions A.05.01.g3, A.05.01.h, since A.05.02.e
This option is the short form for the combination of the options ‑IDMtracefile <filepath> for activating the tracing and ‑IDMstrace for setting the safety mode.
In the file name, place holders can be used (see chapter “Place Holders in File Names”).
Availability
IDM versions A.05.01.g3, A.05.01.h, since A.05.02.e
This option activates the safety tracing and at the same time defines the settings for this. For this option to work, the tracing must be switched on via the ‑IDMtracefile <filepath> option.
The string parameter influences the setting as follows:
|
Template |
Setting |
|---|---|
|
c<integer> |
Bytes per line |
|
h |
Hierarchical output: Retention of as many hierarchical levels as possible |
|
l<integer> |
Number of lines |
|
r |
Rotating output (default): The oldest line is replaced by the newest |
|
s<integer> |
Length limit for strings |
Through concatenation it is possible to carry out numerous settings at the same time. The order is arbitrary.
Instead of this option the environment variable IDM_STRACEOPTS can be used. The command line option overwrites the environment variable when both are set.
Example
Safety tracing with 300 lines and 80 bytes per line is activated via the option ‑IDMstraceopts l300c80.
Availability
IDM versions A.05.01.g3, A.05.01.h, since A.05.02.e
This option defines, which variant of the target resources is used for drag&drop actions.
This option sets the tile variant to be used.
This startup option specifies the DPI value to be applied to tiles. This DPI value plays a role if images were created for a specific DPI value and are to be displayed accordingly. By default, 96 DPI is assumed.
Availability
See also
This option activates the tracing, which logs all function calls from the IDM, all calls from the IDM to the application and all executed rules into the given file (trace file, see chapter “Tracing” for further information).
The same can be achieved by setting the environment variable IDM_TRACEFILE to a file path.
The command line option overwrites the environment variable when both are set.
In the file name, place holders can be used (see chapter “Place Holders in File Names”).
This option writes additional timestamps into the trace file , in which all IDM function calls, all calls from the IDM to the application, and all executed rules are logged. It is thus possible to perceive the absolute or relative time needed for functions or rules and to take tuning measures if necessary.
Value range
- 0
- No times are logged in the trace file.
- 1
-
This value indicates start time mode. In this mode all start and end times are logged. The time needed for a single structure may then be calculated with the difference. In this mode only the system and user time will be considered.
The times are given in format [hh:mm:ss:uuu] at the beginning of line:
- hh =
- mm =
- ss =
- uuu =
- hh =
- 2
-
This value indicates the trace time mode. In this mode the time difference to the last logged call is given. It is thus possible to easily recognize how much time is needed for individual actions.
In this mode the time difference to the last trace output is given in the format [sss:uuu] at the beginning of line:
- ss =
- uuu =
- ss =
- 3
-
This value specifies the real-time mode. In this case the real time is indicated for each action to be logged in the trace file.
In this mode the real time is given in format [hh:mm:ss] at the beginning of line:
- hh =
- mm =
- ss =
- hh =
This option controls the conversion of a Use Path into a file name. It allows to control file name conversion to upper and lower case. This option should only be used with caution.
The following options are available:
|
L |
The entire file path is converted to lower case. The Use Path |
|
U |
The entire file path including the extension is converted to upper case. The Use Path |
|
u |
The entire file path except for the extension is converted to upper case. The Use Path |
|
l |
Only the first letter of each file path segments is converted to lower case. The Use Path |
Availability
This option queries the version of the IDM runtime environment in use.
The version is output with the pattern
k.vn.sv.pl<additional_info>.
The meaning of the parts is:
|
k |
Kind of release (capital letter, |
|
vn |
Version number, major release (two digits) |
|
sv |
Sub-version number, minor release (two digits) |
|
pl |
Patch level (lowercase letter and optionally one digit) |
|
<additional_info> |
for internal purposes only |
2.1 Place Holders in File Names
When it is stated for command line options or environment variables, that place holders can be used in the file name, these are the available place holders:
|
%Y |
year |
|
%O |
month |
|
%D |
day |
|
%H |
hour |
|
%M |
minute |
|
%S |
second |
|
%J |
day of year |
|
%C |
unique number |
|
%A |
application name |
|
%T |
tty ID |
|
%U |
user ID |
|
%P |
process ID |
The place holders are substituted through the respective values at runtime.
2.2 Command Line Options for Setting Code Pages
The code page options allow to set the character encoding that IDM uses for different operations. The following command line options are available, in which <code page> may be replaced by the code page identifiers listed in chapter “Code Page Identifiers”.
|
Option |
Description |
|---|---|
|
Defines the code page for strings received or returned by application functions. The better solution however is to set this code page through DM_Control from within the application. |
|
|
Defines the code page for strings received or returned by format functions. The better solution however is to set this code page through DM_Control from within the application. |
|
|
Defines the code page which IDM uses for interpreting dialog-, module-, interface-, and init-files if the files carry no encoding mark (see chapter “Encoding Marks for Files”). |
|
|
Abbreviation for setting input and output code page at once (‑IDMcp_input and ‑IDMcp_output). |
|
|
Defines the code page which IDM uses for output files. The option applies to dialogs, modules, interfaces, init-, log-, and trace-files as well as stdout and stdin. |
2.2.1 Code Page Identifiers
With the command line options for setting code pages the identifiers listed below may be used for the parameter <code page>:
|
acp |
ascii |
cp437 |
cp850 |
cp1252 |
|
dec169 |
hp15 |
iso6937 |
iso8859 |
no_conv |
|
utf8 |
utf16 |
utf16b |
utf16l |
winansi |
2.2.2 Encoding Marks for Files
Text files can contain encoding marks within their first 8 bytes that indicate the character encoding of the files. Is an encoding mark is present it takes precedence over a command line option for IDM.
These are the encoding marks recognized by IDM:
|
Encoding mark |
Character encoding |
|---|---|
|
Byte sequence 0xfeff |
UTF-16 BE (big-endian) |
|
Byte sequence 0xffef |
UTF-16 LE (little-endian) |
|
// UTF8 or // utf8 |
UTF-8 |
|
// 8859 |
ISO-8859-1 |
|
// 1252 |
CP1252 |
The hexadecimal byte sequences feff
and ffef
are called Byte Order Marks
(BOM) and are defined in the Unicode standard. The define the sequence of bytes within character codes. feff
indicate big-endian
order where bytes with higher numeric significance come first, ffef
indicates little-endian
order, where bytes with lower numeric significance come first.
If the output code page is set to UTF‑8, UTF‑16, ISO‑8859, or CP1252 through ‑IDMcp_output or ‑IDMcp_io, IDM writes the appropriate encoding mark as prefix into dialogs, modules and interfaces.
Note
Text editors normally do not display the byte order marks feff
or ffef
, but they are visible when opening files with a hex editor.
2.3 Command Line Options in the Simulation Program
The following options can only be used in the simulation program:
This option is only valid with the option +writeproto!
When giving this option, the function prototypes of the functions included in the object applicationID are written out.
This option allows the definition of the target directory where the binary files (with the file extension .bin) are created. By default they are created in the working directory.
The option can only be used in combination with the command line options ‑compile, ‑compile1, ‑recompile and ‑recompile1.
This option causes the IDM and PIDM to run in the builder mode. If it has not already happened, it is started as IDM builder process in the background. All requests for writing interface, binary, funcmap or trampoline files are passed to this IDM builder process. This process works in the shared modules mode to save time when reloading imported modules.
With ‑builder, the server and client mode is determined by the actions (‑writebin, ‑writeexport…) while +builder explicitly activates the client mode. For ‑builder, client mode is automatically assumed when it is used with an action. Without an action it works in the builder process (server).
Availability
Versions since A.05.02.f; platforms Microsoft Windows, Unix/Linux
-builderid <builder-identifier>
Normally the IDM builder process and the IDM or PIDM, that use the process in the builder mode, have the same father process. This can be bypassed by specifying an own builder ID as a file name without the preceding path.
Availability
Versions since A.05.02.f; platforms Microsoft Windows, Unix/Linux
With this option, a running IDM builder process can be stopped before reaching its time-out period.
Availability
Versions since A.05.02.f; platforms Microsoft Windows, Unix/Linux
With this option, the waiting time of the IDM or the PIDM in the builder process mode is defined in seconds. After this time has been reached, the IDM builder process terminates. After the defined waiting period, connection attempts and calls fail.
Note for Unix/Linux
If a too small builder timeout is chosen, this may result in no communication at all between client and server. The pipe file (usually found under /tmp/pipe_idmbuilder…) that is created as a result and not cleared by the system may then have to be deleted manually.
Availability
Versions since A.05.02.f; platforms Microsoft Windows, Unix/Linux
This option limits the writing of class definitions of USW classes for the IDM Eclipse Plugin to the specified class.
It is only valid with the option ‑writeclassdef.
This option deletes all interface and binary files for the loaded dialog and module files as well as all submodules imported with use.
The option -cleancompile1 performs the action only for the loaded dialog or module and not for submodules imported per use.
Availability
See also
Chapter “Compiling Interface and Binary Files for Imports with use” in manual “Programming Techniques”
Sets the base name used in the COPY statement of the generated COBOL file. This option overrides the value that is computed from the -cpyname, -cobname or -writetrampolin options.
Can only be used together with the option +/-writetrampolin.
Availability
Sets the base name for the generated COBOL file. This option overrides the value that is computed from the name specified with -writetrampolin.
The file extension of this file is .cbl
if one of the options -ufcob, -mfviscob or -mfviscob-u is given, otherwise .cob
.
Can only be used together with the option +/-writetrampolin.
Availability
This option causes the interface and binary files to be written for the loaded module or dialog and for all loaded submodules imported per use.
However, these are only rewritten if the file date of the source file(s) is newer than the interface and binary files. This option is intended for use in a Makefile.
To recreate the target files in any case, without checking the file date, the -recompile option can be used.
Possibly necessary directories resulting from the Use Path are created if required. The output directories of the target files can be controlled using the -ifdir and -bindir options.
Since the generated interface and binary files have predefined file extensions (.if and .bin), it is possible to create these files mixed with the sources.
Attention
Existing files will be overwritten.
The option -compile1 performs the action only for the loaded dialog or module and not for submodules imported per use.
Availability
See also
Chapter “Compiling Interface and Binary Files for Imports with use” in manual “Programming Techniques”
Sets the base name for the generated COBOL copy file. This option overrides the name that is given by -cobname or -writetrampolin. The file extension of this file is .cpy
.
Can only be used together with the option +/-writetrampolin.
Availability
This option allows the definition of the target directory where the interface files (with the file extension .if) are created. By default they are created in the working directory.
The option can only be used in combination with the command line options ‑compile, ‑compile1, ‑recompile and ‑recompile1.
Generates COBOL copy files for Micro Focus Visual COBOL.
Can only be used together with the options +writeheader and +/-writetrampolin.
Availability
COBOL Interface for Micro Focus Visual COBOL only.
Generates COBOL copy files for Micro Focus Visual COBOL with support for National Character (Unicode, UTF-16).
Can only be used together with the options +writeheader and +/-writetrampolin.
Availability
COBOL Interface for Micro Focus Visual COBOL only.
This option suppresses the generation of interface files.
The option can only be used in combination with the command line options ‑compile, ‑compile1, ‑recompile and ‑recompile1.
With help of this option a configuration file is loaded.
|
-profile |
configuration file is loaded before DM_StartDialog |
|
+profile |
configuration file is loaded after DM_StartDialog |
See Also
C interface function DM_LoadProfile
COBOL interface function DMcob_LoadProfile
This option causes the interface and binary files to be written for the loaded module or dialog and for all loaded submodules imported per use.
Unlike the option -compile, the target files are always regenerated. There is no date check.
Possibly necessary directories resulting from the Use Path are created if required. The output directories of the target files can be controlled using the -ifdir and -bindir options.
Since the generated interface and binary files have predefined file extensions (.if and .bin), it is possible to create these files mixed with the sources.
Attention
Existing files will be overwritten.
The option -recompile1 performs the action only for the loaded dialog or module and not for submodules imported per use.
Availability
See also
Chapter “Compiling Interface and Binary Files for Imports with use” in manual “Programming Techniques”
A module is searched in a path which is defined via an environment variable. If the corresponding file is found in a directory, it will be loaded and the further search will be interrupted.
In order for this environment variable to be considered on loading the modules, the following option has to be indicated additionally when creating the interface file:+searchsymbol IDMLIB. All file names will then be prefixed by the symbol IDMLIB
.
General Syntax
idm +writeexport <export file name> +searchsymbol <environment variable> <module name>
Example
idm +writeexport color.if +searchsymbol IDMLIB color.mod
See Also
Chapter “Modularization” in manual “Programming Techniques”
Generates COBOL copy files for Micro Focus COBOL.
Can only be used together with the options +writeheader and +/-writetrampolin.
This option can be specified in addition to ‑writeole to register an OLE control for the current user only. The registration data is then written to the Windows Registry under HKEY_CURRENT_USER.
Availability
Since IDM version A.06.01.g
A binary file is created from the ASCII dialog file when this option is specified.
The binary file has a significantly shorter load time, and it cannot be edited by the end user.
With this option the class definitions of all registered USW classes are written to the specified file, which can be used with the IDM Eclipse Plugin. The class definitions are required by the IDM Eclipse Plugin, e.g to enable content assist to propose the attributes for USW classes.
With this option a dialog or module in its current state can be written as text file to filename
. The character encoding (code page) of the file can be set through ‑IDMcp_output or ‑IDMcp_io (see chapter “Command Line Options for Setting Code Pages”). Without these options, the dialog or module will be ASCII encoded.
With this option the developer can create the interface file out of her/his module. Comments which are prefixed by !! and which are attached before the actual objects are included in the interface file. In doing so, the commenting of dialog sources can be made available also to the user of a module.
See Also
Chapter “Modularization” in manual “Programming Techniques”
This option creates a C file and an include file. The include file contains the function prototypes for all functions declared in the DM dialog file (see also option +writeproto). A function table is put in the C file so that, to link the functions, the contained function BindFunctions_<name of dialog> has to be called.
See Also
Manual “C Interface - Basics”
The command line option +writeheader may be used to generate prototypes and record definitions for dynamically connected functions.
The command line for the simulation is built like this:
pidm [+application <name of application>] +writeheader <basefilename> <dialogfile>
If there are C functions, a header file with the suffix .h is created that contains the appropriate function types and record definitions. If COBOL functions with record parameters exist, the copy sections are written to the file with the extension .cpy. If no respective functions are present, no file will be generated.
The command line option is sort of a mixture between the options +writefuncmap and +/-writetrampolin, but without the generation of C and COBOL code. Therefore it is only suitable for the dynamic binding of application functions.
Availability
With this option, the ISA Dialog Manager generates the necessary files to register an OLE server with the system. An idl file for creating the type library and a reg file with the registry entries are generated. The registry entries are stored under HKEY_LOCAL_MACHINE in the Windows Registry so that the registration is effective for all users.
To register an OLE control for the current user only, you can additionally specify the option ‑userregistry.
Note
The Windows tool regedit.exe usually sets no error status in case of an error. If there are problems with the start of an OLE control, the registry should be checked to see if the registry data was loaded at all. Changes to the Windows Registry should be made with caution, as Windows may fail to start in case of errors.
See Also
Chapter “Generating Interface Information” in manual “OLE Interface”
This option creates a file that contains function prototypes for all function declared in the DM dialog file. This file can be used as C include file for the application to check the correctness of the function call.
By means of this option you can check for any dialog whether all defined models are really used within this dialog.
If a model is not used, i.e. it has 0 references, it can be possible that this model is used in a rule to create objects dynamically. Therefore, the output of this option should be used as a hint for a used model.
Example
idm +writerefs TestRefs.txt Test.dlg
+/-writetrampolin <basefilename>
To provide functions for dialogs including records with an application, the C modules generated by the DM have to be compiled and linked. The modules are generated by calling the simulation via the option +/-writetrampolin:
idm +writetrampolin <outfile> <dialogscript>
This statement generates the necessary modules from a dialog script in order to call the functions. The corresponding header files (C and/or COBOL) are created according to the kind of functions using such records.
In combination with +/-writetrampolin the following options can be used:
- -ufcob, -mfviscob and -mfviscob-u to create copy files for Micro Focus COBOL or Micro Focus Visual COBOL respectively.
- -cobbasename, -cobname and -cpyname to customize the base names of the created files.
Support