SL8500 - CAP Procedure Error With ACSLS Auto CAP Mode (Doc ID 1548341.1)

Last updated on APRIL 03, 2024

Applies to:

Symptoms

CAP operation fail.

SL8500 CAP procedure error with ACSLS auto CAP mode.

Intermittent CAP ejecting failure due to CAP procedure error.

ACSLS log shows it is assuming entering cart with CAP door opened and now library is enter mode even though ejecting cart.
ACSLS log shows:
2013-01-11 23:47:00 ACSLH[0]:
2377 N Co_ProcessResponses.C 1 589
ACS: 0; LMU error: Co_4400:st_parse_error:
Request: CAP Lock
Error: 0306 - CAP procedure error: CAP door is open
2013-01-11 23:47:05 ACSLH[0]:
2377 N Co_ProcessResponses.C 1 589
ACS: 0; LMU error: Co_4400:st_parse_error:
Request: CAP Reserve
Error: 0302 - CAP procedure error: CAP is already reserved
2013-01-11 23:47:19 ACSLH[0]:
2034 N EventLog.C 1 123
ACSLH: Request Recoverer: Cap: unlock(): Acs 0 Cap Lsm: 1 CapNum: 0
Invalid Mode - 0 assuming ENTER.

ACSLS log indicated "Error: 0306 - CAP procedure error: CAP door is open" and "Invalid Mode - 0 assuming ENTER". Therefore we could consider operator error with their comments.

HBZ/HBC log show operator pressed CAP button to open CAP but ACSLS attempted to reserve CAP for EJECT before CAP was opened ,
With this behavior, ACLS assumed that operator attempted to enter....
Finally library CAP state was invalid...
(2hours and 10 minutes differed between ACSLS and Library)

2013-01-11T21:37:24.143603, cap-if, Button Press
2013-01-11T21:37:24.213498, cap, capa open move
2013-01-11T21:37:26.573 info 1.0.0.0.0 3851 "Cap reserve changed", state=reserved cap=1,0,0,-2
2013-01-11T21:37:31.106 info 1.2.15.2.0 3854 "Cap door opened", reserver=hli0 hostName=1

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.