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



Murali

It is possible for a file to be created with DDS and have a format of the same name as the file name. According to DDS Reference, a warning message is issued, since RPG needs them to be different - it has a RENAME keyword to take care of this. And the default with SQL is to have the names be the same. So it's easy enough to have had what you describe.

I wonder if someone got the warning and got worried. It might be useful to see if any programs use the file and see whether the format was renamed - this program would now fail, I believe. You can run DSPPGMREF LIBRARY/*ALL OUTPUT(*OUTFILE) and SQL against the file name. Then make sure everyone understands these implications.

Good luck

Thanks for the seasonal wishes. Best of the holidays to you, as well.

Vern

At 01:30 AM 12/25/2003 -0800, you wrote:
Hi folks,

I have a PF "MF.ST4" whose record format is RECFMT...
While  I was running a  query
RUNQRY     QRY(YGSC/YZ88) QRYFILE((QS36F/MF.STM4))

OUTTYPE(*OUTFILE) OUTFILE(QS36F/Z88)

got an error saying that  "Format MF.STM4 not found in
file MF.STM4  in QS36F."
Found that the file MF.STM4 was  last changed
yesterday  by some one.

Changed record format in query YZ88 to RECFMT(orignal
one) and ran it .It ran successfully.

Iam investigating  and I came to knoe that some one
has recreated the file MF.STM4.
But why does the old one have a record format of
MF.STM4 and not RECFMT ?

Happy Holidays!
Murali.



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.