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
Thanks -
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
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,
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
>
>
>
>
>
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
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,
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
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:
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
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
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
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
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
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 /
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
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
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:
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
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
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
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,
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
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
23 matches
Mail list logo
