How to find out the log for failed execution in endevor

subhasis4u · New User Joined: 29 Oct 2009 Posts: 5 Location: Mumbai

Hi Everyone!!

While Migrating the component to the PROD (STAGE- 6) , the package execution failed. Please refer the attachment. How can i find the exact reason or some sort of report for the failed execution.

Please let me know.
Thanks,

expat · Posted: Thu Nov 19, 2009 5:26 pm

You could start by not using attachments as not everyone is permitted to open them

subhasis4u · New User Joined: 29 Oct 2009 Posts: 5 Location: Mumbai

Hi expat
Thanks for your suggestion !!
well i am keeping the question like this way

How can i find an error log or report in Endevor while the package execution failed at the time of migrating components to higher environment like production? Is there any option to in the Endevor menu?

Regards,[/img]

kgrimes · Posted: Thu Nov 19, 2009 10:18 pm

Hello subhasis4u,

It depends. Some package execution output is (can be) viewable in Endevor. But some output is not viewable directly in Endevor.

Most companies do not allow foreground package execution. Also, many companies have an automated process setup to execute packages such as an Endevor package sweep job that may be scheduled in your site job scheduling system (CA-7 or whatever your site uses) to run daily or even hourly. Just guessing from the screen shot included in your attachment, it looks like your site may have such an Endevor package sweep batch job named SNDSWEE. Check the SDSF output que or output archival system for the output. If this is indeed an Endevor package sweep, then many Endevor packages might be executed in the same batch job depending on how the sweep job is setup.

Maybe another easier way to find the output is to ask your Endevor Administrator where to find the output.

Best Wishes,
Kevin Grimes

dbzTHEdinosauer · Posted: Thu Nov 19, 2009 10:58 pm

What?
Ask somebody at their site about something that is site specific?
What a novel idea.

expat · Posted: Fri Nov 20, 2009 5:23 pm

subhasis4u · New User Joined: 29 Oct 2009 Posts: 5 Location: Mumbai

@kgrimes
Thanks Kevin for your reply. i will try to find out the sweep job.

@expat

sorry i am realy not getting you ---- i joined for the first time and i put a question with attachment to the forum which i need to know urgently. would you just explain what kind of help from my seed is expected ? if the attchment is not opening properly i will send the image.

waiting for tour suggestion

regards

enrico-sorichetti · Posted: Fri Nov 20, 2009 6:54 pm

Anuj Dhawan · Posted: Fri Nov 20, 2009 8:00 pm

Best approach is to get in touch with your Change management group there at your site as Dick has suggested.

dbzTHEdinosauer · Posted: Fri Nov 20, 2009 8:11 pm

actually Kevin Grimes suggested that, about 30 posts ago.

I just chimed in with my usual sarcasm.

kgrimes · Posted: Fri Nov 20, 2009 8:48 pm

Actually, all Endevor "E" level errors produce a return code 12. So the Endevor documentation (Error codes and messages) would be of no value without the Endevor output that contains the Endevor error message number to lookup. The screen shot in the attachment does not give all the needed information, but it does tell you the userid who executed the package (SNDSWEE) along with the date and time that the package was executed. So you could look for the Endevor output in the SDSF output queue by filtering the OWNER SNDSWEE. Of course I can't know for certain without more information, but just from looking at the userid this looks like it could stand for Endevor (ND) Sweep (SWEE) - but not sure what the leading S would stand for, maybe a system identifier, a life cycle stage, or something like that.

The real problem is that some developers and support staff are put into a situation where they must use an unfamiliar set of tools and systems without proper training. If it's an outsource situation (very likely), then they my not want to admit that they don't know what they are doing by having to ask the client's technical support staff for help. I guess this is what we get when executive management chooses to outsource work to the lowest bidder who is often unqualified to perform the service.

Regards,
Kevin