WES-2 Bridge News

The current WES-2 Bridge release is 17.3.1 for RedHat 7. A 19.x build to support Hazard Services is under development.

Warning Decision Training Division

Office of Chief Learning Officer

AWIPS-2 Archiver

Enter Your Main Content Here

Every site needs to perform some local configuration for the AWIPS-2 archiver to include their local datasets which could not be archived otherwise. This page includes actual ("tested") configurations for situations encountered at NWS field offices for both LDM pqact.conf and the archiver configuration files RAW_DATA.xml and PROCESSED_DATA.xml. These configurations ensure the archives are in a format that WES-2 Bridge can use.

Below are examples of configurations for Raw Data, Processed Data, and the LDM pqact.conf file. Click on any of the blue bars to open or close the item.

These examples were updated and tested on June 6, 2016.

Raw Data

Note that the RAW_DATA.xml entries below are very sensitive to the punctuation and other characters that immediately precede or follow the digits that represent the date. In many cases, in the actual filename, an underscore character precedes or follows the ten digits that represent YYYYMMDDHH. While this underscore could be captured by a .* regular expression, specifying it explictly ensures that those ten digits are used for the date (as opposed to the second ten digits that sometimes appear at the end of the filename which represent the Epoch seconds for the LDAD file write time).

Canadian Model (HRDPS)

Canadian Model (Northern Hemisphere)

This data is found in /data_store/manual/grib/YYYYMMDD/HH, where YYYYMMDD/HH is the time the data were received and processed by AWIPS-2. The processed versions are typically found in /awips2/edex/data/hdf5/grid/Canadian-NH or /archive/grid/Canadian-NH.

Sample Filenames:

CMC2_nh_ACPCP_SFC_0_latlon.6x.6_2015082500_P144.Grb2.1440478052
LDAD-GRIB-CMC2_nh_APCP_SFC_0_latlon.6x.6_2015082100_P126.Grb2_2015-08-21_043450

This sample entry works for both of these filenames.

RAW_DATA.xml

<dataSet>
    <dirPattern>(manual)/grib/\d{8}/\d{2}</dirPattern>
    <filePattern>.*(CMC2_nh).*_(\d{4})(\d{2})(\d{2})(\d{2}).*</filePattern>
    <timeType>Date</timeType>
    <displayLabel>{1}-Canadian Model (Northern Hemisphere)</displayLabel>
    <dateGroupIndices>3,4,5,6</dateGroupIndices>
</dataSet>

Sample Filename: LDAD-GRIB.GEMWRSubsector_2015111012_P156.grib2.1447175704

RAW_DATA.xml

<dataSet>
     <dirPattern>(manual)/grib/\d{8}/\d{2}</dirPattern>
     <filePattern>.*(GEMWR).*_(\d{4})(\d{2})(\d{2})(\d{2}).*</filePattern>
     <timeType>Date</timeType>
     <displayLabel>{1}-Canadian</displayLabel>
     <dateGroupIndices>3,4,5,6</dateGroupIndices>
</dataSet>

Sample Filename: LDAD-GRIB.GEMWRSubsector_.1446524277

This file was in /data_store/manual/grib/20151103/04. The epoch seconds (1446524277) represents Nov 3, 2015 at 041757 UTC, but the file itself was from the 00Z run of the Canadian model (determined by ingesting this particular file on a standalone system).

Can the LDAD configuration be changed to include the model cycle time in the filename? The other alternative, which is used below, is to use the directory name to get the time (or the Epoch seconds from the filename), but it is not representative of the actual data, because it is the time the file was processed by the system, and not the time of the data.

RAW_DATA.xml

<dataSet>
     <dirPattern>(manual)/grib/(\d{4})(\d{2})(\d{2})/(\d{2})</dirPattern>
     <filePattern>.*(GEMWRSubsector)_.*</filePattern>
     <timeType>Date</timeType>
     <displayLabel>{1}-Canadian Model Western Region Sector</displayLabel>
     <dateGroupIndices>2,3,4,5</dateGroupIndices>
</dataSet>

Canadian Model (Regional)

Climo PoP

This data may be found in /data_store/manual/grib/YYYYMMDD/HH, where YYYYMMDD/HH is the time the data were received and processed by AWIPS-2. The processed versions are probably found in /awips2/edex/data/hdf5/grid and /archive/grid with names like MAVClimoPoP, METClimoPoP, MEXClimoPop, WPCClimoPop.

Sample Filenames:

LDAD-GRIB-MAVClimoPoP_20151008_0600__20151009_0000.grb2_2015-10-08_104822
LDAD-GRIB-METClimoPoP_20151002_0000__20151002_1200.grb2_2015-10-02_034711
LDAD-GRIB-MEXClimoPoP_20151008_1200__20151013_1200.grb2_2015-10-08_172719
LDAD-GRIB-WPCClimoPoP_20151002_0000__20151009_1200.grb2_2015-10-02_052738

Since there are four different types of ClimoPop grids, they can be archived either separately or together; both strategies are shown below:

Separate Entries:

RAW_DATA.xml

<dataSet>
     <dirPattern>(manual)/grib/\d{4}\d{4}/\d{2}</dirPattern>
     <filePattern>.*(MAVClimoPoP)_(\d{4})(\d{2})(\d{2})_(\d{2}).*</filePattern>
     <timeType>Date</timeType>
     <displayLabel>{1}-MAVClimoPoP</displayLabel>
     <dateGroupIndices>3,4,5,6</dateGroupIndices>
</dataSet>

<dataSet>
     <dirPattern>(manual)/grib/\d{4}\d{4}/\d{2}</dirPattern>
     <filePattern>.*(METClimoPoP)_(\d{4})(\d{2})(\d{2})_(\d{2}).*</filePattern>
     <timeType>Date</timeType>
     <displayLabel>{1}-METClimoPoP</displayLabel>
     <dateGroupIndices>3,4,5,6</dateGroupIndices>
</dataSet>

<dataSet>
     <dirPattern>(manual)/grib/\d{4}\d{4}/\d{2}</dirPattern>
     <filePattern>.*(MEXClimoPoP)_(\d{4})(\d{2})(\d{2})_(\d{2}).*</filePattern>
     <timeType>Date</timeType>
     <displayLabel>{1}-MEXClimoPoP</displayLabel>
     <dateGroupIndices>3,4,5,6</dateGroupIndices>
</dataSet>

<dataSet>
     <dirPattern>(manual)/grib/\d{4}\d{4}/\d{2}</dirPattern>
     <filePattern>.*(WPCClimoPoP)_(\d{4})(\d{2})(\d{2})_(\d{2}).*</filePattern>
     <timeType>Date</timeType>
     <displayLabel>{1}-WPCClimoPoP</displayLabel>
     <dateGroupIndices>3,4,5,6</dateGroupIndices>
</dataSet>

Combined Entry:

RAW_DATA.xml

<dataSet>
     <dirPattern>(manual)/grib/\d{4}\d{4}/\d{2}</dirPattern>
     <filePattern>.*(ClimoPoP)_(\d{4})(\d{2})(\d{2})_(\d{2}).*</filePattern>
     <timeType>Date</timeType>
     <displayLabel>{1}-ClimoPoP</displayLabel>
     <dateGroupIndices>3,4,5,6</dateGroupIndices>
</dataSet>

ECMWF MOS Text

Extended ETA or NAM (66-84 hours)

This data consists of ETA grids beyond those that are normally distributed over the SBN. In AWIPS-2, the raw data will be found in /data_store/manual/grib/YYYYMMDD/HH. The processed data is stored with the normal ETA model (e.g., /awips2/edex/data/hdf5/grid/ETA218 or /archive/grid/ETA218). For raw data, several different filename conventions have been observed, depending on local LDAD configurations.

Sample Filename: 2015082418.ExtEtaF18.1440447412. The distinguishing characteristic in the filename is ExtEtaF##.

RAW_DATA.xml

<dataSet>
    <dirPattern>(manual)/grib/\d{8}/\d{2}</dirPattern>
    <filePattern>(\d{4})(\d{2})(\d{2})(\d{2}).ExtEtaF(\d{2}).*</filePattern>
    <timeType>Date</timeType>
    <displayLabel>{1}-Extended NAM</displayLabel>
    <dateGroupIndices>2,3,4,5</dateGroupIndices>
</dataSet>

Sample Filename: LDAD-GRIB-2015082206.GribF66_2015-08-22_084555. The distinguishing characteristic in the filename is GribF##.

RAW_DATA.xml

<dataSet>
    <dirPattern>(manual)/grib/\d{8}/\d{2}</dirPattern>
    <filePattern>.*(\d{4})(\d{2})(\d{2})(\d{2}).GribF(\d{2}).*</filePattern>
    <timeType>Date</timeType>
    <displayLabel>{1}-Extended NAM</displayLabel>
    <dateGroupIndices>2,3,4,5</dateGroupIndices>
