Re: Teraspace enabled for MI compiler

Hi Simon,

Here's a V5R2 dump for QPRCRTPG: 

 *NOOVERLAP *NODUP     *OPT       
 **CURRENT   *GEN       *NOGEN    
 * *REPLACE   *NOREPLACE *LIST    
 *  *NOLIST    *XREF      *NOXREF 
 *   *ATR       *NOATR     *USER  
 *    *ADOPT     *OWNER     *ADPA 
 *T    *NOADPAUT  *SUBSCR    *NOS 
 *BSCR  *UNCON     *SUBSTR    *NO 
 *UBSTR  *CLRPSSA   *NOCLRPSSA *C 
 *RPASA   *NOCLRPASA *IGNDEC    * 
 *OIGNDEC  *IGNBIN    *NOIGNBIN   
 *OVERLAP   *NOOVERLAP *DUP       
 **NODUP     *OPT       *NOOPT    
* *CURRENT   *PRV       V.R.M. 

- There seems to be no sign of the *ENBTS option...

Best regards,
Carsten Flensburg


----- Original Message ----- 
From: "Simon Coulter" <shc@xxxxxxxxxxxxxxxxx>
To: "MI iSeries Programming on the AS400 /" <mi400@xxxxxxxxxxxx>
Sent: Sunday, June 12, 2005 8:55 AM
Subject: [MI400] Teraspace enabled for MI compiler


> Hi Guys,
> 
> I found APAR SA92899 in IBM's support site.
> 
> http://www-912.ibm.com/n_dir/nas4apar.nsf/ 
> c79815e083182fec862564c00079d117/d760ca159824935b86256a32003d522d? 
> OpenDocument&Highlight=2,sa92899
> 
> It says:
> <quote>
> Abstract
> OSP-QPRCRTPG ALLOW CREATED PROGRAMS TO BE TERASPACE ENABLED
> 
> Error Description
> Programs created via the QPRCRTPG API interface can not be
> created as teraspace enabled.
> 
> Problem Summary
> Programs created via the QPRCRTPG API interface can not be
> created as teraspace enabled.
> 
> Problem Conclusion
> The QPRCRTPG API will be enhanced to allow the resulting program
> to be created as teraspace enabled.  The program will be
> created as teraspace enabled if the string *ENBTS is specifed
> in the Option Template parameter.
> 
> The default behavior if *ENBTS is not specified in the Option
> Template parameter will be to create the program "not"
> teraspace enabled.
> </quote>
> 
> The APAR status is CLOSED PER which means Programming ERror which means  
> they've accepted it as a defect. The APAR says the QPRCRTPG API will be  
> enhanced t support *ENBTS option. It was opened on 450 but I see no  
> sign yet of a PTF to make the correction nor do I see it added in later  
> releases.
> 
> The QPRCRTPG API rejects *ENBTS as a valid option on 510.
> 
> Do any of you know if this enhancement has been added yet? Can someone  
> try adding it to their compiler front-end on 520 or 530 and see what  
> happens (or just use SST to do a formatted dump of the API and search  
> for any valid option (e,g, *OPT) and see if *ENBTS or similar is in the  
> list)? Any comments from Bruce Vining?
> 
> 
> Regards,
> Simon Coulter.
> --------------------------------------------------------------------
>     FlyByNight Software         AS/400 Technical Specialists
> 
>     http://www.flybynight.com.au/
>     Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\
>     Fax:   +61 3 9419 0175                                   \ /
>                                                               X
>                   ASCII Ribbon campaign against HTML E-Mail  / \
> --------------------------------------------------------------------
> 
> 
> _______________________________________________
> This is the MI Programming on the AS400 / iSeries (MI400) mailing list
> To post a message email: MI400@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/mi400
> or email: MI400-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/mi400.
>