Reusable Server Kernel

Problem 29 (Major): Storage management problem?

=============== 1999-11-16 13:39:56 (-05.00) ===============
 
Name:        ** Suppressed **
Company:     ** Suppressed **
Telephone:   ** Suppressed **
E-mail:      ** Suppressed **
 
Text:
 
I have fixed the BKWSBPSK problem.  The fix is in
/rsk/rskfix.vmarc on this web server.
 
/rsk/rskfix.vmarc replaces /rsk/bkwlib.vmarc as the
fix delivery vehicle.  rskfix.vmarc is what you get
if you take the RSKFIX package from the download
library.
 
Brian
=============== 1999-11-15 16:29:27 (-05.00) ===============
 
Name:        ** Suppressed **
Company:     ** Suppressed **
Telephone:   ** Suppressed **
E-mail:      ** Suppressed **
 
Text:
 
The BKWLIB VMARC on this web server fixes the MCR problem.
Haven't worked on the BKWSBPSK problem yet, but will soon.
Brian
=============== 1999-11-15 16:22:33 (-05.00) ===============
 
Name:        ** Suppressed **
Company:     ** Suppressed **
Telephone:   ** Suppressed **
E-mail:      ** Suppressed **
 
Text:
 
Dave,
There is a problem in BKWMCR that causes it to call
CMSSTOR RELEASE to release the storage at address
X'00000000' for a length of X'138'.  This release
is an error and I will post a new BKWLIB in a short
while.  I will update this when I have posted the
new BKWLIB.
I do not yet know what the BKWSBPSK problem is but
I will check on it next.
Brian
=============== 1999-11-14 12:04:21 (-05.00) ===============
 
Name:        ** Suppressed **
Company:     ** Suppressed **
Telephone:   ** Suppressed **
E-mail:      ** Suppressed **
 
Text:
 
We are getting DMSFFR161E (error code 6) and DMSFFR818E
error messages when attempting to release storage.
For error DMSFFR818E the subpool named is BKWSPBSK,
a RSK managed subpool. Is there a problem with RSK storage
management?