Re: SCHEDIRB Jon Perryman is correct re-linked as AC=1 no ABEND ON SVC 8

2023-10-31 Thread Doug Fuerst
have enough of this in the world these days? Can't we be decent and civil to each other? Is it really THAT difficult? Doug Fuerst -- Original Message -- From "Jon Perryman" To IBM-MAIN@LISTSERV.UA.EDU Date 10/31/2023 20:04:24 PM Subject Re: SCHEDIRB Jon Perryman i

Re: SCHEDIRB Jon Perryman is correct re-linked as AC=1 no ABEND ON SVC 8

2023-10-31 Thread Jon Perryman
On Tue, 31 Oct 2023 23:15:44 +, Doug Fuerst wrote: >I am not OK with any of it, and after Mr. Johnson, I suspect the list is >not as well. I'm also not ok with this but it's Crayford you should be calling out. By ignoring his insults the first couple of times, I showed far more respect and

Re: SCHEDIRB Jon Perryman is correct re-linked as AC=1 no ABEND ON SVC 8

2023-10-31 Thread Doug Fuerst
keep this civil and professional. Please? Doug Fuerst -- Original Message -- From "Jon Perryman" To IBM-MAIN@LISTSERV.UA.EDU Date 10/31/2023 19:06:25 PM Subject Re: SCHEDIRB Jon Perryman is correct re-linked as AC=1 no ABEND ON SVC 8 On Tue, 31 Oct 2023 21:53:36 +

Re: SCHEDIRB Jon Perryman is correct re-linked as AC=1 no ABEND ON SVC 8

2023-10-31 Thread Jon Perryman
On Tue, 31 Oct 2023 21:53:36 +, Doug Fuerst wrote: >Did we just trade Bill Johnson for Jon Perryman? Are you two related? We >are back to backbiting and insults. >Can we just stop? If I'm showing a pattern of being confused or being constantly wrong (as claimed by Crayford), please show me

Re: SCHEDIRB Jon Perryman is correct re-linked as AC=1 no ABEND ON SVC 8

2023-10-31 Thread Doug Fuerst
Did we just trade Bill Johnson for Jon Perryman? Are you two related? We are back to backbiting and insults. Can we just stop? Doug Fuerst -- Original Message -- From "Jon Perryman" To IBM-MAIN@LISTSERV.UA.EDU Date 10/31/2023 17:34:02 PM Subject Re: SCHEDIRB Jon P

Re: SCHEDIRB Jon Perryman is correct re-linked as AC=1 no ABEND ON SVC 8

2023-10-31 Thread Jon Perryman
On Fri, 29 Sep 2023 14:35:45 +, Peter Relson wrote: > As this related to a purported need to link with AC=1, > I was perfectly sure that that was not correct. And I remain so. Is it truly a coincidence that this group failed in 1 week to solve a simple SCHEDIRB and LOAD failing when shortly

Re: SCHEDIRB

2023-10-05 Thread Joseph Reichman
Thanks I have verified the IRB ran to completion while at a test breakpoint in the originating TCB the IRB ran under IKJEFT01 on a different cpu > On Oct 4, 2023, at 10:56 PM, Jon Perryman wrote: > > On Mon, 2 Oct 2023 16:18:24 -0400, Joseph Reichman > wrote: > >> Do suggest when schedulin

Re: SCHEDIRB

2023-10-04 Thread Jon Perryman
On Mon, 2 Oct 2023 16:18:24 -0400, Joseph Reichman wrote: >Do suggest when scheduling an Async IRB I have a Wait/Post Joseph, yes you need to wait/post because an async IRB only serializes on 1 TCB (TCB with the IRB). If you do use WAIT, then you should implement recovery in the IRB. While i

Re: SCHEDIRB

2023-10-04 Thread Binyamin Dissen
On Wed, 4 Oct 2023 12:06:15 + Seymour J Metz wrote: :>Peter: is there a redbook that discusses the role of the IRB, or, more generally, a document suitable for citing on Wikipedia that discusses the RB types in lay terms? Not Peter, but I have used IRBs in two cases. (1) In SRB mode, but

Re: SCHEDIRB

2023-10-04 Thread Seymour J Metz
? From: IBM Mainframe Discussion List on behalf of Jon Perryman Sent: Tuesday, October 3, 2023 10:19 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SCHEDIRB On Mon, 2 Oct 2023 16:18:24 -0400, Joseph Reichman wrote: >Do suggest when scheduling an Async IRB I have a Wait/Post I only k

