Not sure if this will work.... but...
Can you use DMSCALLER to "look back" to see who called you... do that
repeatedly (looking further and further back) until you:
A - find the origin of the universe you currently know
or
B - find VMSTART
You would only need to do this one time when your program starts, then
set your own flag for other parts to check as needed.
Or.... (untested), try calling an MT function (that actually requires
MT).... if it works, you're MT; if not, you're not. (Might need an ESPIE
or similar routine to "catch" an abend.)
Gillis, Mark wrote:
Unfortunately, not applicable to what I'm doing - the module where I'm
doing this is CMSCALL'd by a client application, so it's not linked in,
and I need to maintain backward compatibility, so it needs to stay that
way.
Good idea, though.
Mark Gillis
Senior Software Engineer
Tel: +61 2 9429 2337
Fax: +61 2 9429 2394
[EMAIL PROTECTED]
-----Original Message-----
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Alan Altmark
Sent: Tuesday, 10 July 2007 10:59 AM
To: [email protected]
Subject: Re: How to determine if running as a multitasking CMS app
On Tuesday, 07/10/2007 at 10:16ZE10, "Gillis, Mark" <[EMAIL PROTECTED]>
wrote:
In case anyone?s interested, I raised this with IBM. Their response
was
that
testing NUCMTDSP wouldn?t work, the only way possible being to run the
CMS
control blocks. Unfortunately, these control blocks have the note?This
information is NOT intended to be used as Programming Interfaces of
z/VM?
? which makes me a little uneasy about doing it this way. I guess it?s
all
there is, though.
I have some assembler code that can run with C or Pascal (called prior
to
entering the "real" module). I put in a WXTRN for CEESTART and VSPASCAL
in order to figure out whether it is running in an LE environment or
not.
Could you put in a WXTRN for VMSTART? If the adcon is non-zero, then
VMSTART was linked.
Alan Altmark
z/VM Development
IBM Endicott
