New parm in VVINSTMGR with 6.4?

[mguske]

Yesterday, I downloaded and installed the VALENCE6 instance for 6.4.
Now I am trying to convert my Test instance to 6.4 and I'm getting the following error:
CALL PGM(VVINSTMGR)
Function check. CPF1015 unmonitored by VVSRVPGM at statement 0000384900,
instruction X'0000'.
The call to VVKEYMGR_V ended in error (C G D F).?
In my conversion program, I have the following code:
chgvar &Action 'deleteInstance'
chgvar &Instance 'SPACEREG'
Chgvar &ToInst ' '
Chgvar &ToType ' '
Chgvar &ToPath ' '
Chgvar &ToPort 0
Chgvar &ToNote ' '
Call VVINSTMGR parm(&Action &Instance &ToInst &ToType &Topath &ToPort &ToNote)?
Is there a new parm in VVINSTMGR for 6.4?

[robert.swanson]

Hi, there is an extra character parameter at the end of the parm list for VVINSTMGR, but it's optional and that shouldn't be causing this. I suspect what you're seeing is a library list issue... Does your library list include any Valence 6.3 objects?

[mguske]

So, the eighth optional parm is 1 character?

I don't believe I have any 6.3 objects:
Library Type Text
SPISYS SYS IBM System Files changed by SPI
QSYS SYS System Library
QSYS2 SYS System Library for CPI's
QHLPSYS SYS
QUSRSYS SYS System Library for Users
VALENCE6 USR
QTEMP USR
SPI_PTF USR Temporary Fix library
QGPL USR General Purpose Library
SIERRA USR General Accounting FILES lib
OBJECT USR General Accounting OBJECT lib

?What is going on at this statement in VVSRVPGM:
unmonitored by VVSRVPGM at statement 0000384900

[mguske]

Just for kicks, I added a one-character parm to the VVINSTMGR call and got the same error.

[mguske]

I also found these "VV" objects in the QSECOFR library list:

Object Type Library Attribute Text
VVEXPORT *LIB QSYS PROD
VVIMPORT *LIB QSYS PROD
VVFUSION *JOBQ QGPL SPACE Fusion5250 Job Queue
VVFUSION51 *JOBQ QGPL SPACESAND Fusion5250 Job Qu
VVFUSION *JOBD QGPL SPACE Fusion5250 Job Descri
VVFUSION *CLS QGPL SPACE Fusion5250 Job Class
VVFUSION *SBSD QGPL SPACE Fusion5250 Subsystem?

[robert.swanson]

I think we'll need to get on a meeting to see what's happening there, as I just created a test program to make the call with your same parameters and it worked fine.

I'll reach out to you directly to set something up.

[mguske]

I'm out of the office until Wednesday, next week. We can follow up with it then. Thanks!

[mguske]

I ended up manually shutting down the Instance before running my conversion program. That seemed to be the issue.
VVINSTMGR doesn't shut down the instance when the 'deleteInstance' Action is specified?
I have updated my notes.

[robert.swanson]

Ah, that would explain why we couldn't replicate it. Yes, you must stop the instance (so there are no object locks) before you call VVINSTMGR directly to update or delete it. The front-end app checks this before calling the program. Glad you got it resolved.