IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

Changeman Audit failure for a package with RC=12


IBM Mainframe Forums -> COBOL Programming
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
uma servepalli

New User


Joined: 13 Feb 2007
Posts: 4
Location: kolkata

PostPosted: Fri Jun 08, 2007 4:31 pm
Reply with quote

Hi,

Audit for a package in Changeman failed with RC=12. Below is the screen shot:

PARTICIPATING PACKAGE FAILED THE AUDIT WITH A RETURN CODE
RC = 12

So, can any one tell me what the problem might be and how it can be solved.


Thanks,
Uma
Back to top
View user's profile Send private message
uma servepalli

New User


Joined: 13 Feb 2007
Posts: 4
Location: kolkata

PostPosted: Fri Jun 08, 2007 4:40 pm
Reply with quote

Hi,

One more thing is, for one of the components of this package its giving SYNCH4!

And hence the AUDIT is failing.

Thanks,
Uma
Back to top
View user's profile Send private message
Anuj Dhawan

Superior Member


Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India

PostPosted: Fri Jun 08, 2007 5:09 pm
Reply with quote

Uma,

In the SYSOUT of Audit JOB search for DD name SYSUT2, select this.
In this search for SYNC or 'Legend and Summary Report', you'll get a listing such as:

Code:
DUPLIC! (Staging duplicates baseline)      ===> 0
SYNCH0! (Not in scope of audit or unknown) ===> 4
SYNCH1! (ISPF statistics not available)    ===> 0
SYNCH2! (Compile/designated proc differ)   ===> 0
SYNCH3! (Unparsable load module)           ===> 0



Right side of above gives the RC for different sunch check done by audit. Here you need to find what caused the RC of 12.

Start with this & please let us know your findings. icon_smile.gif
Back to top
View user's profile Send private message
Anuj Dhawan

Superior Member


Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India

PostPosted: Fri Jun 08, 2007 6:17 pm
Reply with quote

Dang..! My reply came bit late.

By the way, what's the explanation/summary there for SYNCH4! ?
as in previous post by me, explanation for SYNCH0! is as:
Code:
SYNCH0! (Not in scope of audit or unknown) ===> 4
Back to top
View user's profile Send private message
uma servepalli

New User


Joined: 13 Feb 2007
Posts: 4
Location: kolkata

PostPosted: Sat Jun 09, 2007 8:39 am
Reply with quote

Hi Anuj,

Thanks for replying. I have checked for the explantion summary and following is the screen shot,

Code:
DUPLIC! (Staging duplicates baseline)      ===> 10
SYNCH0! (Unknown to Change Man)            ===> 98
SYNCH1! (ISPF statistics not available)    ===> 0
SYNCH2! (Compile/designated proc differ)   ===> 0
SYNCH3! (Unparsable load module)           ===> 0
SYNCH4! (CPY problem in staging)           ===> 1
SYNCH5! (CPY high-date problem in baseline)===> 1


Can u please tell me what the problem might me.

Thanks,
Back to top
View user's profile Send private message
senapa

New User


Joined: 29 May 2007
Posts: 1
Location: Bangalore

PostPosted: Sat Jun 09, 2007 9:44 am
Reply with quote

One of your component is having a name which is already existing in production. That component must have given error/warning while staging.Change that component name and Audit will be a success.
Back to top
View user's profile Send private message
uma servepalli

New User


Joined: 13 Feb 2007
Posts: 4
Location: kolkata

PostPosted: Mon Jun 11, 2007 3:24 pm
Reply with quote

Hi Senapa,

The problem is coming for a component that is already existing in production.

Actually this component was checked out from production and then staged after making some changes. So this component can't be renamed.

Also staging was successful without any warnings.

so,please suggest if there is any other way to solve this problem.

Thank u.
Back to top
View user's profile Send private message
Anuj Dhawan

Superior Member


Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India

PostPosted: Mon Jun 11, 2007 8:09 pm
Reply with quote

Uma,

Code:
DUPLIC! (Staging duplicates baseline)      ===> 10

For this, do the following-
1. Take the back-up of your staged component in your personal PDS.
2. Delete this component from the package.
3. Checkout the component again & paste the code from your back-up.
4. Stage the component again.
Here make sure that your component contains all the changes done by other teams as well. I hope you have done retrofitting before auditing your package.
Code:
SYNCH0! (Unknown to Change Man)            ===> 98

Just now, not getting wat to do for this. Actually, RC for audit should not exceed 8. Just for now, try to implement other suggestions.
Code:
SYNCH4! (CPY problem in staging)           ===> 1

Do the same as above
Code:
SYNCH5! (CPY high-date problem in baseline)===> 1

Do the same as above.

Perform audit again & let us know the results. icon_smile.gif
Back to top
View user's profile Send private message
kothai

New User


Joined: 01 Sep 2008
Posts: 32
Location: chennaii

PostPosted: Sat Dec 06, 2008 4:37 pm
Reply with quote

Hi Uma,,

Did u find y the audit of the package is 12 when SYNC! = 4..
If so please let me know.. me facing the same issue :-(
Back to top
View user's profile Send private message
Anuj Dhawan

Superior Member


Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India

PostPosted: Sat Dec 06, 2008 4:44 pm
Reply with quote

Hi,

In the SYSOUT of Audit JOB search for DD name SYSUT2, select this, in this search for SYNC or 'Legend and Summary Report' and post the listing.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> COBOL Programming

 


Similar Topics
Topic Forum Replies
No new posts Changeman - how can we know the curr... Compuware & Other Tools 2
No new posts how to solve this power failure shutd... ABENDS & Debugging 5
No new posts Rebind issue - Package DB2 2
No new posts IMS Restart Failure IMS DB/DC 4
No new posts Auto ticketing of a job failure ABENDS & Debugging 1
Search our Forums:

Back to Top