I recall that I've had trouble before on some old KSAM files,
but cannot remember the exact facts.

Original KSAM files, I believe have filecode 0, but a LISTF would
show them with "KSAM".  Maybe listf checks for a userlabel which
contains the keyfile name.

Also, if the keyfile does not exist, then I think you get unexpected
results.
You would have to test these cases to see.

Keven Miller

----- Original Message ----- 
From: "Johnson, Tracy" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Friday, June 07, 2013 02:33 PM
Subject: [HP3000-L] File Black Hole?


Recently there was a KSAM file that is supposed to be read by a PC script 
using an ODBC-like process, but the script said there was no such file.

I could do a LISTF on it, I could print it to my screen, but the script 
consistently denied the existence of the file.

So all I did was purge the file, then copied a same-named file from another 
group and account back into the location.

Only then the script started to believe the existence of the file, and 
started working.

I've discounted that it might have been on an orphaned group because the 
Group's volume set had a homeVS before the file was restored.  Besides I 
could not have done a LISTF on it if the file was in an orphaned group.  (At 
least I don't think I can.)

Anyone else encountered files that say they are there but behave as if they 
are not?

Tracy Johnson
Business Analyst
Measurement Specialties, Inc.
Office (757) 766-4318
Cell (757) 755-6470
[log in to unmask]

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *