Hi,
I talked to the devlopers today, and they said that they did not actually
see a RC of 3, they just looked at the code and assumed that it had to be
a 3. We have a program that restores data to a pack. It issues a DIAG
A8, and then checks the codes. The code was setup in the past for a DIAG
20, and so had code that if a DASD error occurred on the write operation,
it would ignore a RC of 3.
We had an issue with FICON cards on the processor, and on a DASD unit
during the restore. The hardware was causing paths to come and go during
the restore. When the restore had finished, they found 6 packs that had
incorrectly restored tracks. They looked at the code, and determined that
the most likely way that could happen was if a RC of 3 was returned by the
DIAG A8. If there is now way for a DIAG A8 to have a RC 3, then it may
have occurred anothey way.
Here is the code segment:
* DC X'831E0020' DIAGNOSE CODE 20 --GENERAL I/O *VM* *SOB1067
DC X'831000A8' DIAGNOSE CODE A8 --GENERAL I/O *SOB1067
BNZ ERROR1 NON-ZERO CC = ERROR *VM*
MVI ECB,X'7F' ZERO R/C = OK *VM*
* FREEMAIN EU,LV=88,A=HCPSTR C6 *SOB1067
BR 10 *VM*
ERROR1 EQU * *VM*
CH R15,=H'3' RC OTHER THAN 3 = PERM I/O ERROR *VM*
BNE ERROR2 GO SEARCH FOR OTHER ERRORS *VM*
MVI ECB,X'41' MAKE ECB OK FOR VM *VM*
MVC IOB+12(2),=X'0C40' IOB OK FOR VM *VM*
BR R10 *VM*
ERROR2 EQU * *VM*
CH R15,=H'1' DEVICE ATTACHED? *VM*
BE ERR02 NO-PUT MSG OUT AND END *VM*
CH R15,=H'2' UNIT EXCEPTION ERROR? *VM*
BE ERR07 YES-PUT MSG OUT AND END *VM*
CH R15,=H'5' VIRTUAL DEV BUSY OR INTERRUPT? *VM*
BE ERR12 YES-PUT MSG OUT AND END *VM*
CH R15,=H'13' PERM I/O ERROR? *VM*
BE ERR13A YES-PUT MSG OUT AND END *CH*VM*
ABEND 2,DUMP,STEP *VM*
Here is a partial list of the errors messages occurring at the time:
15:07:40 OPERATOR *3 HCPCIO2263I Path AE to device B227 is available and
15:07:42 OPERATOR *3 HCPCIO2263I Path AA to device B227 is available and
15:07:43 OPERATOR *3 HCPCIO2263I Path AC to device B227 is available and
15:09:01 OPERATOR *3 HCPDPM1283I Path AA to device B227 currently not res
15:09:01 OPERATOR *3 HCPDPM1283I Path AC to device B227 currently not res
15:09:01 OPERATOR *3 HCPDPM1283I Path AE to device B227 currently not res
16:11:17 OPERATOR *3 HCPCIO2263I Path AE to device B227 is available and
16:11:49 OPERATOR *3 HCPCIO2263I Path AC to device B227 is available and
16:12:32 OPERATOR *3 HCPCIO2263I Path AA to device B227 is available and
16:25:11 OPERATOR *3 HCPDPM1283I Path AA to device B227 currently not res
16:25:11 OPERATOR *3 HCPDPM1283I Path AC to device B227 currently not res
16:25:11 OPERATOR *3 HCPDPM1283I Path AE to device B227 currently not res
16:26:43 OPERATOR *3 HCPCIO2263I Path AA to device B227 is available and
16:26:43 OPERATOR *3 HCPCIO2263I Path AC to device B227 is available and
16:26:44 OPERATOR *3 HCPCIO2263I Path AE to device B227 is available and
16:27:51 OPRVM2 12 Path A8 offline to devices B225 B226 B227 B228 B229
16:28:39 OPERATOR *3 HCPDPM1283I Path AA to device B227 currently not res
16:28:39 OPERATOR *3 HCPDPM1283I Path AC to device B227 currently not res
16:28:39 OPERATOR *3 HCPDPM1283I Path AE to device B227 currently not res
16:30:17 OPERATOR *3 HCPCIO2263I Path AA to device B227 is available and
16:30:17 OPERATOR *3 HCPCIO2263I Path AC to device B227 is available and
16:30:18 OPERATOR *3 HCPCIO2263I Path AE to device B227 is available and
16:30:28 OPERATOR *3 HCPDPM1283I Path AA to device B227 currently not res
They have now altered the code so that the program will no longer ignore a
RC of 3.
We are now running zVM 5.2, but we are running a backlevel CMS19 on that
system. I do not know if that could cause a problem. We are rolling out
CMS22 in the systems over the next month or so.
Thanks,
Ken Vance
Amadeus
- Re: Diag A8 R15 RC of 3 Ken Vance
- Re: Diag A8 R15 RC of 3 Ken Vance
