6. Database Tailoring and Retrofitting Techniques › 6.3 Retrofitting Guidelines › 6.3.1 Correcting a File After Creation › 6.3.1.1 General Recovery Job

6.3.1.1 General Recovery Job

The general format of a data element recovery job is that of
a SAS DATA step.  The data step reads the existing file
cycle, modifies the value, and replaces the cycle with
observations that have the proper data element values.  In
SAS, the DATA step follows this template:

    DATA &diiit..iiifffnn (%fffFILE(OP=FILEOPTS,TS=ssssss));
    SET  &diiit..iiifffnn;
    (correction logic)
    RUN;

where "d" is the database unit identifier
      "iii" is the information area identifier
      "t" is the timespan identifier
      "fff" is the file identifier
      "nn" is the file cycle number
      "sssss" is the timespan name

SPECIAL NOTE:  Examples in this section are based on a
               CA MICS component called NPA, the CA MICS
               Network Performance Analysis Component.
               Though that component has been superseded
               entirely by the CA MICS SNA Network Analyzer,
               references to NPA remain in the section as an
               illustration of how such tailoring operations
               would apply to any hypothetical CA MICS
               component.

For clarity, we will return to the NPA example used thus far
in chapter 6 of this manual.  Assume that the CA MICS NPA
component has been installed in the CA MICS test database
unit whose PROC identifier is "T".  Treating a bad value in
the NPANCP01 file in the DETAIL timespan would be done by a
data step such as:

    DATA &TNPAX..NPANCP01 (%NCPFILE(OP=FILEOPTS,TS=DETAIL));
    SET  &TNPAX..NPANCP01;
    (correction logic)
    RUN;