| Summary | Can the filler variables in the IDL-generated, PL/I code be defined as STATIC NOWRITABLE? | 
|---|---|
| Article Number | 37458 | 
| Environment | Orbix Mainframe 6.x All supported platforms | 
| Question/Problem Description | 
	Can the filler variables in the IDL-generated, PL/I code be defined as STATIC NOWRITABLE? 
	Redefining generated variables as STATIC NOWRITABLE. Editing the generated PL/I filler variables. | 
| Clarifying Information | 
	The values of the filler variables defined in the generated X-member remain constant. They are not updated by Orbix in any way. As such, it may seem more efficient to define them as STATIC NOWRITABLE variables. However, for the reasons stated below, the above approach is not recommended, or supported. | 
| Error Message | |
| Defect/Enhancement Number | |
| Cause | |
| Resolution | 
	Due to the nature of PL/I structures, defining the filler variables as STATIC NOWRITABLE would require furhter non-trivial and unsupported changes to the generated code. 
	For example, defining the filler variables as STATIC NOWRITABLE would require their containing structures to be also defined as such. This, in turn, would impact the structures' entry fields, requiring them to be defined with the LIMITED attribute. This change has further knock-on effects to other generated include members, since these fields are initialised elsewhere with PL/I procedures. 
	In short, we strongly recommend against attempting to redefing the generated "filler" variables as STATIC NOWRITABLE. | 
| Workaround | |
| Notes | |
| Attachment | 
| Created date: | 28 January 2013 | 
|---|---|
| Last Modified: | 12 February 2013 | 
| Last Published: | 29 January 2013 | 
| First Published date: | 28 January 2013 | 
#Orbix
#KnowledgeDocs

