"RETAIN" here actually means "leave the volume mounted on the device, and
unwound"...pending possible further usage in one of the next jobsteps...
On Fri, 9 Nov 2018 23:25:06 -0500, Tony Thigpen wrote:
.
.
>Position 1 can be:
>Blank = Verify
>M = Mount
>D = Demount
>K = Keep (put in rack)
>R =
Yup.. should be SMF30PF1 that "1" and "I" look pretty close at the font size I
had up.
Scott
On Fri, 9 Nov 2018 07:16:03 -0600, Elardus Engelbrecht
wrote:
>Sorry, but is it not SMF30PF1 (number one instead of letter i)?
--
Given the choice of using the SSAR instruction with a ALET of 1
And adding a access list entry via ALESERV which is the preferred method
I do not accept the conditions of contest. Neither is an acceptable method
in general.
You might not have authorization to SSAR. And a target address space
You don't know -- it might have been 18 MB of brilliant functionality.
Seriously, one other thing I forgot to mention. This used to work. I know I
have done a "practice" distro using a debug build. But the debug build must
have grown from < to > 16 MB in the interim.
Charles
-Original Me
What is this load module written?
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Ed Jaffe
Sent: Friday, November 9, 2018 10:53 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: IGW01203E MEMBER EXCEEDS LIMITATIONS FOR PDS LOAD
The recommended method for accessing secondary address spaces is to have a
valid cross memory bind that permits it, for example PC-ss or spawned ASID via
ASCRE.
Do NOT use CHKEAX=NO on ALESERV
On 9 Nov 2018 18:13, Joseph Reichman wrote:
Hi
Given the choice of using the SSAR instruction with a
I think for SSAR I might need to set the AX value to 1
Via AXSET macro correct ?
> On Nov 10, 2018, at 8:43 AM, Peter Relson wrote:
>
>
> Given the choice of using the SSAR instruction with a ALET of 1
> And adding a access list entry via ALESERV which is the preferred method
>
>
> I do n
It might help matters if you outline what you are trying to achieve.
On 10 Nov 2018 22:38, Joseph Reichman wrote:
I think for SSAR I might need to set the AX value to 1
Via AXSET macro correct ?
> On Nov 10, 2018, at 8:43 AM, Peter Relson wrote:
>
>
> Given the choice of using the SSAR ins
I’m writing windows front end to display system info from a z/os system. The
program getting the info is a Assembler z/os TCP/IP server
Certain information such as executing program name ACEE is in not in common
As for swappable issues my Estae can catch the s0c4 and bypass that address
space
As Peter mentioned, there is no reason for either SSA(I)R or adding the ALET.
The ALET 1 is useable as it is. Simply LAM it into the AR and go AR mode.
What is the issue you are trying to solve?
On Sat, 10 Nov 2018 17:37:50 -0500 Joseph Reichman
wrote:
:>I think for SSAR I might need to set the
Unless I missing something I have to set the secondary address space in order
to use an alet of 1
> On Nov 10, 2018, at 6:52 PM, Binyamin Dissen
> wrote:
>
> As Peter mentioned, there is no reason for either SSA(I)R or adding the ALET.
> The ALET 1 is useable as it is. Simply LAM it into the
There is no real supported way to access private storage in another address
space uninvited.
The general consensus amongst developers, typically ISVs, who are confronted
with this requirement is to schedule a SRB into the target ASID and use some
sort of shared memory buffer to relay the inform
On Sat, 10 Nov 2018 18:45:03 -0500 Joseph Reichman
wrote:
:>Im writing windows front end to display system info from a z/os system. The
program getting the info is a Assembler z/os TCP/IP server
:>Certain information such as executing program name ACEE is in not in common
Ah, you want to exam
13 matches
Mail list logo
