IMAGINE command: Difference between revisions
Jump to navigation
Jump to search
Created page with "{{DISPLAYTITLE:IMAGINE command}} <span class="pageSubtitle">Move Model 204 data to Imagine</span> This command provides the facilities to extract <var>Model 204</var> data and load it into <var>Imagine</var>. ==Summary== <dl> <dt>Privileges</dt> <dd>File manager</dd> <dt>Function</dt> <dd>provides the facilities to extract <var>Model 204</var> data and load it into <var>Imagine</var>.</dd> </dl> ==Syntax for IMAGINE== <p class="syntax">IMAGINE SYNC | EXTRACT [NOCOMMIT..." |
(No difference)
|
Revision as of 03:34, 2 May 2025
Move Model 204 data to Imagine
This command provides the facilities to extract Model 204 data and load it into Imagine.
Summary
- Privileges
- File manager
- Function
- provides the facilities to extract Model 204 data and load it into Imagine.
Syntax for IMAGINE
IMAGINE SYNC | EXTRACT [NOCOMMIT] [TICK t] [MAXPENDING m]
Where:
- SYNC indicates that data is to be extracted and the Model 204 file and Imagine are to be kept in sync after the command.
- SYNC indicates that data is to be extracted but the Model 204 file and Imagine are not to be kept in sync after the command.
- NOCOMMIT indicates that the data is to be sent to Imagine and processed, but not committed. This provides a way of validating that a file can be loaded into Imagine without actually doing so.
- TICK indicates the number of records between progress messages (M204.3073) to the journal. This parameter also sets the frequency of progress messages on Imagine. TICK defaults to 100000.
- MAXPENDING indicates the maximu number of uncommitted record sends to be allowed in the extract. Setting this to a low value could result in reduced transfer rates because of network latency. MAXPENDING defaults to 4095.
There is also a format of the IMAGINE command:
IMAGINE ENDSYNC
That indicates a SYNC or EXTRACT for the file should be terminated.