Jcl Error B37-04
Contents |
(troubleshooting) Problem(Abstract) When scanning JCL in IBM
System Abend Code = B37, Reason Code = 00000004
WebSphere Studio Asset Analyzer, B37-04 errors are reported. Cause B37-04 is a e37-04 space issue, specifically with the temporary file space used by the EXIT processing in the DMH610Z routine. DMH610Z is ifg0554a used to create a list of libraries and members which are to be analyzed and loaded in the database. The code in DMH610Z that allocates it is: /* This ALLOCATION is about 40,000 files per container, as 500 */
Iec028i 837-08
/* files fit in 1 track: ((5 + (5 * 15)) * 500) = 40,000 */ "ALLOC FI(FILELIST) DA('"ssParmFile"') NEW CATALOG TRACKS SPACE(5,5) LRECL(80) RECFM(F,B) DSORG(PS)" The space is set up for 40,000 files so the B37-04 means you have run out of extents (only allowed 16). Resolving the problem Change the space allocation by editing yourHLQ.SDMHREXX(DMH610Z) and increasing the space allocation in the code shown above. Document information More support for: WebSphere Studio Asset Analyzer Inventory scan Software version: 4.1 Operating system(s): z/OS Reference #: 1227089 Modified date: 2009-09-11 Site availability Site assistance Contact and feedback Need support? Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility
File for Statistics STERLINGPRI iec070i 209-220 Technote (troubleshooting) Problem(Abstract) Your Batch job receives an abend B37 04
Iec032i
when trying to extract and allocate a TEMP Dataset File for the Statistics. Symptom Batch job encounters Abend B37-04 http://www.ibm.com/support/docview.wss?uid=swg21227089 when trying to extract and allocate a TEMP Dataset File for the Statistics. Resolving the problem Choose one of these options: In the Connect:Direct User's Guide under the section 'Using SIGNON through the Batch Interface'. You can add http://www.ibm.com/support/docview.wss?uid=swg21538876 a SPACE= parameter to the SIGNON statement in the DMBATCH control statements. SIGNON SPACE= (CYL | TRK | blk,([prim],[sec])) to increase the size of the temporary data set. You can also pre-allocate a file and reference it on the SIGNON statement with the TMPDD= temporary data set ddname or TMPDSN= temporary data set name but not both. Historical Number PRI8208 SCI66215 Document information More support for: Sterling Connect:Direct for z/OS Software version: 4.8, 5.0, 5.1, 5.2 Operating system(s): z/OS Reference #: 1538876 Modified date: 2011-10-07 Site availability Site assistance Contact and feedback Need support? Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility
is not enough space on the DASD unit[s], defined for the data set allocation. Sequential data set can be allocated in up to 16 extents (normally one primary and http://mainframe-tips-and-tricks.blogspot.com/2011/12/jcl-how-to-fix-b37-abend.html up to 15 secondary). When Operating System can't find space for primary allocation, http://faculty.madisoncollege.edu/schmidt/mainframe/abendcodes.html job gets cancelled with JCL error before attempting to execute it. If primary allocation request is satisfied, job starts running, allocating secondary extents when (and if) necessary. If an attempt to allocate secondary extent fails, job AbEnds with B37. There is a popular belief that increasing primary space solves B37 AbEnd problem. Indeed, it jcl error might work for some situations, but it might fail to work for other (those with significant deviations in the size of the data set). B37 AbEnd is caused by the failure of secondary space allocation and this is what should be addressed when fixing a B37 problem. The right solution is to specify more than one (default) UNIT for the output data set, E.g.: UNIT=(SYSALLDA,3). Thus, when system jcl error b37-04 can't find secondary extent on the first volume (i.e. volume where primary extent is allocated), it switches to the second volume, etc. Normally specifying 2 or 3 UNITs will work, but it might make sense to specify more, depending on the number of generally available DASD units and predicted deviations in the data set size. Provided that there are enough DASD units for secondary space allocation, it is important also to maintain some sort of a reasonable balance between primary and secondary space requests. While there are no universal rules for determining what balance is "right", there is "rule of a thumb" that works reasonably well in most cases. Evaluate the "peak" volume of the output data set (CYLs or TRKs). One good way is to look at input file processing of which caused B37 AbEnd and make approximate adjustments based on the ratio of output/input record lengths. Let it be 100 CYLs, for example. Use 50% of the "peak" volume as primary space and 10% of the peak volume as secondary space. This will give the following space allocation for 100 CYL "peak" volume example: SPACE=(CYL,(50,10),RLSE). Request to ReLeaSE unused space when the output data set gets closed is a good
Disk space problem Below is a summary of the common messages that could occur. Each message is identified by a message number, and is formatted as: NNNNNNN ccc-rr jjj sss ddname where NNNNNNN is the error message number ccc is the system completion code associated with the message rr is the return code associated with the message jjj is the job name sss is the step name ddname is the file associated with the problem Message Number Parameters/Description IEA702I 80A-1 There is not enough storage to run the request program IEA703I 806-x x=4 The requested program could not be found. Check the JCL STEPLIB or JOBLIB statements to be sure they define the library containing the requested program. x=8 An uncorrectable input-output error has occurred. Try to run the job again. If the error reoccurs, consult your technical support staff IEC015I A34-04 An attempt was made to read an unopened file. IEC020I 001-x x=1, 3, or 4 The dataset characteristics don't match the specified file. Check your FD, JCL and data set information x=2 An error occurred when the program tried to close the file x=5 The program tried to read the file after end of file had been reached. IEC030I B37-04 There is no space left on the disk volume The data set has reached it's limit of space The disk volume table of contents is full IEC031I D37-04 The file has used up all of its space IEC032I E37-x x=04 All available disk space is used up IEC141I 013-x x=10, 34 The block size and record length are both 0 or the block size is not a multiple of the record length. x=20 The record format indicates that the file is a blocked file, but the block size is not a multiple of the record size. x=60 The record format indicates that the file is an unblocked file, but the block size does not equal the record length x=68 The block size exceeds the maximum allowable IEC143I 213-x x=04 1) An incorrect volume or data set name parameter 2) Data set not found on disk 3) The data set has been deleted x=08 Password violation x=18, 1C I/O error Common Completio