Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

ATTACH-DEVICE

&pagelevel(3)&pagelevel

Attach hardware units

Component:

BS2000

Functional area:

Device management

Domain:

DEVICE

Privileges:

OPERATING

Routing code:

G

Function

This command enables the operator to make available one or more hardware units, i.e. to allow the operating system to use these units for I/O operations. The hardware units are attached via SVP.

Effect of the ATTACH-DEVICE command

  1. If the specified hardware units were in the “detached explicitly” state, they are placed in the “attached” state and can be used again.

  2. If the specified hardware units were in the “detached implicitly” state, an ATTACH is rejected. The “detached explicitly” state, if applicable, is canceled.

  3. If the outward connections associated with the unit were in the “removed implicitly” state, they are placed in the “included” state. The connections can be used again.

  4. All outward hardware units in the “detached implicitly” state which have at least one connection to the relevant unit in the “included” state are placed in the “attached” state. These units can be used again.

  5. If there are hardware attach actions (SVP actions) for the units to be attached, these actions are initiated. The hardware units addressed explicitly in the command are not placed in the “attached” state unless the hardware reactions resulting from SVP processing receive a positive acknowledgment, otherwise ATTACH is rejected.

  6. In the case of disks and tape devices for which it is possible to set up path groups, such path groups are set up for all the available paths.

  7. When a PAV (Parallel Access Volumes device is attached (see the “Introductory Guide to Systems Support” [14])), the following applies:

    In the case of a base device, the associated alias devices are searched for and implicitly attached. Alias devices can only be explicitly attached using the ATTACH-DEVICE command when the associated base device is already attached.

  8. If a FastDPAV basis device is attached, the associated FastDPAV alias devices are not attached implicitly (FastDPAV see the manual “Introduction to System Administration” [14]). The FastDPAV alias devices have to be explicitly ENABLED for input/output.

  9. For a FastDPAV alias device in the state DISABLED, the ENABLED state is set by means of the ATTACH-DEVICE command:

    • In native operating mode

    • In VM2000 operating mode, if the implicit device assignment to VM is permitted (ASSIGN-BY-GUEST=*YES) or the alias device is explicitly assigned to VM

Format

ATTACH-DEVICE                                                                                                                                          

UNIT = *CPU(...) / *EXTRA-CPU(...) / *CHANNEL(...) / *CONTROLLER(...) /




*CHANNEL-RANGE(...) / *DEVICE-RANGE(...) / *PUBSET-DEVICES(...) /




list-poss(255): <alphanum-name 2..2> / <x-text 4..4>


*CPU(...)



|

CPU-IDENTIFIER = list-poss(16): <x-text 2..2>


*EXTRA-CPU(...)



|

CPU-IDENTIFIER = *ALL / *ANY / <x-text 2..2>


*CHANNEL(...)



|

CHANNEL-PATH-ID = list-poss(16): <x-text 2..2>



|

,SCOPE = *OWN-SYSTEM-ONLY / *VM2000-GLOBAL


*CONTROLLER(...)



|

CONTROLLER-UNIT = list-poss(16): <alphanum-name 2..2> / <x-text 4..4>



|

,SCOPE = *OWN-SYSTEM-ONLY / *VM2000-GLOBAL


*CHANNEL-RANGE(...)



|

FROM = <x-text 2..2>



|

,TO = <x-text 2..2>



|

,SCOPE = *OWN-SYSTEM-ONLY / *VM2000-GLOBAL


*DEVICE-RANGE(...)



|

FROM = <alphanum-name 2..2> / <x-text 4..4>



|

,TO = <alphanum-name 2..2> / <x-text 4..4>


*PUBSET-DEVICES(...)



|

PUBSET = list-poss(255): <cat-id 1..4> / *BY-PUBRES-DEVICE(...)



|


*BY-PUBRES-DEVICE(...)



|



|

UNIT = list-poss(255): <alphanum-name 2..2> / <x-text 4..4>

Operands

UNIT =
Specifies the hardware units to be attached to the system.

UNIT = *CPU(...)
Specifies the CPU to be attached.

CPU-IDENTIFIER = list-poss(16): <x-text 2..2>
Specifies the CPU identifier.

UNIT = *EXTRA-CPU(...)
Specifies the extra CPU that is to be attached.

CPU-IDENTIFIER = *ALL / *ANY / <x-text 2..2>
Specifies the identifier of the extra CPU. *ANY attaches one available extra CPU. *ALL attaches all available extra CPUs.

UNIT = *CHANNEL(...)
Specifies the channel to be attached.

CHANNEL-PATH-ID = list-poss(16): <x-text 2..2>
Specifies the channel path ID of the channel. In the case of channels, the device name (MN) is the same as the channel path ID in hexadecimal representation.

SCOPE = 
Specifies how the command is to be executed in VM2000 operating mode.

SCOPE = *OWN-SYSTEM-ONLY
The command is only executed in the local system.

SCOPE = *VM2000-GLOBAL
If entered in the Monitor System (SU /390), the command is executed in all guest systems. If entered in  another guest system or in the Monitor System (SU x86), the command is rejected with the message NKR0178.

UNIT = *CONTROLLER(...)
Specifies the controller to be attached.

