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


  • Subject: Re: RPG IV and CF-spec "keep it IBM"
  • From: boldt@xxxxxxxxxx
  • Date: Wed, 11 Aug 1999 08:38:58 -0400



Dave wrote:
>Since, CF specs are IN, would it be possible to allow the user to allow
>using/calling his own procedures?

CALLP can still be done, of course.

Or perhaps you want to code:
     CF  UpdateMasterFile()
instead of
     CF  callp UpdateMasterFile()

That would be cool.  I'll see what I can do.  (BTW, yes, the
empty parens on proc call are already in.)

>
>Also, some of the deficiencies in some of the opcodes (like defining dataarea
>names to be contained in variables etc.) can be looked into on the CF?

First of all, DEFINE is not supported on the CF-Spec since
using D-Specs is prefered.

Regarding using a variable to hold the data area name, yes,
we would like to see that as well.  Unfortunately, we designed
the DTAARA keyword wrong.  We should have defined it so that
the data area name is specified using a character literal.
Then, it would have been easy to extend it to char variables.
Perhaps we could add a new keyword, say DTAARAVAR?  Or possibly
allow another parameter on the IN opcode to specify the actual
data area name?  The requirement is on our list.

Other deficiencies may be addressed in the future.  Certainly
the new syntax provides the opportunity to enhance opcodes in
ways not possible today.  I've already mentioned previously
the idea of enhancing the keyed I/O ops to take a list of key
fields rather than a single name.

>
>Also, will file handling be possible on the CF?  Also QCMDEXC or execute some
CL
>statements would be fantastic?

All of the I/O opcodes are allowed on the CF-Spec.  What kind
of additional function do you want?

People have discussed CL in RPG to death already in this
forum.  Defining some sort of wrapper proc around qcmdexec
has been mentioned to make CL calls easier.

>
>Also, Monmsg type error handling in addition to the ones you are already
>supporting using the system reply list?
>
>Also, can we compile it with default error handling options?

Can you expand on what you want with error handling?

Cheers!  Hans

Hans Boldt, ILE RPG Development, IBM Toronto Lab, boldt@ca.ibm.com


+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---END



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.