Author Topic: CMOD 10.5 Release Notes  (Read 6448 times)

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1199
    • View Profile
CMOD 10.5 Release Notes
« on: August 10, 2020, 11:51:57 AM »
This is an oldie that tripped up an install.

z/OS V2.3 is a pre-req, but also this very old LE APAR / PTF from 2017:

https://www.ibm.com/support/pages/apar/PI80298

CEE3559S External variable _StdStringExponentialAllocation...not found in DLL C128

Ed

#zOS #ODF

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1199
    • View Profile
Needs Clean SMP/E Zones
« Reply #1 on: January 13, 2021, 07:37:54 AM »
When I tried to install 10.5 in a zone that had a previous CMOD release I could never get it to work.

It never cleaned up properly the old release.

So I installed 10.5 in a fresh SMP/E.

Ed
#zOS #ODF

rjchavez

  • Jr. Member
  • **
  • Posts: 67
    • View Profile
Re: Needs Clean SMP/E Zones
« Reply #2 on: January 14, 2021, 10:39:49 AM »
When I tried to install 10.5 in a zone that had a previous CMOD release I could never get it to work.

It never cleaned up properly the old release.

So I installed 10.5 in a fresh SMP/E.

Ed
I always install into a new zone in order to preserve and maintain multiple releases.

chuckalugk

  • Jr. Member
  • **
  • Posts: 23
    • View Profile
Re: CMOD 10.5 Release Notes
« Reply #3 on: January 15, 2021, 06:21:37 PM »
Hi Ed. What is the part number for cmod and odf 10.5 for z/OS?  My passport advantage only seems to show System I

rjchavez

  • Jr. Member
  • **
  • Posts: 67
    • View Profile
Re: CMOD 10.5 Release Notes
« Reply #4 on: January 16, 2021, 09:04:34 AM »
FYI, I think you need to use ShopZ to order

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1199
    • View Profile
Re: CMOD 10.5 Release Notes
« Reply #5 on: January 23, 2021, 04:11:45 PM »
FYI, I think you need to use ShopZ to order

Correct!

And what you want to order are the FMIDs for CMOD and ODF, H272A50 and J272A52.

Ed

#zOS #ODF

chuckalugk

  • Jr. Member
  • **
  • Posts: 23
    • View Profile
Re: CMOD 10.5 Release Notes
« Reply #6 on: February 01, 2021, 05:56:45 AM »
Is there a link to 10.5 installation for z/OS?  I recall 10.1 having jobs to run that setup the SMPE zones and DDDEF.  When doing shopz and trying to run the job it is failing on GIM54501S ** ALLOCATION FAILED FOR SMPLOG BECAUSE THERE IS NO DD STATEMENT IN THE JCL AND NO DDDEF ENTRY IN THE GLOBAL
             ZONE.                                                                                                     

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1199
    • View Profile
Re: CMOD 10.5 Release Notes
« Reply #7 on: February 02, 2021, 11:54:20 AM »
Is there a link to 10.5 installation for z/OS?  I recall 10.1 having jobs to run that setup the SMPE zones and DDDEF.  When doing shopz and trying to run the job it is failing on GIM54501S ** ALLOCATION FAILED FOR SMPLOG BECAUSE THERE IS NO DD STATEMENT IN THE JCL AND NO DDDEF ENTRY IN THE GLOBAL
             ZONE.                                                                                                   

I think what you're looking for is the Program Directory of the base FMID for CMOD 10.5:

https://www.ibm.com/support/pages/node/608849

Ed
#zOS #ODF

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1199
    • View Profile
PH31060 may cause an error in ARSUUPDX exit
« Reply #8 on: March 23, 2021, 09:54:53 AM »
PH31060 -                                                           
  ARSUUPDT FIELD ARSCSXITUPDTEXIT-FILENAME VALUE CHANGED IN VERSION 10.1                                                             
  PROBLEM SUMMARY:                                                   
  ****************************************************************   
  * USERS AFFECTED: All Content Manager OnDemand for z/OS 10.1   *   
  *                 and above using arsload -E and loading files *   
  *                 from the JES spool.                          *   
  ****************************************************************   
  * PROBLEM DESCRIPTION: When loading files from the JES spool   *   
  *                      and specifying the -E option to         *   
  *                      arsload, the arsuupdt exit              *   
  *                      ArsCSXitUpdtExit->pFileName parameter   *   
  *                      receives a pointer to a string that     *   
  *                      starts with 'DD:'.  Previously it       *   
  *                      pointed to a string containing a        *   
  *                      psudo-filename like                     *   
  *                      /arsa/tmp/MVS042.BPXAS.ADFOUT.STD.20110 *   
  *                      5.1804170016779814.ARD.                 *   
  ****************************************************************   
  ARGLOAD was inadvertently changed to pass the DD name as the       
  pFileName parameter when processing a spool files.                 
  PROBLEM CONCLUSION:                                               
  ARGLOAD is changed to pass the psudo-filename as the pFileName     
  parameter when processing a spool file. 


