Author Topic: 10.1 Release Notes  (Read 5810 times)

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1027
    • View Profile
10.1 Release Notes
« on: May 25, 2017, 09:53:05 AM »
CMOD V10.1 is compiled with option ARCH( 8 ), meaning a z10 processor or newer is required.

Running on any processor prior to a z10 is likely to result in a S0C1.

Note:  z/OS 2.2 pre-reqs a z10 processor.

Also, CMOD V10.1 is compiled with the option TARGET(zOSV2R2).

Bottom line:  don't try to run CMOD V10.1 on z/OS 2.1.

Ed
« Last Edit: May 26, 2017, 05:53:55 AM by Ed_Arnold »
#zOS #ODF

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1027
    • View Profile
Re: 10.1 Release Notes
« Reply #1 on: June 30, 2017, 12:46:37 PM »
The 64 bit admin client does not work with PDF graphical indexer.

https://www.ibm.com/support/knowledgecenter/SSQHWE_10.1.0/com.ibm.ondemand.ir.doc/dodig087.htm


Ed
« Last Edit: June 27, 2018, 10:45:44 AM by Ed_Arnold »
#zOS #ODF

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1027
    • View Profile
Indexer parm tightened up
« Reply #2 on: June 26, 2018, 08:59:43 AM »
If you see this:


 2018-06-21 08:48:47.176639: ARS5481I TRIGGER1=*,1,X'F1',TYPE=(GROUP)
 2018-06-21 08:48:47.176654: ARS5481I FIELD1=0,2,8,(TRIGGER=1,BASE=0)
 2018-06-21 08:48:47.176663: ARS5481I INDEX1='SEGMENT_NUMBER',FIELD1,(TYPE=GROUP,BREAK=NO)
 2018-06-21 08:48:47.176677: ARS5481I INDEX2='REPORT_DATE',FIELD1,(TYPE=GROUP,BREAK=NO)
 2018-06-21 08:48:47.176685: ARS5481I INDEX3='PAGE_NO',FIELD1,(TYPE=GROUPRANGE)
 2018-06-21 08:48:47.176746: ARS1146I Loaded 0 rows into the database

2018-06-21 08:48:47.176646: ARS5488E INVALID INDEXING PARM. ERROR OCCURS NEAR TYPE


