Charles
Finding out which SMF subsystems are defined in SMFPRMxx is also something to
consider as SYS.IEFU83 and SYS.IEFU83 can point to different module lists
and your software may have to install its exit to every SMF subsystem.
I am surprised that IFAQUERY has not been enhanced to
In
cace9d90ab02da4f8de4c45db43ba3452a4d927...@phxccrprd03.adprod.bmc.com,
on 04/24/2014
at 05:45 AM, Dyck, Lionel lionel_d...@bmc.com said:
)PROC
PANEXIT ((Field1 Field2 Field3 zuser),REXX,PANEXIT,EXITDATA,MSG=PEX001)
)END
Is that legal without the commas? Shouldn't it be
PANEXIT
In 20140424213615.6004883.18431.8...@yahoo.ca, on 04/24/2014
at 05:36 PM, Ted MacNEIL eamacn...@yahoo.ca said:
Early compiler writers used the term for languages that used 'call by
name' sub-routines (such as FORTRAN) when something like an
expression was passed.
That's not call by name.
It worked without commas :-)
--
Lionel B. Dyck
BMC Software
Product Development Lead, Common Install and Services
10431 Morado Circle, Building 5, Austin, Texas 78759
Office Phone: 512-340-6031 (extension x26031)
E-Mail: lionel_d...@bmc.com
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of John Gilmore
[ snip ]
COBOL 5.2 is a very large step forward in performance; . . . [ snip ]
I've not yet seen the IBM Announcement for [Enterprise] COBOL 5.2. Would you
kindly furnish a pointer to it?
Thanks,
John [Chase],
Your implicit point is well taken: 'COBOL 5.2' should of course have
been 'COBOL 5.1'.
John Gilmore, Ashland, MA 01721 - USA
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to
Of course there is also DSCLI and the TSO utilities
Whats the TSO utility name that would help me in Controlling TPCR flash
initiation ?
On Mon, Nov 4, 2013 at 6:50 PM, Scott Chapman sachap...@aep.com wrote:
If you're talking about just flashing datasets or volumes for local
purposes (not
Anthony,
If you have DB2 in that plex, I would think twice (or thrice) about increasing
the resmil value, as DB2 does heavy enqueue activity. I remember one
presentation (I think it was at share or maybe another conference), where
someone from IBM GRS presented the following item:
Company A
Has anyone encountered the f00 disk being full in step 8o of the
starter-system-guide?
ACCESS 151 G
Ready; T=0.01/0.01 11:21:50
VMARC UNPACK NOV151 VMARC G * * A
DMSERD107S Disk A(F00) is full
Unexpected error during output. RC=13.
Ready(00013); T=2.27/2.49 11:22:16
MDISK 0191 3390 0001
I see the descriptions of the XPLINK and XPLINK-64 conventions in that manual,
but nothing about those conventions would prevent calls to programs with other
linkage conventions or address modes, IMHO without much trouble at all. The
code to implement a call to a 31-bit program will obviously
Has anyone heard any good rumors about what will be coming out next year as the
latest and greatest model?
z296?
Ec14?
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu
Answering my own question for the benefit of future searchers.
Yes, CSVDYNEX LIST may be used to answer this question, and Yes, the
relevant bit is EXAAEDEFINED. FWIW, I think all of the information in this
regard that SHOWMVS obtains from non-GUPI interfaces may be obtained in this
manner in a
On 4/25/2014 8:09 AM, Klein, Kenneth E wrote:
Has anyone heard any good rumors about what will be coming out next year as the
latest and greatest model?
z296?
Ec14?
You bring up an interest point to contemplate as IBM eventually
considers official names for its 13th-generation machine (if
The z196/z114 names were just plain confusing, so yeah, I'd assume they
wouldn't do that. If they were going to have an aberration, they should
have done that for 13.
Let's see, z10EC/BC, zEC12/zBC12...maybe z1EC3/z1BC3 to hide the 13?!
On Fri, Apr 25, 2014 at 11:47 AM, Ed Jaffe
On 4/25/2014 at 10:30 AM, Le Blanc, Frank flebl...@bu.edu wrote:
Has anyone encountered the f00 disk being full in step 8o of the
starter-system-guide?
ACCESS 151 G
Ready; T=0.01/0.01 11:21:50
VMARC UNPACK NOV151 VMARC G * * A
DMSERD107S Disk A(F00) is full
Unexpected error during
Or you can consider the EC10/EC12 as ECyy so at this point the next EC would be
EC14 if it were to come out this year.
Just my $0.01 to add to the discussion
--
Lionel B. Dyck
BMC Software
Product Development Lead, Common Install and
I don't remember where I heard this, or even I really did hear this, but
immediately, Next jumped to the front of my brain. zNext - NextZ. It
could be real, it could just a hallucination.
On Fri, Apr 25, 2014 at 1:17 PM, Dyck, Lionel lionel_d...@bmc.com wrote:
Or you can consider the
Which utility?
http://www-03.ibm.com/software/products/en/migration
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Maybe they'll resurrect Future System. :-)
-jc-
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of zMan
Sent: Friday, April 25, 2014 11:52 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Beyond the EC12
The z196/z114 names
If the superstition about 13 was considered, why did they come out with z/OS
1.13? :)
Al Nims
Systems Admin/Programmer 3
Information Technology
University of Florida
(352) 273-1298
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Ed
It's always referred to as zNext until the formal announcement and final name
is released.
CIT | Ken Porowski | VP Mainframe Engineering | Information Technology | +1 973
740 5459 (tel) | ken.porow...@cit.com
This email message and any accompanying materials may contain proprietary,
Around here, people are betting on EC14 or EC15. We don't understand where the
name z196 came from, but didn't z9's come out in 2009, z10's in 2010, EC12's in
2012...
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Ken Porowski
My bet:
BHV3B4
Reason: completely unrelated to the predecessor,
Of course B4 is number of procesors in hex, 3 could be understood as
third generation (z196 - 1 was first generation), V is for
Virtualization, finally BH stand for absolutely nothing.
--
Radoslaw Skorupka
Lodz, Poland
Ah, thanks, I was sure I had heard it before.
On Fri, Apr 25, 2014 at 1:54 PM, Ken Porowski ken.porow...@cit.com wrote:
It's always referred to as zNext until the formal announcement and final
name is released.
CIT | Ken Porowski | VP Mainframe Engineering | Information Technology | +1
Funny, I was just looking at that.
Thanks. I am real aware of SYS(EXITS()) versus SUBSYS(XXX,EXITS()).
My product now warns if it is told to monitor subsystem XXX but
SUBSYS(XXX,EXITS(IEFU83/4/5)) has not been specified. But it does not know if
there is also a subsystem YYY that it has not
And if IBM has disclosed anything to ISVs, the NDAs undoubtedly prohibit
disclosing even that fact publicly.
-jc-
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Bob Shannon
Sent: Friday, April 25, 2014 1:28 PM
To:
On 4/25/2014 10:57 AM, DiBianca, Robert wrote:
Around here, people are betting on EC14 or EC15. We don't understand where the
name z196 came from, but didn't z9's come out in 2009, z10's in 2010, EC12's in
2012...
I realize time flies, but the IBM Danu z9-109 EC 2094 (9th generation
That's because we haven't ANNOUNCED anything. :-) TGIF :-)
Cheers, Martin
Martin Packer,
zChampion, Principal Systems Investigator,
Worldwide Banking Center of Excellence, IBM
+44-7802-245-584
email: martin_pac...@uk.ibm.com
Twitter / Facebook IDs: MartinPacker
Blog:
I can neither confirm nor deny that I know anything at all.
On Fri, Apr 25, 2014 at 2:41 PM, Chase, John jch...@ussco.com wrote:
And if IBM has disclosed anything to ISVs, the NDAs undoubtedly prohibit
disclosing even that fact publicly.
-jc-
-Original Message-
From: IBM
Since moving my sandbox LPARs to z/OS 1.13, I have been getting this error
message frequently. So for, I just pressed the Enter key and continued. It
finally irritated me enough to ask if others have this experience. It is
possible it is due to the way I have the these two LPARs sharing disk
It's all about what we don't know that we don't know.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
jo.skip.robin...@sce.com
From: Mark Pace pacemainl...@gmail.com
To:
Looking at software renewals, and I was asked about several. This stumped
me.
I read the Getting Started Guide to Technical Support Services for IBM
zSeries Software at http://www-935.ibm.com/services/us/its/pdf/swxcel.pdf.
It is a whopping 2 paragraphs, and no detail.
The description on
True dat. Bad idea.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
jo.skip.robin...@sce.com
From: Gibney, Dave gib...@wsu.edu
To: IBM-MAIN@LISTSERV.UA.EDU,
Date: 04/25/2014
My suspicion is:
ZFH3FF-z/Fog Horn 3rd Gen 255 processors and will be end of line for Z. To
be
sup'd by VCN4FFF-Virtual Cumulo nimbus 4th gen 1023 engines. Well it is
Friday!
In a message dated 4/25/2014 1:25:07 P.M. Central Daylight Time,
r.skoru...@bremultibank.com.pl writes:
My
It may be a bad idea. And actually I agree. But, my z9-L03 capped at 16 MSU
doesn't have an ICF or any resources to fire up GRS in ring mode, let alone
star. Since I am the only user in one sandbox and one of two sysprogs in the
other, we get by. :)
The message does not occur with z/OS 1.11
W dniu 2014-04-25 20:41, Chase, John pisze:
And if IBM has disclosed anything to ISVs, the NDAs undoubtedly prohibit
disclosing even that fact publicly.
ISV may not know the names, just because they don't need to know names.
They need to know technical details of zNEXT.
BTW: Let's guess:
1.
Dave,
Do you have 'Profile Sharing' turned on? IIRC that was new with 1.13. In
addition to allowing safe sharing of ISPPROF between systems, it also provides:
1.3.3.2 Temporary data set names
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Steve Conway
Sent: Friday, April 25, 2014 2:38 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Relationship of Resolve to ServiceLink?
Looking at software renewals, and I was asked
Thanks, I will look at that setting. I don't remember doing anything with that
when I installed 1.13, so I bet that is it. And might not be an issue in my two
other LPARs (Development and Production) where the Catalogs and stuff aren't
as broadly shared.
-Original Message-
From: IBM
Thanks, John.
Found a SHARE presentation that shows Resolve is one of the Electronic
Support offerings. I didn't even know that, having nothing to do with the
contracts.
Since I was asked the question without seeing the contract, guess I need
to see what all we're actually paying for.
;-) Sorry for the snarky comeback. I got carried away with my current fav
'true dat'.
I logged on to two different sysplex members. They use GRS, but I don't
think that's your problem. Here's what I see:
useird.$SYSX0.SPFLOGn.LIST on SYSX0
userid.$SYSX1.SPFLOGn.LIST on SYSX1
That is, my two
In
985915eee6984740ae93f8495c624c6c232c1e0...@jscpcwexmaa1.bsg.ad.adp.com,
on 04/25/2014
at 10:59 AM, Farley, Peter x23353 peter.far...@broadridge.com
said:
Seems wasteful of CPU cycles to me,
How often do you expect to hit the guard page? An explicit test for
stack overflow costs you at
On 25 April 2014 14:41, Chase, John jch...@ussco.com wrote:
And if IBM has disclosed anything to ISVs, the NDAs undoubtedly prohibit
disclosing even that fact publicly.
I've seen lots of NDA technical material over the years, but in my
experience IBM has *never* disclosed any branding info to
Well sure. It's need to know.
If the next mainframe is going to have 96-bit word support and a Load Inverted
instruction, this is information that may be of benefit to an ISV and, given a
couple of months' lead time, allow them to offer Day One support.
But whether it is going to be called the
Everything is relative. Certainly some 31-bit code is easy to thunk
to, but it's not just arguments that need to go below the bar, it's
any control blocks those arguments point to and any control blocks
those control blocks point to, etc. You also need to handle call-backs
from 31-bit code,
I've heard rumors that the names are often not determined until shortly
before release anyway, after some not-so-fun marketing meetings...
On Fri, Apr 25, 2014 at 6:14 PM, Tony Harminc t...@harminc.net wrote:
On 25 April 2014 14:41, Chase, John jch...@ussco.com wrote:
And if IBM has
On Fri, Apr 25, 2014 at 9:59 AM, Farley, Peter x23353
peter.far...@broadridge.com wrote:
I see the descriptions of the XPLINK and XPLINK-64 conventions in that
manual, but nothing about those conventions would prevent calls to programs
with other linkage conventions or address modes, IMHO
47 matches
Mail list logo
