× 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.



I'm getting weird stuff from QZRUCLSP API (call service program procedure).

Through the QZRUCLSP API, I'm calling procedure 'Qp0zSpawn' in service
program QSYS/QP0ZSPWN.  The batch-immediate job starts okay.  Several times
I call my program that invokes QZRUCLSP API, and each time the BCI job is
spawned okay.

But, if I do "STRDBG PGM(___)" on my program that calls QZRUCLSP API, end
the debugger, execute "ENDDBG" and "SIGNOFF", sign back on, and call my
program that calls QZRUCLSP API again, then 'Qp0zSpawn' fails and the BCI
job is not started.

Huh?  The only way to make QZRUCLSP API work again is if I delete my
program that calls QZRUCLSP API, recompile it and reexecute it.

It seems that starting ILE debug on my program that calls QZRUCLSP API that
calls 'Qp0zSpawn' somehow registers an address in the system that forever
breaks my program from working correctly again (even if my program isn't
executed in debug mode).  Sign off/sign on doesn't fix it.  The only way to
clear this breakage is to delete and recreate my program.

This is weird shit.  Can someone help me invoke 'Qp0zSpawn' without this
problem?

+---
| This is the MI Programmers Mailing List!
| To submit a new message, send your mail to MI400@midrange.com.
| To subscribe to this list send email to MI400-SUB@midrange.com.
| To unsubscribe from this list send email to MI400-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: dr2@cssas400.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.