Had a report of loads failing.

(a) be sure to test the exit after applying this maintenance

(b) Level 2 might have a workaround

Ed
#zOS #ODF

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1199
    • View Profile
Re: CMOD 10.5 Release Notes
« Reply #9 on: March 23, 2021, 04:24:40 PM »
Using 31-bit COBOL exits?

New DD def per the ++ACTION HOLD

++HOLD(UI74252) SYSTEM FMID(H272A50) REASON(ACTION) DATE(21062)     
  COMMENT(                                                           
  New DD definition to be added:  ARSSYSOU.     
                   
  Changed DD definition: SYSOUT as used by the CMOD. 
               
  This fix changes the LE runtime options for 31-bit exits.   
     
  Previously, any 31-bit exit COBOL DISPLAYs appeared in SYSOUT.
   
  With this change 31-bit exit COBOL displays will now appear in     
  the ARSSYSOU DD definition.               
                       
  This change fixes a problem with a 64-bit LE enclave interfering   
  with 31-bit LE enclave usage.   
                                   
  It does this by separating 31-bit enclave usage of the MSGFILE     
  with the default of SYSOUT from the 64-bit LE enclave usage of     
  the MSGFILE with the default of SYSOUT.     
                       
  This change will cause any 31-bit exit COBOL DISPLAYs to now       
  appear on a DD of ARSSYSOU instead of a DD of SYSOUT. 
           
  If customers are relying on the output from the exits appearing   
  on the SYSOUT DD, the ARSSYSOU DD needs to be used instead.).
                                                               
#zOS #ODF

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1199
    • View Profile
Malformed PTFs Were Shipped By IBM From Boulder
« Reply #10 on: April 14, 2021, 10:42:33 AM »
Red Alert

PTF service orders from 4 December 2020 to 10 December 2020 need to be reviewed.

CMOD PTFs are on the list.

https://www.ibm.com/support/pages/node/6441973

Ed
#zOS #ODF

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1199
    • View Profile
Re: CMOD 10.5 Release Notes
« Reply #11 on: August 30, 2021, 08:19:45 AM »
Customers installing the PTF for PH31060 should also install PH36829 at the same time.

This affects customers at both the 10.1 and the 10.5 level.

Ref (a):  https://www.ibm.com/support/pages/apar/PH31060

Ref (b):  https://www.ibm.com/support/pages/apar/PH36829     

PH31060 fixed an incompatibility issue with the ARSUUPDT exit. 

Unfortunately, at the same time it exposed an issue in some exits which was then resolved by PH36829.

Note the following in the HOLD ACTION for PH36829:

This sysmod updates INSTALLDIR/bin/exits/arsusec, arsuupdt, and   
     arsuupdt. If the installation has copied those to another         
     location, they will need to get copied again.   
                 
                                                                       
This sysmod updates SARSINST(ARSUSEC, ARSUPERM, and ARSUUPDT) to 
     allow them to call a COBOL program. 

If you have been compiling   
     SARSINST(ARSUSECC or ARSUPERC) solely in order to call a COBOL   
     program named ARSUSECX, the supplied bin/exits/arsusec and       
     arsuperm will now do that without needing to compile ARSUSECC or 
     ARSUPERC.

If you have been compiling SARSINST(ARSUUPDC) only in   
     order to call a COBOL program named ARSUUPDX, the supplied       
     bin/exits/arsuupdt will now do that without needing to compile   
     ARSUUPDC. 

If you are compiling SARSINST(ARSUSECC, ARSUPERC,     
     and/or ARSUUPDC) for other changes, the changes will need to get 
     reworked in the updated SARSINST(ARSUSECC, ARSUPERC, and/or       
     ARSUUPDC).


In short, the PTFs for these two APARs should be installed together.

Of course, ensure any exits are tested before upgrading to production.
#zOS #ODF

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1199
    • View Profile
Re: CMOD 10.5 Release Notes
« Reply #12 on: September 23, 2021, 06:57:38 AM »
The doc

Further guidance for Content Manager OnDemand exits beyond what's in the V10 readmes

has had some minor updates:

https://www.ibm.com/support/pages/node/1165276

Ed
#zOS #ODF

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1199
    • View Profile
Re: CMOD 10.5 Release Notes
« Reply #13 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
#zOS #ODF

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1199
    • View Profile
ODF Users
« Reply #14 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
#zOS #ODF