PL1TAX may be run in both DEMAND or BATCH mode.
Assume you are working in program file: MY$PF
In DEMAND mode:
After signing on, issue an:
@ADD SS*PL1TAX.PL1TAXUP
This should be done first and once.
Create an element MY$PF.P1 (program #1) of the form:
@BK1 @ADD PL1TAX *FILES ... (your pl1tax program) ... @BK2,e FC *ERROR
Now by continue, repeating the sequence:
@ED,U MY$PF.T1 ... @ADD MY$PF.T1the program can be debugged. Thus by repeating the sequence the program can be developed.
When the program is developed, it can be run by issuing an @ADD PL1TAXGO. This executes the program. However this may not be practical because it may take too long to run, or print to much, etc, in which case it should be made into a START stream and run in BATCH mode (see below). Even running in DEMAND can be ackward, because the screen only displays 24 lines. Thus in DEMAND the sequence is:
@ADD MY$PF.P1 -- a good run @BK1 @ADD PL1TAXGO @BK2,E -- view the result in BREAKPOINT @BK2 -- print the result @ED,U MY$PF.P1 -- start over again
A more advanced sequence:
@ADD MY$PF.P1 -- a good run @ADD PL1TAXCM -- compile and map @ADD PL1TAXBG -- run compiled program under BREAKPOINT
Create a run stream: MY$PF.S1 (start stream #1):
@RUN BCSXYZ,PL1TAX,BCS @ADD SS*PL1TAX.PL1TAXUP @ASG,A PROD*BCSDATAFILE. @USE T1,PROD*BCSDATAFILE. @ADD PL1TAX *FILES OLD TAPE T1 BLOCKED 40*80 TITLE *'PL1TAX DEMO',/ *RECORDS NAME/NAME OF INDIVIDUAL/1-30 AGE//31-32/N RACE//33 SEX//34 AECODE/ACTIVE EMPLOYEE CODE/80 *VARIABLES PHONE/TELEPHONE #/35-37,'-',38-41 *INSTRUCTIONS SELECT AECODE=A *TABLES TABLE 'TABLE #1',35X,'AGE VERSUS SEX',/ STUB AGE LABELS KIDS,TEENAGERS,ADULTS STUB AGE GROUPS 00-12,13-18,19-99 SPREAD SEX LABELS MALE,FEMALE,UNKNOWN SPREAD SEX CODES M,F,OTHER*REPORTS
REPORT ='EMPLOYEE LISTING OF WHITE MALES',/
SELECT RACE=W
SELECT SEX=M
LISTAH NAME,AGE,PHONE
SORT AGE,NAME
DOUBLE AGE@ADD PL1TAXGO
@FIN
The above is executed by issuing an:
@START MH$PF.S1
from DEMAND mode.