10.1 Release Notes

[Ed_Arnold]

We implemented this in our V10 Level 2 test system :

APAR PI98845.

****************************************************************
* 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.


Not only did we implement it but we changed the source assembler.  Our test system is V2.3 so we updated the operating system parms in the assembler source as a test.

Originally:

ARSUSEC4 TITLE 'Assembler arsusec'                   
         sysstate archlvl=3,OSREL=ZOSV2R2,amode64=YES

New:

ARSUSEC4 TITLE 'Assembler arsusec'                   
         sysstate archlvl=6,OSREL=ZOSV2R3,amode64=YES

Ref:   https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieaa900/state.htm



Originally - everywhere there's a racroute macro, for example:

racroute  request=VERIFY,     validate user id and pw         +
      envir=CREATE,                                           +
      passchk=YES,                                            +
      acee=wkaceep,                                           +
      userid=ansi_cur_useridl,                                +
      passwrd=ansi_cur_passwdl,                               +
      worka=wkracwka,                                         +
      release=77A0,                                           +
...

New:

racroute  request=VERIFY,     validate user id and pw         +
      envir=CREATE,           create an acee                  +
      passchk=YES,                                            +
      acee=wkaceep,                                           +
      userid=ansi_cur_useridl,                                +
      phrase=ansi_cur_passwdl,                                +
      newphrase=ansi_new_passwdl,                             +
      worka=wkracwka,                                         +
      release=77B0,                                           +
...

Ref:  https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.ichc600/racrout.htm

Ed

[Ed_Arnold]

If you try to compile and execute the COBOL ARSUTBL exit sample you'll get the following:

ARS0160E ODV733 Unable to load module >/usr/lpp/ars/V10R1M0/bin/exits/arsutbl<. The return code is 103587  Srvr->MVS222<-

This is a 31/64 compatibility mismatch.

What the arsutbl exit is probably used for has been supplanted by new function available in PH12893.

Ed

[Ed_Arnold]

I've been getting a few questions lately about falling back from V10.1 during an upgrade.

I consulted with the lead architect who had this to say:

We support a customer trying to upgrade to 10.1, changing the db (e.g arsdb �u) � then if issues, they can fall back to 9.5 [executables - SARSLOAD and HFS] without restoring the database. 

However, always recommended to have db backup

Ed

[Ed_Arnold]

The PTF includes this ACTION HOLD item:

SPECIAL CONDITIONS:
ACTION:
   This SYSMOD ships a gson-2.8.1.jar .  After applying
   this SYSMOD, the path to gson-2.8.1.jar must be added
   to all ODWEK java API classpaths.  This includes the
   arsMSVR.sh midserver invocation script.

The sample in /usr/lpp/ars/V10R1M0/samples/arsMSVR.sh has been updated with the following:

OD_ODAPI=${OD_PATH}/www/api/ODApi.jar:${OD_PATH}/jars/gson-2.8.1.jar
export OD_ODAPI

Ed

[Ed_Arnold]

If you're considering implementing CMOD's Encryption at Rest, be sure that you're working from the September 5th, 2019 or later white paper.

It contains an update specifically for z/OS.

IBM Content Manager OnDemand Native Encryption

https://www-01.ibm.com/support/docview.wss?uid=swg27049568&aid=1

And a great companion doc:

Transporting AES encrypted data keys

http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP102736

Ed

[Justin Derrick]

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

Is this just on z/OS, or all platforms? 

-JD.

[Ed_Arnold]

Is this just on z/OS, or all platforms? 

-JD.

All platforms.

Ed

[Ed_Arnold]

Is there further guidance for CMOD exits for V10.1 beyond what's in the readme?

Now there is. 

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

Suggestions for improvement are welcome.

Ed

[Nolan]

Adding to Indexer parm tightened up for NODX

If you see this:

ARS5488E INVALID INDEXING PARM. ERROR OCCURS NEAR NAME

Then the solution is to change

INDEX03=PAGE_NO,FIELD1,(TYPE=GROUPRANGE)

to

INDEX03='PAGE_NO',FIELD1,(TYPE=GROUPRANGE)

Quotes are now enforced on the index name.

We found all of ours to clean up using this query.

select name  from $DBOWNER$.arsapp
where indexer like '%INDEXSTYLE=NODX%' and indexer like '%INDEX%=P%'

[Ed_Arnold]

If you try to compile and execute the COBOL ARSUTBL exit sample you'll get the following:

ARS0160E ODV733 Unable to load module >/usr/lpp/ars/V10R1M0/bin/exits/arsutbl<. The return code is 103587  Srvr->MVS222<-

This is a 31/64 compatibility mismatch.

What the arsutbl exit is probably used for has been supplanted by new function available in PH12893.

Ed

IBM Enterprise COBOL V6.3 is AMODE 64 capable.

https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&appname=gpateam&supplier=877&letternum=ENUSZP19-0488

Can I use that for my ARSUTBL exit?

Sadly, no.

Down in the fine print is, �No support for building AMODE 64 applications containing � or using the THREAD compiler option.�

THREAD is required.

Ed

[Ed_Arnold]

Sample JCL to compile a 64-bit arsutbl C exit:

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

Ed

[Ed_Arnold]

Twice recently I've had problems reported where people had carried forward their LE overrides from V9.5 to V10.1, causing abends in ARSSOCKD and in ARSODF.

Do not override the default LE settings anywhere in V10.1 unless you have re-run the LE tuning exercise.

Ed

[Ed_Arnold]

Report from the field of a tightening of the code:

This works in Version 9.5 and does not work in Version 10 � from the OS/390 Indexer.

The following line is missing the comma between �NO�� AND �(TYPE�

TRIGGER2=*,2,'THERE WAS NO' (TYPE=GROUP)

Ed

[Ed_Arnold]

PROBLEM:  Indexer Field definitions can no longer have an asterisk (*) as an offset.

The Application Indexer used to look like this:

TRIGGER1=*,1,'1',(TYPE=GROUP)          /* ANS:  Skip to channel 1 and print line */
FIELD1=5,3,9,(TRIGGER=1,BASE=0)
FIELD2=*,13,40,(TRIGGER=1,BASE=0)
FIELD3=*,98,10,(TRIGGER=1,BASE=0)

It needed to be changed to this:

TRIGGER1=*,1,'1',(TYPE=GROUP)          /* ANS:  Skip to channel 1 and print line */
FIELD1=5,3,9,(TRIGGER=1,BASE=0)
FIELD2=5,13,40,(TRIGGER=1,BASE=0)
FIELD3=5,98,10,(TRIGGER=1,BASE=0)
_________________________________________________

This used to be acceptable to the indexer:

TYPE=GROUP,BREAK=Y

Now you have to spell out the BREAK=YES

TYPE=GROUP,BREAK=YES
________________________________________________

This comment line���last line in the indexer parms. Period caused failure:

/* WARNING:  APP VALUES HAVE NOT BEEN CHECKED/UPDATED */.

Ed

[Ed_Arnold]

This worked on 9,5

INDEX1='INDEX_1',FIELD1,(TYPE=GROUP,BREAK=YES)                                                            /* INDEX_1 */
INDEX2='INDEX_2',FIELD2,(TYPE-GROUP,BREAK=NO)
INDEX3='INDEX_3',FIELD3,(TYPE-GROUP,BREAK=NO)

For version 10    TYPE-GROUP  had to change to  TYPE=GROUP

Ed