Next Number Issue

Soumen

Soumen

Reputable Poster
Hello,

We have been facing sporadic issues with Next Numbers failures in our JDE Xe setup. The issue appears while Order Entry and is normally a show stopper. The issue gets resolved when we delete some jobs from submitted jobs (WSJ). At the same time we get the errors (as menioned below) in the job logs. The issue is not consistant and happens anytime within the week.

We also checked the PRINTQUEUE archiving process and as a measure changed the retaining period of the Member files from 15 days to 10days. But still we are getting the errors, after chaging the settings. Our printqueue archiving job is running as a scheduled (RPG) night job.

Configuration of our system is ..

JDE Application Release: Xe
Tools Release: SP23_K1
Application Server: AS400 (V5R3)

Also the issue started suddenly during mid of september. We did not have any changes during that time related to Security, Patches, or any configuration changes.

Ironically, our night jobs had failed a couple of times (again intermittent) during these periods.

Can you please suggest some solutions to this problem.
Any help will be much appreciated.

Many Thanks,
Soumen

========================
Error reported in logs..

27277 Thu Oct 15 07:42:16 2009 k2pdfutils.c3080
ADDPFM error, after 10 tries couldn't add FILE(B73SPSYS/PRINTQUEUE) MBR(F5434757)
27277 Thu Oct 15 07:42:16 2009 k2pdfutils.c3080
ADDPFM error, after 10 tries couldn't add FILE(B73SPSYS/PRINTQUEUE) MBR(F5434757)
27277 Thu Oct 15 07:42:16 2009 k2pdfutils.c3080
ADDPFM error, after 10 tries couldn't add FILE(B73SPSYS/PRINTQUEUE) MBR(F5434757)
27277 Thu Oct 15 07:42:16 2009 k2pdfutils.c3080
ADDPFM error, after 10 tries couldn't add FILE(B73SPSYS/PRINTQUEUE) MBR(F5434757)
 
It could be you've maxed the max members allowed for a PF (DSPFD and search for MAXMBRS).

We also had issue with this table when it had too many members and one of the programmers wrote a CL program that cleans up that table every week based on creation date. The downfall is that you're deleting PDF files indiscriminately.
 
Thanks for the response!

I have checked the DSPFD for PRINTQUEUE physical file and all it's members and found the setting for MAXMBRS to be set as *NOMAX. (Attached is the screen shot). Does that mean we can add any amount of files under our PrintQueue file.

We are currently cleaning the members on a regular basis (retention period is 10 days), Do you think reducing the retenstion time (from say 10 to 8) will help with the issue.

Once more thing to add is that the file mentioned in the error log is not the only file which throws error. There are different files at different time and is not specific to this particular file F5434757 only.

Any help with this will be highly appreciated.

Many Thanks,
Soumen
 

Attachments

  • 152131-DSPFD.doc
    171.5 KB · Views: 97
Hi
In Xe there is a limit of 32K entries in the WSJ table. It sounds to me that you are continually reaching this limit. I expect you could see how many batches you are running each day and then use that to work out how many days to retain
 
The max number of members you can have in the Printqueue physical file is 32767. Another reason for the errors is that the Printqueue file could be locked. I would check to make sure your purge program is not locking it.
 
As a follow-on. If you are using DSPFD to list member to an output file, the file is 'locked' until the list is generated, This can cause issues of it's own.

Tom
 
Thanks for the inputs...

We are keeping a close watch on the Printqueue member files count. In the meantime, is there a upper limit on the Job Control Master table (F986110). Does this table also needs purging from time to time?

Thanks again..
Soumen
 
Well ...

We faced the issue again today .. and this time the count of members on PrintQueue file was not even near to 32K. KIt was around 16K also there was no locks on the PrintQueue, since our purging jobs runs at night...

Can this issue be related to someting else apart from PrintQueue? Any ideas will help a lot ..

Thanks as always..

Soumen
 
Hi There,
Am facing the same kind of problem. The 'Next number Failed' Occurs and cause damage to all the dependent programs (P4210 and subsystem jobs and rest).

Please let me know you got any fix or work around or any clue.

Server : AS400
E1 Version : 8.12
Tools release : 8.98

Thnaks in Advance.
 
Hello Ramesh/and All,

Sorry the delayed response.

We evnetually found the cause for the Next Number Failure. This went to the Journaling that was in place for the IFS files. Actually we have a cusotomised FTP tool in our system which archives a lot of flat files into the IFS folder. This IFS folder was being Journaled and since there was no clean up for a long time, the amount of file that were getting Journaled (mind you it was not the space, but the amount of file that were getting Journaled) was crossing the limit of 250.000 mark, resulting in the Next Number failure. Once we cleared all the old files the issue got resolved and our system is now running fine !!! (touch wood) ;-)

Hope this helps.

ciao,
soumen
 
Back
Top