Right, is it not IBM owns AAA through IZZ or perhaps JZZ?
They will make exceptions. At CorreLog I registered CZA.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Paul Gilmartin
Sent: Wednesday, September 14, 2022 8:02 PM
To
On Wed, 14 Sep 2022 20:36:14 -0500, Paul Gilmartin wrote:
>On Wed, 14 Sep 2022 17:33:13 -0700, Retired Mainframer wrote:
>
>>It is in chapter 10 of "Standard Packaging Rules for z/OS-Based Products,"
>>SC23-3695-10.
>>
>A search for that gets many hits; mostly containing rotten links.
>
>Several
On Wed, 14 Sep 2022 17:33:13 -0700, Retired Mainframer
wrote:
>It is in chapter 10 of "Standard Packaging Rules for z/OS-Based Products,"
>SC23-3695-10.
>
A search for that gets many hits; mostly containing rotten links. IBM could do
better.
Several are HTTP links, for which Firefox reports s
Thank you. All the search keywords I had tried turned up nothing.
Regards,
Steve Thompson
On 9/14/22 20:33, Retired Mainframer wrote:
It is in chapter 10 of "Standard Packaging Rules for z/OS-Based Products,"
SC23-3695-10.
-Original Message-
From: IBM Mainframe Discussion List On Beha
It is in chapter 10 of "Standard Packaging Rules for z/OS-Based Products,"
SC23-3695-10.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Steve Thompson
Sent: Wednesday, September 14, 2022 4:28 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Title of book -- Naming Conventio
Once upon a time I had a copy of a book that gave the naming
convention for naming elements for SMPE so that one would not
conflict with IBM either in LPA, or LNKLST, etc. And one could
even share a common CSI.
I know it has to have been updated by now (my copy was from back
about 1997).
An
The road is littered with pensions now being paid by the PBGC @ a fraction of
their promised benefit. In Ohio, the public employee and teachers pension funds
are severely underfunded.
Ohio ranked as the state with the fifth-most unfunded liabilities at $429.53
billion. The top four included Cal
LOLOLOLOL see AIG.
Sent from Yahoo Mail for iPhone
On Wednesday, September 14, 2022, 7:01 PM, Charles Mills
wrote:
No, I would guess that the two insurance companies are on the hook, at least
each for their 50% share, no matter how well or poorly their investments do. I
would guess that th
No, I would guess that the two insurance companies are on the hook, at least
each for their 50% share, no matter how well or poorly their investments do. I
would guess that their full faith and credit is on the line. Your insurance
company never says "sorry 'bout your house burning down. We inve
AIG was so bad in 2007-08 the government had to bail them out to the tune of 85
billion and 80% government ownership. And they were America’s largest insurer.
Sent from Yahoo Mail for iPhone
On Wednesday, September 14, 2022, 5:47 PM, Tony Harminc
wrote:
On Wed, 14 Sept 2022 at 17:02, Charl
On Wed, 14 Sep 2022 16:25:43 -0500, Matthew Stitt wrote:
>If you specify HFS as a filesystem in BPXPRMxx on z/OS V2R5 it will get
>rejected. The system will come up, but the mounting of HFS file systems will
>fail.
>
>You can also specify ZFS as a parameter in IDCAMS when defining a VSAM
>data
No it isn’t just a financial thing. They transferred the money & liabilities to
a firm that thinks it can turn a profit on the investment. The current IBM
pension liability was over funded. (Over 100%) If the new pension fund owner
invests in say Bitcoin and loses 2/3 like Bitcoin did over the p
On Wed, 14 Sept 2022 at 17:02, Charles Mills wrote:
> It's purely a financial thing, right? Like if they had moved their
> checking account from Chase to Wells?
>
> Pensioners should not see any significant change. These are defined
> benefit plans: you get $X/month no matter who pays the bills o
More details required.
Sent from my iPhone
> On Sep 14, 2022, at 16:22, Tommy Phillips wrote:
>
> I'm running a search for a privately held computer software company with
> 1500+ employees and offices all over the world. They need help (multiple open
> positions) with post sales delivery an
If you specify HFS as a filesystem in BPXPRMxx on z/OS V2R5 it will get
rejected. The system will come up, but the mounting of HFS file systems will
fail.
You can also specify ZFS as a parameter in IDCAMS when defining a VSAM dataset.
This replaces the Dataset type of LINEAR and obviates the
It's purely a financial thing, right? Like if they had moved their checking
account from Chase to Wells?
Pensioners should not see any significant change. These are defined benefit
plans: you get $X/month no matter who pays the bills or what the rate of
return. Nor do they incur any significant
I'm running a search for a privately held computer software company with 1500+
employees and offices all over the world. They need help (multiple open
positions) with post sales delivery and making customers successful with the
software they purchase.
Salary is $120k/yr with a 10% bonus and it'
I’m shocked the IBM haters haven’t mentioned IBM’s announcement today regarding
offloading 16 billion in pension liabilities.
https://www.pionline.com/pension-risk-transfer/ibm-offloads-16-billion-pension-liabilities-annuity-purchases
---
On Wed, 14 Sep 2022 18:32:48 +, Michael Watkins wrote:
>IBM says: 'Before z/OS V1R7, the HFS file system was the primary hierarchical
>file system. As of z/OS V1R7, you can use any combination of HFS and zFS file
>systems. Because zFS has higher performance characteristics than HFS and is
>
On Wed, 14 Sep 2022 18:20:19 +, Farley, Peter x23353 wrote:
>Well, both JCL and the TSO/E ALLOCATE command still only take "HFS" as a value
>for DSNTYPE when allocating a Unix PATH file.
>
>E.G. for ALLOC:
>
>ALLOC FI(MYDDNAME) PATH('/u/tsouser/file') DSNTYPE(HFS) PATHMODE(SIRUSR)
>PATHOPTS(
IBM says: 'Before z/OS V1R7, the HFS file system was the primary hierarchical
file system. As of z/OS V1R7, you can use any combination of HFS and zFS file
systems. Because zFS has higher performance characteristics than HFS and is the
strategic file system, you should migrate your HFS file syst
Well, both JCL and the TSO/E ALLOCATE command still only take "HFS" as a value
for DSNTYPE when allocating a Unix PATH file.
E.G. for ALLOC:
ALLOC FI(MYDDNAME) PATH('/u/tsouser/file') DSNTYPE(HFS) PATHMODE(SIRUSR)
PATHOPTS(ORDONLY) FILEDATA(TEXT) PATHDISP(KEEP, KEEP)
For JCL, see here:
I just submitted an RCF on various z/OS 2.5. TSO/E publications which
mention HFS with no mention of HFS EOS.
--
gil
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with
I could also reword it to be 'I cannot configure it to meet the unknown
standards of the check'
The SDSF display of the check does not include any internal buffers used inside
the check.
The SDSF display of the check is the check's message buffer (and might well be
documented as such, since t
24 matches
Mail list logo
