Space allocation issue in production jobs

In this Mainframe Forum - You can post your queries on JCL, OS/390 JCL, MVS JCL, z/OS JCL, JES2 & JES3

Moderators: Frank Yaeger, DikDude, Moderator Group

Post Reply
diwz
Member
Posts: 44
Joined: Sun Feb 10, 2013 10:39 am

Space allocation issue in production jobs

Post by diwz » Tue Feb 26, 2013 5:23 pm

Some of jobs are running with space violations (reported by stopx37 report) at my shop. Stopx37 tool dynamically allocates the spaces at run time and prevent the jobs from abend. As a permanent fix I have to increase the SPACE parameter in JCL and implement in Production.

After increasing the SPACE parameter, while I am testing the job in Dev region I am looking for similar SPACE violation each time when I execute the job. If SPACE violation occurs, I will be increasing the SPACE parameter and test it again until the job doesnot get SPACE violation (SPACVOLA)

I will run the job by increasing the space parameter until I will not get the below message
IEF233A M 0C41,E50223,,A12457Q,SORT,AFRGT.QDPDBRUN.POSFLE.G0618V00
SVM4000I A12457Q, STEP01.SORT, SORTOUT, ATTEMPTING SPACVOLA FOR ANN2107.PZPOSRU
SVM4400I VOLUME ADDED - OLD VOLUME DMAX14, NEW VOLUME SMS
SVM4000I A12457Q, STEP01.SORT, SORTOUT, ATTEMPTING SPACVOLA FOR A12457.QDPOSRU
SVM4400I VOLUME ADDED - OLD VOLUME DMAX01, NEW VOLUME SMS

Now the issue is, There is a dataset which has huge data in production, STOPX37 dynamically allocates the space and preventing the space abend daily. When I try to increase the space parameter inorder to give permanent fix, I couldn't do it. The z/OS says,

GD17277I THERE ARE (61) CANDIDATE VOLUMES OF WHICH (57) ARE ENABLED OR QUIESCED
GD17290I THERE WERE 2 CANDIDATE STORAGE GROUPS OF WHICH THE FIRST 2
ERE ELIGIBLE FOR VOLUME SELECTION.
HE CANDIDATE STORAGE GROUPS WERE:SMSXLRG OVFLD1
GD17279I 4 VOLUMES WERE REJECTED BECAUSE THEY WERE NOT ONLINE
GD17279I 4 VOLUMES WERE REJECTED BECAUSE THE UCB WAS NOT AVAILABLE
GD17279I 57 VOLUMES WERE REJECTED BECAUSE OF A DADSM FAILURE (044E0097)
EF272I ANN2107Q SORT STEP01 - STEP WAS NOT EXECUTED.

Is there anyway that I can correct the issue before I go to SMS admin.

William Collins
Active Member
Posts: 732
Joined: Thu May 24, 2012 4:07 am

Post by William Collins » Tue Feb 26, 2013 5:42 pm

Have you thought of calculating the expected SPACE requirements from the profile of the data? You shouldn't have to keep running things until your messages go away.

No, I don't think you'll be able to do anything yourself to get space for your huge file to run in that test environment.

diwz
Member
Posts: 44
Joined: Sun Feb 10, 2013 10:39 am

Post by diwz » Tue Feb 26, 2013 6:40 pm

Yeah. I should do that as next step. I have to find out the nature of volumes of data that came in the past runs from the dataset and contact SMS admin

Now do I have to contact SMS admin now to see what volume is suitable for this dataset in production region?

William Collins
Active Member
Posts: 732
Joined: Thu May 24, 2012 4:07 am

Post by William Collins » Tue Feb 26, 2013 8:05 pm

A good idea, I think. I suspect they are "aware" of it, and will perhaps appreciate the interest, and may have suggestions about the file, and how you should go about your task generally.

diwz
Member
Posts: 44
Joined: Sun Feb 10, 2013 10:39 am

Post by diwz » Fri Mar 01, 2013 1:22 pm

I checking with them. I wil update if they find any.

Post Reply

FREE TUTORIALS

Tutorials
Free tutorials from mainframegurukul
  • JCL Tutorial
    Covers all important JCL concepts.
  • Cobol Tutorial
    This tutorials covers all Cobol Topics from STRING to COMP-3.
  • DB2 Tutorial
    DB2 Tutorial focuses on DB2 COBOL Programming.
  • SORT Tutorial
    This Tutorial covers all important aspects of DFSORT with examples
  • CICS Tutorial
    This CICS tutorial covers CICS concepts and CICS Basics, CICS COBOL Programming.
Interview
Mainframe Interview questions



Other References
Mainframe Tools and others