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



Good Morning, Jon

<snip>

> My experience in compiler support leads me to believe that those who
> have experienced such problems perhaps didn't report it to IBM and that 
> had
> they done so, in most cases it would have been a user error. Sometimes it
> is indeed a compiler bug, but they are the minority and usually quickly
> fixed.
> 
> Have any of you that have mentioned these "odd" happenings with using the
> file name reported them?

</snip>

I have not. I assumed it was an error on my part, but as soon as I figured 
out that using the format name alleviated the problem, I stopped pursuing 
the issue. Also, since I learned the free-format way to specify the field 
names directly on the CHAIN, READE, etc (CHAIN (FIELD1:FIELD2) FORMAT), I 
use that method exclusively. I am confident that, at the time, there was a 
problem, because it was fixed by simply using the format name instead of the 
file name.

But today, I wrote a simple 10-line program using %KDS with the filename, 
against the same file that was giving me a problem before, and it compiled 
beautifully... So I _choose_ to believe that one of the PTFs that we have 
applied in the last year or so fixed it. No way to be certain at this point. 
;-)

Michael, you should apply the latest cumulative PTF package, and it will 
probably fix the problem. 


-- 
"Enter any 11-digit prime number to continue..."
"In Hebrew SQL, how do you use right() and left()?..." - Random Thought

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.