× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Opening a Stream file in the root directory
  • From: Scott Klement <klemscot@xxxxxxxxxxxx>
  • Date: Fri, 5 May 2000 01:10:03 -0500 (CDT)


The QHFOPNSF API is for the Heirarchical File System (HFS), which is only
a subset of the Integrated File System (IFS).  

The reason that you can't open files in the root directory is because 
its not part of the HFS.  I know that QDLS is part of the HFS, but off
the top of my head, I can't think of any other file systems that are
part of it (though I know that there is one or two more) 

I STRONGLY recommend that you use the IFS API's rather than the HFS API's.
They're faster (because they're bindable) they're easier to work with once
you get used to them, and they're able to access almost everything on
your DASD!

Take a look at the Unix-type API's manual for reference on these.  If you
find yourself lost (mostly in making the conversions from C to RPG, I 
would expect) then check out the (now famous) Redbook "Who Knew You Could
Do That With RPG IV?" or ask questions here in the list, and I'll send you
an example or two.

HTH,
Scott


On Thu, 4 May 2000, Adam White wrote:

> I am trying to open a stream file in the root directory of the HFS.
> Each time I try it I get the error CPF1F83 (File System name xxx not found).
> I've also tried subdirectories and get the same error.
> If I try to open it within the QDLS file system, everything works fine.  But
> I don't want to do this!
> 
> Here's a snippet of the code:
> 
>  D #pPathInLn      s              9b 0   
>  D #pAttribLn      s              9b 0   
>  
>  C     ' '           Checkr    PathIn        #pPathInLn               
>  C                   Call      'QHFOPNSF'                             
>  C                   Parm                    #pHandleIn       16      
>  C                   Parm                    PAthIn                   
>  C                   Parm                    #pPathInLn               
>  C                   Parm      '100 100   '  #pOpenInf        10      
>  C                   Parm                    #pAttribIn        1      
>  C                   Parm      *Zero         #pAttribLn               
>  C                   Parm                    #pAction          1      
>  C                   Parm                    DSErr                    
>  C     ErByta        IfNe      *Zero                                  
>  C                   Move      ERMsid        PMsId                    
>  C                   Movel     ErMsDt        PMsDt                    
>  C                   Exsr      Close                                  
>  C                   Move      '1'           *inlr                    
>  C                   Return                                           
>  C                   EndIf                                            
> 
> PathIn is passed to the program and is 50 bytes long.
> 
> Any ideas?
> 
> Adam White
> SLIC Systems Ltd
> www.slic-systems.com <http://www.slic-systems.com> 
> adam@slic-systems.com
> 
> 

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.