This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
>From: Local Data Manager <address@hidden> >Organization: UCAR/Unidata >Keywords: 200409202219.i8KMJknJ026598 > >Hello. > >I am upgrading GEMPAK from 5.6j to 5.7.2p2. I am unclear on how to alter the > pqact.conf in order to make the most of these changes. Simp[ly installing th > e pqact.conf generated by the script in the new GEMPAK distribution has no af > fect. > >Any help is appreciated. > >Thanks. > >Pat > > > -- Pat, The pqact.conf lines generated from the GEMPAK script can be installed (merged or copied) to your ~ldm/etc/pqact.conf file. When changes are made to your pqact.conf file, use the LDM commands: ldmadmin pqactcheck ldmadmin pqactHUP to check your pqact.conf, and notify your running pqact process to reread the configuration file respectively. Alternately, if your pqact.conf file is complicated with many processing actions for other packages etc, then you can create separate "exec" lines in the LDM's etc/ldmd.conf to run different pqact processes for separate pqact.conf files generated from gen_pqact.csh so that when upgrading GEMPAK, you don't have to modify merge GEMPAK lines in with your other actions. Steve Chiswell NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.