Re: Subsystem = 111 error.....what actually is the cause ? (189 Views)
Reply
Advisor
seanharrodine
Posts: 29
Registered: ‎09-28-2006
Message 1 of 3 (189 Views)

Subsystem = 111 error.....what actually is the cause ?

Hi there,

Could anyone point me in the right direction on the fault that i am seeing please.

For a week or so, we have had a batch job failing doing a disk-to-disk backup. Here is the error....

Store is 97% complete
UNKNOWN:163:TAPEIO: Buffer allocation failed, parms=208,-18,70217
STORE :163:TAPEIO: Error allocating disk-to-disk backup block, parms=-5207,-1,4
02001
UNKNOWN:163:TAPEIO: Unexpected ESCAPE encountered, parms=-5207,-159,402015
STORE :163:TAPEIO: Error getting next disk-do-disk backup record, parms=-5207,-
12,402016
STORE :163:TAPEIO: Error when writing a block, parms=-5207,-162,402037
STORE: Write to tape set failed, parms =0,0,12152
#O1138276:(150/234) Continue?
SON PROCESS:
STORE :163:TAPEIO: Unexpected ESCAPE encountered, parms=-5207,-116,700112

Resetting store bits and compiling file statistics ...

**** PROCESS QUIT; PARAM = 200

To my knowledge, the general system performance and status is fine.

Initial thoughts were lack of space but there is more than plenty to cope. Support from Orbit have confirmed this also.

So, next i decided to check the syslogs, to find 67 "TYPE 111 (I/O ERROR) errors"

Here is an extract of one of them......

===============================================================================
FRI, MAY 20, 2011 3:55 PM LOG3725.PUB.SYS SYSTEM (PIN 188)
I/O ERROR
PRODUCT NAME: PDEV: 32
LDEV: DEVICE CLASS: 15
I/O EVENT CLASS: Software LLIO STATUS: $0000006F

MPE/XL I/O Status: Proc. Num. = 0, Error Num. = 0, Subsystem = 111

RETRY SCHEME: Summarized Retries WILL RETRY: NO
I/O RESULT: I/O Failed RUN AUTODIAG: NO
RETRY COUNT: 0 MGR PORT NUM.: $0
TRANS. NUM.: $0 # HDWR BYTES: 0
HARDWARE STATUS:

No hardware status was logged.

DATA LEN: 32 MGR CODE: 111
HLIO PROCEDURE: enable_term_signal_cLDEV NUMBER: 14
MPE XL STATUS: $FFCC0071 PROC DEPEND. PARM4: $3B
PROC DEPEND. PARM5: $2 PROC DEPEND. PARM6: $19
PROC DEPEND. PARM7: $0 PROC DEPEND. PARM8: $1
===============================================================================


Could anyone assist as to what the problem may be please as the ever reliable Google seems to be struggling.

Thanks in advance for any replies.

Sean
Please use plain text.
Trusted Contributor
donna hofmeister
Posts: 191
Registered: ‎08-29-2008
Message 2 of 3 (189 Views)

Re: Subsystem = 111 error.....what actually is the cause ?

what is ldev 14 on your system?
Please use plain text.
Respected Contributor
Stan Sieler
Posts: 321
Registered: ‎10-16-1996
Message 3 of 3 (189 Views)

Re: Subsystem = 111 error.....what actually is the cause ?

Donna...LDEV 14 is most like not configured, and is
allocate as a Virtual Terminal (based on "enable_term_signal" in the log)

Sean: contact Orbit...they should absolutely be handling
this for you. The error information at:

UNKNOWN:163:TAPEIO: Buffer allocation failed, parms=208,-18,70217
STORE :163:TAPEIO: Error allocating disk-to-disk backup block, parms=-5207,-1,4
02001
UNKNOWN:163:TAPEIO: Unexpected ESCAPE encountered, parms=-5207,-159,402015

should pinpoint the area in their code where the problem occurred. Normally, a program printing a message about an unexpected escape will display one or two numbers ... and I could map them into a somewhat informative error message. In this case, none of the three values stand out as being useful to me (hence the need for ORBiT to look at their own code). The -159 is an error (if interpreted as a VSM error) saying that a prefetch request was too large, but it's not clear if that's the correct interpretation.

Stan
Please use plain text.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation