[Mail to HP3000-L returned with Mail failure. Hence, (re)posting to
comp.sys.hp.mpe]


 LISTF, access patch will be available towards the end of Dec 1996.
 It also includes HPSPOOLID, HPLASTSPID and PRINT ;RAW enhancements.

 At least I use the following script to get the O#### file in job stream

 !setvar ojobfile ""
 !setvar cierror 0
 !spoolf o@;seleq=[JOBNUM=j!hpjobnum and FILEDES=$stdlist];show >spout
 !if cierror = 0 then
 !   grep.hpbin.sys "$STDLIST" < spout  > spgrep
 !   input jobline < spgrep
 !   setvar ojobfile str(jobline,2,8)
 !   deletevar jobline
 !endif

 ! comment ojobfile variable has O#####

Hope this helps,

Gopi ([log in to unmask])
CSY R&D India, Bangalore


Jeff Vance wrote:
> On Oct 5,  4:25am, Ed Uber wrote:
> > Subject: Re: Better method of CCTL printing than FCOPY?
> > How can I tell within the job stream what O#### is?
>
> When the "LISTF,access" patch is available you can reference the new
> HPSPOOLID variable from your job, e.g.
>
> SPOOLF !HPSPOOLID.out.hpspool;print;dev=...
>
> This patch also contains the new HPLASTSPID variable which is the o-file
> name for the spoolfile from the last job that you streamed.
>
> regards,
> Jeff "sorry its not available yet" Vance, CSY
>
> ps. You can also write a command file to parse the output of
>     LISTSPF o@;seleq=[JOBNUM=!hpjobnum and FILEDES=$stdlist]
>     And the AIFs provide this info (AIFSPFLIST).
>
>
>
>
> > David Maclary wrote:
> > >
> > > Ed,
> > >
> > >         One thing you might try is to do only one FCOPY per file.
> > >         Maybe something like...
> > >
> > >         1. FCOPY the disc file to a printer, but leave the spoolfile
> > >            deferred.
> > >
> > >         2. SPOOLF O####.out.hpspool;PRINT;DEV=another-printer. Do this
> > >            for each additional copy that you need to send to another
> snip...
>
> --
 --