Re: SRC B900 3610

["Keith Carpenter" <CarpCon@xxxxxxx>]

If that doesn't work, you can take the more drastic "Clear job queues" and
"clear output queues" at the "IPL Options" screen (manual IPL).  You'll lose
your reports which I suspect was cause of the problem (too many completed
jobs).

Anyone know what the maximum number of jobs (queued,active,completed) is ?


----- Original Message ----- 
From: "DeLong, Eric" <EDeLong@xxxxxxxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
Sent: Friday, October 10, 2003 7:47 AM
Subject: RE: SRC B900 3610


> Albert,
>
> You can compress the job tables during IPL by changing CHGIPLA attribute
> CPRJOBTBL.  Do DSPJOBTBL to see the current status....
>
> Eric DeLong
> Sally Beauty Company
> MIS-Project Manager (BSG)
> 940-898-7863 or ext. 1863
>
>
>
> -----Original Message-----
> From: York, Albert [mailto:albert.york@xxxxxxxxxxxxxx]
> Sent: Friday, October 10, 2003 9:37 AM
> To: 'Midrange Systems Technical Discussion'
> Subject: RE: SRC B900 3610
>
>
> Thanks Scott.
>
> Do you know how to fix it? Will reducing the number of jobs on the system
> help (assuming I can get signed on).
>
>
> Albert York
>
> -----Original Message-----
> From: Ingvaldson, Scott [SMTP:SIngvaldson@xxxxxxxxxxxx]
> Sent: Friday, October 10, 2003 7:25 AM
> To: 'midrange-l@xxxxxxxxxxxx'
> Subject: RE: SRC B900 3610
>
> srcB9003610 = the system is out of job table entries
>
> Regards,
>
> Scott Ingvaldson
> AS/400 System Administrator
> GuideOne Insurance Group
>
> -----Original Message-----
> date: Thu, 9 Oct 2003 15:57:35 -0700
> from: "York, Albert" <albert.york@xxxxxxxxxxxxxx>
> subject: SRC B900 3610
>
> Can anyone tell me what SRC B900 3610 means or where I can find it?
>
> Thanks,
>
> Albert York
>
> This message and accompanying documents are covered by the
> Electronic
> Communications Privacy Act, 18 U.S.C. §§ 2510-2521, and contains
> information
> intended for the specified individual(s) only. This information is
> confidential. If you are not the intended recipient or an agent
> responsible
> for delivering it to the intended recipient, you are hereby notified
> that
> you have received this document in error and that any review,
> dissemination,
> copying, or the taking of any action based on the contents of this
> information is strictly prohibited. If you have received this
> communication
> in error, please notify us immediately by e-mail, and delete the
> original
> message.
>
> _______________________________________________
> 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/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.
>
> _______________________________________________
> 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/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.
>
>
>
> _______________________________________________
> 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/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.
>
>