Yeah, it looks like the 2nd parameter might have to be BYVAL, as it is declared as int in the H source file in QSYSINC. When did BYVAL come into play in CL?

Vern

On 3/2/2021 4:46 PM, Larry "DrFranken" Bolhuis wrote:
I think with i 7.3 and above maybe even 7.2 you can call pretty much all of the APIs. New variable types including pointers and such enabled that. You will have to compile as CLLE but then that's not bad anyway. :-)
-Dr F

On 3/2/2021 5:01 PM, Vern Hamberg wrote:
This can be done in CL very easily, this might be a repeat of someone else's post.

Basically, the information from QWDRSBSD comes back in a receiver variable that is just one of the parameters. Status is at position 29, I think, a 10-character field there, either *ACTIVE or *INACTIVE. I think I saw someone say it was format SBSD0100 - that's the least information.

You CAN call APIs from CL - not all, necessarily, but many of the simpler ones, sure. This looks like one of those. It's just a program call in this case, no special stuff like user spaces and all that.

Regards
Vern

On 3/2/2021 2:56 PM, PaulMmn wrote:
This isn't CL, and it does use an API (but does not require a user space).  I put this together in 1996 or so...  We were going to totally automate our week-end IPL.  That never happened, but some useful pieces survived.

QWDRSBSD API was introduced in V2R1...

--Paul E Musselman

.

At 8:55 AM -0800 3/2/21, James H. H. Lampert wrote:
I'll admit that I haven't done more than a cursory look at the CMDJOB and CMDSBS menus (and even that only on our V4R4 box, even though the box I'm asking this for is on V7), but short of an API call, can a CL program easily check to see if a given subsystem is active?

--
JHHL





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.