Information

This site will undergo a brief period of maintenance on Friday, 18 December at 12:30 AM Central/12:00 PM IST. During a 30 minute window, site availability may be intermittent.

Information
Newer version of documentation BMC provides a newer version of the documentation for this version of the product. As a result, BMC no longer accepts comments in this space.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see bao8301.

Customizing TapeSHARE


Use the TapeSHARE Parameters panel to see and modify parameters for the TapeSHARE application and control how TapeSHARE automates the sharing of tape devices among your z/OS images.

The following figure shows an example of this panel.

BMC Software --------------- TapeSHARE Parameters --------------  BMC AMI OpsA
COMMAND ===>                                                 TGT  --- BBSYSA
                                                             DATE --- YY/MM/DD
                                                             TIME --- 16:27:51
                  Member     Current
PARTNER    ===>                      * LIST * (Enter ? for a partner list)
TIMEOUT    ===>      120         120          Subsystem response timeout value
RETRYCNT   ===>        2           2          Times to retry a take request
RETRYINT   ===>       30          30          Interval between take retries
ACTION     ===>  DEFAULT     DEFAULT          Allocation failure action
NOGIVE     ===>                               (Enter ? for a device list)
NOTAKE     ===>                               (Enter ? for a device list)
PREF       ===>  NO          NO               Enable / Force preferencing
PREFDEV    ===>                               (Enter ? for a device list)
FREE       ===>  DEALLOC     DEALLOC          Deallocation procedure name
TRACE      ===>  NO          NO               Start / Stop TapeSHARE tracing
Press END to save changes, CANCEL to cancel changes

This panel provides two columns of data:

  • On the left, the value of the parameters in the AAOTSPxx member for the target BBI-SS PAS
    You can enter your modifications on this side of the panel.
  • On the right, the value of the parameters that are currently in effect for the target BBI-SS PAS; these values cannot be edited

The first time you bring up this panel, the display-only fields match the input fields and default values are shown in both columns.

A description of the fields on this panel follows. 

Field name

Description

PARTNER

Specifies a BBI-SS PAS name (that can be associated with either one or a range of tape devices) that is a TapeSHARE PLEX partners

You also can include with the BBI-SS PAS name, the device address (or a range of device addresses) that TapeSHARE cannot GIVE to the named partner. See examples below.

Information
Example
PARTNER=SYSA

In this example, SYSA is a partner to this image.

Information
Example
PARTNER=SYSC,0123

In this example, SYSC is a partner to this image and the device whose address is 0123 cannot be GIVEN to partner SYSC.

Information
Example
PARTNER=SYSB,0120-0127

In this example, SYSB is a partner to this image and the devices whose addresses fall between 0120 and 0127 cannot be GIVEN to partner SYSB.

If no values are associated with this parameter, TapeSHARE assumes that any BBI node defined in BBINOD00 member is a partner within a TapeSHARE PLEX.

TIMEOUT

Specifies the amount of time (in seconds) to wait for the partners to respond to a request for devices

When this time is reached and a successful GIVE has not been completed, an Allocation Failed Event occurs unless you have specified a number of retries on the RETRYCNT parameter. See below.

Information
Example
TIMEOUT=20

Valid values are 0 - 999 seconds and 120 seconds is the default.

RETRYCNT

Specifies the number of times thatTapeSHARE attempts to satisfy a request for devices after an initial attempt has failed

For example, suppose this system’s request for devices is not satisfied and three retries are specified. TapeSHARE attempts three more times to satisfy this request for devices.

Information
Example
RETRYCNT=3

This parameter is used in conjunction with the RETRYINT parameter that specifies how long TapeSHARE waits between retry attempts.

Valid values are 0-10 retries and 2 is the default.

RETRYINT

Specifies the number of seconds that TapeSHARE waits for devices between attempts after an initial attempt has failed

For example, suppose

  • the RETRYCNT= parameter is set to 3 retries
  • the RETRYINT= parameter is set to 45 seconds
  • this system’s request for devices is not satisfied

TapeSHARE waits 45 seconds after the initial attempt fails and retries to satisfy the request (retry attempt 1). If this attempt fails, TapeSHARE waits another 45 seconds and retries (attempt 2). If this attempt also fails, TapeSHARE waits another 45 seconds and retries (attempt 3).

