Author Topic: z/OS V2.3 Release Notes  (Read 7517 times)

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1147
    • View Profile
Re: z/OS V2.3 Release Notes
« Reply #15 on: July 17, 2018, 01:29:06 PM »
Looks like you're picking up a default.

Ed
#zOS #ODF

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1147
    • View Profile
Re: z/OS V2.3 Release Notes
« Reply #16 on: July 19, 2018, 07:01:29 AM »
More recommended maintenance:

After applying z/OS maintenance I can no longer retrieve OnDemand V2 migrated documents.

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

Ed

#zOS #ODF

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1147
    • View Profile
LE PTF Changes Behavior of ABENDs
« Reply #17 on: August 16, 2018, 11:25:38 AM »
LE APAR PI93384

Quote

PROBLEM SUMMARY:                                                   
****************************************************************   
* USERS AFFECTED:                                              *   
* Users of POSIX(ON) Language Environment                      *   
* applications which expect to roll back the                   *   
* in-progress update to the recoverable                        *   
* resources when SIGXCPU is received and                       *   
* there are no signal handlers registered for                  *   
* SIGXCPU by the applications.                                 *   
****************************************************************   
* PROBLEM DESCRIPTION:                                         *   
* When Language Environment applications                       *   
* are terminated with return code 3000                         *   
* due to unhandled SIGXCPU under                               *   
* POSIX(ON), the in-progress updates to                        *   
* recoverable resources would be                               *   
* committed instead of being rolled back.                      *   
****************************************************************   
* RECOMMENDATION:                                              *   
****************************************************************   
See the problem description.                                       
                                                                   
PROBLEM CONCLUSION:                                               
The code has been changed to ensure that, when a Language         
Environment application is terminated with return code 3000 due   
to unhandled SIGXCPU under POSIX(ON), the ThliAbnormalTerm flag   
for all the threads in the process which receives SIGXCPU are     
set to ON to notify Unix System Service to propagate the flag     
to TCB_PTHREADTERMABNORMAL. The TCB_PTHREADTERMABNORMAL flags     
are set to ON to indicate that the TCBs are terminated             
abnormally. Then DB2 or other resource managers can check the     
TCB_PTHREADTERMABNORMAL flags to determine commit or roll back     
the in-progress transactions.                                     
                                                                   
TEMPORARY FIX:                                                     
*********                                                         
* HIPER *                                                         
*********                                                         

In other words

OLD BEHAVIOR - the in-progress updates to recoverable resources would be committed instead of being rolled back.

NEW BEHAVIOR - DB2 or other resource managers can check the TCB_PTHREADTERMABNORMAL flags to determine commit or roll back the in-progress transactions.    Which in the case of CMOD because there are no signal handlers registered for SIGXCPU by the applications means that things uncommitted get rolled back.

Ed
#zOS #ODF

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1147
    • View Profile
Re: z/OS V2.3 Release Notes
« Reply #18 on: March 05, 2019, 12:26:27 PM »
Do you have OAM toleration APAR OA51129 already installed on your z/OS V2.1 or V2.2 system?

If so, then you're all set and the rest of this doesn't apply to you.

If, however, you're upgrading to V2.3 and haven't put on the following toleration APAR yet then this applies:


1) APAR OA51129 has the following warning message:                         
                                                                           
   "**Warning** Information APAR II14842 should be reviewed before         
   applying OA51129. If II14842 precautions are not observed then         
   there may be a potential loss of object addressability."               
   http://www-01.ibm.com/support/docview.wss?uid=isg1OA51129               
                                                                           
2) Technote to alert customers about the possible effects:                 
                                                                           
   OAM Object Required Considerations prior to installing OA51129 or       
   upgrading to z/OS 2.3                                                   
   https://www-01.ibm.com/support/docview.wss?uid=ibm10728703             
                                                                           
