CBR0014I   Invalid option "option" specified with keyword {MSG= | OTIS= | UPD= | MOS= | LOB= | QB= | DP=}, for the OAM entry in IEFSSNXX parmlib member. Default option for the keyword is assumed.

Explanation

One of the keyword options specified on the OAM entry in the IEFSSNXX member of PARMLIB, was specified incorrectly.
  • For keyword MSG=: An invalid option, option was specified following the MSG= keyword. Following the keyword must be one of the following options:
    Option
    Meaning
    EM
    OAM messages may consist of mixed case English characters.
    EU
    OAM messages will conform to the minimum character set consisting of upper case English letters, digits, special characters and blank.
  • For keyword OTIS=: An invalid option, or no option was specified following the OTIS= keyword. Following the keyword must be one of the following options:
    Option
    Meaning
    Y
    OTIS address space will not start until JES has started.
    N
    OTIS address space will not wait for JES prior to starting.
  • For keyword UPD=: An invalid option, or no option was specified following the UPD= keyword. Following the keyword must be one of the following options:
    Option
    Meaning
    Y
    OAM/OSREQ will update Pending Action Date (ODPENDDT) and Last Reference Date (ODLREFDT) on all OSREQ retrieves.
    N
    OAM/OSREQ will NOT update Pending Action Date (ODPENDDT) and Last Reference Date (ODLREFDT) on any OSREQ retrieves.
  • For keyword MOS=: An invalid option, or no option was specified following the MOS= keyword. Following the keyword must be a number between 50 and 2000 which specifies OAM’s maximum object size in megabytes. The maximum object size is checked when objects are initially stored through the OSREQ programming interface. The maximum object size default is 50MB.
  • For keyword LOB=: An invalid option, or no option was specified following the LOB= keyword. Following the keyword must be one of the following options:
    Option
    Meaning
    A
    All object storage groups are LOB enabled, so all large objects stored in DB2® are stored into LOB storage structures.
    P
    Some, but not all object storage groups are LOB enabled. Large objects stored in DB2 for LOB enabled object storage groups are stored into LOB storage structures, and large objects stored in DB2 for object storage groups that are not LOB enabled are stored into 32K tables.
    N
    No object storage groups are LOB enabled, so all large objects stored in DB2 are stored into 32K tables. This is the default value.
  • For keyword QB=: An invalid option, or no option was specified following the QB= keyword. Following the keyword must be one of the following options:
    Option
    Meaning
    Y
    An OSREQ QUERY will result in a call into the OAM address space for each backup copy. The OSREQ QUERY will return a complete backup retrieval order key for each backup copy. If a backup copy does not exist, then the OAM address space will not be called and the backup retrieval order key will contain binary zeros. This is the default.
    N
    An OSREQ QUERY will not result in a call into the OAM address space for each backup copy. The backup retrieval order key will contain binary zeros for each backup copy regardless if the backup copy exists or not.
  • For keyword DP=: An invalid option, or no option was specified following the DP= keyword. Following the keyword must be one of the following options:
    Option
    Meaning
    A
    Deletion-protection is enabled for all object storage groups regardless of the OAM Deletion-Protection value specified in the SMS storage group construct for a given object storage group. Any attempts to OSREQ DELETE an object before its expiration date is failed regardless of what object storage group the object resides in.
    P
    Deletion-protection is partially enabled. Specifically, DP=P indicates that deletion-protection is enabled at the object storage group level through the OAM Deletion-Protection value specified in the SMS storage group construct for a given object storage group.
    • Any attempts to OSREQ DELETE an object before its expiration date is failed if that object resides in an object storage group that has OAM Deletion-Protection enabled.
    • The expiration date of an object is not a factor when an OSREQ DELETE request is processed if that object resides in an object storage group that has OAM Deletion-Protection disabled.
      Note: A retention-protected object cannot be deleted before its expiration date even if deletion-protection is disabled. Retention-protection takes precedence over deletion-protection.
    N
    Deletion-protection is enabled for no object storage groups regardless of the OAM Deletion-Protection value specified in the SMS storage group construct for a given object storage group. The expiration date of an object is not a factor when an OSREQ DELETE request is processed. DP=N is the default.
    Note: A retention-protected object cannot be deleted before its expiration date even if deletion-protection is disabled. Retention-protection takes precedence over deletion-protection

System action

OAM subsystem initialization continues. The default option for the invalid keyword is assumed.

Operator response

Notify the system programmer.

System programmer response

Specify a valid option for the invalid keyword on the OAM entry in the IEFSSNxx member of PARMLIB. At the next IPL of the MVS™ operating system the change will become effective.

Source

Object Access Method (OAM)

Routing Code

2

Descriptor Code

4

Parent topic: CBR messages