Re: dumb STORAGE OBTAIN question.

2019-06-10 Thread John McKown
On Sat, Jun 8, 2019 at 12:53 PM Jim Mulder wrote: > If you will have the storage fixed for a longer period of time than you > would want > a CONFIG STOR,OFFLINE to be delayed, then you should specify LONG=YES. > I all my years as a sysprog, back to OS/VS1, I have _never_ had the need to ta

Re: dumb STORAGE OBTAIN question.

2019-06-08 Thread Jim Mulder
If you will have the storage fixed for a longer period of time than you would want a CONFIG STOR,OFFLINE to be delayed, then you should specify LONG=YES. Similarly, in that case, you should use SYSEVENT TRANSWAP instead of SYSEVENT DONTSWAP to become nonswappable. Note that specifying FIX

Re: dumb STORAGE OBTAIN question.

2019-06-08 Thread Peter Relson
I am trying to avoid running key 0 or supervisor state to the extent possible Avoiding key 0 is nice. Avoiding supervisor state is less important. Unintended bad consequences of running with more privilege than absolutely needed are quite uncommon when the privilege is "supervisor state" (b

Re: dumb STORAGE OBTAIN question.

2019-06-07 Thread Charles Mills
ly exclusive. > LOCHIH REG,VALUE yes, load max Yeah, jumps are cache-killers. LOCxxx is goodness. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John McKown Sent: Friday, June 7, 2019 10:38 AM To: IBM-MAIN@LISTSERV.UA.EDU

Re: dumb STORAGE OBTAIN question.

2019-06-07 Thread John McKown
---Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of John McKown > Sent: Friday, June 7, 2019 9:58 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: dumb STORAGE OBTAIN question. > > On Fri, Jun 7, 2019 at 11:24 AM Charles Mills

Re: dumb STORAGE OBTAIN question.

2019-06-07 Thread Charles Mills
d I don't have the PoOp open in front of me, so perhaps I am off base.) Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John McKown Sent: Friday, June 7, 2019 9:58 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: dumb STORAGE

Re: dumb STORAGE OBTAIN question.

2019-06-07 Thread John McKown
harles > > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of John McKown > Sent: Friday, June 7, 2019 9:01 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: dumb STORAGE OBTAIN question. > > On Fri, Jun 7

Re: dumb STORAGE OBTAIN question.

2019-06-07 Thread Charles Mills
7, 2019 6:33 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: dumb STORAGE OBTAIN question. > > I know this is a dumb question in that the answer should obviously be "no > problem". I am messing around with rewriting MVSCPMCD. It currently does > PGFIX & PGFREE to fix and

Re: dumb STORAGE OBTAIN question.

2019-06-07 Thread John McKown
clear. I am doing the STORAGE OBTAIN,FIX=LONG to avoid doing the PGSER functions entirely. > > Charles > > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of John McKown > Sent: Friday, June 7, 2019 6:33 AM &

Re: dumb STORAGE OBTAIN question.

2019-06-07 Thread Charles Mills
, June 7, 2019 6:33 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: dumb STORAGE OBTAIN question. I know this is a dumb question in that the answer should obviously be "no problem". I am messing around with rewriting MVSCPMCD. It currently does PGFIX & PGFREE to fix and free the areas being c

dumb STORAGE OBTAIN question.

2019-06-07 Thread John McKown
I know this is a dumb question in that the answer should obviously be "no problem". I am messing around with rewriting MVSCPMCD. It currently does PGFIX & PGFREE to fix and free the areas being communicated to VM as required for the DIAGNOSE (Hypervisor call) instruction. I was rewriting the code t