Message when compiling Value of 0, for number of message types, not valid.

[brett.elston]

Hi Folks,

We have just upgraded to 5.12 but now receive the message Value of 0, for number of message types, not valid when trying to compile.

The full message is:-
Message . . . . : Value of 0, for number of message types, not valid.
Cause . . . . . : You attempted one of the following:
-- You specified a non-zero value for the number of message types when
requesting to move a single message by key.
-- You specified a value for number of message types which is not valid
when requesting to move messages by type.
Recovery . . . : Do one of the following and try the request again:
-- Specify zero for the number of message types if you are requesting to
move a single message by its message key.
-- Specify a value for the number of message types which is from 1 through
4 if you are requesting to move messages by type.

This is new to us? Please could you assist? We have obviously missed something? No complie listings either so not sure sure which way to go.

Your assistance would be much appreciated.

Kind Regards

Brett

[Scott Klement]

Never heard of anything like this or anything even similar to it. Please file a support ticket so we can work with you to look into it.

[brett.elston]

Thank you Scott, also never seen anything close to this this. Ticket submitted.

[brett.elston]

Hot sure if this helps buts its from the UI compile joblog..
Member CHAIN3 not added to file QPUILEINC in QTEMP.
Member CHAIN3 already exists in file QPUILEINC in library QTEMP.
Member CHAIN3 not added to file QPUILEINC in QTEMP.
Member OPEN1 added to file QPUILEINC in QTEMP.
Object QRPGLEMSG in library *LIBL not found.
Problem log updated.
Output queue QSCAPAROQ in QSC4563076 already exists.
Message file QRPGLEMSG in *LIBL not found.
Application error. CPF2407 unmonitored by QRN4CPP at statement
0000000019, instruction X'0000'.
Value of 0, for number of message types, not valid.
Value of 0, for number of message types, not valid.

[emhill]

Sounds like a library list issue??? Maybe?

[Scott Klement]

It turns out he's still using the old preprocessors that we created for V5R3 and V5R4. Simply adding the IBM QDEVTOOLS library to the library list appears to resolve the problem, but the best solution is to start using Open Access.

[brett.elston]

A big thanks to the support team at Profound. It turns out we were on V7R1, without the required PTF’s. Full support for the newest versions only started on V7R2. We upgraded to V7R3 and everything is working.