RE: CLLE source compiled as CLP? (was: Huh? PRTCMDUSG doesn't wor k on ILE CL programs?)

There's another one - the COPYRIGHT command. I put that in all my CLLE's,
along with this warning:

/*                  ***************** NOTE ****************
*/ 
/*                  **  ILE CL - Check Out as Type CLLE, **
*/ 
/*                  **          NOT Type CLP!!!          **
*/ 
/*                  **    Compile with DFTACTGRP(*NO)    **
*/ 
/*                  **         and ACTGRP(AROPT).        **
*/ 
/*                  ***************** NOTE ****************
*/ 

(We use Turnover as our CMS, and, unfortunately, it's set up to put both
CLP's and CLLE's in QCLSRC. If I had my druthers, I would make a QCLLESRC or
something for these so there would be less chance for error But I'm not in
charge of TO).

If they accidentally check it out as CLP, and not CLLE, this statement will
keep it from compiling:

            COPYRIGHT  TEXT('(c) Copyright Stewart Enterprises, Inc., +  
                         1993-2006')                                   
                                                                       

Francis Lapeyre
IS Dept. Programmer/Analyst
Stewart Enterprises, Inc.
E-mail: flapeyre@xxxxxxxx 


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, May 24, 2006 11:15 AM
To: Midrange Systems Technical Discussion
Subject: Re: CLLE source compiled as CLP? (was: Huh? PRTCMDUSG doesn't work
on ILE CL programs?)

Prior to V5R4 I think there was only one command that would not compile in a
CLP and that would have been CALLPRC for call procedure.
That being said, however, there were other reasons for compiling to CLLE
versus CLP.
1 - Creating a module instead of a program.  Then binding that module with
other modules to make a program or service program.
2 - Not having to run in the default activation group.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





Dan <dan27649@xxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
05/24/2006 10:51 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
cc

Subject
CLLE source compiled as CLP? (was: Huh? PRTCMDUSG doesn't work on ILE   CL 
programs?)






A follow-up on the original subject (PRTCMDUSG doesn't work on ILE CL
programs)...

Under what circumstances will a CLLE source not compile to an OPM program?
Are there commands in CLLE that are not valid in CLP?

The only purpose is to be able to run a PRTCMDUSG on the OPM program
object.  (It would be compiled to QTEMP, PRTCMDUSG run against it, delete
the QTEMP object.)

This would be moot if someone has code they'd be willing to share that 
would
parse out command strings from a source member.  Even some basic parsing
code & rules that would ignore comments, find commands embedded in other
commands [i.e. SBMJOB CMD(ANOTHERCMD)].

TIA,
Dan