Re: Refresh my memory: is there some sort of unstructured object that's cheap to create, and can automatically expand?
Dave McKenzie <[email protected]>
| Newsgroups | gmane.comp.lang.as400.mi |
|---|---|
| Message-ID | <[email protected]> |
I've used *USRQ's in QTEMP, and the only "gotcha" I remember was that *USRQ's are limited in size to about 24 MB. That shouldn't normallly be a problem, but in our application, we could exceed 24 MB on vary rare occasions. We had to build homemade queues out of multiple *USRSPC's (and a *USRIDX if it required keys). The 24 MB number seems very strange. Usually objects are limited to some multiple of 16 MB (the size of a segment group). E.g. *USRSPC's are limited to 16 MB because they are designed to consist of just one segment group. I never dug in deep enough to find why the 24 MB limit. --Dave James H H Lampert wrote: > Dave McKenzie <[email protected]> wrote: >> Since you mentioned FIFO access, you may also be thinking of a User >> Queue, which you can create with the QUSCRTUQ API, and access with ENQ >> and DEQ/DEQWAIT instructions (in MI or C). > > Thanks. I'd forgotten the somewhat convoluted way in which *USRSPCs can > be made self-expansile, and I've never used a *USRQ. > > Are there any known V5 "gotchas" regarding *USRQs in QTEMP? > > -- > JHHL > _______________________________________________ This is the MI Programming on the AS400 / iSeries (MI400) mailing list To post a message email: MI400-Zwy7GipZuJhWk0Htik3J/[email protected] To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/mi400 or email: MI400-request-Zwy7GipZuJhWk0Htik3J/[email protected] Before posting, please take a moment to review the archives at http://archive.midrange.com/mi400.