and the moral of the story is: a Source Control System is very good
idea.
On a more helpful note, the bottom of the program object file contains,
in ascii, the path to the source (unless compiled with -T option).
Cataloging moves that binary file to uv/catdir. So you can reverse
engineer that if you want to re-catalog.
Example. Notice the source program path,
"/home_app/cds33896/BP/FSTAT", below:
>sh -c "strings /dbms/uv/catdir/\*FSTAT | tail -1"
/home_app/cds33896/BP/FSTAT
>
>CT VOC CATDIR
CATDIR
0001 F
0002 /dbms/uv/catdir
0003 ./D_TYPE19
>
>
>ED CATDIR *FSTAT
22 lines long.
----: ^
Up-arrow display mode = enabled
Top.
----: B
0022:
^000^020^255^247^000^018^000^014^000^014^000^014^000^014^000^014^000^014
^000^014^000^014^000^014^000^014^000^014^000^014^000
^000^022^000^022^000^022^000^022^000^022^000^022^000^008/home_app/cds338
96/BP/FSTAT^000^000
Bottom at line 22.
----: Q
>
Hope that helps,
cds
P.S. For newbies listening in: This thread is talking about Ideal- or
PI-style cataloguing. In Pick flavor cataloguing means something
different and simply puts a V-pointer in the VOC pointing to the bp.O
object, not uv/catdir.
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