3) AI that was included in PTF UA91367                                     
                                                                           
   "Prior to coexistence APAR OA51129, OAM s object support would         
   maintain collection information in two places; in DB2 (in the           
   OAM collection table) and also in the catalog. With new function       
   introduced in z/OS V2R3 (support for multiple OAM instances to         
   exist on the same LPAR) and requirements around that support,           
   OAM is now only going to maintain this collection information in       
   DB2 (regardless of whether the new support is being used). For         
   most customers, the information that was in the catalog and in         
   DB2 should be in synch; however, there is no absolute guarantee         
   that this is the case. As we have discovered, the most likely           
   cause for an out-of-synch condition is the customer themselves         
   needing to clean-up and/or rebuild their collection environment.       
   To be as proactive as possible information APAR II14842 was             
   created along with a REXX comparison tool for customers to run.         
   This tool compares the OAM collection information in the catalog       
   and in DB2 and surfaces any inconsistencies that it detects. If         
   the tool is not run, this out-of-synch condition could exist for       
   years, until the customer goes and retrieves an object from that       
   particular collection."                                                 
                                                                           
4) Informational APAR II14842 with the CATDB2CP tool                       
                                                                           
   http://www-01.ibm.com/support/docview.wss?uid=isg1II14842
       
#zOS #ODF

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1147
    • View Profile
Re: z/OS V2.3 Release Notes
« Reply #19 on: July 01, 2019, 11:56:54 AM »
Abstract:

EXCEPTION S0C4 IN IGZXPRS1 OFFSET X'3E2'

ERROR DESCRIPTION:
                                           
s0c4 exception in IGZXPRS1 due to an invalid GBCP address.     
Failing instruction is an OI (9601 E004).  The failing program
is compiled with THREAD, DLL, EXPORTALL, and                   
PGMNAME(LONGMIXED), and when program is linked on z/OS 2.3.   
                                                               
LOCAL FIX:
                                                   
Link on z/OS 2.1 or 2.2 

PI98700   

PROBLEM SUMMARY:                                               
****************************************************************
* USERS AFFECTED: Users of Enterprise COBOL V5 and later       *
*                 releases, running COBOL programs compiled    *
*                 with the DLL option.                         *
****************************************************************
* PROBLEM DESCRIPTION: Runtime ABEND S0C4 in IGZXPRS1.         *
****************************************************************
* RECOMMENDATION: Apply the provided PTF.                      *
****************************************************************
When an Enterprise COBOL V5+ program compiled with the DLL     
option is loaded and entered without LE knowing, for example   
with SVC LOAD and BASR, or when the DLL program is used as a   
Content Manager OnDemand user exit
, the program WORKING-STORAGE
may not be initialized properly, resulting in a S0C4 ABEND in   
COBOL runtime module IGZXPRS1.                                       
                           
« Last Edit: July 15, 2019, 11:53:57 AM by Ed_Arnold »
#zOS #ODF

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1147
    • View Profile
High Volume zFS RWSHARE Issue
« Reply #20 on: August 02, 2019, 06:47:34 AM »
CMOD has exposed the following:

OA57775: FILE READ/WRITE FAILURES. OPEN FILE WITH O_APPEND RWSHARE

Opening files with O_APPEND for IO operations can have
unexpected results in an RWSHARE environment sysplex
where concurrent access from multiple systems to the same
file(s) is occurring.

Symptoms vary, depending upon the application but some symptoms
are lseek errors
Ex.
 -EDC5137I Inappropriate I/O control operation
 - Incorrect offsets returned
 - file corruption


This issue was encountered when the CMOD zFS cache was converted to RWSHARE in a very high volume environment.

Ed
#zOS #ODF

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1147
    • View Profile
Re: z/OS V2.3 Release Notes
« Reply #21 on: December 09, 2019, 11:51:46 AM »
If you're migrating from z/OS V2.2 or below, make sure you use the current CBRIBIND member from SYS1.SAMPLIB:

...
//*    $P2=OAMR23M R23 161013 TUCAED: Missing prolog multi reference
//*    $P3=138323  R23 161101 TUCAED: Added CBRIDBSV package and     
//*                                   updated prolog                 
...

Ed
#zOS #ODF

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1147
    • View Profile
