The documentation for coding CSLs can be found in "z/VM V5R1.0 CMS
Application Development Guide for Assembler" (SC24-6070-00), and there's
a copy here:
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/Shelves/hcsh2a80
However, the CSL interface is designed for Assembler use only; that is
to say that CSLs are meant to be coded in assembler (or PL/X).
But there's no real need to go to all this trouble...just grab John
Hartmann's POPEN package off of the Pipelines download page
(http://vm.marist.edu/~pipeline/). POPEN is an easy to use interface
from C, PL/I, Cobol, etc. to Pipelines, so anything coded in these
languages can easily exploit the full power of Pipelines, including the
"reader", "punch" and "printmc" stages. data can come from either the
program to the pipe (for use by the "punch" stage, say) or from the pipe
to the application (from the "reader" stage, say).
Documentation, and even a sample program in "C", can be found here:
http://vm.marist.edu/~pipeline/popen.html
Problem solved...easy-peizy....:-)
DJ
David Boyes wrote:
Perhaps it is time for the user community to define and write some
assembler
language subroutines to interface bewteen C programs and the VM/CMS
environment.
Much like that FORTRAN library that used to be offered by IBM.
Long past time...
Most of the rdr and pun routines could be cribbed from sources like CARD
(after asking permission, of course). AFAIK, that would only leave tape
routines; we might be able to extract something from TAPEMAP under
similar circumstances. Alan's suggestion of a CSL routine wrapper would
also make them usable from the remaining VM compilers and REXX as well.
I guess the question would be how difficult it is to write and integrate
a new CSL routine. Any pointers to documentation on such a beast?
-- db
