Automated Testing

Automated Testing

Automated Testing

Build an automated testing process to enable continuous integration of your hybrid cloud applications including z/OS

 View Only
Back to discussions
Expand all | Collapse all

Error during ZDT IPL AWSEMI307I Warning! Disabled Wait CPU 0

  • 1.  Error during ZDT IPL AWSEMI307I Warning! Disabled Wait CPU 0

    Posted Mon September 25, 2017 11:11 AM

    A customer is working on a full lpar copy scenario and - during the IPL - they are not able to start

    Their message error is this one:

    AWSEMI307I Warning! Disabled Wait CPU 0 = 00020000 80000000 00000000 00878040

    This scenario is very similar  to the scenario described in the following link

    https://www.ibm.com/developerworks/community/forums/html/topic?id=fc3ac280-eed7-4bb4-8dd2-ba55c47bc9ab

    but I'm not able to find more details in MVS system codes (https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieah700/h7scc.htm)

     

     

    gius


  • 2.  Re: Error during ZDT IPL AWSEMI307I Warning! Disabled Wait CPU 0

    Posted Mon September 25, 2017 11:29 AM

    This is another wait state PSW.  As documented in z/OS MVS System Codes V2R1 - SA38-0665, the wait state code is the rightmost 3 bytes, in this case, 040.  040 is documented in the previously mentioned publication as follows:

    40
    Explanation:     The system abended a task during nucleus initialization program (NIP) processing.

    The right-most four bytes of the program status word (PSW) have the following format:

    x0cccwww

    where:

    x Irrelevant information.

    ccc A hexadecimal abend code indicating the reason for the failure.

    www The wait state code.

    System action: The system issues message IEA303W. The system enters a non-restartable wait state.

    Operator response: Record the wait state PSW and report the problem to the system programmer. If the system programmer requests it, obtain a stand-alone dump.

    System programmer response: See the system programmer response for the abend code displayed in message IEA303W.

    The abend SVC entry in the system's SVC table contains the address of a trap routine in NIP, and not the address of the abend SVC. The registers (0 through 15) at the time of the abend SVC request are found in the area pointed to by field NVTDIAGA (mapped by macro IHANVT).

    If the problem persists, search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM Support Center. Providing the contents of the wait state PSW.

    Source: Nucleus initialization program (NIP)

     

    The abend code for this error is 878.  Again, referring to the previously mentioned pub, an 878 abend is documented as follows:

    878

    Explanation: The error occurred when the system was trying to do one of the following: v Satisfy a request made through the STORAGE macro
    v Process an RU or VRU form of the GETMAIN macro
    v Process an RU form of the FREEMAIN macro

    A reason code in the SDWACRC field of the system diagnostic work area (SDWA) explains the error:

    Code Explanation
    04     There is not enough virtual system queue area (SQA) storage available to satisfy the request. 08 There is not enough virtual common service area (CSA) storage available to satisfy the request.

    Chapter 2. System Completion Codes 341

    878

    0C There is not enough virtual local system queue area (LSQA) storage available to satisfy the request.
    10 There is not enough virtual private area storage available to satisfy the request. This is due to one of the

    following:

    v A program is requesting virtual storage, but not subsequently freeing the storage.

    v The region size specified is too small.

    v An installation exit is requesting virtual storage from a V=R region before initialization of the region has completed.

    14 A negative amount of storage was specified on a GETMAIN macro.
    Note: If this error is detected, the calling program abnormally ends even though RC, EC, LC, or VC is

    specified for GETMAIN, or COND=YES is specified for STORAGE.
    18 A negative amount of storage was specified on the FREEMAIN or STORAGE macro.

    Note: If this error is detected, the calling program abnormally ends even though RC, EC, LC, or VC is specified for FREEMAIN, or COND=YES is specified for STORAGE.

    1C During request processing, the system tried to get LSQA virtual storage for virtual storage management's (VSM) cell pool. There was not enough LSQA virtual storage available.

    20 There is not enough virtual storage in the LSQA to build a new address queue anchor table (AQAT) stack. 24 A GETMAIN or STORAGE OBTAIN request with the LOC=EXPLICIT keyword specified failed for one of

    the following reasons:

    v Part of the requested area was already allocated.

    v Storage was already allocated in the same page as this request, but one of the following characteristics of the storage was different:

    • -  The subpool

    • -  The key

    • -  Central storage backing

    28 A GETMAIN or STORAGE OBTAIN request with the LOC=EXPLICIT keyword specified failed because part of the requested area exceeds the bounds of the region.

    System action: The system issues message IEA705I. The system abnormally ends the current task.

    Programmer response: A complete dump is necessary to diagnose this out of storage condition. If no dump was produced, SLIPs should be set to obtain a dump on problem recurrence. Further debugging information may be found in Informational APAR II05506. An abend 80A can cause this same condition, so both SLIPs should be set as follows: 

     SLIP SET,COMP=878,A=SVCD,SDATA=(ALLNUC,   PSA,SQA,CSA,LPA,TRT,LSQA,RGN),END
     SLIP SET,COMP=80A,A=SVCD,SDATA=(ALLNUC,   PSA,SQA,CSA,LPA,TRT,LSQA,RGN),END

    Also, depending on the reason code, do one of the following:

    10

    24

    Try increasing the region size specified in the region parameter on the JOB or EXEC statement in the JCL for the job. However, if the cause of the problem is actually that a program is requesting virtual storage and not freeing it, the abend will recur when the program uses the virtual storage in the larger region.

    Ensure that the calling program specifies the following correctly:

    342

    z/OS V2R1.0 MVS System Codes

    v v v v v

    The storage address on the INADDR keyword.
    The length on the LENGTH keyword for the STORAGE macro or the LV keyword for the GETMAIN macro. The desired subpool or key.
    The target address space for the STORAGE macro.
    The TCB address for the STORAGE macro.

    Make sure also that the area of storage you are requesting is completely free. If part of the area requested is in a page that is already allocated, make sure that the central storage backing specified on the LOC=EXPLICIT keyword matches that of the allocated storage.

    28 Ensure that the calling program specifies the following correctly:
    v The storage address on the INADDR keyword.
    v The length on the LENGTH keyword for the STORAGE macro or the LV keyword for the GETMAIN macro.

    Make sure also that the calling program correctly specifies the value on the JCL REGION keyword. If the JCL REGION value is not large enough for the requested storage area, increase the size of the JCL REGION and resubmit the job.

    04-0C, 14-20

    Check for program errors that incorrectly modify the macro expansion and correct them. If necessary, change the program to request less virtual storage.

    Source: Virtual storage management (VSM)

     

     

    Since this is a storage related error as defined by the 878, I would double check the memory settings in the devmap to ensure there is available memory to start the emulator.  You can refer to the zPDT redbooks for recommendations on the minimum recommended memory allocations.

     

    RDzJohn

     

    RDzJohn


Related Content