E1: PKG: How To Stop A Server Package Deployment - AS400 iSeries Platform (Doc ID 639263.1)

Last updated on JULY 17, 2017

Applies to:

JD Edwards EnterpriseOne Tools - Version SP23 and Prior and later
Information in this document applies to any platform.



Goal

Customer wants to know how to delete deployment record of a deployed server package to their AS400 server to take MUTEX off of the jobs running on their AS/400 (OS400 -V5R2).
Customer is having problem with processes stopping or delay because of the deployment record. JDE recommendation's are to deploy packages during off-hours, but client is a 24x7 shop, so doesn't have down times to deploy the packages. So, when a long-running job is processing when the package is deployed, all jobs are put to a wait status until the job completes and the package deploy is completed.

When you submit the job to deploy the package to the enterprise server a request is sent to the enterprise sever to allow all currently running jobs to run until completion. Any new jobs to be run will be set on the AS400 in a Mutex wait status. After all running jobs are completed the paktotam occurs. After completion of the paktotam the waiting jobs are released from the mutex wait status. System is then back to normal.

CLIENT SCENARIO:
A job was running on the AS400 that ended up running 11 hours, it was started at 8:45 AM and completed at 7:55 PM. At approx 3:00 PM I deployed the enterprise package, all jobs running continued as normal. All new jobs were placed in a Mutex wait status. For the next 4 hours nothing else was processing until the long running job is completed. All of our night time jobs kicked off but sat in a wait status. I canceled the deployment on the workstation, but the AS400 stayed in Mutex wait. How can I cancel the deployment once the request was sent to the AS400?

The only solution I found was to cancel the long running job and then the deployment occurred and all jobs continued as normal. How can I cancel the deployment on the AS400 without ending the long running job? I realize the solution would be not to have long running jobs, but in a production environment we need to be able to decide if we can cancel the long running job and If we can not cancel the long running job then we need to be able to cancel the deployment.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms