Re: AW: Re: Seeking for help finding cause of S23E/S53E with preceeding S202, and PGM 011/004

> >a) I see a couple of FREEMAIN (SSRV 78) trace entries pointing to a > TCB in read/write nucleus (TCB address is 00FDD4F8). Do these hold > some useful information for me? > The only tcb I know of that actually, really is located in the R/W > nucleus is the first tcb in the *master* address

Re: 64 bit execution above the bar

Doesn't the 64-bit Java Runtime Environment on z/OS already support code execution above the bar? That's my understanding. Also, I've stumbled into at least one non-IBM product that is already executing code above the bar.

Re: 64 bit execution above the bar

On 3/27/2017 3:59 PM, Paul Gilmartin wrote: It has been discussed here for a while. You could disable interrupts, branch to code above the bar, and branch back later. (I suppose the Old PSW was unconditionally scrunched.) More recently, interrupts above the bar are tolerated, but no system

Re: Odd Syntax error

I use an ISPF application to generate a receive package job. The dialog has the user copy/paste the *entire* contents of SERVINFO directly from the Shopz order into the job stream, meaning that the correct format of the data should be available in the completed order. All such data is

Re: ComputerWorld Says: Cobol plays major role in U.S. government breaches

I saw it as an update on the article that started the existing thread. New article,, same author, similar subject (COBOL/mainframe), more positive. I didn't see it as political, so apologies if anyone sees it that way. "Common sense is not so common." * Voltaire, Dictionnaire

Re: ComputerWorld Says: Cobol plays major role in U.S. government breaches

> On Mar 28, 2017, at 2:45 PM, Edward Gould wrote: > >> On Mar 28, 2017, at 12:36 PM, John Crossno wrote: >> >> Just in... >>

Re: How does ABO report its outcome? (was: Migrating Cobol)

> On Mar 28, 2017, at 3:47 PM, Bill Woodger wrote: > > Without any TEST option on the compile, LE gives you nothing but the offset > of the failing instruction, then you find it in the compile listing. ABO gets > you a new listing of the new code, a new place to consult

Re: Odd Syntax error

On Tue, 28 Mar 2017 17:00:43 -0400, Mark Pace wrote: >I'm trying to download some software using HTTPS. > hash="03638FB010AAEA65109594DF96C0D458102E0BFE" > >And I get - >GIM45500S ** VERIFICATION OF HASH VALUE OF > >Oops - I forgot to change the HASH > >

Re: ComputerWorld Says: Cobol plays major role in U.S. government breaches

j...@crossno.us (John Crossno) writes: > Just in... > http://www.computerworld.com/article/3185530/government-it/trump-s-son-in-law-jared-kushner-prepares-for-cobol-cloud-mainframes.html O'Malley showed Chaffetz the developers at work. "They see a working environment that looks exactly like

Odd Syntax error

I'm trying to download some software using HTTPS. //SERVINFO DD * And I get - GIM45500S ** VERIFICATION OF HASH VALUE OF FILE /mnt/mainline/IBM/OS221677.content/GIMPAF.XML FAILED. SMP/E WILL NOT RETRY FILE RETRIEVAL. Oops - I forgot to change the HASH

Re: AW: How does ABO report its outcome? (was: Migrating Cobol)

Without any TEST option on the compile, LE gives you nothing but the offset of the failing instruction, then you find it in the compile listing. ABO gets you a new listing of the new code, a new place to consult for the offset. If you compile with TEST options, the code generated for those

Re: ComputerWorld Says: Cobol plays major role in U.S. government breaches

On Mar 28, 2017, at 2:45 PM, Edward Gould wrote: > > I thought politics were a NONO on the list? The article wasn’t particularly political, mostly just “a new administration wants to upgrade Federal IT, just like all the ones before it said they would do.” This part

Re: SMP/E Tutorial

> Wow! It's rare, to say the least, for someone who doesn't already know how to > run SMP/E in batch to package a product with it. That was I also! With all respect, John, I think IBM's logic there is a little circular. Perhaps one reason people don't tackle SMP/E package development is

