If a client using SAS^® 9.1.3 SP4 assigns a library to a SAS/SHARE^® 9.1.3 server running on the mainframe, and then the client's job or session times out with a system abend SEC6, the library might remain allocated to the server. If other jobs outside of SAS/SHARE try to update such a library, IKJ56225I messages will appear, stating that the dataset is allocated to another job or user.

In such a situation under SAS^® 8.2, the client receives a S322 abend, the library is deallocated, and updates can take place.

To circumvent this problem, use the STOP LIBRARY command to immediately terminate access to the library in question. The syntax for this command is as follows:

If there are numerous libraries that need to be deallocated, specify the _ALL_ argument. The syntax is as follows:

For more information regarding stopping a library, consult Library Management Commands: Stopping a Library

Operating System and Release Information

Product Family	Product	System	SAS Release
			Reported	Fixed*
SAS System	SAS/SHARE	z/OS	9.1 TS1M3 SP4	9.2 TS2M2

* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.

---

A fix for SAS 9.1.3 (9.1 TS1M3) for this issue is available at:

http://www.sas.com/techsup/download/hotfix/e9_sbcs_prod_list.html#033892

---

A fix for SAS 9.1.3 (9.1 TS1M3) with Asian Language Support (DBCS) for this issue is available at:

http://www.sas.com/techsup/download/hotfix/e9_dbcs_prod_list.html#033892

---

If a 9.1.3 client assigns a library to a 9.1.3 SAS/SHARE® server, then times out with a SEC6 ABEND, the library will stay allocated to the server. This will cause contention for other jobs outside SAS/SHARE trying to update that library.

Type:	Problem Note
Priority:	medium

Date Modified:	2008-11-25 12:37:24
Date Created:	2008-11-11 21:46:00