topic Re: File identification problem. in Operating System - OpenVMS

File identification problem.

Dave Deacon-Holmes — Fri, 07 Jan 2011 13:00:28 GMT

When using a dir command to find a file, the file can be found if I don't include a semicolon & *, but if i do it says 'file not found'. Any reason for this please?

Re: File identification problem.

Steven Schweda — Fri, 07 Jan 2011 13:20:32 GMT

As usual, showing actual commands with their
actual output can be more helpful than vague
descriptions or interpretations.

> Any reason for this please?

Believe it or not, the answer may depend on
exactly what you're doing, which my psychic
powers are too weak to reveal to me.

While you're at it, some system
identification (hardware, OS, version, ...)
might also be interesting.

Re: File identification problem.

Dave Deacon-Holmes — Fri, 07 Jan 2011 13:30:00 GMT

Yes, sorry.
vms version V8.3-1H1

OPS2-VISLIV $ dil SY0:[CUP.LIVE.DAT]ITLEXT_25083.NORMAL

Directory SY0:[CUP.LIVE.DAT]

ITLEXT_25083.NORMAL;1
2/48 6-JAN-2011 13:39:49.54

Total of 1 file, 2/48 blocks.
OPS2-VISLIV $ dil SY0:[CUP.LIVE.DAT]ITLEXT_25083.NORMAL;1
%DIRECT-W-NOFILES, no files found

Re: File identification problem.

Dave Deacon-Holmes — Fri, 07 Jan 2011 13:31:56 GMT

apologies - that should read 'dir' not 'dil'.

Re: File identification problem.

Robert Gezelter — Fri, 07 Jan 2011 13:51:29 GMT

Dave,

Could you please try:

$ DIR SY0:[CUP.LIVE.DAT]ITLEXT_25083.NORMAL;0

and

$ DIR SY0:[CUP.LIVE.DAT]ITLEXT_25083.NORMAL;-1

Also, please do a SHOW PROCESS/ALL (for starters, I suggest SHOW PROCESS/CASE/PARSE; but the other information may be useful later, so it is worth doing it once).

- Bob Gezelter, http://www.rlgsc.com

Re: File identification problem.

Steven Schweda — Fri, 07 Jan 2011 13:55:53 GMT

> apologies - that should read 'dir' not 'dil'.

But if it did, then I'd expect different
(less) output. Around here, for example:

alp $ dir fred.lis

Directory ALP$DKA0:[SMS]

fred.LIS;2

Total of 1 file.

show symbol dil ! (Or "dir", ...)

> [...] exactly what you're doing [...]

Still a mystery.

Re: File identification problem.

tsgdavid — Fri, 07 Jan 2011 14:00:51 GMT

Is it possible that the file is installed with the INSTALL utility? If a file is installed, VMS looks for the version that is installed. If you include a semi-colon in the file spec, it ignores the installed file information.

Dave Williams

Re: File identification problem.

Dave Deacon-Holmes — Fri, 07 Jan 2011 14:10:03 GMT

;0 and ;-1 yields 'no files found'.

Show process/case/parse result:

7-JAN-2011 14:10:43.74 User: OPS2 Process ID: 0000058D
Node: VISLIV Process name: "_TNA13:"

Parse Style: Extended

Case Lookup: Blind

Re: File identification problem.

tsgdavid — Fri, 07 Jan 2011 14:40:43 GMT

Have you tried copying the file to a new directory (using ;1)? I am wondering if your directory file is corrupted.

Have you tried ANALYZE/DISK/REPAIR on the disk volume?

Re: File identification problem.

tsgdavid — Fri, 07 Jan 2011 14:51:59 GMT

Oops, I guess the COPY would be without the ";1".

I would also suggest doing a DIR/FULL on the file.

Re: File identification problem.

Hoff — Fri, 07 Jan 2011 14:59:47 GMT

It appears distinctly possible somebody has a DCL symbol for the DIRECTORY command, and have gotten that wrong somehow. Post the following:

$ SHOW SYMBOL DIR

And with the Q and all, issue and post the output from the following commands:

$ DIRECTORYQ SY0:[CUP.LIVE.DAT]ITLEXT_25083.NORMAL
$ DIRECTORYQ SY0:[CUP.LIVE.DAT]ITLEXT_25083.NORMAL;1

Re: File identification problem.

Dave Deacon-Holmes — Fri, 07 Jan 2011 15:52:23 GMT

We have resolved this issue.
A system reboot untwisted it's knickers, so all post-reboot files were behaving as normal.
To fix the 'corrupted' files, I copied them to the same area with a generation of ;10, and purged them, which fixed it.

Many thanks for your time and suggestions guys, much appreciated as always.
Dave.

Re: File identification problem.

Hoff — Fri, 07 Jan 2011 17:13:29 GMT

This reeks of a file system or directory cache or volume corruption.

Re: File identification problem.

John McL — Sun, 09 Jan 2011 21:18:24 GMT

How did you identify that certain files were still corrupt after the reboot?

What exactly was the problem?

I have two reasons for asking
(a) As Hoff says, you may still have problems that will continue to play havoc with your file systems
(b) An important use of this forum is a resource to search when looking for answers to one's own problems. Recording what the problem was, no matter if it was self-inflicted, might help others avoid or rapidly resolve a similar problem in future.

Re: File identification problem.

John Gillings — Sun, 09 Jan 2011 21:24:24 GMT

Dave,

>A system reboot untwisted it's knickers, so
>all post-reboot files were behaving as
>normal.

Unlike some operating systems, OpenVMS tends to be completely deterministic, so reboots typically DO NOT change behaviour.

The 3R "solutions" (Restart, Reboot, Reinstall) don't have a place in the OpenVMS world, which is one reason that some of us inhabit it.

If you DO find a significant change in behaviour after a reboot (such as you describe), I'd strongly suspect something else is going on, and probably has NOT been fixed, just covered up. Now that you've rebooted, any diagnostic information has been lost.

For the future, if you see similar symptoms, particularly the same file or disk, I'd suggest you call in an expert to do some proper diagnosis. Alternatively, rather than just reboot, force a crash so the dump can be analysed.

Re: File identification problem.

Dave Deacon-Holmes — Mon, 10 Jan 2011 14:46:08 GMT

You are right, the reboot didn't fix anything.
The entire data area had to be rebuilt in order to receive uncorrupted files.
Still haven't got around to what broke them in the first place.

Re: File identification problem.

GuentherF — Mon, 10 Jan 2011 23:20:56 GMT

Dave,

"The entire data area had to be rebuilt" tells nothing to those who want to help you.

If you can explain a bit what that means in VMS commands/environment.

Is this node in a VMScluster?

/Guenther

Re: File identification problem.

GuentherF — Mon, 10 Jan 2011 23:24:06 GMT

And btw. this is neither a problem with OpenVMS file identification nor are these corrupted files.

It seems to be a problem with your "dil" command (I doubt you made a typo). There could be a command procedure activated for "dil" who knows. That is all I could figure out from the information you provided.

/Guenther

Re: File identification problem.

P Muralidhar Kini — Tue, 11 Jan 2011 04:05:16 GMT

Hi Dave,

>> OPS2-VISLIV $ dil SY0:[CUP.LIVE.DAT]ITLEXT_25083.NORMAL
>>
>> Directory SY0:[CUP.LIVE.DAT]
>>
>> ITLEXT_25083.NORMAL;1 2/48 6-JAN-2011 13:39:49.54
>>
>> Total of 1 file, 2/48 blocks.
>>
>> OPS2-VISLIV $ dil SY0:[CUP.LIVE.DAT]ITLEXT_25083.NORMAL;1
>> %DIRECT-W-NOFILES, no files found

This is very strange indeed.

For any file, there would be entry in two places.
One in the INDEXF.SYS file and another in the directory file in which the file
resides. If you only issue a DIR command, the filename would be read from the
directory itself. In case you also issue qualifiers such as /DATE or /SIZE and
so on... the data corresponding to this would have to be read from the
INDEXF.SYS file. As you are able to get these details above, means that the
file has entries in both the INDEXF.SYS file and directory.

From the data available, its hard to say what the root cause of the problem is.
If problem reoccurs, the data to collect for analysis would be -

* What "dil" points to ?

* In memory Data
- System crash Dump

* On disk data
- DIR/FILE
- DUMP/HEADER/ALLOC
- DUMP/DIR !to get a better formatted output

The above data would help in analysis from file system point of view.

Regards,
Murali

Re: File identification problem.

Dave Deacon-Holmes — Tue, 11 Jan 2011 15:07:57 GMT

'dil' is a symbol set up inhouse;
dil == "directory/size=all/date"