What tasks are generating the message? Here the explanation for S0B0 RC3C which IEF431E points to
| 3C The SWA Manager encountered a zero value as the pointer to the | QMPA while attempting to process an assign request. 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 are: | 1. Started jobs with PROC statements may not be run SUB=MSTR. | Either: | o remove the PROC statement, or | o remove the JOB statement and run it as a started task | o 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. System Action: The task ends and the system writes a dump. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Duane Weaver Sent: Friday, April 21, 2006 3:05 PM To: [email protected] Subject: IEF431E ZERO QMPA POINTER FOUND. SWA MANAGER REASON CODE=3C We copied our zOS 1.7 system (in test mode here) to another set of dasd to be run on a different mainframe under VM. We are getting the message IEF431E ZERO QMPA POINTER FOUND. SWA MANAGER REASON CODE=3C Anyone have any idea what this is referring to? Duane ---------------------------------------------------------------------- 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 ==================== This email/fax message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution of this email/fax is prohibited. If you are not the intended recipient, please destroy all paper and electronic copies of the original message. ---------------------------------------------------------------------- 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
