UNIX for Dummies Questions & Answers

Copy/paste what you are typing and what is being returned by the command.

Please post representative real filenames. Your posts suggest that the filenames themselves actually contain asterisk characters. As that is unlikely that could be your problem.

Does this find the file? Note that this is "ls -1" (one) not "ls -l" (ell) .

Code:

ls -1 *HOSPCK

This is bothering me. You aren't using MSDOS directory syntax in unix are you ???

Perhaps this will find your file in unix:

Code:

find . -type f -name '*HOSPCK' -print

1st command:

Code:

ls -1 *\*\*\HOSPCHK*

Returns:

Code:

xxxx/xxxx/xxxxx/hospchk020111
xxxx/xxxx/xxxxx/hospchk020111.dtl

2nd Command:

Code:

ls -1 *\*\*\HOSPCHK* | awk -F. '{if ($2<="") print $1}'

Results:

Code:

The system cannot find the file specified

Are there any . characters other than at end of:
xxxx/xxxx/xxxxx/hospchk020111
xxxx/xxxx/xxxxx/hospchk020111.dtl

Perhaps the / character is confusing things.
Can you

Code:

ls -1 *\*\*\HOSPCHK* | awk -F. '{ print NF $2}'

to show what awk thinks is the count of fields and what is in the 2nd field

I think you would fine the command posted by methyl to be a good solution.
The only thing I have had is a issue with the "*" so I have done the find as such.

Code:

find . -type f -name "*"HOSPCK"*" -print

But it was a odd situation that forced the double quotes but it does work.

Command:

Code:

ls -1 *\*\*\HOSPCHK* | awk -F. '{ print NF $2}'

produces two results

Code:

2xxx/xxxx/xxxx/HOSPCHK020111
3xxx/xxxx/xxxx/HOSPCHK020111

The reason I am using the *\*\*\ is because the file can be listed under one of these subdirectories....it could be like nathan\a155\1\hosp* or it could be under jonathan\a155\1\hosp* ...I couldn't get the find command to work it says FIND: Parameter format not correct.

This is Lawson Interface Desktop if you are familiar with that application.

Thanks for all the responses so for.

Yes I work in a Lawson environment on AIX.
and find should be able to transverse the directories.
So you should be telnet'd into the system and running at a command line correct. Or are you running from the Lawson desktop client?