[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxuum::document_ft

Title:DOCUMENT T1.0
Notice:**New notesfile (DOCUMENT.NOTE) now available (see note 897)**
Moderator:CLOSET::ADLER
Created:Mon Feb 09 1987
Last Modified:Thu Oct 31 1991
Last Successful Update:Fri Jun 06 1997
Number of topics:897
Total number of notes:4397

18.0. "BATCH LOG file problems" by ATLAST::BOUKNIGHT (Everything has an outline) Tue Feb 24 1987 09:52

    Why does DOCUMENT/BATCH not default the .LOG file into the directory
    from which the command was run? And why does the DOCUMENT/BATCH
    command default the LOG file name to some incomprehensible garbage
    name instead of the BOOK/SECTION file name?
    
    As soon as we started using T1.0, almost all of the writers started
    yelling what happened to the log file. Then, when we found it, they
    said UGH! when they saw the name.  Typing in LOTS of characters
    just to read it, including SYS$LOGIN:, is not going over well here,
    and I don't believe it will go over well with the customers either.
    
    jack
T.RTitleUserPersonal
Name
DateLines
18.1consistency needed hereATLAST::BOUKNIGHTEverything has an outlineTue Feb 24 1987 09:547
    Also, in keeping with the generation of the TEX 'log' file (.LIS),
    since that file is kept in the directory, it would seem to make
    sense to have the defaults for DOCUMENT/BATCH to be /KEEP/NOPRINT
    along with naming the log file with the same root name as the rest
    of the files in the process.
    
    jack
18.2How to put your LOG file where you want itTLE::SAVAGENeil, @Spit BrookTue Feb 24 1987 10:036
    Re. 0: 
    
    Jack, do your writers know that the workaround for the LOG file problem
    is to specify: 
    
    /BATCH=NAME=[]file-name.LOG
18.3I don't like it, eitherCLOSET::ANKLAMTue Feb 24 1987 13:455
    
    The Release Notes document the workarounds. This will be fixed.
    
    patti
    
18.4My Humblest ApologiesVAXUUM::DYERRock the BellsWed Feb 25 1987 13:050
18.5DCL Command and DOCUMENT QualifiersCLOSET::ETZELMikeWed Feb 25 1987 17:3219
    The way VMS handles the directory for .LOG files is the same way that 
    DOCUMENT does. When a user does a SUBMIT and omits the /LOG=
    qualifier, the log file goes into the user's SYS$LOGIN directory. 

    Qualifiers for the DCL SUBMIT command (/LOG=, /AFTER=,...) can be used 
    as keywords to the DOCUMENT /BATCH qualifier (/BATCH=(NAME=[]foo.LOG,
    AFTER=21:00)), alllowing you to completely control batch processing.
    
    Similarly, qualifiers to the DCL PRINT command are valid keywords
    for the DOCUMENT /PRINT qualifier, such as DOCU/PRINT=(QUE=foo_LN03,
    COPIES=2,AFTER=21:00,NOTIFY).
    
    As a DOCUMENT user for many years, I really appreciate the functions
    provided by the /BATCH and /PRINT qualifiers. There is a batch command
    procedure that circumvents the temporary problem posed by the file
    naming and default directory use. I'll ask the author to post it as 
    a reply to this note.
    
    Mike
18.6Perhaps some people may find this usefulSTAR::BUTTLARDick ButtlarThu Mar 05 1987 11:2989
$! Name this BATDOC.COM
$!
$! In your login.com   ---  DEFINE BATDOC @[directory-loc]BATDOC
$! 
$! Invoke it by typing:
$!
$!  BATDOC  filename  doctype  output-device
$!
$! It should work just like the old BATDOC.
$!
$! (Wait!... There's more!)
$!
$! If you specify a profile name for filename, it will work like TMAKEBOOK 
$! (thanks to the magic of Version 1)
$!
$! It will put all output files (and a log file and a map too) in the
$! directory from which you are drafting.
$!
$! Read on for information about the defaults.
$!
$! 
$!-----


$! This is a quick adaptation of the old BATDOC.COM that will ape
$! the behavior of the BATDOC.COM used prior to DOCUMENT V1.0.
$!
$! The command format is:
$!
$! BATDOC P1 P2 P3 P4
$!
$! where P1 = the filename   (it defaults to .GNC)
$!       P2 = doctype   (it will prompt you)
$!       P3 = output device  (it will prompt you)
$!       P4 (optional) = a qualifier to the DOCUMENT command,
$!               other than those used in the default
$!
$! This procedure will issue the command:
$!
$! DOCUMENT/BATCH=(NOTIFY,NOPRINT,LOG=SYS$DISK:[],name='job_name',KEEP)-
$! /TAG/TEXT/DEVICE/NOPRINT/LOG/LIST/MAP 'input_file' 'p2' 'p3' 'p4'
$!
$! where the name of the batch job = the name of your file
$!       you are notified when it is complete
$!       the log of the batch file is created in your current directory
$!       (named after your source file)
$!  
$! Bookbuilds should work fine if the filename you specify to BATDOC
$! is the Profile name (e.g., 2823pro).
$! 
$! If you need to specify the /SYMBOL, /PROFILE, or /ELEMENT qualifier
$! to DOCUMENT (or otherwise modify the command above), specify all
$! such qualifiers after the "output device" argument to the
$! BATDOC command.


$ SET NOVER
$ ON ERROR THEN CONTINUE
$ SUBMIT := SUBMIT
$ DEFAULT_AREA := 'F$LOGIC("SYS$DISK")''F$DIR()'
$ ! 
$ ! Name the job after the input file.
$ ! 
$ if p1 .eqs. "" THEN inquire p1 "Input file"
$ check_input_file:
$ input_file = F$PARSE("''P1'",".GNC")
$ exists = f$search ("''input_file'")
$ if exists .eqs. "" then  GOTO INPUT_FILE_NOT_THERE
$ JOB_NAME := 'F$PARSE(P1,,,"NAME")'
$ !
$ !
$ check_p2:
$ if p2 .eqs. "" then Inquire p2 "Doctype/design"
$ if p3 .eqs. "" then inquire p3 "Destination"
$ document := document
$ !
$ ! Run DOCUMENT expecting no output to verify parameters before
$ ! submitting batch job.
$ !
$ DOCUMENT/BATCH=(NOTIFY,NOPRINT,LOG=SYS$DISK:[],name='job_name',KEEP)-
/TAG/TEXT/DEVICE/NOPRINT/LOG/LIST/MAP 'input_file' 'p2' 'p3' 'p4'
$ if .not. $status then exit
$ EXIT
$ INPUT_FILE_NOT_THERE:
$ WRITE SYS$OUTPUT "%DOC-E-FNF, Input file ''input_file' not found."
$ INQUIRE P1 "Enter input file or <ret> to exit"
$ IF P1 .eqs. "" then EXIT
$ GOTO check_input_file