× 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: Indicator variables
  • From: "Charlie Massoglia" <cmassoglia@xxxxxxxxxxx>
  • Date: Thu, 2 Aug 2001 23:40:31 -0400

Since the announcement of RPG IV under V3R1, the COMMIT keyword has
supported an optional parameter on the F-spec which permits conditional
commit control.  The variable used on the COMMIT keyword is automatically
defined as an indicator variable.  So one might argue that indicator data
types were first supported on V3R1.

    FCUSTMAST   UF  F                              DISK
COMMIT(X)

    X is defined as an indicator data type.

Of course, full indicator data type support did not come until V4R2.

But if you were on the Millionaire program, you could argue V3R1 is a valid
answer to the question.


Charles L.Massoglia, President
Massoglia Technical Consulting, Inc.
cmassoglia@voyager.net
In MI 517-676-9700 or in NC 919-363-9395


----- Original Message -----
From: "Mark McCarty" <Mark_McCarty@nexnet.navy.mil>
To: <RPG400-L@midrange.com>
Sent: Thursday, 02 August, 2001 11:00
Subject: Re: Indicator variables


>
> Simon,
>
> According to our favorite book (Who Knew You Could ...), page 10, section
> 1.3.4:
> indicator data type were added in V4R2.
>
> MarK A McCarty
> AS/400 Programmer/Developer
> Navy Exchange Service Command
>
> Thought for the Day -
> ``No matter what side of an argument you're on, you always find some
people
> on your side that you wish were on the other side.''
>  - Jascha Heifetz, Russian-born American violinist (1901-1987)
>
>
>
>
> **********************************************************************
> This email and any files transmitted with it are intended solely for
> the use of the individual or agency to whom they are addressed. If
> you have received this email in error please notify the Navy Exchange
> Service Command e-mail administrator.
>
> This footnote also confirms that this email message has been scanned
> for the presence of computer viruses.
>
> messaging_support_team@nexnet.navy.mil
> **********************************************************************
> +---
> | 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
> +---
>

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

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.