MVSFORUMS.com

karthikeyan · Posted: Fri Feb 10, 2006 10:33 pm Post subject: Changeman Audit Error

Hi all
Regarding to Changeman tool.
Am facing an audit Error when am promoting my Package in the Changeman.I have given a full promotion of my package from the Level 0 to another Level 15.There was an return code of 12 saying an error in audit.But the package loadlibs are been copied to the 15 level loadlib pds so am able to test with that loadlib.But our client is saying they will face problem when they are moving the package to production if theres an audit error in promotion.
Do anyone have come across this Audit Error in changeman?If so please let me know the reasons for this Audit Error
Thanks
Karthik

kolusu · Posted: Sat Feb 11, 2006 8:48 am Post subject:

karthikeyan,

What exactly is the error message?

Kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu

German Castillo · Posted: Sun Feb 12, 2006 10:39 am Post subject:

That why Audit exists!

Go to your Audit report, browse all the way to the bottom, the you will find the cause, and probably a suggested way to overcome your error, sometimes you get something like a 'pointer' to previous pages of the same report indicating the offending member(s)
_________________
Best wishes,

German Castillo

karthikeyan · Posted: Mon Feb 13, 2006 10:54 am Post subject:

Thanks Kolusu and German for ur reply.
Am still not able to figure out.Kolusu am pasting the Error message i got

Out-of-synch messages (hint - search for "!" marks)
DUPLIC! (Staging duplicates baseline) ===> 0
SYNCH0! (Unknown to Change Man) ===> 10
SYNCH1! (ISPF statistics not available) ===> 4
SYNCH2! (Compile/designated proc differ) ===> 0
SYNCH3! (Unparsable load module) ===> 0
SYNCH4! (CPY problem in staging) ===> 0
SYNCH5! (CPY high-date problem in baseline)===> 5
SYNCH6! (Activity file not checked out) ===> 0
SYNCH7! (Called subroutine in staging) ===> 0
SYNCH8! (Called subroutine in baseline) ===> 0
SYNCH9! (Source and load discrepancy) ===> 0
SYNCH10! (Version regression problem) ===> 0
SYNCH11! (Component hash discrepancy) ===> 0
SYNCH12! (Orphan module in staging) ===> 0
SYNCH13! (Baseline/staging discrepancy) ===> 0
SYNCH14! (Components not in active status) ===> 0
SYNCH15! (Source to relationship problem) ===> 0
SYNCH16! (CPY low-date problem in baseline)===> 0
SYNCH17! (CPY deleted problem in staging) ===> 0
SYNCH18! (LOD deleted problem in staging) ===> 0

Highest return code encountered ===> 8
CMN3060A - This package has failed the audit.
CMN2684I - INSTALL DATE HAS PASSED, AUDIT RETURN CODE WILL NOT BE UPDATED.

Recommendation Summary Report
Listed below are some solutions to resolving out of synch situations
that can be flagged within this audit report.

SYNCH0! (Unknown to Change Man)
Cycle component through Change Man.
Check if component resides in another participating package excluded from audit due to install date.

SYNCH1! (ISPF statistics not available)
Create/reset statistic for component.

SYNCH5! (CPY high-date problem in baseline)
Recompile source component from baseline to include copylibs residing in the staging libraries.

CMN7540I - End of job; RC = 08

But I just went ahead with selective promotion so that it doesnt include those programs and copy books listed here still it gives me the error.

German Castillo · Posted: Mon Feb 13, 2006 4:00 pm Post subject:

The recomendations are right at the bottom.

Ussually less than 04 in the audit rc could not mean anything that stops your promotion, anyway:

Take a look at your SYNCH5... It means that the named component(search for it at the beggining of the report), probably a copy book, has a newer date in your baseline dataset. it could be either becouse of lacking of ISPF statistic or because it is indeed newer. In any case, get that component into your package and apply any modification you need. Please note that you will need to modify that component to get the proper date, a comment will do it fine. this should take care of your problem.

Furthermore take a look at your promotion date, you will need to provide a valid one, this could be done in your package listing using the option U7
_________________
Best wishes,

German Castillo

svhgk · Beginner Joined: 14 Feb 2006 Posts: 12 Topics: 5

German,

Thanks a lot for your answers. We were able to solve the SYNCH5 error. It was due to some other programs using the copybook not present in the changeman package but present in the base library. So all we needed to do was take all those programs into the package & re-compile.

BTW, I am in the same team as Karthikeyan (who posted the query).

Thanks,
Ganesh

sahulkhan · Beginner Joined: 31 Aug 2006 Posts: 1 Topics: 0

Hi All,
Good Day

I am getting a SYNCH12! (Orphan module in staging), though I deleted from the pkg and restaged, anyone can help. You solutions are appreciated

manish.rojiwadiya · Posted: Thu Oct 12, 2006 5:20 am Post subject:

Can anyone explain in which scenario SYNCH18! audit error will occur in changeman audit???
_________________
Thanks & Regards,

Manish Patel

numarsu · Beginner Joined: 13 Oct 2006 Posts: 1 Topics: 0

I got a SYNCH 12! (Orphan module in staging), and was advised to contact the Changeman Support team, who "Adopted" the Orphan module, and then the audit ran fine.