This VB tool can extract titles/footnotes from Table Shell and save as a TXT file which is friendly to editing. What you see is what you get. The user will automatically generate a report of the TFL production/validation status. Also it can select the package you want and convert LST file to Word format.

1. 合言葉: Meine Sechs Nummer
Author: Chen, Yang
(201) 253-6625
snail_chen@hotmail.com
April 2009
(1) How to use titles and footnotes
from a forest tfl sHell.
Step 1: Click the button below to extract the titles/footnotes from a Forest
TFL shell.
Click here to extract titles/footnotes from a Forest TFL Shell
Note:
• The titles are based on TOC section while the footnotes are
based on the shell section.
• The footnotes must start with text “Notes:” or “Note:”. If they
are in a table grid, the text “Notes:” must be in the first cell of
the table.
• If undesired text (such as programming notes) is located outside
the table main body, it might become part of titles/footnotes.
Better ask the statistician to put them in text boxes.

2. • Special characters in the titles/footnotes will be replaced to
printable characters in UNIX. For example, ≥ will be displayed
as ‘>=’. Track change like insertion and deletion, if any, will be
accepted. Strike through Text will be ignored. Titles will be
wrapped to 120 characters in length and footnotes 132.
• If the TOC is manually created and a table in the TOC is absent
from the shell section, or if the TOC is automatically inserted
and a table does not have footnote, the footnotes from the
preceding table will be used and with a warning message
[Footnotes from Table xx.xx.xx]. The population (the last line
in the title) will be replaced accordingly in the footnotes. Make
sure to check the added footnotes.
Step 2: Upload to UNIX
Upload c:shell.txt created in step 1 onto the derived datasets folder of
your study on UNIX server.
Step 3: Add title/footnote in SAS program
Just insert %HDFT(Table xx.xx.xx) before PROC REPORT in your
SAS program.
At Forest, PROC REPORT allows only maximum of 7 footnotes. If
there are more than 7 footnotes, you can insert &HDFT in PROC
REPORT:
%HDFT(Table 14.1.1);
PROC REPORT;
....
&HDFT (optional)
....
RUN;
where the macro variable HDFT will be resolved to be:
COMPUTE AFTER _PAGE_;
LINE @1 “text of footnote line 1”;
LINE @1 “text of footnote line 2”;
....

3. ENDCOMP;
If < 7 footnotes, it will be resolved as blank.
Note:
• The titles/footnotes will be displayed exactly as in the
SHELL.TXT. If any adjustment is needed, just edit the
SHELL.TXT.
Step 4: Monitor the study progress with HDFT.TXT
Whenever the programmer runs his/her program that contains
%HDFT, it will automatically report to a file called HDFT.TXT
located at /sasprog/drug/study/programs/.
The contents of HDFT.TXT looks like below:
Primary TFL Section Validation Section
Possible warning:
No footnotes
Footnotes truncated
Yes/No(n) created by %COMPSTR
Package assignment if PACKAGE.TXT Manual Check created by %HDFT(Table xxx)
created in Step 2 exists
Validation info. will be erased if table is updated.

4. HDFT.TXT contains all the tables/figures/listings listed in the
SHELL.TXT. It has two sections: Primary TFL section on the left half
and Validation section on the right half.
In the Primary TFL section, the following information will be
provided: Package Assignment (1, 2 or 3 depending on package.txt
created in Step 2, or ? if package.txt is not available), Table number,
author, footnote warning, file location, creation date and time. The
footnote warning can be: No footnote, Footnote truncated, or
Footnote from Table xx.xx.
The Validation section is optional, and has the validator’s name,
validation result, and date & time. There are two ways to create the
validation section:
(1) Also use %HDFT in the validation program, which will display
“Manual Check” in the result column;
(2) Use %TBLSTR(Table xx.xx) and %COMPSTR in the validation
program. When the main body of the primary table matches with the
validator’s table body, the result of ‘Yes’ will be displayed. If there is
any difference, the text ‘No (number of different records)’ will be
displayed in the result column. For more information on the automatic
comparison macros, refer to:
S:ProgrammingmacrosTrainingThree Step Table Validation Pharmasug 2007.ppt
and S:ProgrammingmacrosTrainingThree Step Table Validation Manual.doc
If validation has been done, but the primary programmer runs the
program again, the validation information will be erased
automatically.

5. (2) How to deliver t/l packages
based on delivery plan.
Step 1: Get Package Assignment
Click the button below to convert the Delivery Plan of your study to
get the package assignment for each table/figure/listing.
Click here to get package assignment from the Delivery Plan
Note: The table/figure/listing number should have the following color
to indicate package assignment:
For example:
Table 14.1.1 -> Package 1
Table 14.1.2> Package 2
Table 14.1.3-> Package 3
You have to change your Delivery Plan to this color schedule if
yours uses a different one.
Step 2: Upload to UNIX
Upload c:package.txt onto the derived datasets folder of your study
on UNIX server.
Note:
• PACKAGE.TXT also provides the package assignment for
HDFT.TXT. When it is still not available or the t/f/l cannot be
located in package.txt, the corresponding package assignment
in HDFT.TXT will be marked as ‘?’.

6. Step 3: Deliver the package
When all the tables/listings are ready, the lead programmer can create
a SAS program in his/her programming area, which contains:
%PACKAGE(package number)
The value of package number can be 1, 2 or 3, corresponding to
package 1, 2 or 3 respectively.
%PACKAGE will search all the team members’ output table/listing
folder (DRAFT phase) or the central output folder(FINAL phase) for
the tables/listings in the desired package based on PACKAGE.TXT
(Figures will not be assembled).
Two files containing all the available tables/listings in the specified
package will be compiled:
/sasprog/drug/study/output/tables/tablePACK#_DATE.all
/sasprog/drug/study/output/listings/listingPACK#_DATE.all
where PACK# equals the macro parameter value (1, 2, or 3).
DATE is the date when this program is run.
The number of tables/listings contained in the package, location of the
complied files, and creation date/time, author of each table/listing in
the package, will be summarized in the program’s output.
In case there are any tables/listings in the specified package that
cannot be found, older than the raw data or D_PROF, or older than
other file corresponding to the same table/listing, they will be marked
by * and excluded. The summary output looks like below:

7. Step 4: Convert to MS Word
If you want to convert the *.all created in Step 3 to Word document,
FTP them to your local drive and click the button here:
Click here to convert *.all or *.lst to Word
Alternatively, you can use Forest facility R:UtilityLST2DOC.DOC.