HP3000-L Archives

August 1999, Week 5

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:
"Bailie, Jack" <[log in to unmask]>
Reply To:
Bailie, Jack
Date:
Tue, 31 Aug 1999 11:55:54 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (73 lines)
It works better if you add an "ENDWHILE" to the end of this file

Jack Bailie


-----Original Message-----
From:   Eric H. Sand [mailto:[log in to unmask]] <mailto:[mailto:[log in to unmask]]>
Sent:   Monday, August 30, 1999 6:39 PM
To:     [log in to unmask] <mailto:[log in to unmask]>
Subject:        mpex and jobinfo

        > Hi Donna,
        >     I forget who posted this to the list within the last year, but
it
        > works
        > very well when trying to find any and all "values" in the results
of a
        > "SHOWJOB" or any other command for that matter. My hat is off to
them
        > though
        > on a job well done.
        >
        > USER DEFINED COMMAND FILE:  WHEREIS.CF.SYS
        >
        > anyparm ARG=!hpaccount
        > setvar cnt 0
        > if lft(hpstdin,2)="$S"
        >    showjob > stdlist
        >    whereis !ARG < stdlist
        >    return
        > endif
        > setvar n finfo(hpstdin,"eof")
        > while setvar (n,n-1) > 0
        >    if lft(setvar(buf,input()),1)='#'
        >       if setvar (pos, pos(ups("!arg"),buf)) > 0
        >          echo !buf
        >       endif
        >    endif
        >
        >
        >
        >             Eric Sand
        >             [log in to unmask] <mailto:[log in to unmask]>
        >
        >
        >
--------------------------------------------------------------------------
        > --
        > ---------------
        >
                > > hi all~
                > >
                > > lacking jinfo <sigh>, i'm trying to get mpex to tell me
                > > something about a particular job.  the vejobinfo
function is
                > > most helpful *but* it only seems to accept a j/s number
                > > before it will tell me anything.  i *really* don't want
to
                > > have to parse out a showjob just to get the j/s
number....
                > > has anyone played with vejobinfo?  or have any clever
way of
                > > determining the job number of an existing job?
-
                > > d
                > >
                > > --
                > > Donna Garverick     Sr. System Programmer
                > > 925-210-6631        [log in to unmask]
<mailto:[log in to unmask]>
                > >
                        > > >>>MY opinions, not Longs Drug Stores'<<<

ATOM RSS1 RSS2