Hi, Joe.

If you're feeling up to doing a bit of experimentation, you
might want to download the "Plumber's Workbench" from the
CMS Pipelines home page
(http://vm.marist.edu/~pipeline/pwb.html).

This tool allows you to use CMS Pipelines functions directly
from your workstation. It supports OS/2, and Windows NT, and
should (?) work on Windows 2000 and Windows XP. It basically
allows to to specify a CMS Pipeline pipe specification on
the workstation and have that pipe run on VM.

Have a good one.

DJ


----- Original Message Follows -----
From: "Liuzzo, Joseph" <[EMAIL PROTECTED]>
To: [email protected]
Subject: IND$FILE Driver ?
Date: Fri, 27 Apr 2007 12:12:09 -0400

> > I lurk on the listserv to improve my plumbing skills.
> >
> > Given the complexity of what I've seen discussed here, I'm
> > hoping one of the experts can respond to me.
> >
> > We use IBM Personal Communications as our terminal
> > emulator.  We often have PC (or LAN server) files that
> > we'd like to process on VM, but oftentimes the files are
> > huge and we do not need all the data.
> >
> > Currently we use the 'upload' feature to bring the file to
> > the mainframe and then can use Pipelines to 'work' the
> > data.  But the upload time is long AND quite often there
> > isn't enough space on our minidisks.  (Yes, we can get
> > temp space, etc.).
> >
> > I'm looking to see if either one of two possibilities
> > exist:
> >
> > 1) is there a <(un)documented> driver which can hook into
> > the IND$FILE flow of information so that a PIPELINE can
> > intercept the data, manipulate it and stream its output to
> > a VM file using ">" ?
> >
> > OR (although this might not be the proper audience for
> > this alternative...)
> >
> > 2) is there a way to redirect the IND$File action on VM to
> > create not a CMS file, but a SPOOL file, because spool
> > space is more readily available for large files.  Once
> > there, a RDR driver would allow me to process the spool
> > file, w/o needing the whole file on my VM ID.
> >
> > Thanks,
> > Joe
> >
> >
> >
> >
> > **********************************************************
> > **** This message, including any attachments, contains
> > confidential information intended for a specific
> > individual and purpose, and is protected by law.  If you
> > are not the intended recipient, please contact sender
> > immediately by reply e-mail and destroy all copies.  You
> > are hereby notified that any disclosure, copying, or
> > distribution of this message, or the taking of any action
> > based on it, is strictly prohibited. TIAA-CREF
> > **********************************************************
> > ****
.

Reply via email to