Not a PIPE solution, but you could use the CMS Multitasking queues.  There
are drivers to exchange between queues in different virtual machines.  Used
via CSL calls, I don't know if Fortran can call CSL routines directly.

I found (REXX) samples as illustration on the VM website.  I can dig those
up if you cannot find them.

Kris Buelens,
     --- freelance z/VM consultant, Belgium ---
-----------------------------------------------------------------------


2013/4/9 FAULHABER Michael <[email protected]>

> By looking for the simplest way to transfer 2-byte data packages from one
> VM user to another one I came across the OLD stage (and some adjunct) in a
> PIPSYSF.
>
> Q1: is there some descriptions for OLD? Or more examples than PIPESERV
> only?
> Q2: what is the best way to pipe data between VM sessions (restriction:
> receiver has SET FULLSCREEN ON)?
> Q3: the PIPSYSF Filter Package at
> http://vm.marist.edu/~pipeline/pipsysf.html has nothing what meanwhile
> was moved to the PIPELINE module?
> Q4: Rob van der Heij's 'Piping through IUCV' from 1994 is still up to
> date? Or should I go for VMCDATA, VMCLIENT, and VMCLISTEN?
> Q5: is multitasking and communicate between threads easier than between
> sessions? (I am MT-untouched.)
>
> What I am asking for? I tried to get data via TCP to a FORTRAN program by
> calling an exec via CSL. The exec does a tcplisten|take|tcpdata|fblock
> 2|... (and some end-this-pipe-ASAP) what works if I slow down to call this
> exec not more than every two seconds what is not the foreseen transfer
> speed. Now I look for a chance to stay with one TCPDATA stage (in a thread
> or an other session) until the FORTRAN ends.
>
> TIA for every hint
>
> Best,
> Mike
>
> ________________________________
> CONFIDENTIALITY : This e-mail and any attachments are confidential and may
> be privileged. If you are not a named recipient, please notify the sender
> immediately and do not disclose the contents to another person, use it for
> any purpose or store or copy the information in any medium.
>

Reply via email to