On my both my zVM 4.4 & 5.2 systems if I use PARM INSTSEG on the IPL 
command the message tells me the name of the segment that could not be 
loaded, such as:

i cms parm instseg bhn                                           
DMSWSP327I The installation saved segment BHN could not be loaded

or: 

i cms parm instseg                                      
DMSWSP327W INSTSEG value omitted; no shared EXECs loaded


Is the message you posted a cut & paste or a retype that might have the 
segment name omiited?

Brian Nielsen

On Mon, 23 Jan 2006 14:00:48 -0000, Dusha, Cecelia, Ms., WHS/ITMD 
<[EMAIL PROTECTED]> wrote:

>The problem I am experiencing on my zVM 5.1 system is described below.
>
>
>
>ipl cms
>
>DMSWSP327I The installation saved segment could not be loaded
>
>
>
>MSG DMSWSP327I               All Help Information                 line 1 
of
>27
>
>(c) Copyright IBM Corporation 1990, 2004
>
>
>
>
>
> DMS327I   The <installation|multitasking> saved segment segname could not
>be
>
>           loaded
>
>
>
>
>
> System Programmer Response:  If the INSTSEG or MTSEG parameter was used 
on
>the
>
> IPL command, verify it is the correct name of a CMS Installation or
>
>
> Multitasking Saved Segment. If the INSTSEG or MTSEG parameter was not 
used
>on
>
> the IPL command, verify the correct name for the Installation or
>Multitasking
>
> Saved Segment was specified in DMSNGP or in response to the Installation 
or
>
>
> Multitasking Saved Segment name prompt when the CMS nucleus was 
generated.
>In
>
> either case, if the correct name was specified, verify the Installation 
or
>
>
> Multitasking Saved Segment has not been purged.
>
>
>
>
>The only updates to zVM 5.1 DMSNGP ASSEMBLE is to change the CMS IPL area 
on
>MAINT's 190 disk.
>
>My zVM 3.1 system does not have any additional changes, but the above
>message does not appear when CMS is IPLed.
>
>DMSNGP   ASSEMBLE F1  F 80  Trunc=71 Size=122 Line=113 Col=1 Alt=0
>
>
>
>
>
>00113                INSTSEG=CMSINST,     * Name of above saved segment
>*
>
>00114                USEMTSG=YES,         *** See Operation section
>@SE062PQ*
>
>00115                MTSEG=VMMTLIB,       *** See Operation section
>@SE062PQ*
>
>
>
>zVM 5.1:
>
>q nss name cmsinst
>
>FILES:   NO NSS
>
>Ready; T=0.01/0.01 08:47:01
>
>q nss name instseg
>
>OWNERID  FILE TYPE CL RECS DATE  TIME     FILENAME FILETYPE ORIGINID
>
>*NSS     0026 NSS  A  0770 12/15 11:13:27 INSTSEG  DCSS     MAINT
>
>Ready; T=0.01/0.01 08:47:11
>
>q nss name mtseg
>
>FILES:   NO NSS
>
>Ready; T=0.01/0.01 08:47:21
>
>q nss name vmmtlib
>
>FILES:   NO NSS
>
>Ready; T=0.01/0.01 08:47:32
>
>
>
>I get the same results from the above queries on my zVM 3.1 system, but 
the
>message does not appear when CMS is IPLed.
>
>
>
>The zVM 5.1 Service Guide on page 3-69 says:
>
>11.  Build the CMSINST logical saved segment.
>
>      Vmfbld ppf segbld esasegs segblist instseg (serviced
>
>This step generates the INSTSEG segment...
>
>
>
>The message says, "If the INSTSEG or MTSEG parameter was not used on the 
IPL
>command, verify the correct name for the Installation or Multitasking 
Saved
>Segment was specified in DMSNGP or in response to the Installation or
>Multitasking Saved Segment name prompt when the CMS nucleus was 
generated."
>
>
>
>Do I need to perform a detailed build of CMS to get CMS to recognize the
>INSTSEG segment?
>
>
>
>Please advice.
>
>
>
>Thank you.
>
>
>
>Cecelia Dusha
>=========================================================================

Reply via email to