Hi,
Would anyone know what DEFINED IOON is in regards to DSPSERV.
BACK=64,BACK=31
Thankx
Sent from my iPhone
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu
I believe that I have gleaned a fair idea. I referenced the Authorized
Assembler Services Reference Volume 1 and DSPSERV in SYS1.MACLIB
The virtual data space must be backed by real storage and the addressability of
the real storage frames (above or below 2GB) is somewhat dependent upon whether
IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu wrote on 09/28/2010
02:41:27 PM:
I believe that I have gleaned a fair idea. I referenced the
Authorized Assembler Services Reference Volume 1 and DSPSERV in
SYS1.MACLIB
The virtual data space must be backed by real storage
] On Behalf Of
Starr, Alan
Sent: Tuesday, September 28, 2010 1:41 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: DSPSERV defined IOON
I'm pretty sure that the new MIDAWs are usually required to access real frames
above 2GB and I'd guess that most of the standard access methods aren't using
MIDAWs yet
Hi,
I would like to allocate memory in Common Data Space with DSPSERV Macro and
my requirement is that Data Space survive my Address Space Termination. That
means it remains allocatad after my AS ends and other Address Spaces or an
Exit-Routine can access it.
One of my trial was, to allocate
@BAMA.UA.EDU
Subject: DSPSERV
Hi,
I would like to allocate memory in Common Data Space with DSPSERV Macro and my
requirement is that Data Space survive my Address Space Termination. That means
it remains allocatad after my AS ends and other Address Spaces or an
Exit-Routine can access it.
One
On Wed, 25 Jul 2007 10:08:49 +0200 Gabor Hoffer [EMAIL PROTECTED]
wrote:
:My program (EventMonitor, EM) installs an ExitModul under IEFU83 and IEFU84
:Exit. The Code and Buffer (for SMF-Records that are collectet with Exit) are
:in ECSA. Exit and EM communicates with ECB and exchange data over
Rob,
My program (EventMonitor, EM) installs an ExitModul under IEFU83 and IEFU84
Exit. The Code and Buffer (for SMF-Records that are collectet with Exit) are
in ECSA. Exit and EM communicates with ECB and exchange data over ECSA.
There are 2 request on this architecture:
1. Able to end
As a mentioned I'm not expert in SRBs and I'm learning MVS system
programming. I'v looked for SRBs in books. If i understand it correct, i can
let an Address Space to run a code in my Address Space. Is it ok?
Gabor
ps: i did'nt ask you to code it for me.
I already told you - look up SRBs.
Gabor
One way to do it is schedule an SRB into *MASTER* and that SRB performs the
DSPSERV CREATE with TTOKEN.
However, I would still advise against this for the following reasons :
(1) There is a simpler and safer solution.
(2) It is very likely that at some point you will cause problems
On Wed, 25 Jul 2007 10:44:19 +0200 Gabor Hoffer [EMAIL PROTECTED]
wrote:
:As a mentioned I'm not expert in SRBs and I'm learning MVS system
:programming. I'v looked for SRBs in books. If i understand it correct, i can
:let an Address Space to run a code in my Address Space. Is it ok?
True. But
have a lot of learning to do.
Gabor
On 7/25/07, Rob Scott [EMAIL PROTECTED] wrote:
Gabor
One way to do it is schedule an SRB into *MASTER* and that SRB performs
the DSPSERV CREATE with TTOKEN.
However, I would still advise against this for the following reasons :
(1) There is a simpler
True. But much more. It allows any address space to schedule work to be run
in
a different address space.
Thanks. I'll try it, but not with *MASTER*. ;-) There is a good example in
book Advanced Assembler Language and MVS Interfaces
Gabor
for a non-trivial period of time the
real frames backing the CADS will just keep increasing and you will not be very
popular . DSPSERV RELEASE can be used to return unused resources back to the
system.
Good luck
Rob Scott
Rocket Software, Inc
275 Grove Street
Newton, MA 02466
617-614-2305
[EMAIL
Gabor
Wouldnt this design be much cleaner by starting a second address space
whose
sole purpose is to own the dataspace ?
Basically it would contain all the Data Space Code to initialize/create
and destroy the dataspace and a Console Routine to stop this Address
space.
Granted not as
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Paul D'Angelo
Sent: Wednesday, July 25, 2007 7:15 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: DSPSERV
Gabor
Wouldnt this design be much cleaner by starting a second address space
On Wed, 25 Jul 2007 08:09:42 -0600 Jeffrey D. Smith
[EMAIL PROTECTED] wrote:
: -Original Message-
: From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
: Behalf Of Paul D'Angelo
: Sent: Wednesday, July 25, 2007 7:15 AM
: To: IBM-MAIN@BAMA.UA.EDU
: Subject: Re: DSPSERV
Rob Scott wrote:
By the way, I applaud your decision to convert ECSA usage to a CADS - that is a
sensible solution.
Personally, I don't like SCOPE=COMMON data spaces (CADS). Exceeding
MAXCAD requires an IPL. (The default is 50.) And, don't forget the
maximum number of entries in a
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: DSPSERV
Rob Scott wrote:
By the way, I applaud your decision to convert ECSA usage to a CADS - that is
a sensible solution.
Personally, I don't like SCOPE=COMMON data spaces (CADS). Exceeding MAXCAD
requires an IPL. (The default is 50.) And, don't forget
-Original Message-
From: IBM Mainframe Discussion List
[mailto:[EMAIL PROTECTED] On Behalf Of Rob Scott
Sent: Wednesday, July 25, 2007 10:49 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: DSPSERV
Ed
I thought that a CADS approach to intercepting SMF records
was appropriate
--snip
I'm likely insane, but I'd like to see some common storage like [E]CSA
in the above the bar area. Simple SAM64 to switch to AMODE(64), store
the data, then SAMxx to go back to 31 or 24 bit amode.
-unsnip---
On Wed, 25 Jul 2007 11:30:44 -0500, Mark Zelden wrote:
There's just a tad bit of virtual storage up there to use. By default it
is 510T. ;-) But for a vendor to use it, they must ensure a minimum
OS level of z/OS 1.5. Since 1.6 EOS is September, developing something
new that uses shared
Mark Zelden wrote:
On Wed, 25 Jul 2007 10:56:00 -0500, McKown, John
[EMAIL PROTECTED] wrote:
I'm likely insane, but I'd like to see some common storage like [E]CSA
in the above the bar area. Simple SAM64 to switch to AMODE(64), store
the data, then SAMxx to go back to 31 or 24 bit amode.
On Wed, 25 Jul 2007 10:56:00 -0500, McKown, John
[EMAIL PROTECTED] wrote:
I'm likely insane, but I'd like to see some common storage like [E]CSA
in the above the bar area. Simple SAM64 to switch to AMODE(64), store
the data, then SAMxx to go back to 31 or 24 bit amode.
There's just a tad bit
On Wed, 25 Jul 2007 11:51:32 -0500, Tom Schmidt
[EMAIL PROTECTED] wrote:
On Wed, 25 Jul 2007 11:30:44 -0500, Mark Zelden wrote:
There's just a tad bit of virtual storage up there to use. By default it
is 510T. ;-) But for a vendor to use it, they must ensure a minimum
OS level of z/OS 1.5.
25 matches
Mail list logo
