Mark Jacobs wrote:
>The Social Security Administration does not reuse Social Security
>numbers. It has issued over 450 million since the start of the
>program, and at a use rate of about 5.5 million per year. It says
>it has enough to last several generations without reuse or changing
>the number
I got a s0c4 in storage I got above the BAR I got 6 sges or 6 megs
The address was valid wondering If I have to do IAVR64 REQUEST=PAGEIN also
not sure of the format of RANGLIST storage is it a 16 byte value of the
starting and ending address that I am referencing
thanks
,SIZE=sizeWhen REQUEST=GET is specified, a required input parameter that
indicates the size of the storage to be obtained. The size can be anywhere
between 1 and [image: Start of change]128K[image: End of change] bytes. The
size is rounded up to a power of 2. So cell sizes are 64, 128, 256, 512,
I've used IARV64 and IARCP64 extensively. This is my first time trying IARST64.
Forgive the staggering after the cut and paste.
dsa_word contains X'8000'
. 169800 str00,dsa_word
Save the size in bytes .
.
In addition to SSNs, the same set of numbers is used for EINs (employers),
ITINs (non-residents), and ATINs (adoptees in process). There may be others
but those are the ones I see as a (currently idle) AARP volunteer tax preparer.
Some numbers are also reserved, such as 111-00- for the
Done.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Susan Shumway
Sent: Tuesday, April 21, 2020 8:17 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: FTP documentation whines
Thanks, Charles. I'll let the content owners know
Did you run it without the ADDRESS keyword?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Binyamin Dissen [bdis...@dissensoftware.com]
Sent: Tuesday, April 21, 2020
I'm guessing that because the second line has a different length than the
first, the Converter will set RECFM to V or VB. It's worth an RCF.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List
Yeah, if you reserve a first digit for every special case, after a while you
run out of possibilities.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Wayne Bickerdike
Sent: Tuesday, April 21, 2020 12:15 PM
To:
I'm soliciting suggestions for what I might put in an RCF.
The JCL Ref. for DD * contains an example containing
the enigmatic line:
Extra line to make DD * variable record length
There is no text accompanying the example explaining
how or why this might work, nor is there a similar
example
Typo when I copied it.
The command is as you wrote and the result is as below.
On Tue, 21 Apr 2020 19:07:48 + Seymour J Metz wrote:
:>What is Xx?
:>
:>What output do you get from
:>
:>RUNARRAY name EXEC((LIST X+8?+114 MULT(1) LENGTH(8)))
:>
:>
:>--
:>Shmuel (Seymour J.) Metz
H1B get a 6-- SSN prefix. Pretty dumb concept. Now they have a big problem
looming. Spouse partners of H1B also get a number with "intelligence "
implied. LOL
On Wed, Apr 22, 2020, 04:54 Charles Mills wrote:
> 8 numeric plus one alphanumeric would be 10**8 * 36 = 36 followed by 8
> zeros = 3.6
What is Xx?
What output do you get from
RUNARRAY name EXEC((LIST X+8?+114 MULT(1) LENGTH(8)))
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Binyamin Dissen
8 numeric plus one alphanumeric would be 10**8 * 36 = 36 followed by 8 zeros =
3.6 billion (American billion, not old UK billion).
EINs ("SSNs for companies") are 9 digits also. Do they have their own "space"
or do they potentially duplicate SSNs? I don't know. They are written
differently but
On Tue, 21 Apr 2020 14:34:20 -0400, Tony Thigpen wrote:
>But, remember, the first 3 positions indicate a zone, so that affects
>your calculation of how many are available.
>
Not since 2011, but still just a Band-Aid:
https://en.wikipedia.org/wiki/Social_Security_number#Historical_structure
https://en.wikipedia.org/wiki/Social_Security_number#Valid_SSNs
9xx-xxx-(100m), xxx-00- (10m), 666-xx- (1m),
000-xx-(1m), xxx-xx-(0.1m) will not be issued.
999,999,999 -112,100,000 = 887,899,999 SSNs (plus multiple
disqualified by 2nd/3rd group).
888m valid - 450m used = 438m
Didnt they stop using the first 3 digits to
indicate the location of the person getting
the SSN a while back ?
If we run out we could just start using
alpha characters in with the numeric :-)
How about base 64 SSN numbers ? :-)
(my opinion only not my employers)
-Original Message-
But, remember, the first 3 positions indicate a zone, so that affects
your calculation of how many are available.
Back in the '80s, I worked for a banking software firm and we were
notified by the feds that all software relating to SSNs needed to be 10
digits because there would be an
Array define via
EQ name X LENGTH(16) ENTRIES(1:20)
Issuing
RUNARRAY ADDR(name) EXEC((LIST Xx+8?+114 MULT(1) LENGTH(8)))
The LIST command constantly displays the data from the first entry.
Without the MULT operand it would display much more storage.
The only example available is from
9 characters with 10 possible values = 10 to the 9th = 999,999,999 aka = 1
billion.
Allow one position to be alphanumeric adds what? Does position matter?
Thought 10 to the 36th plus 10 to the 8th??
But if allow all alphanumeric = 36 to the 9th = ?
=Ken
On Tue, Apr 21, 2020 at 1:03 PM Joe Monk
The Social Security Administration does not reuse Social Security numbers. It
has issued over 450 million since the start of the program, and at a use rate
of about 5.5 million per year. It says it has enough to last several
generations without reuse or changing the number of digits.
Mark
https://en.wikipedia.org/wiki/Social_Security_number#Exhaustion_and_re-use
450 million issued and 5.5 million issued a year.
On Tue, Apr 21, 2020 at 5:03 PM Joe Monk wrote:
>
> 9 digits = 999,999,999. There afe only 350,000,000 in the USA.
>
> Joe
>
> On Tue, Apr 21, 2020 at 10:08 AM Paul
There are also many non-human entities like corporations that use the same SSN
value space.
There are a LOT of those . . . and they spring up and fade away at a rate far
higher than human births and deaths.
I don't think SSN's are ever re-used, are they? Besides use by identity
thieves of
Right! Your car is out of gas, and so you complain "This darned Chevrolet
doesn't run."
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Seymour J Metz
Sent: Tuesday, April 21, 2020 8:37 AM
To: IBM-MAIN@LISTSERV.UA.EDU
9 digits = 999,999,999. There afe only 350,000,000 in the USA.
Joe
On Tue, Apr 21, 2020 at 10:08 AM Paul Gilmartin <
000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
> On Tue, 21 Apr 2020 08:45:14 +, Seymour J Metz wrote:
>
> >My guess is that they needed to update the online
Indirectly, of course, unless I strike an adjacent key, drop a keystroke or
transpose keystrokes, in which case it will be typed incorrectly :-(
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List
Please excuse the typo; I meant, of course, "indirectly". EQUATE is a standard
IPCS subcommand; it doesn't need to come from a script. Or are you looking for
a way to do it in a single command?
I've generally used the IPCS panels, and there is a similar issue there;
following pointers within
Sir,
You are an absolute legend.
Thank you 3000.
‐‐‐ Original Message ‐‐‐
On Tuesday, April 21, 2020 9:08 PM, Sri h Kolusu wrote:
> Kekron,
>
> > I'm looking to get 1 record for each type-subtype combination.
> > That is, 1 rec of 30_1, 1 of 30_2, and so on.
>
> AFAIK SMF records which
Kekron,
> I'm looking to get 1 record for each type-subtype combination.
> That is, 1 rec of 30_1, 1 of 30_2, and so on.
AFAIK SMF records which have a subtype are
2,30,32,33,41,42,70-79,84,86,88,89,92,94,96,97,98,106,108 and 113 . If you
have any other record type that have a subtypes then
> At this point they need to bring back people who know the system.
Quite likely, but, absent good documentation, that would be true whether it
were written in Ada, BLISS, COBOL, DIBOL, ESPOL, FLOW-MATIC, GOM, Haskell,
Icon, Java, Kotlin, Lua, Mesa, Napier88, occam, PL/I, QtScript, Raku,
Thanks, Charles. I'll let the content owners know to watch for it.
https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.e0zc100/mhvrcfs.htm
-Sue Shumway
On 4/20/2020 1:41 PM, Charles Mills wrote:
RCF. I am so annoyed I can't type.
Heck, the implementation is one thing!
On Tue, 21 Apr 2020 08:45:14 +, Seymour J Metz wrote:
>My guess is that they needed to update the online application to support the
>new legislation,
>...
Meanwhile, how close is the 9-digit SSN space to saturation?
-- gil
[Default] On 21 Apr 2020 01:45:25 -0700, in bit.listserv.ibm-main
sme...@gmu.edu (Seymour J Metz) wrote:
>My guess is that they needed to update the online application to support the
>new legislation, that it is written in COBOL for CICS, that they negligently
>failed to require, or even allow,
Yes, it can be done via code/clist/rexx. My query was whether it can be done
directly.
"Is there an IPCS command to list storage when the pointer is in a different
address space, or does this require an IPCS clist?"
Appreciate your effort.
On Tue, 21 Apr 2020 09:09:03 + Seymour J Metz
[Default] On 21 Apr 2020 02:09:14 -0700, in bit.listserv.ibm-main
sme...@gmu.edu (Seymour J Metz) wrote:
>Can't you do it incorrectly via an intermediate EQUATE or EVALUATE subcommand?
Incorrectly or indirectly?
Clark Morris
--
Nope, no shared spool. Harping is welcome.
Lou
--
Artificial Intelligence is no match for Natural Stupidity
- Unknown
On Tue, Apr 21, 2020 at 7:36 AM Lennie Dymoke-Bradshaw <
lenni...@rsmpartners.com> wrote:
> Lou,
> Sorry to harp on about this, but these systems do not share a spool do
>
Cheryl;
Thanks for writing back.
As usual, I have a lot to say, so I'll start with a summary:
A pandemic and potential economic crisis (May Oil futures went negative and
hit -$40/barrel yesterday for the first time ever) is not the time for IBM
to be maximizing only shareholder value.
Lou,
Sorry to harp on about this, but these systems do not share a spool do they?
Lennie Dymoke-Bradshaw | Security Lead | RSM Partners Ltd
Web: www.rsmpartners.com
‘Dance like no one is watching. Encrypt like everyone is.’
-Original Message-
From: IBM Mainframe Discussion
>From the article:
"Systems revenue saw $1.4bn in revenue, up 3 per cent thanks to the IBM Z
mainframe line."
https://www.theregister.co.uk/2020/04/21/ibm_q1_fy2020_coronavirus/
Regards,
*Mark T. Regan, K8MTR*
CTO1 USNR-Retired, 1969-1991
Nationwide Insurance, Retired, 1986-2017
Can't you do it incorrectly via an intermediate EQUATE or EVALUATE subcommand?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Jim
Mulder [d10j...@us.ibm.com]
Sent:
Lou
This problem is caused by the SYSLOG outputs that were created when the LPAR
was running under TSS still being on the spool.
If you look at the system logs when running under TSS, you will most likely see
some IEF196I messages for SYSLOG output dataset creation with *BYPASS* in the
name.
My guess is that they needed to update the online application to support the
new legislation, that it is written in COBOL for CICS, that they negligently
failed to require, or even allow, adequate documentation and that they're too
cheap to maintain adequate staffing. There are other
Le 20/04/2020 à 21:17, Paul Gilmartin a écrit :
> Unemployment checks are being held up by a coding language almost nobody
> knows - The Verge
>
> https://www.theverge.com/2020/4/14/21219561/coronavirus-pandemic-unemployment-systems-cobol-legacy-software-infrastructure
>
> -- gil
I'm not
43 matches
Mail list logo
