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



MKirkpatrick@xxxxxxxxxxxxxxxxx wrote:
I have a CLP that starts the S36 environment via the STRS36PRC command. I want to now place this CLP into a S36 procedure. This causes a problem as this CLP will now try to STRS36PRC while already in the S36 environment. I have reviewed the RTVJOBA command but find
no attribute that tells me my environment. Any suggestions on how to
determine (in the CLP) if I am executing in the S36 environment?
Thanks.

The "Special environment" field for job information as retrieved using both the QUSRJOBI API [JOBI0600 Format] and QWTRTVTA API [Format RTVT0100 key 1908].

However I seem to recall that the STRS36PRC command, when invoked while a S/36 procedure is _running_ [not just because the S/36EE is active] will actually fail with an escape message that can be monitored. If so, the error could be monitored, and from that, inferred the request is not allowed; i.e. the command itself has done the work to determine the condition.? Maybe this is not relevant, because perhaps instead it was meant the CLP does STRS36; thus the desire is to prevent the CLP from sending the job to the S36EE menu?

For the definition of the Special Environment field:
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/apis/WMAttrDesc.htm

For the key API to retrieve the Special Environment value:
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/apis/qwtrtvta.htm

Regards, Chuck

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.