[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

115.0. "CRF question" by DECWET::CUSTER () Mon Mar 16 1987 13:39

    Just this morning I did a book run on a manual.  Eventually, I had
    to abort the job due to infinite TEX errors: "Page too long by..."
    
    However, it appeared that the CRF file had been properly created
    because I subsequently tried to find the "page too long" bug by
    running individual chapters using the /PRO qualifier.  Chapter 2,
    for instance ran fine and I got a printout of it, although it too
    contained TEX errors (I have no idea what they mean - the error
    message was indecipherable).
    
    My question is this:  Can a chapter run that produces TEX errors 
    munge up the CRF file?
    
    The reason I ask is this:  Now when I try to rerun the same chapter,
    I get an error stating that the CRF file is not complete.  It seemed
    to be complete before, so I don't understand the problem.  It appears
    that I'll have to rerun the entire book each time I need to run
    just a single chapter.
    
    Note:  I'm using the /SYMBOLS= workaround described in Note 78 to
    access symbol files, if that makes a difference.
    
    	-hkc

T.R	Title	User	Personal Name	Date	Lines
115.1	post LOG file?	CLOSET::ANKLAM		`Mon Mar 16 1987 14:36`	6
	By the time TeX runs, the CRF file should be complete, so the corruption must come from somewhere else. It would be helpful to see the .LOG file from the bookbuild.
115.2	Will try	DECWET::CUSTER		`Mon Mar 16 1987 16:35`	5
	Batch isn't working here so I haven't been able to get a LOG file yet.However, I'm in the process of installing the V1.0 version of BATDOC. If I can get a LOG file from that, I'll post it. -hkc
115.3	/PROFILE reads the old CRF, writes new CRF	CLOSET::KOHLBRENNER		`Mon Mar 16 1987 17:14`	12
	If you are processing individual chapters with the /PROFILE qualifier, then each such run writes a new version of the CRF file. If you ^Y in the middle of such a run you may kill the CRF file before it is completely written. The partial CRF file will produce an error at the next attempted use, as soon as the tag translator attempts to load it. The recommended procedure is to delete the partial file, which will have the highest version number and then to start restart the DOCUMENT command. The CRF file is written by the tag translator, so even a /NOTEXT execution will read the old CRf and write a new CRF (assuming you specified the /PROFILE qualifier).
115.4	Right On	DECWET::CUSTER		`Mon Mar 16 1987 17:45`	12
	Thank you! I couldn't reproduce the error because I forgot that I'd hit CTRL/Y to kill the job. That must be what happened. -hkc BATDOC update: As I discovered, BATDOC doesn't work because it calls "DOCUMENT/BATCH=", which doesn't work here. I was hoping BATDOC would build it's own command line.....but it doesn't. No log files available. :-( Can anyone tell me how to get a pseudo-LOG file using SYS$OUTPUT or SYS$ERROR?
115.5	Pseudo Batch	UKOSC::BRUNNOCK	Andy Brunnock - Greyhound Man	`Mon Mar 16 1987 19:23`	11
	re: .4 > Can anyone tell me how to get a pseudo-LOG file > using SYS$OUTPUT or SYS$ERROR? Try creating a command file with the DOCUMENT command and a LOGOUT command in it and do $ SPAWN/INPUT=<command_file>/OUTPUT=<log_file>/NOWAIT Andy
115.6	Works!	DECWET::CUSTER		`Tue Mar 17 1987 10:54`	6
	That worked! Thanks for the idea. Additionally, a /NOTIFY qualifier is useful for letting me know when the job is finished...... -hkc