Should all three attempts fail, an Allocation Failed Event occurs and the specified action is taken.

Information
Example
RETRYCNT=3

Valid values are 0 - 300 seconds and 30 is the default.

ACTION

Specifies the action that TapeSHARE should take when an Allocation Failed Event occurs because a successful GIVE cannot be performed

Possible values and their definitions are as follows:

  • DEFAULT: specifies that the installation’s default action is to occur
  • WTOR: issues a WTOR to the operator (the default for the ACTION parameter)
  • CANCEL: cancels the job
  • NOHOLD: specifies that the job waits without holding resources
  • HOLD: specifies that the job waits while holding resources
Information
Example
ACTION=WTOR

NOGIVE

Specifies a list of device addresses (or a range of addresses) that should not be GIVEN to other request devices to TAKE

Warning

Note

This action does not prevent you from manually GIVING a NOGIVE device.

If a device address is not associated with this parameter, TapeSHARE assumes that no devices are dedicated to this image.

Information
Example
NOGIVE=0123

or

NOGIVE=0120-012F

You also can use this parameter in conjunction with the NOTAKE parameter. By specifying a device address on both these parameters, the device will be a NOGIVE-NOTAKE device and it will be excluded completely from TapeSHARE control.

Information
Example
NOGIVE=0123
NOTAKE=0123

If the device address 0123 is specified on both the NOGIVE and NOTAKE parameters, the 0123 is completely excluded from TapeSHARE control. TapeSHARE does not attempt to GIVE or TAKE this device.

The default value is none.

NOTAKE

Specifies a list of device addresses (or a range of addresses) that this image should not TAKE when a request for resources is made

TapeSHARE on this image will not accept (TAKE) the devices specified. If a value is not associated with this parameter, TapeSHARE assumes that it can accept any tape devices when a request for resources is made.

Information
Example
NOTAKE=0123

or

NOTAKE=0120-012F

You also can use this parameter in conjunction with the NOGIVE parameter. By specifying a device address on both these parameters, the device will be a NOGIVE-NOTAKEdevice and it will be excluded completely from TapeSHARE control.

Information
Example
NOGIVE=0123
NOTAKE=0123

If the device address 0123 is specified on both the NOGIVE and NOTAKE parameters, the 0123 device is completely excluded from TapeSHARE control. TapeSHARE does not attempt to GIVE or TAKE this device.

The default value is none.

PREF

Specifies whether Preferencing is activated

If activated, TapeSHARE uses the devices identified on the PREFDEV parameter for only the operation (input or output) identified for that device.

This parameter must be used in conjunction with the PREFDEV parameter.

Specifying YES turns on Preferencing in Guideline mode. For example, in Guideline mode, if SYSA needs an output-only device but only input-only devices are available, the input-only device is GIVEN to SYSA.

Specifying FORCE turns on Preferencing in Force mode. If Force mode were in place, the input-only device would not be GIVEN to SYSA and an Allocation Failure Event would occur.

Information
Example
PREF=YES

or

PREF=NO

or

PREF=FORCE

PREFDEV

Specifies a tape device address (or a range of tape device addresses) followed by either an I for input-only or an O for output-only; see examples

This parameter must be used in conjunction with the PREF parameter.

With the PREF activated, when a device is needed for an output-only operation, TapeSHARE attempts to choose from those devices identified by this parameter as output-only.

If a value is not associated with this parameter, TapeSHARE will not invoke device preferencing.

Information
Example
PREFDEV=01A0-01A3,I

or

PREFDEV=0130,O

or

PREFDEV=0150-015F,O

Default value is none.

FREE

Specifies a 1- to 8-character deallocation procedure which starts after TapeSHARE issues the VARY OFFLINE command to GIVE a device to another image

Scheduling this procedure triggers deallocation processing in the system GIVING the device and places the device in an OFFLINE state.

The default deallocation name is DEALLOC.

TRACE

Specifies that diagnostic information be written to the BBITST DD statement

Information
Example
TRACE=NO

If YES is specified, the BBITST DD statement must appear in the BBI-SS PAS startup JCL for information to be written to it (see BBSAMP member SSJCL).

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI Ops Automation 8.3