27.12.2012 Views

z/VM: CP Commands and Utilities Reference - z/VM - IBM

z/VM: CP Commands and Utilities Reference - z/VM - IBM

z/VM: CP Commands and Utilities Reference - z/VM - IBM

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

SALIPL<br />

ORIGIN<br />

specifies the address at which SAPL should load the module.<br />

This option is ignored by SAPL if the module that is being loaded has not been<br />

generated with the RLDSAVE option. In this case, the module is loaded into<br />

storage at the location at which the module was generated.<br />

The entire module, including its required <strong>CP</strong> data structures, must fit below the<br />

2G line.<br />

When loading <strong>CP</strong> for z/<strong>VM</strong> V5R1 or later, the ORIGIN option is accepted, but<br />

<strong>CP</strong> will relocate itself to location X'2000'.<br />

X'1000'<br />

is the default address.<br />

1868 z/<strong>VM</strong>: <strong>CP</strong> <strong>Comm<strong>and</strong>s</strong> <strong>and</strong> <strong>Utilities</strong> <strong>Reference</strong><br />

hexloc<br />

is the address at which to load the module.<br />

WWPN wwpn<br />

specifies the world wide port name for a specific path to a SCSI device. The<br />

wwpn must be a 16-digit hexadecimal number between X'00000000 00000000'<br />

<strong>and</strong> X'FFFFFFFF FFFFFFFF'. At least one separator blank is required after the<br />

eighth hex digit. WWPN is only valid if the vdev oper<strong>and</strong> refers to an F<strong>CP</strong><br />

device.<br />

If fewer than eight hex digits are specified for either part of the wwpn, that part<br />

will be padded with leading zeros to make it an eight hex digit number.<br />

LUN lun<br />

specifies the logical unit number for a specific path to a SCSI device. The lun<br />

must be a 16-digit hexadecimal number between X'00000000 00000000' <strong>and</strong><br />

X'FFFFFFFF FFFFFFFF'. At least one separator blank is required after the<br />

eighth hex digit. Note that the number of digits recognized by the SCSI device<br />

may vary by manufacturer, type <strong>and</strong> model. LUN is only valid if the vdev<br />

oper<strong>and</strong> refers to an F<strong>CP</strong> device.<br />

If fewer than eight hex digits are specified for either part of the lun, that part will<br />

be padded with leading zeros to make it an eight hex digit number, but this will<br />

almost certainly produce an invalid value. You must be careful to specify all 16<br />

digits, using trailing zeros, as per the note below.<br />

Important Note!<br />

Because SALIPL cannot know how many digits your device recognizes,<br />

you must enter all 16 digits. If your SCSI device is identified by fewer than<br />

16 digits, you should use trailing zeros to fill out the 16-digit lun. Note that<br />

if you enter non-zero digits following the digits identifying the SCSI device,<br />

those extra digits may be ignored by your device. (For example, if your<br />

device recognizes a four-digit lun, 5A51888811221122 <strong>and</strong><br />

5A51999933443344 would both represent the same device.) This could<br />

lead to unintended device sharing <strong>and</strong> hence might introduce data-integrity<br />

exposures. Always identify your SCSI device by its actual logical unit<br />

number as defined in your storage-area network, padded on the right<br />

with zeros.<br />

Volid<br />

specifies whether SALIPL should check the volume serial identifier of the <strong>CP</strong> or

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!