When you run a
SAS/AF
application with the AFAPPLICATION command, remember that other applications
may be running at the same time. Those other applications may try
to access the same SAS data sets or members of SAS catalogs as your
application. For example, suppose your application uses the FILLIST
function to read an SLIST catalog member. Before your application
updates the list and writes it back to the SLIST entry, another application
that has update access to the catalog can read from and write to the
same SLIST entry. This situation can create problems with data integrity.
If your application
needs to share data with another application, you should consider
-
opening your data sets with member-level
locking to prevent other applications from opening the data sets at
the same time
-
accessing your catalog and data
files through
SAS/SHARE
software so that other applications can have simultaneous update access
-
locking your catalog entries and
other SAS data files by using the SCL LOCK function.