RE: RE: ECM -- BPCS-L

he guid is generated  by the application - when an inbound PO comes in a
guid is assigned in EDI - when ASN's come from the application, the guid is
assigned in the ASN generation programs. I don't remember all of the
details, but the guid is built (for us) based upon the date, the time and a
sequential number from a data area. It has to be unique for ECM to work
properly.

A TPEC is created by an external request - your PO 850 EDI maps should
create a TPEC; 

once a record is accepted for processing and errors out, the TPEB should be
there. you should have tpebs for all of your internal requests (the trading
partners in error).

Help is available through SSA's OGS - the ECM help guide is decent at
explaining more and I'm sure much better than I'm trying to do.

> sage-----rom: Jesse Salazar [SMTP:jesse.salazar@trin.net]
> Sent: Friday, April 06, 2001 7:43 AM
> To:   BPCS-L@midrange.com
> Subject:      Re: RE: ECM
> 
> You have been extremely helpful!
> 
> A couple more questions:
> 
>        1.)  Whiat is the GUID?
> 
>        2.)  TPEC & TPEB are both empty.  How are they updated?
> 
> Thanks!!
> 
> >>> Steve Segerstrom <SSegerstrom@intermatic.com> 04/05 3:59 PM >>>
> Is the subsystem active or is it taking the subsystem down?
> 
> We have run into situations where there was an endsbs command "stuck" in a
> jobque. I deleted it, brought the subsystem up and we we're up and running
> again.
> 
> Generally the problems we have here are ECM looping not running - but this
> may help. Look at the external requests, in file TPEC. Process flag should
> be set to 0 - there should be a bunch. If there are none, there are no
> external requests and the job process internal requests. Internal requests
> are stored on file  tpeb.
> 
> Do a dsppfm on TPEB.  After the partner number you will see a 5 with a
> "Z",
> or "0" or "4" or "2".  The TPEB that has a "2" is the one that ECM is (or
> was) looping on.  If it is still running, you may want to monitor the
> record
> for a few minutes to make sure it really is looping.  If it sits there in
> a
> status "2" for say, 5 minutes, it's probably looping.  Another way we look
> at it is to do a wrkactjob and look at the call stack.  If it keeps saying
> "Get Key" over and over, that means it's looping.  You will have to kill
> the
> job.
> 
> Next, look at your GUIDs in TPEB.  You are looking for duplicates. These
> usually are attached to ECM605B3 and/or ECM605B2.  Those are the records
> to
> delete.  There may be more than one set of duplicates, or triplicates.
> Once
> you have deleted those, you will need to go into 54 (Control Center) and
> reset whatever is active. You do this by putting in a "13".  (It will ask
> if
> you're sure.)
> 
> Anyway, you should have a bunch of tpebs that have a status of 0. If there
> are no tpecs or tpebs with status of 0; ECM has nothing to process.
> 
> 
> 
> > -----Original Message-----
> > From:       Jesse Salazar Jr., CSP [SMTP:Jesse.Salazar@trin.net] 
> > Sent:       Thursday, April 05, 2001 3:16 PM
> > To: bpcs-l@midrange.com 
> > Subject:    ECM
> > 
> > Thank you to those who replied on my earlier message regarding ECM.
> > 
> > Unfortunately, I still cannot get ECC/ECM to stay active.  Below is the
> > Notification Log messages
> > 
> > Any suggestions?
> > 
> > Thanks.
> >
> 
> >  ECA
> > 
> >  Text       Trading Partner Type Rst/Rvd  Date      Time       Incident
> #
> > 
> >  
> > 
> >  ECM607     608423            E     0      4/05/01   15:11:42  7883380
> > 
> >  No configuration for this ECA/Trading Partner.
> > 
> >  ECM607     608423            E     0      4/05/01   15:11:41  7883379
> > 
> >  No configuration for this ECA/Trading Partner.
> > 
> >  ECM607     608423            E     0      4/05/01   15:11:41  7883378
> > 
> >  No configuration for this ECA/Trading Partner.
> > 
> >  ECM607     608423            E     0      4/05/01   15:11:41  7883377
> > 
> >  No configuration for this ECA/Trading Partner.
> > 
> >  ECM607     608423            E     0      4/05/01   15:11:41  7883376
> > 
> >  No configuration for this ECA/Trading Partner.
> > 
> >  ECM607     608423            E     0      4/05/01   15:11:41  7883375
> > 
> >  No configuration for this ECA/Trading Partner.
> > +
> >  
> > 
> > Help  F3=Exit  F5=Refresh  F7=Backward  F8=Forward  F13=Filters
> > 
> > Jesse Salazar Jr., CSP
> > Certified Systems Professional
> > 
> > Senior Programmer/Analyst
> > EDI Services Coordinator 
> > 
> > 
> > 
> > 
> +---
> | 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
> +---
+---
| 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
+---