MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » January 2002

V5R1 savsys problem.



fixed

Trying to do a SAVSYS (V5R1M0) and get the following error(s) in my joblog.




MCH5203    Escape                  60    01/18/02   16:32:09   IoDriverTape
001C44   QSRSVDEQ     QSYS         018A
                                     Message . . . . :   Condition of
source/sink object TAP01 not valid.
                                     Cause . . . . . :   The condition of
the source/sink object is not valid. The
                                       affected operation value is X'4001'
and the primary object is TAP01.   The
                                       condition is not valid for one of the
following reasons: -- Source/sink
                                       object associated with a create,
destroy, modify, or request input/output
                                       (I/O) instruction is not in the
correct condition to run this operation. --
                                       An independent ASP number was
specified for the instruction and the
                                       independent ASP is not varied on. --
A pointer to an independent ASP LUD was
                                       specified for the instruction and the
independent ASP is not varied on.

MCH1668    Escape                  40    01/18/02   16:42:09   #cfdamst
000A34   QTACLOSE     QSYS         045E
                                     Message . . . . :   System object TAP01
partially damaged. Internal dump ID .
                                       Error class 0, device number X'0000'.
                                     Cause . . . . . :   This partially
damaged system object TAP01 has an error
                                       class 0 and a device number X'0000'.
Error class indicates how damage was
                                       detected: 0000-previously marked
damage; 0001-detected abnormal condition;
                                       0002-logically invalid device sector;
0003-device error. for error class
                                       0003, the device number identifies
the failing device, or contains zero if
                                       main storage is damaged.


This is followed by a CPF8105.


I deleted the device after varying it off….did an IPL and it installed the
device again after the reboot and made sure it was “available” which it was.

Doing a CHKPRDOPT *OPSYS or CHKPRDOPT 5722SS1 (all options) shows nothing.

I have no damaged objects on the system (I checked this by doing a DSPOBJD
*ALL/*ALL  *ALL to an outfile and querying the ODOBDM field)
So unless there are objects that don’t get picked up by DSPOBJD I assume I
don’t have a bad object.

I can do a savlib <pick a library> just fine.
Also can do a SAVLIB *IBM , SAVLIB *NONSYS, SAVLIB *ALLUSR just fine.

I can do a SAVSECDTA and SAVCFG just fine.

So I don’t know what to try next…..and IBM hasn’t provided a solution yet
either.

Jim Norbut
Systems Administrator
Grubb & Ellis Company
Phone   (847) 753-7620
Fax     (847) 753-9854







Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact