Re: An old 'mystery job'

[Jim Oberholtzer <midrangel@xxxxxxxxxx>]

That's a good idea I had not thought of!  I am convinced that the job 
table is the issue, but the question was what to do about it.

Jim Oberholtzer
CEO/Chief Technical Architect
Agile Technology Architects, LLC


On 1/3/2011 4:35 PM, Chris Bipes wrote:
> You may have to set your IPL Attributes, CHGIPLA, to check and compress
> the job tables.  I do not think the RCLSTG will help but it won't hurt.
>
> -- Chris Bipes Director of Information Services CrossCheck, Inc. 
> -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx 
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of DrFranken Sent: 
> Monday, January 03, 2011 2:08 PM To: Midrange Systems Technical 
> Discussion Subject: An old 'mystery job' Trying to determine 'What Up' 
> with a badly behaving string of twinax devices connected with Cat3 and 
> a passive hub. I used WRKJOB using the device name of each device on 
> the string to see if there were any recent jobs on the devices in 
> order to disconnect unused cables. Since this shop keeps joblogs 
> around for two weeks it's a reasonably effective test. It worked well 
> except for one device DSP020604. On this device WRKJOB DSP020604 came 
> up with only one job, no biggie as it's been a holiday and one job 
> does in fact mean the device is still used. Or does it? The job is 
> dated 10/29/2005 and it's status is *OUTQ. OK that's a long time ago 
> so let's just see what output it has waiting. So I check WRKJOB option 
> 4 and, there is nothing there! Has anyone seen this? A job still in 
> the system through more than 5 years dozens of IPLs an O/S Upgrade (to 
> V454) with no spooled files. I'm afraid a RCLSTG may be in our future 
> here....