When you expand the contents of a library that is allocated with SAS/SHARE, it might require more than two minutes to load. This problem occurs when the library contains more than 100,000 members. This problem might impact the migration process when you use SAS^® Explorer.

The increased time is caused by the remote engine that is used by SAS/SHARE. This engine attempts to read the details of each data set, even though this information is not required. Prior to SAS^® 9.3, the SAS/SHARE server only returned member names when asked for the contents of a library. In SAS 9.3, the server also began including file details for each member, such as the last date modified. Retrieving and returning the additional information impacts the performance in a way that becomes more noticeable as the number of members in the library increases. 

If you prefer the performance available prior to SAS 9.3 and are not interested in the additional details for each member, install the hot fix in this note. This hot fix reverts to the behavior prior to SAS 9.3 when an undocumented macro variable is set on the client as follows:

This hot fix is required on both the client and server.

As a best practice, you should limit the number of members contained in any given library. Even in Base SAS^®, numerous operations on a library can have an undesirable performance impact when the library contains thousands of members.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for this issue for Base SAS 9.4_M6 is available at:

A fix for this issue for Base SAS 9.4_M5 is available at: