Page 1 of 1

Endevor MOVSCL

PostPosted: Mon Feb 27, 2012 12:37 pm
by Briannnnn
When move program from stage A to stage B in Endevor, i found that some programs were compiled and some were not.
Coz in the FOOTPRINT of stage B, some programs shows "COMPILE....... RC=0000", some shows "NOCOMPILE(S)".
Can anyone tell me why this happened?

Thanks.

Re: Endevor MOVSCL

PostPosted: Mon Feb 27, 2012 5:50 pm
by Robert Sample
Because that's the way your site set it up. Your question is one of those in the category "can only be answered by someone working at your site" -- so asking on this forum is a waste of time; it is very unlikely that anybody here works at your site and would know how / why your Endevor was set up the way it is.

Re: Endevor MOVSCL

PostPosted: Tue Feb 28, 2012 7:44 pm
by Briannnnn
Robert Sample wrote:Because that's the way your site set it up. Your question is one of those in the category "can only be answered by someone working at your site" -- so asking on this forum is a waste of time; it is very unlikely that anybody here works at your site and would know how / why your Endevor was set up the way it is.


So...this is due to Endevor setup by site admin, but not the common Endevor setup. i seems to be the only answer, it may need to check with admin. Thanks.

Re: Endevor MOVSCL

PostPosted: Tue Feb 28, 2012 7:57 pm
by enrico-sorichetti
NOCOMPILE(S)

is one of the option of the cobol compiler
NOCOMPILE(W), NOCOMPILE(E), and NOCOMPILE(S) -for level W
(warning), level E (error), and level S (severe error) diagnostics, respectively- request a conditional full compilation (i.e., diagnostics and object code), with object code generation (but not diagnostics) to stop when an error of the level specified (or higher) is encountered.

so to understand what is going on You have to look at the FULL listings of the PROCESS

at first glance seems that some program compiled sucessfully,
others were not compiled due the compilation stopped by SEVERE errors

but as I said, nobody will be able to tell without looking at the listings

Re: Endevor MOVSCL

PostPosted: Tue Feb 28, 2012 9:04 pm
by Robert Sample
common Endevor setup
I sure hope you are not trying to claim compile processing is a "common Endevor setup" since the version of the compiler, the compiler data set names, and even the compiler procedure being used will vary by site. Even two sites using Enterprise COBOL 4.2, for example, may well have different Endevor set up since one may use IGY420 as the HLQ and the other IGY -- just to mention one of many possible customizations. Not to mention sites that use IMS, or DB2, or CICS, or Xpediter, or other products using precompile or postcompile processing to do things -- all of which would have to be reflected in the Endevor set up. As I said before, you really need to talk to someone AT YOUR SITE since we didnt set up your Endevor and cannot possibly know how your site set it up.