TapeSHARE parameters in AAOTSPxx
BBPARM members AAOTSPxx contain the parameters that you can modify to customize the way that the MainView AutoOPERATOR TapeSHARE component automates the sharing of tape devices among your z/OS images.
Remember, the MainView AutoOPERATOR TapeSHARE component is designed to perform tape sharing automation without you needing to customize any of these parameters. For more information about TapeSHARE and how these parameters affect TapeSHARE, refer to the MainView AutoOPERATOR Options User Guide.
To modify an AAOTSPxx member, type S in the Cmd field of the Dynamic Parameter Manager panel.
The following figure shows an example of the panel.
Dynamic Parameter Manager panel
COMMAND ===> TGT ===> BBSYSA
Primary command: Add Date --- YY/MM/DD
Time --- 11:41:36
LC CMDS --- (S)elect, (B)rowse w/o Symbolic Substitution
(A)ctivate, B(r)owse w/ Symbolic Substitution
Cmd Member Lib VV.MM Created Changed Size ID
________
_ AAOALS00 1 01.11 YY/MM/DD YY/MM/DD 20:12 4 JDB1
_ AAOALS01 1 00.01 YY/MM/DD YY/MM/DD 13:30 3 JDB1
_ AAOARP01 1 00.01 YY/MM/DD YY/MM/DD 13:30 3 JDB1
_ AAOEXP00 1 02.26 YY/MM/DD YY/MM/DD 20:12 27 JDB1
_ AAOPRM00 1 02.26 YY/MM/DD YY/MM/DD 20:12 27 JDB1
S AAOTSP00 1 02.01 YY/MM/DD YY/MM/DD 20:12 12 JDB1
**************************** END OF MEMBERS ******************************
Use this panel to see a list of all the AAOALSxx, AAOARPxx, AAOEXPxx, AAOPRMxx, and AAOTSPxx members in BBPARM.
From this panel, you can
- use the line commands; refer to Line commands for the Dynamic Parameter Manager panel for more information
use the primary command ADD to add a new members
To add a new member or members, type the following command on the COMMAND line, wherexx is a new suffix for a new member:
ADD AAOTSP xx
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. In this example, SYSA is a partner to this image. In this example, SYSC is a partner to this image and the device whose address is 0123 cannot be GIVEN to partner SYSC. 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. 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. 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
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. 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:
|
NOGIVE | specifies a list of device addresses (or a range of addresses) that should not be GIVEN to other request devices to TAKE If a device address is not associated with this parameter, TapeSHARE assumes that no devices are dedicated to this image. 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. 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. 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. 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. |
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. Default value is none. |
FREE | For use with MVS SP4.x only 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 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). |