z/OS DFSMSrmm Managing and Using Removable Media
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


ADDOWNER: Adding owner information

z/OS DFSMSrmm Managing and Using Removable Media
SC23-6873-00

Purpose

Before you begin: To use the RMM ADDOWNER subcommand, you need CONTROL access to the STGADMIN.EDG.MASTER resource profile.

Use the ADDOWNER subcommand to define an owner to DFSMSrmm. An owner can be an individual or a group defined by a RACF® group name, or any other value you choose.

DFSMSrmm automatically creates an owner record if a user who is not defined to DFSMSrmm requests a job that writes to a volume managed by DFSMSrmm. DFSMSrmm uses the user ID that requested the job as a DFSMSrmm owner ID. To use DFSMSrmm automatic owner notification, you must manually add the user ID and node to be used as an electronic address.

You must supply an owner ID and a department name. The owner ID can be the owner's RACF user ID or any name you select to identify a single owner or owner group to DFSMSrmm. We suggest that you use a RACF user ID or RACF group name.

To use DFSMSrmm automatic owner notification, define an owner's electronic address by supplying the USER operand and the NODE operand, or a valid e-mail address. DFSMSrmm uses this address to notify the owner when the owner's volumes are eligible for release. Notification used as one of the actions to be performed upon the volume's release, and the parmlib option, OPTION NOTIFY, set to Y. Use the ADDVOLUME or CHANGEVOLUME subcommands to set release actions for a volume. See ADDVOLUME: Adding volume information or CHANGEVOLUME: Changing volume information for more information. See z/OS DFSMSrmm Implementation and Customization Guide for more information on setting parmlib options.

Format

Read syntax diagramSkip visual syntax diagram
                                                    (1)     
>>-+-ADDOWNER-+--owner_ID--+-DEPARTMENT(department)-----+------->
   '-AO-------'            |                  (1)       |   
                           '-DEPT(department)-----------'   

>--+-----------------------+--+-----------------------+--------->
   '-ADDR1(address_line_1)-'  '-ADDR2(address_line_2)-'   

>--+-----------------------+--+-----------------------+--------->
   '-ADDR3(address_line_3)-'  '-EMAIL(id@domain_name)-'   

>--+----------------------------------+--+-----------------+---->
   '-EXTEL(external_telephone_number)-'  '-FNAME(forename)-'   

>--+----------------------------------+--+----------------+----->
   '-INTEL(internal_telephone_number)-'  '-SNAME(surname)-'   

>--+-----------------------+--+---------------------------+----><
   '-TZ({+|-}HH[:MM[:SS]])-'  '-USER(user_ID)--NODE(node)-'   

Notes:
  1. The DEPARTMENT operand must contain at least one non-blank character.

Parameters

ADDR1(address_line_1)
Specifies the first address line. An address line is one to forty characters enclosed in single quotation marks if it contains any special characters or blanks.

The default is blanks.

ADDR2(address_line_2)
Specifies the second address line. An address line is one to forty characters enclosed in single quotation marks if it contains any special characters or blanks.

The default is blanks.

ADDR3(address_line_3)
Specifies the third address line. An address line is one to forty characters enclosed in single quotation marks if it contains any special characters or blanks.

The default is blanks.

DEPARTMENT/DEPT(department)
Specifies the owner's department name. A department name is one to forty characters and must not be all blanks. Enclose the department name in single quotation marks if it contains any special characters or blanks. A department name is required.
EMAIL(id@domain_name)
Specifies an Internet identifier for the user represented by this owner record. An Internet identifier specifies the path address of the mail recipient. The format of recipient is equivalent to the path syntax, as described in RFC 821, without the (<) and (>) delimiters. The Internet Protocol suite is still evolving through requests for comments (RFC). New protocols are being designed and implemented by researchers and are brought to the attention of the Internet community in the form of RFCs. See z/OS Communications Server: IP User's Guide and Commands for details.
This EMAIL operand has one of these formats:
  • user_id@host_name.domain - User on a host in a specified domain.
  • user_id%nje_host_name@ gateway_name.domain - User on an NJE or RSCS node connected to a TCP network at gateway_name.