</dataSet>

Sample Filename: namA280.2016053112.F66.Grb2.1464706237.

RAW_DATA.xml

<dataSet>
    <dirPattern>(manual)/grib/\d{8}/\d{2}</dirPattern>
    <filePattern>namA280.*(\d{4})(\d{2})(\d{2})(\d{2}).F(\d{2}).*</filePattern>
    <timeType>Date</timeType>
    <displayLabel>{1}-Extended NAM 66-84 hr</displayLabel>
    <dateGroupIndices>2,3,4,5</dateGroupIndices>
</dataSet>

GFS Simulated Satellite

GOES-16 Raw Data

hpcqpf

HPCWWD (HPC Winter Weather Desk)

HREF

HRRR (CR/GSD version)

LDAD.mesonet and LDAD.hydro (/data_store/ldad)

Lightning Mapper Array (LMA)

Local METARs

This raw data is found in /data_store/manual/obs/YYYYMMDD/HH/, where YYYYMMDD/HH is the time the data were received and processed by AWIPS-2. The processed versions are found with all other METAR data in /awips2/edex/data/hdf5/obs or /archive/grid/obs.

Sample Filename: /data_store/manual/obs/YYYYMMDD/HH/SAUS80KWBC.022055.GTFMTR1S3

Because the filename does not contain a full date/time specification, it is necessary to use the date/time from the directory (which represents the receipt time and not the valid time of the data).

RAW_DATA.xml

<dataSet>
    <dirPattern>(manual)/obs/(\d{4})(\d{2})(\d{2})/(\d{2})</dirPattern>
    <timeType>Date</timeType>
    <displayLabel>{1}-Local Obs</displayLabel>
    <dateGroupIndices>2,3,4,5</dateGroupIndices>
</dataSet>

Sample Filename:SAUS70_KGID_240211_440382479.2015082402_2015-08-24_021503

RAW_DATA.xml

<dataSet>
     <dirPattern>(manual)/obs/\d{8}/\d{2}</dirPattern>
     <filePattern>.*(SAUS70).*(\d{4})(\d{2})(\d{2})(\d{2})_.*</filePattern>
     <timeType>Date</timeType>
     <displayLabel>{1}-Local METARs</displayLabel>
     <dateGroupIndices>3,4,5,6</dateGroupIndices>
</dataSet>

Sample Filename:SAUS44KWBC_KDWU.dat.1462072462

In this situation, we need to use the last ten digits as the Epoch seconds.

RAW_DATA.xml

<dataSet>
     <dirPattern>(manual)/obs/\d{8}/\d{2}</dirPattern>
     <filePattern>(SAUS).*(\d{10})</filePattern>
     <timeType>EpochSec</timeType>
     <displayLabel>{1}-Local METARs</displayLabel>
     <dateGroupIndices>3</dateGroupIndices>
</dataSet>

Sample Filename:/data_store/manual/obs/20160531/00/SWRALBMTRABG.dat.1464656042.310054

Here the date/time from the directory apparently matches the date/time from the filename (310004).

RAW_DATA.xml

<dataSet>
     <dirPattern>(manual)/obs/(\d{4})(\d{2})(\d{2})/(\d{2})</dirPattern>
     <filePattern>SWR.*dat.*.(\d{10}).*</filePattern>
     <timeType>Date</timeType>
     <displayLabel>{1}-Various Local Surface Obs</displayLabel>
     <dateGroupIndices>2,3,4,5</dateGroupIndices>
</dataSet>

Local WRF

Local WRF models typically have their raw data located in /data_store/manual/grib/YYYYMMDD/HH. Exact filenames differ depending on local configurations. The processed data also are in /awips2/edex/data/hdf5/grid and /archive/grid, but the exact names typically differ at each WFO. A number of examples follow.

All of these examples do not have the full year specified in the filename, so we have to get the year from the directory (YYYYMMDD/HH).

Sample Filename: LDAD-GRIB-1509301200_arw_d03.grb2f530000_2015-90-30_165747

RAW_DATA.xml

<dataSet>
     <dirPattern>(manual)/grib/(\d{4})\d{2}\d{2}/\d{2}</dirPattern>
     <filePattern>LDAD-GRIB-(\d{2})(\d{2})(\d{2})(\d{2}).*(arw_d03).*</filePattern>
     <timeType>Date</timeType>
     <displayLabel>{1}-ARW8KM</displayLabel>
     <dateGroupIndices>2,4,5,6</dateGroupIndices>
