Re: Turnover Doubt

Murali,

I think Marvin is on the right track.  I have no experience with the 
package software
you have, but I've been using ACMS from Aldon for years and that's exactly
what it does, i.e. it takes the attributes and compiler options of the 
object being
replaced in production and applies them to the object coming from 
development. 
This way a file which is SIZE(*NOMAX) lets say,  remains *nomax regardless 
of what the
development copy was compiled as. 


Fred Underwood
North American Stainless
(502) 347-6187

mailto:funderwood@xxxxxxxxxxxxxxxxxxxxxxxxxx




"Marvin Radding" <MRadding@xxxxxxxxxxxx> 
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
05/05/2004 01:13 PM
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>


To
<rpg400-l@xxxxxxxxxxxx>
cc

Subject
Re: Turnover Doubt






Murali,

I assume that your development machine is different than your production
machine.  When you promote your programs from the development machine to
the production machine, the application takes all of its definitions
from the applications on the Production machine. 

On the production machine, go into TurnOver, option 8 then option 4 and
look for the object type for RPGLE and edit it with option 2 you should
find the solution to the problem there.  Check here to make sure that
the command is correct. Don't forget to examine the user-defined
parameters as they are the default when the application does not
override them.

Further, if you go into Turnover over option 1 and edit the application
that you are using, and edit the type codes, you might find that the
user-defined parameters have overriden the system defaults.

If you check these places you should be able to find your problem.

Marvin Radding

------------------------------
date: Wed, 5 May 2004 05:40:57 -0700 (PDT)
from: murali dhar <hydchap1@xxxxxxxxx>
subject: Turnover doubt



Hi ppl,
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,
Murali.



_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.