There is no default value. When you specify EMAIL, the USER and NODE values are ignored by NOTIFY processing, and any notify messages are sent using your system's SMTP server.

The maximum length of the value supported by DFSMSrmm is 63 characters.

EXTEL(external_telephone_number)
Specifies the owner's external telephone number. An external telephone number is one to twenty characters enclosed in single quotation marks if it contains any special characters or blanks.

The default is blanks.

FNAME(forename)
Specifies the owner's forename, or first name, initials, or title. A forename is one to twenty characters enclosed in single quotation marks if it contains any special characters or blanks.

The default is blanks.

INTEL(internal_telephone_number)
Specifies the owner's internal telephone number. An internal telephone number is one to eight characters enclosed in single quotation marks if it contains any special characters or blanks.

The default is blanks.

NODE(node)
Specifies the node name for electronic communication to the owner. A node ID is one-to-eight alphanumeric characters, $, #, or @. If you use NODE, you must also use USER.

The default is no electronic mail address.

owner_ID
Specifies an owner ID. An owner ID consists of one-to-eight alphanumeric characters, $, #, or @. The first character cannot be a number. We suggest that you use a RACF user ID or RACF group name. This operand is required and must immediately follow the ADDOWNER subcommand.

The Owner 'SMTP' is now a reserved owner name value that you can use to configure the Node name and SMTP server address space or machine name. You use the NODE operand to identify the node that runs the SMTP server, and the USER operand to identify the SMTP server. Note: You must specify both values. When you do not have the Owner SMTP defined, DFSMSrmm uses the JES node name of the running system and SMTP as the SMTP server address space name.

SNAME(surname)
Specifies the owner's surname, or last name. A surname is one to twenty characters enclosed in single quotation marks if it contains any special characters or blanks.

The default is blanks.

TZ({+|-}HH[:MM[:SS]])
Specifies the time zone offset when date and time values are specified. The format is{+|-}HH[:MM[:SS]] where:
  • +|- is the offset direction. Specify + to indicate that the offset is East of the zero median (UT). Specify - to indicate that the offset is West of the zero median (UT). The offset direction is required.
  • HH is hours
  • MM is minutes
  • SS is seconds

An optional colon (:) separates hours from optional minutes and optional seconds.

You can specify a time in the range between 00:00:00 to 15:00:00 for HH:MM:SS. MM and SS value range is 00 to 59.

USER(user_ID)
Specifies the owner's user ID to be used for electronic communication. A user ID is one-to-eight alphanumeric characters. If you specify USER, you must also use NODE.

The default is no electronic mail address.

Examples

Task: Add details for the new owner information shown in Table 1.
Table 1. New owner information
Field name Sample value
Owner's user ID OWNERAS
Owner's department Personnel
First line of owner's address XYZ Company (UK)
Second line of owner's address London
Owner's surname Smith
Owner's initials A B
Owner's internal telephone number 321 1234
Owner's electronic user ID RANDSTER
Owner's electronic node ID BUBVM30
Command:
  RMM ADDOWNER OWNERAS DEPT('Personnel') ADDR1('XYZ Company (UK)') -
       ADDR2('London') SNAME('Smith') FNAME('A B') INTEL('321 1234') -
       USER(RANDSTER) NODE(BUBVM30)

Return codes

See DFSMSrmm return codes and reason codes for DFSMSrmm reason codes.

0
Subcommand completed normally.
4
Warning. Subcommand completed but some operands could have been ignored or modified. DFSMSrmm sets a reason code.
8
User not authorized.
12
Subcommand ended with an error. DFSMSrmm sets a reason code.
16
Error. The DFSMSrmm subsystem is not active.
20
Error. The data is incomplete or incorrect and the TSO user has set NOPROMPT.
24
The TSO subcommand is not APF authorized.
28
The user pressed the attention key.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014