Re: Creating a qr code using OGL
Hi Attila, I managed to create a QR code using OGL with the following code: DEFINE QR BARCODE QRCODE HEIGHT 15 MM RATIO 1.01; POSITION 1 IN 1 IN; PLACE BARCODE QR CHAR 'HTTP://WWW.YNET.CO.IL'; The current problem is that when I scan the code, it does return the required text. Gadi -Original Message- From: IBM Mainframe Discussion List On Behalf Of Attila Fogarasi Sent: יום ג 20 יוני 2023 09:17 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Creating a qr code using OGL I doubt OGL has changed in past 20 years. It does fully support barcodes (which is what I used OGL for) but I would be astonished if it has been extended to QR codes. OGL can embed graphics from PDS members, but I don't know how to create the graphic (it won't be jpeg). Finally OGL allows defining arbitrary printing using a bitmap at 240 pel per inch, so string of 1 and 0 where 1 prints a black pel at that position. You could construct QR code that way, should be possible to automate with scan. I guess Xerox still makes printers which use OGL, not sure what other printers are still supported. As for manual, google found several which look valid, https://det.wi.gov/Documents/ibm_overlay_generation_language_user_guide.pdf On Tue, Jun 20, 2023 at 3:14 PM Gadi Ben-Avi wrote: > 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 message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Creating a qr code using OGL
I doubt OGL has changed in past 20 years. It does fully support barcodes (which is what I used OGL for) but I would be astonished if it has been extended to QR codes. OGL can embed graphics from PDS members, but I don't know how to create the graphic (it won't be jpeg). Finally OGL allows defining arbitrary printing using a bitmap at 240 pel per inch, so string of 1 and 0 where 1 prints a black pel at that position. You could construct QR code that way, should be possible to automate with scan. I guess Xerox still makes printers which use OGL, not sure what other printers are still supported. As for manual, google found several which look valid, https://det.wi.gov/Documents/ibm_overlay_generation_language_user_guide.pdf On Tue, Jun 20, 2023 at 3:14 PM Gadi Ben-Avi wrote: > 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 message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Creating a qr code using OGL
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 message: INFO IBM-MAIN
OGL Manual
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
Re: GRS setup for MONOPLEX to SYSPLEX
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 members because multiple people can end up overlaying each other. The reserves alone that will happen in a Sandbox are probably already affecting your other LPARs and you might not even realize it. HSM backups are a good example of something that issues reserves that can slow things down for the systems that aren't doing the backups, but are using those volumes. There are many more issues, too many to list. Can you get away without some sort of Plex? The answer is, if you are careful and don't mind the ENQ's, yes, until you do something that you should not have, in which case you can have a really bad day. The best you can hope for in that situation is that you lock out the other system(s), the worst is that you end up with wrong or corrupt data. It's far too easy (and cheap) to at least set up a basic plex (with ficon ports) than to expose yourself to problems. Honestly, you can use extra Ficon ports or buy a (or a couple) ficon cards on ebay or from some third party hardware (re)seller and have them installed. Connecting things up is extremely easy and quick, plus (since GRS is free) you end up with not only safety, but the ability to route commands from any system to any other system and several other niceties. Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
SYSPLEX
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 the message: INFO IBM-MAIN
Re: GRS setup for MONOPLEX to SYSPLEX
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 Sent: Monday, June 19, 2023 1:17 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: GRS setup for MONOPLEX to SYSPLEX 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 DASD available from several systems. Of course, the more mentioned facilities you have the better sharing is. And yes, in order to share PDSEs (properly) you still have sysplex. However you can share ICF BCSes (catalogs), VSAM, PS, PDS, etc. Note: there are various flavours of sharing. Shared DASD as a data transport method, shared PDSes with jobs, REXX tools, etc. - it can be shared easily, because it is not heavily used. Batch datasets - assuming proper batch windows it is also can be shared easily. For frequent sharing it is good to think about ICF ECS or RLS, etc. -- Radoslaw Skorupka Lodz, Poland W dniu 19.06.2023 o 17:03, Michael Babcock pisze: > 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 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 a monoplex z/OS system to share DASD, user cats, >> etc., with a SYSPLEX via GRS management and coupling facility? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: GRS setup for MONOPLEX to SYSPLEX
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 to SYSPLEX 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 a monoplex z/OS system to share DASD, user cats, etc., with a SYSPLEX via GRS management and coupling facility? Thanks -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: GRS setup for MONOPLEX to SYSPLEX
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 DASD available from several systems. Of course, the more mentioned facilities you have the better sharing is. And yes, in order to share PDSEs (properly) you still have sysplex. However you can share ICF BCSes (catalogs), VSAM, PS, PDS, etc. Note: there are various flavours of sharing. Shared DASD as a data transport method, shared PDSes with jobs, REXX tools, etc. - it can be shared easily, because it is not heavily used. Batch datasets - assuming proper batch windows it is also can be shared easily. For frequent sharing it is good to think about ICF ECS or RLS, etc. -- Radoslaw Skorupka Lodz, Poland W dniu 19.06.2023 o 17:03, Michael Babcock pisze: 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 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 a monoplex z/OS system to share DASD, user cats, etc., with a SYSPLEX via GRS management and coupling facility? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: GRS setup for MONOPLEX to SYSPLEX
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 > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Michael Babcock OneMain Financial z/OS Systems Programmer, Lead -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: GRS setup for MONOPLEX to SYSPLEX
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 message: INFO IBM-MAIN
Re: GRS setup for MONOPLEX to SYSPLEX
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 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 a monoplex z/OS system to share DASD, user cats, etc., > with a SYSPLEX via GRS management and coupling facility? > > Thanks > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Michael Babcock OneMain Financial z/OS Systems Programmer, Lead -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: GRS setup for MONOPLEX to SYSPLEX
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 > 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 a monoplex z/OS system to share DASD, user cats, etc., > with a SYSPLEX via GRS management and coupling facility? > > Thanks > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
GRS setup for MONOPLEX to SYSPLEX
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 a monoplex z/OS system to share DASD, user cats, etc., with a SYSPLEX via GRS management and coupling facility? Thanks -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: After installing z/OS 2.5 , we are not able to connect IP.
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: Re: After installing z/OS 2.5 , we are not able to connect IP. [CAUTION: This Email is from outside the Organization. Unless you trust the sender, Don’t click links or open attachments as it may be a Phishing email, which can steal your Information and compromise your Computer.] 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 able to connect IP. [CAUTION: This Email is from outside the Organization. Unless you trust the sender, Don’t click links or open attachments as it may be a Phishing email, which can steal your Information and compromise your Computer.] I don't think any were removed yet, but the older SSL stuff was moved to TLS. I think SSL is still technically supported though. What is the exact circumstances of the failure and/or what messages are being generated at IP startup and/or when they try to connect? I'm sure there is probably a really big error in the log. If you use SSL, was PAGENT and RESOLVER started successfully? Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Checkpoint/restart in COBOL applications?
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 Email is from outside the Organization. Unless you trust the sender, Don’t click links or open attachments as it may be a Phishing email, which can steal your Information and compromise your Computer.] Greetings! Does anyone know if there are people/applications using checkpoint/restart in COBOL applications? The doc only shows it is usable in programs that use SORT, I have not heard of customers doing this in years, but someone in IBMMAIN would know better than me! The reason for the question is that IBM is considering removing that capability from z/OS and we are wondering how much of an impact, if any, this would be on COBOL applications? (Actually PL/I also, but I work in COBOL so kind of focused on that :-) Cheers, TomR >> COBOL is the Language of the Future! << -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: After installing z/OS 2.5 , we are not able to connect IP.
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 able to connect IP. [CAUTION: This Email is from outside the Organization. Unless you trust the sender, Don’t click links or open attachments as it may be a Phishing email, which can steal your Information and compromise your Computer.] I don't think any were removed yet, but the older SSL stuff was moved to TLS. I think SSL is still technically supported though. What is the exact circumstances of the failure and/or what messages are being generated at IP startup and/or when they try to connect? I'm sure there is probably a really big error in the log. If you use SSL, was PAGENT and RESOLVER started successfully? Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
