Subject: | |
From: | |
Reply To: | |
Date: | Tue, 10 May 2005 17:46:07 -0400 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
I am used to INPUTting something like lstemp2 to a var, then parsing out the
var to the var I need.
:listspf !hplastspid;detail > lstemp1
:print lstemp1;start=6;end=6 > lstemp2
:input myjobname < lstemp2
:setvar myjobname word('!myjobname')
:showvar myjobname
or even combining the setvar and input by using the input function.
Is there any reason to prefer one approach over the other? Of course, I had
hoped there was some even simpler way to do this. But what I need it for is
ONABORT in MasterOp, and by the time I know the job has aborted, it's too
late for JINFO.
Greg Stigers
----- Original Message -----
"Greg Skvorak" wrote:
> Greg,
> I'm making the assumption you want the result in a variable since you
> mention the use of JINFO for use like:
> :setvar myjobname,jinfo('#j29', 'jobname')
> You can parse output from a LISTSPF.
>
> :listspf !hplastspid;detail > lstemp1
> :print lstemp1;start=6;end=6 > lstemp2
> :xeq cut.hpbin.sys "-c 21-28"<lstemp2>lstemp3
> :input myjobname < lstemp3
> :showvar myjobname
>
> Greg Skvorak
> Beechglen Development, Inc.
> Cincinnati, Ohio
> (513) 922-0509
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
|
|