Re: IBM-MAIN Digest - 25 Mar 2017 to 26 Mar 2017 (#2017-85)

Was there an actual reply in there anywhere? I didn't see any. Please trim digest replies to just the message you are replying to. Peter -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ron Hagler Sent: Tuesday, March 28, 2017 3:40

Re: ComputerWorld Says: Cobol plays major role in U.S. government breaches

> On Mar 28, 2017, at 12:36 PM, John Crossno wrote: > > Just in... > http://www.computerworld.com/article/3185530/government-it/trump-s-son-in-law-jared-kushner-prepares-for-cobol-cloud-mainframes.html > > > > > "Common sense is not so common." > * Voltaire,

Re: IBM-MAIN Digest - 25 Mar 2017 to 26 Mar 2017 (#2017-85)

Sent from my iPad > On Mar 27, 2017, at 12:00 AM, IBM-MAIN automatic digest system > wrote: > > There are 16 messages totaling 872 lines in this issue. > > Topics of the day: > > 1. GREAT presentation on the history of the mainframe > 2. Migrating Cobol (7) > 3.

AW: How does ABO report its outcome? (was: Migrating Cobol)

>There is a new listing when a program is processed by ABO, and this listing is used by IBM Fault Analyzer, but it is not used by LE. For CEEDUMP, you would manually map the offset to the line number. So what you're saying is that an optional chargeable product knows how to handle problems

Re: SMP/E Tutorial

Dan Kalmar wrote: This may be a dumb question so forgive me in advance. I'm reading the User's Guide section on adding a new FUNCTION SYSMOD: https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.gim3000/fsmod.htm So the MCS statements are listed, but why on earth there

How does ABO report its outcome? (was: Migrating Cobol)

>To help search engines: ABO = Automatic Binary Optimizer >>We haven't set off down the yellow-brick ABO road, so it's hard to gauge h= >>ow much angst we'll actually have to overcome. I'm pretty sure it won't be = >>trivial. >I haven't seen ABO in action yet. Is there a listing that relates

Re: 64 bit execution above the bar

On Tue, Mar 28, 2017 at 12:30 PM, Paul Gilmartin <000433f07816-dmarc- requ...@listserv.ua.edu> wrote: > On Tue, 28 Mar 2017 13:04:10 -0400, Steve Smith wrote: > > > >I presume IBM would like to deprecate and retire dataspaces completely, > >although the eternal backward-compatibility may

Re: 64 bit execution above the bar

There is no restriction on AR mode with AMODE 64. See DAT Address Translation in Chapter 3 of the POPS manual, specifically the right side of page 3-36 As determined by its address-space-control element, a virtual address space may be a 2G-byte space consisting of one region, or it may be up to

Re: ComputerWorld Says: Cobol plays major role in U.S. government breaches

Just in... http://www.computerworld.com/article/3185530/government-it/trump-s-son-in-law-jared-kushner-prepares-for-cobol-cloud-mainframes.html "Common sense is not so common." * Voltaire, Dictionnaire Philosophique (1764) On Sun, Mar 26, 2017 at 7:14 PM, Anne & Lynn Wheeler

Re: 64 bit execution above the bar

On Tue, 28 Mar 2017 13:04:10 -0400, Steve Smith wrote: > >I presume IBM would like to deprecate and retire dataspaces completely, >although the eternal backward-compatibility may prevent that for 100 years >or more. > (Wow! We're halfway there!) My impression, also. Is there anytning possible

Re: 64 bit execution above the bar

My understanding is that a "data space" is a z/OS construction, the hardware has no such concept. There's no reason a "dataspace" couldn't execute instructions as far as the hardware is concerned. Just connect the DAT tables as the primary and fire away. Of course, you'd be programming on the

Re: 64 bit execution above the bar

On Tue, 28 Mar 2017 08:32:49 -0700 Ed Jaffe wrote: :>On 3/28/2017 8:23 AM, Tom Marchant wrote: :>> I could be wrong, but I don't think that the hardware cares about :>> data spaces. A data space is an address space that contains no :>> operating system information,

Re: 64 bit execution above the bar

On Tue, 28 Mar 2017 08:32:49 -0700, Ed Jaffe wrote: >On 3/28/2017 8:23 AM, Tom Marchant wrote: >> >> I could be wrong, but I don't think that the hardware cares about >> data spaces. A data space is an address space that contains no >> operating system information, including Nucleus, LPA, CSA,

Re: 64 bit execution above the bar

On 3/28/2017 8:23 AM, Tom Marchant wrote: I could be wrong, but I don't think that the hardware cares about data spaces. A data space is an address space that contains no operating system information, including Nucleus, LPA, CSA, and SQA. The hardware does not perform ALET-qualified

Re: 64 bit execution above the bar

On Tue, Mar 28, 2017 at 10:23 AM, Tom Marchant < 000a2a8c2020-dmarc-requ...@listserv.ua.edu> wrote: > On Tue, 28 Mar 2017 09:44:28 -0500, Paul Gilmartin wrote: > > >On Tue, 28 Mar 2017 08:43:18 +0300, Binyamin Dissen wrote: > > > >>Well, they never supported code execution from a dataspace

Re: 64 bit execution above the bar

On Tue, 28 Mar 2017 09:44:28 -0500, Paul Gilmartin wrote: >On Tue, 28 Mar 2017 08:43:18 +0300, Binyamin Dissen wrote: > >>Well, they never supported code execution from a dataspace .. >> >Isn't that a hardware limitation. whereas execution above the bar is >restricted by (some) software? I

Re: 64 bit execution above the bar

On Tue, 28 Mar 2017 08:43:18 +0300, Binyamin Dissen wrote: >On Mon, 27 Mar 2017 18:10:35 -0400 Charles Mills wrote: > >:>The fact that the hardware guys and gals made the hardware capable of >execution above the bar means IBM is giving this some thought. (The thought >may be "Heck, no!" ) >

Re: 64 bit execution above the bar

On Mon, 27 Mar 2017 18:10:35 -0400, Charles Mills wrote: >The fact that the hardware guys and gals made the hardware capable of >execution above the bar means IBM is giving this some thought. (The thought >may be "Heck, no!" ) It would have been a bizarre decision to limit the hardware to only

Re: 64 bit execution above the bar

Tony Harminc wrote: On 27 March 2017 at 20:15, Mike Schwab wrote: ...it's the ability to IPL and run in ESA/390 architecture that's going. Exactly right. -- John Eells IBM Poughkeepsie ee...@us.ibm.com

Re: Seeking for help finding cause of S23E/S53E with preceeding S202, and PGM 011/004

On Tue, Mar 28, 2017 at 7:06 AM, Peter Hunkeler wrote: ​​ > > > This is complex, multitasking code that has run for years without problem. > The developer tried to change a tiny bit of code, and the errors startet do > appear. The problem is that the code change has been backed out,

AW: Re: AW: Re: Seeking for help finding cause of S23E/S53E with preceeding S202, and PGM 011/004

>b) I know "SVC D" is also entered for normal task termination. In an ld >MVS debugging manual I found that the first byte of R1 is x'08' this indicates >RTM2 is called for task termination cleanup. The x'08 does no longer seem to >hold true. How can I identify such an non-error an SVC D

Re: 64 bit execution above the bar

All, This a great discussion, what about a 64bit program doing dasd I/O for example? I saw a Share.org presentation by the father of HLASM and he had a tri-modal program, it did I/O below the line and moved data to Above the bar ... Scott On Tue, Mar 28, 2017 at 5:34 AM Martin Packer

AW: Re: Seeking for help finding cause of S23E/S53E with preceeding S202, and PGM 011/004

>I'm not really sure why IBM service would help someone debug an application error, aside from on a for-fee basis, unless there is reason to believe there could be a system problem. I agree. But when all else fails, we might even try going down that route. >23E reason 0: you have an error in

Re: Seeking for help finding cause of S23E/S53E with preceeding S202, and PGM 011/004

>>a) I see a couple of FREEMAIN (SSRV 78) trace entries pointing to a TCB in >>read/write nucleus (TCB address is 00FDD4F8). Do these hold some useful >>information for me? >The only tcb I know of that actually, really is located in the R/W nucleus is >the first tcb in the *master* address

Re: Seeking for help finding cause of S23E/S53E with preceeding S202, and PGM 011/004

I'm not really sure why IBM service would help someone debug an application error, aside from on a for-fee basis, unless there is reason to believe there could be a system problem. 23E reason 0: you have an error in the input to detach. The system program-checked referencing the data that you

Re: LISTCAT QUESTION - TEMP-EXP

 Radoslaw, Thanks for answering my question.  I guess the TEMP-EXP must have been result of an EXPORT command being run in the past. Thanks to everyone who responded and helped out.  From: R.S. To: IBM-MAIN@LISTSERV.UA.EDU Sent: Tuesday, March 28, 2017

Re: LISTCAT QUESTION - TEMP-EXP

W dniu 2017-03-27 o 17:21, esmie moo pisze: Gentle Readers, i have a question about TEMP-EXP which appears on a LISTCAT of the HSM BCDS. I did a REPRO to a test BCDS however when I run the LISTCAT of the Prod version (so as to compare the TEST & PROD. allocations) it shows TEMP-EXP in the

Re: 64 bit execution above the bar

It's basically "give people what they need, ahead of when they need it". I'm glad Development take this approach; I'd like them to spend effort / time / money where it's really needed. And doing it all in one go, whatever "it all" might be, would've taken us longer to get what was needed out

Looking for z/OS system programmer - Australia

Hello, I am posting this Job opening behalf of my colleague who is looking for z/OS system programmer(Contract Position) also with some experience in CICS,DB2,MQ,IMS for Australia, Melbourne with the contract of 1 year. If interested please contact me directly Regards, Nathan