On Fri, 7 Dec 2012 04:29:22 -0600, Boris Lenz wrote:
>Have you tried APPLY REDO?
>
Yup. Failed because of the prior RESTORE failure.
>If that doesn't work, can you post the SYSMOD entry here? You might have to
>replace that SYSMOD (i.e., remove the RESTORE entry which I assume is there)
>with UCLIN.
>
OK. It's my test CSI; expendable only at the cost of rebuilding it. So I
tried the nuclear option:
SET BOUNDARY ( target )
.
UCLIN .
DEL SYSMOD( xxxxxxx ) .
ENDUCL.
Then I edited my Link Edit JCLIN to:
NAME nnnnnnn(R) RC=16
did REJECT; RECEIVE; APPLY REDO; RESTORE. All worked. My first
foray into UCLIN other than to create CSIs.
It seems to me that it would be terribly easy to introduce inconsistencies
in a CSI with UCLIN. For example, might my DEL SYSMOD have left
dangling RMID subentries or dangling PRErequisities? Or does UCLIN
processing prevent or automatically repair those? If not, is there anything
like a CSI health checker that would report any such inconsistencies?
I assume my APPLY REDO; RESTORE has refreshed then obliterated any
subentries concerning my PTF.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
