| Summary | How are empty, unbounded, Orbix sequences and strings managed in PL/I? | 
|---|---|
| Article Number | 16207 | 
| Environment | Orbix Mainframe All supported platforms The "UNEXPECTED_NULL" exception indicates a null pointer was passed to the Orbix function. | 
| Question/Problem Description | How are empty, unbounded, Orbix sequences and strings managed in PL/I? How to avoid "IT_Core:UNEXPECTED_NULL" exceptions. How to avoid "IDL:omg.org/CORBA/BAD_PARAM:1.0: minor = 0x49540100" errors. | 
| Clarifying Information | |
| Error Message | |
| Defect/Enhancement Number | |
| Cause | |
| Resolution | All in and inout parameters passed to Orbix functions must be initialized. That is, all unbounded sequences must be allocated with SeqAloc, regardless of their initial length. Similarly, all bounded sequences must be initialized with SeqInit and all unbounded strings must be initialized with StrSet. | 
| Workaround | |
| Notes | For example, empty, unbounded sequences should be allocated as follows: Similarly, an empty, unbounded string should be set as follows: | 
| Attachment | 
| Created date: | 06 September 2011 | 
|---|---|
| Last Modified: | 21 May 2013 | 
| Last Published: | 23 June 2012 | 
| First Published date: | 10 September 2011 | 
#Orbix
#KnowledgeDocs

