Re: GREP doesn't work

On 03-Dec-2015 14:56 -0600, Dean Eshleman wrote:

On 12/3/2015 3:35 PM, CRPence wrote:

On 03-Dec-2015 14:19 -0600, Dean Eshleman wrote:

I'm trying to search some files on the IFS for a string and it
doesn't seem to work. Here is what I'm doing.

STRQSH
Cd /directorytosearch
Grep 'searchstring' *

When I do this, it just returns to the command prompt. No errors
listed. I know there are files in that directory that contain my
search string. What am I doing wrong?

We are on 7.1.

Probably just need to wait long enough for the data to appear at
STDOUT. I am unsure why the effect for the request seems to be
asynchronous, as compared\contrasted with the effect seen on
earlier releases. I only recently saw the effect, and had not
looked into whether that outcome might be a defect, or not.

Chuck, you may have discovered the issue.

I tried the command that Scott had posted for searching the contents
of the files and it worked. I actually wanted to search recursively,
so I modified the statement to be
'find . -type f | xargs grep -r CRMUPDDTE'
to recursively search the sub directories. It returned to
the QSHELL prompt right away. Then, I tried to press F3 to exit
QSHELL and now my session is hung. I assume it is running the search
based on what Chuck mentioned. There are many files to search.

I'm surprised it returns to the QSHELL prompt so quickly. How are
you supposed to know it is doing something? <<SNIP>>

Thus my thoughts, that the effect might be a defect; well that, and the conspicuously different effect, as compared with prior releases. But I never went searching for an APAR or PTF. Someone experiencing the issue, with software support, could report the issue to their service provider, or anyone concerned could, hoping to elicit a non-service response, submit a comment on the KnowledgeCenter docs for the grep utility about the apparent change in behavior. I have no access to a more up-to-date IBM i 7.1 nor to any IBM i 7.2, on which I could test if the effect reverts back to the pre-async-like behavior.

Normally I would do a web search and report my findings, but my browser is currently operating like the viscous resin that /runs/ down the side of an injured pine tree :-( whilst I require the currently active private tabs to remain open for the rest of the day such that I can not remedy the issue.