Re: SCHEDIRB

2023-10-04 Thread Peter Relson
>does the SCHEDIRB wait for IRB completion? No. Any coordination between the scheduler of the IRB and the IRB routine itself is up to the scheduler and IRB routine to provide. Peter Relson z/OS Core Technology Design -- For

Re: SCHEDIRB

2023-10-04 Thread Binyamin Dissen
No, it does not. On Tue, 3 Oct 2023 21:19:58 -0500 Jon Perryman wrote: :>On Mon, 2 Oct 2023 16:18:24 -0400, Joseph Reichman wrote: :>>Do suggest when scheduling an Async IRB I have a Wait/Post :>I only know the basics about IRB because none of the products I've worked on use it. Is async f

Re: SCHEDIRB

2023-10-03 Thread Jon Perryman
On Mon, 2 Oct 2023 16:18:24 -0400, Joseph Reichman wrote: >Do suggest when scheduling an Async IRB I have a Wait/Post I only know the basics about IRB because none of the products I've worked on use it. Is async for the address space or for the TCB? In other words, does the SCHEDIRB wait for

Re: SCHEDIRB

2023-10-02 Thread Joseph Reichman
Do suggest when scheduling an Async IRB I have a Wait/Post > On Sep 29, 2023, at 4:16 AM, Binyamin Dissen > wrote: > > On Thu, 28 Sep 2023 20:37:02 -0500 Jon Perryman wrote: > > :>Another problem with your code dawned on me. Your IRB routine and passed > storage could be freed while the IR

Re: SCHEDIRB

2023-10-02 Thread Leonard D Woren
Joseph Reichman wrote on 9/28/2023 5:25 PM: I pointing to the first that would be IKJEFT01 Most of the time.  But not on _my_ typical TSO sessions.  And since I'm using an IBM program for this, other sites would also be using it.  If I remember when I'm working I'll go check where T01 is in t

Re: SCHEDIRB Jon Perryman is correct re-linked as AC=1 no ABEND ON SVC 8

2023-09-29 Thread Joseph Reichman
Looking into it now > On Sep 29, 2023, at 10:36 AM, Peter Relson wrote: > >  >> >> even Peter Relson wasn't sure if this correct > > As this related to a purported need to link with AC=1, I was perfectly sure > that that was not correct. And I remain so. > > Joe R: you've mentioned multipl

Re: SCHEDIRB Jon Perryman is correct re-linked as AC=1 no ABEND ON SVC 8

2023-09-29 Thread Peter Relson
> even Peter Relson wasn't sure if this correct As this related to a purported need to link with AC=1, I was perfectly sure that that was not correct. And I remain so. Joe R: you've mentioned multiple times that you abended after the load. But did you ever share what abend code and abend reason

Re: SCHEDIRB

2023-09-29 Thread Seymour J Metz
TSO/E added, e.g. authorized commands, and ATTACH RSAPF=YES tests for AC(1). From: IBM Mainframe Discussion List on behalf of Michael Stein Sent: Friday, September 29, 2023 1:07 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SCHEDIRB On Thu, Sep 28, 2023

Re: SCHEDIRB

2023-09-29 Thread Binyamin Dissen
On Thu, 28 Sep 2023 20:37:02 -0500 Jon Perryman wrote: :>Another problem with your code dawned on me. Your IRB routine and passed storage could be freed while the IRB is still executing. The IRB routine only does a LOAD but the I/O time could be long enough for the originating program to end a

Re: SCHEDIRB

