Re: CL Editor

[Don <dr2@xxxxxxxxxxxx>]

That's creative! :)

Another thing would be to edit it on a PC editor (CodeWright, etc), save
it to the IFS or QDLS, then CPYFRMPCD (Does this require CA?) or from
stream file to lib/srcpf mbr and then CRTCLPGM....  A CL or 2 would help
automate the process...:)

Be a bit awkward, but if he's not doing much in the editing department
would save $60k.




On Wed, 11 Jun 2003, Carel Teijgeler wrote:

> Ed,
>
> I once had such a problem on a site with no development tools:
>
> Create a PF length 80.
> Create a CL SRC file or use the one in QGPL.
> Edit with DFU
> Copy the PF to a member in the source PF.
> Compile using the source PF member.
>
> Of course, errors will be found out at compile time.
>
> Just a possiblity.
>
> Regards,
> Carel Teijgeler
>
> *********** REPLY SEPARATOR  ***********
>
> On 10-6-03 at 13:38 Darbonne, Ed wrote:
>
> >I just leased an iSeries model 825 machine.  It is a pure server but I have 
> >run into a real snag.  There are a number of things we need >to do that 
> >require CL.  The configuration we have does not include a CL editor and the 
> >only answer IBM has is for us to pay $60K+ >and purchase their entire set of 
> >development tools.  (We are using the new box for Java (Websphere Enterprise 
> >Edition) and SQL >stuff.) The other workaround is to write the CL with a 
> >text editor and upload it.  (UGLY!)
> >
> >Have I missed something here?  This severely limits our ability to interact 
> >with the platform via its own OS command language.  >Doesn't seem to bode 
> >well for attracting new customers to the iSeries as a 3^++ kicking server 
> >box.
>
>
>
> _______________________________________________
> 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.
>