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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

|<br />

|<br />

|<br />

|<br />

|<br />

|<br />

SALIPL<br />

Responses<br />

Messages<br />

4. If you are IPLing <strong>CP</strong> from an F<strong>CP</strong> device (SCSI disk), PDVOL=raddr must be<br />

specified as an IPL parameter. Any device address that is not in the I/O<br />

configuration of the system to be IPLed can be specified for raddr. <strong>CP</strong> requires<br />

this parameter in order to build the EDEVICE control block for the SYSRES /<br />

PARM disk device during <strong>CP</strong> initialization.<br />

5. Attention: As of z/<strong>VM</strong> V5R1, the number of blocks on FBA DASD (SCSI or<br />

not) that SALIPL uses for SAPL has increased. SALIPL writes to blocks 5-207<br />

on <strong>CP</strong>-formatted DASD. In previous releases, SALIPL wrote to blocks 5-31. You<br />

must ensure that no other functions, such as <strong>CP</strong> directory, warmstart,<br />

checkpoint, paging, spooling, or minidisks, are using the area to which SALIPL<br />

writes.<br />

On a CMS minidisk with a RECOMP area, SALIPL writes SAPL to blocks 5-207<br />

of the RECOMP area. In previous releases, blocks 5-31 of the RECOMP area<br />

were used. In order to accommodate the larger size of SAPL, you may need to<br />

increase the size of the RECOMP area on the CMS minidisk.<br />

The following data is in the blocks that SALIPL writes out:<br />

Blocks 5–196 SAPL program<br />

Blocks 197–199 Reserved for <strong>IBM</strong> Use<br />

Blocks 200–207 SCSI boot records<br />

If you want to install SAPL on device 0400, a full-pack minidisk to which you have<br />

R/W access, <strong>and</strong> you want SAPL to use the CMS-formatted minidisk that is 210<br />

cylinders into the full-pack minidisk as the disk from which it will read a module, you<br />

enter this comm<strong>and</strong>:<br />

salipl 0400 (offset 210 module cpnew iplparms fn=sysnewVOLUME ID IS ESARES<br />

MINIDISK VOLID AT OFFSET 210 IS PARMD1<br />

Ready;<br />

The parameters entered on the SALIPL comm<strong>and</strong> specify that SAPL should look for<br />

a module called <strong>CP</strong>NEW on the CMS-formatted minidisk <strong>and</strong> should pass the IPL<br />

parameter fn=sysnew to the program when it is loaded.<br />

H<strong>CP</strong>003E INVALID OPTION - {option|COMMAND<br />

CONTAINS EXTRA OPTION(S)<br />

STARTING WITH option}<br />

H<strong>CP</strong>004E INVALID HEXLOC - hexloc<br />

H<strong>CP</strong>006E INVALID DEVICE TYPE - vdev<br />

H<strong>CP</strong>013E CONFLICTING OPTION - option<br />

H<strong>CP</strong>022E A VIRTUAL DEVICE NUMBER WAS<br />

NOT SPECIFIED OR IT WAS INVALID.<br />

H<strong>CP</strong>023E VOLID MISSING OR INVALID<br />

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

H<strong>CP</strong>040E DEVICE vdev DOES NOT EXIST.<br />

H<strong>CP</strong>352E FATAL DASD I/O ERROR<br />

H<strong>CP</strong>393E I/O ERROR ON DISK vdev; INCORRECT<br />

RECORD LENGTH<br />

H<strong>CP</strong>394E I/O ERROR; DISK rdev IS BUSY OR<br />

HAS INTERRUPT PENDING<br />

H<strong>CP</strong>395E PERMANENT I/O ERROR ON DISK<br />

rdev; SENSE=xxxxxxxx<br />

H<strong>CP</strong>396E I/O ERROR. THIN STACK<br />

FUNCTION=function RC=rc

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

Saved successfully!

Ooh no, something went wrong!