76
z/OS Server / Re: Recommended DB2 on z/OS Service, V12
« on: March 30, 2022, 11:29:25 AM »
I'm still maintaining this. Noting that there's been nothing new since my last update.
Ed
Ed
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
77
Report Indexing / Re: Bad Character in data file
« on: March 14, 2022, 09:17:10 AM »
Echoing what others have already said ---
We have seen this usually with a German "sharp S" ---- let me see if I can cut and paste one in here:
What is sharp S in German?
Image result for german sharp s
In German orthography, the letter ß, called Eszett (IPA: [ɛsˈtsɛt] ess-TSET) or scharfes S (IPA: [ˌʃaʁfəs ˈʔɛs], lit. "sharp S"),
When loading it'll often get converted to "ss" or one extra character. If the field is defined as length 10, and the sharp s makes it go to 11, then boom!
Ed
We have seen this usually with a German "sharp S" ---- let me see if I can cut and paste one in here:
What is sharp S in German?
Image result for german sharp s
In German orthography, the letter ß, called Eszett (IPA: [ɛsˈtsɛt] ess-TSET) or scharfes S (IPA: [ˌʃaʁfəs ˈʔɛs], lit. "sharp S"),
When loading it'll often get converted to "ss" or one extra character. If the field is defined as length 10, and the sharp s makes it go to 11, then boom!
Ed
78
z/OS Server / ODF Users
« on: March 08, 2022, 10:42:47 AM »
10.5.0.4 did not pick up PH37343/UI76042:
S0C4 IN ARSRPRNB
PROBLEM SUMMARY:
****************************************************************
* USERS AFFECTED: All ODF 10.1 and above users using *
* submitted job processing. *
****************************************************************
* PROBLEM DESCRIPTION: ODF is encountering an ABEND0C4 in *
* ARSRPRNB+01D8 when ARSRPSUB starts up. *
****************************************************************
ODF is using the wrong length to clear memory.
PROBLEM CONCLUSION:
ODF is modified to use the correct length
Ed
S0C4 IN ARSRPRNB
PROBLEM SUMMARY:
****************************************************************
* USERS AFFECTED: All ODF 10.1 and above users using *
* submitted job processing. *
****************************************************************
* PROBLEM DESCRIPTION: ODF is encountering an ABEND0C4 in *
* ARSRPRNB+01D8 when ARSRPSUB starts up. *
****************************************************************
ODF is using the wrong length to clear memory.
PROBLEM CONCLUSION:
ODF is modified to use the correct length
Ed
79
MP Server / Re: ARSJESD Issue in 10.5.0.4
« on: March 03, 2022, 02:34:41 PM »
Hello JeanineJ --- I don't have an answer for your issue but want to add some background info.
arsjesd is the only piece of code that starts with "ARS" that doesn't come CMOD development.
It's a part of PSF - the Print Services Facility product. I asked the CMOD Chief Architect about that many moons ago and his answer was "historical reasons."
Anyway - just checking, is this the started task with PGM=APFKAFPD ?
Make sure you have all of the service for whatever it is that is the PGM=.
Ed Arnold
arsjesd is the only piece of code that starts with "ARS" that doesn't come CMOD development.
It's a part of PSF - the Print Services Facility product. I asked the CMOD Chief Architect about that many moons ago and his answer was "historical reasons."
Anyway - just checking, is this the started task with PGM=APFKAFPD ?
Make sure you have all of the service for whatever it is that is the PGM=.
Ed Arnold
80
z/OS Server / Re: z/OS V2.5 Release Notes
« on: March 02, 2022, 08:19:36 AM »
Content Manager OnDemand exposed the following issue:
After upgrading z/OS from 2.3 to 2.5 loading OnDemand AFP report in batch results in a loop along with looping ARSSOCK and ARSODF address spaces.
After cancelling the AFP load job that ran for 12 min instead of 1-2 seconds, ARS* address spaces continued to loop and had to be cancelled.
Attempted run of OAM cycle and OAM looped and would not finish processing the cycle and had to be cancelled (OSMC STOP command would not work).
Resolution: APAR PH44548 in Query Monitor product
After upgrading z/OS from 2.3 to 2.5 loading OnDemand AFP report in batch results in a loop along with looping ARSSOCK and ARSODF address spaces.
After cancelling the AFP load job that ran for 12 min instead of 1-2 seconds, ARS* address spaces continued to loop and had to be cancelled.
Attempted run of OAM cycle and OAM looped and would not finish processing the cycle and had to be cancelled (OSMC STOP command would not work).
Resolution: APAR PH44548 in Query Monitor product
81
z/OS Server / Re: z/OS V2.5 Release Notes
« on: February 17, 2022, 08:41:45 AM »
LE for COBOL issue.
Symptom is arsload started task can't be brought down with a normal STOP, has to be cancelled to terminate.
PH43756: Loop during thread termination starting with IGZETHT and involving repeated invocation of IGZXWAIT
During COBOL runtime thread termination in a multithreaded environment, IGZXWAIT is repeatedly driven waiting on a state that never arrives.
Symptom is arsload started task can't be brought down with a normal STOP, has to be cancelled to terminate.
PH43756: Loop during thread termination starting with IGZETHT and involving repeated invocation of IGZXWAIT
During COBOL runtime thread termination in a multithreaded environment, IGZXWAIT is repeatedly driven waiting on a state that never arrives.
82
z/OS Server / Re: z/OS V2.4 Release Notes
« on: February 17, 2022, 08:41:25 AM »
LE for COBOL issue.
Symptom is arsload started task can't be brought down with a normal STOP, has to be cancelled to terminate.
PH43756: Loop during thread termination starting with IGZETHT and involving repeated invocation of IGZXWAIT
During COBOL runtime thread termination in a multithreaded environment, IGZXWAIT is repeatedly driven waiting on a state that never arrives.
Symptom is arsload started task can't be brought down with a normal STOP, has to be cancelled to terminate.
PH43756: Loop during thread termination starting with IGZETHT and involving repeated invocation of IGZXWAIT
During COBOL runtime thread termination in a multithreaded environment, IGZXWAIT is repeatedly driven waiting on a state that never arrives.
83
MP Server / Re: 10.5.0.4 ifix is only for the FTS server
« on: February 16, 2022, 09:51:03 AM »
Note that the the 10.5.0.4 ifix (10.5.0.4.001) fixes the obsolete (but not vulnerable) files shipped with the FTS server:
Ed
Quote
2) Full Text Search Server History
2.10.5.0.4) Release (10.5.0.4)
pre-reqs:
- Previous install of Full Text Server 10.5.0.0
Enhancements:
- Upgrade of the Full Text Server to 5.5.8.0-1.1-76
- Log4j remediation for CVE-2021-44228, CVE-2021-44832, CVE-2021-45046,
and CVE-2021-45105.
Ed
84
Windows Client / There is no 10.5.0.4 Windows Client Update
« on: February 09, 2022, 12:35:48 PM »
10.5.0.4 is a server-only and ODWEK-only release, primarily to incorporate log4j remediation.
There is no 10.5.0.4 Windows client release.
As of this writing, there are no plans to come out with a 10.5.0.4 Windows client.
Probably what will happen is that level will just be skipped - next Windows client will be 10.5.0.5.
Ed
There is no 10.5.0.4 Windows client release.
As of this writing, there are no plans to come out with a 10.5.0.4 Windows client.
Probably what will happen is that level will just be skipped - next Windows client will be 10.5.0.5.
Ed
85
MP Server / 10.5.0.4 ifix is only for the FTS server
« on: February 07, 2022, 11:32:00 AM »
The interim fix for the FTS server is now out (10.5.0.4.001) on fix central.
It looks like it's an OD server fix but once you dig deep enough you will see it is only for the FTS server.
You can search using the normal parameters on fix central (product, installed version, platform).
For instance, if you search on “Content Manager OnDemand for Multiplatforms”, “10.5.0.4”, and “AIX 64-bit, pSeries” and then select “Browse for fixes” you will see what looks to be an interim fix for the OD server product because the Abstract states “This I-fix contains the SERVER files and readme.”
But, if you select this interim fix and continue you will then see the list of files:
odftsaix.bin
readfts.txt
It's only a fix for the FTS server.
Note that the FTS server only runs on AIX, Linux, Windows and zLinux
It looks like it's an OD server fix but once you dig deep enough you will see it is only for the FTS server.
You can search using the normal parameters on fix central (product, installed version, platform).
For instance, if you search on “Content Manager OnDemand for Multiplatforms”, “10.5.0.4”, and “AIX 64-bit, pSeries” and then select “Browse for fixes” you will see what looks to be an interim fix for the OD server product because the Abstract states “This I-fix contains the SERVER files and readme.”
But, if you select this interim fix and continue you will then see the list of files:
odftsaix.bin
readfts.txt
It's only a fix for the FTS server.
Note that the FTS server only runs on AIX, Linux, Windows and zLinux
86
OD/WEK & JAVA API / There is no 10.5.0.4 Windows Client Update But There Is a 10.5.0.4 ODWEK Client
« on: February 07, 2022, 11:25:49 AM »
10.5.0.4 is primarily a server-only release, mostly to incorporate log4j remediation.
There is no 10.5.0.4 Windows client release.
As of this writing, there are no plans to come out with a 10.5.0.4 Windows client.
Probably what will happen is that level will just be skipped - next Windows client will be 10.5.0.5.
However, there is a 10.5.0.4 ODWEK client that picks up some minor fixes.
Ed
There is no 10.5.0.4 Windows client release.
As of this writing, there are no plans to come out with a 10.5.0.4 Windows client.
Probably what will happen is that level will just be skipped - next Windows client will be 10.5.0.5.
However, there is a 10.5.0.4 ODWEK client that picks up some minor fixes.
Ed
87
MP Server / Reminder - CMOD V10.1 End of Service 30 April 2022
« on: January 31, 2022, 02:09:59 PM »
90 days out.
Ed
Ed
88
z/OS Server / Re: CMOD 10.5 Release Notes
« on: January 26, 2022, 12:05:35 PM »
The end all and be all for 10.5 and log4j remediation is this doc:
https://www.ibm.com/support/pages/node/6525888
Highly recommended is the 10.5.0.4 fixpack as it removes vulnerable releases of log4j from the installation directories.
https://www.ibm.com/support/pages/how-do-ptf-numbers-relate-content-manager-ondemand-product-version-numbers-and-maintenance-fix-packs
Ed
https://www.ibm.com/support/pages/node/6525888
Highly recommended is the 10.5.0.4 fixpack as it removes vulnerable releases of log4j from the installation directories.
https://www.ibm.com/support/pages/how-do-ptf-numbers-relate-content-manager-ondemand-product-version-numbers-and-maintenance-fix-packs
Ed
89
z/OS Server / Re: 10.1 Release Notes
« on: January 26, 2022, 12:03:18 PM »
The end all and be all doc for 10.1 log4j remediation is this techdoc:
https://www.ibm.com/support/pages/node/6525892
Highly recommend the 10.1.0.10 fixpack no matter whether you're directly affected or not as it completely shuts down questions about log4j and CMOD.
https://www.ibm.com/support/pages/how-do-ptf-numbers-relate-content-manager-ondemand-product-version-numbers-and-maintenance-fix-packs
Reminder - V10.1 goes EoS all platforms April 30th, 2022.
Ed
https://www.ibm.com/support/pages/node/6525892
Highly recommend the 10.1.0.10 fixpack no matter whether you're directly affected or not as it completely shuts down questions about log4j and CMOD.
https://www.ibm.com/support/pages/how-do-ptf-numbers-relate-content-manager-ondemand-product-version-numbers-and-maintenance-fix-packs
Reminder - V10.1 goes EoS all platforms April 30th, 2022.
Ed
90
MP Server / Re: Upgrade CMOD 8.5 to 10.5
« on: January 21, 2022, 12:28:34 PM »
Andre - sadly I don't have the requirements for those levels anymore.
But usually the CMOD pre-req doc always says "such and such a level or later."
So you might want to try upgrading everything non-CMOD first and save it for last.
Ed
But usually the CMOD pre-req doc always says "such and such a level or later."
So you might want to try upgrading everything non-CMOD first and save it for last.
Ed