Re: compile causes run-a-way jobs

I think it would be reasonable to say that we have run a fair number of 
compile through our V5R2 machine and have not experienced this problem.

Any time that this would have happened I would have immediately on the 
phone with IBM.  Granted, we have a support line contract.

(You did expect these stock questions, didn't you?)     :-)
Do a DSPPTF and list the first one that appears.  Mine isTL03077.
Do a WRKPTFGRP and display that.  Mine looks like:
PTF Group             Level  Status 
SF99519                  47  Installed
SF99502                   6  Installed
SF99271                   7  Installed
SF99190                  10  Installed
SF99169                   8  Installed
SF99149                   3  Installed
SF99148                   3  Installed
SF99098                   8  Installed
SF99085                   3  Installed
SF99039                   2  Installed

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 




MWalter@xxxxxxxxxxxxxxx
Sent by: midrange-l-bounces@xxxxxxxxxxxx
04/29/2003 08:57 AM
Please respond to Midrange Systems Technical Discussion
 
        To:     midrange-l@xxxxxxxxxxxx
        cc: 
        Fax to: 
        Subject:        compile causes run-a-way jobs


Good morning,

I submitted a compile (CRTBNDRPG)  this morning for a seemingly benign
program, but the compile just runs away. It consumes most of the cpu, and
cannot be ended. The last time I submitted it, I had to force the entire
system down and IPL. What is happening here? We are at V5R2.

Thanks,

Mark

Mark D. Walter
Senior Programmer/Analyst
CCX, Inc.
mwalter@xxxxxxxxxx
http://www.ccxinc.com

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.