OCD processes

[Ted Flanders]

I was having problems with a lot of my printers. My support told me that we needed to (re)parse our OCD's. We did this with a -k at the end of the command. Can anyone explain to me (where I can understand it) what an OCD process is, does? What happened to them where we had to reparse them? What caused that?

[Rodney Hills]

OCD is part of DDFA. DDFA is used to create /dev entries that can be used to access remote devices. For instance if you have a DTC with a serial printer on one of the ports, you would use DDFA to define a /dev entry that can be used by an hpux command as an output device.

The OCD processes itself it picks up any output sent to the /dev entry and then handles the necessary communication to the remote device.

Hope this helps...

-- Rod Hills

[S.K. Chan]

Hope this helps a little .. (see attached doc). I've not been dealing with DTC for a while, let me re-collect my thought and post more info as it comes to me.

[S.K. Chan · Accepted solution]

Can anyone explain to me (where I can understand it) what an OCD process is, does?
==> My first posting with the attached doc should answer this.
What happened to them where we had to reparse them? What caused that ?
==> What it means is you'll have to run this ..
# /etc/dpp /etc/ddfa/dp -k
ie "re-read" the DTC config file "dp", each DTC definition in that file will have an ocd process tie to it, sometimes that process dies in order to restart it you have to re-parse the "dp" file. Take a look at the dp file and then do ..
# ps -ef|grep ocd
You will see what I mean. When you run the "dpp" command any error if found will be flaged, so keep a close watch. Also take a look at /var/adm/syslog/syslog.log for and logged ocd error.

Hope this helps ..