On Dazel 3.3 job databases tend to grow very large, sometimes up to 200 or 300 MB per JQM. Stopping or starting the JQM won't solve this problem; you'll have to recreate the JQM:
Stop the JQM:
# stop_server jqm
Delete the JQM:
# config_server -d jqm
Don't worry about the delivery pathways, the CM will still hold their configurations.
Recreate the JQM:
# config_server -t JQM jqm
If you have a special start order for the JQM, set it now:
# config_server -u -x"server-start-order 700" jqm
This will bring back the job database to approximately 400 KB.
HPOS users may have wondered: is there still development on HP Output Server? The release of HPOS 3.5 in January 2006 surely is a proof of the continuing development on HPOS. HP has given a five year commitment for HPOS in the summer of 2005 to continue development and marketing of the product (A few years ago, this wasn't the case).
Windows is a supported platform for running HP Output Server. However, the intial development on HPOS takes place on the UNIX environment, and is also seen as the correct environment to run HPOS on. The UNIX environment is usually tested a lot more thourougly than the Windows environment. You can use the Windows server version of HPOS as a test environment; just don't run your production system on it. However some customers use Windows environments though. Unix is typically more stable.
Configuration: AIX 5.2, maintenance level 1 and Dazel 3.3, Service Pack 9.
Problem: sysdumpdev -e shows increasing usage of the system dump device. Eventually the dump device needed, grows to 1200 MB, after which the server becomes unresponsive and a reboot is the only solution.
Even though HP suggests using maintenance level 1 for AIX 5.2, try using maintenance level 2; after loading ML2, this problem is gone; it's an AIX bug with a memory leak in the TCP/IP stack, which is solved in ML2.
What it does, is very simple: it creates a web page that shows an overview of the jobs which passed through HP Output Server.
What do you need to accomplish this?
The Event Monitor (EM) of HP Output Server, which is usually running anyway in any HP Output Server environment.
A subscription file, in which you register what events to react to.
A Description file, which formats the incoming events into HTML output and writes it to a file.
An HTML header file, used as an header for the webpage; this one is created automatically by the following:
An original HTML header file, which is used to create the HTML header file.
An HTML header update script, which updates the HTML header file, from the original HTML header file. It updates the date and number of succesfull jobs.
An EPOD update script, which updates the webpage.
Perl script web_server.pl, which is included in the HP Output Server distribution. This perl script is the (small) webserver (You can also use the Apache webserver, in case you have the WebGUI installed).
An EPOD clear log script, to empty the EPOD log once a week.
Start and stop scripts for this EPOD web monitor.
Put all of these items in a separate directory, e.g.: /appl/hpos/epod
# epod.desc
# support file for HPOS Epod logging
# see also EPOD.SUBS for event subscriptions
# This file generates HTML coded logging and can be viewed with
# the web_server.pl script
# Initialize HP Output Server environment
# Change to wherever your setup_env.sh file is.
. /appl/hpos/etc/setup_env.sh
set itext $instance
does $instance
# all abort messages (blue)
match ..1.0.10175.1.0.0.6.121.*
set itext <font color=Blue>
endmatch
# all error messages (red)
match ..1.0.10175.1.0.0.6.122.*
set itext <font color=Red>
endmatch
# all warning messages (black)
match ..1.0.10175.1.0.0.6.123.*
set itext <font color=Black>
endmatch
# all report messages (green = good)
match ..1.0.10175.1.0.0.6.124.0
set itext <font color=Green>
endmatch
Okay, so now we have a file, which listens to certain events (epod.subs), and a script (epod.desc) that formats it into HTML output and writes is to file epod.log. Now on to the header of the webpage:
This HTML header file is a fancy header. It shows information about the number of jobs succesfully processed, the current date and the creator of the page. It refreshes every 3 seconds.
You need a script to update this HTML header file with the current date and number of jobs:
HTML header update script
This is called update-htmlheader.sh:
# update-htmlheader.sh
# replace string <!--kkkk--> in file htmlheader for the number of jobs
now=`date`
nrjobs=`grep -i green /appl/hpos/epod/epod.log* | wc -l | awk '{print $1}'`
totjobs2=`cat /appl/hpos/totjobs | awk '{print $1}'`
let nrjobs="$nrjobs+$totjobs2"
cat /appl/hpos/epod/htmlheader.org | sed "s/<!--kkkk-->/$nrjobs jobs since 28-07-03. ($now)/g" > /appl/hpos/epod/htmlheader
This script above uses a file named totjobs which is nothing more than a plain file containing the total number of jobs since last week. This file is created once a week by the Clear EPOD log script (see further down below).
Now, to put this together, we need a script that creates the webpage by putting in the header and adding a tail of the epod.log file. The next script updates it a 100 times, with pauses of 3 seconds in between and then exits:
EPOD Update script
Filename: epodupd.sh
#!/bin/ksh
unset result
result=`ps -ef | grep epodupd | grep -v grep | grep -v $$ | wc -l | awk '{print $1}'`
# check if i am running
if [ $result -gt 0 ]
then
exit
fi
let teller=0
while [ $teller -lt 100 ]
do
cat /appl/hpos/epod/htmlheader > /appl/hpos/epod/epodhtml2.log
tail -r -35 /appl/hpos/epod/epod.log >> /appl/hpos/epod/epodhtml2.log
mv /appl/hpos/epod/epodhtml2.log /appl/hpos/epod/epodhtml.log
sleep 3
let teller="$teller+1"
done
Now, the web page is created. We need to make sure the file epod.log doesn't fill up the complete file system, by clearing its contents and writing the number of succesful jobs to file totjobs once a week.
Clear EPOD log script
Filename: clear_epod_log.sh
#!/bin/ksh
# Little script to clear the epod.log file
# base directory for this script
base=/appl/hpos
# number of succesfully completed files this week
complete=`grep -ci green $base/epod/epod.log | awk '{print $1}'`
# number of succesfully completed files before this week
compl=`cat $base/totjobs | head -1 | awk '{print $1}'`
# add those two
let total=0
let total="$total+$compl"
let total="$total+$complete"
# save the previous total
cp $base/totjobs $base/totjobs.old
# clear the log file
cp /dev/null $base/epod/epod.log
# write the new total to totjobs
echo $total > $base/totjobs
Put this script into your root crontab:
# Clear the epod log once a week on Sunday
0 0 * * 0 /appl/hpos/epod/clear_epod_log.sh 2>/dev/null
Make sure epodstart.sh is also somewhere in the startup script of your HPOS environment, so it gets started as soon HPOS is started. The same goes for your stop script.
The PERL web_server.pl is a modified web_server.pl file, from the Snapshot2 feature of HPOS. It listens to port 8089. You can download this PERL web server here.
Once the EPOD Web Monitor has started via epodstart.sh, you can browse the page: http://[hostname-of-your-hpos-server]:8089
The web page should look like this:
Now, you have a GREAT way of monitoring your system! Green entries are jobs succesfully ended. Any other colors show problems occured, or queues cleaned or whatever.
For any further description of the HPOS EPOD, check out the HPOS System Administration Guide, Appendix D.
Dazel is the former name for what is now known as HP Output Server (HPOS), part of the HP Output Management suite.
Hewlett Packard (HP) bought Dazel Corporation in 2001.
HPOS is an output management system: its task is to centrally manage the output of complete enterprises, whether it is printed output, e-mail, fax, paging, web or file delivery, and so on. It provides a means for cross-platform management of output.
Currently, HPOS is supported on AIX, HP-UX,
Sun Solaris, Windows 2000/2003 server and Linux (Red Hat Enterprise Linux ES and Suse Linux Enterprise Server). Also several add-on's are available, such as Output Managers for SAP or Oracle applications.
The most current version of HPOS is version 4.0. Support for versions 3.3 and 3.4 have ended in July 2007. The main difference between versions 3.5 and previous versions is, that version 3.5 uses a MySQL database to store its data, where older versions uses a proprietary flat file database (Velocis).
Version 3.5 of HP Output Server has been released in December 2005. A new accompanying course was also released. Version 3.3 has proven to be a very stable version. Version 3.4.1 was the first version to use MySQL for its database and has known some issues. Most customers have either stayed on version 3.3 or moved to version 3.5. With the release of 3.5, the support for 3.4.1 ended in 2006, and customers were requested to move to version 3.5.
For Windows users client software is available, known as HP Output Envoy. Also, for HPOS system administrators, an extended Envoy package is available, known as HP Output Explorer.
From July 2006 no more service packs will be released. Instead of SP's, Maintenance Releases will be made. This means that these will not only contain fixes, but also new additional functionality and new printer drivers. In March 2006 the Linux Server version was also released for Red Hat Enterprise Linux ES 4.0 and Suse Linux Enterprise Server 9 SP2. And in July 2006, a new WebGUI was introduced. First step in this, is to provide for a WebGUI for job management. Later on, the WebGUI will become a full administration GUI for HP Output Server. Probably the Windows HP Output Explorer tool will no longer be needed by then. In July 2006 also a sftp (Secure FTP) destination was made available, besides the already available regular FTP destination.
Advantages of using HP Output Server:
Scalability of output management.
Central management and monitoring of all output in the enterprise.
Reliable delivery of output, including tracking information and confirmation of successfull completion.
A single administrator is usually enough for large organizations; without Output Server more staff would be necessary; thus Output Server reduces costs of output management.
Requires only one printer driver (Envoy) on a Windows client, which reduces testing efforts.
Ability to transform output as required.
Configurable to work with Oracle and SAP.
Support for many devices, both HP and third-party.
Accounting and auditing of output possible.
Runs on several operating systems and accepts output requests from a variety of client sources.
Number of results found for topic HP Output Server: 16. Displaying results: 11 - 16.
.
Dazel is the former name for what is now known as HP Output Server (HPOS), part of the HP Output Management suite.
Hewlett Packard (HP) bought Dazel Corporation in 2001.
