|
View previous topic :: View next topic
|
| Author |
Message |
ap_mainframes
Active User
Joined: 29 Dec 2005
Posts: 181
Location: Canada
|
|
|
|
Hi,
I am using DFSORT and doing some processing, but since I am processing lots of records , its taking time and hence I am getting time abend S722.
I tried putting TIME=1440 in my job card, but still its not working.
Can anybody please suggest something so that there in limit to my JOB, as it is bound to take lot of time.
Thanks for all the information you can provide.
Thanks
ap_mainframes |
|
| Back to top |
|
 |
parikshit123
Active User
.jpg)
Joined: 01 Jul 2005
Posts: 269
Location: India
|
|
|
|
Hi,
You may need to use different class.
Please consult your admin as to which other classes are available. |
|
| Back to top |
|
|
ralph_v
New User
Joined: 07 Jul 2005
Posts: 27
|
|
|
|
| S722 time abend occurs when you specify number of pages to print using OUTLIM parameter and when the number of pages exceeds the limit specified in the OUTLIM parameter , you will get this error. |
|
| Back to top |
|
|
ap_mainframes
Active User
Joined: 29 Dec 2005
Posts: 181
Location: Canada
|
|
|
|
Ralph,
Thanks for reply, however I am not specifying any OUTLIM parameter in my JCL.
I guess it is taking some system default. If it is, then whats the remedy ???
Thanks
ap_mainframes |
|
| Back to top |
|
|
Bharanidharan
New User
Joined: 20 Jun 2005
Posts: 86
Location: Chennai, India
|
|
|
|
| I believe S722 is not time abend, but rather is given when JES2 output limit is exceeded. Try LINES=999999 in your JOBPARM. |
|
| Back to top |
|
|
cjcpr
New User
Joined: 21 Mar 2006
Posts: 21
Location: USA
|
|
|
|
S722 - TIMEOUT (OUTPUT LIMIT REACHED, JOB EXCEEDED NUMBER OF ALLOWABLE LINES)
Eventhough the book definition says it is time abend the real cause is given in the paranthesis. may be DUMMY the SYSOUT? |
|
| Back to top |
|
|
ap_mainframes
Active User
Joined: 29 Dec 2005
Posts: 181
Location: Canada
|
|
|
|
| Ok..Any remidies for this issue ??? |
|
| Back to top |
|
|
Bharanidharan
New User
Joined: 20 Jun 2005
Posts: 86
Location: Chennai, India
|
|
|
|
Please see my previous posting. Include LINES=999999 in your JOBPARM.
| Code: |
//jobname JOB 'acct','name',
// CLASS=A,MSGCLASS=H,NOTIFY=&SYSUID
/*JOBPARM LINES=999999
|
If this is not successful, check if you have defined any limits for any or all of BYTES, CARDS, LINES or PAGES. If so, then you may need to change them to 999999. |
|
| Back to top |
|
|
Prasanthhere
Active User
Joined: 03 Aug 2005
Posts: 306
|
|
|
|
Check Whether ur program has any input/output loops.since more lines is getting populated and check whther it conflicts with the installation dependent values  |
|
| Back to top |
|
|
varun_sharma
New User
Joined: 08 Jun 2005
Posts: 19
Location: new delhi
|
|
|
|
Hi
Give it a try with sort work files, i'm quite sure it'll work. Also when the pgm goes into an infinite loop, u get this stuff. Check it in expeditor and try to send the jcl.
Cheers
Varun |
|
| Back to top |
|
|
ap_mainframes
Active User
Joined: 29 Dec 2005
Posts: 181
Location: Canada
|
|
|
|
Hi Varun/Prasanthhere,
I am not runing a program, its a sort.
Thanks
ap_mainframes |
|
| Back to top |
|
|
cjcpr
New User
Joined: 21 Mar 2006
Posts: 21
Location: USA
|
|
|
|
| ap_mainframes wrote: |
| Ok..Any remidies for this issue ??? |
| cjcpr wrote: |
| may be DUMMY the SYSOUT? |
|
|
| Back to top |
|
|
cjcpr
New User
Joined: 21 Mar 2006
Posts: 21
Location: USA
|
|
|
|
| ap_mainframes wrote: |
| Ok..Any remidies for this issue ??? |
| cjcpr wrote: |
| may be DUMMY the SYSOUT? |
|
|
| Back to top |
|
|
sril.krishy
Active User
Joined: 30 Jul 2005
Posts: 183
Location: hyderabad
|
|
|
|
You can also try to create a file for the SYSOUT with more space.We used to follow this method whenever we will get an S722 error during the debugging phase of the programs.
Thank you
Krishy |
|
| Back to top |
|
|
Prasanthhere
Active User
Joined: 03 Aug 2005
Posts: 306
|
|
|
|
| Did u tried coding LINES=999999 in your jobcard.Actually this should resolve the error S722.Did u tried going for that option.Please let us know. |
|
| Back to top |
|
|
thirunarayanan_sampath
New User
Joined: 04 Dec 2006
Posts: 6
Location: Pune,India
|
|
|
|
Hi
I did have similar problem and it did get solved by coding
JOBPARM LINES=999999
Thanks,but can anyone brief me abt this parameter.
Regards
Thiru |
|
| Back to top |
|
|
Bharanidharan
New User
Joined: 20 Jun 2005
Posts: 86
Location: Chennai, India
|
|
|
|
| JORPARM is a JES2 command and translates as such - job parameters. LINES=999999 instructs JES2 to print literally unlimited number of lines in spool (without that, JES2 will stop the execution if spool output from any step exceeds installation default). |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
Did you look at the definition of a 722 abend. It is available in the Fine Manual linked to on this site.
| Quote: |
Explanation: One of the following output limits was exceeded:
? The output limit specified by the OUTLIM keyword on the SYSOUT DD
statement
? The job output limit specified in the LINES and CARDS parameters
of the JES2 JOBPARM statement
? The job output limit specified in the BYTES, CARDS, LINES, and
PAGES parameters on the STANDARDS initialization statement or the
JES3 MAIN statement
Source: JES
|
If you have a sort that is exceeding the spool limit, do not just increase the allowable number of output lines without understanding why.
Did you by chance sort many records and have SORTOUT defined as SYSOUT=*? Sometimes sort output is directed to sysout for testing, but if the volume is high, that is not a good choice. |
|
| Back to top |
|
|
|
|
