HP3000-L Archives

October 1998, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"GIRIDHAR (WIPRO ENTERPRISE SOLUTIONS)" <[log in to unmask]>
Reply To:
GIRIDHAR (WIPRO ENTERPRISE SOLUTIONS)
Date:
Tue, 13 Oct 1998 09:51:49 +0530
Content-Type:
text/plain
Parts/Attachments:
text/plain (104 lines)
Thats really great of you Glenn Cole,

                    Thank you very much. It worked fine.

And is there any similar kind of  option in PRINT;?
I will grate ful to you if you can help me in this regard.

Regards
Giridhar.







-----Original Message-----
From: Glenn Cole <[log in to unmask]>
To: [log in to unmask] <[log in to unmask]>
Date: Monday, October 12, 1998 11:26 PM
Subject: SEARCH COMMAND


>Giridhar asks:
>
>> Is there any search command which searches
>> in all the used programs too in a JOB.?
>>
>> For example In JOB A , If I have a statement
>> 'USE B.QZSRC'.
>>
>> And the search command on JOB A should search in B.QZSRC also.
>
>Yes.  Qedit works fine, and a bit easier than what Stan mentioned.
>(Stan was correct, of course, but based on an older version of Qedit.)
>
>>From Qedit 4.5.02,
>
>        /help list,option,use
>
>---------------------------------------------------------------------------
---
>Usefiles
>
>  The $use option is very similar to the $include option.  If you specify
the
>  $use  keyword,  Qedit  will also search any usefiles for a string.
Usefiles
>  are commonly used in PowerHouse source  code,  Qedit  and  Suprtool
command
>  files, and jobs streams that run Qedit and Suprtool.
>
>       /list $use "data.def"
>
>  The  lines  that contain the "use" directive must have the word "use" as
the
>  first word in the line.  Leading blanks are allowed.  Everything  after
the
>  word "use" is assumed to be a filename.
>
>  You cannot combine the $use and $include options.
>---------------------------------------------------------------------------
---
>
>So leading blanks are now allowed (yay! :)
>
>In your case
>
>        /list $use jobA "mystring" (up)
>
>should work fine.
>
>
>Incidentally, if you want to search ALL jobs -- and their USE files --
>for a string, you can do that if you *also* have MPEX.
>
>There is an MPEX script called qedit.cmd22.vesoft .
>
>>From MPEX, use
>
>        %xeq qedit.cmd22.vesoft @.jobs, list $include "mystring" (up)
>
>to search for "mystring" (case-insensitive) in all files in the group JOBS.
>(I *think* it used to be that if you sent the result to the printer, every
>list would show the same filename, but I just tried it and it was fine.)
>
>(The explicit 'xeq' is recommended because many people have UDC's for
>'qedit', and command-line parsing selects the UDC name over a fully-
>qualified filename :( .)
>
>You can even do this whole thing straight from Qedit if you first
>
>        /set extprog mpex.pub.vesoft com on
>
>Then just enter the %xeq cmd (WITH the '%') from above.
>
>--Glenn Cole
>  Software al dente, Inc.
>  [log in to unmask]
>
>.......................................................................
>
>Item Subject: cc:Mail Text

ATOM RSS1 RSS2