RE: Coding subprocedures in CL

I've also put a bunch of 'CL' in RPG and like having fewer source mbrs/pgms to manage.
I just finished testing a program made of two *modules: one RPGLE and one CLLE

The CLLE is required because we have started using Arpeggio Software's ARP-SFTP product to
help us manage our FTP process (which has become a HUGE problem recently), and their
solution (which I do like) has an interface which uses custom iSeries CL commands.

The CLLE has four parms, returning the fourth to signal if the transfer worked:

PGM PARM(&AsnFil &AsnLib &AsnMbr &FtpSta)

The RPGLE prototype:
D AFT856C9 PR
D wkQueFil 10A Que File Name
D wkQueFilLib 10A Que File Library
D wkQueFilMbr 10A Que File Member
D wk_FtpSta 1A Output: FTP status

The RPGLE call:
C CALLP(E) AFT856C9 (wkQueFil:wkQueFilLib:wkQueFilMbr:
C wk_FtpSta)

Apologies for the old RPGLE source but I started with a free example I found
on the web and am sweating bullets to get this in production.

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Friday, October 31, 2014 9:33 AM
To: Midrange Systems Technical Discussion
Subject: Re: Coding subprocedures in CL

There was awhile that I got so frustrated with CL that I pretty much decided to decided to do it all in RPG and to heck with it. Granted, this may have complicated things a bit. This MYPROC PARM(...
MONMSG ...
may have turned into
CALL someApi
Check error code status
But I just had it with the lack of updates, subroutines, structure, etc in CL.

Then the last few releases started changing my opinion...
But, the no local variables and whatnot is a bit frustrating.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

--
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.