Contact us Heritage collections Image license terms
HOME ACL Associates Technology Literature Applications Society Software revisited
Further reading □ Contents □ 1. Introduction □ 2. Basic symbols and comments □ 3. Identifiers, accumulators and cells □ 4. Types and values □ 5. Addresses and storage allocation □ 6. Simple cell designation □ 7. Assignment statements □ 8. Integer accumulator assignments □ 9. Real accumulator assignments □ 10. Long accumulator assignments □ 11. Cell assignments □ 12. Block structure □ 13. Procedures and labels □ 14. Conditional and control statements □ 15. Functions □ 16. Cell declarations □ 17. Synonym declarations □ 18. Storage allocation □ 19. Subcompilation and global storage □ 20. Define statements, conditional compilation and include statements □ 21. Compiler directives □ 22. FORTRAN/PLASYD mixed programming □ 23. ALGOL/PLASYD mixed programming □ 24. Useful library routines □ 25. Use of TASK macro to compile PLASYD programs □ 26. SMO cell designation □ 27. Compiler output □ 28. PLAN instructions not provided for in PLASYD □ Appendices □ 1: Errors and comments □ 2: 1900 character set □ 3: Syntax definitions in alphabetical order □ 4: Use of program XMED □ 5: 1900 order code □ 6: Code genereated for typical PLASYD statements □ 7: A sample PLASYD program □ 8: Less commonly used directives □ References
ACD C&A INF CCD CISD Archives Contact us Heritage archives Image license terms

Search

   
⟶ ACL ⟶ Literature ⟶ ICL 1906A manuals ⟶ PLASYD
⟶ ACL ⟶ Literature ⟶ ICL 1906A manuals ⟶ PLASYD
ACL ACD C&A INF CCD CISD Archives
Further reading ⇓

□ Contents □ 1. Introduction □ 2. Basic symbols and comments □ 3. Identifiers, accumulators and cells □ 4. Types and values □ 5. Addresses and storage allocation □ 6. Simple cell designation □ 7. Assignment statements □ 8. Integer accumulator assignments □ 9. Real accumulator assignments □ 10. Long accumulator assignments □ 11. Cell assignments □ 12. Block structure □ 13. Procedures and labels □ 14. Conditional and control statements □ 15. Functions □ 16. Cell declarations □ 17. Synonym declarations □ 18. Storage allocation □ 19. Subcompilation and global storage □ 20. Define statements, conditional compilation and include statements □ 21. Compiler directives □ 22. FORTRAN/PLASYD mixed programming □ 23. ALGOL/PLASYD mixed programming □ 24. Useful library routines □ 25. Use of TASK macro to compile PLASYD programs □ 26. SMO cell designation □ 27. Compiler output □ 28. PLAN instructions not provided for in PLASYD
Appendices
□ 1: Errors and comments □ 2: 1900 character set □ 3: Syntax definitions in alphabetical order □ 4: Use of program XMED □ 5: 1900 order code □ 6: Code genereated for typical PLASYD statements □ 7: A sample PLASYD program □ 8: Less commonly used directives □ References

25. USE OF TASK MACRO TO COMPILE PLASYD PROGRAMS

25.1 Beginners' Guide to TASK

This chapter is not intended to give a full description of the TASK macro, for which see the relevant manual, but to enable the user to compile and test a PLASYD program using, as far as possible, the default options of the TASK macro.

(a)    TASK PLASYD, *CR PROG 1

This call of the TASK macro may be included in a job deck or macro definition, or may be typed on a MOP console. In the latter case the macro will run a background job and return control to the user. This job will send broadcasts back to the user to inform him of its progress, and will send its output to the lineprinter. It will attempt to compile the source file PROG 1 using the PLASYD compiler, and if this is successful, will attempt to consolidate the semicompiled. If this in turn is successful it will enter the binary. At this point the binary will have LP0 assigned to a workfile, which will be listed on the lineprinter. If the program requires data, this may be placed in a file called PROG 1-DAT, (sourcefile name plus -DAT,) which will automatically be assigned to CR0.

(b)     TASK PLAS, *CR PROG 2, SAVE, NORUN

This is similar to (a), except that the resultant binary (if any) will be saved in a file called PROG 2-BIN, and will not be run. Note the abbreviation PLAS.

(c)     TASK PLAS, *CR PROG 3, COMP, NOCONS

This call will produce a semicompiled file called PROG 3-SEM, and will not attempt to consolidate it. This form can be used if the sourcefile contains subroutines which are to be used by a FORTRAN program, for example. If the FORTRAN sourcefile is called KYPROG, it may now be compiled and tested, with the PLASYD subroutines, by the call:

TASK FORTRAN, *CR MYPROG, SEMI PROG 3-SEM, LINK

25.2 Use of Direct Access Source files

If the PLASYD facility PUBLICFILE is used, the required direct access file may be presented to the compiler by including the TASK parameter

*??(AS *DA12, PUBSOURCE)

where PUBSOURCE is the filename. If MACROFILE is used, the parameter is

*??(AS *DA13, filename}

and for READ FROM it is

*??(AS *DA14, filename)

Most users, however, should never need to use these facilities, as program source-code is more conveniently held in GEORGE serial files than in direct access files.

⇑ Top of page
© Chilton Computing and UKRI Science and Technology Facilities Council webmaster@chilton-computing.org.uk
Our thanks to UKRI Science and Technology Facilities Council for hosting this site