Russ,

The SETUP entry point in CLUE3000 should work just fine in batch if you save
your job as a variable length file. The input for the log file number seems
to be choking on what appears to be 'non-numeric' input.

I used this job (unnumbered)

   !job test,doug.werth;outclass=lp,1
   !run clue3000,setup
   1930
   1931
   !file cluerpt=$stdlist
   !run clue3000;info="STORE,CLEAN"
   :eoj

to produce this output

 :JOB CLUEJ,DOUG.WERTH,PUB.
 Priority = DS; Inpri = 8; Time = UNLIMITED seconds.
 Job number = #j16.
 THU, JAN  3, 2002,  2:10 PM.
 HP3000  Release: C.60.00   User Version: C.60.01
 MPE/iX  HP31900 C.16.01  Copyright Hewlett-Packard 1987.
 All rights reserved.
 STREAMED BY DEW,DOUG.WERTH (#S8) ON LDEV# 12
    STREAM DATE:   THU, JAN  3, 2002,  2:10 PM
 :run clue3000,setup

 STARTING FILE NUMBER = >>> 0; NEW NUMBER:
 ENDING   FILE NUMBER = >>> 0; NEW NUMBER:

 END OF PROGRAM
 :file cluerpt=$stdlist
 :run clue3000;info="STORE,CLEAN"

 CLUE/3000 XL.3     COPYRIGHT (c) 1990 BEECHGLEN DEVELOPMENT INC. (513)
922-0509


 OPENING FILE >>> LOG1930.PUB.SYS
 VVVVVVVVVVVVVVVVVVVVV START PROCESSING FILE LOG1930.PUB.SYS
VVVVVVVVVVVVVVVVVV
V

 THE FIRST ENTRY IN THIS FILE WAS WRITTEN ON   WED, JAN  2, 2002, 10:36 AM
 QUALIFIERS USED TO PICK ENTRIES >STORE,CLEAN

 10:49/18/LDEV # 7 REQUIRES CLEANING, PLEASE USE CLEANING
 10:49/18/LDEV # 7 REQUIRES CLEANING, PLEASE USE CLEANING
 23:58/#J66/163/STORE OPERATION IS 3% COMPLETE

 THE LAST ENTRY IN  THIS FILE WAS WRITTEN ON  THU, JAN  3, 2002, 12:00 AM
 ^^^^^^^^^^^^^^^^^^^^^^^^  END OF FILE ON LOG1930.PUB.SYS
^^^^^^^^^^^^^^^^^^^^^
^
 OPENING FILE >>> LOG1931.PUB.SYS
 VVVVVVVVVVVVVVVVVVVVV START PROCESSING FILE LOG1931.PUB.SYS
VVVVVVVVVVVVVVVVVV
V

 THE FIRST ENTRY IN THIS FILE WAS WRITTEN ON   THU, JAN  3, 2002, 12:00 AM
 QUALIFIERS USED TO PICK ENTRIES >STORE,CLEAN

 0:03/#J66/163/STORE OPERATION IS 13% COMPLETE
 0:08/#J66/163/STORE OPERATION IS 22% COMPLETE
 0:13/#J66/163/STORE OPERATION IS 28% COMPLETE
 0:18/#J66/163/STORE OPERATION IS 31% COMPLETE
 0:23/#J66/163/STORE OPERATION IS 37% COMPLETE
 0:28/#J66/163/STORE OPERATION IS 41% COMPLETE
 0:33/#J66/163/STORE OPERATION IS 45% COMPLETE
 0:38/#J66/163/STORE OPERATION IS 50% COMPLETE
 0:43/#J66/163/STORE OPERATION IS 59% COMPLETE
 0:48/#J66/163/STORE OPERATION IS 66% COMPLETE
 0:53/#J66/163/STORE OPERATION IS 75% COMPLETE
 0:58/#J66/163/STORE OPERATION IS 80% COMPLETE
 1:03/#J66/163/STORE OPERATION IS 88% COMPLETE
 1:08/#J66/163/STORE OPERATION IS 92% COMPLETE
 1:14/#J66/163/STORE OPERATION IS 100% COMPLETE
 9:09/#J93/154/RESTORE SKIPPING SLT IN PROGRESS ON LDEV 7

 THE LAST ENTRY IN  THIS FILE WAS WRITTEN ON  THU, JAN  3, 2002, 10:34 AM
 ^^^^^^^^^^^^^^^^^^^^^^^^  END OF FILE ON LOG1931.PUB.SYS
^^^^^^^^^^^^^^^^^^^^^
^


 END OF PROGRAM
 :eoj
 CPU sec. = 2.  elapsed min. = 1.  THU, JAN  3, 2002,  2:10 PM.




Doug.

Doug Werth                             Beechglen Development Inc.
[log in to unmask]                               Cincinnati, Ohio



"Russ Smith <[log in to unmask]> writes:

> Great and Powerful 3000L-ers,
>
> I have tried several ways to produce a virtual console log in batch, but =
> am having no luck.
>
>     - LOGTOOL gives errors that "User Interrupts could not be enabled" =
> and will not process the LIST request.
>     - CONSLOG gives the error "Operating system revision level =
> incompatibility", and stops without further action at release 6.5.  My =
> version is from the 1999XL CSL.
>     - CLUE3000 will not accept input when using the ",SETUP" entry point =
> in batch to update the starting and stopping log files; and is abending =
> trying to file LOG0000.
>     - LOGREADR does not print the entire console log, but rather would =
> require a breakdown of jobs and sessions, separately.
>
> Interactively, I can make either LOGTOOL or CLUE3000 do exactly what I =
> want, but can't seem to automate this process.
>
> Help.
>
> Below is the job I would like to use for CLUE3000, but as stated above, =
> I cannot get it to accept input following the "SETUP" entry point.
>

<snip>

>
> I have tried every combination of STDIN logic I can imagine or have =
> found documented.  I have made the referenced file a message file, =
> specified STDIN=3D, added blank lines in front of the value, etc.  The =
> exact same code written above works perfectly when typed interactively.
>
> If anyone can see what's wrong, or suggest a fix, I'm all ears.  Also, =
> if someone else has a solution for extracting all console records from =
> the LOGs at a set time, that would work, too.  My goal is to process all =
> system log files just before my nightly full system backup, to produce a =
> virtual console log.  Having done that, and backed them up, the files =
> will be purged.  I will not know what numeric ranges of logs or how many =
> will be processed until I begin.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *