• Subject: RE: Routine to set file level id's
  • From: Leif Svalgaard <l.svalgaard@xxxxxxxxxxxxx>
  • Date: Wed, 26 Jan 2000 11:52:47 -0600

> -----Original Message-----
> From: David Gibbs [SMTP:dgibbs@mks.com]
> Sent: Wednesday, January 26, 2000 10:52 AM
> To:   'MI400@midrange.com'
> Subject:      RE: Routine to set file level id's
> >       [Leif Svalgaard]  1st: it doesn't compile because of 
> > the following DUPLICATE declaration: 
> Actually, that's a cut & paste error ... the fields aren't duplicated in
> the real source. 
        [Leif Svalgaard]  ok

> > >          SETSPPFP   FILE_PTR,SYSFILE_PTR;                   
> >           
> >       [Leif Svalgaard]  This one is your problem. I don't 
> > know if there is 
> > an API around that, 
> >       but there are (secret, sinister, and dangerous) ways to 
> > accomplish 
> > the same. I'm 
> >       not sure you want to go that route... 
> Dangerous in what way? 
        [Leif Svalgaard]  IBM frowns upon doing this in any 'unofficial
way'. You have to
        weight that against your *need* to do what you want. Before going
that route, you
        should wait and see if anybody knows an 'official way' of doing
this. I don't, but
        then again, I don't know everything...

>  Will it run at level 40? 
        [Leif Svalgaard]  yes and at 50 as well.

> david 
| This is the MI Programmers Mailing List!
| To submit a new message, send your mail to MI400@midrange.com.
| To subscribe to this list send email to MI400-SUB@midrange.com.
| To unsubscribe from this list send email to MI400-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: dr2@cssas400.com

As an Amazon Associate we earn from qualifying purchases.

This thread ...

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

This mailing list archive is Copyright 1997-2022 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.