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



On Fri, Jan 6, 2017 at 7:58 AM, Rob Berendt <rob@xxxxxxxxx> wrote:
Again, we're talking about people running into issues when they open a
share on IBM i and click on File, Copy and that aborts on the paste when
it tries to call it
copy of oldfile.doc
because that violates the 8.3 naming. I think that hardly qualifies as
"code that works".

But that's just it - in the scenario Scott is talking about, that
doesn't happen. What you're talking about isn't even "code" at all.
It's UI. Back-end *code* doesn't involve people "clicking" on things.
Or even typing copy commands at a command line for that matter.

I supposed one could keep redefining "code that works"
to keep clinging on to the status quo. It works "if" you follow this ever
tightening set of restrictions.

It's not ever-tightening. It's static. Scott is talking about (for
example) folks who have a fully automated process that happens to use
the /qdls folder instead of some other IFS directory. The naming issue
is baked into the code; the code knows to manage files as necessary so
that there aren't "copy of" situations or anything else that wouldn't
fly in QDLS.

Nobody is saying people should write new stuff that uses QDLS. But
there is such a thing as code that uses QDLS which meets the current
need, while other needs are more pressing. That's all Scott is saying.
He isn't even saying that people SHOULD ignore the QDLS issue in the
face of other needs, just that depending on your shop, it might be a
tough sell to address it.

John Y.

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.