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.

DIRECTXA<br />

Responses<br />

Messages<br />

To do a test compile of a USER DIRECT source directory for a specific system<br />

named SYS<strong>VM</strong>A in a z/<strong>VM</strong>-only complex of systems sharing the source directory,<br />

enter directxa user direct * (edit sysafnid sysvma.<br />

To compile a USER DIRECT source directory for this system <strong>and</strong> to suppress the<br />

compatibility error messages, enter directxa user direct * (mixed nomixmsg.<br />

Response 1:<br />

When you enter the DIRECTXA comm<strong>and</strong>, you receive the following response:<br />

z/<strong>VM</strong> USER DIRECTORY CREATION PROGRAM - VERSION n RELEASE n.n<br />

You then receive Response 2, 3, or 4.<br />

Response 2:<br />

If the directory is updated <strong>and</strong> <strong>CP</strong> places the new directory in use, you receive the<br />

following response:<br />

EOJ DIRECTORY UPDATED AND ON LINE<br />

Response 3:<br />

If the directory is written to a <strong>CP</strong>-formatted DASD that is not a <strong>CP</strong>-owned volume,<br />

or if your virtual machine does not have the necessary privilege class to change the<br />

<strong>CP</strong> directory that is in use, you receive the following response:<br />

EOJ DIRECTORY UPDATED<br />

Response 4:<br />

If you issued DIRECTXA with the EDIT option or errors prevented the directory from<br />

being updated, you receive the following response:<br />

EOJ DIRECTORY NOT UPDATED<br />

H<strong>CP</strong>480E AN OPERAND OF THE LOAD<br />

STATEMENT IS MISSING.<br />

H<strong>CP</strong>481E THE LOAD STATEMENT TYPE FIELD IS<br />

INVALID; ONLY “C”, “G”, “P”, OR “U”<br />

IS ALLOWED.<br />

H<strong>CP</strong>482E THE FORMAT OF AN OPERAND ON<br />

THE LOAD STATEMENT IS INVALID.<br />

H<strong>CP</strong>483E THE CMS STATE COMMAND FAILED<br />

WITH RETURN CODE nnnn WHILE<br />

TRYING TO LOCATE THE DEFINITION<br />

FILE SPECIFIED ON THE LOAD<br />

STATEMENT.<br />

1818 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>485I THE DIRECTORY PROCESS IS<br />

RUNNING IN <strong>CP</strong>UID = nnnnnn-xxxx,<br />

WITH SYSTEM AFFINITY NAME =<br />

aaaaaaaa.<br />

H<strong>CP</strong>486E THE DIRECTORY CONTROL<br />

STATEMENT HAS AN INVALID <strong>CP</strong>UID<br />

FIELD.<br />

H<strong>CP</strong>487E NO DIRECTORY CONTROL<br />

STATEMENT WAS FOUND THAT<br />

MATCHES OUR <strong>CP</strong>UID (nnnnnn-xxxx).<br />

H<strong>CP</strong>489E THIS DIRECTORY CONTROL<br />

STATEMENT DOES NOT HAVE A<br />

SYSTEM AFFINITY ID.

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

Saved successfully!

Ooh no, something went wrong!