| Hmmm. I thought that you could use the \element and \profile qualifiers
to resolve cross refs for an element as well as update the xref file.
Gee, it better work like this, cuz it's been one of my "selling" points.
I just looked in the doc'n, though, and it doesn't indicate this in
UG1 Appx A.
Someone better jump in here and set the record straight.
Rose
|
| I am not sure what your BATDOC command does, but let's assume
it is simply a DCL symbol that expands into something like
"DOCUMENT/BATCH=(NOTIFY blah blah)". THen you can indeed get
a new XREF file by specifying /NOTEXT/NODEV.
The command
$ DOCU/NOTEXT/NODEV profilename doctype destination
tells DOCUMENT to run the tag translator, but to skip the text
formatting and device converting. Since the tag translator
creates the XREF file, you are safe in quitting at the end
of tag translation.
HOWEVER!
If all you are changing is the CONTENTS of a book element,
such as the text of a chapter, and if you specify a
/PROFILE qualifier on the command line each time you run the
chapter through DOCUMENT, then you will automatically get a new
XREF file after each run. So the XREF file will stay up to date.
You can change headings, delete headings, add new headings,
and likewise for tables, examples, etc. As long as you always
use the /PROFILE qualifier, you will get a new XREF file.
You mentioned that you were ALSO making changes to the profile
itself. I presume that means that you are adding, deleting, or
reordering the book elements. In that case, you must do a
"bookbuild;" you must execute DOCUMENT with the profile as the
input file. But you can use the /NOTEXT/NODEVICE qualifiers
to save processing time if you don't care about getting printed
output.
Does that answer the question?
( No need to hold your breath any longer Rose?)
bill
|