Re: Non system LX value

2023-12-05 Thread Joseph Reichman
Sorry meant ETCRE > On Dec 5, 2023, at 8:55 AM, Joseph Reichman wrote: > > Got it I have to pass the token from ETCON returned in register 0 some how > to the client > > Thanks > >> On Dec 5, 2023, at 8:13 AM, Peter Relson wrote: >> >>  >> where you specify an asid indicating what address

Re: Non system LX value

2023-12-05 Thread Joseph Reichman
Got it I have to pass the token from ETCON returned in register 0 some how to the client Thanks > On Dec 5, 2023, at 8:13 AM, Peter Relson wrote: > >  > where you specify an asid indicating what address space you want to provide > this service to > > > You don't "specify". You provide a

Re: Non system LX value

2023-12-05 Thread Peter Relson
where you specify an asid indicating what address space you want to provide this service to You don't "specify". You provide a way for the connector to issue ETCON. This is all very well described in the extended addressability guide. Peter Relson z/OS Core Technology Design

Re: Non system LX value

2023-12-04 Thread Binyamin Dissen
You need an authorized routine that can run in the client address space to issue the ATSET. On Mon, 4 Dec 2023 08:19:38 -0500 Joseph Reichman wrote: :>Hi :> :>I have been looking over syncrounes cross memory or PC rtn’s :> :>What I seem to be missing is where you want to make that service

Non system LX value

2023-12-04 Thread Joseph Reichman
Hi I have been looking over syncrounes cross memory or PC rtn’s What I seem to be missing is where you want to make that service available to certain address spaces So you code on the LXRES SYSTEM=NO But I don’t see any where where you specify an asid indicating what address space you