What does your JES2 proc look like? Are all datasets in it catalogued in the MASTER catalog? Are all datasets in the proc properly catalogued? I.e. the correct device type a volser. One thing that occurs to me might be that something is indirectly catalogued (to volser ******), but with a DEVT of other than X'0000'.
ref: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/iea2m8a0/2.255 http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2H7A0/2.163 <quote> 3C While attempting to process an assign request, the 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 is not yet totally established. Some specific causes are as follows: 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 data sets in the JCL is cataloged in a USER catalog (usercat). Allocation issues a dynamic allocation for the required catalog. 3. The device type in the catalog for one of the data sets that is started as SUB=MSTR is incorrect (for example, the information specifies that the data set is on a 3380 device, but the data set is really on a 3390 device.). Corrective actions are: 1. You cannot run started jobs with PROC statements as SUB=MSTR. Do one of the following actions: * 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. System Action: The task ends and the system writes a dump. Operator Response: Notify the system programmer. Application Programmer Response: If the program that ended was a started task, and the code in register 15 is X'08' or X'0C', check the JCL for this task. For all started tasks, the JCL must either: * refer to existing data sets that are cataloged in the master catalog; or * include unit and volume information on the DD statements for existing data sets. Modify the JCL to meet one of these requirements, and resubmit the job. System Programmer Response: If the problem recurs and if the program is not in error, search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. It is the responsibility of the caller to SWA manager to take the dump, and if none was taken, then a SLIP would need to be set up to capture the failure. Provide the dump to the IBM Support Center. Source: Scheduler work area (SWA) manager </quote> -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * (817)-961-6183 cell [email protected] * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM > -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:[email protected]] On Behalf Of Matan Cohen > Sent: Thursday, February 25, 2010 8:20 AM > To: [email protected] > Subject: URGENT - PROBLEM WHILE STARTING JES2 > > Hi, > > I got $HASP050 on BUFX - Extended logical buffers . > so i added bufx with the $t defbuf. > the message disappeared but jobs and started task were stuck . > i started performing IPL with cancel all jobs/stc/db2, the i > try one more > time to execute my STC for shutdown the computer and it > actually worked. > so i finish ipl as always . > when the system start jes2 it failed and i get the following > message : > *16.15.02 *IEF431E ZERO QMPA POINTER FOUND. SWA > MANAGER REASON > * CODE=3C > > i don't get any further message by jes2. > re-ipl didn't work also . > > any idea? > > -- > best regards, > matan cohen > MF System Administrator. > > ---------------------------------------------------------------------- > 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 > > ---------------------------------------------------------------------- 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