</dataSet>

Sample Filename: 1509071200_arw_d01.Grb2LDAD-GRIBf010000.1441655188

RAW_DATA.xml

<dataSet>
     <dirPattern>(manual)/grib/(\d{4})\d{4}/\d{2}</dirPattern>
     <filePattern>\d{2}(\d{2})(\d{2})(\d{2})(\d{2})_arw.*.Grb.*</filePattern>
     <timeType>Date</timeType>
     <displayLabel>{1}-Local WRF Model</displayLabel>
     <dateGroupIndices>2,3,4,5</dateGroupIndices>
</dataSet>

Sometimes a WFO runs the WRF at different resolutions. In this case, the arw_d01 and arw_d02 files are different resolutions. They can be archived either separately or together as shown below:

Sample Filenames:

LDAD-GRIB-MTRWRF-15101512_arw_d01.grbF0410000.1444934189
LDAD-GRIB-MTRWRF-15101512_arw_d02.grbF0410000.1444933869

Combined Entry:

RAW_DATA.xml

<dataSet>
     <dirPattern>(manual)/grib/(\d{4})\d{4}/\d{2}</dirPattern>
     <filePattern>.*\d{2}(\d{2})(\d{2})(\d{2})_arw.*.grb.*</filePattern>
     <timeType>Date</timeType>
     <displayLabel>{1}-Local WRF Model</displayLabel>
     <dateGroupIndices>2,3,4,5</dateGroupIndices>
</dataSet>

Separate Entries:

RAW_DATA.xml

<dataSet>
     <dirPattern>(manual)/grib/(\d{4})\d{4}/\d{2}</dirPattern>
     <filePattern>.*\d{2}(\d{2})(\d{2})(\d{2})_arw_d01.*.grb.*</filePattern>
     <timeType>Date</timeType>
     <displayLabel>{1}-Local WRF Model</displayLabel>
     <dateGroupIndices>2,3,4,5</dateGroupIndices>
</dataSet>

<dataSet>
     <dirPattern>(manual)/grib/(\d{4})\d{4}/\d{2}</dirPattern>
     <filePattern>.*\d{2}(\d{2})(\d{2})(\d{2})_arw_d02.*.grb.*</filePattern>
     <timeType>Date</timeType>
     <displayLabel>{1}-Local WRF Model (1km)</displayLabel>
     <dateGroupIndices>2,3,4,5</dateGroupIndices>
</dataSet>

mPING (Meteorological Phenomena Identification Near the Ground)

NAM CONUS Nest

NAM Simulated Satellite

NARRE (North America Rapid Refresh Ensemble)

NBM (National Blend of Models)

NCAR 3km ensembles

NWPS (Nearshore Wave Prediction System)

NSSL WRF

nucaps

ProbSevere (convectprob)

RegionalSat

This raw data is stored under /data_store/manual/regionalsat/YYYYMMDD/HH. The processed data is stored alongside the regular satellite data in /awips2/edex/data/hdf5/satellite/ in directories named like centralRegionEast, centralRegionWest, goesEast, goesWest, conus, eastConus, goesEast, goesWest, westConus, etc.

Depending on local LDAD configurations and the source of the data, slightly different filenames have been observed.

Sample Filename: LDAD-REGIONALSAT-20150824_1815_sport_econus_uahci.nc_2015-08-24_182943

RAW_DATA.xml

<dataSet>
     <dirPattern>(manual)/regionalsat/\d{8}/\d{2}</dirPattern>
     <filePattern>.*(\d{4})(\d{2})(\d{2})_(\d{2}).*(sport).*</filePattern>
     <timeType>Date</timeType>
     <displayLabel>{1}-Regional Sat (SPoRT)</displayLabel>
     <dateGroupIndices>2,3,4,5</dateGroupIndices>
</dataSet>

Sample Filename: 20151002_1625_sport_econus_uahci.nc

