gholden
Member
We are having a difficult time managing the enormous number and size of PDF's from OW. We haven't been successful in locating any tools to effectively age and delete the Outq's. Any suggestions?
Thanks....
Thanks....
WWells
Active Member
One thing we discovered, was to be sure to do it within OW.
If you decide to start deleting stuff from the Printqueue directory
then go back into OW and try to view print files, you can't, and sometimes
you wind up with orphan entries that may require SQL to clean up.
If you decide to start deleting stuff from the Printqueue directory
then go back into OW and try to view print files, you can't, and sometimes
you wind up with orphan entries that may require SQL to clean up.
MSiebenschuh
Well Known Member
Gary,
On the server side I have just created a regular UNIX script to
delete any job over X days old. It deletes the PDF and the record in the Job
Master. It is scheduled to run every night. I think there is even a UBE to
this if you search the archives. ( I just keep my script because I know it
works ). On the client side we just delete all the jobs in the PrintQueue
directory on all the Citrix servers every week. No big deal here because
when they go to view a job it will just get pulled from the server. Seems
like this should work for any config.
Mark Siebenschuh
HP9000/Oracle 8.0.5/B733 Base Distribution/XE Financials
On the server side I have just created a regular UNIX script to
delete any job over X days old. It deletes the PDF and the record in the Job
Master. It is scheduled to run every night. I think there is even a UBE to
this if you search the archives. ( I just keep my script because I know it
works ). On the client side we just delete all the jobs in the PrintQueue
directory on all the Citrix servers every week. No big deal here because
when they go to view a job it will just get pulled from the server. Seems
like this should work for any config.
Mark Siebenschuh
HP9000/Oracle 8.0.5/B733 Base Distribution/XE Financials
tbrandley
Member
There is a UBE R9861101 which drives another UBE R9861102 that allows you to
purge the Job Control Status Master table F986110 and delete the pdf files
from the server's printqueue directory (at least on NT). You need to modify
the proccessing options to define your servermap datasource and number of
days old that you want to purge. A note of caution: if you're at pre-Xe
release, you will need to run this ube locally because it will fail when you
submit it to the server (see SARS 4064853 and 2685496).
Hope this helps
Tim Brandley
QNX Software Systems Ltd., Canada
B73.3.2, NT, SQL7.0, SP11.3
WTS W2K
purge the Job Control Status Master table F986110 and delete the pdf files
from the server's printqueue directory (at least on NT). You need to modify
the proccessing options to define your servermap datasource and number of
days old that you want to purge. A note of caution: if you're at pre-Xe
release, you will need to run this ube locally because it will fail when you
submit it to the server (see SARS 4064853 and 2685496).
Hope this helps
Tim Brandley
QNX Software Systems Ltd., Canada
B73.3.2, NT, SQL7.0, SP11.3
WTS W2K
sgallaher
Member
We've had the same problem here... our enterprise server is an AS400 and
twice already we've hit the maximum number of members in the PRINTQUEUE
file (32,766). I ended up writing a CL program to clean up my PRINTQUEUE
file of anything older than 30 days. I also wrote something similar to
clean the WSJ file so users wouldn't get an error when they tried to view
an old report.
-Scott
B7332, SP13.1_CACHE, AS400 CO & ES, TSE w/ Citrix
"Wells, Wade"
<WWells@futurenex To: "'[email protected]'" <[email protected]>,
t.com> [email protected]
Sent by: cc:
owner-jdelistml@j Subject: RE: Outq Managment
delist.com
05/11/01 08:30 AM
Please respond to
jdelist
One thing we discovered, was to be sure to do it within OW.
If you decide to start deleting stuff from the Printqueue directory
then go back into OW and try to view print files, you can't, and sometimes
you wind up with orphan entries that may require SQL to clean up.
twice already we've hit the maximum number of members in the PRINTQUEUE
file (32,766). I ended up writing a CL program to clean up my PRINTQUEUE
file of anything older than 30 days. I also wrote something similar to
clean the WSJ file so users wouldn't get an error when they tried to view
an old report.
-Scott
B7332, SP13.1_CACHE, AS400 CO & ES, TSE w/ Citrix
"Wells, Wade"
<WWells@futurenex To: "'[email protected]'" <[email protected]>,
t.com> [email protected]
Sent by: cc:
owner-jdelistml@j Subject: RE: Outq Managment
delist.com
05/11/01 08:30 AM
Please respond to
jdelist
One thing we discovered, was to be sure to do it within OW.
If you decide to start deleting stuff from the Printqueue directory
then go back into OW and try to view print files, you can't, and sometimes
you wind up with orphan entries that may require SQL to clean up.
Solack
Active Member
Re: RE: Outq Managment
can you email me the cl program to purge from enterprise server?
I just looked at our printqueue and there are 24,000+ members.
[email protected]
Ed Solack
OW-XE SP13.1/ES-As400/DEP-Nt4.0 Sql7.0/Citrix TS
can you email me the cl program to purge from enterprise server?
I just looked at our printqueue and there are 24,000+ members.
[email protected]
Ed Solack
OW-XE SP13.1/ES-As400/DEP-Nt4.0 Sql7.0/Citrix TS
Toni_Nanneman
Active Member
RE: RE: Outq Managment
You can run R01131P with date parameters to clear out the printqueue file.
B7322 SP12.2; NT; SQL 6.5; coexist on AS/400 with A73 cum 8
You can run R01131P with date parameters to clear out the printqueue file.
B7322 SP12.2; NT; SQL 6.5; coexist on AS/400 with A73 cum 8
dschlieder
Well Known Member
Re: RE: RE: Outq Managment
Toni,
I do not believe that R01131P will touch the printqueue file. It deletes messages from the workcenter only. I run 2 versions of this UBE every week, one to delete all "deleted" messages and one to delete all messages older than 7 days. But this has nothing to do with submitted jobs, their logs, or the PDF files they create.
I also spend considerable time cleaning up the submitted jobs, their logs, or the PDF files they create for jobs older than 2 weeks and they still exist after running R01131P.
Dave Schlieder
Toni,
I do not believe that R01131P will touch the printqueue file. It deletes messages from the workcenter only. I run 2 versions of this UBE every week, one to delete all "deleted" messages and one to delete all messages older than 7 days. But this has nothing to do with submitted jobs, their logs, or the PDF files they create.
I also spend considerable time cleaning up the submitted jobs, their logs, or the PDF files they create for jobs older than 2 weeks and they still exist after running R01131P.
Dave Schlieder
dschlieder
Well Known Member
Re: RE: Outq Managment
Ed,
Funny you should resurrect this thread now! I just finished sitting down with our operations manager of the AS/400 and showed him how to clean up the printqueue!
A little background. When we updated to SP 15, we started having an issue with random UBEs ending in an error with a "Object label badly formatted" message in the job log. After going round and round with tech support, they finally suggested that we add to our INI file "UBEUSEAdobe=1". Well, that solved our problem. However a few weeks later I noticed that the number of members of our printqueue on our AS/400 was not decreasing when I deleted jobs from the OW Work With Servers screen! It always did before. Standard JDE, fix one issue, create another. So back to tech support. Yes, they could duplicate it and issued SAR 5293703 for SP 16.1, but in the meantime I needed a solution as we run well over 2,000 UBEs a week (We may not update to SP 16.1 for months yet). And the only way I had at the time was manually from the green screen, typing in 4s. So I wrote this CL (Hope you can read it from this post):
*************** Beginning of data **************************************
PGM PARM(&STRDATE)
DCL VAR(&STRDATE) TYPE(*CHAR) LEN(6)
DCL VAR(&SELECT) TYPE(*CHAR) LEN(50)
DCLF FILE(QGPL/PQDOIT)
CHGVAR VAR(&SELECT) VALUE('MLCDAT *LE ' || '''' || +
&STRDATE || '''')
DSPFD FILE(B7332SYS/PRINTQUEUE) TYPE(*MBRLIST) +
OUTPUT(*OUTFILE) OUTFILE(QGPL/PQPURGE)
OPNQRYF FILE((QGPL/PQPURGE)) QRYSLT(&SELECT)
CPYFRMQRYF FROMOPNID(PQPURGE) TOFILE(QGPL/PQDOIT) +
MBROPT(*REPLACE) CRTFILE(*YES)
CLOF OPNID(PQPURGE)
RUNQRY QRY(QGPL/PQDOIT)
LOOP: RCVF
MONMSG MSGID(CPF0864) EXEC(GOTO CMDLBL(END))
SBMJOB CMD(RMVM FILE(B7332SYS/PRINTQUEUE) +
MBR(&MLNAME)) JOBQ(QGPL/QBATCH)
GOTO CMDLBL(LOOP)
END: ENDPGM
****************** End of data *****************************************
The query is pretty straight forward. Based on the file created from the DSPF command, it selects out the members older than the date passed in. BEWARE: THERE IS NO ERROR CHECKING! The date format is 'YYMMDD' and needs single quotes around it to work. So today is PARM('010725'). If you inadvertently typed in '072501', 'MMDDYY' format, it would delete EVERY member of the printqueue. SO USE WITH CARE!
I also find it necessary to clean up 2 other areas.
The Integrated File System is where the job and job debug logs are kept. These are often times orphaned when deleting jobs from OW and there are logs in there from the kernals which you will never see in the submitted job search screen. So I use Windows Explorer to select out all old logs from there to delete after deleting jobs from OW.
I also review all the output queues (WRKOUTQ) on the AS/400 - our QPRINT que loads up as well and I manually purge from here - but I shouldn't have to and my operations manager is looking into that issue.
Hope this helps,
Dave Schlieder
B7332 SP 15 AS/400 NT
Ed,
Funny you should resurrect this thread now! I just finished sitting down with our operations manager of the AS/400 and showed him how to clean up the printqueue!
A little background. When we updated to SP 15, we started having an issue with random UBEs ending in an error with a "Object label badly formatted" message in the job log. After going round and round with tech support, they finally suggested that we add to our INI file "UBEUSEAdobe=1". Well, that solved our problem. However a few weeks later I noticed that the number of members of our printqueue on our AS/400 was not decreasing when I deleted jobs from the OW Work With Servers screen! It always did before. Standard JDE, fix one issue, create another. So back to tech support. Yes, they could duplicate it and issued SAR 5293703 for SP 16.1, but in the meantime I needed a solution as we run well over 2,000 UBEs a week (We may not update to SP 16.1 for months yet). And the only way I had at the time was manually from the green screen, typing in 4s. So I wrote this CL (Hope you can read it from this post):
*************** Beginning of data **************************************
PGM PARM(&STRDATE)
DCL VAR(&STRDATE) TYPE(*CHAR) LEN(6)
DCL VAR(&SELECT) TYPE(*CHAR) LEN(50)
DCLF FILE(QGPL/PQDOIT)
CHGVAR VAR(&SELECT) VALUE('MLCDAT *LE ' || '''' || +
&STRDATE || '''')
DSPFD FILE(B7332SYS/PRINTQUEUE) TYPE(*MBRLIST) +
OUTPUT(*OUTFILE) OUTFILE(QGPL/PQPURGE)
OPNQRYF FILE((QGPL/PQPURGE)) QRYSLT(&SELECT)
CPYFRMQRYF FROMOPNID(PQPURGE) TOFILE(QGPL/PQDOIT) +
MBROPT(*REPLACE) CRTFILE(*YES)
CLOF OPNID(PQPURGE)
RUNQRY QRY(QGPL/PQDOIT)
LOOP: RCVF
MONMSG MSGID(CPF0864) EXEC(GOTO CMDLBL(END))
SBMJOB CMD(RMVM FILE(B7332SYS/PRINTQUEUE) +
MBR(&MLNAME)) JOBQ(QGPL/QBATCH)
GOTO CMDLBL(LOOP)
END: ENDPGM
****************** End of data *****************************************
The query is pretty straight forward. Based on the file created from the DSPF command, it selects out the members older than the date passed in. BEWARE: THERE IS NO ERROR CHECKING! The date format is 'YYMMDD' and needs single quotes around it to work. So today is PARM('010725'). If you inadvertently typed in '072501', 'MMDDYY' format, it would delete EVERY member of the printqueue. SO USE WITH CARE!
I also find it necessary to clean up 2 other areas.
The Integrated File System is where the job and job debug logs are kept. These are often times orphaned when deleting jobs from OW and there are logs in there from the kernals which you will never see in the submitted job search screen. So I use Windows Explorer to select out all old logs from there to delete after deleting jobs from OW.
I also review all the output queues (WRKOUTQ) on the AS/400 - our QPRINT que loads up as well and I manually purge from here - but I shouldn't have to and my operations manager is looking into that issue.
Hope this helps,
Dave Schlieder
B7332 SP 15 AS/400 NT
Thai
Member
RE: RE: Outq Managment
I want to know that too.
Thai Nguyen
J.D. Edwards System Admin.
email: [email protected]
I want to know that too.
Thai Nguyen
J.D. Edwards System Admin.
email: [email protected]
daneppich25
Member
Re: RE: Outq Managment
I would be interested in seeing that CL as well.
B7332 Coex/sp11.3(15.1 in Dev)
I would be interested in seeing that CL as well.
B7332 Coex/sp11.3(15.1 in Dev)
Solack
Active Member
Re: RE: Outq Managment
Thanks,
This will be very helpful. I am new at this whole thing, so I may have questions later, but I should be able to find answers through other resources. Thanks Again.
ed solack
Ed Solack
OW-XE SP13.1/ES-As400/DEP-Nt4.0 Sql7.0/Citrix TS
Thanks,
This will be very helpful. I am new at this whole thing, so I may have questions later, but I should be able to find answers through other resources. Thanks Again.
ed solack
Ed Solack
OW-XE SP13.1/ES-As400/DEP-Nt4.0 Sql7.0/Citrix TS
