Re: CEA200O

There is a BMR for the CHGPRTF problem.....BMR51520, if you look on OGS
under 'CEA200%' and 'CHGPRTF' you can see it and order it via Support
Center.

Thanks,

Genyphyr Novak
SSA GT

----- Original Message -----
From: "Smith, Graham (EBM)" <Graham_SmithEBM@heinz.co.uk>
To: <BPCS-L@midrange.com>
Sent: Thursday, May 31, 2001 4:39 PM
Subject: RE: CEA200O


> Terri,
>
> we've had this problem.
>
> For some reason SSA coded the CL around the CEA200B area to perform a
> CHGPRTF rather than use an OVRPRTF.  You obviously have two jobs trying to
> use the print file and the 2nd one which is attempting the CHGPRTF cannot
> get a lock on it.
>
> I'll try and ask around here as to what we did to get around it.  I have a
> nasty feeling all we could do was ensure all CEA jobs single threaded via
> one jobq so we didn't get the contention in the first place.
>
> Cheers
> Graham
>
> > ----------
> > From:
> > THarteau@felkerbrothers.com[SMTP:THarteau@felkerbrothers.com]
> > Sent: 31 May 2001 15:00
> > To: BPCS-L@midrange.com
> > Subject: CEA200O
> >
> > Hi,
> >      Has anyone had any problems with CEA200o? We had some problems on
May
> > 24th that we didn't find out about until this week. Some labor didn't
> > post,
> > some INV transactions didn't post to GL & some reports didn't finish.
We
> > use Robot to run our night jobs, and it said everything completed
> > normally.
> > Looking back though, the programs that didn't work right all had an
error
> > message saying 'CEA200o is in use'.  We only discovered this last night,
> > and the actual logs are gone now.  Wondering if anyone else has run
across
> > this?  Thanks
> >
> > <===================================================>
> >
> > Terri Harteau
> >
> > ****************
> >
> > "I'm not sure who he is, but I get the feeling he's got his hand in a
lot
> > of things." - Kermit The Frog speaking about Jim Henson.
> >
> > ****************
> >
> >
> >
> >
> >
> > +---
> > | This is the BPCS Users Mailing List!
> > | To submit a new message, send your mail to BPCS-L@midrange.com.
> > | To subscribe to this list send email to BPCS-L-SUB@midrange.com.
> > | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
> > | Questions should be directed to the list owner: dasmussen@aol.com
> > +---
> >
>
>
> **********************************************************************
>  This email and any attachments are confidential and solely
>  for the use of the intended recipient.  They may contain
>  material protected by legal professional or other privilege.
>  If you are not the intended recipient or the person responsible
>  for delivering to the intended recipient, you are not authorised
>  to and must not disclose, copy, distribute or retain this email
>  or its attachments.  Although this email and its attachments
>  are believed to be free of any virus or other defect, it is the
>  responsibility of the recipient to ensure that they are virus free
>  and no responsibility is accepted by the company for any
>  loss or damage arising from receipt or use thereof.
>
> **********************************************************************
> +---
> | This is the BPCS Users Mailing List!
> | To submit a new message, send your mail to BPCS-L@midrange.com.
> | To subscribe to this list send email to BPCS-L-SUB@midrange.com.
> | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner: dasmussen@aol.com
> +---
>



+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---