CONTROLLER-UNIT = list-poss(16): <alphanum-name 2..2> / <x-text 4..4>
Specifies the mnemonic device code (MN) of the controller to be attached.

SCOPE = 
Specifies how the command is to be executed in VM2000 operating mode.

SCOPE = *OWN-SYSTEM-ONLY
The command is only executed in the local system.

SCOPE = *VM2000-GLOBAL
If entered on the Monitor System (SU /390 ), the command is executed on all guest systems. If entered at another guest system or at the Monitor System (SU x86), the command is rejected with the message NKR0178.

UNIT = *CHANNEL-RANGE(...)
Specifies a set of channels to be attached.

FROM = <x-text 2..2>
Specifies the channel path ID of the first channel in the set of channels to be attached.

In the case of channels, the device name (MN) is the same as the channel path ID in hexadecimal representation.

TO = <x-text 2..2>
Specifies the channel path ID of the last channel in the set of channels to be attached. The following rules apply: chn 1 -id < chn 2 -id, and chn 2 -id - chn 1 -id < 64, i.e. a maximum of 64 channels can be attached at a time.

SCOPE =
Specifies how the command is to be executed in VM2000 operating mode.

SCOPE = *OWN-SYSTEM-ONLY
The command is only executed in the local system.

SCOPE = *VM2000-GLOBAL
If entered in the Monitor System (SU /390 ), the command is executed in all guest systems. If entered in another guest system or in the Monitor System (SU x86), the command is rejected with the message NKR0178.

UNIT = *DEVICE-RANGE(...)
Defines the maximum of 256 devices, that can be attached. The mnemonic codes defined do not have to be contiguous. If no device is generated for one of the codes, processing continues with the next device code.

FROM = <alphanum-name 2..2> / <x-text 4..4> 
Defines the mnemonic device code (MN) of the first device in the set of devices to be attached.

TO = <alphanum-name 2..2> / <x-text 4..4> 
Defines the mnemonic device code (MN) of the last device in the set of devices to be attached.

UNIT = *PUBSET-DEVICES(...)
Specifies that a pubset’s disks are to be attached. Since the mnemonic device names (MNs) of the associated disks are administered in the SVL of the system disk, the latter must have been entered into the MRSCAT. The entry is made whenever the pubset is imported or exported and in the case of modifications to the composition of the pubset (see MODIFY-PUBSET-PROCESSING). Alternatively, you can enter the system disk manually with the ADD-MASTER-CATALOG-ENTRY and MODIFY-MASTER-CATALOG-ENTRY commands. 

In all cases, as many disks as possible are attached. If pubset disks are mirrored then the following should be noted:

  • If mirroring is performed with DRV, both disks are always attached.

  • In the case of mirroring in external disk storage systems (see the “SHC-OSD” User Guide [37]) only the standard disks are attached (source or normal unit). If the mirror disks are to be attached then the mirror disk (target or additional mirror unit) of the system disk (pubres) must be specified in the PUBSET operand.

PUBSET = list-poss(255): <cat-id 1..4> / *BY-PUBRES-DEVICE(...) 
Identifies the pubset whose disks are to be attached. The pubset can be specified via its catalog ID or the device code of its system disk.

PUBSET = <cat-id 1..4>
Specifies the pubset’s catalog ID. There must be a corresponding entry in the MRS catalog. If there is no entry then the disks can only be attached by specifying the system disk (see PUBSET=*BY-PUBRES-DEVICE).

PUBSET = *BY-PUBRES-DEVICE(...)
Specifies the pubset’s system disk (pubres).

UNIT = list-poss(255): <alphanum-name 2..2> / <x-text 4..4>
Mnemonic device code (MN) of the pubres.

UNIT = list-poss(255): <alphanum-name 2..2> / <x-text 4..4>
Specifies the mnemonic device code (MN) if a device is to be attached.

Return codes

(SC2)

SC1

Maincode

Meaning


0

CMD0001

No error

1

64

ETMRK..

Command execution faulty

2

64

ETMRK..

Command partially processed without error

4

64

NKR0...

Hardware unit was already attached

12

64

NKR0...

Internal check negative

16

64

NKR0...

Caller error

20

64

NKR0...

Software error

If there is an error in command termination, the maincode contains the message code of the message output during command processing. The command return codes with the ETMRK.. maincodes occur only if the hardware unit to be reconfigured is a CPU.

Examples

  1. Attach the channels with the channel path IDs 10 through 1F

    /ATTACH UNIT=*CHANNEL-RANGE(FROM=10,TO=1F) or
    /ATT *CH-R(10,1F)

  2. Attach devices D1, D2 and C1
    /ATTACH-DEVICE UNIT=(C1,D1,D2) or
    /ATT (C1,D1,D2)

  3. Attach CPU 1

    /ATTACH-DEVICE UNIT=*CPU(CPU-IDENTIFIER=01) or
    /ATT *CPU(01)

  4. Attaching the pubset’s disks with the catalog ID 2OSG

    /ATTACH-DEVICE UNIT=*PUBSET-DEVICES(PUBSET=2OSG) or
    /ATT *PUB-DEV(2OSG)

Powered by Atlassian Confluence and Scroll Viewport.