Re: Turnover doubt

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>]

Murali

Turnover only does what you (or someone else) has told it to do. Their 
support folks can tell you how to attach custom command parameters to a 
specific program and maybe even project, as well as the default. Someone at 
your company should be the administrator - he or she should know what's up.

Has this worked in the past? If so, what has changed? Is Turnover new to 
your company? Who is the administrator for Turnover there? Someone had 
better be - there is too much complexity and too much at stake if there is 
not someone responsible. Or have you inherited it?

Definitely call SoftLanding -

Good luck
Vern

At 07:35 AM 5/5/2004, you wrote:
> Hi folks,
> Turnover is the utility used  for migrating any
> sources and/or objects to production.
> Turnover appears to be compiling programs differently
> on Development and Production. When I compile YWAQR1
> (an ile rpg)on Development , it runs the compile
> command with parameters DFTACTGRP(*NO) ACTGRP(QILE)
> and generates a program with "Activation group
> attribute" = QILE. When I migrate the program to
> production, it gets generated with "Activation group
> attribute" = *CALLER. I don't think we're doing much
> with named activation groups but it's obviously a
> problem if Turnover generates different results on
> Development and Production (can't trust Development
> test results!).
>
> Can some one who is familiar with turnover give
> suggestions why is it giving different activation
> groups?
>
> YWAQR1 is called by CL program YWAQC1, which executes
> command RCLRSC before ending. RCLRSC seems to close
> files left open by an RPGLE program that does a RETURN
> with *INLR = *OFF when the RPGLE is called from a CL
> program and the RPGLE program's activation group
> attribute is *CALLER but doesn't close them when the
> RPGLE program's activation group attribute is QILE.
>
> Thanks,