Duane,
When I first became aware of the "LookAt" function on the IBM web pages
( http://www-03.ibm.com/servers/eserver/zseries/zos/bkserv/lookat/ )
I immediately stored the URL among my favourites - (actually spelled
"Favorites", of course).
Rushing off to do the same when I saw your post, I discovered that it may be
even cleverer than I thought.
It first provides this reference:
<quote>
Ranked Search Results for Book: zidocmst "APAR and ++HOLD Documentation"
1 topics have matches for: IEF431E
NEW MESSAGE IEF431E IN ZOS 1.6 NOT DOCUMENTED IN SYSTEM MESSAGES MANUAL.,
477.1
</quote>
which, when selected, yields the following:
<quote>
477.1 NEW MESSAGE IEF431E IN ZOS 1.6 NOT DOCUMENTED IN SYSTEM MESSAGES
MANUAL.
CLOSING DATE: 12/21/2004
CLOSING CODE: DOC
Problem Summary
****************************************************************
* USERS AFFECTED: All HBB7709 and above installations *
****************************************************************
* PROBLEM DESCRIPTION: MSGIEF431E not documented *
****************************************************************
* RECOMMENDATION: *
****************************************************************
New message MSGIEF431E is not documented in the System
Messages manual.
Problem Conclusion
BOTH THE Z/OS V1R6.0 MVS SYSTEM MESSAGES MANUAL AND THE
z/OS V1R6.0 MVS System Codes manual will be updated with
the MSGIEF431E information below.
ORDER NO - SA22-7638-08
BOOK TITLE - z/OS V1R6.0 MVS System Messages, VOL8 (IEF-IGD)
CHANGE DESCRIPTION - Add the following message and associated
description to section 2.0 IEF Messages:
|IEF431E
|
|
| IEF431E Zero QMPA pointer found. SWA Manager reason code=3C
|
|
|EXPLANATION: While attempting to process an assign request,
| SWA Manager encountered a zero value as the pointer
| to the QMPA.
|
|System Action: The task ends and the system may issue an
| abend 0B0 and write a dump.
|
|Operator Response: Notify the application or system programmer.
|
|SYSTEM PROGRAMMER RESPONSE: See Application Programmer
|Response and take appropriate action. If the error
|persists, search the Problem Reporting data bases for
|a fix. If no fix exists, contact the IBM Support Center.
|
|APPLICATION PROGRAMMER RESPONSE: This message indicates that
|an error was found while attempting to assign a SWA block.
|The assign could not be completed due to the bad QMPA
|pointer. The reason code (''3C''x) associated with this message
|is described along with the reason codes for an abend 0B0.
|Refer to the MVS System Codes manual under the System
|Completion code 0B0, reason code ''3C''x for an explanation of
|how the QMPA pointer could contain a zero value. If an
|abend 0B0 was issued, review the dump for further diagnosis.
|
|Source: Scheduler Work Area (SWA) Manager
|
|Detecting Modules: IEFQB551, IEFQB556
|
|Routing Code: 2,11
|
|Descriptor Code: 11
|
ORDER NO - SA22-7626-09
BOOK TITLE - z/OS V1R6.0 MVS System Codes
CHANGE DESCRIPTION - Add the reason code (3C) description for
the existing 0B0 system abend code entry,
in topic 2.0 System Completion Codes,
subtopic 2.161 0B0 :
2.161 0B0
0B0
Explanation: The scheduler work area (SWA) manager detected
an uncorrectable error. Register 15 contains a reason code
explaining the error:
Reason Code (hex) Explanation
04
The routine that called SWA manager requested an incorrect
function
:
:
34
An attempt has been made to allocate or delete an SWA
block in environment.
| 3C
| While attempting to process an assign request, SWA
| Manager encountered a zero value as the pointer to the
| QMPA. The most likely cause of this error condition
| is that a task running under the Master Subsystem
| (SUB=MSTR) attempted a dynamic allocation in its own
| address space, but that address space had not yet been
| totally set up.
|
| Some specific causes are:
|
| 1. Attempting to run a Started JOB as SUB=MSTR or
| under a WLM Initiator (INIT), when the JOB to be
| started has an instream procedure (proc). The
| Converter issues a dynamic allocation to create
| a temporary PDS to hold the procedure being read
| in.
| 2. Attempting to run a Started Task (STC) as
| SUB=MSTR, but not all of the data sets needed
| for that Started Task are cataloged in the
| MASTER CATALOG. Either a JOBCAT or STEPCAT is
| included in the JCL, or simply one of the
| datasets in the JCL is cataloged in a USER
| catalog (usercat). Allocation itself issues a
| dynamic allocation for the required catalog.
| 3. The device type in the catalog for one of the
| data set needed by something being started
| SUB=MSTR is incorrect (e.g., it says that the
| data set is on a 3380, but it''s really on a
| 3390).
|
|
| Corrective Actions:
|
| 1. Started jobs with PROC statements may not be run
| SUB=MSTR.
| Either:
| - remove the PROC statement, or
| - remove the JOB statement and run it as a started
| task,
| - run it as SUB=JES2 (or JES3).
| 2. Ensure that all data sets required by jobs or tasks
| running SUB=MSTR are cataloged in the Master
| catalog or are directly pointed to by the
| specification of UNIT and VOL=SER parameters
| on the DD statement.
| 3. Ensure that the device types for all required
| catalogued data sets and any UNIT parameters
| on DD statements are correct.
</quote>
Of course, this looks like an APAR - but without the APAR number. Checking
the standard Search on the IBM home page confirms this - only after having,
as always, to select "Advanced search" and select "All" rather than "Any".
One "hit" is returned, the same text under the APAR OA09985.
So the strict answer to your question is "no" - but I hope I have indicated
how you might be self-sufficient when you find a supposedly undocumented
message. And, actually, the answer is still "no", I have no idea what is
causing the message to appear, but perhaps you will when you've read through
the text.
Chris Mason
----- Original Message -----
From: "Duane Weaver" <[EMAIL PROTECTED]>
Newsgroups: bit.listserv.ibm-main
To: <[email protected]>
Sent: Wednesday, 26 April, 2006 4:59 PM
Subject: ZERO QMPA pointer
> We presently have zOS1.7 in test under VM here. We made a copy of
> the system volumes for use on another mainframe also running VM.
>
> When we go to ipl 1.7 on the other mainframe running VM, the
> following message appears.
>
> IEF431E ZERO QMPA POINTER FOUND. SWA MANAGER REASON CODE=3C
>
>
> Does anyone have any idea what is causing this?
>
>
> Duane
> Ohio State U.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
