Re: COBOL V3.2 to COBOL V6.3 conversion effort and Any z/OS or LE limits
Michael, I have to disagree with your blanket statement about never trying to debug optimized code. While it is sometimes true that debugging optimized code presents a problem, this is NOT always the case. Certainly recompiling with OPT(0) makes debugging easier, but it can hide subtle bugs if you do that. The TEST(SOURCE) compiler option is very helpful for debugging optimized code. At least in my experience, TEST(SOURCE) makes the Intertest debugger behave a lot better. TEST(SOURCE) seems to force the compiler to use "a little less optimization" regarding intermediate results, and for example to actually populate the target of a MOVE at the time of (or very near the time of) that MOVE statement. Without TEST(SOURCE) you may well see only garbage or a prior value in that target variable even after the MOVE has supposedly been executed, because for optimization purposes the compiler is keeping the actual value in a generated temp field invisible to any debugger. In other words, TEST(SOURCE) reduces a little bit of optimization in return for making debugging optimized code much more effective and possible. This can be a critical advantage when shooting a production issue at oh-dark-thirty with Operations and other management breathing down your neck for a resolution NOW before their critical (to them) SLA is missed. It is only when the compiler tells you (in the messages at the end of the listing) that it "copied procedures" to multiple locations where it is performed that one always has a problem, because any interactive breakpoint set in the "copied" paragraphs will never stop there. In that case it is unfortunately true that one must recompile with OPT(0) to see what is actually happening in those "copied" paragraphs. Otherwise (again, in my experience), optimized code can be debugged fairly easily if TEST(SOURCE) is used. Peter -Original Message- From: IBM Mainframe Discussion List On Behalf Of Michael Schmitt Sent: Thursday, October 6, 2022 6:25 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: COBOL V3.2 to COBOL V6.3 conversion effort and Any z/OS or LE limits IBM COBOL for z/OS V5 and later can not live in a PDS library. You must link to a PDS/E Program Object library. This may have consequences. If you are using IGZERRE to establish a resusable run-time environment, you must convert to CEEPIPI. If you are using ORDER statements in the Binder, they will not behave as expected when the module contains a mixture of COBOL 6 and assembler or COBOL 3 modules. If you are solving dumps without aid of an abend diagnosis product, you will be severely challenged. It is much harder to find your program's working storage in a dump. Do not attempt to debug optimized COBOL 6 code. The compiler drastically rearranges the code path. When debugging, compile as OPT(0). If you are using SuperZAP to zap modules, it takes different commands because the COBOL 6 sections are in a different class name. ...those are the biggest differences that we've hit. -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: COBOL V3.2 to COBOL V6.3 conversion effort and Any z/OS or LE limits
Thanks - -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: COBOL V3.2 to COBOL V6.3 conversion effort and Any z/OS or LE limits
IBM COBOL for z/OS V5 and later can not live in a PDS library. You must link to a PDS/E Program Object library. This may have consequences. If you are using IGZERRE to establish a resusable run-time environment, you must convert to CEEPIPI. If you are using ORDER statements in the Binder, they will not behave as expected when the module contains a mixture of COBOL 6 and assembler or COBOL 3 modules. If you are solving dumps without aid of an abend diagnosis product, you will be severely challenged. It is much harder to find your program's working storage in a dump. Do not attempt to debug optimized COBOL 6 code. The compiler drastically rearranges the code path. When debugging, compile as OPT(0). If you are using SuperZAP to zap modules, it takes different commands because the COBOL 6 sections are in a different class name. ...those are the biggest differences that we've hit. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FW: RMM Question
Here's the previous version. https://ibmdocs.pocnet.net/SG24-4998-00.pdf On Thu, Oct 6, 2022 at 12:08 PM Steve Beaver wrote: > > Does anyone in the group have the following Redbook on their PC or Laptop > > > > SG24-4998-01, Converting to Removable Media Manager: A Practical Guide > > > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
FW: RMM Question
Does anyone in the group have the following Redbook on their PC or Laptop SG24-4998-01, Converting to Removable Media Manager: A Practical Guide -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: z/OSMF PSWI
Unfortunately, that system is not up and z/OSMF is set to "connect" to our sandbox. I IPL'd that system but the IZU* tasks do not start (no RACF Started class profile defined either). On 10/6/2022 10:15 AM, Kurt J. Quackenbush wrote: As I understand your scenario, you have two z/OS systems, a driving system (call it A) where the z/OSMF server is running and a target system (call it B), and you want to install z/OS 2.5 into the existing master catalog for system B. Currently you have selected A as the target system for the deployment. Unfortunately Software Management does not have support for installing into an existing alternate master catalog. Yes it can install into the driving system's master catalog, or create and install into a brand new master catalog, but it does not install into an existing master catalog that is not the driving system's active master catalog. As a circumvention, is B IPL’d? Is a z/OSMF server running on B? If so, then define system B in the z/OSMF Systems task and select it as the target system for the deployment instead of selecting A. Kurt Quackenbush -- IBM, z/OS SMP/E and z/OSMF Software Management Chuck Norris never uses CHECK when he applies PTFs. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Michael Babcock Sent: Wednesday, September 28, 2022 3:40 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [EXTERNAL] Re: z/OSMF PSWI Okay, more issues. As I stated, we use a permanent maintenance volume/system. With ServerPac, we could define an SSA and have the SYSRES datasets cataloged in our maintenance systems master cat then ServerPac would allocate the dataset using an SSA. later it would generate jobs to remove the SSA. Unless I’m missing something, this doesn’t seem possible with z/OSMF because the Modify Catalog section doesn’t let us change the master cat (even though it says it will). The only way I see around that is to rename the SYSRES dataset with the SSA. Of course we would then need to create our own rename job to remove the SSA. Jeez, COME ON PEOPLE! We were told z/OSMF would provide the same functionality as ServerPac but I guess not. On Wed, Sep 21, 2022 at 3:28 PM Michael Babcock wrote: We are installing z/OS 2.5 via z/OSMF and are using the Modify Deployment screens. We can easily change the volumes, HLQs, etc, but wanted to modify the Primary and/or secondary allocation and don’t see a way to do that. We have a case opened with IBM and have been told there is no way to do that and no plans for it in the future. What?We could do that with the ServerPac, why not with z/OSMF? I was under the impression that z/OSMF would provide most functions that ServerPac provided. So, is that capability not going to be provided? -- Michael Babcock OneMain Financial z/OS Systems Programmer, Lead -- 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 -- 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: COBOL V3.2 to COBOL V6.3 conversion effort and Any z/OS or LE limits
IBM provides some significant help on their COBOL Migration portal here: https://www.ibm.com/docs/en/cobol-zos/6.4?topic=SS6SG3_6.4.0/migration-portal.html Tom Ross has given SHARE presentations on migration to V5 and then to V6, if you have a SHARE membership check the 2016 and 2017 proceedings archives. He probably also presented them at more recent SHARE conferences as well. FWIW, we are running V6.1 (+ back-ported updates) and have many existing V3.x programs and subroutines working fine without any changes. The rubber hits the road when you need to re-compile an older module to add new function or repair a defect. That's when you need to be aware of what changed and how it might affect your program. Watch out particularly for changes in the way DISPLAY NUMERIC's are handled, that is one of the places our teams have found tacit assumptions that are no longer necessarily true in the V5/6 compiler output code. E.G., in V3/V4 compiled code, a DISPLAY NUMERIC field that contains all SPACES at runtime will successfully compare to the ZEROES literal but will NOT compare successfully to ZEROES in V5/6 compiled code because the hardware instructions output from the compiler for the compare operation have changed. I can't answer authoritatively about CICS V5.6, but since V3/V4 compiled code runs without issue in batch I would tend to assume it will continue to run fine in CICS too, at least for the foreseeable future. IBM's decades of adherence to backward compatibility is a pretty good track record to depend on, but if you have CICS-specific questions I suggest asking again over on CICS-L. HTH Peter -Original Message- From: IBM Mainframe Discussion List On Behalf Of Paul Gorlinsky Sent: Thursday, October 6, 2022 12:12 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: COBOL V3.2 to COBOL V6.3 conversion effort and Any z/OS or LE limits I have a customer that is still using COBOL V3.2 on z/OS 1.13, 2.2 and 2.4 with CICS V5.3, IMS 15.2 and DB2 V12. Are there any major issues taking them to V6 COBOL ... Are there limits on LE interface with COBOL V3 going forward .. Are there limits on CICS V5.6 interface with COBOL V3 Thanks in advance ... Paul -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [Public] RE: EXTERNAL: Re: JES3 SMPE zone in Serverpac
On 10/6/2022 6:14 AM, Usher, Darrold wrote: That makes sense. Also, if you need to keep JES3 around, need to look at a support model with Phoenix Software. We have been providing significant enhancements as well as support. JES3plus V1R2 just went out the door last month: https://phoenixsoftware.com/article.php?20220927 Running a SPOOL I/O-intensive benchmark workload, JES3plus ran almost twice as many jobs as IBM JES3 while at-the-same-time reducing channel utilization by 92%. There have been important functional improvements as well -- such as enhancements to MVS exits, operator commands, and JCL. A JES3plus license is free to any ISV that wishes to join our partner program. Some of our participants are listed here: https://phoenixsoftware.com/jes3plus_isv.htm -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 https://www.phoenixsoftware.com/ This e-mail message, including any attachments, appended messages and the information contained therein, is for the sole use of the intended recipient(s). If you are not an intended recipient or have otherwise received this email message in error, any use, dissemination, distribution, review, storage or copying of this e-mail message and the information contained therein is strictly prohibited. If you are not an intended recipient, please contact the sender by reply e-mail and destroy all copies of this email message and do not otherwise utilize or retain this email message or any or all of the information contained therein. Although this email message and any attachments or appended messages are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by the sender for any loss or damage arising in any way from its opening or use. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
COBOL V3.2 to COBOL V6.3 conversion effort and Any z/OS or LE limits
I have a customer that is still using COBOL V3.2 on z/OS 1.13, 2.2 and 2.4 with CICS V5.3, IMS 15.2 and DB2 V12. Are there any major issues taking them to V6 COBOL ... Are there limits on LE interface with COBOL V3 going forward .. Are there limits on CICS V5.6 interface with COBOL V3 Thanks in advance ... Paul -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: z/OSMF PSWI
As I understand your scenario, you have two z/OS systems, a driving system (call it A) where the z/OSMF server is running and a target system (call it B), and you want to install z/OS 2.5 into the existing master catalog for system B. Currently you have selected A as the target system for the deployment. Unfortunately Software Management does not have support for installing into an existing alternate master catalog. Yes it can install into the driving system's master catalog, or create and install into a brand new master catalog, but it does not install into an existing master catalog that is not the driving system's active master catalog. As a circumvention, is B IPL’d? Is a z/OSMF server running on B? If so, then define system B in the z/OSMF Systems task and select it as the target system for the deployment instead of selecting A. Kurt Quackenbush -- IBM, z/OS SMP/E and z/OSMF Software Management Chuck Norris never uses CHECK when he applies PTFs. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Michael Babcock Sent: Wednesday, September 28, 2022 3:40 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [EXTERNAL] Re: z/OSMF PSWI Okay, more issues. As I stated, we use a permanent maintenance volume/system. With ServerPac, we could define an SSA and have the SYSRES datasets cataloged in our maintenance systems master cat then ServerPac would allocate the dataset using an SSA. later it would generate jobs to remove the SSA. Unless I’m missing something, this doesn’t seem possible with z/OSMF because the Modify Catalog section doesn’t let us change the master cat (even though it says it will). The only way I see around that is to rename the SYSRES dataset with the SSA. Of course we would then need to create our own rename job to remove the SSA. Jeez, COME ON PEOPLE! We were told z/OSMF would provide the same functionality as ServerPac but I guess not. On Wed, Sep 21, 2022 at 3:28 PM Michael Babcock wrote: > We are installing z/OS 2.5 via z/OSMF and are using the Modify > Deployment screens. We can easily change the volumes, HLQs, etc, but > wanted to modify the Primary and/or secondary allocation and don’t see a way > to do that. > > We have a case opened with IBM and have been told there is no way to do > that and no plans for it in the future. What?We could do that with > the ServerPac, why not with z/OSMF? I was under the impression that > z/OSMF would provide most functions that ServerPac provided. > > So, is that capability not going to be provided? > > > -- > Michael Babcock > OneMain Financial > z/OS Systems Programmer, Lead > -- 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 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: z/OSMF PSWI
You're OK to just restart the z/OSMF server after installing PTFs for PH45201 and PH46392. No need to restart the Deployment operation. Kurt Quackenbush, IBM z/OS SMP/E and z/OSMF Software Management Chuck Norris never uses CHECK when he applies PTFs. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Michael Babcock Sent: Thursday, October 6, 2022 8:33 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [EXTERNAL] Re: z/OSMF PSWI I have applied the two missing PTFs and will IPL them in. But do we need to restart our PSWI of z/OS 2.5 to pick up the changes? The hold data says it's just a restart to pick up the changes but doesn't mention restarting the installation process for z/OS 2.5 PSWI. On 9/29/2022 7:44 AM, Marna WALLE wrote: > Michael, > Have you verified that you have all the correct Driving System PTFs > installed, as indicated with FIXCAT IBM.DrivingSystem-RequiredService ?. > > Check out slide 33 onwards in this presentation that KurtQ did for the Z > Exchange, https://www.newera-info.com/KQ1.html . It explains how a new > master catalog can be used, including how the SSA (now called Temporary > Catalog Alias) is to be specified and used. > > -Marna WALLE > z/OS System Install and Upgrade > IBM Poughkeepsie > > -- > 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
ShopZ software report not working?
Ive noticed for some time now that my uploaded software report no longer seems to have any effect when I create an order for CBPDO products that have new version/release. I typically upload a fresh report (binary), then create a CBPDO order and typically filter by "my installed products with upgrades". So that I can see which products have installed I need to order to refresh my installation. This is a problem, because manually looking for updates is error prone, and quite time consuming. Has anyone else noticed this?I have opened a PMR with ShopZ support. Its been that way for quite awhile for me, not something that just occurred. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ICHEINTY - RACF interface
Peter, I tried many combinations of parameters using DATAMAP=NEW and RELEASE 1.8. I initially got return code x'24' and reason code 1. So something was wrong with my parameters. Juggling the parameters, I got past that. Then I got abend SD84-10. I fooled around with the WKAREA and WKSP parameters but couldn't advance. Then I removed DATAMAP and RELEASE and now get a S0C4. Regards, Pierre. PS - I'll look at my parameters just before calling ICHEINTY and match them with what's in the diagnosis manual. PPS - I will look at R_admin though. PPPS - The parameters described with ICHEINTY don't tell you what you can supply ((rxx) or A-type, etc) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ICHEINTY - RACF interface
I was pointed to ICHEINTY. I want to change the password for a particular userid. I'll look at R_admin. I used R_datalib about 15 years ago and had forgotten about the Callable Services. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ICHEINTY - RACF interface
I should have said that my TSO id is not authorized to issue SLIP commands. I will look at Diagnosis. Thanks. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: JES3 SMPE zone in Serverpac
Hi Keith, z/OS V2.5 is the last release that IBM will deliver JES3. That may also be related to the separate Target Zone. Regards, David On 2022-10-06 09:11, Keith Gooding wrote: Thanks Paul. We still need to have JES3 because as an ISV we do have to do some testing on a JES3 system. It would probably be safer to change our cloning jobs rather than ZONEMERGE the zones just in case an element with the same name as a JES3 element is added to z/OS. Keith On 6 Oct 2022, at 13:41, Paul Gorlinsky wrote: JES3 is no longer being maintained by IBM product. Phoenix Software International - https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fphoenixsoftware.com%2Fjes3plus.htmdata=05%7C01%7C%7Cc2b8dc67c3b7444b70c308daa79c6431%7C84df9e7fe9f640afb435%7C1%7C0%7C638006587499175581%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=3xevMw0LEgZ82r4GbAjUUMDeqoWRoI6t9vASdwSaWYc%3Dreserved=0 - is licensed to maintain and enhance JES3. This is probably the reason for the SMP/E split. Note also that z/VSE is in a similar situation. As of June 1, 2021, 21st Century Software Technologies, Inc. has a source code license agreement for z/VSE. https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.21stcenturysoftware.com%2Flicense-z-vse-code-from-ibm%2Fdata=05%7C01%7C%7Cc2b8dc67c3b7444b70c308daa79c6431%7C84df9e7fe9f640afb435%7C1%7C0%7C638006587499175581%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=JeijjNDPcGFzskZEi%2F1ogpX%2F2bU1bjGJwB2vxokC%2FGY%3Dreserved=0 IBM is investing every thing in z/OS w/JES2, z/VM and z/Linux. z/VM only as far as a hosting environment and no longer an application development / deployment environment. -- 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
[Public] RE: EXTERNAL: Re: JES3 SMPE zone in Serverpac
That makes sense. Also, if you need to keep JES3 around, need to look at a support model with Phoenix Software. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Keith Gooding Sent: Thursday, October 6, 2022 8:12 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: EXTERNAL: Re: JES3 SMPE zone in Serverpac Thanks Paul. We still need to have JES3 because as an ISV we do have to do some testing on a JES3 system. It would probably be safer to change our cloning jobs rather than ZONEMERGE the zones just in case an element with the same name as a JES3 element is added to z/OS. Keith > On 6 Oct 2022, at 13:41, Paul Gorlinsky wrote: > > JES3 is no longer being maintained by IBM product. Phoenix Software > International - > https://urldefense.com/v3/__https://phoenixsoftware.com/jes3plus.htm__;!!GryZGb6B1VCs0SfC!VlGquu4R4KAw1DxSOAe1BpRhwPaIEwCmwu5D_NrY8t_cu_5TVm7-t8KeDWJn71lh$ > - is licensed to maintain and enhance JES3. This is probably the reason for > the SMP/E split. > > Note also that z/VSE is in a similar situation. As of June 1, 2021, > 21st Century Software Technologies, Inc. has a source code license > agreement for z/VSE. > https://urldefense.com/v3/__https://www.21stcenturysoftware.com/licens > e-z-vse-code-from-ibm/__;!!GryZGb6B1VCs0SfC!VlGquu4R4KAw1DxSOAe1BpRhwP > aIEwCmwu5D_NrY8t_cu_5TVm7-t8KeDWbLqALE$ > > > IBM is investing every thing in z/OS w/JES2, z/VM and z/Linux. z/VM only as > far as a hosting environment and no longer an application development / > deployment environment. > > -- > 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 USAA Classification: Public Disclaimer: This email and any attachments are the property of USAA and may contain confidential and/or privileged material. If you are not the intended recipient, any use, disclosure or copying of this email or any attachments is unauthorized. If you received this email in error, please immediately notify the sender and delete the email and any attachments from your computer. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: JES3 SMPE zone in Serverpac
Thanks Paul. We still need to have JES3 because as an ISV we do have to do some testing on a JES3 system. It would probably be safer to change our cloning jobs rather than ZONEMERGE the zones just in case an element with the same name as a JES3 element is added to z/OS. Keith > On 6 Oct 2022, at 13:41, Paul Gorlinsky wrote: > > JES3 is no longer being maintained by IBM product. Phoenix Software > International - https://phoenixsoftware.com/jes3plus.htm - is licensed to > maintain and enhance JES3. This is probably the reason for the SMP/E split. > > Note also that z/VSE is in a similar situation. As of June 1, 2021, 21st > Century Software Technologies, Inc. has a source code license agreement for > z/VSE. https://www.21stcenturysoftware.com/license-z-vse-code-from-ibm/ > > > IBM is investing every thing in z/OS w/JES2, z/VM and z/Linux. z/VM only as > far as a hosting environment and no longer an application development / > deployment environment. > > -- > 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: JES3 SMPE zone in Serverpac
I found a partial explanation for the changes to Serverpac in “z/os v2.5: Planning for Installation” - SDSF and JES2 are now delivered in the BCP zone but JES3 is delivered only if ordered. It makes sense that the SDSF/JES2/JES3 merge feature may not have been included in the z/OSMF version but having a separate target zone for JES3 upsets our cloning procedures. Keith > On 6 Oct 2022, at 13:00, Keith Gooding > <034af3894af4-dmarc-requ...@listserv.ua.edu> wrote: > > I installed z/os 2.5 using z/OSMF in October last year and noticed that the > installation placed JES3 in a target zone separate from the rest of z/os. I > do not recall being given the option to put JES2 and JES3 in the same > zone but I may have skipped over it . I know that there was such an option in > the ISPF version. > > Has anyone else experienced this and can anyone foresee any problems if I now > use the SMP/E ZONEMERGE command to merge the zones so that I can remove the > second target zone ? I see that the z/OS 2.5 program directory states that > all elements must be installed into the same target zone. > > Keith Gooding -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: JES3 SMPE zone in Serverpac
JES3 is no longer being maintained by IBM product. Phoenix Software International - https://phoenixsoftware.com/jes3plus.htm - is licensed to maintain and enhance JES3. This is probably the reason for the SMP/E split. Note also that z/VSE is in a similar situation. As of June 1, 2021, 21st Century Software Technologies, Inc. has a source code license agreement for z/VSE. https://www.21stcenturysoftware.com/license-z-vse-code-from-ibm/ IBM is investing every thing in z/OS w/JES2, z/VM and z/Linux. z/VM only as far as a hosting environment and no longer an application development / deployment environment. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: z/OSMF PSWI
I have applied the two missing PTFs and will IPL them in. But do we need to restart our PSWI of z/OS 2.5 to pick up the changes? The hold data says it's just a restart to pick up the changes but doesn't mention restarting the installation process for z/OS 2.5 PSWI. On 9/29/2022 7:44 AM, Marna WALLE wrote: Michael, Have you verified that you have all the correct Driving System PTFs installed, as indicated with FIXCAT IBM.DrivingSystem-RequiredService ?. Check out slide 33 onwards in this presentation that KurtQ did for the Z Exchange, https://www.newera-info.com/KQ1.html. It explains how a new master catalog can be used, including how the SSA (now called Temporary Catalog Alias) is to be specified and used. -Marna WALLE z/OS System Install and Upgrade IBM Poughkeepsie -- 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
JES3 SMPE zone in Serverpac
I installed z/os 2.5 using z/OSMF in October last year and noticed that the installation placed JES3 in a target zone separate from the rest of z/os. I do not recall being given the option to put JES2 and JES3 in the same zone but I may have skipped over it . I know that there was such an option in the ISPF version. Has anyone else experienced this and can anyone foresee any problems if I now use the SMP/E ZONEMERGE command to merge the zones so that I can remove the second target zone ? I see that the z/OS 2.5 program directory states that all elements must be installed into the same target zone. Keith Gooding -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ICHEINTY - RACF interface
Pierre, Could you please share with us what you tried that did not work? Making something reentrant is not generally at all difficult. Nor would I expect examples of service invocations to be in sys1.samplib. But I would expect them in the documentation. Peter Relson z/OS Core Technology Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
