ADRDSSU RESET with CONCURRENT

Sam_nura · New User Joined: 04 Dec 2008 Posts: 46 Location: Bangalore

During DUMP backup if we used the option RESET & CONCURRENT then RESET will be ignored. so we can do this by setting the byte at offset X'18' in ADRPATCH to a nonzero value. for this we can use the SET PATCH command or JCL . i have used the below JCL and executed fine. still i am getting the message RESET ignored in my backup joblog. can any one help me to resolve this problem.

//ZAP EXEC PGM=AMASPZAP,PARM=’IGNIDRFULL’
//SYSPRINT DD SYSOUT=*
//SYSLIB DD DISP=SHR,DSN=LIBNAME.LINKLIB
//SYSIN DD *
NAME ADRDSSU ADRPATCH
VER 18 00
REP 18 FF
/*

expat · Posted: Tue Nov 10, 2009 4:21 pm

What happens when you use SET PATCH 18 = FF in the Dfdss job

Sam_nura · New User Joined: 04 Dec 2008 Posts: 46 Location: Bangalore

Yes, thats working fine. But it will be a dynamic only right. By using the JCL only we can able to set permanently. Also in the JCL we have to specify the two values. any idea about these two values? Thanks.

VER 18 00
REP 18 FF

expat · Posted: Tue Nov 10, 2009 4:53 pm

Ok, it works within the inflight job stream, so that makes me think that the 'permanent' application has not worked.

Maybe the verify that pos X'18' = X'00' is giving a failure, so that the REP X'18' doesn't get applied.

We should really wait for a sysprog to appear. They are like busses though, wait for ages and then 3 come along at once

Sam_nura · New User Joined: 04 Dec 2008 Posts: 46 Location: Bangalore

Thanks Expat

Robert Sample · Posted: Tue Nov 10, 2009 5:39 pm

What does the ZAP output look like? And have you verified you're updating the right library? If you run the ZAP job on your test LPAR, for example, the linklib is usually on the SYSRES pack so running your test job on the production LPAR would not pick up the change -- unless you STEPLIB to the test LPAR version.