BBPARM member AAOTSP00 parameters

ACTION=[DEFAULT | CANCEL | WTOR | NOHOLD | HOLD]

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

Possible values and their definitions are as follows:

• DEFAULT: allows the installation’s default action to occur

• CANCEL: cancels the job

• WTOR: issues a WTOR to the operator

  If the site does not have a defined default action, this action is the default.

• NOHOLD: enables the job to wait without holding resources

• HOLD: enables the job to wait while holding resources

FREE=[DEALLOC | deallocation procedure name]

For use with MVS SP4.x only.

enables you to specify the one- to eight-character name of a deallocation procedure that starts after TapeSHARE issues the VARY OFFLINE command to GIVE a device to another image

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

NOGIVE=device address

Default value is none.

list of device addresses (or a range of addresses) that should not be GIVEN to other partners within the TapeSHARE <Times9>plex when they request devices to TAKE (in other words, a list of device addresses that are dedicated to this image)

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

NOGIVE=0123
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.

NOGIVE=0123
NOTAKE=0123

If the device addresses 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.

NOTAKE=device address

Default value is none.

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.

NOGIVE=0123
NOGIVE=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-NOTAKE device and it will be excluded completely from TapeSHARE control.

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.

PARTNER=subsystem name

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

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.)

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.

SYSA is a partner to this image.

SYSC is a partner to this image and the device whose address is 0123 cannot be given to partner SYSC.

SYSB is a partner to this image and the devices whose addresses fall between 0120 and 0127 cannot be given to partner SYSB.

PREF=[YES |NO | FORCE]

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 is in place, the input-only device is not given to SYSA and an Allocation Failure Event occurs.

PREFDEV=device address

specifies a tape device address (or a range of tape device addresses) followed by either an I (for input-only) or O for (output-only) that are identified to TapeSHARE on this image that are allocated to perform input-only or output-only functions

Default value is none.

This parameter should 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 output-only.

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

PREFDEV=01A0-01A3,I
PREFDEV=0130,O
PREFDEV=0150-015F,O

RETRYCNT=(0 |2 through 10)

number of times TapeSHARE 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 3 retries is specified. TapeSHARE attempts three more times to satisfy this request for devices.

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

Possible values are 0 - 10.

RETRYINT=(0 |30 through 300)

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

For example, suppose

• RETRYCNT= parameter is set to 3 retries

• RETRYINT= parameter is set to 45 seconds

If 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.

Possible values are 0 - 300.

TIMEOUT=(0 | 120 through 999)

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.

Possible values are 0 - 999.

TRACE=[YES | NO]

writes diagnostic information to BBITST DD statement

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).