× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Folks:

I found something interesting on my 7.1 system the other day.

I was doing some analysis of command objects in QSYS, using the QCDRCMDI api, and encountered a command that gave an error.

When I ran the QCDRCMDI api on the ADDBLDOPTE command, I got a CPF9810 indicating that the QBLDSYS library didn't exist.

So I looked in QSYS and there is a *CMD object for ADDBLDOPTE ... but it appears to be a proxy for a command of the same name in QBLDSYS. QBLDSYS, however, does not exist on my system.

----------
Target command . . . . . . . . . . . . : ADDBLDOPTE
Library . . . . . . . . . . . . . . : QBLDSYS
Text . . . . . . . . . . . . . . . . . :
Current proxy chain . . . . . . . . . : QSYS/ADDBLDOPTE
QBLDSYS/ADDBLDOPTE
----------

Anyone now why there would be a proxy command but no target command?

A bit more analysis returned a bunch more commands in a similar state. Most are pointing to QBLDSYS. Others are pointing to QSSP (we don't have the S/36 env installed, so that can 'kind of' be explained).

Thanks!

david


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.