Hi,
Does anyone have an example to create a QR code using OGL.
The QR code should encode a url.
Thanks
Gadi
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the
Hi,
Can anyone point me to the current OGL manual?
I can't find it.
Thanks
Gadi
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
There really is no "safe" way to share DASD without some sort of PLEX, either a
full sysplex (with the CF's) or a baisc (baby) sysplex with Ficon adapters as
CTC's.
Otherwise, Catalog sharing is problematic and PDS/e sharing is not possible,
and actually neither is standard PDS sharing of
Google and the document setting a SYSPLEX will walk you through how to set a
PLEX up
Regards,
Steve Beaver
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with
Even PDSE can be safely shared. If updates only occur from one LPAR and
read-only everywhere else. And, said updates may not be reflected immediately
(or until next IPL) in the other read-only LPARs
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Radoslaw Skorupka
It's possible to share some things, but others can only be safely shared within
a sysplex.
From: IBM Mainframe Discussion List on behalf of
Paul Gorlinsky
Sent: Monday, June 19, 2023 10:25 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: GRS setup for MONOPLEX
Yes, PDSE do require SYSPLEX. Not GRS-plex, not CA-MIM (or MII), but
SYSPLEX.
Reason: PDSE use sysplex communication, not GRS facilities.
Regarding to the topic: in order to share datasets you need ...nothing.
No parallel sysplex
No base sysplex
Not even GRSplex
No SMSplex
Simply nothing except
That’s exactly what we do. We share the SMS config though.
On Mon, Jun 19, 2023 at 11:04 AM Paul Gorlinsky
wrote:
> I think I will do the same ... put in it the PLEX but run with a different
> master catalog, spool, etc.
>
> Thanks
>
>
I think I will do the same ... put in it the PLEX but run with a different
master catalog, spool, etc.
Thanks
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the
Beware of PDSEs. I’m not 100% sure but I think the sandbox needs to be in
the plex to share them. Updating a PDSE outside of the plex can cause
corruption.
We have our sandbox in the plex just to avoid issues.
On Mon, Jun 19, 2023 at 9:25 AM Paul Gorlinsky wrote:
> We have a sandbox system
Yes but the monoplex needs to communicate over CTCs to the SYSPLEX.
Sent from my iPhone
> On Jun 19, 2023, at 10:25 AM, Paul Gorlinsky wrote:
>
> We have a sandbox system that references TSO user and ISV catalogs and
> datasets. The sandbox has a unique master catalog but shares virtually
We have a sandbox system that references TSO user and ISV catalogs and
datasets. The sandbox has a unique master catalog but shares virtually
everything else.
It does have access to the couple facility that the Sysplex is using ... But it
is not a member of the Sysplex.
Is it possible for
Classification: Confidential
I retract the above below. I was conflating SSH with SSL. My apologies. SSL
can/should be dropped.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Allan Staller
Sent: Monday, June 19, 2023 6:58 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject:
Classification: Confidential
At leas one of my clients are using this.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Tom
Ross
Sent: Saturday, June 17, 2023 9:50 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Checkpoint/restart in COBOL applications?
[CAUTION: This
Classification: Confidential
IIRC, SSL is now supported by the base OS IIRC z/OS 2.1+
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Brian Westerman
Sent: Friday, June 16, 2023 9:01 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: After installing z/OS 2.5 , we are not
15 matches
Mail list logo