Vvfusionp

[rsnell]

We are using the latest version of Valence 6.3. I've noticed that we have a lot of VVFUSIONP jobs running. If I have to restart the server, I'm having to manually end what could be hundereds of VVFUSIONP jobs. Is there a better way to manage these? Are they just orphaned jobs?

Thanks,

Ray

[robert.swanson]

Each interactive Fusion5250 session will spawn a dedicated VVFUSIONP job to service it. The job will self-terminate when one of the following occurs:

• the user logs off, terminates their session or closes the Fusion window
• the Valence instance is ended via command VVSTOP
• the Valence instance is restarted via command VVSTART
• the interactive job is manually terminated

There is a "reserve" of Fusion jobs (configured in Settings, default is 3) that are kept alive to immediately connect any users initiating a new session. If you terminate the Valence instance manually (meaning, not using VVSTOP), those reserve Fusion jobs, along with all active 5250 sessions running in Fusion, will stay active until manually terminated. Hence it would be highly advisable to use the VVSTOP and/or VVSTART commands to end your Valence instance when necessary.

By default, the Fusion5250 jobs all run in the same QHTTPSVR subsystem as the Valence CGI jobs. If you're using Fusion regularly at your site, it is recommended you alter the configuration such that the Fusion jobs all run inside their own subsystem. You can find instructions for that here:
Configuring the Fusion5250 Server-Side Jobs

[rsnell]

OK. Thanks. I'll give that a try.

Can I use that same subsystem across all environments? Do I use the same or different ports?

[robert.swanson]

Yes, you can have all your Valence instances run their Fusion5250 jobs in the same subsystem (the job name will match the instance name), but each instance must have a unique port for the Fusion connection.