Note the message, error occurs near TYPE.  (This really should be a mixed case message, it's in the works.)

Then the solution is to change

TRIGGER1=*,1,X'F1',TYPE=(GROUP)

to

TRIGGER1=*,1,X'F1',(TYPE=GROUP)

Ed
« Last Edit: June 29, 2018, 07:58:34 AM by Ed_Arnold »
#zOS #ODF

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1027
    • View Profile
Performance Enhancement Available
« Reply #3 on: July 05, 2018, 02:30:47 PM »
APAR PI98845 adds the following to V10.1:

**************************************************************** 
* USERS AFFECTED: All Content Manager OnDemand for z/OS        * 
*                 10.1 using arsusec                           * 
**************************************************************** 
* PROBLEM DESCRIPTION: Provide an AMODE 64 sample arsusec      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
**************************************************************** 
With CMOD 10.1, the ARSSOCKD server runs as a 64-bit             
application.  In order to support existing AMODE 31 exits, glue   
code is provided at the cost of additional overhead.  In order   
to eliminate that cost for the arsusec exit, a sample AMODE 64   
arsusec assembler exit is provided.                               
#zOS #ODF

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1027
    • View Profile
Re: 10.1 Release Notes
« Reply #4 on: September 19, 2018, 09:17:46 AM »
LE storage usage completely changes in V10.1 compared to V9.x because of the exploitation of 64 bit.

   Ref:  Content Manager OnDemand for z/OS - Initial Recommended LE Settings

   http://www-01.ibm.com/support/docview.wss?uid=swg22011284

If you have overridden the default values you will want to run the LE storage tuning exercise again.

If you are not overriding the default values make sure you aren't choking off the values to a lesser amount.

How can you tell what values you're using and whether anything is being overridden?

Run with RPTOPTS(ON).  It costs nothing, just writes the LE options to SYSOUT.

There's more than one way to run with RPTOPTS(ON).  My favorite is to use the following parm line:

//  PARM='RPTOPTS(ON)/-S -I ARCHIVE -v'

I recommend if you have a test ARSSOCKD started task to change that now, adding RPTOPTS(ON). 

Ed
#zOS #ODF

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1027
    • View Profile
Re: 10.1 Release Notes
« Reply #5 on: September 27, 2018, 01:37:12 PM »
Following up on the previous append ----

As long as you have a test ARSSOCKD in addition to RPTOPTS(ON) please specify the -v for verbose option.

It lists the CMOD parms in effect in the output of the started task.

Neither RPTOPTS(ON) nor -v cost a thing as far as performance goes.

All either do is write options in effect to the output.

I consider both to be a definite good practice when sending output to support.

Ed
#zOS #ODF

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1027
    • View Profile
Re: 10.1 Release Notes
« Reply #6 on: December 07, 2018, 12:06:36 PM »
If you're using the old style parms on ARSSOCKD - or no parms at all - it's time to use the new parms when you roll out V10.1.

For example:

If you start ARSSOCKD with no parms at all that's fine, it means you're taking all of the defaults:

//ONMVS222 EXEC PGM=ARSSOCKD,REGION=0M,TIME=NOLIMIT


Recommend you change that when you initially bring up V10 to the following:

//ONMVS222 EXEC PGM=ARSSOCKD,REGION=0M,TIME=NOLIMIT,
//  PARM='/-S -I ARCHIVE -v'


Why?  Two reasons.

1. The -v means verbose.  All it does is echo the parms in effect to SYSOUT.  It costs nothing in performance, no traces, nothing like that.  It makes seeing what parms you have in effect (and communicating to that support) far easier than copying the ars.cfg and ars.ini files.

2. If requested to add a trace, it now becomes simple:

//ONMVS222 EXEC PGM=ARSSOCKD,REGION=0M,TIME=NOLIMIT,
//* PARM='/-S -I ARCHIVE -v'
//  PARM='/-S -I ARCHIVE -v -1 /tmp/ed.trc -2 ALL=15'


The -1 parm gives the path and file name for where to put the trace and the ALL=15 tells it trace everything.

In the preceding example to start a trace all you have to do is comment out the first parm line and uncomment the second and recycle ARSSOCKD.  Easy!
________________________________________________

If you start ARSSOCKD with parms that look something this

//ONMVS222 EXEC PGM=ARSSOCKD,REGION=0M,TIME=NOLIMIT,
// PARM=('/NEWARCH ARSSOCKD')


then change that to

//ONMVS222 EXEC PGM=ARSSOCKD,REGION=0M,TIME=NOLIMIT,
// PARM=('/-S -I NEWARCH -v')


Some shops already have VERBOSE on the old style parm line:

//ONMVS222 EXEC PGM=ARSSOCKD,REGION=0M,TIME=NOLIMIT,
// PARM=('/INSTANCE ARSSOCKD VERBOSE')


then change that to effectively the same thing, but still, the way to pre-position tracing parameters:

//ONMVS222 EXEC PGM=ARSSOCKD,REGION=0M,TIME=NOLIMIT,
// PARM=('/-S -I INSTANCE -v')
//*PARM=('/-S -I INSTANCE -v -1 /tmp/ed.trc -2 ALL=15')



Ed
#zOS #ODF

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1027
    • View Profile
The ARSTSPAC Job, Default in V10 is Partition-By-Growth
« Reply #7 on: February 15, 2019, 02:52:50 PM »
If you do a 3.12 and compare

  ARS.ARSV1010.SARSINST(ARSTSPAC)

with

  ARS.ARSV950.SARSINST(ARSTSPAC)

you'll see the addition of

  MAXPARTITIONS 2

in each CREATE TABLESPACE statement.

Per https://www.ibm.com/support/knowledgecenter/en/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_createtablespace.html

Table space type to create    Clauses to specify

Partition-by-growth           MAXPARTITIONS


Ed

#zOS #ODF

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1027
    • View Profile
ARSSTGET no longer shipped with V10.1
« Reply #8 on: February 20, 2019, 02:08:47 PM »
In the 8.5 readme doc there was mention there was a newer module,     
ARSZ390I , that going forward would be used in the newer sample code   
for newer exits ... but that the ARSSTGET module in existing exit pgms
would still be supported.

But ARSSTGET is no longer shipped as of V10.1.

You can change your exits to use ARSZ390I (or ARSZ390F) instead of     
ARSSTGET.  Refer to the shipped samples for ARSEXINP,           
ARSE2INP, or ARSEXANY.                                                 
                                                                       
So the question is can we still use the ARSSTGET load module in our older user exits     
without issue in V10.1?                                                         
                                                                       
Since CMOD development doesn't test ARSSTGET anymore there are no guarantees.

Ed   

07/16/2019 Update - was just talking with a CMOD shop that recently updated to V10.  They said that neither ARSZ390I nor ARSZ390F worked in their exit.  Their solution?  Call the C library functions like FREAD and FOPEN directly from the COBOL.     
« Last Edit: July 16, 2019, 01:37:48 PM by Ed_Arnold »
#zOS #ODF

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1027
    • View Profile
Re: 10.1 Release Notes
« Reply #9 on: February 27, 2019, 01:29:58 PM »
This is a z/OS 2.2 issue only.  Does not affect either 2.1 or 2.3.

CMOD exposes the following:

IF PE PTF UA96465 is installed and fixing HIPER APAR OA54570 PTF UA97572 is not

THEN page datasets can be filled and not freed even after the started task is ended.

This is more likely to occur with ODF but can also affect ARSSOCKD.

From OA54570:

Quote
ERROR DESCRIPTION:                                                 
Freemain processing does not indicate that we should free the     
auxiliary storage of any related in-flight IO, so when IO         
completes we do not release the backing frame and                 
instead lose the blockid. Later, SCM evacuation discovers         
the bad blockid and issues an ABENDC0D.                           
                                                                   
Additional problem can also occur, when an application uses       
IARVSERV TARGET_VIEW=HIDDEN, this results in storage being paged   
to auxiliary slots or SCM block.   Should this storage be         
freemained while having a status of hidden the aux slot/scm       
block can be orphaned.  This was introduced by changes made in     
APAR OA54820.  LE Stack management behaves in this manner.         
XPLINK applications that quickly create and destroy pthreads       
can observe aux slots orphaned at a high rate.                     

Ed

#zOS #ODF

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1027
    • View Profile
Reduction of CPU Usage When Loading
« Reply #10 on: April 02, 2019, 11:53:31 AM »
PH09636 / UI61995

No action required, just install the PTF.

Ed

07/16/2019 update:  and be sure to add PH10168 / UI62202 which fixes the PE of PH09636 / UI61995.
« Last Edit: July 16, 2019, 01:40:28 PM by Ed_Arnold »
#zOS #ODF

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1027
    • View Profile
Re: 10.1 Release Notes
« Reply #11 on: May 16, 2019, 07:38:00 AM »
Had two reports recently of problems with the ANYEXIT moving to CMOD V10.1.

Both were resolved by changing the code in the exit.

1. In the first ANYEXIT a file was not being closed, resulting in the following:

ARS4328E ARSSAPIR failed: return code is 00000006 00000000(04200000).

The "ARS4328E ARSSAPIR failed: return code is 00000006 00000000(04200000)" is a dynamic unallocation failure, 0420 being the reason code:
Meaning: Specified ddname or dsname associated with an open data set. (ddname allocation, concatenation, deconcatenation, unallocation, dsname allocation).


2. In the second ANYEXIT, the following was encountered:

$HASP708 QUIKLOAD SYSIN    OPEN FAILED                               
RC=03 DATA SET ALREADY OPENED                                       
DSNAME=FEFG.QUIKLOAD.JOB12234.D0000101.?                             
IEC141I 013-C0,IGG0199G,QUIKLOAD,ARSLOAD,SYSIN                   
BPXP018I THREAD 16BAD00000000000, IN PROCESS 16780854, ENDED WITHOUT BEING UNDUBBED WITH COMPLETION CODE 04013000, AND REASON CODE 000000C0.       

The report received on the resolution of that issue was "I changed the ACCEPT by on OPEN FILE and that works, please add         
somewhere in the DOC that the behavior of the ARSLOAD changed and you can't use SYSIN anymore with EXIT called by ARSLOAD."

Ed                                                   
« Last Edit: May 16, 2019, 07:56:18 AM by Ed_Arnold »
#zOS #ODF

geoffwilde

  • Administrator
  • Full Member
  • *****
  • Posts: 249
  • z/os erm icn
    • View Profile
Re: 10.1 Release Notes
« Reply #12 on: May 17, 2019, 12:38:08 PM »
If you do a 3.12 and compare

  ARS.ARSV1010.SARSINST(ARSTSPAC)

with

  ARS.ARSV950.SARSINST(ARSTSPAC)

you'll see the addition of

  MAXPARTITIONS 2

in each CREATE TABLESPACE statement.

Per https://www.ibm.com/support/knowledgecenter/en/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_createtablespace.html

Table space type to create    Clauses to specify

Partition-by-growth           MAXPARTITIONS


Ed



Ed, how would you change this post install?  Does this need to be done during an upgrade/install process, or can it be changed after the fact?
President, OnDemand Users Group
Lead Technician for Content Manager OnDemand @
US Bank
#zSeries

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1027
    • View Profile
Re: 10.1 Release Notes
« Reply #13 on: June 13, 2019, 01:19:41 PM »
Ed, how would you change this post install?  Does this need to be done during an upgrade/install process, or can it be changed after the fact?

* action taken                                                         
                                                                       
Development has just shipped a new function PTF which I believe resolves this issue.                                                             
                                                                       
APAR PH12893 / PTF UI63542                                             
                                                                       
PROBLEM SUMMARY:                                                       
****************************************************************       
* USERS AFFECTED: All Content Manager OnDemand for z/OS 10.1   *       
*                 and above                                    *       
****************************************************************       
* PROBLEM DESCRIPTION: 1. The applgrp data tablespaces are     *       
*                      created with SEGSIZE 64.  SEGSIZE is    *       
*                      deprecated.                             *       
*                      2. The applgrp data tablespaces are     *       
*                      created with MAXPARTITIONS 1.           *       
****************************************************************       
1 ARGSEG was specifying SEGSIZE 64                                     
2 ARGSEG was always using 1 for the MAXPARTITIONS value                 
                                                                       
COMMENTS:                                                               
1. ARGSEG will no longer specify SEGSIZE 64                             
2. ARGSEG is enhanced to determine a MAXPARTITIONS value when a         
new ars.cfg setting is specified:                                       
                                                                       
ARSMVS_DB_DSSIZE                                                       
                                                                       
Specifies the value to use for the DSSIZE value for the                 
application group data table tablespaces.  This must be a               
power-of-two in the range of 1 - 256.                                   
                                                                       
When not specified, the application group data table tablespaces       
\ will be created with a MAXPARTITIONS 1, and the PRIQTY and           
SEQTY will be chosen based on the max rows for the application         
group.  The INDEX will be created with a PRIQTY and SECQTY also         
based on the max rows.                                                 
                                                                       
When ARSMVS_DB_DSSIZE specifies a valid value, that value will         
be used in the DSSIZE N G clause when creating the application         
group data table tablespace.  Additionally, the PRIQTY and             
SECQTY will default to -1, and the MAXPARTITIONS will be set           
based on the application group max rows value.  Any index               
created will specify a PIECESIZE based on the max rows, and             
default to a PRIQTY and SECQTY of -1                                   
                                                                       
Regardless of ARSMVS_DB_DSSIZE being specified or not, the             
ARSMVS_MAXROWS_PRIQTY, ARSMVS_MAXROWS_SECQTY,                           
ARSMVS_NOMAXROWS_PRIQTY, ARSMVS_NOMAXROWS_SECQTY,                       
ARSMVS_MAXROWS_INDEX_PRIQTY, ARSMVS_MAXROWS_INDEX_SECQTY,               
ARSMVS_NOMAXROWS_INDEX_PRIQTY, and ARSMVS_NOMAXROWS_INDEX_SECQTY       
can be used to override the PRIQTY and SECQTY values chosen by         
CMOD.                                                                   
                                                                       
For example, with ARSMVS_DB_DSSIZE=4 and an applgrp with a max         
rows of 50,000,000, the tablespace might get created with:             
                                                                       
CREATE TABLESPACE DAA23 IN ARSDBA10 USING STOGROUP SYSDEFLT             
PRIQTY -1 SECQTY -1  MAXPARTITIONS 2  DSSIZE 4 G  BUFFERPOOL BP0       
                                                                       
and the index with:                                                     
                                                                       
CREATE INDEX ARSUSE10.DAA23_0 ON ARSUSE10.DAA23                         
( REPORT_NUMBER ) USING STOGROUP SYSDEFLT PRIQTY -1 SECQTY -1           
BUFFERPOOL BP0 PIECESIZE 512 M
                                         
                                                                       
This is heavier into Db2 than I usually get.  Hopefully your DBA's can sort this all out for you.

Ed                                                                       
     
                         
#zOS #ODF

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1027
    • View Profile
Re: 10.1 Release Notes
« Reply #14 on: June 19, 2019, 09:47:19 AM »
Starting in 10.1.0.1,

if -h HOST:PORT is used

(i.e. a colon [:] is used as a separator between hostname and port),

the connection will fail.

Use a comma instead.

Ed
#zOS #ODF