z/VM: System Messages and Codes Š CP - z/VM - IBM
z/VM: System Messages and Codes Š CP - z/VM - IBM
z/VM: System Messages and Codes Š CP - z/VM - IBM
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
H<strong>CP</strong>1353E H<strong>CP</strong>1358E<br />
description of that abend code for further information.<br />
H<strong>CP</strong>1353E An invalid {name name|page range<br />
nnnnn- nnnnn} was detected in the<br />
{DEFSYS|DEFSEG} comm<strong>and</strong>.<br />
Explanation: You issued a DEFSYS or DEFSEG<br />
comm<strong>and</strong> with an invalid name or page range. The<br />
variables in this message are as follows:<br />
name The name of the saved segment or NSS.<br />
nnnnn A 1- to 5-digit hexadecimal page number that<br />
must be less than or equal to X'7FEFF' (2047<br />
MB).<br />
<strong>System</strong> Action: <strong>CP</strong> halts processing of the DEFSYS<br />
or DEFSEG comm<strong>and</strong>, <strong>and</strong> creation of the system data<br />
file does not take place.<br />
Programmer Response: Correct the required name or<br />
page range <strong>and</strong> reissue the comm<strong>and</strong>.<br />
H<strong>CP</strong>1354E An invalid storage page descriptor<br />
code invalid-code was detected for page<br />
range nnnnn-nnnnn.<br />
Explanation: You specified an invalid page descriptor<br />
code (invalid-code) for page range nnnnn-nnnnn on the<br />
comm<strong>and</strong> line. Valid page descriptor codes are:<br />
EN Exclusive read/write access, no data saved<br />
ER Exclusive read-only access<br />
EW Exclusive read/write access<br />
SC <strong>CP</strong>-writeable, virtual machine shared read-only<br />
access, no data saved<br />
SN Shared read/write access, no data saved<br />
SR Shared read-only access<br />
SW Shared read/write access<br />
All page ranges in the same segment must be defined<br />
for either shared access (SC, SN, SR, or SW) or<br />
exclusive access (EN, ER, or EW), but not both.<br />
<strong>System</strong> Action: <strong>CP</strong> halts processing of the DEFSYS<br />
or DEFSEG comm<strong>and</strong>, <strong>and</strong> creation of the system data<br />
file does not take place. <strong>CP</strong> does not purge the<br />
previously-defined class S system data file for this NSS<br />
or saved segment name.<br />
Programmer Response: Correct the invalid storage<br />
page descriptor code <strong>and</strong> reissue the comm<strong>and</strong>.<br />
H<strong>CP</strong>1355E Segment number nnn was defined with<br />
both shared <strong>and</strong> exclusive page<br />
descriptor codes.<br />
Explanation: You specified a pair of page ranges for<br />
segment nnn with page descriptor codes specifying both<br />
shared <strong>and</strong> exclusive access. Valid page descriptor<br />
codes are:<br />
EN Exclusive read/write access, no data saved<br />
ER Exclusive read-only access<br />
EW Exclusive read/write access<br />
234 z/<strong>VM</strong>: <strong>System</strong> <strong>Messages</strong> <strong>and</strong> <strong>Codes</strong> — <strong>CP</strong><br />
SC <strong>CP</strong>-writeable, virtual machine read-only access,<br />
no data saved<br />
SN Shared read/write access, no data saved<br />
SR Shared read-only access<br />
SW Shared read/write access<br />
All page ranges in the same segment must be defined<br />
for either shared access (SC, SN, SR, or SW) or<br />
exclusive access (EN, ER, EW), but not both.<br />
If no ranges specified on the comm<strong>and</strong> have conflicting<br />
descriptor codes, the conflict is with a range in a<br />
previously-defined member of the segment space.<br />
<strong>System</strong> Action: <strong>CP</strong> halts processing of the DEFSEG<br />
or DEFSYS comm<strong>and</strong>, <strong>and</strong> creation of the system data<br />
file does not take place. <strong>CP</strong> does not purge the<br />
previously-defined class S system data file for this NSS<br />
or saved segment name.<br />
Programmer Response: Reissue the comm<strong>and</strong> <strong>and</strong><br />
make sure that all page ranges in the specified segment<br />
are defined with compatible page descriptor codes.<br />
When the conflict is with a currently-defined member of<br />
the segment space, use the QUERY NSS NAME fn<br />
MAP comm<strong>and</strong>. The output of this comm<strong>and</strong> shows the<br />
page ranges <strong>and</strong> their descriptor codes for each existing<br />
member of the logical saved segment.<br />
H<strong>CP</strong>1356E nnnnn-nnnnn is a conflicting page<br />
range. Please check for overlaps <strong>and</strong><br />
reissue the comm<strong>and</strong>.<br />
Explanation: You specified overlapping page ranges<br />
(nnnnn-nnnnn) on the comm<strong>and</strong> line.<br />
<strong>System</strong> Action: <strong>CP</strong> halts processing of the DEFSEG<br />
or DEFSYS comm<strong>and</strong>, <strong>and</strong> creation of the system data<br />
file does not take place.<br />
Programmer Response: Correct the overlap condition<br />
<strong>and</strong> reissue the comm<strong>and</strong>.<br />
H<strong>CP</strong>1358E <strong>CP</strong> saved segment name cannot be<br />
loaded in exclusive mode<br />
Explanation: You attempted to load the <strong>CP</strong> saved<br />
segment specified by name using the DIAGNOSE X'64'<br />
LOADNSHR subcode. A <strong>CP</strong> saved segment is one in<br />
which one or more page ranges were defined with the<br />
“SC” page descriptor code.<br />
<strong>System</strong> Action: <strong>System</strong> processing continues. The<br />
user’s storage is not changed.<br />
User Response: Verify that you specified the correct<br />
saved segment name. If you specified an incorrect<br />
saved segment name, reissue the Diagnose with the<br />
correct name. If the name was correct, <strong>and</strong> you want<br />
access to the <strong>CP</strong> saved segment, reissue the Diagnose<br />
with the LOADSHR (load shared) or LOADNOVL (load<br />
shared with no overlay) subcode instead of with the<br />
LOADNSHR (load non-shared) subcode.