2023-09-28 Thread Michael Stein
On Thu, Sep 28, 2023 at 08:37:02PM -0500, Jon Perryman wrote: > I don't have access to z/OS. Joseph, can you run a simple test to > find out if this is a problem because others say it's not. Assemble, > link (with AC=1) and run from JCL the following prog: Unless something major has changed (which

Re: SCHEDIRB

2023-09-28 Thread Jon Perryman
On Thu, 28 Sep 2023 01:30:05 -0400, Joseph Reichman wrote: Another problem with your code dawned on me. Your IRB routine and passed storage could be freed while the IRB is still executing. The IRB routine only does a LOAD but the I/O time could be long enough for the originating program to en

Re: SCHEDIRB

2023-09-28 Thread Joseph Reichman
ace. > > > From: IBM Mainframe Discussion List on behalf > of Joseph Reichman > Sent: Thursday, September 28, 2023 7:42 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: SCHEDIRB > > Thanks > > Again, for getting back went

Re: SCHEDIRB

2023-09-28 Thread Seymour J Metz
There are at least two jobstep TCBs in your address space. From: IBM Mainframe Discussion List on behalf of Joseph Reichman Sent: Thursday, September 28, 2023 7:42 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SCHEDIRB Thanks Again, for getting back

Re: SCHEDIRB

2023-09-28 Thread Joseph Reichman
MP does that. > > > From: IBM Mainframe Discussion List on behalf of > Joseph Reichman > Sent: Thursday, September 28, 2023 9:14 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: SCHEDIRB > > I did get an abend after SVC 8 in the code that ran th

Re: SCHEDIRB

2023-09-28 Thread Seymour J Metz
AC(1) is only relevant with ATTACH RSAPF=YES, and AFAIK nobody but the Initiayor and the TMP does that. From: IBM Mainframe Discussion List on behalf of Joseph Reichman Sent: Thursday, September 28, 2023 9:14 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re

Re: SCHEDIRB Jon Perryman is correct re-linked as AC=1 no ABEND ON SVC 8

2023-09-28 Thread Joseph Reichman
Jon Kudos to you even Peter Relson wasn’t sure if this correct -Original Message- From: IBM Mainframe Discussion List On Behalf Of Jon Perryman Sent: Wednesday, September 27, 2023 10:00 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SCHEDIRB On Tue, 19 Sep 2023 20:29:52 -0400

Re: SCHEDIRB

2023-09-28 Thread Binyamin Dissen
On Thu, 28 Sep 2023 11:48:37 -0400 Joseph Reichman wrote: :>I known that if I am running TESTAUTH and I do the test LOAD subcommand and the pds(member) is not from an APF authorized library I get a nasty message from TEST LOAD from non-APF when APF is not allowed. Integrity violation. 306-C ab

Re: SCHEDIRB

2023-09-28 Thread Joseph Reichman
I known that if I am running TESTAUTH and I do the test LOAD subcommand and the pds(member) is not from an APF authorized library I get a nasty message from TEST > On Sep 28, 2023, at 11:40 AM, Binyamin Dissen > wrote: > > On Thu, 28 Sep 2023 07:42:37 -0400 Joseph Reichman > wrote: > >> On

Re: SCHEDIRB

2023-09-28 Thread Binyamin Dissen
On Thu, 28 Sep 2023 07:42:37 -0400 Joseph Reichman wrote: >One more idea you said TSO does SVC screening which is why my LOAD abended I have written programs that did SVC screening, including setting up screening before invoking the TMP. Never saw that TSO did SVC screening, and there should mo

Re: SCHEDIRB

2023-09-28 Thread Joseph Reichman
I did get an abend after SVC 8 in the code that ran the IRB the module was not linked AC=1 > On Sep 28, 2023, at 9:11 AM, Peter Relson wrote: > > Jon P wrote > > I believe that LOAD will abend if the module is not linked with the AC=1 > attribute when running authorized. > > > It will no

Re: SCHEDIRB

2023-09-28 Thread Peter Relson
Jon P wrote I believe that LOAD will abend if the module is not linked with the AC=1 attribute when running authorized. It will not. You should have AC=1 only for a module that is the target of something akin to EXEC PGM= (i.e., the jobstep program). It's easier to obey this rule than to ensu

Re: SCHEDIRB

2023-09-28 Thread Joseph Reichman
Michael Stein Sent: Thursday, September 28, 2023 2:12 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SCHEDIRB On Thu, Sep 28, 2023 at 01:30:05AM -0400, Joseph Reichman wrote: > Thanks > > The one glaring thing that was happening was that load was indeed > abending you said linking it wit

Re: SCHEDIRB

2023-09-27 Thread Michael Stein
On Thu, Sep 28, 2023 at 01:30:05AM -0400, Joseph Reichman wrote: > Thanks > > The one glaring thing that was happening was that load was indeed > abending you said linking it with ac=1 would solve that issue No, but it needs to come from an authorized library. > I don't understand your suggest

Re: SCHEDIRB

2023-09-27 Thread Joseph Reichman
Thanks The one glaring thing that was happening was that load was indeed abending you said linking it with ac=1 would solve that issue I don’t understand your suggestion about doing a storage obtain and load to the obtained area isn’t storage also tied into the TCB ? And your suggestion abou

Re: SCHEDIRB

2023-09-27 Thread Michael Stein
On Wed, Sep 27, 2023 at 09:00:13PM -0500, Jon Perryman wrote: > 4. I believe that LOAD will abend if the module is not linked with >the AC=1 attribute when running authorized. No, it has to be in an authorized library. Only the EXEC PGM= name needs AC=1 (TSO APF in addtion needs to be in some

Re: SCHEDIRB

2023-09-27 Thread Jon Perryman
On Tue, 19 Sep 2023 20:29:52 -0400, Joseph Reichman wrote: > Source code below. Sorry for chiming in so late but I've had other priorities. I think you're being led down the wrong path. A 30 second glance at your code shows obvious coding errors. SRB and IRB are the the real danger. Running k

Re: SCHEDIRB with CIRB

2023-09-22 Thread Michael Stein
On Fri, Sep 22, 2023 at 04:50:23PM -0400, Joseph Reichman wrote: > Micheal > > Thanks for looking at it I see 8E76D0 at IQETCB Oh, I mangled it when aliging the hex data, the 0s are from the 64 bit address high word... -- For I

Re: SCHEDIRB with CIRB

2023-09-22 Thread Joseph Reichman
0 ** -Original Message- From: IBM Mainframe Discussion List On Behalf Of Michael Stein Sent: Friday, September 22, 2023 4:22 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SCHEDIRB with CIRB On Fri, Sep 22, 2023 at 01:58:00PM -0400, Joseph Reichman

Re: SCHEDIRB with CIRB

2023-09-22 Thread Michael Stein
On Fri, Sep 22, 2023 at 01:58:00PM -0400, Joseph Reichman wrote: > I am posting my code in addition to some displays I captured as I am getting > the feeling my IRB was not dispatched for some reason > > So here is the code in my STIMER routine from where I issue the SCHEDIRB > pointing to the IQ

Re: SCHEDIRB getting real close showing the code

2023-09-20 Thread Joseph Reichman
It didn’t seem to work that way Ep= didn’t equal RBEPA RBEPA documented in the data areas Manuel At location +C from RBBASIC say entry point of irb routine in fact the last digit was odd The cirb is running amode 31 I’ll re-read again But and set a breakpoint after the the cirb And loo

Re: SCHEDIRB getting real close showing the code

2023-09-20 Thread Michael Stein
On Wed, Sep 20, 2023 at 06:00:06PM -0400, Joseph Reichman wrote: > I decided to use the CIRB macro so that way I could build my own IRB > > The problem seems to be the AMODE of my RBOPSW is 24 so the high order > byte of my rbepa gets chopped off RPEPA doesn't belong to you, you should not to

Re: SCHEDIRB with a timer

2020-08-05 Thread Seymour J Metz
...@listserv.ua.edu] Sent: Wednesday, August 5, 2020 1:35 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SCHEDIRB with a timer The IRB will be driven the next time the task gets interrupted... note that SCHEDULEing the IRB does not in itself cause the interrupt that drives the IRB. If the task was

Re: SCHEDIRB with a timer

2020-08-05 Thread Adam Johanson
The IRB will be driven the next time the task gets interrupted... note that SCHEDULEing the IRB does not in itself cause the interrupt that drives the IRB. If the task was already WAITing, however, the IRB will run. == Adam Johanson R&D Software Engineer adam.johan...@br

Re: SCHEDIRB with a timer

2020-08-05 Thread Joseph Reichman
Thanks > On Aug 5, 2020, at 1:38 PM, mike.lamartina > wrote: > > STIMERM supports a parameter. > > On 8/5/2020 10:13:48 AM, Joseph Reichman wrote: > Hi > > > > I am looking for an exit that will be executed after a time interval, > in addition I need a parameter. The SCHEDIRB gives the

Re: SCHEDIRB with a timer

2020-08-05 Thread mike.lamartina
STIMERM supports a parameter. On 8/5/2020 10:13:48 AM, Joseph Reichman wrote: Hi I am looking for an exit that will be executed after a time interval, in addition I need a parameter. The SCHEDIRB gives the parameter but I am not quite sure when it will execute Looking at the data area manua