Avaya Media Processing Server Series System (Software Release 2.1) Instrukcja Użytkownika Pobierz pdf (Strona 293)

Configuration Procedures and Considerations

# P0602477 Ver: 3.1.11 Page 293

• If the target machine is different from the source, then vengine’s command

line has to define the node running vmst with the -v option for both the

reader and writer (only one example is shown here):

vengine -p202 -v hostname:mps# -O "read:(line:201)

write:(file:xyz)" dbcopy

Database Format Conversion

Performing a database format conversion is similar to a platform conversion, except

that the target database file (writer) created by dbman is of a different format.

Considerations:

• If the record length of the new file is less than the original, records are

truncated.

• If the new file format doesn't allow copying of all the records (number of

records for HSAM or unique/non unique keys for KSDS/DISAM) records are

copied up to the violating record.

Reader/Writer Synchronization

By default, the reader waits one minute to connect to the writer. To change this timer,

modify the wait:hhmmss parameter in the -O option:

vengine -p201 -v1 -O "read:(file:abc) write:(line:202)

wait:300" dbcopy

This example represent a 3 minute delay (00 hours, 03 minutes, 00 seconds).

File Size Limitations

Because of the vmst message size limitations, the maximum record size is limited to

4,000 bytes. Use TDQ files for larger records.

For further information on databases, applications, and their manipulation, see the

PeriProducer User’s Guide.

1 2 ... 288 289 290 291 292 293 294 295 296 297 298 ... 305 306

Brak uwag

Avaya Media Processing Server Series System (Software Release 2.1) Instrukcja Użytkownika Strona 293