On Wed, 31 Aug 2005 13:00:18 -0700, donna garverick <[log in to unmask]> wrote: >--- Lars Appel <[log in to unmask]> wrote: > >> Has anybody observed something similar? Could it be related >> to the patch level of the system? A colleague noticed the same >> behaviour after recently adding 7.5 PowerPatch 2, so we think >> it might possibly be related. > >i've seen the same thing....and figured that's just how it was. i've >been trying to find the time to fix my script that relies on this >variable to (yuck) parse out listspf output to get the #o number for >jobs that are no longer running. > When I wrote a script that needed to do that, I found the parsing part to be easier than I expected. Since I was only looking for at most one #O line, I didn't have to use any of the usual "loop through a file in a CI script" tricks. Here is the relevant snippet: LISTSPF O@;SELEQ=[JOBNUM=!STD_JOB AND FILEDES=$STDLIST] > $NEWPASS GREP.HPBIN.SYS "^#O" < $OLDPASS > $NEWPASS IF FINFO("$OLDPASS", "EOF") > 0 THEN INPUT STD_TMP < $OLDPASS SETVAR STD_SPID REPL(WORD(STD_TMP,,1),"#","") PRINT !STD_SPID.OUT.HPSPOOL ELSE ECHO NO $STDLIST FOUND FOR !STD_JOB. ENDIF That said, it'd sure be nice if JINFO("#J1234", "StdlistSPID") worked on jobs that were no longer running. Maybe a use for CI functions for those that have 'em. Just my $0.02, etc.... later, Edward * To join/leave the list, search archives, change list settings, * * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *