Author Topic: z/OS 2.3 - OAM Line Item of Interest for CMOD  (Read 2356 times)

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1199
    • View Profile
z/OS 2.3 - OAM Line Item of Interest for CMOD
« on: July 20, 2017, 07:43:02 AM »
IBM z/OS Version 2.3 Announcement Letter:

https://www.ibm.com/common/ssi/rep_ca/9/872/ENUSAP17-0239/ENUSAP17-0239.PDF

Quote
In z/OS V2.3, an optional multiple OAM configuration enables a separate OAM tape library address space and up to two OAM object support address spaces...

What this means is that one could have TEST and PROD CMOD instances using separate TEST and PROD OAMs on the same LPAR or two independent CMODs and OAMs on the same LPAR.

Ed
#zOS #ODF

Greg Ira

  • Full Member
  • ***
  • Posts: 240
    • View Profile
Re: z/OS 2.3 - OAM Line Item of Interest for CMOD
« Reply #1 on: July 20, 2017, 08:04:37 AM »
Well this one makes me happy.   Good news.

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1199
    • View Profile
One Hand Giveth, The Other Taketh Away
« Reply #2 on: November 14, 2017, 10:24:29 AM »
TL;DR - no support for optical in multi-OAM LPAR

I was talking to one of my counterparts in OAM and learned the following:

If accounts want to use the new multi-address space function OAM available with z/OS V2.3, then optical libraries/drives/media are NOT supported.

When an OAM address space is started in this environment, it will bypass any optical related definitions that it finds in the CBROAMxx parmlib member and users would be unable to retrieve objects from optical in this environment.

If users still need access to their optical environments in 2.3, they have to start OAM in Classic mode.

Per the OAM Object PISA:

Quote
In a multiple OAM configuration, the optical level of the OAM storage hierarchy is
not supported within an object address space. Therefore, customers who want to
implement a multiple OAM configuration must first take the following actions
before attempting to implement a multiple OAM configuration:

-  Transition any existing objects from the optical level of the OAM storage
hierarchy to another level of the OAM storage hierarchy (required)

-  Remove all optical related definitions for libraries and drives (recommended;
warning messages are issued if this is not done)

- Update definitions in the CBROAMxx  member of PARMLIB to remove any
optical related keywords (recommended; if specified, optical related keywords
are ignored).

Ed
#zOS #ODF