|
Simon, I think the asterisk in '*NONE' may be a problem as well; the CPP will not allow the asterisk on the object type (it expects "FILE', not '*FILE'). But that does not explain, why it did not dump at the check of the unknown object (the second call); there the CPP behaves normal. That amazes me. As this was just an experiment, I will lay it to rest. Besides, I find it strange that no one mentioned the Retrieve Object Desription API (QUSOBJD) to use instead. It was my assumption, that CHKOBJ worked with that API and if an object was not found send an escape message (which can be monitored). For those who contributed, thanks. Regards, Carel Teijgeler *********** REPLY SEPARATOR *********** On 28-8-02 at 22:53 Simon Coulter wrote: >I see that others have given you alternative solutions but no one has >explained your problem which is quite simple. You have code the fourth >parameter as: > > D Aut S 10 INZ('*NONE') > >but the command allows a list of up to 10 values for AUT. Since a CA >list is prefixed by a 2-byte count of the number of elements in the list >the QLICKOBJ program is interpreting the first 2 bytes of Aut as a >length. *N is x'5CD5' which is decimal 23765 which is much longer than >the space available hence you cause it to walk off the end of your >available storage. > >Define Aut as a structure, pass the DS, and it should work: > >D AutDS DS >D len 5I 0 INZ(1) >D aut 10 INZ('*NONE') > >C Call(E) 'QLICKOBJ' >C Parm Fullobj >C Parm InType ObjType >C Parm InMember Member >C Parm AutDS > >Also QLICKOBJ is a system domain program which means you cannot call it >from a non-system state program when QSECURITY is above 30. > >Also it is an undocumented interface and subject to change (although it >hasn't changed in years).
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.