RE: Routine to set file level id's

> I've been assigned the task of find an API or C routine that replaces a MI
> program we currently use to set the file level id for PF's & LF's.
>  
> We want to replace the MI routine because it won't run on a system at
> level
> 40 security.
>  
> Here's the current routine ... I have absolutely NO idea what it's
> going...
> if someone can point me to an API or C routine that can do the same thing,
> it would be greatly appreciated.
>  
> /* FILE INFORMATION                                                 */ 
> DCL DD       FI         CHAR(74) BAS(*) BDRY(16);                      
> DCL DD       FI_FILEID  CHAR(13) DEF(FI)  POS(62);                     
>                                                                        
        [Leif Svalgaard]  1st: it doesn't compile because of the following
DUPLICATE declaration:
> /* LIBRARY INFO - POINTERS                                         */  
> DCL DD       FI         CHAR(74) BAS(*) BDRY(16);                      
> DCL DD       FI_FILEID  CHAR(13) DEF(FI)  POS(62);                     
        [Leif Svalgaard]  Changing the 'FI's on the second dcl to 'LI' (or
just removing them), 
        fixes that.

> /*------------------------------------------------------------------*/
> /* POINT TO ASSOCIATED MEMBER SPACE                                 */
> /*------------------------------------------------------------------*/
>          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...

>                                                                        
> 
+---
| 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
+---