Re: LE question

This particular exit only looks at the commands issued (from consoles or jobs, etc.) so the overhead is pretty small. I wanted to do a lot of optional work at the time though so it made more sense to code things so that they told me what to look at and I only looked at those commands (instead

Re: LE question

Brian, I would agree it must be a lot of overhead looking at everything and then having the code make the decision on what to do. Especially in a System exit. Scott On Thu, May 16, 2019 at 12:19 AM Brian Westerman < brian_wester...@syzygyinc.com> wrote: > HI, > > ALL commands issued at a

Re: Saving in memory data in case of operator cancel was Re: LE question

Peter/Clark, Since we are a ISV, we try to intervene ourselves. My issue was on how to do it. I know LE but I am faced with we cant just convert to pure HLASM or even threaded C or C++ . So i have to come up with an alternative solution that works. We have been using Subpool 231 and it works

Re: Saving in memory data in case of operator cancel was Re: LE question

The choices are between saving the data yourself as you go, such as by some sort of checkpoint or other method, or saving the data yourself after the cancel (for which some sort of TERM=YES ESTAE-type recovery is necessary) or not allowing the CANCEL (whether by intercepting CANCEL or making

Re: LE question

HI, ALL commands issued at a console or from a program or JCL are processed in the command exit, whether they are JES or MVS commands or just random text typed on the console. When I developed our console message processing facility, I originally set it up to run as a command exit and then

Saving in memory data in case of operator cancel was Re: LE question

[Default] On 14 May 2019 11:23:01 -0700, in bit.listserv.ibm-main idfli...@gmail.com (scott Ford) wrote: >All: > >I need to do some research on how job is cancelled via the Operator , Abend >S222. I read through some of the Boston share doc of some time ago by Ed, >Sam and Skip. Its great. >I

Re: LE question

-Original Message- > From: IBM Mainframe Discussion List On Behalf > Of Brian Westerman > Sent: Tuesday, May 14, 2019 10:41 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: (External):Re: LE question > > I think that one of the CBTtape files has a program that is a generic

Re: LE question

; > -Original Message- > From: IBM Mainframe Discussion List On Behalf Of > Brian Westerman > Sent: Tuesday, May 14, 2019 10:41 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: (External):Re: LE question > > I think that one of the CBTtape files has a program that is a gene

Re: LE question

Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List On Behalf Of Brian Westerman Sent: Tuesday, May 14, 2019 10:41 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: LE question I think that one of the CBTtape files has a program

Re: LE question

I think that one of the CBTtape files has a program that is a generic abend catcher and you execute it, passing it a parm of your program and it builds the ESTAEX cushion around your program. Alternatively, our SyzMPF/z product can intercept the cancel command and keep it from being done when

Re: LE question

(Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of scott Ford Sent: Tuesday, May 14, 2019 2:22 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: LE question All: I need to do some research on how job is cancelled via

Re: LE question

I might be going off on a weird tangent. But if this is a started task, instead of a program running in a batch job. And if it can be run as a single step STC (not sure if this is a requirement). And it resides in an APF authorized library. Then I would "register" the program in the SCHEDnn member

Re: LE question

scott Ford wrote: >I need to do some research on how job is cancelled via the Operator , Abend >S222. I read through some of the Boston share doc of some time ago by Ed, Sam >and Skip. Its great. >I have a job written in Cobol, this job has mission critical data storage in a >table or array in

Re: LE question

On Tue, 14 May 2019 14:22:37 -0400 scott Ford wrote: :>I need to do some research on how job is cancelled via the Operator , Abend :>S222. I read through some of the Boston share doc of some time ago by Ed, :>Sam and Skip. Its great. :>I have a question in regard to something that was stated on

Re: LE question

Good luck! -Original Message- From: IBM Mainframe Discussion List On Behalf Of scott Ford Sent: Tuesday, May 14, 2019 1:59 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: LE question Alan, I found some more info, we have a ECVT customer table entry. This sounds like what I want. Scott

Re: LE question

: Extended Addressability Guide >> >> For the pendants on the list, please forgive me I have used incorrect >> terminology. >> Additional responses interspersed below. >> >> HTH, >> >> -Original Message- >> From: IBM Mainframe Dis

Re: LE question

inframe Discussion List On Behalf > Of scott Ford > Sent: Tuesday, May 14, 2019 1:35 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: LE question > > Alan, > > Yes that was my thinking. What about persistence ? > --> "common dataspace" vs. dataspace

Re: LE question

rspersed below. HTH, -Original Message- From: IBM Mainframe Discussion List On Behalf Of scott Ford Sent: Tuesday, May 14, 2019 1:35 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: LE question Alan, Yes that was my thinking. What about persistence ? --> "common dataspace

Re: LE question

ptional routine to save the dataspace @ shutdown. > > HTH, > > -Original Message- > From: IBM Mainframe Discussion List On Behalf > Of scott Ford > Sent: Tuesday, May 14, 2019 1:23 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: LE question > > All: > >

Re: LE question

- From: IBM Mainframe Discussion List On Behalf Of scott Ford Sent: Tuesday, May 14, 2019 1:23 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: LE question All: I need to do some research on how job is cancelled via the Operator , Abend S222. I read through some of the Boston share doc of some time ago

LE question

All: I need to do some research on how job is cancelled via the Operator , Abend S222. I read through some of the Boston share doc of some time ago by Ed, Sam and Skip. Its great. I have a question in regard to something that was stated on the presentation. I have a job written in Cobol, this

Re: COBOL/LE question

On Mon, 13 Feb 2017 17:50:22 -0600, Dale R. Smith wrote: > >http://www.computerworld.com/article/3163192/data-center/just-because-it-fails-doesnt-mean-its-a-failure.html > I had one of those, many years ago. We were trying to convert our programmers from HLASM to an ISV cross-assembler. One of

Re: COBOL/LE question

On Mon, 13 Feb 2017 20:57:56 +, Pommier, Rex wrote: >All, > >Just to circle back and close the issue, I was "barking up the wrong tree" >with the IGZ0268W message. Turns out the driver program that was calling the >OS/VS COBOL program had a logic error in it that

Re: COBOL/LE question

o:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Pommier, Rex Sent: Wednesday, February 01, 2017 4:55 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: COBOL/LE question We're starting down that path. Management doesn't want to have to recompile things but I'm thinking we may need to do so just to see

Re: COBOL/LE question

Rex, I sure would re-compile the Cobol programs. I have ran into issues but it was going backward. It was in regard to callable LE functions and what was supported... Scott On Thu, Feb 2, 2017 at 12:12 PM, Bill Woodger wrote: > The IGZ0268W is a warning message (no

Re: COBOL/LE question

The IGZ0268W is a warning message (no kidding). If your are using up to Enterprise COBOL V4.2 (which you are), it is just a warning that some time in the future (going to V5+, or perhaps with some future LE) you *will* have a problem. If you are using V5+ (which you are not) it is a problem

Re: COBOL/LE question

No I don't. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Steve Beaver Sent: Thursday, February 02, 2017 9:56 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: COBOL/LE question You would not happen to have z/XDC to debug this mess

Re: COBOL/LE question

You would not happen to have z/XDC to debug this mess? Steve -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Pommier, Rex Sent: Thursday, February 2, 2017 9:15 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: COBOL/LE question Hi

Re: COBOL/LE question

[mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Sri h Kolusu Sent: Wednesday, February 01, 2017 5:30 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: COBOL/LE question Rex, I forgot to mention that DO NOT SET RTEREUS(ON) as default. Just set it for the particular job you are having problem with. Something

Re: COBOL/LE question

/#!topic/bit.listserv.ibm-main/DFSpeCSKUog https://groups.google.com/forum/#!topic/bit.listserv.ibm-main/_QnqYPU3eIk Thanks, Kolusu From: "Pommier, Rex" <rpomm...@sfgmembers.com> To: IBM-MAIN@LISTSERV.UA.EDU Date: 02/01/2017 03:41 PM Subject: COBOL/

Re: COBOL/LE question

IGZ0268W means that OS/VS COBOL is trying to interface with COBOL 5. Which is a no-no. Thanks, Tom Savor Software Developer, Sr FRMS-SCM Fiserv -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to

Re: COBOL/LE question

@LISTSERV.UA.EDU Subject: (External):Re: COBOL/LE question i am guess the c/vs was nores nodynam and the asm90 is your real trouble maker Sent from my iPhone Steve Beaver > On Feb 1, 2017, at 16:58, Steve Beaver <st...@stevebeaver.com> wrote: > > Rex OS VS call Wold to call Bo

Re: COBOL/LE question

problem. >> >> Rex >> >> -Original Message- >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On >> Behalf Of Steve Beaver >> Sent: Wednesday, February 01, 2017 4:54 PM >> To: IBM-MAIN@LISTSERV.UA.EDU >> S

Re: COBOL/LE question

need to do so just to see if that's the > problem. > > Rex > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Steve Beaver > Sent: Wednesday, February 01, 2017 4:54 PM > To: IBM-MAIN@LISTSERV.UA.EDU

Re: COBOL/LE question

t; To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: COBOL/LE question > > I have a simple question do you happen to have a the source modules that if > you attempted to reassemble them and recompile them to see if that's the > problem > > Sent from my iPhone > Steve Beaver >

Re: COBOL/LE question

: Wednesday, February 01, 2017 4:54 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: COBOL/LE question I have a simple question do you happen to have a the source modules that if you attempted to reassemble them and recompile them to see if that's the problem Sent from my iPhone Steve Beaver > On Fe

Re: COBOL/LE question

I have a simple question do you happen to have a the source modules that if you attempted to reassemble them and recompile them to see if that's the problem Sent from my iPhone Steve Beaver > On Feb 1, 2017, at 16:41, Pommier, Rex wrote: > > Hello all, > > We are

COBOL/LE question

Hello all, We are in the process of migrating from z/OS 1.13 to 2.2. We just ran into an issue with our COBOL and LE environment. We are running COBOL 4.2. Within the maintenance for COBOL and the upgrade in LE from 1.13 to 2.2, IBM introduced the warning message "IGZ0268W An invocation was

Re: LE question

if you don't. > > Charles > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Hank Oerlemans > Sent: Thursday, November 26, 2015 2:43 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: LE question > > If

Re: LE question

If it's that sensitive then linking in your own options module would be a good idea.   IMO   Hank  -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO

LE question

All, I have a new to verify the correct LE runoption are in effect prior to our STCs initialization. I need to check things like: 1.ALL31 2. HEAP 3. STACK I would like to do this pro grammatically. Can i do this ? If I can , can some point me the direction of a manual which mentions it

Re: LE question

-MAIN@LISTSERV.UA.EDU Subject: Re: LE question The parms are controlled via (depending on the z/OS Level) a CEEPRMxx member in Parmlib or CEEOPT module in the code. Generally - one size fits all. In CEEPRMxx are parms for CICS, Other, and I am not sure if there is another delineation or not. So

Re: LE question

If you can assume R12 point to the CAA then: USING CEECAA,12 USING CEEEDB,11 USING CEEOCB,10 L 11,CEECAAEDB L 10,CEEEDBOPTCB CEECAA CEEEDB CEEOCB then use the following information to parse

Re: LE question

Hank: Much appreciated , exactly what I needed. Regards, Scott IDMworks On Thu, Nov 26, 2015 at 5:13 PM, Hank Oerlemans wrote: > If you can assume R12 point to the CAA then: > > USING CEECAA,12 > USING CEEEDB,11 > USING CEEOCB,10 > L 11,CEECAAEDB > L 10,CEEEDBOPTCB

Re: LE question

015 1:53 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: LE question > > All, > > I have a new to verify the correct LE runoption are in effect prior to our > STCs > initialization. > I need to check things like: > > 1.ALL31 > 2. HEAP > 3. STACK >

Re: LE question

ll of the options currently in effect. > > Charles > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Lizette Koehler > Sent: Thursday, November 26, 2015 1:22 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: L

Re: LE question

@LISTSERV.UA.EDU Subject: Re: LE question If it's that sensitive then linking in your own options module would be a good idea. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu

Re: LE Question

/ Facebook IDs: MartinPacker Blog: https://www.ibm.com/developerworks/mydeveloperworks/blogs/MartinPacker From: Alan Young ayo...@teleport.com To: IBM-MAIN@LISTSERV.UA.EDU Date: 10/03/2015 06:44 Subject:Re: LE Question Sent by:IBM Mainframe Discussion List IBM-MAIN

Re: LE Question

...@uk.ibm.com Twitter / Facebook IDs: MartinPacker Blog: https://www.ibm.com/developerworks/mydeveloperworks/blogs/MartinPacker From: Scott Ford idfzos...@gmail.com To: IBM-MAIN@LISTSERV.UA.EDU Date: 10/03/2015 01:37 Subject:Re: LE Question Sent by:IBM Mainframe Discussion

Re: LE Question

Alan: I was thinking along the lines of what you suggested. cant suggest as a ISV and developer to customers to use CICS or DB2 as a solution. I personally think its overkill for a system type application which we are..besides we handle sensitive security type data. Regards, Scott On Tue, Mar

Re: LE Question

On Tue, 10 Mar 2015 09:37:42 +, Martin Packer wrote: More likely IEFUSI or similar. Hiperspace is NOT in the 31-bit (or 64-bit) memory map. That's the point of it. Are you saying that it's there in case 64-bit is not enough? -- gil

Re: LE Question

Blog: https://www.ibm.com/developerworks/mydeveloperworks/blogs/MartinPacker From: Paul Gilmartin 000433f07816-dmarc-requ...@listserv.ua.edu To: IBM-MAIN@LISTSERV.UA.EDU Date: 10/03/2015 12:29 Subject:Re: LE Question Sent by:IBM Mainframe Discussion List IBM-MAIN

Re: LE Question

/developerworks/mydeveloperworks/blogs/MartinPacker From: Paul Gilmartin 000433f07816-dmarc-requ...@listserv.ua.edu To: IBM-MAIN@LISTSERV.UA.EDU Date: 10/03/2015 15:21 Subject:Re: LE Question Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU On Tue, 10 Mar

Re: LE Question

On Tue, 10 Mar 2015 15:14:55 +, Martin Packer wrote: Hiperspace came along about 22 years before 64-bit ANYTHING, let alone 64-Bit Virtual. Nowadays, what advantage does hiperspace offer over 64-bit? Performance, perhaps? From: Paul Gilmartin Date: 10/03/2015 12:29 On Tue, 10 Mar 2015

Re: LE Question

The C runtime I/O functions fopen(), fread(), fwrite(), etc. support hiperspace data if the fopen() file mode parameter type=memory(hiperspace) is specified. The functions are callable from COBOL. You just have to setup the parameters for what C expects and compile with NODYNAM. On our system

AW: Re: LE Question

One more potential option is the UNIX shared memory feature. I have not used this in any of my own programs, so I cannot say for sure it is an option in your case. Anyway, you might want to have a look. There is a set of C functions called shmget(), shmat(), shmdt(), and shmctl(). A program

Re: LE Question

On 10/03/2015 7:02 AM, Sam Siegel wrote: 64 bit memory is the cleanest in terms of using linear addresses. However, if data needs to be referenced by COBOL, you will face problems. You might need to copy back data to 31bit address space or other means. dataspaces cannot be directly accesses

LE Question

I have a question about heaps. I want to have a Cobol program call a C routine, the C routine to place data onto the heap then return back to Cobol. The question is can Cobol then reference that data ? Regards, Scott www.identityforge.com

Re: LE Question

Scott - You will need to pass the address of the heap variable back to COBOL. Then use set address of to associate the address with a COBOL linkage section entry. You may also need to take into consideration how LE clean's up the heap. Depending on which heap the variable is created in, the life

Re: LE Question

Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Scott Ford Sent: Monday, March 09, 2015 9:09 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: LE Question I have a question about heaps. I want to have a Cobol program call a C routine, the C routine to place data onto the heap then return back

Re: LE Question

Guys: I will have to read and try ..my question is how do i pass a lot of data ...a dataspace ? i would like to avoid dasd if I can .. Regards, Scott On Mon, Mar 9, 2015 at 12:29 PM, Sam Siegel s...@pscsi.net wrote: Scott - You will need to pass the address of the heap variable back to

Re: LE Question

How much data? 10meg? 100meg? 1gig? On Mar 9, 2015 2:06 PM, Scott Ford idfzos...@gmail.com wrote: Guys: I will have to read and try ..my question is how do i pass a lot of data ...a dataspace ? i would like to avoid dasd if I can .. Regards, Scott On Mon, Mar 9, 2015 at 12:29 PM, Sam

Re: LE Question

On Mon, 9 Mar 2015 14:18:15 -0700, Sam Siegel wrote: How much data? 10meg? 100meg? 1gig? How about 10 gig? None of those numbers would be unreasonable if COBOL supported 64-bit addressing. But IBM can't see the use for that. Of course if the data are large enough they go into page data

Re: LE Question

Sam, 2-3 G . Regards, Scott On Monday, March 9, 2015, Paul Gilmartin 000433f07816-dmarc-requ...@listserv.ua.edu wrote: On Mon, 9 Mar 2015 14:18:15 -0700, Sam Siegel wrote: How much data? 10meg? 100meg? 1gig? How about 10 gig? None of those numbers would be unreasonable if

Re: LE Question

OK ... that is a lot of data. Since an address space provides for just 2GB in the 31 bit range for code, data and system code, you cannot get 3GB in there. You have the following choices: 1) 1 or more data spaces 2) 64bit memory 3) some 31 bit data in current address space; remainder in

Re: LE Question

Sam, Yeah I agree. I might have to stay with QSAM file until we can write and test an API.. Thanks a lot, As always much appreciated. Regards, Scott On Monday, March 9, 2015, Sam Siegel s...@pscsi.net wrote: OK ... that is a lot of data. Since an address space provides for just 2GB in the