There are parms in the ECA setup for this.
There are 2 jobs/ECAs ... the Collection Control Manager and the Dispatch
Manager ... both have entries in the ECA option of the ECM menu. For each
one take option 15 (parameters).
From the documentation ...
If the LPFCTTIME parameter is present and contains a value other than
000000, the Collection Control Manager goes to sleep until that time. If
the time held in this parameter is later than the current time at the end
of the previous processing cycle, processing is delayed until the next day
at the specified time. When this scheduling condition is true, the
Collection Control Manager does not look at the number of loops specified,
but continues to cycle until some other process stops the Collection
Control Manager.
If the above condition is not true, and the LPFCTSEC parameter is greater
than 000000 and the LPFCTLOOP parameter is equal to 000000, the Collection
Control Manager goes to sleep for the specified number of seconds at the
end of each processing cycle. When this scheduling condition is true the
Collection Control Manager does not look at the number of loops specified,
but continues to cycle until some other process stops the Collection
Control Manager.
If the above conditions are not true, and the LPFCTSEC parameter is
greater
than 000000 and the LPFCTLOOP parameter is greater than 000000, the
Collection Control Manager goes to sleep for the specified number of
seconds at the end of each processing cycle, At the end of each cycle, the
Collection Control Manager subtracts 1 from the number of cycles specified
when the Collection Control Manager started. When the number of cycles
reaches 0, the Collection Control Manager ends.
When none of the above conditions are true, the Collection Control Manager
does not cycle and discontinues further processing.
The LPFCTLOOP parameter is evaluated when the Collection Control Manager
is
started. The LPFCTSEC and LPFCTTIME parameters are re-evaluated at the end
of each processing cycle. Therefore it is possible to adjust these two
parameters without ending the Collection Control Manager processing. This
should only be done while the Collection Control Manager is asleep and
there is no chance that the Collection Control Manager processing could
continue while the record is being maintained. 0 to 999999
___________
Karyn Young
Information Management Consultants, Inc.
kyoung@xxxxxxxxxx
office 812.421.0045 ext 204
cell 812.205.5200
From:
Norman.Boyd@xxxxxxxxxxxxxxxxx
To:
BPCS ERP System <bpcs-l@xxxxxxxxxxxx>
Date:
04/15/2010 06:47 AM
Subject:
Re: [BPCS-L] BPCS ECM Question
Sent by:
bpcs-l-bounces+jdyer=imcedi.com@xxxxxxxxxxxx
Rob,
This may or may not be the case. Check your Robot job to see if someone
entered parameters there to end the job IF it is running after a certain
amount of time.
Good luck.
Norman K. Boyd
MIS Administrator
Showa Aluminum Corp. of America
CONFIDENTIALITY NOTICE: This e-mail message is intended only for the
person or entity to which it is addressed and may contain confidential
and/or privileged material. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
message. If you are the intended recipient but do not wish to receive
communications via email, please advise the sender immediately.
Re: [BPCS-L] BPCS ECM Question
SKumaran
to:
BPCS ERP System
04/14/2010 04:10 PM
Sent by:
bpcs-l-bounces+norman.boyd=showaaluminum.com@xxxxxxxxxxxx
Please respond to BPCS ERP System
Rob,
ECM (Electronic Commerce Manager) which brings in our customer orders to
BPCS via EDI ( Electronic Data Interchange).
We have the ECM startup jobs in ROBOT but the problem is that it ends
itself after 480 minutes. The job log does not show errors.
There should be a parameter some where in BPCS ECM files that is set with
a timer to end the jobs.
Thanks
Suresh
midrange.com
