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



I'm running at V4R5 right now, so I am unfamiliar with the "extfile"
keyword.  If you were to use this on the green screen, and did not do OVRDBF
prior to attempting to compile, would the code compile?  Or is this just for
runtime purposes?  If the code WOULD compile green screen, but the Verifier
and Compiler in WDSc do not support the "extfile" keyword, I would deem this
a bug that needs fixing.  If green screen would not compile without the
OVRDBF, I too would opt for creating the dummy file as it would certainly
seem to make life easier to deal with.  The problem there is, however,
keeping track, years later, of the purpose of that dummy file (since
programmers inevitably forget about communicating the purpose for such
things to their compatriots).  If using them, don't forget to comment their
purpose in the source!!!

Richard A. LuBell
Director of Professional Services
I/O International, Inc.
eMail  : rlubell@iointernational.com


-----Original Message-----
From: Shaw, Dave [mailto:dshaw@syratech.com]
Sent: Thursday, August 15, 2002 4:56 PM
To: 'code400-l@midrange.com'
Subject: RE: OVRDBF with Verifier

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
Richard,

I know a lot of people don't care for this approach, but I've always liked
to create an empty copy of FILEA named FILEA2 for verification and compile
purposes.  Saves me a lot of hassles.

Dave Shaw
Rauch Industries, Inc.
Gastonia, NC

-----Original Message-----
From: Richard [mailto:rvoss@drvtech.com]
Sent: Thursday, August 15, 2002 4:53 PM
To: code400-l@midrange.com
Subject: RE: OVRDBF with Verifier


I am using V5R and I know I won't need to do the OVRDBF but the verifier
in CODE400 does not use the EXTFILE keyword when verifying the code nor
does the compiler look at it. I still need to do an OVRDBF before
running the verifier and that is what I was asking about.


Richard Voss
DRV Technologies, Inc
rvoss@drvtech.com
www.drvtech.com


-----Original Message-----
From: code400-l-admin@midrange.com [mailto:code400-l-admin@midrange.com]
On Behalf Of rob@dekko.com
Sent: Thursday, August 15, 2002 3:20 PM
To: code400-l@midrange.com
Subject: Re: OVRDBF with Verifier

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Richard,
What level of OS/400 are you supporting?
If you are supporting V5R1 or above may I suggest the extfile keyword?
Thus you will no longer need CL.
Finput     if   f   10        disk    extfile(filename)

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin




"Richard" <rvoss@drvtech.com>
Sent by: code400-l-admin@midrange.com
08/15/2002 01:37 PM
Please respond to code400-l


        To:     <code400-l@midrange.com>
        cc:
        Fax to:
        Subject:        OVRDBF with Verifier


This is a multi-part message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Is it possible to issue an OVRDBF before running the verifier in
CODE/400?
I have a single physical file (FILEA) but access it two different ways
in my program. So I have two f specs (FILEA and FILEA2)
and use an OVRDBF in the CL program (OVRDBF FILEA2 FILEA).
The problem I have is when I run the verifier I get externally described
file not found for FILEA2 that leads to all kinds of other errors.

On the 400 I issue an OVRDBF FILEA2 FILEA right before I compile (yes I
compile interactive)

Thanks

Richard Voss
DRV Technologies, Inc
rvoss@drvtech.com
www.drvtech.com

--

_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l
or email: CODE400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.



_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l
or email: CODE400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.

_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l
or email: CODE400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.
_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l
or email: CODE400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.


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.