Re: LXRES best practices

Wayne Driscoll > Rocket Software > Note - All opinions are strictly my own. > > -Original Message- > From: IBM Mainframe Discussion List On Behalf Of > Joseph Reichman > Sent: Thursday, December 6, 2018 6:49 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: LXRE

Re: LXRES best practices

List On Behalf Of Joseph Reichman Sent: Thursday, December 6, 2018 6:49 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: LXRES best practices Wasn’t aware that name/token was valid across an ipl > On Dec 6, 2018, at 1:35 AM, Ed Jaffe wrote: > >> On 11/29/2018 5:17 AM, Joseph Reichman

Re: LXRES best practices

AFAIK it's not. If so, please educate me. Mark Jacobs Joseph Reichman wrote on 12/6/18 7:48 AM: Wasn’t aware that name/token was valid across an ipl > On Dec 6, 2018, at 1:35 AM, Ed Jaffe > wrote: > >> On 11/29/2018 5:17 AM, Joseph Reichman wrote: >> I am

Re: LXRES best practices

Wasn’t aware that name/token was valid across an ipl > On Dec 6, 2018, at 1:35 AM, Ed Jaffe wrote: > >> On 11/29/2018 5:17 AM, Joseph Reichman wrote: >> I am using s system LX but with our re-usable I would have to save the LX to >> a file >> Right ? If I restart the task right ? > > I

Re: LXRES best practices

On 11/29/2018 5:17 AM, Joseph Reichman wrote: I am using s system LX but with our re-usable I would have to save the LX to a file Right ? If I restart the task right ? I would not use a file. you might try to use an old LX across an IPL. I suggest common storage. Are you familiar with

Re: LXRES best practices copy of the link

https://share.confex.com/share/124/webprogram/Handout/Session17096/SHARE_Seattle_2015_Storage.pdf > On Dec 1, 2018, at 1:13 PM, scott Ford wrote: > > How can I get a copy of your presentation Peter? It would be appreciated by > this ‘mere’ padawn.. > > Regards, > Scott > > On Sat, Dec 1,

Re: LXRES best practices

So On restart I need to do everything but LXRES the linkage number is still valid meaning I need to do the following three ETDEF,ETCRE and ETCON and the ETCON uses the saved linkage number correct ? On Dec 1, 2018, at 9:10 AM, Peter Relson wrote: >> the regular LX is easier as I only

Re: LXRES best practices

How can I get a copy of your presentation Peter? It would be appreciated by this ‘mere’ padawn.. Regards, Scott On Sat, Dec 1, 2018 at 9:12 AM Peter Relson wrote: > >the regular LX is easier as I only need I register to PC > > That strikes me as the wrong attitude. This is authorized code. You

Re: LXRES best practices

>the regular LX is easier as I only need I register to PC That strikes me as the wrong attitude. This is authorized code. You should also be considering what is best for the system (and the rest of the users within the system), not only what is easiest. >If my started task goes down and I

Re: LXRES best practices

I am sorry I should of thought this out better If my started task goes down And I restart it the virtual address in private of the PC routine would be different isn’t that An issue Thanks Joe Reichman 170-10 73 rd ave Fresh meadows NY 11366 > On Nov 30, 2018, at 7:36 AM, Peter Relson

Re: LXRES best practices

Okay thanks the regular LX is easier as I only need I register to PC Joe Reichman 170-10 73 rd ave Fresh meadows NY 11366 > On Nov 30, 2018, at 7:36 AM, Peter Relson wrote: > > > I am using s system LX but with our re-usable I would have to save the LX > to a file > Right ? If I restart

Re: LXRES best practices

I am using s system LX but with our re-usable I would have to save the LX to a file Right ? If I restart the task right ? No. Whether reusable or not, you in effect save the LX because you need to build a PC number for programs to use. So you already must save it either as part of the PC

Re: LXRES best practices

I am using s system LX but with our re-usable I would have to save the LX to a file Right ? If I restart the task right ? > On Nov 29, 2018, at 8:10 AM, Peter Relson wrote: > > For non-system LX, reusable=yes is always better. > I agree with Rob that you might save the sequence number in the

Re: LXRES best practices

For non-system LX, reusable=yes is always better. I agree with Rob that you might save the sequence number in the same place that you save the LX for later use (or the PC number itself that you derive from the LX). For system LX, reusable=yes is not needed if you expect to restart and

Re: LXRES best practices

e you > store the PC number. > > -Original Message- > From: IBM Mainframe Discussion List On Behalf Of > Joseph Reichman > Sent: Wednesday, November 28, 2018 1:02 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: LXRES best practices > > Hi > > Just

Re: LXRES best practices

On Behalf Of Joseph Reichman Sent: Wednesday, November 28, 2018 1:02 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: LXRES best practices Hi Just went thru Peter Relson presentation Presentation ״Session 17096” on extended addressability My question is I guess it’s always better to use a r

LXRES best practices

Hi Just went thru Peter Relson presentation Presentation ״Session 17096” on extended addressability My question is I guess it’s always better to use a reusable LX With a sequence number That’s way if your server goes down the system can assign it to another process System Service such as