Re: z/OS V2.3 Release Notes
« Reply #22 on: April 07, 2020, 10:37:05 AM »
CMOD exposes the following z/OS issue:

Symptom:  long running ARSYSPIN task hangs.

Cause:  Virtual storage shortage

Fix:  OA58421: PRLRMAIN & DAGSH WORK AREA NOT BEING FREED AFTER ABEND IN DADSM PARTIAL RELEASE

Ed
#zOS #ODF

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1147
    • View Profile
Re: z/OS V2.3 Release Notes
« Reply #23 on: July 29, 2020, 07:45:21 AM »
CMOD exposes the following z/OS issue:

Symptom:  long running ARSYSPIN task hangs.

Cause:  Virtual storage shortage

Fix:  OA58421: PRLRMAIN & DAGSH WORK AREA NOT BEING FREED AFTER ABEND IN DADSM PARTIAL RELEASE

Ed

Hit this again --- not so long running but fairly active ARSYSPIN started task took an 878.

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

Ed
« Last Edit: August 24, 2021, 10:46:12 AM by Ed_Arnold »
#zOS #ODF

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1147
    • View Profile
Displaying OAM and OSREQ reason code information
« Reply #24 on: September 14, 2020, 01:53:27 PM »
You can display reason code information for the OAM and OSREQ macros directly from a console or a TSO session, as of APAR OA58344 for V2R3 or later. These commands can also be invoked via JCL to aid in automation of error information capturing in real time.

https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.idao200/displayoaddr.htm

Ed
#zOS #ODF

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1147
    • View Profile
Implementing Multi Factor Authentication?
« Reply #25 on: February 07, 2021, 10:39:50 AM »
There was a problem with mixed case passphrases during MFA Web authentication where MFA incorrectly folded a passphrase to uppercase, and is fixed in MFA 2.0 and MFA 1.3 with PTF UI66464.
#zOS #ODF

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1147
    • View Profile
Re: z/OS V2.3 Release Notes
« Reply #26 on: April 12, 2021, 01:05:58 PM »
CMOD exposes the following JES2 issue:

OA60092: STORAGE ABENDS IN INITIATOR FOR SSI FUNCTIONS

VERIFICATION STEPS:
1) z/OS 2.2 and later, HJE77A0, HJE77B0, HJE77C0
2) Storage abends for jobs in Initiator
#zOS #ODF

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1147
    • View Profile
OAM Problem Surfaced by CMOD
« Reply #27 on: December 20, 2021, 08:51:00 AM »
OA62618: CBR9912I RSN9013 DURING OSMC OR OSREQ RETRIEVE REASON CODE X'80030200'
 
Error description
   The issue may be surfaced in either of the following ways:  1)
   During OSMC processing: CBR9912I groupxx CBRHRDAS A request to
   read Object from collection  collection-name,object object-name
   in groupxx  failed. The return code is 16, and the reason code
   is 9013.  2) Failure from an application to OSREQ RETRIEVE an
   affected object. The OSREQ REASON CODE returned to the
   application is x'80030200'.  This issue occurs for a subset of
   object sizes if BUFFER64 was used on the OSREQ STORE that stored
   the object and the object was stored to the LOB table.
   
   IDENTIFICATION:
   The following SPUFI may be run against each Object Storage Group
   that utilizes LOB tables to identify objects affected by this
   issue:
   
   SELECT 'GROUPxx', ODNAME, ODCLID, ODLOBFL, ODSIZE, LENGTH(OTOBJ)
    AS LENGTH
    FROM hlq.OSM_OBJ_DIR
    LEFT JOIN hlq.OSM_LOB_BASE_TBL
    ON OTNAME = ODNAME
    WHERE LENGTH(OTOBJ) <> ODSIZE;
   
   *where hlq is the DB2 qualifier of the Object Storage Group
   table being investigated
   
   If the ODSIZE is 1 byte greater than the length of OTOBJ and is
   a multiple of (1048568 x n) +1, then the object is affected by
   this issue.
   
   ADDITIONAL SYMPTOMS:
   CBR9912I OSREQ ODSIZE

Contact OAM support for details and fix.
#zOS #ODF