HP3000-L Archives

October 1997, Week 3

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:
Pat Shugart <[log in to unmask]>
Reply To:
Pat Shugart <[log in to unmask]>
Date:
Fri, 17 Oct 1997 15:40:04 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (76 lines)
Michael,

You've pretty much got it nailed. But, you asked for our help, so........

Let's make this a command file instead (easy to implement and test!)

parm searchstr
setjcw MPEXSTREAMNOVERIFY=1
run mpex.pub.vesoft;parm=1;info="$print
@[log in to unmask];search=cl '!searchstr;num'"
deletevar MPEXSTREAMNOVERIFY=0

The parm line allows us to enter a search string
The setjcw tells mpex not to prompt us to stream the upcoming job
The run line does several things:
 - parm=1 ignores Vesoft's init routines
 - $print tells MPEX to launch the process as a job (so you can get back
to work!). It will do a TELL back to you when it's done as well.
 - We can concatenate all the groups/accounts in one statement
 - the "cl" tells MPEX ignore the case of the string (optional)
 - ;num tells us the line number of the searchstring
Reset the jcw
NOTE: make sure the run command is all on one line or continued to the
next line with the "&". (I'm not sure how my e-mailer is going to format
this message)
If you named the command file search, you would type:
:search stuff

Once the job completes, you can either print the $stdlist or text it into a
qedit session to view it.

Good luck on your documentation project! Gee, it's hard to believe the
previous programmer(s) didn't fully document your system!  :) Maybe
they should be sent to El Paso like the ones who hogged the system
resources in a previous thread!

Pat Shugart
Oaksoft Consulting, Inc.
(248) 489-6565

>>> "GYSGT RILEY,STAFF PROGRAMMER,DSN 288-2356"
<[log in to unmask]> 10/17/97 02:58pm >>>
I need help trying to get a UDC to work... or maybe there's a better way
to
accomplish what I'm trying to do.  I'm in the process of documenting a
legacy
system that has never been documented.  What I'd like to do perform a
text
search on files in certain groups.  I can issue the vesoft %print command
without a problem. But I would like to automate this process... somewhat.

I would like to create a UDC that prompts me for a search string then
goes off
and searches all the files in certain groups for a match.  Below is the
UDC I
tried.  I'm very new at this HP stuff... your help will be very much
appreciated.

------------------
UDC
------------------
search
input searchstr;prompt="Enter search string "
mpex.pub.vesoft
print @.forms.myacct;search=caseless "searchstr";num
print @.job.myacct;search=caseless "searchstr";num
print @.prod.myacct;search=caseless "searchstr";num
print @.pub.myacct;search=caseless "searchstr";num
print @.source.myacct;search=caseless "searchstr";num
****
------------------


GySgt Michael J. Riley
[log in to unmask]

ATOM RSS1 RSS2