• If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Announcement

Collapse
No announcement yet.

Call VVFUSIOND job “Address already in use”

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Call VVFUSIOND job “Address already in use”

    Hi, the following job (Call VVFUSIOND) gets submitted randomly after some of our Valence Apps complete processing. The job ends with end code 20 with the message “Address already in use”.
    I have copied a part of the job log below.

    Could you please let us know what’s causing this job to get submitted?


    Message . . . . : Job 604077/QTMHHTTP/V6QAC submitted.
    Cause . . . . . : Job 604077/QTMHHTTP/V6QAC submitted to job queue QZHBHTTP
    in QHTTPSVR from job 591053/QTMHHTTP/V6QAC. Job 604077/QTMHHTTP/V6QAC was
    started using the Submit Job (SBMJOB) command with the following job
    attributes: JOBPTY(5) OUTPTY(5) PRTTXT() RTGDTA(HTTPWWW) SYSLIBL(QSYS
    QSYS2 QHLPSYS QUSRSYS) CURLIB(V6QAC) INLLIBL(V6QAC) INLASPGRP(*NONE)
    LOG(4 00 *NOLIST) LOGCLPGM(*NO) LOGOUTPUT(*JOBEND) OUTQ(/*DEV) PRTDEV(PRT01)
    INQMSGRPY(*RQD) HOLD(*NO) DATE(*SYSVAL) SWS(00000000) MSGQ(QUSRSYS/FAIZS)
    CCSID(37) SRTSEQ(*N/*LANGIDSHR) LANGID(ENU) CNTRYID(US) JOBMSGQMX(64)
    JOBMSGQFL(*WRAP) ALWMLTTHD(*NO) SPLFACN(*KEEP) ACGCDE(MINT).

    Message . . . . : -CALL PGM(V6QAC/VVFUSIOND)

    From module . . . . . . . . : VVFUSIOND
    From procedure . . . . . . : ENDD
    Statement . . . . . . . . . : 44700
    Message . . . . : Address already in use.
    Cause . . . . . : No additional online help information is available.

    Message . . . . : Job ended. Cancel message received at command processor.
    Message . . . . : Job 604077/QTMHHTTP/V6QAC ended on 05/23/22 at 11:55:07;
    .018 seconds used; end code 20 .

    Thank you

  • #2
    It appears you've got two separate instances attempting to use the same Fusion5250 port.

    In your QAC instance, you can go to Portal Admin > Settings > Fusion5250 Settings and either (1) turn off Fusion in that instance by unchecking the "Service Active" checkbox, or (2) change the listener port to another value that isn't in use in one of your other instances.

    Comment


    • #3
      Changing the Fusion listener port in QAC/Test resolved the issue.
      Fusion in both QAC/Test and Production were listening on the same port.

      Thank you for your help

      Comment

      Working...
      X