Upgrade to LSF 9.0.0.9-need help huge production problem

Are all of those programs compiled correctly? 

What version are the LP programs compared to other programs such as HR, Procurement and Financials? Are you licensed for the LP programs?

Does the problem happen both in LID and Portal?

Do other jobs/reports run OK?

I'm sure if you've got both Lawson and Velocity on it, some solution will come forth soon.

Thank you for the information.

Yes, Velocity recompiled all programs. All jobs run okay, except for LP100, LP130,LP140 and PR135. The problem does occur in both LID and Portal.

Below is the summary from Velocity of all that has been done thus far:
This issue started after ESP 9 was applied for LSF900. It is duplicated in all product lines (DEV & TEST in the dev. environment and PROD in the production environment). It is affecting the production payroll, which has already been established. We have recompiled the programs, product line, recycled the environment, and last night recycled the entire server (which included PROD and DEV Lawson, DB and LDAP). We are processing the jobs through LID, so the Websphere application servers should not come into play.

What platform are you on?
Do you have errors in lajs.log or ladb.log?
When you upgraded, did you recompile BSI tax factory?

Thank you John for replying.

We are on AIX. I am not sure if they recompiled Tax Factory....but I will ask Velocity immediately.

As for the lajs.log or ladb.log errors....
Tue Jun 28 20:54:26 2011: Received Death Notification, Pid=967140
Tue Jun 28 20:54:26 2011: execjob Process Died, Pid=967140
Tue Jun 28 20:54:26 2011: WARNING: Running Job Removed From Running Queue.
Tue Jun 28 20:54:26 2011: Job Log Process Id Should Be Checked For Defunct Or Orphaned Process.
Tue Jun 28 20:54:26 2011: User Name = z925229, Job Name = PR135.OOOO, Job Number = 0000000151


No ladb errors.

Thanks so much!

If it's only those specific jobs which are bombing out, can you create *new* versions of the those jobs and see if those new versions will run?

What do you see in the 'examine log' for one of those failed jobs?
Are they listed in job scheduler as 'needs recovery' or as 'completed"

Roger....Yes, our IT person created a copy of the PR135 in TEST and it ran.....but she is scared to do the same to the LP update jobs.  She is sharing that information with Lawson to see if that helps to resolve the problem.

Thanks for replying!

John...The jobs are listed as "needs recovery" in the job scheduler.

Thanks for replying!

What I would try at this point:

In the TEST productline, I would pgmdump on PR135, save off the PR135 source code files, and then remove the program in pgmdef. Then I would copy the PR135 source back in the the /prsrc directory and run the pgmload on the PR135. Just something I would try. Jeff

Jeff -

Thank you....I am passing your suggestion on to the IT staff now.

Thank you again!

What do you see in the 'examine log' ??

Hi John....I will find out what is in the "examine log".

I can overhear the IT group and Lawson are on a Webex together. It sounds as if Lawson can see the reports behind the scenes but the User only sees the job ending in error in the Job Scheduler.....no output in the Print Manager.

I should have asked one of the IT guys to open post this question on Guru, so that we could respond quicker. I am a Functional Consultant working at this client on another project....When I heard that they upgraded their production environment and these errors popped up, I went into panic mode and tried to help by posting on Guru.

Thank you so much! I will check on the "examine log".

Ok guys....

Here is an update on our emergency. Lawson found the problem....something was wrong with a PR135.cfg file. They removed it and the jobs ran....but when they put the config file back it broke the jobs. Lawson is going to give us new config files.

As a functional person, I am not sure I understand this.....but I know all of you will understand. I am just glad they finally found a resolution.

MANY THANKS to all you that replied to my question .

Have a great evening!
Kay