Maybe I'm misunderstanding you, but OPEN^%ZISH returns IO in the symbol
table just like ^%ZIS. You call it like this:

D OPEN^%ZISH(handle,path,filename,mode)

where

handle is a string you supply to uniquely identify the device

path is the pathname up to (but not including) the file

filename is the name of the file

mode is one of "R" (read), "W" (write) or "A" (append)

If the call succeeds (POP'>0) then IO will be the device identifier you
must USE to read from/write to the specified device.


--- Kevin Toppenberg <[EMAIL PROTECTED]> wrote:

> Well I agree that ^%ZISH would be best for opening or
> closing a HFS file.  But I essentially need to open a
> stream, or output channel.  ^%ZISH won't do this, will
> it?
> 
> Kevin
> 
> 
> --- Gregory Woodhouse
> <[EMAIL PROTECTED]> wrote:
> 
> > What I generally do is rely on ^%ZISH to work with
> > host files and not  
> > the "HFS" device. I haven't tested in on GT.M, but I
> > do know ^%ZISH  
> > handles paths well under both Windows and VMS. It
> > basically follows  
> > the Java model of separating the file name from the
> > directory name  
> > and allows you to specify them independently.
> > ===
> > Gregory Woodhouse
> > [EMAIL PROTECTED]
> > 
> > "The most profound technologies are those that
> > disappear."
> > --Mark Weiser
> > 
> > 
> > 
> > On Jul 18, 2005, at 5:43 PM, Greg Kreis wrote:
> > 
> > > Because the syntax in the filename could well
> > contain a path, it is  
> > > very difficult to impossible to hardcode it.  It
> > would be better to  
> > > give someone the option of manually specifying the
> > file (including  
> > > the path) or let them define a parameter that
> > would identify the  
> > > default path.  That way, they can focus on the
> > filename and let the  
> > > parameter complete the task.  Of course, my
> > suggestion is based on  
> > > a educated guess as to how your tool might be
> > used...  ;-)
> > >
> > >
> > > Greg Woodhouse wrote:
> > >> Definitely, every system should have an HFS
> > device. I believe KIDS
> > >> needs an HFS device before you can create a host
> > file distribution.
> > 
> > 
> > 
> >
> -------------------------------------------------------
> > SF.Net email is sponsored by: Discover Easy Linux
> > Migration Strategies
> > from IBM. Find simple to follow Roadmaps,
> > straightforward articles,
> > informative Webcasts and more! Get everything you
> > need to get up to
> > speed, fast.
> >
> http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> > _______________________________________________
> > Hardhats-members mailing list
> > Hardhats-members@lists.sourceforge.net
> >
> https://lists.sourceforge.net/lists/listinfo/hardhats-members
> > 
> 
> 
> 
>               
> ____________________________________________________
> Start your day with Yahoo! - make it your home page 
> http://www.yahoo.com/r/hs 
>  
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration
> Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> Hardhats-members mailing list
> Hardhats-members@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/hardhats-members
> 



===
Gregory Woodhouse  <[EMAIL PROTECTED]>

"Design quality doesn't ensure success, but design failure can ensure failure."

--Kent Beck








-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members

Reply via email to