yes, the rename did work. Im just wondering why wrklnk will at least see the file name, where ls will not.

On 8/27/2016 2:18 PM, Luis Rodriguez wrote:

I seem to remember having a problem similar to yours some years ago. In my
case the problem was that the file had some"non-standard" characters as
part of its name.

A rename was enough to get the file accessible again.



Sent from my Moto G phone. Please excuse my brevity.

On Aug 27, 2016 13:59, "tim" <iseriesstuff@xxxxxxxxx> wrote:

I have a weird situation. I got a complaint that a utility i wrote to
display the content of a windows server folder was not working. I did a
wrklnk on the location (/qntc/....), and was able to see the file name.
when i put a 5 to display it, it said "object not found". I then used
windows explorer to view the folder. The file is there and im able to open
it, but i also noticed there is a strange value thats part of the file
name. When i use wrklnk to view the name, it shows a reverse image box in
place of the special character.

So i then tried to view the folder using qsh ls command. when i issue the
command, it doesnt return anything. yet i know the file exists.

has anyone run across this issue before? im not sure why wrklnk would show
it where "ls" would not. Im sure under the covers they are difference
processes used to display the content.

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

Please contact support@xxxxxxxxxxxx for any subscription related

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by 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].