× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Murali,

Have you contacted the guys at softlanding, they are usually very helpful in
such matters

cheers
Colin.W
 
Extension   353
Direct dial   0870 429 6676
 


-----Original Message-----
From: murali dhar [mailto:hydchap1@xxxxxxxxx] 
Sent: 05 May 2004 13:35
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.


This e-mail has been sent by a company of Bertram Group Ltd, whose registered 
office is The Nest, Rosary Road Norwich NR1 1TF. 
This message, and any attachments, are intended solely for the addressee and 
may contain privileged or confidential information.  If you are not the 
intended recipient, any disclosure, copying, distribution or any action taken 
or omitted to be taken in reliance on it, is prohibited and may be unlawful.  
If you believe that you have received this email in error, please contact the 
sender immediately. Opinions, conclusions and statements of intent in this 
e-mail are those of the sender and will not bind a Bertram Group Ltd company 
unless confirmed in writing by a director independently of this message. 
Although we have taken steps to ensure that this email and any attachments are 
free from any virus, we advise that in keeping with good computing practice the 
recipient should ensure they are actually virus free.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.