(Note: The above RAW_DATA.xml also works for this sample file as well as the one below. The above example works because the leading .* means to capture zero or more characters before before the specified digits (the eight digits, underscore, and two digits).

RAW_DATA.xml

<dataSet>
     <dirPattern>(manual)/regionalsat/\d{8}/\d{2}</dirPattern>
     <filePattern>(\d{4})(\d{2})(\d{2})_(\d{2}).*(sport).*</filePattern>
     <timeType>Date</timeType>
     <displayLabel>{1}-Regional Sat (SPoRT)</displayLabel>
     <dateGroupIndices>2,3,4,5</dateGroupIndices>
</dataSet>

Sample Filename:
GOESR-PG_SSEC_AWIPS_GEOCAT-GEOW_CONUS_4KM_FOGDEPTH_20151009_2230.55779861.1444430872

RAW_DATA.xml

<dataSet>
     <dirPattern>(manual)/regionalsat/\d{8}/\d{2}</dirPattern>
     <filePattern>(GOESR-PG_SSEC).*(\d{4})(\d{2})(\d{2})_(\d{2}).*</filePattern>
     <timeType>Date</timeType>
     <displayLabel>{1}-Regional Sat (GOESR-PG SSEC)</displayLabel>
     <dateGroupIndices>3,4,5,6</dateGroupIndices>
</dataSet>

Sample Filename: 20151009_1645_sportA2_nesdis_conusa_qpe000hr

RAW_DATA.xml

Note: this entry is identical to the one used for the uahci.nc file above.

WFOs typically ingest multiple satellite products, and it is possible to archive them separately, as shown here:

Sample Filenames:

20151002_1519_sport_modis_sre_12.0um
20151002_1601_sport_goesSndr_conus_airmass

RAW_DATA.xml

<dataSet>
<dirPattern>(manual)/regionalsat/\d{8}/\d{2}</dirPattern>
     <filePattern>(\d{4})(\d{2})(\d{2})_(\d{2}).*(sport_modis).*</filePattern>
     <timeType>Date</timeType>
     <displayLabel>{1}-Regional Sat (SPoRT) MODIS</displayLabel>
     <dateGroupIndices>2,3,4,5</dateGroupIndices>
</dataSet>
<dataSet>
     <dirPattern>(manual)/regionalsat/\d{8}/\d{2}</dirPattern>
     <filePattern>(\d{4})(\d{2})(\d{2})_(\d{2}).*(sport_goesSndr).*</filePattern>
     <timeType>Date</timeType>
     <displayLabel>{1}-Regional Sat (SPoRT) GOES SOUNDER</displayLabel>
     <dateGroupIndices>2,3,4,5</dateGroupIndices>
</dataSet>

Sample Filename: satxgoesvsfg_20150824_2030.nc

RAW_DATA.xml

<dataSet>
     <dirPattern>(manual)/regionalsat/\d{8}/\d{2}</dirPattern>
     <filePattern>.*(satx).*_(\d{4})(\d{2})(\d{2})_(\d{2}).*</filePattern>
     <timeType>Date</timeType>
     <displayLabel>{1}-Regional Sat</displayLabel>
     <dateGroupIndices>3,4,5,6</dateGroupIndices>
</dataSet>

satellite.mcidas

sportlis (SPoRT Land Information System)

SPoRT SST

Various Products in /data_store/manual/text

text_decrypted (Watch County List or WCL)

unknown (/data_store/manual/unknown)

Processed Data

FFMP (Flash Flood Monitoring and Prediction)

mPING (Meteorological Phenomena Identification Near the Ground)

nucaps

ProbSevere (convectprob)

Spot Forecast Requests (STQ)

LDM pqact.conf configurations

CADAS and/or HADS SHEF data

/data_store/firewx directory

Local addition for GLERL

Two-digit directories in /data_store/shef

The symptom of this problem is two-digit directories (typically representing HH) in /data_store/shef that are alongside proper 8-digit directories that represent YYYYMMDD, as shown below:

dx2-xxx$ cd /data_store/shef
dx2-xxx$ ls
00 02 04 06 08 10 12 14 16 18 20 20151103 20151105 20151107 20151109 22
01 03 05 07 09 11 13 15 17 19 20151102 20151104 20151106 20151108 21 23

The two-digit directories result from entries in LDM's pqact.conf file that do not match the storage paradigm used throughout AWIPS-2 and expected by the archiver.

Example 1:

Here are some sample incorrect pqact.conf entries followed by corrected versions.

IDS|DDPLUS      ^(SXUS53) (KWOH) (..)(..)(..)
     FILE     -overwrite -log -close -edex     /data_store/shef/\4/\1_\2_\3\4\5_(seq).txt
IDS|DDPLUS     ^(SXUS58) (KWOH) (..)(..)(..)
     FILE     -overwrite -log -close -edex     /data_store/shef/\4/\1_\2_\3\4\5_(seq).txt
IDS|DDPLUS     ^(SXUS59) (KWOH) (..)(..)(..)
     FILE     -overwrite -log -close -edex     /data_store/shef/\4/\1_\2_\3\4\5_(seq).txt
IDS|DDPLUS     ^(SXUS60) (KWOH) (..)(..)(..)
     FILE     -overwrite -log -close -edex     /data_store/shef/\4/\1_\2_\3\4\5_(seq).txt
IDS|DDPLUS     ^(SXUS56) (KSCS) (..)(..)(..)
     FILE     -overwrite -log -close -edex     /data_store/shef/\4/\1_\2_\3\4\5_(seq).txt
IDS|DDPLUS     ^(CXUS86) (KSCS) (..)(..)(..)
     FILE     -overwrite -log -close -edex     /data_store/shef/\4/\1_\2_\3\4\5_(seq).txt

In the above sample, the highlighted \4 expressions are responsible for creating the directory that is locatedd just under /data_store/shef. The \4 means to take the fourth regular expression group that was defined using the WMO header. So if a sample WMO header was SXUS53 KWOH 091200 then the 4th regular expression group in this sample would be 12. The solution is to insert the YYYYMMDD expression in the FILE entries just before this \4 as shown here:

IDS|DDPLUS     ^(SXUS53) (KWOH) (..)(..)(..)
      FILE     -overwrite -log -close -edex     /data_store/text/(\3:yyyy)(\3:mm)\3/\4/\1_\2_\3\4\5_(seq).%Y%m%d%H
IDS|DDPLUS     ^(SXUS58) (KWOH) (..)(..)(..)
      FILE     -overwrite -log -close -edex     /data_store/text/(\3:yyyy)(\3:mm)\3/\4/\1_\2_\3\4\5_(seq).%Y%m%d%H
IDS|DDPLUS     ^(SXUS59) (KWOH) (..)(..)(..)
      FILE     -overwrite -log -close -edex     /data_store/text/(\3:yyyy)(\3:mm)\3/\4/\1_\2_\3\4\5_(seq).%Y%m%d%H
IDS|DDPLUS     ^(SXUS60) (KWOH) (..)(..)(..)
      FILE     -overwrite -log -close -edex     /data_store/text/(\3:yyyy)(\3:mm)\3/\4/\1_\2_\3\4\5_(seq).%Y%m%d%H
IDS|DDPLUS     ^(SXUS56) (KSCS) (..)(..)(..)
      FILE     -overwrite -log -close -edex     /data_store/text/(\3:yyyy)(\3:mm)\3/\4/\1_\2_\3\4\5_(seq).%Y%m%d%H
IDS|DDPLUS     ^(CXUS86) (KSCS) (..)(..)(..)
      FILE     -overwrite -log -close -edex     /data_store/text/(\3:yyyy)(\3:mm)\3/\4/\1_\2_\3\4\5_(seq).%Y%m%d%H

Example 2:

This WFO has two-digit directories as well (the \2 expression below creates the two-digit directory).

pqact.conf.XXX

IDS|DDPLUS      ^SXUS52 KWBC (..)(..)(..)
      FILE    -overwrite -close -edex /data_store/shef/\2/SXUS52_KWBC_\1\2\3_(seq).txt
IDS|DDPLUS     ^SXUS54 KORN (..)(..)(..)
      FILE    -overwrite -close -edex /data_store/shef/\2/SXUS54_KORN_\1\2\3_(seq).txt
IDS|DDPLUS     ^SEXX60 PAAQ (..)(..)(..)
      FILE    -overwrite -close -edex /data_store/text/\2/SEXX60_PAAQ_\1\2\3_(seq).txt

replacement lines for pqact.conf.XXX

IDS|DDPLUS      ^(SXUS52) (KWBC) (..)(..)(..)
      FILE     -overwrite -close -edex /data_store/shef/(\3:yyyy)(\3:mm)\3/\4/\1_\2_\3\4\5_(seq).%Y%m%d%H
IDS|DDPLUS     ^(SXUS54) (KORN) (..)(..)(..)
      FILE     -overwrite -close -edex /data_store/shef/(\3:yyyy)(\3:mm)\3/\4/\1_\2_\3\4\5_(seq).%Y%m%d%H
IDS|DDPLUS     ^(SEXX60) (PAAQ) (..)(..)(..)
      FILE     -overwrite -close -edex /data_store/shef/(\3:yyyy)(\3:mm)\3/\4/\1_\2_\3\4\5_(seq).%Y%m%d%H

Follow WDTD on Facebook