PAM / DARTS Replication Task

Background

As the DARTS system is introduced, PAM data files need to be sent to it. But since it is running in parallel with PAM processing, it was decided that PAM files input from test cells would be split into 2 independent streams, one going to PAM as usual and the other to DARTS. This task replicates a single PAM stream into a PAM and a DARTS stream.

This task is based on the standard external data manager (ext.dat.man) process and file structure. The standard file structure is:

<data_type>/ready/<test_cell_1>
                 /<test_cell_2>
                 /...
<data_type>/hold/<test_cell_1>
                /<test_cell_2>
                /...
<data_type>/complete/<test_cell_1>
                    /<test_cell_2>
                    /...
Each test cell directory will then contain input or response files for that test cell. There are 3 sets of directories in this format, the source files, the target PAM files and the target DARTS files. All 3 have the standard ext.dat.man file structure illustrated above.

Managing Load Processing

Test cells are responsible for getting files to the appropriate location under the source "ready" directory. Once there this task will copy them to the corresponding target PAM and DARTS directories.

The source directory only needs to be monitored to insure that this task is running and that files are not backing up because it isn't running. This directory should typically only have files under the "ready" directory for a short period of time and in the "complete" directory. The "hold" directory should only ever have incomplete files since this is the only type of error possible for this task. An incomplete file is one for which the standard PAM terminate line, '*DONE' never shows up even after a reasonable period of time.

The target directories have their own processing programs. Those programs determine the policies and handling of files here. The standard PAM data loading applies to the PAM target and the DARTS data loading applies to the DARTS target.

There are 2 scripts involved in managing this task.

This process is controlled by a configuration properties file. A documented sample should be included in the package containing this writeup. See it for further details.