6. SOC7 Abend

        The most frequent abend and famous one is SOC7 Abend while submitting a Jcl.
This occurs for so many reasons.  See below for how to fix it.

Fix
----
1. Check your decimal data being used in program. Try to pass valid decimal data.
2. Data being passed is not initialized correctly.
3. Array index is not valid. It is a kind of subscript error.
4. Value being passed is not available in table.
5. COBOL working storage section is not initialized with given variable.
6. 'Parm' used in subroutine or program is not in correct order or missing.

Check for all the above fix. Now re run your job, your SOC7 will be fixed.

5. S806 Abend

     If you are getting S806, this may be due to one of the following reasons.

1. Load Module not found in loadlib.
2. Missing Joblib or Steplib card.
3. Tried to execute a non existent program
4. SYSIN card given incorrectly to LKED or name card missing.

Sample JCL
--------------
//LOADJOB JOB 'LOAD',NOTIFY=&SYSUID

//STEP1  EXEC PGM=IKJEFT01, 
//              DYNAMNBR=20 
//STEPLIB DD DSN=SAMPLE.LOAD,DISP=SHR 
//        DD DSN=SAMPLE.LOAD.IN,DISP=SHR 
//        DD DSN=SAMPLE.RUNLIB.LOAD,DISP=SHR 
//        DD DSN=SAMPLE.CICS410.LOADLIB,DISP=SHR 
//DBRMLIB DD DSN=SAMPLE.MAC.DBRM,DISP=SHR   
//SYSTSPRT DD SYSOUT=A 
//SYSPRINT DD SYSOUT=A 
//SYSUDUMP DD SYSOUT=A 
//SYSTSIN DD * 
      DSN SYSTEM(DSN) 
      BIND PLAN(PLAN1) MEM(PGM1)  -
      LIBRARY ('SAMPLE.MAC.DBRM')    -
      RELEASE(COMMIT) ISOLATION(CS)   - 
      VALIDATE(BIND)                                       - 
      ACTION(REPLACE) OWNER(NAGU)    
      END 
/* 
//

Fix:
----
1. Make sure your load module is available in the given load lib.
2. Check whether PDS name given in step lib is spelled correct.
3. The member name given in SYSIN card should be available in given library.

Check the above three fix and re-run your job. S806 abend will be fixed.

4. U3303 - IRT060W 

   If you find the above abend while running your job, just follow the below steps to fix it.

Fix:
----
1. Check for your spool output messages.
2. See Your Database will be in stopped status.
3. Search for the name of your DB and start it.
4. Try re running your job. This will fix your U3303.

3. SB37 - IEA848I NO DUMP WAS PRODUCED FOR THIS ABEND, DUE TO SYSTEM OR                   
    INSTALLATION REQUEST.

     If you get SB37 abend in your JCL and if you find the above information in your spool output message, then follow the below fix.


//Spacejob Job Class=A,Msglevel=1,Msgclass=s
//Step1       Exec Pgm=SpacUtil
//Input        DD    Dsn=Sample.Space.Input,Disp=SHR
//Output     DD    Dsn=Sample.Space.Output,
//                       Disp=(New,Catlg,Delete),
//                       Dcb=(Lrecl=80,Blksize=800,Recfm=FB),
//                       Space=(Trk(500,100),Rlse)
//Master      DD    Dsn=Sample.Master.Output,Disp=SHR 


Fix
----
1. Find the Master Data set 'Sample.Master.Output'. Note the space allocated for it.
2. Delete the Data set 'Sample.Master.Output'.
3. Create a new data set with the same name with increased amount of space.

Example:
----------
Previously 'Sample.Master.Output' has Allocated space as Trk(100,100).
Now, increase its size as Trk(800,500).

This will fix your job.

  2.  SB37 Abend

The most primary abend you will be getting is SB37.

//Spacejob Job Class=A,Msglevel=1,Msgclass=s
//Step1       Exec Pgm=SpacUtil
//Input        DD    Dsn=Sample.Space.Input,Disp=SHR
//Output     DD    Dsn=Sample.Space.Output,
//                       Disp=(New,Catlg,Delete),
//                       Dcb=(Lrecl=80,Blksize=800,Recfm=FB),
//                       Space=(Trk(500,100),Rlse)                                


If you are getting this SB37, then you need to increase the primary allocated space.
Follow the below steps to fix it.

Fix 1:
------
In the above Jcl, you need to change the 500 to, say, 800.

//                       Space=(Trk(800,100),Rlse)             

This will almost fix you SB37. If you are still getting SB37, follow Fix 2.

Fix 2:
------
If you are still getting SB37, then you need to increase the secondary allocated space. See the below line.

//                       Space=(Trk(800,500),Rlse)        

This will fix your job.

Fix 3:
------

If still you are getting the same SB37, then you need to change the Tracks to Cylinders. See below for the change.

//                       Space=(Cyl(10,10),Rlse)  

This will make your job fine.

1. S837 Abend
    
If you are getting S837 abend, then follow the below steps to fix it.


//Spacejob Job Class=A,Msglevel=1,Msgclass=s
//Step1       Exec Pgm=SpacUtil
//Input        DD    Dsn=Sample.Space.Input,Disp=SHR
//Output     DD    Dsn=Sample.Space.Output,
//                       Disp=(New,Catlg,Delete),
//                       Dcb=(Lrecl=80,Blksize=800,Recfm=FB),
//                       Unit=Disk,
//                       Space=(Cyl(1,1),Rlse)         



Well, this abend happens when memory need to be released.
You can follow any of the below two steps to fix it. Most recommended one is the first fix.

Fix 1:
------

You need to contact your project analyst to free up the allocated memory space.
In this case, you have given the minimum cylinders of cyl(1,1). But that itself is considered to be more. 

So, the project analyst need to free up the unwanted memory space and after that if you re-run the job, your S837 will be fixed.

Fix 2:
------

If you change the Unit parameter as Tape from Disk as below

//                       Unit=Tape,

Then space will automatically be freed. If you re-run your job, S837 will be fixed.
But, this will work until your tape has free space.

When tape is also full, then again S837 abend will come. You need to contact your project analyst again to free up space. So, its better to follow Fix 1 always.

Hi Guys,
     This is a new blog where you can search for all the Jcl Abend Codes and how it can be fixed. In my next posts, i will be giving the most frequent Jcl Abend and fix for the same.