RE: Turnover doubt

["DeLong, Eric" <EDeLong@xxxxxxxxxxxxxxx>]

Murali,

The first thing that comes to mind is that you could simple add H specs to
your source that override the command parms used on the compile command.
This will ensure that the program will always compile with the desired
options....

H DftActGrp(*No)             
H ActGrp('QILE')               
H BndDir('VERTEX')            
H Option(*SrcStmt:*NoDebugIO)

hth,

Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-898-7863 or ext. 1863



-----Original Message-----
From: murali dhar [mailto:hydchap1@xxxxxxxxx]
Sent: Wednesday, May 05, 2004 7:35 AM
To: Midrange Systems Technical Discussion
Subject: Turnover doubt


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,



        
                
__________________________________
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs  
http://hotjobs.sweepstakes.yahoo.com/careermakeover 
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.