|
I was thinking he'd do:
CHKOBJ OBJ(*LIBL/&CMDNAME) OBJTYPE(*CMD)
And if it failed (i.e. didn't find a command with that name) he'd simply
ASSUME it was an S/36 proc.
Jerry Adams wrote:
Couple of things. First, CHKOBJ may be problematic against 36--
"commands." As you probably know, these are really source members,
not objects, that reside in the QS36PRC source physical file. I just
ran a test of CHKOBJ using *LIBL and, if the procedure/command (which
does exist in the library) is not in the first source PF, CHKOBJ
returns a 'not found' error. So you will have to know the specific
library or, as in my test, use *CURLIB if the procedure is supposed
to be there.
Second, are these really always going to be *CMD objects or might
they be CL *PGM objects from time-to-time?
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.