>There shouldn’t be Jake. I'm running MOD-54's for my sysres volumes and have
>been for years. Probably the only issue you might have is if you are going
>from a multi-sysres config where you had multiple system symbols for catalog
>purposes, you'll just have to fix that to all use either
The pointers contain the offsets (0-based) of the sections
from the beginning of the record.
Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp.
Poughkeepsie NY
> From: "Shivang Sharma"
> To: IBM-MAIN@LISTSERV.UA.EDU
> Date: 08/28/2019 12:27 AM
> Subject: Re: Reverse map Adsadmp
Thanx Jim , that was beneficial.
One additional question, I can see
the PL/s structure defined in
Amdsaddo which has pointers to
different sections for example
a pointer to console options.
So how we can convert these pointers
in terms of character position (offset)
to identify the start of each
On 28/08/2019 11:52 am, Paul Gilmartin wrote:
I wonder whether nowadays more address spaces are created for batch
job steps or for fork()? Of course, it's environment-sensitive. Which
path should be optimized? Whenever I see the message
BPXAS ON INTRDR
it appears the batch path is
On 27/08/2019 10:54 pm, David Crayford wrote:
On 2019-08-27 8:19 PM, David Crayford wrote:
Great write-up. Bash doesn't use local spawn so it always runs
sub-processes in child address spaces. I have reported this so Rocket
are aware
and have opened a ticket. I'm not sure if it will be
Jesse,
EMC has a few different types of SRDF, both synchronous and asynchronous.
Hitachi has TrueCopy, which is synchronous and can be mixed on the floor with
the IBM kit for point in time replication as long as the connection is between
the same vendor. GDPS can manage TrueCopy for Hyperswap
We’ve used XRC for DR for two decades, the first decade without GDPS (in-house
RYO), much easier after we added GDPS. Some of your 'options' are determined by
hardware. For example, with XRC, your source volumes must be IBM, but the
target volumes can be any flavor. Dell/EMC has their own
Fred,
Have a look outside the nine dots at what the other vendors are offering.
There is more than one way to skin a cat, and the IBM products and services are
not necessarily the best or most cost-effective way to get the job done.
RON HAWKINS
Director, Ipsicsopt Pty Ltd (ACN: 627 705 971)
Thanks for checking. I'm thinking IBM is working on it now, as I can no longer
get to the MVS feature download page.
From: IBM Mainframe Discussion List on behalf of
Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu>
Sent: Tuesday, August 27, 2019
I can't say for sure how it works now, but at one time IEBGENER did not depend
on (or pay any attention to) DS1LSTAR. It would read successive blocks of data
until EOF was encountered, or an I/O error occurred because of
differing/invalid BLKSIZE. It provided a way to salvage data from a file
On Tue, 27 Aug 2019 19:07:45 +, Mike Hochee wrote:
>Hi, I suspect an IBM doc server issue. Downloads of PDFs from IBM z/OS V2R2
>Elements and Features PDF Downloads (
>https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r2-pdf-download?OpenDocument
> ) from the z/OS MVS
Since hello world worked, most user's probably aren't experiencing this
problem. At this point, you just need to wait for IBM to create a fix or
circumvention.
Good luck. Jon.
On Tuesday, August 27, 2019, 05:34:27 AM PDT, Joseph Reichman
wrote:
Yes worked
> On Aug 26, 2019, at
Hi, I suspect an IBM doc server issue. Downloads of PDFs from IBM z/OS V2R2
Elements and Features PDF Downloads (
https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r2-pdf-download?OpenDocument
) from the z/OS MVS shelf (
Or as a temporary solution until you're firmly onto a single SYSRES, you could
place something like this in IEASYMxx:
SYSDEF
SYMDEF(='')
This way you won't need to change your catalog entries at the cutover time,
minimizing your chance of problems.
Rex
If SYS1.PARMLIB is on your SYSRES, DO NOT Catalog it on VOL().
VOL(**), however, does work for SYS1.PARMLIB.
On 2019-08-27 14:06, Mark Jacobs wrote:
> resolves to the same value as ** and was meant as a replacement
> for using ** in catalog entries.
>
> Mark Jacobs
>
>
> Sent from
I actually still use both. Everything on my sysres (except ZFS) are cataloged
with ** for historical reasons I guess. I don’t migrate to a new
mastercat when building next z/os release in Serverpac, so the only really
"safe" method to convert from ** to in the catalog would be to
Here is a link to the GDPS REDBOOK:
http://www.redbooks.ibm.com/abstracts/sg246374.html?Open
And to get information on the products, capabilities, etc., send an email to
g...@us.ibm.com
--
For IBM-MAIN subscribe / signoff /
resolves to the same value as ** and was meant as a replacement for
using ** in catalog entries.
Mark Jacobs
Sent from ProtonMail, Swiss-based encrypted email.
GPG Public Key -
https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com
‐‐‐ Original Message ‐‐‐
On
Yes I do have two and Might be having ** would be a
good idea ?
On Tue, 27 Aug, 2019, 9:42 PM Jousma, David, <
01a0403c5dc1-dmarc-requ...@listserv.ua.edu> wrote:
> There shouldn’t be Jake. I'm running MOD-54's for my sysres volumes and
> have been for years. Probably the only issue
sme...@gmu.edu (Seymour J Metz) writes:
> The proper way to provide encryption and non-repudiation is to have
> two key pairs. You sign a message using your private key. People
> wanting to send you encrypted data encrypt using your public key. So
> if foo wants to send bar a signed encrypted
There shouldn’t be Jake. I'm running MOD-54's for my sysres volumes and have
been for years. Probably the only issue you might have is if you are going
from a multi-sysres config where you had multiple system symbols for catalog
purposes, you'll just have to fix that to all use either **
Hello Group
I am planning convert the SMPE res volume DASD from mod 9 to mod 27 and
also our production alternate respack to mod 27.(Which is not live now).
This is due to the growing res volume .
With this conversion will there be any impact or any other changes that
need to be looked at prior
My personal email provider (see below) just recently supported ed25519 for
users public/private key pairs. They still support RSA keys of course.
Mark Jacobs
Sent from ProtonMail, Swiss-based encrypted email.
GPG Public Key -
Keeping with ibm-main tradition, I'll steer this into a different ditch :-)
"Seriously, stop using RSA"
This is a very interesting writeup/presentation, I've shorted the URL for
obvious reasons
https://tinyurl.com/yxw5xvmv
IMO, ECDSA (NIST curves) are much better than RSA, although researchers
On a related subject: it would be fantastic IMO to patch bash for z/OS so
that it used local spawn and followed _BPX_SHAREAS rules. It would
perform better and also allow you to use DD's in batch shell scripts like
you can with the z/OS UNIX shell.
Unfortunately, bash is pretty complicated
It's not the complexity of your code that matters, it's the complexity of the
code in the compiler.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List on behalf of
Joseph Reichman
Sent: Tuesday, August 27,
I have question
If you saw my code it wasn’t complicated a call to debug tool a call to DLL
I would imagine this must of happened to some company using XL C
> On Aug 27, 2019, at 11:25 AM, Seymour J Metz wrote:
>
> I've been programming for over half a century, and one thing that I can
>
I've been programming for over half a century, and one thing that I can assure
you of is that until you dig into the code you don't have a clue how easy the
fix will be. Things that you thought would be trivial turn out to be
intractable and things that you thought were difficult turn out to be
One simple rule is that every SMS managed dataset must be cataloged. So, unless
technical tricks are exploited, an SMF record 61 must have been produced to
Catlog-Define the dataset.
So a first check should be if all relevant SMF records are being recorded.
A second check could be to see if the
Shmuel,
I am a novice when it comes to some of the deep dive stuff that you guys
meander off, and into.
I was thinking a GTF SSCH trace off a volume allocating a data set with
IEFBR14 may be a starting point, along with looking for any SMF records
generated at the time of allocation would be a
" Non-repudiation for the message is not guaranteed by a hash. There is more
than 1 message that could match that hash. "
The breadth of privacy on the internet as we know it depends upon being able to
trust that a hashing algo + cryptographic signature verifies the
non-repudiation of the
On 2019-08-27 8:19 PM, David Crayford wrote:
On 2019-08-27 8:13 PM, Andrew Rowley wrote:
FWIW - debugging performance of forked Unix process startup/overhead
is a
mess - we had one customer who was seeing terrible performance when
fork/execing tiny little shell processes that did practically
Yes worked
> On Aug 26, 2019, at 10:14 PM, Jon Perryman wrote:
>
> Did you compile the hello world example and it abended? I can't believe this
> won't compile. IBM does QA so it's hard to believe the commonly used features
> fail with this abend.
> CEETEST and DLL are used less. The
A few random comments about this discussion:
1. Someone mentioned performance. If that is a concern, use hardware to do
the public-key algorithm - for example the Crypto Express HSM.
2. Remember that not all public-key algorithms can directly encrypt data. For
example, RSA can, but
I actually might share that with this vendor! They still have not
realized/acknowledged their error.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message:
willie bunter wrote:
>The file is PS. I haven't tried type 42. I will give it a shot.
>I am trying to find the user/job which created a dsn. I run my trustworthy
>SMF job which looks for recids 05 14 15 17 18 61 62 63 64 65 66 67 68 136 139
>163.
If you have setup your profiles correctly
On 2019-08-27 8:13 PM, Andrew Rowley wrote:
FWIW - debugging performance of forked Unix process startup/overhead
is a
mess - we had one customer who was seeing terrible performance when
fork/execing tiny little shell processes that did practically
nothing. It
was only happening on one of
On 24/08/2019 1:41 am, Kirk Wolf wrote:
FWIW - debugging performance of forked Unix process startup/overhead is a
mess - we had one customer who was seeing terrible performance when
fork/execing tiny little shell processes that did practically nothing. It
was only happening on one of their
John,
The file is PS. I haven't tried type 42. I will give it a shot.
On Tuesday, August 27, 2019, 02:16:46 a.m. UTC, John Kelly
wrote:
Did you try Type 42 subtype 27, VTOC update? Since you mentioned all of the
60 records, I assume the file is VSAM, surprised that there's nothing in
I did search for recid 61-64.
On Monday, August 26, 2019, 03:58:31 p.m. UTC, Carmen Vitullo
wrote:
was a the dataset renamed possibly? not created, if so there should be an SMF
60-64 breadcrumb I believe to see if it was renamed from another dataset ?
Carmen Vitullo
-
EBCDIC x'15' is NL New Line. Translates to ASCII as LF Line Feed.
Other common line ending sequence is CR Carrriage Return plus LF.
On Tue, Aug 27, 2019 at 4:33 AM PIETIN Jean-Loup
wrote:
>
> Hi all
>
> For information
>
> It's ok when we use a non SMS managed storage
>
> So I will use non SMS
Hi all
For information
It's ok when we use a non SMS managed storage
So I will use non SMS storage during installation and after convert all in SMS
But another problem detected during SMP/E Apply.
Different member like KCPVRTMS in TKANDATV library was created with $$GIMC but
the result file
Very likely to be Freedom units $$$.
- Vignesh
Mainframe Infrastructure
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Timothy Sipples
Sent: 27 August 2019 07:21
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Re: GDPS, Metro Mirror, Global Mirror
Tom Conley
Tom Conley wrote:
>Your management needs to brace themselves, because even
>the smallest shops are looking at 7+ figures to install
>GDPS.
Which currency are you talking about there? :-)
There are various GDPS offerings, and their prices vary.
AFAIK, no EOF is written, but LSTAR is set to zero which is recognized by SMS
that the dataset is empty.
EOF is data and needs a track to write on, while SMS datasets can be zero
tracks and still read empty.
Kees.
> -Original Message-
> From: IBM Mainframe Discussion List
45 matches
Mail list logo
