Subsystem Processing issue

Hi List,

I'm hoping someone can help me with this issue.

We run 12 subsystem jobs for 12 separate divisions for printing invoices. We have separate versions of R42565 that are started automatically after a reboot through the a batch file that submits the 12 versions to run with RUNUBE on our application server. These versions allow the divisions to print 2 copies of invoices.

When a full build/deployment is completed 1 subsystem job will not print 2 the copies. Somehow the first job gets corrupted after a full build/deployment. We’ve switched the order of when the jobs get submitted from the startup batch file and it only seems to be the first one submitted that won’t print the 2 copies. We can restart the subsystem jobs and it still won’t work. The only fix is to build an update package with all the versions of R42565, stop the subsystem jobs, deploy the update and restart the jobs. We’ve moved the order of the list and it’s always the first one. Also the version of the UBE works but it just stops printing 2 copies.

This only started happening when we added the 12th subsystem job. We do full package builds and deployments weekly and it doesn't happen every week but most weeks.

Any help would be gladly appreciated.

thanks,
Kevin
ERP8, SP23_F1

First of all, it sounds like something "fishy" is going on with your version. If a version is giving you trouble (and its the same version) - then I always recommend deleting the version COMPLETELY and adding the version back into the system from scratch. That always seems to fix the issue.

Make sure there are no weird User Overrides for your batch process. You should be able to delete those.

A full package should be BETTER than an update package - so your statement that its more reliable after the update package is very strange. Either it should work after the full package or not.

Secondly, make sure you secure down your versions. Don't allow users to launch versions that a server might launch as part of a process or as part of a schedule - keep them separate.

Hi Jon,

Thanks for the quick response. We thought the same thing about it being fishy. We ended up trying the deletion of the version and recreate a brand new one. We changed the order of how the versions are started and it seems like the first one in the list will experience the same behavior.

I'm with you on the thoughts of the full builds being better that the updates. This is why it stumps me. I tend to expect these types of issues with updates rather that fulls.

We don't have any User Overrides for this batch process.

We typically will not give the user the same UBE version as the subsystem but we do give them another version for doing invoice reprints.

We don't see this after the weekly reboot only when we reboot after the latest package.

Thanks,
Kevin

Do you have web users ?

Yes, on WebSphere 5.0.2



_____

From: [email protected] [mailto:[email protected]] On
Behalf Of altquark
Sent: Monday, April 09, 2007 2:36 PM
To: [email protected]
Subject: Re: Subsystem Processing issue



Do you have web users ?

Jon Steel EnterpriseOne Technical Specialist erpSOURCING LLC
http://www.erpsourcing.com [email protected] 24/7 Assistance - (904) 382 5701

_____


The entire <http://www.jdelist.com/ubb/showflat.php?Cat=&Board=> JDELIST
thread is available for viewing.


Looking for a job? Check out the Job
forum


This is the JDELIST EnterpriseOne Mailing List.
JDELIST is not affiliated with JDEdwardsR.

To unsubscribe from this list via email, Click
<mailto: [email protected]?Subject=Unsubscribe&Body=Sirs,

Pl
ease remove this address from the JDELIST EnterpriseOne M

Re: RE: Subsystem Processing issue

ah. Then are you bouncing your web clients after the update package ? I think the web clients are caching the version information ! Each time you deploy anything to the web, you need to restart your web services to ensure the cache is deleted.

Re: RE: Subsystem Processing issue

Hi Jon,

Yes we do have web servers (not sure why someone else was answering that question for me) and we always bounce the web servers after we bounce the application servers.

Here's a question...could there be something with submitting the UBE's by the batch file? It's just a normal file that has a list of RUNUBE commands and it's started when the server gets rebooted.

Also, does 12 subsystem jobs sound like a lot? Could I be missing something from a subsystem side of things like from a maintenance or routine side? As you can see I'm grasping here...

thanks,
Kevin

Re: RE: Subsystem Processing issue

Kevin,
If its not related to CNC then check the UBE and C function if its doing the job correctly. since its subsystem ube submission you must have customised C function to which you need to pass call the parameters. there are chances that the first function call might not be happening correctly due to variables not initialised correctly.

my 2 cents.

Re: RE: Subsystem Processing issue

Hi Chan,

Thanks for the input. I'll take any ideas that might point me in the right direction.

I talked to our applications people and they said that the C BSFN wasn't customized and to turn on subsystem processing for that UBE we just needed to select the check box for subsystem processing in the design. We are on Intel/SQL so I'm not sure if AS/400 handles this a little different.

thanks,
Kevin

Re: RE: Subsystem Processing issue

Kevin,

Where are you building the full from? If you are running it from the DEP environment on the Deployment Server, maybe it has something to do with all the specs being jiti'd when all the versions are launched the first time...

This is a bit of a stretch, but stranger things have happened....

Matthew

Re: RE: Subsystem Processing issue

Hi Matthew,

We have a package build workstation for all builds. But thanks for the idea. Like I said before...I'm open to ideas.

The past 2 weeks all the subsystem jobs work fine and we haven't made any changes to the versions. I'm confused by this.

I think I might just deal with the issue when it happens. The fix seems to be an update package. So I'll continue doing that.

Thanks for all the responses. If I find a solution for some reason I'll post it.

Thanks again,
Kevin

Re: RE: Subsystem Processing issue

Hi, have you found a solution to this aside from building an update package?

We have a similar situation with submitting jobs through a batch file with the RUNUBE command. I'm not sure if it's the same as your or not but let me explain.

We have a process that execute a batch file which submits about 7 UBEs to run on the enterprise server. Monday-Thursday, everything works great. Friday nights, after we build a full package and deploy it, the first UBE in that list of UBE fails. We still cannot figure out the actual problem so what we did was to include a small UBE (R0006P) in our list of UBEs to be submitted. As expected the first UBE (R0006P) does not run successfully but the rest of the UBEs run as expected.